SMGR and ASM connection problem

[eslim]

Please I have installed a VM of SMGR and ASM in ESXI5.5

I have problem of connection between SMGR and ASM.

it is snchronised but still no connection.

In join same traces.

can some one help.

[mlombardi1]

Unless you're using DNS, make sure SMGR has an entry in its hosts file for SM. Verify SMGR and SM are the same version. Service pack levels should match. Try pinging both ways to make sure there is no one-way communication.

If SM received DRS from SMGR, the SM100 should respond to ping.

[eslim]

Thank you mlombardi1

Please below the version used of SMGR and SM:

Please can ou confirm the compatibility between SMGR and SM:

************************************************
System Manager - Software Information
************************************************

===== Software Update Revision: 6.3.2.4.1529 =====

System Manager 6.3.8.0 Build Number 6.3.0.8.5682
Patch 6.3.8.1628 Build Number 6.3.2.4.1529

Quantum 3.1.8-SNAPSHOT(6135) 3.1.8.0 Build Number 6.3.0.8.5682
Communication Server 1000 1.0.2.0 Build Number 1.0-SNAPSHOT-8665
Patch 1.0.2.63204006 Build Number 6.3.2.4.1399

MMCS 6.3.8.0 Build Number 6.3.0.8.1
Patch 6.3.8.4 Build Number 6.3.2.4.1399

Communication System Management 6.3.8.0 Build Number 6.3.8.0.4379
Patch 6.3.8.63204008 Build Number 6.3.2.4.1399

Messaging 6.3.8.0 Build Number 6.3.8.0.1794
Patch 6.3.8.63204009 Build Number 6.3.2.4.1529

Device Inventory 6.3.8.0 Build Number 6.3.8.0.1833
Patch 6.3.8.63204007 Build Number 6.3.2.4.1399

B5800 Branch Gateway 6.3.8.0 Build Number 6.3.8.0.2376
Patch 6.3.8.63204015 Build Number 6.3.2.4.1399

Upgrade Manager 6.3.8.0 Build Number 6.3.8.0.2148
Patch 6.3.8.63204008 Build Number 6.3.2.4.1399

Session Manager Element Manager 6.3.2.0 Build Number 6.3.0.0.630002
Patch 6.3.2.632001 Build Number 6.3.2.4.1399

Conferencing 6.3.107.0 Build Number 6.3.0.0.107
Patch 6.3.107.2 Build Number 6.3.2.4.1399

Presence Extensions 6.3.8.0 Build Number 6.3.0.0.0800
Patch 6.3.8.1 Build Number 6.3.2.4.1399

SMGR on VMware 6.3.2.0 Build Number 6.3.2.4-SNAPSHOT-1290
Patch 6.3.2.1 Build Number 6.3.2.4.1399

SMGR Template Version II 6.3.0.8 Build Number 6.3.0.8.923

************************************************
Operating System Information
************************************************
CentOS release 5.6 (Final)
Linux SMGR.onetech-bs.com 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:43 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

************************************************
JAVA Version
************************************************
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>><
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>
SESSION MANGER



[cust01@avaya-asm ~]$ swversion

Avaya Aura Session Manager Software Version Inventory

Release: 6.3.2.0.632023
Call Processing: 6.3.2.0.632023
Management: 6.3.2.0.632023
SM Tools: 6.3.2.0.632023
DRS: 6.3.2.0.632023
CDR: 6.3.2.0.632023
NCS: 7.65.04
Security Module: 6.3.2.0.632003
nginx: 1.2.0
Firewall: 6.3.2.0.632003
WebSphere AS: 8.0.0.5
SAL Agent: 6.3.2.4
OS: Enterprise Linux Server release 6.2 (Feb 07 11:23:30 MST 2013)
VMware Tools: 9.0.0.15210 (build-782409)

[lazar24]

Hi,

1. Inventory -> manage elements -> session manager -> Management Access Point Host Name - use ip instead of FQDN.

2. You should have all correct hostname-ip mappings in /etc/hosts on both SMGR and SM.

3. Check that you use different ip addresses in session manager's mgmt interface and sip interface. Sounds dumb, but that misconfiguration happens surprisingly often. You can use smconfig command in shell to verify your sm has been successfully provisioned.

PS. This applies to to 7.0.x Dunno if it helps in 6.3.x.

[eslim]

Yes I use Ip instead of FQDN

in the log I see "The Session Manager Instance cannot be resolved. Double check the administration on the Session Manager Administration, NRP SIP Entities screen(s)."


please below the hots-ip mapping in both SMGR and ASM

in SMGR:
root >cat hosts
127.0.0.1 localhost.localdomain localhost
10.112.45.150 SMGR.onetech-bs.com SMGR
10.112.45.151 ASM.onetech-bs.com ASM
::1 localhost6.localdomain6 localhost6

In ASM
[cust@ASM etc]$ cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
192.11.13.5 services-laptop
192.11.13.17 SMGR.vmonetech-bs.com SMGR AsmSysMgr
10.112.45.150 SMGR.onetech-bs.com SMGR AsmSysMgr1
10.112.45.151 ASM.onetech-bs.com ASM




all services are up

[cust@ASM etc]$ statapp
Watchdog 9/ 9 UP
logevent 18/ 18 UP
ncsd 4/ 4 UP
postgres-db 24/ 24 UP
mgmt 175/175 UP
WebSphere 128/128 UP
CDRService 23/ 23 UP
sal-agent 52/ 52 UP
secmod 4/ 4 UP

[hurdk]

If you do an ifconfig is your security module have an ip address?