Table 9-10 Ethernet Threshold Variables (Mibs) - Cisco 15454-TCC - Network Processor Card Operation Manual

Chapter 9 Ethernet Operation
One of the ONS 15454's RMON MIBs is the Alarm group. The alarm group consists of the alarmTable.
An NMS uses the alarmTable to find the alarm-causing thresholds for network performance. The
thresholds apply to the current 15-minute interval and the current 24-hour interval. RMON monitors
several variables, such as Ethernet collisions, and triggers an event when the variable crosses a threshold
during that time interval. For example, if a threshold is set at 1000 collisions and 1001 collisions occur
during the 15-minute interval, an event triggers. CTC allows you to provision these thresholds for
Ethernet statistics.
Note You can find performance monitoring specifications for all other cards in the Cisco ONS 15454
Troubleshooting and Maintenance Guide.
Note The following tables define the variables you can provision in CTC. For example, to set the collision
threshold, choose etherStatsCollisions from the Variable menu.

Table 9-10 Ethernet Threshold Variables (MIBs)

Variable
iflnOctets
iflnUcastPkts
iflnErrors
ifOutOctets
ifOutUcastPkts
dot3statsAlignmentErrors
dot3StatsFCSErrors
dot3StatsSingleCollisionFrames
dot3StatsMutlipleCollisionFrame
dot3StatsDeferredTransmissions
dot3StatsLateCollision
dot3StatsExcessiveCollision
etherStatsJabbers
November 2001
Remote Monitoring Specification Alarm Thresholds
Definition
Total number of octets received on the interface, including
framing octets
Total number of unicast packets delivered to an appropriate
protocol
Number of inbound packets discarded because they contain
errors
Total number of transmitted octets, including framing packets
Total number of unicast packets requested to transmit to a single
address
Number of frames with an alignment error, i.e., the length is not
an integral number of octets and the frame cannot pass the Frame
Check Sequence (FCS) test
Number of frames with framecheck errors, i.e., there is an
integral number of octets, but an incorrect Frame Check
Sequence (FCS)
Number of successfully transmitted frames that had exactly one
collision
Number of successfully transmitted frames that had multiple
collisions
Number of times the first transmission was delayed because the
medium was busy
Number of times that a collision was detected later than 64 octets
into the transmission (also added into collision count)
Number of frames where transmissions failed because of
excessive collisions
Total number of Octets of data (including bad packets) received
on the network
Cisco ONS 15454 Installation and Operations Guide
9-31