Ultra M Manager Integration with AutoIT

• Feature Summary and Revision History, on page 1• Feature Changes, on page 1

Feature Summary and Revision HistorySummary Data

AllApplicable Product(s) or FunctionalArea

UGPApplicable Platform(s)

Disabled - Configuration RequiredFeature Default

Not ApplicableRelated Features in this Release

• Ultra Gateway Platform System Administration Guide

• Ultra M Solutions Guide

• Ultra Services Platform Deployment Automation Guide

Related Documentation

Revision History

ReleaseRevision Details

N6.0First introduced.

6.2Though this feature was introduced in N6.0, it was not fully qualified. It is now fullyqualified as of this release.

Feature ChangesIn previous software releases, the Ultra MManager was distributed as an RPM bundle which was distributedboth within the USP ISO and as a separate RPM.

Ultra M Manager Integration with AutoIT1

In this release, the functionality enabled through the Ultra M Manager is now part of AutoIT and AutoVNF.Once these UAS modules are installed, health monitoring features and functionality are available forconfiguration and use.

The integrated UltraMManager functionality is currently supported only with UltraMUGPVNF deploymentsbased on OSP 10 and that leverage the Hyper-Converged architecture. The Ultra M Manager RPM is stilldistributed separately and is intended only for use in specific deployment scenarios. Contact your local salesor support representative for more information.

Important

Event Aggregation Functionality

With its integration into AutoIT, the Ultra M Manager event aggregation (fault management) configurationprocess has also changed.

Previously, Ultra M Manager event aggregation configuration was performed through the ultram_cfg.yamlfile.

As of this release, this functionality is now configured through NETCONF API-based remote procedure callsinvoked via AutoIT or through a network service descriptor (NSD) configuration file activated throughAutoDeploy. In either scenario, the parameters related to this functionality are defined by/within the faultmanagement descriptor (FMD).

This API is used to configure:

• Fault domains: The specific components within the Ultra M solution for which fault management is tobe performed. During configuration, the individual domains for which you wish to perform eventaggregation can be specified. Alternatively, if no domains are specified, then the default behavior is tomonitor all domains.

• Event severity: Configures the lowest-level severity of the events that are to be monitored. The severitycan be specified as one of the following (arranged highest to lowest severity):

• emergency -- System level FAULT impacting multiple VNFs/Services

• critical -- Critical Fault specific to VNF/Service

• major -- component level failure within VNF/service.

• alert -- warning condition for a service/VNF may eventually impact service.

• informational -- informational only does not impact service

Configuring the lowest-level severity means that events of that severity and higher are monitored. Forexample, if a severity of “major” is configured, then “major”, “critical” and “emergency” events aremonitored.

If no severity is specified, “informational” is used as the default.

• SNMP descriptor: Configures parameters related to the version(s) of SNMP that are supported. SNMPv2c and v3 are supported.

• VIM parameters: Configures VIM parameters and the specific aspects of OpenStack to be monitored:

• Modules (e.g. ceph, cinder, nova, etc.)

• Controller services (e.g. cinder, glance, heat, etc.)

Ultra M Manager Integration with AutoIT2

Ultra M Manager Integration with AutoITFeature Changes

• Compute services (e.g. ceph-mon.target, ceph-radosgw.target, ceph.target, etc.)

• OSD compute services (e.g. ceph-mon.target, ceph-radosgw.target, ceph.target, etc.)

Individual modules and services can be configured. If no specific modules are configured, then eventaggregation is enabled for all modules.

Controller, compute, and OSD compute services cannot be configured unless thesystemctl module is enabled.

Important

Though the FMD configuration can be included in the NSD configuration file, it is recommended that theconfiguration for this functionality be maintained in a separate, FMD-specific NSD configuration file.

Refer to the Cisco Ultra Services Platform NETCONF API Guide for more information on configuringparameters related to the FMD.

Ultra M MIB Changes

A new object called cultramSiteId was added to the cultramFaultTable in the Ultra M MIB. The addition ofthis object resulted in the object IDs for all other objects in cultramFaultTable being incremented by 1.

Refer to SNMP MIB Changes in StarOS 21.8 and USP 6.2 for details on this change.

Syslog Proxy Functionality

Syslog proxy functionality is supported at the following levels:

• Syslogging for UCS Hardware

Syslogs for the UCS servers that comprise the Ultra M solution are proxied through AutoIT.

The server list is based on the configuration specified in the VIMOrchestrator andVIMNSD configurationfile. As such, syslog proxy functionality for the hardware must be performed after the VIM has beendeployed.

• Syslogging for OpenStack services

AutoIT can be configured to serve as a proxy for OpenStack service syslogs.

The list of servers on which OpenStack is running is based on the configuration specified in the VIMOrchestrator and VIMNSD configuration file. As such, syslog proxy functionality for the hardware mustbe performed after the VIM has been deployed.

Syslogging is automatically enabled for the following services:

• Nova

• Cinder

• Keystone

• Glance

• Ceph monitor (Controller nodes only)

• Ceph OSD (OSD Compute nodes only)

Ultra M Manager Integration with AutoIT3

Ultra M Manager Integration with AutoITFeature Changes

• Syslogging for UAS Modules

Each UAS software module can be configured to send logs and syslogs to one or more external collectionservers.

• AutoDeploy and AutoIT

Logs and syslogs are sent directly to one or more external syslog collection servers configured whenthese modules are first installed. The configured collection servers are also the receivers for UCSserver hardware and OpenStack services for which AutoIT is a proxy.

The following logs are sent:

• AutoDeploy:

• /var/log/upstart/autodeploy.log

• /var/log/syslog

• AutoIT:

• /var/log/upstart/autoit.log

• /var/log/syslog

In order to support syslogging functionality, additional operators were added to the boot_uas.pyscript used to install these modules:

• --syslog-ip<ext_syslog_server_address>

• --port<syslog_port_number>

• --severity<syslog_severity_to_send>

Multiple collection server addresses can be configured.

Furthermore, the following additional AutoIT installation parameters have been added to theProvisioning Network Details:

• Provisional NetworkHAVIP: The VIP address to be assigned to AutoIT's provisional networkinterface.

• AutoVNF

AutoVNF serves as the syslog proxy for the VNFM, UEM, and CF VNF components (VNFCs). Italso sends its own logs to the same external syslog collection server:

• /var/log/upstart/autovnf.log

• /var/log/syslog

Syslogging for the AutoVNF module is configured through the AutoVNF VNFC configurationwithin the VNF Rack and VNF NSD configuration file.

• Syslogging for VNFM, UEM, and CF VNFCs

AutoVNF can be configured as the syslog proxy for the following VNFM, UEM, and CFVNF component(VNFC) logs:

Ultra M Manager Integration with AutoIT4

Ultra M Manager Integration with AutoITFeature Changes

• VNFM (ESC): /var/log/messages

escmanager andmona logs are not configured as part of syslog automation. ESCcan be manually configured to send these logs to the syslog proxy or to an externalsyslog collection server.

Note

• UEM:

• /var/log/em/vnfm-proxy/vnfm-proxy

• /var/log/em/ncs/ncs-java-vm

• /var/log/em/zookeeper/zookeeper

• /var/log/syslog

• CF: All syslogs configured within the StarOS.

Syslogging for the VNFM, UEM, and CF is configured through their respective VNFC configurationswithin the VNF Rack and VNF NSD configuration file.

UCS Server Utility Integration with AutoIT

TheUltraMManager provided utilities to simplify the process of upgrading the UCS server software (firmware)within the Ultra M solution. The integration of Ultra M Manager into AutoIT include full support for theseutilities. Additionally, there is no difference in function or use except that the utilities are executed from theAutoIT VM.

Refer to the Ultra M Solutions Guide for more information.

Ultra M Manager Integration with AutoIT5

Ultra M Manager Integration with AutoITFeature Changes

Ultra M Manager Integration with AutoIT6

Ultra M Manager Integration with AutoITFeature Changes