Re: Spanning tree performance issue

a-abdulrahim · ‎04-23-2005

I have a 4503 with Sup II Plus and a 24 Port Fiber MTRJ module. Running redundancy link to 12 C2950 switch. Configured Spanning Tree and it is working. But when I do a pin from a PC to the 4503, the time varies and seems unstable between 2ms up to 29 ms. Why is that?

Georg Pauwen · ‎04-23-2005

Hello,

before investigating this any further, you might want to try a PING utility like hrPING (see the link below). Most likely you are using the standard Windows PING, which is not really accurate when it comes down to miliseconds. Can you check if you get the same results with this utility ?

hrPING v2.26

http://www.cfos.de/ping/ping.htm

Regards,

GP

a-abdulrahim · ‎04-25-2005

Thanks.. I will try and see how it goes...

a-abdulrahim · ‎04-25-2005

Hi,

These is what I get:

Reply from 192.168.11.200: seq=0002 time=12.860ms TTL=255 ID=1721

Reply from 192.168.11.200: seq=0003 time=13.328ms TTL=255 ID=1722

Reply from 192.168.11.200: seq=0004 time=11.654ms TTL=255 ID=1723

Reply from 192.168.11.200: seq=0005 time=12.276ms TTL=255 ID=1724

Reply from 192.168.11.200: seq=0006 time=7.009ms TTL=255 ID=1725

Reply from 192.168.11.200: seq=0007 time=13.584ms TTL=255 ID=1726

Reply from 192.168.11.200: seq=0008 time=14.731ms TTL=255 ID=1727

Reply from 192.168.11.200: seq=0009 time=12.045ms TTL=255 ID=1728

Reply from 192.168.11.200: seq=000a time=15.342ms TTL=255 ID=1729

Reply from 192.168.11.200: seq=000b time=14.022ms TTL=255 ID=172a

Reply from 192.168.11.200: seq=000c time=11.873ms TTL=255 ID=172b

Reply from 192.168.11.200: seq=000d time=15.061ms TTL=255 ID=172c

Reply from 192.168.11.200: seq=000e time=17.325ms TTL=255 ID=172d

Reply from 192.168.11.200: seq=000f time=10.849ms TTL=255 ID=172e

Reply from 192.168.11.200: seq=0010 time=10.740ms TTL=255 ID=172f

Reply from 192.168.11.200: seq=0011 time=10.243ms TTL=255 ID=1730

Reply from 192.168.11.200: seq=0012 time=14.698ms TTL=255 ID=1731

Reply from 192.168.11.200: seq=0013 time=16.028ms TTL=255 ID=1732

Reply from 192.168.11.200: seq=0014 time=9.969ms TTL=255 ID=1733

Reply from 192.168.11.200: seq=0015 time=13.027ms TTL=255 ID=1734

Reply from 192.168.11.200: seq=0016 time=16.138ms TTL=255 ID=1735

Reply from 192.168.11.200: seq=0017 time=15.764ms TTL=255 ID=1736

Reply from 192.168.11.200: seq=0018 time=11.176ms TTL=255 ID=1737

Reply from 192.168.11.200: seq=0019 time=15.773ms TTL=255 ID=1738

Reply from 192.168.11.200: seq=001a time=15.379ms TTL=255 ID=1739

Reply from 192.168.11.200: seq=001b time=0.712ms TTL=255 ID=173a

Reply from 192.168.11.200: seq=001c time=1.659ms TTL=255 ID=173b

Reply from 192.168.11.200: seq=001d time=1.940ms TTL=255 ID=173c

Reply from 192.168.11.200: seq=001e time=11.565ms TTL=255 ID=173d

Reply from 192.168.11.200: seq=001f time=13.085ms TTL=255 ID=173e

Reply from 192.168.11.200: seq=0020 time=15.729ms TTL=255 ID=173f

Reply from 192.168.11.200: seq=0021 time=3.759ms TTL=255 ID=1740

Reply from 192.168.11.200: seq=0022 time=9.527ms TTL=255 ID=1741

Reply from 192.168.11.200: seq=0023 time=11.139ms TTL=255 ID=1742

Reply from 192.168.11.200: seq=0024 time=3.608ms TTL=255 ID=1743

Reply from 192.168.11.200: seq=0025 time=9.441ms TTL=255 ID=1744

Reply from 192.168.11.200: seq=0026 time=11.853ms TTL=255 ID=1745

Reply from 192.168.11.200: seq=0027 time=4.208ms TTL=255 ID=1746

Reply from 192.168.11.200: seq=0028 time=3.529ms TTL=255 ID=1747

Reply from 192.168.11.200: seq=0029 time=7.097ms TTL=255 ID=1748

Reply from 192.168.11.200: seq=002a time=3.979ms TTL=255 ID=1749

Reply from 192.168.11.200: seq=002b time=6.610ms TTL=255 ID=174a

Reply from 192.168.11.200: seq=002c time=6.743ms TTL=255 ID=174d

Reply from 192.168.11.200: seq=002d time=3.100ms TTL=255 ID=1750

Reply from 192.168.11.200: seq=002e time=8.770ms TTL=255 ID=1753

Reply from 192.168.11.200: seq=002f time=3.569ms TTL=255 ID=1756

Reply from 192.168.11.200: seq=0030 time=8.729ms TTL=255 ID=1759

Reply from 192.168.11.200: seq=0031 time=1.554ms TTL=255 ID=175c

Reply from 192.168.11.200: seq=0032 time=2.843ms TTL=255 ID=175d

Reply from 192.168.11.200: seq=0033 time=5.638ms TTL=255 ID=175e

Reply from 192.168.11.200: seq=0034 time=4.319ms TTL=255 ID=175f

Reply from 192.168.11.200: seq=0035 time=0.969ms TTL=255 ID=1760

Reply from 192.168.11.200: seq=0036 time=7.016ms TTL=255 ID=1761

Reply from 192.168.11.200: seq=0037 time=9.230ms TTL=255 ID=1762

Reply from 192.168.11.200: seq=0038 time=7.507ms TTL=255 ID=1763

Reply from 192.168.11.200: seq=0039 time=7.578ms TTL=255 ID=1764

Reply from 192.168.11.200: seq=003a time=9.443ms TTL=255 ID=1765

Statistics for 192.168.11.200:

Packets: sent=78, rcvd=77, error=0, lost=1 (1% loss) in 38.504375 sec

I do not know what is wrong, but I know something is not right.

glen.grant · ‎04-24-2005

pinging the management address on the switch will vary widely dependingh on what the switch is doing at any given time as ping response is given low priority in the switch . Always ping thru the switch to devices attached to the switch .