VRF stands for virtual routing and forwarding. When you create a vrf, you tell it what routes to import/export. Then you assign that vrf to an interface. Once the vrf is attached to an interface, the switch/router creates a separate routing table to hold those routes. To see those, you'd type "sho ip route vrf MGNT-VRF".
VRF are used in MPLS and VRF-Lite implementations. So a vrf would look like this:
ip vrf MGNT-VRF
rt export 100:100
rt import 100:100
ip vrf Red
rd both 200:200 (export and import)
Under the interface:
ip vrf forwarding Red
ip address 192.168.200.1 255.255.255.0
ip vrf forwarding MGNT-VRF
ip address 192.168.100.1 255.255.255.0
Any global address that you have on your switch will still be in what's now called the "global routing table" and any addresses assigned to the above 2 customers are in their respective VRF.
I guess that what you wanted to say but isn't clear is that the VRF is a separate routing table within a router. VRFs are to a router what VLANs are to a switch. Using VRFs, it is possible to virtualize a single router into several instances, each of them being (relatively) independent of each other, allowing for overlapping subnets, separate instances of routing protocols, separate set of interfaces assigned to each VRF, etc.
"Once the vrf is attached to an interface, the switch/router creates a separate routing table to hold those routes."
I thought I said that here...
Either way, the OP stated that it wasn't working while pinging to the switch from a connected host, but can from another switch. Chances are the vrf that the user is in isn't importing the route that the vrf MGNT-VRF is exporting OR the user isn't in a vrf and the management address is which would then need to leak the address in the global routing table. Correct?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...