SD-WAN Nokia-Nuage Networks Collector AMQP Alarms

SevOne Documentation

All documentation is available from the IBM SevOne Support customer portal.

© Copyright International Business Machines Corporation 2023.

All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of IBM and its respective licensors. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of IBM.

IN NO EVENT SHALL IBM, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF IBM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IBM DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.

IBM, the IBM logo, and SevOne are trademarks or registered trademarks of International Business Machines Corporation, in the United States and/or other countries. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on ibm.com/trademark.

About

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

Alerts in SevOne NMS for AMQP Alarms

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.

    • If targetObject is nsgateway or nsport, create alerts for the respective device on SevOne NMS.

    • Create alerts based on the following.

      • 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.

      • 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.

    • Alarm type is not CREATE or DELETE.
    • targetObject is not nsgateway or nsport.
    • Alarms do not have sourceEnterpriseID.

  3. Clear alerts from SevOne NMS if the alarm type is DELETE.

Mappings

Severity

Severity from AMQP SevOne NMS alert
CRITICAL Critical
MAJOR Error
WARNING Warning
MINOR Info
INFO Info

errorCondition

errorCondition from AMQP Category Name
3712 Control NSG_RELOAD_CONFIG_STILL_PENDING
4000 Control NODE_EXECUTION_FAILURE
50050 Control DC_BGP_NEIGHBOR_ALARM
7012 Control VPORT_NOT_FOUND
60001 Control ELASTIC_HEALTH_CHECK_FAILURE
8011 System SYSMON_VSC_DOWN
2722 System INVALID_L2DOMAIN_IN_VM_REQUEST
2701 System DUPLICATE_MAC_IN_SUBNET
2702 System SUBNET_FULL
2703 System STATIC_IP_OUT_OF_RANGE
2704 System STATIC_IP_ALREADY_ASSIGNED
3729 Control INFRASTRUCTURE_VSC_PROFILE_NOT_ASSIGNED
2706 System INVALID_ENTERPRISE_IN_VM_REQUEST
2707 System VM_ASSOCIATION_WITH_ENTERPRISE_CANNOT_CHANGE
2708 System INVALID_USER_IN_VM_REQUEST
2709 System INVALID_DOMAIN_IN_VM_REQUEST
2710 System INVALID_ZONE_IN_VM_REQUEST
2711 System PUBLIC_SUBNET_NOT_ASSOCIATED_TO_SHARED_PUBLIC_SUBNET
2705 Security VM_ATTACH_TO_ZONE_PERMISSION
2713 System NEW_VM_NO_LIBVIRT
50001 Control HTTP_PROBE_FAILURE
3743 Control INFRASTRUCTURE_VSC_PROFILE_ADDRESS_DUPLICATE
2720 System VM_INTERACE_LICENSE_VALIDATION
4001 Control BGP_NEIGHBOR_ALARM
3746 Control NSG_PORT_PHYSICAL_NAME_INVALID Error
4707 Control DISCONNECTED_GATEWAY
4708 Control DISCONNECTED_GATEWAY_CONTROLLER_LESS
4711 Control DISCONNECTED_GATEWAY_HEAD_LESS
4712 Control NSG_PORT_DOWN
4713 Control GATEWAY_DISCONNECTED_FROM_CONTROLLER
4715 Control DISCONNECTED_VRS
4716 Control VRS_DISCONNECTED_FROM_CONTROLLER
50003 Control IKE_TUNNEL_FAILURE
2804 System NO_LICENSES_FOUND
2723 Security VM_ATTACH_TO_L2DOMAIN_PERMISSION
2806 System LICENSE_USAGE_ABOVE_THRESHOLD
2807 System VRS_LICENSE_VALIDATION
2724 System MAINTENANCE_MODE_PARENT
2719 System VM_LICENSE_VALIDATION
3710 Control INFRASTRUCTURE_PROFILE_NOT_ASSIGNED
4002 Control ROUTING_POLICY_ALARM