In previous software releases, the Ultra M Manager was distributed as an RPM bundle which was distributed both within the
USP ISO and as a separate RPM.
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 for configuration and use.
The integrated Ultra M Manager functionality is currently supported only with Ultra M UGP VNF deployments based on OSP 10
and that leverage the Hyper-Converged architecture. The Ultra M Manager RPM is still distributed separately and is intended
only for use in specific deployment scenarios. Contact your local sales or support representative for more information.
Event Aggregation Functionality
With its integration into AutoIT, the Ultra M Manager event aggregation (fault management) configuration process has also
Previously, Ultra M Manager event aggregation configuration was performed through the ultram_cfg.yaml file.
As of this release, this functionality is now configured through NETCONF API-based remote procedure calls invoked via AutoIT
or through a network service descriptor (NSD) configuration file activated through AutoDeploy. In either scenario, the parameters
related to this functionality are defined by/within the fault management descriptor (FMD).
This API is used to configure:
Fault domains: The specific components within the Ultra M solution for which fault management is to be performed. During configuration,
the individual domains for which you wish to perform event aggregation can be specified. Alternatively, if no domains are
specified, then the default behavior is to monitor all domains.
Event severity: Configures the lowest-level severity of the events that are to be monitored. The severity can 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. For example, if a severity
of “major” is configured, then “major”, “critical” and “emergency” events are monitored.
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. SNMP v2c 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.)
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 event aggregation is enabled
for all modules.
Controller, compute, and OSD compute services cannot be configured unless the systemctl module is enabled.
Though the FMD configuration can be included in the NSD configuration file, it is recommended that the configuration 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 configuring parameters 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 of this 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 VIM Orchestrator and VIM NSD configuration file. As such, syslog
proxy functionality for the hardware must be performed after the VIM has been deployed.
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 VIM Orchestrator and VIM
NSD configuration file. As such, syslog proxy functionality for the hardware must be performed after the VIM has been deployed.
Syslogging is automatically enabled for the following services:
Syslogging for UAS Modules
Each UAS software module can be configured to send logs and syslogs to one or more external collection servers.
AutoDeploy and AutoIT
Logs and syslogs are sent directly to one or more external syslog collection servers configured when these modules are first
installed. The configured collection servers are also the receivers for UCS server hardware and OpenStack services for which
AutoIT is a proxy.
The following logs are sent:
In order to support syslogging functionality, additional operators were added to the boot_uas.py script used to install these modules:
Multiple collection server addresses can be configured.
Furthermore, the following additional AutoIT installation parameters have been added to the Provisioning Network Details:
AutoVNF serves as the syslog proxy for the VNFM, UEM, and CF VNF components (VNFCs). It also sends its own logs to the same
external syslog collection server:
Syslogging for the AutoVNF module is configured through the AutoVNF VNFC configuration within the VNF Rack and VNF NSD configuration
- Syslogging for VNFM, UEM, and CF VNFCs
AutoVNF can be configured as the syslog proxy for the following VNFM, UEM, and CF VNF component (VNFC) logs:
Syslogging for the VNFM, UEM, and CF is configured through their respective VNFC configurations within the VNF Rack and VNF
NSD configuration file.
UCS Server Utility Integration with AutoIT
The Ultra M Manager 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 these utilities. Additionally, there
is no difference in function or use except that the utilities are executed from the AutoIT VM.
Refer to the Ultra M Solutions Guide for more information.