HP Security Class: Customer Viewable User Doc ID: PAM39EF55E1

K-Class Troubleshooting

Quality Score: 0 0 Date Certified: 20001019
Doc Info
Doc Type: AN Date Last Updated: 20001019
HP Security Class: Customer Viewable Date Submitted: 20001013
  • Author: Paul Mulberry
  • Doc Submitter: PAUL A MULBERRY
  • Certifier: PAUL A MULBERRY
  • Product:
  • HW Model Number:
  • Operating System:
  • Platform Name: UNKNOWN
  • Product Name/Version:
  • Customer Defined: SupportRom:
  • SupportRom Database:
  • SupportRom Article Number:
  • SupportRom Issue/Volume:
  • Patch Categories: Sweep Date:
    Project: Cust View After Date: 19970101

    Last Modified: October 04, 2000

    HP 9000: K-Class Trouble-Shooting 


    Why do Extraneous Characters Appear in Front Panel Display Codes

    HP 9000 K-Class: Kx00, Kx10, Kx20

    Extraneous characters appear on Kx00, Kx10 and Kx20 front panel display codes when there is a problem.  The error will typically appear as 5 character hex code when OS is running.

    Normal HP-UX codes would be FxyF, where:

    Typical codes with fifth characters are a hex display code of FxyF? or FxyF1.

    Other 5th characters are possible.

    This problem does not affect the operation of the system and can be resolved by updating the Firmware/PDC Code to PDC 2.2 or higher.  See Verifying CPU Firmware Version (PDC code) to verify and update your system.

    Return to Contents

    What does it mean when "Memory not optimized" is displayed?

    If your memory is not configured for optimum performance, the following warning message appears when you boot the system:

    WARNING: Memory configuration is not optimized for performance. Refer to the System Installation or Memory Installation Manuals for memory configuration guidelines.

    Return to Contents

    How can I verify the firmware version (PDC code)?

    The current version of firmware can be determined using on-line diagnostics.  If on-line diagnostics are not present on your system, use the Boot Console Handler Procedure to verify the current revision.  Refer to the appropriate on-line diagnostic procedure to determine the version of firmware presently installed on your system.

    Verifying Firmware Version with On-line Diagnostics




    Return to Contents

    Verifying Firmware Version with Boot Console Handler (BCH)

    Boot Console Handler Procedure

    1. Log on as root, and enter reboot -r
      This command will shutdown the operating system and reboot the system.
    2. If AUTOBOOT is on, you will receive the following message:

    Process is starting autoboot process.
    To discontinue, press any key within 10 seconds.

    1. At this point, press any key within 10 seconds to interrupt the booting process.
    2. The Main Menu is displayed. The following prompt will appear:

    MAIN MENU: Enter command or menu>

    1. Enter the command: in
    2. The following prompt will appear:

    Information Menu: Enter Command>

    1. Enter the command fv.
      The system will respond with the current firmware revision.

    Creating the Firmware Update Tape

    The firmware patch applicable for your system can be obtained through the HP IT Resource Center (ITRC). The procedure for creating a bootable tape with firmware, and the procedure for updating is included with the patch, after the patch file has been "unpacked'.
    Unpack the patch file with the sh command.            

    prompt: sh (patch name)

    Two additional files will now be available. These files are xxxxyyyy.text and xxxxyyyy.frm.  The text file provides specific instructions for that release of firmware.  The frm file is the actual update image file.

    Return to Contents

    How Do I Troubleshoot & Configure the Internal Modem?

    General Comments

    The internal modem on the K-Class is provided so that the HP Predictive Support Software can alert your HP Customer Engineers of possible hardware events that need their attention. You should be aware of the fact that if you disable the modem or reconfigure it, your Predictive Software will not be able to use the modem and alert your HP CE of possible hardware related problems. With this in mind, you may want to consider adding an additional modem on another port for remote system administration activities. Most high speed modems can be used on other Modem (MDP or ADP) Mux ports and the Response Center can provide limited configuration information for many of them. Any use other than the intended purpose of the internal modem is not supported by the Hewlett Packard Response Center. This includes any getty process, kermit or UUCP.

    Return to Contents

    Internal or External Modem Configuration

    The "K' series modem architecture provides for either an internal (always installed) or external modem configuration. The internal modem is installed on the system's multifunction card and the phone line is connected through a line adapter module (LAM). This module is country specific and is attached to the back of the multifunction card. The external modem can be connected through a DB25 RS-232 port also on the multifunction card. This port is chosen using one of the Access Port commands from the system console.

    The procedure is as follows:

    1. Turn the front panel keyswitch right from vertical position to the service position.
    2. From the Console type [Ctrl] B to initiate the CM> prompt.
    3. At the CM> prompt, enter ca (Configure system remote support modem port.)
    4. The response will be:

    Current terminal mode identification: HP mode terminal
    Do you wish to change it? (Y[N]):

    1. Enter y
    2. The response will be:

    Select new terminal mode: (0=HP, 1=NON_HP, 2=AUTO_PWON)

    1. Enter 0 (This is typically set to 0 (HP) or 2 (AUTO))
    2. The response will be:

    The terminal mode is now: HP mode terminal

    Current remote console configuration: (current setting)
    Do you wish to change it? (Y[N]):

    1. Enter y
    2. The response will be:

    Select the new configuration (0=Internal Modem, 1=External modem, 2=AUTO):

    1. Enter 2
    2. The response will be:

    The new selection is now: AUTO Identification at power on.

    (Internal modem is currently selected)

    NOTE: Auto is the default setting for this configuration. It will always select the internal modem if it is available and the Line Adapter Module is installed. If you wish to force the selection of the external modem you must choose option 1.
    Current remote support modem port configuration:

    System identification: (current setting)
    Do you wish to change the configuration? (Y[N]):

    1. Enter y
    2. The response will be:

    Current system identification:
    New system identification (limited to 1 to 20 displayable characters or space for none): <chosen name>

    New configuration: (takes effect at next remote connection):
    System Identification: <chosen name>


    (Configuration complete)

    1. At the CM> prompt, enter co (Takes you back into console mode)

    You may now put the front panel keyswitch into the vertical (ON) position.

    Return to Contents


    The operating system configuration for the modem can be accomplished in one of the following four ways: 


    Included with the operating system on the "K" series system is a program called DIALIN. This program gives you the ability to configure and disable the internal modem port. The syntax is as follows:

    dialin [-b baud] action
    where action = enable | disable | status

    The way this works is when you type the command dialin enable the script will create the device files necessary to support the modem (ttyd0p7, cul0p7, and cua0p7) When you type dialin disable it removes the files.

    Do not use the -b option on the dialup script.  The communication speed at this level should always be set to 19200. The modem will speed sense to whatever modem you connect with (in or out), but it will talk to the "K" series backplane at 19200 baud.

    If you are running Predictive Support, the dialin script will not work. You will get the following message:

    HP Predictive Support/UX is configured to run on this system. Use HP Predictive Support/UX to enable/disable dialin access.

    If you are trying to configure the modem using the dialin command and get this message, the modem should already be configured and functional. If not then there is a problem with the Predictive configuration.

    Return to Contents


    To execute the predictive configuration program (psconfig) and enable or disable the modem proceed as follows:

    /opt/pred/bin/psconfig (run the program)

    1. At the main menu select option 4 - CONFIGURATION Options Menu
    2. At the "Configuration Options" menu select option 2 - Transfer Information
    3. At the "Configure Transfer Information" menu select option 2 SETUP modem port

    The system will scan the hardware for currently configured modem devices and list the configuration. Once the scan is complete, the output will look like this:

    1 - Callout device file [cul0p7] type [MUX]
    2 - Hardware Address [10/4/0] port [7]
    3 - Dialer name [ps_mt1932_tone]
    4 - Automatic transfer [y]
    5 - CCITT modem [n]
    6 - Maximum modem speed [2400]
    7 - Callin enabled [y]

    Set up the modem ports with these values? (Type y, n, or // to cancel):n
    Type a number or // to cancel:
    Select number 7 (Callin enabled)
    Type y or n for callin on /dev/ttyd0p7 or // to cancel:

    If the modem dialin is enabled and you want to disable it, answer no to this question. It will remove the entry from inittab and disable the SESSION dialin.

    To re-enable SESSION mode retrace your steps and reply yes to the dialin question. When remote console is enabled you will be able to connect regardless of the SESSION Status. (See remote console below)

    Return to Contents

    System Administration Manager (SAM)

    1. Log on as root
    2. Type SAM
    3. Highlight Peripheral devices and press [RETURN]
    4. Highlight Terminals and Modems and press [RETURN]
    5. At the Terminals and Modems screen, press [TAB] to go to the menu bar.
    6. Use the arrow and [RETURN] keys to select the Actions menu.
    7. Use the down arrow key to highlight Add Modem and press [RETURN].
    8. In the Add Modem screen, set or select the following parameters:
      1. The hardware path to the serial interface to be used by this modem.
      2. The port number to be used by this modem.(This should be port 7 )
      3. The speed (baud rate) to be used by this modem (19200 is the setting for the internal modem). (This is the serial line to the modem baud rate,Not the modem bps on-line rate.)
      4. Whether or not the modem will be used for calling out from your system.
      5. Whether or not the modem will receive incoming calls.
      6. Whether or not this is a CCITT Modem (European standard modem).Press [RETURN] to turn the CCIT modem selection on/off.  When you finish setting parameters,activate OK by pressing [F5] or tabbing to ok and pressing  [RETURN].
    9. You will receive a series of messages indicating the progress of the task. When you receive the message: 

    This modem has been added

    Select OK

    1. Exit the SAM by pressing EXIT[F8] then EXIT SAM[F8] or by tabbing to the file menu and selecting the first EXIT then EXIT SAM.

      Verify the device files with: 

      # lssf /dev/*0p7
      mux2 card instance 0 port 7 callout at address 10/4/0 /dev/cua0p7
      mux2 card instance 0 port 7 callout at address 10/4/0 /dev/cul0p7
      mux2 card instance 0 port 7 hardwired at address 10/4/0 /dev/tty0p7
      mux2 card instance 0 port 7 callin at address 10/4/0 /dev/ttyd0p7

      NOTE: The hardware path on the K100 will be 8/4/0

    Return to Contents


    NOTE: The external modem port is /dev/tty0p7. The modem device files are named the same as they were in HPUX 9.04, except of course, there is no "LU" number - but there is an Instance number. The major number will  vary and the minor number has been rearranged.

    /usr/sbin/mksf -d mux2 -H 8/4/0 -p7 -f -v -a 0 (tty = /dev/tty0p7)
    /usr/sbin/mksf -d mux2 -H 8/4/0 -p7 -f -v -a 1 (dialout = /dev/cul0p7, /dev/cua0p7)
    /usr/sbin/mksf -d mux2 -H 8/4/0 -p7 -f -v -a 2 (dialin = /dev/ttyd0p7)

    Notice the -f option adds the "H/W flow control bit" and the -a is for the "access-mode Port" (access modes are 0,1, or 2). The default access mode is 0 (Direct connect). The access-mode meanings are:

    Access-Mode    Port Operation  
    0                    Direct connect  
    1                      Dial out modem 
    2                      Dial in modem   

    Device file Examples:

    # ll /dev/*0p7
    crw-rw-rw- 1 bin bin 193 0x000701 Jun 14 11:16 /dev/cua0p7
    crw-rw-rw- 1 bin bin 193 0x000701 Jun 22 12:48 /dev/cul0p7
    crw--w--w- 1 bin bin 193 0x000700 Jun 1 11:14 /dev/tty0p7
    crw--w---- 1 uucp bin 193 0x000702 Jun 27 08:58 /dev/ttyd0p7

    # lssf /dev/*0p7
    mux2 card instance 0 port 7 callout at address 10/4/0 /dev/cua0p7
    mux2 card instance 0 port 7 callout at address 10/4/0 /dev/cul0p7
    mux2 card instance 0 port 7 hardwired at address 10/4/0 /dev/tty0p7
    mux2 card instance 0 port 7 callin at address 10/4/0 /dev/ttyd0p7

    If you had used the "-f" option, then the hardware flow control bit would
    be set and the minor number would have a "1" in the 5th position...

    crw-rw-rw- 1 bin bin 193 0x000711 Jun 22 12:48 /dev/cul0p7


    You still need a proper getty definition, which sets the protocol that the modem will use (internal or external modem). First edit the /etc/gettydefs file and add an entry similar to the following, at the BOTTOM of that file. You may want to make a backup copy of your gettydefs file first. You must use the "vi" visual editor for this operation, because the file will not work with tabs at the end of a line.


    # This is a comment line. Make sure you have one and only one blank line
    # before and after each definition in the gettydefs file. This is a sample
    # for the internal modem (19.2 kbs faxmodem; setup at 19,200 baud)

    # login:
    # 19200M

    # Notice the *one* blank line after the definition.....


    Now, test your new gettydefs file entry with this command:

    /etc/getty -c /etc/gettydefs | more

    If you get any error message, you will have to edit the file until it tests (or "parses") correctly. Now you can change the /etc/getty command in the /etc/inittab file to point to the correct getty definition:

    a1:3:respawn:/usr/sbin/getty -h ttyd0p7 19200M # This is typical a0:3:respawn:/usr/lbin/uucp/uugetty -r -t 60 ttyd0p7 19200M # Typical w/ uucp

    NOTE: 19200M is the speed or /etc/gettydefs entry, not the baud rate.  The /etc/gettydefs file sets protocols and baud rates for the login attempt and the user shell. It includes more than just the baud rate (ie. parity, flow control, data bits, etc.)

    See manpages for inittab, stty, or gettydefs for more details.

    Return to Contents


    To enable remote console on the "K" series system,   do the following from the local console:

    CM> er
    (enable remote)

    The following will be displayed:

    Current remote console access configuration:

    Remote CS: Disabled
    Mode: Multiple
    Password faults:

    Do you wish to change the configuration (Y[N]) (Enter Y)

    Remote console access is now enabled

    To change the parameters reply yes to the change request.

    To disable remote console access proceed as follows:

    CM> dr
    (Remote console access disabled.)

    Return to Contents


    To dial in using the remote console you would connect with the modem as with  any normal dialup. When the modems connect you will see the following:

    Remote console enabled

    To gain access to the console you must send a break from the remote terminal. For the operator to get access back while the session is still connected send a break from the console. While the remote console is active you have full control of the system to reboot, run offline diagnostics, and evaluate the system using the Access Port commands. Also, when you are using the remote console, all work will be echoed on the local console and when the local console is used, information will be echoed on the remote.

    When you want to disconnect from the remote console type:

    CM> di

    This will disconnect the remote console and return the control to the local console. You must still disable remote console ([CTRL]B CM>dr) to secure the system.

    Return to Contents


    One of the first things to check is the Phone Line that is connected to the modem. This can be done by disconnecting the Telephone line from the back of the modem and connecting it to a known good telephone.If this is ok then reconnect the phone line to the back of the modem.

    To unhang the modem port:

    1. First follow this procedure:   
    1. Logon as root
    2. Run SAM
    3. Select peripheral Devices
    4. Select TERM & Modems
    5. Highlight modem port in question (with space bar)
    6. Select actions (use F4 softkey and tab to Actions)
    7. Remove device
    8. Go back to actions
    9. Add MODEM
    10. Add modem for port in question (10/4/0.7 or 8/4/0.7 on K100)
    11. Exit SAM
    1. At prompt, #cd /var/spool/uucp and remove any LCKxxxxx files associated with the port in question
    1. At root, run kermit, then enter the
          C-Kermit> set line /dev/tty0p7
          C-Kermit> set speed 19200,
      Then the following message will be displayed:
          /dev/tty0p7, 19200 bps
      (This is what should be returned)
      Then enter the following:

          C-Kermit> connect

    This is what the system should respond with:
        Connecting to /dev/tty0p7, speed 19200
        The escape character is Ctrl-\ (Ascii 28, FS)

    Type the escape character followed by C to get back, or followed by ? to see other options.

    WARNING:  It is very important that the instructions below are followed to the letter.  If you make any mistakes, exit Kermit and start this step over.

    Type ATZ   (This tells the modem to break whatever its doing)

    Type OK    (This is what should come back from the modem)

    NOTE: (Hold the [CTRL] key down and press the [\] key -- let go of both keys and press the [C] key)

    [Ctrl \C] (To return to C-Kermit prompt)

    1. If the modem does NOT respond back with OK after connecting to the device file then go to STEP 6. Otherwise, continue with step 5.
    1. This port should now be unhung if the software or if a process was locked on to the port. Try using the port at this time to see if the problem has cleared up. If the problem is resolved, go to step 8, otherwise go to step 6.
    1. If the port still does not respond, then the only option is to HALT the system and cycle power on the system. It is very important that you HALT and not reboot.  A reboot or shutdown -r will not reset the internal modem, only a power cycle will.  You must do a shutdown -h. While the power is down, check the connection from the Core I/O Board to the Line Access Module (LAM).  This is the small module into which the phone line plugs.
    1. If halting the system and recycling power do not work, then a service call should be logged through the ITRC call logging function or call your local HP hardware service number.
    1. If the software and modem begin working after halting and recycling the power, make sure all current modem patches have been applied to resolve any potential problems in the future.

      Verifying Modem Internal Settings:
          Log on as root and run kermit
          C-Kermit> set line /dev/cua0p7
          C-Kermit> set speed 19200
          C_Kermit> parity none
          C-Kermit> show (to confirm 8, parity none)
          C-Kermit> connect

      There will be no prompt at this point, you are connected to the modem.

      Type atl5

    A string of characters will be returned. If &W0 and &E7 are in the string,  Then the modem has the correct values. Exit Kermit by typing:

    [Ctrl\C] (Control-backslash c), then exit.

    If instead &W1 and &E6 are returned then proceed to change the values as follows:

    Type one line at a time and wait for OK to appear on the next line before proceeding.

    The modem parameters are now set. Type atl5 again to see the new parameters, verify &E7 and &W0 are set.  Exit Kermit by typing:

    [Ctrl\C] (Control-Backslash C)

    Return to Contents

    Troubleshooting HP PowerTrust UPS configuration

    What is an Uninterruptable Power Supply (UPS) ?

    An Uninterruptable Power Supply(UPS) device is a power supply unit designed to monitor mains power being delivered to the host system, and in the event of a power failure supply power from an emergency source. In the case of HP PowerTrust this is from lead acid batteries.

    The function of the UPS is to provide enough power to maintain all system resources and attached peripherals in order that a graceful shutdown can be performed to avoid damage to the systems hardware and software.

    The graceful shutdown negates the need to perform file system checks and other potentially hazardous routines because the system was closed down in the correct manner and power isolated from the system to avoid hardware damage.

    Return to Contents

    What UPS Products does HP have to offer?

    HP PowerTrust Product Line




    600Va Standalone


    1300Va Standalone


    1.3KVa Rackmounted


    1.8KVa Rackmounted


    3.0KVa Rackmounted

    The 1.3KVa and 1.8KVa devices feature a single removable battery box, while the 3.0KVa unit features two removable battery boxes.

    Return to Contents

    What are the hardware installation and configuration requirements?

    Installation of these units must be performed by a qualified HP Customer Engineer(CE).

    NOTE: The customer will be responsible for supplying necessary mains supply and connection of the mains supply to the UPS. The HP CE can do the rest, and will connect the mains input cable from the system into the UPS output port.

    Then if peripherals are also to be protected by this UPS then the standard Power Distribution Unit (PDU) in the rack will be replaced by a specialist UPS PDU (unless the UPS was factory fitted in the rack) and all peripherals can then be connected to this PDU.

    The only other connection is the UPSs serial RS-232 cable to a suitable UPS port or mux port on the host system.

    It is important that either have a large enough single UPS unit to cover your load requirements, or that you purchase more than one UPS unit and split the equipment across the multiple UPS controllers.

    In the event of UPS controller or battery problems - normally signified by the lights on the front panel of the UPS controller. The first level of defense is that the UPS has a power source switch on the rear of the controller that can be in two positions, Normal and Bypass.

    • Normal - Normal UPS operation, mains power runs thru the UPS and is supplied to the host.
    • Bypass - All UPS hardware is bypassed and this is like a standard mains supply.

    Return to Contents

    What are the software installation and configuration requirements?

    The HP PowerTrust software is bundled with HP-UX 10.01 and newer versions, so there are no other software products to purchase, and the engineer or end user has a choice of using SAM or manual methods for configuration of the UPS system.

    Loading the software

    The software is found on the core-OS media bundle as part of the standard OS. The fileset to look in to specify the software to load if it hasn't been loaded is as follows:

    HP-UX 10.01

    Software on 10.01 can be found and loaded using swinstall, again the software is on the core-os media, and is under the CORE-OS fileset and is also called UPS-TOOLS, the loading process will be the same as any other fileset loading operation within swinstall.

    1. Find the fileset and highlight it.
    2. Either press [m] or use the mark for install option from the ACTIONS pull down menu.
    3. Select the INSTALL ANALYSIS option from the ACTIONS pull down menu.

    Configuring the Software

    The software may be configured either using manual commands or by using SAM, either way is permissible and relatively straight forward.

    Configuration through SAM

    • Start SAM
    • Select 'Peripheral devices' option from main menu
    • Select 'Uninterruptable Power Supplies' option from this menu

    You will now be presented with the following configuration screen:

    Global Configuration

    Daemon status:  Active
    Configuration file:   /etc/ups_conf
    Shutdown delay (Minutes):  1
    Shutdown timeout (Minutes):  5


    UPS Type Device File Hardware Path Port Number Shutdown Enabled

    SOLA /dev/tty0p n nn.nn n Yes

    Where n should replaced by the appropriate number for device, hardware path and port number.

    All of the above fields can have their values modified, according to the configuration pertinent to your  system. Having changed the required fields, SAM will ask if you want to restart the /etc/ups_mond monitoring daemon in order for the changes to take effect.


    Manual Configuration Method

    The manual configuration method is as simple if not in some cases easier than using SAM. The above configuration fields can be found in the UPS configuration file /etc/ups_mond.

    Completing the configuration and starting the daemon

    The configuration is made complete by adding the ups_mond entry into /etc/inittab to ensure automatic startup at boot time - this entry is discussed in SECTION 6: CONFIGURATION FILES, so for the moment we need only know that the required ups_mond line must be added to the /etc/inittab file.

    If the ups_mond daemon needs to be started by hand for any reason then we need to issue the following command:

    HP-UX 10.01

    /usr/bin/rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf

    Return to Contents

    What are the HP PowerTrust UPS Commands?


    HP PowerTrust Uninterruptable power supply monitor daemon

    When the daemon detects loss of ac power for a period of time exceeding a configured limit, ups_mond ensures file system integrity by shutting the system down in a graceful manner.

    You can specify the -f option along with a path and filename to specify an alternate configuration file, other than /etc/ups_conf.

    By default ups_mond is locked into memory and is not swappable, although it can be forced to swap if extreme caution is exercised. This caution takes the form of ensuring that all configured swap disks are protected by the UPS hardware so that in the event of a mains power failure, you do not lose the daemon process. Having ensured this the -s option can be specified to allow the daemon to be swapped.

    The process is normally started from /etc/inittab and started by init(1m), when adding the ups_mond entry to /etc/inittab, you must ensure the entry follows the rc inittab entry as you must ensure that syslog is up and running before ups_mond starts.

    ups_mond MUST always be started using rtprio(1) to set real time priority.

    Messages from ups_mond are displayed on the system console and recorded in /var/adm/syslog/syslog.log(10.01)


    power_onoff instructs the UPS monitor (ups_mond(1m)) to shut down the system, and optionally tells it when to power the system back up. The daemon then instructs the UPS hardware when to turn the power on and off. The time to restart the system(power on) is specified with power_onoff(1m) command line arguments.

    The PowerTrust UPS hardware has a maximum limit on the elapsed time between power off and the power on time of 99.9 hours, if you set the options to exceed this value it will default back to 99.9 anyway.



    No power on. This will cause the UPS to switch off and NOT be powered back on. A manual reset of the power WILL be required.


    Can be specified as one, two or four digits to specify time - the following are allowable formats: 0815, 8:15, 8'15, 8h15, 8.15, 8,15


    Can be specified as the day of the week spelt out, or a date as a day month and optional two digit year field. You can also specify the special names 'today' and 'tomorrow'. If no date is specified the command will assume today.


    This parameter can be set after the date and time parameters to specify a further delay minutes, hours or days ahead.

    For fuller details and command line examples review the power_onoff(1m) man page.


    Where are the commands?

    HP-UX 10.01



    Return to Contents

    What are the HP PowerTrust Configuration files?

    There are two configuration files for HP PowerTrust UPS systems, they are /etc/inittab and /etc/ups_conf. This is an overview of the contents of both, and the valid settings.


    ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf (10.01)

    Remember the UPS entry MUST follow the rc entry in /etc/inittab to ensure that syslogd has been started before ups_mond is started.


    shutdown_delay_mins 1
    shutdown_timeout_mins 5
    upstty:/dev/tty0p1 # port 1 (second) on terminal mux 0 for UPS RS-232

    Explanation of the above fields:

    Shutdown_delay_mins:1(Default) (maximum 15 minutes)

    This is the time the system waits to see if mains power will be restored, before issuing a shutdown -h 60 command.

    Shutdown_timeout_mins:5(Default) (maximum 15 minutes)

    This is the length of time in minutes that the UPS will supply power to the system after the shutdown -h 60 process has started.

    WARNING: If this parameters value is set to be too short for your normal shutdown process to complete - UPS will stop power supply output to the system and your shutdown process will crash before completion. It is advised to time a standard shutdown process, in order that one can be reasonably certain of assessing the value for this parameter accurately.

    upstty:/dev/tty0p1 (Default)

    This is the field to be used to specify the port that your UPS serial connection is connected to, and down which it will communicate with the host system.

    Shutdown Parameter Calculations

    HP will only guarantee 15 minutes of battery life on the PowerTrust UPS system. The parameters shutdown_delay_mins and shutdown_timeout_mins MUST add up to no greater than 15 minutes.

    So you can have 5 and 10, 3 and 12, 1 and 14 or 0 and 15 respectively; as long as the two added together DO NOT exceed 15 minutes. If you  try to exceed this 15 minute total limit for the total of both parameters, then ups_mond has the defaults (1 minute and 5 minutes) hard coded into it and it will ignore your values in /etc/ups_conf and revert back to the defaults.

    WARNING:   As shutdown_delay_mins can be set to 15, this would mean that given the 60 second grace period issued as part of the shutdown command; once shutdown_delay_mins has expired, the shutdown will not start for 16 minutes. This together with the fact that the fastest shutdowns will take 5 minutes (best case),  would mean you need 21 minutes of battery life which you might not have. The problem occurs when ups_mond will signal withdrawal of power supply from the UPS at the 15 minute time limit, regardless of battery life.

    Return to Contents

    What should I expect when powerfail occurs, and what should I expect when mains returns?

    First of all lets clarify that in UPS terms there are two types of powerfail event, short and long. Lets discuss the two types and then describe what happens in both cases.


    A short powerfail is quite simply a powerfail event that recovers before the value set for shutdown_delay_mins has expired - i.e. the mains power returns before we issue the shutdown -h 60.


    A long powerfail event would be where mains power has not returned within the time value set for shutdown_delay_mins and we have issued the shutdown -h 60 command and are in the process of shutting down the system.

    Events as they occur - Short powerfail

    1. AC power is lost
    2. UPS notifies its host system
    3. Message written to console and syslog(9.04) or syslog.log(10.x)

    Message on console reads:
    ups_mond: UPS /dev/tty0p1 AC POWER FAILURE - running on UPS battery.
    if power is not returned within previously configured time period,
    your system will automatically go to graceful shutdown.

    ** Mains power returns within shutdown_delay_mins time value: 

    1. Power restored
    2. UPS notifies host system
    3. Write message to console and syslog(9.04) or syslog.log(10.x)

    Message on console reads:
    ups_mond:UPS /dev/tty0p1 OK:AC power back on
    ups_mond:AC power to all recognized system critical UPSs OK system will not shutdown

    Events as they occur - Long powerfail

    1. AC power is lost
    2. UPS notifies its host system
    3. Message written to console and syslog(9.04) or syslog.log(10.x)

      Message on console reads:
      ups_mond: UPS /dev/tty0p1 AC POWER FAILURE - running on UPS battery.
      if power is not returned within previously configured time period,
      your system will automatically go to graceful shutdown.

      ** Mains power has not returned **

    4. shutdown_delay_mins expires - ups_mond is now using shutdown_timeout_mins and will signal UPS hardware to withdraw power in shutdown_timeout_mins 'minutes'.
    5. shutdown -h 60 - command issued
    6. shutdown_timeout_mins expires - UPS turns power off

    If mains power returned after shutdown_delay_mins expired, UPS will NOT come back on line. it will remain in battery backup mode until shutdown_timeout_mins expires and the UPS turns off power. The UPS will stay powered off for a number of seconds and then turn back on.  Once the mains supply is re-established the system itself will regain power and start to boot.

    Return to Contents

    Can I have more than one HP PowerTrust UPS on my system?

      Yes, the configuration remains exactly the same, there will still only be one entry for ups_mond in /etc/inittab, but:

      1. The extra UPSs must be plugged into a tty port.
      2. That tty reference must be added into an 'upstty' statement on a separate line in /etc/ups_conf.
      3. And ups_mond restarted to pick up the new entries.

    Return to Contents

    My syslog file is filling up very rapidly with ups_mond messages, what is happening?

      In this case a quick look in /etc/ups_conf to make a note of the tty ports being used, and then a comparison done against the tty ports set to respawn in /etc/inittab, should reveal that you have a getty respawning on the same port as the UPS connection is configured for.

      In /etc/inittab either set the rogue getty entries to off or remove them completely, save the inittab file and from a ux command prompt type 'init q' to re-read the new inittab file - this should resolve the problem.

    Return to Contents

    I have a SITE UPS can or should HP PowerTrust be connected to it?

    NO, PowerTrust requires sinisoidal input. Output from a site UPS is often clipped, which can cause PowerTrust to exhibit erratic behavior - such as rogue power failures and complete shutdowns.

    Return to Contents

    How do I use Kermit to clear the UPS ?

    If you are having a problem where you are getting the following error message from ups_mond to the console, its cause is likely to be that the UPS is set to the wrong baud rate.

    UPS /dev/tty2p1 Read Failed: File Exists: Uninterruptable Power Supply has not been connected correctly: Loss of power will not be detectable

    The UPS should be set to 1200 baud. The UPS box can get into a bad state  The result is that the UPS is trying to communicate at the wrong baud rate or is not set up with any baud rate. To clear the UPS, do the following:

    1. Make sure the ups_mond program is not running.
      1. Type ps -ef|grep UPS to see if it is.  If it is still running, copy the inittab file:  cp /etc/inittab /etc/inittab.backup 
    1. Then edit the /etc/inittab file and look for a line like:
      ups1::respawn:rtprio 0 /etc/ups_mond -f /etc/ups_conf
    1. Insert a # in front of line so it looks like
      #ups1::respawn:rtprio 0 /etc/ups_mond -f /etc/ups_conf
    1. Save your changes. Then type: init q
    1. Verify with ps -ef|grep ups that the /etc/ups_mond program is not running.
    1. Look in /etc/ups_conf and check for port that this program uses. It is most likely /dev/tty0p1. Use this port for all subsequent commands where the word PORTNAME is shown.
    1. Type kermit
      Prompt will be 
    1. A the C-Kermit> prompt type the following:
      set line PORTNAME <-----Remember to use name from above
      set speed 1200

      <-- no prompt. You type a carriage return If you get a ?? from ups, it is working fine and you just need to exit kermit - Skip to step 8.
    1. If no ??, type [CTRL\C] <---- That is simultaneous CTRL and \ keys followed by a C. you will then get kermit prompt.  At the C-Kermit> prompt Type:
      set speed 9600
        <-- no prompt. You type a carriage return. 
    1. If no ??, try 2400 or 4800 baud. If none of the different baud rates work, the problem is possibly a bad or wrong cable, device file or mux board problem, bad UPS, or some other process is using the port. Go to step 8 to exit kermit. This procedure will not work.
    1. When you get the ??, type [N] <-----------NO Carriage return. You will see NM
      [CTRL\C] <---- That is simultaneous CTRL and \ keys followed by a C. you will then get kermit prompt.
      C-Kermit>set speed 1200
      <-- no prompt. You type a carriage return
      You should now see ?? You might see "CM" instead. If so, hit
      [ENTER]and you should now get ??
    1. Type [CTRL\C] <---- That is simultaneous CTRL and \ keys followed by a C. you will then get kermit prompt.
      <------------- shell prompt. May be #.
    1. Copy the original inittab file back by typing cp /etc/inittab.backup /etc/inittab
      init q
        Verify that the
      ups_mond program is running.

    Return to Contents

    What do the front panel display codes mean?

    This page lists PDC Chassis Codes and Error Codes displayed on the system console and on the front panel LCD display located on the SPU cabinet for models Kxxx.  Each code consists of four hex digits: D0, D1, D2, D3.  "D0" is the Major Code category.

    Return to Contents

    Major Code 0: (not used)

    Return to Contents

    Major Code 1: Interrupts



    Where x=Processor Memory bus slot number
    *Should not happen in PDC code.

    FLT 1x01 HPMC
    FLT 1x02 *PowerFail Interrupt (UNUSED)
    FLT 1x03 *Recovery counter trap
    FLT 1x04 External interrupt
    FLT 1x05 LPMC
    FLT 1x06 *ITLB page fault
    FLT 1x07 *Instruction memory protection trap
    FLT 1x08 Illegal instruction trap
    FLT 1x09 Break instruction trap
    FLT 1x0A *Privileged instruction trap
    FLT 1x0B *Privileged register trap
    FLT 1x0C *Overflow trap
    FLT 1x0D *Conditional trap
    FLT 1x0E Assist exception trap
    FLT 1x0F *DTLB miss/page fault
    FLT 1x10 *Non-access ITLB fault
    FLT 1x11 *Non-access DTLB/page fault
    FLT 1x12 *Data memory protection trap or unaligned data reference trap
    FLT 1x13 *Data memory break trap
    FLT 1x14 *TLB dirty bit trap
    FLT 1x15 *Page reference trap
    FLT 1x16 *Assist emulation trap
    FLT 1x17 *Higher-privilege transfer trap
    FLT 1x18 *Lower-privilege transfer trap
    FLT 1x19 *Taken branch trap
    FLT 1x1A Data memory access rights trap
    FLT 1x1B Data memory protection ID trap
    FLT 1x1C Unaligned data reference trap

    Return to Contents

    Major Code 1: Selftests and Diagnostics (CPU/TLB)



    Where x = CPU number

    TEST 1x30 Starting early selftest
    WARN 1x31 Early selftest skipped
    FLT 1x32 Bad CPU test mode
    INIT 1x3C Initialize the CPU
    TEST 1x3E Exiting early selftest
    FLT 1x3F Cache load fault
    TEST 1x40 Starting CPU basic selftest
    FLT 1x40 - 1x48 CPU basic selftest failure
    TEST 1x49 Starting CPU ALU selftest
    FLT 1x49 - 1x50 CPU ALU selftest failure
    TEST 1x51 Starting CPU branch selftest
    FLT 1x51 - 1x58 CPU branch selftest failure
    TEST 1x59 Starting CPU side effect selftest
    FLT 1x59 - 1x5A CPU side effect selftest failure
    WARN 1x61 Starting CPU carry/borrow selftest
    FLT 1x61 - 1x66 CPU carry/borrow selftest fault
    TEST 1x67 Starting CPU arithmetic condition selftest
    FLT 1x67 - 1x75 CPU arithmetic condition selftest fault
    TEST 1x76 Starting CPU bit operation selftest
    FLT 1x76 - 1x77 CPU bit operation selftest fault
    TEST 1x78 CPU SAR selftest
    FLT 1x78 - 1x79 CPU SAR selftest fault
    TEST 1x7A Starting CPU extract/deposit selftest
    FLT 1x7A - 1x80 CPU extract/deposit selftest fault
    TEST 1x81 Starting CPU branch on bit selftest
    FLT 1x81 - 1x83 CPU branch on bit selftest fault
    TEST 1x84 Starting CPU control register selftest
    FLT 1x84 - 1x89 CPU control register selftest fault
    TEST 1x8B Starting CPU external interrupt selftest
    FLT 1x8B - 1x8D CPU external interrupt selftest fault
    TEST 1x8E Starting CPU interval time selftest
    FLT 1x8E - 1x93 CPU interval time selftest fault
    TEST 1x94 Starting CPU shadow register selftest
    FLT 1x94 - 1x97 CPU shadow register selftest fault
    TEST 1x98 Starting CPU diagnostics register selftest
    FLT 1x98 - 1x99 CPU diagnostics register fault
    TEST 1xA0 Starting Coprocessor selftest
    TEST 1xA1 Starting Coprocessor Register selftest
    FLT 1xA1 Coprocessor register fault
    TEST 1xA2 Starting Coprocessor instruction selftest
    FLT 1xA2 Coprocessor instruction fault
    TEST 1xA3 Starting Coprocessor traps selftest
    FLT 1xA3 Coprocessor traps fault
    TEST 1xA4 Starting Coprocessor misc selftest
    FLT 1xA4 Coprocessor misc fault
    WARN 1xAF FPUs disabled warning
    TEST 1xB0 TLB initialization test
    FLT 1xB0 TLB initialization fault

    Return to Contents

    Major Code 1: Boot Errors (Forward Progress)



    (Where x = CPU number)

    FLT 1xBA Bad Monarch CPU
    FLT 1xBC Bad CPU clock speed detected.
    FLT 1xBD CPUs not installed in sequential order.
    FLT 1xBF Slave CPU halted due to catastrophic boot failure
    INIT 1xCA Initializing runway CPU arbitration
    FLT 1xCB Mismatched CPU revisions
    FLT 1xCC Mismatched cache sizes
    WARN 1xCD CPU was deconfigured
    FLT 1xCE CPU was sContentsped via PDC_PROC call
    FLT 1xCF Slave halted itself when selftest status <0
    WARN 1xDy Monarch (x) deconfigured slave (y)
    FLT 1xDF Monarch failed dual-issue test
    WARN 1xEF Selftest returned a warning
    WARN 1xFy Monarch (x) sContentsped a non-responding slave (y)
    INIT 1xFC Synchronizing CPUs
    FLT 1xFF Monarch Selftest returned a failure

    Return to Contents

    Major Code 2: Cache (Selftests and Diagnostics) Codes



    Description (Where x = CPU number)

    TEST 2x00 Starting instruction cache address line selftest
    FLT 2x01 - 2x03 Instruction cache address line fault
    TEST 2x10 Starting instruction cache data line selftest
    FLT 2x11 - 2x12 Instruction cache data line fault
    TEST 2x20 Starting instruction cache RAM selftest
    FLT 2x21 - 2x23 Instruction cache RAM fault
    TEST 2x30 Starting instruction cache tag selftest
    FLT 2x31 - 2x33 Instruction cache tag fault
    TEST 2040 Starting cache ierr selftest
    FLT 2x41-2x43 Cache ierr fault
    TEST 2x50 Starting data cache address line selftest
    FLT 2x51 - 2x53 Data cache address line fault
    TEST 2x60 Starting data cache data line selftest
    FLT 2x61 - 2x62 Data cache data line fault
    TEST 2x70 Starting data cache RAM selftest
    FLT 2x71 - 2x73 Data cache RAM fault
    TEST 2x80 Starting data cache tag selftest
    FLT 2x81 - 2x83 Data cache tag fault
    TEST 2x90 Starting Cache derr selftest
    FLT 2x91-2x93 Cache derr fault
    TEST 2xA0 Starting PM cache selftest
    FLT 2xA0 PM cache selftest fault
    TEST 2xA1 Starting PM cache RAM selftest
    FLT 2xA1-2xA2 PM cache RAM selftest fault
    TEST 2xA3 Starting PM cache pointer selftest
    FLT 2xA3-2xA6 PM pointer selftest failure
    TEST 2xA7 Starting PM cache CAM selftest
    FLT 2xA7-2xA8 PM CAM selftest failure

    The following codes are used by HPMC processing.
    In PIM logs, the second digit will always be 0 (i.e. 20B0), but on the Hex Display or AP, they will log the CPU number as the second digit (i.e. 22B0 for proc 2).

    FLT 20B0 DCache parity error
    FLT 20B1 DCache parity error in tag
    FLT 20B2 DCache parity error in word 0
    FLT 20B3 DCache parity error in word 1
    FLT 20C0 Icache parity error
    FLT 20C1 Icache tag parity error
    FLT 20C2 Icache word0 parity error
    FLT 20C3 Icache word1 parity error

    Return to Contents

    Major Code 3: Processor Dependent Hardware (PDH) Codes



    Description (Where x = Processor Memory bus slot number)

    TEST 3x00 Start checksuming the FEPROM
    FLT 3x00 FEPROM checksum failure
    INIT 3x00 FEPROM checksum correct
    TEST 3x01 Testing PDH control register
    INIT 3x01 Initialize the PDH control register
    FLT 3x01 PDH control register failure
    TEST 3x02 Scratch RAM under test
    INIT 3x02 Scratch RAM successfully initialized
    FLT 3x02 Fatal fault in scratch RAM
    WARN 3x03 Error reading stable storage, contents are invalid
    FLT 3x03 Fault reading stable storage and no console present
    WARN 3x04 Error writing to the EEPROM
    FLT 3x04 Fatal fault writing to the EEPROM
    FLT 3x05 Write limit exceeded
    WARN 3x06 Error reading EEPROM
    FLT 3x06 Fatal fault reading EEPROM
    INIT 3x07 Entering LDB
    FLT 3x08 Invalid system board byte
    FLT 3x09 Invalid system mode byte
    FLT 3x0A Invalid system MFG test byte
    WARN 3x1A System Hversion in stable storage does not match the hardware
    INIT 30C4 Clearing and revalidating EEPROM
    FLT 30F4 Number of boots exceeded 95,000

    Return to Contents

    Major Code 4: Late Selftests



    Description (Where x = CPU number)

    TEST 4x00 Starting late selftest
    WARN 4x01 Skipping late selftest
    TEST 4x0E Exiting late selftest
    TEST 4010 Starting PM cache byte selftest
    FLT 4x10 PM cache byte selftest fault
    TEST 4x20 Starting data cache byte selftest
    FLT 4x20 - 4x27 Data cache byte selftest fault
    TEST 4x30 Starting PM cache flush selftest
    FLT 4x30 PM cache flush selftest fault
    TEST 4x40 Starting data cache flush selftest
    FLT 4x40 - 4x47 Data cache flush selftest fault
    TEST 4x50 Starting Instruction cache miss selftest
    FLT 4x51 Instruction cache miss selftest fault
    TEST 4x60 Starting Data cache miss selftest
    WARN 4x60 Data cache miss selftest warning
    FLT 4x60 - 4x66 Data cache miss selftest fault
    TEST 4x70 Starting dual issue selftest
    FLT 4x71 Dual issue selftest fault

    Return to Contents

    Major Code 5: Bus Transactions



    Description (Where x = slot number and y = bus number)

    FLT 5xy0 Unknown bus fault
    FLT 5xy1 I/O module internal fault
    FLT 5xy2 Assertion of path fault detected
    FLT 5xy3 Mode phase fault
    FLT 5xy4 Data parity fault
    FLT 5xy5 Bus protocol fault
    FLT 5xy6 Failure to assert path slave ACK
    FLT 5xy7 Processor Memory bus directed fault
    FLT 5xy8 Processor Memory bus broad fault
    FLT 5xy9 Improper access fault
    FLT 5xyA Illegal response
    FLT 5xyB Bus time-out
    FLT 5xyD HSC module failed to release the bus (one of the HSC guests hung the HSC bus and failed to get off the bus, even when the I/O Adapter asserted error L)
    FLT 5xyE HP-PB to GSC bus adapter TOC error
    FLT 5xyF TLB fault in the I/O adapter or invalid PDIR entry

    Return to Contents

    Major Code 6: Reserved (not used)

    Return to Contents

    Major Code 7: Memory Subsystem Codes




    FLT 7000 HPMC in the memory system
    FLT 7001 Icache parity fault in memory test
    FLT 7002 DCache parity fault in memory test
    FLT 7003 MSI read time-out (usually caused by reading beyond the end of memory)
    FLT 7004 MSI write time-out (usually caused by writing beyond the end of memory)
    FLT 7005 Processor/Memory bus parity fault
    FLT 7006 Write bomb fault (Processor/Memory bus parity detected on incoming data)
    FLT 7007 Memory address ECC fault (Suspect memory carrier or controller first - probably not SIMMs)
    FLT 7008 Multi-bit memory fault
    FLT 7009 Single bit memory fault
    FLT 70FF Unknown HPMC
    FLT 7FFF Catastrophic memory fault
    FLT 7101 Master Memory Controller not responding
    FLT 7102 Master Memory Controller not ready fault
    FLT 7103 Master Memory Controller failed to clear
    FLT 7104 Master Memory Controller sticky bits
    FLT 7105 Master Memory Controller bad revision
    FLT 7106 Master Memory Controller register selftest fault
    FLT 7107 Master Memory Controller fault in ECC test
    FLT 7200 No Slave Memory Controller available
    FLT 721x Slave Memory Controller failed
    FLT 722x Bad Slave Memory Controller revision
    FLT 723x Slave Memory Controller failed to respond
    FLT 7301 SIMM 0 bytes are not equal
    FLT 7302 SIMM 1 bytes are not equal
    FLT 7303 SIMM 0 data and SIMM 1 data have a mismatch error
    FLT 7304 Unknown sizing compare fault
    FLT 7305 Multi-bit error occurred during sizing
    FLT 7306 Address test failed on memory bank
    FLT 7307 ECC test failed on memory bank
    FLT 7308 Single bit memory error caused HPMC
    FLT 7401 No memory SIMMs installed
    FLT 7402 Both EDO and STD memory SIMMs installed
    FLT 7403 Address did not map to bank
    FLT 7404 Address did not map to Group Configuration Table
    FLT 7405 Dual issue test failed
    FLT 7500 No RAM found
    FLT 7501 Not enough good memory to run Operating System
    FLT 7502 Not enough good memory to run Boot Console Handler
    FLT 7604 No bits set in memory test status
    WARN 7701 Using alternate memory configuration
    WARN 7702 Memory not tested, initialized only
    WARN 7703 SIMM loading warning
    WARN 7704 RAM bus warning
    WARN 7705 Good memory required to run Operating System is greater than memory size
    WARN 770F Rev 1 Slave Memory Controller search routine being used
    WARN 7800 PDT disabled warning
    FLT 7800 PDT disabled halt
    WARN 7801 Overwrite single bit error with multi-bit error in Page Deallocation Table
    WARN 7802 Duplicate Page Deallocation Table entry
    WARN 7803 EEPROM fault while updating Page Deallocation Table
    WARN 7804 Page Deallocation Table is full
    FLT 7D03 MSI read time-out (HPMC, caused by accessing beyond the end of memory or non-responding Slave Memory Controllers)
    FLT 7D04 MSI write time-out (HPMC, caused by accessing beyond the end of memory or non-responding Slave Memory Controllers)
    FLT 7D05 Processor Memory bus parity fault (HPMC)
    FLT 7D06 Write bomb fault (HPMC, earlier write transaction to memory had a bus parity error)
    FLT 7D07 Memory address fault (HPMC)
    FLT 7D08 Multi-bit memory fault (HPMC)
    FLT 7D09 Single bit memory fault (HPMC)
    FLT 7D0A Address did not map to bank (HPMC)
    FLT 7Fxy x = memory carrier card number, y = SIMM pair number

    Return to Contents

    Major Code 8: I/O Device Fault Codes for K100/K200/K400




    On the following 3 IOA tests; x=0 means IOA 0; x=1 means IOA 1

    FLT 8x00 Error in IOA RAM Test
    FLT 8x01 Error in IOA TLB Test
    FLT 8x02 Error in IOA DMA Test
    WARN 80F3 PDC IODC failed to retrieve header information
    WARN 80F4 PDC IODC failed to return Entry Init
    WARN 80F5 Error executing Entry Init
    WARN 80F6 PDC IODC failed to return Entry I/O
    WARN 80F7 Error executing Entry IO
    WARN 80F8 Invalid device class, must be sequential, random, or tftp
    WARN 80F9 PDC IODC failed to return Entry Test
    WARN 80FA Error executing Entry Test
    WARN 80FC Invalid device (internal PDC structure error)
    FLT 802B I/O bus overlap (usually due to graphics configuration violation)
    FLT 803D To many graphics responding to the same address
    WARN 8FFF Late I/O selftest warning
    FLT 8FFF Late I/O selftest failure.
    x = GBOA Slot number; y=GSC+ bus number
    TEST 8xy0 Begin HP-PB to GSC Bus adapter (GBOA) register tests
    FLT 8xy1-8xy4 Failures of HP-PB to GSC Bus adapter(GBOA) register tests
    TEST 8xy5 Begin HP-PB to GSC Bus adapter (GBOA) DMA tests
    FLT 8xy6-8xyB Failures of HP-PB to GSC Bus adapter (GBOA) DMA tests
    INIT 8300 Begin MFIOC (LASI) tests
    FLT 8301 Failed LASI LAN test
    FLT 8303/8305 Failed other LASI tests

    Return to Contents

    Major Code 9: Console Initialization Errors




    WARN 9000 Stable storage console not found
    WARN 9001 Alternate console(s) not found

    Return to Contents

    Major Code A: Boot Device Initialization Errors




    FLT A088 No console found, unable to boot
    WARN A008 No bootable device found
    WARN A50F Initialize primary path failed boot
    WARN A70F Initialize other boot path failed
    WARN A00F Retrieve path failed
    WARN A0BD Entry Initialization returned a -8, device not ready
    FLT A0FF Unknown launch fault (control returned from IPL)

    Return to Contents

    Major Code B: HP-UX System Panic Codes



    B000 Kernel panic
    B009 Panic dump completed (disks not fully synchronized)
    B00A Panic dump completed (disks fully synchronized)

    Return to Contents

    Major Code C: System Initialization Codes




    INIT C10x Starting the monarch processor selection, where x = CPU number
    INIT C200 Starting memory configuration
    INIT C201 Starting the destructive memory initialization
    INIT C202 Starting the non-destructive memory initialization
    INIT C20F RAM configuration forward progress indicator
    TEST C210 Memory hard reset
    TEST C220 Physical configuring memory
    TEST C230 Sizing memory banks
    TEST C240 Loading memory configuration from EEPROM
    TEST C250 Configuring memory interleave
    TEST C260 Testing memory interleave
    TEST C261 Testing first page of memory
    TEST C262 Testing dual issue
    TEST C263 Testing memory, write test
    TEST C264 Testing memory, read/write test
    TEST C265 Testing memory, read test
    TEST C270 Updating memory configuration
    TEST C280 Configure to EEPROM
    TEST C2E0 Memory testing done
    TEST C2A0 Flat configuration test
    TEST C2B0 Flat RAM test
    TEST C2C1 Memory soft reset
    TEST C2C2 A non destructive RAM test
    INIT C300 Monarch is executing extended selftests
    INIT C30C Monarch slave check, making sure slaves responded
    TEST C3EE Internal slave test complete
    TEST C3FF Late monarch I/O test OK
    INIT C400 Retrieving the stable storage console path
    INIT C40A Retrieving special console path
    INIT C440 Initializing the stable storage console path
    INIT C44A Initializing special console path
    INIT C4CC Initialize close console
    INIT C4CD Close console not found
    INIT C4CF Found the close console
    INIT C500 Retrieving the primary boot path from stable storage
    INIT C540 Initialize primary path
    INIT C550 Execute entry test for primary boot path
    INIT C580 Load IPL primary path
    WARN C5F0 Primary IPL warning
    FLT C5F0 Primary IPL fault and no console found
    WARN C5F1 LIF file address is nor 2K bytes aligned or it is zero
    WARN C5F2 LIF not present on media
    WARN C5F3 LIF file is not a multiple of 2K bytes, is zero, or is greater than 256K bytes
    WARN C5F4 LIF file entry point is not word aligned or is greater than or equal to the size
    WARN C5F8 The arithmetic sum of the words in IPL mismatch 0
    INIT C5FF Branching to IPL on primary boot device
    INIT C600 Retrieving default console path
    INIT C601 Retrieving graphics console path
    INIT C602 Retrieving keyboard console path
    INIT C640 Initializing default console path
    INIT C641 Initializing graphics console path
    INIT C642 Initializing keyboard console path
    INIT C700 Get manufacturing defaults
    INIT C740 Initialize a non-primary boot path
    INIT C750 Execute entry test for a non-primary boot path
    INIT C780 Loading IPL from a non-primary boot path
    INIT C7F0 An error occurred reading IPL
    INIT C7F1 LIF file address is not 2K byte aligned or it is zero
    INIT C7F2 LIF file not present on media
    INIT C7F3 LIF file is not a multiple of 2K bytes, is zero, or is greater than 256K bytes
    INIT C7F4 LIF file entry point is not word aligned or is greater than or equal to the size
    INIT C7F8 The arithmetic sum of the words in IPL mismatch 0
    INIT C7FF Branching to IPL from a non-primary boot device
    INIT CB00 Transfer of Control (TOC) initiated by the firmware
    WARN CB01 No Operating System TOC vector found
    WARN CB02 Invalid OS TOC vector
    WARN CB03 Invalid OS TOC code
    WARN CB04 Invalid OS TOC code length
    WARN CB05 Invalid checksum for OS TOC code
    WARN CB09 Seed error TOC entered
    WARN CB0A Previous TOC PIM logged, current TOC PIM data is lost
    INIT CB0B Branching to OS TOC handler
    INIT CB0C Branch to OS TOC failed
    FLT CB10 TOC_IN_PROGRESS (Displayed by OS_TOC, not PDC)
    INIT CB1B Branching to OS_LPMC handler
    WARN CB15 Central bus LPMC error
    WARN CB19 Seed Error LPMC entered
    INIT CB1F Branching to OS LPMC returned
    FLT CB99 PDC_SEED_ERROR IVA table, HPMC handler entered
    FLT CB9A HPMC PIM overwritten
    FLT CBF0 HPMC handling initiated
    FLT CBF1 OS did not replace PDC IVA
    FLT CBF2 Invalid length for OS HPMC code
    FLT CBF3 Invalid address for OS HPMC code
    FLT CBF4 Invalid checksum for OS HPMC code
    FLT CBF5 IVA + 32 was equal to zero
    INIT CBF7 PDC_IO initialization started
    INIT CBF8 PDC_IO initialization completed
    WARN CBF9 PDCE_HPMC or PDC_IO found unconfigured IOA or bus converter
    WARN CBFA Previous HPMC PIM logged, current HPMC can not be logged
    FLT CBFB Branching to the OS HPMC handler
    FLT CBFC Branch to OS HPMC failed
    FLT CBFE HPMC interrupted a TOC
    FLT CBFF Nested HPMC occurred
    INIT CC0x Operating System rendezvous, Where x = CPU
    INIT CC1x Early CPU rendezvous, Where x = CPU
    INIT CC2x CPU rendezvous, Where x = CPU
    INIT CC3x Cache CPU rendezvous, Where x = CPU
    INIT CC4x Memory CPU rendezvous, Where x = CPU
    FLT CCF0 CPU slave fault
    TEST CD00 I/O Adapter test
    INIT CD08 Initialize I/O Adapter 0
    INIT CD0A Initialize I/O Adapter 1
    FLT CD0A IOA 1 did not respond
    INIT CD0F Initialize MMC
    INIT CDEA Initialization of EISA
    INIT CDEB Checking for EIAS cards in slots
    WARN CDEC No Configuration Data for card in this slot.
    WARN CDED ID from card <> IO in EEPROM config data.
    FLT CDEF No EISA Found
    INIT CDFx Starting initialization of EISA card in slot x.
    INIT CDE0 EISA Initialization complete

    The following may apply to all system types

    INIT CDxy Indicates system found a device and is resetting it; x = bus and y = slot
    FLT CDxy Indicates system found a device error; x = bus and y = slot
    INIT CDxC Initialize Graphics; x = HSC bus number
    INIT CDxD (init hyperdrive) x = GSC+ bus number (graphics hyperdrive/dodger)
    INIT CDxF (init lasi) x = GSC+ bus number
    INIT CDFF Building the system map table

    Return to Contents

    Major Code C: HP-UX ISL Boot Codes



    CEC0 HP-UX boot has been loaded and initialization begun
    CED0 HP-UX boot has entered main
    CED2 HP-UX boot is about to configure the I/O system
    CED4 HP-UX boot is about to mount the root file system
    CEDA HP-UX boot is about to list the contents of a directory
    CEDB HP-UX boot is about to load the kernel into memory
    CEDC HP-UX boot is about to start a copy operation
    CEDD HP-UX boot is about to sContents (return to Remote Data Base)
    CEDE HP-UX boot is about to return to ISL
    CEDF HP-UX boot is about to launch the kernel

    Return to Contents

    Major Code C: HP-UX System Initialization Codes



    CEE0 Kernel was loaded and initialization has begun
    CEF0 Kernel has entered main
    CEF2 Kernel is about to configure the I/O system
    CEF4 Kernel is about to mount the root file system
    CEF6 Kernel is about to set up the page-out demon
    CEF8 Kernel is about to start the initialization process

    Return to Contents

    Major Code D: HP-UX System Shutdown Codes (OS)



    D000 Shutdown begun, boot () has been entered
    D004 Transfer of Control (TOC) core dump begun
    D010 High priority machine check (HPMC) core dump begun
    D400 Shutdown in progress, returned from update (), about to wait for buffers to be flushed
    D600 Shutdown in progress, busy-wait after update () has completed
    D900 Shutdown completed, disks not fully synchronized
    D904 TOC dump completed, disks not synchronized)
    D910 HPMC completed, disks not synchronized
    DA00 Shutdown completed, disks fully synchronized

    Return to Contents

    Major Code E: (not used) Warning Codes (OS)

    Return to Contents

    Major Code F: HP-UX Run Codes (OS)



    FxnF (HP-UX) Indicates the system is running. An F in the first and fourth digits indicates the system is running normally.
    The x is updated every five seconds with the length of the run queue at that time (an instantaneous reading not an average). It indicates the number of processes. Loads higher than nine display as A.
    The n indicates the number of processors (1 or 2).

    Return to Contents

    What is an HPMC, and how do you access this information?

    An HPMC error condition means that a high priority machine check has occured. An HPMC is an abnormal condition which has compromised the integrity of system processing. A CPU detects the hpmc and halts the system.

    The HPMC information is stored in a non-volatile memory location. To access the HPMC information, first reset the system, either by your normal system shutdown/reset procedure, or from the system console:

    NOTE:  If the operating system is running, you need to shut it down properly first.

    After the system reset, interrupt the autoboot process if it is enabled:

    After the interrupt, from the menu presented, go to the service menu, enter the 'pim' command.

    Record the pim report information, specifically:

    NOTE: If you have more than one processor in the system, you need to gather this information for each processor.

    This pim report information will be helpful to the HP Response Center, in determining the cause of the HPMC

    Return to Contents