Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Network Performance Monitor (NPM) > WorldWide Map Auto Placement fails if the Latitude or Longitude ends in 0

WorldWide Map Auto Placement fails if the Latitude or Longitude ends in 0

Created by Travis.Hebbert, last modified by Caroline Juszczak on Feb 05, 2018

Views: 94 Votes: 0 Revisions: 4

Updated October 13, 2017

Overview

If there is a trailing '0' in the Latitude or Longitude value of the SNMP Location field, this will cause the Auto Placement feature of the WorldWide map to fail for that node.

 

The following is an example of an SNMP Location field, using Latitude and Longitude, that failed to resolve during Auto Placement:

Location: 45.13460,-93.09620

Environment

  • NPM 12.0.1 or higher.

Resolution

 

To work around this, you can either verify that the Latitude and Longitude values for 'Location' don't end in '0':

Location: 45.1346,-93.0962

 

Or, you can add a trailing 1 to the end of the value:

Location: 45.134601,-93.096201

 

Suggested Tags:  

 

Reason for Rework or Feedback from Technical Content Review:

 

 

Last modified

Tags

Classifications

Public