No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
NVO3_1.3.6.1.4.1.2011.5.25.335.2.1 hwNvo3VxlanTnlDown

NVO3_1.3.6.1.4.1.2011.5.25.335.2.1 hwNvo3VxlanTnlDown

Description

The status of the vxlan tunnel changed to down. (SourceIpAddress=[SrcIpAddr], DestinationIpAddress=[DstIpAddr], TunnelStatus=[TnlStatus])

The VXLAN tunnel went Down.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwNvo3VxlanTnlDown

Trap OID

1.3.6.1.4.1.2011.5.25.335.2.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance. 

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

SourceIpAddress

Source VTEP address of the VXLAN tunnel

DestinationIpAddress

Remote VTEP address of the VXLAN tunnel

TunnelStatus

VXLAN tunnel status

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.335.1.3.1.3

hwNvo3VxlanTnlStatus

hwNvo3VxlanTnlSrcAddress

hwNvo3VxlanDestAdress

Impact on the System

The system will not be affected, but services will be interrupted.

Possible Causes

Cause 1: Terminal users went offline.

Cause 2: The network topology changed, causing a Layer 3 communication failure.

Procedure

  • Cause 1: Terminal users went offline.
    1. Check whether the terminal users went offline normally.

      • If the terminal users went offline normally, this trap message is informational only, and no action is required.
      • If the terminal users went offline abnormally, go to Step 2.

    2. Check the abnormal logout cause and rectify the fault. Then check whether the trap persists. If the trap persists, go to Step 3.
    3. Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 2: The network topology changed, causing a Layer 3 communication failure.
    1. Check whether devices are reachable at Layer 3.

      • If the devices are reachable at Layer 3, go to Step 3.
      • If the devices are unreachable at Layer 3, go to Step 2.

    2. Check physical links. If any link fails, rectify the fault. Then check whether the trap persists. If the trap persists, go to Step 3.
    3. Collect alarm information and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 80544

Downloads: 21

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next