Cisco MWR 2941 Command Reference Manual page 636

snmp-server enable traps ethernet cfm cc
•
•
•
The mep-up trap (cEtherCfmCcMepUp) serves three functions. One function is to notify the network
management system (NMS) that a new MEP has been discovered and learned by the device. The second
function is that the trap notifies the NMS that there is a change in the port-state of a previously
discovered remote MEP. The third is to notify the NMS when connectivity from a previously discovered
MEP is restored after interruption.
Mep-up traps are suppressed while cross-check is operational because the cross-check traps more
efficiently convey the status of the service.
The mep-up trap is generated in the following cases:
•
•
•
The mep-up trap includes the following fields:
•
•
•
•
•
•
•
•
Examples The following example shows how to enable SNMP trap generation for Ethernet CFM continuity checks
when a new remote MEP is discovered and learned by the device:
Router(config)# snmp-server enable traps ethernet cfm cc mep-up
Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR
618
MPID of the remote MEP that is being reported down.
MAC address of the remote MEP that is being reported down.
Event code indicating one of the following: lastGasp, timeout, configClear, loopClear,
xconnectClear, unknownClear.
A valid CCM with a non-zero hold-time is received from a remote MEP for the first time, and hence
an entry is created for that MEP in the continuity check database (CCDB). This trigger has the event
code "new."
A valid CCM with a non-zero hold-time is received from a remote MEP for which the device has an
expired entry in the CCDB (that is, the device has an entry for that remote MEP in the archived DB).
This trigger has the event code "returning."
A valid CCM with a non-zero hold-time is received from a remote MEP for which the device has a
valid entry in the CCDB and the port-state indicated in the CCM is different from what is cached in
the CCDB. This trigger has the event code "portState"
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.
MPID of the remote MEP that is being reported up.
MAC address of the remote MEP that is being reported up.
Event code indicating one of the following: new MEP, returning MEP, or port-state change.
Port state of remote MEP.
Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR
OL-23890-01