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.  Automatic Failover for Secondary Link Outage

    Posted 02-07-2024 04:27
    {master}[edit]
    ABC COMPANY_CORE# run show configuration | match ABC_IIG_IN | display set
    set policy-options policy-statement ABC_IIG_IN term 1 from route-filter 0.0.0.0/0 exact
    set policy-options policy-statement ABC_IIG_IN term 1 then local-preference 200
    set policy-options policy-statement ABC_IIG_IN term 1 then accept
    set policy-options policy-statement ABC_IIG_IN term 100 then reject
    set routing-instances CTG_CORE protocols bgp group eBGP_ABC_Sec neighbor 123.49.54.165 import ABC_IIG_IN

    {master}[edit]
    ABC COMPANY_CORE# run show configuration | match ABC_IIG_OUT | display set
    set policy-options policy-statement ABC_IIG_OUT term 1 from route-filter 10.101.0.0/24 exact
    set policy-options policy-statement ABC_IIG_OUT term 1 from route-filter 45.24.10.0/24 exact
    set policy-options policy-statement ABC_IIG_OUT term 1 from route-filter 103.17.24.0/24 exact >> This line add manually after secondary link down
    set policy-options policy-statement ABC_IIG_OUT term 1 then as-path-prepend "65534 65534"
    set policy-options policy-statement ABC_IIG_OUT term 1 then accept
    set policy-options policy-statement ABC_IIG_OUT term 100 then reject
    set routing-instances CTG_CORE protocols bgp group eBGP_ABC_Sec neighbor 123.49.54.165 export ABC_IIG_OUT
    ==================================================================================================================
    {master}[edit]
    ABC COMPANY_CORE# run show configuration | match ABC_IIG_Sec_IN | display set
    set policy-options policy-statement ABC_IIG_Sec_IN term 1 from route-filter 0.0.0.0/0 exact
    set policy-options policy-statement ABC_IIG_Sec_IN term 1 then accept
    set policy-options policy-statement ABC_IIG_Sec_IN term 100 then reject
    set routing-instances CTG_CORE protocols bgp group eBGP_ABC_Pri neighbor 123.49.54.229 import ABC_IIG_Sec_IN

    {master}[edit]
    ABC COMPANY_CORE# run show configuration | match ABC_IIG_Sec_OUT | display set
    set policy-options policy-statement ABC_IIG_Sec_OUT term 2 from route-filter 103.17.24.0/24 exact
    set policy-options policy-statement ABC_IIG_Sec_OUT term 2 then as-path-prepend "65534 65534"
    set policy-options policy-statement ABC_IIG_Sec_OUT term 2 then accept
    set policy-options policy-statement ABC_IIG_Sec_OUT term 100 then reject
    set routing-instances CTG_CORE protocols bgp group eBGP_ABC_Pri neighbor 123.49.54.229 export ABC_IIG_Sec_OUT
    ==============================================================================================================
    Problem :
    Here , firsly share primary link incoming and outgoing policy
    ABC_IIG_IN
    ABC_IIG_OUT

    Then, share secondary link policy
    ABC_IIG_Sec_IN
    ABC_IIG_Sec_OUT

    Here , our mainly 2 prefix 45.24.10.0/24 and 103.17.24.0/24
    45.24.10.0/24 prefix use only primary link
    103.17.24.0/24 prefix use only secondary link

    Problem is , when secondary link is down , we manually add 103.17.24.0/24 prefix in the primary link. But i want this work will be
    automatically . Have any process?? Pls share here



    ------------------------------
    Md.Kamruzzaman Khan
    Sr .Core Engineer at Planning and Implementation
    parveaj_cse@yahoo.com
    https://www.linkedin.com/in/md-kamruzzaman-khan/
    Bangladesh
    =================================================
    ------------------------------


  • 2.  RE: Automatic Failover for Secondary Link Outage

    Posted 02-08-2024 20:00

    If I follow you correctly you can change the export policy for both peers should include both prefixes.

    With the prefix you want to be primary on that peer have no prepend at all.

    With the prefix you want as backup for that peer have the two AS prepend.

    During normal operations each prefix will be primary on each side.

    When a peer fails, the second prefix is automatically active on the remaining peer.



    ------------------------------
    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
    http://puluka.com/home
    ------------------------------

    Original Message


  • 3.  RE: Automatic Failover for Secondary Link Outage

    Posted 02-12-2024 05:10

    Thanks for your reply.

    Now, I mainly want the 45.24.10.0/24 prefix to use only the primary link, and the 103.17.24.0/24 prefix to use only the secondary link. When one link is down, then both prefixes will run on the remaining active link. Can you help me with this? You can also share a demo example for my understanding."



    ------------------------------
    Md.Kamruzzaman Khan
    Sr .Core Engineer at Planning and Implementation
    parveaj_cse@yahoo.com
    https://www.linkedin.com/in/md-kamruzzaman-khan/
    Bangladesh
    =================================================
    ------------------------------

    Original Message