JP1 Version 12 Network Management: Getting Started


Organization of this preface

■ What you can do with JP1 network management products

Network management is essential for providing stable environments and services, but as networks continue to become larger and more complex each day, the workload of administrators also increases.

If you have encountered any of the problems shown below, take a look at your current system for network management and operation problems, and consider installing JP1 network management products. By doing so, you can efficiently monitor the status of the network to rapidly identify and solve failures.


JP1 network management products provide various windows from which you can get an intuitive understanding of the configuration of networks and the statuses of resources, and provide support for the day-to-day tasks of network administrators.


The JP1 network management products consist of manager programs to be installed on the Monitoring Manager, and agent programs to be installed on the monitored servers. The following figure shows the basic system configuration of JP1 network management products.


JP1/Network Node Manager i (hereinafter abbreviated to NNMi)

A manager program that uses industry-standard SNMP and that enables the management of network configurations and failures. You can use this program to automatically discover nodes in an IP network and to manage the network configuration. This program can also be used to detect network failures and issue warnings to the system administrator.

JP1/SNMP System Observer (hereinafter abbreviated to SSO)

A manager program that collects information about resources, performs alive-status monitoring of processes, and monitors the statuses of Windows services on the servers and network devices that support SNMP. By using this program, you can perform monitoring without differentiating between the vendors of network devices or between the agent types of servers.

JP1/Network Element Manager (hereinafter abbreviated to NEM)

A manager program that manages detailed information (such as port status, slot configuration, and the installation statuses of memory cards) from the GUI panel windows designed in the image of actual network devices. By using this program, you can easily and intuitively determine the statuses of network devices. Note that NEM can only be used in a Japanese environment for Windows.

JP1/Extensible SNMP Agent for Windows or JP1/Extensible SNMP Agent (hereinafter abbreviated to ESA)

An agent program that can obtain information about resources such as the CPU, memory, and file systems via SNMP. By using this program, you can obtain information that cannot be obtained by using OS-standard SNMP agents. This is a prerequisite program for JP1/SNMP System Observer - Agent for Process.

JP1/SNMP System Observer - Agent for Process (hereinafter abbreviated to SSO - AP)

An agent program that manages processes and services running on servers via SNMP.

The following table describes the main functionalities of the manager programs:





Node discovery

Automatically discovers nodes according to defined rules. Nodes can also be added manually.

Discovery and display of topologies

Automatically discovers the Layer 2 topology (network configuration using physical connection lines) in addition to the Layer 3 topology (logical network configuration), and then displays them in a map.

Monitoring by using ICMP/SNMP polling and SNMP traps

Monitors the statuses of objects by using ICMP and SNMP polling, and monitors failures by using SNMP traps.

Root cause analysis

Analyzes the root cause of a failure based on the Layer 2 and Layer 3 topologies that were discovered.

Incident management

Reports failures discovered through polling and SNMP traps as incidents.

Automatic action

Enables user-specified commands to be executed as automatic actions in response to certain incident statuses.


Resource collection

Monitors various system resources including server operational information (such as CPU usage and memory usage) and network performance information (such as line usage).

Monitoring of processes and services

Monitors the operating status of an application through the statuses of processes and services.


Panel operation

Displays windows designed in the image of the surface panels of network devices (switches and routers). By selecting a menu, you can monitor device statuses and perform operations on each device.

■ What is explained in this manual

This manual describes the basic methods for configuring and operating JP1 network management products. The goal of this manual is to enable users who read this manual to perform day-to-day tasks for network management and to rapidly handle failures by using the JP1 network management products.

The operating procedures described in this manual are based on the system configuration and organizational structure shown in the following figure.


Setup procedure explained in this manual

  1. The supervisor operator asks the system build engineer to set up an environment for the JP1 network management products.

  2. The system build engineer prepares a server to be used as the Monitoring Manager and then sets up the Monitoring Manager environment.

  3. The system build engineer asks each site system administrator to set up an environment for the Monitoring Agent.

  4. Each site system administrator sets up the Monitoring Agent environment and then notifies the system build engineer.

  5. After receiving notification from the site system administrators, the system build engineer configures the JP1 network management products.

  6. After configuring the JP1 network management products, the system build engineer notifies the supervisor operator.

  7. After receiving notification from the system build engineer, the supervisor operator registers an operator responsible as a user and starts operation using the JP1 network management products.

■ How to read this manual

In addition to this manual, the JP1 network management product provides multiple manuals and Help resources. To learn more about advanced functionality and operations, read these manuals and Help resources as shown below according to your purpose.


A reference to another manual is written as follows: For details about something, see topic-title in the manual-name. Using topic-title as a keyword, search for the relevant section in the target manual.

This manual assumes the use of the following environments:

For operations performed on the Monitoring Manager or Monitoring Agents

Windows: Environment where Windows Server 2012 is used

Linux: Environment where Linux 6.1 (x64) is used

For operations performed from the Web browser

Environment where Internet Explorer 11 is used

Some windows in this manual might differ from the windows of your product because of improvements made without prior notice.

■ Conventions: Fonts and symbols

The following table explains the text formatting conventions used in this manual:

Text formatting



Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:

  • From the File menu, choose Open.

  • Click the Cancel button.

  • In the Enter name entry box, type your name.


Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:

  • Write the command as follows:

    copy source-file target-file

  • The following message appears:

    A file was not found. (file = file-name)

Italic characters are also used for emphasis. For example:

  • Do not delete the configuration file.


Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:

  • At the prompt, enter dir.

  • Use the send command to send mail.

  • The following message is displayed:

    The password is incorrect.

The following table explains the symbols used in this manual:




In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example:

A|B|C means A, or B, or C.

{ }

In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example:

{A|B|C} means only one of A, or B, or C.

[ ]

In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example:

[A] means that you can specify A or nothing.

[B|C] means that you can specify B, or C, or nothing.


In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted.

In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example:

A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.