Table of Contents
Advertisement
Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR
•
The MAC address of the device reporting the event. This is typically the Bridge Brain MAC address.
•
MPID of local MEP that has the same ID as that received in the CCM.
•
Name of the interface on which the MEP above is configured.
MAC Address of the remote device sending the CCM.
•
The cross-connect service trap (cEtherCfmCcCrossconnect) is generated when a device receives a
continuity check message (CCM) whose service ID is different from what is locally configured on the
device for the given service VLAN (S-VLAN). This mismatch indicates that there could be a
cross-connected service in the network. The trap includes the following fields:
Service ID designating the customer service instance to which the event belongs, as configured on
•
the device reporting the event.
•
The MAC address of the device reporting the event. This is typically the Bridge Brain MAC address.
•
MPID of remote MEP causing the alarm to be raised.
MAC address of remote MEP causing the alarm to be raised.
•
Service ID reported by the remote MEP.
•
The loop trap (cEtherCfmCcLoop) is generated when a device receives a CCM that has the same source
MAC Address and MPID as its own, thereby indicating that the device is receiving its own CCMs and
that a forwarding loop exists in the network. The loop trap includes the following fields:
•
Service ID designating the customer service instance to which the event belongs, as configured on
the device reporting the event.
The MAC address of the device reporting the event. This is typically the Bridge Brain MAC address.
•
MPID of the MEP originating the CCM.
•
•
Name of the interface on which the MEP above is configured.
The mep-down trap (cEtherCfmCcMepDown) notifies the NMS that the device has lost connectivity
with a remote MEP. This trap also serves as a clear for Loop, Config, Cross-Connect and Unknown-MEP
events.
The mep-down trap is generated in the following cases:
A valid CCM with a zero hold-time is received from a remote MEP, and the device either has a valid
•
(non-expired) CCDB entry for that MEP or does not have any CCDB entry. In other words, the trap
is not generated for an already expired CCDB entry. This trigger has the event code "lastGasp."
•
An entry for a remote MEP in the CCDB expires and is archived. This trigger has the event code
"timeout."
A previous configuration error trap is cleared. This trigger has the event code "configClear."
•
•
A previous loop trap is cleared. This trigger has the event code "loopClear."
•
A previous Crossconnect trap is cleared. This trigger has the event code "xconnectClear."
•
A previous unknown trap is cleared. This trigger has the event code "unknownClear."
The mep-down trap includes the following fields:
Service ID designating the customer service instance to which the event belongs, as configured on
•
the device reporting the event.
•
The MAC address of the device reporting the event. This is typically the Bridge Brain MAC address.
•
A count of the local MEPs on the same domain and S-VLAN as the remote MEP that are affected
by the event.
•
A count of the different interfaces on which the local MEPs above are configured.
OL-23890-01
Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR
snmp-server enable traps ethernet cfm cc
617
Advertisement
Table of Contents
