SD-WAN Nokia-Nuage Networks Collector AMQP Alarms

This document provides details on the working of Nokia-Nuage alarm runner along with the mapping details for severity and errorCondition.

This section describes how alarms from AMQP are translated to SevOne NMS alerts.

1. Create alerts in SevOne NMS if the alarm type is CREATE.
   1. If targetObject is nsgateway or nsport, create alerts for the respective device on SevOne NMS.
   2. Create alerts based on the following.
      1. Message - (sdwan:<Category>:<Name>)<title>/<remedy>)
         • <Category> - Category is defined based on the mapping between Category and errorCondition from AMQP. The default category must be Control. For details related to mapping, please refer to section Mappings > errorCondition.
         • <Name> - Name is defined based on the mapping between Name and errorCondition from AMQP. The default name must be description from AMQP. For details related to mapping, please refer to section Mappings > errorCondition.
         • <title> / <remedy> - Title / remedy must be the same as AMQP. If either is unavailable, please leave it as blank.
      2. Severity - Severity of the alerts is based on the mapping between SevOne NMS alert and severity from AMQP. The default value is Error. For details related to mapping, please refer to section Mappings > Severity.
2. Discard alarms if any of the following conditions arise.
   1. Alarm type is not CREATE or DELETE.
   2. targetObject is not nsgateway or nsport.
   3. Alarms do not have sourceEnterpriseID.
3. Clear alerts from SevOne NMS if the alarm type is DELETE.