sig svr missing when building new node in E manager

[steve64]

Equipment is CS1000E rel 7.5. Installation is new. The Sig servers have been programmed with all required patches and the SU. The deployments have been done and everything looks fine. (It all looks the same as another system when doing a stare and compare) The problem is that when I go into element manager to build the Node there are no sig servers in the pull down box. I have heard of this problem before on rel 7.5. Does anyone have a idea what has gone wrong?

 

[Triton101]

maybe the deployed apps on the sigserv don't match the selected options for the node?

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[KCFLHRC]

Is the server showing up in your elements list in UCM. Is this a Primary, backup or member server?

 

[steve64]

The servers, both show up in UCM on both servers "elements". One server is configured as the Primary deployment and security and the other is configured as a member server. The deployed applications on both servers are SS and EM.

 

[Triton101]

ok, so when you are building your node you are selecting only

LTPS
Virtual Trunk Gateway
and Personal Directory?



__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[MJSR8R]

I had this same problem. The fix was to reload the Linux on the Signaling Server. I would undeploy and make sure the CS1000 system is out of the UCM. Then reload the Linux on the SS, install the first 3 patches via CLI then register it into the security domain. Then push the Linux SP to it from UCM. Then re-deploy the apps, push the SP again so it patches the newly deployed apps. Once that done try and configure the Node again. The trouble I had was the IP address in the XML file of the deployed applications had the wrong IP address of the Signaling Server in it so the SS was not being recognized in EM. I had ETAS go in and change the file for me in the Linux so that I could avoid reloading the Linux. His recommendation was that if this happened again to go ahead and reload the Linux in the SS. Once the Linux server is deployed and you can get into EM, the UCM portion of controll is over and you should focus all your troubleshooting on the Linux SS piece..........Hope this helps.

 

[steve64]

Problem solved. There was a "license key" mismatch between the security server and the switch. I had Avaya help with it and they tel me that this is not all that uncomon with 7.5.