Wavence device support

Wavence radio family

The Nokia Wavence is a microwave digital radio family that supports PDH and Ethernet to migrate from TDM to IP. The Wavence provides a generic, modular IP platform for multiple network applications such as 2G, 3G, HSDPA, and WiMAX to accommodate broadband services to Metro Ethernet areas. This solution improves packet aggregation, increases bandwidth, and optimizes Ethernet connectivity.

The Wavence supports low, medium, and high capacity applications using ANSI and ETSI data rates, frequencies, channel plans, and tributary interfaces and has both indoor and outdoor applications.

The NE icon in the NFM-P GUI shows the chassis name Wavence, for example, Wavence MSS-4. NEs from earlier releases show the former name of the Wavence NE, 9500 MPR.

Note: To determine which versions of the Wavence NEs and variants are supported by NFM-P, see the NSP NFM-P and 5620 SAM Network Element Compatibility Guide for information.

Note: Only discovery of port segregation rules is supported.

Wavence SM

The Wavence SM is the split-mount application of a shelf unit and an indoor or outdoor radio. The Wavence SM provides fixed or mobile Ethernet site backhauling and supports converged MPLS metro networks. As a native NE, the Wavence SM appears on NFM-P maps and equipment managers. Some features require a cross-launch of the NEtO external element manager or the WebCT browser-based element manager. See  Wavence management support for more information.

Wavence SA

The Wavence SA is the standalone, outdoor application of the outdoor radio unit without a shelf unit. As a native NE, the Wavence SA appears on NFM-P maps and equipment managers. All standard SNMP-based features, including discovery and alarms, are supported with the same naming as the rest of the Wavence family. Some features require a cross-launch of the NEtO external element manager. See  Wavence management support for more information.

Note: From an NFM-P perspective, the Wavence SA (standalone), and Wavence MSS-1c variants belong to same product family; both variants display on the NFM-P GUI as the Wavence SA. However, for Wavence software upgrades, the Label column allows you to distinguish between the Wavence SA and Wavence MSS-1c variant types.

Wavence MSS-1c

The Wavence Microwave Service Switch-1c (MSS-1c) is an ultra-compact indoor unit (1/2 rack size) offering 10 E1 and 4 user interfaces. The Wavence MSS-1c provides user port interface, cross-connection, and switching management. The cross-connection matrix implements all the cross-connections between the User ports (four Ethernet ports and E1/T1 streams) and the radio port. The matrix is a standard Ethernet switch, based on VLAN, assigned by the MCT.

The NE backup and restore functionality for this node type is only supported for Releases 5.2, 6.0, 6.1, and 7.0 or later. A new backup and restore policy has been added to support this device type. You can access the policy from the Administration→NE Maintenance→Backup/Restore menu. Click on the Backup/Restore Policy tab, select the MPR-SA Default Policy and click Properties.

Note: This policy type requires the FTP/SFTP parameters to be configured.

The following functionality is supported for the Wavence MSS-1c using NFM-P:

Wavence MSS-O

The Wavence Microwave Services Switch-Outdoor (MSS-O) is a compact, full outdoor microwave networking device, for boosting link capacity and reliability for small cell backhaul networks. The device provides both optical and electrical Ethernet interfaces and can be installed indoors or outdoors.

You can configure the following on a Wavence MSS-O using NFM-P:

The LAG size for a Wavence MSS-O is restricted to the following:

UBT-SA

The Wavence Ultra Broadband Transceiver-SA (UBT-SA) is a standalone outdoor radio unit. Adaptive modulation is supported. The UBT microprocessor manages transmit and receive frequencies, transmit power, alarms, and performance monitoring. See the Wavence documentation for information about channel spacing, shifter and frequency management, and modem profiles.

As a native NE, the UBT-SA appears on NFM-P maps and equipment managers. Some features require a cross-launch of the WebCT browser-based element manager. See  Wavence management support for more information.

The UBT-SA is commissioned in the Wavence element manager. The NFM-P will discover the UBT-SA and display the variant in the equipment tree. UBT-SA discovery is performed as a part of the Connect Service operation; see Connect service. When a UBT-SA is configured as a pass-thru in a Y-cable or ring topology, the NFM-P discovers all the UBT-SA nodes involved, regardless of the configured service on the Wavence element manager.

The following variants are supported:

The following functionality is supported for the UBT-SA using NFM-P:

The following functionality is supported for the UBT-SA using NFM-P with the Wavence, Release 20A or later:

The following functionality is supported for the UBT-SA using NFM-P with Wavence, Release 22 or later:

1+1 HSB FP/SD protection is supported for UBT-S and UBT-I standalone variants using Wavence 23A or later. Configuring protection is performed using WebCT, see the Wavence documentation for more information. Protection information is displayed in the NFM-P on the Protection tab of the Equipment view for the UBT-SA. One node is configured as Main and the other as Spare; these configurations do not change, instead the Protection switching status (EPS/TPS and RPS) will change between Active and Standby to indicate which node is currently active, mirroring the values displayed in the Wavence Element Manager. Statistics collection can be configured individually on each member of a protection link, as supported by the node; the following considerations apply for statistics collection in a protection configuration:

Note: Some node parameters are only updated by performing a manual node resync and not automatically when the values change. For the UBT-SA these parameters include:

Wavence MSS-E/HE

The Wavence Microwave Service Switch-E/HE (MSS-E/HE) is a compact indoor unit. This is an extension of MSS1v2. All standard SNMP-based features, including discovery and alarms, are supported with the same naming as the rest of the Wavence family. As a native NE, the MSS-E/HE appears on NFM-P maps and equipment managers. Some features require a cross-launch of the WebCT browser-based element manager. See  Wavence management support for more information.

The NE backup and restore functionality for this node type is only supported using the NFM-P, Release 20.11 or later. A mediation policy with valid credentials must be configured for the node in order to support Backup/Restore operations. Refer to the node documentation for the credentials that are required.

The following functionality is supported for the Wavence MSS-E/HE using NFM-P:

Wavence MSS-XE

The Wavence Microwave Service Switch-XE (MSS-XE) is an indoor split-mount solution. All standard SNMP-based features, including discovery and alarms, are supported with the same naming as the rest of the Wavence family. As a native NE, the MSS-XE appears on NFM-P maps and equipment managers. Some features require a cross-launch of the WebCT browser-based element manager. See  Wavence management support for more information.

The NE backup and restore functionality for this node type is only supported using the NFM-P, Release 22.9 or later. A mediation policy with valid credentials must be configured for the node in order to support Backup/Restore operations. Refer to the node documentation for the credentials that are required.

The following functionality is supported for the MSS-XE using NFM-P:

UBT-NIM

The Wavence Ultra Broadband Transceiver-Network Integrated Module (UBT-NIM) is a hardware plugin to be attached to UBT-m/-T/-S in order to provide multiple ethernet interfaces to UBT. The ethernet ports on NIM unit are managed as ethernet user ports or as connection ports to an UBT.

All standard SNMP-based features, including discovery and alarms, are supported with the same naming as the rest of the Wavence family. As a native NE, the UBT-NIM appears on NFM-P maps and equipment managers. Some features require a cross-launch of the WebCT browser-based element manager. See  Wavence management support for more information.

The NE backup and restore functionality for this node type is only supported from NFM-P from release, 21.6 onwards. Refer to node document for the credentials to be supplied. The UBT-NIM is commissioned in the Wavence element manager. After configuration in Wavence is complete, the NFM-P discovers the UBT-NIM and displays it in the equipment tree.

The following functionality is supported for the UBT-NIM using NFM-P:

MPT device support using GNE drivers

GNE drivers are optional software modules corresponding to specific Wavence devices. They extend the management of selected Wavence devices beyond the basic GNE management that would otherwise be available to them.

The GNE drivers are installed with the NFM-P software. It is no longer necessary to obtain these drivers separately from the NSP software delivery site. See “Device management using drivers” in the NSP NFM-P Classic Management User Guide for more information. Driver compatibility information is located in the NSP NFM-P and 5620 SAM Network Element Compatibility Guide.

Drivers are provided for extended management of the following devices in the Wavence product family:

Note: The 9500 MPT-BWA device is a hardware variant of the MPT-SUB6. The NFM-P uses the MPT-SUB6 driver to manage the MPT-BWA.

9500 MPT-GM

The MPTGM driver extends the management capabilities of the NFM-P for MPT-GM devices in the following applicable areas.

Table 1-1: MPTGM driver capabilities

Configuration management

Radio link inventory – Operators can view all radio links terminating on this device by drilling down from the network topology map or network equipment tree representations of the MPT-GM.

Note: To create a physical link, select the endpoints as type “Port”.

Additionally, radio links associated with the MPT-GM are included in the inventory list accessed through the Equipment Manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Radio link (Network) from the object type drop-down).

Radio link inventory information is also available to the XML API through the installation of the driver, under the following package and class netw.RadioPhysicalLink.

Radio link discovery – The NFM-P extends the link auto-discovery to radio links interconnecting MPT-GM devices.

Radio port parameters – The driver extends the NFM-P management of the MPT-GM to include its radio port interfaces. With the installation of the driver, a "Radio" tab is added to the Generic NE interface form, allowing NFM-P operators to view the following generic radio port parameters of the device:

  • ATPC Enabling

  • ATPC Max Tx Power

  • ATPC Low Power Threshold – The value displayed for this parameter is the minimum value, not a configurable threshold.

  • ATPC High Power Threshold

  • Mode

  • Current Modulation

  • Actual Speed (kbps)

  • MTU

  • Manual Local Tx Mute

  • Tx Frequency

  • MPT Shifter Value

  • Channel Spacing

  • Received Power Level

  • Transmitted Power Level

  • Radio PM

  • Normalized MSE (dB)

  • Available Bandwidth (Mbps)

These parameters are also available to the XML API under the following package and class radioequipment.RadioPortSpecifics.

Radio port inventory parameters – The following radio port inventory parameters are displayed on the Inventory tab for the radio ports:

  • Company ID

  • Mnemonic

  • Part No

  • Serial No

  • Port ID

  • Software Part No

These parameters are also available to the XML API under the following package and class radioequipment.RadioEquipmentInventory.

Longitude and latitude – The NFM-P displays the location of the MPT-GM with latitude and longitude. The coordinates are displayed as additional parameters on the General tab of the Properties form. The longitude and latitude parameters are configurable.

Generic NE Profile automation – The Generic NE Profile for the MPT-GM is automatically created when the MPTGM driver is installed.

Alarm catalog integration – The MPT-GM alarm catalog is automatically populated during driver installation. Operators can edit the alarm catalog to customize alarm characteristics.

Note – Since "info" traps are not present in the automatically generated alarm catalog, the NFM-P may throw an error in the log viewer. There is no impact on the functionality of alarms reporting.

NE software version display – The NE software version is displayed on the General tab of the NE Properties form.

Port labeling – The Name parameter in the MPT-GM port list is customized to facilitate the mapping of the interface index with the interface type.

TMN Inband management – The NFM-P displays the VLAN ID parameter identifying the TMN Inband management traffic/signal. On the Polling tab, click on the TMN Details sub-tab, and double-click on the row. The TMN Inband setting is read-only.

MAC address – The NFM-P displays the MAC Address of the node on the General tab of the NE form. The MAC Address is also accessed through the Equipment manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Network Element (Network) from the object type drop-down).

Bulk PM operations – Bulk PM operations are supported. Choose Tools→Bulk Operations from the NFM-P main menu to create a bulk change. You can specify filter options while creating a bulk change. During a bulk execution, if there are exceptions encountered, all following bulk executions are cancelled. See the "Bulk Operations" chapter in the NSP NFM-P Classic Management User Guide for more information.

PM enable/disable – You can enable/disable PM at the radio port level.

Port parameters – The NFM-P displays the following read-only parameters on the General tab of each port:

  • Mode

  • Encapsulation Type

  • Speed

Interface name description – The MPTGM port descriptions are aligned to the WebLCT as follows:

Port Name

Description

1/1/1

Mngt

1/1/2

Aux

1/1/6

LAN-2

1/1/9

Radio

1/1/10

LAN-1

Service management

When driver-managed GNE devices are collocated with the 9500 MPR, the NFM-P supports creation of the microwave backhaul service spanning across MPRs and OEMs. The NFM-P recognizes OEM as a site to add to the microwave backhaul service. The NFM-P also recognizes the Ethernet and radio ports on OEM as adjacencies to add to OEM sites. However, the NFM-P does not support deployment of these services to OEM devices. Deployment to OEM devices must be done from the respective EMS. Consequently, discovery of this service does not discover OEM sites. Therefore, OEM sites can be either manually added for the MPTGM/MPTGS/MPTSUB6, or populated using the Complete Ring feature for the MPTGM.

Service assurance

Performance management – The driver extends NFM-P performance management to the MPT-GM device so that statistics related to the GNE can be viewed through the NFM-P GUI. Statistics are also available to the XML API; see the NSP NFM-P Statistics Management Guide.

Alarm resynchronization – The NFM-P performs periodic polling of trap sequence numbers and detects gaps, if present. Upon NE alarm loss detection, the NFM-P performs full NE alarm resynchronization.

Alarm reporting – The NFM-P supports the reporting of all alarms present in the automatically generated alarm catalog.

Radio link fault management – The NFM-P tracks the radio link down scenario. When a radio link interconnects two MPT-GM devices, the NFM-P manages the operational state at the node and processes any alarms affecting the radio link extremities. The NFM-P changes the operational state on the General tab of the radio interface based on the link down alarm.

Note – The operational state on the Radio tab does not change based on link status. When the link is operationally down, the link shows red. When the link is operationally up, the link shows green.

Physical link fault management – The NFM-P tracks the physical link down scenario when a physical link is interconnecting an MPT-GM and an MSS-8/4/1/O. A link down alarm is raised when the LOS (Loss Of Signal) alarm at the MPT-GM port is notified by the node from the NFM-P. The link (physical or radio) is displayed as alarmed in the topology view (red line) and the link down alarm is reported in the alarm list.

Alarm correlation – The NFM-P supports alarm correlation for the Fault Management application for the following fault scenario:

  • radio link down

  • physical link down

Both “LinkDown” alarms are correlated to the “adjacencyDown” alarm at the service level.

Device life cycle management

Backup – The driver extends the NFM-P management of the MPT-GM device to include the backup functionality. The driver receives the necessary information regarding the FTP/SFTP server from the NFM-P backup/restore policy and initiates a backup execution on the target device. The driver monitors the backup execution and provides the necessary information to the policy, such as success/failure, date of backup, etc. See the "NE backup and restore" chapter in the NSP NFM-P Classic Management User Guide for more information.

Software upgrade – The NFM-P supports software upgrade operations for the MPT-GM. An MPT-GM software package is provided by the vendor with a single zip file. The zip file name must not be changed. A folder containing this zip file must be selected on an import.

The software upgrade consists of 2 steps:

  • download – Transfers the new software to the offline software bank.

  • activate – Reboots the system and switches the active status between the banks so the downloaded software becomes active.

The Software tab on the NE form displays the software version and status of each bank.

Note – When upgrading an operational link of an inband managed node, upgrade the remote system first and then the local system. Activate the software at both ends after verifying that the link performs as expected. Always upgrade both ends of the link.

See the “NE software upgrades” chapter in the NSP NFM-P Classic Management User Guide for more information.

Workflow to discover and manage the MPT-GM

This workflow describes how to discover and manage the MPT-GM in the NFM-P after driver installation.

Consult the NSP NFM-P Classic Management User Guide chapter "Device commissioning and management" for full procedural details.

Create mediation policies and configure a discovery rule

  1. Use the NFM-P to create an SNMPv1 mediation policy that specifies “admin” as the Read Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  2. Use the NFM-P to create an SNMPv1 mediation policy that specifies “NMS5UX” as the Write/Trap Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  3. Use the NFM-P to configure a discovery rule for the MPT-GM that specifies the following mediation policies; see the NSP NFM-P Classic Management User Guide for information about creating discovery rules:

    • Read Access Mediation Policy – mediation policy created in step 1.

    • Write Access Mediation Policy and Trap Access Mediation Policy - mediation policy created in step 2.

Perform configuration management tasks using the device EMS

  1. Right-click on the MPT-GM icon on the NFM-P topology map and choose Open URL.

  2. Enter your user name and password. The device EMS opens to allow configuration.

  3. Choose Main→Alarm Severity Config→SETS and double-click on the following alarms to change the Severity setting from Warning to Status:

    • timingGeneratorFreeRunningStatus

    • timingGeneratorHoldoverStatus

View statistics

  1. Click on the Statistics tab of the MPT-GM interface properties form. The MPT-GM Statistics form opens.

  2. View statistics as required.

    The availability of historical data requires the activation of Performance Monitoring.

Note: It is recommended that you schedule historical data statistics only, and collect current data statistics on demand. For example, History Data Stats - 15 min returns the same information as Current Data Stats collected for the same 15 minute interval, therefore, it is redundant to schedule Current Data Stats. Scheduling Current Data Stats may result in an error message. Scheduling Interface Additional Stats (Generic NE) is not supported and may result in stopping the collection of other statistics.

Note: For the NFM-P to successfully display the supported History Data Stats, it is expected that the node has collected at least 19 entries of 15 minute statistics. For a newly deployed node, after statistics collection is initiated, you must wait for 5 h before you can view the History Data Stats on the NFM-P.

Note: The plotting of statistics is supported for Interface Stats (Generic NE).

The following counters are supported on Radio interface 9.

Interface Type

Statistic Type

Radio (index 9)

Adaptive Modulation Current Data Stats - 15 min

Adaptive Modulation Current Data Stats – 24 Hr

Adaptive Modulation History Data Stats - 15 min

Adaptive Modulation History Data Stats – 24 H

Hop Current Data Stats – 15 min

Hop Current Data Stats – 24 Hr

Hop History Data Stats - 15 min

Hop History Data Stats - 24 Hr

RSL Hop Current Data stats – 15 min

RSL Hop Current Data stats – 24 Hr

RSL Hop History Data Stats - 15 min

RSL Hop History Data Stats - 24 Hr

TSL Hop Current Data Stats – 15 min

TSL Hop Current Data Stats – 24 Hr

TSL Hop History Data Stats - 15 min

TSL Hop History Data Stats - 24 Hr

Note – On the Ethernet interfaces with index 9 (Radio), 10 (LAN 1), and 6 (LAN 2), the Interface Stats (Generic NE) are also applicable.

Note – On the Radio interfaces, real-time and historical plots are not supported.

Note – On the Ethernet interfaces, real-time and historical plots are supported only for interface statistics.

9500 MPT-GS

The MPTGS driver extends the management capabilities of the NFM-P for MPT-GS devices in the following applicable areas.

Table 1-2: MPTGS driver capabilities

Configuration management

Radio link inventory – Operators can view all radio links terminating on this device by drilling down from the network topology map or network Equipment Tree representations of the MPT-GS device.

Note –To create a physical link, select the endpoints as type “Port”.

Additionally, radio links associated with the MPT-GS device are now included in the inventory list accessed through the Equipment Manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Radio link (Network) from the object type drop-down).

Radio link inventory information is also available to the XML API through the installation of the driver, under the following package and class netw.RadioPhysicalLink.

Radio link discovery – The NFM-P extends the link auto-discovery to radio links interconnecting MPT-GS nodes.

Radio port parameters – The driver extends the NFM-P management of the MPT-GS device to include its radio port interfaces. With the installation of the driver, a "Radio" tab is added to the Generic NE Interface form, allowing NFM-P operators to view the following generic radio port parameters of the device:

  • Channel Width (MHz)

  • TX Frequency (MHz)

  • Role

  • Mode

  • Modulation

  • Actual Speed (kbps)

  • MTU

  • Sub Channels

  • Repetitions

  • FEC Rate

  • Rx Link ID

  • Tx Link ID

  • Rx State

  • Tx State

  • RSSI (dBm)

  • CINR (dB)

  • Oper. Status

  • RF Temperature

  • Tx Mute

  • Tx Mute Timeout (sec)

  • Tx Power (dBm)

  • Encryption Status

These parameters are also available to the XML API under the following package and class radioequipment.RadioPortSpecifics.

Radio port inventory parameters – The following radio port inventory parameters are displayed on the Inventory tab for the radio ports:

  • Company ID

  • Mnemonic

  • Port ID

  • Software Part No

  • Serial No

These parameters are also available to the XML API under the following package and class radioequipment.RadioEquipmentInventory.

Ethernet (user) port parameters – The Actual Speed (kbps) parameter is displayed on the General tab for the Ethernet ports.

Generic NE Profile automation – The Generic NE Profile for the MPT-GS is automatically created when the MPTGS driver is installed.

Alarm catalog integration – The MPT-GS alarm catalog is automatically populated during driver installation. Operators can edit the alarm catalog to customize alarm characteristics.

NE software version display – The NE software version is displayed on the General tab of the NE Properties form.

TMN Inband management – The NFM-P displays the VLAN ID parameter identifying the TMN Inband management traffic/signal. On the Polling tab, click on the TMN Details sub-tab, and double-click on the row. The TMN Inband setting is read-only.

MAC address – The NFM-P displays the MAC Address of the node on the General tab of the Network Element form. The MAC Address is also accessed through the Equipment manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Network Element (Network) from the object type drop-down).

NTP management – The NFM-P reports NTP-related parameters. NTP enabling and disabling and server configuration is supported through the Alternate Element Manager. Server configuration is also supported using the NFM-P Create option.

Radio encryption status – The NFM-P reports the Encryption Status (enable/disable) at the radio interface. This parameter is read-only.

Sensor measurements – The NFM-P reports the Equipment Input Voltage and Temperature (Celsius) parameters on the Statistics form.

SNMPv3 support – The NFM-P supports SNMPv3 management of the node.

Port parameters– The NFM-P displays the following read-only parameters on the General tab of each port:

  • Mode

  • Encapsulation Type – for HBS

    Note – This parameter is not supported for HSU.

  • Speed

Service management

When driver-managed GNE devices are collocated with the 9500 MPR, the NFM-P supports creation of the microwave backhaul service spanning across MPRs and OEMs. The NFM-P recognizes OEM as a site to add to the microwave backhaul service. The NFM-P also recognizes the Ethernet and radio ports on OEM as adjacencies to add to OEM sites. However, the NFM-P does not support deployment of these services to OEM devices. Deployment to OEM devices must be done from the respective EMS. Consequently, discovery of this service does not discover OEM sites. Therefore, OEM sites can be either manually added for the MPTGM/MPTGS/MPTSUB6, or populated using the Complete Ring feature for the MPTGM.

Service assurance

Performance management – The driver extends NFM-P performance management to the MPT-GS device so that statistics related to the GNE can be viewed through the NFM-P GUI. Statistics are also available to the XML API; see the NSP NFM-P Statistics Management Guide.

Alarm resynchronization – The NFM-P performs periodic polling of trap sequence numbers and detects gaps, if present. Upon NE alarm loss detection, the NFM-P performs full NE alarm resynchronization.

Alarm reporting – The NFM-P supports the reporting of all alarms present in the automatically generated alarm catalog.

Radio link fault management – The NFM-P tracks the radio link down scenario. When a radio link interconnects two MPT-GS devices, the NFM-P manages the operational state at the node and processes any alarms affecting the radio link extremities. The radio link color is updated depending on the radio link status. The color is red when the link is down and green when the link is up, according to the radio interface operational status.

Alarm correlation – The NFM-P supports alarm correlation for the Fault Management application for the following fault scenario:

  • radio link down

  • physical link down

Both “LinkDown” alarms are correlated to the “adjacencyDown” alarm at the service level.

Device life cycle management

Backup – The driver extends the NFM-P management of the MPT-GS device to include the backup functionality. The driver receives the necessary information regarding the FTP/SFTP server from the NFM-P backup/restore policy and initiates a backup execution on the target device. The driver monitors the backup execution and provides the necessary information to the policy, such as success/failure, date of backup, etc. See the "NE backup and restore" chapter in the NSP NFM-P Classic Management User Guide for more information.

Software upgrade – The NFM-P supports software upgrade operations for the MPT-GS. An MPT-GS software package is provided by the vendor with a single file, e.g. siklu-uiimage-6.7.2-15594. The file name must strictly follow the format: siklu-uimage-<major>.<minor>.<sub>-<build #>

The software upgrade consists of 3 steps:

  • download – Transfers the new software to the offline or “not running” software bank.

  • activate – Reboots the system and switches the active status between the banks. The downloaded software status is set to "Running Wait Accept", whereas the previously active software is set to "Not Running" or offline status.

  • accept – The new software is accepted, changing its state from "Running Wait Accept" to "Running”.

The NFM-P performs reachability checks on GNEs every 10 min by default. Therefore the Accept Timeout parameter default is set to 20 min to allow the NFM-P to detect a node reboot triggered by an activate operation. If the timer for reachability checks for GNEs is changed, the Accept Timeout parameter must be adjusted accordingly or the node auto-reverts before the NFM-P sends the accept command, causing the accept to fail. If the accept time-out expires and an auto-revert occurs, it is recommended to resync the node to see the currently active software version on the NE.

The Software tab on the NE form displays the software version and status of each bank.

Note – When upgrading an operational link of an in-band managed node, upgrade the remote system first and then the local system. Accept the software at both ends after verifying that the link performs as expected. Always upgrade both ends of the link.

See the “NE software upgrades” chapter in the NSP NFM-P Classic Management User Guide for more information.

Note – Between activate and accept actions, it is recommended that you perform the following acceptance tests to ensure the radio link is restored correctly and the new software functions properly.

RF Link verification - verifies the RF link status as before the upgrade.

  • Link is up

  • RSSI values are as prior to the upgrade

  • CINR values are as prior to the upgrade

  • ODU reaches the modulation prior to the upgrade

RF Link test - verifies error-free operation of the radio link by checking the RF statistics counters for lost/errored packets.

  • No errors/loss on the RF statistics counters

Workflow to discover and manage the MPT-GS

This workflow describes how to discover and manage the MPT-GS in the NFM-P after driver installation.

Consult the NSP NFM-P Classic Management User Guide chapter "Device commissioning and management" for full procedural details.

Create mediation policies and configure a discovery rule

  1. Use the NFM-P to create an SNMPv2 mediation policy that specifies “public” as the Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  2. Use the NFM-P to create an SNMPv3 mediation policy with V3 user and credentials as configured on the node. Authentication and privacy algorithms that are supported are MD5 and DES respectively.

  3. Use the NFM-P to configure a discovery rule for the MPT-GS that specifies the following mediation policies; see the NSP NFM-P Classic Management User Guide for information about creating discovery rules:

    • Read Access Mediation Policy and Write Access Mediation Policy– default mediation policy

      Note – For NE backups and software downloads, the CLI user and password must be set to valid node credentials for the default (or “private” policy).

    • Trap Access Mediation Policy - mediation policy created in step 1

Perform configuration management tasks using the device EMS

  1. Right-click on the MPT-GS icon on the NFM-P topology map and choose Open URL.

  2. Enter your user name and password. The device EMS opens to allow configuration.

View statistics

  1. Click on the Statistics tab of the MPT-GS interface properties form. The MPT-GS Statistics form opens.

  2. View statistics as required.

    The availability of historical data requires the activation of Performance Monitoring.

Note: It is recommended that you schedule historical data statistics only, and collect current data statistics on demand. For example, History Data Stats - 15 min returns the same information as Current Data Stats collected for the same 15 minute interval, therefore, it is redundant to schedule Current Data Stats. Scheduling Current Data Stats may result in an error message. Scheduling Interface Additional Stats (Generic NE) is not supported and may result in stopping the collection of other statistics.

Note: The plotting of statistics is supported for Interface Stats (Generic NE).

The following counters are supported.

Interface Type

Statistic Type

Supported Counters

Radio (index 2: ETH0)

Ethernet Aggregate Rx Stats

Total Received Correct Frames

Total Received Correct Octets

Total Received Severely Errored Frames

Rx Throughput (Mbps)

Rx Utilization Percentage (%)

Ethernet Aggregate Tx Stats

Total Transmitted Frames

Total Transmitted Octets

Aggregate Tx Throughput (Mbps)

Aggregate Tx Utilization Percentage (%)

RSL Hop Current Data Stats - 15 min

Average Level (dBm)

MPT Equipment Measurement

Temperature (Celsius)

Equipment Input Voltage

Ethernet

(index 3–6: ETH1 to ETH4)

Ethernet Aggregate Rx Stats

Total Discarded Frames

Total Received Correct Frames Broadcast

Total Received Correct Frames Multicast

Total Received Correct Frames Unicast

Total Received Correct Octets

Total Received Severely Errored Frames

Rx Throughput (Mbps)

Rx Utilization Percentage (%)

Ethernet Aggregate Tx Stats

Total Discarded Frames

Total Transmitted Frames Broadcast

Total Transmitted Frames Multicast

Total Transmitted Frames Unicast

Total Transmitted Octets

Aggregate Tx Throughput (Mbps)

Aggregate Tx Utilization Percentage (%)

Note – On the Ethernet interfaces with index 2 (ETH0) and 3-6 (ETH 1-ETH 4), the Interface Stats (Generic NE) are also applicable.

Note – On the Radio interfaces, real-time plots are not supported and historical plots are supported for all supported counters.

Note – On the Ethernet interfaces, real-time plots are supported only for interface statistics and historical plots are supported for all supported statistics.

9500 MPT-SUB6

The MPTSUB6 driver extends the management capabilities of the NFM-P for MPT-SUB6 devices in the following applicable areas.

Table 1-3: MPTSUB6 driver capabilities

Configuration management

Radio link inventory – Operators can view all radio links terminating on the device by drilling down from the network topology map or network equipment tree representations of the MPT-SUB6.

Note –To create a physical link, select the endpoints as type “Port”.

Additionally, radio links associated with the MPT-SUB6 device are now included in the inventory list accessed through the Equipment Manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Radio link (Network) from the object type drop-down).

Radio link inventory information is also available to the XML API through the installation of the driver, under the following package and class netw.RadioPhysicalLink.

Radio port parameters – The driver extends the NFM-P management of the MPT-SUB6 to include its radio port interfaces. With the installation of the driver, a "Radio" tab is added to the Generic NE Interface properties form, allowing NFM-P operators to view the following generic radio port parameters of the device:

  • Channel Bandwidth (KHz)

  • Operational Frequency (MHz)

  • Band

  • Sector ID

  • HSU Far-end ID

  • Current Tx Power (dBm)

  • Current Rx Power (dBm) — This is not applicable for HBS in Point-to-Multipoint configurations, i.e. HBS connected to multiple HSUs.

  • MTU - This is not supported for version 2.8.X.

  • Antenna Type

  • Available Bandwidth (Mbps)

  • Encryption Status

The following five parameters pertain to the radio link and differ according to the link that is present. The operator can create up to four separate radio links interconnecting the HBS and HSUs. Interfaces 101 – 104 are enabled as radio ports. The Radio panel is associated with each radio port so that operators can access the radio parameters by selecting any of the logical radio interfaces. These parameters are supported only on the Radio tab of HBS, not HSU.

  • RSL (dBm)

  • Down-link Throughput (Mbps)

  • Down-link Peak Throughput (Mbps)

  • Up-link Throughput (Mbps)

  • Up-link Peak Throughput (Mbps)

These parameters are also available to the XML API under the following package and class radioequipment.RadioPortSpecifics.

Radio port inventory parameters – The following radio port inventory parameters are displayed on the Inventory tab for the radio ports:

  • Company ID

  • Factory ID

  • Mnemonic

  • Part No

  • Serial No

  • Port ID

  • Software Part No

These parameters are also available to the XML API under the following package and class radioequipment.RadioEquipmentInventory.

Radio link discovery - The NFM-P extends link auto-discovery to radio links interconnecting HBS and HSUs. The HSU radio port with index 101 is connected to the HBS logical radio port matching the following criteria:

  • The remote HBS has the same sectorID as the selected HSU.

  • The HBS radio port index is equal to 101 + value (.1.3.6.1.4.1.4458.1000.4.1.3.0).

Longitude and latitude – The NFM-P displays the location of the MPT-SUB6 with latitude and longitude. The coordinates are displayed as additional parameters on the General tab of the Properties form. The longitude and latitude parameters are ready-only and are only displayed when the GPS state is synchronized. For all other states, the NFM-P displays an invalid value of 999.

Generic NE Profile automation – The Generic NE Profile for the MPT-SUB6 is automatically created when the MPTSUB6 driver is installed.

Alarm catalog integration – The MPT-SUB6 alarm catalog is automatically populated during driver installation. Operators can edit the alarm catalog to customize alarm characteristics.

NE software version display – The NE software version is displayed on the General tab of the NE Property form.

TMN Inband management – The NFM-P displays the VLAN ID parameter identifying the TMN Inband management traffic/signal. On the Polling tab, click on the TMN Details sub-tab, and double-click on the row. The TMN Inband setting is read-only.

MAC address – The NFM-P displays the MAC Address of the node on the General tab of the NE form. The MAC Address is also accessed through the Equipment manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Network Element (Network) from the object type drop-down).

NTP management – The NFM-P reports NTP-related parameters. NTP enabling and disabling and server configuration is supported through the Alternate Element Manager. Server configuration is also supported using the NFM-P Create option.

Radio encryption status – The NFM-P reports the Encryption Status (enable/disable) at the radio interface. This parameter is read-only.

Sensor measurements – The NFM-P reports the Power Consumption (Watts) and Temperature (Celsius) parameters on the Statistics form.

SNMPv3 support – The NFM-P supports SNMPv3 management of the node.

Port parameters – The NFM-P displays the following read-only parameters on the General tab of each port:

  • Mode

  • Encapsulation Type

    Note – The Encapsulation Type parameter is not supported by the NFM-P for HSU. Any displayed value should be ignored.

  • Speed

Service management

When driver-managed GNE devices are collocated with the 9500 MPR, the NFM-P supports creation of the microwave backhaul service spanning across MPRs and OEMs. The NFM-P recognizes OEM as a site to add to the microwave backhaul service. The NFM-P also recognizes the Ethernet and radio ports on OEM as adjacencies to add to OEM sites. However, the NFM-P does not support deployment of these services to OEM devices. Deployment to OEM devices must be done from the respective EMS. Consequently, discovery of this service does not discover OEM sites. Therefore, OEM sites can be either manually added for the MPTGS/MPTSUB6/MPTGM, or populated using the Complete Ring feature for the MPTGM.

Service assurance

Performance management – The driver extends NFM-P performance management to the MPT-SUB6 so that statistics related to the GNE can be viewed through the NFM-P GUI. Statistics are also available to the XML API; see the NSP NFM-P Statistics Management Guide.

Alarm resynchronization – Since traps do not have a sequence ID to detect trap gaps, the "auto resynch of alarm table" based on the trap gap is not supported. The NFM-P performs the following for auto alarm table resync:

  1. Before a resync of the alarm table, the NFM-P fetches the parameter that contains the "table last change time (or counter)" from the NE. This action is performed every polling interval.

  2. The NFM-P compares the value of the last NE change with the value stored in the NFM-P for that alarm table.

  3. Only if the NE value is different from the value stored in the NFM-P will the entire alarm table be resynchronized.

    OR After connectivity is restored, you can perform a manual full node resync from the NFM-P to fetch the current alarms present on the NE at that moment.

To ensure that alarm table resync occurs after NE connection is lost with the NFM-P and a trap sequence number mismatch exists between the NFM-P and NE, you can modify the Polling Interval parameter. Choose Administration→Mediation→MIB Entry Policies→fm.CurrentAlarmEntry. For better performance, it is recommended to select 5 min for the Polling Interval.

Note – For two consecutive polling intervals - If the NE connection is lost and then re-established, and if there are any trap losses in the NFM-P, but the alarm is in the NE alarm table (step 2 above is satisfied), then alarm table resync occurs (step 3 above). If an alarm is raised and cleared in between the interval of a connection lost and re-established from the NFM-P, the NFM-P does not detect the alarm.

Alarm reporting – The NFM-P supports the reporting of all alarms present in the automatically generated alarm catalog.

Radio link fault management – The NFM-P tracks the radio link down scenario. When a radio link interconnects two MPT-SUB6 devices (HBS and HSU), the NFM-P manages the operational state at the node and processes any alarms affecting the radio link extremities. The NFM-P changes the operational state on the General tab of the radio interface based on the link down alarm.

Note – The operational state on the Radio tab does not change based on link status. When the link is operationally down, the link shows red. When the link is operationally up, the link shows green.

Physical link fault management – The NFM-P tracks the physical link down scenario when a physical link is interconnecting an MPT-SUB6 and an MSS-8/4/1/0. A link down alarm is raised when the LOS (Loss Of Signal) alarm at the MPT-SUB6 port is notified by the node from the NFM-P. The link (physical or radio) is displayed as alarmed in the topology view (red line) and the link down alarm is reported in the alarm list.

Alarm correlation – The NFM-P supports alarm correlation for the Fault Management application for the following fault scenario:

  • radio link down

  • physical link down

Both “LinkDown” alarms are correlated to the “adjacencyDown” alarm at the service level.

Workflow to discover and manage the MPT-SUB6

This workflow describes how to discover and manage the MPT-SUB6 in the NFM-P after driver installation.

Consult the NSP NFM-P Classic Management User Guide chapter "Device commissioning and management" for full procedural details.

Create mediation policies and configure a discovery rule

  1. Use the NFM-P to create an SNMPv1 mediation policy that specifies “public” as the Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  2. Use the NFM-P to create an SNMPv1 mediation policy that specifies “netman” as the Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  3. Use the NFM-P to create an SNMPv3 mediation policy with V3 user and credentials as configured on the node. Security level support is as follows:

    1. No Authentication.

    2. Authentication Only with MD5.

    3. Authentication and Privacy with MD5 and DES respectively.

    4. Authentication and Privacy with SHA and AES respectively.

  4. Use the NFM-P to configure a discovery rule for the MPT-SUB6 that specifies the following mediation policies; see the NSP NFM-P Classic Management User Guide for information about creating discovery rules:

    • Read Access Mediation Policy and Trap Access Mediation Policy – mediation policy created in step 1

    • Write Access Mediation Policy – mediation policy created in step 2

Perform configuration management tasks using the device EMS

  1. Right-click on the MPT-SUB6 icon on the NFM-P topology map and choose Alternate Element Manager. The device EMS opens to allow configuration.

  2. Configure the parameters as required.

Note: The EMS is only available if the NFM-P client is on a Windows station. In addition, the EMS manager must be installed in the location pointed to by the default Alternate Element Manager in the Generic NE Profile.

View statistics

  1. Click on the Statistics tab of the MPT-SUB6 interface properties form. The MPT-SUB6 Statistics form opens.

  2. View statistics as required.

    The availability of historical data requires the activation of Performance Monitoring.

Note: It is recommended that you schedule historical data statistics only, and collect current data statistics on demand. For example, History Data Stats - 15 min returns the same information as Current Data Stats collected for the same 15 minute interval, therefore, it is redundant to schedule Current Data Stats. Scheduling Current Data Stats may result in an error message. Scheduling Interface Additional Stats (Generic NE) is not supported and may result in stopping the collection of other statistics.

Note: On the Radio interfaces:

Note: On the Ethernet interfaces:

The plotting of statistics is supported for Interface Stats (Generic NE).

The following counters are supported on Radio interfaces 101 – 104 on HBS.

Interface Type

Statistic Type

Radio (index 101 – 104)

Aggregate Rx History Data Stats – 15 min

Aggregate Rx History Data Stats – 24 hr

Aggregate Tx History Data Stats – 15 min

Aggregate Tx History Data Stats – 24 hr

Hop Current Data Stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

RSL Hop Current Data stats – 15 min

RSL Hop History Data Stats – 15 min

RSL Hop History Data Stats – 24 hr

TSL Hop Current Data Stats – 15 min

TSL Hop History Data Stats – 15 min

TSL Hop History Data Stats – 24 hr

MPT Equipment Measurement

Note - The aggregate historical data statistics and MPT equipment measurement statistics are not supported for version 2.8.X.

Ethernet (index 1 and index 2)

Aggregate Rx History Data Stats – 15 min

Aggregate Rx History Data Stats – 24 hr

Aggregate Tx History Data Stats – 15 min

Aggregate Tx History Data Stats – 24 hr

Hop Current Data stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

Note – On Ethernet interfaces with indices 1(ETH) and 2(ETH), the Interface Stats (Generic NE) are also applicable

On HSU, the following counters are supported only on interface 101.

Interface Type

Statistic Type

Radio (index 101)

Hop Current Data Stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

RSL Hop Current Data stats – 15 min

RSL Hop History Data Stats – 15 min

RSL Hop History Data Stats – 24 hr

TSL Hop Current Data Stats – 15 min

TSL Hop History Data Stats – 15 min

TSL Hop History Data Stats – 24 hr

Power Consumption (Watts)

Temperature (Celsius)

Ethernet (index 1)

Aggregate Rx History Data Stats – 15 min

Aggregate Rx History Data Stats – 24 hr

Aggregate Tx History Data Stats – 15 min

Aggregate Tx History Data Stats – 24 hr

Hop Current Data stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

Ethernet (index 1 and index 2)

Hop Current Data stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

Note – On Ethernet interfaces with indices 1(ETH) and 2(ETH), the Interface Stats (Generic NE) are also applicable.

9500 MPT-BWA

The MPT-SUB6 driver extends the management capabilities of the NFM-P for the MPT-BWA in the following applicable areas.

Table 1-4: MPTBWA driver capabilities

Configuration management

Radio link inventory – Operators can view all radio links terminating on this device by drilling down from the network topology map or network equipment tree representations of the MPT-BWA.

Note –To create a physical link, select the endpoints as type “Port”.

Additionally, radio links associated with the MPT-BWA device are now included in the inventory list accessed through the Equipment Manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Radio link (Network) from the object type drop-down).

Radio link inventory information is also available to the XML API through the installation of the MPT-SUB6 driver, under the following package and class netw.RadioPhysicalLink.

Radio port parameters – The MPT-SUB6 driver extends the NFM-P management of the MPT-BWA device to include its radio port interfaces. With the installation of the driver, a "Radio" tab is added to the Generic NE Interface properties form, allowing NFM-P operators to view the following generic radio port parameters of the device:

  • Channel Bandwidth (KHz)

  • Operational Frequency (MHz)

  • Band

  • Sector ID

  • HSU Far-end ID

  • Current Tx Power (dBm)

  • Current Rx Power (dBm) — This is not applicable for HBS in Point-to-Multipoint configurations, i.e. HBS connected to multiple HSUs.

  • MTU

  • Antenna Type

  • Available Bandwidth (Mbps)

  • Encryption Status

The following five parameters pertain to the radio link and differ according to the link that is present. Operators can create up to 64 separate radio links interconnecting the HBS and HSUs. Interfaces 101 – 164 are enabled as radio ports. The Radio panel is associated with each radio port so that operators can access the radio parameters by selecting any of the logical radio interfaces. These parameters are supported only on the Radio tab of HBS, not HSU.

  • RSL (dBm)

  • Down-link Throughput (Mbps)

  • Down-link Peak Throughput (Mbps)

  • Up-link Throughput (Mbps)

  • Up-link Peak Throughput (Mbps)

These parameters are also available to the XML API under the following package and class radioequipment.RadioPortSpecifics.

NE parameters – The following read-only parameters are displayed on the NE Properties form, General tab:

  • Name

  • IP address

  • Location

  • SW version

  • Status

  • Geographic Location (longitude/latitude)

  • Up time

  • MAC Address

  • Serial Number

  • Temperature

  • Power Consumption

    The Temperature and Power Consumption parameters are refreshed when the NE Properties form is opened. Dedicated statistics based on periodic polling of the power consumption and temperature measures are provided by the NE.

These parameters are also available to the XML API under the class equipment.PhysicalPort; see the NSP NFM-P Statistics Management Guide.

The configuration of the following Radius server parameters is supported at the HBS NE level:

  • Authorization mode – enable/disable HBS working with a radius server

  • User name and password – used for HSU authentication

  • Install confirmation required – if enabled, the HSU registration at HBS is completed when acknowledged by HSU

The NFM-P supports the configuration of multiple Radius servers (two servers in nominal network scenario) on a single HBS. Configuration of the following server parameters is supported:

  • IP address – IP address of Radius server

  • Port – communication port to which HBS connects

  • Number of retries – max number of retries in case of connection failure to server

  • Timeout

  • Secret string – key used to encrypt passwords and exchange responses for communication between HSB and Radius server

The following actions are supported for each server instantiated at HBS:

  • Clear config – clears selected server configuration

Radius server configuration and deletion are supported network-wide through the Bulk Operations tool.

Queue configuration is supported at the radio port level for uplink and downlink traffic. Up to four queues can be enabled and configured on each port. For each queue the following parameters can be configured:

  • Strict – parameter enabling the strict priority working mode. Enabling strict priority on a queue is allowed only if the higher priority queues are also in strict priority.

  • Weight [%] – Percentage of the throughput dedicated to the selected queue. If Strict is enabled, the Weight parameter is dimmed. Validation prevents the weight percentage from exceeding 100%.

  • MIR [Mbs]

Network-wide configuration is supported through the Bulk Operations tool.

Mapping between queues and the prio/exp bits range is supported at the NE level. Operators can associate each queue to a range of prio/exp bits. The configuration depends on the QoS mode that is selected:

  • Disable – queue mapping is disabled

  • VLAN – each queue can be mapped over a range of prio bits

  • DiffServ – each queue can be mapped over a range of exp bits

Up to four queues are supported. Each queue can be configured as enabled or disabled.

Choose Policies→QoS→9500 MPR QoS→9500 NE QoS from the NFM-P main menu.

Radio port inventory parameters – The following radio port inventory parameters are displayed on the Inventory tab for the radio ports:

  • Company ID

  • Factory ID

  • Mnemonic

  • Part No

  • Serial No

  • Port ID

  • Software Part No

These parameters are also available to the XML API under the following package and class radioequipment.RadioEquipmentInventory.

Radio link discovery - The NFM-P extends link auto-discovery to radio links interconnecting HBS and HSUs. The HSU radio port with index 101 is connected to the HBS logical radio port matching the following criteria:

  • The remote HBS has the same sectorID as the selected HSU.

  • For each HSU the linked HBS radio port index is equal to 100 + value(winlink1000HsuAirHsuId).

Longitude and latitude – The NFM-P displays the location of the MPT-BWA with latitude and longitude. The coordinates are displayed as additional parameters on the General tab of the Properties form. The longitude and latitude parameters are ready-only and are only displayed when the GPS state is synchronized. For all other states, the NFM-P displays an invalid value of 999.

Generic NE Profile automation – The Generic NE Profile is automatically created when MPT-SUB6 driver is installed.

Alarm catalog integration – The MPT-BWA alarm catalog is automatically populated during driver installation. Operators can edit the alarm catalog to customize alarm characteristics.

NE software version display – The NE software version is displayed on the General tab of the NE Property form.

TMN Inband management – The NFM-P displays the VLAN ID parameter and Prio parameter identifying the TMN Inband management traffic/signal. On the Polling tab, click the TMN Details sub-tab, and double-click on the row. The TMN Inband setting is read-only.

MAC address – The NFM-P displays the MAC Address of the node on the General tab of the Network Element form. The MAC Address is also accessed through the Equipment manager (Manage→Equipment→Equipment from the NFM-P main menu, then choose Network Element (Network) from the object type drop-down).

NTP management – The NFM-P reports NTP-related parameters. NTP enabling and disabling and server configuration is supported through the Alternate Element Manager. Server configuration is also supported using the NFM-P Create option.

Radio encryption status – The NFM-P reports the Encryption Status (enable/disable) at the radio interface. This parameter is read-only.

Sensor measurements – The NFM-P reports the Power Consumption (Watts) and Temperature (Celsius) parameters on the Statistics form.

SNMPv1/v3 support – The NFM-P supports SNMPv1 or SNMPv3 management of the node.

Port parameters – The NFM-P displays the following read-only parameters on the General tab of each port:

  • Mode

  • Encapsulation Type

    Note – The Encapsulation Type parameter is not supported by the NFM-P for HSU. Any displayed value should be ignored.

  • Speed

Service management

When driver-managed GNE devices are collocated with the 9500 MPR, the NFM-P supports creation of the microwave backhaul service spanning across MPRs and OEMs. The NFM-P recognizes OEM as a site to add to the microwave backhaul service. The NFM-P also recognizes the Ethernet and radio ports on OEM as adjacencies to add to OEM sites. However, the NFM-P does not support deployment of these services to OEM devices. Deployment to OEM devices must be done from the respective EMS. Consequently, discovery of this service does not discover OEM sites. Therefore, OEM sites can be either manually added or populated using the Complete Ring feature for the MPTGM.

Service category configuration is supported at the HBS (NE level). There are eight QoS profiles referenced by Radius for service provisioning. The following parameters are associated with the service category class:

  • Category name - text string representing the service category label

  • Uplink resources

  • Downlink resources

  • Resource type

    CIR - grants the service a certain guaranteed percentage of HBS resources

    Best Effort - grants resources as they become available in the sector

  • MIR Up

  • MIR Down

To configure QoS queues profiles for uplink and downlink traffic, click on the relevant tab to open the QoS configuration form associated with the selected service category. You can configure up to four queues with the selected service category:

  1. real time

  2. near real time

  3. controlled load

  4. best effort

For each queue, the following parameters can be configured:

  • Strict - Flag parameter enabling strict priority working mode. Enabling strict priority on a queue is allowed only if the higher priority queues are also in strict priority.

  • Weight [%] - Percentage of the throughput dedicated to the selected queue. If Strict is enabled, the Weight parameter is dimmed. Validation prevents the weight percentage to exceed 100%.

  • MIR [Mbs]

  • TTL [ms]

    Note: The node accepts TTL values in increments of 5 only. The range of values is 0 to 500 ms.

Network-wide configuration is supported through the Bulk Operations tool.

Network assurance

Not applicable

Service assurance

Performance management – The MPT-SUB6 driver extends NFM-P performance management to the MPT-BWA device so that statistics related to the GNE can be viewed through the NFM-P GUI. Statistics are also available to the XML API; see the NSP NFM-P Statistics Management Guide.

Alarm resynchronization – Since traps do not have a sequence ID to detect trap gaps, the "auto resynch of alarm table" based on the trap gap is not supported. The NFM-P performs the following for auto alarm table resync:

  1. Before a resync of the alarm table, the NFM-P fetches the parameter that contains the "table last change time (or counter)" from the NE. This action is performed every polling interval.

  2. The NFM-P compares the value of the last NE change with the value stored in the NFM-P for that alarm table.

  3. Only if the NE value is different from the value stored in the NFM-P will the entire alarm table be resynchronized.

    OR After connectivity is restored, you can perform a manual full node resync from the NFM-P to fetch the current alarms present on the NE at that moment.

To ensure that alarm table resync occurs after NE connection is lost with the NFM-P and a trap sequence number mismatch exists between the NFM-P and NE, you can modify the Polling Interval parameter. Choose Administration→Mediation→MIB Entry Policies→fm.CurrentAlarmEntry. For better performance, it is recommended to select 5 min for the Polling Interval.

Note – For two consecutive polling intervals - If the NE connection is lost and then re-established, and if there are any trap losses in the NFM-P, but the alarm is in the NE alarm table (step 2 above is satisfied), then alarm table resync occurs (step 3 above). If an alarm is raised and cleared in between the interval of a connection lost and re-established from the NFM-P, the NFM-P does not detect the alarm.

Alarm reporting – The NFM-P supports the reporting of all alarms present in the automatically generated alarm catalog.

Radio link fault management – The NFM-P tracks the radio link down scenario. When a radio link interconnects two MPT-BWA devices (HBS and HSU), the NFM-P manages the operational state at the node and processes any alarms affecting the radio link extremities. The NFM-P changes the operational state on the General tab of the radio interface based on the link down alarm.

Note – The operational state on the Radio tab does not change based on link status. When the link is operationally down, the link shows red. When the link is operationally up, the link shows green.

Physical link fault management – The NFM-P tracks the physical link down scenario when a physical link is interconnecting an MPT-BWA and an MSS-8/4/1/0. A link down alarm is raised when the LOS (Loss Of Signal) alarm at the MPT-BWA port is notified by the node from the NFM-P. The link (physical or radio) is displayed as alarmed in the topology view (red line) and the link down alarm is reported in the alarm list.

Alarm correlation – The NFM-P supports alarm correlation for the Fault Management application for the following fault scenario:

  • radio link down

  • physical link down

Both “LinkDown” alarms are correlated to the “adjacencyDown” alarm at the service level.

Workflow to discover and manage the MPT-BWA

This workflow describes how to discover and manage the MPT-BWA in the NFM-P after driver installation.

Consult the NSP NFM-P Classic Management User Guide chapter "Device commissioning and management" for full procedural details.

Create mediation policies and configure a discovery rule

  1. Use the NFM-P to create an SNMPv1 mediation policy that specifies “public” as the Read/Trap Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  2. Use the NFM-P to create an SNMPv1 mediation policy that specifies “netman” as the Write Community String value. See the NSP NFM-P Classic Management User Guide for information about creating mediation policies.

  3. Use the NFM-P to create an SNMPv3 mediation policy with V3 user and credentials as configured on the node. Security level support is as follows:

    1. No Authentication.

    2. Authentication Only with MD5.

    3. Authentication and Privacy with MD5 and DES respectively.

    4. Authentication and Privacy with SHA and AES respectively.

  4. Use the NFM-P to configure a discovery rule for the MPT-BWA that specifies the following mediation policies; see the NSP NFM-P Classic Management User Guide for information about creating discovery rules:

    • Read Access Mediation Policy and Trap Access Mediation Policy – mediation policy created in step 1

    • Write Access Mediation Policy – mediation policy created in step 2

Perform configuration management tasks using the device EMS

  1. Right-click on the MPT-BWA icon on the NFM-P topology map and choose Alternate Element Manager. The device EMS opens to allow configuration.

  2. Configure the parameters as required.

Note: The EMS is only available if the NFM-P client is on a Windows station. In addition, the EMS manager must be installed in the location pointed to by the default Alternate Element Manager in the Generic NE Profile.

View statistics

  1. Click on the Statistics tab of the MPT-BWA interface properties form. The MPT-BWA Statistics form opens.

  2. View statistics as required.

    The availability of historical data requires the activation of Performance Monitoring.

Note: It is recommended that you schedule historical data statistics only, and collect current data statistics on demand. For example, History Data Stats - 15 min returns the same information as Current Data Stats collected for the same 15 minute interval, therefore, it is redundant to schedule Current Data Stats. Scheduling Current Data Stats may result in an error message. Scheduling Interface Additional Stats (Generic NE) is not supported and may result in stopping the collection of other statistics.

Note: The plotting of statistics is supported for Interface Stats (Generic NE).

Note: On the Radio interfaces:

Note: On the Ethernet interfaces:

The following counters are supported on Radio interfaces 101 – 164 on HBS.

Interface Type

Statistic Type

Radio (index 101 – 164)

Aggregate Rx History Data Stats – 15 min

Aggregate Rx History Data Stats – 24 hr

Aggregate Tx History Data Stats – 15 min

Aggregate Tx History Data Stats – 24 hr

Hop Current Data Stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

RSL Hop Current Data stats – 15 min

RSL Hop History Data Stats – 15 min

RSL Hop History Data Stats – 24 hr

TSL Hop Current Data Stats – 15 min

TSL Hop History Data Stats – 15 min

TSL Hop History Data Stats – 24 hr

MPT Equipment Measurement

Ethernet (index 1)

Aggregate Rx History Data Stats – 15 min

Aggregate Rx History Data Stats – 24 hr

Aggregate Tx History Data Stats – 15 min

Aggregate Tx History Data Stats – 24 hr

Hop Current Data stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

Note – On Ethernet interfaces with index 1(ETH), the Interface Stats (Generic NE) are also applicable

On HSU, the following counters are supported only on interface 101.

Interface Type

Statistic Type

Radio (index 101)

Hop Current Data Stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

RSL Hop Current Data stats – 15 min

RSL Hop History Data Stats – 15 min

RSL Hop History Data Stats – 24 hr

TSL Hop Current Data Stats – 15 min

TSL Hop History Data Stats – 15 min

TSL Hop History Data Stats – 24 hr

Power Consumption (Watts)

Temperature (Celsius)

Ethernet (index 1)

Aggregate Rx History Data Stats – 15 min

Aggregate Rx History Data Stats – 24 hr

Aggregate Tx History Data Stats – 15 min

Aggregate Tx History Data Stats – 24 hr

Hop Current Data stats – 15 min

Hop History Data Stats – 15 min

Hop History Data Stats – 24 hr

Note – On Ethernet interfaces with index 1(ETH), the Interface Stats (Generic NE) are also applicable.