Table 9-9 Ethernet Threshold Variables (Mibs) - Cisco ONS 15327 User Documentation

Remote Monitoring Specification Alarm Thresholds
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.
You can find performance monitoring specifications for all other cards in
Note
Monitoring."
Table 9-9
Note
choose etherStatsCollisions from the Variable menu.
Table 9-9
Variable
iflnOctets
iflnUcastPkts
iflnErrors
ifOutOctets
ifOutUcastPkts
dot3statsAlignmentErrors
dot3StatsFCSErrors
dot3StatsSingleCollisionFrames
dot3StatsMutlipleCollisionFrame
dot3StatsDeferredTransmissions
dot3StatsLateCollision
dot3StatsExcessiveCollision
etherStatsJabbers
etherStatsUndersizePkts
etherStatsFragments
etherStatsPkts64Octets
Cisco ONS 15327 User Documentation, R3.3
9-32
defines the variables you can provision in CTC. For example, to set the collision threshold,
Ethernet Threshold Variables (MIBs)
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 FCS
test
Number of frames with framecheck errors, i.e., there is an
integral number of octets, but an incorrect FCS
Number of successfully transmitted frames that had exactly one
collision
Number of successfully transmitted frames that had multiple
collisions
Number of times that 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
Number of packets received with a length less than 64 octets
Total number of packets that are not an integral number of octets
or have a bad FCS, and that are less than 64 octets long
Total number of packets received (including error packets) that
were 64 octets in length
Chapter 9 Ethernet Operation
Chapter 8, "Performance
June 2002