Updated on 2024-01-25 GMT+08:00

ALM-15795368 hwSiteDisconnect

Description

All connections between sites have entered down state. (SrcSite=[SrcSite],DestSite=[DestSite],CurrentConnectionNumber=[CurrentConnectionNumber])

All links between sites are unavailable.

Attribute

Alarm ID

OID

Alarm Severity

Alarm Type

15795368

1.3.6.1.4.1.2011.5.25.241.6.3.7

Major

Quality of service alarm

Parameters

Name Meaning

SrcSite

Name of the source site.

DestSite

Name of the destination site.

CurrentConnectionNumber

Number of current connections of a site.

Impact on the System

  • Cause 1: The site tunnel route is deleted.

    Services are interrupted.

  • Cause 2: The DH group does not match.

    Service may be interrupted.

  • Cause 3: The DH group is changed.

    Services may flap.

  • Cause 4: The TNP is deleted.

    Service may be interrupted.

  • Cause 5: The TNP status changes to down.

    Service may be interrupted.

  • Cause 6: The TNP weight is changed.

    Services may flap.

  • Cause 7: KA detection fails.

    Service may be interrupted.

  • Cause 8: Reset by user.

    Services may flap.

Possible Causes

  • Cause 1: The site tunnel route is deleted.
  • Cause 2: The DH group does not match.
  • Cause 3: The DH group is changed.
  • Cause 4: The TNP is deleted.
  • Cause 5: The TNP status changes to down.
  • Cause 6: The TNP weight is changed.
  • Cause 7: KA detection fails.
  • Cause 8: Reset by user.

Procedure

  • Cause 1: The site tunnel route is deleted.

    Check whether the service route to the corresponding site is deleted.

    1. Run the display tunnel all command to check information about all tunnels.
    2. Run the display tunnel tunnel-id command to check SD-WAN tunnel information one by one and check whether corresponding service routes exist.
      • If no, configure the corresponding site route.
      • If yes, collect alarm and configuration information and contact technical support personnel.
  • Cause 2: The DH group does not match.

    Check whether the DH group configured on the local device matches that configured on the peer device.

    Run the display ipsec p2mp-policy command to check the Key-Exchange information on both ends of the IPSec tunnel.

    If the DH groups of the two communication parties are different and one party uses the strict mode, the DH groups of the two communication parties do not match.

    Configure the same DH group or disable the strict mode.

  • Cause 3: The DH group is changed.

    Run the display ipsec p2mp-policy command to check the DH group used by the key exchange algorithm in the IPSec P2MP security policy of the peer device.Check whether the DH group is changed.

  • Cause 4: The TNP is deleted.
    1. Run the display evpn site-tnp site-id command to check whether the TNP of the peer device is deleted.
      • If yes, configure TNP information.
      • If no, collect alarm and configuration information and contact technical support personnel.
  • Cause 5: The TNP status changes to down.
    1. Run the display evpn site-tnp site-id verbose command to check whether the TNP on the local device is bound to an interface.
      • Yes: Go to Step 3.
      • If not, go to step 2.
    2. Configure the source interface of the TNP.
    3. Check whether the protocol status of the physical interface bound to the TNP is Up.
    4. Check whether the shutdown command is run on the interface.
  • Cause 6: The TNP weight is changed.
    1. Run the display evpn site-tnp site-id verbose command to check whether the TNP's weight is changed.
  • Cause 7: KA detection fails.
    1. Check whether the interfaces bound to the TNP can ping each other.
      • If so, go to step 3.
      • If not, go to step 2.
    2. Check whether the intermediate transport network is faulty.
    3. Collect alarm and configuration information, and contact technical support personnel.
  • Cause 8: Reset by user.

    Check whether BGP or EVPN connections are reset on the local device.

Clearing

After the fault is rectified, the system clears this alarm, removing the need to manually clear it. This alarm will not be displayed on the CurrentAlarms page.