Can an IDSM2 Bring Down a 6513 ??

[davidculp]

We have had 2 instances in the past 2 months where our 'network' came to a crawl/stop. It is related to our IDSM2 blade in our 6513 via

a) Moments before stoppage, could not ping management intf of IDSM2

b) After issuing reset via the 6513

by the command:

hw-module module 11 reset

The Network returned to normal.

notes: 1) The IDSM2 is a 4.1 sensor with the latest software 4.1.g.

2) There is no TCP Reset or Blocking being done.

I opened a TAC case after the first instance, but a top engineer did not

think a IDSM2 could bring down a 6513.

Thanks for any thoughts !

[marcabal]

There is nothing in the module itself or in the IPS code that could bring the network down when running promiscuous mode.

However, there could be something in the switch code and how it interacts with the module. It would be a switch bug and not an IPS software bug.

I have heard of some issues with spanning tree and the msfc autostate on the supervisor when the IDSM-2 interfaces go down and up.

I am not sure what the state of those DDTS Issues are.

It is possible that there is an issue on the IDSM-2 that causes it to bring it's ports down and up, which could then trigger a spanning tree or msfc autostate issue on the switch itself. So one issue on the IDSM-2 could trigger a separate issue on the switch.

If you were going to attempt further debugging you would want to concentrate on what is happening to both the IDSM-2 and the switch.

You may also want to check what version is running on your switch. You may want to ensure you are running the latest IOS version.