./asu: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory.
If this message is displayed, install the compat-libstdc++*.rpm that is included on the distribution media. 2. The ASU Version 3.60 does not update the PC-DOS and Sun Solaris executable files. No technical support is available for these two operating systems. For BIOS-based servers, run the ASU on the system that contains the settings that you want to view and change. When the ASU performs setting configuration, it interacts with the physical hardware. On operating systems that require root or administrator access to interact with physical hardware, you must run the ASU from an account that has root or administrator access. (Windows and Linux require root and administrator access.) The Remote Supervisor Adapter device drivers and Remote Supervisor Adapter II USB daemon are used to view and change Remote Supervisor Adapter or Remote Supervisor Adapter II settings. If there is no Remote Supervisor Adapter or Remote Supervisor Adapter II device driver for an operating system (such as PC-DOS), the ASU does not support changing Remote Supervisor Adapter or Remote Supervisor Adapter II settings for that operating system. For baseboard management controller settings, an Intelligent Platform Management Interface (IPMI) device driver and a corresponding IBM IPMI mapping layer (if required) are required. The ASU supports interfacing with different versions of the IPMI device driver (OSA, MSI, Microsoft IPMI Driver, and OpenIPMI). For Microsoft Windows-based implementations, see IPMI device driver support for Windows on page 7. For Linux-based implementations, see IPMI device driver support for Linux on page 8.
Notes: v You cannot use the ASU to configure Remote Supervisor Adapter II settings from Red Hat Enterprise Linux AS 2.1 because there is no Remote Supervisor Adapter II device driver for the Red Hat Enterprise Linux AS 2.1 operating system. v You cannot use the ASU to configure Remote Supervisor Adapter or Remote Supervisor Adapter II settings from PC-DOS because there is no Remote Supervisor Adapter or Remote Supervisor Adapter II device driver for PC-DOS. v You can view or change settings on a local server only. v You cannot use the ASU to configure baseboard management controller settings from PC-DOS because there is no baseboard management controller device driver for PC-DOS. v The PC-DOS version of the ASU does not support a multi-node-capable server when it is configured as multi-node. v The PC-DOS version of the ASU does not support a server in which the BIOS settings are stored in the baseboard management controller (for example, an IBM System x3950 M2 server). v You cannot unpack the Windows ASU packages on a server or workstation that is running a 64-bit version of Windows PE. You can unpack the Windows ASU packages on a server or workstation that is running any of the other Windows operating systems that support the ASU. (For a list of operating systems that support the ASU, see Operating-system support on page 2.)

You can also configure the DHCP setting by using the ASU. To use the ASU, continue with the following procedure. If you have an enabled DHCP server and you want to configure the serial connector, go to Example of configuring the serial connection on a Remote Supervisor Adapter II. To configure the Ethernet settings if you do not have a DHCP server on your network, complete the following steps. Note: If you are using a Linux operating system, be sure to type./ before asu. 1. If you have not already done so, unpack the ASU files. For more information, see Unpacking the ASU files for Windows on page 11 or Unpacking the ASU files for Linux on page 12. 2. At the command prompt, change to the directory that contains the ASU files. 3. If you have not already done so, add the Remote Supervisor Adapter/Remote Supervisor Adapter II ASU patch. For more information, see Patchadd command on page 63 and Patchlist command on page 65. Note: This step is not required if you are using ASU version 2.0 or later. 4. To view a list of all settings and their assigned values, type the following command and press Enter:

asu show all

5. From the following list, select the items that you want to set: v To enable the network interface on the Remote Supervisor Adapter II, type the following command and press Enter:
asu set RSA_Network1 Enabled
v To set the IP address, type the following command and press Enter:
asu set RSA_HostIPAddress1 192.169.70.140
v To set the subnet mask, type the following command and press Enter:
asu set RSA_HostIPSubnet1 255.255.255.0.
v To set the gateway IP address, type the following command and press Enter:
asu set RSA_GatewayIPAddress1 192.168.70.1
v To enable DHCP, type the following command and press Enter:
asu set RSA_DHCP1 Enabled
v To set the data-transfer rate, type the following command and press Enter:
asu set RSA_LANDataRate1 "10M Ethernet"
v To set duplex mode, type the following command and press Enter:

asu set RSA_Duplex1 Full

6. Type asu rebootrsa and press Enter.
Example of configuring the serial connection on a Remote Supervisor Adapter II
You can use the ASU to configure the Remote Supervisor Adapter II serial connection. The serial connector connects to a modem for dial-out support only. To configure the Remote Supervisor Adapter II serial connection for access to a modem, complete the following steps. Note: If you are using a Linux operating system, be sure to type./ before asu.
1. If you have not already done so, unpack the ASU files. For more information, see Unpacking the ASU files for Windows on page 11 or Unpacking the ASU files for Linux on page 12. 2. At the command prompt, change to the directory that contains the ASU files. 3. To view a list of all of the settings and assigned values, type the following command and press Enter:

asu show

You can request that the ASU connect locally, exclusively using the KCS interface, which avoids the automated connection over the LAN over USB interface (and the fallback to the KCS interface). If you use the --kcs option, the ASU communicates through the KCS interface only. In the following example, the ASU attempts to connect through the KCS interface only, without the need for authentication parameters.

asu show --kcs

You can also request that the ASU connect locally, exclusively using the LAN over USB interface, by specifying the --host connectivity option. The ASU does not attempt to fall back to use the KCS interface when this option is specified. In the following example, the ASU attempts to connect through the LAN over USB interface only by using the default user ID and password account.
asu show --host 169.254.95.118
When the ASU runs any command on an IMM-based server, it attempts to connect and automatically configure the LAN over USB interface, if it detects that this interface is not configured. The ASU provides a level of automatic and default settings. You have the option of specifying that the automatic configuration process is skipped, if you have manually configured the IMM LAN over USB interface by using different settings than those used by the ASU application default settings. You can use the --noimmlancfg option to skip automatic configuration process, if you have manually configured the interface. For example, if you want to show the IMM list of settings and avoid using the automatic configuration process when you attempt to connect through the LAN over USB interface, type the following command:
asu show IMM --noimmlancfg
If the ASU is connecting remotely to the IMM over the LAN, there is no requirement for the remote operating system of the targeted IMM to be booted (online). The ASU can connect to the IMM remotely when the server is connected to power or is using standby power.
To connect remotely, the --host option is required. The following example indicates the minimum required parameter when the ASU connects remotely through the LAN to the IMM external port.
asu show --host target_IMM_external_IP_address
Enabling and disabling the LAN over USB interface You can use the ASU to enable or disable the IMM LAN over USB interface by using the IMM.LanOverUsb setting. When you enable or disable this setting, you must use the KCS interface because the LAN over USB interface is removed during the set command process. This prevents the ASU set command from terminating correctly. You must use the --kcs connectivity option to make sure that the asu command is completed correctly and relates status.

asu set IMM.HostIPAddress 9.5.51.37
where IMM.HostIPAddress is the IMM setting that is used to configure the IMM external IP address. The setting is part of the IMM group. There are settings that include an additional index, which is referred to in this document as an instance. The index is used to identify and set different instances of the same setting when these are available. Example: To set the first instance of a number or login ID, type the following command:
asu set IMM.LoginId.1 testid
where IMM.LoginId.1 is the IMM setting that is used to configure the first instance of a login account.

Instances of settings

Support for instances of settings on IMM-based servers was introduced in the ASU 3.0. The ASU 3.01 is extending the support of instances in several different ways. Commands have been created or modified to provide more information about instances and ways to create and delete them. Instances are denoted by adding a dot, followed by the instance number to the end of the setting name. For example, if the setting name is IMM.LoginId, instance number 1 of the setting is IMM.LoginId.1. Note: There is an exception to the naming convention for single instances. Single instances do not have the dot followed by an instance number. The setting instead appears like a non-instance setting. Single instance settings are denoted in the output of the showvalues command by having a maximum number of instances of single. For example, the setting iSCSI.initiatorName is a single instance. Notice that the usual dot followed by an instance number is not used. If the single instance exists, the setting iSCSI.initiatorName is displayed in the show command output. If it does not exist, the setting is not displayed in the show command output. Instance settings are now defined to have a minimum and maximum number of allowed instances. To determine which settings can have instances and the minimum and maximum number of instances allowed, use the showvalues command with the new --instances parameter. The output of this command is detailed in Showvalues command on page 89.
Creating and deleting instances
Beginning with the ASU 3.01, you can create or delete instances. Use the set command to create an instance. If the instance does not already exist, and the instance number is between 1 and the maximum number of allowed instances, the instance is automatically created and set to the value specified in the set command. Use the new delete command to delete an instance. This command deletes the instance, if deleting the instance does not cause the number of instances for the setting to go below the minimum number of allowed instances for the setting. Note: There are restrictions for creating and deleting instances of settings that are part of a record. For more information about the restrictions, see Record management.

Table 1. IMM LAN over USB configuration application commands (continued) Configuration application command installdriver detectdriver Operating system support

Description

Command syntax to set the command asu immcfg --installdriver [--inf inf_path/name] asu immcfg -detectdriver
Installs the IMM LAN over USB Windows only device driver Detects whether the device Windows only driver for the IMM LAN over USB interface is installed in the operating system Automatically configures the IMM LAN over USB interface using all default settings. The default settings include packaged.inf,.cat, and.sh files. The default IP address is 169.254.95.119 for the operating system IP address. Note: The IMM IP address is 169.254.95.118; however, this address can change if the default address is used by another device. Windows Linux VMware

autocfg

asu immcfg --autocfg

Classes of settings

For commands that support operating on multiple settings, classes are used to indicate groups of settings. The commands that support classes are comparedefault, help, loaddefault, show, showdefault, showlocation, and showvalues. The ASU classes of settings are described in the following list: all This class includes all settings that are listed in the ASU for the Remote Supervisor Adapter or Remote Supervisor Adapter II, baseboard management controller, and BIOS. authentication This class includes all settings that are classified as authentication settings, which include passwords, user IDs, and authority-related settings. The save and restore commands do not save or restore this class of settings. You can list the user IDs and authority-related settings by using the show command. You cannot list the password settings by using the show command. To list the password settings, use the showvalues command. Example: List the settings defined as authentication, including the password settings. Password settings are normally not displayed when you use the show command. To display the available password, use the showvalues command with the password class:
asu showvalues authentication
backupctl This class lists all settings that are not restored when you run the restore command. An additional flag is required for these settings to be included during a restore operation. For more information, see the Restore command on page 74. Class filter for the show, showvalues, showdefault, and showlocation commands. To list the settings that are not restored if saved, type the following command:

asu show backupctl

bios This class includes all settings that match the installed BIOS code level. bmc This class includes all settings that are identified as baseboard management controller settings. change This class includes all settings that are not in the reboot class that can be changed safely and changed back before the system is restarted. critical This class includes all settings that you cannot change safely before a restart but that must be tested. group This class includes all settings that belong to the specified group. To view the supported groups, use the showgroups command. Settings in BIOS-based servers and IMM-based servers are cataloged in classes or groups. If specified, the class is used as a filter for the command that is displaying or operating on the settings. Class filter for the show, showvalues, showdefault, showlocation, save, restore, and replicate commands. Examples: To list the settings that are part of the IMM group (IMM-based servers):

Table 4. ASU return codes Return code value Description Successful command Input error Explanation The ASU command has been completed successfully. The input that was provided to the ASU has an error. This might be a user-input error or an error with the provided definition file. An error occurred when you tried to use specific software. An error occurred when the ASU tried to communicate with or find specific hardware. An error occurred in the data that the ASU reads or sets. An error occurred in the ASU program execution flow. An ASU patch is missing or an ASU patch does not match the required level.
Software error Hardware error
Data error Program error Invalid or missing patch detected The command is not supported. Invalid value input error
The input value that is provided to the ASU has a syntax error. One or more of the commands that were specified in the batch file has failed. The ASU application is a 32-bit version, and you are attempting to run it on a 64-bit operating system.

Batch command error

32-bit version running on 64-bit operating system
RDCLI return code messages
The following table lists the RDCLI return code messages
Table 5. RDCLI return code messages Situation Success Invalid parameters Unknown character No login name Failed to read.netrc file Cannot find (HOME) environment Failed to allocate memory to read Failed to open.netrc file Cannot find any entry in the.netrc file No IMM address provided No filepath provided Invalid process ID Cannot get the program process ID (pid) or parent process ID (ppid) from the system Failed to get login/drive/IMM information Another mount session exists Cannot find an existing mount session Failed to passthrough authentication Return message The virtual disk mount successfully Invalid parameter in command line Unknown option character Please indicate your login name on the IMM Error when load username and password Problem read environment parameters Could not allocate memory Could not open.netrc file Please indicate your login or password in IMM Please indicate a target IMM by hostname or IP Pleas indicate a target CD/DVD drive or image Error in system call Malformed output from system process list Malformed output from system process list Theres already a session on the machine, unmount first. No rdmount session found Fail in authentication, please check your username and password or IMM setting and try later. sockConnet: Could not connect to IMM address at port PORT1 Failed in login authentication to IMM. Failed to map the local file to the remote disk. Unknown error while mounting. Invalid token

asu show iscsi

Example: The following example shows the list of settings if a single attempt group is defined. All setting names with the same instance.1 belong to the same attempt group:
iSCSI.InitiatorName iSCSI.MacAddress.1 iSCSI.AttemptName.1 iSCSI.IscsiMode.1 iSCSI.ConnectRetryCount.1 iSCSI.ConnectTimeout.1 iSCSI.InitiatorInfoFromDhcp.1 iSCSI.LocalIp.1 iSCSI.SubnetMask.1 iSCSI.Gateway.1 iSCSI.TargetInfoFromDhcp.1 iSCSI.TargetName.1 iSCSI.TargetIp.1 iSCSI.TargetPort.1 iSCSI.BootLun.1 iSCSI.CHAPType.1 iSCSI.CHAPName.1 iSCSI.CHAPSecret.1 iSCSI.ReverseCHAPName.1 iSCSI.ReverseCHAPSecret.1 iSCSI.MacAddress.2
Example: The following example shows the list of settings if two attempts are defined:
iSCSI.InitiatorName iSCSI.MacAddress.1 iSCSI.AttemptName.1 iSCSI.IscsiMode.1 iSCSI.ConnectRetryCount.1 iSCSI.ConnectTimeout.1 iSCSI.InitiatorInfoFromDhcp.1 iSCSI.LocalIp.1 iSCSI.SubnetMask.1 iSCSI.Gateway.1 iSCSI.TargetInfoFromDhcp.1 iSCSI.TargetName.1 iSCSI.TargetIp.1 iSCSI.TargetPort.1 iSCSI.BootLun.1 iSCSI.CHAPType.1 iSCSI.CHAPName.1 iSCSI.CHAPSecret.1 iSCSI.ReverseCHAPName.1 iSCSI.ReverseCHAPSecret.1 iSCSI.MacAddress.2 iSCSI.AttemptName.2 iSCSI.IscsiMode.2 iSCSI.ConnectRetryCount.2 iSCSI.ConnectTimeout.2 iSCSI.InitiatorInfoFromDhcp.2 iSCSI.LocalIp.2 iSCSI.SubnetMask.2 iSCSI.Gateway.2 iSCSI.TargetInfoFromDhcp.2 iSCSI.TargetName.2 iSCSI.TargetIp.2 iSCSI.TargetPort.2 iSCSI.BootLun.2 iSCSI.CHAPType.2 iSCSI.CHAPName.2 iSCSI.CHAPSecret.2 iSCSI.ReverseCHAPName.2 iSCSI.ReverseCHAPSecret.2
The RDCLI is designed to mount an ISO image file or DVD or CD drive to a remote IMM-based server. Before you start to invoke RDCLI, make sure that: v The remote IMM is connected to the network environment. v There is no other remote presence session opened through the RDCLI or IMM web interface. v The server has a virtual media key installed and the remote presence feature is enabled. Example: Type the following commands to mount an ISO image file or DVD or CD drive to a remote IMM-based server:
rdmount -s 192.168.1.12 d /dev/cdrom -l USERID -p PASSW0RD rdmount -s 192.168.1.12 d /home/install.iso -l USERID -p PASSW0RD rdmount s 192.168.1.12 d /dev/cdrom -l USERID p PASSW0RD w 90
If the mounting command is successful, a message stating that the mount operation is completed without error is displayed. Otherwise, a message stating that the mount operation has failed and the detailed reasons for the failure is displayed. Type -w 90 to switch the authentication port number to 90. The default port number is 80. Example: Type the following command to query existing mount sessions between the client operating system and the remote server:

rdmount q

If the command is successful, all available token values on the client operating system are listed in the following format:
"Token 507: drive path /home/install.iso, mounted to SP 192.168.0.1, by user USERID"
Note: The token value is a unique ID of an existing successful mounting record in the client operating system. If the command is not successful, the error message and reason for the failure are displayed. Example: Type the following command to unmount an ISO image file or DVD or CD drive that is already mounted to the remote system. In the command, the remote mount session has the token 507.

rdumount 507

If the command is successful, a message that the remote presence session is ended is displayed. If the command is not successful, the error message and reason for the failure are displayed.
Chapter 3. Command reference
This chapter describes the Advanced Settings Utility (ASU) commands.

Batch command

Use the batch command to queue ASU operations without any knowledge of the scripting capabilities of the operating system on which the ASU is running.
The syntax of the batch command is
asu batch batch_filename [-nx] [connect_options]
where batch_filename is the name of a file that contains a list of ASU commands. Notes: 1. If the optional -nx parameter is specified, the ASU performs the operation for node x, where x is the selected node in a multi-node system. x can be a number from 1 through 8. If the -nx parameter is not specified, the operation is performed on the primary node (node 1). 2. Do not specify the nx optional parameter in the batch file for any of the batched commands. 3. The connect options are defined for only IMM-based servers. The --host ip_address connect option is required if you connect remotely to the IMM. The --user user_id and --password password connect options are required only if the default user ID and password settings are changed in the IMM for either a local or remote LAN connection. The --user user_id and --password password connect options are not required if you are using the local KCS interface.
When you use the batch command on a batch file, the output that is sent to stdout and stderr is the collective output of all the commands in the batch file. The output of each command in the batch file is preceded by the command itself, surrounded by brackets ( [ ] ).
[command 1] output of command 1 [command 2] output of command 2
[command n] output of command n

The syntax of the createuuid command is:
asu createuuid UUID_setting_name [connect_options]
Notes: 1. The UUID_setting_name is usually defined as SYSTEM_PROD_DATA.SysInfoUUID. 2. To view the actual setting name, which can vary from server to server, use the show command to list the setting name that belongs to the SYSTEM_PROD_DATA group. To view the available groups, use the showgroups command. 3. The connect options are defined for only IMM-based servers. The --host ip_address connect option is required if you connect remotely to the IMM. The --user user_id and --password password connect options are required only if the default user ID and password settings are changed in the IMM for either a local or remote LAN connection. The --user user_id and --password password connect options are not required if you are using the local KCS interface.
To see the value that is set by the createuuid command, use the show command.
asu show SYSTEM_PROD_DATA.SysInfoUUID
The output of the show command is the new randomly generated UUID.
SYSTEM_PROD_DATA.SysInfoUUID=801a3b663e82b60104af001a64e50c94
The createuuid command and corresponding output are shown in the following examples. Command line:
asu createuuid SYSTEM_PROD_DATA.SysInfoUUID
Output: The command does not produce output. To see the generated UUID, use the show command.
asu show SYSTEM_PROD_DATA.SysInfoUUID SYSTEM_PROD_DATA.SysInfoUUID=801a3b663e82b60104af001a64e50c94

Delete command

Note: This command is for IMM-based servers only. Use the delete command to delete an instance of a setting. Note: Using this command to delete the instance of a setting that is a record key results in all other settings with the same instance number to be deleted.
The syntax of the delete command is
asu delete setting_instance [-nx] [connect_options]
where setting_instance is the name of an instance of a setting to delete. Use the command asu show all to show a list of available setting instances. Use the asu showvalues setting command to show a list of all values that are available for the setting.

Limitations

Settings can have a minimum number of allowed instances. The delete command does not allow you to delete an instance if doing so causes the number of instances to drop below the minimum number of allowed instances. To determine the minimum number of instances allowed, use the command:
asu showvalues --instances The output for each setting that can have instances will be displayed, along with the minimum and maximum number of allowed instances.
Also, deleting instances that are part of a record is allowed for only the record key setting. To determine whether or not a setting is part of a record, use the command:

The output of the set command when the v parameter is not specified is the setting name and the new value. When the v parameter is specified, the description of the setting is also shown. Setting with a single value without the -v parameter:
<setting>=<new value>
Setting with a single value with the -v parameter:
<setting>: <setting description> = <new value>
Setting with multiple values without the -v parameter:
<setting>=<new value1>=<new value2>=<new valueN>
Setting with multiple values with the -v parameter:
<setting>: <setting description>=<new value1>=<new value2>=<new valueN>
The set command and corresponding output are shown in the following examples. Command line:
asu set CMOS_CRTRequired Disabled
CMOS_CRTRequired=Disabled
asu set CMOS_DisketteA 1.44 MB 3.5\
CMOS_DisketteA=1.44 MB 3.5
asu set RSAIP_HostIPAddress1 192.168.0.100
RSAIP_HostIPAddress1=192.168.0.100
asu set RSAString_LoginId2 rsauser
RSAString_LoginId2=rsauser
Command line to set the boot order to be CD/DVD ROM, then diskette, and then Hard Disk 0:
asu set BootOrder.BootOrder "CD/DVD Rom=Floppy Disk=Hard Disk 0"
BootOrder.BootOrder=CD/DVD Rom=Floppy Disk=Hard Disk 0
To create a new record instance and set the record key setting: Command line:
asu set iSCSI.AttemptName.2 "MyAttempt2Name"
iSCSI.AttempName.2=MyAttempt2Name
Note: All other settings in this record (for example, iSCSI.LocalIp.2 and iSCSI.SubnetMask.2) are set to default values. To set the other settings for this instance in this record: Command line:
asu set iSCSI.LocalIp.2 "9.5.107.170"
iSCSI.LocalIp.2=9.5.107.170
Which is followed by the command line:
asu set iSCSI.SubnetMask.2 "255.255.255.0"
iSCSI.SubnetMask.2="255.255.255.0"

Show command

Use the show command to see the current value of one or more settings.
The syntax of the show command is
asu show [all | --group group_name | setting_name | --setlist name1.nameN | class] [-v] [-nx] [connect_options]
If no setting command modifier or class setting is specified, all settings and their current values are displayed. Notes: 1. If the optional all parameter is specified, all settings are displayed. 2. If the optional --group group_name is specified, only settings in the group group_name are displayed. 3. If the optional --setlist name1.nameN is specified, only the settings that are specified in name1.nameN are displayed. 4. If the optional class setting is specified, only settings that belong to the specific class are displayed. 5. If the optional -v parameter is specified, the output is verbose. 6. If the optional -nx parameter is specified, the ASU performs the operation for node x, where x is the selected node in a multi-node system. x can be a number from 1 through 8. If the -nx parameter is not specified, the operation is performed on the primary node (node 1). 7. The connect options are defined for only IMM-based servers. The --host ip_address connect option is required if you connect remotely to the IMM. The --user user_id and --password password connect options are required only if the default user ID and password settings are changed in the IMM for either a local or remote LAN connection. The --user user_id and --password password connect options are not required if you are using the local KCS interface.

Without the -v parameter:
<setting>: <setting description> { <location>[<extra location info>] } if <location> is CMOS, <extra location info> is of the form <byte offset>","<bit offset>","<number of bits> if <location> is SP, <extra location info> is of the form <SP dot byte 1>"."<SP dot byte 2>".". "."<SP dot byte n> if <location> is SP6, <extra location info> is of the form ">"<write command info> "<"<read command info> and <write command info> and <read command info> are of the form <read command byte>["@"<data offset>] ("."<command data>)*["|"<request data length>]
The showlocation command and corresponding output are shown in the following examples. Command line:
asu showlocation CMOS_SerialA
CMOS_SerialA=CMOS[70,00,03]
asu showlocation CMOS_SerialA v
CMOS_SerialA: Serial Port A { CMOS[70,00,03] }
asu showlocation RSA_Network1
RSA_Network1=SP[04.09.01.01.02]
asu showlocation RSA_Network1 -v
RSA_Network1: Network Interface 1 { SP[04.09.01.01.02] }

Showvalues command

Use the showvalues command to list all possible values for one or more settings. This is useful for finding the value parameter that is used for the set command.
The syntax of the showvalues command is
asu showvalues [all | --group group_name | setting_name | --setlist name1.nameN | --instances | class] [-v | -t] [-nx] [connect_options]
Notes: 1. If the optional all parameter is specified, all setting are displayed. 2. If the optional --group group_name is specified, only settings in the group group_name are displayed. 3. If the optional --setlist name1.nameN is specified, only the settings that are specified in name1.nameN are displayed. 4. If the optional class setting is specified, only settings that belong to the specific class are displayed. 5. If the optional -v parameter is specified, the output is verbose. 6. If the optional -t parameter is used, the output includes the raw values. 7. If the optional -nx parameter is specified, the ASU performs the operation for node x, where x is the selected node in a multi-node system. x can be a number from 1 through 8. If the -nx parameter is not specified, the operation is performed on the primary node (node 1). 8. The connect options are defined for only IMM-based servers. The --host ip_address connect option is required if you connect remotely to the IMM. The --user user_id and --password password connect options are required only if the default user ID and password settings are changed in the IMM for either a local or remote LAN connection. The --user user_id and --password password connect options are not required if you are using the local KCS interface. 9. If the optional --instances parameter is specified, only settings that can have instances are displayed. The minimum and maximum number of instances allowed for the settings is also displayed. For more information about instances, see Instances of settings on page 18.

IBM Taiwan product service contact information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd. Taipei, Taiwan Telephone: 0800-016-888

Appendix B. Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product, and use of those websites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the web at Copyright and trademark information at http://www.ibm.com/legal/ copytrade.shtml.

Some software might differ from its retail version (if available) and might not include user manuals or all program functionality.

Documentation format

The publications for this product are in Adobe Portable Document Format (PDF) and should be compliant with accessibility standards. If you experience difficulties when you use the PDF files and want to request a web-based format or accessible PDF document for a publication, direct your mail to the following address: Information Development IBM Corporation 205/AE. Cornwallis Road P.O. Box 12195 Research Triangle Park, North Carolina 27709-2195 U.S.A. In the request, be sure to include the publication part number and title. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Index A

accessible documentation 99 Advanced Settings Utility, using asu command 12 configuring Ethernet settings for Windows overview 13 configuring serial connection for Windows 2000 configuring settings in IMM-based server 15 connecting to IMM-based server 15 obtaining the ASU and patch files 9 operating system support 2 supported firmware 1 supported systems 6 unpacking ASU files for Linux 12 unpacking ASU files for Windows 11 using the ASU patches 10 assistance, getting 95 ASU files unpacking for Linux 12 unpacking for Windows 11
DHCP server, using 13 documentation format 99
Ethernet, configuring settings 14 13
firmware types supported 1

getting help 95

hardware service and support help, getting 95 96
baseboard management controller startup sequence settings 34 boot-order settings for IMM-based servers 36
IBM Support Line 96 IMM settings syntax 17 IMM-based server configuring settings 15 connecting ASU to 15 IPMI device driver support for Linux 8 for Windows 7 iSCSI configuration 37
classes of settings for ASU 23 command configuration applications immcfg 22 savestat 22 command connectivity options 27 command general options --help 32 -nx 29 bypass 28 dumptofile 28 showsptraffic 30 silent 31 command modifiers 25 command reference 41 command syntax 21 configuring Ethernet settings 13 serial connection 14 settings in IMM-based server 15 configuring Remote Supervisor Adapter settings configuring Ethernet settings 13 setting up communication with the ASU 13 connectivity options 27

IBM server memory upgrades
guaranteed compatibility | lifetime warranty | free technical support
Kingston delivers reliable memory designed specifically for IBM servers, complete with a lifetime warranty, 100-percent testing, guaranteed compatibility and free, 24/7 tech support. For added peace of mind, Kingston has signed a service agreement with IBM, and Kingston modules work with all of IBMs server diagnostic pre-failure warning software. KingstonCare completes the package with a free suite of service tools that includes service reimbursement, cross-ship RMAs and on-site spares. Model
BladeCenter HC10 (7996-xxx) BladeCenter HS21 (8853-xxx) BladeCenter HS21 XM (7995-xxx) BladeCenter JS21 (8844-xxx) BladeCenter JS22 Express (7998-61X) BladeCenter LS21 7971-xxx BladeCenter LS41 7972-xxx eServer xSeries 100 (8486-xxx) eServer xSeries 206 (NX82, NY82xxx) eServer xSeries 206m (8485, 8490-xxx) eServer xSeries 305 (NX73xxx) eServer xSeries 306m (8491, 8849-xxx) eServer xSeries 326m (7969-xxx) eServer xSeries 335 (NX76xxx) eServer xSeries 336 (NY37xxx) eServer xSeries 345 (NX70xxx) eServer xSeries 346 (NY40xxx) eServer xSeries 445 (NX7Rxxx) eServer xSeries BladeCenter HS20 (7981-xxx)

Linked Products

KTM2822K2/1G; KTM2822K2/2G; KTM2822K2/4G KTM5780/1G; KTM5780/2G; KTM5780/4G; KTM5780/8G KTM5780/1G; KTM5780/2G; KTM5780/4G; KTM5780/8G KTM2707K2/1G; KTM2707K2/2G; KTM2707K2/4G; KTM2707K2/8G; KTM2865/1G; KTM2865/2G; KTM2865/4G; KTM2865/8G KTM2759K2/2G; KTM2759K2/4G; KTM2759K2/8G KTM5861K2/1G; KTM5861K2/2G; KTM5861K2/4G; KTM5861K2/8G; KTM5861NCK2/1G; KTM5861NCK2/2G KTM5861K2/1G; KTM5861K2/2G; KTM5861K2/4G; KTM5861K2/8G; KTM5861NCK2/1G; KTM5861NCK2/2G KTM5148/2G; KTM5148/4G; KTM5149/2G; KTM5149/4G KTM4049/1G; KTM4049/256; KTM4049/512; KTM4053/1G; KTM4053/256; KTM4053/512 KTM5148/2G; KTM5148/4G; KTM5149/2G; KTM5149/4G KTM-X305/1G; KTM-X305/256; KTM-X305/512 KTM5148/2G; KTM5148/4G; KTM5149/2G; KTM5149/4G KTM3233/1G; KTM3233/2G; KTM3233/4G KTM5037/1G; KTM5037/2G; KTM5037/4G; KTM5037/512 KTM2865/1G; KTM2865/2G; KTM2865SR/4G; KTM3523/1G; KTM3523/512 KTM5037/1G; KTM5037/2G; KTM5037/4G; KTM5037/512 KTM2865/1G; KTM2865/2G; KTM2865SR/4G; KTM3523/1G; KTM3523/512 KTM5037/1G; KTM5037/2G; KTM5037/4G KTM2865/1G; KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM3523/1G; KTM3523/512

more >>

memory
Kingston your best source for
Kingston your best source for IBM server memory upgrades
System x3400 (7973, 7974, 7975, 7976-xxx) System x3455 (7984, 7986-xxx) System x3500 (7977-xxx) System x3550 (1913, 7978-xxx) System x3650 (1914, 7979-xxx) System x3650 T (7980-xxx) System x3655 (7985-xxx) System x3755 (8877-xxx) System x3800 (8865, 8866-xxx) System x3850 (8863, 8864-xxx) System x3850 M2 (7141, 7144-xxx) System x3950 (7363, 7366-xxx) System x3950 (8872, 8878-xxx) System x3950 M2 (7141-xxx) System x3950E (7364, 7367-xxx) System x3950E (8874, 8879-xxx)
KTM5780/1G; KTM5780/2G; KTM5780/4G; KTM5780/8G KTM2759K2/1G; KTM2759K2/2G; KTM2759K2/4G; KTM2759K2/8G KTM5780/1G; KTM5780/2G; KTM5780/4G; KTM5780/8G KTM5780/1G; KTM5780/2G; KTM5780/4G; KTM5780/8G KTM5780/16G; KTM5780/1G; KTM5780/2G; KTM5780/4G; KTM5780/8G KTM2865/1G; KTM2865/2G KTM2759K2/1G; KTM2759K2/2G; KTM2759K2/4G; KTM2759K2/8G KTM2759K2/1G; KTM2759K2/2G; KTM2759K2/4G; KTM2759K2/8G KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM5145/8G KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM5145/8G KTM2759K2/2G; KTM2759K2/8G; KTM2759SRK2/4G KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM5145/8G KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM5145/8G KTM2759K2/16G; KTM2759K2/2G; KTM2759K2/8G; KTM2759SRK2/4G KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM5145/8G KTM2865/2G; KTM2865/4G; KTM2865/8G; KTM5145/8G
For a complete list of supported systems, or more information on Kingston products and services, contact your dedicated Kingston representative.
2008 Kingston Technology Company, Inc. 17600 Newhope Street, Fountain Valley, CA 92708 USA. All rights reserved. All trademarks and registered trademarks are the property of their respective owners. Printed in the USA MKF-1203.6