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

OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02

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).
NEBD_XC_DIF

NEBD_XC_DIF

Description

The NEBD_XC_DIF alarm indicates that the cross-connect matrix data of the NE and board is different. For the board supporting service cross-connection, the alarm occurs when the cross-connection data stored on the SCC is not consistent with that stored on the board.

Attribute

Alarm Severity Alarm Type
Critical

Processing alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

Parameter Description

Parameter 1 and Parameters 2

Indicates the slot ID.

Parameters 3

Indicates the cross-connect type. For example:

0x3 indicates inconsistent space division cross-connections.

Impact on the System

Services are interrupted during service grooming or perform warm reset on the board.

Possible Causes

  • Cause 1: The cross-connection data of the board is incorrect.

  • Cause 2: The cross-connection data stored on the board is different from that on the SCC board.

Procedure

  • Query the alarm on the NMS. Record the slot ID of the board that reports the alarm.
  • Cause 1: The cross-connection data of the board is incorrect.
    1. Re-configure the cross-connection data on the NMS.
  • Cause 2: The cross-connection data stored on the board is different from that on the SCC board.
    1. If the alarm persists, perform a warm reset on the board related to service cross-connections on the NMS.
    2. If the alarm persists, perform warm reset on the SCC on the NMS.

Related Information

None

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 75146

Downloads: 138

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