SMGR and SM link down 1

[Bonker1974]

Hi All,
I'm installing a SMGR and SM 7.1. I did the configuration for the Entity link however I can't get the link to register.

 

[avayaguy23]

certificate issue or you didn't configure the trust management correctly.

 

[Bonker1974]

How can I configure it correctly?
Do you have any docs on it?

 

[dialtonebone]

I'm assuming you are trying to get an entity link between SM and CM up.

This is TCP, there shouldn't be any certificates involved

Is .244 your PROCR address? "display ip-interface procr" from CM.
What does the signal group look like? "display signal- XX" from CM

What version of CM? What version of SM and SMGR?

 

[avayaguy23]

you are installing it via vmware? If you are then flip the nics. Also,

https://www.youtube.com/watch?v=z2jv2MacwHI

 

[avayaguy23]

It could be a certificate issue if a certificate was configured for the system manager web interface. You would have to configure the certificate to include the virtual domain (its used for synchronization between system/session manager)

 

[Bonker1974]

Here is my Sig information

The sig is showing in service and the trunks are all idle.

CM 7.1
SMGR 7.1
SM 7.1

 

[avayaguy23]

Are you able to ping your sip management ip but not your sip entity? If that is your scenario you probably have your NICS set up wrong. Try flipping it.

 

[Bonker1974]

I can ping both IP SM management IP and the SIP entity IP.

 

[avayaguy23]

If no certificate issue found in system manager, please rum command initDRS (this isn't service affecting) in Session Manager.

If system manager certificate expired and just renewed, need run command initTM -f (this is service affecting) in session manager to get Session Manager certificates renewed.

If System Manager certificates are fine but Session Manager

initDRS and initTM can be ran as user craft, no need root, initTM is needing Enrollment Password from System Manager Security / Certificates / Enrollment Password

If initDRS or initTM still not able to fix this issue please open a service request with Backbone support team.

Note: for initTM commands to work properly server time on the ASM and SMGR have to be within 30 seconds of each other or it may cause DRS to fail. This can be checked by running the "date" command in CLI

===============================================================================
In some customer system -Session Manager and System Manager are unable to exchange the certificates between them and hence we see “No Connection”.
For some reason, both SM and SMGR would be unable to exchange the HeartBeat because of the certificate issue.

So, we need to run the below commands in Session manager, if SM uses a Demo certificate :-

 initTM –f
 initTM –d

Symmetric logs reads below :-

2018-01-18 13:00:56,327 WARN [com.avaya.mgmt.drs.debug] [NodeHeartbeatThread] Unable to send heartbeat : Received fatal alert: certificate_unknown
2018-01-18 13:01:01,877 ERROR [org.jumpmind.symmetric.service.impl.DataLoaderService] [pulljob] Failed while reading batch because: Received fatal alert: certificate_unknown

Note: If issue still persists after running initTM commands please investigate network for possible issues between ASM and SMGR