10-03-2013 09:31 PM - edited 03-07-2019 03:50 PM
Hello,
I am facing this from ong time.Please check attached file for reference.I am pinging from local machine to access switch where i am getting ping reply more that 1ms.Then to second hop also i am getting some delay.
i have also check traffic on all trunk link but still response is same.
I think i should get reply equal to 1ms in local lan.
Need expert advise on this
10-04-2013 12:33 AM
HI Jeevak,
Can you please check your local machine NIC settings.
go to run> type devmgmt.msc then go to NIC>Configuration>Advanced. Click Speed and Duplex
Both side it should be speed 100, duplex full.
Please also check the port of the swicth where your machine is connected, it should also the same setting on port.
Speed 100
Duplex full.
Hope it helps.
Regards
10-04-2013 03:14 AM
Hello Sandeep,
Thanks for your reply,
My switch end is auto speed and duplex mode.Speed between pc and switch is 1gbps.
10-04-2013 03:18 AM
Can you paste the output from your switch of this command:
sh int XXX (Where your pc is connected).
Regards
10-04-2013 03:41 AM
@ sandeep
GigabitEthernet4/0/5 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is d0c2.829f.9805 (bia d0c2.829f.9805)
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 20:25:52, output 00:00:18, output hang never
Last clearing of "show interface" counters 21:19:55
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 97661
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 10000 bits/sec, 6 packets/sec
5 minute output rate 133000 bits/sec, 159 packets/sec
237192 packets input, 45850775 bytes, 0 no buffer
Received 3616 broadcasts (1218 multicasts)
0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1218 multicast, 0 pause input
0 input packets with dribble condition detected
2004530 packets output, 304690608 bytes, 0 underruns
0 output errors, 0 collisions, 0 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
10-04-2013 03:54 AM
GigabitEthernet4/0/5 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is d0c2.829f.9805 (bia d0c2.829f.9805)
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 20:25:52, output 00:00:18, output hang never
Last clearing of "show interface" counters 21:19:55
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 97661
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 10000 bits/sec, 6 packets/sec
5 minute output rate 133000 bits/sec, 159 packets/sec
237192 packets input, 45850775 bytes, 0 no buffer
Received 3616 broadcasts (1218 multicasts)
0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1218 multicast, 0 pause input
0 input packets with dribble condition detected
2004530 packets output, 304690608 bytes, 0 underruns
0 output errors, 0 collisions, 0 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
I recommend clearing the interface counters and then observing the number of drops over the next hour
can you do : clear counter GigabitEthernet4/0/5
chane the speed and duplex setting and then check it.
Output drops typically indicate a congested interface. This can occur when going from a high speed interface (such as the SW B to SW C link at 1000Mbps) to a lower speed link (SW A to SW B at 100Mbps).
Output drops are not all bad, as the drops indicate the flow control mechanisms of the upper layer protocols are working to decrease the TCP window size. Also, if the drops are due to a constant high-rate flow of traffic you cannot prevent them, but you can control them.
Regards
10-04-2013 05:46 AM
@ Sandeep,
All PCs which are 3 hop away for that i am getting perfect 1ms reply
10-04-2013 07:22 AM
Ok then we will start troubleshooting from swicth :
Can you show the output of all the interface between these devices.
PC--------???>Access Switch ??------------???> Core switch
Command should be : sh int Interface
Can you post the "sh interface
Regards
10-06-2013 07:32 PM
Hello
Remember that ICMP traffic for a switch CPU is lower priority packet, that is not a good way to measure performance or availability in your switches. Having said that once the switch sees the echo request it will process it at software or at hardware, and remember switches do everything at hardware / hard-wired speed.
If you want really to measure speed then, ping from one host to another host across the switches that will give you more accurate information, if you are still concern about it then, take a capture rx in the ingress and tx at the egress port, so that you can check timestamps how long did the packet take to enter and exit the switch.
Regards.
Wilson B.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide