Writing /app/www/public/data/meta/onboarding/snmpmanager/troubleshooting_-_node_monitor_not_loading_issues.meta failed
onboarding:snmpmanager:troubleshooting_-_node_monitor_not_loading_issues

Troubleshooting - Node Monitor Not Loading Issues

Author: Michelle McCausland

Example Customer Request

Support, The SNMP Node Monitor is currently not loading. 
Agents which started the application earlier today appear to be operational, but if they attempt to restart application, it stays hung in “Loading application, please wait…

Solution

The logs revealed this was caused by bad lat/long data being inserted into the database.

Query to find bad lat/long data

select h.id as hubId, h.name as hubName, n.id as nodeId, n.name as nodeName, m.latitude, m.longitude 
from network_element h, network_element n, map_details m 
where n.map_details_id=m.id and n.parent_id=h.id and h.ne_type='Controller'
and (m.latitude like "%'%" or m.longitude like "%'%");

If no rows are returned, then the issue is somewhere else. These are the sites that had the issue:

Hub Id Hub Name Node Id Node Name Latitude Longitude
88567 ATT_MS_UnivMississippi_40 94316 REMOTE 34?21'42.78 89?32'7.70
88568 ATT_MS_UnivMississippi_41 94474 REMOTE 34?21'45.93“N 89?32'5.36”W
111778 VRZ_MS_UnivMississippi_06 111780 SouthWest Prism 34?21'43.60“N 89?32'7.39”W
111778 VRZ_MS_UnivMississippi_06 111781 NorthWest Prism 34?21'45.75“N 89?32'5.71”W

To fix it, first find the relevant map_details_id entries:

select map_details_id from network_element where id in (94316,94474,111780,111781);

Then, null out the map_details_id in network_element for each node:

update network_element set map_details_id=null where id in (94316,94474,111780,111781);

Then, delete the map_details_ids:

delete from map_details where id in (30196,30198,34776,34777);

Reload the node monitor to ensure the issue is resolved.

onboarding/snmpmanager/troubleshooting_-_node_monitor_not_loading_issues.txt · Last modified: 2021/06/25 10:09 by 127.0.0.1