Locating and Troubleshooting DHCP, TFTP, and DNS Services on the NonStop Dedicated Service LAN HP Part Number: 632166-002 Published: August 2011 Edition: J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs.
Copyright 2011 Hewlett-Packard Development Company, L.P. Legal Notice See Appendix : Legal Notice (page 13) for legal notices.
About This Document This document describes how to locate and troubleshoot DHCP, TFTP, and DNS services on a dedicated service LAN for NonStop systems. Supported Release Version Updates (RVUs) This topic supports J06.03 and all subsequent J-series RVUs and H06.03 and subsequent H-series RVUs until otherwise indicated in a replacement publication. Intended Audience While initial configuration of DHCP, TFTP, and DNS services on a dedicated service LAN for NonStop systems should be done only by HP authorized service providers, this document is intended for anyone who needs to understand the important role these services provide particularly for HP Integrity NonStop BladeSystems and NonStop NS2200 series systems and how to locate, check the status of, or troubleshoot these services on the dedicated service LAN. New and Changed Information in This Edition Version 632166-002 632166-001 Date August 2011 August 2010 Changes Added information for HP Integrity NonStop NS2200 series systems. None. New document. Related Information For more information on the role of DHCP, TFTP, and DNS services on your dedicated service LAN, see the planning guide for your NonStop system type. For service providers responsible for setting up and configuring the dedicated service LAN, see the hardware installation manual for the appropriate NonStop system type and the NonStop Dedicated Service LAN Installation and Configuration Guide. For Important Safety Information, Safety and Compliance, and Waste Electrical and Electronic Equipment (WEEE) information, see the HP Integrity NonStop Server Safety and Compliance collection in SAW at http://www.hp.com/go/nonstop-support-docs. NOTE: NTL has moved to http://www.hp.com/go/nonstop-docs (external view) and http:// www.hp.com/go/nonstop-support-docs (internal view.) To get an alphabetical list of manuals in SAW, click the icon next to the desired documentation collection, click Technical Manuals in the menu on the left, then click Title to sort a table of manuals by title. HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document. Supported Release Version Updates (RVUs) 3
About DHCP, TFTP, and DNS Services for NonStop Systems The purpose of this document is to help you understand: The importance of DHCP, TFTP, and DNS services for HP Integrity NonStop BladeSystems, NonStop NS2200 series systems, and any HP Integrity NonStop NS-series systems with CLuster I/O Modules (CLIMs) attached. The Rules for DHCP, TFTP, and DNS Services (page 4) on a dedicated service LAN (also called a maintenance LAN). How to Migrate DHCP, TFTP, and DNS Services (page 5) between NonStop system consoles and CLIMs. How to locate, check the status of, or troubleshoot the DHCP, TFTP, and DNS services for a dedicated service LAN On a NonStop System Console (page 6) or On CLIMs (page 10). NonStop systems require Internet protocol (IP) addresses for the components that are connected to the dedicated service LAN. Each component must have a unique IP address that does not conflict with the IP addresses of other components on the LAN. The dedicated service LAN is set up and configured by your service provider during system installation, as described in the hardware installation manual for your NonStop system type and in the NonStop Dedicated Service LAN Installation and Configuration Guide. It is important to understand the purpose of DHCP, TFTP, and DNS services on the dedicated service LAN, why they are especially crucial for NonStop BladeSystems and NonStop NS2200 series systems, and the Rules for DHCP, TFTP, and DNS Services (page 4). The purpose of DHCP, TFTP, and DNS services on the LAN include: DHCP provides the dynamic IP addresses to DHCP-enabled devices in the dedicated service LAN, such as onboard administrators (OAs) and CLIM Integrated Lights Out (ilo) services. TFTP is used by DHCP to download the Halted State Services (HSS) files to the blade server processors in NonStop BladeSystems and NonStop NS2200 series systems. DNS services are required for addressing a number of devices on the dedicated service LAN that acquire their IP addresses dynamically from DHCP. DNS provides the service to assign a name to the dynamically assigned IP addresses for these devices and provides the service that allows other entities on the network to resolve device names to their assigned IP address. Rules for DHCP, TFTP, and DNS Services Because of the critical nature of these services to NonStop BladeSystems and NonStop NS2200 series systems they must have access to the services in order to start the processors the following rules apply for all LANs containing either of those systems; they are strongly recommended but, except where noted, are not required for all other NonStop NS-series systems. Also, the same rules (or recommendations) apply whether a NonStop system is configured on a dedicated service LAN of its own or is connected to a service LAN servicing up to eight NonStop systems. Two NonStop system consoles, a primary and a backup, to manage the dedicated service LAN. Two and only two sources DHCP, TFTP, and DNS services on the dedicated service LAN. They may be located on either the NonStop system consoles or on two CLuster I/O Modules (CLIMs) attached to a system connected to the LAN. All other sources of these services on the LAN should be disabled. Note: while having a second source of these services is recommended rather than required for NonStop NS-series systems, having no more than two is a requirement for NonStop NS-series systems, in order to avoid duplicate/conflicting IP addresses. For NonStop BladeSystems and NonStop NS2200 series systems, the same two consoles or CLIMs also provide the Halted State Services (HSS) file required to start the processors. It is important to keep those file versions consistent in both places. The NonStop System Console Installer Guide describes how to download the latest version from the NonStop System Console 4 About DHCP, TFTP, and DNS Services for NonStop Systems
DVD; the OSM Low-Level Link is used to update the files used for each NonStop BladeSystem and NonStop NS2200 series system, whether those files are stored on the system consoles or CLIMs. How to Migrate DHCP, TFTP, and DNS Services By default, HP ships AC-powered systems with DHCP, TFTP, and DNS services installed and enabled on a NonStop system consoles. For DC-powered systems, these services are installed and enabled on CLIMs. You can move these services from NonStop system consoles to two designated CLIMs, or from CLIMs to consoles, using the OSM CLIM Boot Service Configuration Wizard. Use the procedure appropriate for your migration scenario (located in the Service Procedures section of NTL). For details, see: Changing the DHCP, DNS, or BOOTP Server from System Consoles to CLIMs Changing the DHCP, DNS, or BOOTP Server from CLIMs to System Consoles NOTE: To enable the DHCP, TFTP, and DNS services on a system console on which those services were not previously configured, you need to ensure that specific ports are open on the console. For more information, see the NonStop System Console Installer Guide. How to Migrate DHCP, TFTP, and DNS Services 5
How To Locate and Troubleshoot DHCP, TFTP, and DNS Services To ensure that your dedicated service LAN is in compliance with the Rules for DHCP, TFTP, and DNS Services (page 4), this chapter describes how to locate, check the status of, and disable (if necessary), those services: On a NonStop System Console (page 6) On CLIMs (page 10) NOTE: If you know the current location, the two system consoles or two CLIMs on which these services are located and wish to migrate or change that configuration, use the OSM CLIM Boot Service Configuration Wizard (see How to Migrate DHCP, TFTP, and DNS Services (page 5)); the wizard not only enables those services on the target devices, but also disables those services on the devices you are migrating from and copies the HSS files required for NonStop BladeSystems and NonStop NS2200 series systems. The procedures that follow are useful when you do not know the location of the services or want to ensure that you do not have more than two sources of those services on your dedicated service LAN. On a NonStop System Console This section describes how to locate, check the status, and disable (if necessary) the DHCP, TFTP, and DNS services installed on NonStop system consoles. The procedures in this section apply to NonStop system consoles running Windows 2003 Server, which is required for all consoles supporting NonStop BladeSystems, NonStop NS2200 series systems, or any NonStop NS-series systems with CLIMs attached. Checking DHCP Status on a NonStop System Console (page 6) Checking DNS Status on a NonStop System Console (page 8) Checking TFTP Status on a NonStop System Console (page 9) CAUTION: There should only be two NonStop system consoles connected to the dedicated service LAN; additional consoles can cause conflicting IP addresses and, for NonStop BladeSystems and NonStop NS2200 series systems, can make it difficult to manage the Halted State Services (HSS) files needed to boot the processors blades in those systems. However, removing an existing console from the LAN can also lead to boot problems, if that console happens to be the only location of the HSS file for a particular NonStop BladeSystem or NonStop NS2200 series system. Removing or replacing a NonStop system console should only be done by an authorized service provider. Checking DHCP Status on a NonStop System Console There are two ways to determine the location of active DHCP services on a dedicated service LAN: You can check the status of DHCP services on each individual system console, as described in this section. You can issue a command on any CLIM on the LAN to show where DHCP services are configured on the LAN regardless of whether on CLIMs or system consoles as described in Checking DHCP Status on a CLIM (page 10) To determine if DHCP service is installed and enabled on a system console running Windows 2003: 6 How To Locate and Troubleshoot DHCP, TFTP, and DNS Services
1. From the Start menu, select Manage Your Server. 2. From the Manage Your Server window, click Manage this DHCP server. 3. In the left pane of the DHCP window, click on the name of the console. The right pane displays the status. A value of **Active** indicates that the DHCP service is running on the console. If the DHCP service is not configured or running, the corresponding sections will not be shown. NOTE: This method only shows the status of DHCP services on that one system console. To determine if DHCP services are running elsewhere on the LAN, see Checking DHCP Status on a CLIM (page 10). At least for NonStop BladeSystems and NonStop NS2200 series systems, there should be two sources of DHCP services on the LAN, each configured by your service provider to avoid overlapping IP address ranges. To view the DHCP lease list, from the same DHCP window accessed in the previous step: 1. In the left pane of the DHCP window, select name of the console and expand its icon to show the subfolders. 2. Select and expand the Scope folder and click on Address Leases. 3. The right pane displays the Address Leases list. On a NonStop System Console 7
Changing the DHCP configuration for your LAN, provided you only have two DHCP servers on the LAN and you know where they are located, should be done through the OSM CLIM Boot Service Configuration Wizard (see How to Migrate DHCP, TFTP, and DNS Services (page 5)). As part of the migration, the wizard automatically disables the DHCP service on the devices you are migrating from. However, if you need to disable the DHCP service on a system console because it is already running on two other sources (consoles or CLIMs): 1. From the Start menu, select Administrative Tools > Services. 2. Select DHCP Server, then right-click and select Stop. 3. Right-click again on the DHCP Server entry, select Properties, and change the Start value from Automatic to Manual. Checking DNS Status on a NonStop System Console To determine if DNS service is installed and enabled on a console running Windows 2003: 1. From the Start menu, select Manage Your Server. 2. From the Manage Your Server window, click Manage this DNS server. 3. In the left pane of the dnsmgmt window, select and expand the name of the console and click on Forward Lookup Zones. If the DHCP service is running on this system console, then the 8 How To Locate and Troubleshoot DHCP, TFTP, and DNS Services
DNS Server should also show a Status of Running in the right pane. If the DNS server is not configured or running, the corresponding sections will not be shown. This is handled automatically when using the OSM CLIM Boot Service Configuration Wizard to migrate services, but if you need to disable the DNS service on a system console because it is already running on two other sources (consoles or CLIMs): 1. From the Start menu, select Administrative Tools > Services. 2. Select DNS Server, then right-click and select Stop. 3. Right-click again on the DNS Server entry, select Properties, and change the Start value from Automatic to Manual. Checking TFTP Status on a NonStop System Console To determine if TFTP service is installed and enabled on a console running Windows 2003: 1. From the Start menu, select Administrative Tools > Services. 2. Select Trivial FTP Daemon. If the DHCP service is running on this system console, then the Trivial FTP Daemon (TFTP service) should also show a Status of Running in the right pane. The TFTP service is used in conjunction with the DHCP and must be configured and running on the same devices (consoles or CLIMs) as the DHCP service. The TFTP service provides the HSS file required for NonStop BladeSystems and NonStop NS2200 series systems to boot. This is handled automatically when using the OSM CLIM Boot Service Configuration Wizard to migrate services, but if you need to disable the TFTP service on a system console because it is already running on two other sources (consoles or CLIMs): On a NonStop System Console 9
On CLIMs 1. From the Windows Start menu, select Administrative Tools > Services. 2. Select Trivial FTP Daemon, then right-click and select Stop. 3. Right-click again on the Trivial FTP Daemon entry, select Properties, and change the Start value from Automatic to Manual. This section describes how to locate, check the status, and disable (if necessary) the DHCP, TFTP, and DNS services installed on CLuster I/O Modules (CLIMs). These services should never be running on both NonStop system consoles and CLIMs on the same dedicated service LAN; for more information, see Rules for DHCP, TFTP, and DNS Services (page 4). NOTE: To alter the DHCP, DNS, and TFTP configuration for your LAN, you should use the OSM CLIM Boot Service Configuration Wizard whenever possible (see How to Migrate DHCP, TFTP, and DNS Services (page 5)). However, if you are not sure where all sources of those services are on your LAN, there are TACL commands for: Checking DHCP Status on a CLIM (page 10) Checking DNS Status on a CLIM (page 11) Checking TFTP Status on a CLIM (page 12) Checking DHCP Status on a CLIM Unlike On a NonStop System Console (page 6), you can issue a command on one CLIM on the LAN that will show where DHCP services are configured on the LAN regardless of whether on CLIMs or system consoles. However, the discover command (described below) should be run multiple times 5 is recommended and on different CLIMs, if possible, to confirm that there are not more than two sources of DHCP services on the LAN. Some DHCP servers do not respond to the DHCP request when another server has already responded to the request. The TACL command to discover where DHCP services are located on a LAN is: climcmd clim-name climdnsconfig server -discover The -discover option lists all DHCP servers (although the command should be repeated, as suggested above, to ensure that you locate all DHCP servers) on the LAN. To check the status of the DHCP service on a particular CLIM, issue the following TACL command from any CLIM on the LAN on which DHCP/DNS services are running: climcmd clim-name climdhcpmgr status This command also shows the lease range for the server and the IP address of the corresponding DNS servers. 10 How To Locate and Troubleshoot DHCP, TFTP, and DNS Services
If DHCP/DNS services are running on CLIMs, use the following command from any CLIM on which those services are running to shows the lease list: climcmd clim-name climdnsconfig server -list If you need to disable the DHCP service on an individual CLIM and cannot use the OSM CLIM Boot Service Configuration Wizard because there are more than two sources of this service on the LAN, use the following TACL command on that CLIM: climcmd clim-name climdhcpmgr stop Checking DNS Status on a CLIM DNS services should be located on the same CLIMs on which DHCP services are running (see Checking DHCP Status on a CLIM (page 10)). To check the status of the DNS service on an individual CLIM, use the following TACL command from any CLIM on which DHCP/DNS services are running: climcmd clim-name climdnsconfig server -status The Service field indicates whether the CLIM is the Master or Slave. The IP address of the peer CLIM (Master/Slave) is also displayed. The Status must show Running. To stop the DNS service on an individual CLIM (if you cannot use the OSM CLIM Boot Service Configuration Wizard), can be done through the following TACL command on that CLIM: climcmd clim-name climdnsconfig server --stop --force On CLIMs 11
Checking TFTP Status on a CLIM TFTP services are located on the same CLIMs on which DHCP services are configured. To check the status of the TFTP service on an individual CLIM, use the following TACL command from any CLIM on which those services are running: climcmd clim-name ps -A ~ grep tftp in.tftpd indicates that the TFTP service is configured and running on the CLIM. The TFTP service is stopped when the DHCP server is disabled (as described under Checking DHCP Status on a CLIM (page 10)). Remove HSS files from a CLIM When using the OSM CLIM Boot Service Configuration Wizard to migrate DHCP, TFTP, and DNS services between NonStop system consoles and CLIMs, the wizard also copies over the HSS files required for NonStop BladeSystems and NonStop NS2200 series systems (see How to Migrate DHCP, TFTP, and DNS Services (page 5)). When properly migrated through the wizard, the OSM Low-Level Link is able to determine whether your LAN is configured to provide DHCP, TFTP, and the HSS boot files required for NonStop BladeSystems and NonStop NS2200 series systems on primary and backup NonStop system consoles or on a pair of designated CLIMs. Accordingly, the Low-Level Link knows where to update the HSS files when it is used to perform an Update HSS action. If you want to remove HSS files from a CLIM no longer being used for that purpose, use the following command on that CLIM: climcmd clim-name rm /opt/hp/images/hss-filename 12 How To Locate and Troubleshoot DHCP, TFTP, and DNS Services
Legal Notice Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor s standard commercial license. Warranty The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. Acknowledgements Microsoft, Windows, Windows NT, Windows XP, and Windows Vista are U.S. registered trademarks of Microsoft Corporation. Intel and Intel Itanium are trademarks of Intel Corporation in the U.S. and other countries. Java is a US trademark of Sun Microsystems, Inc.. Motif, OSF/1, UNIX, X/Open, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries. OSF, OSF/1, OSF/Motif, Motif, and Open Software Foundation are trademarks of the Open Software Foundation in the U.S. and other countries. 1990, 1991, 1992, 1993 Open Software Foundation, Inc. The OSF documentation and the OSF software to which it relates are derived in part from materials supplied by the following: 1987, 1988, 1989 Carnegie-Mellon University. 1989, 1990, 1991 Digital Equipment Corporation. 1985, 1988, 1989, 1990 Encore Computer Corporation. 1988 Free Software Foundation, Inc. 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. 1988, 1989 Massachusetts Institute of Technology. 1988, 1989, 1990 Mentat Inc. 1988 Microsoft Corporation. 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. 1990, 1991 Siemens Nixdorf Informations systeme AG. 1986, 1989, 1996, 1997 Sun Microsystems, Inc. 1989, 1990, 1991 Transarc Corporation. OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material. Legal Notice 13