Processes and services

NNMi is built on a group of processes and services. For information about each process or service, see the following:

• Processes and services
• Processes and services

To verify that everything is running properly, you can use the ovstatus command:

• Verify that NNMi Processes Are Running
• Verify that NNMi Services are Running

Processes

Network Node Manager Processes

Process Name	Description
OVsPMD	The control process that manages all the other NNMi processes.
ovjboss	The process that controls the NNMi application server that contains all of the NNMi Services (see About Each NNMi Service for more information).
nnmaction	The process that controls the Action Server. The NNMi Action Server runs any actions configured for incidents. See Configure an Action for an Incident for more information about incident actions. See also the nnmaction Reference Page for more information
nmsdbmgr	NMS Database Manager. Controls the NNMi embedded database, including periodic database connectivity testing.

Verify that NNMi Processes Are Running

After you install Network Node Manager, a group of processes run on the NNMi management server.

To verify that all NNMi processes are running, do one of the following:

1. Select Tools → NNMi Status to display a report.

2. At the command line, type: ovstatus –c

   See the ovstatus Reference Page for more information.

Review the list of processes to ensure that all are running. For more information about each process, see About Each NNMi Process.

Stop or Start an NNMi Process

You can stop and start NNMi processes from the command line. See the ovstop and ovstart Reference Pages for more information.

To stop or start an NNMi process:

At the command line, type the appropriate command (see About Each NNMi Process):

ovstop <process name>

ovstart <process name>

To generate a list of process names, see Verify that NNMi Processes Are Running.

Services

NNMi Services run inside the ovjboss process. The ovjboss process controls the NNMi application server that contains all of the NNMi services.

Network Node Manager Services

ovjboss Service Name	Description
CommunicationModelService	Creates the cache for communication configuration and listens for changes.
CommunicationParametersStatsService	Tracks internal statistics for measuring SNMP and ICMP configuration performance.
CustomPoller	Provides MIB instance polling to augment out-of-the-box state polling (performed by StatePoller). Enables users to create configurations based on dynamic grouping. Data collected by CustomPoller can be consumed by the NNM iSPI Performance for Metrics.
IslandSpotterService	Automatically discovers any Island Node Groups using Layer 2 connectivity information in the topology. An Island Group is a group of fully-connected nodes discovered by NNMi, and NNMi determines this group is not connected to the rest of the topology.
ManagedNodeLicenseManager	Responsible for ensuring that the number of managed nodes does not exceed the NNMi licensed capacity limit.
MonitoringSettingsService	Calculates how to monitor each device based on the Monitoring Configuration settings.
NamedPoll	NMS Named Poll Service. Used to trigger immediate state polls for monitored objects. Used by the Causal EngineThe NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a Causal Engine management event has an Origin of NNMi in your incident views. during neighbor analysis and interface up/down investigations.
NnmTrapService	Used by trapd to receive traps from the standalone Operating System TrapReceiver process and forwards them to events.
NmsApa	NMS Active Problem Analyzer (APA) service determines the root cause of network problems and reports the root cause to the NMS Event Service. The NNMi APA service depends on the Causal EngineThe NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a Causal Engine management event has an Origin of NNMi in your incident views..
NmsCustomCorrelation	Custom Correlation Service. Enables the NNMi administrator to correlate one or more child incidents under an existing incident or a new parent incident.
NmsDisco	NMS Discovery Service. Adds new devices to the database and keeps the configuration of the managed devices up to date in the database by periodically rechecking the configuration of the devices. State Poller uses the Discovery service results to determine what to monitor. The Causal EngineThe NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a Causal Engine management event has an Origin of NNMi in your incident views. depends on the Discovery service to monitor node configurations. The Causal Engine uses the configuration information when calculating status and root cause. NNMi uses the information provided by the Discovery service to maintain current device configuration information.
NmsEvents	NMS Events Service. Populates and manages the information displayed in the incident table. The information displayed comes from the other NNMi services that are running on your system. The incidents are filtered so you see only the most important information about your network.
NmsEventsConfiguration	Handles incident configuration changes.
NmsExtensionNotificationService	Responsible for applications that are integrated into NNM using the extension deployment model.
NmsTrapReceiver	Used by NNMi events to receives traps from the NnmTrapService and sends them to the events pipeline. For information about the standalone TrapReceiver service that is started automatically by the Operating System, see NNMi TrapReceiver Process in the "NNMi Incidents" chapter of the Network Node Manager i Software Deployment Reference for more information.
PerformanceSpiConsumptionManager	Verifies licensing capacity for Network Node Manager iSPI Performance for Metrics Software.
SpmdjbossStart	The SpmdjbossStart service interacts with the OVsPMD process during startup (ovstart), shutdown (ovstop), and reporting on the status of the ovjboss services (ovstatus –v ovjboss). Caution If your NNMi management server participates in a high availability (HA) environment, under certain circumstances, you should not use ovstop or ovstart.
StagedIcmp	Used by the State Poller to ping IP addresses using the Internet Control Message Protocol (ICMP). Also used by auto-discovery if Ping Sweep is enabled.
StagedSnmp	Used by the State Poller and Discovery to perform Simple Network Management Protocol (SNMP) read-only queries.
StatePoller	NMS State Poller Service. State Poller collects measurements that assess the current state of discovered devices. This information is provided for the Causal EngineThe NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a Causal Engine management event has an Origin of NNMi in your incident views. to use when calculating device health.
TrapConfigurationServices	Merges configuration changes between the NNMi database and Trap Server.
TrapPropertiesService	Handles properties of the Trap Server.
TrustManager	Manages the trust information that is used when making trust decisions. Decides whether credentials presented by a peer should be accepted.

 

Network Node Manager iSPI Network Engineering Toolset Software Services (NNM iSPI NET)

ovjboss Service Name	Description
RbaManager	Requires Network Node Manager iSPI Network Engineering Toolset Software (NNM iSPI NET) and requires installation of a Diagnostic Server. Tracks internal statistics and provides performance counters related to diagnostic flow execution using Operations Orchestration servers through the Network Node Manager iSPI Network Engineering Toolset Software. See Rba.

Verify that NNMi Services are Running

After you install Network Node Manager, a group of services run on the NNMi management server. For information about each service, see About Each NNMi Service.

To verify that all NNMi services are running, do one of the following:

• Select Tools → NNMi Status to display a report.

• At the command line, type:

  ovstatus –v ovjboss

  See the ovstatus Reference Page for more information.

Review the list of services to ensure that all are running.

"Service is started" means this service is working properly.

"Service is stopped" means this service/process is not running.

If you see any of the messages in this list, investigate the log files and look for the keyword Exception (within the log file for the parent ovjboss process and the log file for the specific service):

"Service is in created state"
"Service is in failed state"
"Service is in registered state"
"Service is in destroyed state"
"Service is in started state"
"Service is in starting state"
"Service is in stopped state"
"Service is in stopping state"
"Service is in unregistered state"

• Windows:
  %NnmDataDir%\log\nnm\<name>.%g
• Linux:
  $NnmDataDir/log/nnm/<name>.%g.

%g represents the archive number of the archived log file

The parent ovjboss process generates the following log files: ovjboss.log and ovjboss.old.log.

Stop or Start NNMi Services

You can stop or start all NNMi services at the same time. You cannot start and stop most individual services. See the ovstop and ovstart Reference Page for more information.

To stop or start the NNMi services:

At the command line, type the command:

ovstop

ovstart