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>

Reminder

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

upgrade

A K2_M Alarm Occurs When the OptiX Metro 1000 V3 Network Is Connected to the Equipment of Company A Through 1+1 LMSP

Publication Date:  2012-07-25 Views:  48 Downloads:  0
Issue Description
In a representative office, the OptiX Metro1000 V3 network is connected to the transmission equipment of company A through 1+1 LMSP. A K2_M alarm is generated. The user, however, provides feedback that the switching is not affected but wants to know the causes of the alarm.
The LMSP of Huawei equipment is in 1+1 single-end recovery mode. The user of company A says that the same attribute configuration is used. 
 
Alarm Information
:alm-get-curdata:0,ALL;
CUR-ALM
NUM      BID   EID      SEVERITY    STATE    START-TIME        END-TIME   PARA1   PARA2   PARA3    PARA4   PARA5
142645   11   K2_M    MN                start    2007-6-28 12:3:53  None            0x04      0x01       0xff         0xff           0xff 
 
Handling Process
1. Do not monitor the K2_M alarm. This alarm does not affect services.
2. Ask the user to check the configuration again. It is confirmed that the 1:1 LMSP mode is configured for company A. Modify the LMSP mode. Then, the alarm is cleared. 
 
Root Cause
Analyze the event according to the returned K bytes.
...........
1 8091   K_RECEIVED   0x0008   2007-6-28 12:3:52   0x01fd7f3a
1 8092   K_DIR                0x0000   2007-6-28 12:3:52   0x01fd8008
.........
The K byte received in the standby path of the OptiX Metro 1000 V3 NE is 0x0008. This indicates that the peer LMSP mode is 1:N. On the OptiX Metro 1000 V3 equipment, the 1+1 LMSP mode is configured. Therefore, the K2_M alarm is reported.
For the linear MS, the BIT5 of the K2 byte is 1, indicating the 1:N mode. 
 
Suggestions
Null

END