This page describes the new features and enhancements for the WaveSuite H&A product. Click the tab for the release you want.
For a description of the main product features, refer to the Customer Release Notes in Downloads.
| Feature | Description |
|---|---|
| Port and service growth monitoring and trending | WaveSuite introduces port utilization time-series and baseline comparison, enabling operators to track total, used, and free ports, and visualize trends. |
| WS Integrated WS-HA and WS-SE IPv6 support | WS-HA and WS-SE support IPv6 Addressing, allowing to deploy WaveSuite Integrated including WS-HA and WS-SE in a IPv6 addressed subnetwork (The restriction is removed). |
| Robust handling and validation of Zero Pre-FEC BER Values | WaveSuite now flags Pre-FEC BER = 0 cases with a clear disclaimer to prevent misleading performance insights. |
| Feature | Description |
|---|---|
| Per-shelf and per-NE power reporting | This feature introduces a new power consumption report that provides a detailed power consumption data per shelf and network element (NE), enabling efficient power management and effective monitoring of energy consumption. |
| Heat maps range selection | This feature provides flexible range selection on heat maps, allowing users to customize data ranges directly within the heat map visualization page. |
| Ordering for span-loss multi-span crossed measurements. | This feature enhances multi-span span-loss visualization by displaying crossed spans in their correct sequential order, improving clarity and overall path visualization. |
| Support columns sorting in the Raw KPI screen | This feature provides column sorting capability on Raw KPI screen for streamlined analysis and usability. |
| Network element system performance monitoring and trending | This feature adds two new KPIs for granular monitoring of NE, CPU and memory utilization. |
| Node thermal status (temperature and fan) monitoring and trending | This feature adds two new KPIs for granular monitoring of thermal status (temperature and cooling fan rotation). |
| In-app context-sensitive support | This feature enables launch of context-sensitive help for the entire suite of WS-HA, accessible from anywhere within the WS-HA GUI. |
| ESG Centralized Function | New navigation from WS-O dashboard to Network Power Map and subsequent navigation to the Power Dashboard. |
| Feature | Description |
|---|---|
| Amplifier degradation monitoring and trending | WS-HA introduces monitoring of amplifier health through derived degradation KPIs (power efficiency and error gain) and native ones (pump current, total input power, signal output power). The user can analyze trends and set TCAs. WS-HA includes a dashboard for at-a-glance view and amplifier's degradation report. |
| Span-loss variation from baseline heat map visualization | WS-HA enhances span loss analysis with a new map-based visualization of the span loss delta. This enhancement enables users to efficiently monitor link's loss health by visually identifying spans with significant loss variation on a geographical map. |
| Streamline troubleshooting and access to log file | WS-HA introduces the capability for the user to download the troubleshooting data and logs file using the GUI and API. |
| Naming for span-loss multi-span crossed measurements. | When displaying the span loss measurement for a connection that crosses multiple spans the WS-HA interface introduces the option to use the name of the external link instead of the name of the amplifier. |
| Display port names in KPI screen | On the Raw KPI page, WS-HA now reports the port name instead of the port index number. |
| Display Customer column in lightpaths screen | WS-HA now displays the column Customer in the LIGHTPATHs page as it is done in the SERVICES list. |
| Linking equipment-related KPIs to context data | For Equipment KPIs, you can access the network element data from the dashboard. From the donut chart you can navigate to the respective filtered list in the Network Entities page. |
| Endpoint label | Endpoint name |
|---|---|
| Returns all data sources | GET /api/v1/data-sources |
| Creates a single data source instance | POST /api/v1/data-sources |
| Deletes a data source instance | DELETE /api/v1/data-sources/{dataSourceId} |
| Returns a single data source instance | GET /api/v1/data-sources/{dataSourceId} |
| Updates a data source instance | PUT /api/v1/data-sources/{dataSourceId} |
| Returns the list of data source interfaces associated to a single data source instance | GET /api/v1/data-sources/{dataSourceId}/data-source-interfaces |
| Associates a data source instance to a list of data source interfaces | POST /api/v1/data-sources/{dataSourceId}/data-source-interfaces |
| Deletes a data source interface instance | DELETE /api/v1/data-source-interfaces/{dataSourceInterfaceId} |
| Returns a single data source interface instance | GET /api/v1/data-source-interfaces/{dataSourceInterfaceId} |
| Updates a data source interface instance | PUT /api/v1/data-source-interfaces/{dataSourceInterfaceId} |
| Returns the list of data sources configured to use a single data source interface instance | GET /api/v1/data-source-interfaces/{dataSourceInterfaceId}/data-sources |
| Associates a data source interface instance to a list of data sources | POST /api/v1/data-source-interfaces/{dataSourceInterfaceId}/data-sources |
| Returns the list of current status of a data source instance for a particular interface | GET /api/v1/data-sources/{dataSourceId}/data-source-interfaces/ {dataSourceInterfaceId}/status |
| Test the reachability of the data source over a particular data source interface | POST /api/v1/data-sources/{dataSourceId}/data-source-interfaces/ {dataSourceInterfaceId}/test |
| Get Network Cards | GET /wavesuite/ha/api/v1/network-cards |
| Save Network Card | POST /wavesuite/ha/api/v1/network-cards |
| Delete the Network Card | DELETE /wavesuite/ha/api/v1/network-cards/{cardId} |
| Get Network Card | GET /wavesuite/ha/api/v1/network-cards/{cardId} |
| Update an existing Network Card | PUT /wavesuite/ha/api/v1/network-cards/{cardId} |
| Get Network Elements | GET /wavesuite/ha/api/v1/network-elements |
| Save Network Element | POST /wavesuite/ha/api/v1/ network-elements |
| Get Network Ports by Network Element ID | GET /wavesuite/ha/api/v1/ network-elements/{elementId}/network-ports |
| Get Network Cards by Network Element ID | GET /wavesuite/ha/api/v1/network-elements/{elementId}/network-cards |
| Get Network Connections by Network Element ID | GET /wavesuite/ha/api/v1/network-elements/{elementId}/network-connections |
| Get Network Lightpaths by Network Element ID | GET /wavesuite/ha/api/v1/ network-elements/{elementId}/network-lightpaths |
| Get Network External Links by Network Element ID | GET /wavesuite/ha/api/v1/ network-elements/{elementId}/network-external-links |
| Delete the Network Element | DELETE /wavesuite/ha/api/v1/ network-elements/{elementId} |
| Get Network Element | GET /wavesuite/ha/api/v1/ network-elements/{elementId} |
| Update an existing Network Element | PUT /wavesuite/ha/api/v1/ network-elements/{elementId} |
| Revert location configuration to a group of network elements | POST /wavesuite/ha/api/v1/ network-elements/revert-location-config/bulk |
| Get Network Ports | GET /wavesuite/ha/api/v1/ network-ports |
| Save Network Port | POST /wavesuite/ha/api/v1/ network-ports |
| Delete the Network Port | DELETE /wavesuite/ha/api/v1/ network-ports/{portId} |
| Get Network Port | GET /wavesuite/ha/api/v1/ network-ports/{portId} |
| Update an existing Network Port | PUT /wavesuite/ha/api/v1/ network-ports/{portId} |
| Get Network Connections by Network Port ID | GET /wavesuite/ha/api/v1/ network-ports/{portId}/network-connections |
| Get Network Lightpaths by Network Port ID | GET /wavesuite/ha/api/v1/ network-ports/{portId}/network-lightpaths |
| Get Network Connections | GET /wavesuite/ha/api/v1/ network-connections |
| Save Network Connections | POST /wavesuite/ha/api/v1/ network-connections |
| Delete the Network Connection | DELETE /wavesuite/ha/api/v1/ network-connections/{connectionId} |
| Get Network Connection | GET /wavesuite/ha/api/v1/ network-connections/{connectionId} |
| Update an existing Network Connection | PUT /wavesuite/ha/api/v1/ network-connections/{connectionId} |
| Get Network Ports by Network Connection ID | GET /wavesuite/ha/api/v1/ network-connections/{connectionId}/network-ports |
| Create or update the list of Network Ports associated to the Network Connection | POST /wavesuite/ha/api/v1/ network-connections/{connectionId}/network-ports |
| Get Network Elements by Network Connection ID | GET /wavesuite/ha/api/v1/ network-connections/{connectionId}/network-elements |
| Get Network External Links by Network Connection ID | GET /wavesuite/ha/api/v1/ network-connections/{connectionId} /network-external-links |
| Get Network Lightpaths by Network Connection ID | GET /wavesuite/ha/api/v1/ network-connections/{connectionId}/network-lightpaths |
| Create or update the list of Network Lightpaths associated to the Network Connection | POST /wavesuite/ha/api/v1/ network-connections/{connectionId}/network-lightpaths |
| Get Network Lightpaths | GET /wavesuite/ha/api/v1/ network-lightpaths |
| Save Network Lightpath | POST /wavesuite/ha/api/v1/network-lightpaths |
| Delete the Network Lightpath | DELETE /wavesuite/ha/api/v1/network-lightpaths/{lightpathId} |
| Get Network Lightpath | GET /wavesuite/ha/api/v1/ network-lightpaths/{lightpathId} |
| Update an existing Network Lightpath | PUT /wavesuite/ha/api/v1/network-lightpaths/{lightpathId} |
| Get Network Ports by Network Lightpath ID | GET /wavesuite/ha/api/v1/network-lightpaths/{lightpathId}/network-ports |
| Get Network Connections by Network Lightpath ID | GET /wavesuite/ha/api/v1/ network-lightpaths/{lightpathId}/network-connections |
| Get Network Elements by Network Lightpath ID | GET /wavesuite/ha/api/v1/network-lightpaths/{lightpathId}/network-elements |
| Get Network External Links by Network Lightpath ID | GET /wavesuite/ha/api/v1/ network-lightpaths/{lightpathId}/network-external-links |
| Create or update the list of Network External Links associated to the Network Lightpath | POST /wavesuite/ha/api/v1/network-lightpaths/{lightpathId} /network-external-links |
| Get Network External Links | GET /wavesuite/ha/api/v1/network-external-links |
| Save Network External Link | POST /wavesuite/ha/api/v1/network-external-links |
| Delete the Network External Link | DELETE /wavesuite/ha/api/v1/network-external-links/{externalLinkId} |
| Get Network External Link | GET /wavesuite/ha/api/v1/network-external-links/{externalLinkId} |
| Update an existing Network External Link | PUT /wavesuite/ha/api/v1/network-external-links/{externalLinkId} |
| Get Network Lightpaths by Network External Link ID | GET /wavesuite/ha/api/v1/network-external-links/{externalLinkId} /network-lightpaths |
| Feature | Description |
|---|---|
| WS-HA in a WaveSuite integrated solution | WS-HA is only installed as part of a WaveSuite integrated solution. In an integrated deployment, WS-HA will be deployed on a dedicated VM in a Classic, Distributed, or Hyper-distributed deployment configuration. Communication between the WS-HA application and WS-NOC server(s) uses a Mutual Transport Layer Security (mTLS) certificate-based authentication for server-to-server communications. Port usage, including which ports must be exposed on the host OS, has changed with the WS-HA integration with WS-NOC. Some features that were previously available in WS-HA are now managed by WS-NOC, such as the backup and restore, certificate management, disaster recovery, license management, redundant deployment management, upgrade and data migration, and user management and user profiles. For more information on how WS-HA functionality has changed since moving to the WaveSuite integrated solution, refer to the Nokia WaveSuite Health & Analytics Dimensioning and System Configuration Guidelines and Nokia WaveSuite Health & Analytics Administration Guide. |
| Access WS-NOC dataa for network objects | The View in WS-NOC action icon is a new feature on the Network Elements, Connections, and External Links pages that lets you launch the 360° View page in WS-NOC for a specific network element, connection, lightpath, or external link. For information about the 360° View page, refer to the WS-NOC user documentation. |
| Connections page | The CONNECTIONS tab on the Connections page now displays a Diversity Group column that displays the name of the diversity group to which the disjointed, dual-homed connection belongs. |
| Fault Localization | On the Configuration page, in the SETTINGS tab, the Event Driven Execution parameters on the FAULT LOCALIZATION sub-tab were updated to include a Measurements in Analysis section that lets you choose KPI measurements (Post-FEC BER, Q2 Factor, or Span Loss) for the analysis. The Include External Links parameter was removed from the settings. These changes also apply to the Fault Localization report parameters on the Reports page. |
| KPI data acquisition | As part of the WaveSuite integrated solution, instead of retrieving raw KPI data directly from NEs, WS-HA now retrieves the KPI data from WS-NOC. The WS-HA KPI adapter, wsha-kpi-data-acquisition-adapter, performs PM data acquisition from WS-NOC and converts it to the WS-HA KPI data format. Weather KPIs are still retrieved from Weather APIs using WS-HA's weather adapter. |
| License file |
The WS-HA license file, including its generation by Nokia, is integrated with WS-NOC. As an optional licensed application that integrates with WS-NOC, WS-HA requires its own license separate from the WS-NOC license. The WS-HA license file is XML-based and aligns with the WS-NOC base license framework. The license also specifies whether WS-HA can be installed in an HA configuration. When requesting the license from Nokia, you must provide the product UUID of the VM on which WS-HA will be installed. In a redundant configuration, you must provide the product UUID for both the active and standby WS-HA VMs. |
| License installation and validation | License installation and validation at login is integrated with WS-NOC. The WS-HA license file is imported when installing WS-HA, whether together with WS-NOC or on an already installed WS-NOC. After WS-HA is installed, the license can be added or replaced at any time. WS-HA performs license validation whenever WS-HA users log in to the application. All users will receive any license expiration warning and error messages when logging in to WS-HA. |
| License management | WS-HA license management is integrated with WS-NOC. WS-NOC lets you view the current status of the WS-HA license and whether WS-HA is licensed for redundancy. |
| Process control | WS-HA process control is integrated with WS-NOC. WS-NOC lets you manually stop, start, and restart certain WS-HA containers and their processes. For information about process control, see the Nokia WaveSuite Health & Analytics Administration Guide. |
| Process monitoring | WS-HA process monitoring is integrated with WS-NOC. WS-NOC lets you monitor the WS-HA containers and their processes. You can view the status, memory usage, CPU usage, and properties of the containers and processes, as well as the process logs. For information about process monitoring, see the Nokia WaveSuite Health & Analytics Administration Guide. |
| Reports page | The Report Runs panel includes a new Message column that displays additional information. |
| Single sign-on authentication | Automatic single sign-on (SSO) to all authorized WS-NOC solution applications. SSO is an authentication method that lets users log in once using a single set of credentials, and access multiple WaveSuite applications during the same session. Users must have authorization permissions in the WaveSuite applications they are trying to access. SSO works in conjunction with WS-NOC user profiles, that have a defined Feature Access Domain (FAD) authorization method, to provide secure access to WaveSuite applications and defines their permissions in the applications. Logging out of one application will log you out of all other WaveSuite applications. |
| Supported inline upgrade path | WS-HA supports inline upgrades for standalone and redundant deployments. WS-HA R24.6 supports the following inline upgrade path: R24.6 to R24.6.x.x. |
| Supported upgrade and data migration paths | WS-HA R24.6 supports R23.7 to R24.6 and R23.12.x to R24.6. These migration paths support migrating from instances of WS-HA installed separately, independent of other solutions (Releases 23.7 and 23.12.x), and instances of WS-HA integrated with WS-NOC (Release 23.12). |
| Supported WS-NOC release | WS-HA added support for WS-NOC R24.6 and removed support for WS-NOC R23.12. |
| TCAs: Configurations page | On the Configuration page, in the SETTINGS tab, the GENERAL sub-tab now includes a setting to either delete TCAs after a configured number of days or not delete TCAs. |
| TCAs: Notifications page | On the Notifications page, the TCA tab includes a new KPI Trend panel that provides visualizations of a selected KPI measurement in chart form for a selected TCA. |
| User documentation: Nokia WaveSuite Health & Analytics Administration Guide | This document provides information to system and network administrators on how to administer and maintain Nokia WaveSuite Health & Analytics (WS-HA) in a WaveSuite integrated solution. |
| User documentation: Nokia WaveSuite Health & Analytics Dimensioning and System Configuration Guidelines | This document provides planning information for a Nokia WaveSuite Health & Analytics (WS-HA) deployment in a WaveSuite integrated solution. This document also describes how WS-HA functionality has changed since moving from a separate installation, independent of other solutions, to a WaveSuite integrated solution. |
| User interface improvements: Configuration page | In the SETTINGS tab, the GENERAL sub-tab was updated to provide a more user-friendly look and feel. |
| User interface improvements: Application banner | The application banner is the horizontal bar across the top of the application window. It is a common-style banner used by all WaveSuite products to provide users with a consistent look and feel across all products. From the application banner, you can click the hamburger icon to expand and collapse the navigation pane, and use the Applications Menu drop-down list to access other WaveSuite applications that are installed and running and to which you have access permissions. |
| User interface improvements: Navigation pane - Notifications icon | The Notifications icon was moved from the application banner to the navigation pane. You can now access the Notifications page from the navigation pane. |
| User interface improvements: Navigation pane - More icon | The new More icon gives you access to the production information and the KPI Measurements Documentation, Reference Data, Audit Log, and Plugin Management pages. You can also access the API documentation in a new browser tab if this option was enabled during installation. |
| User management and user profiles | User management and user profiles are integrated with WS-NOC. WS-NOC lets you create and manage user accounts and user profiles. The WS-NOC user account must have a user profile that has a defined WS-HA Feature Access Domain (FAD) that controls a user's role and their permissions in WS-HA. |
| Video tutorials | Create and Implement TCA Configurations and Profiles, Create Non-recurring Maintenance Intervals, Using Fault Localization, Using the Dashboard, and Using the Network Map video tutorials are now available. |
| Feature | Description |
|---|---|
| Installing WS-HA separately from other solutions | WS-HA is no longer installed separately, independent of other solutions. WS-HA is only installed as part of a WaveSuite integrated solution. In an integrated deployment, WS-HA will be deployed on a dedicated VM in a Classic, Distributed, or Hyper-distributed deployment configuration. For instructions about installing WS-HA in a WaveSuite integrated solution, refer to the Nokia WaveSuite Installation Guide. For information about how WS-HA functionality has changed since moving to a WaveSuite integrated solution, refer to the Nokia WaveSuite Health & Analytics Dimensioning and System Configuration Guidelines. |
| Optical Time-Domain Reflectometer (OTDR) | The ability to monitor the fiber integrity of an external link using OTDR technology, manage OTDR definitions, and manage OTDR scans has been removed from WS-HA. WS-HA now retrieves OTDR KPI data directly from WS-NOC. For information about the OTDR feature in WS-NOC; refer to the WS-NOC user documentation. |
|
NE connectivity management |
The ability to configure profiles for network management protocols (gNMI, SFTP, SNMP, and NMS API) to define the connection between WS-HA and NE or NMS data sources so that WS-HA can collect KPI data is no longer available or required as WS-HA no longer retrieves its KPI data directly from NEs. WS-HA now retrieves all raw KPI data directly from WS-NOC and uses the WS-HA KPI adapter to convert that data into the WS-HA KPI format. The following WS-HA NE connectivity features have been removed. On the Configuration page, the NE CONNECTIVITY tab lets you create and manage connectivity protocol configurations. On the Data Sources page, the following has been removed. NETWORK DOMAINS tab. The ability to view and define default connectivity protocol configurations. NETWORK MANAGEMENT tab. The ability to enable and disable PM bin data retrieval stored by the NMS. NETWORK ELEMENTS tab. The ability to view connectivity states and to apply connectivity configurations. DATA SOURCES tab. The ability to view and edit network element data sources. DATA SOURCE INTERFACES tab. The ability to create data source interfaces for network elements. On the Plugin Management page, the gNMI, SFTP, and SNMP connectivity protocol plugins have been removed. On the Reports page, The NE Connectivity report type has been removed. The gNMI State, SFTP State, SNMP State, NE Reachability Connectivity KPIs have been removed. In the WaveSuite Health & Analytics API, The related NE connectivity API endpoints have also been removed from the Network API set. For information about NE connectivity states, refer to the WS-NOC user documentation. |
| WaveSuite Administration | Product administration is no longer available using WaveSuite Administration. WS-NOC now provides the administration features for WS-HA that were previously available in WaveSuite Administration. These include email and SMTP configuration settings, user management (for information about the new WS-NOC user profiles and access permissions in WS-HA Release 24.6, refer to the Nokia WaveSuite Health & Analytics User Guide. For information about WS-NOC user account and user profile management, refer to the WS-NOC user documentation), and system backup management (WS-HA system backup management and restore operations are performed using the WS NOC UI; refer to the Nokia WS-NOC Administration Guide). For information about the mentioned administration features in WS-NOC, refer to the WS-NOC user documentation. The following features from WaveSuite Administration are either no longer available or have been moved. external URL launch configuration is no longer available (Note: Any custom external URL launch configurations you created in WS-HA Release 23.12 or earlier will no longer be available when you upgrade to WS-HA Release 24.6). The network map setting has been moved to the WS-HA SETTINGS tab on the Configuration page. |
| WS-HA installation guide | The Nokia WaveSuite Health & Analytics Installation and System Level Administration Guide is discontinued. For WaveSuite integrated solution installation information, refer to the Nokia WaveSuite Health & Analytics Dimensioning and System Configuration Guidelines, the Nokia WaveSuite Dimensioning and System Configuration Guideline, and the Nokia WaveSuite Installation Guide. |