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. You can perform tasks on multiple devices using large-scale Operations, and configure devices and services using Intents. Management tasks you can accomplish using the NSP include the following.

Equipment monitoring:

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

• 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 NSP data collection see the NSP Data Collection and Analysis Guide. Statistics collection for Wavence nodes must be configured in the NFM-P.

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

Configuration:

• Perform software upgrades using NSP operations. See the NSP Device Management Guide.

• Perform backup and restore actions using NSP operations. See Wavence backup and restore using NSP Operations.

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

• Change the WebCT password on Wavence nodes using an NSP operation. See To change the WebCT password on one or more Wavence nodes using an NSP operation.

Troubleshooting:

• 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

• Retrieve I&C, RSL, and log files using NSP operations. See To retrieve RSL files, I&C files, or log files stored by the Wavence using the NSP.

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.

Configuring Wavence operation default wait times

Optionally, you can create an environment file to change the wait time defaults for some operations that apply to Wavence devices. For more information about working with environments, see the Workflows tutorial on the Network Developer Portal. The environment file must be named WaitTimeEnv. The following table describes the variables you can define in the file, and the operations they affect.

Workflow	Variable	Definition
Software Upgrade	SU_waitTimeToRetrieveResult	The amount of time, in seconds, to wait for a response before retrying.
	SU_numOfRetries	The number of times to retry getting a response from the NE.
Backup and Restore	backup_waitTimeToRetrieveResult	The amount of time, in seconds, to wait for a response before retrying.
	backup_numOfRetries	The number of times to retry getting a response from the NE.
Bulk password update	npm_waitTimeToRetrieveResult	The amount of time, in seconds, to wait for a response before retrying.
	npm_numOfRetries	The number of times to retry getting a response from the NE.
File Retrieval	fileRetrieval_waitTimeToRetrieveResult	The amount of time, in seconds, to wait for a response before retrying.
	fileRetrieval_numOfRetries	The number of times to retry getting a response from the NE.

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.

Misalignments only appear for attributes and objects configured in the intent. When you make a configuration change that creates new objects or attributes, misalignments are only shown for the changes to objects originally configured by the intent. For example, if you use WebCT to change the Radio QoS classification of a node from Disabled to Diffserv, new attributes and objects become available for configuration, but only the QoS classification attribute displays as misaligned in the NSP.

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.

The NSP provides intent types for configuring Wavence devices, contained in the nsp-mpr-icm-intent-types artifact package. If this package is not installed, you can obtain it from the Nokia Support Portal or your Nokia support representative.

Device configuration intents

The following table lists supported device configuration tasks and the related intents to use in the NSP. For example, if you need to perform ethernet port configuration, you would import the icm-wavence-ethernet-port-configuration intent. For information on how to use intent-based device configuration, see the NSP Network Automation Guide. For detailed information about each intent, see the NSP Device Configuration Intent Type Catalog.

Task	Intent	Notes
Network element configuration	icm-wavence-network-element-config	Use the Bulk Configurations template to configure common parameters on multiple NEs, and the Default template to configure specific parameters for a single NE.
Ethernet port configuration	icm-wavence-ethernet-port-configuration	Use the MSS-Based template to configure MSS nodes, and the Pizzabox-UBT-SA-Based template to configure single-shelf (MSS-E/HE/XE or UBT-NIM) and UBT-SA nodes.
L3 system interface configuration	icm-wavence-l3-config-system-interface	—
L3 network interface configuration	icm-wavence-l3-config-network-interface	—
TDM port configuration	icm-wavence-tdm-port-specifics	—
Port timing synchronization configuration	icm-wavence-port-timing-config	—
1588 PTP configuration	icm-wavence-1588-ptp	—
Shelf timing synchronization configuration	icm-wavence-time-synchronization	—
Loopback radio configuration	icm-wavence-radio-port-specifics	—
Radio queue mapping configuration	icm-wavence-radio-queue-map	—
Radio QoS configuration	icm-wavence-radio-qos	Misalignments only appear for objects and attributes configured in the intent. See Intent-based radio parameter configuration considerations.
Ethernet ring element configuration	icm-wavence-ring-element	—
Ethernet radio ring configuration	icm-wavence-radio-ring	—

Service configuration intents

The following table lists intents used in service configuration, such as backhaul services and tunnel configuration. For information on how to use intent-based device configuration, see the NSP Network Automation Guide.

Task	Intent	Notes
Service tunnel deployment	tunnel	When you create a tunnel template using the intent, select Wavence in the Config Form parameter.
Microwave service backhaul configuration	wavencebackhaul	See Microwave backhaul service creation using NSP Intent-Based Service Fulfillment

Policy distribution intents

The following table lists intents used in policy configuration and distribution, for use with NSP operations such as bulk password changes. The role of each intent is described in the associated procedure.

Task	Intents	Notes
Bulk WebCT password change	icm-wavence-node-password-policy-management icm-wavence-node-password-policy-assignment	See To change the WebCT password on one or more Wavence nodes using an NSP operation
Backup and restore	icm-wavence-backup-restore-policy icm-wavence-backup-restore-policy-assignment	See Wavence backup and restore using NSP Operations
File retrieval (RSL, I&C, or log files)	icm-wavence-file-retrieval-policy icm-wavence-fileretrieval-policy-assignment	See To retrieve RSL files, I&C files, or log files stored by the Wavence using the NSP
Software upgrade	icm-wavence-software-upgrade-policy icm-wavence-software-upgrade-policyassignment	See the NSP Device Management Guide and the NSP Device Configuration Intent Type Catalog.