SNMP Traps Table
No. Trap Name
106 healthMonIpcTrap
healthMonIpcPoolStatus—The IPC Pools usage status.
107 bcmHashCollisionTrap
bcmHashCollisionTrap—The ?
108 healthMonCpuShutPortTrap
healthModuleSlot—The slot on which anomaly is detected.
ifIndex—The port on which anomaly is detected.
healthModuleCpuLatest—The average module-level CPU utilization over the latest sample period (percent).
109 arpMaxLimitReached
110 ndpMaxLimitReached
111 ripRouteMaxLimitReached
112 ripngRouteMaxLimitReached
113
-
Reserved
118
page B-20
Objects
Family
health-
health
MonIpcPool-
Status
?
eth
healthModule-
health
Slot
ifIndex
healthMod-
uleCpuLatest
none
ip
none
ipv6
none
rip
none
ripng
OmniSwitch 6250/6450 Switch Management Guide
SNMP Trap Information
Description
This trap is sent when IPC Pools
exceed usage.
This trap is sent when ?
This trap is sent when port is shut
down because of a CPU spike.
This trap is sent when the hard-
ware table has reached the
maximum number of entries sup-
ported. The OS6400 will not
generate new ARP request for
new nexthops.
This trap is sent when the hard-
ware table has reached the
maximum number of entries sup-
ported. The OS6400 will not
generate new ARP request for
new nexthops.
This trap is sent when the RIP
database reaches the supported
maximum number of entries.
When the maximum number is
reached, RIP discards any new
updates.
This trap is sent when the RIPng
database reaches the supported
maximum number of entries.
When the maximum number is
reached, RIPng discards any new
updates.
May 2012