Txload and Rxload problem

[sivaalthi85]

Hi Friends,

Could someboody can please explain what is that txload and rxload and how to solve the issue,

Usually they should be 1/255 but on my atm interface it is showing as below.

My Lan users are facing extreme slow internet access.

Network is dead slow.

Please help

ATM0 is up, line protocol is up

  Hardware is MPC ATMSAR, address is ccef.48b4.fef4 (bia ccef.48b4.fef4)

  MTU 1600 bytes, sub MTU 1600, BW 1236 Kbit/sec, DLY 290 usec,

    reliability 255/255, txload 6/255, rxload 80/255

  Encapsulation ATM, loopback not set

  Keepalive not supported

  Encapsulation(s): AAL5

  4 maximum active VCs, 1024 VCs per VP, 1 current VCCs

  VC Auto Creation Disabled.

  VC idle disconnect time: 300 seconds

  Last input never, output 00:00:00, 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: Per VC Queueing

  5 minute input rate 389000 bits/sec, 35 packets/sec

  5 minute output rate 33000 bits/sec, 10 packets/sec

    35310 packets input, 46261530 bytes, 0 no buffer

    Received 0 broadcasts (0 IP multicasts)

    0 runts, 0 giants, 0 throttles

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

    23085 packets output, 4104088 bytes, 0 underruns

    0 output errors, 0 collisions, 0 interface resets

    0 unknown protocol drops

    0 output buffer failures, 0 output buffers swapped out

[John Blakley]

Your best bet would be to enable netflow on the interface ingress and configure top talkers.

TXLoad is the amount of traffic being transmitted from your interface and the RXLoad is the amount of traffic received on the interface. Your rxload is 80/255 which is about 31% utilization of your total bandwidth inbound.

Top talkers will tell you what port and source/destination address is being used. If your router supports it you'll probably want to configure it so you can see what the traffic is fairly easy:

ip flow-top-talkers

sort bytes

top 10

Apply the following to your external interface:

ip flow ingress

Then to see top talkers, do:

sh ip flow top

HTH,

John

Please rate all useful posts...

[Joseph W. Doherty]

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

Txload and rxload are just another way to show your average utilization, i.e.:

txload 6/255 = 2.35%

rxload 80/255 = 31.37%

input rate 389 (K) / 1236 Kbps = 31.47%

output rate 33 (K) / 1236 Kbps = 2.66%

Both of these are based on a 5 minute average (the default).

As to why your network is "dead slow", not enough information to hazard a guess.

[Leo Laohoo]

You've got to give us more information than this.

I don't see any discrepancies to your "sh interface" output of the ATM.  You say your LAN is slow?  Show us the output of the LAN.

What kind of switches do you have?

Be more specific when you said that the LAN is "slow".

Can the PC's ping the server?  How about something in the same subnet (like a printer)?

Is the slowness happening during office hours?  How about during lunch time?  How about 5pm in a working afternoon?