Routing

last person joined: 5 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.  IP SLA equilvilent for Junos

    Posted 09-25-2016 23:08

    Hi there, I have configured IP SLA equivilent for JUNOS on MX-960 Junos 13.3R1 as shown below

    hedra@MX-960# show services 
    rpm {
        probe A {
            test ICMP {
                probe-type icmp-ping;
                target address 10.0.0.1;
                test-interval 3;
                thresholds {
                    successive-loss 1;
                }
            }
        }
        probe B {
            test ICMP2 {
                probe-type icmp-ping;
                target address 10.0.0.1;
                test-interval 3;
                thresholds {
                    successive-loss 1;
                }
            }
        }
    }
    
    {master}[edit]
    hedra@MX-960# show event-options 
    policy failover {
        events ping_test_failed;
        within 100 {
            trigger on 1;
        }
        attributes-match {
            ping_test_failed.test-owner matches A;
            ping_test_failed.test-name matches ICMP;
        }
        then {
            change-configuration {
                retry count 5 interval 4;
                commands {
                    "delete routing-options static route 2.2.2.2/32 next-hop 10.0.0.2";
                    "set routing-options static route 2.2.2.2/32 next-hop 10.10.10.2";
                }
            }
        }
    }
    policy revert {
        events ping_test_completed;
        within 15 {
            trigger on 1;
        }
        attributes-match {
            ping_test_completed.test-owner matches B;
            ping_test_completed.test-name matches ICMP2;
        }
        then {
            change-configuration {
                retry count 3 interval 3;   
                commands {
                    "delete routing-options static route 2.2.2.2/32 next-hop 10.10.10.2";
                    "set routing-options static route 2.2.2.2/32 next-hop 10.0.0.2";
                }
            }
        }
    }

    {master}[edit]
    hedra@MX-960# show system syslog file test
    daemon info;

    Now what I am concerned with is the chage-config event for reverting back to primary link. as it indicates that the commands will be applied every time there is a successful ICMP responce, will this be any burden on the system because if the primary continues to stay alive then the configuration changes will continue occuring on every successful ICMP responce of probe B.



  • 2.  RE: IP SLA equilvilent for Junos

    Posted 09-29-2016 02:41

    Hi,

     

    the trick is that only one RPM probe is active at the same time. So, you have to include

     

     

    deactivate services rpm probe A
    activate services rpm probe B

     

     

    as change commands in policy failover and vice versa in policy revert.

     

    Cheers,

    Carsten