Operating System - HP-UX
1752569 Members
5011 Online
108788 Solutions
New Discussion юеВ

Randon High count on ping

 
g700304
Super Advisor

Randon High count on ping

Hi

I am using HPUX11.11 with rp3440. I do occassionally get high ping respond even trying to ping itself??

4 bytes from 10.155.4.86: icmp_seq=151. time=2. ms
64 bytes from 10.155.4.86: icmp_seq=152. time=2. ms
64 bytes from 10.155.4.86: icmp_seq=153. time=1682. ms < ----------????
64 bytes from 10.155.4.86: icmp_seq=154. time=1093. ms < ----------???
64 bytes from 10.155.4.86: icmp_seq=155. time=2. ms


What causing this? even pinging to it own ip??
It is driving crazy.

Please advice.
8 REPLIES 8
B. Hulst
Trusted Contributor

Re: Randon High count on ping

Do you get the same ping times to your default gateway?

Are your network card and/or switch/hub or router port set to auto-sense/auto-negotiate the duplex mode and speed?

SoorajCleris
Honored Contributor

Re: Randon High count on ping

Is this from same subnet?
Are you facing problem with all the other IP address ?

Whats your current settings for lancard?

# lanadmin -x 1
Speed = 100 Full-Duplex.
Autonegotiation = On.


Regards,
Sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie
Bill Hassell
Honored Contributor

Re: Randon High count on ping

Run this command on all your LAN cards:

lanadmin -g 0

(where 0=lan0, 1=lan1, and so on). You are looking for errors in the last half of the listing following the Index line. Unless you are connected to a (very old, very slow) 10 Mbit switch, there should be no collisions.


Bill Hassell, sysadmin
g700304
Super Advisor

Re: Randon High count on ping

Here are my respond; Seems looks okay to me.

# lanadmin -x 1
Speed = 1000 Full-Duplex.
Autonegotiation = On.

# lanadmin -g 0

LAN INTERFACE STATUS DISPLAY
Mon, Apr 26,2010 09:50:26

PPA Number = 0
Description = lan0 HP PCI Core I/O 1000Base-T Release B.11.11.27
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x1a4b0b9898
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 466
Inbound Octets = 570859297
Inbound Unicast Packets = 523710764
Inbound Non-Unicast Packets = 136683197
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 84268742
Outbound Octets = 415130206
Outbound Unicast Packets = 484835134
Outbound Non-Unicast Packets = 25166
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

Ethernet-like Statistics Group

Index = 1
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0

Also, tHis server only have one ip.

g700304
Super Advisor

Re: Randon High count on ping

Also when i do this, is this looks good?

netstat -p icmp
icmp:
3638418 calls to generate an ICMP error message
245407 ICMP messages dropped
Output histogram:
echo reply: 188300
destination unreachable: 33918
source quench: 3416147
routing redirect: 0
echo: 0
time exceeded: 52
parameter problem: 0
time stamp: 0
time stamp reply: 0
address mask request: 0
address mask reply: 0
22 bad ICMP messages
Input histogram:
echo reply: 40958431
destination unreachable: 810334
source quench: 87772
routing redirect: 47
echo: 188300
time exceeded: 4289117
parameter problem: 0
time stamp request: 0
time stamp reply: 0
address mask request: 0
address mask reply: 0
188300 responses sent
B. Hulst
Trusted Contributor

Re: Randon High count on ping

And what about pinging the default gateway?
g700304
Super Advisor

Re: Randon High count on ping

Same thing with pinging the default gateway, regards of pinging the server itself or the default gateway.

One thing I notice is, if i ping from other Server to this server... i dont have those problem. Only if i ping itself. :(
B. Hulst
Trusted Contributor

Re: Randon High count on ping

when pinging run in another terminal the tcpdump to trace the lan interface....

you could see error messages.