HP Rx2620-2 - Integrity - 0 MB RAM User manual

HP Integrity Servers with Microsoft®
Windows Server™ 2003 and Windows
Server™ 2008
Kernel Debugging Guide
HP Part Number: 5992-4491
Published: September 2008

Legal Notices
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.
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.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries.
Java is a US trademark of Sun Microsystems, Inc.
UNIX is a registered trademark of The Open Group.

Table of Contents
About This Document.........................................................................................................7
Intended Audience.................................................................................................................................7
New and Changed Information in This Edition.....................................................................................7
Document Organization.........................................................................................................................7
Typographic Conventions......................................................................................................................7
Related Information................................................................................................................................8
Publishing History..................................................................................................................................8
HP Encourages Your Comments............................................................................................................8
1 Debugging the kernel locally........................................................................................9
Overview.................................................................................................................................................9
Setting up the host machine..................................................................................................................10
Install Debugging Tools for Windows.............................................................................................10
Building a converter for your cable......................................................................................................11
Build a 5x2-to-DB9M converter (rx1620).........................................................................................11
Build a RJ45-to-DB9F converter (rx5670, rx7620, rx8620, and Superdome/sx1000)........................12
Setting up and connecting to the target machine.................................................................................13
Change the boot configuration (applies to all servers)...................................................................14
Windows Server 2003 Systems Only ⇒ Option 1: Using Bootcfg (recommended)...................14
Windows Server 2003 Systems Only ⇒ Option 2: Using Nvrboot............................................17
Windows Server 2008 Systems Only ⇒ Using BCDEdit...........................................................18
BL860c and BL870c servers..............................................................................................................19
rx1620 server....................................................................................................................................19
rx2600 and rx2620 servers................................................................................................................20
rx2660 servers..................................................................................................................................20
rx3600 and rx6600 servers................................................................................................................21
rx4640 server....................................................................................................................................21
rx5670 server....................................................................................................................................22
rx7620, rx8620, and Superdome/sx1000 servers..............................................................................23
Locate the debug port................................................................................................................23
Option 1: Identifying the core cell using an EFI command (recommended).......................23
Option 2: Identifying the core cell using an nPartition command.......................................24
Copy the KD utility to the EFI system partition (applies to rx7620 and rx8620 servers
only)............................................................................................................................................24
Enable the debugging port (applies to rx7620 and rx8620 servers only)...................................24
Connect to the debug port..........................................................................................................25
2 Debugging the kernel remotely..................................................................................27
Overview...............................................................................................................................................27
Setting up the host machine..................................................................................................................27
Install Debugging Tools for Windows.............................................................................................28
Setting up and connecting to the target machine.................................................................................29
Change the boot configuration........................................................................................................29
Windows Server 2003 Systems Only ⇒ Option 1: Using Bootcfg (recommended)...................29
Windows Server 2003 Systems Only ⇒ Option 2: Using Nvrboot............................................32
Windows Server 2008 Systems Only ⇒ Using BCDEdit...........................................................33
Enable IPMI LAN access and the debugging option......................................................................34
Connect with the target machine and initiate debugging...............................................................34
Table of Contents 3

3 Debugging HP Virtual Machines guests....................................................................35
HPVM Windows guest debug process.................................................................................................35
4 Table of Contents

List of Figures
1-1 rx1620 debug port (male pins on system board)...........................................................................12
1-2 Required plug ends and internal wiring.......................................................................................12
1-3 BL860c/BL870c debugging port.....................................................................................................19
1-4 rx1620 debugging port..................................................................................................................20
1-5 rx2600 and rx2620 debugging port................................................................................................20
1-6 rx2660 debugging port..................................................................................................................21
1-7 rx3600 and rx6600 debugging port................................................................................................21
1-8 rx4640 debugging port..................................................................................................................22
1-9 Location of three jumpers on rx4640 motherboard.......................................................................22
1-10 rx5670 debugging port..................................................................................................................23
1-11 Debugging port on the rx8620.......................................................................................................25
1-12 Debugging port on Superdome/sx1000.........................................................................................26
5

List of Tables
1-1 Kernel debugging setup options.....................................................................................................9
1-2 DB9 male pin-out to 5x2 female....................................................................................................12
1-3 Computer pin-outs or HP Integrity rx5670 servers.......................................................................13
1-4 Computer pin-outs for HP Integrity rx7620 and rx8620 servers...................................................13
1-5 Computer pin-outs for HP Integrity Superdome/sx1000 servers.................................................13
6 List of Tables

About This Document
This document describes the process for debugging the operating system kernel on HP Integrity
servers running Microsoft® Windows® Server 2003 and Windows® Server 2008.
The document printing date and part number indicate the document’s current edition. The
printing date changes when a new edition is printed. Minor changes may be made at reprint
without changing the printing date. The document part number changes when extensive changes
are made.
Document updates may be issued between editions to correct errors or document product changes.
To ensure that you receive the updated or new editions, you should subscribe to the appropriate
product support service. See your HP sales representative for details.
The latest version of this document can be found online at http://docs.hp.com.
Intended Audience
This document is intended for system administrators and HP support personnel responsible for
installing, configuring, and managing HP Integrity servers. This document is not a tutorial.
New and Changed Information in This Edition
This document includes the following changes since its last release:
• changed the BCDEdit command option order
• added debug port photo and description for rx2660 servers
• added prefatory sections at beginning of document, per HP standards
Document Organization
This document is organized as follows:
Describes how to debug the OS kernel locally. In a local debugging environment,
you are physically located near the server you want to debug. You use a host
machine, typically a laptop, that has the Windows debugging software installed
on it. You connect the host machine to the server with a cable and begin the
debugging process.
“Debugging the kernel locally”
(page 9)
Describes how to debug the OS kernel remotely. In a remote debugging
environment, you are not physically located near the server you want to debug.
You use a host machine, typically a laptop, that has the Windows debugging
software installed on it. You connect the host machine to the server across a LAN
and begin the debugging process.
“Debugging the kernel remotely”
(page 27)
Describes how to debug the virtual machine guests.“Debugging HP Virtual
Machines guests” (page 35)
Typographic Conventions
This document uses the following typographical conventions:
WARNING A warning calls attention to important information that if not understood
or followed will result in personal injury or nonrecoverable system
problems.
CAUTION A caution calls attention to important information that if not understood
or followed will result in data loss, data corruption, or damage to
hardware or software.
IMPORTANT This alert provides essential information to explain a concept or to
complete a task
Intended Audience 7

NOTE A note contains additional information to emphasize or supplement
important points of the main text.
KeyCap The name of a keyboard key or graphical interface item (such as buttons,
tabs, and menu items). Note that Return and Enter both refer to the
same key.
Computer output Text displayed by the computer.
User input Commands and other text that you type.
Command A command name or qualified command phrase.
Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you must hold
down the key labeled Ctrl while you press another key or mouse button.
Related Information
You can find more information about HP Integrity servers, server management, and software
in the following locations:
• For an overview of the HP Integrity server family:
http://hp.com/go/integrity
• For other documents supporting Windows Server 2003 and Windows Server 2008 on HP
Integrity Servers:
http://docs.hp.com/en/hw.html#Windows%2064-bit%20on%20HP%20Integrity%20Servers
• For technical support resources (drivers, patches, upgrades, migration issues, to sign up for
alerts, and so on):
http://h20000.www2.hp.com/bizsupport/TechSupport/
Product.jsp?prodTypeId=15351&prodCatId=321933
Publishing History
The publishing history below identifies the edition dates of this manual. Updates are made to
this publication on an unscheduled, as needed, basis. The updates will consist of a complete
replacement manual and pertinent online or CD documentation.
Publication DateSupported Products
(Servers)
Supported SmartSetup
Version
Supported Operating
Systems
Manufacturing Part
Number
September, 2008BL860c, BL870c,
rx2660, rx3600,
rx6600, rx7620,
rx7640, rx8620,
rx8640, Superdome,
Superdome/sx2000
Version 6.1Microsoft Windows
Server 2003 for
Itanium-based
Systems, 64-bit
Microsoft Windows
Server 2008 for
Itanium-based
Systems, 64-bit
5992-4491
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:
[email protected]
Please include the document title, manufacturing part number, and any comment, error found,
or suggestion for improvement you have concerning this document.
8

1 Debugging the kernel locally
If you have programmed on the Windows operating system for any length of time, you are
probably familiar with user-mode debuggers and aware of kernel-mode debuggers. User-mode
debuggers help developers to debug applications. Kernel-mode debuggers are used mostly by
driver writers to debug device drivers and by support professionals to analyze system crashes.
This chapter describes how to locally debug the operating system kernel on HP Integrity servers.
In a local debugging environment, you are physically located near the server you want to debug.
You use a host machine, typically a laptop, that has the Windows debugging software installed
on it. You connect the host machine to the server with a cable (this sometimes requires the use
of a custom-made converter plug), and begin the debugging process.
NOTE: You can use the local debugging procedures described in this chapter on all HP Integrity
servers, except the following:
• HP Integrity rx7640 servers
• HP Integrity rx8640 servers
• HP Integrity Superdome servers with the sx2000 chipset
You debug these servers remotely, over a LAN, using the methods described in the next chapter.
Overview
A typical local kernel debugging environment for Windows systems consists of a host machine,
which runs the debugging software; a connecting cable (and sometimes a custom-made converter
plug); and an HP Integrity server target machine. The host is usually a laptop installed with
Microsoft Debugging Tools for Windows (x86) software, and the cable is either a null modem
serial or CAT-5 cable. The target is always an HP Integrity server running Microsoft Windows
Server 2003 or Windows Server 2008 for Intel® Itanium-based systems.
Use the following table to determine which setup is required, based on your target:
Table 1-1 Kernel debugging setup options
TargetCable (+ Converter)Host (+ Debugging software)
Works with the following HP Integrity
server models:
• BL860c
• BL870c
• rx1620
• rx2600
• rx2620
• rx2660
• rx3600
• rx4640
• rx6600
Serial (RS232) null modem cable (DB9
female)
+
5x2-to-DB9M converter (for rx1620
only)
Laptop or workstation
+
Microsoft Debugging Tools for
Windows
Overview 9

Table 1-1 Kernel debugging setup options (continued)
Works with the following HP Integrity
server models:
• rx5670
• rx7620
• rx8620
• Superdome/sx1000
CAT-5 cable (RJ45)
+
RJ45-to-DB9F converter
Laptop or workstation
+
Microsoft Debugging Tools for
Windows
Works with the following HP Integrity
server models:
• rx7640
• rx8640
• Superdome/sx2000
No cable required.
(These servers are debugged
remotely, over a LAN, as described
in the next chapter.)
Laptop or workstation
+
Microsoft Debugging Tools for
Windows
The following sections provide instructions for setting up the host, building a cable converter if
necessary, setting up the target, and connecting the components with the cable. Setting up the
host involves installing the debugging tools. Setting up the target can involve locating and
enabling the kernel debug port and adding a boot configuration option to the operating system.
IMPORTANT: Using the Microsoft Debugging Tools for Windows software to debug kernel
problems is beyond the scope of this document. Debugging the kernel requires deep knowledge
of operating system internals and familiarity with the architecture of the HP Integrity servers.
This is best done by someone with expertise in both areas.
Setting up the host machine
The host is a machine that runs the debugging session. In a typical environment, the host is the
computer that is connected to the target (the machine being debugged) and that runs the debug
tools.
Microsoft provides the Debugging Tools for Windows software, which is a package of extensible
tools for debugging user-mode and kernel-model programs on the Windows family of operating
systems. The Debugging Tools for Windows package contains four debuggers: CDB, NTSD, KD,
and WinDbg.
•Console Debugger (CDB) and NT Symbolic Debugger (NTSD) are console applications
that can debug user-mode programs. These two debuggers are nearly identical except in
the manner in which they are launched.
•Kernel Debugger (KD) is a character-based console application that enables in-depth analysis
of kernel-mode activity on all operating systems based on Windows. You can use KD
(kd.exe) to debug kernel-mode programs and drivers or to monitor the behavior of the
operating system itself. KD also supports multiprocessor debugging. Typically, the KD tool
runs on the host but not on the computer being debugged.
•Windows Debugger (WinDbg) is a powerful debugging tool capable of both user-mode
and kernel-mode debugging. WinDbg (windbg.exe) provides full source-level debugging
for the Windows kernel, kernel-mode drivers, system services, and for user-mode applications
and drivers. WinDbg can view source code, variables, stack traces, and memory. It can also
set breakpoints.
Debugging Tools for Windows includes an online help file with detailed documentation about
each tool. See this help file for more information.
Install Debugging Tools for Windows
Versions of the Debugging Tools for Windows package are available for 32-bit x86, native Intel
Itanium, and native x64 platforms. Choose the package version based on the processor of the
host computer. Typically, you would select the Debugging Tools for Windows (x86) 32-bit
package.
10 Debugging the kernel locally

x86 Host If the host uses an x86 processor, always use the 32-bit package.
Itanium Host If, like the target, the host is Itanium-based — an entry-level HP Integrity
server being used as a development platform, for example — then the
following rules apply:
• To analyze a dump file, use either the 32-bit package or the Itanium
package. It does not matter whether the dump file is a user-mode dump
file or a kernel-mode dump file.
• To perform live kernel-mode debugging, use either the 32-bit package
or the Itanium package. It does not matter whether the target is an
Itanium-based machine.
• To perform live user-mode debugging, always use the Itanium package.
It does not matter whether the target is a 64-bit application or a 32-bit
application.
You can install the Debugging Tools for Windows package from the Windows Driver Development
Kit (DDK), Platform Software Development Kit (SDK), or the Customer Support Diagnostics
CD. You can also download the latest release of the package from the Web. The package is
updated frequently. To ensure that you have the most up-to-date tools for the task, obtain the
package from the Web site:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
If you select Custom Install, you can control which features in this package are installed. The
Custom Install options are as follows:
• The Debuggers feature is selected by default. If you leave this selected, installation includes
the debuggers WinDbg, KD, CDB, and NTSD; associated modules, such as DbgHelp; the
symbol server SymSrv; the source server SrcSrv; the dump file tool ADPlus; the remote
debugging tool DbgSrv; and several extension libraries.
• The Tools feature and its Helpful Tools subfeature are selected by default. If you leave these
selected, installation includes the tools SymStore, SymChk, DbgRpc, Logger, LogViewer,
KDbgCtrl, DumpChk, GFlags.exe,TList.exe,Kill.exe,List.exe,Breakin.exe,
and UMDH, as well as the remote debugging tools Remote.exe, DbEngPrx, and KdSrv.
• The Documentation feature and its Debugging Tools subfeature are selected by default. If
you leave these selected, installation includes the Debugging Tools for Windows
documentation (debugger.chm).
• The SDK feature and its subfeatures are not selected by default. If you select these features,
installation includes the headers and libraries necessary to build debugger extensions, several
sample extensions and other samples, the “Debug Help Library” documentation
(dbghelp.chm), and the source server documentation (srcsrv.doc).
After the installation completes, and after you complete the other required tasks, such as preparing
your cable and setting up the target machine, you can launch the Windows Debugger (WinDbg)
by selecting Start > All Programs > Debugging Tools for Windows > WinDbg.
Building a converter for your cable
Some HP Integrity servers do not have a DB9 serial port. To connect the host to these servers,
you must build or buy a converter plug to use to connect a cable to the debug port on the server.
The following sections provide pin-out details for the debug ports on each server, so you can
make the converter you need.
Build a 5x2-to-DB9M converter (rx1620)
On the rx1620 system board, the kernel debug port 5x2 male pins are wired as follows:
Building a converter for your cable 11

Figure 1-1 rx1620 debug port (male pins on system board)
1
2 4
3 5
6
7
8
9
10
5x2 Male Pins on System Board
Front of
Server
You can sometimes find a 5x2-to-DB9M converter in electronics surplus stores because it was
often used on the motherboards of older computers. If you cannot locate one, you can build the
connector yourself using the information in the following table.
Table 1-2 DB9 male pin-out to 5x2 female
5x2 Female ConnectorSignal DescriptionDB9 Male Pin
1CD (carrier detect)1
2RX (receive data)2
3TX (transmit data)3
4DTR (data terminal ready)4
5GND (ground)5
6DSR (data set ready)6
7RTS (request to send)7
8CTS (clear to send)8
9RI (ring indicator)9
10——
Build a RJ45-to-DB9F converter (rx5670, rx7620, rx8620, and Superdome/sx1000)
The following picture shows the orientation of the individual wires inside the required plug
ends (RJ45 and DB9 Female).
Figure 1-2 Required plug ends and internal wiring
Use these wiring details and one of the following pin-out tables to build the RJ45-to-DB9F
converter that applies to your server model number.
12 Debugging the kernel locally

Table 1-3 Computer pin-outs or HP Integrity rx5670 servers
DB9 Female PinWire ColorRJ45 Pin
1Blue1
3Orange2
2Black3
4Red4
5Green5
6Yellow6
7Brown7
8Gray (White)8
Table 1-4 Computer pin-outs for HP Integrity rx7620 and rx8620 servers
DB9 Female PinWire ColorRJ45 Pin
4Blue1
8Orange2
5Black3
3Red4
2Green5
NCYellow6
7Brown7
6Gray (White)8
Table 1-5 Computer pin-outs for HP Integrity Superdome/sx1000 servers
DB9 Female PinWire ColorRJ45 Pin
7Blue1
5Orange2
NCBlack3
8Red4
3Green5
NCYellow6
2Brown7
NCGray (White)8
Setting up and connecting to the target machine
To set up the server and initiate local debugging, complete the following steps:
1. Change the boot configuration (required for all servers).
2. Locate and enable the correct debug port (required for cell-based servers with multiple
operating system instances and BL860c/BL870c blade servers).
3. Connect the host machine to the server debugging port.
Setting up and connecting to the target machine 13

Because you must reboot for the boot configuration changes to take effect, change the boot options
first, locate and enable the debug port if necessary, and then connect the cable to the debug port
and proceed with debugging.
The procedures that follow are presented in the order they should be performed. Some sections
apply to all servers; some apply to certain models only, as indicated in the title. Follow only the
instructions in the sections that are marked with your server model number and in the sections
marked “applies to all servers.”
Change the boot configuration (applies to all servers)
To perform kernel-mode debugging, you must enable and configure certain features that are
established when the operating system loads. The settings for these features are included in the
boot options — values that determine how the boot loader loads and configures the operating
system and other bootable programs and devices. Windows Server 2003 and Windows Server
2008 use different mechanisms to store these boot options. Consequently, different procedures
and tools must be used to set or change them.
In systems running Windows Server 2003, you can edit the boot options in Extensible Firmware
Interface (EFI) nonvolatile RAM (NVRAM) in two ways, using different tools:
•Bootcfg (bootcfg.exe) is a command-line tool that enables you to edit boot options while
the operating system is running. You can use Bootcfg to add, delete, and change the values
of all valid boot options. You can also use Bootcfg commands in a script or batch file to set
boot options or to reset them after you replace or upgrade an operating system.
•Nvrboot (nvrboot.efi) is an EFI-based boot entry editor that you can run when the
operating system is shut down. Nvrboot edits boot entries and includes commands to export
backup copies of boot entries and to import backup copies of boot entries into NVRAM.
You can access Nvrboot from the EFI Shell in the msutil directory of the system partition
(fsN:/msutil/nvrboot.efi, where Nis the number of the file system).
In systems running Windows Server 2008, you must edit the boot options with a different tool:
•BCDEdit (bcdedit.exe) is a command-line tool for adding, deleting, editing, and modifying
boot data in a boot configuration data (BCD) store. The usage information provided below
is a quick summary of some of the main features. For a complete description of all arguments
and parameters, refer to the Microsoft documentation found here:
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/
BCDedit_reff.doc
Windows Server 2003 Systems Only ⇒ Option 1: Using Bootcfg (recommended)
To edit boot options using the Bootcfg tool, complete the following steps:
14 Debugging the kernel locally

1. At the command-line prompt, enter the following command:
C:\>bootcfg
The current boot configuration appears, as shown in the following example:
Boot Options
------------
Timeout: 20
Default:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
CurrentBootEntryID: 1
Boot Entries
------------
Boot entry ID: 1
OS Friendly Name: Windows Server 2003, Enterprise
OsLoadOptions: /redirect
BootFilePath:
\Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efi
OsFilePath:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
Boot entry ID: 2
OS Friendly Name: Internal Bootable DVD
Boot entry ID: 3
OS Friendly Name: EFI Shell [Built-in]
In this example, you can see that “Boot entry ID 1” is the default Windows boot option. It
has only the out-of-band management (EMS or SAC prompt) configured as an option (the
“redirect” option). On some systems, the NOVESA option is listed here, too.
You must add a couple of options to enable live debugging. Make a copy of the boot entry
and then add the options.
2. Make a copy of the default boot entry by issuing the following command:
C:\>bootcfg /copy /d “Windows Server 2003, Enterprise with Debugging
Enabled”/id 1
The system indicates that it successfully copied boot entry “1.”
The new entry is copied to the bottom of the list and becomes the last entry. Because the
previous example contains only three boot entries, the new boot entry is assigned “ID 4”
(remember, this is only an example; if your system has more boot options, your ID number
will be higher).
3. Issue the bootcfg command again to see the new boot entry ID 4:
C:\>bootcfg
The new boot configuration appears:
Boot Options
------------
Timeout: 20
Default:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
CurrentBootEntryID: 1
Boot Entries
------------
Boot entry ID: 1
Setting up and connecting to the target machine 15

OS Friendly Name: Windows Server 2003, Enterprise
OsLoadOptions: /redirect
BootFilePath:
\Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efi
OsFilePath:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
Boot entry ID: 2
OS Friendly Name: Internal Bootable DVD
Boot entry ID: 3
OS Friendly Name: EFI Shell [Built-in]
Boot entry ID: 4
OS Friendly Name: Windows Server 2003, Enterprise with Debugging Enabled
OsLoadOptions: /redirect
BootFilePath:
\Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efi
OsFilePath:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
Boot entry 4 is the same as boot entry 1 except for the description (or operating
system-friendly name).
4. Add the Debug and Baud options to boot entry 4 by executing the following command:
C:\>bootcfg /debug on /baud 115200 /id 4
The system indicates that the operating system load options were changed for boot entry
ID 4.
In this example, the baud rate is configured at 115200. If your laptop does not support this
speed, try a different value, such as 38400. Remember to use the same value in the kernel
debugger where appropriate.
16 Debugging the kernel locally

5. To confirm that the entries were added correctly, run the bootcfg command again:
C:\>bootcfg
The new boot configuration appears:
Boot Options
------------
Timeout: 20
Default:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
CurrentBootEntryID: 1
Boot Entries
------------
Boot entry ID: 1
OS Friendly Name: Windows Server 2003, Enterprise
OsLoadOptions: /redirect
BootFilePath:
\Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efiOsFilePath:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
Boot entry ID: 2
OS Friendly Name: Internal Bootable DVD
Boot entry ID: 3
OS Friendly Name: EFI Shell [Built-in]
Boot entry ID: 4
OS Friendly Name: Windows Server 2003, Enterprise with Debugging Enabled
OsLoadOptions: /redirect /debug /baudrate=115200
BootFilePath:
\Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efi
OsFilePath:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
Boot entry ID 4 now shows the debug and baud rate switches. As mentioned previously, a
COM port entry is not required for HP Integrity servers.
Windows Server 2003 Systems Only ⇒ Option 2: Using Nvrboot
To edit boot options using the Nvrboot tool, complete the following steps:
1. From the EFI shell, navigate to the MSUTIL directory and execute the NVRBOOT.EFI
command, as shown here:
fs1:\> dir
Directory of: fs1:\
03/25/03 05:00a 841,216 SETUPLDR.EFI
06/25/03 11:14a <DIR> 1,024 EFI
06/25/03 11:14a <DIR> 1,024 MSUtil
2 File(s) 841,343 bytes
2 Dir(s)
fs1:\> cd msutil
fs1:\MSUtil> nvrboot
2. Select M(Modify) to modify the operating system boot loader.
Setting up and connecting to the target machine 17

3. At the Enter OS boot option to modify: prompt, select the first boot option by
entering: 1. The system displays the following:
1 LoadIdentifier = Windows Server 2003, Datacenter
2 OsLoadOptions = /REDIRECT /NOVESA
3 EfiOsLoaderFilePath = cf5f2ddc-b885-11d7-b831-000000000000 ::
\efi\microsoft\winnt50\ia64ldr.efi
4 OsLoaderFilePath = e605a034-b885-11d7-b831-000000000000 :: \windows
Enter VAR to modify: 2
4. At the Enter VAR to modify: prompt, select the second variable to modify
(OsLoadOptions) by entering: 2.
5. Reenter the OsLoadOptions variable, this time adding the /DEBUG and /BAUDRATE switches,
as follows:
OsLoadOptions=/REDIRECT /NOVESA /DEBUG /BAUDRATE=115200
NOTE: The /NOVESA switch is needed only on cell-based servers running Windows Server
2003 without SP1 and with a VGA card installed in the nPartition.
6. Verify that the change was made by repeating step 1 through step 3. The system displays
the following:
1 LoadIdentifier = Windows Server 2003, Datacenter
2 OsLoadOptions = /REDIRECT /NOVESA /DEBUG /BAUDRATE=115200
3 EfiOsLoaderFilePath = cf5f2ddc-b885-11d7-b831-000000000000 ::
\efi\microsoft\winnt50\ia64ldr.efi
4 OsLoaderFilePath = e605a034-b885-11d7-b831-000000000000 :: \windows
7. After verifying the changes to the OsLoadOptions variable, exit and boot the operating
system.
After debugging is complete, remove the /DEBUG and /BAUDRATE=115200 switches from the
boot configuration OsLoadOptions variable and reboot the operating system.
Windows Server 2008 Systems Only ⇒ Using BCDEdit
The values you assign with this tool depend on the type of connection you are trying to make
with the target system. At any time from the command line you can enter the following commands
to see the online help regarding tool usage:
bcdedit /?
or
bcdedit /dbgsettings /?
To enable debugging for a typical serial connection in Windows Server 2008, complete the
following steps:
1. Make a copy of the default boot entry by issuing the following command:
C:\>bcdedit /copy {identifier_of_boot_entry_to_be_copied} /d
“original non-debug boot entry”
The system indicates that it successfully copied the boot entry with a new description.
2. Set the connection type and baud rate for the debugger:
C:\>bcdedit /dbgsettings SERIAL BAUDRATE:115200
18 Debugging the kernel locally

3. Enable the debugger for the desired boot entry:
C:\>bcdedit /debug
{identifier_of_boot_entry_targeted_for_kernel_debugging} ON
Once again, for a complete description this tool, refer to the Microsoft documentation found
here:
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/
BCDedit_reff.doc
BL860c and BL870c servers
Connect the serial-USB-video cable (or SUV, part number 416003–001 that was supplied with
the server) to the 9–pin serial connector on the front of the BL860c/BL870c server (target), as
shown in the following image.
Figure 1-3 BL860c/BL870c debugging port
Now connect one end of a null modem cable to the SUV serial port. Connect the other end of the
null modem cable to the laptop, PC, or other blade server acting as the host. Because the SUV
serial port is shared between the iLO console and the debug serial port, you must issue the
following command at the MP command prompt to direct output to the debug serial port:
MP:CM> ca –local –mode aux
rx1620 server
Connect the cable between the laptop (host) and the rx1620 server (target) using the 5x2-to-DB9M
converter as shown in the following image.
Setting up and connecting to the target machine 19

Figure 1-4 rx1620 debugging port
When you face the front of the server, the first pin (#1) is located in the lower right corner of the
rectangle shown in the previous image. It is also indicated directly on the board with a small
white circle or a similar mark.
rx2600 and rx2620 servers
For rx2600 and rx2620, connect the serial port on the laptop or workstation to the DB9 port in
the back of the server using a standard DB9 female-terminated RS-232 null modem cable. The
following image shows the location of the DB9 port.
Figure 1-5 rx2600 and rx2620 debugging port
rx2660 servers
For rx2660 servers, connect the serial port on the laptop or workstation to the DB9 port marked
“Auxiliary”, located on the back of the server, using a standard DB9 female-terminated RS-232
null modem cable. The following image shows the location of the DB9 port.
20 Debugging the kernel locally