cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
993
Views
0
Helpful
2
Replies

Ping time fluctuated on 3560X

jacko.tang
Level 1
Level 1

I connect a laptop (Intel NIC) to int gi0/5 on WS-C3560X-48T-S (IOS version: Version 12.2(55)SE1). When I try to ping one of the SVI interface address in 3650X, I found that the ping time will be fluctrated. Ping time: average = 5ms , Max. = (may up to 120ms).

The autonegotiation Setting on laptop NIC and int gi0/5 is enabled.


CLI on 3560X

!
interface GigabitEthernet0/5
switchport access vlan 107
switchport mode access
switchport nonegotiate
spanning-tree portfast


!

GigabitEthernet0/5 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is d0d0.fd00.c185 (bia d0d0.fd00.c185)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:07:06, output 00:00:01, 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/40 (size/max)
  5 minute input rate 1000 bits/sec, 1 packets/sec
  5 minute output rate 1000 bits/sec, 1 packets/sec
     572 packets input, 51652 bytes, 0 no buffer
     Received 200 broadcasts (16 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 16 multicast, 0 pause input
     0 input packets with dribble condition detected
     821 packets output, 66524 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

Can anyone tell me how to solve this issue?

Tang

2 Replies 2

glen.grant
VIP Alumni
VIP Alumni

   That is normal .  You shouldn't really ping  internal switch interfaces as benchmark because it puts ping response on the low end of things it is supposed to be doing .  Ping devices thru the switch   if you want real ping response times.

kapathak
Cisco Employee
Cisco Employee

As Glen said. ICMPs are not high priority for switches, and are subject to occasional slowness here and there depending on the other processes occupying the switch's CPU at a particular point of time. The best way to test latency is to check pings through the device, i.e. from one host to another host across the switch.

Cheers!