Brocade Unified IP MIB Reference (Supporting FastIron Releases 07.5.00 and 08.0.10) - Manual (Page 725)

Unified IP MIB Reference 699
53-1003106-01
Proprietary traps
67
MCT notifications
The following traps are generated for the MCT objects supported only on the Brocade NetIron MLX,
Brocade MLXe, Brocade NetIron XMR, Brocade NetIron CES, and Brocade NetIron CER series
devices.
Use the [no] snmp-server enable traps command to enable or disable MCT notifications.
snTrapMacMoveThresholdR
ate
brcdIp.0.197 snAgGblTrapMessage Notifica
tion The SNMP notification is generated when MAC
movement is exceeding the certain threshold for
a sampling interval is detected.
Sample trap message:
Mac-Move threshold-rate: MAC
address moved from interface
to interface
for vlan ,
times exceeding the
threshold rate
for a sampling interval
seconds
snTrapMacMoveIntervalHist
ory
brcdIp.0.198 snAgGblTrapMessage Notifica
tion The SNMP notification is generated for every
user configured interval, summarizing the
moves in the interval.
Sample trap message:
Mac-Move Interval-History:
<#macs> macs moved in last
seconds. Total number
of mac moves in the interval is
<#moves>
Trap name and
number Varbinds Severity Description and trap message
brcdMctCluste
rPeerStatus
brcdIp.1.1.12.
1.0.1 brcdMctClusterPee
rOperStatus,
brcdMctClusterPee
rDownReason Notification Generates when the brcdMctClusterPeerOperStatus object
for peer entry in brcdMctClusterPeerTable changes the state
to ccpUp(2), ccpDown(3), or reachable(4) from any other
state.
brcdMctCluste
rClientStatus
brcdIp.1.1.12.
1.0.2 brcdMctClusterClie
ntOperStatus Notification Generates when the brcdMctClusterClientOperStatus object
for peer entry in brcdMctClusterClientTable changes the state
to remoteUp(4), localUp(5), up(6), slave(7), master(8), or
masterPeerUp(9) from any other state.
Sample syslog message:
BROCADE-MCT-CLUSTER-MIB:brcdMctClusterClie
ntOperStatus.10.99.108.105.101.110.116.49 :
(up) Syntax: INTEGER, Instance IDs: (10
client1)
NOTE: The change in the cluster peer state from ccpUp(2) to
ccpDown(3) or vice versa changes the state of all the
clients. This creates the brcdMctClusterClientStatus
notification storm. The brcdMctClusterClientStatus
notification will not be sent when the client state
change happens due to a cluster peer state change
from ccpUp(2) to ccpDown(3) or vice versa.
Trap name and number Varbinds Severity Description and trap message