Anthony
If you can readdress as Collin suggests that would probably be the easiest thing to do.
But it's not clear from your diagram exactly how things works. In the DC vlans 17 & 18 exist on the switch shown. This switch is connected to a switch in the office site. But your diagram does not make it clear whether the office switch has vlans 17 and 18 on it as well.
If it does, then what is the interconnect configured as ? If it is a trunk allowing vlans 17 & 18 across then -
a) you cannot use NAT on the switches (even if supported)
and
b) you have effectively merged the vlans together in each site with the same IP subnets. This could create problems ie. 192.168.17.10 arps out for 192.168.17.20 and would get 2 replies ie. one from the local host in the same site but then one from the remote 192.168.17.20 in the other site.
It looks like the routing for each subnet is done via the respective ASA so it is only going to be a problem within the same vlan but you need to avoid it.
So the questions are -
1) how is the office switch actually setup ie. is it the same as the DC switch
2) what is the interconnect between the switches configured as ie. an access port link (if so which vlan), a trunk link
Because the routing looks to be done on each ASA is it safe to assume that the switches are only acting as L2 devices ie. neither of the switches have any inter vlan routing on them ?
Finally, depending on which subnets need to communicate with each other between sites it may be possible to use NAT on each ASA before packets are sent to the other site but it really is dependant on how the switch connectivity works.
Even if you readdress you still need to pay attention to the switch connectivity because you could still be merging vlans together, just with different IP subnets.
Jon
