I have two IDSM2 in two 6500 running 6.0(3)E1. Both of these IDSM are rebooting several times per day. They are running at around 60-70% CPU set in promiscuous mode monitoring three VLANs filtered on two gigabit trunks each.
The only thing I see on the 6500s is "18150: Card in module 5, is being power-cycled off (Module not responding to Keep Alive polling)" just before they reboot.
Where do I start? Is there a crashinfo to collect?
The IDSMs were delivered as "refurbished" with 4.1 installed, I have since upgraded them to 5.1.6-E1 and then to 6.0(3)E1. Is this setup too much to handle for the IDSM?
After some traffic and inspection tuning it seems to me that it was the amount of traffic that caused this problem for me. When I decreased the inspected traffic from vlans (some 500mbit/sec) to specific interfaces AND lowered the packet logging the IDSM stopped rebooting.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...