Cisco Systems 15454M6DC Benutzerhandbuch

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