Changing the DHCP, DNS, or BOOTP Server from System Consoles to CLIMs

Changing the DHCP, DNS, or BOOTP Server from System
Consoles to CLIMs
Overview
NOTE: How you configure DHCP, DNS, and BOOTP services applies to all NonStop systems
configured on the same maintenance LAN (dedicated service LAN). You can configure your
environment to have DHCP/DNS/BOOTP server functionality on either two (primary and backup)
system consoles or two designated CLIMs.
Moving DHCP/DNS/BOOTP server functionality for NonStop systems from system consoles to
CLIMs includes:
1. Making sure the system consoles meet all Minimum Requirements to perform the process.
2. Preparing to Migrate BOOTP to CLIMs.
3. Disabling DHCP, DNS, and BOOTP on NonStop System Consoles.
4. Enabling DHCP, DNS, and BOOTP on CLIMs.
5. Verifying DHCP.
CAUTION: DHCP/DNS/BOOTP server functionality should be configured on two (primary and
backup) system consoles or two designated CLIMs for fault-tolerance, but should exist on no more
than two per maintenance LAN (dedicated service LAN).
Minimum Requirements
To move the BOOTP, DHCP and DNS server functionality for NonStop systems from system consoles
to CLIMs, those system consoles must be running Windows 2003 or later authorized for NonStop
System Consoles and have these minimum product versions installed:
• NonStop Maintenance LAN DHCP DNS Configuration Wizard (part of OSM Console Tools,
T0634 G06 ABB or later)
• OSM Low-Level Link, T0633 G07 ABN or later
• PuTTY (part of Console CLIM Utilities, T0697 H01 AAA or later)
These products are all available on NonStop System Console (NSC) Installer DVD,
S7X-SWV2/HNSC-SWV2, Update 17 or later. Updates to Halted State Services (HSS) firmware
for NonStop systems (T8004) are also downloaded from the NSC Installer DVD, as needed.
Preparing to Migrate BOOTP to CLIMs
This section applies only to NonStop systems running J-series software (except NonStop NS2000
series systems). These steps will ensure that you have the appropriate HSS firmware file configured
for each of those systems on the shared maintenance LAN (dedicated service LAN).
From the primary system console (since that’s the one from which the NonStop Maintenance LAN
DHCP DNS Configuration Wizard must be run):
1. Check the HSS version currently running on the processor blades in each system. Use the
Update HSS or Copy HSS Files actions in the OSM Low-Level Link to compare the HSS version
on all processors in the system against each other and also against versions available on the
console. These actions are launched from the Tools menu or, before system discovery, from
the toolbar:
6 Changing the DHCP, DNS, or BOOTP Server from System Consoles to CLIMs