Routing

 View Only
last person joined: 23 hours 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.
Back to discussions
Expand all | Collapse all

VPLS Reachability Issue Between DC and DRC (ACX5048 - VLAN 353)

  • 1.  VPLS Reachability Issue Between DC and DRC (ACX5048 - VLAN 353)

    Posted 07-28-2025 06:28
    Edited by Mostafa Nabil 08-01-2025 15:35

    Hello Community,

    I am working on a VPLS deployment using three Juniper ACX5048 routers and facing a reachability issue I'd like to get your insights on.

    Topology Overview:

    • PE1 and PE2 are located at the main site (DC), acting as Primary and Secondary VPLS PEs respectively.

    • PE3 is located at a remote site (DRC) and acts as the spoke in the VPLS topology.

    • PE1 and PE2 are individually connected to a stacked switch at the main site (note: the routers themselves are not stacked).

    • PE3 is connected to a stacked switch at the DRC via two links configured as an LACP bundle

      Topolgy

      Configuration Context:

      • PE2 is configured as the Primary VPLS PE.

      • PE1 is configured as the Secondary VPLS PE.
        using below 

        PE1

        set interfaces ae2 unit 353 encapsulation vlan-vpls
        set interfaces ae2 unit 353 vlan-id 353

        set routing-instances RI-TCC-VPLS-SECONDARY-HUB instance-type vpls
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls site TCC-CE interface ae2.353
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls site TCC-CE site-identifier 1
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls site TCC-CE multi-homing
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls site TCC-CE site-preference backup
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls site-range 5
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls no-tunnel-services
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB protocols vpls mac-flush
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB forwarding-options family vpls filter input VPLS-FLOOD-FILTER
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB interface ae2.353
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB route-distinguisher 10.128.0.93:404
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB vrf-import PS-VPLS-SECONDARY-IMPORT
        set routing-instances RI-TCC-VPLS-SECONDARY-HUB vrf-export PS-VPLS-SECONDARY-EXPORT

        -----------------------------------------------------------------------------------------------------
        PE2
        set interfaces ae2 unit 353 encapsulation vlan-vpls
        set interfaces ae2 unit 353 vlan-id 353

        set routing-instances RI-TCC-VPLS-PRIMARY-HUB instance-type vpls
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls site TCC-CE interface ae2.353
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls site TCC-CE site-identifier 1
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls site TCC-CE multi-homing
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls site TCC-CE site-preference primary
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls site TCC-CE active-interface primary ae2.353
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls site-range 5
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB protocols vpls no-tunnel-services
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB forwarding-options family vpls filter input VPLS-FLOOD-FILTER
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB interface ae2.353
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB route-distinguisher 10.128.0.94:404
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB vrf-import PS-VPLS-PRIMARY-IMPORT
        set routing-instances RI-TCC-VPLS-PRIMARY-HUB vrf-export PS-VPLS-PRIMARY-EXPORT

        --------------------------------------------------------------------
        PE3 spoke 
        set interfaces ae8 unit 353 encapsulation vlan-vpls
        set interfaces ae8 unit 353 vlan-id 353

        set routing-instances RI-TCC-VPLS-SPOKE instance-type vpls
        set routing-instances RI-TCC-VPLS-SPOKE protocols vpls site CE-2 site-identifier 2
        set routing-instances RI-TCC-VPLS-SPOKE protocols vpls site-range 5
        set routing-instances RI-TCC-VPLS-SPOKE protocols vpls no-tunnel-services
        set routing-instances RI-TCC-VPLS-SPOKE forwarding-options family vpls filter input VPLS-FLOOD-FILTER
        set routing-instances RI-TCC-VPLS-SPOKE interface ae8.353
        set routing-instances RI-TCC-VPLS-SPOKE route-distinguisher 10.128.0.2:404
        set routing-instances RI-TCC-VPLS-SPOKE vrf-import PS-VPLS-SPOKE-IMPORT
        set routing-instances RI-TCC-VPLS-SPOKE vrf-export PS-VPLS-SPOKE-EXPORT

    Issue Observed:

    When I add VLAN 353 to the VPLS routing instances on both PE1 and PE2, there is no connectivity between the DC and DRC.

    However, when I remove VLAN 353 from PE1, reachability between DC and DRC is restored.

    Could anyone assist in identifying the root cause of this issue? I've attached the relevant configuration snippets below.



    ------------------------------
    Mostafa Nabil
    ------------------------------