After going through pretty much every document I could find on ACL-Paritions, I have a few questions I couldn't find answers to.
I have inherited 2 old 6500 switches with FWSM (in fail-over) - each FWSM with 12 contexts and 5 partitions. I have 1 partition which is completely full at the moment. There are 2 contexts on this partition, one fairly huge and a smaller one.
There is another partition to which I could move the smaller context.
1; If I change the value of "allocate-acl-partition X" on the fwsm to move a context, does it take effect immediately, or after a full FWSM or context reload?
2; I'm assuming this should be done on the FWSM on both switches at the same time?
3; Other related question; some of my partitions are "Exclusive" and one is "Non-exclusive". What would the difference be? I couldn't find documentation on this. My guess is that non-exclusive partition can host partitions for which the partition is non explicit ("allocate-acl-partition X") while to use an exclusive partition, you must set the partition to use in the context?
This AMA will serve as the Q&A for the Cisco Live Digital breakout DGTL-BRKSEC-1011 - "A Challenger Appears: Defending Mailboxes in the Cloud" which covers a brand new product which will be announced during the event: Cloud Mailbox Defense.
I've fixed this before but now I'm running into a different type of an issue. My firewall isn't booting to the image so I have to keep reloading the image onto the ASA. Any help would be appreciated. Also my Config-Register is set to 0x1. As of right now,...
Join us live on Tuesday, May 19th at 10 am PT (and on demand after) as we officially bust the myths around SMBs and cybersecurity. Join our experts for a live Cisco Chat - we'll share some fascinating survey results, and outline key factors for a suc...
Join us live on Tuesday, May 19th at 10 am PT (and on demand after) as we officially bust the myths around SMBs and cybersecurity. Join our experts for a live Cisco Chat - we'll share some fascinating survey results, and outline key factors for a success...
Recently I upgraded an ASA 5525-X HA pair to the latest recommended code (9.12(3)12). Our previous release was 9.8(4)17. This was a routine upgrade to address a recent set of vulnerabilities announced by Cisco. A review of the release notes (bot...