5620 SAM SERVICE AWARE MANAGER 14.0 R9. Applications Guide. 3HE AAAG-TQZZA Issue 1 November 2017

Transcription

1 SERVICE AWARE MANAGER Applications Guide 3HE AAAG-TQZZA

2 Legal notice 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 Nokia. 2 3HE AAAG-TQZZA

3 Contents About this document...6 Part I: Getting started Safety information Structure of safety statements What s new? Overview What s new for applications in, Release Part II: applications applications Overview...17 applications overview Overview applications Procedures to use applications To set the browser path in the client applications REST API Overview...25 REST API overview Overview...26 Part III: applications administration applications administration Overview...29 applications administration overview Overview Workflow to manage applications...31 applications administration procedures To add access permissions for applications to a user group To limit the number of concurrent web client sessions for a user To add links to URLs to the application dashboard To change the order of application icons on the dashboard and menu HE AAAG-TQZZA 3

4 6 Assurance monitoring and troubleshooting Overview...37 Fault management Introduction to fault management Fault Management procedures To create an alarm policy To enable navigation to the 1350 Optical Management System...40 Supervision applications Introduction to supervision applications Workflow to manage supervision applications supervision management procedures To configure a supervision group To configure a summary view To enable SAP Down State Cause KPI for the Service Supervision application...46 Logging events Event timeline overview To purge assurance event records...47 Analytics Introduction to Analytics Workflow to configure analytics analytics procedures To configure a analytics rule To configure analytics aggregation...51 Link Utilization Introduction to link utilization statistics Workflow to configure Link Utilization Link Utilization procedures To overwrite the default database partitioning size...54 Subscriber Management Subscriber Management overview Configuration Overview...59 Golden configuration overview Golden configuration HE AAAG-TQZZA

5 Golden configuration procedures Procedures To enable NETCONF access on an NE To customize NE-specific configurations in a golden configuration HE AAAG-TQZZA 5

6 About this document Purpose The Applications Guide provides information for users about how to manage the 5620 SAM applications and the required tasks that must be performed by a system administrator. Document organization This guide contains the following volumes: Getting started what s new for the current release in the for applications applications contains information about applications, including the following: applications overview user preferences REST API overview Applications administration contains information about administrative functions, including the following: user security domain-specific configurations Safety information For your safety, this document contains safety statements. Safety statements are given at points where risks of damage to personnel, equipment, and operation may exist. Failure to follow the directions in a safety statement may result in serious consequences. Document support Customer documentation and product support URLs: Customer Documentation Welcome Page Technical support How to comment Documentation feedback 6 3HE AAAG-TQZZA

7 Part I: Getting started Overview Purpose This part provides an overview of the latest features in the for applications. Contents Chapter 1, Safety information 9 Chapter 2, What s new? 11 3HE AAAG-TQZZA 7

8 8 3HE AAAG-TQZZA

9 Safety information 1 Safety information 1.1 Structure of safety statements Overview This topic describes the components of safety statements that appear in this document General structure Safety statements include the following structural elements: CAUTION Lifting hazard SAMPLE Lifting this equipment by yourself can result in injury due to the size and weight of the equipment. Always use three people or a lifting device to transport and position this equipment. [ABC123] Item Structure element Purpose 1 Safety alert symbol Indicates the potential for personal injury (optional) 2 Safety symbol Indicates hazard type (optional) 3 Signal word Indicates the severity of the hazard 4 Hazard type Describes the source of the risk of damage or injury 5 Safety message Consequences if protective measures fail 6 Avoidance message Protective measures to take to avoid the hazard 7 Identifier The reference ID of the safety statement (optional) 3HE AAAG-TQZZA 9

10 Structure of safety statements Signal words The signal words identify the hazard severity levels as follows: Signal word DANGER WARNING CAUTION NOTICE Meaning Indicates an extremely hazardous situation which, if not avoided, will result in death or serious injury. Indicates a hazardous situation which, if not avoided, could result in death or serious injury. Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury. Indicates a hazardous situation not related to personal injury. 10 3HE AAAG-TQZZA

11 What s new? 2 What s new? 2.1 Overview Purpose This chapter provides an overview of the latest features in the for the use and administration of applications Contents 2.1 Overview What s new for applications in, Release What s new for applications in, Release General information This section highlights new features in the, Release 14.0, for applications, and provides pointers into the documentation for more information. New features and enhancements for this release are also described in the following guides: User Guide LTE RAN User Guide Optical User Guide VSAP User Guide NFV Solutions Guide 5650 CPAM User Guide Application API Developer Guide The Release Description provides Committed and Candidate feature lists for the entire 14.0 Release. The Planning Guide provides scaling and deployment guidelines Maintenance releases Some maintenance releases may not be listed in this section, either because no new features are introduced or the features introduced do not require documentation. 3HE AAAG-TQZZA 11

12 What s new for applications in, Release What s new for applications in Release 14.0 R7 Table 1 Feature ID applications features in Release 14.0 R7 Feature or function Description See Network management features SAM Apply same look and feel to all reports Reports in the Analytics application have been updated to reduce space occupied by non-graphic elements. Analytics Report Catalog SAM Analytics platform enhancements The Analytics application supports deployment of custom reports. SAM Support for new features in Analytics The Analytics application supports a number of new statistics including: New Firewall statistics for TCP Validation for 7750 MG, available in the Security Gateway Dashboard(SAM-86195) ISA Performance Dashboard and IPDR ISA Performance record now support the 7750 MG for Overload and Flow exhaust (SAM-86197) Support for AA TCP Optimization for 7750 MG (SAM-86199) What s new for applications in Release 14.0 R5 Table 2 Feature ID applications features in Release 14.0 R5 Feature or function Description See General application features - Launch the Java client from the application dashboard You can launch the Java client from the applications dashboard and from the main menu on each application. - SAM Subscriber Management - enable statistics/kpis The Subscriber Management application automatically configures statistics collection in the for supporting NE versions in the KPI and Troubleshoot views. Subscriber Management (p. 56) SAM Support 250 concurrent web application sessions The number of concurrent web application sessions supported has been raised from 150 to 250 for the Fault Management and Service Supervision applications. Table 6, applications (p. 21) SAM Accessibility - Improve keyboard access in Fault Management You can use the keyboard to navigate and interact with most of the applications. Table 5, Accessibility options (p. 19) Assurance features 12 3HE AAAG-TQZZA

13 What s new for applications in, Release 14.0 Table 2 applications features in Release 14.0 R5 (continued) Feature ID Feature or function Description See - Access control for Service Supervision summary view Configuration features You can add user groups to summary views to restrict access to summary views to only users that belong to a selected user group. 6.9 To configure a supervision group (p. 43) SAM Support for 7210 SAS The GC Snapshot Manager supports the snapshot creation, audit and golden configuration creation and deployment of 7210 SAS NEs NE support (p. 60) What s new in applications Release 14.0 R3 Table 3 Feature ID applications Release 14.0 R3 features Feature or function Description See Network management features Analytics reports based on AA Cflowd data The Analytics application has reports and dashboards such as the following, which are based on AA Cflowd data: Top N devices TCP performance DNS performance Top N HTTP host domains IP family usage VoIP MOS, including forensics OTT VoIP usage Analytics Report Catalog SAM SAM SAM Add Two Way Delay Reports for Y.1731 per Network and Node Analytics AA firewall IPDR Analytics network and subscriber dashboard Analytics reporting for CFM OAM tests has been added to the. The reporting includes the Y.1731 test results for two-way delay tests, which provide information on jitter, loss, and delay. All reports are per Class of Service (CoS). The Analytics application includes AA firewall dashboards for the top session filter, policer, and anomaly drop counts, and for the top session filter and policer admit counts. The Analytics application includes a network and subscriber dashboard. The dashboard contains dashlets for router bandwidth, subscriber activity, and per-router distribution of applications and application groups. 3HE AAAG-TQZZA 13

14 What s new for applications in, Release 14.0 Table 3 applications Release 14.0 R3 features (continued) Feature ID Feature or function Description See SAM Analytics report enhancements The Analytics application includes a number of enhancements that include: Analytics application an updated display layout with additional descriptive information a wider range of report criteria the ability to save report criteria for re-use during subsequent runs a drill-down function Configuration features SAM SAS-K deployment in the GC Snapshot Manager You can create a golden configuration of a 7210 SAS-K and deploy the configuration to other 7210 SAS-K NEs. You can generalize an NE-specific configuration when creating a golden configuration by parameterizing the configuration to suit another NE at the time of deployment. 7.5 To customize NE-specific configurations in a golden configuration (p. 63) applications Release 14.0 R1 Table 4 Feature ID applications Release 14.0 R1 features Feature or function Description See Assurance features SAM Support 150 concurrent web application sessions The number of concurrent web application sessions supported has been raised from 50 to SAM Integration and crosslaunch of 1350 OMS A system that manages a 1350 OMS as an EM system supports the integration of 1350 OMS and alarm information. This enables the display of 1350 OMS alarm information in the 5620 SAM Fault Management application, and enables a operator to open the 1350 OMS web GUI directly from the application using a contextual menu option To enable navigation to the 1350 Optical Management System (p. 40) SAM Analytics landing page The Analytics application opens to a landing page that provides the following: a high-level view of the analytics functions a video tutorial An operator can use the landing page to become familiar with the application, and then choose to suppress the landing page in subsequent application sessions. 14 3HE AAAG-TQZZA

15 Part II: applications Overview Purpose This part provides information about applications. Contents Chapter 3, applications 17 Chapter 4, applications REST API 25 3HE AAAG-TQZZA 15

16 16 3HE AAAG-TQZZA

17 applications 3 applications 3.1 Overview Purpose This chapter describes the applications Contents 3.1 Overview 17 applications overview Overview applications Procedures to use applications To set the browser path in the client 23 3HE AAAG-TQZZA 17

18 Overview applications overview 3.2 Overview General information The provides network management functions using browser-based web applications. The use of the applications is intended mainly for network fault monitoring and troubleshooting purposes. The applications are external to the client and do not require a local client installation Browser connections For information on which browsers the applications are supported, see the Planning Guide. 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. See Table 6, applications (p. 21), for the number of supported concurrent application sessions for each application. You can use the following URLs to access the dashboard, from which you can launch all supported applications. For a non-secured connection: where server is the hostname or IP address of a main server For a secured connection: where server is the hostname or IP address of a main server Note: In a redundant deployment, if the primary and standby main servers are up, you can connect to either main server to open an application User preferences You can configure the following user preferences for applications from the applications dashboard: User preferences Polling Time (seconds) Language 18 3HE AAAG-TQZZA

19 Overview Show Severity Color On Entire Row User preferences override system settings and can be configured by application user. Only a user with administrator privileges can configure system settings and system color settings. See Application preferences (p. 30) for more information. Other application preferences can be configured from within the specific application. See the online help for the application 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. Table 5 Accessibility options Keystroke Tab Shift + Tab Alt + down arrow Option/ALT + down arrow in Apple/OSX Shift + F10 Shift + Fn + F10 in Apple/OSX Ctrl+c Command +cinapple/osx Ctrl+v Command +vinapple/osx Enter F8 Fn + F8 in Apple/OSX F5 Shift + Fn + F5 in Apple/OSX Shift+F1 Shift + Fn + F1 in Apple/OSX Esc Action Move to next element Go back to previous element Open pop-up menus, such as drop-down menus Open contextual menus Copy Paste Open a folder or expandable object, such as a tile Invoke an action on a button or menu item Move over larger components or to the next page of a perspective Refresh Open tooltip Close tooltip or menu 3HE AAAG-TQZZA 19

20 applications Table 5 Accessibility options (continued) Keystroke Arrow Shift + right or left arrow Action 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 Re-order columns of a data table when applied to a selected header button Online help Each application provides online help in the form of tours. You can access the online help for the applications by clicking on the?or choosing the tour menus from the More... menu in the application toolbar. The application tours provide high-level navigational information about the application, window, or perspective. The How To tours provide task-based information. 3.3 applications General information Table 6, applications (p. 21), describes the applications and lists the URLs from which you can access the individual applications. You can also open certain applications from a 5620 SAM GUI client; others allow you to open the GUI client from the application. You must configure the Browser Path parameter in your User Preferences to launch a specific browser from the client. See 3.5 To set the browser path in the client (p. 23) for more information. 20 3HE AAAG-TQZZA

21 applications Table 6 applications Application and URL Description Domain Maximum number of concurrent application sessions Launch 5620 SAM GUI client from application Launch application from 5620 SAM GUI client Analytics http(s)://server/analytics 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 PSS Equipment View http(s)://server/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 http(s)://server/faultmanagement 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 GC Snapshot Manager http(s)://server/gcsnapshotmanager Allows you to create multiple snapshots of an NE configuration, view snapshots, and compare two selected snapshots IP core/edge 50 Inventory Management http(s)://server/dcinventory 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 Link Utilization http(s)://server/utilizationstats Provides IP, MPLS, and aggregated utilization statistics for interfaces within a specific domain IP core/edge 4 3HE AAAG-TQZZA 21

22 applications Table 6 applications (continued) Application and URL Description Domain Maximum number of concurrent application sessions Launch 5620 SAM GUI client from application Launch application from 5620 SAM GUI client Network Supervision http(s)://server/networksupervision Monitors the health of physical NEs and virtual NFs using pre-defined KPIs and alarms to provide a dashboard for monitoring the overall health of NEs in the network. IP core/edge NFV 50 Power Management Dashboard http(s)://server/xrspowermanagement Provides detailed information about the power usage of 7950 XRS NEs in the network 7950 XRS 50 Service Navigator http(s)://server/dcservicenavigator Provides a dashboard of the operational health of the service objects in a specified administrative domain Data center Nuage VSAP 50 Service Supervision http(s)://server/servicesupervision Provides alarm and KPI monitoring on user-defined service views and groups IP core/edge Mobile backhaul 250 Subscriber Management Dashboard http(s)://server/subscribermanagement VNF Manager http(s)://server/vnfmanager Provides NE and subscriber KPI information, alarm monitoring and correlation, and troubleshooting functions for subscriber hosts Provides VNF lifecycle management functionality for an NFV network Subscriber 5 NFV 50 Wireless Supervision http(s)://server/wirelesssupervision Provides alarm monitoring based on user-defined views and groups for an LTE RAN network Wireless (LTE RAN) HE AAAG-TQZZA

23 Procedures to use applications Table 6 applications (continued) Application and URL Description Domain Maximum number of concurrent application sessions Launch 5620 SAM GUI client from application Launch application from 5620 SAM GUI client Wireless NE Views http(s)://server/wirelessneviews Provides a visual representation of enodeb hardware, links, states and fault status for a single NE. Wireless (LTE RAN) Procedures to use applications Purpose The following procedures describe tasks that you must perform using a client to enable application use on the client station. See Part III: applications administration for administrative tasks that must be performed by a administrator, such as creating user groups, configuring supervision settings, configuring NE access, enabling statistics collection, and configuring system preferences. 3.5 To set the browser path in the client General information Steps You must configure the Browser Path parameter in your User Preferences to launch a specific browser from the client. Note: In a Citrix environment in which there are multiple browsers installed and the Java client is also installed, if no browser is specified in the client, the default browser of the system is launched when you cross-launch an application. When you specify a browser in the Java client, that browser is launched. If you remove the browser configuration from the client, the default browser of the system is used. 1 2 Choose Application User Preferences from the main menu. The User Preferences form opens. Click Browse to choose the.exe file from the appropriate application folder. 3HE AAAG-TQZZA 23

24 To set the browser path in the client 3 Save the changes and close the form. END OF STEPS 24 3HE AAAG-TQZZA

25 applications REST API 4 applications REST API 4.1 Overview Purpose This chapter provides a general overview of the applications REST API Contents 4.1 Overview 25 REST API overview Overview 26 3HE AAAG-TQZZA 25

26 Overview REST API overview 4.2 Overview Published URLs 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. To view a dashboard of all the available applications: http(s)://<host> where host is the hostname or IP address where the is installed. HTTP(S) must be used when the system is secure. To view the published URLs of an application: http(s)://<host>/<app_name>/api-docs where host is the hostname or IP address that hosts the application and app_name is the name of the application. For example, Fault Management applications REST API See the Application API Developer Guide for more information about REST API and the applications that use it. 26 3HE AAAG-TQZZA

27 Part III: applications administration Overview Purpose Contents This part provides information about the tasks that must be performed by a user with admin privileges. Chapter 5, applications administration 29 Chapter 6, Assurance monitoring and troubleshooting 37 Chapter 7, Configuration 59 3HE AAAG-TQZZA 27

28 28 3HE AAAG-TQZZA

29 applications administration 5 applications administration 5.1 Overview Purpose This chapter describes the administration tasks required to use applications. Only users with administrator privileges can perform the procedures described in this chapter Contents 5.1 Overview 29 applications administration overview Overview Workflow to manage applications 31 applications administration procedures To add access permissions for applications to a user group To limit the number of concurrent web client sessions for a user To add links to URLs to the application dashboard To change the order of application icons on the dashboard and menu 34 3HE AAAG-TQZZA 29

30 Overview applications administration overview 5.2 Overview Browser compatibility See the Planning Guide for the browsers on which the applications are supported. Each application user must ensure that the browser path is configured in the user preferences. See 3.5 To set the browser path in the client (p. 23) for more information Access permissions Access to the applications is controlled through user groups. The default admin user group can access all applications. Note: On installations where there is a web proxy between the web clients and the web server, it is possible that all of the web clients appear to the server as having the same source IP address the IP address of the proxy. For the to be able to differentiate between web clients, each web client must use a unique user account name. Failure to do so may cause session issues when users cross-launch between the Java client and the web client in a proxy network. See the System Administrator Guide for more information about how to create users and user groups Application preferences You can configure the following application preferences for application users: System preferences Polling Time (seconds) Default Language Show Severity Color On Entire Row System color settings 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 Linked URLs You can link up to 20 external URLs that application users can launch to a new browser tab from the application dashboard. See 5.6 To add links to URLs to the application dashboard (p. 33) for more information. 30 3HE AAAG-TQZZA

31 Workflow to manage applications 5.3 Workflow to manage applications Purpose The following workflow describes the high-level steps that you must perform to allow access to a application Stages Create user groups and users, and grant permissions to a user group to access the applications. See the System Administrator Guide for more information about how to create user groups and users. See 5.4 To add access permissions for applications to a user group (p. 32) and 5.5 To limit the number of concurrent web client sessions for a user (p. 32) for information about how to add access permissions for applications and limit the number of web sessions for users and user groups. For supervision applications, you must configure supervision groups and summary groups. See 6.9 To configure a supervision group (p. 43). For applications that can be launched from the client GUI, you must ensure the path to the executable of a supported browser is specified. See 3.5 To set the browser path in the client (p. 23). Note: In a Citrix environment in which there are multiple browsers installed and the 5620 SAM Java client is also installed, if no browser is specified in the client, the default browser of the system is launched when you cross-launch an application. When you specify a browser in the Java client, that browser is launched. If you remove the browser configuration from the client, the default browser of the system is used. 3HE AAAG-TQZZA 31

32 To add access permissions for applications to a user group applications administration procedures 5.4 To add access permissions for applications to a user group Steps Choose Administration Security User Security from the main menu. The User Security - Security Management (Edit) form opens. Click on the User Groups tab. Choose a user group and click Properties. The User Group (Edit) form opens. Click on the Web Applications tab and enable the applications for which you want to grant access to the user group. Note: If you change the access permissions to a web application when a user in a user group is logged in to the web application, the changes are not effective until the user logs out and logs in again. 5 Save your changes and close the forms. END OF STEPS 5.5 To limit the number of concurrent web client sessions for a user 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 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 Steps 1 Choose Administration Security User Security from the main menu. The User Security - Security Management (Edit) form opens. 32 3HE AAAG-TQZZA

33 To add links to URLs to the application dashboard Click on the Users tab. Choose a user group and click Properties. The User (Edit) form opens. 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 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. END OF STEPS 5.6 To add links to URLs to the application dashboard Steps Log in to the application as an administrator. Choose Preferences Linked URL(s) Settings from the application dashboard. The Linked URL(s) Settings form opens. Click on the + button. The Add Linked URL(s) form opens. Configure Display Name and URL parameters. To add an icon to the URL drop-down list, configure the Icon parameter. Enter <favicon>.ico, where <URL> is the location of the icon, and <favicon> is the name of the icon. 3HE AAAG-TQZZA 33

34 To change the order of application icons on the dashboard and menu 6 7 Click Add. Click Done. END OF STEPS 5.7 To change the order of application icons on the dashboard and menu Steps Log in to the main server station as the samadmin user. Open a console window. Navigate to the /opt/5620sam/server/nms/web/tomcat/webapps/root/ds/app_sorting directory. Open the app_order.data.json file using a plain-text editor such as vi. Modify the order of the application groups. The default order is: [ { "groups": [ "common", "ip", "wireless", "optics", "dc", "other" ] } ] 34 3HE AAAG-TQZZA

35 To change the order of application icons on the dashboard and menu 6 Save and close the file. END OF STEPS 3HE AAAG-TQZZA 35

36 To change the order of application icons on the dashboard and menu 36 3HE AAAG-TQZZA

37 Assurance monitoring and troubleshooting 6 Assurance monitoring and troubleshooting 6.1 Overview Purpose This chapter describes the administration tasks for monitoring and troubleshooting using the applications Contents 6.1 Overview 37 Fault management Introduction to fault management Fault Management procedures To create an alarm policy To enable navigation to the 1350 Optical Management System 40 Supervision applications Introduction to supervision applications Workflow to manage supervision applications supervision management procedures To configure a supervision group To configure a summary view To enable SAP Down State Cause KPI for the Service Supervision application 46 Logging events Event timeline overview To purge assurance event records 47 Analytics Introduction to Analytics Workflow to configure analytics analytics procedures To configure a analytics rule To configure analytics aggregation 51 3HE AAAG-TQZZA 37

38 Overview Link Utilization Introduction to link utilization statistics Workflow to configure Link Utilization Link Utilization procedures To overwrite the default database partitioning size 54 Subscriber Management Subscriber Management overview HE AAAG-TQZZA

39 Introduction to fault management Fault management 6.2 Introduction to fault management General information The Fault Management application is a web-based application that 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. 6.3 Fault Management procedures Purpose The following procedures describe general application fault management procedures. 6.4 To create an alarm policy Purpose Steps A administrator can create up to five policies for notifications with alarm notification rules and a list of recipients. When a filter is matched, an is sent to the list of recipients. The is a text version of a set of alarm fields, and includes a URL to the Impact Analysis tool in Fault Management application in the context of the alarm. Note: You must have permissions to access the Fault Management application. Contact your system administrator for more information. Your administrator must ensure that the outgoing SMTP server is configured. See the System Administrator Guide for more information. LI alarms are not sent in the s. s 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 policy filters for critical alarms will not include this alarm. When you modify the policy properties form, the counts for the policy are reset. If you select a different filter for the policy, the counts are reset. If you modify the contents of the saved filter from the alarm table, the counts for the policy are not reset. 1 Choose Administration Alarm Settings from the main menu. The Alarm Settings form opens. 3HE AAAG-TQZZA 39

40 To enable navigation to the 1350 Optical Management System Click on the tab and click Create. The Alarm Filter (Create) form opens. Configure the Name and Max s Per Hour parameters. Select an alarm filter. To configure and apply an advanced search filter using the filter configuration form, see the User Guide for more information. Click on the Users tab, then on Add to create a list of recipients. The is sent to the address configured for the selected users. See To create a user account in the System Administrator Guide for more information. You can add up to 20 users as recipients of an for each policy. Save the changes and close the forms. END OF STEPS 6.5 To enable navigation to the 1350 Optical Management System OMS navigation from Fault Management You must perform this procedure to enable navigation to the 1350 OMS web client from the Fault Management application for alarms on optical NEs that are managed by the 1350 OMS Steps Log in to the main server station as the samadmin user. Navigate to the /opt/5620sam/server/nms/config directory. Create a backup copy of the nms-server.xml file. 40 3HE AAAG-TQZZA

41 To enable navigation to the 1350 Optical Management System 4 CAUTION Service Disruption Contact your Nokia technical support representative before you attempt to modify the nmsserver.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 Set the navigationenabled parameter to true. By default, this parameter is set to false. navigationenabled=true Save and close the nms-server.xml file. Open a console window. Navigate to the /opt/5620sam/server/nms/bin directory. Enter the following at the prompt: bash$./nmsserver.bash read_config The main server reads the nms-server.xml file. Log out of the main server and close the open console windows. END OF STEPS 3HE AAAG-TQZZA 41

42 Introduction to supervision applications Supervision applications 6.6 Introduction to supervision applications Overview Supervision applications allow users to monitor the health of objects, such as services, cards, ports, or links, using KPIs, and monitor the fault status of a network. Supervision applications use supervision groups, which can belong to one or more summary views. Supervision groups A supervision group is a logical set of monitored objects that is specified by user-defined filters. 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 that an object can belong to. For the Service Supervision application, up to services can be included in a supervision group. VLL, VPLS, MVPLS, IES, and VPRN services can be included. Summary views 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 that a supervision group can belong to, but each summary view can contain only up to 200 supervision groups. 6.7 Workflow to manage supervision applications Purpose The following workflow describes the high-level steps that you must perform to use supervision applications Stages Configure supervision groups. See 6.9 To configure a supervision group (p. 43). Configure summary views. See 6.10 To configure a summary view (p. 45). For the Service Supervision application, enable the SAP Down State Cause KPI. See 6.11 To enable SAP Down State Cause KPI for the Service Supervision application (p. 46). 42 3HE AAAG-TQZZA

43 supervision management procedures 6.8 supervision management procedures Purpose Perform the following procedures to configure parameters and objects for supervision applications. 6.9 To configure a supervision group Purpose Steps Supervision groups include monitored objects. The type of monitored object depends on the application. For most applications, the monitored objects are NEs. For the Service Supervision application, the monitored objects are services. For the Network Supervision application, the monitored objects are NEs and VNFs. 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 Choose Administration Supervision Settings from the main menu. The Supervision Settings (Edit) form opens. Configure the KPI History Interval (minutes) and KPI History Duration (hours) parameters. Click on the Supervision Groups tab and click Create. The Supervision Group (Create) form opens. 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. For the Wireless Supervision application, the Category parameter must be set to NE Access for enodeb supervision. The Supervised Alarms Severities parameter does not apply to enodeb supervision. All enodeb alarms are displayed in the Wireless Supervision application regardless of severity. 3HE AAAG-TQZZA 43

44 To configure a supervision group 5 To apply an inclusion filter to the supervision group, click on the Inclusion Filters tab and click Add to select a filter. 6 To create an inclusion filter: 1. Click on the Inclusion Filters tab and click Create. 2. Click Add. 3. Configure the filter properties: Choose an item from the Attribute drop-down menu. Choose an item from the Function drop-down menu. Configure the Value parameter. Choose a Boolean Operator from the Operators drop-down menu, if applicable. Click Add. Note: For the Service Supervision application: inclusion filters will include only VLL, VPLS, MVPLS, IES, and VPRN services up to services can be included in a supervision group To add an exclusion filter: 1. Click Add. 2. Configure the filter properties: Choose an item from the Attribute drop-down menu. Set the Function to NOT EQUAL. Configure the Value parameter. Choose a Boolean Operator from the Operators drop-down menu, if applicable. Click Add. Save the changes and close the forms. Search for the filter you created and click OK. The filter is added to the supervision group. Save the changes and close the forms. END OF STEPS 44 3HE AAAG-TQZZA

45 To configure a summary view 6.10 To configure a summary view Steps Choose Administration Supervision Settings from the main menu. The Supervision Settings (Edit) form opens. Configure the KPI History Interval (minutes) and KPI History Duration (hours) parameters, if required. Click the Summary View tab and click Create or choose a summary view and click Properties. The Summary View (Create Edit) form opens. Configure the required general parameters. Configure the Application parameter to select the application to which to associate the view. Click on the Supervision Groups tab. Click Add to select the supervision group you created in 6.9 To configure a supervision group (p. 43). If you are creating a summary view for the Service Supervision application, 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. Save the changes and close the forms. END OF STEPS 3HE AAAG-TQZZA 45

46 To enable SAP Down State Cause KPI for the Service Supervision application 6.11 To enable SAP Down State Cause KPI for the Service Supervision application Purpose Steps Because the monitoring of the operational state of all SAPs in the can create performance concerns, you must choose only the SAPs you want to monitor by performing this procedure Choose Manage Service Services from the main menu. The Manage Services form opens. Choose a service and click Properties. The Service (Edit) form opens. Click on the Sites tab. Choose the site on which you want to monitor the operational state of access interfaces and click Properties. The Site (Edit) form opens. Enable the Monitor Access Interface Operational State parameter. Save the changes and close the forms. END OF STEPS 46 3HE AAAG-TQZZA

47 Event timeline overview Logging events 6.12 Event timeline overview Overview 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 To purge assurance event records Purpose Steps 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 Choose Tools Event Policies from the main menu. The Manage Event Policies form opens. Choose the assurance.assuranceevent event type and click Properties. The Event Policy - assurance.assuranceevent (Edit) form opens. Click the More Actions button and choose Purge Event Records. The Event Policy - assurance.assuranceevent (Edit) Filter form opens. Click OK to purge all event records. If necessary, configure the Event Retention Time (hours) to a value lower than the default value. When all the alarms that are related to the disk space issue are cleared, set the Administrative State parameter to Up. 3HE AAAG-TQZZA 47

48 To purge assurance event records 7 Save the changes and close the forms. END OF STEPS 48 3HE AAAG-TQZZA

49 Introduction to Analytics Analytics 6.14 Introduction to Analytics Analytics function The 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 browser-based Analytics application. See Chapter 3, applications, for information about gaining access to the Analytics application. 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. To accommodate the significant Analytics data throughput, storage, and analysis requirements, a system requires the following components: one or more auxiliary servers a auxiliary database one or more Analytics servers that each host the business intelligence software and a web server See the Planning Guide for specific information about the system requirements for Analytics, based on the managed network size, functional requirements, and deployment scope 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 A 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. 3HE AAAG-TQZZA 49

50 Workflow to configure analytics 6.15 Workflow to configure analytics Stages This workflow outlines the sequence of actions required to configure and manage analytics Configure and enable the collection of the required statistics from NEs. See the Statistics Management Guide for information. Configure one or more analytics rules to specify the statistics to collect. See 6.17 To configure a analytics rule (p. 49). Configure one or more aggregation rules. See 6.18 To configure analytics aggregation (p. 51) analytics procedures Purpose The following describes general analytics procedures. You do not require administrator privileges to perform the following procedures To configure a analytics rule Steps Note: The raw data collection is enabled by default for each statistics class. 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 analytics Choose Tools Statistics Analytics Manager from the main menu. The Analytics Manager form opens with a list of analytics rules displayed. Select the required analytics rule and click Properties. The Analytics Rule (Edit) form opens. Configure the Collection Enabled parameter. 50 3HE AAAG-TQZZA

51 To configure analytics aggregation Configure the Raw Data Retention Time (days) parameter. Click OK to save your changes and close the form. Close the Analytics Manager form. END OF STEPS 6.18 To configure analytics aggregation Purpose Steps Perform this procedure to configure the following for a statistics class to be processed using 5620 SAM analytics: level of data aggregation 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 Choose Tools Statistics Aggregation Manager from the main menu. The Aggregation Manager form opens with a list of aggregation rules displayed. Select the required aggregation rule and click Properties. The Aggregation Rule (Edit) form opens. Select the Enable Aggregation parameter. Configure the Aggregation Sync Time parameter. 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. 3HE AAAG-TQZZA 51