1. Manuals
  2. Brands
  3. HP Manuals
  4. Server
  5. Rx2620-2 - Integrity - 0 MB RAM
  6. Manual

HP Rx2620-2 - Integrity - 0 MB RAM Manual

Integrity servers with microsoft windows server 2003 and windows server 2008 kernel debugging guide
Hide thumbs Also See for Rx2620-2 - Integrity - 0 MB RAM:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Service Manual, Manual
HP Integrity Servers with Microsoft®
Windows Server™ 2003 and Windows
Server™ 2008
Kernel Debugging Guide
HP Part Number: 5992-4491
Published: September 2008

Advertisement

Table of Contents
loading

Related Manuals for HP Rx2620-2 - Integrity - 0 MB RAM

Summary of Contents for HP Rx2620-2 - Integrity - 0 MB RAM

  • Page 1 HP Integrity Servers with Microsoft® Windows Server™ 2003 and Windows Server™ 2008 Kernel Debugging Guide HP Part Number: 5992-4491 Published: September 2008...
  • 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......................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...
  • Page 4 3 Debugging HP Virtual Machines guests..............35 HPVM Windows guest debug process....................35 Table of Contents...
  • Page 5 List of Figures rx1620 debug port (male pins on system board)................12 Required plug ends and internal wiring..................12 BL860c/BL870c debugging port.....................19 rx1620 debugging port........................20 rx2600 and rx2620 debugging port....................20 rx2660 debugging port........................21 rx3600 and rx6600 debugging port....................21 rx4640 debugging port........................22 Location of three jumpers on rx4640 motherboard...............22 1-10 rx5670 debugging port........................23 1-11...
  • Page 6 List of Tables Kernel debugging setup options.....................9 DB9 male pin-out to 5x2 female....................12 Computer pin-outs or HP Integrity rx5670 servers...............13 Computer pin-outs for HP Integrity rx7620 and rx8620 servers...........13 Computer pin-outs for HP Integrity Superdome/sx1000 servers..........13 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 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.

  • Page 8: Related Information

    NOTE A note contains additional information to emphasize or supplement important points of the main text. The name of a keyboard key or graphical interface item (such as buttons, KeyCap tabs, and menu items). Note that Return and Enter both refer to the same key.

  • Page 9: 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 10: Setting Up The Host Machine

    Table 1-1 Kernel debugging setup options (continued) Laptop or workstation CAT-5 cable (RJ45) Works with the following HP Integrity server models: • rx5670 Microsoft Debugging Tools for RJ45-to-DB9F converter • rx7620 Windows • rx8620 • Superdome/sx1000 Laptop or workstation No cable required. Works with the following HP Integrity server models: (These servers are debugged...

  • Page 11: Building A Converter For Your Cable

    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: •...

  • Page 12: Build A Rj45-To-Db9F Converter (Rx5670, Rx7620, Rx8620, And Superdome/Sx1000)

    Figure 1-1 rx1620 debug port (male pins on system board) 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.

  • Page 13: Setting Up And Connecting To The Target Machine

    Table 1-3 Computer pin-outs or HP Integrity rx5670 servers RJ45 Pin Wire Color DB9 Female Pin Blue Orange Black Green Yellow Brown Gray (White) Table 1-4 Computer pin-outs for HP Integrity rx7620 and rx8620 servers RJ45 Pin Wire Color DB9 Female Pin Blue Orange Black...

  • Page 14: Change The Boot Configuration (Applies To All Servers)

    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;...
  • Page 15 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 16 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 17: 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 18: 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 19: Bl860C And Bl870C Servers

    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.

  • Page 20: Rx2600 And Rx2620 Servers

    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.

  • Page 21: Rx3600 And Rx6600 Servers

    Figure 1-6 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 22: Rx5670 Server

    Figure 1-8 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 23: Rx7620, Rx8620, And Superdome/Sx1000 Servers

    Figure 1-10 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 24: 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 25: 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 26: Debugging Port On Superdome/Sx1000

    Figure 1-12 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 27: 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 28: Install Debugging Tools For Windows

    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.

  • Page 29: Setting Up And Connecting To The Target Machine

    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).
  • Page 30 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 31 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 32: 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 33: 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 34: 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 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 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 35 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: •...

This manual is also suitable for:

Integrity series

Table of Contents