HP 9000 rp7410 Service Processor (GSP or MP) - User Guide, Second Edition - Page 21

nPartition Console Access versus Direct OS Login, Network Configuration for a Service Processor

Page 21 highlights

Each nPartition console can display a variety of information about the nPartition, including: • Partition startup, shutdown, and reset output. • The system boot environment: either Boot Console Handler (BCH, on HP 9000 servers) or Extensible Firmware Interface (EFI, on HP Integrity servers). The system boot environment is available when the nPartition has not yet booted an operating system and has completed Power-On Self Tests (POST) and completed nPartition rendezvous to become active. • The HP-UX login prompt and "console shell access". CAUTION: When you use an nPartition console connection to login to an operating system running on the nPartition, logout from the operating system when you have finished using it before you enter ^B (Control-b) to disconnect from the nPartition console. If you fail to logout from the operating system console session, then any other service processor user who has permission to access the nPartition could connect to the nPartition console and use the open login session. Disconnecting from an nPartition console does not close any open operating system login sessions. nPartition Console Access versus Direct OS Login You may need to consider the following factors when deciding whether to interact with an nPartition through the service processor console interface or a direct operating system (OS) login session. • Whether you want to log your activity to the console log for the nPartition (all console activity is stored at least temporarily). • Whether the OS is installed, booted, and properly configured on the nPartition. If the OS is not installed on an nPartition, you should access the nPartition console (through the service processor) in order to install and configure the OS. You should use the network to login to the OS running on an nPartition when you do not need to use service processor features and do not want to record a log of your activity. Before an OS has booted, the service processor nPartition consoles are the primary method of interacting with an nPartition. After an nPartition has booted the OS, you should be able to connect to the nPartition by using telnet, rlogin, or ssh to remotely login to HP-UX or Linux or by using remote desktop for a remote Windows session. Network Configuration for a Service Processor This section describes how to list and configure the network settings for service processor (MP or GSP) hardware. These settings are used for connections to the service processor and are not used for HP-UX networking. Details on configuring service processor networking are given in the procedure "Configuring Service Processor Network Settings" (page 23). The service processor utility hardware on HP Superdome servers has two network connections: the customer LAN and private LAN. The service processor on other (non-Superdome) nPartition-capable servers does not have a private LAN; only a customer LAN connection is provided. Features of service processor LANs are provided in the following list. • Customer LAN for Service Processor The customer LAN is the connection for login access to the service processor menus, consoles, commands, and other features. All HP nPartition servers have a customer LAN. Network Configuration for a Service Processor 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38

Each nPartition console can display a variety of information about the nPartition, including:
Partition startup, shutdown, and reset output.
The system boot environment: either Boot Console Handler (BCH, on HP 9000 servers) or
Extensible Firmware Interface (EFI, on HP Integrity servers).
The system boot environment is available when the nPartition has not yet booted an operating
system and has completed Power-On Self Tests (POST) and completed nPartition rendezvous
to become active.
The HP-UX login prompt and “console shell access”.
CAUTION:
When you use an nPartition console connection to login to an operating system
running on the nPartition, logout from the operating system when you have finished using it
before you enter
^B
(
Control-b
) to disconnect from the nPartition console.
If you fail to logout from the operating system console session, then any other service processor
user who has permission to access the nPartition could connect to the nPartition console and use
the open login session.
Disconnecting from an nPartition console does not close any open operating system login sessions.
nPartition Console Access versus Direct OS Login
You may need to consider the following factors when deciding whether to interact with an
nPartition through the service processor console interface or a direct operating system (OS) login
session.
Whether you want to log your activity to the console log for the nPartition (all console activity
is stored at least temporarily).
Whether the OS is installed, booted, and properly configured on the nPartition.
If the OS is not installed on an nPartition, you should access the nPartition console (through
the service processor) in order to install and configure the OS.
You should use the network to login to the OS running on an nPartition when you do not need
to use service processor features and do not want to record a log of your activity.
Before an OS has booted, the service processor nPartition consoles are the primary method of
interacting with an nPartition.
After an nPartition has booted the OS, you should be able to connect to the nPartition by using
telnet
,
rlogin
, or
ssh
to remotely login to HP-UX or Linux or by using remote desktop for
a remote Windows session.
Network Configuration for a Service Processor
This section describes how to list and configure the network settings for service processor (MP
or GSP) hardware. These settings are used for connections to the service processor and are not
used for HP-UX networking.
Details on configuring service processor networking are given in the procedure
“Configuring
Service Processor Network Settings” (page 23)
.
The service processor utility hardware on HP Superdome servers has two network connections:
the customer LAN and private LAN.
The service processor on other (non-Superdome) nPartition-capable servers does not have a
private LAN; only a customer LAN connection is provided.
Features of service processor LANs are provided in the following list.
Customer LAN for Service Processor
The customer LAN is the connection for login access
to the service processor menus, consoles, commands, and other features.
All HP nPartition servers have a customer LAN.
Network Configuration for a Service Processor
21