Workflow to manage Wavence devices

Wavence workflow sequence

The following workflow describes the high-level tasks required to commission and discover Wavence devices, configure and manage the device objects, and configure and manage the policies and services associated with the devices.

Process
 

Review the “Workflow to manage network objects” in the NSP NFM-P Classic Management User Guide before you use this workflow. The steps in this workflow are common to all NFM-P-managed devices.


Commission Wavence devices for NFM-P management; see Chapter 2, Wavence device commissioning and management.


Use NFM-P to discover Wavence devices; see the “Discovering devices using the NFM-P” chapter of the NSP NFM-P Classic Management User Guide.


View, manage, and configure Wavence device network objects as required; see the “Working with network objects using the NFM-P” chapter of the NSP NFM-P Classic Management User Guide.


Modify Wavence device shelf objects; see Chapter 8, Wavence shelf and card object configuration. You can only configure cards using a Wavence element manager. See the Wavence documentation for more information.


Modify ports on Wavence devices, as required; see Chapter 9, Wavence port object configuration. You can only configure ports using a Wavence element manager. See the Wavence documentation for more information.


View, manage, and configure Wavence device LAG objects; see Chapter 10, Wavence LAG object configuration.


As required, perform bulk configuration changes on Wavence devices to change the same configuration on multiple objects at the same time; see the “Bulk operations” chapter of the NSP NFM-P Classic Management User Guide for general guidelines. For example, configure a bulk change by choosing Wavence→System Settings - (mpr.MprNeProperties) in the Object Type drop-down menu to specify the bridge type for all Wavence devices. See the XML API Reference for information about all bulk change XML classes associated with the Wavence objects.


Create NFM-P policies that define the conditions for NFM-P management functions on Wavence devices.

  1. Before creating policies for Wavence devices, review the “Policies overview” chapter of the NSP NFM-P Classic Management User Guide for information about NFM-P policy management and the workflow to create and distribute policies.

  2. Create QoS device-specific policies as required for Wavence devices; see Chapter 13, QoS policies.


10 

Before configuring backhaul, or composite services and related functions on Wavence devices, perform the following as required:

  1. Review the “Service management and QoS” chapter of the NSP NFM-P Classic Management User Guide for information about configuring services on Wavence devices using the NFM-P.

  2. Review the “Customer configuration and service management” chapter of the NSP NFM-P Classic Management User Guide for information about how to create and manage customers. As required, create customer profiles.

  3. Review the Wavence service management and service tunnels chapter for specific information on supported service types; see Chapter 14, Wavence service tunnels.

  4. Configure service tunnels to carry service traffic on Wavence devices; see Chapter 14, Wavence service tunnels.


11 

Configure backhaul services for subscribers connected to Wavence devices; see Chapter 15, Wavence microwave backhaul service management.


12 

Configure composite services to connect the types of services for subscribers connected to Wavence devices; see Chapter 16, Wavence composite service.


Fault management
 
13 

Monitor and acknowledge incoming Wavence-specific alarms to check the type and characteristics of the alarms, and to resolve the network problems or physical equipment failures identified by the alarms; see the “Alarm management overview” chapter of the NSP NFM-P Classic Management User Guide for more information.

In addition:

  • Click on the Abnormal Conditions tab of the Network Element (Edit) form to check for the abnormal conditions on the Wavence, such as loopback or TxMute conditions, to determine the appropriate corrective action. In previous releases of NFM-P, each abnormal condition on the Wavence was reported as an individual alarm on the Faults tab. Abnormal conditions are now reported as a single alarm.

  • Refresh the Abnormal Conditions tab to ensure the latest content is displayed.

  • Clear the abnormal condition alarm after all the individual abnormal conditions are cleared.

  • Objects that can have alarms raised against them contain a Faults tab, on their properties form. When you click on the Faults tab a list is displayed of the alarms raised against the specific object. You can launch the Fault Management application from the Object Alarms tab. To launch the Fault Management application, right-click on an alarm and choose View Impact. A web browser opens to the Alarm Impacts window of the Fault Management application. See the “Alarm management overview” chapter in the NSP NFM-P Classic Management User Guide for more information.


14 

Perform specific Wavence device maintenance functions as required:

  • configure on-demand or scheduled NE configuration backup and restore device configurations

  • perform a Wavence device on-demand software upgrade; see Chapter 4, Wavence software upgrade

  • monitor deployment of configuration changes to Wavence devices

  • configure the OLC state on a Wavence device object to specify whether the object is in maintenance or in-service mode to filter alarms in the alarm window

  • perform daily, weekly, monthly, and supplemental routine maintenance to maintain hardware and system integrity and efficiencies of Wavence devices

See the NSP System Administrator Guide for more information.


15 

Collect NFM-P and NE statistics to monitor NFM-P and Wavence devices, network and service performance, compile equipment usage and billing data, and ensure SLA compliance; see the NSP NFM-P Statistics Management Guide.