IBM SAN768B-2, User Manual

Page: 190 / 228

Table 30. Troubleshooting (continued)
Entire chassis powers off
automatically. Power supplies are inadequate to
support the installed components. Add an additional power supply.
Several or all components
are not operating. One or more power cables may
not be connected to a live source. Ensure that all power cables are connected to live
outlets.
One or more AC power supplies
may be off Ensure that all switches on the AC power supplies
are turned on. (AC switches light up green when
on).
Serial connection is faulty
or serial port logs have
incorrect or missing
information. Serial cable is not connected
correctly. Ensure that the cable is firmly connected to
workstation computer and to the SAN768B-2.
Terminal emulator application
parameters are not set correctly. Ensure that the terminal emulator application is
configured as follows: 9600 bits per second, 8
databits, no parity, 1 stop bit, no flow control.
Serial port might be incompatible
(only RS–232 is supported). Ensure that the SAN768B-2 is connected to an
RS–232 port. RS–423 serial ports might experience
difficulties due to corner-case incompatibilities of
the standards.
Pins on the serial cable or serial
port might be damaged. Remove the cable and inspect the pins on the cable
and in the serial port. Do not reinstall if the pins
on either component have any visible damage, as
this could damage the pins on the other
component. Replace components as required.
CP Ethernet link speed is
different than expected or
a link cannot be
established. There might be a conflict with the
CP Ethernet link speed negotiation
set up by the network. Specify the CP Ethernet link speed by entering the
ifModeSet
command.
Configuration data is
inaccurate or cannot be
accessed. Chassis was powered off/on while
the WWN card was uninstalled or
failed. Install an operational WWN card and power the
system off/on again.
The SAN768B-2 was rebooted
while the WWN card was
uninstalled or failed.
Initial set up results in IP
address/Domain ID
conflict. The SAN768B-2 was connected to
the fabric before being configured. Refer to Chapter 3, “Starting and configuring the
SAN768B-2,” on page 35 and the
Fabric OS
Administrator's Guide for configuration information.
LEDs on one or more
components are changing
rapidly or do not indicate
a healthy state. The SAN768B-2 might be booting
or running POST. Verify that boot and POST are complete. The
SAN768B-2 requires a minimum of 3 minutes,
usually, after power-on to complete POST.
Beaconing might be on for the
entire SAN768B-2 or for individual
components. Determine whether beaconing is on by entering
the
switchShow command and determine whether
switch beaconing or blade beaconing is on.
Individual components might have
failed. Refer to the LED tables in Chapter 4, “Monitoring
system components,” on page 53 for interpretation
and recommended actions.
Pins on the components might be
damaged. Remove component from chassis and inspect pins
on component and inside chassis. Do not reinstall
if pins on either component are visibly damaged,
as this could damage pins on other component.
Replace parts as required.
162
SAN768B-2 Installation, Service, and User Guide