HP NonStop G-Series - Manual (Page 288)

N
name For the OSM software, the name attribute is determined by the connection type. When you use
the service connection, the
logical name is used. When you use the low-level link, the service
processor (SP) logical name is used.
Examples of logical names:
•
$DATA04-P is the logical name of the disk CRU located in group 1, module 1, slot 13.
•
IOMF2.SCSI-3.GRP-1.MOD-1.SLOT-50 is the logical name of the third SCSI bus on the
IOMF2 CRU located in group 1, module 1, slot 50.
Examples of service processor (SP) logical names:
•
SCSICRU.GRP-1.MOD-1.SLOT-3 is the SP logical name of the disk CRU located in group
1, module 1, slot 3.
•
PMF.SCSI-3.GRP-1.MOD-1.SLOT-50 is the SP logical name of the third SCSI bus on the
PMF CRU located in group 1, module 1, slot 50.
neighbor check A check performed between processor switch and the millicode before enabling the ServerNet
connection.
network Two or more computer systems (nodes) connected so that they can exchange information and
share resources.
See also local area network (LAN) , ServerNet system area network (ServerNet SAN) , and wide
area network (WAN) .
node A uniquely identified computer system connected to one or more other computer systems in a
network . 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 resource .
OSM notification A notification generated by the OSM software when something occurs that might affect the
performance of a resource managed by OSM.
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
OSM Low-Level Link and the OSM Service Connection .
OSM Low-Level
Link A component of the OSM software that enables you to communicate with a server 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
OSM Service Connection . 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
Director A component of the OSM software. The OSM Notification Director receives notifications and
incident reports from the server , 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
OSM Low-Level Link .
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
288 Glossary