Owner's manual

service processor
(SP) event
messages
A notification generated by the master service processors (MSPs) on the NonStop server.The
OSM Notification Director can gather SP event messages directly from the MSPs, allowing SP
event messages to be received when the NonStop operating system is not running.
service provider 1. A person trained and qualified to service field-replaceable units (FRUs) associated with a
NonStop server.
2. An organization, such as the Global Customer Support Center (GCSC), that helps you
resolve problems with your server or ServerNet cluster. OSM allows you to utilize the help
of a service provider by configuring OSM to support remote notification and remote access.
service side The side of a system enclosure that contains the CRUs. It is the side opposite the appearance
side. Cables are accessed from the service side.
single-mode
fiber-optic (SMF)
ServerNet cable
A fiber-optic cable that allows only one mode to propagate. SMF ServerNet cable has a
small-diameter core for optimized long-distance transmission.
See also multimode fiber-optic (MMF) ServerNet cable.
slot A physical labeled space or sheet-metal frame in an enclosure into which a logic board or other
system component can be installed. Slots have numbers that are unique in the enclosure.
small computer
system interface
(SCSI)
An ANSI-standard protocol used by a controller for access to a device. For example, the disk
drives in NonStop S-series servers are connected on a SCSI bus.
snapshot A record of the condition of your NonStop server, including alarms and attribute values of all
supported resources at the time the file was saved. Snapshots are created and saved manually
using the OSM Service Connection.
SNETMON Abbreviation for the ServerNet cluster monitor process. SETMON is a process pair named
$ZZSCL that manages the state of the ServerNet cluster subsystem. Each node (system) in a
ServerNet cluster must have one SNETMON process pair.
software
configuration
incident report
An incident report that notifies you of changes in the software configuration of your NonStop
server. Software configuration incident reports include the server’s software configuration file.
See also periodic incident report and problem incident report.
source One of two selection types for filtering OSM status messages. These category types are
supported:
OSM encountered an SNMP protocol error.SNMP
The OSM client or server application encountered an error while performing an OSM operation.SP Interface
The OSM operation failed due to a system error.System
The user specified an incorrect value for the requested operation. Check the specified value
and retry the operation.
User
split-star topology A network topology that uses up to two HP NonStop Cluster Switches for each external fabric.
External routing is implemented between the two starred halves of a ServerNet cluster. (A
starred half consists of up to eight nodes attached to one set of cluster switches.) The starred
segments are joined by four-lane links. The split-star topology supports up to 16 nodes.
See also star topology, tri-star topology, and layered topology.
star topology A network topology in which all nodes are connected to a central hub (HP NonStop Cluster
Switch). Each node has its own connection to the network, so a break in the connection does
not affect other nodes in the network. In a ServerNet cluster, a star topology requires one cluster
switch for each external fabric and can support up to eight nodes.
See also split-star topology, and tri-star topology, and layered topology.
status/console
message
A message that keeps the user informed about the status of the requested action.
subnetwork A physical network within an internet protocol (IP) network. Each IP network can be divided
into a number of subnetworks.Within a given network, each subnetwork is treated as a separate
293