I wonder, if given the absence of all other location information for a device, the final action could be to resolve location via geo-ip location mapping. Obviously this would not help with devices numbered out of RFC1918 but may be of some additional use. I would be happy to attempt a patch. I know geo-ip isn't exact and there are issues, especially with IPv6. But seems like an easy gain.
Thoughts?
--chip
On Wed, Aug 7, 2013 at 10:13 AM, Adam Armstrong adama@memetic.org wrote:
On 2013-08-07 13:45, Josh Hopper wrote:
What I have is more of a question….
· Environment:
Sonicwall, Windows Server 2003, Windows Server 2008, Dell PowerConnect 6224, Dell PowerConnect 3524, Dell PowerConnect 5448, ESX5 and ESX4
DESCRIPTION
I have Observium 0.13.8.4256 installed. I believe this is the most updated version. I have entered a sysLocation on all of my devices and within the Observium GUI I set a sysLocation as well. All of my devices sit in the Atlantic ocean.
This is the default location when a location doesn't properly geolocate.
You've either been unlucky enough to chose a load of un-geolocatable locations, or your server doesn't have access to the geolocation API. Are you firewalling it?
BTW, don't set the in-GUI location if you have a sysLocation. It's only there to provide workaround when you can't set sysLocation.
The location will only be re-geolocated if the location changes. You can force it to be re-located by setting location_lat and location_lon to NULL in the devices table in the database.
adam.
______________________________**_________________ observium mailing list observium@observium.org http://postman.memetic.org/**cgi-bin/mailman/listinfo/**observiumhttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium