Network Services Platform - Help · PDF fileNetwork Services Platform Release 17.6...

NSP Network Services Platform Release 17.6

Applications Guide

3HE-11988-AAAC-TQZZA Issue 1 June 2017

Nokia — Proprietary and confidential.

Use pursuant to applicable agreements.

NSP Applications Guide

Issue: 1 3HE-11988-AAAC-TQZZA 2

Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners. The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein. © 2017 Nokia.

Contents

1. Applications overview 5 1.1. About ......................................................................................................... 5 Applications ............................................................................................................ 5 Licensing ............................................................................................................. 8 Browser connections .............................................................................................. 8 1.2. Getting Started .......................................................................................... 8 Setting the browser path in the NFM-P client ........................................................ 8 1.3. Administrator ............................................................................................. 9 Workflow to manage applications .......................................................................... 9 Maximum number of user operator positions ........................................................ 9 Limiting the number of concurrent web client sessions for a user ......................... 9 NSP settings ........................................................................................................ 10 Configuring security message .............................................................................. 10 NFM-P settings .................................................................................................... 10 Configuring NFM-P system settings .................................................................... 10 Configuring NFM-P colors .................................................................................... 10 Linked URLs ......................................................................................................... 11 Adding links to URLs to the application ............................................................... 11 1.4. REST API ................................................................................................ 11 1.5. Accessibility ............................................................................................. 11

2. Service Supervision overview 14 2.1. About ....................................................................................................... 14 2.2. Getting Started ........................................................................................ 14 Creating Supervision Groups ............................................................................... 14 Creating Summary Views .................................................................................... 15 Enabling SAP Down State Cause KPI ................................................................. 15 Purging assurance event records ........................................................................ 15

3. Network Supervision overview 17 3.1. About ....................................................................................................... 17 3.2. Getting Started ........................................................................................ 17 Creating Supervision Groups ............................................................................... 17 Creating Summary Views .................................................................................... 18 Purging assurance event records ........................................................................ 18

4. Fault Management overview 19 4.1. About ....................................................................................................... 19 4.2. Getting Started ........................................................................................ 19 Creating an alarm e-mail policy ........................................................................... 19

5. Analytics overview 21 5.1. About ....................................................................................................... 21 Analytics reports ................................................................................................... 21 Analytics configuration ......................................................................................... 21 5.2. Getting Started ........................................................................................ 21 Workflow to configure NFM-P analytics ............................................................... 21 Configuring an NFM-P analytics rule ................................................................... 22 Configuring NFM-P analytics aggregation ........................................................... 22



6. Golden Configuration overview 23 6.1. About ....................................................................................................... 23 NE Support ........................................................................................................... 23 Golden configuration of 7210 SAS....................................................................... 24 6.2. Getting Started ........................................................................................ 25 Enabling NETCONF access on an NE ................................................................ 25 Customizing NE-specific configurations in a golden configuration ...................... 26

7. Link Utilization overview 31 7.1. About ....................................................................................................... 31 Current and historical utilization ........................................................................... 31 Troubleshooting to confirm statistics collection ................................................... 31 7.2. Getting Started ........................................................................................ 32 Workflow to configure Link Utilization .................................................................. 32 Overwriting the default database partitioning size ............................................... 32 Troubleshooting statistics collection .................................................................... 33

8. Subscriber Management overview 34 8.1. About ....................................................................................................... 34 8.2. Getting Started ........................................................................................ 34


1. Applications overview

About

NSP provides network management functions using browser-based web applications. The applications are external to the client and do not require a local client installation.

Applications

The following table describes the applications and lists the URLs from which you can access the individual applications. You can also open certain applications from the client; others allow you to open the client from the application. See Licensing for information about application licensing. You must configure the Browser Path parameter in your User Preferences to launch a specific browser from the NFM-P client. See Setting the browser path in the NFM-P client.

Application and License

Description

Domain

Maximum number of concurrent application

sessions

Launch

client from application

Launch

application from client

Analytics Standard or Premium license with AA_ANALYTICS_BASE optional license Network and Service reports: Premium license only

Provides graphical and tabular reports of network conditions and trends, based on the analysis of raw statistics data and big-data aggregation using business intelligence software

AA IP

core/edge Mobile

gateway

10 yes

1830 PSS Equipment View Standard license The 1830 PSS Equipment View application is not available from the Launchpad in NFM-P Release 17.3 and later. You can access the application directly by using the URL: https://server:8543/EquipmentView

Provides a view of shelves that are configured on 1830 PSS devices, and displays and traces physical links

Optical

(1830 PSS)

50



Fault Management Standard license

Provides alarm monitoring, correlation, and troubleshooting for the most unhealthy NEs in the network, allowing you to filter, identify root causes, and determine the impact of alarms

IP

core/edge Optical Mobile

gateway Mobile

backhaul Packet

microwave mobile

backhaul Wireless

(LTE RAN)

250 yes yes

Golden Configuration Premium license

Allows you to create multiple snapshots of an NE configuration, view snapshots, and compare two selected snapshots

IP

core/edge

50

Inventory Management Standard license

Provides a dashboard inventory view of virtual network components and virtualized services in the network, allowing you to filter, search, and map data center network elements

Data center

- Nuage VSAP

50 yes

Link Utilization Premium license

Provides IP, MPLS, and aggregated utilization statistics for interfaces within a specific domain

IP

core/edge

4 yes

Network Supervision Standard license

Monitors the health of physical NEs and virtual NFs using pre-defined KPIs and alarms to provide a launchpad for monitoring the overall health of NEs in the network

IP

core/edge NFV

50 yes


Service Navigator Standard license

Provides a launchpad of the operational health of the service objects in a specified administrative domain

Data center

— Nuage VSAP

50 yes

Service Supervision Premium license

Provides alarm and KPI monitoring on user-defined service views and groups

IP

core/edge Mobile

backhaul

250 yes

Subscriber Management Premium license

Provides NE and subscriber KPI information, alarm monitoring and correlation, and troubleshooting functions for subscriber hosts

Subscriber

5 yes

Telemetry Standard license

Provides a graphical dashboard of NE KPIs based on real-time telemetry statistics

IP

core/edge

100

VNF Manager Premium license

Provides VNF lifecycle management functionality for an NFV network

NFV

5 yes yes

Wireless Supervision Premium license

Provides alarm monitoring based on user-defined views and groups for an LTE RAN network

Wireless

(LTE RAN)

50 yes yes

Wireless NE Views Premium license

Provides a visual representation of eNodeB hardware, links, states and fault status for a single NE.

Wireless

(LTE RAN)

50 yes



Licensing

When a Premium license is in use, all the application icons appear on the Launchpad. When a Standard NFM-P license is in use, Premium application icons are displayed with a badge. See the Applications Table for a list of Premium and Standard applications. NOTE: To acquire a license for applications in the Premium suite, please contact your local Nokia representative.

Browser connections

For information on which browsers the NFM-P applications are supported, see the NSP NFM-P Planning Guide. When you first connect to an application for which SSL is enabled, you must add the browser exception and proceed, as prompted by your browser. When you first launch the Analytics application from the Launchpad, the application prompts you to add the Analytics server SSL certificate to continue. NOTE: The Safari web browser requires special configuration in order to open the Analytics application. You must ensure that the Cookies and website data setting on the Safari Preferences page is set to Always allow, or the browser cannot open the Analytics application. NOTE: If you are using Chrome or Firefox on Windows 8.1 or Windows Server 2012, it is recommended that you enable ClearType Text for optimal viewing of fonts. In the Windows Control Panel, open the Display settings, and enable the Turn on ClearType parameter under the Adjust ClearType text settings. NOTE: You cannot switch browsers between clients or applications. You must always use the browser configured as the default. See Setting the browser path in the NFM-P client.

Getting Started

The following procedure describes tasks that you must perform using a NFM-P client to enable NFM-P application use on the client station.

Setting the browser path in the NFM-P client

You must configure the Browser Path parameter in your User Preferences to launch a specific browser from the NFM-P client. NOTE: In a Citrix environment in which there are multiple browsers installed and the NFM-P Java client is also installed, if no browser is specified in the NFM-P client, the default browser of the system is launched when you cross-launch an application. When you specify a browser in the NFM-P, that browser is launched. If you remove the browser configuration from the NFM-P client, the default browser of the system is used. You cannot switch browsers between clients or applications. You must always use the browser configured as the default.


1. Choose Application→User Preferences from the NFM-P main menu. The User Preferences form opens.

2. Click Browse to choose the .exe file from the appropriate application folder. 3. Save the changes and close the form.

Administrator

This section describes the administration tasks required to use the applications. Only users with administrator privileges can perform the procedures.

Workflow to manage applications

The following workflow describes the high-level steps that you must perform to allow access to an application.

1. For supervision applications, you must configure supervision groups and summary groups. See the online help in the supervision applications.

2. For applications that can be launched from the NFM-P client, you must ensure the path to the executable of a supported browser is specified. See Setting the browser path in the NFM-P client. NOTE: In a Citrix environment in which there are multiple browsers installed and the NFM-P Java client is also installed, if no browser is specified in the NFM-P client, the default browser of the system is launched when you cross-launch an application. When you specify a browser in the NFM-P, that browser is launched. If you remove the browser configuration from the NFM-P client, the default browser of the system is used.

Maximum number of user operator positions

You can limit the number of concurrent user operator positions allowed for a user. One operator position allows for one NFM-P non-web client session and one web client session for the user. By default, the limit for the user is the limit specified for the user group to which the user belongs. Perform this procedure to set a limit that is lower than the maximum number of concurrent operator positions allowed for the user group to which the user belongs.

Limiting the number of concurrent web client sessions for a user

1. Choose Administration→Security→NFM-P User Security from the NFM-P main menu. The NFM-P User Security - Security Management (Edit) form opens.

2. Click on the Users tab. 3. Choose a user and click Properties. The User (Edit) form opens. 4. In the UI Session panel, configure the Maximum User Operator Positions Allowed

parameter to specify the maximum number of concurrent operator positions for the user, where one operator position allows for one NFM-P non-web client session and one web client session for the user. The value for the Maximum User Operator Positions Allowed parameter cannot be greater than the Maximum User Group Operator Positions Allowed parameter value of the user group to which the user belongs. NOTE: When two or more sessions of the same type are registered from a user ID, two or more operator positions are consumed.



5. Save your changes and close the forms.

NSP settings

You can create a security message that appears on the NSP Launchpad sign on page for application users.

Configuring security message

1. Sign in to NSP as an administrator. 2. Choose More→Settings from the NSP launchpad. 3. Click NSP and then NSP System Settings. 4. Configure the required parameters:

o Language o Security Statement

5. Click Save.

NFM-P settings

You can configure the following application preferences for application users:

• NFM-P settings • NFM-P color settings

NOTE: The user preferences override system settings and can be configured by the application user. Only a user with administrator privileges can configure system settings and system color settings.

Configuring NFM-P system settings

1. Sign in to NSP as an administrator. 2. Choose More→Settings from the NSP launchpad. 3. Click NFM-P and then NFM-P Settings. 4. Configure the parameters:

o Polling Time (sec) o Color row with severity in IP and Wireless applications

5. Click Save.

Configuring NFM-P colors

1. Sign in to NSP as an administrator. 2. Choose More→Settings from the NSP launchpad. 3. Click NFM-P and then NFM-P Colors. 4. Choose an alarm and a color with which to associate the alarm severity. 5. Click Save.


Linked URLs

You can link up to 20 external URLs that application users can launch to a new browser tab from the application launchpad.

Adding links to URLs to the application

1. Sign in to NSP as an administrator. 2. Choose More→Settings from the NSP launchpad. 3. Click NFM-P and then NFM-P linked URLs. 4. Configure Display Name and URL parameters. 5. Click Add.

REST API

Applications that use REST APIs publish a set of URLs that point to resources, or web services, managed by them. Each domain application documents the URLs that are available to users. These URLs can be accessed through a browser by any authorized user, including OSSs that can use them to cross-launch from their own application. See the NSP API Programmer Guide for more information.

Accessibility

You can use the keyboard to navigate and interact with most of the applications. Keyboard navigation allows you to highlight and select interactive components in the application using keystrokes instead of a mouse. The following table lists the accessibility options.

Keystroke

Action

Tab

Move to next element

Shift + Tab

Go back to previous element

Alt + down arrow Option/ALT + down arrow in Apple/OSX

Open pop-up menus, such as drop-down menus



Shift + F10 Shift + Fn + F10 in Apple/OSX

Open contextual menus

Ctrl + c Command + c in Apple/OSX

Copy

Ctrl + v Command + v in Apple/OSX

Paste

Enter

Open a folder or expandable object, such as a tile Invoke an action on a button or menu item

F8 Fn + F8 in Apple/OSX

Move over larger components or to the next page of a perspective

F5 Shift + Fn + F5 in Apple/OSX

Refresh

Shift + F1 Shift + Fn + F1 in Apple/OSX

Open tooltip

Esc

Close tooltip or menu

Arrow

When you select a tile using the Tab key, navigate across tiles in a matrix, such as the Fault Management Top Unhealthy NEs view, or matrix view in Service Supervision, using the arrow keys. Up and down arrows for navigation across menu items in an open contextual menu or pop-up menu Up and down arrows for navigation across table rows Left and right arrows for navigation across table column headers

Shift + right or left arrow

Re-order columns of a data table when applied to a selected header button



2. Service Supervision overview

About

Service Supervision allows you to monitor the health of services using KPIs, and monitor the fault status of a network. Service Supervision uses supervision groups, which can belong to one or more summary views. A supervision group is a logical set of monitored services that is specified by user-defined filters. Supervision groups can be used to partition services into distinct categories and are associated with summary views. There is no limit to the number of supervision groups to which a service can belong. Up to 50 000 services can be included in a supervision group. VLL, VPLS, MVPLS, IES, and VPRN services can be included. The criteria for monitored objects in a supervision group are based on inclusion filters. The inclusion filter is the rule on whether to include an object in a supervision group. For example, for the Wireless Supervision application, the inclusion filters used to specify the eNodeBs in a supervision group must exclude pre-provisioned NEs and all other non-eNodeB NE types to avoid misleading alarms and KPI numbers. A summary view is a collection of one or more supervision groups that provides a summarized, high-level view of a group of services. There is no limit to the number of summary views to which a supervision group can belong, but each summary view can contain only up to 200 supervision groups.

Getting Started

This section describes the tasks you must perform to use the Service Supervision application.

Creating Supervision Groups

1. Choose Administration→Supervision Settings from the NMF-P main menu. The Supervision Settings (Edit) form opens.

2. Configure the KPI History Interval (minutes) and KPI History Duration (hours) parameters.

3. Click on the Supervision Groups tab and click Create. The Supervision Group (Create) form opens.

4. Configure the parameters. The Category parameter distinguishes which monitored objects the Supervision Group manages, and to which application it applies in the Summary View. For instance, when you set the Category parameter to service, you can create inclusion filters that apply only to service properties. You can add the supervision group to a Summary View that has the Application parameter set to Service Supervision.



6. To apply an inclusion filter to the supervision group, click on the Inclusion Filters tab and click Add to select a filter.

7. To create an inclusion filter, click on the Inclusion Filters tab and click Create, then Add. Configure the filter properties.

8. To create an exclusion filter, click on the Exclusion Filters tab and click Create, then Add. Configure the filter properties.

9. Search for the filter you created and add it to the supervision group. 10. Save the changes and close the forms.

Creating Summary Views


2. Configure the KPI History Interval (minutes) and KPI History Duration (hours) parameters, if required.

3. Click the Summary View tab and click Create or choose a summary view and click Properties. The Summary View (Create|Edit) form opens.

4. Configure the required general parameters. Configure the Application parameter to select the application to which to associate the view.

5. Click on the Supervision Groups tab. 6. Click Add to select the supervision group you created. 7. You can add user groups to restrict access to the summary view to only the users that

belong to the selected user group or groups. Users with administrative privileges have access to all summary views. If no user group is assigned to a summary view, all users have access to the summary view. Click on the User Groups tab, and click Add to select one or more user groups.

8. Save the changes and close the forms.

Enabling SAP Down State Cause KPI

Because the monitoring of the operational state of all SAPs in the NFM-P can create performance concerns, you must choose only the SAPs you want to monitor by performing this procedure.

1. Choose Manage→Service→Services from the NFM-P main menu. The Manage Services form opens.

2. Choose a service and click Properties. The Service (Edit) form opens. 3. Click on the Sites tab. 4. Choose the site on which you want to monitor the operational state of access interfaces

and click Properties. The Site (Edit) form opens. 5. Enable the Monitor Access Interface Operational State parameter. 6. Save the changes and close the forms.

Purging assurance event records

Perform this procedure to purge assurance event records when the AssuranceEventLoggingTurnedOff alarm is raised. This alarm is raised when the database disk space used to log assurance events grows above the predefined threshold.



Assurance Event logging is disabled to protect the database disk space. 1. Choose Tools→Event Policies from the NFM-P main menu. The Manage Event Policies

form opens. 2. Choose the assurance.AssuranceEvent event type and click Properties. The Event

Policy - assurance.AssuranceEvent (Edit) form opens. 3. Click the More Actions button and choose Purge Event Records. The Event Policy -

assurance.AssuranceEvent (Edit) Filter form opens. 4. Click OK to purge all event records. 5. If necessary, configure the Event Retention Time (hours) to a value lower than the

default value. 6. Save the changes and close the forms.


3. Network Supervision overview

About

Network Supervision allows users to monitor the health of objects, such as NEs, cards, ports, or links, using KPIs, and monitor the fault status of a network. Network Supervision uses supervision groups, which can belong to one or more summary views. A supervision group is a logical set of monitored objects, in this case NEs and VNFs, that is specified by user-defined filters. NEs are both physical network functions and virtual network functions. Physical network functions are referred to as PNFs and virtual network functions are referred to as VNFs in the online help. Supervision groups can be used to partition objects into distinct categories and are associated with summary views. There is no limit to the number of supervision groups to which an object can belong. The criteria for monitored objects in a supervision group are based on inclusion filters. The inclusion filter is the rule on whether to include an object in a supervision group. A summary view is a collection of one or more supervision groups that provides a summarized, high-level view of a group of network objects. There is no limit to the number of summary views to which a supervision group can belong, but each summary view can contain only up to 200 supervision groups.

Getting Started

This section describes the tasks you must perform to use the Network Supervision application.

Creating Supervision Groups

1. Choose Administration→Supervision Settings from the NFM-P main menu. The Supervision Settings (Edit) form opens.


3. Click on the Supervision Groups tab and click Create. The Supervision Group (Create) form opens.

4. Configure the parameters. The Category parameter distinguishes which monitored objects the Supervision Group manages, and to which application it applies in the Summary View. For instance, when you set the Category parameter to VNF, you can create inclusion filters that apply only to VNF properties. You can add the supervision group to a Summary View that has the Application parameter set to Network Supervision.




6. To apply an inclusion filter to the supervision group, click on the Inclusion Filters tab and click Add to select a filter.

7. To create an inclusion filter, click on the Inclusion Filters tab and click Create, then Add. Configure the filter properties.

8. To create an exclusion filter, click on the Exclusion Filters tab and click Create, then Add. Configure the filter properties.

9. Search for the filter you created and add it to the supervision group. 10. Save the changes and close the forms.

Creating Summary Views


2. Configure the KPI History Interval (minutes) and KPI History Duration (hours) parameters, if required.

3. Click the Summary View tab and click Create or choose a summary view and click Properties. The Summary View (Create|Edit) form opens.

4. Configure the required general parameters. 5. Set the Application parameter to Network Supervision. 6. Click on the Supervision Groups tab. 7. Click Add to select the supervision group you created. 8. Save the changes and close the forms.

Purging assurance event records

The event timeline in applications is a log of events that is mapped over a specified period of time. You can filter the event types presented on the timeline, such as alarm events, OAM test failures, and configuration and state change events. You can use the event timeline to search for patterns in events over a period of time. Perform this procedure to purge assurance event records when the AssuranceEventLoggingTurnedOff alarm is raised. This alarm is raised when the database disk space used to log assurance events grows above the predefined threshold. Assurance Event logging is disabled to protect the database disk space.

1. Choose Tools→Event Policies from the NFM-P main menu. The Manage Event Policies form opens.

2. Choose the assurance.AssuranceEvent event type and click Properties. The Event Policy - assurance.AssuranceEvent (Edit) form opens.

3. Click the More Actions button and choose Purge Event Records. The Event Policy - assurance.AssuranceEvent (Edit) Filter form opens.

4. Click OK to purge all event records. 5. If necessary, configure the Event Retention Time (hours) to a value lower than the

default value. 6. Save the changes and close the forms.


4. Fault Management overview

About

Fault Management provides alarm monitoring, correlation, and troubleshooting for the most unhealthy NEs in the network, allowing you to filter, identify root causes, and determine the impact of alarms. Fault management is also available across many other applications in the application suite, such as the supervision applications. The Fault Management application and alarm lists in applications allow you to perform faster investigations on network problems and assessments of service impact. Advanced filtering allows you to target specific alarms based on a set of criteria.

Getting Started

This section describes procedures that are required to use the Fault Management application.

Creating an alarm e-mail policy

A user with admin privileges can create up to five policies for E-mail notifications with alarm notification rules and a list of recipients. When a filter is matched, an e-mail is sent to the list of recipients. The e-mail is a text version of a set of alarm fields, and includes a URL to the Impact Analysis tool in Fault Management in the context of the alarm. Your administrator must ensure that the outgoing SMTP e-mail server is configured. See the NFM-P System Administrator Guide. LI alarms are not sent in the e-mails. E-mails are not sent for alarm attribute change events, only for alarm creation. For example, if an alarm is created with a severity of major, and the severity is subsequently changed to critical, alarm e-mail policy filters for critical alarms will not include this alarm. When you modify the e-mail policy properties form, the e-mail counts for the e-mail policy are reset. If you select a different filter for the e-mail policy, the e-mail counts are reset. If you modify the contents of the saved filter from the alarm table, the e-mail counts for the e-mail policy are not reset.

1. Choose Administration→Alarm Settings from the NFM-P main menu. The Alarm Settings form opens.

2. Click on the E-mail tab and click Create. The Alarm Email Filter (Create) form opens. 3. Configure the Name and Max Emails Per Hour parameters. 4. Select an alarm filter. To configure and apply an advanced search filter using the filter

configuration form, see the NFM-P User Guide. 5. Click on the Users tab, then on Add to create a list of e-mail recipients. The e-mail is

sent to the e-mail address configured for the selected users. See To create an NFM-P user account in the NFM-P System Administrator Guide. You can add up to 20 users as recipients of an e-mail for each policy.



6. Save the changes and close the forms.Enabling navigation to NFM-T You must perform this procedure to enable navigation to the NFM-T web client from the Fault Management application for alarms on optical NEs that are managed by the NFM-T.

1. Log in to the main server station as the nsp user. 2. Navigate to the /opt/nsp/nfmp/server/nms/config directory 3. Create a backup copy of the nms-server.xml file. 4. CAUTION: Contact your Nokia technical support representative before you attempt to

modify the nms-server.xml file. Modifying the nms-server.xml file can have serious consequences that can include service disruption. Open the nms-server.xml file using a plain-text editor.

5. Locate the following XML tag: integration

6. Set the navigationEnabled parameter to true. By default, this parameter is set to false. navigationEnabled=true

7. Open a console window. 8. Navigate to the /opt/nsp/nfmp/server/nms/bin directory. 9. Enter the following at the prompt so that the main server reads the nms-server.xml file:

bash$ ./nmsserver.bash read_config 10. Log out of the main server and close the open console windows.


5. Analytics overview

About

The NFM-P analytics function provides insight into network infrastructure conditions, service utilization, subscriber traffic analysis, and quality of user experience using a variety of reports. The data is analyzed using business intelligence software, and is presented in graphical or tabular reports that are viewable using the Analytics application.

Analytics reports

Analytics reports enable a network operator to quickly determine the overall status of network functions and monitor trends. For example, you can identify the top subscribers in terms of overall network traffic, or based on application usage. The Analytics browser-based application allows a user to specify the reporting period, the objects on which to report, and the desired view. A report can be displayed in different formats such as a pie chart, trend diagram, or histogram. You can also export reports to files using various formats.

Analytics configuration

An operator uses a GUI or OSS client to: • Enable or disable the collection of data. • Specify the statistics classes for data aggregation. • Specify how long to retain the raw and aggregated data.

NOTE: The Safari web browser requires special configuration in order to open the Analytics application. You must ensure that the “Cookies and website data” setting on the Safari Preferences page is set to “Always allow”, or the browser cannot open the Analytics application.

Getting Started

To accommodate the significant NFM-P Analytics data throughput, storage, and analysis requirements, an NFM-P system requires the following components:

• one or more NFM-P auxiliary servers • an NFM-P auxiliary database • one or more NFM-P Analytics servers that each host the business intelligence software

and a web server See the NFM-P Planning Guide for specific information about the NFM-P system requirements for Analytics, based on the managed network size, functional requirements, and deployment scope.

Workflow to configure NFM-P analytics

This workflow outlines the sequence of actions required to configure and manage NFM-P analytics.



1. Configure and enable the collection of the required statistics from NEs. See the NFM-P Statistics Management Guide for information.

2. Configure one or more analytics rules to specify the statistics to collect. See Configuring an NFM-P analytics rule.

3. Configure one or more aggregation rules. See Configuring NFM-P analytics aggregation.

Configuring an NFM-P analytics rule

Perform this procedure to enable or disable the raw data collection, and to specify the data retention, for a statistics class to be processed using NFM-P analytics. Note: The raw data collection is enabled by default for each statistics class.

1. Choose Tools→Analytics→AA Collection Manager from the NFM-P main menu. The AA Collection Manager form opens with a list of analytics rules displayed.

2. Select the required analytics rule and click Properties. The Analytics Rule (Edit) form opens.

3. Select the Collection Enabled parameter. 4. Configure the Raw Data Retention Time (days) parameter. 5. Click OK to save your changes and close the form. 6. Close the AA Collection Manager form.

Configuring NFM-P analytics aggregation

Perform this procedure to configure the following for a statistics class to be processed using NFM-P analytics:

o level of data aggregation o retention of the aggregation data

NOTE: You can also configure the aggregation rule for a statistics class from the properties form of the analytics rule associated with the statistics class.

9. Choose Tools→Analytics→Aggregation Manager from the NFM-P main menu. The Aggregation Manager form opens with a list of aggregation rules displayed.

10. Select the required aggregation rule and click Properties. The Aggregation Rule (Edit) form opens.

11. Select the Enable Aggregation parameter. 12. Configure the Aggregation Sync Time parameter. 13. Configure the Aggregation Levels parameter. NOTE: When you select or

deselect an option, other options may be automatically selected or deselected, as the aggregation logic requires.

14. Configure the parameters in the Aggregation Retention Configuration panel to specify how long the aggregation data is stored.

15. Click OK to save your changes and close the form. 16. Close the Aggregation Manager form.


6. Golden Configuration overview

About

The Golden Configuration application takes snapshots of NE configurations, and allows you to compare the differences between two selected snapshots. The service category in the snapshots and in the audit include data about VLL, VPLS, IES, and VPRN services. The audit between two snapshots shows context-based differences for services based on the context of service entities identified by the service ID, and line-based differences for all other categories, without considering the context. NETCONF must be configured in the mediation policy for 7750 SR, 7450 ESS, and 7950 XRS NEs. FTP and Telnet must be configured on 7210 SAS NEs and on 7705 SAR NEs. See the NFM-P User Guide and NFM-P System Administrator Guide.

NE Support

The following table lists the 7210 SAS support for snapshot creation, audit and golden configuration creation and deployment.

7210 SAS variant

Releases

7210 SAS-M 7210 SAS-M 24F 2XFP 7210 SAS-M 24F 2XFP ETR

6.0 R1 to latest supported by NFM-P

7210 SAS-Mxp 8.0 R1 to latest supported by NFM-P

7210 SAS-X 6.0 R1 to latest supported by NFM-P

7210 SAS-T 12F 10T 4XFP 7210 SAS-T 12F 10T 4XFP ETR


7210 SAS-D 6F 4T 7210 SAS-D 6F 4T ETR


7210 SAS-E 6.0 R1 to latest supported by NFM-P

7210 SAS-R6 6.0 R1 to latest supported by NFM-P

7210 SAS-R12 6.0 R1 to latest supported by NFM-P

7210 SAS-Sx (24- and 48-port fiber versions)


7210 SAS-K 7.0 R4 to latest supported by NFM-P



The following table lists additional NEs that are supported by the Golden Configuration application. Note that Releases 14.0 R5 and 14.0 R6 are not supported for 7750 SR, 7950 XRS and 7450 ESS NEs.

NE

Supported from NE Release

Snapshot creation and audit supported up to NE Release

Supports creation and deployment of golden configuration

7450 ESS 13.0 R1 Snapshot creation and audit only

Latest supported by NFM-P

—

7705 SAR 5.0 R1 Snapshot creation and audit


—

7750 SR 13.0 R1 Snapshot creation and audit only


—

7950 XRS 13.0 R1 Snapshot creation and audit only


—

7705 SAR-H 5.0 R1 Snapshot creation and audit only


—

Golden configuration of 7210 SAS

The Golden Configuration application allows you to take snapshots of 7210 SAS NE configurations, create golden configurations from these snapshots by parameterizing the snapshot configurations, and deploy the golden configurations to other 7210 SAS NEs. Consider the following when creating snapshots and deploying them to 7210 SAS NEs:

• Golden configurations can be created and deployed only between 7210 SAS NEs of the same release.

• You must ensure that FTP and Telnet are properly configured in the mediation policy in the NFM-P.

• You must ensure that security parameters, such as SNMP community strings and user security parameters, are identical on the NE on which the golden configuration is created and on the NE to which the golden configuration is deployed.

• If the NE is discovered in SNMPv3, the SNMP authentication for the user must be properly re-configured after a successful deployment (when the deployment state is Configured), so that the NFM-P re-syncs the NE. See the NFM-P System Administrator Guide for more information.

• You must ensure that the values for the read-version and write-version values for the hash-control parameter under config system security are the identical. For example: configure system security hash-control read-version 2 write-version 2 or configure system security hash-control read-version 1 write-version 1 See the appropriate device documentation for more information.

• You must configure the System Name, System IP, Management IP, Management SAP, and Connection Port parameters on the NE to which the golden configuration is deployed.


• You cannot deploy golden configurations to an NE that has a management type (in-band/out-of-band) or mode (network/access-uplink) that is different from the NE from which the golden configuration has been created.

• A golden configuration that is created from an NE with an IPv4 configuration cannot be deployed on a NE with an IPv6 configuration, and vice versa. If a deployment attempt is made, the deployment may fail and a loss of configuration on the destination NE may occur.

• Nokia recommends that you back up the NE configuration of the destination NE using the NFM-P before the golden configuration is deployed, to ensure the possibility of restoration in the event of a deployment failure.

• During the deployment of a golden configuration, if the configuration is not accepted by the NE to which the golden configuration is being deployed, a deployment failure may occur and a partial configuration may result on the NE. The original pre-deployment configuration of the NE may be lost.

• Golden configuration creation and deployment can be performed only from and to an in-band managed 7210 SAS NE that is configured in network mode if the in-band management is done through the network interface or port that is configured under the router configuration in the NFM-P.

• Users with administrative privileges can parametrize NE parameters in a golden configuration. See Customizing NE-specific configurations in a golden configuration.

Getting Started

Before you can create NE snapshots, a user with administrator privileges must configure NETCONF in the mediation policy and enable NETCONF access on NEs that support NETCONF. On the 7705 SAR and 7210 SAS, you must ensure that Telnet and FTP are properly configured in the mediation policy.

Enabling NETCONF access on an NE

1. Enable the user and password on NETCONF: 1. Choose Administration→Mediation from the NFM-P main menu. 2. Click on the Mediation Security tab. 3. Choose the mediation policy for the NEs and click Properties. The Mediation

Policy (Edit) form opens. 4. In the NETCONF panel, configure the User Password parameter.

2. Open a CLI session on the device. 3. Enter the following commands in the order shown:

configure system netconf no shutdown configure system security user username access netconf



Customizing NE-specific configurations in a golden configuration

You can generalize an NE-specific configuration on a source NE when you create a golden configuration by parameterizing the source NE configuration, then customizing the configuration to suit the target NE when deployed. NE-specific information is identified using regular expressions in an XML file and replaced by parameters in a golden configuration. You can replace these parameters with values in the Golden Configuration application when you deploy the golden configuration to another NE. Consider the following parameterization guidelines:

• No validation is performed on the format of the GcParams.xml file. If you include invalid entries or tags in the GcParams.xml file, only the entries up until the invalid entry are processed and the rest is ignored by the Golden Configuration application.

• You can parameterize only the configuration displayed in admin display-config. • You can use regular expressions in a parameterization. For example:

where:

o createRegex is a regular expression to identify NE specific information, such as NE IP address

o deployRegex is a regular expression to validate the user-entered parameter values on the deployment form

o parameterName is a variable name to be assigned to the NE specific information identified by createRegex. The same name is used as the parameter name on the deployment form.

o defaultValue is the default value that appears for the parameter on the deployment form

o regexVariableDefinitions is a collection of <regexVariableDefinition> tags o regexVariableDefinition — createRegex and deployRegex can be variables

whose values are defined in the regexVariableDefinition. This regexVariableDefinition can be used throughout the GcParams.xml file. Braces ({ and }) must not be used in the regexVariableDefinition. For example:


• Regular expressions beginning and ending with braces ({ and }) are considered

variables and must have a corresponding definition. • Regex and parameter name combinations must be unique throughout the

GcParams.xml file. Multiple <regex>..</regex> entries with the same <parameterName>..</parameterName> are not supported. The following example is not supported:



• Parameters that require spaces within the tags are not supported. For example, for the

destination MAC parameter: dst-mac aa:bb:cc:dd:12:21 ff:ff:ff:ff:ff:ff only the MAC address aa:bb:cc:dd:12:21 can be defined as a parameter, and not the mask ff:ff:ff:ff:ff:ff.

• You cannot parameterize parameters for specific identifiers. In the following example, the parameterization must apply to all Epipe descriptions, and cannot apply to a specific Epipe.

• Specific identifiers cannot be stated in the <cliPath> tag. For example, the following is

not supported because the specific identifier, 10, is stated in the <cliPath> tag.

• If you want to deploy the golden configuration on an NE in a different subnet from the

NE from which the golden configuration was created, you must parameterize the static route with two mandatory CLI paths, and any number of optional CLI paths. For example:


The mandatory and any optional parameters must be filled with the correct details of the subnet in which the destination NE exists. If the source NE does not have a static route, and the destination NE requires a static route to be reachable, you must create a placeholder static route and parameterize with the values corresponding to the destination NE before deployment. Otherwise, the destination NE becomes unreachable after you deploy the golden configuration.

• If NEs are configured in network mode with in-band management, and if one or more SAPs are created on a port on the source NE, which is also the connection port containing the management SAP on the destination NE, you must ensure that the parameterization of the SAPs is correct before you create the golden configuration. Otherwise, replication of these SAPs may fail on the destination NE.

• Parameters that have mandatory default configurations, for example, Dot1P classification under QoS, cannot be changed. Because specific parameterization is not supported, if you attempt to parameterize any user-created, or non-default, entity such as the description parameter, a configuration error upon deployment may occur and the NE may appear with a partial configuration.



• If one or more SAPs are created on a port on the source NE (NE from which the golden configuration is created), which is also the connection port (containing the management SAP) on the destination NE (NE to which the golden configuration is to be deployed), you must ensure the correct parameterization of the SAPs before you create the golden configuration. Otherwise, replication of these SAPs may fail on the destination NE. For example, if the source NE with SAP 1/1/3:2.3 and destination NE with management SAP on port 1/1/3, you must ensure proper parameterization of the SAPs in GcParams.xml before you create the golden configuration.

• If you want to parameterize multiple CLI paths with the same regular expressions, you can use multiple <cliPath> entries under one <gcParam> tag. The following example defines parameters for two CLI paths with the specific regular expression:

The parameterization is successful if a matching configuration is found in any one of the multiple CLI paths for each of the regular expressions.

• To turn up and manage the 7210 SAS successfully in the NFM-P after deploying a golden configuration, a template for the connection port, which includes the port mode and port encapsulation type, is maintained in the golden configuration. You must re-apply other configurations that are absent on the template on the destination connection port after deployment.

Parameterizing an NE-specific configuration Perform the following procedure to parameterize an NE-specific configuration by adding parameters to the GcParams.xml file located on the NFM-P server before you create a golden configuration with the Golden Configuration application.

1. Log in to the main server station as the nsp admin user. 2. Navigate to the /opt/nsp/nfmp/server/nms/config/goldenconfig directory 3. Create a backup copy of the GcParams.xml file. 4. Open the GcParams.xml file using a plain-text editor such as vi and add golden

configuration parameters as required. 5. Save the changes and close the file.


7. Link Utilization overview

About

The Link Utilization application provides graphical views of link utilization statistics for IP and MPLS interfaces within a specific administrative domain. The views allow you to assess how efficiently your network is managing traffic, both historically and in near real-time. Statistics and other data are provided for the application using functions in the NFM-P. You must enable collection of the required performance statistics for the NEs or objects that participate in the Link Utilization application. The NFM-P performs calculations on the performance statistics to produce an average rate of utilization for a given time period. The average rate is displayed as a percentage of the available bandwidth on the link. The result is displayed graphically and in the List of interfaces table.

Current and historical utilization

The link utilization application allows you to view current or historical utilization. Current utilization is displayed by default, and shows the latest statistics for which a calculated percentage is available. The time period is based on the polling interval configured in the MIB Entry policy used for statistics collection. Historical utilization is available when you select a date and time that is in the past, in the Set Data Retrieval Time dialog. The utilization shown in the application is for the hour that ends at the selected time. The NFM-P delays historical utilization calculations by half an hour, to ensure that all statistics have been flushed to the database. NOTE: For historical utilization, Nokia recommends that you select a time that is at least one hour in the past. If the selected time is too recent, statistics collection and calculations may not be complete. In such cases, NFM-P systems that deploy an auxiliary DB may show no results, and systems with no auxiliary DB may show current rather than historical utilization.

Troubleshooting to confirm statistics collection

For IP and MPLS utilization, a very low utilization rate may show as zero per cent. In such a case, to confirm that the application is functioning properly, you can view the List of interfaces table in the lower part of the display. If the table contains results and shows a Time of Computation, then interfaces are appropriately managed for statistics collection. To confirm values for very low utilization rates, open the properties form for the IP or MPLS interface in the NFM-P GUI, and view the Statistics tab. Note that link utilization calculations use the actual port speed as a reference for interface utilization percentages.



Getting Started

This section outlines the sequence of actions required to use the Link Utilization application.

Workflow to configure Link Utilization

1. Overwrite the default partitioning in the NFM-P database. See Overwriting the default database partitioning size.

2. Enable performance statistics collection for IP interfaces, MPLS interfaces, and LSPs by setting the Administrative State parameter of the MIB entry policy to Up and setting the Polling Interval parameter to less than one hour:

o IP interfaces—for a MIB statistics policy, or for the IP Interface Stats (Routing Management: General) monitored statistics class on the Statistics tab of the Network Interface properties form, configure the policy for the MIB entry vRtrIfStatsEntry.

o MPLS interfaces—for a MIB statistics policy, or for the MPLS Interface Stats (Path/Routing Management: MPLS) monitored statistics class on the Statistics tab of the MPLS Interface properties form, configure the policy for the MIB entry vRtrMplsIfStatEntry.

o LSPs—for a MIB statistics policy, or for the MPLS LSP Egress Stats (Path/Routing Management: MPLS) monitored statistics class on the Statistics tab of the Dynamic LSP properties form, configure the policy for the MIB entry vRtrMplsLspStatisticsEntry.

See Statistics collection configuration in the NFM-P Statistics Management Guide for more information about how to configure performance statistics collection.

3. For LSP utilization, on the Accounting tab of the Dynamic LSP properties form for each LSP, assign an accounting policy and set the Administrative State to Up. See “To configure a Dynamic LSP” in the NFM-P User Guide for more information.

4. For LSP utilization, create an LSP path monitor for each LSP. See “To monitor a dynamic LSP” in the CPAM User Guide for more information about how to configure performance statistics collection.

5. Configure retention times for historical LSP utilization statistics. A statistics event occurs each time an object is polled and statistics are collected. For LSP utilization statistics, an event policy defines the retention times for statistics in the NFM-P database. For longer retention times, ensure that the system has sufficient physical disk space. See “To monitor a dynamic LSP” in the CPAM User Guide for more information.

Overwriting the default database partitioning size

Database Partitioning

The Link Utilization application provides database partitioning with the following default values: CPAM_STATS_DEFAULT_DB_SIZE_IN_MBYTE = 20480 CPAM_STATS_MIN_DB_SIZE_IN_MBYTE = 500 CPAM_STATS_MAX_DB_SIZE_IN_MBYTE = 61440

1. Log in to the main server station as the nsp user. 2. Navigate to the /opt/nsp/nfmp/server/nms/config directory


3. Create a backup copy of the nms-server.xml file. 4. CAUTION: Contact your Nokia technical support representative before you attempt to

modify the nms-server.xml file. Modifying the nms-server.xml file can have serious consequences that can include service disruption. Open the nms-server.xml file using a plain-text editor.

5. To overwrite the default size, add the following lines to the nms-sever.xml file. <cpamUtilizationStats cpamStatisticDbSizeInMBytes = "<size_in_bytes>"/> For example: <cpamUtilizationStats cpamStatisticDbSizeInMBytes = "1024"/>

6. Save and close the nms-server.xml file. 7. Open a console window. 8. Navigate to the /opt/nsp/nfmp/server/nms/bin directory. 9. Enter the following at the prompt:

bash$ ./nmsserver.bash read_config The main server reads the nms-server.xml file.

10. Log out of the main server and close the open console windows.

Troubleshooting statistics collection

For IP and MPLS utilization, a very low utilization rate may show as zero per cent. See Troubleshooting to confirm statistics collection for more information.



8. Subscriber Management overview

About

The Subscriber Management application KPI Monitor view displays the NEs within a specified supervision group or site. Each NE object in the view displays abbreviated KPI information, and the view can be expanded to display detailed KPI and alarm information for individual NEs. The Troubleshoot view displays session-related information for subscriber hosts and user equipment (UE) devices connected to an access point (AP In order for the Subscriber Management application to display information, statistics collection must be configured in the NFM-P. For the Subscriber Management application released with the former 5620 SAM Release 14.0 R5 or later, statistics collection is configured automatically the first time the Subscriber Management application is launched. Automatic statistics configuration is supported on the following NE versions:

• 7750 SR - Release 10.0 and later • 7750 SR - Release 10.0 and later • 7750 SR - Release 10.0 and later • 7750MG - Release 5.0 and later

Getting Started

Statistics polling is only enabled for MIB entry policies applicable to NE types and versions, managed for default and non-default NE MIB statistics policies. The Subscriber Management application scans for newly-managed NEs, and enables applicable MIB entry policies every 30 seconds. Statistics polling is not disabled when an NE is un-managed. NFM-P users may change the administrative state and polling interval of MIB entry policies through the Java GUI or OSSI. This means that polling may be disabled for a policy, or its polling interval changed after it is enabled by the Subscriber Management application. If an NE is un-managed and re-managed, polling is enabled on all applicable policies and the polling interval set to 15 minutes. If you are working with NE versions that are older than the versions listed above, you must configure statistics collection manually in the NFM-P, as described in "Statistics collection configuration" in the NFM-P Statistics Management Guide. Enable collection for the following MIB entries:


KPI Monitor perspective

Troubleshoot perspective

sgiCpuUsage

SLAProfInstStatsEntry

sgiMemoryUsed

SLAProfInstEgrPStatsEntry

tmnxSubMgmtMdaStatsEntry

SLAProfInstEgrQStatsEntry

tmnxSubMgmtSystStatsEntry

SLAProfInstIngPStatsEntry

tmnxWlanGwIsaMemberEntry

SLAProfInstIngQStatsEntry

wlanGwStatsGroup

SubIngPStatsEntry

tmnxDhcpServerStatsEntry

SubscriberIngQStatsEntry

tmnxDhcpSvrPoolStatsEntry

SubscriberEgrQStatsEntry

tmnxDhcpServerStats6Entry

SubEgrOverrideCounterEntry

tmnxDhcpsPoolStats6Entry

Network Services Platform - Help · PDF fileNetwork Services Platform Release 17.6...

Documents

Transcript of Network Services Platform - Help · PDF fileNetwork Services Platform Release 17.6...