IBM System Storage SAN384B-2 Installation, Service And User Manual page 170

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