We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 639 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

341 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: ,


Forum Replies

  1. EVN only knows what tags to use since we configured the tags on the VRFs.

    Also, it basically only does this for us:

    interface GigabitEthernet3.10
     description Subinterface for VNET Blue
     encapsulation dot1Q 10
     vrf forwarding Blue
     ip address 192.168.56.5 255.255.255.0
    

    The sub-interface above was created by EVN. If you don’t want to use EVN, you could configure sub-interfaces like this yourself.

  2. Hopefully, this will be easier. I don’t know what it means when it says please use the “code” button to post configurations.
    ISP1:

    vrf definition Blue
     vnet tag 10
     !
     address-family ipv4
     exit-address-family
    !
    vrf definition Red
     vnet tag 20
     !
     address-family ipv4
     exit-address-family
    !
    interface GigabitEthernet1
     vrf forwarding Blue
     ip address 192.168.1.254 255.255.255.0
     negotiation auto
    !
    interface GigabitEthernet2
     vrf forwarding Red
     ip address 192.168.2.254 255.255.255.0
     negotiation auto
    !
    interface GigabitEthernet3
     vnet trunk
     ip address 192.168.56.
    ... Continue reading in our forum

  3. Hello Don.

    I’m assuming the EVN trunk is working and that you’ve checked the VRF configuration, and you’ve successfully verified that the vnet trunk has been created with the appropriate show and ping commands. I’m also assuming you’ve checked the output from the command show derived-confg and that the subinterfaces Gi3.10 and Gi3.20 are showing up. Check these first to see that the EVN is working correctly before any routing has been configured.

    Looking through your config, I’m not able to find something that stands out as an error. It seems like it should

    ... Continue reading in our forum

  4. Hi Mercedes,

    Good question, I can’t think of any technical reason why those routes don’t show up but I think they did it on purpose. EVN is one of those “automatically” solutions (unlike VRF lite) and I think they do it so you don’t accidentally share routes from VRF X > Y > Z unintentionally.

    If you look at vrf Blue on ISP1, it doesn’t have the entire 192.168.2.0/254 network from VRF Red but only 192.168.2.254 (its own IP address).

    Rene

  5. Hello Johnson

    The vrf forwarding command can only be used under the interface configuration. You may be referring to the ip vrf forwarding command which can also be implemented in global configuration mode.

    Cisco explains the difference like so:

    In earlier Cisco IOS releases, you created a VRF to be applied only to an IPv4 address family (single-protocol VRF) by entering the ip vrf command. To activate the single-protocol VRF on an interface, you entered the ip vrf forwarding (interface configuration) command.

    You can now define multiple address families und

    ... Continue reading in our forum

33 more replies! Ask a question or join the discussion by visiting our Community Forum