Serial Management Console Troubleshooting; Retrieving The System Log - IBM TotalStorage SAN16M-R SAN Installation And Service Manual

Serial Management Console troubleshooting

Serial Management Console troubleshooting

Table 23
Problem
The Serial Management Console will not
come up.
The characters on the Serial
Management Console screen are
garbled.
There are strange messages on my
screen.

Retrieving the system log

Review Table 23, Serial Management Console troubleshooting
troubleshoot problems with the console connected to the
management port.
Solution
There are several reasons that you may not be able to bring up a console connected to
the serial port. Make sure the "null modem" cable on the management workstation is
plugged in securely to the proper serial port.
Check that the settings for the VT100 terminal emulator are correct. The default
settings are:
• Baud Rate: 9600
• Data Bits: 8
• Parity: None
• Stop Bits: 1
• Flow Control: None
Make sure that you have selected the proper COM port for the emulator and that the
Serial port is enabled in the system BIOS (check with your computer manufacturer for
more information on this).
This is typically caused by a configuration problem with the VT100 emulator terminal:
Go to the advanced settings for the terminal and make sure that the VT100 terminal
emulation setting is set to ANSI or auto detect.
There are different occasions during loading sequences or operation where messages
may appear, but if they continue to appear for no apparent reason, or if you have
further questions, contact Customer Support for further assistance.
The System Log (different from the Element Manager Message Log)
contains errors or warning states encountered at the SAN Router.
This could include ports going up and down, mSNS unable to zone, a
SAN Router task failing, and so on.
The System Log is a fixed size. New entries are written to the
beginning of the log overwriting the oldest entries. The log may be
cleared out from time to time, so it is important to remember that the
log may not include every error.
Chapter 3: Maintenance and troubleshooting
to help
57