Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMGR-ASM connection

Status
Not open for further replies.
Sort by date Sort by votes
Other traces of swversion

SMGR
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

admin >swversion
************************************************
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)
 
Upvote 0 Downvote
The Synchronization is between System Manager and Session Manager which means you're good to program the system.

The "No Connections" under the Session Manager Dashboard shows that you don't have any SIP entities built, such as Communication Manager. Nothing is wrong, you just need to add more programming.

Go to Elements / Routing and you'll find a step-by-step outline of how to build Domains, Locations, Adaptations, SIP Entities, Routing Policies, and Dial Patterns.
 
Upvote 0 Downvote
ZerozeroOne, SIP entities was created.

Domains, locations, SIP entities was done but always still no connection.
 
Upvote 0 Downvote
How about we verify the installation?

Looks like the software loads are the same - 6.3.2. There are newer updates available so you may want to confirm you have the latest on each.

Under Home / Services / Inventory / Manage Elements
Make sure both the Management and Service IP addresses are correct, along with everything else.

Log in to the the command line on Session Manager and run SMNetSetup to tell ASM how to reach Sysmgr.

I'm not sure if there's anything else. Any alarms?
 
Upvote 0 Downvote

#5 Add to eslim's Reputation Report Post
Old Yesterday, 01:20 PM
eslim eslim is online now
Member


Join Date: Feb 2015
Posts: 7
eslim has 10 reputation points
Default
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
 
Upvote 0 Downvote

What would it take to try again with lowercase hostnames? Can you ping and nslookup both the SMGR.vmonetech-bs.com and ASM.vmonetech-bs.com and asm.vmonetech-bs.com and smgr.vmonetech-bs.com from both boxes just to make sure nothing in the Avaya scripts ultimately drops everything to lowercase?

It's a thought, and I've never seen anyone else use mixed case FQDNs in recent memory.
 
Upvote 0 Downvote
Keylee555, thank you for your answer

I have this alarm in System manager " SM/BSM host name resolution failed; [The following SM/BSM failed the Host Name Resolution test: 10.112.45.152]"

10.112.45.152 is Mgmt IS @ of Session manager.
10.112.45.151 is the ip ^@ SIP instance.

Please see alsoo trace in join

it can help

thank you
 
 http://files.engineering.com/getfile.aspx?folder=14304e9d-4bc3-4103-bb61-f7f8fd5a43ff&file=traces_SMGR.docx
Upvote 0 Downvote
So, the name in the SIP entities doesn't matter. The name in the hosts file in SMGR's Linux must match what was entered in the SM OS's setup.

That's the hostname resolution that's failing. I'm thinking it might be dumbing everything down to lowercase somewhere in the background and you should see if you can reproduce your problem following the exact same steps with capital letter short hostnames vs lowercase to see if it's the problem.
 
Upvote 0 Downvote
below is what entred in both SMGR and SM

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
 
Upvote 0 Downvote
Your name resolution is wrong

You are resolving the SM100 address rather than the management one

10.112.45.152 is Mgmt IS @ of Session manager.
10.112.45.151 is the ip ^@ SIP instance.
Click to expand...

Code: 
10.112.45.150        SMGR.onetech-bs.com SMGR
10.112.45.[b]151[/b]        ASM.onetech-bs.com ASM

Code: 
10.112.45.150        SMGR.onetech-bs.com SMGR
10.112.45.[b]152[/b]        ASM.onetech-bs.com ASM


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Upvote 0 Downvote
I have changed the hosts but always some probem.

Note that from SMGR I can't ping Mgt IP of SM
admin >ping 10.112.45.152
PING 10.112.45.152 (10.112.45.152) 56(84) bytes of data.
From 10.112.45.150 icmp_seq=1 Destination Host Unreachable
From 10.112.45.150 icmp_seq=2 Destination Host Unreachable
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
admin >ping 10.112.45.151
PING 10.112.45.151 (10.112.45.151) 56(84) bytes of data.
64 bytes from 10.112.45.151: icmp_seq=1 ttl=64 time=0.386 ms
64 bytes from 10.112.45.151: icmp_seq=2 ttl=64 time=0.415 ms
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
from SMGR
admin >cat hosts
127.0.0.1 localhost.localdomain localhost
10.112.45.150 SMGR.onetech-bs.com SMGR
10.112.45.152 ASM.onetech-bs.com ASM
::1 localhost6.localdomain6 localhost







 
Upvote 0 Downvote
I'm afraid I give up

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Upvote 0 Downvote
This is the issue so the question is what information you've entered on Session Manager in the System Manager configuration.

"SM/BSM host name resolution failed; [The following SM/BSM failed the Host Name Resolution test: 10.112.45.152]"

It's pretty easy to get this running if you follow the documentation, also you should be running the latest patches on SM/SMGR.

"Trying is the first step to failure..." - Homer
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

phoneguy55
  • Locked
  • Question
SMGR reboot with geo redundancy
Replies
1
Views
313
JefferP
JefferP
hcmbmt
  • Locked
  • Question
SMGR and CM sync but change no update
Replies
3
Views
434
hcmbmt
hcmbmt
G
  • Locked
  • Question
Avaya SMGR 8 - Migrating to Softphones
Replies
2
Views
481
dialtonebone
dialtonebone
fondog2
  • Locked
  • Question
ASM to SBC link down
Replies
2
Views
766
fondog2
fondog2
bignose21
  • Locked
  • Question
SMGR 6.3 Log Viewer
Replies
2
Views
338
bignose21
bignose21

Part and Inventory Search

Sponsor

Back
Top