JP1 Version 13 Network Management: Getting Started

3021-3-L31-20(E)

Notices

Relevant program products

JP1/Network Node Manager i (for Windows)

P-2942-82DL JP1/Network Node Manager i 13-50

P-2942-89DL JP1/Network Node Manager i Developer's Toolkit 13-00

JP1/SNMP System Observer (for Windows)

P-2942-8RDL JP1/SNMP System Observer 13-00

JP1/Network Node Manager i (for Linux)

P-8442-82DL JP1/Network Node Manager i 13-50

P-8442-89DL JP1/Network Node Manager i Developer's Toolkit 13-00

JP1/SNMP System Observer (for Linux)

P-8442-8RDL JP1/SNMP System Observer 13-00

Trademarks

This product includes software developed by the Apache Software Foundation.

(http://www.apache.org)

This product includes software developed by the Indiana University Extreme! Lab.

(http://www.extreme.indiana.edu)

This product includes software developed by The Legion Of The Bouncy Castle.

(http://www.bouncycastle.org)

BSAFE is a trademark or registered trademark of Dell Inc. in the United States and other countries.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This product includes software developed by the University of California, Berkeley and its contributors.

This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).

Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

1. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

2. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)

3. This product includes software written by Tim Hudson (tjh@cryptsoft.com)

4. This product includes the OpenSSL Toolkit software used under OpenSSL License and Original SSLeay License. OpenSSL License and Original SSLeay License are as follow:

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a double license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts.

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2019 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by Andy Clark.

Java is a registered trademark of Oracle and/or its affiliates.

Other company and product names mentioned in this document may be the trademarks of their respective owners.

Microsoft product screen shots

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

Issued

Sep. 2025: 3021-3-L31-20(E)

Copyright

All Rights Reserved. Copyright (C) 2025, Hitachi, Ltd.

Copyright (C) 2023, 2025, Hitachi Solutions, Ltd.

This software and documentation are based in part on software and documentation under license from Open Text or one of its affiliates, including Micro Focus. The copyright for Open Text Software and Documentation is owned by Open Text. 2009-2025 Copyright Open Text.

Summary of amendments

The following table lists changes in this manual (3021-3-L31-20(E)) and product changes related to this manual.

Changes

Location

Windows Server 2025 was added as an applicable OS for the server on which the Monitoring Manager is to be set up.
1.2.1, C.2

In addition to the above changes, minor editorial corrections were made.

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 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 on the network devices that support SNMP. By using this program, you can perform monitoring without differentiating between the vendors of network devices.

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

Product

Functionality

Description

NNMi

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.

SSO

Resource collection

Monitors various system resources including network performance information (such as line usage).

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

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

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

The system build engineer configures the JP1 network management products.

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

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

Windows: Environment where Windows Server 2019 is used

Linux: Environment where Linux 8.1 (x64) is used

For operations performed from the Web browser

Environment where Microsoft Edge 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

Convention

Bold

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

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

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:

Symbol

Convention

|

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.

1 Setting Up JP1 Network Management Products

This chapter describes how you (the system build engineer) install JP1 network management products and create an environment that monitors the network.

1.1 General procedure for setting up JP1 network management products

To set up JP1 network management products, the Monitoring Manager needs to be set up. The procedure for setting up the Monitoring Manager is different between Windows and Linux.

The following table shows the general procedure for setting up the Monitoring Manager.

Task overview

Step

Task details

Reference

Windows

Linux

Preparation before installation

1

Check the server environment.

1.2.1

2

Check the prerequisites of the Monitoring Manager.

1.2.2

1.2.3

Setting up the Monitoring Manager

3

Install NNMi.

1.3.1

1.4.1

4

Install SSO.

1.3.2

1.4.2

5

Set up NNMi.

1.3.3

1.4.3

6

Set up SSO.

1.3.4

1.4.4

1.2 Preparation before installation

1.2.1 Checking the server environment

Before installing JP1 network management products, check whether the server environment to be used for operation is appropriate.

Before you begin

The following figure shows the system configuration that is assumed by this manual:

Procedure

Make sure that the specifications of the server on which the Monitoring Manager is to be set up satisfy the following conditions:

OS

For Windows: Windows Server 2016, Windows Server 2019, Windows Server 2022, or Windows Server 2025

For Linux: Linux 7.1, Linux 8.1, Linux 9.1, Oracle Linux 7.1, Oracle Linux 8.1, Oracle Linux 9.1, or SUSE Linux 12

Note that this manual describes the setup procedure for Windows Server 2019 and Linux 8.1.

Disk capacity:

For Windows: 14.5 GB or more

For Linux: 14.0 GB or more

Memory:

For Windows: 4.5 GB or more

For Linux: 6.0 GB or more

Check the language settings of the server on which the Monitoring Manager is to be set up.

For Windows, set the locale as follows:

For a Japanese environment: Japanese

For an English environment: English

For a Chinese environment: Chinese

For Linux, set the locale as follows:

For a Japanese environment: ja_JP.UTF-8

For an English environment: C

For a Chinese environment: zh_CN.utf8

Check the port number of the Web server.

The port number of the Web server is used during the installation of NNMi. The default HTTP port is 20480, and the default HTTPS port is 20481.

Make sure that the Web browser to be used satisfies the following conditions:

If the OS is Windows: Firefox ESR, Google Chrome or Microsoft Edge (Chromium version)

For details, see the Release Notes.

Next steps

After making sure that there is no problem in the server environment, proceed to the next task of checking the prerequisites.

Related topics

Topic Preinstallation Checklists in the JP1/Network Node Manager i Setup Guide.

1.2.2 Checking the prerequisites of the Monitoring Manager (for Windows)

1.2.3 Checking the prerequisites of the Monitoring Manager (for Linux)

1.2.2 Checking the prerequisites of the Monitoring Manager (for Windows)

If the Monitoring Manager is to run on Windows, check the settings below, and then start installing the JP1 network management products.

Before you begin

For details about the prerequisites, see the topic Preinstallation Checklists in the JP1/Network Node Manager i Setup Guide.

Procedure

Check the host name of the Monitoring Manager.

The host name is used when setting the trap destination and during login.

Make sure that the port number to be used by the Monitoring Manager is not used.

If you execute netstat -an at the command prompt, you can check the currently used port numbers.

For details about the port numbers, see the topic List of Ports Used by NNMi in the JP1/Network Node Manager i Setup Guide. For details about SSO, see Port Number Settings.

Assign a static IP address to the Monitoring Manager.

You need to assign a static IP address, not a dynamic IP address by DHCP.

Check the installation folder of NNMi.

The installation folder of NNMi is used during its installation. The default folders are as follows:

For the program: C:\Program Files (x86)\Hitachi\Cm2NNMi\

For data: C:\ProgramData\Hitachi\Cm2NNMi\

Consider the NNMi system account password.

The NNMi system account is used to sign in to the NNMi console first.

Between 1 and 40 characters can be entered for the password.

Alphanumeric characters (A to Z, a to z, 0 to 9), and underscores (_) can be used.

Check the installation folder of SSO.

The installation folder of SSO is used during its installation. The default folder is as follows:

C:\Program Files\HITACHI\JP1SSO\

Disable the antivirus software.

Disable the antivirus software only during the installation of the JP1 network management products.

Set the SNMP Trap service, which is a Windows SNMP-related service, to Disabled.

If you monitor the Monitoring Manager by using SNMP, make sure the SNMP service is available.

Use Windows Firewall to make sure that access to the port number used by the Monitoring Manager is enabled.

For details about access to the port number, see the topic Firewall pass-through direction in the JP1/Network Node Manager i Setup Guide.

Make sure that the values set for the environment variables TEMP and TMP are the same.

If the values of the environment variables TEMP and TMP differ, the installation of NNMi might fail. If the values differ, set the same value. Note that 500.0 MB of the %TEMP% folder is used during the installation.

Click Administrative Tools, Remote Desktop Services, and then Remote Desktop Session Host Configuration. Specify the Remote Desktop settings as follows:

Do not delete temporary folders on exit

Do not use temporary folders per session

Next steps

After you make sure that there is no problem in the prerequisite environment, proceed to the next task of setting up the Monitoring Manager.

Related topics

1.3 Setting up the Monitoring Manager (for Windows)

1.2.3 Checking the prerequisites of the Monitoring Manager (for Linux)

If the Monitoring Manager is to run on Linux, check the settings below, and then start installing the JP1 network management products.

Before you begin

For details about the prerequisites, see the topic Preinstallation Checklists in the JP1/Network Node Manager i Setup Guide.

Procedure

Check the host name of the Monitoring Manager.

The host name is used for setting the trap destination and during login.

Make sure that the port number to be used by the Monitoring Manager is not used.

If you execute netstat -an at the command prompt, you can check the currently used port numbers.

For details about the port numbers, see the topic List of Ports Used by NNMi in the JP1/Network Node Manager i Setup Guide.

Assign a static IP address to the Monitoring Manager.

You need to assign a static IP address, not a dynamic IP address by DHCP.

Disable the antivirus software.

Disable the antivirus software only during the installation of the JP1 network management products.

Make sure that the required packages are installed:

The required packages differ depending on the type or version of the OS. For details, see the Release Notes.

Open the /etc/sysctl.conf file, and set the kernel parameters.

Add the following entries to the /etc/sysctl.conf file:

# NNM settings for embedded database
kernel.shmmax = 68719476736
kernel.shmall = 68719476736
# NNM settings for UDP receive and send buffer sizes
net.core.rmem_max = 8388608
net.core.wmem_max = 2097152

In the entries above, the shared memory (kernel.shmmax, kernel.shmall) is set to 64.0 GB, the UDP receive buffer (net.core.rmem_max) is set to 8.0 MB, and the UDP send buffer (net.core.wmem_max) is set to 2.0 MB.

Next steps

After you make sure that there is no problem in the prerequisite environment, proceed to the next task of setting up the Monitoring Manager.

Related topics

1.4 Setting up the Monitoring Manager (for Linux)

1.2.4 Storage location of the commands of each product

The following shows the storage location of the commands of each product:

Storage location of the NNMi commands

For Windows

installation-folder-of-NNMi\bin\

For Linux

/opt/OV/bin/

Storage location of the SSO commands

For Windows

installation-folder-of-SSO\bin\

For Linux

/opt/CM2/SSO/bin/

1.3 Setting up the Monitoring Manager (for Windows)

You need to install and set up NNMi and SSO to set up the Monitoring Manager in a Windows environment.

1.3.1 Installing NNMi (for Windows)

If the Monitoring Manager is to run on Windows, use the Hitachi Integrated installer and follow the wizard to install NNMi.

Procedure

As a user with Administrators permissions, log in to the server on which the Monitoring Manager is to be set up, and then insert the distribution media.

Select JP1/Network Node Manager i.

A window to confirm the NNMi setting values appears.

Specify the port number of the Web server, and then press the Enter key.

If you press the Enter key without entering a value, the default value is specified. The default value of the http port is 20480, and the default value of the https port is 20481.

Specify the installation folder of NNMi.

If you press the Enter key without entering a value, the default value is specified. The default value is as follows:

For the program: C:\Program Files (x86)\Hitachi\Cm2NNMi\

For data: C:\ProgramData\Hitachi\Cm2NNMi\

The NNMi settings file, database, and log file are stored in the installation folder for data.

Enter yes, and then press the Enter key.

The installation of NNMi starts. After a while, you will be prompted to set the system account password.

Set the system account password.

Follow the instructions on the screen to set a password.

To set it after installation, enter \quit.

After the configuration is complete, press Enter to close the command prompt.

Next steps

Next, install SSO.

Related topics

1.3.2 Installing SSO (for Windows)

1.3.2 Installing SSO (for Windows)

If the Monitoring Manager is to run on Windows, use the Hitachi Integrated installer and follow the wizard to install SSO.

Procedure

As a user with Administrators permissions, log in to the server on which the Monitoring Manager is to be set up, and then insert the distribution media.

Select JP1/SNMP System Observer.

Install SSO by following the installer instructions.

Next steps

Next, set up NNMi.

Related topics

1.3.3 Setting up NNMi (for Windows)

1.3.3 Setting up NNMi (for Windows)

If you skip setting the system account password during installation, stop the NNMi service and set the system account. To register other members, first log in to the NNMi console, and then register users.

Before you begin

If the command prompt was opened before the installation and remains open, close it, and then open it again.

Procedure

Steps a. and b. are performed only if you skip setting the system account password during installation.

In the command prompt, execute ovstop -c to stop the NNMi service.

The NNMi service stops. Immediately after the installation, the NNMi service is stopped.

Execute nnmchangesyspw.ovpl to set the password.

Enter y, and then specify the password by following the message.

Execute ovstart -c to start NNMi.

Execute ovstatus -c to check the NNMi status.

If all statuses are in the running status, there is no problem.

Next steps

Next, set up SSO.

Related topics

1.2.4 Storage location of the commands of each product

2.2.3 Registering users

1.3.4 Setting up SSO (for Windows)

1.3.4 Setting up SSO (for Windows)

If the Monitoring Manager is to run on Windows, set the community name and the SSO definition information to set up SSO.

(1) Adding information about the connection from SSO to NNMi

Execute the ssonnmsetup command of SSO to set the connection information for linking with NNMi.

Procedure

Execute the following command:

ssonnmsetup -add -user user-name -password password -port port-number -ssl

Specify the user name and password of the system account. For port-number, specify the port number of the Web server. Specify the -ssl option only if HTTPS is used for communication.

Related topics

1.2.4 Storage location of the commands of each product

1.3.3 Setting up NNMi (for Windows)

1.2.1 Checking the server environment

(2) Setting the SSO definition information for NNMi

Execute a command to set the SSO definition information for NNMi.

Procedure

Execute the nnmconfigimport.ovpl command of NNMi to set the incident definition.

nnmconfigimport.ovpl -u user-name -p password -f installation-folder-of-SSO\incident\ssoincident.def

Specify the user name and password of the system account.

If an APM instance that does not use TCP communication for event notification is used to monitor processes or services, the following incident definition must also be set:

nnmconfigimport.ovpl -u user-name -p password -f installation-folder-of-SSO\incident\apmtrap.def

Execute the nnmconfigimport.ovpl command of NNMi to set the URL action definition.

nnmconfigimport.ovpl -u user-name -p password -f installation-folder-of-SSO\urlaction\ssourlaction.def

Specify the user name and password of the system account.

Execute the ssoauth command of SSO to register a user in SSO.

ssoauth -add -user user-name -password password

Set the user name and password that are used for logging in from the SSO console.

Execute the ssostart command of SSO to start SSO.

Execute the ssostatus command of SSO to check the SSO status.

If all statuses are in the running status, there is no problem.

Related topics

1.2.4 Storage location of the commands of each product

(3) Setting the community name

The community name is a password for accessing the MIB object by using the SNMP protocol. To collect resources, you need to match the get community names of the Monitoring Agent and the Monitoring Manager.

Procedure

Open the SNMP definition file (installation-folder-of-SSO\conf\ssosnmp.conf).

Edit the SNMP definition file.

Execute the ssoapcom command as follows to load the definition file again:

ssoapcom -r

Execute the ssocollectd command as follows to load the definition file again:

ssocollcetd -r

Next steps

You have now successfully completed the setup of the Monitoring Manager. Make sure that the setup of the Monitoring Agent at each site is complete. If the setup of the Monitoring Agent at each site is complete, proceed to the next task of setting up the JP1 network management products.

Related topics

1.2.4 Storage location of the commands of each product

1.3.3 Setting up NNMi (for Windows)

2. Configuring JP1 Network Management Products

1.3.5 Setting up WebGUI of SSO (for Windows)

Set up WebGUI of SSO on Windows where you use SSO Console.

Do the following by an user with Administrators permissions.

Procedure

Copy ssogui_fileset.zip file to the Windows and extract the zip file.

File location:

installation-folder-of-SSO\webgui\ssogui_fileset.zip

Execute the following command included in the extracted folder at command prompt.

extracted-path\SSOGUI\bin\webguisetup.bat extracted-path\SSOGUI

1.4 Setting up the Monitoring Manager (for Linux)

Install and set up NNMi and SSO to set up the Monitoring Manager in a Linux environment.

1.4.1 Installing NNMi (for Linux)

If the Monitoring Manager is to run on Linux, use the Hitachi Integrated installer and follow the wizard to install NNMi.

Procedure

As a user with root permissions, log in to the server on which the Monitoring Manager is to be set up.

For the environment variable LC_ALL, LANG, set the following locale:

For a Japanese environment

# LC_ALL=ja_JP.utf8

# export LC_ALL

# LANG=ja_JP.utf8

# export LANG

or

# LC_ALL=ja_JP.UTF-8

# export LC_ALL

# LANG=ja_JP.UTF-8

# export LANG

For an English environment

# LC_ALL=C

# export LC_ALL

# LANG=C

# export LANG

or

# LC_ALL=en_US.utf8

# export LC_ALL

# LANG=en_US.utf8

# export LANG

or

# LC_ALL=en_US.UTF-8

# export LC_ALL

# LANG=en_US.UTF-8

# export LANG

For a Chinese environment

# LC_ALL=zh_CN.utf8

# export LC_ALL

# LANG=zh_CN.utf8

# export LANG

Insert the distribution media of NNMi, and then execute the following command:

/mount-directory-name-of-the-provided-media/X64LIN/setup /mount-directory-name-of-the-provided-media

In the initial window of Hitachi PP Installer, enter I.

Select JP1/Network Node Manager i, and then enter I.

A message confirming that you want to continue the installation appears.

Enter Y.

Enter information by following the installer instructions.

If you press the Enter key without entering a value, the default value is specified.

NNMi is installed in the following folders:

For the program: /opt/OV/

For data: /var/opt/OV/

After a while, you will be prompted to enter the password for the system account. To set it after installation, enter \quit.

Next steps

Next, install SSO.

Related topics

1.4.2 Installing SSO (for Linux)

1.4.2 Installing SSO (for Linux)

If the Monitoring Manager is to run on Linux, use the Hitachi Integrated installer and follow the wizard to install SSO.

Procedure

As a user with root permissions, log in to the server on which the Monitoring Manager is to be set up, and then insert the distribution media.

Execute the following command:

/mount-directory-name-of-the-provided-media/X64LIN/setup /mount-directory-name-of-the-provided-media

In the initial window of Hitachi PP Installer, enter I.

Select JP1/SNMP System Observer, and then enter I.

A message confirming that you want to continue the installation appears.

Enter Y.

SSO is installed.

Next steps

Next, set up NNMi.

Related topics

1.4.3 Setting up NNMi (for Linux)

1.4.3 Setting up NNMi (for Linux)

If the Monitoring Manager is to run on Linux, set the system account to set up NNMi.

(1) Setting up the system account

If you skipped setting the System account password during installation, set the NNMi system account. The procedure for setting up the account is the same as that for Windows.

After setting the system account, set up SSO.

Related topics

1.2.4 Storage location of the commands of each product

1.3.3 Setting up NNMi (for Windows)

1.4.4 Setting up SSO (for Linux)

1.4.4 Setting up SSO (for Linux)

If the Monitoring Manager is to run on Linux, set the language environment and the definition information to set up SSO.

(1) Setting the language environment

After the installation of SSO is complete, you need to add the language setting to the /etc/rc.d/init.d/sso file.

Procedure

Open the /etc/rc.d/init.d/sso file.

Add the following two lines immediately after the line ./etc/rc.d/init.d/functions.

For a Japanese environment

LANG=ja_JP.UTF-8

export LANG

For an English environment

LANG=C

export LANG

For a Chinese environment

LANG=zh_CN.utf8

export LANG

Overwrite the /etc/rc.d/init.d/sso file.

Now, the language environment is set.

(2) Adding information about the connection from SSO to NNMi

Set the connection information for linking with NNMi. The procedure for setting the information is the same as that for Windows.

Related topics

(1) Adding information about the connection from SSO to NNMi

(3) Setting the SSO definition information for NNMi

Execute a command to set the SSO definition information for NNMi.

Procedure

Execute the nnmconfigimport.ovpl command of NNMi to set the incident definition.

nnmconfigimport.ovpl -u user-name -p password -f /etc/opt/CM2/SSO/incident/ssoincident.def

Specify the user name and password of the system account.

If an APM instance that does not use TCP communication for event notification is used to monitor processes or services, the following incident definition must also be set:

nnmconfigimport.ovpl -u user-name -p password -f installation-folder-of-SSO \incident\apmtrap.def

Execute the nnmconfigimport.ovpl command of NNMi to set the URL action definition.

nnmconfigimport.ovpl -u user-name -p password -f /etc/opt/CM2/SSO/urlaction/ssourlaction.def

Specify the user name and password of the system account.

Execute the ssoauth command of SSO to register a user in SSO.

ssoauth -add -user user-name -password password

Set the user name and password that are used for logging in from the SSO console.

Execute the ssostart command of SSO to start SSO.

Execute the ssostatus command of SSO to check the SSO status.

If all statuses are in the running status, there is no problem.

Related topics

1.2.4 Storage location of the commands of each product

(4) Setting the community name

The community name is a password for accessing the MIB object by using the SNMP protocol. To collect resources, you need to match the get community names of the Monitoring Agent and the Monitoring Manager.

Procedure

Open the SNMP definition file (/etc/opt/CM2/SSO/conf/ssosnmp.conf).

Edit the SNMP definition file.

Execute the ssoapcom command as follows to load the definition file again:

ssoapcom -r

Execute the ssocollectd command as follows to load the definition file again:

ssocollcetd -r

Next steps

After setting the community name, make sure that the setup of the Monitoring Agent at each site is complete. If the setup of the Monitoring Agent at each site is complete, proceed to the task of setting up the JP1 network management products.

Related topics

1.2.4 Storage location of the commands of each product

(2) Setting the SSO definition information for NNMi

2. Configuring JP1 Network Management Products

1.4.5 Setting up WebGUI of SSO (for Linux)

Set up WebGUI of SSO on Windows where you use SSO Console.

Do the following by an user with Administrators permissions.

Procedure

Copy ssogui_fileset.zip file to the Windows and extract the zip file.

File location:

/etc/opt/CM2/SSO/webgui/ssogui_fileset.zip

Execute the following command included in the extracted folder at command prompt.

extracted-path\SSOGUI\bin\webguisetup.bat extracted-path\SSOGUI

2 Configuring JP1 Network Management Products

This chapter describes how you (the system build engineer) access NNMi or SSO to start network management.

2.1 General procedure for configuring JP1 network management products

The following table shows the general procedure for configuring JP1 network management products.

Task overview

Step

Task details

Reference

Configuring NNMi

1

Access NNMi.

2.2.1

2

Register users.

2.2.3

3

Configure communication protocols.

2.2.4

4

Discover a network.

2.2.5

5

Configure node groups.

2.2.6

6

Configure monitoring.

2.2.7

7

Configure incidents.

2.2.8

Configuring SSO

8

Access SSO.

2.3.1

9

Configure resource collection.

2.3.2

2.2 Configuring NNMi

2.2.1 Accessing NNMi

In the following procedure, from the Web browser, you access NNMi and start setup.

Before you begin

Configure the following Web browser settings:

Allow pop-up windows to open (disable the pop-up blocker).

Enable active scripting, and allow cookies to be saved.

Procedure

From the Web browser, access NNMi.

URL: http://host-name:port-number/nnm/

host-name: Specify the host name (FQDN) of the server on which you installed NNMi. You can also specify the IP address.

port-number: Specify the port number of the Web server specified during installation of NNMi.

The NNMi Sign in window is displayed.

Enter the user name and password.

Sign in by using the system account.

User name: system

Password: Password for the system account

Click Sign in.

The NNMi console is displayed.

Important

The user name of the system account is fixed to system. The system account is used for initial settings and maintenance work. We recommend not using this account during normal operations because the password for the account can be changed by using a command.

Next steps

You have now successfully signed in to NNMi. In the next section, you will learn basic operations while configuring NNMi.

Related topics

1.3.3 Setting up NNMi (for Windows)

1.4.3 Setting up NNMi (for Linux)

2.1 General procedure for configuring JP1 network management products

2.2.2 About the NNMi console

If you access NNMi, the NNMi console is displayed. Use the NNMi console to become familiar with basic operations. You can use the console as you like because the settings are not changed until you click (Save), (Save and Close), or (Delete).

From the NNMi console, you can use icons to view information and specify definitions. Place the cursor on an icon to display a description of the icon.

Clicking the Help menu displays the topic related to the window on which you are performing operations. From this topic, you can immediately check what you want to know about setup items, such as the number and type of specifiable characters.

2.2.3 Registering users

Create user accounts for the system administrator and supervisor operator to register users. First create a user account for the system administrator, and sign in again as that user. Then, create a user account for the supervisor operator.

Procedure

In the Configuration workspace, select Security and then Security Wizard.

Read the description under Welcome to the Configuration Security Wizard, and then click Next at the bottom of the window.

In the User Accounts field, click (Create User Account).

Enter the values in Name and Password, and then click Add.

The user account is created.

Example:

System administrator Name: nnmiadm, password: password

Supervisor operator Name: nnmiope, password: password

After adding the user, click Close.

Select the user account that you created, and then click the user group to which you want to assign the user.

Example:

nnmiadm: System administrator

nnmiope: Supervisor operator

Click Save & Close.

In the confirmation dialog box, click OK.

The user account is configured.

Note

What to do if you forgot the password:

For details about how to reset the password for a user account, see the topic Change user name and password of Configure user accounts in the Help for Administer.

To reset the password for the system account, use the nnmchangesyspw.ovpl command. If you want to change the password for a user account, you can change the password for the current user by clicking the File menu and then Change Password.

Next steps

You have now successfully registered users. In the Configuration workspace, select Security, and then User Account Mappings, to make sure that the created user accounts are displayed.

Related topics

1.3.3 Setting up NNMi (for Windows)

1.4.3 Setting up NNMi (for Linux)

2.2.4 Configuring communication protocols

2.2.4 Configuring communication protocols

NNMi uses SNMP and ICMP (ping) to discover and monitor devices, and receives SNMP traps (notifications of problems).

Before you begin

Devices are classified into SNMP devices that respond to SNMP and non-SNMP devices that do not respond to SNMP.

In the following procedure, you can configure the behavior of communication protocols SNMP and ICMP (ping) that NNMi uses to discover and monitor networks. In the procedure, the settings below are used as an example. Change the setting values as necessary.

Settings for the timeout and the number of retries for SNMP and ICMP: Default (do not change)

SNMP Minimum Security Level: Default (do not change)

Read Community Strings: public

Procedure

In the Configuration workspace, select Communication Configuration.

In the Default SNMPv1/v2 Community Strings tab, click (New).

Enter the value in Read Community Strings, and then click (Save and Close).

Example: Read Community Strings: public

If a network to be monitored uses multiple community strings, repeat steps 2 and 3 to specify those community strings. NNMi checks the community strings configured in the network in parallel, and uses the appropriate value.

In the Communication Configuration view, make sure that the configured settings are displayed, and then click (Save and Close).

The configured settings are saved.

Next steps

You have now successfully configured the communication protocols. Next, you will perform network discovery in the network to be monitored.

Related topics

2.2.5 Performing network discovery

2.2.5 Performing network discovery

NNMi collects information from devices on a network, and obtains the details of individual devices and the network configuration (topology).

(1) About network discovery

NNMi discovers details of the entire network by collecting via SNMP, ARP cache information of each device and information about adjacent devices recognized by a protocol such as LLDP.

The following description uses an example of network discovery using an ARP cache.

Note

NNMi can perform network discovery by using a ping sweep. The ping sweep method monitors a specified range of IP addresses by using ICMP (ping), and discovers devices that return a response. This method can be used to promptly discover devices in the specified network range, but it places a load on the network. Use a ping sweep that matches your operations. We recommend that you limit the target range when using a ping sweep.

(2) Layer 2 and Layer 3 topologies

NNMi can recognize and display the network topology (the network configuration) by using not only a Layer 3 topology but also a Layer 2 topology. By recognizing a Layer 2 topology (physical connection lines), you can analyze the causes of network problems in more detail.

Layer 2 topology

This topology displays a network configuration by using physical connection lines.

To check the connection lines between switches and terminals at the ends of a network, use a Layer 2 topology. By using it together with a Layer 3 topology, you can intuitively check the situation when a failure occurs, and understand the range affected by the failure.

Layer 3 topology

This topology displays a logical network configuration by using IP addresses.

To check the logical configuration of a core network, use a Layer 3 topology.

Tip

Layer 2 and Layer 3 are the terms that are used in the OSI seven-layer model.

Layer 2 (data link layer): Controls data transfer between physical links by using MAC addresses.

Layer 3 (network layer): Controls selection of routes in a network by using IP addresses.

For IP network communications or when configuring NNMi, you specify destinations by using IP addresses, and generally you do not need to be conscious of physical connections. NNMi recognizes physical connection lines, the Layer 2 topology, by collecting and analyzing MIB information about adjacent devices.

The following figure provides an example of displaying a Layer 2 topology when a failure occurs in the switch (S1) to which NNMi is connected to, and NNMi cannot communicate with the network beyond the switch.

(3) Specifying how to perform network discovery

You can discover network devices connected to the monitored network. Before you start network discovery, the system administrator needs to complete configuration of the Monitoring Agent.

Before you begin

To perform network discovery, you can use a method that performs network discovery automatically, or a method that performs network discovery of explicitly specified items. You can also use these methods in combination. The following table describes these methods, and gives examples of operations.

Discovery method

Description

Example of operation

Automatic discovery

In this method, NNMi automatically discovers devices according to the auto-discovery rules you specified.

You want to automatically discover the changes in a network.

There are many devices connected to a large-scale network.

Discovery of explicitly specified items

In this method, you explicitly specify a device as a discovery seed.

You want to strictly specify the targets to be managed.

The network configuration is fixed.

The following procedure describes how to discover explicitly specified items.

Procedure

In the Configuration workspace, click Discovery and Seeds, and then click (New).

Enter the IP address of the discovery seed in Hostname/IP, and click (Save and Close).

The discovery processing immediately starts for the specified discovery seed.

For the device to be set as a discovery seed, specify a router that supports SNMP and has much information about adjacent devices.

Click (Refresh).

Make sure that the specified discovery seed has been created.

Note

You can also use the nnmloadseeds.ovpl command as shown below to register discovery seeds in a batch operation.

To directly specify seeds:

Example: nnmloadseeds.ovpl -n 192.168.8.82 192.168.100.24

To specify a list of seeds:

Example: nnmloadseeds.ovpl -f c:\jp1\seeds.txt

Example of describing a seed file:

192.168.8.82 # node1

192.168.100.24 # node2

For details about the nnmloadseeds.ovpl command, see the topic displayed by selecting the Help menu, NNMi Documentation Library, Reference Pages, and then nnmloadseeds.ovpl.

Tip

If you want to perform network discovery automatically, in the Configuration workspace, select Discovery Configuration and then Auto-Discovery Rules. Also, when specifying IP Ranges, if you specify the IP addresses that you do not want to discover and set the range type to Ignored by rule, the IP addresses are excluded from discovery.

Use the operation of selecting Discovery Configuration and then Excluded IP Addresses only when excluding specific IP addresses from the discovered nodes. If you use this operation to specify nodes to be excluded from monitoring, the IP addresses might disappear while the nodes still remain. Use the method appropriate for your usage.

For details about automatic discovery, see the topic Setting up auto-discovery rules in the JP1/Network Node Manager i Setup Guide.

Related topics

1.2.4 Storage location of the commands of each product

(4) Checking the discovered network and devices

You can view a discovered network by using a topology map. Immediately after you configure the discovery settings, you can view the process of node discovery.

Procedure

Click the Topology Maps workspace and then Network Overview.

In the Network Overview view, check the network status.

Click the Inventory workspace and then Nodes.

Make sure that the devices that you specified as discovery targets are discovered and registered correctly. If the specified devices are displayed, the network discovery has been performed successfully.

Check Device Category and Device Profile to check what devices have been discovered.

Tip

If a node in a cluster system is included in the monitored targets, specify the logical IP address as an excluded IP address so that it is not monitored. If you do not configure this setting, a problem occurs if the node is deleted or the status of a different node is applied when the logical IP address is moved. For details, see the Release Notes.

Note

If a node that does not need to be monitored is discovered, you can either delete the node from the monitored targets or exclude it from the monitored targets.

To delete the node from the monitored targets:

In the Topology Maps workspace, select Network Overview and then the icon for the node that you want to delete. Note that if the node is specified as a discovery seed, the node is not removed from the list displayed in the Seeds view even if you delete it. Delete the discovery seed.

To exclude the node from the monitored targets:

In the Inventory workspace, select Nodes and then the target node. Select Actions, Management Mode, and Note Managed. Use this method if you do not want to delete the node from a map, or want to temporarily exclude the node from monitoring.

Related topics

(5) Deleting the discovery seeds for which discovery is complete

(5) Deleting the discovery seeds for which discovery is complete

After the network discovery is complete, delete the discovery seeds.

Procedure

In the Configuration workspace, click Discovery and then Seeds.

Select all discovery seeds, and then click (Delete).

To select multiple rows, click the rows while pressing the Ctrl key.

Verify that the discovery seeds have been deleted.

Next steps

You have now successfully performed network discovery. In the next section, you will configure node groups.

Related topics

2.2.6 Configuring node groups

2.2.6 Configuring node groups

By defining node groups, you can configure monitoring settings and perform filtering for each node group. You can also display any of the defined node groups as the initial screen of the NNMi console.

(1) About node groups

A node group is a collection of discovered network devices that are put into a group in a hierarchy, based on conditions such as IP address or device type. NNMi provides, as standard, node groups for which appropriate settings are configured for each of basic categories, such as Windows or routers. You can classify a node group into six hierarchies by defining child node groups.

You can also create a map (a node group map) that displays discovered network devices by dividing them into categories. By creating and using a node group map, you can understand the network configuration from a more focused viewpoint than by using a topology map. You can find the location in which a problem occurred more easily, and check the details immediately.

You can freely configure the background image of a node group map by using an image file. By customizing the display method to suit your purpose by, for example, setting the floor layout image, you can manage networks more effectively.

How to use the Important Nodes node group

In NNMi, the Important Nodes node group is configured as standard. You can register important servers and network devices to the Important Nodes node group.

If no reply is received from a registered important node, a NodeDown incident is issued for the device. If you have particular nodes for which you want incidents reported whenever those nodes do not respond, even when they are not the root cause of a failure, register the nodes as Important Nodes.

An incident is also issued when child node groups are put into a hierarchy and configured in the Important Nodes node group or a node that is included in another node group is added to the Important Nodes group.

(2) Configuring a node group

By configuring a node group, you can freely group discovered nodes regardless of the network configuration. The following procedure describes how to specify the attribute values to configure a node group.

Procedure

In the Configuration workspace, click Object Groups and then Node Groups.

Click (New).

Specify the name of the node group in Name.

Example: Name: System division

If you select the Add to View Filter List check box, the name of the node group to be created is displayed in the Nodes view, and in the Empty Group filter of the Incidents view.

In the Additional Filters tab, specify the conditions for nodes to be added to the node group.

Select the values in the Attribute and Operator fields, and enter a value in Value, and then click Append.

Example: Attribute: hostedIPAddress, Operator: between, Value: 10.208.102.2 to 10.208.102.254

The specified conditional expression is added to Filter String. To delete a conditional expression, select it, and then click Delete.

Tip

You can specify the range of IP addresses, device category, and installation location as grouping conditions. You can also specify flexible conditions by using SQL operators (such as between, in, and like). A node group can have a maximum of six hierarchical levels. You can use a node group as follows:

To define a node group map: Select Node Group Maps.

To adjust the monitoring method for each node group: Select Monitoring Configuration and then Node Settings.

To monitor performance for each node group: Select Monitoring, Custom Poller Configuration, and Custom Poller Policy.

Click (Save and Close).

The Node Groups view closes, and the node group is created.

Select and right-click the row of the created node group, and then click Node Group Details and Show Members (Include Child Groups).

Make sure that the nodes that you specified as targets are included in the node group.

Right-click the desired node group, and select Maps and then Node Group Maps.

The node group is displayed in a map format.

Note

NNMi provides various grouping conditions other than those that are set by using operators. The following table describes the tabs used to set grouping conditions, and provides examples of operations.

Tab for configuring the settings

Setup item

Example of operation

Device Filters

Device Category

Device Vendor

and others

Perform monitoring according to the importance of devices.

Set an appropriate monitoring method for each model.

Understand the situation immediately by reducing conditions so that, for example, only routers are displayed.

Additional Filters

hostedIPAddress (IP address)

sysLocation (location)

and others

Set monitoring conditions and filter the displayed items for each installation location or organization.

Additional Nodes

Node Hostname

Set particularly important nodes individually.

Set the nodes for which it is difficult to specify conditions.

Child Node Groups

Child Node Group

(Set in the hierarchy order)

Put node groups into a hierarchy for each workplace or region

(3) Configuring a node group map

By configuring a node group map, you can specify an image for the background image. You can also display the created node group map in the list of map names under the Topology Maps workspace.

Procedure

In the Configuration workspace, click Object Groups and then Node Groups.

Select the node group whose map you want to configure, right-click it to display the menu, and then click Maps and Node Group Maps.

From the File menu, click Open Node Group Map Settings.

From the Node Group pull-down menu, select the node group whose map you want to configure.

In the Background Image tab, specify the background image for the map in Background Image.

Enter the value in Background Image as follows:

Example: /nnmdocs/images/image-file-name

You can specify a .gif, .png, or .jpg file that can be displayed in the Web browser. Store the image file in the following folder for the Monitoring Manager:

For Windows

installation-data-folder\shared\nnm\www\htdocs\images

For Linux

/var/opt/OV/shared/nnm/www/htdocs/images

Specify a value in Topology Maps Ordering.

By specifying the value, you can configure the created node group to be displayed in Quick Access Maps under the Topology Maps workspace. The created node group is displayed after you complete the setting and sign in to NNMi again.

Select the Indicate Key Incidents check box.

If you select the check box, the icons in the map are enlarged if a key incident occurs, and you can easily find the location where the problem occurred.

After you complete the setting, click (Save and Close).

Adjust the icon positions, and then click (Save Map).

The icon positions are saved.

Next steps

You have now successfully configured the node group map. In the next section, configure monitoring definitions.

Related topics

2.2.7 Configuring monitoring settings

2.2.7 Configuring monitoring settings

NNMi periodically monitors devices discovered by network discovery.

(1) About monitoring

Monitoring is a process to periodically monitor whether nodes on a discovered network work properly. NNMi monitors target devices by using SNMP or ICMP (ping). By default, monitoring is performed at five-minute intervals to check the status of the targets.

The following table describes the relationship between the settings for communication, discovery, and monitoring, and communication protocols SNMP and ICMP (ping).

Target of configuration

Description

Location for configuring the setting

Setup item

Default value

Protocol behavior

Configure the timeout and retry count per communication for SNMP or ICMP (ping). Communications for discovery and monitoring are performed based on these settings.

Select the Configuration workspace and then Communication Configuration.

SNMP

Five minutes

(two retries)

ICMP (ping)

Behavior during network discovery

Configure the setting so that rediscovery is performed on a daily basis because generally the configuration of a network is not changed frequently.

Select the Configuration workspace, Discovery, and Discovery Configuration.

Sweep Interval

One day

Behavior during network monitoring

Configure the setting so that monitoring is performed in a short cycle to immediately discover a failure. However, configure the setting so that polling is performed in minutes to keep a proper monitoring load.

Select the Configuration workspace, Monitoring, and Monitoring Configuration.

Fault Polling Interval

Five minutes

Items that can be monitored by NNMi are displayed in the Inventory view. The following figure shows the correspondence between the items monitored by NNMi and a device.

(2) Viewing monitoring definitions and checking the monitoring method

NNMi provides monitoring definitions as standard to help you immediately start monitoring. Therefore, you do not need to change the settings unless you want to customize the monitoring method or polling interval. In the following procedure, you will view the standard monitoring definitions, and check the monitoring method.

Procedure

In the Configuration workspace, select Monitoring and then Monitoring Configuration.

Select the Default Settings tab.

The default monitoring settings are displayed.

Check the settings such as the targets to be monitored and the number of minutes set for the monitoring interval.

Select the Interface Settings tab or the Node Settings tab to view the monitoring definitions.

In the Node Settings tab, the following definitions are specified:

Routers

Networking infrastructure devices

Microsoft Windows systems

Non-SNMP devices

Double-click a monitoring definition item.

Monitoring definitions for the item are displayed.

An appropriate monitoring method is defined for each node type. Check and compare the difference in monitoring targets and monitoring interval among the methods.

Next steps

You have now successfully checked the default monitoring definitions. In the next section, you will configure incidents.

Related topics

(3) Items configured in monitoring definitions

2.2.8 Configuring incidents

(3) Items configured in monitoring definitions

NNMi provides, as standard, appropriate monitoring definitions as the settings for monitoring networks. Monitoring definitions define the type and cycle of polling performed during monitoring. By using these monitoring definitions, you can start network monitoring in an appropriate method immediately after installing NNMi.

You can configure the monitoring method in the Monitoring Configuration view. The following table describes the main monitoring definition items that can be defined.

Location for configuring the setting

Monitoring definition item

Description

Global Control field

Enable State Polling

Selecting this item monitors the operating status of SNMP agents, interfaces, and IP addresses.

SNMP agents: Monitored via SNMP

Interfaces: Monitored via SNMP

IP addresses: Monitored via ICMP (ping).

Enable Card Polling#

Selecting this item monitors the status of cards via SNMP.

Enable Chassis Polling#

Selecting this item monitors the status of the chassis via SNMP.

Enable Physical Sensor Polling#

Selecting this item monitors the status of physical sensors via SNMP.

Default Settings tab

Enable Management Address Polling

Selecting this item monitors the IP addresses that are classified as management addresses via ICMP (ping).

A management address is used by NNMi to communicate with the SNMP agent in its node.

Enable IP Address Fault Polling

Selecting this item monitors IP addresses via ICMP (ping).

Enable Interface Fault Polling

Selecting this item monitors the status of interfaces via SNMP.

Enable Card Fault Polling#

Selecting this item monitors the status of cards via SNMP.

Enable Chassis Fault Polling#

Selecting this item monitors the status of the chassis via SNMP.

Enable Physical Sensor Fault Polling#

Selecting this item monitors the status of physical sensors via SNMP.

Fault Polling Interval

Specify the interval for status monitoring.

Node Settings tab

Networking Infrastructure Devices

Core devices in the network are monitored. Not only SNMP devices but also components (fans, power supplies, etc.) are configured as targets to be monitored.

Non-SNMP Devices

Devices that do not respond to SNMP are automatically managed as non-SNMP devices. They are configured to be monitored via ICMP (ping), and therefore their active status can be monitored. If a non-SNMP device becomes able to respond to SNMP, it is managed via SNMP.

#: Cards, chassis, and physical sensors can be monitored only in specific models supported by NNMi.

2.2.8 Configuring incidents

NNMi analyzes problems discovered during monitoring and SNMP traps by using the functionality for resolving root causes, and if the root cause is identified, NNMi reports the cause as an incident.

(1) About incidents

An incident is network-related information with high importance that needs to be reported to the administrator. NNMi monitors a network, detects events that have occurred, analyzes them by using the functionality for analyzing root causes, and then reports only the incidents that the administrator needs to know about.

An incident is reported as a result of root cause analysis performed based on the information obtained through network monitoring via SNMP and ICMP (ping) and from problem reports by SNMP traps.

NNMi provides, as standard, definitions for approximately 150 types of incidents, including Management Event incidents and SNMP Trap incidents, which are configured as incident definitions corresponding to this network monitoring. These incident definitions correspond to various events, and therefore you can use them without change for operation.

For example, the information below is configured in the Management Event incidents as incidents that occur when a node goes down. The functionality for analyzing root causes analyzes the status, and reports the appropriate one from the incidents.

NodeDown (The node is down.)

NodeOrConnectionDown (The node or connection is down.)

As one of the operation methods, you can include a node in the Important Nodes node group. Monitor a NodeDown incident that is issued if an important node does not respond.

Examples of issued incidents

The table below provides examples of incidents that are generated when the node of a network device is down and stopped. The functionality for analyzing root causes reports only the root cause events as incidents.

To minimize the impact of a failure during the operation of a network, NNMi provides the following approaches to appropriately handle all incidents without omission.

Functionality

Description

Reference

Automatic action for incidents

You can configure the setting so that actions are automatically performed according to the lifecycle state of incidents.

2.2.8(4)

Failure monitoring through incidents

If an incident is generated, it is reported and displayed on the NNMi console. You can check the details by switching the windows between Topology Maps and Incident Browsing.

3.1

Incident lifecycle management

NNMi manages the progress of handling of an incident by lifecycle states.

4.2

You need to configure incidents in order to use the above functionality.

Related topics

2.2.6 Configuring node groups

(4) Configuring automatic actions for an incident

3.1 Network monitoring by using JP1 network management products

4.2 Troubleshooting mechanism

(2) Checking the details of incident settings

The JP1 network management products provide pre-configured standard incident settings usable for operations. In the following procedure, you will view the incident settings provided as standard, and check the basic items.

Procedure

In the Configuration workspace, click Incidents and then SNMP Trap Configurations or Management Event Configurations.

To check the incidents caused by SNMP traps, select SNMP Trap Configurations. To check the incidents detected by NNMi network monitoring, select Management Event Configurations.

Click the row of the incident that you want to check, and then click (Open).

The details of the incident configurations are displayed. As examples, check the following Management Event incidents that are generated when a node goes down.

NodeDown (The node is down.)

NodeOrConnectionDown (The node or connection is down.)

The meaning of the incident is displayed in Description.

Result

Check the details of incidents to deepen your understanding. If necessary, configure the incident for an SNMP trap, and set up automatic actions for the incident.

(3) Configuring SNMP trap incidents

Some network devices might provide SNMP trap definitions as an extended MIB file to report the occurrence of a failure by using an SNMP trap. NNMi provides many incident definitions for SNMP traps as standard, but you can also load a vendor-specific extended MIB file for a device such as a network device, and configure incident definitions for SNMP traps that are unique for the device. General MIB files contain MIB definitions and SNMP trap definitions. For details about MIB files for each vendor, see the vendor's manual. Many MIBs have already been loaded during installation of NNMi. You can view a list of loaded MIBs by selecting the Configuration workspace, MIBs, and Loaded MIBs.

Before you begin

To receive an SNMP trap, the following conditions must be met. If the conditions are not met, the trap is discarded.

The incident that corresponds to the SNMP trap is configured. In addition, the Enabled check box is selected.

The source node that issued the SNMP trap is discovered. In addition, the management mode of the node is set to Managed.

For details, see the topic Manage SNMP Traps in the Help for Administer. If you want to receive SNMP traps from a node that has not been discovered, see the topic Manage unresolved incoming SNMP traps in the Help for Administer.

Procedure

Execute the nnmloadmib.ovpl command of NNMi.

Example of specification: nnmloadmib.ovpl -load MIB-file-name

Executing this command loads the contents of the MIB file to NNMi. Specify the MIB file to be loaded for the -load option.

Execute the nnmincidentcfg.ovpl command of NNMi.

Example of specification: nnmincidentcfg.ovpl -loadTraps MIB-module-name

Executing this command creates the incident configuration from the MIB database of NNMi.

Specify the MIB module name defined in the MIB file for the -loadTraps option.

In the Configuration workspace, click Incidents and then SNMP Trap Configurations.

You can check the status of SNMP traps.

Note

You can also use the nnmtrapdump.ovpl command to check the status of SNMP traps.

Example:

nnmtrapdump.ovpl -source IP-address

Executing this command displays traps received from the IP address.

nnmtrapdump.ovpl -t

Executing this command continuously displays received traps. Use the command when you check the configuration.

For details, see the topic SNMP Traps view in the Help for Operators, and information displayed by clicking the Help menu, NNMi Documentation Library, Reference Pages, and nnmtrapdump.ovpl.

Note

To find the MIB module name, open the MIB file, and check the area around the top of the file. The name defined before DEFINITIONS ::= BEGIN is the MIB module name.

Example:

Example of a MIB module name

------ MIB Simple Sample

SAMPLE-MIB DEFINITIONS ::= BEGIN

In this example, the MIB module name is SAMPLE-MIB.

Related topics

1.2.4 Storage location of the commands of each product

(4) Configuring automatic actions for an incident

If you configure automatic actions for an incident, you can execute a specified command under a specific lifecycle state.

Context

Note

By linking to JP1/IM, you can send an email when a failure occurs and use a signal light.

Procedure

In the Configuration workspace, click Incidents and then SNMP Trap Configurations or Management Event Configurations.

To configure automatic actions for incidents caused by SNMP traps, select SNMP Trap Configurations. To configure automatic actions for incidents detected by NNMi network monitoring, select Management Event Configurations.

Click the row of the incident that you want to configure automatic actions, and then click (Open).

Switch the tab display by clicking , and if the Actions tab is displayed, click it.

Tip

If you want to configure different automatic actions for each node, you can specify conditions for each node by configuring the settings from the following tabs:

The Actions tab in the Interface Settings tab: You can specify conditions for each interface group.

The Actions tab in the Node Settings tab: You can specify conditions for each node group.

The Actions tab: The target is not limited.

The order of priority is the Interface Settings tab, the Node Settings tab, and the general Actions tab, from highest to lowest. Actions are performed only once because the action settings configured from a tab with a higher priority overwrite the settings configured from a tab with a lower priority. Therefore, for example, you can configure automatic actions for all nodes, and then different automatic actions for a specific node group.

For details, see the topic Configure Incidents in the Help for Administer.

Select the Enabled check box.

If you omit this setting, automatic actions are not performed even if an incident occurs.

Set Author to Customer.

The user needs to change the author to Customer before changing incident definitions.

Under Lifecycle Transition Actions on the Actions tab, click (New).

Select the timing for executing automatic actions in Lifecycle State.

Specify the setting as follows, depending on the timing you want to execute automatic actions:

Registered: When a failure is detected and an incident is issued, an automatic action is executed.

In Progress: When Lifecycle State becomes In Progress, such as when a person responsible for handling is assigned to an incident, or when an incident is investigated, an automatic action is executed.

Completed: When handling of the failure is completed and Lifecycle State becomes Completed, an automatic action is executed.

Closed: When NNMi detects that the failure has been solved and Lifecycle State becomes Closed, an automatic action is executed. For example, if you want a node to link with the report system when the node restarts after recovery, specify Closed.

Select a command type in Command Type.

To specify the Jython command, select Jython. To specify an execution file or a batch file, select ScriptOrExecutable.

Enter a command in Command.

If the command type is ScriptOrExecutable, enter a command that can be executed on the OS, and for which necessary parameters are specified.

Example:

msg.exe Administrator "Incident $name occurred at $sourceNodeName."

For details about how to enter commands whose command type is Jython, see the topic Configure an action for an incident in the Help for Administer.

Click (Save and Close).

In the SNMP Trap Configurations view or Management Event Configurations view, click (Save and Close).

The settings are saved.

Tip

To check the execution status of automatic actions, click the Tools menu and then Incident Actions Log. You can also check the status by using the following log file:

For Windows

NNMi-installation-data-folder\log\nnm\incidentActions.*.*.log

For Linux

/var/opt/OV/log/nnm/public/incidentActions.*.*.log

If you fail to select the Enabled check box of the action settings, automatic actions are not executed and the history is not output to the log file. If automatic actions are not performed, make sure that the Enabled check box is selected. For details, see the topic Configure Incidents in the Help for Administer.

Next steps

You have now successfully configured automatic actions for incidents. In the next section, access and configure SSO.

Related topics

2.3 Configuring SSO

2.3 Configuring SSO

With SSO, you can check the detailed server and network device status by using the resource collection functionality.

2.3.1 Accessing SSO

In this procedure you log in to SSO, and start configuring SSO.

Procedure

From the Web browser, access SSO.

http://host-name:port-number/SSOConsole/

For host-name, enter the host name of the Monitoring Manager. The default port number is 20393.

Enter the user name and password.

For user-name and password, enter the values that you set in the SSO definition information.

Click Login.

The SSO console is displayed.

Note

You can also display the SSO console by selecting the Windows Start menu, Programs and Features, SNMP System Observer, and SSO.

Next steps

You have now successfully logged in to SSO. In the next section, configure the settings to collect resources by using SSO.

Related topics

(2) Setting the SSO definition information for NNMi

2.3.2 Resource collection

2.3.2 Resource collection

By using SSO, you can collect system resources. If you configure the time zone, interval, and period, you can collect resources at regular intervals, and view them.

(1) About resource collection

Resource collection is a process for collecting system resources from the servers connected to a network and monitoring target resources that users arbitrarily configured.

With SSO, you can collect the user resources (resources that can be uniquely defined by a user) and system resources (performance information, statistical information, and operating information) of the network devices and various server products that are supported on the OS (Windows or Linux) and SNMP, and monitor the resources in real time. For example, you can perform monitoring by which an incident is issued when NIC interface utilization rate exceeds 90%. In addition to issuing incidents, any action can be executed automatically.

You can easily configure resources to be collected by selecting resources from those displayed in the GUI because resource candidates are registered in advance in SSO. You can also automate the operation because collection can be started and ended by using the command.

Tip

In the resource collection functionality of SSO, a substance of the source from which a resource is collected is defined as an instance, the smallest unit of resources that can be obtained from SNMP agents is defined as a subresource, and a group of multiple subresources is defined as a resource.

Note

You can create a report for any period such as month or hour, by using collected resources. You can check the operating trend of servers and network devices by checking the reports, and can create system operation plans more easily. You can output reports in CSV or HTML format. You can output a report that best suits your purpose because you can select various graph formats.

Related topics

Topic Resource IDs in the manual JP1/SNMP System Observer

(2) Starting resource collection

In this procedure, you configure the settings to collect resources by using SSO, and start resource collection.

Procedure

In the SSO console, click Resource Configuration.

Click Edit and then Add Collection Condition.

Select a monitored server, and then click Next.

Directly specify a monitoring object in New Server, or select a registered monitoring object in Registered Server.

Select whether to automatically determine the agent type of the monitored server, and then click Next.

Resources that can be collected differ depending on the agent type. Selecting Yes in the Add Collection Condition (2/3) wizard displays only the resources that can be collected for the agent type in the Add Collection Condition (3/3) wizard.

From Do not Collect, select the resources that you want to collect, and then click Add.

The selected resources are added to Collect.

Click Complete.

Resources to be collected are configured.

Select the resource for which you want to set the collection conditions, and then click Edit and then Change Collection Detail Condition. Select the instance, subresource, and collection mode.

If you do not set the collection conditions, all instances are subject to collection. For the collection mode, you can set whether to save the collected data and whether to monitor thresholds. To monitor thresholds, you also need to set the thresholds and commands that are executed when the thresholds are exceeded.

Click OK.

Resource collection conditions are configured.

Click Edit and then Set Collection Time Zone.

Configure the resource collection time zone if you want to collect resources in a fixed time zone every day.

Select the check box for the number in which you want to specify a time zone, and specify the start and stop times.

For example, to collect resources during the period between 8:00 and 18:00, specify 08:00:00 for the start time, and 18:00:00 for the stop time.

Click OK.

The resource collection time zone is configured.

Tip

You can also configure collection intervals to suit your purpose. By configuring collection intervals, you can reduce the load on the system. To configure collection intervals, click Edit and then Change Collection Interval.

To detect a sharp rise in the used amount or usage rate of resources, configure a short collection interval.

To monitor the resource usage for a long period, configure a long collection interval.

From the Actions menu, click Start Collection.

Configure the period of time for collecting resources in Start Collection and Stop Collection fields, and then click Start.

Resource collection is started.

If you have configured the collection time zone, make sure that the time zone is within the period from the start to the stop of collection specified in the Start Collection window.

Note

To manually stop resource collection, from the Resource Configuration window, select the resource that you want to stop collecting, and then from the Actions menu, click Stop Collection.

To check the status of resource collection, check the collection status in the Resource Configuration window. The current collection status is displayed by Deferred, Collecting, Completed, etc.

Result

Now resource collection has successfully started. You can start monitoring resources, such as by viewing collected resources and outputting the resources to a report.

Related topics

Topic Register Application window in the manual JP1/SNMP System Observer

Topic Remote Command window in the manual JP1/SNMP System Observer

3.1.4 Monitoring resources

3 Normal Operation by Using JP1 Network Management Products

After you start periodic monitoring of the network by using JP1 network management products, you can view the map windows or collected resources to get an understanding of the status of the entire network and start monitoring the network. In addition, to ensure continuous network management, periodically perform maintenance work.

3.1 Network monitoring by using JP1 network management products

3.1.1 Network monitoring types

There are several ways to monitor the network by using JP1 network management products. This subsection describes how to perform operations based on the map windows and how to check the resources.

(1) Monitoring by using topology maps (NNMi)

In NNMi, network configuration diagrams (topology maps) are automatically created based on the discovered network devices. For this reason, you can visually determine the status of the network immediately after starting operation.

From the topology map, you can distinguish, based on the shape of the icon, the type of the network device, such as a router or computer. In addition, based on the color of the icon, you can determine the status of the network device, such as whether a failure has occurred. You can view not only the Layer 3 topology of the network, but also the Layer 2 topology. This enables you to intuitively check the status when a failure occurs and to understand the affected range.

Related topics

3.1.3 Starting network monitoring

(2) Resource monitoring (SSO)

With SSO, you can collect information about user resources (resources that can be uniquely defined by a user) and system resources (performance information, statistics, and operational information) of network devices and various server products that support SNMP and the OS (Windows or Linux), and monitor those resources in real time. For example, you can monitor an incident that was issued when the NIC interface utilization rate exceeds 90%.

In addition to issuing an incident, you can also specify that an action is to be automatically executed.

Related topics

3.1.4 Monitoring resources

3.1.2 Polling

Polling is using SNMP and ICMP (pings) to periodically discover and monitor network devices. NNMi monitors the discovered network devices by performing polling based on the SNMP and ICMP protocols. NNMi monitors not only the statuses of network devices but also the statuses of the components (such as fans, power supplies, and voltages) of those devices. This enables a wide range of failure monitoring.

If you set an interval (in seconds, minutes, hours, or days), polling can be performed automatically and periodically. You can also perform polling manually when you want to perform polling immediately, for example, immediately after resolving a failure. You can set different polling conditions for multiple ranges, such as for each network device or for each node group. This enables you to change the interval of polling depending on the severity of each monitoring target.

Note

There are two types of polling:

Polling for discovery

Polling for monitoring

The above two types of polling are referred to by the following names according to the purpose or situation:

Polling for discovery

Discovery polling (polling performed immediately by selecting the Actions menu, Polling, and then Configuration Poll)

Rediscovery polling (periodic polling to rediscover discovered nodes to check whether the configuration has changed)

Setting polling (polling for discovering settings)

Finding polling (polling for finding nodes)

Polling for monitoring

Status polling (polling performed immediately to monitor statuses by selecting the Actions menu, Polling, and then Status Poll)

State polling (polling for monitoring states)

Fault polling (polling for monitoring whether a failure has occurred)

Demand polling (polling for immediate monitoring when a manual operation is performed)

3.1.3 Starting network monitoring

This subsection describes how to monitor a network by displaying the map windows (topology maps) of the network configuration. NNMi performs network monitoring. For example, the operation management center always displays the most important map on a large screen to monitor the network. Immediately after specifying discovery settings, you can check the progress of node discovery.

Before you begin

Before you can start monitoring the network, the person (operator) responsible for the monitoring operation must be registered as a user.

Procedure

Access the NNMi console.

In the Topology Maps workspace, click Network Overview.

Check the statuses of the nodes based on the colors and details of the icons.

If you select an icon on the map, detailed information is displayed in the Analysis pane at the bottom of the window. You can display or hide the Analysis pane by clicking .

Tip

To check the MIB information for a node, use the nnmsnmpwalk.ovpl command.

Icon colors and their meanings

By using the more than 6,000 types of device information registered in Device Profiles of the Configuration workspace, device types are automatically decided. When a device profile is decided, the shape of the icon used in maps is decided according to the category (device category). The following table shows the icon colors and their meanings in maps.

Icon color

Meaning

Icon color

Meaning

Green

Normal

Red

Critical

Light blue

Warning

Blue

Unknown

Yellow

Minor

Gray

Disable

Orange

Major

Beige

No Status

For details about icons, see the topic About Map Symbols in the Help Use.

Note

To temporarily stop monitoring during maintenance

You can stop monitoring and rediscovery by selecting a node from the topology map, selecting Management Mode from the Actions menu, and then selecting OUT OF SERVICE. Alternatively, you can stop monitoring by using the nnmmanagementmode.ovpl command to change the management mode to out of service.

To resume monitoring

To resume monitoring, select the node from the topology map, select Management Mode from the Actions menu, and then select Manage. Alternatively, you can resume monitoring by using the nnmmanagementmode.ovpl command to change the management mode to managed.

To list the nodes that were removed from the nodes to be managed

In the Management Mode workspace, click Unmanaged Nodes.

Tip

In general, a window times out if you do not perform any operations for a certain period of time. You can set the timeout time in the console timeout section that is displayed by clicking the Configuration workspace, User Interface, and then User Interface Configuration. The default is 18 hours.

Note that a window that you open by specifying a URL will not time out. If you want to continuously display a topology map for monitoring, specify the applicable URL.

Network Overview

http://host-name:port-number/nnm/launch?cmd=showNetworkOverview

Node Group Maps

http://host-name:port-number/nnm/launch?cmd=showNodeGroup&name=node-group-name#

#: To include a multi-byte character in a URL, you need to URL-encode the character. Use UTF-8 encoding to URL-encode the node group name, and then specify the name.

Example: Important node

%e9%87%8d%e8%a6%81%e3%81%aa%e3%83%8e%e3%83%bc%e3%83%89

In addition, to open multiple windows for monitoring, such as a topology map and an incident window, click to display the view in a new window. Alternatively, you can display multiple windows by entering a URL to open a window.

Tip

To set the initial window that is displayed when you sign in, specify the setting in the initial view section that is displayed by clicking User Interface Configuration. To display incidents, specify Open Key Incidents. To display a map, specify Network Overview. Note that, although you can also set a node group map created by a user for the initial window, you can specify only the first or last item in the map list. For this reason, you need to adjust the Topology Maps Ordering setting in the Node Group Map Settings window. For details, see the Configure the NNMi User Interface in the Help for Administer.

Next steps

You have now successfully displayed the topology map. Next, start monitoring the network.

Related topics

2.2.3 Registering users

3.1.4 Monitoring resources

View the resources to be monitored. SSO performs resource monitoring.

Before you begin

Set the conditions for collecting resources.

Procedure

Access the NNMi console.

In the Topology Maps workspace, click Network Overview.

Select the server whose resources you want to view, and from the Actions menu, click SNMP System Observer and Resource Data Reference.

Tip

If you click (Search), you can search for the server name you want to view.

Select the resource that you want to view, and select View and Collection Data Details.

From Collection Period List and Instance List, select the period and instance that you want to view, respectively.

Click List Display.

You can view a list of collected data.

Tip

In the Resource Data Reference window, you can copy or delete the data of the collected resources.

For example, you can secure free space in the database by copying and retaining the resources only for the period during which a problem occurred, and then deleting other unnecessary resources.

Next steps

You have now successfully viewed information about the collected resources. If necessary, you can output information about the collected resources to a report to understand the operational trends of the server and to make system operation plans.

Note

You can output information about the collected resources to a report by using Report Browser of the SSO console. To output a report, you need to configure the report settings in advance. For details about outputting reports, see the topic Report Configuration window in the manual JP1/SNMP System Observer.

Related topics

2.3.2 Resource collection

Topic Copy Collection Condition window in the manual JP1/SNMP System Observer

3.2 Periodic maintenance of JP1 network management products

To continuously perform network management, periodic maintenance work is important. This section describes the operational tasks of JP1 network management products.

3.2.1 Checking the NNMi operating status

To manage the network, NNMi first needs to be operating normally. Make sure that NNMi is operating normally.

Procedure

From the Help menu, click System Information.

In the Product tab, check Status.

Make sure the status is the normal level.

In the Health tab, check the detailed status of NNMi.

In the State Poller tab, check the operating status.

In the Database tab, check the number of discovered objects.

Result

You were able to confirm that NNMi was operating normally.

Tip

If a problem occurs in NNMi itself, a warning is displayed in yellow at the bottom of the NNMi console, and the NnmHealthOverallStatus incident is issued. If this incident is reported during operation, check Custom Attributes of Incident.

Related topics

Topic Check NNMi Health in the Help for Administer

3.2.2 Exporting or importing the NNMi settings

Storing the system settings for each important point and managing changed items are important operational tasks. With NNMi, you can export and import system settings. This enables you to obtain a snapshot of the current system settings, and to restore settings that contain a mistake by importing settings.

Procedure

Execute the nnmconfigexport.ovpl command or the nnmconfigimport.ovpl command.

The following table shows the execution examples of the nnmconfigexport.ovpl command and the nnmconfigimport.ovpl command.

Purpose

Command

To export all settings

nnmconfigexport.ovpl -c all -f c:\nnmiconf

To import all settings

nnmconfigimport.ovpl -f c:\nnmiconf

To import the settings of a node group

nnmconfigimport.ovpl -f c:\nnmiconf\nodegroup.xml

Result

You were able to export or import the NNMi settings.

Related topics

1.2.4 Storage location of the commands of each product

Topic Export and Import Configuration Settings in the Help for Administer

3.2.3 Backing up or restoring NNMi

Periodically backing up NNMi in preparation for unexpected situations (such as system failure or data loss due to an operational error) is an important operational task. You can perform an online backup of NNMi while continuing to monitor the network. Thus, you can systematically back up NNMi.

Procedure

Execute the nnmbackup.ovpl command or the nnmrestore.ovpl command.

The following table shows the execution examples of the nnmbackup.ovpl command and the nnmrestore.ovpl command.

Purpose

Command

To perform an online backup of NNMi as a whole

nnmbackup.ovpl -type online -scope all -force -target c:\nnmi

In the folder specified for -target, a folder whose name includes the date and time (for example, nnm-bak-20150922002454) is created.

To restore the backed up data

nnmrestore.ovpl -force -source c:\nnmi\nnm-bak-20150922002454

Result

You were able to back up or restore NNMi.

Related topics

1.2.4 Storage location of the commands of each product

Topic Backup and Restore NNMi in the Help for Administer

3.2.4 Archiving or deleting NNMi incidents

NNMi can record a maximum of 100,000 SNMP trap incidents in the database. In addition, you can use NNMi to automatically delete (trim) data starting from the oldest data, or save data to an archive to prevent an increase in data items from affecting performance.

(1) Checking the number of SNMP trap incidents

Check the number of SNMP trap incidents.

Procedure

In the Incident Browsing workspace, click SNMP Traps.

At the bottom of the displayed incident list, the number of SNMP trap incidents is displayed to the right of Total.

Result

You were able to check the number of SNMP trap incidents.

Note

When the number of SNMP trap incidents is close to the upper limit, the following incidents are reported:

90% of the upper limit: SnmpTrapLimitWarning

95% of the upper limit: SnmpTrapLimitMajor

Upper limit: SnmpTrapLimitCritical

Related topics

Topic Archive and Delete Incidents in the Help for Administer

(2) Enabling the automatic trimming feature

If you enable the automatic trimming feature, data can be automatically deleted (trimmed) starting from the oldest data or an archive can be automatically created during trimming when the number of SNMP trap incidents exceeds the specified number. The automatic trimming feature is enabled by default in the new installation environment. We recommend that you enable this feature for operation.

Related topics

Topic Configuring the auto-trim oldest SNMP trap incidents feature in the JP1/Network Node Manager i Setup Guide

3.2.5 Periodically deleting SSO collection data

The amount of data in the SSO collection database monotonically increases because the database does not have a retention period. Thus, as SSO continues to collect data and the size of the database increases, the collection or deletion performance of the database might decrease significantly. For this reason, we recommend that you periodically back up the database or delete collection data to maintain the performance of the collection database. Set the retention period of the collection data to a maximum of one year.

Procedure

Execute the ssodbdel command.

The following shows an execution example of the command to delete collection data for which the retention period has expired:

ssodbdel -all -stop BMONTH 13

When you execute this command, of the data in the collection database, data for which the retention period (of one year) has expired is deleted. If you execute this command on the first day of every month, the collection database will store data only for about one year.

Result

You were able to delete SSO collection data.

Related topics

1.2.4 Storage location of the commands of each product

Topic ssodbdel in the manual JP1/SNMP System Observer

4 Troubleshooting by Using JP1 Network Management Products

This chapter describes how to use the incident management features of JP1 network management products to quickly identify and solve failures.

4.1 Analyzing the root cause of a failure

When a failure occurs, the Monitoring Manager uses the functionality for analyzing root causes to investigate and filter the correlations among the large number of events that occur. The Monitoring Manager analyzes the failure based on the Layer 2 topology and Layer 3 topology to identify the root cause, and then reports the root cause as an incident. The Monitoring Manager manages the progress of incident handling (lifecycle state), from the occurrence of the problem to its solution.

The following uses an example of monitoring a network device (router) to check how to analyze the root cause.

If the Router03 node goes down, there is no response from a large number of interfaces and IP addresses that Router03 has.

A large number of failure events occur due to interface failures and no response from IP addresses.

The Monitoring Manager decides that the lack of responses from IP addresses was caused by the interface failures, and then suppresses the corresponding incidents.

Based on the fact that communication was lost at neighboring nodes, the Monitoring Manager decides the root cause is the Router03 node going down. The Monitoring Manager also decides that the interface failures were caused by the node going down, and associates the interface failures with the Router03 node going down.

The Router03 node going down is reported as the root-cause incident.

In addition, the Monitoring Manager effectively uses Layer 2 topology information to analyze the root cause even for multiple nodes that compose a network. The following table shows examples of analyzing the root cause by using a Layer 2 topology network configuration.

Analysis of a Layer 2 topology

Description

Normal time

The Monitoring Manager is connected to the top-level switch S1, and the networks that are being monitored are all in the normal status.

When a failure occurs in the top-level switch

Detailed failure: The top-level switch S1 went down.

Events that occur:

Communication with S1 is unavailable.

Communication with other switches via S1 is unavailable.

The Monitoring Manager handles this situation as follows:

Detects the failure of the S1 node.

Decides that the failure of S1 caused communication via S1 to be unavailable, suppresses the corresponding incidents, and then decides that the status is unclear.

As a result, the Monitoring Manager reports only the failure of S1 as the root-cause incident.

When a failure occurs in a middle-level switch

Detailed failure: The middle-level switch C2 went down.

Events that occur:

Communication with C2 is unavailable.

Each node interface connecting with C2 went down.

The Monitoring Manage handles this situation as follows:

Detects the failure of the C2 node.

Decides that each interface connecting with C2 went down because of the failure of C2, and then suppresses the corresponding incidents.

As a result, the Monitoring Manager reports only the failure of C2 as the root-cause incident.

The Monitoring Manager can also analyze many other correspondences between an event and a root cause.

4.2 Troubleshooting mechanism

The Monitoring Manager manages the progress of incident handling as lifecycle states in the Incidents view. If multiple persons share the management, you can specify a person responsible for the operation other than you (by using Assigned To) to share the tasks on the GUI when starting the tasks to resolve a failure.

As shown in the following figure, if you assign a person responsible for handling an incident and change the lifecycle state, you can appropriately handle a failure that occurred:

After reporting an incident, the Monitoring Manager continues to monitor the state. If the Monitoring Manager detects a recovery, the state of the incident is automatically set to Closed. For example, when a node for which NodeDown was reported starts operation again, the state of the incident is automatically set to Closed.

Tip

As an exercise illustrating the operation, the following describes how to cause a dummy failure to occur in order to check the reported incident:

Cause a failure to occur by disconnecting the LAN cable from a monitoring target node or stopping the node.

Make sure the problem will not affect your business's work.

After selecting the node in a map window, from the Actions menu, select Polling, and then select Status Poll.

The state polling is performed, and then the failure is detected.

4.3 Troubleshooting a network failure

You can use several methods to troubleshoot a network failure. This section describes how to handle a network device node going down.

4.3.1 Handling a network device node that is going down

If an incident reports a network device node going down, you need to check the location that has the problem, and then take corrective action.

Procedure

Use the topology map of the NNMi console to check the location in which a failure occurred.

When a failure is detected, the color of an icon on the map changes.

If you put maps into a hierarchy, open the child node group to check the status. For the status of a node group, the most critical status is displayed. The statuses of child node groups are applied to the parent node group.

Open the Incident Browsing workspace to check the incident that was reported as the root cause.

Open the Open Key Incidents view or the All Incidents view to reference the content of the incident, and then check the location that has the problem. If you select the target node, and then open the Incident tab, you can check occurrence of the incidents in chronological order. First, check Source Node, Source Object, and Custom Attributes.

Double-click the incident to check detailed information about the incident.

The Incident view is displayed. Use the message and name information to check the type of the incident. Use the source node information to check the location where the failure occurred. Use the date and time information to check the time when the failure occurred.

Note

For an SNMP trap incident, use the Custom Attributes tab to check the detailed information. In the Custom Attributes tab, the information reported by an SNMP trap is displayed. Check the content by referring to the documentation of the devices that issued the SNMP trap.

Set Lifecycle State of the incident to In Progress.

After you understand the details of the problem, from the Lifecycle State pull-down menu, select a state. Immediately after an incident is registered, the state is set to Registered.

From the Assigned To pull-down menu, select your account.

If you want to assign an operator other than you, make sure that the operator can access the assigned incident.

Click (Save and Close).

The changed setting is saved.

Check the situation of the related parts.

A network failure often affects related parts of the communication routes. Therefore, check not only the root cause but also the related parts.

In a map window, check the related parts to understand the situation.

In the Monitoring workspace, make sure that there is no part that has a problem.

Take corrective action.

If you configure automatic actions for an incident beforehand, the specified command can be automatically executed.

After taking corrective action, set Lifecycle State of the incident to Completed.

Closed is automatically set when the system identifies that there is no problem.

Click (Save and Close).

The changed setting is saved.

Check the changed state of the incident.

In the Incident Browsing view, make sure that Lifecycle State is set to Closed.

Result

You have now successfully taken corrective action for a network device node going down.

Related topics

(4) Configuring automatic actions for an incident

3.1.3 Starting network monitoring

4.2 Troubleshooting mechanism

Appendixes

A. Advanced Use

This appendix provides reference information for making full use of JP1 network management products.

Introduction to NNMi Advanced

Among the JP1 network products, NNMi Advanced is provided as a higher-level version of NNMi and enables monitoring that supports advanced network technology. The following table describes the main functionalities of NNMi Advanced.

Functionality

Description

Global network management

Enables central management by using a regional manager to monitor each site and a global manager to control the regional managers. A global manager can be used to manage a maximum of 80,000 nodes.

NNMi IPv6 Management Feature

Enables efficient and unified management of next-generation networks and existing networks, because NNMi Advanced can manage IPv6 and IPv4 networks at the same time.

Discover and monitor VMware hypervisor-based virtual networks

Enables automatic identification of ESX hosts and virtual machines in the same way as automatic identification of routers and switches, and enables you to manage inventory information in a list.

Discovering link aggregation

Automatically recognizes aggregated link configurations. In maps, aggregated links are displayed as thick lines.

Router Redundancy Group

Automatically recognizes the configuration of a redundant router group. In addition, this functionality enables you to monitor whether a router group routes packets appropriately.

For details, see the JP1/Network Node Manager i Setup Guide.

Introduction to operational methods

The following table provides examples of how to use the JP1 network management products. For details, see the locations listed in the Reference column.

Case example

Description

Reference

I want to try out the product. Is it easy to start using the products immediately?

To start using the products, perform the following three steps:

In Communication Configuration, configure the SNMP community strings.

In Discovery Configuration, specify the range of IP addresses to be automatically discovered, enable ping sweeps, and then enable SNMP node discovery.

In the Topology Maps work space, open Network Overview to start operations.

2.2.4

2.2.5

3.1.3

No nodes were discovered.

In Discovery Configuration, specify the range of IP addresses to be discovered, and then specify the discovery seed used as the starting point of discovery. You can check the discovery status from Topology Maps or Inventory. You can also check the status of the discovery processing by clicking the Help menu, System Information, and then State Poller.

2.2.5

Only routers and switches were discovered.

By default, only routers and switches will be discovered.

To change this setting, in Discovery Configuration, select Auto-Discovery Rules, and then select the Discover Any SNMP Device and Discover Non-SNMP Devices check boxes as needed.

2.2.5

After node groups were defined, the topology map became hard to read because too many topology map names were displayed.

If you specify a blank for Topology Maps Ordering of a node group map, the topology map name of the node group map will not be displayed in the Quick Access Maps folder under the Topology Maps workspace.

2.2.6

It is impossible to communicate with a node, but the status is determined to be unrecognized (blue icon) instead of critical.

For example, if a failure occurs on a switch located in the middle of a network route and communication with a certain node becomes unavailable, NNMi determines the switch to be the root cause and reports an incident. In addition, the statuses of nodes with which communication has become unavailable due to the failure are determined to be unrecognized. To report an incident when communication becomes unavailable, use important nodes.

2.2.6

2.2.8

How can I specify the IP address of the SNMP manager (NNMi)?

To specify the IP address of the SNMP manager (to permit a connection) in the SNMP settings on the SNMP agent side, specify all IP addresses of the NNMi manager, because an IP address that corresponds to the destination IP address will be dynamically selected depending on the network routing settings of the OS.

To revise the IP address, specify the IP address for NNM_INTERFACE in the ov.conf file. Adjust the routing settings of the OS to enable communication by using the fixed IP address.

Release Notes

An SNMP trap was issued, but it was not reported as an incident.

To report an SNMP trap as an incident when NNMi receives the SNMP trap, the node must have already been discovered and an incident for the relevant SNMP trap must already be defined and enabled. To change a trap issued from an undiscovered node to an incident, from Incident Configuration, clear the Discard Unresolved SNMP Traps and Syslog Messages check box.

Topic Manager Unresolved Incoming SNMP Traps in the Help for Administer

I want to create a list of servers or incidents.

In a window (such as the inventory window) where data is displayed in table format, you can output the data to a file in CSV format. To do this, for example, in the Inventory workspace, open Nodes, and then perform the following operations:

Select the row that you want to output.

Right-click the row, and then select Export to CSV from the displayed menu.

Perform operations according to the displayed information.

Import the output data into a spreadsheet application to create a list. You can create a list of nodes from data in the Nodes view, and a list of incidents from data in the Management Event Configuration view.

Topic Export Table Information of Use Table Views in the Help Use

B. Version Changes

B.1 Changes in version 13-50

(1) Changes in manual 3021-3-L31-20(E)

Windows Server 2025 was added as an applicable OS for the server on which the Monitoring Manager is to be set up.

B.2 Changes in version 13-10

(1) Changes in manual 3021-3-L31-10(E)

The maximum number of nodes managed by a global manager was changed.

B.3 Changes in version 13-00

(1) Changes in manual 3021-3-L31(E)

Descriptions related to JP1/Network Element Manager were deleted.

Descriptions related to the following products were changed or deleted.

JP1/Extensible SNMP Agent for Windows

JP1/Extensible SNMP Agent

JP1/SNMP System Observer - Agent for Process

The following operating systems were added as supported operating systems for the Monitoring Manager.

Linux 9.1

Oracle Linux 9.1

The following supported operating systems were removed.

Windows Server 2012

CentOS

Linux 6.1

Oracle Linux 6.1

The default values of the HTTP port and HTTPS port used by NNMi were changed.

Following the end of support for the Internet Explorer web browser, the relevant descriptions were deleted.

Descriptions related to the packages and library files required for the server to be used as the Monitoring Manager were changed.

B.4 Changes in version 12-60

(1) Changes in manual 3021-3-E01-30(E)

Windows Server 2022 was added to the applicable OSs of servers for the Monitoring Manager and Monitoring Agents.

The procedure was changed so that the system account password is set during installation of NNMi.

Setting of the system account password was added to the procedure for installing NNMi.

The locales set in the environment variables LC_ALL and LANG were changed.

B.5 Changes in version 12-50

(1) Changes in manual 3021-3-E01-20(E)

A description of the default value of the HTTPS port used by NNMi was added.

The description about supported OSs for servers used as the Monitoring Manager or as Monitoring Agents was changed.

The conditions on web browsers that can be used were changed.

A description about the packages and library files required as part of the prerequisite conditions for the Monitoring Manager was added.

A description about kernel.shmall was added.

LANG was added as an environment variable to be specified during the installation of NNMi.

A description about the language environment was deleted.

The description about the automatic trimming feature was changed.

B.6 Changes in version 12-10

(1) Changes in manual 3021-3-E01-10(E)

Windows Server 2019 was added as an applicable OS for the server on which the Monitoring Manager is to be set up.

B.7 Changes in version 12-00

(1) Changes in manual 3021-3-E01(E)

Windows Server 2008 R2 was removed from the applicable OSs.

The following were added to the OSs applicable for the server used as the Monitoring Agent:

SUSE Linux 15

AIX V7.2

The following were removed from the OSs applicable for the server used as the Monitoring Agent:

AIX V6.1

Solaris 10

Internet Explorer 10 is no longer supported.

The supported Firefox versions for Windows were changed. Also, Firefox for Linux is no longer supported.

The procedure for setting up JP1/SNMP System Observer was changed. Also, the descriptions about the Java Plug-in were deleted.

B.8 Changes in version 11-10

(1) Changes in manual 3021-3-A71-10(E)

Windows Server 2016 is now supported.

The following browser is no longer supported:

Internet Explorer 9

Supported Firefox versions were changed.

C. Reference Material for This Manual

This appendix provides reference information, including various conventions, for this manual.

C.1 Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

JP1 Version 13 JP1/Network Node Manager i Setup Guide (3021-3-L32(E))

JP1 Version 13 JP1/Network Node Manager i Developer's Toolkit Guide (3021-3-L33(E))

JP1 Version 13 JP1/SNMP System Observer Description, Operator's Guide and Reference (3021-3-L34(E))

In this manual, the JP1 Version 13 JP1/Network Node Manager i Setup Guide is abbreviated as the JP1/Network Node Manager i Setup Guide. JP1 Version 13 JP1/SNMP System Observer Description, Operator's Guide and Reference is abbreviated as JP1/SNMP System Observer.

C.2 Abbreviations for Microsoft product names

This manual uses the following abbreviations for Microsoft product names.

Abbreviation

Full name or meaning

Windows

Windows Server 2016

Microsoft(R) Windows Server(R) 2016 Datacenter

Microsoft(R) Windows Server(R) 2016 Standard

Windows Server 2019

Microsoft(R) Windows Server(R) 2019 Datacenter

Microsoft(R) Windows Server(R) 2019 Standard

Windows Server 2022

Microsoft(R) Windows Server(R) 2022 Datacenter

Microsoft(R) Windows Server(R) 2022 Standard

Windows Server 2025

Microsoft(R) Windows Server(R) 2025 Datacenter

Microsoft(R) Windows Server(R) 2025 Standard

C.3 Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Abbreviation

Full name or meaning

Firefox

Firefox ESR

Mozilla Firefox(R) ESR

JP1/IM

JP1/Integrated Management - Manager

Linux

Linux 7.1

Red Hat Enterprise Linux(R) Server 7 (64-bit x86_64) (version 7.1 or later)

Linux 8.1

Red Hat Enterprise Linux(R) Server 8 (64-bit x86_64) (version 8.1 or later)

Linux 9.1

Red Hat Enterprise Linux(R) Server 9 (64-bit x86_64) (version 9.1 or later)

Oracle Linux 7.1

Oracle Linux(R) Operating System 7 (version 7.1 or later)

Oracle Linux 8.1

Oracle Linux(R) Operating System 8 (version 8.1 or later)

Oracle Linux 9.1

Oracle Linux(R) Operating System 9 (version 9.1 or later)

SUSE Linux 12

SUSE Linux(R) Enterprise Server 12

NNMi

JP1/Network Node Manager i

NNMi Advanced

JP1/Network Node Manager i Advanced

SSO

JP1/SNMP System Observer

VMware

VMware(R)

C.4 Conventions: Acronyms

This manual also uses the following acronyms:

Acronym

Full name or meaning

ARP

Address Resolution Protocol

CPU

central processing unit

CSV

comma separated values

DHCP

Dynamic Host Configuration Protocol

DNS

Domain Name System

ESC

Enhanced Security Configuration

FQDN

fully qualified domain name

GIF

Graphics Interchange Format

GUI

graphical user interface

HTML

Hypertext Markup Language

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol over SSL

ICMP

Internet Control Message Protocol

IP

Internet Protocol

IPv4

Internet Protocol version 4

IPv6

Internet Protocol version 6

LAN

local area network

LLDP

Link Layer Discovery Protocol

MAC

media access control

MIB

management information base

OS

operating system

PC

personal computer

SNMP

Simple Network Management Protocol

TCP

Transmission Control Protocol

UDP

User Datagram Protocol

URL

uniform resource locator

UTF

Unicode Transformation Format

VPN

virtual private network

WWW

World Wide Web

C.5 Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,024² bytes

1 GB (gigabyte) is 1,024³ bytes.

1 TB (terabyte) is 1,024⁴ bytes.

Glossary

D

device

An IT device such as a router, switch, PC, or printer.

discovery seed

A node from which the discovery of the monitoring target nodes starts. If nodes are to be automatically discovered, the ARP cache of the discovery seed is used to discover neighboring devices. For the discovery seed, specify a router that has a lot of information about neighboring devices.

I

incident

Among various events that occur in a network, one with high importance for which information needs to be reported to the administrator. NNMi analyzes the root causes of events that occur in a network, and then reports those root causes as incidents.

instance

The source from which a resource is collected. For example, the instance of the resource CPU Utilization is the CPU utilization of each CPU.

L

Layer 2 topology

The connection relationship of a network as seen from the data link layer of the OSI Reference Model. A Layer 2 topology shows the connections between the switches and terminals in the network.

Layer 3 topology

A connection relationship of a network as seen from the network layer of the OSI Reference Model. A Layer 3 topology shows the logical configuration of the network.

lifecycle state

An attribute that is used for checking the progress of an incident. The lifecycle states are Registered, In Progress, Completed, and Closed. The state is updated according to the incident-handling status of an incident.

M

management information base (MIB)

Status information that an SNMP server product or SNMP network device releases externally.

MIB object

A unit of management information in the MIB. A MIB object consists of a hierarchical tree structure. Each level of the tree has a unique name and an identifier that indicates the unique name by using a numerical value. Note that a specific value of a MIB object is called an instance.

N

node

A device that is monitored by NNMi.

node group

A collection of discovered network devices that are grouped and organized into a hierarchy based on, for example, the IP address or device type.

node group map

A map that categorizes (such as by each business or region) and displays the network devices in each node group.

R

resource

A collection of information that SSO collects from SNMP agents. Examples of resources include CPU Utilization and Run Queue Length.

root cause analysis (RCA)

Identification of the cause of a failure by investigating and filtering the correlations among various events that occur because of a network failure, and then analyzing the failure based on the Layer 2 topology.

S

SNMP trap

Processing that reports information from an SNMP agent to the SNMP manager when a failure occurs on the SNMP agent.

T

topology map

A network configuration diagram that shows the statuses of discovered network devices and their connection relationships.

Index

A

abbreviations for products[1]

accessing NNMi[1]

accessing SSO[1]

acronyms[1]

adding information about connection from SSO to NNMi [for Linux][1]

adding information about connection from SSO to NNMi [for Windows][1]

analyzing root cause of failure[1]

analyzing root causes[1]

archiving or deleting NNMi incidents[1]

auto-discovery rules[1]

automatic action[1]

B

backing up or restoring NNMi[1]

C

checking details of incident settings[1]

checking discovered network and devices[1]

checking NNMi operating status[1]

checking number of SNMP trap incidents[1]

checking prerequisites of Monitoring Manager (for Linux)[1]

checking prerequisites of Monitoring Manager (for Windows)[1]

checking server environment[1]

configuring automatic action for incident[1]

configuring communication protocols[1]

configuring incidents[1]

configuring JP1 network management products[1]

configuring monitoring settings[1]

configuring NNMi[1]

configuring node group[1]

configuring node group map[1]

configuring node groups[1]

configuring SNMP trap incident[1]

configuring SSO[1]

conventions

abbreviations for products[1]

acronyms[1]

fonts and symbols[1]

KB, MB, GB, and TB[1]

D

deleting discovery seeds for which discovery is complete[1]

devices[1]

discovery seed[1]

disk capacity [Monitoring Manager][1]

E

enabling automatic trimming feature[1]

example of issued incident[1]

exporting or importing NNMi settings[1]

F

failure monitoring[1]

font conventions[1]

G

GB meaning[1]

general procedure for configuring JP1 network management products[1]

general procedure for setting up JP1 network management products[1]

global network management[1]

H

handling network device node that is going down[1]

Help menu[1]

how to discover explicitly specified items[1]

how to read this manual[1]

How to use Important Nodes node group[1]

I

icon[1]

incident[1], [2]

installation folder of NNMi[1]

installation folder of SSO[1]

installing NNMi (for Linux)[1]

installing NNMi (for Windows)[1]

installing SSO (for Linux)[1]

installing SSO (for Windows)[1]

instance[1]

IPv6 network management[1]

items configured in monitoring definitions[1]

J

JP1/Network Node Manager i[1]

JP1/SNMP System Observer[1]

K

KB meaning[1]

L

language settings of server[1]

Layer 2 topology[1]

Layer 3 topology[1]

lifecycle management[1]

lifecycle state[1]

link aggregation management[1]

M

Management Event incident[1]

MB meaning[1]

memory [Monitoring Manager][1]

menu[1]

MIB[1]

MIB object[1]

monitoring[1]

monitoring by using topology maps[1]

monitoring resources[1]

N

network configuration[1]

network discovery[1]

network monitoring by using JP1 network management products[1]

network monitoring types[1]

nnmbackup.ovpl[1]

nnmchangesyspw.ovpl[1]

nnmconfigimport.ovpl (for Windows)[1]

nnmconfigimport.ovpl [for Linux][1]

NNMi[1]

NNMi Advanced[1]

NNMi console[1]

nnmincidentcfg.ovpl[1]

nnmloadmib.ovpl[1]

nnmmanagementmode.ovpl[1]

nnmrestore.ovpl[1]

nnmsnmpwalk.ovpl[1]

node group[1]

node group map[1]

node groups[1]

non-SNMP devices[1]

normal operation by using JP1 network management products[1]

notifications of problems[1]

O

OS [Monitoring Manager][1]

ovstart[1]

ovstatus[1]

ovstop[1]

P

pane[1]

performing network discovery[1]

periodic maintenance of JP1 network management products[1]

periodically deleting SSO collection data[1]

polling[1]

port number of Web server[1]

preface[1]

preparation before installation[1]

R

redundant router management[1]

registering discovery seeds in batch operation[1]

registering users[1]

resource[1]

resource collection[1], [2]

resource monitoring[1]

S

setting community name [for Monitoring Manager (Linux)][1]

setting community name [for Monitoring Manager (Windows)][1]

setting language environment [for SSO][1]

setting SSO definition information for NNMi [for Linux][1]

setting SSO definition information for NNMi [for Windows][1]

setting up JP1 network management products[1]

setting up Monitoring Manager (for Linux)[1]

setting up Monitoring Manager (for Windows)[1]

setting up NNMi (for Linux)[1]

setting up NNMi (for Windows)[1]

setting up SSO (for Linux)[1]

setting up SSO (for Windows)[1]

setting up system account[1]

Setting up WebGUI of SSO [for Monitoring Manager (Linux)][1]

Setting up WebGUI of SSO [for Monitoring Manager (Windows)][1]

setup procedure explained in this manual[1]

SNMP devices[1]

SNMP Trap incident[1]

SNMP traps[1]

specifying how to perform network discovery[1]

SSO[1]

ssoapcom [for Linux][1]

ssoapcom [for Windows][1]

ssoauth [for Linux][1]

ssoauth [for Windows][1]

ssocollectd [for Linux][1]

ssocollectd [for Windows][1]

ssodbdel[1]

ssonnmsetup[1]

ssostart [for Linux][1]

ssostart [for Windows][1]

starting network monitoring[1]

starting resource collection[1]

storage location of commands[1]

subresource[1]

symbol conventions[1]

system configuration that is assumed by this manual[1]

system resource[1]

T

TB meaning[1]

topology[1]

topology maps[1]

troubleshooting by using JP1 network management products[1]

troubleshooting mechanism[1]

troubleshooting network failure[1]

U

user resource[1]

V

view[1]

viewing monitoring definitions and checking monitoring method[1]

VMware ESX server management[1]

W

Web browser[1]

webguisetup [for Linux][1]

webguisetup [for Windows][1]

what is explained in this manual[1]

what you can do with JP1 network management products[1]

workspace[1]

Publisher

Hitachi, Ltd.

6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo, 100-8280 Japan