Unity Server randomly reboots after expansion chassis installation
We are running Unity 126.96.36.199 integrating to a Nortel Meridian Option 11c switch through Calista boxes. We were out of PCI ports and wanted to expand from 32 ports to 40. We purchased a Magma PCI expansion chassis and an additional 12 port card. We moved all cards from the Unity server into the expansion box, linked them together and all was working well. Unity sees all 40 ports and I can manage them from the Unity server.
About 2 weeks later, on a Monday morning (the busiest morning), the server reboots. The only messages in the event log that are of any consequence are as follows:
The Compaq System Management Driver has detected that the system encountered a Non-Maskable Interrupt (NMI) prior to this boot. The NMI source was PCI bus error, slot 6.
The previous system shutdown at 10:48:20 AM on 1/27/2003 was unexpected.
The reboots have moved up from once per 2 weeks to twice in one day last week. These are the only messages every time. We've checked all the usual areas, event logs, memory dumps (none), device manager, etc. No clues.
We would prefer not to go back to 32 ports inside one box, but we're beginning to feel that is the only way to keep Unity up and running reliably. Any thoughts, suggestions? Thanks.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.