6500 MSFC2 nbar problem

[jheckart]

I have a 6500 with redundant SUP2/MSFC2 runing hybrid. I setup a new SVI to connect a new VLAN to the network, and have been working great. I went ahead and enabled nbar protocol-discovery on the SVI, and started having some instability.

With nbar proto turned on, I began getting these messages in the logs of the sup every 2 minutes -

%SYS-5-MOD_OK:Module 16 is online

On the msfc, I had the following -

%SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=15A

%RUNCFGSYNC-6-SYNCEVENT:

Non-Designated Router is now online

Running Configuration Synchronization will begin in 1 minute

%RUNCFGSYNC-6-SYNCEVENT:

Syncing Running Configuration to the Non-Designated Router

%RUNCFGSYNC-6-SYNCEVENT:

Syncing Startup Configuration to the Non-Designated Router

The msfc has c6msfc2-psv-mz.121-19.E1a.

Is this a bug in my ios version, or what?

Thanks.

[sundar.palaniappan · Accepted solution]

Yes, it does look like this bug. The error messages, you posted, indicate the config doesn't sync up on the redundant MSFC and that triggers the software crash.

CSCec40719 Bug Details

Headline Using NBAR and SRM crashes redundant MSFC

Product IOS

Feature OTHERS Components Duplicate of

Severity 2 Severity help Status Resolved Status help

First Found-in Version 12.1(19)E01 All affected versions First Fixed-in Version 12.1(19.4)E01, 12.1(21.2)E, 12.2(17b)SXA, 12.1(20)EC, 12.1(21.4)EC Version help

Release Notes

A non-designated router (MSFC) in a catalyst 6500 running single-router-mode

(SRM) may fail to synchronize configuration with the designated router and

reload unexpectedly with a software-forced error if using network-based

application recognition (NBAR) in modular QoS when running 12.1(19)E1.

The workaround is to remove the class-maps that have 'match protocol'

configured, or revert back to 12.1(13)E10.

HTH

Sundar

[jheckart]

Thanks Sundar.

It's probably about time to upgrade the ios anyways.