9 Replies Latest reply on Jan 13, 2014 7:15 AM by aaron.deacon

    able to ping ip but node shows down

      I have an icmp node that Orion shows down.

       

      I'm able to ping this ip from any pc both inside and outside my network.

      It is a static public IP.

      I've deleted the node and made a new one.

      The IP belongs to a Linksys router that has global pings accepted.

      I'm able to port scan and telnet into open ports on this static public IP.

       

      How can i get a simple icmp node to show status up?

       

      Thanks!

        • Re: able to ping ip but node shows down
          Congo

          I'm able to ping this ip from any pc both inside and outside my network.

          But can you trace to it from your polling engine box?

          • Re: able to ping ip but node shows down
            etucker

            I had this issue and found that I could not ping the device from my solarwinds box but could from my pc. After I found the issue and corrected it then everything was fine. do a ping or traceroute from your solarwinds box and I believe you will find the issue

              • Re: able to ping ip but node shows down

                Tracert from Orion box is fine all the way back to their ISP.   Two hops 'request timed out' but it does complete.

                 

                Why would an ICMP node show down but I'm able to ping the IP from the same box as Orion NPM?

                  • Re: able to ping ip but node shows down
                    etucker

                    can you provide the traceroute from your NPM box? Something does not sound correct. have you tried deleting the node and then readding it?

                      • Re: able to ping ip but node shows down

                        Node:

                            66.224.33.58        0047_Txxxxxxxxxxxxxxxxxx_66.224.33.58_2007047115    No response    No response        100 %

                         

                        From the same box as Orion NPM.

                         

                        Pinging 64.62.16.238 with 32 bytes of data:

                        Reply from 64.62.16.238: bytes=32 time=149ms TTL=107
                        Reply from 64.62.16.238: bytes=32 time=148ms TTL=107
                        Reply from 64.62.16.238: bytes=32 time=149ms TTL=107
                        Reply from 64.62.16.238: bytes=32 time=148ms TTL=107

                        Ping statistics for 64.62.16.238:
                            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                        Approximate round trip times in milli-seconds:
                            Minimum = 148ms, Maximum = 149ms, Average = 148ms

                         

                         

                        Tracing route to 64.62.16.238 over a maximum of 30 hops

                          1    <1 ms    <1 ms    <1 ms  10.5.220.1
                          2    <1 ms    <1 ms    <1 ms  ip-65-38-102-2.hou.vericenter.com [65.38.102.2]

                          3     2 ms     2 ms     2 ms  ip-63-101-54-3.hou.vericenter.com [63.101.54.3]

                          4     9 ms     9 ms     9 ms  border8.p4-1.vericenter-2.hou.pnap.net [216.52.1
                        70.49]
                          5    10 ms    10 ms     9 ms  core5.po2-bbnet2.hou.pnap.net [216.52.168.74]
                          6    12 ms    11 ms    12 ms  border3.te4-4.xocomm-25.ext1.dal.pnap.net [63.25
                        1.44.41]
                          7    12 ms    12 ms    12 ms  core3.tge5-2-bbnet2.ext1.dal.pnap.net [216.52.19
                        1.98]
                          8    12 ms    12 ms    12 ms  aer1-ge-4-5.dallasequinix.savvis.net [208.175.17
                        5.17]
                          9    12 ms    12 ms    12 ms  dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.2
                        04.146]
                         10    12 ms    12 ms    13 ms  cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196
                        .29]
                         11    42 ms    41 ms    42 ms  cr1-pos-0-0-3-0.losangeles.savvis.net [204.70.19
                        2.249]
                         12    41 ms    42 ms    41 ms  bpr1-ge-3-0-0.losangeles.savvis.net [204.70.192.
                        222]
                         13    87 ms    87 ms    87 ms  wiltel-communications-group-inc.losangeles.savvi
                        s.net [208.173.55.186]
                         14   109 ms   109 ms   108 ms  tg9-4.cr01.lsancarc.integra.net [209.63.113.57]

                         15   107 ms   108 ms   107 ms  tg13-1.cr01.sntdcabl.integra.net [209.63.113.106
                        ]
                         16   111 ms   108 ms   112 ms  tg13-4.cr02.sntdcabl.integra.net [209.63.113.134
                        ]
                         17   108 ms   107 ms   107 ms  tg13-1.cr02.rcrdcauu.integra.net [209.63.114.169
                        ]
                         18   110 ms   110 ms   109 ms  tg13-4.cr01.rcrdcauu.integra.net [209.63.114.101
                        ]
                         19   107 ms   107 ms   107 ms  tg13-2.cr01.ptleorte.integra.net [209.63.114.45]

                         20   109 ms   108 ms   109 ms  tg13-1.cr01.sttlwatw.integra.net [209.63.114.97]

                         21   107 ms   110 ms   107 ms  209.210.12.30
                         22     *        *        *     Request timed out.
                         23   107 ms   107 ms   107 ms  64.65.188.138
                         24     *        *        *     Request timed out.
                         25   150 ms   148 ms   150 ms  64.62.16.238
                         26   151 ms   149 ms   149 ms  64.62.16.238

                        Trace complete.

                  • Re: able to ping ip but node shows down
                    aaron.deacon

                    Removing and then re adding worked for me - it did a rediscover and it came back online