8000 Intelligent Network Manager SR6.1 Installation and Configuration Guide For Management Server and Recovery Server

8000 Intelligent Network Manager SR6.
1
Installation and Configuration Guide for
Management Server and Recovery Server
76.8061-70202A
31.03.2015
Document Information
© 2015 Coriant. All rights reserved.
This manual is protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual is
subject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification,
distribution, display or other use of this manual may result in criminal and civil penalties.
The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.
Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
8000 Intelligent Network Manager SR6.1 76.8061-70202A

Installation and Configuration Guide for Management Server and Recovery Server © 2015 Coriant.
2
Document Information
Terms and Conventions
Term Explanation
API Application Programming Interface
BGP Border Gateway Protocol
BLC Business Logic Component
BMP Broadband Management Protocol. A communication protocol which is used between
the 8600 network elements and 8000 Intelligent Network Manager.
CLI Command Line Interface
CORBA Common Object Request Broker Architecture
DB Database
EMS Element Management System
FMS Fault Management System
GUI Graphical User Interface
IP Internet Protocol
LAN Local Area Network
LSA Link State Advertisement
LSLL License Server
MPLS Multiprotocol Label Switching
MTOSI Multi-Technology Operations System Interface
NBI Northbound Interface
OSPF Open Shortest Path First
OSR Object Server
OSS Operations Support System
QoS Quality of Service
RNO Real Network Operator
RPC Remote Procedure Call
SATSRV Management Server running Satellite Service
SATWS Workstation
SRVCTRUI The 8000 Server Command Center dialog (controlling panel) of the server. Server
Supervisor is controlled and monitored through this process.
SUPERVI- The main process of Communication Server and Management Server. It starts and
SOR stops other server processes, controls the status of processes and recovers processes
in case of an internal error.
TAO See http://www.cs.wustl.edu/~schmidt/TAO.html
TCP Transmission Control Protocol
UAC User Account Control
76.8061-70202A 8000 Intelligent Network Manager SR6.1

© 2015 Coriant. Installation and Configuration Guide for Management Server and Recovery Server
3
4
Table of Contents
Table of Contents
About the Manual .............................................................................................................. 8
Objectives....................................................................................................................................................................... 8
Audience......................................................................................................................................................................... 8
Related Documentation .................................................................................................................................................. 8
Document Conventions .................................................................................................................................................. 9
Documentation Feedback............................................................................................................................................... 9
1 General ......................................................................................................................... 10
1.1 Server Platform.................................................................................................................................................... 11

1.1.1 General................................................................................................................................................. 11
1.1.2 Configuring Server Platform ............................................................................................................... 12
1.2 Controlling Communication Server and Management Server ............................................................................ 12
1.2.1 Starting Servers.................................................................................................................................... 12
1.2.2 Stopping Servers.................................................................................................................................. 13
1.2.3 Controlling Servers with Server Command Center Application ......................................................... 13
2 Management Server .................................................................................................... 15
2.1 General................................................................................................................................................................. 15
2.2 Management Server Services .............................................................................................................................. 15
2.2.1 Configuring Management Server Service............................................................................................ 15
2.2.2 Backing up Management Server Services ........................................................................................... 16
2.2.3 Configuring Client/Server Relationships Manually ............................................................................ 16
2.3 EMS Service ........................................................................................................................................................ 17
2.3.1 General................................................................................................................................................. 17
2.3.2 Starting EMS Service .......................................................................................................................... 17
2.3.3 Configuring EMS Service.................................................................................................................... 17
2.3.4 Configuring 8600 and 8800 Network Element Drivers....................................................................... 17
2.3.5 Troubleshooting................................................................................................................................... 19
2.4 Fault Service ........................................................................................................................................................ 19
2.4.1 General................................................................................................................................................. 19
2.4.2 Using Management Server Running Fault Service ............................................................................. 20
2.4.3 Processes of Fault Service ................................................................................................................... 21
2.4.4 Fault Service Settings .......................................................................................................................... 21
2.4.5 Fault Service Clients............................................................................................................................ 28
2.5 VPN Provisioning Service................................................................................................................................... 29
2.5.1 Starting VPN Provisioning Service ..................................................................................................... 30
2.5.2 VPN Business Logic Service............................................................................................................... 30
2.5.3 Ethernet OAM Business Logic Service............................................................................................... 30

5
Table of Contents
2.6 Northbound Interface Service.............................................................................................................................. 30

2.6.1 MTOSI Adapter ................................................................................................................................... 32
2.7 Packet Loop Test Service .................................................................................................................................... 33
2.7.1 General................................................................................................................................................. 33
2.7.2 Starting Packet Loop Test Service....................................................................................................... 33
2.7.3 Configuring Packet Loop Test Service ................................................................................................ 34
2.8 Performance Management Service ..................................................................................................................... 35
2.8.1 General................................................................................................................................................. 35
2.8.2 Starting Performance Management Service ....................................................................................... 35
2.8.3 Configuring Performance Management Server Service ..................................................................... 35
2.9 Service Management Service ............................................................................................................................. 35
2.9.1 General................................................................................................................................................. 35
2.9.2 Starting Service Management Service ................................................................................................ 35
2.9.3 Configuring Service Management Server Service .............................................................................. 36
2.10 Element Software Management Service.............................................................................................................. 36
2.10.1 General................................................................................................................................................. 36
2.10.2 Starting Element Software Management Service................................................................................ 36
2.10.3 Configuring Element Software Management Service ......................................................................... 36
2.11 ADC Service........................................................................................................................................................ 37
2.11.1 General................................................................................................................................................. 37
2.11.2 Starting ADC Service .......................................................................................................................... 37
2.11.3 Configuring ADC Service ................................................................................................................... 37
2.12 Satellite Service ................................................................................................................................................... 38
2.12.1 General................................................................................................................................................. 38
2.12.2 Using Management Server Running Satellite Service ........................................................................ 39
2.12.3 Processes of Satellite Service ............................................................................................................. 39
2.12.4 Hardware and Software Requirements for Management Servers Running Satellite Service.............. 40
2.12.5 Installing Management Servers with Satellite Service ........................................................................ 40
2.12.6 Configuring Satellite Service System .................................................................................................. 41
2.12.7 Workstations ........................................................................................................................................ 44
2.13 Macro Manager Service ...................................................................................................................................... 50
2.13.1 General................................................................................................................................................. 50
2.13.2 Starting Macro Manager Service........................................................................................................ 50
2.13.3 Configuring Macro Manager Service .................................................................................................. 50
2.14 Web Reporter Service ......................................................................................................................................... 50
2.15 Scheduling Service .............................................................................................................................................. 51
2.15.1 General................................................................................................................................................. 51
2.15.2 Starting Scheduling Service................................................................................................................. 51
2.15.3 Configuring Scheduling Service.......................................................................................................... 52
2.16 Node Management and Query Service................................................................................................................ 52
2.16.1 General................................................................................................................................................. 52
2.16.2 Starting Node Management and Query Service .................................................................................. 52
2.16.3 Configuring Node Management and Query Service............................................................................ 52
2.17 SLA Service......................................................................................................................................................... 53

6
Table of Contents
3 Recovery Server .......................................................................................................... 54
3.1 Configuration ....................................................................................................................................................... 54

3.2 Controlling Recovery Server ............................................................................................................................... 54
3.2.1 Starting Recovery Server..................................................................................................................... 54
3.2.2 Stopping Recovery Server ................................................................................................................... 55
Server Platform Related Parameters............................................................................... 56
Common Initialization File Settings (nms.ini)............................................................................................................... 56

Server Platform Trace Flags........................................................................................................................................... 57
Service Specific Initialization File Settings ................................................................................................................... 58

7
About the Manual
About the Manual
Objectives
This manual provides instructions on installing and configuring 8000 Intelligent Network Manager
Management Server and Recovery Server.
Audience
This manual is designed for software installation and administration personnel.
Related Documentation
The document numbering scheme consists of the document ID, indicated by numbers, and the
document revision, indicated by a letter. The references in the Related Documentation table below
are generic and include only the document ID. To make sure the references point to the latest
available document versions, please refer to the relevant product document program on the Tellabs
and Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > Data
Networking > 8000 Intelligent Network Manager > Technical Documentation.
8000 Intelligent Network Manager SR6.1 Third Describes all the needed third party software
Party Hardware and Software Requirements components and versions (operating systems and
(76.8061-70222) software versions) in the 8000 Intelligent Network
Manager system. Describes also the relevant
requirements and recommendations of the 8000
Intelligent Network Manager system.
8000 Intelligent Network Manager SR6.1 System Describes 8000 Intelligent Network Manager
Description (76.8061-70200) architectures, all major software applications and
key concepts of the software.
8000 Intelligent Network Manager SR6.1 Software Provides instructions on installing and configuring
Installation Manual (76.8061-70201) 8000 Intelligent Network Manager in different
computer platforms (workstation, servers).
8000 Intelligent Network Manager SR6.1 Provides instructions on installing and configuring
Installation and Configuration Guide for the Northbound Interface in 8000 Intelligent
Northbound Interface (76.8061-70204) Network Manager.
8000 Intelligent Network Manager SR6.1 Release Describes the new supported features, lists the
and Installation Notes (76.8061-70209) made enhancements and fixed bugs and provides
instructions on upgrading 8000 Intelligent Network
Manager.
Web Reporter for 8000 Intelligent Network Provides instructions on installing and configuring
Manager SR6.1 Installation and Configuration the Web Reporter tool.
Manual (76.8061-70215)

8
About the Manual
Document Conventions
This is a note symbol. It emphasizes or supplements information in the document.
This is a caution symbol. It indicates that damage to equipment is possible if the instructions
are not followed.
This is a warning symbol. It indicates that bodily injury is possible if the instructions are not
followed.
Documentation Feedback
Please contact us to suggest improvements or to report errors in our documentation:
Email: fi-documentation@tellabs.com

9
1 General
1 General
This chapter describes the configuration of Communication Server and Management Server. Both
servers have the same server platform software and they are configured partly in the same way. A
typical configuration for running 8000 Intelligent Network Manager with a reasonably large Coriant
network is presented in the figure below.
Fig. 1 Typical Configuration of 8000 Intelligent Network Manager
1.1 Server Platform contains information on the configurations common to both Communication
and Management Servers. For information on server specific configurations refer to chapters
2.12 Satellite Service and 2 Management Server.

10
1 General
1.1 Server Platform
1.1.1 General
The term server platform is used for the software platform which is used in all Communication and
Management Server configurations of 8000 Intelligent Network Manager. The Management and
Communication Server configuration consists of the server platform and one or several server
services listed in the following.
• VPN Provisioning Service

• EMS Service
• Performance Management Service
• Service Management Service
• Element Software Management Service
• ADC Service
• Northbound Interface Service
• Packet Loop Test Service
• Fault Service
• Communication Service
• Discovery Service
• Satellite Service
• SLA Service
• NetAct Adapter
• Macro Manager Service
• Web Reporter Service
• Scheduling Service
• Node Management and Query Service
Note that although it is possible to install several server services in the Management Server
configuration, it is not always recommended because of reduced system resources. The services are
explained in more detail in 2 Management Server.
The server platform functionality can be described as follows.
• Server service definition

• Controlling server service start up and shutdown
• Monitoring the status of the server processes
• Recovering server processes that shut down due to an internal error
• Updating server fault log
• Remote and local control of the server

11
1 General
The following processes are part of the server platform. They are used in all Communication and
Management Server configurations.
Process Explanation
SUPERVISOR.EXE The main process of Communication and
Management Servers. It starts and stops other
server processes, controls the status of processes
and recovers processes in case of an internal error.
SRVCTRUI.EXE The 8000 Server Command Center dialog
(controlling panel) of the server. Server Supervisor
is controlled and monitored through this process.
1.1.2 Configuring Server Platform
Server configurations are defined in the nms.ini and server service configuration files. The common
initialization settings in nms.ini are configured from SETUP.EXE. Server services also have
their own definitions in nms.ini or server service specific files, which are described in chapters
2.12 Satellite Service and 2 Management Server. The server platform related parameters and their
possible values and explanations can be found in Server Platform Related Parameters.
1.2 Controlling Communication Server and Management Server
1.2.1 Starting Servers
Before a Communication Server can be configured to the database with Network Editor, a
Management Server has to be running. After installing the necessary components and performing
the necessary configurations in the nms.ini and server service initialization files and the database
with Network Editor, the server can be started. The server software can be started on the server
computer by activating a respective shortcut to %NMSINSTDIR%\bin\supervisor.exe or by
typing the following command into the Command Prompt window.
%NMSINSTDIR%\bin\SUPERVISOR.EXE
A server can also be started using the Server Command Center. First you have to start SUPERVISOR
as follows.
Step 1 Click the Server Command Center icon.

The 8000 Server Command Center dialog opens.
Step 2 Select the SUPERVISOR process from the list of Running Processes.
Step 3 Select Start Process from the Commands drop-down list.
Step 4 Click Run Command.
SUPERVISOR starts.
To start the server, proceed as follows.
Step 1 Select Start All Services or Start Service from the Commands drop-down list.
For more information on the graphical user interface process, see chapter 1.2.3 Controlling Servers
with Server Command Center Application.

12
1 General
1.2.2 Stopping Servers
To stop Communication or Management Server, proceed as follows.
Step 1 Click the Server Command Center icon.

The 8000 Server Command Center dialog opens.
Step 2 Select Stop All Services from the Commands drop-down list.
All processes except the SUPERVISOR process are stopped.
To stop the SUPERVISOR process, proceed as follows.
Step 1 Select the SUPERVISOR process from the list of Running Processes.
Step 2 Select Stop Process from the Commands drop-down list.
Note that the SUPERVISOR process should be left running if you intend to start the services
remotely.
1.2.3 Controlling Servers with Server Command Center Application
A graphical user interface program, Server Command Center, controls Communication and
Management Servers. With Server Command Center you can monitor the status of the server
and its processes and send simple commands to the server supervisor process. SUPERVISOR
returns an acknowledgement after receiving the given command and then executes the command.
If the command delivery is successful, the Server Command Center displays the text Command
Executed Successfully. Otherwise the text Error in command and a short error description is
displayed. The Server Command Center does not display any further information on the command
execution but the results can be checked in the NmsTrace of the server computer. To obtain more
information in NmsTrace on the Server Command Center and SUPERVISOR, set the nms.ini
parameter SUPERVISOR_TRACE to YES.
The Server Command Center is started by launching a respective shortcut, or by typing the following
command in the Command Prompt window.
%NMSINSTDIR%\bin\SRVCTRUI.EXE
For instructions on starting and stopping SUPERVISOR.EXE with the graphical user interface, see
chapters 1.2.1 Starting Servers and 1.2.2 Stopping Servers.
Managing Remote Servers on Workstation
The Server Command Center can be used on a workstation computer for controlling a remote
Communication and Management Servers. You have to be logged into the system with privileges to
control servers. Remote control is performed by entering the LAN name of the remote computer
as a command line parameter to the Server Command Center.
%NMSINSTDIR%\bin\SRVCTRUI <LAN name of server computer>

13
1 General
or by entering all_servers as the parameter.
%NMSINSTDIR%\bin\SRVCTRUI all_servers
The all_servers parameter enables controlling all the server computers which are defined in the
nms.ini file with the parameter SRV_COMPNAME[x] = <LAN name of server computer>. This
definition is not needed when the program is started on a local server.
The server names must be defined in nms.ini as follows.
SRV_COMPNAME[x] = <LAN name of server computer>

14
2 Management Server
2 Management Server
2.1 General
Management Servers consist of functional entities, Business Logic Components (BLCs), which are
grouped together to form functional subsystems (server services). BLCs are accessed through their
CORBA interfaces. A subsystem is a solid software entity providing the functionality of the area
it is responsible for.
In this chapter you can find instructions on configuring the different services on Management Server.
For information on the server platform, refer to chapter 1.1 Server Platform and for instructions on
starting and stopping the server, and using the Server Command Center application, refer to chapter
1.2 Controlling Communication Server and Management Server.
2.2 Management Server Services
2.2.1 Configuring Management Server Service
In this chapter you can find instructions on how to use several Management Servers.
There is a limitation for Packet Loop Test Service, only one of those should be installed with the
background test scheduling support.
The other services can be run in multiple servers without limitations. Installing Management
Server in the setup.exe selects the usual set of services which can run in multiple servers.
Additional services can be selected manually, and the Packet Loop Test background test scheduling
can be enabled or disabled. The default services can also be disabled or their distribution changed
manually, but then the client nms.ini files need to be manually edited correspondingly.
The services which are running in a Management Server can be found in the nms.ini file of that
server. For instance, the following line in the nms.ini file of a Management Server indicate that
the server is running EMS Services.
SRV_SERVICE1 = EMSSRV
The service numbering scheme is internal to the server. Thus, in each Management Server the
service numbers should follow the format below.
SRV_SERVICE1 = XX_SERVICE
SRV_SERVICE2 = YY_SERVICE
etc.
Refer to 8000 Intelligent Network Manager Third Party Hardware and Software Requirements for
further details on the number of workstations recommended per Management Server.

15
2 Management Server
2.2.2 Backing up Management Server Services
The backup of services can be handled so that if there are e.g. two Management Servers and ten
workstations, the first Management Server can be the primary Management Server for the first
five workstations and the second Management Server can be the primary server for the other five
workstations. The first Management Server can be configured to backup the services running in
the second Management Server and vice versa.
The setup.exe should be used to install the preferred and backup Management Servers, and
to define their names for the clients. Refer to 8000 Intelligent Network Manager Software
Installation Manual for more information.
In addition to the standard set of services, Fault Service can also be backed up. For more information
on configuring Fault Service, refer to chapter 2.4 Fault Service.
2.2.3 Configuring Client/Server Relationships Manually
It is possible to edit the nms.ini files in order to set up also combinations which are
not supported by the setup.exe application, but doing this is neither recommended nor
guaranteed to be compatible with system upgrades. The procedure is explained below in
order to allow fine tuning the system.
For editing the configuration manually, one should know that it is based on the names in nms.ini.
For instance, the entry
NameService.BbmsMplsVpn = BBMS_EEM_MplsVpn_SERVER_A
tells that if VPN Provisioning Service is run on this computer, it should register using the
BBMS_EEM_MplsVpn_SERVER_A name to the CORBA naming service. And if a Provisioning
GUI is run on this computer, it will attempt to reach a VPN Provisioning Service with the
BBMS_EEM_MplsVpn_SERVER_A CORBA name.
Adding a dot and the number 1, i.e. “.1” after a key, tells a client that it is an alternative instance
of a service. For instance,
NameService.BbmsMplsVpn.1 = BBMS_EEM_MplsVpn_SERVER_B
tells the client that if the default service cannot be found, it should use
BBMS_EEM_MplsVpn_SERVER_B as the first alternative service.
The Packet Loop test server which runs the background tests is distinguished by an entry in the
nms.ini files. It can be manually edited to select a different server, only one of the servers should
have the value set as TRUE, the others should be FALSE as in the following.
# PLT Server Background Manager

PLTSRV_BCKMGR = FALSE

16
2 Management Server
2.3 EMS Service
2.3.1 General
EMS Service provides a platform for several element management level services. It sends commands
to the network element via Communication Server and stores the configurations into the database
facilitating the preplanning mode for network element configuration. EMS Service also contains
separate processes for operations related to Quality of Service settings, and protocol authentication.
2.3.2 Starting EMS Service
EMS Service is installed into the Management Server computer. After installing Management
Server successfully the following line should be found in nms.ini.
SRV_SERVICEx = EMSSRV
where x is 1, 2, 3 etc.
The entry means that Supervisor start the EMS Service when Management Server is started. Before
EMS Service can be started, Object Server, NCAM and NAMS must be up and running on the
same computer.
2.3.3 Configuring EMS Service
The following parameters can be defined in nms.ini.
Parameter Explanation
EMSSERVER_BLCS Defines which services are loaded into EMS
Service.
EMSSERVER_DLL_PATH Designates the path to the dynamically
loaded DLLs (both services and other plug-in
libraries). Typically, the DLLs are stored in
the%NMSINSTDIR%\bin.
EMSSERVER_DLLS Defines the plug-in libraries.
The EMS Service initialization file is called emssrv_service.ini and it is located in the
%NMSDIR%\dat\service subdirectory. The file is used by the Supervisor process. As a rule,
the file should not be edited.
2.3.4 Configuring 8600 and 8800 Network Element Drivers
8000 Intelligent Network Manager has a driver activation program that is triggered during the
database update and creation allowing the user to define the used drivers.

17
2 Management Server
Fig. 2 Program for Activating 8600/8800 Network Element Drivers
In the main menu of the driver activation program, the user can select between the following options.
1. To enable all the drivers required by the existing network elements in the database and in ad-
dition to enable all the newest drivers and to disable the rest. This selection is recommended
when there is a plan to either upgrade ESW in some of the 8600 or 8800 NEs in the network or
to purchase new 8600 or 8800 NEs.
2. To enable all different drivers existing in the database and to disable the rest. This selection is
recommended when there are no plans to upgrade ESW for the 8600 NEs in the near future.
3. To go to the Advanced driver configuration menu. This selection needs to be performed when
no 8600 or 8800 NEs yet exist in the network, but new ones are going to be added.
4. To view the details of possible alerts related to the existing driver configuration.
By selecting 0, you can exit the corresponding dialog.
If the following alert text is displayed during the driver configuration: “ALERT: There are x
disabled driver(s) for existing nodes.”, you must enable the corresponding drivers to be able
to configure those 8600/8800 NEs.

18
2 Management Server
If the following alert text is displayed during the driver configuration: “ALERT: There are x
nodes with unsupported info model version in the database.”, you must manually edit the
corresponding drivers in the nms.ini in a Management Server to be able to configure those
8600/8800 NEs.
All unsupported NEs should be upgraded. When doing the upgrade, edit the nms.ini by
adding the driver version which you are upgrading to.
After the upgrade, remove the corresponding driver definition line from nms.ini and restart
the Management Server.
All the alerts are also saved to the %NMSDIR%\SQL\list_of_node_drivers_problems.log file.
2.3.5 Troubleshooting
If you suspect any problems in EMS Service, you can add the following flags to nms.ini.
NMS_INFO_LOGGING = TRUE
NMS_DEBUG_LOGGING = TRUE
EMS_FULL_LOGGING = TRUE
OBJS_SQLTEST = TRUE
OBJS_TESTFLAGS = 00f0f000
EMS_INFO_LOGGING = TRUE
EMS_DEBUG_LOGGING = TRUE
Note that these flags affect the performance of 8000 Intelligent Network Manager. Especially
EMS_FULL_LOGGING creates extensive amount of information. Adding the flags will increase
the amount of data in the EMS Service log file emsserver.log in the log directory, and in the trace
log file.
2.4 Fault Service
2.4.1 General
Fault Service is a Management Server service that consists of one or more Management Servers
providing fault services for workstations. Fault Management GUI applications use the services
provided by Management Server running Fault Service. Fault Service reads changed faults in
the database, analyzes the fault data and informs clients of changes in the fault condition. Fault
Service maps the raw fault data to different kinds of network objects, e.g. network elements and
links, and to the higher level objects, e.g. services, customers and service categories. The Fault
Service clients listen to the notifications from Fault Service and invoke fault queries for different
kinds of objects under fault monitoring.
In addition to the basic fault processing tasks, one Fault Service of the Management Server running
Fault Service can store service faults in the database. The service faults can be read in the database
by any tool that is not capable of communicating with Fault Service. Fault Service process can also
provide fault and service fault data via Northbound Interface Service.

19
2 Management Server
Backup configurations are supported for Fault Services. For each Fault Service client, several
backups for the primary Fault Service can be defined. For further information on defining the Fault
Service mode see chapter 2.4.5 Fault Service Clients. One Fault Service can also be a backup for
the Fault Service maintaining the servicefault database table.
2.4.2 Using Management Server Running Fault Service
By default, Fault Service is running in every standard Management Server.
Fig. 3 Management Server Running Satellite and Fault Services in 8000 INM

20
2 Management Server
2.4.3 Processes of Fault Service
FMSP
This is the actual Fault Service process. This process takes care of fault processing and fault services
for the Fault Management System.
2.4.4 Fault Service Settings
Common Initialization File Settings (nms.ini)
Fault Service supports both named pipes and sockets in communication with clients. Pipe names
and socket ports of the Fault Service process (FMSP.EXE) are defined in the nms.ini file. The
default values are as follows.
FMSP_PIPE = FLTSRV
FMSP_PORT = 8816
If there is a firewall system between 8000 Intelligent Network Manager workstation and
Management Servers running Fault Service, one Management Server port is accessed from the
8000 INM workstations, and needs to be opened in the firewall from the workstation towards
Management Server. This port is defined as follows.
FMSP_PORT = 8816
This parameter defines the TCP/IP socket port number of the Fault Service. This port is used by
Fault Management System of the 8000 Intelligent Network Manager workstation.
Note that additional ports may need to be opened in the firewall due to third party software
requirements.
The FMSP_PIPE and FMSP_PORT entries in the nms.ini file are common to both the client and
the server. The pipe name and port number can be any available (non-reserved) name and
number, but they must be the same on both the client and server.
Fault Service Initialization File Settings (FMSP.INI)
The Fault Service initialization file (FMSP.INI) contains some parameters which configure general
functions, such as tracing and the maximum number of faults. The FMSP.INI file entries are
described below.
FmspTrace Enables major tracing. The default value
is ON, which means that tracing of major
events is enabled.
FmspTraceFaultUpdates Enables fault update tracing. The default
value is ON, which means that tracing of
fault updates is enabled.

21
2 Management Server
FmspTraceDetails Enables detailed tracing. The default value
is OFF, which means that tracing of details
is disabled.
FmspTraceChangeMessages Enables change message tracing. The
default value is OFF, which means that
tracing of change message handling is
disabled.
FmspTraceInternalMessages Enables internal message tracing. The
default value is OFF, which means that
tracing of internal message handling is
disabled.
FmspTraceClientRequests Enables client request tracing. The default
value is OFF, which means that tracing of
client requests is disabled.
FmspTraceClientEvents Enables client event tracing. The default
client notifications is disabled.
FmspTraceDebug Enables debug level tracing. The default
debug information is disabled.
FmspLog Enables writing into the FMSP.LOG log
file. The default value is OFF, which
means that writing is disabled.
FmspStdout Enables printing to a standard output
device such as a console. The default value
is OFF, which means that printing is not
enabled.
FmspServerGtwsSlaveEnabled Enables Supervisor control. The default
value is ON, which means that Supervisor
control is enabled.
FmspLanPollInterval Defines the polling interval of the
client-server connection. The client and
server poll each other and, when the polling
fails for the specified time-out, the session
is cleaned up. The default value is 30. If
the value is 0, polling is off.
FmspLanPollTimeout Defines the polling time-out of the
client-server connection in seconds. The
time-out must be greater than two times
FmspLanPollInterval. The default value
is 65.
FmspThreadStartTimeout Defines the time-out for starting server
threads in seconds. The default value is 60.
FmspRecommendedMaxFaults Defines the recommended limit for the
number of active or unacknowledged
faults. When the limit is exceeded, Fault
Service sends a warning message to
all active clients. The default value is
1000000.

22
2 Management Server
FmspMaxReportFaults Defines the maximum number of faults in
reports. If the number of faults in the Fault
History report or in Web Reporter also the
Active Fault report exceeds the configured
value, the report is truncated so that only
the first FmspMaxReportFaults faults are
shown in the report. The default value is
300000.
FmspMaxFaultsMode The default value is OFF, which means
Fault Service will not stop fault polling
if the FmspRecommendedMaxFaults
limit is exceeded. If this option is ON
and the limit is exceeded, Fault Service
stops fault processing and shuts down. In
that case Fault Service must be restarted
after the limit is increased or faults are
acknowledged and cleared. This option
provides backward compatibility e.g. for
the NBI users.
FmspPeriodicFaultRefresh Enables periodic fault refreshing. This
means that periodically all faults are read
from the database. Normally this is done at
server startup and later only fault changes
are read from the database. The default
value is OFF, which means that refreshing
is not enabled.
FmspMaxFaultRefreshHours Defines the maximum interval for periodic
fault refreshing in hours. The default value
is 24.
FmspMaxActualFaultPollingPeriod Defines the maximum time for actual
fault polling period in seconds. If polling
time exceeds this value and fault history
has been updated during that time, all the
faults must be reread in order to avoid
inconsistency situation in Fault Server. The
default value is 120.
FmspPeriodicConsistencyCheck Enables periodic fault consistency
checking. This means that periodically
all fault ids are read from the database
and then compared to the faults that are
in memory. If inconsistencies between
memory and database are detected, they
are solved and client windows are notified
about changes. The default value is OFF,
which means that periodic fault consistency
checking is not enabled.
FmspPeriodicConsistencyCheckMinutes Defines the interval for periodic fault
consistency checking in minutes. The
default value is 10.

23
2 Management Server
FmspContinuousConsistencyCheck Enables continuous fault consistency
checking. This means that at each fault
poll number of faults in the database and
memory are compared. If inconsistencies
between memory and database are detected,
they are solved and client windows are
notified about changes. The default value
is OFF, which means that continuous fault
consistency checking is not enabled.
FmspContinuousConsistencyCheckPeriod This parameter is used if continuous
consistency checking above is active.
It defines how many successive fault
polling rounds with possible inconsistency
situation has to be performed before
consistency checking of faults between
memory and database is activated. The
default value is 5.
FmspIncludeExternalsInBundles Enables external link faults. This parameter
controls whether all interface faults at both
endpoints of the external link are summed
and shown for the external link. The
default value is OFF, which means that the
setting is disabled.
FmspServerLayerTrunkSupport Enables server layer link faults. This
parameter controls whether the faults of the
link and the server layer link are summed
and shown for the link. The default value
is OFF, which means that the setting is
disabled.
FmspMaxFaultBlocksBeforeSfmUpdate The maximum number of fault blocks
after which the service fault monitoring is
updated in the boot phase of Fault Service.
FmspServerFaultMappingStart Enables service fault mapping in the Fault
Service mode. The default value is ON,
which means that service fault mapping is
automatically started.
FmspServerFaultMappingThreads The number of service fault mapping
threads in the Fault Service mode.
FmspMaxMappingBootErrors The limit of the service fault mapping
errors during the boot phase. When the
limit is reached, a warning is displayed.
FmspMaxMappingRuntimeErrors The limit of the service fault mapping
errors during the runtime phase. When the
limit is reached, a warning is displayed.
FmspRootCauseFormat Defines what fields of the root cause fault
are used for generating the root cause
description text.
FmspDbMoveServiceFaultsToHistoryAtExit Enables moving of the servicefault record
to the servicefaulthistory table at Fault
Service exit. The default value is ON,
which means that the servicefault table is
cleaned up when the Fault Service shuts
down.

24
2 Management Server
FmspServerServiceFaultMappingLevel Sets the Service Fault Mapping level for
the servicefault database table.
FmspServerServiceFaultFilterOks Enables filtering of servicefault records
whose state is OK (mtnevent=0). The
default value is ON, which means that
service faults whose state is OK are not
stored in the servicefault table and they are
not provided to the NBI.
FmspNbifFilterElementServiceFaults Enables filtering of element servicefault
records for NBI. The default value is ON,
which means that service faults whose
service type is some element type (trunk,
node, iface), are not provided to the NBI.
FmspNbifFaultSourceFormat Defines which fields are used for generating
the fault source text in case of NBI.
FmspDataFileName Defines the filename of the data file. If no
path is given, the current working directory
is used (typically %NMSDIR%\bin).
FmspDataFilePrintAtExit Enables writing information to the data file
at exit. The default value is OFF, which
means that the data file is not written at
exit.
FmspDataFileTrunks Enables writing trunk information to the
data file. The default value is ON, which
means that trunk information is written
to the data file when the file writing is
requested.
FmspDataFileNodes Enables writing node information to the
means that node information is written
requested.
FmspDataFileBlocks Enables writing fault block information
to the data file. The default value is ON,
which means that fault block information is
written to the data file when the file writing
is requested.
FmspDataFileFaults Enables writing fault information to the
means that fault information is written
requested.
FmspDataFileServices Enables writing service fault information
which means that service fault information
is written to the data file when the file
writing is requested.
FmspDataFileOnlyFaulty Enables writing only faulty trunk and node
information to the data file. The default
value is ON, which means that only faulty
trunks and nodes are written to the data file
when the file writing is requested.

25
2 Management Server
FmspDataFileServiceStatus Enables writing service fault view status
value is ON, which means that view status
information of service faults is written
requested.
FmspDataFileBlockStatus Enables writing fault block view status
information of fault blocks is written to the
data file when the file writing is requested.
FmspDataFileFaultStatus Enables writing fault view status
information of faults is written to the data
file when the file writing is requested.
FmspDataFileBlockRefs Enables writing fault block references only
which means for trunks and service faults
only fault block references, not actual fault
block data, are written to the data file when
the file writing is requested.
FmspUsePlatformIndependentByteBuffers Defines if messages are sent from Fault
Server to the client in platform independent
format. The default value is ON, which
means that platform independent format is
used.
FmspMaxWidgetWorkerThreads Defines the maximum number of threads
used for processing Dashboard client
operations.
FmspAsyncOperationMaxWaitTime Defines the time in seconds that the server
waits for a confirmation from the client
after a fault report request. The default
value is 20 seconds.
FmspNotificationDelayInMs Defines the change notification delay value
in milliseconds (e.g. 1000 for 1 second)
for CPU load balancing. This can be used
in session installations where there are
several FMS clients running in the same
computer. If the value differs from 0, the
clients will not handle the notifications at
the same time. The default value is 0.
FmspEnableIfaceServiceMapping Enables creating interface-level service
faults if interfaces are added to the services
created by Service Management. The
default value is ON.
The FmspLanPollInterval and FmspLanPollTimeout entries in the FMSP.INI file are common
to both the client and the server.

26
2 Management Server
Fault Service Specific Commands
In addition to normal service control commands, like Start Service, there are some Fault
Service specific commands available in the 8000 Server Command Center dialog. Those
commands can be used for controlling, tracing and data file generation. The Fault Service specific
commands are described below.
Command Parameters Explanation

EnableTrace <none> Enables the following trace flags: Fmsp-
TraceDetails, FmspTraceChangeMessages,
FmspTraceInternalMessages, FmspTraceclien-
tRequests, FmspTraceClientEvents.
EnableTrace <one trace flag> Enables the given trace flag (any FmspTrace* as
in FMSP.INI).
DisableTrace <none> Disables the following trace flags: Fmsp-
TraceDetails, FmspTraceChangeMessages,
FmspTraceInternalMessages, FmspTraceclien-
tRequests, FmspTraceClientEvents.
DisableTrace <one trace flag> Disables the given trace flag (any FmspTrace*
as in FMSP.INI).
PrintSettings <none> Prints Fault Service settings to the trace log. This
can be used for checking the current settings.
Those settings are also stored to FMSP.INI when
the Fault Service is shut down.
ReadSettings <none> Reads Fault Service settings from the FMSP.INI
file. This can be used to load new settings without
restarting the Fault Service. Note that only some
of the simple parameters, such as tracing options,
are applied right away. Other, more complex
parameters, such as thread settings, may require
restarting the Fault Service.
CheckConsistency <none> Performs the fault consistency checking
immediately. This means that all fault ids are
read from the database and then compared to
the faults that are in memory. If inconsistencies
between memory and database are detected, they
are solved and client windows are notified about
changes.
RefreshFaults <none> Reads all faults from database immediately. If
changed faults are detected, client windows are
notified about changes.
EnableDataFile <none> Enables all data file flags except
FmspDataFilePrintAtExit.
EnableDataFile <one data file flag> Enables the given data file flag, e.g.
FmspDataFileTrunks.
DisableDataFile <none> Disables all data file flags except
FmspDataFilePrintAtExit.
DisableDataFile <one data file flag> Disables the given data file flag, e.g.
FmspDataFileTrunks.

27
2 Management Server
Command Parameters Explanation

PrintDataFile <none> Writes network fault status information to the data
file. This command uses the file name defined by
FMSP.INI/FmspDataFileName.
PrintDataFile <filename> Writes network fault status information to the
data file with the given file name. If the file path
is given, the path must exist. If no path is given,
the current working directory is used (typically
%NMSDIR%\bin).
Note that when FMSP.INI related settings are changed by the 8000 Server Command Center
dialog (e.g. EnableTrace FmspTraceDetails) those changes are stored to FMSP.INI (e.g.
FmspTraceDetails=ON) when the Fault Service is shut down.
Backup Fault Services
There are two different backup functions for Fault Services: backup for clients and backup between
Fault Services.
The backup for clients means how the clients are reconnecting if the connection to the current
Fault Service fails. For further information on defining the backup Fault Services for clients see
chapter 2.4.5 Fault Service Clients.
The backup system between Fault Services means how updating of the service fault table is
protected. One Fault Service is defined as a primary responsible for the update, and another Fault
Service is a backup for it. The primary Fault Service can be defined in the Configure Mapping
Primary Fault Server dialog of the Fault Management System tool. The backup Fault Service can
be defined in the Configure Mapping Backup Fault Server dialog in the FMS tool.
2.4.5 Fault Service Clients
Any workstation with the Fault Management tool can be a Fault Service client. Communication
is established between the client and Fault Service when Fault Management is started, and all
connections are closed when Fault Management is closed.
Northbound Interface Service also uses the Fault Server process. For more information about
Northbound Interface, see the document 8000 Intelligent Network Manager Installation and
Configuration Guide for Northbound Interface.
Note that some parameters in the Fault Service configuration file (FMSP.INI) are common to the
workstations and server. If those parameters are changed on the server, they must be changed also on
all workstations using the server. For more information, refer to chapter 2.4.4 Fault Service Settings.
Settings for More Than One Backup Fault Service (nms.ini)
Customarily, the FAULTSERVER entry must be commented out and the MNGTSRV entry
must contain the LAN name of the Management Server running Fault Service. The MNGTSRV
parameter contains the LAN name of the preferred Management Server that was selected during the
installation. Editing the MNGTSRV parameter manually in nms.ini is not recommended.

28
2 Management Server
#FAULTSERVER = <leave empty>

MNGTSRV = <LAN name of server computer>
The backup Management Server is also used for the backup Fault Service.
MNGTSRV1 = <LAN name of 1. backup server>

If Fault Service needs to be run in a different computer than the preferred Management Server, or
more than one backup Fault Server is needed, the FAULTSERVER parameters must be edited
in nms.ini as follows.
FAULTSERVER = <LAN name of the main fault server>

FAULTSERVER1 = <LAN name of 1. backup server>
...
FAULTSERVER9 = <LAN name of 10. backup server>
Communication Protocol Settings in Fault Service nms.ini File
The communication protocol between the client and Fault Service can be defined on the workstation.
By default the nms.ini file contains the following entries.
FMSP_PIPE = FLTSRV
FMSP_PORT = 8816
The FMSP_PIPE and FMSP_PORT entries in the nms.ini file are common to both the client and
the server. The pipe name and port number can be any available (non-reserved) name and
number but they must be the same on both the client and the server.
When both entries are defined, the named pipe protocol is used in local communication (workstation
mode) and TCP/IP sockets in remote communication (server mode) by default.
To use TCP/IP sockets in the workstation mode, the FMSP_PIPE entry must be disabled in the
nms.ini file as follows.
#FMSP_PIPE = FLTSRV
FMSP_PORT = 8816
To use named pipes in the server mode, the FMSP_PORT entry must be disabled in the nms.ini
file as follows.
FMSP_PIPE = FLTSRV
#FMSP_PORT = 8816
For each workstation it is possible to select which protocol to use but the pipe names and port
numbers must be the same on all clients and the server.
2.5 VPN Provisioning Service
VPN Provisioning Service contains the VPN Business Logic and Ethernet OAM Business Logic
services, which are started or stopped when VPN Provisioning Service starts or stops them.

29
2 Management Server
2.5.1 Starting VPN Provisioning Service
After installing Management Server successfully the following line should be found in nms.ini.
SRV_SERVICEx = VPNPSRV
where x is 1,2,3 etc.
This entry means that Supervisor will start the VPN Provisioning Service when Management Server
is started. The service processes are defined in the vpnpsrv_service.ini file.
2.5.2 VPN Business Logic Service
The VPN Business Logic Service handles the creation and maintenance of IP VPNs and
their subcomponents such as LSPs and VRFs. It handles the business logic services for VPN
Provisioning, Tunnel Engineering and third party tools.
If you suspect any problems in the VPN Business Logic Service, you can add the following flags to
the nms.ini file.
MPLSSRV_DEBUG_LOGGING = YES
MPLSSRV_INFO_LOGGING = YES
The mplssrv process log file, mplssrv.log, will be created into the log directory and also more
mplssrv process specific data will be written to the trace log file.
2.5.3 Ethernet OAM Business Logic Service
The Ethernet OAM Business Logic Service handles the operations related to the Ethernet connection
fault management operations. These services are used by the OAM Management and VPN
Provisioning applications.
TCP socket connection is used between the client application and the Ethernet OAM Business Logic
Service. After installing the Management Server successfully, the following lines can be found in
the nms.ini file.
MPLSSRV_PORT = x
where x is the port
OAMSERVER =
OAMSERVER1 =
where OAMSERVER is the server computer and OAMSERVER1 is the backup computer.
In the default setup the server computer names are the same that are used for the VPN Provisioning
Service.
2.6 Northbound Interface Service
The Northbound Interface (NBI) in 8000 Intelligent Network Manager is a gateway which enables
interoperability with third party OSSes in a multivendor environment.

30
2 Management Server
The northbound interface enables third party OSSes to request operations in the 8000 INM network.
The NBI is also able to notify the third party OSSes about configuration changes and alarms in the
8000 INM network.
The northbound interface supports Fault Management and macro execution. The NBI also offers a
future growth path to other areas of network management like topology management, performance
management and connection management.
The northbound interface software consists of the communication adapter process and NBI Kernel
process. Communication adapters are responsible for the communication protocol (e.g. TCP/IP)
specific tasks whereas the NBI Kernel is responsible for executing the service requests by calling the
lower layer services of 8000 INM, e.g. Fault Server, Macro Manager and Object Server. The NBI
Kernel has an interface called Internal Adaptation interface. Communication adapters publish NBI
information models (NBI IMs) which describe the services available to third party clients.
The northbound interface contains a communication adapter providing a TCP/IP interface. The
NBI supports retrieving active NE faults and faulty services and sending notifications about the
NE faults and faulty services. The NBI also supports acknowledging NE faults. SNMP adapter is
supported as an optional adapter for retrieving faults.
As an optional adapter TM Forum’s Multi-Technology Operations System Interface (MTOSI)

release 2.0 is supported in NBI.
The NBI runs on a Management Server computer. It can serve the maximum of ten simultaneous
clients. If needed, more than one Management Server computer may be running the NBI per one
8000 INM network.
For installation and configuration instructions of the NBI service refer to 8000 Intelligent Network
Manager Installation and Configuration Guide for Northbound Interface.

31
2 Management Server
Fig. 4 Architecture of Northbound Interface Service Software
2.6.1 MTOSI Adapter
General
MTOSI adapter provides a platform for TM Forum’s Multi-Technology Operations System Interface
(MTOSI) release 2.0.
Starting MTOSI Adapter
MTOSI adapter is installed into the NBI Management Server computer. After
installing NBI Management Server successfully the following line should be visible in
%NMSDIR%\dat\service\nbifsrv_service.ini.

32
2 Management Server
SLAVE_PROCESS6_NAME = NMA
The entry means that Supervisor will start MTOSI adapter when NBIFSRV Service is started. Before
MTOSI adapter can be started, MMSRV and MMAG must be up and running on the same computer.
Configuring MTOSI Adapter
NMA_HTTP_PORT Defines the HTTP port MTOSI adapter is using.
NMA_HTTPS_PORT Defines the HTTPS port MTOSI adapter is using.
The MTOSI adapter initialization is done in a file called nbifsrv_service.ini and it is located in
the %NMSDIR%\dat\service subdirectory. The file is used by the Supervisor process. As a rule,
Troubleshooting
If you suspect any problems in the MTOSI service, you can add the following flags to the nms.ini
file.
The nma.log nma process log file will be created into the log directory.
2.7 Packet Loop Test Service
2.7.1 General
The 8000 Intelligent Network Manager Packet Loop Test business logic component offers an open
CORBA interface for testing the network, tunnels and configured VPN services. The tests can be
managed in the hardware and database. Background Manager can schedule tests into the database
and run them in the background at the specified time.
2.7.2 Starting Packet Loop Test Service
After installing Management Server successfully with the Packet Loop Test Service, the following
line should be found in the nms.ini file.
SRV_SERVICEx = PLTSRV

33
2 Management Server
This entry means that Supervisor will start the Packet Loop Test Service when Management
Server is started. The Packet Loop Test Service process is PLTSRV.EXE, which is defined in
the pltsrv_service.ini file. Additional processes included in the Packet Loop Test Service are
SUPERVISOR, OBJECT SERVER, NCAM and BBSECURITY. There may be several Packet Loop
Test Services in 8000 Intelligent Network Manager but only one can run Background Manager,
which supports test scheduling. Before PLT Service can be started, Object Server, NCAM and
NAMS must be up and running on the same computer.
2.7.3 Configuring Packet Loop Test Service
PLTSRV_BCKMGR = <TRUE/FALSE> The default value is TRUE, which means that
Background Manager is running in the Packet
Loop Test Service. If several Packet Loop Test
Services are running in 8000 Intelligent Network
Manager, Background Manager may be enabled in
only one of them.
PLTSRV_BMP_DELETE = <TRUE/FALSE> The default value is TRUE, which means that
delete commands are sent to the 8600 network
elements after the hardware commands for a test.
The Packet Loop Test Service initialization file is called pltsrv_service.ini and it is located in the
%NMSDIR%\dat\service directory. The file is used by the Supervisor process and it should
not be modified.
The Packet Loop Test Service is configured to use a command prompt window to trace server
process activity. At startup it traces the pltsrv.exe file and build versions. If the startup is successful,
it traces the PLTSRV Server is running... item.
As only one instance of Background Manager can be run in the system, it is advised to check that it
is disabled. When disabled, the nms.ini file should read as follows.
PLTSRV_BCKMGR = FALSE
Moreover, the PLTSRV.LOG file in the %NMSDIR%\log directory can be used for
troubleshooting.

34
2 Management Server
2.8 Performance Management Service
2.8.1 General
The Performance Management Service handles the access to the performance data and the
configuration of the performance data collection to the database. The performance data is either
performance real-time data (from the network element) or performance history data (from the
database). The Performance Management Service interacts with the PMS GUI components and
with the PMS Business Logic component. The communication to these components is handled
through CORBA.
2.8.2 Starting Performance Management Service
SRV_SERVICEx = PMSSRV
where x is a unique integer among the SRV_SERVICE entries.
The entry means that Supervisor will start the Performance Management Service when the
Management Server is started. The Performance Management Service process is PMSSRV.EXE
which is defined in the PMSSRV_service.ini file.
2.8.3 Configuring Performance Management Server Service
The Performance Management Service startup parameters are stored in the PMSSRV_service.ini
file, which is located in the %NMSDIR%\dat\service directory. The file is used by the Supervisor
process and it is not to be edited.
All the entries in this file are standard entries and described in chapter 1.1.2 Configuring Server
Platform.
2.9 Service Management Service
2.9.1 General
The Service Management Service handles the operations related to service objects. It contains the
logic for service creation and setting of the parameters. The service interacts with the Service
Management application. The communication between these components is handled through
CORBA.
2.9.2 Starting Service Management Service
SRV_SERVICEx = SMSSRV
where x is a unique integer among the SRV_SERVICE entries.

35
2 Management Server
The entry means that Supervisor will start the Service Management Service when the Management
Server is started. The Service Management Service process is SMBLC.EXE which is defined in
the smssrv_service.ini file.
2.9.3 Configuring Service Management Server Service
The Service Management Service startup parameters are stored in the smssrv_service.ini file, which
is located in the %NMSDIR%\dat\service directory. The file is used by the Supervisor process and
it is not to be edited.
All the entries in this file are standard entries and described in chapter 1.1.2 Configuring Server
Platform.
2.10 Element Software Management Service
2.10.1 General
Element Software Management Service provides services for the Element Software Management
application to manage ESW files and download plans. It provides also a functionality to create ESW
inventory reports. The core idea is to provide functionality to update the software in the network
elements according to the download plans.
2.10.2 Starting Element Software Management Service
Element Software Management Service is installed into the Management Server computer. After
installing Management Server successfully with the Element Software Management Service option
the following line should be found in nms.ini.
SRV_SERVICEx = ESWMSRV
The entry means that Element Software Management Service is started when Management Server
is started.
2.10.3 Configuring Element Software Management Service
Currently Element Software Management Service does not include any parameters to be configured.
If you suspect any problems in the Element Software Management Service, you can add the
following definitions to nms.ini.
ESWMSRV_INFO_LOGGING = TRUE
ESWMSRV_DEBUG_LOGGING = TRUE

36
2 Management Server
After modifying the nms.ini file, the ESWMSRV process or the whole Management Server
must be restarted. Optionally you can enable the trace logging in the Server Command Center
dialog by selecting the ESWMSRV Service and ESWMSRV process and then applying the
SetDebugLoggingOn and SetInfoLoggingOn commands for the process. It is much easier to
enable the tracing this way but note that these settings are cleared when the process is restarted.
Element Software Management Service writes log events to the eswmsrv.log file. By default, all
error events are logged and optionally also the debug and info messages.
2.11 ADC Service
2.11.1 General
The Automated Deployment Controller Service (ADC Service) is responsible for handling
operator-defined deployment steps in the context of the automated deployment. When ADC Service
has been notified that a newly deployed network element has appeared in the network, ADC
Service starts to execute post processing operations to push configuration from the database to
the network element.
2.11.2 Starting ADC Service
After installing the Management Server successfully the following line should be found in nms.ini.
SRV_SERVICEx = ADCSRV
This entry means that Supervisor will start the ADC Service when Management Server is started.
2.11.3 Configuring ADC Service
ADC_THREAD_POOL_SIZE Defines the number of threads to run parallel
deployment tasks in Automatic Deployment
Controller (ADC). The default value is 5.
ADC_STOP_WAIT_TIME Defines the maximum time to wait for Automatic
Deployment Controller to finish ongoing tasks,
when stopping the server.
Note that also %NMSDIR%/dat/service/mm-
srv_service.ini needs to be modified with a
matching value. The default is 600 seconds.
The ADC Service initialization file is called adcsrv_service.ini and it is located in the

37
2 Management Server
The ADC Service process log file adc.log will be created into the log directory.
2.12 Satellite Service
2.12.1 General
A Management Server with Satellite Service takes care of serving the workstations. Management
Server with Satellite Service uses 8000 Intelligent Network Manager services through a server
computer. The system provides access to 8000 INM and a servicing interface for the 8000 INM
workstation computers (previously satellite workstations). The Satellite Service running in a
Management Server is a required service for 8000 INM workstations.
Workstations are “lightened” denoting the lightened processing load of the 8000 Intelligent Network
Manager workstation as a part of the 8000 INM processing is shifted to Satellite Service. The
processing load of the workstations is reduced because the clients do not run Object Server (OSR)
unlike standard workstation type clients prior to SR4.2.
The workstations do not have direct database connections; their access to the database is multiplexed
through Satellite Service. The workstations are connected to the Satellite Service in a Management
Server with routed LAN. Individual remote clients and their connections to the database can be
better tolerated because the 8000 INM applications of the workstations cannot lock directly the
database tables. Satellite Service serializes transactions to the Database Server.
The workstations can commit the same functions that are provided for the earlier standard
workstation. The operability of the workstations is not restricted or limited, and they can use the
services of Database Server, DXX Servers, Communication Servers and Recovery Server through
Satellite Service.
The number of supported workstation clients that are served by one Satellite Service depends to
a great extent on the frequency of use, as well as load and operational tasks performed on the
workstations. The number of supported workstation clients per server depends also on the other
installed services of the Management Server. In heavy use the number may need to be reduced
to keep up the operating performance at a required level. Refer to 8000 Intelligent Network
Manager Third Party Hardware and Software Requirements for the maximum number of supported
workstations per server.
The number of workstations that are served by one Satellite Service affects also the hardware
requirements of the Satellite Service; the more clients there are for a single Satellite Service, the
more processing power and system resources (memory, disk space) is needed in the Satellite Service.
It is recommended to close unnecessary applications and windows in the workstation to achieve a

better system response time.

38
2 Management Server
2.12.2 Using Management Server Running Satellite Service
The benefits aimed at are to make client/server architecture more fault tolerant and to achieve
more system throughput. This goal can be fulfilled with a server multiplexing the connections of
the clients to the database. Individual clients and their connections to the database can be better
tolerated, thus preventing some serious database locks (clients cannot lock the database tables
directly, the calls go through the server).
The Satellite Service concept is also suitable for serving remote connections where LAN breaks
typically take place quite often. The problems in the connection between an individual workstations
and Satellite Service do not affect other workstations and 8000 Intelligent Network Manager
computers.
When there is a LAN break between a Management Server running Satellite Service and a
workstation, the operation under execution in the workstation will not succeed. The operation with
Database Server is terminated if the operation was already under execution in the Management
Server running Satellite Service, but the return data writing has not succeeded. In any case, an
8000 INM application notices the loss of connection as a deformed return code of the 8000 INM
software in the workstation. Depending on the application, it will inform the user of this and the
user needs to start a new execution of the operation.
Slow LAN connections, slow computers and LAN breaks between the client and the server do not
cause unnecessarily long blocking of the database tables. The server resides in the operator’s main
LAN near the Database Server, and there is a good connection between the Database Server and the
Satellite Service. Because of this, transactions do not terminate easily when LAN breaks occur.
It is possible to increase the number of management stations (workstations) if more servers

are provided. Because Satellite Service in Management Server is multiplexing the workstations
connections to the database and all the traffic goes through the Satellite Service(s), there are fewer
connections to serve (from the database point of view) compared to a situation in which individual
workstations (standard workstations prior to SR4.2) would have their connections directly to the
database.
2.12.3 Processes of Satellite Service
The most important processes of Satellite Service are described below.
Satellite Service Processes

VPNM This process starts and controls the service
processes for the workstations.
VPNR This is the recovery handling process of Satellite
Service. This process communicates with
Recovery Server and Workstation Recovery
Control Program.

39
2 Management Server
VPNS This is the service and change message handling

process in Satellite Service. It is a sign of an
active workstation. There can be as many service
processes running in Satellite Service as there are
workstations connected.
CICO, TDSV, NAMS, LSLL Circuit connector, test data server, name server
and license server processes are also needed in the
Satellite Service configuration.
The most important processes of workstations are described below.
Workstation Processes
WSNM This is the process selecting the available Satellite
Service for the other workstation components. It
is also the core of the workstation session: one
WSNM corresponds to one VPNS on the server
side keeping the workstation session alive.
It also includes the change handling function
for the workstations receiving change messages
from Satellite Service (the VPNS process)
and forwarding them to the correct 8000 INM
applications in the workstations.
8000 INM applications 8000 INM application processes.
2.12.4 Hardware and Software Requirements for Management Servers Running

Satellite Service
It is recommended that Satellite Service and workstation software are running on separate computers.
For further information on hardware requirements, refer to the 8000 Intelligent Network Manager
Third Party Hardware and Software Requirements.
2.12.5 Installing Management Servers with Satellite Service
Management Servers running Satellite Service use the 8000 Intelligent Network Manager SR6.1
database. Older database versions must be updated to SR6.1 database before the Satellite Service
can be used. Instructions on updating the database are provided in 8000 Intelligent Network
Manager Release and Installation Notes.
Management Server needs a database connection. For more details refer to 8000 Intelligent
Network Manager Software Installation Manual and 8000 Intelligent Network Manager Third
Party Hardware and Software Requirements.
Management Servers running Satellite Service should always reside in the operator’s main LAN, i.e.
in the same LAN as Database Server. The connections between the workstations and LAN can be
implemented in two ways.
1. Workstations can be connected to the same LAN as Satellite Services, or

2. Workstations can reside in a separate LAN segment that is physically connected to Satellite
Service.

40
2 Management Server
Both the first and the second option can be connected directly, or with routers or routed LANs.
In the first option there is only one LAN adapter in the Satellite Service, whereas in the second option
two LAN adapters are needed. In the second option one LAN adapter of Satellite Service is toward
the main LAN, and the other one is toward the separate LAN segment containing the workstations.
Although there are two alternative options, the latter one is recommended.
If you want to run the server as Windows Service, tick the Install as a Windows Service check
box.
In case of installing workstation the name of the Management Server running Satellite Service is
referred to as Preferred Management Server in the Setup program.
For further instructions about installing the Satellite Service license, refer to 8000 Intelligent
Network Manager Release and Installation Notes.
2.12.6 Configuring Satellite Service System
Server Platform Settings
Configuration File Settings (nms.ini)
For the compulsory fields to be filled out and for further instructions, refer to Common Initialization
File Settings (nms.ini).
Service-Specific Configuration File Settings
Service has its own SATSRV_SERVICE.INI configuration file. This file is located in the
%NMSDIR%\dat\service directory. SUPERVISOR needs these settings in order to know which
processes should be started and how. Normally, you need not to change these parameters.
For the compulsory fields to be filled out and for further instructions, refer to Service Specific
Initialization File Settings.
Satellite Service Configuration File Settings (nms.ini)
Process Limit
The server administrator can limit the service processes of the server. If the limit value is reached,
Satellite Service does not allow service processes to be started even if there is a servicing request
coming from the workstation. The process limit can be defined as follows.
SATSRV_PROCESS_LIMIT = 120 = < Number of processes >

This value can be any positive value up to 120, which is the maximum and also the default value.

41
2 Management Server
Socket Definition
Sockets are used between the workstation and Satellite Service process (VPNS.EXE).
The VPNS_PORT_RANGE flag (nms.ini) defines in the Management Server running Satellite
Service which ports are available in the server for serving client connections between the
workstation and the running VPNS.EXE process. The default range is 35010…35999 but this
can be parameterized with the VPNS_PORT_RANGE flag. The values must be defined before
starting the server.
The port range defined by VPNS_PORT_RANGE flag in the nms.ini file can be any available
(non-reserved) TCP/IP port interval. Management Server running Satellite Service selects
from that port range the port to be used by VPNS.EXE.
Compulsory Satellite Service nms.ini Flags
The cacher must always be set ON in the server.
CACHER = ON
Satellite Service stores the application views of the workstation applications in the cacher.
However, the cacher settings in the workstation have no effect. The cacher is not used in the
workstation, even if the cacher is set ON.
Workstation Configuration File Settings (nms.ini)
The compulsory fields to be filled out in the configuration file are CONFIGURATION,
COMPUTERNAME, MNGTSRV and SRV_SERVICE1. These parameters are filled by the
setup.exe program during the installation and those should not be edited manually.
CONFIGURATION = SATWS
COMPUTERNAME = <LAN name of the computer>
MNGTSRV = <LAN name of Management server running SATSRV>
SRV_SERVICE1 = DASHBOARDSATWKST (this enables starting of
Dashboard when executing Supervisor application)
If the SATSRV_COMPNAME parameter is given, the workstation will be connected to the
Management Server that has the same LAN name that is defined in that field, otherwise the
Management Server defined in the MNGTSRV parameter is used. It is recommended to use
Satellite Service in the Preferred Management Server and to keep the SATSRV_COMPNAME
parameter disabled. In both of these cases no load balance is used. Every 8000 Intelligent
Network Manager application running on the workstation uses the same Management Server. The
connections are direct without load sharing.
Trace Flags in Satellite Service
### PS and Satellite Server trace (YES/NO)

SATSRV_CHGMSG_TRACE = YES

42
2 Management Server
### PS and Satellite Server communications/filtering trace

(YES/NO)
RPC_TRACE = YES
### Log PS and Satellite Server security events (YES/NO)
SRV_COMM_SECURITY_LOG = YES
### Log file name, full path
SRV_COMM_SECURITY_FILE = %nmsdir%\log\sec.log
### PS and Satellite Service Error log file name, full path
SRV_COMM_ERROR_FILE = %nmsdir%\log\err.log
The SATSRV_CHGMSG_TRACE flag is used to trace change messaging activity of the Satellite
Service in a Management Server. It can be used in Management Server and workstation. The
change messaging activity concerns all kinds of trace printing that is related to the Satellite Service
change messaging system, e.g. select change requests that applications send to Management Server
with Satellite Service (tables and logical objects ordered by the 8000 Intelligent Network Manager
applications), incoming change messages in Management Server, change message sending from
Management Server to the workstation and receiving incoming change messages in the workstation.
This flag requires level 9 tracing.
RPC_TRACE is used for tracing RPC information in the Satellite Service system, and it can
be used in both the Management Server running Satellite Service and the workstation. RPC
communication is traffic between the workstation and Management Server. The workstation is
calling the OSR API functions of the server remotely, and the server is responding to the calls. This
flag requires level 9 tracing.
SRV_COMM_SECURITY_LOG can be set to YES or NO. The default is YES after the
installation of the Management Server. This applies only to a Management Server where
some security issues are traced, e.g. server startup and the maximum number of service
processes. If the flag is set to YES, it produces a log file with the name and path defined in the
SRV_COMM_SECURITY_FILE flag. By default, the %NMSDIR%\LOG directory is used.
The SRV_COMM_ERROR_FILE flag is used both in Management Server and workstation. It

prints error information to the specified log file. By default, the %NMSDIR%\LOG directory is
used.
Recovery Server Connection
Recovery Server connection is not required in the ini file anymore, it is handled automatically
by the software.
Controlling Management Servers
A shortcut to SUPERVISOR.EXE starts Management Server. The 8000 Server Command

Center dialog can be started by launching a shortcut to the Server Command Center. The 8000
Server Command Center dialog can be started independently of the state of Management Server
(whether the server is started or not).
After the startup, the 8000 Server Command Center dialog shows the state of the Satellite Service
(SATSRV). It also shows the processes belonging to the server service and the active workstations
of the server.
The server name in the 8000 Server Command Center dialog is either local or it has the name of
the (remote) Management Server to be controlled.
Data of the controlled server is updated automatically in the 8000 Server Command Center dialog.

43
2 Management Server
Local Server Configuration
If the server name is local in the Server Name drop-down list, all those controlling operations that
can be generated with the 8000 Server Command Center dialog are directed to the local server
computer (Management Server is running on the same computer as the 8000 Server Command
Center dialog).
Controlling the local Management Server computer does not require any nms.ini file settings.
Starting Management Server Running Satellite Service
For information on starting Management Server, refer to chapter 1.2.1 Starting Servers.
Starting Management Server Running Satellite Service as Windows Service
Management Server running Satellite Service can be installed as a Windows service. This enables
restarting the server automatically at computer startup. For more information on setting a server as a
Windows service, refer to chapter 2.12.5 Installing Management Servers with Satellite Service.
2.12.7 Workstations
General
With the workstation you can perform all the operations that can be done with the previous standard
workstation (workstation client type in releases prior to SR4.2).
Starting Workstation
Starting workstation means starting the Dashboard application in the workstation computer. The
Dashboard is started by executing the binary SUPERVISOR.EXE. There is a shortcut icon on the
desktop for this if creating shortcut icons was selected during the installation. All the necessary
system settings must be in the nms.ini files of the system, and Satellite Service must be in the
running and enabled state.
The username of the operator and the name of the Management Server running Satellite Service to
which the workstation is connected is shown at the bottom of the Dashboard screen.
Managing Remote Servers from Workstation Computer
The Management Server computers can be controlled by giving controlling commands to these
servers from the workstation.
It is possible to start the 8000 Server Command Center dialog (srvctrui.exe) to control only a
single server computer. The name of the computer is given as a command line parameter. The
prerequisite is that the operator has logged in to the system with the privileges to control servers.
Moreover, controlling multiple servers is also possible by starting the 8000 Server Command
Center dialog in a workstation computer. The operator must first login to the system and must have
privileges to control servers. SRVCTRUI.EXE is started with the following command.

44
2 Management Server
%NMSINSTDIR%\bin\srvctrui all_servers
You can configure or target the controlling operations of the 8000 Server Command Center
dialog for the desired server computer (for the computer that has been selected from the Server
Name drop-down list).
When controlling multiple remote servers, the server names are read from the nms.ini file. The
server names are declared in the nms.ini file according to the following principle.
SRV_COMPNAMEn = X
where n is an ordinal number between 1 … 99 and X is the name of the server.
The Satellite Service is selected from the Server Name drop-down list. The controlling command is
sent to the targeted server computer.
Fault Service Connections with Workstation
Fault clients running in a workstation need a connection to Management Server running Fault
Service if local fault polling process is not run in the workstation. In the recommended configuration
workstations are connected to Management Server running Satellite Service directly through a
separate LAN segment. The connections from workstations to any other computer than Management
Server with Satellite Service must be routed separately in order for the workstations to notify the
other computers in the 8000 Intelligent Network Manager system network.
Step List
Step 1 Define the static route in Management Server running Fault Service.
• Type route -p add <SATWS IP address> <SATSRV IP address> metric 1.
For example, if the workstation has the IP address 20.20.20.1 in its separate LAN, and
the Satellite Service (connected to the main LAN) has the IP address 172.19.20.205, the
command is route –p add 20.20.20.1 172.19.20.205 metric 1. The option [-p] makes the
route persistent so that the path does not vanish when the computer is booted. Metric 1
defines that there is one hop (Management Server running Satellite Service) between
Management Server running Fault Service and the workstation.
Command prompt must be launched using the Run as administrator menu in the UAC (User
Account Control) supported Windows operating systems such as Windows 2008.

45
2 Management Server
Step 2 Enable IP forwarding in Management Server running Satellite Service. IP forwarding must be
enabled in Satellite Service in order for the communication to work between the workstation and
Management Server running Fault Service.
• Locate the regedt32.exe file.
• Double-click the file.
Registry Editor opens.
• Browse to the following location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
• Locate the key named IPEnableRouter.
• Double-click the key. The Edit DWORD Value dialog opens.
• Type 1 into the Value Data entry field.
• Click OK.
Step 3 Map the name of the workstations and the name of the Management Servers running Fault Service
to their IP addresses in their hosts files (e.g. \WINNT\system32\drivers\etc\hosts).
<IP address> <machine name>
E.g. in the hosts file of the workstation the entry is as follows.
<Fault Service IP address> <Fault Service machine name>
6300 Craft Terminal
General
Craft Terminal can also be started from a workstation. In the recommended configuration where
Management Server running Satellite Service has two LAN interfaces, a static route must be
configured to the workstation on Communication Server to make Craft Terminal function on the
workstation (so that the workstation can communicate with Communication Server).
Step List
To define the static route and to enable IP forwarding, proceed as follows
Step 1 Define the static route in Communication Server.

route persistent, so that the path does not vanish when the computer is booted. Metric 1
defines that there is one hop (Management Server running Satellite Service) between the
Communication Server and the workstation.

46
2 Management Server
Communication Server.
• Browse to the following location
• Double-click the key.
The Edit DWORD Value dialog opens.
• Click OK.
Step 3 Check the validity of the route by pinging Communication Server from workstation, and vice versa.
7191 Craft Station
General
Note that the recommended tool to manage the 7100 network elements is 7100 Node Manager.
7191 Craft Station can be used with workstation. In the recommended configuration Management
Server running Satellite Service has two LAN interfaces, one LAN interface with workstation LAN
segment and the other with the 8000 Intelligent Network Manager LAN. In this configuration
a static route must be added on the Communication Server machine to enable communication
between workstation and Communication Server.
Step List
To define the static route and to enable IP forwarding, proceed as follows.
Step 1 Define the static route in Communication Server.

route persistent, so that the path does not vanish when the computer is booted. Metric 1
defines that there is one hop (Management Server running Satellite Service) between the
Communication Server and the workstation.

47
2 Management Server
Communication Server.
• Browse to the following location.
• Click OK.
Step 3 Check the validity of the route by pinging Communication Server from workstation, and vice versa.
8890 Client
General
Note that the recommended tool to manage the 8800 network elements is 8800 Node Manager.
8890 Client can be used with workstation. In the recommended configuration Management Server
running Satellite Service has two LAN interfaces. To enable workstation to communicate with 8890
Server a static route must be defined on 8890 Server.
Step List
To define the static route and to enable IP forwarding, proceed as follows.
Step 1 Define the static route in 8890 Server. The route to workstation is defined so that is goes through the
Satellite Service machine.

48
2 Management Server
8890 Server.
• Browse to the following location.
• Click OK.
Step 3 Check the validity of the route by pinging 8890 Server from workstation, and vice versa.
Typical error situations are related mostly to the stage during which the system is installed but the
workstations are not connected to the server.
System Recovery from LAN Breaks
If the LAN breaks are severe, the service processes and the capabilities of change handling are run
down for the workstation suffering from the LAN break.
After the most severe LAN breaks, network view errors can appear in the network level applications
when changing the view. In this case the network level application must be restarted.
Database Connections
The default number for simultaneous database connections from Management Server running
Satellite Service to Database server is 8. This is defined by the OBJS_DBPROCNUM flag in the
Management Server nms.ini file. If the number of connected workstations is increasing, there
might be a need to increase the OBJS_DBPROCNUM setting, however, so that the value of
OBJS_DBPROCNUM should not exceed the number of workstations served by the server.
The OBJS_DBPROCNUM flag value is read in the server only when the server is starting up. It
cannot be effectively changed during server run time. In the workstation this flag has no effect, it
is not read.
License (Program) Starting
Even if an appropriate license is installed, there can sometimes be problems starting the license
server program. There is a license server client running on every 8000 Intelligent Network Manager
computer and the startup of the licensing can sometimes terminate. The Dashboard application of
the workstation will try 600 times by default to get the process up.

49
2 Management Server
The time and iterations needed depend on, e.g., the size of the network. The LSLL (License server
binary) maximum wait time can be adjusted with the following flag in nms.ini of the workstation.
LSLLMAXWAIT = n
where n represents the number of iterations, e.g. 600.
2.13 Macro Manager Service
2.13.1 General
The Macro Manager Service handles operations related to macros. It contains the logic required
in macro compiling and execution.
2.13.2 Starting Macro Manager Service
After installing the Management Server successfully the following line should be found in nms.ini.
SRV_SERVICEx = MMSRV
This entry means that Supervisor will start the Macro Manager Service when Management
Server is started. The Macro Manager Service process is mmsrv.exe which is defined in the
mmsrv_service.ini file.
2.13.3 Configuring Macro Manager Service
The Macro Manager Service startup parameters are stored in the mmsrv_service.ini file, which
is located in the %NMSDIR%\dat\service directory. The file is used by the Supervisor process
and it is not to be edited. All the entries in this file are standard entries and described in chapter
1.1.2 Configuring Server Platform.
If you suspect any problems in the Macro Manager Service, you can add the following flags to
the nms.ini file.
The mmsrv process log file mmsrv.log will be created into the log directory and also more mmsrv
process specific data will be written to the mmsrv_ems.log and trace log files.
2.14 Web Reporter Service
The Web Reporter Service provides access to various 8000 Intelligent Network Manager reports.
The service enables the operator’s personnel groups or end customers to receive relevant network
data through the intranet or the Internet.

50
2 Management Server
The Web Reporter Service reads the 8000 INM database and it can provide e.g. the following
reports: general statistics, node, service, trunk, performance and different fault reports.
The Web Reporter Service is running on one Management Server at the time and the Web Reporter
tool requires a separate license.
For more detailed information on the installation and configuration of Web Reporter, refer to both
8000 Intelligent Network Manager Software Installation Manual and Web Reporter for 8000
Intelligent Network Manager Installation and Configuration Manual.
2.15 Scheduling Service
2.15.1 General
Scheduling Service is responsible for executing scheduled tasks at specified intervals.
2.15.2 Starting Scheduling Service
Scheduling Service is installed into the Management Server computer. After installing Management
Server successfully the following line should be found in nms.ini.
SRV_SERVICEx = GSSRV
The entry means that Supervisor will start the Scheduling Service when Management Server is
started. Before Scheduling Service can be started, Object Server must be up and running on the
same computer.
The following tasks can be scheduled with the Scheduling Service.
• Script/command line tasks. Any type of operating system scripts and commands can be sched-
uled.
• Maintenance tasks. The database maintenance tasks can be scheduled. The database requires
regular maintenance in order to function optimally. These are mandatory tasks, and a default
schedule is automatically installed.
• Remote maintenance tasks. Maintenance tasks for the replicate database can be scheduled
(mandatory if NMRS is used).
• Database polling. Certain types of data can be polled from the main tables to the secondary tables
for reporting purposes.
• Backup tasks. Database resiliency requires database backups to be taken in adequate intervals.
These are mandatory tasks, and a default schedule is automatically installed.
• Housekeeper tasks. Housekeeper tasks clean up obsolete data, monitor the Sybase database server
parameters and delete aged data. These are mandatory tasks, and a default schedule is automati-
cally installed.
• Web Reporter tasks. Web Reporter tasks can produce reports and collect trend data.
• Enhanced Reporting tasks. Reports can be scheduled and post-processed e.g. e-mailed.
• Stored procedure. The stored procedures can be scheduled.

51
2 Management Server
2.15.3 Configuring Scheduling Service
The Scheduling Service initialization file is called gssrv_service.ini and it is located in the
2.16 Node Management and Query Service
2.16.1 General
The Node Management and Query Service on the Management Server provides business logic and
infrastructure for multiple user components on multiple element types, including the Node Manager,
macro services, GMPLS management, enhanced reporting and Web Reporter. This infrastructure
includes dispatching requests to Communication Servers, forwarding alarm and other notifications,
executing user queries and assembling Microtopology views across network elements.
2.16.2 Starting Node Management and Query Service
The Node Management and Query Service is installed on the Management Server computer. After
installing Management Server successfully, the following line should be found in nms.ini.
SRV_SERVICEx = NMGRSRV
The entry means that the Supervisor starts the Node Management and Query Service when
Management Server is started. Before Node Management and Query Service can be started, Object
Server, NCAM and NAMS must be up and running on the same computer.
2.16.3 Configuring Node Management and Query Service
The Node Management and Query Service reads the common 8000 Intelligent Network Manager
configuration from the nms.ini file; there is no special configuration for this service.
The Node Management and Query Service process configuration file, used only by the Supervisor,
is found in the following location: %NMSDIR%\dat\service\nmgrsrv_service.ini. As a rule,
this file should not be edited.
There is also a private configuration file, which can be found as follows: %NMS-
DIR%\ems\mw\cfg\emsSettings. This file should also normally not be edited. It contains low-level
configuration and tuning parameters, and, if edited, it must in many cases also be edited on any
Communication Servers.
The Node Management and Query Service, by default, produces a variety of trace files in this
location: %NMSDIR%\ems\mw\log.

52
2 Management Server
Trace files are named after the corresponding process with randomly-generated suffixes, and “roll
over” such that the newest file always ends in .0, the next-newest file in .1, etc. (the maximum
allowable log size is controlled by values in the above-mentioned emsSettings file; the default
is 20 files of 20 MB each.).
This level of tracing does not need to be explicitly enabled, and should normally not be explicitly
disabled, as it is designed to provide useful output while limiting disk usage and not impacting
performance. Captures of diagnostic data should normally be made by zipping up this entire
directory.
If a problem specific to database access is suspected, deeper database logging may be enabled by
creating the %NMSDIR%\ems\mw\log\DBLOG file.
Note that this file name does not have an extension, and note that the contents of this file do not
matter and it may be empty. The presence of this file dynamically requests the running Node
Management and Query Service processes to start writing every SQL statement they execute into
their trace files. Once the file is deleted again, the extra tracing ceases. This typically increases the
trace output significantly, causing log data to roll over more quickly and the saved history to be
shorter, so it is disabled by default.
2.17 SLA Service
The SLA Service component for the 6300 and 8100 systems is run on one server at the time and
used for calculating 24-hour G.826 performance history data for TDM circuits and trunks in the
network. Performance history data is calculated into the 8000 Intelligent Network Manager database
to be accessed through the Northbound Interface Service. SLA Service requires a Performance
Management license.
It is recommended to use a dedicated Management Server for SLA Service.

SLA Service must not be configured in more than one Management Server in the whole
8000 Intelligent Network Manager system.

53
3 Recovery Server
3 Recovery Server
Recovery Server provides facilities to restore user communication links if trunk or node faults occur
in the 8100 system network. The Recovery Server is used for circuit and trunk protection. Recovery
Server is optional and runs on a dedicated recovery computer. If there is only one DXX Server in
the system, both Recovery and DXX Servers can run in the same computer.
Recovery Server can be installed in a separate computer (standalone installation) or in the same
computer with a DXX Server (combined installation). The combined installation is suitable for
small networks; for medium to large networks the standalone installation is recommended.
For detailed instructions on how to install Recovery Server both as a standalone or combined with
DXX Server, see 8000 Intelligent Network Manager Software Installation Manual.
3.1 Configuration
The behavior of the Recovery Server depends on the configurations, so it is recommended that
before starting the Recovery Server the related entries are checked and correctly set.
The configuration will be valid only on that single computer.
Recovery Server has to be located in the same LAN with the other servers. In this respect, the
requirements are similar to the DXX Server LAN requirements. Fast LAN connection between
the Recovery Server, Database Server and DXX Servers is highly recommended. For more
detailed information on LAN requirements, refer to 8000 Intelligent Network Manager Third Party
Hardware and Software Requirements.
3.2 Controlling Recovery Server
3.2.1 Starting Recovery Server
To start the Recovery Server proceed as follows.
Step 1 In the 8000 Intelligent Network Manager folder, double-click the Recovery Server shortcut.
Step 2 Once the server has been successfully started, make sure that the following executables, at least,
are running.
• rmss.exe
• rmst.exe
• rmsc.exe (and rmsa.exe if RMS_AMS = ON is enabled)

54
3 Recovery Server
Recovery Management System uses a single centralized Recovery Server (at a time) that provides
the recovery functionality. However, it is possible to switch a server over another one at any time.
The server switching operations can be initiated from the Recovery Control Program, assuming that
the required privileges are granted.
Recovery Server might need to be started after previous improper shutdown. Improper shutdown
can be noticed from the RCPR Control window, where another Recovery Server is shown Active
and Not responding. The RMS_BK_SWITCH entry settings will have the following effect.
• RMS_BK_SWITCH = OFF then the server can not be activated in case of previous improper
shutdown.
• RMS_BK_SWITCH = MAN then the server can be manually activated from RCPR even in case
of previous improper shutdown.
• RMS_BK_SWITCH = AUT then the server will be activated automatically after few tens of
minutes even in case of previous improper shutdown.
If previously in the network a Recovery Server was not properly stopped (for example tasks
terminated or killed), the related rmsserver record should be deleted from the database. If
the computer name of the Recovery Server in the network has not changed, the rmsserver
table can be left unmodified.
3.2.2 Stopping Recovery Server
To stop Recovery Server proceed as follows.
Step 1 In the 8000 Intelligent Network Manager folder, double-click on the Recovery Server Command
Center shortcut.
This will start dxxsoper.exe.
Step 2 In dxxsoper.exe, the following text will be displayed.
Remote DXX Server? (Y/N)
• If the server is running in a local computer select N.
• If the server is running in a remote computer select Y. In this case you will need to provide
the LAN name of the remote DXX Server.
Select option K (kill) for stopping the server.
Do not stop the tasks either from the 8000 Intelligent Network Manager Task Manager or the
task manager of the operating system. This can break transactions that are being processed,
leaving inconsistency between the hardware and the database.

55
Server Platform Related Parameters
Common Initialization File Settings (nms.ini)
The compulsory fields to be filled out in the nms.ini file of Communication and Management Server
are CONFIGURATION, SRV_SERVICEx, COMPUTERNAME, DBSRVR, DBNAME, and
the NameService and NotificationService host names. They identify the server in 8000 Intelligent
Network Manager and build up the database connection.
CONFIGURATION The name of the configuration:
• MNGTSRV in case of Management and
Communication Servers
SRV_SERVICEx The name of the server service. x can have the
values 1, 2, 3 etc. The first server service in the list
must have the value 1, and the second service must
have the value 2, etc. The name can be e.g.:
• EMSSRV in case of EMS Service
• VPNPSRV in case of VPN Provisioning Ser-
vice
For the names of the other services refer to the
related chapter in 2 Management Server.
COMPUTERNAME LAN name of the server computer
DBSRVR Name of the database server
DBNAME Name of the database
Other server platform related entries in the nms.ini file are listed below.
SRV_COMPNAME[x] LAN name of the computer. [x] can have values
1, 2, 3 etc. This parameter identifies the name of
the server whose Supervisor is to be managed with
Server Command Center.
DISABLE_COMMAND_VERIFICATION Defines if a command verification will be requested
in the 8000 Server Command Center dialog.
The default value is NO, which means that the
verification will be asked for.
SERVER_SHUTDOWN_AFTER_DB_DISCON- Defines if the server is shutdown after a LAN
NECT break. The default value is YES.

56
SERVER_SHUTDOWN_WAITTIME_AF- Defines the delay in seconds before the server is
TER_DB_DISCONNECT shutdown in a LAN break. The default value is 0.
SERVER_SINGLE_COMPUTER_MODE This parameter should be set to YES when using
the Single Server option for the Management
Server. The default value is NO.
Server Platform Trace Flags
The following trace flags are defined in nms.ini.
SUPERVISOR_TRACE = <YES/NO> Defines if supervisor debug traces are written into
the NmsTrace log file. NmsTrace should be started
at level 9. This option should be used with care
because the log file may increase rapidly and cause
operational problems in the server. The default
value is NO.
NMS_INFO_LOGGING = <TRUE/FALSE> Controls the normal information message tracing.
If the value is TRUE, all server processes write
information messages about the normal server
operation into NmsTrace. The traces are written
into the NmsTrace log file and the log file of the
process. The process log file is called [process
name].log and it is located in the %NMSDIR%\log
directory. The default value is FALSE.
[process name]_INFO_LOGGING = Defines if server process info logging is on for a
<TRUE/FALSE> specific server process. The traces are written into
the NmsTrace log file and also into the log file of
the process. The process log file is called [process
NMS_DEBUG_LOGGING = <TRUE/FALSE> Controls more detailed debug type message
tracing. If the value is TRUE, all server processes
write detailed information on their operations
into NmsTrace. This option should be used with
care because NmsTrace and process specific log
files may increase rapidly and cause operational
problems in the server. The traces are written into
[process name]_DEBUG_LOGGING = Defines if server process debug logging is on for a
<TRUE/FALSE> specific server process. The traces are written into

57
Service Specific Initialization File Settings
Each server service has its own initialization file. These files are located in the
%NMSDIR%\dat\service directory. SUPERVISOR needs these settings in order to know which
processes should be started and how. The files contain the following service specific information.
Normally, you do not need to change these parameters.
SERVICE_IS_INDEPEN- Defines if the service is related to the Object Server
DENT_FROM_SERVER_CORE = <YES/NO> or core service. The value YES means that if the
Object Server or a core service process fails, the
service will not be stopped. The default value is
NO.
SERVICE_COMMAND[x] = <command string> Defines service specific commands. The command
list can be seen in the 8000 Server Command
Center dialog.
SERVICE_IS_DEPENDENT_FROM_SER- Lists other services which the current service is
VICE[x] = <Service name> dependent on. If any of the listed services are
configured to start on the same server computer,
they will be started first.
SERVICE_RESTART = <YES/NO> Defines if a service is restarted after a shutdown
which has been made because a single process has
failed. The default value is NO.
SERVICE_TIMESTAMP_UPDATE_INTERVAL Defines how often the service timestamp is updated
= <time in seconds> to the database. The default value is 20 seconds.
A service is always shut down and restarted in case of an Object Server failure regardless of
the value of the SERVICE_RESTART parameter.
The server service initialization files contain the following server process specific information. [x]
can have values 1, 2, 3 etc.
SLAVE_PROCESS[x]_NAME = <process name> Defines the name of the process.
SLAVE_PROCESS[x]_NAME_EXT = <name> Defines the process name extension or a
user-friendly name.
SLAVE_PROCESS[x]_STARTTIME = <time in Defines the allowed start time for the process in
seconds> seconds. The process status should be changed
from starting to running during that time.
SLAVE_PROCESS[x]_STOPTIME = <time in Defines the allowed stop time for the process in
seconds> seconds. This is the time which the process can
spend on finalizing its actions before Supervisor
kills it.
SLAVE_PROCESS[x]_STARTPARAMS = Defines the process command line parameters.
<params>

58
SLAVE_PROCESS[x]_GENSRVSUPPORT = Defines if the process has server platform support.
<YES/NO> NO means that the process is a third party process.
The default value is YES.
SLAVE_PROCESS[x]_CONSOLE = <YES/NO> Defines if the process has a command prompt
window. The default value is NO.
SLAVE_PROCESS[x]_COMMON_PROCESS = If the same process is defined in another server
<YES/NO> service and the value is YES, only one instance of
the common process will be started. If the value is
NO, the process will be started in both services as
separate instances. The default value is YES.
SLAVE_PROCESS[x]_PRIORITY = <priority Defines the starting order among the other
value> processes of the same service. The process with
the smallest priority value will be started first.
SLAVE_PROCESS[x]_RESTART = <YES/NO> Defines if the process will be restarted after a
crash. The default value is YES.
SLAVE_PROCESS[x]_RESTART_TIME = Defines the time in seconds for which the process
<restart time in seconds> should have been running in order for a restart to
take place if the process fails.
SLAVE_PROCESS[x]_POLLING_INTERVAL = Defines how often the process status is polled by
<polling interval in seconds> Supervisor. The value is given in seconds.

59

8000 Intelligent Network Manager SR6.1 Installation and Configuration Guide For Management Server and Recovery Server

Uploaded by

Copyright:

Available Formats

You might also like

8000 Intelligent Network Manager SR6.1 Installation and Configuration Guide For Management Server and Recovery Server

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

8000 Intelligent Network Manager SR6.1 Installation and Configuration Guide For Management Server and Recovery Server

Uploaded by

Copyright:

Available Formats

8000 Intelligent Network Manager SR6.

© 2015 Coriant. All rights reserved.

8000 Intelligent Network Manager SR6.1 76.8061-70202A

Terms and Conventions

76.8061-70202A 8000 Intelligent Network Manager SR6.1

About the Manual .............................................................................................................. 8

1.1 Server Platform.................................................................................................................................................... 11

2 Management Server .................................................................................................... 15

76.8061-70202A 8000 Intelligent Network Manager SR6.1

2.6 Northbound Interface Service.............................................................................................................................. 30

8000 Intelligent Network Manager SR6.1 76.8061-70202A

3 Recovery Server .......................................................................................................... 54

3.1 Configuration ....................................................................................................................................................... 54

Server Platform Related Parameters............................................................................... 56

Common Initialization File Settings (nms.ini)............................................................................................................... 56

76.8061-70202A 8000 Intelligent Network Manager SR6.1

About the Manual

This manual is designed for software installation and administration personnel.

8000 Intelligent Network Manager SR6.1 76.8061-70202A

This is a note symbol. It emphasizes or supplements information in the document.

Please contact us to suggest improvements or to report errors in our documentation:

76.8061-70202A 8000 Intelligent Network Manager SR6.1

Fig. 1 Typical Configuration of 8000 Intelligent Network Manager

8000 Intelligent Network Manager SR6.1 76.8061-70202A

1.1 Server Platform

• VPN Provisioning Service

The server platform functionality can be described as follows.

• Server service definition

76.8061-70202A 8000 Intelligent Network Manager SR6.1

1.1.2 Configuring Server Platform

1.2 Controlling Communication Server and Management Server

1.2.1 Starting Servers

Step 1 Click the Server Command Center icon.

8000 Intelligent Network Manager SR6.1 76.8061-70202A

1.2.2 Stopping Servers

To stop Communication or Management Server, proceed as follows.

Step 1 Click the Server Command Center icon.

1.2.3 Controlling Servers with Server Command Center Application

Managing Remote Servers on Workstation

%NMSINSTDIR%\bin\SRVCTRUI <LAN name of server computer>

76.8061-70202A 8000 Intelligent Network Manager SR6.1

or by entering all_servers as the parameter.

The server names must be defined in nms.ini as follows.

SRV_COMPNAME[x] = <LAN name of server computer>

8000 Intelligent Network Manager SR6.1 76.8061-70202A

2.2 Management Server Services

2.2.1 Configuring Management Server Service

76.8061-70202A 8000 Intelligent Network Manager SR6.1

2.2.2 Backing up Management Server Services

2.2.3 Configuring Client/Server Relationships Manually

# PLT Server Background Manager

8000 Intelligent Network Manager SR6.1 76.8061-70202A

2.3 EMS Service

2.3.2 Starting EMS Service

2.3.3 Configuring EMS Service

The following parameters can be defined in nms.ini.

2.3.4 Configuring 8600 and 8800 Network Element Drivers

76.8061-70202A 8000 Intelligent Network Manager SR6.1