Slow response while typing on the CLI

Mohit Chauhan · ‎09-04-2012

Hi friends,

I have a client for whom i set up a new network infrastructure. Everything is working but i have realised that when remote login to devices, I see slow response on the cli when i am typing.

it doesnt matter if i am remote logging in from outside or inside, but its the same result.

What could be the reason for that?

I did few checks to see there wasnt much load on the device, which included the following:

ROUTER-A#sh processes cpu extended

################################################################################

Global Statistics

-----------------

5 sec CPU util 2%/1% Timestamp 2w1d

Queue Statistics

----------------

Exec Count Total CPU Response Time Queue Length

(avg/max) (avg/max)

Critical 1 0 0/0 1/1

High 653 0 0/0 1/2

Normal 631 12 0/0 1/7

Low 10 32 0/0 1/2

Common Process Information

-------------------------------

PID Name Prio Style

-------------------------------

CPU Intensive processes

-------------------------------------------------------------------------------

PID Total Exec Quant Burst Burst size Schedcall Schedcall

CPUms Count avg/max Count avg/max(ms) Count Per avg/max

-------------------------------------------------------------------------------

Priority Suspends

------------------------------------

PID Exec Count Prio-Susps

------------------------------------

Latencies

-------------------------

PID Exec Count Latency

avg/max

-------------------------

################################################################################

ROUTER-A#sh int g0/1

GigabitEthernet0/1 is up, line protocol is up

Hardware is CN Gigabit Ethernet, address is 30f7.0d95.8521 (bia 30f7.0d95.8521)

Description: Internet

Internet address is X.X.X.X/30

MTU 1500 bytes, BW 10000 Kbit/sec, DLY 1000 usec,

reliability 255/255, txload 3/255, rxload 36/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full Duplex, 10Mbps, media type is RJ45

output flow-control is unsupported, input flow-control is unsupported

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

Last input 00:00:00, 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: 1815

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 1413000 bits/sec, 147 packets/sec

5 minute output rate 128000 bits/sec, 90 packets/sec

25525566 packets input, 618421246 bytes, 1812 no buffer

Received 85815 broadcasts (0 IP multicasts)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast, 0 pause input

20940307 packets output, 2234891539 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

85814 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

6 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

Any suggestions?

Cheers,

Mo

Lee Smitherman · ‎09-05-2012

Hi,

A couple of questions Im sure everyone will ask...

1) is it slow via the console connection?

2) are you using telnet or ssh?

3) Its it slow to connect and when entering the login credentials

4) If you ping from the device your using to connect(use a good packet size such as 1400), good response times with no drops?

Lee.

Mohit Chauhan · ‎09-05-2012

Hi Lee

To answer to your questions:

1. its not slow on console

2. i am only using ssh, telnet is disabled

3. Connecting is not slow whne you see the login banner, however when i start typing in it takes some time to show me the characters (not always but quite often) as if it is a slow connection, which is not the case.

4. i'll have to double check this response time but for sure dont see any single drop out. i am glad even the users are not complaining. but it is just out of concern that i wanted to make sure everything is OK.

I'll ley you how the response time is..

Mohit Chauhan · ‎09-05-2012

Hi Lee

I did some continuous ping with the load of 1500 and it was constantly at 1ms without a single drop out.

Just to see there wasnt any cpu related error when i did "sho log"

i saw the following setting and info regardng the logging

Console logging: level debugging, 392438 messages logged, xml disabled,

filtering disabled

Monitor logging: level debugging, 726 messages logged, xml disabled,

filtering disabled

Buffer logging: level informational, 418837 messages logged, xml disabled,

filtering disabled

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 418207 message lines logged

I have a feeling if this is causing this grief??

Cheers,

Mo

Lee Smitherman · ‎09-05-2012

Hi,

good spot!!! Worth switching off the logging to see if it helps, quite a few entries there!!! When was the log last cleared?(wondering how long a period these stats are for).

Lee.

Mohit Chauhan · ‎09-05-2012

Lee Smitherman wrote:

Hi,

good spot!!! Worth switching off the logging to see if it helps, quite a few entries there!!! When was the log last cleared?(wondering how long a period these stats are for).

Lee.

Not long, this router is being up for 2 -3 weeks now. which logging you want to try disabling? i was thinking of turning off console logging as i still want to see the buffered logs....

Lee Smitherman · ‎09-05-2012

I would switch it all of just for a minute or two to test, then if it proves to be that, refine what you need logged.

To be honest since your connectivity to the router seems fine, Im not sure what the issue is, but looks a good place to start.

Lee.

singhaam007 · ‎09-21-2012

Hello Mohit,

may be u alredy resolve this issue. but if not it may be a memeory issue, i think the new IOS requered more memory, kindly use

Router#show mem sum

and check ur used and free memory.

please rate if this helpful

thanks

Inderjeet Singh · ‎06-27-2017

Hi Mohit,

Did you find any fix to this issue ?