Installation guide

Release Notes for Catalyst 6000 Family Software Release 5.x 11

Resolved Caveats in Software Release 5.3(4)CSX

• In systems with redundant supervisor engines, after a switchover to the redundant supervisor

engine, the following message might be reported to the console:

Got main interrupt val : 0x2

Interrupt in DBus Slave block: 0x200

Soft reset of titan : done

Note that this bug has no impact and you should ignore these messages.(CSCdp03131)

• When you change an IPX ﬂow to destination-source, the show mls entry ipx destination

command used to specify a speciﬁc destination displays all IPX Layer 3 entries rather than just

those for a speciﬁc destination IPX address. (CSCdm46984)

• In systems with redundant supervisor engines, occasionally during the removal of the active

supervisor engine, a bus ASIC sequence error syslog message is reported to the console as

follows:

%SYS-1-MOD_SEQMISMATCH:Bus asic sequence mismatch occurred on module 8

Additionally, “CentauriInterrupt” and “perseus_intr_hdlr” syslog messages might be generated.

These messages might be generated for some or all installed modules. Ignore these messages.

(CSCdm01334)

Note This problem also occurred after a system power up or a switchover to the redundant

supervisor engine; these issues have been resolved in software release 5.3(3)CSX.

• Occasionally, removal or insertion of a module does not generate any syslog messages.

(CSCdm63338)

• Enabling RSVP installs local ACLs when COPS is the policy and DSBM is enabled on the port.

This problem is caused when you conﬁgure a port to have COPS policy instead of local NVRAM

policy and then you enable DSBM. The workaround is to enable DSBM ﬁrst and then change the

policy to COPS. If the port policy is already COPS, toggle this conﬁguration to avoid the problem

described. (CSCdp52924)

Resolved Caveats in Software Release 5.3(4)CSX

This section describes resolved caveats in supervisor engine software release 5.3(4)CSX:

• When a lot of QoS and/or Security ACLs are conﬁgured on the switch, the switch may

occasionally reset. This problem is resolved in software release 5.3(4)CSX. (CSCdp17331)

• When an RMON alarm is conﬁgured for ATM related MIB objects, the switch used to stop

responding to SNMP requests. The workaround was to avoid conﬁguring the RMON alarm on

ATM related MIB objects or to reset the switch if the alarm was conﬁgured. This problem is

resolved in software release 5.3(4)CSX. (CSCdp48766)

Note that this is a global command that will affect all the 10/100 UTP modules in the switch and

cause an increase of 3 seconds for reconvergence if you have other switches connected to these

10/100 UTP ports. Use this command only as a workaround for interoperating with out-of-spec

NICs.

• The clear conﬁguration command on the MSM does not properly clear the conﬁguration of the

trunk. Some of the trunk ports have VLAN 1 removed and some do not. This might prevent

setting the port-channel with other MSM ports. The workaround is to reset the MSM module.

This problem is resolved in software release 5.3(4)CSX. (CSCdp11427)