CMA 5000 Server Serial Console Access

[medrt]

CMA 5000 Server

Version 6.0.1

I am getting "AM Master Service Failed to Start - reason: Unable to connect to the Database"

So in trying to debug this I was attempting to get serial console so that I can ping, etc. the db server.

I connected to the serial port using the serial cable that comes with the CMA server and using parameters

19200,8,n,1

However I see no messages.  I reboot and still see no messages.

How to get serial console access?

Or is there a better way to debug what is going on?

Thanks

[simons]

Serial console access is no longer available in CMA v6.

Your best best is to reimage using the CMA v6 DVD and apply the latest patches to your system, v6.0.1 and some other patch.

S.

[medrt · Accepted solution]

It is quite unbelievable that if the SQL server is causing issues, there is no way to get to the box for diagnostic purposes.  

Both redundant CMA servers are experiencing this problem, so I am sure nothing is wrong with the CMA server. 

To re-image it would frankly be a waste of time.  

I have looked at SQL Server log messages, and did a TCPDUMP off the ports, but still have not tracked down exactly what the problem is.

I know I will, so there is no need to respond to this post.

However, I would like a product change for CMA server.

There needs to be a way to get console or desktop access to be able to debug this kind of problem.

If nothing else, the web interface should come up, regardless of whether it can connect to the remote db and provide rudimentary debugging capabilities.

Ping, telnet, traceroute, etc.

Thanks

[AlexH]

How about connecting by RDP together with Support staff of Polycom to analyze the Problem? That would be my first task.....

[medrt]

Alex,

Thanks for the input.  That is what I ultimately did. But getting the user password is difficult at best. 

I solved the issue, but Polycom needs to give a way to debug these kinds of issues.

Serial console, ssh, rdc.  I don't really care how, but some method..

[AlexH]

I know this what we are also attempting all the time, but currently without success. Maybe a feature request would help. Will think about it.

[dd]

Hello MEDRT - I have the same problem.  Both 5000's say 'Master Service failed to start-Unable to connect to database'.  I know why, the DBA P-to-V'd the SQL serverand changed the IP address.  How can I repoint the CMA at the correct IP address?  It's Sunday so I can't get to PLCM support through my third party service.  I will in the morning, but if you can let me know anything today I can get it donebefore production hours.  Thanks.

[medrt]

You will have to get windows console/rdp access.  There is a default password, but it is not documented.  

[dd]

I do have that password and I have console access, what's next?  I would like to change the DB at the new SQL server's IP address.

[simons]

DD,

If you have v5.x, then you can use the serail console access to reset to factory defaults which will give you access in order to point to the new external SQL server IP address. In v6, you are out of luck and are left with a reimage. You data is still fine as it resides in the external DB.

On a side note, I agree with everything posted above. If more folks would voice their concern with this process, then Product Management would finally have to pay attention to the needs of the customers.

S.