We are changing our T1 server to an other company; I know I need to change the IP address to the new provider on the outside, do I need to change the translation table and all ACL?s assoc with the old IP address. It would greatly appreciate if someone can put together some steps to follow or point me to a good document. Thanks
You need to change anything that references the old IP addresses, including but not limited to: NAT entries, ACL's, access management, DNS entries, VPN clients/peers, and anything else that might rely on the old addresses.
The previous poester spelled it out for you accurately, you need to make a thorought assesment of your current outside public IP block and create a change cutover plan that not only covers what Srue indicated but also default routes and one-to-one nat statements.
Start with ducumenting current static NATs related to public IP and internal mappings, global nat pools for outside interface etc.., from past experiences I have found that you mostly need to change logical IP addresses for one-to-one nats
and global pools, pay attention to your current local DNS services and current ISP and the new ISP.
If you have any other concerns or need assistance please drop us a line.
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...