Hitachi

JP1 Version 12 Network Management: Getting Started


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 65,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:

  1. In Communication Configuration, configure the SNMP community strings.

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

  3. 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:

  1. Select the row that you want to output.

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

  3. 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