Differences

This shows you the differences between two versions of the page.

--- resolution_area:watchdog_resolutions:res-w9501 [2021/06/29 17:08] – btobin
+++ resolution_area:watchdog_resolutions:res-w9501 [2021/07/05 20:37] (current) – 10.91.120.28
@@ Line 4: / Line 4: @@
-**Purpose:**
+**Purpose:** Link Polling checks the customer's network elements for their link status i.e are they down or not. This process creates alarms and tickets for the customer's equipment if it is not reachable. If this process has stopped working, it means our customers are not getting alerted to potential outages.
 **Scenario:**
-**Resolution:**
+**Resolution:** First check the Snmp Manager logs to try determine why the link poller has stopped running. The link poller runs on the load balancer for most customers but not all. To be sure, check the database thread config for the server used for IP_CONNECTIVITY.
 **Manual Action Steps:**
+<code>
+-- Database
+select * from thread_config; -- Determine server link polling is running on
-**Auto Clear:**
+-- Server: Check the SNMP Manager logs to see if the issue can be determined
+tailf ~/logs/grails/SnmpManager.log
+</code>
+If the link poller is still down, it can be restarted through the Snmp Manager application *ensure to use fall back on the handler the Link Poller is running on*
+<code>
+https://{env}/SnmpManager/linkPollerConfiguration/list
+-> Start/Stop IP Connectivity Poller
+</code>
+**Auto Clear:** Yes

Internal Errigal Collaboration Wiki