Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

experiencing delay in pinging to gateway ip


hi all

I HAVE EXPERIENCED HUGE DELAY CONSTANTLY TO REACH GATEWAY.

mY NETWORK TOPO:

L2 switch(cisco 2960)------------fibre(200fts)-----------------L3switch(cisco 3750)--------Firewall(sonic wall)

Under L2 switch we have 30 users which is our branch office l2 switch is serving DHCP based on mac-binding.

L2 config:

interface vlan 99

ip add   10.10.14.2 255.255.255.0

DHcp:

ip dhcp pool branch office

network 10.10.14.0 255.255.255.0

default-router 10.10.14.1 255.255.255.0-----------------pointing to L3(3750) switch vlan99

dns-s erver 10.10.10.6

enabled dhcp snooping globally and ip source guard per interface and provide child pools for all the mac addresses.

L3 config:

interface vlan 99

ip add 10.10.14.1 255.255.255.0

L3switch# sh ip route

C       10.10.14.0/24 is directly connected, Vlan99

C       10.10.10.0/23 is directly connected, GigabitEthernet1/0/24

S*   0.0.0.0/0 [1/0] via 10.10.10.1

Here is my Output of ping to gateway from branch office:

C:\Users\srikanth.athelly>ping 10.10.10.1 -t

Pinging 10.10.10.1 with 32 bytes of data:

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time=36ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<38ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<38ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time=38ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time=31ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<25ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

Reply from 10.10.10.1: bytes=32 time<1ms TTL=63

C:\Users\srikanth.athelly>tracert 10.10.10.1

Tracing route to 10.10.10.1 over a maximum of 30 hops

  1     6 ms    <1 ms    <1 ms  10.10.14.1

  2    <1 ms    <1 ms    <1 ms  10.10.10.1

Is dere anything i have to change here in topology wise or command wise

thanks for the help in advance

regards

sreek

2 REPLIES
Cisco Employee

experiencing delay in pinging to gateway ip

Hello,

Can you ping same GW from L3 switch and compare trace results. I'm wondering if there are any CPU load on the GW which adds to the processing of the ICMP coming to it. Thus the new ping can help us to come closer to it eliminating part of infra.

Nik

Silver

experiencing delay in pinging to gateway ip

why there is Ip given on vlan 99 on L2 switch? I think this should not be required since ur L3 has already SVI configured..

1.can u try to ping between user and check the latency ?

2. If that is good then check fibre between L2 and L3 .. I mean just try to check with high troughput ..

Lets try this then we will see further

---

Posted by WebUser Vishal Nijapkar

430
Views
0
Helpful
2
Replies
CreatePlease login to create content