Network, Osm event viewer – HP Integrity NonStop J-Series User Manual
Page 312

network
Two or more computer systems (nodes) connected so that they can exchange information and
share resources.
See also
ServerNet system area network (ServerNet SAN)
.
node
A uniquely identified computer system connected to one or more other computer systems in a
. For example, each server in a ServerNet cluster, an Expand network, and a FOX ring
is a node.
notification
A message that is generated by the OSM software when something occurs that might affect
resource performance and availability. The two types of notifications are OSM notifications and
service processor (SP) event messages
.
O
object
One or more of the devices, lines, processes, and files in a subsystem. In the OSM Service
Connection, an object is equivalent to a resource.
See also
.
OSM Event Viewer
A component of the OSM software that lets you set up criteria to view log files in several ways,
enabling you to rapidly assess service problems. The OSM Event Viewer is launched from within
the
and the
.
OSM Low-Level
Link
A component of the OSM software that enables you to communicate with a
when the
NonStop operating system is not running, as long as both the server and the workstation have
power. When the operating system is running, you usually communicate with the server using
the
. However, some operations on a running server require that you
use the OSM Low-Level Link. To start the operating system on a server, you use the OSM Low-Level
Link.
OSM notification
A
generated by the OSM software when something occurs that might affect the
performance of a resource managed by OSM.
OSM Notification
Director
A component of the OSM software. The OSM Notification Director receives
and
from the
, displays them, and allows you to take action or forward the
incident reports to your service provider for resolution.
OSM Service
Connection
A component of the OSM software that enables you to communicate with a NonStop server when
the NonStop operating system is running. When the operating system is not running,
communication must take place using the
.
OSMCONF
Optional OSM server configuration file, created from the OSMINI template if you want to change
any default configuration settings. In the absence of an OSMCONF file, the OSM server uses
default configuration settings, as listed in the OSMINI file. For more information, see the OSM
Configuration Guide.
P
PAL firmware
The Processor Abstraction Layer is firmware that directly handles all aborts and initialization and
platform management interrupts.
part number
A unique number assigned to a product. The part number can be used for ordering purposes.
path
The route between a processor and a subsystem. If a subsystem is configured for fault tolerance,
it has both a primary path (from the primary processor) and a backup path (from the backup
processor).
pending incident
report
An
that has never been delivered to your service provider, either because delivery
to both the primary and the backup sites was unsuccessful or because the incident report was
generated at an
.
See also
,
software configuration incident report
.
periodic incident
report
A type of
that is generated periodically to test the connection to the service provider
and report the current system configuration. The default frequency is 14 days. Periodic incident
reports include the system configuration file as an attachment.
See also
,
software configuration incident report
,
.
peripheral device
Any device used by processors to communicate with users or to acquire or store data. Peripheral
devices include terminals, workstations, printers, disk drives, and tape drives.
312
Glossary