Troubleshooting management connections, Port bypass conditions and recovery, Roubleshooting – Emulex 355 (for Apple) User Manual

Page 58: Anagement, Onnections, Ypass, Onditions, Ecovery

Advertising
background image

E

MULEX

M

ODEL

355 SAN S

TORAGE

S

WITCH

U

SER

S

G

UIDE

C

HAPTER

4: T

ECHNICAL

R

EFERENCE

E

MULEX

C

ORPORATION

55

P

ART

N

UMBER

00041407-002 R

EV

. B

T

ROUBLESHOOTING

M

ANAGEMENT

C

ONNECTIONS

P

ORT

B

YPASS

C

ONDITIONS

AND

R

ECOVERY

Problem

Recommended Action

Serial cable installed but
connection does not
appear on terminal

1. Cycle power by reinstalling the power cord.

2. Check the terminal emulation program’s serial port parameters.

3. Replace the serial cable. (Make sure it is a null modem cable.)

Ethernet cable installed
but Web Manager does
not appear

1. Ensure that a crossover ethernet cable is used (unless using an ethernet

hub).

2. Check the IP addresses on the switch and workstation as follows:

At a command line prompt, type ping

DNSorIP (where DNSorIP is the

switch’s DNS name or IP address) and press ENTER.
If a “Reply from…” or “...is alive...” message appears, the devices can
communicate.
If a “Request timed out” message appears (or the command times out),
the devices cannot communicate. Trace the cabling. If needed,
reconnect the devices.

Operational Condition

Recovery

Rx_los is asserted by an
SFP/GBIC

The port stays bypassed until rx_los is de-asserted. At that time, the port
insertion will be automatically retried. The port continues to stay bypassed
until the port can pass the port insertion criteria.

Tx_fault is asserted by
an SFP/GBIC

The port stays bypassed until tx_fault is de-asserted. At that time, the port
insertion will be automatically retried. The port continues to stay bypassed
until the port can pass the port insertion criteria.

F8 Failure notification is
received by the port
(when the LIP F8
Recover policy is
enabled)

The switch automatically tries to re-insert the device, by sending F7
Initialization notifications to the device connected to the bypassed port. The
port continues to stay bypassed until the device returns F7 Initialization
notifications to the port and passes the port insertion criteria.

Loss of Sync (>100ms)

The port stays bypassed until a signal is re-established. At that time, the
port insertion will be automatically retried. The port continues to stay
bypassed until the port can pass the port insertion criteria.

Firmware Initiated

The port stays bypassed until the firmware sets the port control back to
automatic. At that time, the port insertion will be automatically retried. The
port continues to stay bypassed until the port can pass the port insertion
criteria.

Advertising