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

S9300, S9300E, and S9300X V200R010C00

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).
OAM_1.3.6.1.4.1.2011.5.12.7.1.2.2 hwMplsOamIgrLSPInDefect

OAM_1.3.6.1.4.1.2011.5.12.7.1.2.2 hwMplsOamIgrLSPInDefect

Description

OAM/3/OAM_LSP_IGRINDEFECT:OID [oid] Ingress enter defect. (IfIndex=[tunnel-index], TunnelName=[tunnel-name], AvailableState=[ingress-available-state], DefectType=[ingress-defect-type])

The LSP checked by the OAM module on the source point was faulty.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.12.7.1.2.2 Minor processingErrorAlarm (4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Index of a tunnel

TunnelName

Name of a tunnel

AvailableState

Indicates the availability state of an ingress:
  • 0: The ingress is available.
  • 1: The ingress is unavailable.

DefectType

Indicates the type of the defect:
  • 0: No defect.
  • 1: The server layer defect arising below the MPLS network layer.
  • 2:The peer maintenance entity defect arising outside the MPLS sub-network.
  • 3: The defect of the packet loss for the connectivity detection. This defect occurs if no FDI packet is received from the server layer or lower level LSP, and no CV or FFD packet with expected TTSI is received.
    • For the LSP that is detected by the CV packet, the egress LSR does not receive the expected CV packet in 3 consecutive seconds.
    • For the LSP that is detected by the FFD packet, the egress LSR does not receive the expected FFD packet in any period of three consecutive intervals for sending the FFD packet.
    NOTE:
    If there is an incoming FDI packet from the server layer, the defect type is set to dServer; if there is an incoming FDI packet from the lower level LSP within the MPLS network, the defect type is set to dPeerMe. In both cases, no more defects occur on this LSP.
  • 4: The defect of mismatching TTSI. This defect occurs when unexpected and no expected TTSI is carried in the incoming CV or FFD packets.
    • For the LSP that is detected by the CV packet, the egress LSR receives the CV or FFD packet with unexpected TTSI in 3 seconds and does not receive the CV packet with the expected TTSI.
    • For the LSP that is detected by the FFD packet, the egress LSR receives the CV or FFD packet with unexpected TTSI in any period of three consecutive intervals and does not receive the FFD packet with expected TTSI.
  • 5: TTSI mismerge defect.
    • For the LSP that is detected by the CV packet, the egress LSR receives the CV or FFD packet with the unexpected TTSI and the CV packet with the expected TTSI in of 3 seconds.
    • For the LSP that is detected by the FFD packet, the egress LSR receives the CV or FFD packet with unexpected TTSI and the FFD packet with the expected FFD packet in any period of three consecutive intervals.
  • 6: Receiving excess rate of CV or FFD OAM packets.
    • For the LSP that is detected by the CV packet, the egress LSR receives five or more than five CV packets with expected TTSI in 3 seconds.
    • For the LSP that is detected by the FFD packet, the egress LSR receives five or more than five FFD packets with expected TTSI in the period of three consecutive intervals.
  • 7: An unknown defect that is detected in the MPLS layer and affects the user plane traffic. This defect is not detected by MPLS OAM; it is reported to MPLS OAM.
  • 9: OAM Ingress Down.

Impact on the System

The OAM module will notify the message to the protection group and the traffic will be switched.

Possible Causes

Cause 1:

OAM detected that the link was faulty.

Cause 2:

An OAM configuration error occurred. As a result, the intervals for transmitting packets on the ingress and egress were different.

Procedure

  1. Run the display interface tunnel command to check the status of the link.

    • If the link is Up, go to Step 2.
    • If the link is Down, go to Step 3.

  2. Run the display mpls oam ingress all command on the OAM source to view MPLS OAM parameters for LSPs and status information. If an LSP or tunnel fails, run the display this command to check MPLS OAM configurations.

    • If the configuration is correct, go to Step 4.
    • If the configuration is incorrect, go to Step 3.

  3. Run the display this command in the tunnel interface view to check whether the destination address, type, and tunnel ID of the TE tunnel are correctly configured, and whether the mpls te commit command is configured. If the configuration on the tunnel interface is incorrect, reconfigure the tunnel interface and run the mpls te commit command.

    • If the fault is rectified, go to Step 5.
    • If the fault is not rectified, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 189228

Downloads: 44

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