Specifications

{
NSB83619—Address resolution failed
{
NSB83589—Failed to boot after 1 attempt
{
NSB70519—Failed to connect to a server
See this Common Reasons and Solutions section in order to determine if you experience one of the common reasons:
Common Reasons and Solutions
The reason for these symptoms can be an interface delay that either Spanning Tree Protocol (STP), EtherChannel, trunking, or an autonegotiation delay causes. For more information about these delays and possible solutions, refer to Using PortFast and Other Commands to Fix
Workstation Startup Connectivity Delays.
If you review and follow the procedure in the document and you still have issues, contact Cisco
Technical Support.
Troubleshoot NIC Compatibility Issues
You can have NIC compatibility or misconfiguration issues with the switch if you experience one of these symptoms:
z
A server or client connection to the switch does not come up.
z
You have autonegotiation issues.
z
You see errors on the port.
See this Common Reasons and Solutions
section for more information on the misconfiguration issues:
Common Reasons and Solutions
z
The reason for these symptoms can be a known NIC driver issue, speed and duplex mismatch, or autonegotiation or cabling problems. For more troubleshoot information, refer to Troubleshooting Cisco Catalyst Switches to NIC Compatibility Issues.
z
This table shows the known issue with the Catalyst 4000 that runs the Supervisor Engine III and IV:
If you still have issues after you review and follow the procedure in the document Troubleshooting Cisco Catalyst Switches to NIC Compatibility Issues, contact Cisco Technical Support for further assistance.
Interface Is in errdisable Status
If the interface status is
err-disable
in the output of the
show interface status
command, see this Common Reasons and Solutions section:
Common Reasons and Solutions
The interface goes into
err-disable
state for a variety of reasons. Some of the possibilities include:
z
Duplex mismatch
z
Port channel misconfiguration
z
Bridge protocol data unit (BPDU) guard violation
z
UniDirectional Link Detection (UDLD) condition
z
Late-collision detection
z
Link-flap detection
z
Security violation
z
Port Aggregation Protocol (PAgP) flap
z
Layer Two Tunneling Protocol (L2TP) guard
z
DHCP snooping rate-limit
In order to determine the reason, issue the
show errdisable recovery
command.
In order to reenable the interface manually, issue the
no shutdown
interface command. Or, you can set up the time-out mechanism in order to reenable the port after a time period that you configure. Once you know the
cause of the errdisable state, you can troubleshoot the problem
and fix the root of the issue. For example, your port can be in
err-disable
state because of the receipt of a BPDU on an access port on which you have enabled PortFast. You can troubleshoot in order to determine if a switch has accidental connection to that port, or if a hub was
connected in a loop fashion, which makes the switch see its own BPDU. In order to troubleshoot other scenarios, refer to the specific feature information in the Catalyst 4500 Series Switch Cisco IOS Software Configuration Guide, 12.1(12c)EW.
If you review and troubleshoot with use of this document and you still have issues, contact Cisco Technical Support for further assistance.
Troubleshoot Interface Errors
If you see an error in the output of the
show interface
command, see this Common Reasons and Solutions section:
Common Reasons and Solutions
z
The reason for the interface errors can be:
{
A physical layer issue, such as a faulty cable or NIC
{
A configuration issue, such as a speed and duplex mismatch
{
A performance issue, such as an oversubscription
In order to understand and troubleshoot these issues, refer to Troubleshooting Switch Port and Interface Problems.
z
At times, error counters increment incorrectly because of a software bug or hardware limitations. This table lists some of the known counter issues with the Catalyst 4000 Supervisor Engine III and IV platform:
1
SVI = switched virtual interface.
2
ISL = Inter-Switch Link Protocol.
3
CRC = cyclic redundancy check.
4
Tx = transmit.
Symptom Description Fix
WS-X4424-GB-RJ45 does not
link up with hard code for speed
and duplex.
A Catalyst 4000 Supervisor Engine that runs Cisco IOS Software Release 12.1(12c)EW or earlier does
not link up on a WS-X4424-GB-RJ45 line card interface if you have hard coded for speed and duplex.
The workaround is to issue the
shutdown/no shutdown
interface command.
Cisco IOS Software
Release 12.1(12c)EW1
and later
Symptom Description Fix
There are output errors in the
show interface
command.
The output queue drops incorrectly count as output errors.
Note:
Valid output errors still count as such.
Cisco IOS
Software
Release 12.1
(11)EW and
later
The input queue size is greater than the input queue maximum size in the
show interface
command output. Here is sample output:
Input queue:
3285/2000
/0/0 (size/max/drops/flushes
The input queue size incorrectly includes counts of all the input
packets.
Cisco IOS
Software
Release 12.1
(12c)EW and
later
The broadcast counter in the
show interface vlan
vlan-id
command output
does not work. The counter is always zero.
The broadcast counter does not count the valid broadcast frames to
the VLAN SVI
1
.
Cisco IOS
Software
Release 12.1
(12c)EW and
later
The ISL
2
trunk port reports giants, and there are input errors on certain line
cards in the
show interface
interface-id
command output.
Packets that are larger than 1522 bytes count as oversize, or
"giants". These giants also show up as input errors. ISL packets
can have a maximum size of 1548 bytes. Packets between 1522
and 1548 bytes switch correctly, but still count as giants because of
a known limitation.
Not available
A CRC
3
error, and input error, appear in the
show interface
interface-id
command output.
Under certain conditions, the Supervisor Engine III can transmit
packets that generate internally with a bad CRC. Packets that enter
the switch on external interfaces do not become corrupt under these
conditions. Refer to Cisco bug ID CSCdx36065 (
registered
customers only
) for more information.
Cisco IOS
Software
Release 12.1
(11)EW and
later
Output that continuously increments drops in the
show interface
interface-
id
command output.
The output total drop count should count the total of all Tx
4
queue
drops for that interface. The counter increments continuously once
the
tx-queue-drop
field has a nonzero value. The drops add
cumulatively, which is erroneous. Refer to Cisco bug ID
CSCdx62202
(
registered customers only
) for more information.
Cisco IOS
Software
Release 12.1
(12c)EW and
later
Baby giants count as oversize giants on certain line cards in the
show
interface
interface-id
command output.
This is a known limitation. For more information, refer to the
Catalyst
4000 Series
section of the document Jumbo/Giant Frame
Support on Catalyst Switches Configuration Example.
Not available