Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
After entering the command "boot enable-break" in configuration mode ("Enable Break" under "show boot" now shows "yes") the switch will stop loading IOS if you send it a break via the console port while it is loading the IOS. It will then give the m...
I'm trying to migrate from a PIX to an ASA but the new NAT commands are driving me nuts. I got most of it working but I still can't figure out my reverse NATs. On the PIX the command is:static (outside,inside) tcp 1.1.1.1 bgp 2.2.2.2 bgp netmask 25...
http://www.cisco.com/en/US/prod/collateral/routers/ps5854/eol_c51-631228.html states the replacement for C2851-VSEC-SRST/K9 is C2951-CME-SRST/K9 with FL-SRST+FL-CME-SRST-100. I am easily able to find C2951-CME-SRST/K9 and FL-CME-SRST-100, but I am u...
If I configure two 3Com switches to run lacp on all ports, I can then connect any ports between the two switches and they will automatically determine which ports they share and turn those ports into a channel.With Cisco switches it appears I have to...
The bug is named Heartbleed, and Cisco refers to it as such. Heartbeat is the section of code that contains the bug, and thus where the name Heartbleed came from in the first place.
When I run the packet-tracer with a nonsense internal IP then the destination NAT is correctly applied. So it looks like the ASA doesn't bother with the destination NAT if the packet matches a source PAT rule.
Neither IP is configured on the ASA or in any subnet the ASA is in. Output of the packet-tracer command is below. The source IP appears to be being PAT'd correctly but the destination IP is not being modified.Phase: 1Type: ACCESS-LISTSubtype:Result...
