Low-level link, Management window – HP Integrity NonStop J-Series User Manual
Page 310
logical interface
(LIF)
A process that allows an application or another process to communicate with data communications
hardware.
logical name
An
of a resource that is either assigned to the I/O process associated with the resource
during configuration using the
Subsystem Control Facility (SCF)
or that represents the type of
resource or its location.
When you are logged on to the OSM Service Connection, you can use the logical name to locate
a resource.
Examples:
•
$DATA04-P is the logical name of the disk CRU located in group 1, module 1, slot 13.
•
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.
•
Switch_Y_Guid_VOPXKH is the logical name for a NonStop Cluster Switch on the external
Y fabric of a ServerNet cluster.
See also
logical processor
The combination of equivalent processor elements in the Blade Elements that are running in the
same instruction stream in loose lock-step.
logical
synchronization
unit (LSU)
The combination of the LSU logic board and the LSU optics adapter. An LSU serves one logical
processor.
Logical Unit
Number (LUN)
A SCSI convention used to identify elements. The host sees a virtual disk as a LUN. The LUN
address a user assigns to a virtual disk for a particular host will be the LUN at which that host
will see the virtual disk.
low-level link (LLL)
A connection between the OSM client software running on a workstation and the
on the
. When the operating system is not running, communication must
take place over a
. You can also communicate with a server over a low-level link
when the operating system is running. Certain tasks can be performed only using a low-level link.
See also
.
LSU logic board
The part of the LSU that performs the synchronization functions of the LSU.
LSU optics adapter
The part of the LSU that interfaces to the ServerNet fabric.
M
maintenance entity
A processing entity in a single HP NonStop™ system that collects state information, environmental
information, and failure data about the system resource or resources for which the maintenance
entity is responsible. A maintenance entity can include both physical and software components,
and a system can contain multiple maintenance entities. For example, each I/O adapter module
(IOAM) and processor switch has its own maintenance entity.
maintenance PIC
A ServerNet PIC that connects the X-fabric and Y-fabric processor switches.
maintenance
switch
The Ethernet switch that links the maintenance entities in various modular components to the OSM
interface.
Management
window
The Management window provides an easy way to browse through a complex system installation.
It contains four panes.
The left pane is the tree pane. It displays a hierarchical tree structure containing server or cluster
resources that you can select.
The lower-right pane is the overview pane. It displays only the high-level system objects (such as
internal fabrics and groups). When you click the Cluster tab, the overview pane displays only
the high-level cluster objects (external fabrics, local node, and remote nodes).
The top pane is the view pane. It might contain a
or an
. You can
select the type of view from the View drop-menu on the toolbar above the view pane.
The lower pane is the details pane. It displays the specific information about the selected resource.
Click a tab to select the type of information to display in the details pane.
master service
processor (MSP)
A type of service processor (SP) pair that provides the basic service processor functions as well
as centralized system functions such as a console port, a modem port for remote support functions,
310
Glossary