Tasks and service aids

Add resources to the resource list

Use this task to add resources back to the resource list.

Shell prompt

This service aid allows access to the AIX® command line. To use this service aid, you must know the root password (if a root password is set).

Analyze the adapter internal log

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 system error log and clears the internal log.

The analyze adapter internal log service aid analyzes these entries in the 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]. The 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 you want to store the output data.

diag -c -d devicename -T "adapela [-s start date -e end date]"

Flag

Description

-c

Specifies not console mode.

-d device name

Specifies the device whose internal log you want to analyze (for example, SCRAID0)

-s start date

Specifies all errors after this date are analyzed.

-e end date

Specifies all errors before this date are analyzed.

-T

Specifies the Analyze Adapter Internal Log task

Back up and restore media

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 wanted device. It then presents a menu of available backup formats and prompts for selecting the wanted 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.

Certify media

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 disk files can be connected either to a SCSI adapter (non-RAID) or a PCI SCSI RAID adapter. The usage and criteria for a hard disk file connected to a non-RAID SCSI adapter are different from the usage and criteria for a hard disk file connected to a PCI SCSI RAID adapter.

Change hardware vital product data

Use this service aid to view the alter or display the vital product data (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.

Configure dials and LPF keys

This service aid provides a tool for configuring and removing dials and LPF keys to the asynchronous system ports.

This selection starts the System Management Interface Tool (SMIT), which allows dial and LPF key 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 whether there are any defined TTYs, select List All Defined TTYs. After all defined TTYs are removed, then add a TTY and configure the dials or LPF keys.

Configure reboot policy (CHRP)

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.

Enable platform automatic power restart

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 is restarted as indicated by the SMIT option: Automatically reboot operating system after a crash. This setting must be set for each partition.

/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] 

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

/usr/lpp/diagnostics/bin/uspchrp -e PlatformBootSpeed=[fast|slow]

With a fast platform speed, the platform firmware performs a minimal set of hardware tests before loading the operating system. With a slow platform speed, the platform firmware performs a comprehensive set of hardware tests before loading the operating system.

Configure platform processor diagnostics

The periodic setting cannot be set by using this service aid, although it can be read. The management console is used to set the periodic setting.

The Configure platform processor diagnostics setting is accessed by using the diag command, and 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

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 in the nonvolatile random access memory (NVRAM) on the system.

/usr/lpp/diagnostics/bin/uspchrp -d

Delete resource from resource list

Disk maintenance

Disk-to disk-copy

Use this selection 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 to be reassigned reaches a threshold.

To prevent problems that can occur when running this service aid from disk, run this service aid from the diagnostics that are loaded from removable media when possible.

Display/alter sector

This selection allows the user to display and alter information about 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.

Display configuration and resource list

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.)

Display firmware device node information

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 might differ depending on which level of the operating system is installed.

Display hardware error report

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.

Display hardware vital product data

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.

Display machine check error log

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 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 in to 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 by using the hardware error report service aid. In either case, the information is analyzed when the sysplanar0 diagnostics are running in problem determination mode.

Display microcode level

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 might not be available in all cases.

The lsmcode command serves as a command-line interface to the display microcode level task.

Display MultiPath I/O (MPIO) device configuration

This service aid displays the status of MPIO devices and their connections to their parent devices.

Use this service aid to send 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 is not shown on the Task Selection menu.

/usr/lpp/diagnostics/bin/umpio

Display or change bootlist

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.

Display or change diagnostic runtime options

/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]

Display previous diagnostic results

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 operating system error log. This information is stored in the /var/adm/ras directory.

/usr/lpp/diagnostics/bin/diagrpt [[-o] ? [-s mmddyy] ? [-a] ? [-r]]

Display resource attributes

This task displays the customized device attributes associated with a selected resource. This task is similar to running the lsattr -E -l resource command.

Display software product data

Display test patterns

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.

Display USB devices

To run the USB devices service aid, go to the diagnostics TASKS SELECTION menu, and 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.

Download microcode

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.

Microcode installation to adapters and devices

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.

Microcode installation to an SES device

diag [-c] -d device -T "download [-s {/etc/microcode|source}]" 

Microcode installation to PCI SCSI RAID adapters

Microcode installation to disk drive attached to PCI SCSI RAID adapters

Fault indicators

This task is only available through a command-line interface. It is not available from the diagnostic menu or from stand-alone diagnostics.

The fault indicators are used to identify a fault with the system. These indicators might 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.

Fibre Channel RAID service aids

Flash drive (USB)

Use this command to update microcode images or boot images for stand-alone diagnostics from a flash memory device.

You must first load an ISO9660 or later image onto a supported USB flash drive. You are prompted to connect a flash drive, select a flash drive from a list of available flash drives, and select a source ISO image. The source image might be on the file system or on removable media.

This service aid is also used to copy the contents of optical media and other flash drives to a flash drive.

Flash SK-NET FDDI firmware

This task allows the flash firmware on the SysKonnect SK-NET FDDI adapter to be updated.

Format media

This task allows the selection of diskettes, hard disks, or optical media to be formatted.

Hard disk attached to SCSI adapter (non-RAID)

This service aid includes the following options:

Hard disk format

Writes all of the disk. The pattern written on the disk is device-dependent; for example some drives might write all zeros, while some might write the hexadecimal number 5F. No bad block reassignment occurs.

Hard disk Format and Certify

Performs the same function as hard disk format. After the format is completed, Certify is run. Certify then reassigns all bad blocks encountered.

Hard disk Erase Disk

This option can be used to overwrite (remove) all data currently stored in user-accessible blocks of the disk. The erase 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.

To use the erase disk option, specify the number (0-3) of patterns to be written. The patterns are written serially; that is, the first pattern is written to all blocks. The next pattern is written to all blocks, overlaying the previous pattern. A random pattern is written by selecting the Write Random Pattern? option.

Note: The erase disk service aid is not certified as meeting the Department of Defense or any other security organization guidelines.

To overwrite the data on the drive, use the following steps:

1. Select Erase Disk.
2. Do a format without certify.
3. Select Erase Disk to run it a second time.

For a newly installed drive, you can ensure that all blocks on the drive are overwritten with your pattern by using the following procedure:

1. Format the drive.
2. Check the defect MAP by running the erase disk option.
   Note: If you use the format and certify option, there might be some blocks which get placed into the grown defect MAP.
3. If there are bad blocks in the defect MAP, record the information presented and ensure that this information is kept with the drive. This data is used later when the drive is to be overwritten.
4. Use the drive as you would normally.
5. When the drive is no longer needed and is to be erased, run the same version of the erase disk option which was used in step 2.
   Note: Using the same version of the service aid is only critical if any bad blocks were found in step 3.
6. Compare the bad blocks which were recorded for the drive in step 3 with the bad blocks that now appear in the grown defect MAP.
   Note: If there are differences between the saved data and the newly obtained data, all sectors on this drive cannot be overwritten. The new bad blocks are not overwritten.
7. If the bad block list is the same, continue running the service aid to overwrite the disk with the chosen pattern or patterns.

diag -c -d deviceName -T "format [-s* fmtcert | erase -a {read | write}
								 -P {comma separated list of patterns}] [-F]*"

Hard disk attached to PCI SCSI RAID adapter

diag -c -d RAIDadapterName -T "format {-l chId | -A }"

Optical media

diag -c -d deviceName -T "format [-s {initialize | fmtcert} ]"

DVD-RAM media

Initialize

Formats the media without certifying. This function does not reassign the defective blocks or erase the data on the media. This format type can be used only with previously formatted media.

Format and Certify

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.

diag -c -d deviceName -T "format [-s{initialize|fmtcert}]"

Diskette format

This selection formats a diskette by writing patterns to it.

Gather system information

If you are using the Linux operating system, the gather system information option does not apply. This service aid uses the snap command to collect configuration information about networks, file systems, security, the kernel, the ODM, and other system components. You can also collect SSA adapter and disk drive configuration data, or trace information for software debugging.

The output of the SNAP service aid can be used by field service personnel. The output can also 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).

Generic microcode download

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 must be downloaded onto diskette or tape in the tar format. The microcode image itself goes onto another one in restore format. Running the generic microcode download task searches for the genucode script on diskette or tape and runs it. You will be prompted to insert a genucode media 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.

Hot plug task

The hot plug task provides software function for those devices that support hot plug or hot plug capability. These devices include PCI adapters, SCSI devices, and some RAID devices. This task was previously known as SCSI Device Identification and Removal or Identify and Remove Resource.

If you are running the AIX operating system, 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 AIX command line, type the following command: 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.

PCI hot plug manager

diag -d device -T "identifyRemove"

However, 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.

SCSI hot plug manager

diag -d device -T "identifyRemove"

diag [-c] -d device -T "identifyRemove -a [identify|remove]"

SCSI and SCSI RAID hot plug manager

diag -d device -T "identifyRemove"

diag -d device -T "identifyRemove -a [identify|remove]"

-a

Specifies the option under the task.

-d

Indicates the SCSI device.

-T

Specifies the task to run.

RAID hot plug devices

The normal subtask is used to return a RAID hot plug device to its normal state. This subtask is used after a device is 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. The status of a device 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 can physically remove that device.

You can run this task directly from the AIX command line. The command-line syntax is:

Identify indicators

The component and attention LEDs assist in identifying failing components in your server.

Identify and system attention indicators

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 might 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 might 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 is detected on a system that supports the attention indicator, the indicator is set to an attention state. After the failure is identified, repaired, and a repair action is logged, the attention indicator is reset to the normal state.

/usr/lpp/diagnostics/bin/usysident [-s {normal | identify}][-l location code | -d device name]

/usr/lpp/diagnostics/bin/usysident [-t] 

-s {normal | identify}

Sets the state of the system identify indicator to either normal or identify.

-l location code

Identifies the resource by physical location code.

-d device name

Identifies the resource by device name

-t

Displays a list of all supported identify indicators by physical location codes.

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.

Local area network analyzer

Log repair action

The log repair action task logs a repair action in the AIX operating system 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, do the following steps:

1. Log in as root user.
2. At the command line, enter diag.
3. Select the Diagnostics Routines option.
4. When the DIAGNOSTIC MODE SELECTION menu displays, select Problem Determination.
5. When the ADVANCED DIAGNOSTIC SELECTION menu displays, do one of the following options:
   • To test a single resource, select the resource from the list.
   • To test all the resources available to the operating system, select All Resources.
6. Press Enter, and wait until the diagnostic programs run to completion, responding to any prompts that appear on the console.
7. Use the location information for the failing part to activate the indicator light that identifies the failing part. For instructions, see Activate the indicator light for the failing part.

Microcode tasks

PCI RAID physical disk identify

For a description of the PCI RAID physical disk identify task, see SCSI RAID Physical Disk Status and Vital Product Data.

PCI-X SCSI disk array manager

This service aid calls the smitty pdam fast path, and is used to manage a RAID array connected to a SCSI RAID adapter. It might also be run from stand-alone diagnostics on systems or logical partitions that are running the AIX operating system. If you are running the Linux operating system, use the iprconfig tool for disk array management.

Other RAID functions are available by using this service aid; they must be used only 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.

Process supplemental media

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/DVD-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.

Read intensive SSD fuel gauge

Use this service aid to display the life expectancy status of pdisk read intensive solid-state drives (SSDs).

This task can be run directly from the AIX command line. To display the status of all supported read intensive SSDs, type the following command and press Enter:

/usr/lpp/diagnostics/bin/pdiskfg

To display the status of a specific SSD, type the following command and press Enter:

/usr/lpp/diagnostics/bin/pdiskfg -d pdiskX, where X is the pdisk number.

diag -d pdiskX -T pdiskfg

Run diagnostics

If you are using the AIX operating system, or by using the stand-alone diagnostics, the run diagnostics task starts 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 runtime options. See Display or change diagnostic run time options.

Run error log analysis

The run error log analysis task starts the resource selection list menu. When the commit key is pressed, error log analysis is run on all selected resources.

SCSI bus analyzer

Use this service aid to diagnose a SCSI bus problem in a freelance mode.

To use this service aid, you must 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. To find a problem on the SCSI bus with this service aid, start with a single device attached, ensure that it is working, then start adding devices and cables to the bus. After each addition, ensure 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.

SCSI RAID physical disk status and vital product data

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"

SCSD tape drive service aid

Use this service aid to obtain the status or maintenance information from an SCSD tape drive. Not all models of SCSD tape drive are supported.

utape [-h | -?] [-d device] [-n | -l | -t]
OR
utape -c -d device [-v] {-n | {-l | -t} { -D | -f [ filename]}}

Spare sector availability

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.

diag -c -d deviceName -T chkspares

SSA service aid

System fault indicator

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 flashing).

System identify indicator

To identify a system from a group of systems, an amber-colored attention LED on the front of the system unit is flashing.

Update disk-based diagnostics

This service aid allows fixes (APARs) to be applied.

This task starts the SMIT update software by fix (APAR) task. The task allows the input device and APARs to be selected. You can install any APAR by using this task.

Update system or service processor flash

This selection updates the system or service processor flash. Some systems might 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.

See 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 try the service aid again. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue the update flash, the system reboots by 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 the 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. If you use a diskette, you must provide the image on backup format diskette because you will not have access to remote file systems or any other files that are on the system. Before you can boot diagnostics from the NIM server, you must ensure that the microcode image is copied to the /usr/lib/microcode directory on the NIM server. Then point to the NIM SPOT (from which you plan to have the NIM client boot stand-alone 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. Choose the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. If there is not enough space 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 by using the reboot -u command. You might receive a Caution: some processes would not 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

Flag

Description

-D

Specifies that the flash update image file is on diskette. The device_name variable specifies the device. The default device_name is /dev/fd0.

-f

Flash update image file source. The file_name variable specifies the fully qualified path of the flash update image file.

-l

Lists the files on a diskette, from which the user can choose a flash update image file.

-q

Forces the update_flash command to update the flash EPROM and reboot the system without asking for confirmation.

Update and manage system flash

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 try the service aid again. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue the update flash, the system reboots by 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. Before performing the NIM boot of diagnostics, the server firmware image must first be copied onto the NIM server in the /usr/lib/microcode directory. Then you must point to the NIM SPOT (from which you plan to have the NIM client boot stand-alone 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. Choose the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. If enough space is not 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 by using the reboot -u command. You might receive a message that says: "Caution: some processes would not 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

Flag

Description

-D

Specifies that the flash update image file is on diskette. The device_name variable specifies the device. The default device_name is /dev/fd0.

-f

Flash update image file source. The file_name variable specifies the fully qualified path of the flash update image file.

-l

Lists the files on a diskette, from which the user can choose a flash update image file.

-q

Forces the update_flash command to update the flash EPROM and reboot the system without asking for confirmation.

-v

Validates the flash update image. No update will occur. This flag is not supported on all systems.

-c

Commits the temporary flash image when booted from the temporary image. This action overwrites the permanent image with the temporary image. This flag is not supported on all systems.

-r

Rejects the temporary image when booted from the permanent image. This action overwrites the temporary image with the permanent image. This flag is not supported on all systems.

Examples: Commands

To identify a physical disk, use this command syntax: diag -c -d deviceName -T "identify"