View Single Post
Old 03-28-2011, 06:56 AM
ahmed1 ahmed1 is offline
Hot Shot
Join Date: Nov 2010
Posts: 17
ahmed1 has 10 reputation points
Default SMGR SM 6.1 and CM

Hi Gary,

Please find my answers below for your queries:
  • Should SM be added under Inventory / Elements? If so, should I add the Management Interface or Security Module IP Address? Also, what do I add for the Access Point?
SM is not required in "Inventory" in System Manager administration. However, CM must be added for the Station data Synchronization between CM and SM.

Make sure that you have the following in SM /etc/hosts file apart from the localhost :

<SM management IP> <SM FQDN>

eg: smgr-node1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

Similarly, in SMGR /etc/hosts file, add the SM IP address and FQDN.

firstly, SM must be added as a SIP Entity in SIP Entity Link under "Routing". Please note that you add, SM100 module/Asset (eth2 port) IP address as SIP Entity and not Management Interface IP (eth0)
Secondary, Under Session Manager --> Session Manager Administration. Here when you add the Session Manager, you would also be asked to enter the "Management Interface IP". Asset IP would be automatically populated.

The Asset IP (eth2) is configured or pushed from the System Manager to SM through Webservice SOAP request / response. Once the eth2 is configured on SM, you would be able to ping the IP from the network and not just from the SM server. Please check /var/asset.log to get further information on eth2 getting configured and coming up.

For everything to work fine, note, that both the initTM (Trust Management) and initDRS (Initialing Data Replication service) should have completed successfully at the time of installation.
  • If I am not able to use DNS, can I still get everything working? Do I use the DNS Override?
DNS server details are important for all Avaya Aura products. Things may work but may have other issues. Provide any DNS server which is atleast reachable from the SM server. It may not necessarily resolve all FQDNs.
  • Also, I have both SMGR and SM at 6.1 Service Pack 1. I noticed that no mater what I do, I can't get the SIP Tracer to show any messages. ...I was able to in version 6.1 Service Pack 0.
Assuming that you are able to:

a. Ping the eth2 IP from the Network
b. See the eth2 when you do: ifconfig eth2

Check if the Security module (SM100) is in "Accept New services" state. You can check this from SMGR admin --> Session Manager links.


Reply With Quote