Campus Switching and Routing

Reply
Contributor I

Ping response on S2500 MAS

 

Gents,
 
I have 2 switches 
 
- 1 Cisco Catalyst 3750
- 1 ARUBA S2500
 
Testing few things I notice when I connect my laptop direct to the Cisco SW and try to ping the SW using just a patch cord I have the follow response.
 
cmd1.JPG
 
 
If I connect my laptop direct to the ARUBA S2500 SW and try to ping the SW I have the follow response.
 
cmd2.JPG
 
 
so.. here is my question.. by default is any configuration enable on the ARUBA SW side? something like QoS or anything like that? why I'm getting this response from the Switch?
 
After that I tried different things..
 
- Used a different patch cord 
- Tried different ports
- Tried different Up-link
-  Used a different laptop
-  Booth Switches have been restored to factory defaults
 
Even trying to ping both switches with different packet size 1024 bytes I'm still getting this response from the ARUBA S2500
 
 
I:\>ping 172.19.19.157 -l 1024 -t
 
Pinging 172.19.19.157 with 1024 bytes of data:
Reply from 172.19.19.157: bytes=1024 time=9ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=1ms TTL=64
Reply from 172.19.19.157: bytes=1024 time=2ms TTL=64
 
 
Any other suggestion to get a <1 ping response? 
 
Best regards,
 
Giovanni Saldarriaga
Aruba

Re: Ping response on S2500 MAS

Giovanni,

My recollection on this behavior is that ping is handled by a lower priority thread in the control plane as it should be handling more important tasks such as STP or OSPF. The ping delays are not an indicator of an issue.

 

Best regards,

 

Madani

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: