Help Center/ Huawei Qiankun CloudService/ More Documents/ Device Alarm Handling/ V600 Device Alarms/ AR Alarms/ ALM-15795185 hwConnectionDownReport
Updated on 2024-01-25 GMT+08:00
View PDF
Share

ALM-15795185 hwConnectionDownReport

Description

The connection has entered the down state. (ConnectionID=[ConnectionID], DestSiteID=[DestSiteID], SrcSiteID=[SrcSiteID], DestTNPID=[DestTNPID], SrcTNPID=[SrcTNPID],DownReason=[DownReason])

The EVPN connection went Down.

Attribute

Alarm ID

OID

Alarm Severity

Alarm Type

15795185

1.3.6.1.4.1.2011.5.25.241.6.3.2

Major

Quality of service alarm

Parameters

Name Meaning

ConnectionID

Connection ID.

DestSiteID

Name of the destination site.

SrcSiteID

Name of the source site.

DestTNPID

Destination TNP.

SrcTNPID

Source TNP.

DownReasonID

Cause ID.

Impact on the System

Service may be interrupted.

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

  1. Check whether the service route to the corresponding site is deleted.
    1. Run the display tunnel all command to view information about all tunnels.
    2. Run the display tunnel tunnel-id command to view information about a specified SD-WAN tunnel and check whether the corresponding service route exists.
    • If the route does not exist, configure a route to the corresponding site.
    • If the route exists, collect alarm and configuration information, and contact technical support personnel.
  2. Check whether the DH group of the local device matches that of the peer device.

    Run the display ipsec p2mp-policy command to check the DH groups used by the key exchange algorithm in the IPSec P2MP security policies of the local and peer devices. If the DH groups of the two devices are different and one device uses the strict mode, the DH groups cannot match. Configure the same DH group or disable the strict mode.

  3. 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.
  4. Run the display evpn site-tnp site-id command to check whether the TNP of the peer device is deleted.
    • If so, configure TNP information.
    • If not, collect alarm and configuration information, and contact technical support personnel
  5. Check whether the TNP of the local device is bound to an interface.
    1. Run the display evpn site-tnp site-id verbose command to check whether the TNP of the local device is bound to an interface.
      • If so, 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.
  6. Run the display evpn site-tnp site-id verbose command to check whether the TNP's weight is changed.
  7. Check the interfaces bound to the TNP.
    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.
  8. 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 Current Alarms page.

Parent topic: AR Alarms