Need technical ""help"" explaining router out put 1

[loveroots]

Hi I am using GRE Tunnel in my network could someone explain please and also what comand could I us from my router to see which user lan ip is consuming all of the network bandwidth doing streaming vedio or downloading.ALSO EXPLAIN BW 9 KBIT DLY 500000 USEC. DO I NEED ALWASYS LOOK AT THE INPUT ERRORS AND CRC PLEASE HELP

Tunnel1 is up, line protocol is up
Hardware is Tunnel
Description: GRE Tunnel to LAXHPL - Los Angeles, CA
Internet address is X.X.X.X/30
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source X.X.X.18 (Serial0/0), destination X.X.X.178
Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
Checksumming of packets disabled, fast tunneling enabled
Last input 00:00:06, output 00:00:02, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 5
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
4171747 packets input, 433840978 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
2783509 packets output, 293098034 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Tunnel2 is up, line protocol is down
Hardware is Tunnel
Internet address is X.X.X.X/30
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source X.X.X.X (Serial0/0), destination 0.0.0.0
Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
Checksumming of packets disabled, fast tunneling enabled
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 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
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Tunnel5 is up, line protocol is up
Hardware is Tunnel
Internet address is X.X.X.X/30
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 12.124.54.218 (Serial0/0), destination X.X.X.X
Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
Checksumming of packets disabled, fast tunneling enabled
Last input 32w0d, output 00:00:05, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 3
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
148 packets input, 16382 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

 

[KiscoKid]

The output you mention (BW and DLY) are default parameters whenever you create a tunnel. BW refers to how much link capacity is available to the tunnel and DLY refers to the delay to place a datagram on the wire. Both of these parameters can be adjusted in interface configuration mode by specifying the 'bandwidth x' and 'delay y' options.

A quick and dirty way to perhaps trying to discover who is consuming all your bandwidth, is to enter interface configuration mode for your tunnel and enter the command 'ip accounting output'.

You can then review the stats captured using the 'show ip accounting' command in enable (#) prompt. This will break down all source and destination IP addresses and the bulk of traffic for each data flow.