Chapter 2 Alarm Message
Remote respond loopback stop fails.
Examples:
00:16:14 01/01/2001 UTC alarm 16128 occurred %ETHOAM% In-
terface loopback respond start command failed on fei_1/1 sent by
NPC 1
00:16:14 01/01/2001 UTC alarm 16128 occurred %ETHOAM% In-
terface loopback respond stop command failed on fei_1/1 sent by
NPC 1
Alarm Description
The local end starts loopback and the remote end fails to respond.
Supported Devices
All series (This alarm can be available from V4.8.22.)
16129
Message No.
16129
Default Security
Level
5
Alarm Type
"CommunicationAlarm"
NM Level
5
Cause
Lost the message that keeps protocol success status within timer
time.
Influence
Cause local Ethernet oam protocol status initialization.
Recommended
Operations
Check if link and packet sending/receiving in receive direction are
normal and re-initiate protocol negotiation.
Alarm Description
Prototype
Interface %s localmac %s peermac %s
The first %slost link in receive direction.
The second %s and the third %ssource MAC address and destina-
tion MAC address.
Examples:
00:16:14 01/01/2001 UTC alarm 16129 occurred %ETHOAM% In-
terface lost ink in receive direction localmac 00d0.d0c6.5e27 peer-
mac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 11
Alarm Description
Packets fail to be received on receive direction of link.
Supported Devices
All series (This alarm can be available from V4.8.22.)
16130
Message No.
16130
Default Security
Level
5
Alarm Type
"ProcessingErrorAlarm"
NM Level
5
Cause
The local or remote configuration modification causes that the local
or remote can’t satisfy the modified configuration.
Influence
Cause Ethernet oam protocol status to change.
Confidential and Proprietary Information of ZTE CORPORATION
31