There is no true way to account for bandwidth utilization on the routers. You can load MRTG to monitor the load that is going across your circuits but the best way to determine this is with a product put out by Jaalam <sp> Technologies called Apparenet. This will give you a truely accurate picture of usage. For more info on MRTG se the following link:
I've been monitoring response time, but I need to show throughput. I have a monitoring utility called qcheck, but my provider wants thorughput stats on the router.
You can look at the stats of the outside interface. If you had a serial interface then you would look at serial0/0 or whatever the interface is. For example, I've got ADSL with an ATM WIC, so I bring up the stats for int virtual-access 1 ..
collossus#sh int dialer0
Dialer0 is up, line protocol is up (spoofing)
Hardware is Unknown
Internet address is 213.249.x.y/32
MTU 1500 bytes, BW 1024 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
DTR is pulsed for 1 seconds on reset
Interface is bound to Vi1
Last input never, output never, output hang never
Last clearing of "show interface" counters 2w4d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 768 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
670399 packets input, 544344358 bytes
542823 packets output, 56191704 bytes
Bound to:
Virtual-Access1 is up, line protocol is up
Hardware is Virtual Access interface
MTU 1500 bytes, BW 1024 Kbit, DLY 100000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
DTR is pulsed for 5 seconds on reset
Interface is bound to Di0 (Encapsulation PPP)
LCP Open
Listen: CDPCP
Open: IPCP
Bound to ATM0 VCD: 1, VPI: 1, VCI: 50
Cloned from Dialer0
Last input 00:00:42, output never, output hang never
Last clearing of "show interface" counters 2w4d
Input queue: 1/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max) 5 minute input rate 605000 bits/sec, 57 packets/sec
5 minute output rate 13000 bits/sec, 39 packets/sec
737217 packets input, 547003438 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
596800 packets output, 57143319 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
collossus#
The bit that you need to look at is the 5 min input/output rates. These show that actual bandwidth utilisation of the router. In this case, I have a 1MB line but while I was downloading some film trailors I managed to get 605K/sec through my router.
If you start doing a large download or file transfer, keep looking at your interface stats and you'll see these figures creep up.
Chris.
************************
Chris Andrew, CCNA
chrisac@gmx.co.uk
************************
If you can test intrusively, I like TTCP (test tcp). You can execute it from your router if you have the right IOS but Cisco recommends that you test *through* the router instead of from the router. This is due to the way that Cisco routers prioritize between traffic that is generated by the router and traffic that is being routed by the router.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.