cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1566
Views
0
Helpful
8
Replies

"Irregular Pinging"

tiagolages
Level 1
Level 1

Hi

I have one problem on two Catalysts 2900 XL. When i ping the switch the responses times are high and very irregular.

I have more catalyst on the same network and they dont have this problem.

I tried to isolate one of the catalyst from the network (disconecting from the network and only with one pc conected to the swicht) and the problem persists.

Thanks

8 Replies 8

Kevin Dorrell
Level 10
Level 10

Switches give a very low priority to internal ping, so if there is anything going on in the switch, pings might become irregular. How is the CPU utilization on those switches? Here is a document that might help:

http://www.cisco.com/en/US/products/hw/switches/ps607/products_tech_note09186a0080094e78.shtml

Is there any particular pattern to this irregularity?

Kevin Dorrell

Luxembourg

I can't see any pattern to this irregularity. I've looked to the document and i can't understand the results: why cpu utilization is higher on the Switch 2?? ()

Switch 1 (Cisco Catalyst 2900 XL, with the 24 FastEthernet ports used by computers)

Pinging the switch:

Reply from 192.168.10.226: bytes=32 time=2ms TTL=254

Reply from 192.168.10.226: bytes=32 time=2ms TTL=254

Reply from 192.168.10.226: bytes=32 time=2ms TTL=254

Reply from 192.168.10.226: bytes=32 time=2ms TTL=254

Reply from 192.168.10.226: bytes=32 time=2ms TTL=254

Reply from 192.168.10.226: bytes=32 time=2ms TTL=254

CPU utilization:

CPU utilization for five seconds: 17%/10%; one minute: 25%; five minutes: 23%

Switch 2 (Cisco Catalyst 2900 XL, with the 1 FastEthernet port used by one computer)

Pinging the switch:

Reply from 192.168.10.233: bytes=32 time=2ms TTL=254

Reply from 192.168.10.233: bytes=32 time=1ms TTL=254

Reply from 192.168.10.233: bytes=32 time=13ms TTL=254

Reply from 192.168.10.233: bytes=32 time=53ms TTL=254

Reply from 192.168.10.233: bytes=32 time=1ms TTL=254

Reply from 192.168.10.233: bytes=32 time=1ms TTL=254

Reply from 192.168.10.233: bytes=32 time=22ms TTL=254

Reply from 192.168.10.233: bytes=32 time=31ms TTL=254

Reply from 192.168.10.233: bytes=32 time=13ms TTL=254

Reply from 192.168.10.233: bytes=32 time=49ms TTL=254

CPU utilization:

CPU utilization for five seconds: 32%/6%; one minute: 31%; five minutes: 29%

Thanks

davisbg5151
Level 1
Level 1

Did you check for duplex mismatch issues?

Yes i did, and i don't have any duplex mismatch.

Hi,

Try connecting the PC to different ports on the Switch and see the ping results.Also look for any CRC errors or drops on the port.If you see any errors then it could be HW issue or compatibility issue.Call your Reseller/distributor.

HTH

MAR

Hi,

I tried with different ports and i've got the same result. I dont have any CRC errors in the switch port:

FastEthernet0/24 is up, line protocol is up

Hardware is Fast Ethernet, address is 00d0.ba99.5258 (bia 00d0.ba99.5258)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive not set

Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 1 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

1958 packets input, 158209 bytes

Received 681 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 10 multicast

0 input packets with dribble condition detected

2516 packets output, 198153 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

Finally you can do one thing, it might be idiotic what i say, but since you say that you tried almost all the possibilitiez, i would request you to erase & configure the switch once again & try, even if still doesn't work out, try to upgrade the IOS, it might help. becuase i faced similar problem in 1700 series Router,serial cable,ehternet port/cable, leased line connectivity was also fine,infact i tried even erasing & configuring once again but still i faced, so finally i upgraded the IOS which i was having the same back-up of that 1700 series)

I h've already tried, but the problem persists.

Review Cisco Networking for a $25 gift card