IBM Advanced Settings Utility for Linux Version 3.60 (Build ID ASUT69K) Installation README File CONTENTS ________ 1.0 Overview 2.0 Installation and Setup Instructions 3.0 Configuration Information 4.0 Unattended Mode 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Known Issue 8.0 RDCLI Supported Hardware and Software 9.0 Disclaimer 1.0 Overview 1.1 This README file contains the latest information about installing the Advanced Settings Utility for DOS. 1.2 Limitations: N/A 1.3 Enhancements: N/A 1.4 Recommendations and Prerequisites for the Update: N/A 1.5 Dependencies - Definition files must be at version 2.4.1 or below. 2.0 Installation and Setup Instructions The procedure to install the Advanced Settings Utility for Linux is as follows: 2.1 Intalling from compressed tar file. 2.1.1 Copy the .tgz to a directory on the hard drive. 2.1.2 Run "tar zxf .tgz" where .tgz is the downloaded .tgz. 2.2 Intalling from rpm file. 2.2.1 Copy the .rpm to a directory on the hard drive. 2.2.2 Run one of the following commands: - To install if the package is not already installed > rpm -i .rpm - To install or update the package, removing other versions. > rpm -U .rpm .tgz is the downloaded .rpm. 2.2 Additional information. - UEFI-Compliant Systems The ASU 3.0 supports configuring settings in UEFI-compliant servers. The IMM has both an external LAN connection and an USB device that supports LAN-over-USB (internal LAN connection). The protocol used over the internal and external LAN are the same, which allows ASU to be used remotely or locally. ASU may also still communicate with the IMM locally via the KCS interface that was used on previous versions of ASU for BIOS-based Systems. In order for the local connection to work properly, the USB device has to be configured. The LAN-over-USB (CDC Ethernet) device driver must be loaded and activated on the Operating System. In order to load the device driver for LAN-over-USB device, there must be no network device on the system configured with an IP adress of 169.254.x.y other than the CDC Ethernet Device (the LAN-over-USB device). The file cdc_interface.sh is used to load a device driver for the CDC Ethernet Device. This file will be extracted along with asu in the same directory. Note: In order for ASU to automatically load the driver, the cdc_interface.sh file must be placed in the same directory as asu. - BIOS-based Systems For ASU version 2.1 and greater, ASU supports certificate generation using RSA/RSAII commands. As part of the rsa command "generate" a xml file is needed as an argument for the generate command. The xml file contains information that is needed at the time of certificate generation. When the extraction is done a template.xml is provided in the same directory where this readme is placed. In the template.xml, XXXX indicates fields where the user should imput the information for that particular item in the xml file. The items have min and max lengths which are defined in the xml file. If the item is defined as "Optional" and if it is not needed, the user should delete that item from the xml file before executing the generate command. The xml file supports the two types of RSA certificate generation: "Generate Self-Signed Certificate" and "Generate Certificate Signing Request (CSR)". Syntax of the asu commands are: ./asu generate RSA_Generate_SSL_Server_Certificate temp.xml ./asu generate RSA_Generate_SSL_Server_CSR temp.xml ./asu generate RSA_Generate_SSL_Client_Certificate temp.xml ./asu generate RSA_Generate_SSL_Client_CSR temp.xml 3.0 Configuration Information ASU 2.0(and higher) contains the RSA and BMC definition files(patches) already. Depending on the machine that you are running, BIOS CMOS definition file(patch) might also be present. To check what definition files(patches) are avaliable run "./asu patchlist". The patches that are available will be displayed. If the system does not have RSA, and the user issues any commands that would use the RSA an error message is presented to remove the RSA patch. To remove the RSA patch, the user should execute "./asu patchlist" to determine which patch # corresponds to the RSA patch. Execute the asu command "./asu patchremove #", where # is the patch number that corresponds to the RSA patch. Similar if the system does not have a BMC, the user would do the same steps as was describe to remove the RSA patch. If a BIOS CMOS definition file(patch) is not present and the operator needs this definition file(patch), then the operator needs to add it. The steps to add the BIOS definition file(patch) to asu: 3.1 Download/copy the definition file .exe to the same directory on the hard drive to which asu.exe was extracted. The BIOS definition file exe can be downloaded from the support download site for the selected machine/model. 3.2 Extract the definition file by running the exe at the command line. This will place the ".def" in the directory the exe is executed from. 3.3 Run "./asu patchadd .def" where .def is the .def extracted from the downloaded .exe. 4.0 Unattended Mode All ASU operations are command line based and don't wait for user input. As such, ASU can be scripted by using "batch" mode (see the Advanced Settings Utility User's Guide for more details) or any scripting facility of your operating system. 5.0 Web Sites and Support Phone Number 5.1 IBM Support Web Site: http://www.pc.ibm.com/support 5.2 IBM Marketing Web Site: http://www.pc.ibm.com/ww/eserver/xseries/ 5.3 If you have any questions about this update or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html. 6.0 Trademarks and Notices 6.1 IBM and the e(logo) are registered trademarks of International Business Machines Corporation. 6.2 U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Contract with IBM Corporation. IBM web site pages may contain other proprietary notices and copyright information which should be observed. 6.3 To view licenses in English supply the "--license" option to ASU. Additional licenses in other languages can be found in the License_Agreement_International.pdf file. This file is part of the ASU application package. The ASU application package is available for download from the Tools Center web site. 7.0 Known Issue 7.1 According to IMM mutinode design spec,Partition changes will fail if any of the systems specified in the change are powered on. These changes include: IMM.PartitionEnabled IMM.PartitionNodes So user may modify these values following these ways: 1. For non-blade system, user could change these two settings by ASU through Out Of Band method when the sytem is poweroff. 2. For blade system,it is not supported in OOB mode. So user can modify these two settings through AMM complex configuration. 8.0 RDCLI Supported Hardware and Software Beginning in ASU 3.60 the following additional RDCLI files are packaged in the RPM and linux tgz file. 8.1 Functional Prerequisite The target IMM-based system's remote disk function has already been enabled. 8.2 Supported Servers All IMM based rack systems. Note: Currently RDCLI does NOT support Blade IMM system. 8.3 Supported Operating Systems Linux SLES 10 and newer SLES Operating System as Client Operationg System. 8.4 Command line interface A) To perform a mount: rdmount {-s -d } [-l -p ] | -h -v Note: -s (required) The ip address of the IMM (service processor) on the target machine -d (required) The path on the client machine to the cd-rom or .iso file to mount -l (optional) Userid on the IMM to perform authentication with (default is USERID) -p (optional) Password on the IMM to perform authentication with (default is PASSW0RD) -h Display the command line help text -v Request verbose output. B) To query an existing successful mounting record: rdmount 每q C) rdumount has a very simple interface as follows: rdumount | -h Note: The ＆token＊ value is an unique id of an existing successful mounting record on the client Operating System. -h Display command line help text for the rdumount command. 8.5 Usage Example A) To mount a CD-ROM in the /dev/cdrom drive or an .iso file to a target system with an IMM ip address 192.168.0.1, using "USERID" as login id and "PASSW0RD" as login password: rdmount 每s 192.168.0.1 每d /dev/cdrom -l USERID 每p PASSW0RD rdmount 每s 192.168.0.1 每d /home/install.iso -l USERID 每p PASSW0RD Result: 1. Success: Tell user mounting is successful. 2. Fail: Tell user the command operation is fail. B) To query for the existing mount information on the local client: rdmount -q Result: 1. Success: List all available mounting information on this client system, in the format: "Token 507: drive path /home/install.iso, mounted to SP 192.168.0.1, by user USERID" 2. Fail: Tell user the command operation is fail. Note: "Token" is an unique id of an existing successful mounting record on the client Operating System. You will not be able to know the mounting record on another remote client system. C) To unmount a CD-ROM or .iso file with already known unique mounting record id 507: rdumount 507 Result: 1. Success: The mounting file will be unmounted from the remote IMM system. 2. Fail: Tell user the command operation is fail. 9.0 Disclaimer THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PANTENTS OR COPYRIGHTS.