File Name: dsa_portable_readme.txt ****************************************************************** | | | IBM(R) Dynamic System Analysis (DSA) Portable Edition, | | Version $$MAJORVERSION$$.$$MINORVERSION$$ | | | | (C) Copyright International Business Machines Corporation | | 2004, 2013. All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under | | "NOTICES" in this document. | | | | This readme file is provided only in English. You can | | obtain the latest version of the readme file from the IBM | | Support Web site. | | | ****************************************************************** CONTENTS -------- 1.0 Overview 1.1 Product overview 1.2 Prerequisites for systems running Linux 1.3 Compatibility with ServeRAID Manager 1.4 Compatibility with Network Virtual Teaming software 1.5 Compatibility with Service Processors 1.6 Compatibility with Some System 2.0 Running Dynamic System Analysis 3.0 Using DSA command-line options 3.1 Running DSA Diagnostics 4.0 Accessing and viewing DSA output 4.1 Naming convention used for output files and directories 4.2 Viewing a compressed collection file 4.3 HTML files created by DSA 5.0 Sending DSA output to IBM xSeries Service and Support 5.1 Sending DSA output via ftp 5.2 Sending DSA output via HTTPS 6.0 Collecting Remote System info via VMware ESXi 7.0 Collecting IPMI event of remote system 8.0 Using DSA with UpdateXpress 9.0 Known problems and workarounds 10.0 Support Web sites 11.0 Notices 12.0 Third-party license terms and conditions, notices and information 12.1 zlib software 12.2 boost software 12.3 linux real mode interface software 1.0 OVERVIEW ------------- This readme file provides information about IBM Dynamic System Analysis (DSA) Portable Edition for Linux. 1.1 Product overview --------------------- IBM DSA Portable Edition is a system information collection and analysis tool that is used by IBM xSeries(R) Service and Support personnel to aid in the diagnosis of system problems. DSA collects information about the following aspects of a system: o System configuration o Installed packages o Kernel Modules o Network interfaces and settings o Performance data and details for running processes o Hardware inventory, including PCI & USB information o IBM LightPath(TM) status o Service Processor status and configuration o Vital product data, firmware, and basic input/output system (BIOS) information o Drive Health Information o ServeRAID configuration o LSI RAID & Controller configuration o Event logs for the operating system, ServeRAID controllers, and service processors Additionally, DSA creates a merged log that includes events from all collected logs. Diagnostics information may optionally be collected by DSA. For more information, see "3.1 Running DSA Diagnostics" The system information is collected into a compressed XML file that can be sent to IBM Service. Additionally, you can view the system information through optionally generated HTML Web pages. For more information, see "5.0 ACCESSING AND VIEWING DSA OUTPUT." DSA Portable Edition is not installed on the target system. When run, DSA Portable Edition expands to a temporary directory, which is removed after DSA information collection is completed. DSA Portable Edition is designed to fit on removable media such as a CD or USB key. The removable media must be supported for use with the server on which you plan to run DSA Portable Edition. Server support list: x3100 M4 (2582) x3200 M2 (4367, 4368) x3200 M3 (7327, 7328) x3250 M2 (7657, 4190, 4191, 4194) x3250 M3 (4251, 4252, 4261) x3250 M4 (2583) x3300 M4 (7382) x3400 M2 (7836, 7837) x3400 M3 (7378, 7379) x3500 M2 (7839) x3500 M3 (7380) x3500 M4 (7383) x3530 M4 (7160) x3550 M2 (7946, 4198) x3550 M3 (7944, 4254) x3550 M4 (7914, 7383) x3620 M3 (7376) x3630 M3 (7377) x3630 M4 (7158, 7518, 7519) x3650 M2 (7947, 4199) x3650 M3 (7945, 4255, 5454) x3650 M4 (7915) X3650 M4 HD(5460) x3690 X5 (7147, 7148, 7149, 7192) x3750 M4 (8722, 8733) x3755 M3 (7164) x3850 X5 (7143, 7145, 7146, 7191) x3950 X5 (7143, 7145, 7146, 7191) iDataplex dx360 M2 (7321, 7323) iDataplex dx360 M3 (6391) iDataplex dx360 M4 (7912, 7913, 7918, 7919) Smart Analytics System (7949) HS22 (7870, 1936, 7809, 1911) HS22V (7871, 1949) HS23 (7875, 1929) HS23E (8038, 8039) HX5 (1909, 1910, 7872, 7873) Flex System x240 Compute Node (8737, 8738, 7863) Flex System x220 Compute Node (7906, 2585) Flex System x440 Compute Node (7917, 2584) Flex System x222 Compute Node (7916) Supported Server Options o Ethernet adapter Broadcom 1Gb Ethernet CFFh Expansion Card Broadcom 10Gb Ethernet CFFh Expansion Card for IBM BladeCenter Broadcom Netextreme II Ethernet Expansion Card (CIOv) for IBM BladeCenter 2/4 Port Ethernet Expansion Card (CFFh) for IBM BladeCenter NetXtreme II 1000 Express Quad port Ethernet Adapter NetXtreme II 1000 Express Dual Port Ethernet Adapter Broadcom 10Gb BaseT dual port NIC Broadcom Dualrunner/ Quad-Runner NetXtreme I Broadcom 1Gb 4 port Mezz Card Tier 1 Emulex 10GbE vNIC w/ BE3 Chipset Emulex 2-Port 10Gb Multi-function IO Adapter (CFFh) for IBM BladeCenter (vNIC) Emulex 10Gb 4 port Mezz card with FCoE/iSCSI key for System X Tier 1 Emulex 2+2 10Gb (CFFh) for IBM BladeCenter (vNIC) Emulex Dual Port 10GbE SFP+ Embedded Adapter Emulex Virtual Fabric Adapter II for HS23 iSCSI and FCoE upgrade IBM NetXtreme II 1000 Express Ethernet Adapter Intel 10GB SFP+ NIC Intel X540-T2 Dual Port 10GBase-T Adapter for IBM System x Mellanox ConnectX-2 Dual Port 10GbE Adapter for IBM System x Mellanox ConnectX-3 Dual Port QDR/FDR10 Mezz Card Mellanox 2-port 10Gb Ethernet Expansion Card (CFFh) Mellanox FDR14 Connect X3 Mezz card Mellanox FDR IB Dual Port Mellanox ConnectX-3 FDR VPI IB/E Adapter Mellanox ConnectX-3 10 GbE Adapter Mellanox IBM Flex System EN6132 2-port 40Gb Ethernet Adapter IBM Flex System IB6132 2-port FDR Infiniband Adapter IBM Flex System EN4132 2-port 10Gb Ethernet Adapter o Fibre Channel adapter Emulex 4G FC exp. card Emulex 4G SFF FC exp. Emulex 4Gb/s FC PCI Express HBA (lpe11000/lpe11002) Emulex 4Gb/s FC PCI-X 2.0 HBA (lp11000/lp11002) Emulex 8Gb FC Single-port HBA for IBM System x Emulex 8Gb FC Dual-port HBA for IBM System x Emulex 10Gb/s Fibre Channel over Ethernet Dual Channel Converged Network Adapter Emulex PCI-e Gen2.0 Dual Port 10Gb NIC Emulex 2-Port 10Gb Multi-function IO Adapter Emulex 16Gb FC Single/Dual-port HBA Emulex 8Gb FC Mezz card Emulex IBM Flex System FC5052 2-port 16Gb FC Adapter Emulex IBM Flex System FC5054 4-port 16Gb FC Adapter QLogic 4G/8G FC CFF exp. card QLogic 4G/8G SFF FC exp. card QLogic 2-Gbps Fibre Channel HBA QLogic 4G and 8G FC single port HBA QLogic 4G and 8G FC dual port HBA QLogic iSCSI PCIe HBA QLogic iSCSI PCIe dual port HBA Qlogic 10Gb FCoE Dual Port Qlogic 10GbE CFFh DC Qlogic 8Gb FC 2 port mezz card Tie 1 for IBM Flex System QLogic Dual Port 10GbE SFP+ Embedded Adapter for IBM System x Qlogic 8200 Dual Port 10GbE SFP+ Adapter Qlogic IBM Flex System FC5172 2-port 16Gb FC Adapter Qlogic 10Gb ASIC Update Qlogic 16Gb FC HBA Brocade 4 Gb FC Single-port HBA Brocade 4 Gb FC Dual-port HBA Brocade 8Gb FC Single-port HBA Brocade 8Gb FC Dual-port HBA Brocade 10Gb CNA Brocade 10Gb Dual-port CNA Brocade 2-port 10Gb Converged Network Adapter Brocade 16Gb FC 2 port Mezz Card Tier 2 Brocade 16Gb FC Single/Dual-port HBA Brocade 16Gb FC Quad Port IBM SAS HBA controller LSI 1068 SAS HBA o Network adapter IBM 10 GbE PCIe SR Server Adapter IBM NetXtreme II 10 GigE Express Fiber SR Adapter Intel PRO/1000 PT Dual Port Server Adapter (no diagnostic support) Intel PRO/1000 PT Quad Port Server Adapter (no diagnostic support) Intel PRO/1000 PF Server Adapter (no diagnostic support) Intel QuadPort Ethernet Server Adapter (no diagnostic support) CFFh Intel Ethernet Adapter (no diagnostic support) Intel 10GB SFP+ NIC Intel X540-T2 Dual Port 10GBase-T Adapter for IBM System x Intel x520 Dual Port 10GbE SFP+ Embedded Adapter Intel X540 Dual Port 10GBaseT Embedded Adapter o RAID adapter Adaptec IBM ServeRAID 6i + Adaptec IBM ServeRAID 7k Adaptec IBM ServeRAID 7t Adaptec IBM ServeRAID 8i, 8k, 8k-l and 8s LSI 12Gb RoMB with Flatwood-e on the planar LSI MR 10is LSI IR 1078, 1064, 1064e and 1068e LSI MegaRAID 8480 LSI ServeRAID MR 10i, 10ie, 10is, 10k and 10m LSI ServeRAID M1015, M5014, M5015 and M5025 LSI ServeRAID M1110, M1115, M5016, M5110, M5110e, M5120, M5115 and M5210 LSI ServeRAID H1110, H1135 LSI ServeRAID M1100 Upgrade, M5100 Upgrade LSI ServeRAID B5015 LSI RAID 0//10 FDE SAS-2 6GB LSI ServeRAID C105 Shikra, IBM Flex System Storage Mezzanine Expansion (SME) LSI N2115 SAS/SATA HBA LSI N2125 SAS/SATA HBA LSI N2126 SAS/SATA HBA LSI N2215 SAS/SATA HBA Adapter LSI 300GB MLC Option Bulk LSI 600GB MLC Option Bulk LSI 800GB MLC Option Bulk LSI 300GB SLC Option Bulk o Tape drive IBM DDS5 36/72 SCSI IBM DDS5 36/72 USB IBM DDS5 36/72 SATA IBM DDS6 80/160 USB IBM LTO2 HH 200/400 SCSI IBM LTO2 FH 200/400 SCSI IBM LTO3 HH 400/800 SAS IBM LTO3 FH 400/800 SCSI IBM LTO4 HH 400/800 SAS IBM LTO5 HH 400/800 SAS IBM VS160 tape drive IBM GoVault tape drive IBM RDX 160/320/500 GB External/Internal USB 3.0 Drive Low Cost HH LTO 6 SAS Tape Drive External Tape Drive HH SAS LTO 6 o Daughter card cKVM Daughter Card for IBM BladeCenter LSI BR10i, BR10ie, BR10il o BPE-4 o GPU nVIDIA Quadro (4000, 5000, 6000, 600)] Nvidia Quadro K600, K2000, K4000, K5000 GPU nVIDIA Tesla (M2090, M2090update, X2090, X2090Update,K20,K20X) nVIDIA "Gemini" Kepler GPU (K10) nVIDIA VGX K1 nVIDIA VGX K2 Intel Xeon Phi 5110P Intel Xeon Phi 7120P Adapter o Storage Fusion IO 640GB High IOPS MLC Duo Fusion IO 1.2TB High IOPS MLC Duo Fusion IO 2.4TB High IOPS MLC Duo Operation System support list: [SUSE] SuSE Linux Enterprise Server (SLES) 10 (Up to SP4) (x86 & x64) SuSE Linux Enterprise Server (SLES) 10 with Xen (Up to SP4) (x86 & x64) SuSE Linux Enterprise Server (SLES) 11 (Up to SP3) (x86 & x64) SuSE Linux Enterprise Server (SLES) 11 with Xen (Up to SP3) (x86 & x64) SuSE Linux Enterprise Real Time 10 AMD64/EM64T [Red Hat] Red Hat Enterprise Linux (RHEL) 6 (Up to U4) (x86 & x64) Red Hat Enterprise Linux (RHEL) 5 (Up to U9) (x86 & x64) Red Hat Enterprise Linux (RHEL) 5 (Up to U9) with Xen (x86 & x64) Red Hat Enterprise Linux (RHEL) 4 (Up to U9) (x86 & x64) [VMware] VMware ESX Server 4.0 (Up to U3) VMware ESX Server 4.1 (Up to U3) VMware ESXi 4.0 (Up to 4.0 U3) (via --vmware-esxi option only) VMware ESXi 4.1 (Up to 4.1 U3) (via --vmware-esxi option only) VMware vSphere Hypersivor 5.0 (ESX5) (Up to u2) (via --vmware-esxi option only) VMware vSphere Hypersivor 5.1 (ESX5) (Up to u1) (via --vmware-esxi option only) Note: o RHEL5 x64 build is used for VMware ESX Server 4.x console. 1.2 Other prerequisites for systems running Linux ---------------------------------------------------- DSA requires above 250MB of available memory during the data collection process. The amount of memory required for this process depends on the size of the logs being collected from the system. To view the information that is collected by DSA, you must use Mozilla 1.4.0 or greater, or Firefox 1.04 or greater In order to display the DSA data, 30 to 100MB of available memory is required. The amount of memory required depends on the size of the logs being viewed. In order to collect SCSI & USB device information, including diagnostics, the "sg" driver must be loaded. Run "lsmod" and verify that "sg" is loaded before running DSA. If it is not loaded, run "modprobe sg". In order to collect Broadcom(TM) Ethernet firmware levels, the Broadcom(TM) NetXtreme Gigabit Ethernet Drivers must be installed. The tg3 driver provided by default in current Linux distributions does not export this information. These drivers are available for download from the IBM Support website at: http://www.ibm.com/support In order to collect LSI Logic(TM) 1020/1030 SCSI Controller & RAID information, the "mptctl" driver must be loaded. Run "lsmod" and verify that "mptctl" is loaded before running DSA. If it is not loaded, run "modprobe mptctl". In order to collect Emulex HBA information, emulex driver and utility (corekit) must be installed. Run "lsmod" and verify that "lpfc" and "lpfcdfc" is loaded before running DSA. In order to collect Service Processor logs, configuration, and environmental data the appropriate Service Processor driver must be installed. These drivers are available from the IBM Support website. DSA requires libcurl to be installed in order transfer data collections to the IBM Support site via FTP. Use of the UpdateXpress comparison analysis feature requires that an Internet connection be available for the system on which the analysis is performed. Notes: o The UpdateXpress comparison analysis feature will only support System Firmware comparisons including BIOS, Diagnostics, and Service Processor. Device drivers will not be compared in this release, due to limitations with UpdateXpress. That it is strongly recommended to have Service processor Drivers installed Prior to running DSA. This Provide IBM with more hardware logs. BMC: drivers are IPMI device drivers with IPMI mapping layer RSA 2: IBM Remote Supervisor Adapter II Server Software See system doc for older systems In order to collect ServeRAID info of ServeRAID controller 7t,8i,8k- l,8k,8s on Red Hat5 and Sles11 OS, user needs to insall libstdc++.so.5 on Red Hat5 and Sles11 platform. Notes: Since ServeRAID tool - arcconf is 32bit, user needs to install libstdc++.so.5 32bit on Red Hat5 and Sles11 64bit platform. 1.3 Compatibility with ServeRAID Manager Logs ----------------------------------------- Preboot DSA will collect configuration data from the following ServeRAID controllers on supported server models. However, ServeRAID Manager logs will not be collected. o ServeRAID 4,5,6,7k o ServeRAID-7t SATA RAID o ServeRAID-8i, 8k and 8k-l 1.4 Compatibility with Network Virtual Teaming software ----------------------------------------- DSA Portable Edition is supported for use with the following Network Virtual Teaming software: o Linux Bonding versions 2.4.1, 2.6.0, & 2.6.1 1.5 Compatibility with Service Processors ------------------------------------------ Environmental data is available from servers which have an Integrated Management Module (IMM), Remote Supervisor Adapter 2 (RSA2) , Remote Supervisor Adapter (RSA) or Integrated System Management Processor (ISMP) . In all cases appropriate support software must be loaded and running. 1.6 Compatibility with Some System ------------------------------------------ The following machine types have not been fully verified by IBM test for complete DSA operation . All major functions have been tested and confirmed as available. 2.0 RUNNING DYNAMIC SYSTEM ANALYSIS ------------------------------------ Complete the following steps to run DSA Portable Edition. Note: User should log in as "root" in order to execute DSA. 1. At a linux shell prompt: 2. Type the name of the DSA Portable Edition executable. 3. (Optional) Type DSA command-line options following the executable file name. For more information, see "3.0 USING DSA COMMAND-LINE OPTIONS." The executable extracts the DSA program files into temporary disk space on the server as defined by the TMP system variable in the Linux environment. DSA will then execute and start the collection process. When DSA is completed, the DSA program files are deleted from temporary disk space. Note: o In order to execute DSA, you need to make sure there is sufficient disk space (>300M)in the directory defined by the TMP variable for the DSA Portable Edition to expand the files. Otherwise DSA is not able to complete successfully. If you ran DSA without any options, DSA collects information into one compressed XML file that can be sent to IBM Service. For information about where this file is created, see "5.0 ACCESSING AND VIEWING DSA OUTPUT." For information about sending the file to IBM Service, see "6.0 Sending DSA output to IBM Service and Support." Note: o DSA Portable Edition for Linux does not execute on a VMFS folder. o Use Portable Edition for Red Hat Enterprise Linux 5 x64 build on VMware ESX Server 4.x. o DSA only executes on the VMware service console and it does not support execution on any guest operating system on virtual machines. One example to run DSA Portable Edition under Linux: cp /tmp chmod +x cd /tmp ./ 3.0 USING DSA COMMAND-LINE OPTIONS ----------------------------------- The command-line syntax in this document uses the following conventions: o Options are shown delimited with a hyphen (-). o Options are shown as lowercase, but are not case-sensitive. o Variables are shown in angle brackets. DSA has the following command-line options: Options: -?, -h Display help for DSA command-line options. -b Run in batch mode. --chkupd [--proxy-address=] [--proxy-port=] [--proxy-user=] [--proxy-password=] Detect if there are available DSA update(s) on the internet. This checks for System Enablement Pack(s). A different version of DSA may be available for your system at: http://www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-DSA&brandind=5000008 -d Create specified directory and place DSA output files in the specified directory rather than in the default location, which is /var/log/IBM_Support. -diags Execute all non-destructive diagnostic tests. --disable-imm-lan Take down USB Over Lan interface after running DSA. -dumpxml Write the DSA .xml.gz file after each plugin runs. --extract Extract DSA executable files into a designated directory (Use /collectall to launch DSA) -f Collect the full ISMP log. -html Specify HTML output directory. -i Read input from rather than collecting data from the local server. -ibmid Users provides their IBM Identifier. Work with -upload. --ipmi-lan Collect IPMI log via Out-Of-Band mode. -l Display license and exit. --no-ipmi-lan This option is used to skip DSA data collection for IMM when running dsa, USB Over Lan state is kept unchanged. -r Run the CIM difference engine comparing the collected or specified (via -i) data to this file. -t Transfer collected data to IBM Service & Support w/o arguments. In the other side, you could upload to your own ftp server. Example: -t username:password@ftphost/path/ -text Create TEXT output files. --update [--proxy-address=] [--proxy-port=] [--proxy-user=] [--proxy-password=] Acquire available DSA update(s) from the internet. This downloads System Enablement Pack(s). A different version of DSA may be available for your system at: http://www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-DSA&brandind=5000008 --update_arch [32][64] This option is used with the option "--chkupd" or "--update" to specify OS architecture. --update_m [XXXX] This option is used with the option "--chkupd" or "--update" to specify machine type. XXXX is 4 digital number of machine type. --update_os [windows][rhel3][rhel4][rhel5][sles9][sles10][sles11][vmware3.5][vmware4.0][vmware5.0] This option is used with the option "--chkupd" or "--update" to specify OS type. -upload Upload DSA output to SRSP and ISP by ecc common client C++ API. -ux [--proxy-address=] [--proxy-port=] [--proxy-user=] [--proxy-password= Compare the installed and latest version of firmware levels. -v Create HTML output files. --vmware-esxi <[userid]:[password]@[IP]> Retrieve system information from the remote target system loaded with VMware Embedded Hypervisor. -x Do not create a compressed XML file. Note: All options must be separated with one or more spaces. For example, to run DSA and generate HTML output files that can be viewed with a browser, run this command: -v To run DSA and create HTML output files in the directory /usr/foo/DSA_Output, run this command: -v -d /usr/foo/DSA_Output 3.1 Running DSA Diagnostics --------------------------- Use the -diags option to execute diagnostics during the DSA collection process. This option will execute all of the non-destructive diagnostic tests that are included with DSA. 3.2 Running DSA Features on Demand (FoD) Activation Key management ----------------------------------------------------------------- DSA also provides a command-line interface for Features on Demand (FoD) activation key management. This interface (fod) is executed followed by subcommands after DSA execution program. Execution may be controlled via the subcommand and command-line options. All command-line switches are case-insensitive. 3.2.1 Subcommands ----------------- The command-line interface (fod) has following subcommands: Common Subcommands: ------------------- display_available_fod This subcommand is used to get and dislpay the available FoD key(s) for a key repository (IMM, CMM, or IOM/Switch). The available FoD key(s) information can be got only if Internet is available. download_fod_key This subcommand is used to acquire and download the activation key from an IBM website (KMS). install_fod_key This subcommand is to install activation key(s) from user specified location (such as removable media) to key repository (IMM, CMM, or Switch). Specifc Subcommands for Key Mgmt. on IMM: ----------------------------------------- export_imm_uid This subcommand is used to export the unique identifier(s) of FoD feature(s) to a file saved in DSA output path, then can save to removable media. report_imm_active_fod This subcommand is to report inventory information of installed activation key(s) on IMM repository. install_imm_fod This subcommand is to download and install activation key(s) to IMM repository. uninstall_imm_fod This subcommand is to uninstall specific activation key(s) from IMM repository. Specifc Subcommands for Key Mgmt. on CMM: ----------------------------------------- report_cmm_active_fod This subcommand is to report inventory information of installed activation key(s) on CMM repository. install_cmm_fod This subcommand is to download and install activation key(s) to CMM repository. uninstall_cmm_fod Specifc Subcommands for Key Mgmt. on Switch: -------------------------------------------- report_switch_active_fod This subcommand is to report inventory information of installed activation key(s) on IOM/Switch install_switch_fod This subcommand is to download and install activation key(s) to CMM repository. uninstall_switch_fod This subcommand is to uninstall specific activation key(s) from IOM/Switch repository. 3.2.2 Options ------------- The command-line interface (fod) has following options for those subcommands: Options: --help Display help for fod interface or subcommand usage --device This option is used to specify the target key repositroy. The supported key repository: IMM, CMM, Switch. --ibmid This option is used to specify the credential IBM ID for the interactive authorization by IBM website (KMS). --host This option is used for the device interface connection to remote key repository, default is local IMM device. The default port is "5989". --mt This option is used for the machine type of key repository device (IMM, CMM, Switch). --uid This option is the unique identifier information of the FoD feature. [--authcode] This option is used to specify IBM authorization code. This option is optional. Once this option is used, a key generation will be performed by KMS. --keyfile This option is used to specify a single activation key file. --sftp or --tftp This option is used to specify the sftp/tftp server for snmp interface --community This option is used to specify the community for snmpv1v2, default: public. [--authproto] This option is used to specify the authorization protocol for snmpv3, default: No auth. This option is optional. [--privproto] This option is used to specify the privacy protocol for snmpv3, default: No privacy. This option is optional. [--privpasswd] This option is optional switch to specify the privacy password for SNMPv3. This option is optional. --keyid This option is used to specify the activation key ID returned from report command. If keyid is "all", will uninstall all keys from key repository. Note: All options must be separated with one or more spaces. 3.2.3 The Usage of the Subcommands and Options ---------------------------------------------- The usage of the FoD interface is : fod [Options] Subcommands Options: -- --help Display help for DSA FoD usage. display_available_fod --help Display help for subcommand display_available_fod usage. --device --ibmid --host --mt Dislpay the available FoD key(s). download_fod_key --help Display help for subcommand download_fod_key usage. --ibmid --uid [--authcode] --mt Acquire and download the FoD key(s). install_fod_key --help Display help for subcommand install_fod_key usage. --keyfile --device [--host] [--sftp or --tftp] [--community] [--authproto] [--privproto] [--privpasswd] Install FoD key(s) from user specified location to key repository (IMM, CMM, or Switch). export_imm_uid --help Display help for subcommand export_imm_uid usage. report_imm_active_fod --help Display help for subcommand report_imm_active_fod usage. [--host] Report inventory information of installed activation key(s) on IMM. install_imm_fod --help Display help for subcommand install_imm_fod usage. --ibmid --uid [--authcode] --mt [--host] Acquire and install FoD key(s) to IMM. uninstall_imm_fod --help Display help for subcommand install_imm_fod usage. --keyid [--host] Uninstall specific FoD key(s) from IMM . report_cmm_active_fod --help Display help for subcommand report_cmm_active_fod usage. --host Report inventory information of installed activation key(s) on CMM. install_cmm_fod --help Display help for subcommand install_cmm_fod usage. --ibmid --uid [--authcode] --mt --host Acquire and install FoD key(s) to CMM. uninstall_cmm_fod --help Display help for subcommand uninstall_cmm_fod usage. --keyid --host Uninstall specific FoD key(s) from CMM. report_switch_active_fod --help Display help for subcommand report_switch_active_fod usage. --host --sftp[or --tftp] --community [--authproto] [--privproto] [--privpasswd] Report inventory information of installed activation key(s) on Switch. install_switch_fod --help Display help for subcommand install_switch_fod usage. --ibmid --uid [--authcode] --mt --host --sftp[or --tftp] --community [--authproto] [--privproto] [--privpasswd] Acquire and install FoD key(s) to Switch. uninstall_switch_fod --help Display help for subcommand uninstall_switch_fod usage. --keyid --host --sftp[or --tftp] --community [--authproto] [--privproto] [--privpasswd] Uninstall specific FoD key(s) from Switch. For example, to run DSA FoD and display the fod interface usage, run this command: fod --help To run DSA FoD subcommand install_switch_fod and install FoD key(s) to Switch, run this command: fod install_switch_fod --keyid --host --sftp[or --tftp] --community [--authproto] [--privproto] [--privpasswd] Note: All options must be separated with one or more spaces. 4.0 ACCESSING AND VIEWING DSA OUTPUT ------------------------------------- By default, DSA output is created in the /var/log/IBM_Support directory. When DSA is run with no command-line options, it creates only a compressed XML file in the IBM_Support directory. When DSA is run with the -v option, it creates a subdirectory that contains HTML files that you can view with a Web browser. Regarding CPU information, the information of physical processors is shown under: - Hardware Inventory -> Processor The information for logical processors is shown under: - Hardware Inventory -> Other Devices NOTE: o With hyper-threading turned on there will be more logical processors shown than physical processors. 4.1 Naming convention used for output files and directories ----------------------------------------------------------- DSA uses the following naming convention for compressed XML files and for subdirectories that it creates: __-