Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Ping fails but device is up

I have Orion installedon a pc that has VPN connectivity to my office. I added the 4 routers to the database and it enumerated them with snmp without any problem and I get stats that way. The only problem I have is Orion shows the devices as down and if I try to ping from the menu it fails. from a cmd prompt I have no problem pinging these devices.

Any ideas?

Find more posts tagged with

Accepted answers

All comments

Network_Guru

What is the latency of your VPN connection?

You may need to increase your ICMP timeout settings in Orion,
although I believe the default setting is 2500ms, which should
be enough for almost any VPN connection.

-=Cheers=-
NG

CaptainMorgan

Check with your firewall administrator to see if ICMP is allowed. Everytime I want to "ping" a device that is on vpn or has an internet IP address, I have to have my firewall guy to allow ICMP from my SWinds server to the location you are pinging. My security guy turns off all ICMP to guard against Denial of Service attacks.

Hope this helps.

snowjay

Change the packet size of the ping in the Orion settings. I think by default its aabout 64k which some devices may discard. Pinging from a command prompt is by default 32k.

jonchill

I'm having a similar problem, nodes show they are down or very high packet loss but if I try to telnet of ping them they are fine and not having any problems. This seems to affect multiple devices at a time.

The rest of the network is fine and not overstretched.

I dropped the ICMP packet size right down and increased the timeout and retrys time to maximum but still have major problems at times.

Anyone got any ideas?

Thanks

IT Infrastructure Manager
Pilgrim Hospital
UK

Network_Guru

Jon,

What version of Orion are you running.I can't be sure, but it seems as though I am
seeing more "packet loss" & nodes in warning than before, but if I look at a node graph
from the past 3 months, it doesn't really seem to be any greater than before the upgrade.
Maybe I'm just watching the website more often & intently ?

I made the mistake of upgrading the Orion server and the Orion software at the same time, so now it's really difficult to be objective as far as performance goes. Some things seem
faster, but not as much as I would've expected going from a dual CPU 933 P3 to a Dual CPU
hyperthreaded 2.4 P4

I believe there may be some optimization for this in the next Orion release, due out in the next few weeks ?

-=Cheers=-
NG

jonchill

I'm running v7.0.5 and it's a real pain as our director wants to start getting reliable stats out of the system and at the moment with all the packet loss that happens the stats are not very reliable at all.

Roll on 7.5 if it's going to resolve this issue.

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

jeff.stewart

I'm seeing a similar problem. I added an ICMP Only device to Orion and everything was working fine for a few days. The device has gone up and down several times and we are looking into that. This last time it went down and we had to reboot the device, after coming back up Orion said it was still down. We can ping the device from any machine excpet the poller that the device is on. I can not ping it from Orion or CMD. Any thoughts? This is the only device on this poller having trouble.

archaic0

I'm actually running IP Monitor and seeing a similar problem. Most often it happens with a data circuit (MPLS 1.5M). The circuit will go down for real, IPM will tell us it's down, then when the circuit comes back up, IPM still shows it is down.

During this time, we can ping the router from any computer on our LAN EXCEPT the IPM server. On that server, at the command prompt, pings fail to just that router, and reply to other devices we test. Recently I decided while this was happening to restart the IPM service and as soon as it went down, the pings started replying again. Once IPM started again, everything showed up and my pings kept replying.

It seems that there is a little ghost in the SolarWinds code somewhere that effects both IPM and Orion and causes this issue. I have a ticket open with them today about it, maybe they can shed some light on it.