Hi again,
thanks for your input, Jeremy and Tom! Of course on the long-run the professional version makes sense but first I have to evaluate Observium using the Open Source Edition. I agree with Tom that using the sysLocation field makes sense as I guess this is what Observium uses to fill the “Location” field in the GUI.
Strange is that only a single device is affected – which is one out of two Windows PC running on exactly the same OS and patch release and using the included SNMP service. One “is” where I would expect it while the second one is showing up on a lonely intersection close to the Bangla border. Both have a valid entry in the service’s “Location” field.
Considering this I am a bit lost and can’t believe that the Professional Edition would change the picture.
Your thought, please!
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans
Sent: Mittwoch, 14. Mai 2014 13:35
To: Observium Network Observation System
Subject: Re: [Observium] Geocoding shows wrong locations
Umm... VLANs or IP addresses are not related to geolocation.
Set a correct sysLocation for your device.
Tom
On 14/05/2014 13:16, Ray, Bjoern Karsten wrote:Hi there,
I am running several VLAN in a distributed environment in Germany. I am using the longitude/latitude options to finally not ending up on “An island in the middle of the ocean”. Yesterday I added another two VLANs and the map shows devices inside e.g. in India.
As I am using private subnet ranges, only, I am wondering why this happens at all and could be done to get over of this little trouble.
Subnets I am using are:
…where the C-octet reflects the VLAN-ID.
Thanks in advance!
_______________________________________________observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium