Question

A network engineer configures VRF-Lite on an IOS router to separate CUSTOMER-A traffic. The engineer runs: 'ip vrf CUSTOMER-A', then under interface GigabitEthernet0/1 applies 'ip vrf forwarding CUSTOMER-A' and 'ip address 10.1.1.1 255.255.255.0'. The directly connected host 10.1.1.10 cannot be reached with a normal 'ping 10.1.1.10', and 'show ip route' does not list the 10.1.1.0/24 network. What is the most likely cause?

Accepted Answer

The interface route exists in the CUSTOMER-A VRF routing table, so the plain 'ping' and 'show ip route' commands query only the global table; VRF-aware commands must be used.

Answer

The 'ip vrf forwarding' command must be applied after the IP address, so the address was removed and no connected route was installed.

Answer

VRF-Lite requires an MPLS core and a route distinguisher with 'address-family ipv4' under BGP before any connected route can appear.

Answer

The interface is administratively down because assigning it to a VRF automatically shuts the interface until 'no shutdown' is reissued.