Data Center

 View Only
last person joined: 3 days ago 

Ask questions and share experiences about Data Center Architecture and approaches.

Q-in-Q through EVPN-VXLAN Fabric

  • 1.  Q-in-Q through EVPN-VXLAN Fabric

    Posted 11-22-2024 16:29

    Hey all, looking for an assist on a use case I have:

    (similar to traffic pattern 3 in  EVPN User guide)

    scenario:  C-Tagged traffic is received on ingress interface.  S-Tag is pushed on ingress.  packet transits my fabric and I hand off dual-tagged packet to the next service provider.  I have IP reachability however my dual-tagged outer (S-Tag) is received as ether-type 8100.  My requirement is to deliver the S-Tag with ether-type of 88a8.  Do I have a way on the QFX platform to tag with 88a8 either at the ingress or egress port?

    additional info:

    QFX5120 Leaf switches running  22.2R3-S3.18.  ERB configuration

    CE Device (scapy)-.Qfx5120 Leaf->Qfx5120 Spine->Qfx5120 Leaf-> SP handoff (using Spirent STC/packet capture.  This is pre-prod)

    S-Tag=100

    C-Tag=200

    mac-vrf.  service-type vlan-bundle

    Current Port configuration:

    Ingress

    set interfaces xe-0/0/1 flexible-vlan-tagging
    set interfaces xe-0/0/1 encapsulation extended-vlan-bridge
    set interfaces xe-0/0/1 ether-options ethernet-switch-profile tag-protocol-id 0x88a8
    set interfaces xe-0/0/1 unit 100 vlan-id-list 100-200

    Egress

    set interfaces xe-0/0/53:0 flexible-vlan-tagging
    set interfaces xe-0/0/53:0 encapsulation extended-vlan-bridge
    set interfaces xe-0/0/53:0 ether-options ethernet-switch-profile tag-protocol-id 0x88a8
    set interfaces xe-0/0/53:0 unit 100 vlan-id 100
    set interfaces xe-0/0/53:0 unit 100 input-vlan-map pop
    set interfaces xe-0/0/53:0 unit 100 output-vlan-map push

    Routing Instance

    set routing-instances Q-in-Q_GB_TEST instance-type mac-vrf
    set routing-instances Q-in-Q_GB_TEST protocols evpn encapsulation vxlan
    set routing-instances Q-in-Q_GB_TEST protocols evpn default-gateway no-gateway-community
    set routing-instances Q-in-Q_GB_TEST protocols evpn extended-vni-list all
    set routing-instances Q-in-Q_GB_TEST vtep-source-interface lo0.0
    set routing-instances Q-in-Q_GB_TEST service-type vlan-bundle
    set routing-instances Q-in-Q_GB_TEST interface xe-0/0/53:0.100
    set routing-instances Q-in-Q_GB_TEST route-distinguisher 10.x.x.x:5
    set routing-instances Q-in-Q_GB_TEST vrf-target target:424xxxxxx:5
    set routing-instances Q-in-Q_GB_TEST vlans v100 interface xe-0/0/53:0.100
    set routing-instances Q-in-Q_GB_TEST vlans v100 vxlan vni 10100
    set routing-instances Q-in-Q_GB_TEST vlans v100 vxlan encapsulate-inner-vlan

    one other note, a different use case I have where my customer sends both C and S tags is received correctly.  i.e. I generate the dual tagged packet in Scapy and it is received with an S-Tag ethertype of 88a8.   The fabric successfully delivers the packet with the correct formatting.

    Appreciate any help that can be provided!



    ------------------------------
    GEORGE BURKE
    ------------------------------