cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10114
Views
0
Helpful
13
Replies

WAN router bandwidth usage

Stephen Sisson
Level 1
Level 1

Hello,

Need some help to figure out the bandwidth usage for the WAN router f2/0 interface, sending you what we have from this interface

30 second input rate 881000 bits/sec, 296 packets/sec

30 second output rate 395000 bits/sec, 292 packets/sec

1297322378 packets input, 1616261346 bytes

Received 59127 broadcasts, 0 runts, 0 giants, 0 throttles

Thank you

1 Accepted Solution

Accepted Solutions

If you want to validate the speed of the link transmit and receive at the time you take the sample, you should only check the following lines:

30 second input rate 2952000 bits / sec, 555 packets / sec

30 second output rate 479000 bits / sec, 470 packets / sec

Here you should not add or subtract anything. As I mentioned earlier in a FastEthernet link in full duplex mode, the transmission is independent (30 seconds output rate) incoming (30 seconds input rate).

These statistics are based on bits per second as this is handled in terms of transmission in data networks.

For the snapshot you send you:

30 second input rate 2952000 bits / sec, 555 packets / sec

30 second output rate 479000 bits / sec, 470 packets / sec

That is for you reception: 2952000 bits / sec,

so if you want to refer this value in kilobits divide by 1000 and you have:

2952000/1000 = 2952 kbps

if you want to refer this value in megabits divide between 1000000 and have:

2952000/1000000 = 2.952 Mbps

Importantly, as the point referring transmission rates in data networks (x Gbps Mbps x, x Kbps, x bps) that are expressed in terms of bits, as opposed to storage that is expressed in terms of Bytes (Gbytes, Mbytes, Kbytes, bytes). It is also important to note that the second character of the velocity:

xbps = second character is "b" in lower case that which be interpreted as bits. "x" or first character can be G, g, M,m,K,k, or not exist if the rate is expressed in bits.

There are statistical tools that add these two values:

Input Ouput rate + rate to generate a total, but personally I'm not decuerdo with this and usually do not use this type of graph. Prefer separate or overlapping graphs.

Important

There are statistical tools that add these two values:
Input Ouput rate + rate to generate a total, but personally I'm not decuerdo with this and usually do not use this type of graph. Prefer separate or overlapping graphs.

View solution in original post

13 Replies 13

David Salazar
Level 1
Level 1

The following document can review useful information, specifically reviewing Table 41:

http://www.cisco.com/en/US/docs/ios/12_2/interface/command/reference/irfshoin.html#wp1018148

Table 41 show interfaces fastethernet Field Descriptions—FEIP

Field

Description

Fast Ethernet0 is ... is up
...is administratively down

Indicates whether the interface hardware is currently active and if it has been taken down by an administrator.

line protocol is

Indicates whether the software processes that handle the line protocol consider the line usable or if it has been taken down by an administrator.

Hardware

Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.

Internet address

Internet address followed by subnet mask.

MTU

Maximum transmission unit of the interface.

BW

Bandwidth of the interface in kilobits per second.

DLY

Delay of the interface in microseconds.

rely

Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.

load

Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.

Encapsulation

Encapsulation method assigned to interface.

ARP type:

Type of Address Resolution Protocol assigned.

loopback

Indicates whether loopback is set or not.

keepalive

Indicates whether keepalives are set or not.

Last input

Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.

output

Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.

output hang

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.

Last clearing

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

*** indicates the elapsed time is too large to be displayed.

0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.

Output queue, input queue, drops

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.

5 minute input rate,
5 minute output rate

Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).

The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.

packets input

Total number of error-free packets received by the system.

bytes

Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

no buffer

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.

Received ... broadcasts

Total number of broadcast or multicast packets received by the interface.

runts

Number of packets that are discarded because they are smaller than the minimum packet size of the medium. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.

giants

Number of packets that are discarded because they exceed the maximum packet size of the medium. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.

input errors

Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.

CRC

Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.

frame

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.

overrun

Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.

ignored

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.

abort

Number of packets whose receipt was aborted.

watchdog

Number of times watchdog receive timer expired. It happens when receiving a packet with length greater than 2048.

multicast

Number of multicast packets received.

input packets with dribble condition detected

Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.

packets output

Total number of messages transmitted by the system.

bytes

Total number of bytes, including data and MAC encapsulation, transmitted by the system.

underruns

Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.

output errors

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.

collisions

Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.

interface resets

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.

restarts

Number of times a Type 2 Ethernet controller was restarted because of errors.

babbles

The transmit jabber timer expired.

late collision

Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.

deferred

Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.

lost carrier

Number of times the carrier was lost during transmission.

no carrier

Number of times the carrier was not present during the transmission.

output buffer failures

Number of failed buffers and number of buffers swapped out.

If you want to verify traffic flows that are going through that interface, you can configure NetFlow TopTalkers.

In the following link you can get valuable information:

http://www.cisco.com/en/US/docs/ios-xml/ios/netflow/configuration/12-4t/cfg-nflow-top-talk.html#GUID-824723EE-2551-4D64-9E0B-F5DF065C83B9

As a summary only need to configure the following commands:

ip flow-top-talkers (global configuration mode)

and in interface configuration mode:

!
FastEthernet0/1.884 interface
ip flow ingress and / or egress ip flow

After you verify with a "show ip flow top-talkers":

MBO-RT-03 # sh ip flow top-talkers

Pr DstIPaddress SrcIPaddress SrcIf DstIf SRCP DSTP Bytes
Fa0/1.884 Fa0/0.4 23.15.5.213 1xx.xxx.xx.123 0050 06 081F 1906K
Fa0/1.884 Fa0/0.4 23.15.5.206 1xx.xxx.xx.123 0050 0E85 06 1306K

100 of 100 Shown top talkers. 538 flows processed.

MBO-RT-03 #

If the information is helpful, please rate me.

Hello,

Thanks for the link and something we need to review in the future, can you help us figure out how much bandwidth we are using based on what I'm sending you, what we have left, we are having a speed issues on our external WAN router that requires fixing. we either need to add more bandwidth or a new circuit, not able to move forward until we know the speed on that interface, can you help with this.

Thank you

I'm sending you the show int f2/0 and from what is shown can you tell us are we using 1.3Mbps or 3.2 Mbps or something else.

astEthernet2/0 is up, line protocol is up

  Hardware is AmdFE, address is 000b.46c5.7431 (bia 000b.46c5.7431)

  Description: To Internal Office From UUNET

  Internet address is 208.251.158.1/24

  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 7/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/s, 100BaseTX/FX

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:10, output 00:00:00, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/203/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  30 second input rate 2751000 bits/sec, 519 packets/sec

  30 second output rate 458000 bits/sec, 445 packets/sec

     1311366632 packets input, 1596377767 bytes

     Received 59947 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog

     0 input packets with dribble condition detected

     1319276459 packets output, 3238626875 bytes, 0 underruns

     0 output errors, 0 collisions, 2 interface resets

     0 babbles, 0 late collision, 0 deferred

     1260 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

thank you

This interface is FastEthernet, operating in full duplex mode at speeds which has 2 fully independent

- One of Outbound. Refers to outbound traffic for the router interface to the remote end of the link. This statistic is: 30 second output rate 458000 bits / sec, 445 packets / sec, ie 458kbps.

- One of Incoming. Refers to traffic from the remote end of the link. This statistic is: 30 second input rate 2751000 bits / sec, 519 packets / sec, ie 2Mbps.

Importantly, this is relative to the time since sampling is recorded or calculated every 30 seconds.

David Salazar
Level 1
Level 1

As I understand, you have a WAN link, which you receive in a ethernet port but do not know the bandwidth that you are actually delivering?

And service degradation think you might be reaching the limit of the BW?

You can monitor the link via SNMP with a tool you have to do, if you have not I recommend SolarWinds Real-Time Bandwidth Monitor, the tool that you can download for free and trial. There you can get almost real upper limit of what the provider will deliver, of course this depends on other varibles. What kind of service do you have? Is internet? Synchronous or asynchronous? O is a point to point link?

You can also contact the service provider to let you know the characteristics of the service and so you can compare with the graphs you get via SNMP.

I'm sorry - hate to be rude, we do not have snmp setup as this is a security issue,

We need to figure out the math for what I'm sending to show much bandwidth we are currently using on that interface, same interface all traffic is going through - yes the MFR circuits at times is hitting the top of the threshold we have set with Verizon.

  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 4/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/s, 100BaseTX/FX

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:02, output 00:00:00, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/203/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  30 second input rate 1716000 bits/sec, 464 packets/sec

  30 second output rate 512000 bits/sec, 437 packets/sec

     1312073261 packets input, 1952867772 bytes

     Received 59972 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog

     0 input packets with dribble condition detected

     1319934024 packets output, 3358607387 bytes, 0 underruns

     0 output errors, 0 collisions, 2 interface resets

     0 babbles, 0 late collision, 0 deferred

     1260 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

thanks

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 4/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

According to what I understand, you have a bottleneck on the provider connection. Your contract is for X bandwidth with MFR (multilink frame relay?), No matter however much the technology used but the actual bandwidth of the link, as the receive connection with a FastEthernet link you have configured with default bandwidth parameter of 100 Mbps

For the above have an asynchronous link: link router (100 Mbps) --- Service Provider (Kbps X), where X is less than 100 Mbps when ecenarios have said you should consider two suggestions:

1) Set the Bandwidth parameter within the FastEthernet interface with the real value contracted in the link, so that the statistics will be more useful in a show interface, I mean counters: Txload and rxload.

2) You must configure Traffic Policing or Shaping Traffic to avoid congesting the link hired, as this will directly affect the performance of your application or service used through the link.

Additionally I suggest that you check the network cable plugged into that port because it reflects a high number of carrier loss.

It is important to note that the settings of Traffic Policing or Traffic Shaping is required, if you want to avoid congestion problems on the link.

paolo bevilacqua
Hall of Fame
Hall of Fame

You can use some software like PRTG to monitor your bandwith usage.

I'm sorry - must be typing something wrong, sent the information for Cisco 3640 router for interface f2/0 - trying to figure out total bandwidth usage - can someone tell me how to figure out what math to use for figuring this out, are adding something? What numbers, subtraction? What numbers, or any other, how do we figure out the total without other software

  30 second input rate 2952000 bits/sec, 555 packets/sec

  30 second output rate 479000 bits/sec, 470 packets/sec

     1312637298 packets input, 2245078841 bytes

     Received 59991 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog

     0 input packets with dribble condition detected

     1320457549 packets output, 3456948494 bytes, 0 underruns

thanks

If you want to validate the speed of the link transmit and receive at the time you take the sample, you should only check the following lines:

30 second input rate 2952000 bits / sec, 555 packets / sec

30 second output rate 479000 bits / sec, 470 packets / sec

Here you should not add or subtract anything. As I mentioned earlier in a FastEthernet link in full duplex mode, the transmission is independent (30 seconds output rate) incoming (30 seconds input rate).

These statistics are based on bits per second as this is handled in terms of transmission in data networks.

For the snapshot you send you:

30 second input rate 2952000 bits / sec, 555 packets / sec

30 second output rate 479000 bits / sec, 470 packets / sec

That is for you reception: 2952000 bits / sec,

so if you want to refer this value in kilobits divide by 1000 and you have:

2952000/1000 = 2952 kbps

if you want to refer this value in megabits divide between 1000000 and have:

2952000/1000000 = 2.952 Mbps

Importantly, as the point referring transmission rates in data networks (x Gbps Mbps x, x Kbps, x bps) that are expressed in terms of bits, as opposed to storage that is expressed in terms of Bytes (Gbytes, Mbytes, Kbytes, bytes). It is also important to note that the second character of the velocity:

xbps = second character is "b" in lower case that which be interpreted as bits. "x" or first character can be G, g, M,m,K,k, or not exist if the rate is expressed in bits.

There are statistical tools that add these two values:

Input Ouput rate + rate to generate a total, but personally I'm not decuerdo with this and usually do not use this type of graph. Prefer separate or overlapping graphs.

Important

There are statistical tools that add these two values:
Input Ouput rate + rate to generate a total, but personally I'm not decuerdo with this and usually do not use this type of graph. Prefer separate or overlapping graphs.

on these two lines:

1312637298 packets input, 2245078841 bytes

1320457549 packets output, 3456948494 bytes

Are variable with cumulative values​​, these variables are cleared or set to 0 to reach a limit. Here it should be noted that the values ​​are expressed in bytes that is amount of data transmitted and received data amount, since the last time the counters were cleared (this can be for a reboot or administratively counters were cleared) or reset limit value may reflect the specific counter.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: