Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
418
Views
0
Helpful
1
Replies

WS-C2960X-48FPS-L Ping performance response

gimp
Level 1
Level 1

‎07-19-2017 01:33 AM - edited ‎03-05-2019 08:52 AM

Hi,

I've just installed 5 new switches  WS-C2960X-48FPS-L in my network. All switches are connected via Port-Channel with two GigaEthernet port into the same central switch c6509.

In particular, when I ping one of this switches, it has a high response time, like this:

Esecuzione di Ping 172.17.1.12 con 32 byte di dati:
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=8ms TTL=254
Risposta da 172.17.1.12: byte=32 durata<1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=11ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=82ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=16ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=16ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=17ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=10ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=15ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=7ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=24ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=95ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=11ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=6ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=16ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=6ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=12ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=5ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=10ms TTL=254
Risposta da 172.17.1.12: byte=32 durata<1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=151ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=14ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=13ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=8ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=10ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=7ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=107ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=2ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=12ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=1ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=10ms TTL=254
Risposta da 172.17.1.12: byte=32 durata=4ms TTL=254

All switches have the same CPU utilization (50%) and IOS: c2960x-universalk9-mz.152-2.E5.bin

Is it normal or not ? 

Below some info and data..

This is the Etherchannel:

Number of channel-groups in use: 1
Number of aggregators:           1

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
7      Po7(SU)         PAgP      Gi1/0/49(P) Gi1/0/50(P)

Ports for the etherchannel

Gi1/0/49  Connesso a C6509E- connected    trunk      a-full a-1000 1000BaseSX SFP
Gi1/0/50  Connesso a C6509E- connected    trunk      a-full a-1000 1000BaseSX SFP

Traffic ports:

GigabitEthernet1/0/49 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 70d3.793a.2831 (bia 70d3.793a.2831)
  Description: Connesso a C6509E-CED-AEA
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX SFP
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:11, output 00:00:10, 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 1833000 bits/sec, 1721 packets/sec
  5 minute output rate 151000 bits/sec, 97 packets/sec
     916986536 packets input, 408411162426 bytes, 0 no buffer
     Received 524916714 broadcasts (483105634 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 483105634 multicast, 0 pause input
     0 input packets with dribble condition detected
     312221958 packets output, 119715192753 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     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
GigabitEthernet1/0/50 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 70d3.793a.2832 (bia 70d3.793a.2832)
  Description: Connesso a C6509E-CED-AEA
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX SFP
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:03, 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 3767000 bits/sec, 668 packets/sec
  5 minute output rate 298000 bits/sec, 213 packets/sec
     900265937 packets input, 371942496711 bytes, 0 no buffer
     Received 490539052 broadcasts (423419826 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 423419826 multicast, 0 pause input
     0 input packets with dribble condition detected
     124433779 packets output, 47160951414 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     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

Best Regards

Michele

Labels:
0 Helpful
1 Reply 1

Joseph W. Doherty
Hall of Fame
Hall of Fame

‎07-19-2017 05:12 AM

Is it normal or not ? 

It very well could be normal.  Ping response is a low priority task to a Cisco network device.  If fact, some Cisco devices support SLA responders to try to provide a much more accurate network delay ping response (one the accounts for internal response delay).

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card