HP Integrity BL890c - i2 Server Software Manual
Windows server 2008 sp2 and windows server 2008 r2 on hp integrity servers kernel debugging guide
Hide thumbs
Also See for Integrity BL890c - i2 Server:
- Manual (229 pages) ,
- Software manual (44 pages) ,
- Quickspecs (34 pages)
Related Manuals for HP Integrity BL890c - i2 Server
Summary of Contents for HP Integrity BL890c - i2 Server
- Page 1 Windows Server 2008 SP2 and Windows Server 2008 R2 on HP Integrity Servers Kernel Debugging Guide HP Part Number: T8704-96000 Published: August 2010...
- Page 2 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.
-
Page 3: Table Of Contents
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......................9 1 Debugging the kernel locally..................11 Overview...............................11 Setting up the host machine........................12 Install Debugging Tools for Windows.....................13 Building a converter for your cable......................14 Build a 5x2-to-DB9M converter (rx1620)..................14 Build a RJ45-to-DB9F converter (rx5670, rx7620, rx8620, and Superdome/sx1000)......14... - Page 4 3 Debugging HP Virtual Machines guests..............37 HPVM Windows guest debug process....................37 Table of Contents...
- Page 5 List of Figures rx1620 debug port (male pins on system board)................14 Required plug ends and internal wiring..................15 rx1620 debugging port........................21 rx2600 and rx2620 debugging port....................21 rx2660 debugging port........................22 rx3600 and rx6600 debugging port....................22 rx4640 debugging port........................23 Location of three jumpers on rx4640 motherboard...............23 rx5670 debugging port........................24 1-10 Debugging port on the rx8620.......................26...
- Page 6 List of Tables Kernel debugging setup options....................11 DB9 male pin-out to 5x2 female....................14 Computer pin-outs or HP Integrity rx5670 servers...............15 Computer pin-outs for HP Integrity rx7620 and rx8620 servers...........15 Computer pin-outs for HP Integrity Superdome/sx1000 servers..........15 List of Tables...
-
Page 7: About This Document
About This Document This document describes the process for debugging the operating system kernel on HP Integrity servers running Microsoft Windows® Server 2008 SP2 and Windows® Server 2008 R2. The document printing date and part number indicate the document’s current edition. The printing date changes when a new edition is printed. -
Page 8: Related Information
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 NOTE A note contains additional information to emphasize or supplement important points of the main text. -
Page 9: Hp Encourages Your Comments
should subscribe to the appropriate product support service. See your HP sales representative for details. Manufacturing Part Supported Operating Supported Smart Supported Products Publication Date Number Systems Setup Version (Servers) T8704–96000 Microsoft Windows Version 7.0 BL860c August, 2010 Server 2008 with BL870c Service Pack 2 (SP2) BL860c i2... -
Page 11: Debugging The Kernel Locally
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. -
Page 12: Setting Up The Host Machine
Table 1-1 Kernel debugging setup options (continued) Laptop or workstation Serial (RS232) null modem cable (DB9 Works with the following HP Integrity female) server models: • BL860c Microsoft Debugging Tools for • BL870c Windows 5x2-to-DB9M converter (for rx1620 • BL860c i2 only) •... -
Page 13: Install Debugging Tools For Windows
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. -
Page 14: Building A Converter For Your Cable
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. -
Page 15: Required Plug Ends And Internal Wiring
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. Table 1-3 Computer pin-outs or HP Integrity rx5670 servers RJ45 Pin Wire Color DB9 Female Pin... -
Page 16: Setting Up And Connecting To The Target Machine
Table 1-5 Computer pin-outs for HP Integrity Superdome/sx1000 servers (continued) RJ45 Pin Wire Color DB9 Female Pin Green Yellow Brown Gray (White) Setting up and connecting to the target machine To set up the server and initiate local debugging, complete the following steps: Change the boot configuration (required for all servers). -
Page 17: Windows Server 2003 Systems Only Option 1: Using Bootcfg (Recommended)
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. - Page 18 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] Boot entry ID: 4 OS Friendly Name: Windows Server 2003, Enterprise with Debugging Enabled...
-
Page 19: Windows Server 2003 Systems Only Option 2: Using Nvrboot
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:... -
Page 20: Windows Server 2008 Systems Only Using Bcdedit
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 OsLoadOptions = /REDIRECT /NOVESA EfiOsLoaderFilePath = cf5f2ddc-b885-11d7-b831-000000000000 :: \efi\microsoft\winnt50\ia64ldr.efi OsLoaderFilePath = e605a034-b885-11d7-b831-000000000000 :: \windows Enter VAR to modify: 2 At the Enter VAR to modify: prompt, select the second variable to modify (OsLoadOptions) by entering: 2. -
Page 21: Rx1620 Server
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://technet.microsoft.com/en-us/library/cc709667(WS.10).aspx 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. -
Page 22: Rx3600 And Rx6600 Servers
Figure 1-5 rx2660 debugging port rx3600 and rx6600 servers For rx3600 and rx6600 servers, connect the serial port on the laptop or workstation to the serial port on the far right side of the back of the server (when facing the back). The following image shows the connection. -
Page 23: Rx5670 Server
Figure 1-7 rx4640 debugging port To enable the debug port, you must open the server's I/O bay and short a jumper header as follows (jumper not provided): Power the system off and verify that it is disconnected from the main AC power supply. Locate the set of three jumpers directly above the brown edge connector socket (the one resembling an AGP slot) on the motherboard, as shown in the following image. -
Page 24: Rx7620, Rx8620, And Superdome/Sx1000 Servers
Figure 1-9 rx5670 debugging port rx7620, rx8620, and Superdome/sx1000 servers To set up the rx7620, rx8620, or Superdome/sx1000 for local debugging, complete the following steps: Locate the correct debugging port by identifying the core cell. Copy the KD utility to the EFI system partition (rx7620 and rx8620 only). Enable debug port (rx7620 and rx8620 only). -
Page 25: Option 2: Identifying The Core Cell Using An Npartition Command
In this example, the root cell is cell 0, physically the topmost cell in the server. Option 2: Identifying the core cell using an nPartition command To identify the nPartition’s core cell while the operating system is running: • You must know the server IPMI password. •... -
Page 26: Connect To The Debug Port
At the EFI Shell prompt, enter the following command: EFI Shell> kd -on Now the shared port on the core cell is enabled for kernel debugging. The state of the port is consistent across reboots. However, removing power to the system reverts the debug port back to its default state. -
Page 27: Bl860C And Bl870C Server Blades
Figure 1-1 1 Debugging port on Superdome/sx1000 This figure shows two adjacent cells and the kernel debugging ports on each. Always use the RJ-45 connector closest to the handle. Only one debug port can be active for a given partition that spans one or more non-consecutive cells, and you must always connect to the port on the root cell of that partition. -
Page 28: Bl860C I2, Bl870C I2, And Bl890C I2 Server Blades
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: ca –local –mode aux... -
Page 29: Debugging The Kernel Remotely
2 Debugging the kernel remotely 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. -
Page 30: Install Debugging Tools For Windows
kd.exe) to debug kernel-mode programs and drivers or to monitor the behavior of the OS 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. -
Page 31: Setting Up And Connecting To The Target Machine
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 >... - Page 32 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...
- Page 33 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...
-
Page 34: Windows Server 2003 Systems Only Option 2: Using Nvrboot
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:... -
Page 35: Windows Server 2008 Systems Only Using Bcdedit
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 OsLoadOptions = /REDIRECT /NOVESA EfiOsLoaderFilePath = cf5f2ddc-b885-11d7-b831-000000000000 :: \efi\microsoft\winnt50\ia64ldr.efi OsLoaderFilePath = e605a034-b885-11d7-b831-000000000000 :: \windows Enter VAR to modify: 2 At the Enter VAR to modify: prompt, select the second variable to modify (OsLoadOptions) by entering: 2. -
Page 36: Enable Ipmi Lan Access And The Debugging Option
Enable the debugger for the desired boot entry: C:\>bcdedit /debug {identifier_of_boot_entry_targeted_for_kernel_debugging} ON For a complete description this tool, refer to the Microsoft documentation found here: http://technet.microsoft.com/en-us/library/cc709667(WS.10).aspx Enable IPMI LAN access and the debugging option Enable the Windows debugging option and enable LAN access to the management processor (MP) by completing the following steps: Log in to the server’s MP. - Page 37 3 Debugging HP Virtual Machines guests HP Virtual Machines (HPVM) is a soft partitioning and virtualization technology that provides operating system isolation with CPU allocation and shared I/O. HPVM enables a single Integrity server to emulate multiple virtual machines running distinct operating systems and environments. The Virtual Machines solution consists of two components: •...