Both FWSM in our core switches went active/active and protected subnets have partial accessibility.
- We have 2 x Cisco Catalyst 6509 switches running IOS version 12.2(18).
- Each switch has a FWSM internal firewall module.
- Both are multi-context split into 2 groups.
- One FWSM should be active for both groups while the other FWSM should be standby.
We upgraded our 6509s to IOS version 12.2(33). This bounced each switch. After the upgrade we noticed that both FWSM were active (not a good thing). We ended up reverting the IOS on both 6509s, but both FWSM remained active.
Before the upgrade our busiest context was at 97% memory utilization measured by the message received after modifiying the rule set on the command line. Now the rules won't compile fully and we're left with a partial config.
show memory shows 67% free memory out of 1gig of RAM.
show resource acl shows 12 partitions and the 97% memory utilized context has only 6,053 out of a max of 14,173 rules in use.
show failover shows each FWSM thinks it is the secondary and its mate is unknown.
We have one of the FWSMs powered off and are trying to get the other one up and stable with a good config, but it still refuses to compile the rule set.
Can somebody explain what the 97% memory utilization really represents? If this is a resource issue it doesn't appear to be rule related based on the
show resource acl output, but the 97% memory utilized messages make me wonder. What next steps should I take at this point?