Hi! I had an incident at work today that was very strange and would like to seek some expert advice. We had about 5 420R's simply go into the ok prompt for no reason. These were production machines that were working fine and all of a sudden they went down. The thing that I can attribute this to was that our network engineer was upgrading our terminal server (a cisco 3600) that was connected to all the servers via a serial connection. We use this in the event that our SSH session fails and we need to physically boot the system when its at the ok. Anyways the engineer claims this is impossible and cannot occur. I took the liberty to call Sun and they stated that this could occur when a terminal connection is stopped it could potentially bring down servers. The strange part is that not all servers connected to the terminal server went down only some 420R's we had v480's and v490's connected and they were up. Has this ever happened to anyone? I have checked /var/adm logs with no luck, They all seemed to have rebooted with no cause. I suspected a power strip went bad but we have all our servers to auto-boot=yes so it was because of power it would have reloaded into the OS. What other logs could show us what happened before the system went down?

Thanks.

This page and the next off of the sun site might be good starting points.

http://docs.sun.com/app/docs/doc/802...q3?l=en&a=view

Thanks adambien, I think I found the solution. I contacted sun and they sent me a document illustrating that if a terminal server is rebooted it has the capability to send a break sequence to the server. We need to disable this option to not allow this.

Thanks for the help.

Don

Pretty freaky when it happens, eh? I have a Wyse terminal that I connect to my v250 for kernel updates. I can't just leave it connected since power it off/on will cause a break