Troubleshooting Guide
For detailed information on Cisco bug IDs, refer to the Bug Toolkit (registered customers only) .
Refer to Cisco Catalyst 5000 Series Switches Release Notes for more Catalyst 5000 and 5500
documented bug fixes.
Catalyst 4000, 2948G, and 2980G Switches
This table lists several known issues found on the Catalyst 4000, 2948G, and 2980G switches.
Table 9
transmitting frames.
Bug ID
Resolved
In
Description
CSCds38973
(registered
customers
only)
4.5(8), 5.2
(7), 5.5(2)
The Catalyst 2948G and
Catalyst 4000 switches can
experience issues with total or
intermittent loss of connectivity.
The frequency of these issues
can vary from once a day to
once a month. This issue can
reoccur even after the switch is
power cycled. The purpose of
this Cisco bug ID is to combine
several software reworks, fixes
that resolve and reduce the loss
of connectivity issues, and
additional troubleshooting
checks in software.
CSCdr37645
(registered
customers
only)
4.5(8), 5.5
(2), 6.1(1)
An invalid packet with a length
of less than 64 bytes received
on a 10/100 port causes both
the Runts and FCS-Error
counters to increment on the
port. To determine the actual
number of FCS-Errors on valid
length packets received on the
port, subtract the value of the
port Runts counter from the
value of the port FCS-Error
counter.
CSCdm38405
(registered
customers
only)
5.1(1)
Some Sun Gigabit Ethernet
NICs do not reliably
autonegotiate flow control with
certain ports on the Catalyst
4000 series oversubscribed
Gigabit Ethernet modules. The
18-port server switching
1000BASE-X (GBIC) Gigabit
Ethernet module (WS-X4418) is
affected.
CSCdm51653
(registered
customers
only)
4.5(3), 5.1
(2a)
In some cases, autonegotiation
with some Sun NICs can result
in a nonoptimal configuration
(such as 10 Mbps, half-duplex
instead of 100 Mbps, full-
duplex).
CSCdt80707
(registered
customers
only)
5.5.7,
6.1.3,
6.2.1
On a Catalyst 4006 with a
Supervisor Engine II, switch
ports in the same VLAN can
lose connectivity with one
another. The loss of connectivity
results in a VLAN that appears
to be partitioned into several
isolated segments. A host can
be able to ping one set of
devices in its VLAN, while it
cannot ping another set of
devices in the same VLAN. This
loss of connectivity is
independent of the slot in which
a linecard is installed; that is,
the same set of ports on a given