This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Report showing interface drops?

XG125, SFOS 18.0.5 MR-5-Build586

We have redundant ISPs at a site. Email notifications reveal that one of the ISPs drops frequently, though briefly. The email notifications are sent once per minute, so we don't really know the exact time or duration of the drops. And it's cumbersome to assemble a report in Excel from the emails to present to the ISP.

I looked for a report that would give me more granular information but didn't manage to find it. Is there a canned report that shows connection drops at each of the WAN interfaces? Is there a way to build a custom report for this? Looking for exact time and duration.

Thanks!



This thread was automatically locked due to age.
Parents Reply Children
  • FormerMember
    0 FormerMember in reply to Jeff Vandervoort

    Hi ,

    I'd suggest checking dgd.log events to get more information on the reported issue.

    ==> Filter out 'Gateway Down' event timestamp from log viewer/reports.

    Here is a sample snapshot: 

    Timestamp: 2021-09-05 10:58:32

    ==> Filter dgd.log file with below command.

    # cat /log/dgd.log | grep -i "Sep 05 10:58"

    ==> Here is a sample example to understand Ping Success/Fail event.

    Ping status: S/F | S: Success | F: Fail

    Ping : S
    =============================================

    DEBUG Sep 07 09:27:48 [11705]: Initiating Ping : <GATEWAY_IP>

    DEBUG Sep 07 09:27:48 [11705]: GW (ISP_GW,Port5) : Waiting for reply

    DEBUG Sep 07 09:27:48 [11705]: Success, Retrying(1) Ping : <GATEWAY_IP>
    DEBUG Sep 07 09:27:48 [11705]: GW (ISP_GW,Port5) : Waiting for reply
    DEBUG Sep 07 09:27:48 [11705]: Current Status : Live

    DEBUG Sep 07 09:27:48 [11705]: Ping Result for : <GATEWAY_IP>
    DEBUG Sep 07 09:27:48 [11705]: Ping : S
    DEBUG Sep 07 09:27:48 [11705]: Current Status [GW(ISP_GW,Port5)] : Live
    DEBUG Sep 07 09:27:48 [11705]: Sleep for 60 Seconds

    =============================================

    Ping : F
    =============================================

    DEBUG Aug 16 18:08:44 [12387]: Initiating Ping : <GATEWAY_IP>

    DEBUG Aug 16 18:08:44 [12387]: GW (ISP_GW,Port5) : Waiting for reply

    DEBUG Aug 16 18:08:46 [12387]: Failed, Retrying(1) Ping : <GATEWAY_IP>
    DEBUG Aug 16 18:08:46 [12387]: GW (ISP_GW,Port5) : Waiting for reply
    DEBUG Aug 16 18:08:46 [12387]: Current Status : Live

    DEBUG Aug 16 18:08:48 [12387]: Failed, Retrying(2) Ping : <GATEWAY_IP>
    DEBUG Aug 16 18:08:48 [12387]: GW (ISP_GW,Port5) : Waiting for reply
    DEBUG Aug 16 18:08:48 [12387]: Current Status : Live

    DEBUG Aug 16 18:08:50 [12387]: Failed, Retrying(3) Ping : <GATEWAY_IP>
    DEBUG Aug 16 18:08:50 [12387]: GW (ISP_GW,Port5) : Waiting for reply
    DEBUG Aug 16 18:08:50 [12387]: Current Status : Live

    DEBUG Aug 16 18:08:52 [12387]: Failed, Retrying(4) Ping : <GATEWAY_IP>
    DEBUG Aug 16 18:08:52 [12387]: GW (ISP_GW,Port5) : Waiting for reply
    DEBUG Aug 16 18:08:52 [12387]: Current Status : Live

    DEBUG Aug 16 18:08:54 [12387]: Failed, Retrying(5) Ping : <GATEWAY_IP>
    DEBUG Aug 16 18:08:54 [12387]: GW (ISP_GW,Port5) : Waiting for reply
    DEBUG Aug 16 18:08:54 [12387]: Current Status : Live

    DEBUG Aug 16 18:08:56 [12387]: Ping Result for : <GATEWAY_IP>
    DEBUG Aug 16 18:08:56 [12387]: Ping : F
    DEBUG Aug 16 18:08:56 [12387]: Current Status [GW(ISP_GW,Port5)] : Dead
    DEBUG Aug 16 18:08:56 [12387]: Sleep for 60 Seconds

    NOTICE Aug 16 18:08:56 [12387]: Actiontree, Live to Dead
    NOTICE Aug 16 18:08:56 [12387]: Actiontree, executing: Live_To_Dead @ISP_GW

    DEBUG Aug 16 18:08:56 [962]: Executing Service : <gateway:gw_live_to_dead> args : <{"param":"@ISP_GW"}>

    =============================================

    Note: <GATEWAY_IP> is the IP address kept in the failover rule condition of IPv4 gateway(Network > WAN link manager).