a problem with the bandwidth utilization filter in the Topology View

Unanswered Question
Jan 26th, 2010
User Badges:

The customer has configured RMON using CM on all switches in the network. When I tried to use the bandwidth filter in the topology view for high utilization (76-100)% - the links with small utilization are filtered. Here is an example of one links which is marked as high utilized in the Topology View:


interface GigabitEthernet4/6
switchport trunk encapsulation dot1q
switchport mode trunk
rmon collection history 21 owner campusmanager buckets 10 interval 300


Entry 21 is active, and owned by campusmanager
Monitors ifEntry.1.21 every 300 second(s)
Requested # of time intervals, ie buckets, is 10,
  Sample # 2042 began measuring at 1d03h
   Received 1051636071 octets, 1562161 packets,
   27295 broadcast and 34512 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 140
  Sample # 2043 began measuring at 1d03h
   Received 1298880964 octets, 1803781 packets,
   26504 broadcast and 59229 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 63
  Sample # 2044 began measuring at 1d03h
   Received 1299131249 octets, 2044214 packets,
   26656 broadcast and 70204 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 64
  Sample # 2045 began measuring at 1d03h
   Received 1480519518 octets, 2117077 packets,
   26366 broadcast and 57120 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 112
  Sample # 2046 began measuring at 1d03h
   Received 1072373018 octets, 1598950 packets,
   30611 broadcast and 47075 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 3
  Sample # 2047 began measuring at 1d03h
   Received 1197494661 octets, 1747580 packets,
   27028 broadcast and 88612 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 36
  Sample # 2048 began measuring at 1d03h
   Received 999134336 octets, 1528403 packets,
   26258 broadcast and 45532 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 126
  Sample # 2049 began measuring at 1d04h
   Received 1277686463 octets, 1837673 packets,
   26667 broadcast and 73821 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 58
  Sample # 2050 began measuring at 1d04h
   Received 1109721861 octets, 1608105 packets,
   26822 broadcast and 44897 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 13
  Sample # 2051 began measuring at 1d04h
   Received 1047859853 octets, 1539916 packets,
   25927 broadcast and 62217 multicast packets,
   0 undersized and 0 oversized packets,
   0 fragments and 0 jabbers,
   0 CRC alignment errors and 0 collisions.
   # of dropped packet events is 0
   Network utilization is estimated at 139


So there is the maximum value 1,4% utilization no between 76 - 100% utilization.


See the interface statistics:

GigabitEthernet4/6 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet Port, address is 000b.5fbb.c47b (bia 000b.5fbb.c4
7b)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 2/255, rxload 3/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, link type is auto, media type is SX
  output flow-control is off, input flow-control is on
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 508819
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 15215000 bits/sec, 2511 packets/sec
  5 minute output rate 11209000 bits/sec, 2416 packets/sec
     44788091362 packets input, 51745134980839 bytes, 0 no buffer
     Received 359010927 broadcasts (64939786 multicast)
     0 runts, 0 giants, 0 throttles
     14790 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     42781664957 packets output, 45757459531444 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out


It seems that CM doesn't diveded RMON statistics by 100:-( The customer uses LMS3.2, CM 5.2.1 on Windows 2008 64bit Standard Server. It is without ACS integration. Thank you for your help.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion