Worldwide Map - Location Field Issues

Hello,

I've already got a FR raised around this where the AD Sites and Services name is used for the location when using WMI (which isn't in OpenStreetMap format) but was hoping someone else may have a clever way to get round the following issues.

Issues

The location field sometimes has character limits

The WMI uses the AD site and services as its 'location'.

Possible Fixes

Change the field used by the WorldWideMap (then use Alerts & Actions & Custom Properties to set a value)

Create a mapping table for Addresses to site codes

Anyone have any other suggestions?

Thanks,

Pete

Find more posts tagged with

worldwide maps

snmp location

Accepted answers

All comments

cobrien1

What if NPM used the "location" attribute of the site element? Would that work in your environment?

PeterLyttle

It would help for the AD/WMI nodes, however for the SNMP ones that have a limited SNMP location field length they'd still have an issue (I noticed this issue on a Cisco Wireless LAN Controller). Hence a mapping table I thought would solve both issues.

cobrien1

Good point.

PeterLyttle

Linking Idea -

PeterLyttle

I've just noticed that on a Linux server with the Agent installed (and SNMPv3 with location field set), once you switch from SNMP to Agent the location field is left blank.

aLTeReGo

If you edit the node and select 'Include SNMP Credentials' you can provide you SNMPv3 information. It will then be used to collect 'location' and 'Contact' information via SNMP, as well as allow you to use SAM's SNMP Component Monitors against Agent managed nodes.

PeterLyttle

Yep I've the SNMPv3 configured along with the Agent but it still not showing Contact or Location (I assumed the Agent was overriding the SNMP values, which worked previously)?

Edit: It seems there was an issue polling SNMPv3 but as the Agent was the main polling method this wasnt showing.

Selecting a polling method of SNMPv3 - this polls successfully, however selecting Agent with SNMPv3 credentials included I get the following message -

Strange as i'd have thought the same polling method would have been used!