User Tools
support:device_missing_alarm_handling
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| support:device_missing_alarm_handling [2018/07/20 12:48] – created ywang | support:device_missing_alarm_handling [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Device Missing Alarm Handling ====== | ||
| + | |||
| + | Author: Yanjun Wang | ||
| + | |||
| + | ===== Device Missing Alarm ===== | ||
| + | |||
| + | Device Missing Alarm from the IDMS is to alert users that a trap was received and processed which referenced an unknown child network element. Unknown meaning there is no such child element under the particular controller in the SNMP-Manager knowledgebase. (this alarm can be assigned to the controller level at this stage depending on the trap rule) | ||
| + | |||
| + | The purpose of Device Missing Alarm is informing IDMS users to investigate if a new network element was loaded onto the controller but the Errigal IDMS Knowledge-base was not updated with this information. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== How does IDMS create Device Missing Alarm ===== | ||
| + | |||
| + | * In trap specific trap rule | ||
| + | * Based on the IP address with the trap, identify controller in the knowledgebase | ||
| + | * Combine child element name in the trap rule based on the information provided in the trap varbind, and try to find the element per the child name under the controller | ||
| + | * If the child element cannot be found, send a Device Missing Alarm from trap rule to IDMS | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Resolve Device Missing Alarm ===== | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | * Identify a Device Missing Alarm by checking the Alarm Name on a General Trap Summary(as above). | ||
| + | * Check the Alarm Identifier, if it's DiscoveredNameMatchingFailed, | ||
| + | * Login to the remote controller with the Hub IP on General Trap Summary or other tools, verify the element is on the remote side. *If the element is now on the remote controller, it may be a trap issue then, please contact Errigal Support. | ||
| + | * Get the controller name and child element name(equipmentIdentifier) on the General Trap Summary | ||
| + | * Check the child element under the controller on EMS Host Tree or download the spreadsheet of the controller from Excel Loading: Export Hub with Nodes, check if the child element is missing from the knowledgebase. | ||
| + | * Add the missing child element through Excel Loading sheet. | ||
| + | * Clear the Device Missing Alarm in Node Monitor. | ||
| + | * For other issues which are not able to resolve with above steps, could be either trap tule issue or RemoteDiscoveryScript issue. | ||
| + | |||
| + | |||
| + | |||
Page Tools
