Cisco Systems 17053 appendix Day to once a month. This issue can

		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.
		An invalid packet with a length of
		less than 64 bytes received on a
CSCdr37645		10/100 port causes both the Runts
( registered	4.5(8),	and FCS−Error counters to
customers only)		increment on the port. To determine
	5.5(2),
		the actual number of FCS−Errors on
	6.1(1)
		valid length packets received on the
		port, subtract the value of the port
		Runts counter from the value of the
		port FCS−Error counter.
		Some Sun Gigabit Ethernet NICs do
CSCdm38405		not reliably autonegotiate flow
		control with certain ports on the
( registered
		Catalyst 4000 series oversubscribed
customers only)
	5.1(1)	Gigabit Ethernet modules. The
		18−port server switching
		1000BASE−X (GBIC) Gigabit
		Ethernet module (WS−X4418) is
		affected.
CSCdm51653		In some cases, autonegotiation with
( registered
		some Sun NICs can result in a
customers only)	4.5(3),
		nonoptimal configuration (such as
	5.1(2a)
		10 Mbps, half−duplex instead of
		100 Mbps, full−duplex).
		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
CSCdt80707		partitioned into several isolated
		segments. A host can be able to
( registered
	5.5.7,	ping one set of devices in its
customers only)
	6.1.3,	VLAN, while it cannot ping another
	6.2.1	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
		linecard are affected regardless of
		the slot in which the linecard is
		installed. The workaround is to
		reset the switch.