The AIX® diagnostic package contains programs called tasks and service aids. Tasks and service aids are used to have the AIX diagnostics perform specific functions on resources contained in a system.
To perform one of these tasks, use the Task Selection option from the FUNCTION SELECTION menu.
After a task is selected, a resource menu might be displayed showing all resources supported by the task.
To run these tasks directly from the command line, specify the resource and other task-unique flags. Use the descriptions in this topic to understand which flags are needed for a given task.
The following tasks are described in this topic:
Use this task to add resources back to the resource list.
This service aid allows access to the AIX command line. To use this service aid, the user must know the root password (when a root password has been established).
The PCI RAID adapter has an internal log that logs information about the adapter and the disk drives attached to the adapter. Whenever data is logged in the internal log, the device driver copies the entries to the AIX system error log and clears the internal log.
The analyze adapter internal log service aid analyzes these entries in the AIX system error log. The service aid displays the errors and the associated service actions. Entries that do not require any service actions are ignored.
When running this service aid, a menu is presented to enter the start time, the end time, and the file name. The start time and end time have the following format: [mmddHHMMyy]. (where mm is the month (1-12), dd is the date (1-31) HH is the hour (00-23) MM is the minute (00-59), and yy is the last two digits of the year (00-99). The file name is the location where the user wants to store the output data.
To invoke the service aid task from the command line, type:
diag -c -d devicename -T "adapela [-s start date -e end date]
This service aid allows verification of backup media and devices. It presents a menu of tape and diskette devices available for testing and prompts for selecting the desired device. It then presents a menu of available backup formats and prompts for selecting the desired format. The supported formats are tar, backup, and cpio. After the device and format are selected, the service aid backs up a known file to the selected device, restores that file to /tmp, and compares the original file to the restored file. The restored file remains in /tmp to allow for visual comparison. All errors are reported.
Normally, run Certify if after running diagnostics on a drive and its media, no problem is found, but you suspect that a problem still exists.
Hard files can be connected either to a SCSI adapter (non-RAID) or a PCI SCSI RAID adapter. The usage and criteria for a hard file connected to a non-RAID SCSI adapter are different from those for a hard file connected to a PCI SCSI RAID adapter.
This selection enables you to verify the data written on a diskette. When you select this service aid, a menu asks you to select the type of diskette being verified. The program then reads all of the ID and data fields on the diskette one time and displays the total number of bad sectors found.
This selection reads all of the ID and data fields. It checks for bad data and counts all errors encountered. If an unrecovered data errors occurs, the data on the media should be transferred to another media and the original media should be discarded. If an unrecovered equipment error occurs or recovered errors exceed the threshold value, the original media should be discarded.
If the drive is reset during a certify operation, the operation is restarted.
If the drive is reset again, the certify operation is terminated, and you are asked to run diagnostics on the drive.
For pdisks and hdisks, this selection reads all of the ID and data fields on the hard file. If bad-data errors are encountered, the certify operation counts the errors.
If the non-recovered data errors, recovered data errors, recovered and non-recovered equipment errors exceed the threshold values, the hard file must be replaced.
After the read certify of the disk surface completes for hdisk hard files, the certify operation performs 2000 random-seek operations. Errors are also counted during the random-seek operations. If a disk timeout occurs before the random seeks are finished, the disk needs to be replaced.
This selection is used to certify physical disks attached to a PCI SCSI RAID adapter. Certify reads the entire disk and checks for recovered errors, unrecovered errors, and reassigned errors. If these errors exceed the threshold values, you are prompted to replace the physical disk.
Use this service aid to display the display/alter VPD selection menu. The menu lists all resources installed on the system. When a resource is selected, a menu displays that lists all the VPD for that resource.
This service aid provides a tool for configuring and removing dials and LPF keys to the asynchronous system ports.
This selection invokes the SMIT utility to allow dials and LPF keys configuration. A TTY must be in the available state on the async port before the dials and LPF keys can be configured on the port. The task allows an async adapter to be configured, then a TTY port defined on the adapter. Dials and LPF keys can then be defined on the port.
Before configuring dials or LPF keys on a system port, you must remove all defined TTYs. To determine if there are any defined TTYs, select List All Defined TTYs. After all defined TTYs have been removed, then add a new TTY and configure the dials or LPF keys.
This service aid controls how the system tries to recover when power is restored after a power outage.
Use this service aid to display and change the following settings for the reboot policy.
When enabled, "Platform auto power restart" allows the platform firmware to restart a system after power is restored following a power outage. If the system is partitioned, each partition that was running when the power outage occurred will be restarted as indicated by that partition's setting of the system management (SMIT) option: "Automatically reboot operating system after a crash".
/usr/lpp/diagnostics/bin/uspchrp -b
/usr/lpp/diagnostics/bin/uspchrp -q platform-auto-power-restart
/usr/lpp/diagnostics/bin/uspchrp -e platform-auto-power-restart=[0|1]where:
1 = Enable Platform Automatic Power Restart
0 = Disables Platform Automatic Power Restart
The Platform Boot Speed system parameter can be read or set from the command line only. To read the Platform Boot Speed system parameter, use the command: /usr/lpp/diagnostics/bin/uspchrp -q PlatformBootSpeed
To set the Platform Boot Speed system parameter, use the command: /usr/lpp/diagnostics/bin/uspchrp -e PlatformBootSpeed=[fast|slow].
With a fast platform speed, the platform firmware will perform a minimal set of hardware tests before loading the operating system. With a slow platform speed, the platform firmware will perform a comprehensive set of hardware tests before loading the operating system.
/usr/lpp/diagnostics/bin/uspchrp -q <variable name> | -e <variable name>=value
The return codes are:
0 = command successful
1 = command not successful
The "periodic" setting cannot be set using this service aid, although it can be read. The HMC is used to set the periodic setting.
The "Configure platform processor diagnostics" is accessed using the diag command, then selecting the appropriate topic from the diagnostics task menus.
/usr/lpp/diagnostics/bin/uspchrp -p
/usr/lpp/diagnostics/bin/uspchrp -q PlatformProcessorDiagnostics
/usr/lpp/diagnostics/bin/uspchrp -e PlatformProcessorDiagnostics=[disabled|staggered|immediate]
Configure scan dump policy allows the user to set or view the scan dump policy (scan dump control and size) in NVRAM. Scan dump data is a set of chip data that the service processor gathers after a system malfunction. It consists of chip scan rings, chip trace arrays, and scan COM (SCOM) registers. This data is stored in the scan-log partition of the system's nonvolatile random access memory (NVRAM).
/usr/lpp/diagnostics/bin/uspchrp -d
This selection allows you to recover data from an old drive when replacing it with a new drive. The service aid recovers all logical volume manager (LVM) software-reassigned blocks. To prevent corrupted data from being copied to the new drive, the service aid stops if an unrecoverable read error is detected. To help prevent possible problems with the new drive, the service aid stops if the number of bad blocks being reassigned reaches a threshold.
To prevent problems that can occur when running this service aid from disk, it is suggested that this service aid be run, when possible, from the diagnostics that are loaded from removable media.
This selection allows the user to display and alter information on a disk sector. Sectors are addressed by their decimal sector number. Data is displayed both in hex and in ASCII. To prevent corrupted data from being incorrectly corrected, the service aid does not display information that cannot be read correctly.
If a device is not included in the test list or if you think a diagnostic package for a device is not loaded, check by using the display configuration and resource list task. If the device you want to test has a plus (+) sign or a minus (-) sign preceding its name, the diagnostic package is loaded. If the device has an asterisk (*) preceding its name, the diagnostic package for the device is not loaded or is not available.
This service aid displays the item header only for all installed resources. Use this service aid when there is no need to see the vital product data (VPD). (No VPD is displayed.)
This task displays the firmware device node information. This service aid is intended to gather more information about individual or particular devices on the system. The format of the output data may differ depending on which level of the AIX operating system is installed.
This service aid uses the errpt command to view the hardware error log.
The display error summary and display error detail selections provide the same type of report as the errpt command. The display error analysis summary and display error analysis detail selections provide additional analysis.
This service aid displays all installed resources, along with any VPD for those resources. Use this service aid when you want to look at the VPD for a specific resource.
When a machine check occurs, information is collected and logged in an NVRAM error log before the system unit shuts down. This information is logged in the AIX error log and cleared from NVRAM when the system is rebooted from the hard disk, LAN, or stand-alone media. When booting from stand-alone diagnostics, this service aid converts the logged information into a readable format that can be used to isolate the problem. When booting from the hard disk or LAN, the information can be viewed from the AIX error log using the hardware error report service aid. In either case, the information is analyzed when the sysplanar0 diagnostics are running in problem determination mode.
This task provides a way to display microcode on a device or adapter. When the sys0 resource is selected, the task displays the levels of both the system firmware and service processor firmware. sys0 may not be available in all cases.
The AIX lsmcode command serves as a command line interface to the display microcode level task.
This service aid displays the status of MPIO devices and their connections to their parent devices.
This service aid is capable of sending SCSI commands on each available path regardless of the default MPIO path algorithm. Therefore, it is useful for testing the unused path for integrity.
Run this service aid if you suspect a problem with the path between MPIO devices and their parent devices.
If there are no devices with multiple paths, this service aid will not be shown on the Task Selection menu.
/usr/lpp/diagnostics/bin/umpio
This service aid allows the bootlist to be displayed, altered, or erased.
The system attempts to perform an IPL from the first device in the list. If the device is not a valid IPL device or if the IPL fails, the system proceeds in turn to the other devices in the list to attempt an IPL.
This option allows the user to turn on or off displaying the DIAGNOSTIC MODE SELECTION MENU (the default is on).
This option allows the user to turn on or off including the advanced diagnostics (the default is off).
This option allows the user to select the number of days for which to search the AIX error log for errors when running the error log analysis. The default is seven days, but it can be changed from one to sixty days.
This option allows the user to turn on or off the progress indicators when running the diagnostic applications. The progress indicators, in a box at the bottom of the screen, indicate that the test is being run (the default is on).
This option allows the user to turn on or off logging information to the diagnostic event log (the default is on).
This option allows the user to select the maximum size of the diagnostic event log. The default size for the diagnostic event log is 100 KB. The size can be increased in 100 KB increments to a maximum of 1 MB.
/usr/lpp/diagnostics/bin/diaggetrto [-a] [-d] [-l] [-m] [-n] [-p] [-s]
/usr/lpp/diagnostics/bin/diagsetrto [-a on|off] [-d on|off] [-l size] [-m on|off] [-n days] [-p on|off]
This service aid allows a service representative to display results from a previous diagnostic session. When the display previous diagnostic results option is selected, the user can view up to 25 no trouble found (NTF) and service request number (SRN) results.
This service aid displays diagnostic event log information. You can display the diagnostic event log in a short version or a long version. The diagnostic event log contains information about events logged by a diagnostic session.
This service aid displays the information in reverse chronological order.
This information is not from the AIX operating system error log. This information is stored in the /var/adm/ras directory.
This task displays the customized device attributes associated with a selected resource. This task is similar to running the lsattr -E -l resource command.
This service aid reads and displays the information in the CEREADME file from the diagnostics media. This file contains information that is not contained in the publications for this version of the diagnostics. The file also contains information about using this particular version of diagnostics.
This service aid provides a means of adjusting system display units by providing test patterns that can be displayed. The user uses a series of menus to select the display type and test pattern. After the selections are made, the test pattern displays.
To run the USB devices service aid, go to the diagnostics TASKS SELECTION menu, select Display USB Devices. From the controller list that displayed on the screen, select one of the items that begins with "OHCDX", where "X" is a number. A list of devices attached to the controller displays.
This service aid provides a way to copy microcode to an adapter or device. The service aid presents a list of adapters and devices that use microcode. After the adapter or device is selected, the service aid provides menus to guide you in checking the current level and installing the needed microcode.
This task can be run directly from the AIX command line. Most adapters and devices use a common syntax as identified in the "Microcode Installation to Adapters and Devices" section. Information for adapters and devices that do not use the common syntax can be found following this section.
For many adapters and devices, microcode installation occurs and becomes effective while the adapters and devices are in use. Ensure that a current backup is available and the installation is scheduled during a non-peak production period.
The following is the common syntax command:diag [-c] -d device -T "download [-s {/etc/microcode|source}] [-l {latest|previous}] [-f]"
The following is the common syntax command: diag [-c] -d device -T "download [-s {/etc/microcode|source}]"
syntax:diag [-c] -d RAIDadapterName -T "download {-l chID | -A} [-D][-P]"
This task is only available through a command line interface. It is not available from the diagnostic menu nor from stand-alone diagnostics.
The fault indicators are used to identify a fault with the system. These indicators may be set automatically by hardware, firmware, or diagnostics when a fault is detected in the system.
The System Attention Indicator is turned off when a Log Repair Action is performed. All other Fault Indicators are turned off when the failing unit is repaired or replaced. After a serviceable event is complete, do a System Verification to verify the fix. Also, do a Log Repair Action if the test on the resource was good, and that resource had an entry in the error log.
/usr/lpp/diagnostics/bin/usysfault [-s normal] [-l location code | -d devicename] /usr/lpp/diagnostics/bin/usysfault [-t]
When the command is used without the -s flag, the current state of the indicator is displayed as normal or fault.
When the command is used without the -l or -d flag, the System Attention Indicator is used.
Use the -l or -d flags only in systems that have more than one fault indicator.
diag -T "certify"
diag -T "certify"
diag -T "format"
diag -T "download"
diag -T "download"
Use to update microcode images or boot images for stand-alone diagnostics from a flash memory device.
After loading an ISO9660 or later image onto a supported USB flashdrive. The user will be prompted to connect a flashdrive, select a flashdrive from a list of available flashdrives, and finally select a source ISO image. The source image may be located on the filesystem or on removable media.
This service aid is also used to copy the contents of optical media and other flashdrives to a flashdrive.
This task allows the flash firmware on the SysKonnect SK-NET FDDI adapter to be updated.
This task allows the selection of diskettes, hardfiles, or optical media to be formatted. Each selection is described below.
Writes all of the disk. The pattern written on the disk is device-dependent; for example some drives may write all 0s, while some may write the hexadecimal number 5F. No bad block reassignment occurs
Performs the same function as hardfile format. After the format is completed, Certify is run. Certify then reassigns all bad blocks encountered.
This option can be used to overwrite (remove) all data currently stored in user-accessible blocks of the disk. The derase disk option writes one or more patterns to the disk. An additional option allows data in a selectable block to be read and displayed on the system console.
For a newly installed drive, you can ensure that all blocks on the drive are overwritten with your pattern by using the following procedure:
Formats and certifies the media. This function reassigns the defective blocks and erases all data on the media.
Formats the media without certifying. This function does not reassign the defective blocks or erase the data on the media. This format type can only be used with previously formatted media.
Formats and certifies the media. This function reassigns the defective blocks and erases the data on the media by writing an initialization pattern to the entire media.
This task can be run directly from the AIX command line. The command line syntax is:diag -c -d deviceName -T"format [-s{initialize|fmtcert}]"
This service aid uses the AIX snap command to collect configuration information on networks, file systems, security, the kernel, the ODM, and other system components. You can also collect SSA adapter and disk drive configuration data, or AIX trace information for software debugging.
The output of the SNAP service aid can be used by field service personnel, or it can be put on removable media and transferred to remote locations for more extensive analysis.
To use the SNAP task, select Gather system information from the task list. You can select which components you want to collect information for, and where to store the data (hard disk or removable media).
The generic microcode download service aid provides a means of executing a genucode script from a diskette or tape. The purpose of this generic script is to load microcode to a supported resource.
The genucode program should be downloaded onto diskette or tape in tar format while the microcode image itself goes onto another one in restore format. Running the generic microcode download task will search for the genucode script on diskette or tape and execute it. It will ask for a genucode media to be inserted into the drive. The service aid moves the genucode script file to the /tmp directory and runs the program that downloads the microcode to the adapter or device.
This service aid is supported in both concurrent and stand-alone modes from disk, LAN, or loadable media.
The hot plug task provides software function for those devices that support hot plug or hot plug capability. This includes PCI adapters, SCSI devices, and some RAID devices. This task was previously known as "SCSI Device Identification and Removal" or "Identify and Remove Resource."
The hot plug task has a restriction when running in stand-alone or online service mode; new devices cannot be added to the system unless there is already a device with the same FRU part number installed in the system. This restriction is in place because the device software package for the new device cannot be installed in stand-alone or online service mode.
To run the hot plug task directly from the command line, type the following: diag -T"identifyRemove"
If you are running the diagnostics in online concurrent mode, run the missing options resolution procedure immediately after removing any device.
If the missing options resolution procedure runs with no menus or prompts, device configuration is complete. Select the device that has an uppercase M in front of it in the resource list so that missing options processing can be done on that resource.
You can run this task directly from the command line by typing the following command: diag -d device -T"identifyRemove"
However, note that some devices support both the PCI hot plug task and the RAID hot plug devices task. If this is the case for the device specified, then the hot plug task displays instead of the PCI hot plug manager menu.
diag -d device-T"identifyRemove" OR diag [-c] -d device -T"identifyRemove -a [identify?remove]"
The list the SCSI hot plug enclosure devices function lists all the SCSI hot plug slots and their contents. Status information about each slot is also available. The status information available includes the slot number, device name, whether the slot is populated and configured, and location.
The identify a device attached to an SCSI hot plug enclosure device function is used to help identify the location of a device attached to a SCSI hot plug enclosure device. This function lists all the slots that support hot plug that are occupied or empty. When a slot is selected for identification, the visual indicator for the slot is set to the identify state.
The attach a device to a SCSI hot plug enclosure device function lists all empty hot plug slots that are available for the insertion of a new device. After a slot is selected, the power is removed. If available, the visual indicator for the selected slot is set to the remove state. After the device is added, the visual indicator for the selected slot is set to the normal state, and power is restored.
The replace/remove a device attached to an SCSI hot plug enclosure device function lists all populated hot plug slots that are available for removal or replacement of the devices. After a slot is selected, the device populating that slot is unconfigured, the power is removed from that slot. If the unconfigure operation fails, it is possible that the device is in use by another application. In this case, the customer or system administrator must be notified to quiesce the device. If the unconfigure operation is successful, the visual indicator for the selected slot is set to the remove state. After the device is removed or replaced, the visual indicator, if available for the selected slot, is set to the normal state, and power is restored.
The configure added/replaced devices function runs the configuration manager on the parent adapters that had child devices added or removed. This function ensures that the devices in the configuration database are configured correctly.
diag -d device -T"identifyRemoveOR
diag -d device -T"identifyRemove -a [identify|remove ]
The normal subtask is used to return a RAID hot plug device to its normal state. This subtask is used after a device has been identified or replaced. This subtask lists all channel/IDs of the RAID and the status of the devices that are connected. A device in its normal state has power and the check light is off.
The identify subtask is used to identify the physical location of a device or an empty position in the RAID enclosure. This subtask lists all channel/IDs of the RAID and the status of the devices that are connected to the RAID enclosure. If a device is attached to the selected channel/ID, the check light on the device will begin to flash. If the channel/ID does not have a device attached, the light associated with the empty position on the enclosure will begin to flash.
The remove subtask is used to put the RAID hot plug device in a state where it can be removed or replaced. This subtask lists all channel/IDs of the RAID adapter that have devices that can be removed. Only devices with a status of Failed, Spare, Warning, or Non Existent can be removed. A device's status can be changed with the AIX smitty pdam command. After a device is selected for removal, the check light on the device will begin to flash, indicating that you may physically remove that device.
You can run this task directly from the command line. The command line syntax is:
The component and attention LEDs assist in identifying failing components in your server.
This task is used to display or set the identify indicators and the single system attention indicator on the systems that support this function.
Some systems may support only the identify indicators or only the attention indicator. The identify indicators are used to help physically identify the system, enclosure, or FRU in a large equipment room. The attention indicator is used to alert a user that the system needs attention and may have a hardware problem. In most cases, when an identify indicator is set to the Identify state, this results in a flashing LED, and when an attention indicator is set to the Attention state, this results in a solid LED.
When a hardware problem has been detected on a system that supports the attention indicator, the indicator is set to an attention state. After the failure has been identified, repaired, and a repair action has been logged, the attention indicator is reset to the normal state.
Subscribe to this information/usr/lpp/diagnostics/bin/usysident [-s {normal | identify}][-l location code | -d device name]
/usr/lpp/diagnostics/bin/usysident [-t]
When this command is used without the -l or the -d flags, the primary enclosure resource is used.
Use the -l flag only in systems that have more than one identify indicator. Use of the -d flag is preferred over use of the -l flag.
When this command is used without the -s flag, the current state of the identify indicator is displayed.
The log repair action task logs a repair action in the AIX error log. A repair action log indicates that a FRU has been replaced, and error log analysis should not be done for any errors logged before the repair action. The log repair action task lists all resources. Replaced resources can be selected from the list, and when commit (F7 key) is selected, a repair action is logged for each selected resource.
To locate the failing part in a system or partition running AIX, do the following:
For a description of the PCI RAID physical disk identify task, see SCSI RAID Physical Disk Status and Vital Product Data.
This service aid calls the smitty pdam fastpath, and is used to manage a RAID array connected to a SCSI RAID adapter. It may also be run from stand-alone diagnostics, which are available on systems or partitions with operating systems other than AIX installed on them (these environments do not allow you to run the smitty pdam command).
Other RAID functions are available using this service aid; they should only be used by the system administrator who is familiar with the RAID configuration. These functions are normally done when booting AIX by running smitty pdam from the command line.
Diagnostic supplemental media contains all the necessary diagnostic programs and files required to test a particular resource. The supplemental media is normally released and shipped with the resource as indicated on the diskette label. Diagnostic supplemental media must be used when the device support has not been incorporated into the latest diagnostic CD-ROM.
This task processes the diagnostic supplemental media. Insert the supplemental media when you are prompted; then press Enter. After processing has completed, go to the resource selection list to find the resource to test.
The run diagnostics task invokes the resource selection list menu. When the commit key is pressed, diagnostics are run on all selected resources.
The procedures for running the diagnostics depend on the state of the diagnostics run-time options. See Display or change diagnostic run-time options.
The run error log analysis task invokes the resource selection list menu. When the commit key is pressed, error log analysis is run on all selected resources.
This service aid allows you to diagnose a SCSI bus problem in a freelance mode.
To use this service aid, the user should understand how a SCSI bus works. Use this service aid when the diagnostics cannot communicate with anything on the SCSI bus and cannot isolate the problem. Normally the procedure for finding a problem on the SCSI bus with this service aid is to start with a single device attached, ensure that it is working, then start adding additional devices and cables to the bus, ensuring that each one works. This service aid works with any valid SCSI bus configuration.
When the SCSI bus service aid is started a description of the service aid displays.
Pressing Enter displays the adapter selection menu. Use this menu to enter the address to transmit the SCSI Inquiry Command.
When the adapter is selected, the SCSI bus address selection menu displays. Use this menu to enter the address to transmit the SCSI inquiry command.
After the address is selected, the SCSI bus test run menu displays. Use this menu to transmit the SCSI inquiry command by pressing Enter. The service aid then indicates the status of the transmission. When the transmission is completed, the results of the transmission displays.
Use this service aid when you want to look at the vital product data for a specific disk attached to a RAID adapter. This service aid displays all disks that are recognized by the PCI RAID adapter, along with their status, physical location, microcode level, and other vital product data. The physical location of a disk consists of the channel number of the RAID adapter and the SCSI ID number of the position in the enclosure. The microcode level is listed next to the physical location of the disk.
diag -c -d devicename -T "identify"
This service aid allows you to obtain the status or maintenance information from a SCSD tape drive. Not all models of SCSD tape drive are supported.
TRACEx.DAT (where x is a sequential diskette number). The complete trace table consists of the sequential concatenation of all the diskette data files.
When the trace table is written to a disk file, the service aid prompts for a file name. The default name is: /tmp/TRACE. x, where x is the AIX name of the SCSD tape drive being tested.
utape [-h | -?] [-d device] [-n | -l | -t]
OR
utape -c -d device [-v] {-n | {-l | -t} { -D | -f [ filename]}}
This selection checks the number of spare sectors available on the optical disk. The spare sectors are used to reassign when defective sectors are encountered during normal usage or during a format and certify operation. Low availability of spare sectors indicates that the disk must be backed up and replaced. Formatting the disk does not improve the availability of spare sectors.
You can run this task directly from the AIX command line. The command syntax is: diag -c -d deviceName -T chkspares
If a failing component is detected in your system, an amber-colored attention LED on the front of the system unit is turned on solid (not blinking).
To identify a system from a group of systems, an amber-colored attention LED on the front of the system unit is blinking.
This service aid allows fixes (APARs) to be applied.
This task invokes the SMIT update software by fix (APAR) task. The task allows the input device and APARs to be selected. You can install any APAR using this task.
If the system is already in a full system partition, use the following normal firmware update procedures.
This selection updates the system or service processor flash. Some systems may have separate images for system and service processor firmware; newer systems have a combined image that contains both in one image.
Look for additional update and recovery instructions with the update kit. You need to know the fully qualified path and file name of the flash update image file provided in the kit. If the update image file is on a diskette or optical media, the service aid can list the files on the diskette or optical media for selection. The diskette must be a valid backup format diskette.
Refer to the update instructions with the kit, or the service information for the system unit to determine the current level of the system unit or service processor flash memory.
When this service aid is run from online diagnostics, the flash update image file is copied to the /var file system. Put the source of the microcode that you want to download into the /etc/microcode directory on the system. If there is not enough space in the /var file system for the new flash update image file, an error is reported. If this error occurs, exit the service aid, increase the size of the /var file system, and retry the service aid. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue the update flash, the system reboots using the shutdown -u command. The system does not return to the diagnostics, and the current flash image is not saved. After the reboot, you can remove the /var/update_flash_image file.
When this service aid is run from stand-alone diagnostics, the flash update image file is copied to the file system from diskette, optical media, or from the Network Installation Management (NIM) server. Using a diskette, the user must provide the image on backup format diskette because the user does not have access to remote file systems or any other files that are on the system. If using the NIM server, the microcode image must first be copied onto the NIM server in the /usr/lib/microcode directory pointed to the NIM SPOT (from which you plan to have the NIM client boot stand-alone diagnostics) prior to performing the NIM boot of diagnostics. Next, a NIM check operation must be run on the SPOT containing the microcode image on the NIM server. After performing the NIM boot of diagnostics, you can use this service aid to update the microcode from the NIM server by choosing the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. If not enough space is available, an error is reported, stating additional system memory is needed. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue with the update, the system reboots using the reboot -u command. You may receive a Caution: some process(es) wouldn't die message during the reboot process. You can ignore this message. The current flash image is not saved.
update_flash [-q ]-f file_name update_flash [-q ]-D device_name -f file_name update_flash [-q ]-D update_flash [-q ]-D device_name -l
This selection validates a new system firmware flash image and uses it to update the system temporary flash image. This selection can also be used to validate a new system firmware flash image without performing an update, commit the temporary flash image, and reject the temporary flash image.
When this service aid is run from online diagnostics, the flash update image file is copied to the /var file system. If there is not enough space in the /var file system for the new flash update image file, an error is reported. If this error occurs, exit the service aid, increase the size of the /var file system, and retry the service aid. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue the update flash, the system reboots using the shutdown -u command. The system does not return to the diagnostics, and the current flash image is not saved. After the reboot, you can remove the /var/update_flash_image file.
When this service aid is run from stand-alone diagnostics, the flash update image file is copied to the file system from optical media, or from the NIM server. If using the NIM server, the server firmware image must first be copied onto the NIM server in the /usr/lib/microcode directory pointed to the NIM SPOT (from which you plan to have the NIM client boot stand-alone diagnostics) prior to performing the NIM boot of diagnostics. Next, a NIM check operation must be run on the SPOT containing the microcode image on the NIM server. After performing the NIM boot of diagnostics one can use this service aid to update the microcode from the NIM server by choosing the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. If not enough space is available, an error is reported, stating additional system memory is needed. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue with the update, the system reboots using the reboot -u command. You may receive a message that says: "Caution: some process(es) wouldn't die" during the reboot process; you can ignore this message. The current flash image is not saved.
update_flash [-q | -v] -f file_name update_flash [-q | -v] -D device_name -f file_name update_flash [-q | -v] -D update_flash [-l] update_flash -c update_flash -r
To identify a physical disk, use this command syntax: diag -c -d deviceName -T "identify"
