CMS Issue

[TykeUK]

After a site power down at the weekend our CMS Server isn't playing ball! The ACD is not connected and there is an MIS alarm on the CM.

I have busied and released the MIS but the error type 1 still appears.

Not really clued up on CMS but I'm 100% sure nothing has changed in the configuration and on the network so I'm not sure where/how to proceed to resolve this now.

Any suggestions?

Thanks

 

[TykeUK]

Sorry, version info...
CM 5.2
CMS R16

 

[ideal]

Can you please advise what the hardware platform is. Is a Sun Netra 210.

 

[TykeUK]

Its a Sun Sparc T5120 (i think). CMS is a bit of a mystery to me!

 

[ideal]

Have you pressed the on button at the bottom left hand side of the server using a pen. For more info there should be an alert label on the top of the server

http://www.fujitsu.com/downloads/SPARCE/manuals/sparc-t5e/t5120t5220-service-en-04.pdf

 

[TykeUK]

I thought that was just the power button? The server has power and we can connect to the CMS, but it seems that the CMS cannot talk to the CM using port 5001.

 

[ideal]

Does the CMS appear to be up. Can you see all the menu's on the Sun via the VDU connected to it.

 

[TykeUK]

yes it's up, and I can log on via CentreVu but the ACD icon has the red line through it.
I can ping the CM and vice versa but the trace route just times out. I can however get the the CMS from the CM server when doing a trace route

 

[ideal]

Is the CLAN that the CMS uses for the link OK.

 

[TykeUK]

We use processor ethernet so there are no clans. The processor ethernet seems to be working fine and we have no other issues.

 

[ideal]

If you have the root login for the CMS, carry out a trace route from the # promp to the phone system and see where it stops. I think it may be a default gateway issue.

 

[TykeUK]

Thanks for your help ideal but this has now been resolved in the most unlikely of fashions!

It turns out that our BP created 2 new signalling groups / trunk groups etc a couple of weeks ago for using internal extension numbers for simulring on 1XM. They used port 5001 on one of them for the listen port. As soon as this was changed the ACD connected! Not sure how this has been working for the past couple of weeks if that was the cause but all is well now.

Thanks