One of our end clients encountered a problem with a FWSM module on a Cisco 6513 Switch.
Following an IOS update and a reload after the procedure, we encountered an issue where two VLAN Interfaces configured on the FWSM with DHCP Relay stopped fowarding DHCP packets, thus clients in those VLANs stopped recieving IP addressed via DHCP.
The issue was resolved with removing the "dhcprelay server" command and re-entering it under the VLAN Interface.
After some research I found that various DHCP Relay related bugs were fixed in the latest FWSM version 3.2(28), but there werent any bugs that fit perfectly with all the symptoms of the issue we are facing..
The FWSM was running version 3.2(2) so an upgrade was scheduled.
After the upgrade the issue still occured.
Has anyone encountered something like this before?
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...