S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
8-14
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 8 Troubleshooting Ports
Common Problems with Port Interfaces
Symptom
Port remains in a link-failure state.
Note
We recommend that you do not disable and then enable a T or TE port. This would affect all the VSANs
crossing the EISL instead of just the VSAN experiencing the problem.
Table 8-3
Port Remains in a Link-Failure State
Symptom
Possible Cause
Solution
Port remains in a
link-failure state.
Port connection is bad.
Use the
show port internal info
CLI command to
verify the port status is in link-failure. Use the
show hardware internal fc-mac port port
gbic-info
CLI command to determine if there is a
signal present.
Note
You must use the
attach module
CLI
command to access the FC-MAC show
commands.
Verify the type of media in use. Is it copper or
optical, single-mode (SM) or multimode (MM)?
Verify that the media is not broken or damaged. Is
the LED on the switch green? Is the active LED on
the host bus adapter (HBA) for the connected
device on?
Right-click on the port in Device Manager and
select
disable
and then
enable
, or use the
shut
CLI
command followed by the
no shut
command
to disable and enable the port. If this does not
clear the problem, try moving the connection to a
different port on the same or another module.
There is no signal because of a transit fault in the
SFP or the SFP may be faulty.
When this occurs, the port stays in a transit port
state and you see no signal. There is no
synchronization at the MAC level. The problem
may be related to the port speed setting or
autonegotiation. See the
“Troubleshooting Port
Problems” section on page 8-15
. Verify that the
SFP on the interface is seated properly. If
reseating the SFP does not resolve the issue,
replace the SFP or try another port on the switch.
Link is stuck in initialization state or the link is in
a point-to-point state.
Choose
Logs > Switch Resident > Syslog
on
Device Manager or use the
show logging
CLI
command to check for a
Link Failure, Not
Connected
system
message.
Right-click on the port in Device Manager and
select
disable
and then
enable
, or use the
shut
CLI
command followed by the
no shut
command
to disable and enable the port. If this does not
clear the problem, try moving the connection to a
different port on the same or another module.
