SRX

 View Only
last person joined: yesterday 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.

  • 1.  Event-options Not Working as Desired on SRX340

    Posted 04-09-2024 20:17

    Hey guys,

    I have a Juniper SRX340 running JunOS 21.4R3-S2.3. I have terminated two ISPs on the SRX, and have configured per-flow load-balancing to utilize both the ISPs equally. I am trying to configure event-options to delete a static route when an ISP goes DOWN and re-add it to the routing table when the ISP is back UP.

    Below is my configuration for RPM:

    probe icmp-echo {
    test isp1 {
        probe-type icmp-ping;
        target address 8.8.8.8;
        test-interval 5;
        history-size 30;
        thresholds {
            successive-loss 3;
        }
        destination-interface ge-0/0/0.0;
    }
    test isp2 {
        probe-type icmp-ping;
        target address 8.8.4.4;
        test-interval 5;
        history-size 30;
        thresholds {
            successive-loss 3;
        }
        destination-interface ge-0/0/1.0;
    }
}

    Below is the configuration for event-options:

    policy enable-isp2 {
    events ping_test_completed;
    within 120 {
        trigger on 12;
    }
    within 125 {
        trigger until 13;
    }
    attributes-match {
        ping_test_completed.test-owner matches icmp-echo;
        ping_test_completed.test-name matches isp2;
    }
    then {
        change-configuration {
            commands {
                "set routing-options static route 0.0.0.0/0 next-hop 192.168.10.1";
            }
        }
    }
}
policy disable-isp2 {
    events ping_test_failed;
    within 60 {
        trigger on 6;
    }
    within 65 {
        trigger until 7;
    }
    attributes-match {
        ping_test_failed.test-owner matches icmp-echo;
        ping_test_failed.test-name matches isp2;
    }
    then {
        change-configuration {
            commands {
                "delete routing-options static route 0.0.0.0/0 next-hop 192.168.10.1";
            }
        }
    }
}
policy enable-isp1 {
    events ping_test_completed;
    within 120 {
        trigger on 12;
    }
    within 125 {
        trigger until 13;
    }
    attributes-match {
        ping_test_completed.test-owner matches icmp-echo;
        ping_test_completed.test-name matches isp1;
    }
    then {
        change-configuration {
            commands {
                "set routing-options static route 0.0.0.0/0 next-hop 192.168.11.1";
            }
        }
    }
}
policy disable-isp1 {
    events ping_test_failed;
    within 60 {
        trigger on 6;
    }
    within 65 {
        trigger until 7;
    }
    attributes-match {
        ping_test_failed.test-owner matches icmp-echo;
        ping_test_failed.test-name matches isp1;
    }
    then {
        change-configuration {
            commands {
                "delete routing-options static route 0.0.0.0/0 next-hop 192.168.11.1";
            }
        }
    }
}

    And below is the syslog configuration:

    syslog {
    file change-log {
        change-log any;
        archive size 10m files 5;
    }
    file daemon-log {
        daemon info;
        archive size 10m files 5;
    }
}

    Event-options to delete the static route works perfectly when an ISP goes DOWN. But policies "enable-isp1" & "enable-isp2" don't always work as desired, after an ISP returns to UP state. I want either of the enable-isp policies to trigger the event after seeing 12 PING_TEST_COMPLETED log messages after a failure has occurred.

    Is there anything wrong with my configuration? Any help in this regard would be highly appreciated.

    Thanks,



    ------------------------------
    Abdul Tayyeb Ratlamwala
    ------------------------------


  • 2.  RE: Event-options Not Working as Desired on SRX340

    Posted 04-09-2024 20:22

    Rather than event options I think you are looking for the Real-time Performance Monitoring / RPM feature.  This sets up probes and failover processes between interface options.

    An example configuration is outlined here.

    https://supportportal.juniper.net/s/article/SRX-Example-Configuring-IP-monitoring-using-RPM-Probes-for-failover-between-multiple-ISPs?language=en_US

    And the fuller documentation is here.

    https://www.juniper.net/documentation/us/en/software/junos/flow-monitoring/network-mgmt/topics/topic-map/real-time-performance-monitoring.html



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

    Original Message


  • 3.  RE: Event-options Not Working as Desired on SRX340

    Posted 5 days ago

    Hi @spulika,

    I'm facing issues with event-options also, but in an SRX1500 in chassi cluster.

    The 1st thing I tried was with RPM and IP-Monitoring, but that worked fine only for adding remove routes, not changing configurations like I need because I want to change BGP LP in a policy instead.

    So I'm trying full with event-options, but nothing happens also.
    I've traceoptions active for event-options, and the file is not even created.
    Are you aware of any limitations with event-options in Chassi cluster mode?

    I tried the same configuration in other set of SRX1500 but in MNHA mode, and there it works.

    Thanks.



    ------------------------------
    JOAO ALVES
    ------------------------------

    Original Message


  • 4.  RE: Event-options Not Working as Desired on SRX340

    Posted 5 days ago

    I'm kinda just listening in here, but I got kind of a similar situation. In my case it is redundancy that does not process the events properly. That is my belief. I believe it is a layer 2 thing and perhaps loopback related. At times my service-events process, no doubt due to topology changes, but other times the they don't, or the routes are misguided. This is further back in my network, so it's not exactly the srx I'm talking about. But 1 metric back is a cluster of switches(also not srx).

    I normally have a layer 2/loopback problem however, in my locale. It's purposely done thus way due to our power scheme. But it may appear that it's more recognized in a network. By this I mean that this area of traffic always seems segmented. In my area it fails purposely. Seemingly looking normal in failure. Perhaps further back in your network a windows DC with event forwarding will push it. I tried this to no avail. It forwarded on the PC, but events on a router are still not firing right. One thing as well though.... the service-event may not operate the way I'm thinking.  I'll post the windows server event forwarding links if I can. In just a few.



    ------------------------------
    Adrian Aguinaga
    B.S.C.M. I.T.T. Tech
    (Construction Management)
    A.A.S. I.T.T. Tech
    (Drafting & Design)
    ------------------------------

    Original Message


  • 5.  RE: Event-options Not Working as Desired on SRX340

    Posted 5 days ago

    Here is the link.

    https://learn.microsoft.com/en-us/defender-for-identity/deploy/configure-event-forwarding

    Here is my topology.

    Arris (xfinity gateway) -> srx300 ->

    Asus AP(5300) ->

    Asus media bridge(rt-ac68u) ->

    Avaya switch cluster

    The media bridge automatically creates

    interfaces for redundancy of its link connections for the avaya cluster and any pcs I connect to it. That's where I used event forwarding on a win server.

    So the service-event is at the media bridge.

    Thanks for your info on the event options on the srx cluster.



    ------------------------------
    Adrian Aguinaga
    B.S.C.M. I.T.T. Tech
    (Construction Management)
    A.A.S. I.T.T. Tech
    (Drafting & Design)
    ------------------------------

    Original Message