- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 09:55 AM - edited 03-05-2019 09:32 AM
Hi all, first post over here whoo!
I have a question, but first heres the scenario I have and what I'm trying to do.
A customer that we recently acquired monitors their sites using certain IP addresses (no suprise there, pretty typical right), well when we bought them we changed their IP scheme to fall in line with the rest of the network. To make a long story short heres the deal. They monitor "DeviceA" using this local IP address (10.200.10.65), well all the sites use a 192.168.31.0/24 scheme so we do NAT at the router to translate the local IP to the site subnet (for this example we'll use 10.6.223.0/24). This site we converted NAT's 192.168.31.65(inside) -----> 10.6.223.65(outside) so anyone outside that site looking to reach 10.6.223.65 can do so, while the devices stay hot swappable between sites with a config of 192.168.31.65. Well they need to be able to continue to monitor "DeviceA" from the address 10.200.10.65, while our team monitors the same device, but from 10.6.223.65. Is there a way to NAT that one local 192 address to both 10.200.10.65 AND 10.6.223.65? I was using this config
ip nat inside source static network 192.168.31.65 10.6.223.65 /32 no-alias
ip nat inside source static network 192.168.31.65 10.200.10.65 /32 no-alias
But as some of you experienced members can probably tell off the bat, it didnt work. That 192 address is already mapped to the 10.6.223.65, I didnt think the NAT pool would be a great solution given that the two addresses are so far apart from each other, BUT if someones got any tricks please share. Hopefully I explained myself completely and concisely. Let me know what yall think.
Solved! Go to Solution.
- Labels:
-
Other Routing
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 10:56 AM
dmacias066,
Have you tried appending the 'extendable' keyword to your static nat statements?
Router#(config)ip nat inside source static network 192.168.31.65 10.6.223.65 /32 extendable no-alias Router#(config)ip nat inside source static network 192.168.31.65 10.200.10.65 /32 extendable no-alias
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 10:56 AM
dmacias066,
Have you tried appending the 'extendable' keyword to your static nat statements?
Router#(config)ip nat inside source static network 192.168.31.65 10.6.223.65 /32 extendable no-alias Router#(config)ip nat inside source static network 192.168.31.65 10.200.10.65 /32 extendable no-alias
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 11:07 AM - edited 11-27-2017 11:07 AM
Hello
try:
ip nat inside source static network 192.168.31.65 10.6.223.65 extendable
ip nat inside source static network 192.168.31.65 10.200.10.65 extendable
res
Paul
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2017 12:03 PM
Thanks for the quick response folks. The router took my commands after adding the "extendable" to it. Let me test the function before I go about marking this issue as resolved!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 07:57 AM
Thanks everyone! I had to do additional specific-to-me configuration to get this working but the "extendable" keyword and the end of the command accomplished what I was wanting to do. Thanks again!
