RE: Help with Ping's on Solaris

From: Rebstock, Roland (Roland.Rebstock_at_usi.net)
Date: 01/08/04

  • Next message: Marco Greene (Home): "Weird behaviour after applying patches..."
    Date: Thu, 8 Jan 2004 10:42:52 -0500
    To: <sunmanagers@sunmanagers.org>
    
    

    Update - all servers are set to 100MB FD via /etc/system updates with
    ndd to only go 100MB FD, all switches are set to 100MB FD and I have
    verified that there are no errors on the switches or Firewall
    Interfaces, netstat -I on the servers is also clean.

    Roland

    -----Original Message-----
    From: Rebstock, Roland
    Sent: Thursday, January 08, 2004 10:15 AM
    To: sunmanagers@sunmanagers.org
    Subject: Help with Ping's on Solaris

    All, I have multiple Solaris 7/8 boxes that seem to have some sort of
    ping anomaly going on that I do not see on HPUX 11 or Linux. In
    troubleshooting all networking issues related to a slow application, I
    stumbled across a issue on Solaris that I cannot explain with "PING".
    When looking at the output below notice the ping count "2-4" they drop
    by 1 second and then continue on a 2ms path. It does not happen all the
    time, Im running a check every 5 minutes, some days I get nothing and
    then some days I get flooded, all with the same result of the 2nd ping
    at ex.. 5132ms, 3rd ping at 4132, 4th ping at 3132, 5th ping at 2132ms,
    6th ping at 1132ms, 7th ping at 132ms and then 2ms there after. Does
    anyone have a clue what is causing this? I have only seen this on
    Solaris and not on other operating systems. This particular pod has all
    3 O/S's and only the Solaris boxes do this. By they way, all servers
    are on the same vlan in this case pinging their default gateway, a
    pingable VRRP address on the firewall. I have 2 example below from about
    500 in my inbox over the past month or 2. I have also changed the times
    of the "ping" via cron from 5 minutes to 8 minutes to 3 minutes thinking
    it may be arp but it does not seem to be the case. The servers are
    plugged into Cisco 2948's.

    -----Original Message-----
    From: Super-User
    Sent: Tuesday, January 06, 2004 11:22 PM
    To:
    Subject: check to gw/fw (172.25.0.18) max ping = 3452

    PING 172.25.0.18: 60 data bytes
    68 bytes from 172.25.0.18: icmp_seq=0. time=3. ms
    68 bytes from 172.25.0.18: icmp_seq=1. time=3452. ms
    68 bytes from 172.25.0.18: icmp_seq=2. time=2453. ms
    68 bytes from 172.25.0.18: icmp_seq=3. time=1453. ms
    68 bytes from 172.25.0.18: icmp_seq=4. time=453. ms
    68 bytes from 172.25.0.18: icmp_seq=5. time=2. ms
    68 bytes from 172.25.0.18: icmp_seq=6. time=2. ms
    68 bytes from 172.25.0.18: icmp_seq=7. time=2. ms
    68 bytes from 172.25.0.18: icmp_seq=8. time=3. ms
    68 bytes from 172.25.0.18: icmp_seq=9. time=2. ms

    PING 172.25.0.18: 60 data bytes
    68 bytes from 172.25.0.18: icmp_seq=0. time=3. ms
    68 bytes from 172.25.0.18: icmp_seq=1. time=4023. ms
    68 bytes from 172.25.0.18: icmp_seq=2. time=3023. ms
    68 bytes from 172.25.0.18: icmp_seq=3. time=2023. ms
    68 bytes from 172.25.0.18: icmp_seq=4. time=1023. ms
    68 bytes from 172.25.0.18: icmp_seq=5. time=24. ms
    68 bytes from 172.25.0.18: icmp_seq=6. time=2. ms
    68 bytes from 172.25.0.18: icmp_seq=7. time=2. ms
    68 bytes from 172.25.0.18: icmp_seq=8. time=2. ms
    68 bytes from 172.25.0.18: icmp_seq=9. time=2. ms

    ----172.25.0.18 PING Statistics----
    120 packets transmitted, 120 packets received, 0% packet loss round-trip
    (ms) min/avg/max = 2/67/3452
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: Marco Greene (Home): "Weird behaviour after applying patches..."

    Relevant Pages

    • Re: How to find virus/worm/trojan on network client
      ... | several of my Windows 2000 and Windows 2003 servers and Cisco switches. ... even be able to "ping" an E-Switch because an E-Switch works at ISO Layer 2. ...
      (microsoft.public.security.virus)
    • Pinging issue on a couple of windows 2003 servers
      ... All servers are HP Proliant DL380, 360, or 320 servers. ... I'm having an issue in which some of the servers can ping both of these APC devices, some can only ping 1 of the APC devices, and some cannot ping either of them. ... The 3COM switches are not specifically configured for anything special. ...
      (microsoft.public.windows.server.general)
    • Re: Ping timeout issue?
      ... Are the servers also hard coded at 100mbps full duplex?Yes, ... When is the last time you performed a software upgrade on the switch?We have tried other switches Cisco, ... Have you reapplied OEM drivers for your serverafter applying MSFT.. ... If they're communicating, why is PING important? ...
      (microsoft.public.win2000.networking)
    • test network aggravation
      ... We have a test network that just has a hub and two microsoft servers with ... Since there is just a dumb hub, there is no default gateway so I just left ... It looks like it makes the solaris server the gateway then. ... can't ping the MS servers. ...
      (comp.unix.solaris)
    • Script to ping
      ... I'd like to create a script that could ping my switches and servers and send ...
      (microsoft.public.windows.server.scripting)