1 Reply Latest reply on Jun 5, 2015 10:41 AM by clubjuggle

    False Down Alerts

    brentbo

      Hey everybody,

       

      We are getting false 'device down' alerts when ping begins failing between the SolarWinds server and a switch. Everything else can ping the switch, but not the SW server. Here are two trace routes to the 'down' switch, the first from the SW server, the second from another device:

       

      Trace Route from the SolarWinds server

      Tracing route to 192.168.2.27 over a maximum of 30 hops

         1     3 ms    <1 ms     5 ms  172.20.20.201

         2    <1 ms    <1 ms    <1 ms  172.20.101.252

         3    29 ms    28 ms    25 ms  cer-priv-21.inet.qwest.net [65.122.88.33]

         4    50 ms    45 ms    42 ms  sxf-priv-10.inet.qwest.net [216.161.12.177]

         5    75 ms    80 ms    93 ms  216.161.12.178

         6     *        *        *     Request timed out.

         7     *        *        *     Request timed out.

       

      Trace Route from another device

      Tracing route to 192.168.2.27 over a maximum of 30 hops

        1    <1 ms    <1 ms    <1 ms  172.20.20.201

        2    <1 ms    <1 ms    <1 ms  172.20.101.252

        3    29 ms    30 ms    59 ms  cer-priv-12.inet.qwest.net [65.122.88.33]

        4    61 ms    52 ms    49 ms  sxf-priv-10.inet.qwest.net [216.161.12.177]

        5    67 ms    80 ms    70 ms  216.161.12.178

        6    64 ms    85 ms    75 ms  192.168.2.27

       

      216.161.12.178 the the last hop in our MPLS network. Cisco says the SW server it 'not responding to the ping' which doesn't make sense to me.

       

      Ideas?

       

      Thanks in advance....

      Brent Papworth