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 619 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

396 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. Hi Collin,

    That’s right, it’s a little side effect of replicating everything. All routes are replicated from blue/red to green and vice versa.

    To solve this, it’s better to use a route-map to define what should/shouldn’t be replicated:

    ISP1(config-vrf-af)#route-replicate from vrf Green unicast all route-map RED_PREFIXES

    Rene

  2. 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.

  3. 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

  4. 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

  5. Hi Kevin,

    If the commands are supported and it works then it’s all good. I didn’t know the 7200 also supported this.

    Rene

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