Labs

 View Only
last person joined: 10 days ago 

Discover how to get the most of Juniper labs and share what you've built.

TPID configuration for IRB interface

  • 1.  TPID configuration for IRB interface

    Posted 03-20-2024 23:38

    Hi, 

    I currently studdying for Junos certification exam.  For my studdy process, I'm using Juniper VLAB to test my knowledge and what I understood.

    In the current issue, I'm trying to understand bridging process on MX platform.  For this lab session, I had used the topology named  "BGP - Multi-AS with Dual Route Reflectors".

    All routeur been erased and I apply the configuration attached to this post.  I already post something about this before, but I was mixing some concept so it wasn't work at all.   Now, I have some interesting results, but it still not working completely.

    For now I had only configured the following host : vMX1, vMX2, vRR1 & vRR2.

    Right now vRR1 can :

    • ping 10.100.111.111 sourcing 10.100.111.1
    • ping 10.100.222.222 sourcing 10.100.222.1
    • ping 10.100.111.2 sourcing 10.100.111.1
    • ping 10.100.222.2 sourcing 10.100.222.1

    The vRRx router were in place to try to undersand where the connectivity was failling at the beginning.

    But not, noting involving routing through the trunk link GE-0/0/0, but since route to the other network is not configured this explanable.

    Same as for vRR2.

    But what is not explainable is : vMX1  can't ping any L3 interface on vMX2, and the reserve case is also true.

    On both router I'm getting MAC address of the remote workstation when I ping the L2 interface from vRR1 to vRR2  and vice versa.

    I past I was suspecting a compatibility issue on Juniper VLAB for L2 bridging fonction for vMX devices. 

    Here their answer : 

    "Thank you for reaching out! Yes, you should be able to do L2 with vMX's. I can see that you have VLAN configuration as well. On JCL however, the virtual devices are deployed on ESXi which drops frames with TPID value of 0x8100. We do have a workaround for this: you can configure a TPID value of 0x9100 which will not be dropped. I have attached a document that goes over an example of such configuration. Please let me know if you have any questions or face any issues!"

    They provide me a workaround (attached to this post (vLabs L2 workaround.docx))  for some reason I wasn't to implement it as explained in the document.  As I understand, my case is like the "Config on vMX-A1" whith in the word document.

    So my topology need this confuiguration based on the document :  (As I understand)

    for Interface trunk configuration : 

    set interfaces ge-0/0/0 gigether-options ethernet-switch-profile tag-protocol-id 0x9100
    set interfaces ge-0/0/0 unit 100 vlan-tags outer 0x9100.100
    set interfaces ge-0/0/0 unit 200 vlan-tags outer 0x9100.200
    set interfaces ge-0/0/0 unit 0 family bridge interface-mode trunk
    set interfaces ge-0/0/0 unit 0 family bridge vlan-id-list [ 100 200 ]

    and for bridge-domain configuration :
     
    set bridge-domains vlan-200 vlan-tags outer 0x9100.100
    set bridge-domains vlan-200 vlan-tags outer 0x9100.200
    But I wasn't able to commit.  "flexible-vlan-tagging" or similar was missing.
    I finally found this trunk interface configuration working (identica;l on both router vMX and vMX:
    cluser@vMX1# show interfaces ge-0/0/0 | display set 
    set interfaces ge-0/0/0 description VMX2
    set interfaces ge-0/0/0 flexible-vlan-tagging
    set interfaces ge-0/0/0 gigether-options ethernet-switch-profile tag-protocol-id 0x9100
    set interfaces ge-0/0/0 unit 0 family bridge interface-mode trunk
    set interfaces ge-0/0/0 unit 0 family bridge vlan-id-list 100
    set interfaces ge-0/0/0 unit 0 family bridge vlan-id-list 200
    With this bridge-domain configuration :
    jcluser@vMX1# show bridge-domains | display set 
    set bridge-domains vlan-100 vlan-tags outer 0x9100.100
    set bridge-domains vlan-100 routing-interface irb.100
    set bridge-domains vlan-200 vlan-tags outer 0x9100.200
    set bridge-domains vlan-200 routing-interface irb.200 
    Configuration of the respective IRB interface from each vMXx
    vMX1 :
    jcluser@vMX1# show | display set 
    set interfaces irb unit 100 family inet address 10.100.111.111/24
    set interfaces irb unit 200 family inet address 10.100.222.111/24
    vMX2 : 
    jcluser@vMX2# show | display set                               
    set interfaces irb unit 100 family inet address 10.100.111.222/24
    set interfaces irb unit 200 family inet address 10.100.222.222/24
    On the ge-0/0/0 I had to setup something due of the the tpid special configuration, but I haven't found anything functionning for the IRB interface.  Should I modify something to make the L3 interface be reachable over the trunk interface between the 2 vMX ?
    I found this documentation about changing the tpid under the IRB interface.
    But on the vMX, the section "rewrite-rules" doesn't exist.
    Is anything I can do to make it work as it supposed to be ?
    Thank you 


    ------------------------------
    Xine
    ------------------------------

    Attachment(s)

    txt
    vmx2 v3.txt   2 KB 1 version
    txt
    vmx1 v3.txt   2 KB 1 version
    txt
    vRR1.txt   1 KB 1 version
    txt
    vRR2.txt   1 KB 1 version