Routing

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.

  • 1.  Configuring the VLAN-Aware Centrally-Routed Bridging Overlay with Virtual Switches on a Spine Device?

    Posted 04-09-2020 22:26

    Hi all,

     

    Im reading this url below and have some question:

    https://www.juniper.net/documentation/en_US/release-independent/solutions/topics/task/configuration/centrally-routed-overlay-cloud-dc-configuring.html#vlan-aware-cro-virtual-switch

     

    On title "Configuring the VLAN-Aware Centrally-Routed Bridging Overlay with Virtual Switches on a Spine Device" may i know why need to put "vlan-id none". Is it supposedly need to put vlan-id value? Or is it as per design no need to assign vlan if choosing "virtual switch" method? Appreciate someone feedback

     

    set routing-instances VS1 vlans VNI_90000 vlan-id none
    set routing-instances VS1 vlans VNI_90000 l3-interface irb.900
    set routing-instances VS1 vlans VNI_90000 vxlan vni 90000
    set routing-instances VS1 vlans VNI_100000 vlan-id none
    set routing-instances VS1 vlans VNI_100000 l3-interface irb.1000
    set routing-instances VS1 vlans VNI_100000 vxlan vni 100000


  • 2.  RE: Configuring the VLAN-Aware Centrally-Routed Bridging Overlay with Virtual Switches on a Spine Device?
    Best Answer

     
    Posted 04-09-2020 22:41

    Hi

     

    I believe vlan-id none is used for the vlan translation in the newer 17.3 and later for vlan aware services. You can get more information in the below link

     

    https://www.juniper.net/documentation/en_US/junos/topics/example/evpn-based-services.html

     

    Starting with Junos OS Release 17.3R1, VLAN-based service with VID translation as described in RFC 7432 is supported. This means that Junos supports VID translation and the customer can have a different VID for each VLAN. As described in the RFC, the VID translation must be performed at the egress PE device while the MPLS encapsulated frames should also retain the originating VID. Figure 2 illustrates a topology where CE devices use different CE-VIDs for single VLAN-based EVI.

    Figure 2: Multiple VIDs with VLAN Translation

    For more information on configuring VLAN-based service, see Configuring EVPN with VLAN-Based Service.

    The following is a sample configuration for a single VLAN-based EVI. The same VID is used on all the PE devices, so VLAN translation is not required. In this example, the VLAN-id=none statement is included to remove the originating VID and to set the Ethernet tag ID to zero in the MPLS frame.

     

    Hope this helps