Preface
This manual describes the settings needed to deploy Job Management Partner 1/Consolidated Management 2/Network Node Manager i and Job Management Partner 1/Consolidated Management 2/Network Node Manager i Advanced (referred to hereafter as NNMi if there is no difference in the products). It also describes the settings needed to upgrade from version 8 and earlier versions of JP1/Cm2/Network Node Manager (abbreviated as NNM). JP1/Cm2/Network Node Manager is a product name in Japan. Note also that this manual is intended for all supported operating systems. When there are differences between the NNMi editions on different operating systems, this manual provides separate descriptions for the relevant operating systems.
In this manual, Job Management Partner 1 is abbreviated as JP1, and Consolidated Management 2 is abbreviated as Cm2.
- Organization of this preface
■ Intended readers
This manual is intended for experienced system administrators, network engineers, and others who are familiar with deploying and managing networks for large-scale systems.
This manual assumes you have already installed NNMi and that you are familiar with the initial configuration tasks, such as configuring community strings, setting up discovery for a limited range of network nodes, and creating an initial administrator account. For details about these tasks, see the Job Management Partner 1/Consolidated Management 2/Network Node Manager i Installation Guide.
■ Organization of this manual
This manual is organized into the following parts:
- PART 1: Preparation
-
Part 1 explains what you need to check before you use NNMi.
- PART 2: Configuration
-
Part 2 explains the settings needed for managing a network.
- PART 3: Advanced Configuration
-
Part 3 explains the settings needed to use NNMi functions, such as certification, integration of directory services through NNMi and LDAP, and so on.
- PART 4: High Availability Environment Configuration
-
Part 4 describes support for high availability (HA) clusters and application failover.
- PART 5: NNMi Maintenance
-
Part 5 explains how to back up, restore, and maintain NNMi.
- PART 6: Migration
-
Part 6 explains the operations needed to upgrade NNMi to version 10.
- PART 7: Integration with NNMi
-
Part 7 explains integration of related products with NNMi.
■ 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:
|
Italic |
Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:
Italic characters are also used for emphasis. For example:
|
Monospace |
Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:
|
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. |
■ Conventions: Version numbers
The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:
-
Version 1.00 (or 1.0) is written as 01-00.
-
Version 2.05 is written as 02-05.
-
Version 2.50 (or 2.5) is written as 02-50.
-
Version 12.25 is written as 12-25.
The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.