cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
398
Views
10
Helpful
6
Replies
dampfhammer
Beginner

NAT overload VRF to Global

On a C1101-4P two VRFs "ABC" and "DEF" and internet access on G0/0/0.

I'd like to NAT overload both VRFs (VLAN interfaces) to G0/0/0.

 

Here's the relevant config:

 

vlan 10
 name ABC
!
vlan 20
 name DEF

vrf definition ABC
 rd 10:10
 !
 address-family ipv4
  route-target export 10:10
  route-target import 10:10
 exit-address-family

vrf definition DEF
 rd 20:20
 !
 address-family ipv4
  route-target export 20:20
  route-target import 20:20
 exit-address-family

interface GigabitEthernet0/0/0
 description #W UPLINK-TO-INET
 ip address 1.2.3.1 255.255.255.248
 ip nat outside
 media-type rj45
 negotiation auto

interface Vlan10
 description #C ABC
 vrf forwarding ABC
 ip address 192.168.9.254 255.255.255.0
 ip nat inside
 standby version 2
 standby 10 ip 192.168.9.1
 standby 10 priority 110
 standby 10 preempt
 standby 10 name ABC

interface Vlan20
 description #C DEF
 vrf forwarding DEF
 ip address 172.16.0.254 255.255.255.0
 ip nat inside
 standby version 2
 standby 20 ip 172.16.0.1
 standby 20 priority 90
 standby 20 preempt
 standby 20 name DEF

ip nat inside source list ABC interface GigabitEthernet0/0/0 vrf ABC overload
ip nat inside source list DEF interface GigabitEthernet0/0/0 vrf DEF overload
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/0 1.2.3.2 name #DEFAULT-TO-INET
ip route vrf ABC 0.0.0.0 0.0.0.0 1.2.3.2 global name #DEFAULT-TO-INET-VRF-ABC
ip route vrf DEF 0.0.0.0 0.0.0.0 1.2.3.2 global name #DEFAULT-TO-INET-VRF-DEF

For testing purposes I have a Loopback Lo0 with IP 50.50.50.50/32 in Global routing table. Also, HSRP is not in use (second device not active).

 

I'm able to reach the IP's 192.168.9.254 and 192.168.9.1 from my client. But never the IP 50.50.50.50 or the INET interface.

Software version is: 17.03.04a (also tried with 16.12.05)

 

Can someone guide me in the right direction?

1 ACCEPTED SOLUTION

Accepted Solutions

Hello
I wasnt aware you didnt have a valid "next hop", the assumption was that you had.
I am quite sure a NAT rtr cannot translate to itself hence the failure, once you created a valid reachable "nexthop" then translation became appllicable.


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

View solution in original post

6 REPLIES 6
paul driver
VIP Expert