I. Glossary
- agent
-
A program that is managed by another program in the system or a host that is managed by another host in the system. JP1/IM - EG for NNMi is installed on an agent host.
- basic attribute
-
A type of information item (attribute) of JP1 events that characterizes all JP1 events.
See JP1 event.
- cluster system
-
A system in which multiple servers are linked and operated as a single system.
The purpose of a cluster system is to improve availability by enabling application processing to be transferred to another server in the event of a failure in the executing server. Such transfer of processing is called a failover.
If a failure occurs on the server that is executing an application (primary node), the standby server (secondary node) inherits the application. This is also called a node switching system because it involves switching of the application processing from the primary node to the secondary node.
There is also a type of cluster system that is configured to distribute the workload by running multiple servers in parallel. However, in this manual, cluster system refers to the configuration that supports failover in order to prevent interruption of application processing.
- common definition information
-
A database that stores the definition parameters for the JP1 execution environment and that is managed by JP1/Base. This database is located on each server's local disk. It contains the definition parameters for the physical host and the logical host separately.
When JP1 is operated in a cluster system, the logical host definition contained in the common definition information must be the same between the servers of the primary and secondary nodes. Therefore, when setup and environment setup are performed, the parameters are set on the active server and then those settings are copied to the standby server.
- conditional statement
-
A filtering conditional statement that is used to include as conversion targets those NNMi incidents that satisfy a specified condition. The conditional statements are specified in the filter condition block in the NNMi incident forwarding filter definition file.
- Event Console window
-
A JP1/IM - View window that displays the JP1 events received by the central console arranged in the order received (by time). This is the first window displayed when you log in to JP1/IM - Central Console.
JP1/IM uses JP1 events to record the events that occur at each host and facilitates centralized management by transferring the important JP1 events to JP1/IM's manager host. By displaying these JP1 events in the Event Console window, you can monitor centrally the significant events that have occurred in the system.
- event ID
-
A JP1 event attribute that identifies the program that issued the JP1 event and that indicates the nature of the event. The event ID is a basic attribute of JP1 events and its attribute name is B.ID.
The event ID is expressed in hexadecimal, such as 7FFF8000.
Unique event IDs are assigned to each JP1-series product. For details about the JP1 events that are issued by each JP1-series product, see the appropriate documentation for each product.
Event IDs that can be used by the user are from 0 to 1FFF and from 7FFF8000 to 7FFFFFFF.
The details of JP1 events are indicated by an 8-byte numeric value that consists of the basic code (leading 4 bytes) and an extended code (trailing 4 bytes). Normally, only the 4-byte basic code is used. The extended code is set to 0 except when the user uses the API to set a code. When specification of both basic and extended codes is needed, they are connected by a colon (:), such as 7FFF8000:0.
- event server
-
A program that provides functions for managing JP1 events in JP1/Base. JP1 events can be collected and distributed while the event server is running.
- event service
-
A function for registering and managing as JP1 events the events that occur in the system.
- exclusion condition
-
A filtering conditional statement that is used to exclude as conversion targets those NNMi incidents that satisfy a specified condition. The exclusion conditions are specified in the filter condition block in the NNMi incident forwarding filter definition file.
- extended attribute
-
A type of information item (attribute) of JP1 events that is specified by the programs that issue events.
See JP1 event.
- failover
-
A function for ensuring uninterrupted processing by switching JP1 to another normal server in the event of a failure on the server where JP1 is running. Failover can also refer to switching of the servers that run JP1 by an action of a system administrator.
This is also referred to as node switching, because failover occurs from the active server to the standby server.
- incident
-
A single failure event that has an adverse effect on the quality of IT services and prevents normal system operation.
- JP1 common definition information
-
See common definition information.
- JP1 event
-
Information used in JP1 to manage events that occur in the system.
JP1 events use the following attributes to record events:
-
Basic attributes
All JP1 events have basic attributes.
For example, when attribute names are specified, B.ID (or just ID) is specified for the event ID.
-
Extended attributes
A program that issues JP1 events can specify any desired extended attributes. The extended attributes consist of the following common information and program-specific information:
• Common information (extended attribute information whose format is standardized according to the JP1 event)
• Program-specific information (information other than the common information whose format is specific to a program)
For example, when attribute names are specified, E.SEVERITY (or just SEVERITY) is specified for the severity.
The JP1 events are managed by the event service of JP1/Base. Events that occur in the system are recorded in the database as JP1 events.
-
- JP1/Base
-
The program that provides the event service. JP1/Base can be used to control the service startup sequence and to send and receive JP1 events. JP1/Base is a prerequisite program for JP1/IM - EG for NNMi.
- JP1/IM - Manager
-
A program used to achieve integrated management of systems by providing for centralized monitoring and operation of the entire system.
- JP1/IM - View
-
The program that provides the viewer function (GUI) for enabling integrated management of systems in JP1/IM.
- JP1/NNMi
-
A collective name for integrated network management programs that manage the network configuration, performance, and failures.
- JP1/Power Monitor
-
A program used to start and terminate hosts automatically. JP1/Power Monitor enables the user to start and terminate hosts on the basis of schedules, as well as to start and terminate remote hosts.
- JP1/Software Distribution
-
A collective name for systems that use a network to perform software distribution and client management in the batch mode.
- jp1hosts information
-
The hosts information that defines the correspondences between JP1-specific host names and IP addresses.
This information is used to customize JP1 communication operations in an environment that is connected to multiple networks. JP1/Base manages the jp1hosts information.
jp1hosts information does not support communication using IPv6 addresses. To use IPv6 addresses for communication, you must set jp1hosts2 information.
See jp1hosts2 information.
During JP1 communication, the jp1hosts information has precedence over other information, such as hosts. This enables JP1-specific correspondences between host names and IP addresses that differ from the settings in the OS to be used for communication.
- jp1hosts2 information
-
The hosts information that defines the correspondences between JP1-specific host names and IP addresses.
This information is used to customize JP1 communication operations in an environment that is connected to multiple networks. JP1/Base manages the jp1hosts2 information.
To use IPv6 addresses for communication, you must set jp1hosts2 information.
During JP1 communication, the jp1hosts2 information has precedence over other information, such as hosts. This enables JP1-specific correspondences between host names and IP addresses that differ from the settings in the OS to be used for communication.
Note that JP1/IM - EG for NNMi supports IPv4/IPv6 mixed environment (dual-stack environment), however, it does not support an environment with IPv6 only.
- logical host
-
A logical server that becomes the JP1 execution environment when JP1 is operating in a cluster system. This is also the unit of failover in the event of a failure.
A logical host has a logical IP address and a shared disk that are inherited during failover. It consists of applications, such as JP1 programs, that are run using the logical IP address and shared disk.
In the event of failover, the logical IP address and shared disk are transferred for continuation of JP1 execution. As a result, although the physical server running JP1 has changed, other hosts can still use the same IP address to access the server as if there had been no change in the operating host.
- manager
-
A program whose role is to manage other programs in the system, or a host whose role is to manage other hosts in the system.
The JP1 events issued by JP1/IM - EG for NNMi are managed by the JP1/IM - Manager that is installed on the manager host.
- NNMi incident
-
A single error event that is reported when something unintended occurs in a network device managed by JP1/NNMi.
- node switching system
-
See cluster system.
- physical host
-
The physical server in a cluster system (when JP1 is operating in the cluster system). In addition to the physical host, there are also logical hosts (so that a logical server can fail over without depending on the physical server).
- severity
-
One of the attributes of JP1 events that indicates the seriousness of events in the system.
Severity belongs to the common information of the extended attributes of JP1 events. Its attribute name is E.SEVERITY.
The severity levels include Emergency, Alert, Critical, Error, Warning, Notice, Information, and Debug.
- viewer
-
A program that provides appropriate GUI-based windows for achieving integrated management of JP1/IM systems. Viewer also refers to the host that runs the viewer.