Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
Introduction
This section describes the environment that must be in place in order for server blades in HP
Integrity NonStop BladeSystems to be successfully reset, powered on, or power cycled. It includes
pointers to proactive steps you or your service provider can take to help ensure trouble-free
system startup. The “Troubleshooting Tips” (page 7) section that follows provides tips to help
you quickly recover in the event of system or server blade startup problems.
In order to be reset or started, the server blades in NonStop BladeSystems require access to DHCP
and TFTP services and a customized Halted State Services (HSS) firmware file, all of which must
be located on either the primary and backup NonStop system consoles or on two designated
CLuster I/O Modules (CLIMs) located on the dedicated service LAN.
DHCP, DNS, and TFTP Services
DHCP, DNS, and TFTP services are configured on the dedicated service LAN by your service
provider during system installation. Whether you have one or multiple NonStop BladeSystems
connected to the LAN, there should always be two, and no more two, sources of these services
on the LAN. You can migrate these services from the NonStop system consoles to CLIMs (and
vice versa) using the OSM CLIM Boot Service Configuration Wizard. Because they are vital for
powering on NonStop BladeSystems, it is important to know where these services are located
on your LAN. If you don't know where they are located, unsure of their status, or need to disable
additional sources of these services, see Locating and Troubleshooting DHCP, TFTP, and DNS
Services on the NonStop Dedicated Service LAN in the NonStop Technical Library.
Halted State Services (HSS) Firmware
While DHCP and TFTP services are provided on a per LAN basis for all systems connected to
the dedicated service LAN, each NonStop BladeSystem requires that a customized HSS firmware
file be present at the same location providing those DHCP and TFTP services, as TFTP is used
by DHCP to download the HSS file to the server blades in the NonStop BladeSystems when
powering on.
The customized HSS files are located:
•
When stored on NonStop system consoles: C:\Images\NBsystem_serial_number.efi.
•
When stored on CLIMs: /opt/hp/Images/NBsystem_serial_number.efi.
Updates to HSS firmware are delivered on the NonStop System Console DVD and downloaded
to the system consoles as described in the NonStop System Console Installer Guide. After
downloading a newer HSS version from the DVD, you are directed to use the OSM Low-Level
Link to update the customized files used by each individual NonStop BladeSystem. OSM
automatically detects whether Bootp services (a term that refers to DHCP and TFTP services as
well as HSS files) are configured on NonStop system consoles or on designated CLIMs. Because
of the importance of keeping HSS file versions consistent in both configured locations, OSM
prompts you for Peer NSC credentials -- or when CLIMs are used, OSM pre-populates the Host
Name fields with their IP addresses and prompts you for their credentials -- so the updated
firmware file will be copied to both configured locations.
To update the HSS firmware currently running on your NonStop BladeSystem, OSM provides
one action that will reset all the server blades and another action if you are only updating one
server blade and do not want to reset all server blades. For more information see the OSM
Low-Level Link online help.
Configuring NonStop BladeSystems to Avoid Startup Problems
Because server blades in NonStop BladeSystems cannot power on without access to services and
files located on either system consoles or CLIMs, there can be a problem when the server blades
DHCP, DNS, and TFTP Services
5
...Other models in this manual:
Desktops - HP Integrity NonStop Troubleshooting Tips (253.78 kb)