TPOAM/4/hwMplsTpOamUnExpectPhb: unexpected phb alarm start. (MegId=[MegId], MegId=[Meg_Id], MeIndex=[MeIndex], MeType=[MeType], MeDirection=[MeDirection], IfName=[IfName], PeerIP=[PeerIP], VcId=[VcId], VcType=[VcType], RemoteIp=[RemoteIp], Ttl=[Ttl], MepId=[MepId], RemoteMepId=[RemoteMepId], LspName=[LspName], VsiName=[VsiName])
Parameter Name | Parameter Meaning |
---|---|
MegId |
Name of a MEG |
Meg_Id |
Name of a MEG |
MeIndex |
Index of an ME |
MeType |
ME type:
|
MeDirection |
Tunnel type for an ME:
|
IfName |
Interface name |
PeerIP |
Peer IP address |
VcId |
VC ID |
VcType |
VC type |
RemoteIp |
IP address of an RMEP |
Ttl |
TTL value |
MepId |
Local ME ID |
RemoteMepId |
RMEP ID |
LspName |
LSP name |
VsiName |
VSI name |
1. Run the display current-configuration command to check whether the CCM priorities on both ends are the same.
2. Run the cc exp command to reconfigure the CCM priorities on both ends, and check whether the alarm is cleared.
3. Collect log information and configuration information, and then contact technical support personnel.
4. End.