04-13-2007 08:00 AM
I want to monitor the amount of collisions and errors I receive on interfaces but I can't find the correct OID can someone help me with this please
GigabitEthernet4/8 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet Port, address is 000d.657d.3387 (bia 000d.657d.3387)
Description: --- 2924_MAIN ---
MTU 1500 bytes, BW 100000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, link type is auto, media type is 10/100/1000-TX
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:47, output never, output hang never
Last clearing of "show interface" counters 20w1d
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 5000 bits/sec, 4 packets/sec
5 minute output rate 153000 bits/sec, 26 packets/sec
143271178 packets input, 34567505950 bytes, 0 no buffer
Received 2731549 broadcasts (295416 multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
253476590 packets output, 117220536494 bytes, 0 underruns
1341644 output errors, 542074 collisions, 0 interface resets
0 babbles, 259071 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
04-13-2007 08:09 AM
What device is this, and what version of IOS is it running?
04-17-2007 04:53 AM
does it really matter ? Are the OID's not a standard.
It's a cisco 4506 with IOS 12.2(20)
04-17-2007 05:06 AM
When it comes to MIB support, it does matter. Different devices and different software versions support different MIBs. For this switch, you can use the ETHERLIKE-MIB to get this information. For collisions, look at dot3StatsSingleCollisionFrames, dot3StatsMultipleCollisionFrames, dot3StatsLateCollisions, and dot3StatsExcessiveCollisions. For errors, you have ifInErrors and ifOutErrors from the IF-MIB as well as ethernet-specific errors such as dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsSQETestErrors, dot3StatsInternalMacTransmitErrors, dot3StatsCarrierSenseErrors, dot3StatsInternalMacReceiveErrors, and dot3StatsSymbolErrors.
The total error count you see in the show interface output will be summed up in ifInErrors and ifOutErrors, but you can drill into the ethernet-specific counters to get a better idea of what is going on.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide