prm_lte_ioms_ldap_parameters.pdf

LTE Radio Access, Rel. RL40, Operating Documentation, Issue 01

LTE iOMS LDAP Parameters

DN0990203

Issue 03AApproval Date 2012-07-25

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN0990203


Id:0900d80580969809Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2012. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN0990203 3



Table of contentsThis document has 31 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Parameter Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Parameter Tool introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Browsing configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3 Modifying configuration data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4 Modifying attributes of configuration data objects . . . . . . . . . . . . . . . . . 17

3 LDAP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1 OMS Northbound interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2 OMS Southbound interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3 OMS process trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.5 Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.6 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.7 Software management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.8 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.9 User management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.10 Overload control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.11 Other parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 DN0990203



List of figuresFigure 1 Parameter Tool main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

DN0990203 5



List of tablesTable 1 OMS Northbound interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 20Table 2 OMS Northbound interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 20Table 3 OMS process trace parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Table 4 Fault management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 5 Configuration management parameters . . . . . . . . . . . . . . . . . . . . . . . . 21Table 6 Performance management parameters . . . . . . . . . . . . . . . . . . . . . . . . 22Table 7 Software management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 8 Security management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 9 User management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 10 Overload control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Table 11 Other parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6 DN0990203


Id:0900d805809791bcConfidential

Summary of changes

Summary of changesChanges between document issues are cumulative.

Changes between issues 03 (2011-12-16, RL40) and 03A (2012-07-25, RL40)

Parameter Tool introduction (2.1)

• References to standalone Parameter Tool have been removed as there is no stand-alone Parameter Tool anymore.

Modifying attributes of configuration data objects (2.4)

• Note about values validation has been added to d Enter the new value..

OMS process trace (3.3)

• Modified parameter: ClusterRoot/OMS/System/TraceConfig/Any/dwLogSizeInKB

• Removed parameters: ClusterRoot/OMS/System/TraceConfig/Any/dwMode1, ClusterRoot/OMS/System/TraceConfig/Any/szFilePath

Fault management (3.4)

• New parameter: ClusterRoot/AlarmMgmt/AlarmProcessors/AlarmProcessor1/Default/fsUseBlockingForExternals

Software management (3.7)

• New parameter: ClusterRoot/OMS/System/RemoteSW/maxQuantityPassiveSWSets

Security management (3.8)

• New parameter: ClusterRoot/OMS/SW/SS_Nwi3Certificate/Nwi3Certificate/CertExpiryAlarmTimer

• Modified parameters: ClusterRoot/NWI3/mediator/fsnwi3PrimaryCipherSuite, ClusterRoot/NWI3/mediator/fsnwi3SecondaryCipherSuite, ClusterRoot/NWI3/mediator/fsnwi3N3CFId=X/fsnwi3PrimaryTLSRequireLevel, ClusterRoot/NWI3/mediator/fsnwi3N3CFId=X/fsnwi3SecondaryTLSRequireLevel

• Removed parameters: ClusterRoot/NWI3/mediator/fsnwi3PrimaryCacertFile, ClusterRoot/NWI3/mediator/fsnwi3SecondaryCacertFile

Changes between issues 02 (2011-09-26, RL30) and 03 (2011-12-16, RL40)

OMS overload control (2.4)

• Chapter Overload control has been added to the document.

DN0990203 7

LTE iOMS LDAP Parameters Summary of changes


Miscellaneous parameters (2.10)

• The ClusterRoot/OMS/Platform/SS_Planwagen/CMPlanManager/DeleteTemporaryFiles has been added.

• The ClusterRoot/OMS/Platform/SS_Planwagen/CMPlanManager/DeleteTemporaryFilesTimePeriod has been added.

Changes between issues 01A (2011-06-23, RL20) and 02 (2011-09-26, RL30)

Performance management parameters (2.3)

• ClusterRoot/OMS/OMSRNC/SS_RNCPM/OMSMeaHandler/PMOverloadCancelThreshold has been renamed to ClusterRoot/OMS/OMSRNC/SS_RNCPM/OMSMeaHandler/PMOverloadAlarmCancelThreshold

8 DN0990203



Summary of changes

DN0990203 9

LTE iOMS LDAP Parameters Introduction

Id:0900d8058091bff4Confidential

1 IntroductionLightweight Directory Access Protocol (LDAP) is a directory based database. LDAP's structure is fairly similar to Windows registry. In OMS (Operation and Management Server) almost all configuration data is stored in LDAP. Some of the data can be config-ured by the user, but most of the data in LDAP is modified in the installation phase.

For more information, see Parameter Tool.

10 DN0990203


Id:0900d805809185b9Confidential

Parameter Tool

2 Parameter Tool

2.1 Parameter Tool introductionParameter Tool is a tool that enables access to the runtime configuration data objects stored in the Lightweight Directory Access Protocol (LDAP) directory. It provides users with a tree-like view to the data structures in the parameter management (PMGMT) LDAP directory.

Parameter Tool allows the user to browse, search, add, delete, and modify configuration data objects and attributes stored in the LDAP directory. The tool also allows the user to view and update online help text information related to the objects and their attributes in the LDAP directory tree. Importing and editing LDAP data interchange format (LDIF) files is also possible.

The network elements (NEs) typically have dedicated tools for the more complex con-figuration management tasks. In these cases, Parameter Tool must not be used.

Parameter Tool can be operated either via the Element Manager. To access the Param-eter Tool the user account must belong to the _nokfsuiexternalldaplogin user group.

For accessing Parameter Tool via the Element Manager the user needs to log into the Application Launcher (AL) and launch the Parameter Tool application from the AL main window.

Figure 1 Parameter Tool main window

Parameter Tool modesThere are three modes available:

• Normal mode is the default operation mode. In normal mode, all modifications sent to the PMGMT server are done according to the notification subscription information. The notification subscription information shows, for example, which branches in LDAP are handled by some target applications and which operations (controls) are supported by the target applications.

DN0990203 11

LTE iOMS LDAP Parameters Parameter Tool


• Extended mode allows the user to select how modifications are handled (that is, by which PMGMT control the LDAP request is extended). This mode is provided for troubleshooting purposes.

• Forced mode is actually a generic LDAP mode, where modifications are not vali-dated by the applications and not activated to the applications either. Only the PMGMT server is updated. Forced mode is provided for troubleshooting purposes.

12 DN0990203


Id:0900d8058061cb59Confidential

2.2 Browsing configuration informationPurposeYou can browse configuration information and view entries (or managed object instances stored in the directory) and their attributes.

SummaryYou have two ways of reaching the target entry:

1. Use direct navigation in the main window entry tree.2. Use the Find dialog.

Steps

1 Use direct navigation.

Steps

a Browse to the target entry.In the main window’s left pane entry tree, use the arrow keys in the keyboard or the left mouse button.

b Select the target entry.You can now view the attributes of the target entry in the main window’s right pane attribute list.

2 Use Find.

Steps

a Choose the entry in which you want to perform the search.In the main window’s left pane entry tree, select the starting point for the search. If you do not know which fragment the target entry belongs to, choose the root entry node.

b Select Entry > Find.The Find dialog opens.

c Specify the target entry.

1. In the Criteria pane's search expression field, specify the naming attribute of the target entry.or

2. In the Options list, choose the type of the searched item.

d Click Find.

e Select the resulting entry.In the Result pane's search result list, select the resulting entry.

DN0990203 13


Id:0900d8058061cb59Confidential

f View the entry's attributes.By clicking Locate and Close, the Find dialog closes, and the entry is automatically selected in the main view's left pane entry tree. You can now see the entry's attri-butes in the attribute list in the right pane.

Expected outcomeThe target entry's attributes are visible in the main window's attribute list in the right pane.

14 DN0990203


Id:0900d805808c6b4fConfidential

2.3 Modifying configuration data objectsPurposeYou can modify or edit (add, delete, rename, copy, or move) entries in the LDAP direc-tory.

Before you startCheck that Parameter Tool is up and running.

Parameter Tool allows you to make any changes to the configuration, but it can verify the correctness of the operation only when the operation manipulates a single configu-ration object at a time. When the desired operation is more complex, which means that it involves manipulating multiple objects in a transactional manner, Parameter Tool cannot verify the correctness of the operation or ensure system consistency in all possible cases. Network elements typically have dedicated tools for the more complex configuration management tasks. Do not use Parameter Tool in these cases.

Steps

1 Add a new entry.

Steps

a Select the target entry.

b Create new entries (sibling, child and copy).

• To create a new entry as a sibling entry (of the selected entry in the node hier-archy), select “Entry j New”.

• To create a new entry as a child entry (of the selected entry in the node hierar-chy), select “Entry j New Child”.

• To create a new entry, which is a copy of the selected entry, select “Entry j New Copy”.

Your new entry is added.

c Enter the object class.Enter the object class (New, New Child), or the naming attribute (New Copy).

The Add New Entry dialog opens.

d Enter the new entry's attribute values.Check that the new entry contains all the necessary attributes and that all of the sug-gested attribute values are valid. Invalid values are highlighted with a red back-ground.

e Add the new entry to the server.Click OK. The new entry with the specified attribute set is added to the server.

2 Move or copy an entry to a different place in the directory.

Steps

a Select the source entry.

DN0990203 15



b Move the source entry.Drag the source entry to the target entry node in the entry tree, then drop it.

c Select an operation.

• Copy to Child: copies the source entry as a child node of the target entry in the entry tree hierarchy.

• Move to Child: moves the source entry as a child node of the target entry in the entry tree hierarchy. The move deletes the source entry after copying it.

• Copy to Sibling: copies the source entry as a sibling node of the target entry in the entry tree hierarchy.

• Move to Sibling: moves the source entry as a sibling node of the target entry in the entry tree hierarchy. The move deletes the source entry after copying it.

• Replace: Replaces the target entry with the source entry. • Cancel: cancels the drag-and-drop operation.

3 Rename an entry.

Steps


b Select rename.Select “Entry j Rename”.

c Select a new naming attribute.From the list below the selected entry in the entry tree, select a new naming attribute. If nothing can be selected, you have to type a new naming attribute. After you have selected or typed the new valid naming attribute, your modification is sent to the server.

You can cancel the operation by pressing ESC before selecting or typing the new naming attribute.

4 Delete an entry.

Steps

a Select the target entry.You can include multiple entries in the set to be deleted by holding the CTRL key down while selecting the entries with the mouse from the entry tree.

b Select Entry > Delete.The Confirm Operation dialog opens.

c Select the deletion confirmation type.Separate confirmation is asked for each selected entry:

• to accept the deletion, click Delete This • to accept all of the deletions, click Delete All • to reject the deletion, click Keep This

16 DN0990203



• to cancel the deletion, click Cancel.No actual deletion is performed in this step.

d Delete the confirmed entries.If you accept any of the deletions the confirmed entries are deleted from the server.

5 Undo an entry operation.

SummaryYou can undo an entry operation for an entry that has a deleted state.

Steps

a Select the deleted target entry.

b Select Entry > Undo Delete.The deleted entry is recreated.

DN0990203 17



2.4 Modifying attributes of configuration data objectsPurposeYou can modify (add, delete, rename) attributes and their values.

Before you startCheck that Parameter Tool is up and running.

Parameter Tool allows you to make any changes to the configuration, but it can verify the correctness of the operation only when the operation manipulates a single configu-ration object at a time. When the desired operation is more complex, which means that it involves manipulating multiple objects in a transactional manner, Parameter Tool cannot verify the correctness of the operation or ensure system consistency in all possible cases. Network elements typically have dedicated tools for the more complex configuration management tasks. Do not use Parameter Tool in these cases.

Steps

1 Rename an attribute name.

Steps


b Select the attribute.In the main window's right pane attribute list, select the attribute to be modified.

c Select rename.Select “Attribute j Rename” or double-click the attribute name column.

d Select a new name.Select a new name from the list below the selected attribute, or type a new name for the attribute and press ENTER or click on any other cell.

You can cancel the operation by pressing ESC before pressing ENTER or clicking on any other cell.

2 Modify the value of an attribute.

Steps


b Select the attribute.In the main window's right pane attribute list, select the attribute to be modified.

c Modify the value.Select “Attribute j Modify value” or double-click the attribute value column.

d Enter the new value.Select a value from the list, or type a new one and press ENTER or click on any other cell.

18 DN0990203




g The values are validated on server application side, so in case you entered invalid value a default will be used instead after validation. Note that Parameter Tool will not validate the value immediately when you enter it and will not inform you that the value is invalid.

3 Add a new attribute.

Steps


b Select an item from the Attribute menu.Select “Attribute j New”. An attribute with an initial name Enter name and an initial value Enter value is added to the attribute list.

c Select a new name.Select a new name from the list below the selected attribute.

d Enter the new value.Select a new value from the list, or type a new one and press ENTER or click on any other cell to send it to the server.


4 Delete an attribute.

Steps


b Select the attribute.

c Select Attribute > Delete.The Confirm Operation dialog opens.

d Confirm the attribute selections.Separate confirmation is asked for each selected attribute:

• to accept the deletion, click Delete This • to accept all the deletions, click Delete All • to reject the deletion, click Keep This • to cancel the deletion, click Cancel.No actual deletion is performed in this step.

e Delete the confirmed attributes.If you accept any of the deletions, and you did not click Cancel, the confirmed entries are deleted from the server.

DN0990203 19



5 Copy attributes to the clipboard.

Steps


b Select the attribute.

c Copy the selected attributes.Select “Attribute j Copy”. The selected attributes are copied to the clipboard.

6 Paste attributes from the clipboard.

Steps


b Select any attribute of the entry.

c Paste the selected attributes.Select “Attribute j Paste”. The copied attributes are added to the target entry’s attri-bute set.

7 Undo an attribute operation.

SummaryYou can undo an attribute operation, if an attribute has previous values. In this case, the previous values are activated and become the new active values.

Steps


b Select the attribute.In the right pane’s attribute list, select the attribute you are targeting for the undo operation.

c Select Attribute > Undo.

Expected outcomeThe attribute has been successfully modified.

20 DN0990203


Id:0900d805809648fdConfidential

LDAP parameters

3 LDAP parameters

3.1 OMS Northbound interface

3.2 OMS Southbound interface

3.3 OMS process trace

Attribute Description Value

ClusterRoot/

OMS/

System/

Network/

CUAccess/

OMS/

szIPAddress

OMS FTP server IP The values are only updated by the zmodifyOMSSettings script.

Table 1 OMS Northbound interface parameters


ClusterRoot/

OMS/

System/

Network/

CUAccess/

OMSS/

szIPAddress

OMS southbound server IP The value is updated only by the zmodifyNetworkSettings script.

Table 2 OMS Northbound interface parameters


ClusterRoot/

OMS/

System/

TraceConfig/

Any/

dwFlags

This parameter defines whether process trace logging is active.

default = 0possible values = 0, 3, 110 = trace OFF

3 = trace ON in synchronous mode, write to file

11 (0xB) = trace ON in synchronous mode, write to file, syslog writings included in the trace logs

Table 3 OMS process trace parameters

DN0990203 21

LTE iOMS LDAP Parameters LDAP parameters


3.4 Fault management

3.5 Configuration management

ClusterRoot/

OMS/

System/

TraceConfig/

Any/

dwLogSizeInKB

This parameter defines the maximum size of trace log.

trace log file size in kilobytes

default = 15360 kB

maximum value: 65535 kB


Table 3 OMS process trace parameters (Cont.)


ClusterRoot/

AlarmMgmt/

AlarmProcessors/

AlarmProcessor1/

Default/

fsUseBlockingForExternals

The parameter decides if alarm blocking from the controller is handled by OMS alarm system.

default = true

Table 4 Fault management parameters


ClusterRoot/

OMS/

OMSPlatform/

SS_Planwagen/

CMPlanManager/

DeleteTemporaryFiles

This parameter indicates whether OMS should delete tem-porary plan files after the related operation has been completed.

Note that when the value is set to 0, OMS does not clean down-loaded or uploaded files after the related operation has been com-pleted. This can result in insuffi-cient free disk space and OMS instability. Therefore, it is recom-mended to set the value to 0 only for a limited time.

default = 10 = OMS does not delete tempo-rary files after the related opera-tion has been completed. The files are deleted after the time specified in DeleteTemporaryFilesTimePeriod

1 = OMS deletes temporary files after the related operation has been completed

Table 5 Configuration management parameters

22 DN0990203



LDAP parameters

3.6 Performance management

ClusterRoot/

OMS/

OMSPlatform/

SS_Planwagen/

CMPlanManager/

DeleteTemporaryFilesTimePeriod

This parameter defines the period of time used for deletion of temporary files from OMS disk.

default = 3 hours

possible values = 1-6 hours


Table 5 Configuration management parameters (Cont.)


ClusterRoot/

OMS/

OMSPlatform/

SS_GenericPM/

GenericPMCtrl/

PMFileBufferAlarmSetThreshold

This parameter sets threshold for buffer build-up alarms. If the number of unacknowledged OMeS files reaches this limit, an alarm is triggered.

default = 100possible values = 0 - N files

ClusterRoot/

OMS/

OMSPlatform/

SS_GenericPM/

GenericPMCtrl/

PMFileBufferAlarmSetDelay

This parameter sets delay for buffer buildup alarms, that is, the duration in seconds that the number of unac-knowledged OMeS files must be over the threshold.

default = 180possible values = 0 - N seconds

0 = alarm is set immediately when PMFileBufferAlarmSetThreshold limit is exceeded

ClusterRoot/

OMS/

OMSPlatform/

SS_GenericPM/

GenericPMCtrl/

PMFileBufferAlarmCancelThreshold

This parameter cancels alarm threshold for buffer build-up alarms. If the alarm is active and the number of files decreases to this limit or below, the alarm is can-celed.

default = 10possible values = 0 - N files

ClusterRoot/

OMS/

OMSPlatform/

SS_GenericPM/

GenericPMCtrl/

PMFileBufferAlarmEnabled

This parameter disables/enables XML-file buffer build-up alarm.

default = 1possible values = 0, 10 = alarm disabled

1 = alarm enabled

Table 6 Performance management parameters

DN0990203 23



ClusterRoot/

OMS/

OMSPlatform/

SS_GenericPM/

OMSNMSFWriter/

BackupEnabled

When this parameter is activated, the copies of measurement files are stored into the /var/opt/OMSftproot/xmlfilesBU directory.

Note that only the OMeS files produced by OMS are notified to NetAct and stored in the backup directory.

default = 0possible values = 0, 10 = copying disabled

1 = copying enabled

ClusterRoot/

OMS/

OMSRNC/

SS_RNCPM/

OMSMeaHandler/

PMOverloadAlarmEnabled

This parameter disables/enables measurement processing overload alarm.

default = 1possible values = 0, 10 = alarm disabled

1 = alarm enabled

ClusterRoot/

OMS/

OMSRNC/

SS_RNCPM/

OMSMeaHandler/

PMOverloadAlarmWindow

This parameter averages window for measurement processing overload alarm. OMSMeaHandler measures data processing time over this time window and if the pro-cessing time exceeds PMOverloadAlarmSetThreshold percentage of total time, an alarm is triggered. The same window is used for canceling the alarm based on PMOverloadAlarmCancelLimit

default = 120possible values = 30 - N minutes

ClusterRoot/

OMS/

OMSRNC/

SS_RNCPM/

OMSMeaHandler/

PMOverloadAlarmSetThreshold

This parameter sets alarm thresh-old for measurement data process-ing overload alarms. If the processing time percentage of total time exceeds the threshold calcu-lated over PMOverloadAlarmWindow duration, an alarm is set.

default = 60 %possible values = 1 - 100 %

ClusterRoot/

OMS/

OMSRNC/

SS_RNCPM/

OMSMeaHandler/

PMOverloadAlarmCancelThreshold

This parameter cancels alarm threshold for measurement data processing overload alarm. If overload alarm is active and the processing time in percentage of total time goes below this threshold calculated over PMOverloadAlarmWindow dura-tion, the alarm is canceled.

default = 50 %possible values = 1 - 100 %


Table 6 Performance management parameters (Cont.)

24 DN0990203



LDAP parameters

3.7 Software management

3.8 Security management

ClusterRoot/

OMS/

OMSRNC/

SS_RNCPM/

OMSMeaHandler/

BTSFTPAlarmSetDelay

This parameter defines the minimum time between consecu-tive failed file transfer operations that trigger alarm.

default = 30possible values = 0 - 1000 minutes

0 = alarm is set immediately after the first failure

ClusterRoot/

OMS/

OMSPlatform/

SS_MeasurementHandling/

OMSBTSFileReader/

DeleteFilesAfterRead

When this parameter is activated, copies of measurement files received from base stations are stored into the /var/opt/Nokia/OMS/OMSRNC/SS_RNCPM/btsfilesBU folder.

default = 10 = files are not deleted and copies remain in the folder

1 = files are deleted perma-nently after transfer (not copied to the folder)


Table 6 Performance management parameters (Cont.)


ClusterRoot/

OMS/

System/

RemoteSW/

maxQuantityPassiveSWSets

Defines the value of possible passive SW sets. OMS limits the number of installed SW sets as passive because of storage disk capacity limits.

default = 3possible values = 1 - 3

Table 7 Software management parameters


ClusterRoot/

NWI3/

mediator/

fsnwi3N3CFId=X/

fsnwi3LDAPConnectionType

LDAP connection type default = TLSpossible values = TLS, TLS_OR_PLAIN_TEXT

Table 8 Security management parameters

DN0990203 25



ClusterRoot/

NWI3/

mediator/

fsnwi3N3CFId=X/

fsnwi3PrimaryTLSRequireLevel

the level at which the server cer-tificates are checked by the client

default = LDAP_OPT_X_TLS_DEMANDpossible values = LDAP_OPT_X_TLS_NEVER, LDAP_OPT_X_TLS_HARD, LDAP_OPT_X_TLS_DEMAND, LDAP_OPT_X_TLS_TRY, LDAP_OPT_X_TLS_ALLOWLDAP_OPT_X_TLS_NEVER = slapd does not ask the server for a certificate

LDAP_OPT_X_TLS_ALLOW = the client certificate is requested. If no certificate is provided, the session proceeds normally. If a bad certifi-cate is provided, it is ignored and the session proceeds normally.

LDAP_OPT_X_TLS_TRY = the client certificate is requested. If no certificate is provided, the session proceeds normally. If a bad certifi-cate is provided, the session is immediately terminated.

LDAP_OPT_X_TLS_HARD and LDAP_OPT_X_TLS_DEMAND = the client certificate is requested. If no certificate is provided, or a bad certificate is provided, the session is immediately terminated.

ClusterRoot/

NWI3/

mediator/

fsnwi3PrimaryUseTLS

specifies whether to use TLS connection to the external NetAct CUAA LDAP

default = quantumpossible values = true, false, quantum

ClusterRoot/

NWI3/

mediator/

fsnwi3PrimaryCipherSuite

the OpenSSL cipher allowed for connecting securely to the external NetAct CUAA LDAP

default = ALL:+MEDIUM:!LOW:!MD5:!EXP:!KRB5:!DES:!ADH


Table 8 Security management parameters (Cont.)

26 DN0990203



LDAP parameters

ClusterRoot/

NWI3/

mediator/

fsnwi3N3CFId=X/

fsnwi3SecondaryTLSRequireLevel

the level at which the server cer-tificates are checked by the client

default = LDAP_OPT_X_TLS_DEMANDpossible values = LDAP_OPT_X_TLS_NEVER, LDAP_OPT_X_TLS_HARD, LDAP_OPT_X_TLS_DEMAND, LDAP_OPT_X_TLS_TRY, LDAP_OPT_X_TLS_ALLOWLDAP_OPT_X_TLS_NEVER = slapd does not ask the server for a certificate

LDAP_OPT_X_TLS_ALLOW = the client certificate is requested. If no certificate is provided, the session proceeds normally. If a bad certifi-cate is provided, it is ignored and the session proceeds normally.

LDAP_OPT_X_TLS_TRY = the client certificate is requested. If no certificate is provided, the session proceeds normally. If a bad certifi-cate is provided, the session is immediately terminated.

LDAP_OPT_X_TLS_HARD and LDAP_OPT_X_TLS_DEMAND = the client certificate is requested. If no certificate is provided, or a bad certificate is provided, the session is immediately terminated.

ClusterRoot/

NWI3/

mediator/

fsnwi3SecondaryUseTLS

specifies whether to use TLS connection to the external NetAct CUAA LDAP

default = quantumpossible values = true, false, quantum

ClusterRoot/

NWI3/

mediator/

fsnwi3SecondaryCipherSuite

the OpenSSL cipher allowed for connecting securely to the external NetAct CUAA LDAP

default = ALL:+MEDIUM:!LOW:!MD5:!EXP:!KRB5:!DES:!ADH



DN0990203 27



3.9 User management

ClusterRoot/

OMS/

SW/

SS_Nwi3Certificate/

Nwi3Certificate/

CertExpiryAlarmTimer

The parameter defines how many days in advance the alarm is set before the EE-certificate or CA-certificate expiry.

default = 14 days

possible values = 1 - 365 days

step = 1

ClusterRoot/

OMS/

System/

Network/

TLS/

TLSModeFT

security mode for file transfer Forced, Probing, Off

ClusterRoot/

OMS/

System/

Network/

TLS/

TLSModeOM

security mode for BTS O&M I/F Forced, Probing, Off




ClusterRoot/

NWI3/

security/

fsnwi3NEAccountUsername

connection username to NetAct's remote LDAP

LDAP is for CUAA parameters, handled by NetAct

username defined in NetAct

string value (with DN path)

ClusterRoot/

NWI3/

security/

fsnwi3NEAccountPassword

connection password to NetAct's remote LDAP

LDAP is for CUAA parameters, handled by NetAct

password defined in NetAct

string value

ClusterRoot/

NWI3/

security/

fsnwi3ActiveN3CF

Description Number (DN) of the currently active mediator configu-ration, maintained by the Nwi3Adapter

Table 9 User management parameters

28 DN0990203



LDAP parameters

ClusterRoot/

NWI3/

mediator/

fsnwi3initialRegistrationPassword

Password correspond-ing to fsnwi3initialRegistrationUsername

The default password is neregn, but it should be changed for security reasons.

ClusterRoot/

NWI3/

mediator/

fsnwi3initialRegistrationUsername

Username which is used for binding to NetAct LDAP when the NE account is not set, or is not working. It can be either in short form or in form of full DN. In the latter case, the value of fsnwi3PrimaryPeopleRootDN is appended when connecting to the external LDAP.

The default username is neregn, but it should be changed for security reasons.

ClusterRoot/

NWI3/

mediator/

fsnwi3N3CFId=X/

fsnwi3takeIntoUseNext

informs CUAA whether to use the given sub-fragment or not

possible values = true, falsetrue = the given subfragment is active

false = the given subfragment is inactive

ClusterRoot/

NWI3/

mediator/

fsnwi3PrimaryLDAPConfigurationRootDN

fragment in NetAct LDAP that contains further configuration attributes for primary NetAct LDAP

ClusterRoot/

NWI3/

mediator/

fsnwi3PrimaryPeopleRootDN

root for searching user accounts in primary NetAct LDAP

ClusterRoot/

NWI3/

mediator/

fsnwi3PrimaryLDAPPort

port number for the primary NetAct LDAP

ClusterRoot/

NWI3/

mediator/

fsnwi3PrimaryLDAPServer

IP address of the primary NetAct LDAP


Table 9 User management parameters (Cont.)

DN0990203 29



3.10 Overload control

ClusterRoot/

NWI3/

mediator/

fsnwi3SecondaryLDAPConfigurationRootDN

fragment in NetAct LDAP that contains further configuration attributes for secondary NetAct LDAP

ClusterRoot/

NWI3/

mediator/

fsnwi3SecondaryPeopleRootDN

root for searching user accounts in secondary NetAct LDAP

ClusterRoot/

NWI3/

mediator/

fsnwi3SecondaryLDAPPort

port number for the sec-ondary NetAct LDAP

ClusterRoot/

NWI3/

mediator/

fsnwi3SecondaryLDAPServer

IP address of the sec-ondary NetAct LDAP

ClusterRoot/

OMS/

System/

RUIM/

RUIMAutomaticActivation

When this parameter is activated, Centralized User Authentication and Authorization auto-mated activation is enabled.

default = 0possible values = 0, 10 = RUIMAutomaticActivation disabled

1 = RUIMAutomaticActivation enabled


Table 9 User management parameters (Cont.)


ClusterRoot/

OMS/

OMSPlatform/

SS_OMSAppControl/

OMSAppControl/

OverloadControlWindowFaultManagementTimeout

This parameter specifies the time-out (in seconds) of inactivity in Fault Man-agement after which OMS attempts to terminate the idle window session.

default = 3600 s

possible values = 60 - 86400 s

Table 10 Overload control parameters

30 DN0990203



LDAP parameters

ClusterRoot/

OMS/

OMSPlatform/

SS_OMSAppControl/

OMSAppControl/

OverloadControlWindowLogViewerTimeout

This parameter specifies the time-out (in seconds) of inactivity in Log Viewer after which OMS attempts to terminate the idle window session.

default = 3600 s


ClusterRoot/

OMS/

OMSPlatform/

SS_OMSAppControl/

OMSAppControl/

OverloadControlWindowSWVersionViewerTimeout

This parameter specifies the time-out (in seconds) of inactivity in SW Version Viewer after which OMS attempts to terminate the idle window session.

default = 3600 s


ClusterRoot/

OMS/

System/

Network/

TrafficControl/

OmsNicBandwidthRelativeLimit

This parameter sets the maximum relative OMS network interface band-width for the outgoing file transfer related traffic. It defines the bandwidth limit as a percentage (%) of the actual OMS NIC link speed.

In case there is only one IP address configured on OMS NIC, it is strongly recommended to change the parame-ter value to 90 %.

default = 70possible values = 1 - 100 %

ClusterRoot/

OMS/

System/

Network/

TrafficControl/

OmsNicBandwidthAbsoluteLimit

This parameter sets the maximum absolute OMS NIC bandwidth for the outgoing file transfer related traffic. It means that the bandwidth used by all clients downloading files from OMS simultaneously cannot exceed con-nection capacity indicated by the current parameter value.

default = 200possible values = 1 - 1000 Mbps

0 = absolute bandwidth limit is inactive

ClusterRoot/

OMS/

System/

Network/

TrafficControl/

OmsNicBandwidthLimitStatus

This parameter enables OMS NIC bandwidth limitation to avoid overload caused by file transfer traffic.

default = 1possible values = 0, 10 = OMS NIC bandwidth limita-tion functionality turned off

1 = OMS NIC bandwidth limita-tion functionality turned on


Table 10 Overload control parameters (Cont.)

DN0990203 31



3.11 Other parameters


ClusterRoot/

OMS/

System/

Network/

CUAccess/

OMS/

szDomainName

OMS domain name values are only updated by the zModifyOMSSettings script

ClusterRoot/

OMS/

System/

Network/

CUAccess/

OMS/

szHostName

OMS hostname values are only updated by the zModifyOMSSettings script

Table 11 Other parameters

Documents

prm_lte_ioms_ldap_parameters.pdf