background image

Compaq ProLiant Server NMI Crash Dump Feature

6

11N8-0100A-WWEN

Initiating a NMI Crash Dump Under NetWare

1.

 

User presses the NMI Crash Dump push button switch which will present the user with a
abend screen.

2.

 

Depending on the version of NetWare, you may see either an ABEND (Abnormal END)
screen or a NetWare debugger screen.

a)

 

From the ABEND screen, press “Y” to create a core dump

b)

 

From the debugger, type the command “.c” (dot-c) to initiate a core dump

3.

 

Note that the core dump file will be saved on the C: drive (typically C:\COREDUMP.IMG).
An adequate amount of free space must be available on the C: drive to store the entire core
dump file, which can be as large as the memory installed in the system.

4.

 

Under some circumstances, you may have to force entry into the NetWare debugger. Press
shift-alt-shift-esc to enter the debugger, then use the “.c” command to initiate a core dump.

Initiating a NMI Crash Dump Under SCO
OpenServer 5 and SCO UnixWare 7

1.

 

User presses the NMI Crash Dump push button switch. The core dump will be written
automatically to the swap area. The size and regions of the core dump are determined by
operating system specific features. The user should refer to SCO System Administration
documentation for information regarding tuning the SCO operation system for generating a
core dump.

Note:

  If the SCO Kernel Debugger is loaded, then the user will be at the SCO Kernel Debugger

command prompt when either the button is pressed or the system management (cpqw) driver is
configured to generate a crash dump for ASR events. The user can usually just quit the SCO
Kernel Debugger to generate a crash dump.

2.

 

When the systems comes back up, the user is prompted if they want to save the dump to a
file. The following information will be required for further analysis of the core dump:

 

The Kernel that was running at the time (/stand/unix)

 

The Crash Dump file

 

For SCO UnixWare 7, the entire contents of the /etc/conf/mod.d directory at the time of
the crash should be captured (i.e. a tar file).

Note:

  Users must save all of the information listed above immediately on the subsequent boot. If

not then there may not be enough information available to perform a detailed analysis of the
problem. Additionally, if the swap area is smaller than the physical memory installed in the
system a selective Crash Dump will be generated. This usually includes kernel memory space.

Summary of Contents for ProLiant 8000

Page 1: ...ndows 2000 8 Microsoft Software subject to change 8 Compaq Software subject to change 9 Where Is the Crash Dump Button located 10 ProLiant 8000 10 ProLiant 8500 11 Compaq ProLiant Server NMI Crash Dum...

Page 2: ...tions tested or described may or may not be the only available solution This test is not a determination of product quality or correctness nor does it ensure compliance with any federal state or local...

Page 3: ...can provide critical information for root cause analysis that may be difficult or impossible to obtain through other means A user initiates a Non Maskable Interrupt NMI event by pressing the dump swi...

Page 4: ...NT 4 0 Windows 2000 SCO OpenServer 5 and SCO UnixWare 7 ASR initiates the NMI Crash Dump instead of resetting the machine ASR does not cover cases where the operating system or applications may be exe...

Page 5: ...ments unless customer wishes to configure to ASR crash dump file generation Allows user level settings for an ASR crash dump file generation Compaq Hardware Push button switch is added to Compaq Serve...

Page 6: ...the core dump are determined by operating system specific features The user should refer to SCO System Administration documentation for information regarding tuning the SCO operation system for gener...

Page 7: ...nel in the usual way and reboot the server to activate the new setting How to Set Up NMI Crash Dump Under Windows NT 4 0 Microsoft Software 1 User installs Microsoft Windows NT 4 0 with Service Pack 4...

Page 8: ...mp HKEY_LOCAL_MACHINE System CurrentControlSet Services Sysmgmt Parameters Featu reASR DWORD 0xe11 Disabling ASR NMI Crash Dump HKEY_LOCAL_MACHINE System CurrentControlSet Services Sysmgmt Parameters...

Page 9: ...ASR DWORD 0xe11 HKEY_LOCAL_MACHINE System CurrentControlSet Services cpqcsm Parameters Featur eASR DWORD 0xe11 HKEY_LOCAL_MACHINE System CurrentControlSet Services cpqss Parameters FeatureA SR DWORD 0...

Page 10: ...utton located Note The NMI Crash Dump button hardware will generate a PCI SERR under all Operating Systems Initiating core memory dumps may be attainable under each individual OS ProLiant 8000 NMI Cra...

Page 11: ...Compaq ProLiant Server NMI Crash Dump Feature 11 11N8 0100A WWEN ProLiant 8500 NMI Crash Dump Button Figure 4 NMI Crash Dump Button Access from the Rear of the ProLiant 8500 Chassis...

Reviews: