Wavence management support

Element manager support

Wavence devices support the following external element managers:

• NEtO: opens the GUIs to manage Wavence SA devices (MCT) and Wavence SM devices with Core-Enhanced cards (WebEML)

• WebCT: web interface for Wavence SM devices using the CorEvo card

Wavence management using the NSP

You can use the NSP to view, configure, and monitor Wavence objects. Wavence nodes that have been discovered using the NFM-P appear in the NSP, and are available for basic NSP functions including supervision and fault management.

Management tasks you can accomplish using the NSP include:

• Monitor device utilization and function using the Network Map and Health dashboard. See the NSP Network Automation Guide for more information.

• Fault management and root cause analysis using the Network Map and Health dashboard. See the NSP Network and Service Assurance Guide.

• Network inventory using the Network Inventory view. See the NSP Network and Service Assurance Guide. This view supports SMR, displaying UBT-SA nodes as sub-units of IXR or SAR nodes.

• Perform OAM tests using NSP troubleshooting. See the NSP Network Automation Guide.

• Perform CFM Loopback and CFM DMM tests using NSP Data Collection and Analysis Management. See Workflow to configure NSP test templates for Wavence CFM Loopback and CFM Stats

• Monitor backhaul service health using the Network Map and Health dashboard. See To display Wavence backhaul service status information on the NSP Network Map and Health dashboard.

• Create microwave backhaul services using intent-based service fulfillment. See Microwave backhaul service creation using NSP Intent-Based Service Fulfillment

• Large-scale device configuration for MPR system settings on Wavence MSS nodes. See Workflow to configure MPR system settings on Wavence MSS nodes using the NSP for an overview of how to import a template to configure MSS nodes, and the NSP Network Automation Guide and NSP Device Management Guide for more information about using the NSP.

• Track indicators using NSP data analysis. For information about Wavence-specific object filters, see Wavence example object filters for the NSP. For information about using the Insights Administrator application, see the NSP Data Collection and Analysis Guide.

Note: When using the wavence-service-migration operation in NSP, if two VLAN services have been created with the same sites and adjacencies, migrating one of the services will migrate both services – even if they have different VLAN service IDs.

Service management considerations

You can provision and activate services across Wavence devices discovered in the NSP. For more information about service management, see the NSP Service Management Guide. When using the NSP to manage Wavence services, be aware of the following considerations.

CAHD ports on MSS-4/8 nodes appear available for service deployment, but are only functional when used in a Radio LAG.

Intent-based radio parameter configuration considerations

You can efficiently configure radio parameters on Wavence devices using intents in the NSP. For more information about using intents, see the NSP Network Automation Guide. When using intents to configure Wavence devices, be aware of the following considerations.

Errors are logged in the EmsServer.log file. When there is a failure in radio parameter configuration, check this log file to determine the cause.

Target port lists may show all radio ports regardless of the type of ports selected. Ensure you are selecting the correct radio ports.

Only one radio LAG per node can be selected when configuring radio PM for the radio LAG.

Configuring parameters that normally cannot be configured from the NFM-P results in a deployment error. The NSP may permit you to choose configuration options that are not supported. This affects the following circumstances:

• When ports are part of a LAG, configuring peak and average PM settings

• When unequipped channel 1B on a UBT-T/XP is selected, configuring TX Mute ON/OFF.

• When a radio LAG contains only UBT-T, configuring peak and average PM settings.

Deleting a deployment from the NSP as a workaround can help when a deployment error occurs, ensure that the Network and NSP option is used.