Looking for some info and recommendations about using Site-to-Site VPNs for SNMP device polling.
My company is looking in to starting a NOC and being able to remotly monitor customer devices, as well as doing proactive/reactive work on their devices. One problem that will likely come up will be overlapping addressing between customers and us. The way around this seems to be to use NAT to re-assign customer subnets into an addressing scheme that we will decide (essentially virtual subnets).
HQ - 10.254.1.0/24
Customer 1 - 10.1.1.0/24 (NAT to appear as 10.100.1.0/24)
Customer 1 - 10.1.2.0/24 (NAT to appear as 10.100.2.0/24)
Customer 1 - 10.1.3.0/24 (NAT to appear as 10.100.3.0/24)
Customer 2 - 10.1.1.0/24 (NAT to appear as 10.101.1.0/24)
Customer 2 - 10.1.2.0/24 (NAT to appear as 10.101.2.0/24)
Customer 2 - 10.1.3.0/24 (NAT to appear as 10.101.3.0/24)
From HQ there would be an IPsec VPN using public addressing to each customer site, from which we should then be able to poll any device on any private subnet (assuming there is a corresponding NAT entry the subnet the device resides).
Does this seem the typical approach (or even correct)? Does anyone else out there do something similar and can give some more info on their setup?
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...
[toc:faq]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 and UDP are I...