Jul 08
    2011

    System Manager + Session Manager

    Daniel Hofmann
    [ITK communications GmbH]
    Hi everyone,

    I have some problems with the replication node from System Manager to Session Manager. I've updatet the Session Manager to 6.1 SP3 and after this the replication node didn't show up anymore. After this I've used the "initTM" command on the Session Manager to reconfigure this node, but it only came up with the following error:

    Register replica node with System Manager DRS master failed.

    I didn't found any information about this error on the net. Maybe someone could help me with this?
    Thanks in advance.
    Renato Nel
    [Inovo Telecom]
    Hi,

    Did you add the host names in the /etc/hosts file?

    You should add the host names in this file on both system and session manager. (I think system manager's hosts file is updated automatically during installation, but just check them both). Then restart both servers, and run the initTM and initDRS again.

    This should solve the issue. Let us know what happens.
    Daniel Hofmann
    [ITK communications GmbH]
    Hi,

    thank you for your reply. In the hosts file of the Session Manager the host name of the System Manager already exists. If I try to connect to the System Manager with putty, I'm not able to use any user to logon. If I try to logon with the "admin"-user and any password (admin01, avaya123, or the admin password of the web-page), it always tells me "Access Denied".

    The initDRS command came up with the following error: "Unable to initialize DRS database replication"

    :( *sigh*
    Jeff Milletary
    [SOHO]
    How about craft/craft01

    Hi,

    thank you for your reply. In the hosts file of the Session Manager the host name of the System Manager already exists. If I try to connect to the System Manager with putty, I'm not able to use any user to logon. If I try to logon with the "admin"-user and any password (admin01, avaya123, or the admin password of the web-page), it always tells me "Access Denied".

    The initDRS command came up with the following error: "Unable to initialize DRS database replication"

    :( *sigh*
    Jeff Milletary
    [SOHO]
    Do you remember what you set the enrollment password and maybe re-enter also if you are able to gain access are the dates correct on both SM and SMGR?

    Hi,

    thank you for your reply. In the hosts file of the Session Manager the host name of the System Manager already exists. If I try to connect to the System Manager with putty, I'm not able to use any user to logon. If I try to logon with the "admin"-user and any password (admin01, avaya123, or the admin password of the web-page), it always tells me "Access Denied".

    The initDRS command came up with the following error: "Unable to initialize DRS database replication"

    :( *sigh*
    Arslan Ali
    Check on System Manager if Enrollement password is expired?
    Daniel Hofmann
    [ITK communications GmbH]
    Hi,
    craft/craft01 didn't work. I've also checked the enrollment password and also re-set it (it wasn't expired), but always the same error.
    We reported this to Avaya and I'm waiting for an answer now.
    Thanks to all, so far.
    damir sincek
    [AvatelIP]
    Do you have System Manager and Session Manager on the same service packs?
    I had System Manager 6.1 on SP1 and Session Manager 6.1 on SP3 and I had same problem as you, after I install on both same service pack, replication started do work.
    Gary Rogerson
    [Fluor Enterprises]
    Yes, make sure System and Session Managers are at the same release / version. The default user / pass for System Manager is admin / admin...yes, it's different from the standard Avaya passwords (root01, craft01, etc...).

    Also, as stated before, make sure both System and Session Managers have each others DNS and IP Addresses in their /etc/hosts file. The Session Manager address in the host file should be the Management Interface address, not the Security Module IP Address.

    Once you validate the above, you can try re-running the initTM. If you still get an error, you can try running upgradeSM and point to the SM 6.1 SP3 Installer; to run the whole install over.

    ...And make sure the Enrollment Password is valid on System Manager.

    Either way, one you have done any of the above, reboot System Manager, then Session Manager. Once both are completely up (May take up to 20 minutes), log into Session Manager and run: statapp

    It should look like this:
    [[login to unmask email] ~]# statapp
    Watchdog 9/ 9 UP
    logevent 26/ 26 UP
    ncsd 4/ 4 UP
    postgres-db 24/ 24 UP
    sm-mgmt 232/232 UP
    sipas-MS 123/123 UP
    sipas-SD 141/141 UP
    sipas-SH 284/284 UP
    sipas-LH 30/ 30 UP
    sipas-CDR 30/ 30 UP
    sal-agent 67/ 67 UP
    secmod 1/ 1 UP

    The only service that should come back as "DOWN" is: sipas-LH. If you have several that are down, then there is still something wrong. You can use: start -s sipas-XX or what ever the down service name is to try and start the down service.

    If all that still does not resolve your issue, there are several additional things to validate / check, but I will wait to hear back before I list those.
    Gary Rogerson
    [Fluor Enterprises]
    Ok, here's a link to a thread that goes into more detail on the various config parts for System and Session Managers

    [URL="http://www.avayausers.com/showthread.php?t=32634&highlight=Session+Manager"]http://www.avayausers.com/showthread.php?t=32634&highlight=Session+Manager[/URL]
    Gregory Gleason
    [Avaya]
    I find that re-running SMnetSetup on ASM is the only thing to fix this sometimes. Make sure the host name you give ASM matches the FQDN that's configured on the SMGR, as it verifies that information within the TLS cert from SMGR.
    Marten Soderberg
    [Tele2 Integration Services]
    Hi,

    I trying to get a new install of SM+SMGR to work.
    I have installed two servers with system platform and installed the template for SMGR and configured it for failover. The failover is working.
    I have then installed two SM servers. The /etc/hosts files on all systems are checked and double checked. The SMGR server have the fqdn and host name for itself and and both the SM servers (not security model). The SM servers have fqdn and host name for itself and the smgr server. Everything is pingable with dns names.
    In SMGR I get error messages when I try to test the communication (couldn't connect to server).

    Attached are screenshots of the versions for SM and SMGR as well as a couple of error messages.

    When I'm logged in to the SMGR and trying to administrate the Domain, SIP entity of Session manager administration suddenly the webpage stops to respond. And then I get "Internet Explorer cannot display the webpage".
    I then try to access the system platform and get the same result. Meanwhile both system platform and SMGR remains pingable and after a couple of minutes I can log in to SP and after a couple of more minutes I can log in to SMGR again.
    I use the latest System platform release and lates service pack for system platform, as well as latest and greatest for SM and SMGR.

    I would appreciate any input to my issues.

    regards

    Mårten
    Gary Rogerson
    [Fluor Enterprises]
    What version of System Platform are you running on System Manager? There are soooo many parts to check in getting the basic setup working, but this sounds more like a problem with System Manager...considering the loss of connectivity to the web-interface.
    Marten Soderberg
    [Tele2 Integration Services]
    System platform is version 6.0.3.0.3 with vsp_patch 6.0.3.1.3

    //Mårten
    Gary Rogerson
    [Fluor Enterprises]
    If you are consistently getting the web-interface crashes / errors in SMGR and in VSP, then I would probably just reinstall System Platform and reload System Manager. Then apply the System Platform patches and service packs for System Manager, then try the ./SMnetSetup.sh again on Session Manager.

    You can PM me your e-mail address and I will send you my notes / screen shots on my setup.
    Marten Soderberg
    [Tele2 Integration Services]
    Thanks, I would appreciate that.
    marten.soderberg(at)tele2.com
    Marten Soderberg
    [Tele2 Integration Services]
    I have now re-installed the system again without success.
    When I try the initTM is succeded, but the rest fails

    Mon Aug 29 16:18:25 CEST 2011: Trust Management Initialization started.
    Mon Aug 29 16:18:26 CEST 2011: Trust Management Initialization of SIP A/S started.
    Mon Aug 29 16:18:37 CEST 2011: Trust Management Initialization of SIP A/S completed.
    Mon Aug 29 16:18:37 CEST 2011: Trust Management Initialization of Session Manager started.
    Session Manager trust already established, skipping
    Mon Aug 29 16:18:37 CEST 2011: Trust Management Initialization completed successfully.
    Stopping all components
    ...........................................................
    Mon Aug 29 16:19:43 CEST 2011: Register replica node with System Manager DRS master started.
    Sending configurations to master node
    IOException occurred in getMBeanConnection()
    ERROR # 1 : Unable to perform Aggregation, Terminating the configuration...................
    Starting all components
    .
    Mon Aug 29 16:19:44 CEST 2011: Register replica node with System Manager DRS master failed.
    Nico Knook
    [Avayasupport.nl]
    When I'm logged in to the SMGR and trying to administrate the Domain, SIP entity of Session manager administration suddenly the webpage stops to respond. And then I get "Internet Explorer cannot display the webpage".
    I then try to access the system platform and get the same result. Meanwhile both system platform and SMGR remains pingable and after a couple of minutes I can log in to SP and after a couple of more minutes I can log in to SMGR again.
    I use the latest System platform release and lates service pack for system platform, as well as latest and greatest for SM and SMGR.

    I would appreciate any input to my issues.

    regards

    Mårten

    Hi Mårten,

    If you have a duplicated system-manager with redundant power supplies, but only one PSU per machine is actually connected to power, the system will interchange indefinitely with errors such as "critical psu failure".
    I believe this is a bug, for which we opened a case with Avaya. Either remove the second PSU or connect it to mains to work around this. And open a case with Avaya (the more the merrier, lol).

    Cheers,
    Nico
    Gary Rogerson
    [Fluor Enterprises]
    Hmmm, interesting and a good find! So, I wonder...what if you had only one SMGR, but two power supplies and only one of the power supplies connected?
    Nico Knook
    [Avayasupport.nl]
    Hi Roger,
    Hmmm, interesting and a good find! So, I wonder...what if you had only one SMGR, but two power supplies and only one of the power supplies connected?
    My guess is it would only generate critical PSU alarms as it has been proven to be quite hard to interchange a simplex system, lol ;) It is possible it will restart the VPS but that would not make much sense to me. The interchange on a duplex system at least has a chance of the backup system having both PSU's connected/in service. But the only way to know is to try. Maybe next week if I have some spare time.
    What I've seen happening is that the alarm is raised right after startup of SMGR on the primary, and then after 10-15 minutes it escalates and the system interchanges, where on the stand-by the same thing happens and it switches back again. This goes on until you connect the second PSU or (I assume, haven't tried) remove the second PSU from the machines.
    I'm using the same versions as Mårten btw.
    Cheers,
    Nico
    Miky Sac
    [Focus]
    Hi Marten,

    Look in the logs on both Session Manager & system manager when you run the initTM. Best is to do a tail -f on symmetric.log in the /var/log/Avaya/mgmt/drs/ folder. This will show you the exact error.

    Cheers,

    Miky
    Marten Soderberg
    [Tele2 Integration Services]
    The issue is now solved. The problem was that I had ran the initTM so the certificates from the SMGR was transferred to SM. When I upgraded SMGR to the correct version the Certificate was already there. So after lookin to the initTM shell script we found out that a xml file is created when running initTM.
    We renamed that file and ran the initTM again. After that the initDRS worked when the system was connected to the customers network and could reach the DNS.

    I believe that the xml file was called truststore.xml or something similar.
    Renato Nel
    [Inovo Telecom]
    This is valuable information. Thanks for sharing
    Gary Rogerson
    [Fluor Enterprises]
    Yes, that also explains some past issues as I have installed SMGR / SM many times between versions 5.x and 6.x! THANKS, now I need to add that to my notes!
    Phillip Ganoe
    [NetVersant]
    So the file you are looking for is:
    /opt/Avaya/jboss-4.2.3.GA/server/smmgmt/conf/tm/TMClientInv.xml
    I did "mv TMClientInv.xml TMClientInv.xml1" , I suppose you could rm it too, but I not that brave.
    After that InitTM went right through and DRS after that.
    Thanks for the pointer MSoderberg
    PG
    Graziano Soccio
    [Delco spa]
    Hi everyone
    I have problem accessing system platform at customer site, I changed default password for admin, and created a new login advanced admin, but i'm not able to access with neither, not even cust.... I tryed even on SSH wirh root but nothing no way in
    can somebody help please
    Nigel Cornes
    [CCT]
    Hi mate
    Might be just aswell to reinstall system platform.
    It only takes 30 mins or so
    Rgds
    Gary Rogerson
    [Fluor Enterprises]
    What version of System Platform are you running? Also, I would agree to just reinstall.
    Nigel Cornes
    [CCT]
    Hi it really depends on what vm your installing. They seem to have different versions for CM,AES SMGR etc
    In my case I had smgr as the vm and my system platform version was 6.0.3.3.3
    Rgds
    Angelo Borbe
    [Middle East Telecom]
    I'm getting the same problem. My platform is:

    SP 6.0.2
    SMGR 6.1.0
    SM 6.1.4

    I noticed that I also am getting the following errors in setting up the SM...
    1. this error...
    Tue Jan 3 12:17:34 AST 2012: Register replica node with System Manager DRS master started.
    Sending configurations to master node
    MBeanException occurred while invoking operation :: NotifyXML
    ERROR # 1 : Unable to perform Aggregation, Terminating the configuration...................
    Starting all components
    .
    Tue Jan 3 12:17:45 AST 2012: Register replica node with System Manager DRS master failed.


    This could most probably be the reason why I cannot see Replica Node in the SMGR for replication procedure.

    2. Prior to getting the above error, I'm getting...
    "Ping of System Manager at xxx.xxx.xxx.xxx failed."

    (Dono if it will work without connection to the live DNS server. I'm doing the installation offline.)

    3. The SM100 status is "DOWN" in the "Home / Elements / Session Manger / System Status / Security Module Status - Security Module Status" although the status "Up" in "Home / Elements / Session Manger / Dashboard - Dashboard".

    Tomorrow, Im planning to re-install everything:

    a. Starting with SP to SP 6.0.3.0.3 (applying Patch 6 to make it SP 6.0.3.6.3).
    b. Installing SMGR 6.1 SP1.1 (applying SMGR 6.1 Patch for SP1.1).
    c. Upgrade SMGR 6.1 SP1.1 to SMGR 6.1 SP6.
    d. Upgrade SM 6.1.4 to SM 6.1.6.

    Hoping that everything goes well. If anyone sees any problem, kindly email me at [email][login to unmask email]/email]. Any input is highly appreciated. :)
    Nico Knook
    [Avayasupport.nl]
    I'm getting the same problem. My platform is:

    SP 6.0.2
    SMGR 6.1.0
    SM 6.1.4

    I noticed that I also am getting the following errors in setting up the SM...
    1. this error...
    Tue Jan 3 12:17:34 AST 2012: Register replica node with System Manager DRS master started.
    Sending configurations to master node
    MBeanException occurred while invoking operation :: NotifyXML
    ERROR # 1 : Unable to perform Aggregation, Terminating the configuration...................
    Starting all components
    .
    Tue Jan 3 12:17:45 AST 2012: Register replica node with System Manager DRS master failed.


    This could most probably be the reason why I cannot see Replica Node in the SMGR for replication procedure.

    2. Prior to getting the above error, I'm getting...
    "Ping of System Manager at xxx.xxx.xxx.xxx failed."

    (Dono if it will work without connection to the live DNS server. I'm doing the installation offline.)

    3. The SM100 status is "DOWN" in the "Home / Elements / Session Manger / System Status / Security Module Status - Security Module Status" although the status "Up" in "Home / Elements / Session Manger / Dashboard - Dashboard".

    Tomorrow, Im planning to re-install everything:

    a. Starting with SP to SP 6.0.3.0.3 (applying Patch 6 to make it SP 6.0.3.6.3).
    b. Installing SMGR 6.1 SP1.1 (applying SMGR 6.1 Patch for SP1.1).
    c. Upgrade SMGR 6.1 SP1.1 to SMGR 6.1 SP6.
    d. Upgrade SM 6.1.4 to SM 6.1.6.

    Hoping that everything goes well. If anyone sees any problem, kindly email me at [email][login to unmask email]/email]. Any input is highly appreciated. :)

    Hi agborbe,

    Without DNS the install (registration of ASM) will fail. You will need to put all entries (system manager en session manager) in the /etc/hosts table of the system- and session manager(s). Both machine names and FQDN:

    10.2.3.4 smgr smgr.mydomain.com
    10.2.3.5 asm asm.mydomain.com

    etc

    Good luck,

    Nico
    Gary Rogerson
    [Fluor Enterprises]
    You're also right in upgrading SP and SMGR to the latest patch release as there are SSL Certs that have expired on earlier SMGR 6.1 SPX versions.
    Angelo Borbe
    [Middle East Telecom]
    Done Installing the SP6.0.3.6.3, SMGR6.1.6, and ASM6.1.6. But still can't make the Security Module Status UP. I've checked the /etc/hosts file in SMGR and I think I need to add ASMs FQDN and IP Address. Anyone can show me how to edit this file? I'm kind of new to Unix commands. Thanks and appreciate the earlier comments.
    Angelo Borbe
    [Middle East Telecom]
    Hi Nico,

    I've added the Hosts and IP addresses on the "Home / Elements / Session Manager / Network Configuration / Local Host Name Resolution - Local Host Name Resolution" to resolve the Local Hosts Naming. I ust need the procedure for the editing of /etc/hosts file. I found a unix note that I should use the vi command but I don't know how to change the file from readonly mode. :(


    Hi agborbe,

    Without DNS the install (registration of ASM) will fail. You will need to put all entries (system manager en session manager) in the /etc/hosts table of the system- and session manager(s). Both machine names and FQDN:

    10.2.3.4 smgr smgr.mydomain.com
    10.2.3.5 asm asm.mydomain.com

    etc

    Good luck,

    Nico
    Nico Knook
    [Avayasupport.nl]
    Hi Nico,

    I've added the Hosts and IP addresses on the "Home / Elements / Session Manager / Network Configuration / Local Host Name Resolution - Local Host Name Resolution" to resolve the Local Hosts Naming. I ust need the procedure for the editing of /etc/hosts file. I found a unix note that I should use the vi command but I don't know how to change the file from readonly mode. :(

    You'll need to be root to be able to edit the file. In vi use :wq! to override read-only mode. Maybe post the contents of the hosts files (both smgr and asm) here.

    Cheers,
    Nico
    Gary Rogerson
    [Fluor Enterprises]
    In SMGR, SSH and login using the admin account, then change to the root user: su - root. Next, type: cat /etc/hosts to view the hosts file. it should look something like this:

    [[login to unmask email] /]# cat /etc/hosts
    127.0.0.1 localhost.localdomain localhost
    10.X.29.26 XXsysmgr.XXnet.com XXsysmgr
    10.X.29.25 avaya-asm.XXnet.com avaya-asm
    10.X.10.143 XXXX01-ASM140.XXnet.com XXXX01-ASM140
    ::1 localhost6.localdomain6 localhost6

    The SMGR hosts file should have the SM Management IP to Hostname entries for all SMs in your network.

    In SM, SSH and login using the craft account, then change to the root user: su - root. Next, type: cat /etc/hosts to view the hosts file. it should look something like this:

    [[login to unmask email] /]# cat /etc/hosts
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    ::1 localhost6.localdomain6 localhost6

    224.0.1.75 sip.mcast.net
    127.0.0.1 localhost.localdomain localhost
    10.XX.29.25 avaya-asm.XXnet.com avaya-asm
    10.XX.29.26 XXsysmgr.XXnet.com XXsysmgr AsmSysMgr

    The SM hosts file should have the IP Address to hostname for your SMGR.

    If you have run the install / setup for SM and the two hosts files do not have the IP to hostname pointers, then you can use VI to edit:

    With root access in both SM and SMGR, type: vi /etc/hosts
    This will open the file in VI. You should see where you can edit. Once you have made your changes, type: :wq to exit and save. After that, you can run initTM on SM to see if it will sync and bring up the Security Module.
    Angelo Borbe
    [Middle East Telecom]
    Thanks everyone. It worked! the Security Module came up after adding the IP Address and FQDN of the SM to /etc/hosts of SMGR using vi text editor. The SM's /etc/hosts file is fine.
    Additional procedure that I did was to make the /etc/hosts file read and write using the command:
    [[login to unmask email] etc]# chmod og=rw /etc/hosts
    Resultant file attributes:
    -rw-rw-rw- 1 root root 122 Jan 16 11:34 hosts
    Tomorrow, I'll setup Session Manager by adding SIP entities, etc.
    by the way, has anyone tried integrating UCM (CS1K 7.5) to System Manager? Is this a simple step? I've seen it working but don't know how to implement.
    Rich White
    [Sanford Health]

    Having some issues with Session Manager an came across this thread. Anyone know where to locate the additional information that the embedded link above refers to? Basically, looking for more information on the CLI for Session Manager (and System Manager for that matter).

    Rich White
    [Sanford Health]

    Anyone know where the thread listed above went? Or where I can find more information on the CLI for ASM and SMGR?


    All Times America/New_York


    Copyright © 2014.'The International Avaya User Group. All Rights Reserved

    All material, files, logos and tradarks within this site are properties of their respective organizations.


    Terms of Service - Privacy Policy - Contact