* Systems Director Management Console Systems Director Management Console /Version 6.730.0 cumulative fix history and Readme/ Contents The information in this Readme contains fix list and other package information about the Systems Director Management Console. * Systems Director Management Console (SDMC) V6.730.0 Media <#1> * SDMC V6.730.0 Appliance <#2> o Terminology differences between SDMC and HMC <#2.1a> o Functional differences between SDMC and HMC <#2.1b> o General requirements <#2.2a> o Web browser requirements <#2.2b> o Restrictions and limitations <#2.3> o Known issues in SDMC V6.730.0 <#2.4> o Hardware configuration <#2.5> * SDMC supported Power Systems <#3> * Supported firmware and software <#4> * SDMC for Power Blades support <#5> * Useful References <#6> * Package Information <#7> o Hardware appliance <#7.1> o Software appliance <#7.2> o Mandatory Fix or PTF <#7.3> o SDMC version information <#7.4> * Installing the hardware appliance <#8> * Installing the software appliance <#9> * After the setup wizard is displayed <#11> * Installing mandatory SDMC fix MF53082 <#10> Systems Director Management Console (SDMC) V6.730.0 This readme information represents the recovery media for SDMC V6.730.0 Hardware Appliance (Product ID - 5765-MCH) or media for SDMC V6.730.0 Virtual Appliance (Product ID - 5765-MCV) along with the mandatory PTF MF53082. The hardware appliance base image can be ordered as PTF MF55752 on media only. The software appliance VMWare ova image can be downloaded or ordered as PTF MF54684 on media. This mandatory PTF is required. It is already installed from manufacturing on the Hardware Appliance, but must be installed as an update to the Software Appliance SDMC V6.730.0. SDMC V6.730.0 Appliance SDMC V6.730.0 provides Power Systems Management functionality similar to HMC V7R7.3.0 ------------------------------------------------------------------------ Terminology differences between SDMC and HMC SDMC introduces new synonyms for standard Power terminology to better align with the cross-platform nature of IBM Systems Director. For more details, refer to the following SDMC Infocenter article: Terminology differences between HMC and SDMC ------------------------------------------------------------------------ Functional differences between SDMC and HMC SDMC introduces some functional differences between SDMC and HMC. For more details, refer to the following SDMC Infocenter link: Comparing HMC and SDMC features Back to top <#ibm-content> ------------------------------------------------------------------------ General requirements * If you are also using an HMC to co-manage any systems, you must install the HMC V7R7.3.0 to keep the management consoles at the same functional level prior to attaching the SDMC to the managed system. * SDMC requires the managed system firmware to be at a supported level prior to attaching the SDMC to the managed system. Refer to Supported Firmware and Software <#4>. * When downloading updates from Fix Central, ensure that you specify "SDMC" as the Product Group and Product. * The supported maximum number of management connections (HMC and SDMC) per Server is two. * Supported deployment topologies include: o SDMC can manage zero or more POWER6 or POWER7 systems. o SDMC can manage an HMC which indirectly manages supported systems, including POWER5 systems. The SDMC can also manage supported systems directly. o An HMC and SDMC can co-manage the same POWER6 or POWER7 system. o Two SDMCs deployed redundantly can manage the same POWER6 or POWER7 systems. o Two SDMCs deployed in a high availability (HA) configuration can manage the same POWER6 or POWER7 systems. o A global IBM Systems Director can manage multiple HMC or SDMC systems that are indirectly managing Power systems. However, the advanced managers VMControl, Active Energy Manager and Network Control are not yet supported with SDMC. Back to top <#ibm-content> ------------------------------------------------------------------------ Web browser requirements * Supported web browsers are Microsoft Internet Explorer (version 7.0 and 8.0), and Mozilla Firefox (version 3.0, 3.5 and 3.6). Other versions of these browsers might work, but are not officially supported. The JavaScript language and cookies must be enabled. * If Firefox rejects a self-signed certificate and does not offer any option to add an exception directly in the alert box, you can use the following steps to add the exception: 1. Select Tools -> Options -> Advanced -> Encryption -> View Certificates to open the Certificate Manager panel. On this panel, the Servers tab should be selected and the Certificate Name for the Systems Director Management Console should be highlighted. 2. Click Add Exception to open the Security Exception panel. 3. Verify the information in the Location field, and then click Confirm Security Exception. *Internet Explorer* 1. Select Tools -> Internet Options 2. Select the Privacy tab, and then select 'Advanced' 3. If not checked, check 'Override automatic cookie handling' and check 'Always allow session cookies' 4. To handle First-party Cookies and Third-party Cookies, you can choose either block or prompt or accept. Prompt is preferred, in which case you are prompted every time a site tries to write cookies. It may be a little annoying, but it is the safe thing to do. Some sites need to be allowed to write cookies. *Firefox* 1. Select Tools -> Options. 2. Select the Privacy tab. 3. Select the 'Allow sites to set cookies' check box. 4. If you want to allow only specific sites, select 'Exceptions', and then you can add this SDMC to the list. Back to top <#ibm-content> ------------------------------------------------------------------------ Restrictions and limitations * SDMC does not support POWER5 servers. Refer to SDMC supported Power Systems <#3> for a list of currently supported servers. * SDMC does not support CEC concurrent maintenance on POWER6 systems. * SDMC and HMC dual management side-by-side requires the latest HMC version V7R7.3.0. Refer to Supported Firmware and Software. <#4> * SDMC supports accessing managed systems in two ways: o SDMC directly discovers managed systems via the service processor (FSP). o SDMC accesses managed systems by discovering the HMC or IVM that is attached to them. * SDMC does not support both scenarios for the same managed system. That is SDMC cannot be used to discover the managed system natively, and also discover an HMC/IVM that manages the same system. * For a list of supported LDAP servers, see the Systems Director Infocenter. * Installing Advanced Managers such as VMControl, Active Energy Manager, Network Control or using other IBM Systems Director add-in features, such as those that require additional driver downloads into IBM Systems Director, are not supported on the SDMC appliance. * DVD-RAM media is not supported as a dump or backup device. * Supported file system formats for backup/restore using a USB device are fat32, ext3, and ext4. * Hardware Inventory collection and transmission for IBM i partitions are not supported by SDMC in V6.730.0 release. That information will be missing from SDMC-generated inventory viewed on the electronic service agent Web site. This also implies that SDMC-created system plans will not contain any I/O devices such as disk drives, tape, DVD, etc., for IBM i virtual servers (partitions). Server level hardware inventory, including COD billing information, is sent to the electronic service agent Web site. * Copy dump to USB is not supported for dumps 4GB or greater. * Copy dump to remote server is not supported from the graphical user interface. Command line support is available. * Backup and restore for multiple consoles in an active/passive High Availability configuration is not supported. This only affects the active/passive High Availability configuration. Backup and restore is fully supported in the more common redundant management configuration. * Configuring the SDMC as a DHCP client is not supported. In the SDMC setup wizard, you will be able to configure a network interface as a DHCP client and obtain the address for the SDMC network interface automatically. * The size of hardware appliance backups can vary depending on the amount of appliance usage and the amount of time the appliance has been running since last boot. The minimum size of a backup is approximately 4 GB, while the maximum can be over 140 GB. It is recommended you use a 64 GB USB key, or external USB hard drive. * USB devices should not be plugged into the HW appliance while doing a reinstallation. * If you use the High Availability configuration wizard and y specify the optional "Network Status IP address, you must specify an IPv4 address. This same limitation applies if you use the "smcli configureHA" command and use the "- tiebreaker-addr" option to specify an IP address. If you specify an IPv6 address for the network status IP address in either of these cases, then High Availability Failover will not work correctly. Back to top <#ibm-content> ------------------------------------------------------------------------ Known issues in SDMC V6.730.0 This package has the following known issues. * Backup/Restore <#backup> * Guided Repair <#guided> * Install/Setup <#installsetup> * Miscellaneous <#miscellaneous> * Network <#network> * Refresh/Out of Sync <#refresh> * Updates (Firmware & HMC) <#updates> * User Management <#usermanagement> * Virtualization <#virtualization> /Known issues/ Description Workaround *Backup/Restore* When backing up to a USB device which does not support a minimum write speed of 5MB/s, SDMC pauses for several minutes and is unreachable during that time. Try using a different device or vendor. Use one of the below tested USB flash keys: - Memory Master 16 GB USB 2.0 Flash Drive P-FD16G-EF/MM -16Gig HP, Memorex, Datastick, and Scandisk -16GB Corsair Flash Voyager USB -Kingston 16Gb DataTraveler USB 2.0 Restore function does not work if you have not run the setup wizard and has rebooted at least once. Restore will work without running the setup wizard as long as the SDMC is not rebooted after installation. If you have rebooted the SDMC without running the setup wizard, then to restore you must either reinstall or run the setup wizard. Some USB keys are not recognized at boot. Removing and reinserting the USB key will cause detection. The Man page for the backup and recovery indicates that the previous copy of the SDMC backup will be removed. However, SDMC currently does not remove the previous backup copy. You can manually remove the previous backup copy if desired. *Guided Repair* Unnecessary steps involving removing UPIC cables from DCAs and BPDs during Repair & Verify when removing a 24" I/O enclosure instead of just disconnecting them. No action is required. If a repair operation is stopped on a panel with radio buttons and then later resumed, all radio buttons will now be enabled. Selecting a previously disabled button and continuing could lead to improper actions. Select a radio button that was enabled when the operation was stopped. During a repair operation, whenever a node activate or deactivate times out, the message "The %commandName for the %fruType at %locationCode did not complete." will be displayed. The inserts will not be filled in. If this message is displayed, the node activate or deactivate timed out. The activation and deactivation could have been finished after the repair operation timed out. Please check that the node activated or deactivated. When doing Prepare for Hot Repair operation, it will take several minutes for the next panel to be displayed while it is querying the node. None. After selecting 'Previous' button on certain repair panels, the same panel may be displayed again when the 'Next' button is selected. To proceed to the next panel, select the 'Next' button again. Do not attempt a PUBook Exchange using SDMC. If needed, use HMC to exchange a PUBook. *Install/Setup* Message not suppressed during ovftool deployment - Warning: No manifest entry found for: SDMC_xxxxx_xxx_xxxx-diskx.vmdk.## This message can be ignored. Startup on boot could have long delays, Director status remains "Starting" for up to an hour. Check that all interfaces have a link-up and that at least one interface has a valid configuration on the network. In the Setup Wizard, if the Clear Configuration button is used to reset a LAN adapter's configuration, properties previously selected for the adapter may subsequently show up when configuring another adapter. Workaround is to ensure default selections are correct if they are to be used If you reach the summary page of the setup wizard, you will be unable to clear LAN adapter configuration if you go back in the Wizard. Cancel the setup wizard, reboot the system, and then restart the setup wizard to reset the subnet mask. SDMC Version 6 Release 730 with MF53082 supports the United States English Keyboard only. Support for other keyboards will be provided in a future fix for V6.730. Use a US English keyboard layout, or contact support regarding the availability of a fix. *Miscellaneous* Keys are not set correctly when the command mkauthkeys is used with -g option. The workaround is to setup the migration key pair without using the "-g" option. mkauthkeys must be run on both management consoles (assuming one is SDMC) if they are to be paired for remote migration. Requesting access to a system fails. Verify your access password is correct. If the access password fails but discovery worked and the IP is not a DHCP IP, then rerunning discovery followed by retrying the access password may be needed to resolve the issue. The IBM Systems Director process on an SDMC may consume an entire CPU due to a problem in the web container if the client browser passes an invalid HTTP header. The server will need to be restarted with smshutdown -t now -r . Hardware appliance keyboard issues: 1. Numeric keypad is not working. 2. Caps-lock indicator doesn't light. 1.Workaround for the numeric keypad not working is: a. Press shift key and then the number keys on right side of keyboard b. Hold Shift key and press NumLock twice, then the number keys on the right side of keyboard would work. 2. None. If an SDMC-managed system is transitioned to IVM-managed, then later transitioned back to SDMC-managed, the system will go into a recovery state. The circumvention is to initialize the server, then recreate the partitions. When you perform a power-on with hardware discovery, the PS703 Falcon blade boots to standby. You can power-off and then do a normal boot after the hardware discovery. The Reset Other Management Console Connection task may not show another attached console if the Power system is powered off. Power on the host, then retry. If new SRCs are not present in the FSP, the lsrefcode command may produce error message: HSCL1400 An error has occurred during the operation to the managed system. Try the task again. No action is required. After you run a task from the SDMC Welcome Page, a new tab is open and it is not apparent how to get back to the Welcome Page without closing all the current tabs that are open. Click the "Welcome" Link on the left hand navigation at the top and it will re-open the SDMC Welcome Page. To anchor the Welcome Page in its own tab, click the "open in new tab" (diagonal arrow icon) in the upper right. Some columns such as Reference Code are not available in all views. Use the welcome screen view. Unable to close Message window by clicking on OK of the "Open Dedicated 5250 Console" task that is available under "Manage Virtual Servers" tasks menu. Click the cancel button instead of the OK button. Multiple selections do not work on user interfaces that use the dual tree chooser (e.g. Check for Updates, Customize User Permissions, etc). Select and add one at a time. When you remove a Power Unit from GUI (Remove) or CLI (rmsys), associated resource information may not be deleted from the backend database, preventing successful rediscovery and management. The workaround is to do the Security -> Revoke Access task prior to Remove for the Power Unit *Network* User cannot configure 2 or more DHCP servers with the same server IP or IP range. This is not currently supported in our current DHCP configuration file. Under Settings -> Network Configure task, if you want to configure an Ethernet to a DHCP Server, you should carefully choose an alternative DHCP IP range which has not been reserved by other Ethernet. The SDMC setup wizard, Network Configuration, Host and Gateway, Specify IP for Hostname selection always seems to default to the IP address on eth0 which is private IP address by convention. The default value should be the first configured interface for an open network. If the default IP is not correct (i.e., the private network), select the drop down to find the correct IP address for the public network. The setup wizard does not prevent you against defining an IP address for an interface that is already used somewhere else. This will cause the Director Agent Manager to fail registration and prevent SDMC from starting up. Workaround is to re-install and define interface IP addresses that do not conflict with the IP address already used on the network. When logged into the SDMC shell, the scp command fails to resolve hostname to IP if the first DNS is failing in /etc/resolv.conf. When using scp, if an IP/hostname is not resolved in /etc/hosts, ensure the first DNS entry in /etc/resolv.conf is functioning properly in order to resolve IP/hostname. No option available to add additional gateway beyond the default. No action is needed. In the Configure Network wizard, some settings may show incorrect current values if the back button is used. Use cancel button and restart. Remove operation for an unauthenticated host on the DHCP private network will succeed. However, the server will be rediscovered. Authenticate to the host and then perform the remove operation. Alternately, remove the server from the network. When using the Network Configuration wizard to modify an existing LAN adapter that's configured as a DHCP server, the gateway device ("Specify IP for Hostname") might inadvertently change to another adapter. Workaround is to check this setting whenever modifying a LAN adapter's settings to verify that it has not changed incorrectly. The Network Configuration wizard may not automatically reboot the SDMC appliance following changes. Workaround is to manually do so from the GUI or CLI. *Refresh/Out of Sync* If there are two or more users logged into the same SDMC instance at the same time, then only one of the users will see the dynamic data refresh on the SDMC Welcome Page. Workaround is to manually click the refresh button available below the navigator table. In some circumstances, user interface displays stale information and does not refresh automatically to reflect the correct status or state after an operation. Click to another area in the user interface and back again or logout and log back in to view the refreshed status. The "Reference Code" column does not display detailed indication of the progress being made in the initial connection process of a host. Instead, only scrolling dots are displayed No action is required. This only affects the initial connection sequence to a host. *Updates (Firmware & SDMC)* 'smcli importupd' from CDROM fails without '-s' option Run the command with '-s' option If updating the firmware on multiple systems at the same time, you could see a message 'Complete with Error' for the compliance sub-task of the install process. This message can be ignored. You cannot do a virtual server data backup on the same server during the firmware update. Virtual server data backup can be performed after the firmware update is completed. The SDMC GUI displays the firmware levels (Version) for the managed system when inventory is collected and viewed. The same feature is not available for the Power Units. View the firmware levels using the command line (smcli lslic -t syspower). When user updates latest firmware on POWER7 systems, install wizard for updates shows the following message "some updates might include installation options, or require that additional updates be installed. Review these options below." and "ATKUPD094W: The advanced options could not be retrieved for #####. The advanced options for the update are unavailable." This message can be ignored and no action needs to be taken by the user. User can continue with the install wizard. *User Management* SDMC fails to start and goes into error state if it is unable to contact the configured LDAP server. Verify the LDAP server is operational. Use CLI to remove or repair the LDAP configuration. After configuring LDAP: 1) LDAP user of smmgr group will not be able execute] 'lsldap','smstop;smstart' and 'chnetcfg' commands via SSH whereas local user can execute them 2)LDAP user of smmon group, cannot execute 'lsldap' command via SSH whereas local user can execute it. Run those commands with an LDAP user that belongs to smadmin group or a local user such as sysadmin. Unable to change SSL LDAP configuration between anonymous and non-anonymous binding using user interface. Use command line to remove the current configuration, then reconfigure: cfgldap -o r . Unable to view user password expiration setting in user interface. No action is required. No password expiration warning message is given when you log into the GUI. When a user whose password has expired attempts to log on, there are two problems: - The message does not indicate password expired: "Login failed. Check the user ID and password and try again. " - No option to change the expired password. Login through the command line to be prompted to change the user password after expiration. Unable to remove some user groups (inherited roles) from a user profile. Delete and recreate the user. Create User wizard and mkuser command will fail when apostrophe (') is used for description field. Don't use apostrophe for user account description. Unable to change user description. Delete and recreate the user. You cannot add or remove a role from a user account via chuser command. Use GUI interface (on left menu, go to Security -> Users, select the user and click Edit button). smcli lsuser incorrectly displays an internal user "ccfw" not available for login. The ccfw user should be ignored. Issues with using LDAP help. When using the LDAP configuration wizard, do not use the main (?) help function to access help content. Instead, use the Learn More links provided on specific pages to access help, and use the links within that help to access more detailed information that you might need to complete this configuration wizard. Incorrect help text for removing a user shows root authority is required. When using the command line interface to complete the Delete a user account task, you must be logged into the management console with smadmin authority, not as the root user as is currently stated in the help for this task. All users are implicitly a member of smuser group. This implies that all users inherit the SMUser role that allows basic operation such as viewing resources and properties for all resource groups. A feature that allows a user to be restricted to viewing only specific resources is being considered for a future release. Popup menu / task items may not appear within the scrollable window on the local console. To ensure all tasks are seen, always scroll down the task list to the bottom to force the window to dynamically scroll. *Virtualization* The following issue occurs on all systems with huge page capability, When a server is powered off and you go to 'Edit Host' panel, advanced tab to change requested huge pages from 0 to 1, the FSP indicates 1 huge page defined, but SDMC still indicates 0 requested. No workaround currently. This will be addressed in a future release. When the user tries to create a shared memory pool and the system does not have sufficient memory it would show an error message "There is insufficient memory on the system". The message does not show how much extra memory is needed to complete the operation if the user wants to keep the maximum memory size. Reduce the maximum pool size or actual pool size or release some memory from other inactive/stopped partitions. After the successful creation of the shared memory pool, the shared memory pool management page closes automatically instead of showing update, delete or close options. You can use Edit Host to view the memory pool properties subsequently. When the user tries to reduce the pool size and there is no lpar used entitled memory and the new size is smaller than the pool memory PHYP is using, the operation fails and the message doesn't tell the user why it fails. Use lshwres -r mempool to display the current pool memory used by PHYP and set the new size smaller than the value shown. The GUI also shows the "free memory in pool" and you can calculate the minimum new size by subtracting "free memory in pool" from "current pool size". When moving processors from a dedicated processor partition to a shared processor partition, the request often fails because the assigned virtual processors value for the shared processor partition is not large enough to accommodate the moved processors and there is no option to adjust it on the same command. Increase the virtual processors, then do the move or do a remove followed by an add. Incorrect error messages during dlpar add of VSCSI adapter "HSCL294C Dynamic add of virtual I/O resources failed: Slot 200 is not in the valid range. The valid range is 11 to 200". The error should read "...between 10 and 200" if the Server is POWER6. and "...between 1 and 200" if the Server is POWER7. Manage virtual server panels for physical I/O, network and storage adapter do not indicate if I/O is required or desired. Look at the last activated profile and then edit the profile to see the adapter settings. When the RMC is inactive for paging space partitions in the shared memory pool, the paging devices belonging to the paging space partitions is not displayed while trying to add them to the shared memory pool. You should check via command line if an RMC session is active for the paging space partitions. Unable to specify min/max or number of partial processing units in create virtual server wizard. To alter the default values used by create virtual server wizard, edit the profile after creation or use the manage virtual server task. Fails to send virtual storage network start/stop events on SNMP traps. No action is required. Back to top <#ibm-content> ------------------------------------------------------------------------ Hardware configuration Hardware appliance The SDMC Hardware Appliance is shipped with a 7042-CR6 system with feature code 0963. While this system is similar to an HMC, it is not the same, and the software cannot be installed on HMC hardware. Software appliance You can also provide your own hardware on which to install and run the SDMC software appliance. The SDMC software appliance requires: An IBM System x x86-based server with a minimum configuration of: * 2.53 GHz IntelŽ XeonŽ E5630, Quad Core processor * 4 virtual processors (NOTE: The underlying host should have at least 4 physical processor cores). * 6GB available memory (NOTE: The underlying host needs more than 6GB of physical memory). * 500GB of available storage. * One (1) or more network interfaces. * Hypervisor - one of the following options: o RHEL 5.5 or later, plus the latest yum updates for base and KVM (kvm-83-164.el5 recommended) virtualization o VMWare ESX4/ESXi 4 or later (ESXi level should be 4.01 to use USB) SDMC supported Power Systems Product Models Machine Type Supported by SW Appliance Supported by HW Appliance POWER 7 Model 795 9119-FHB X Model 770 HE 9179-MHB X Model 770 9117-MMB X Model 750 HPC 8236-E8C X X Model 750 8233-E8B X X Model 740 Express 8205-E6B X X Model 720 Express 8202-E4B X X Model 710 Express and 730 Express 8231-E2B X X PS704 7891-74X X X PS703 7891-73X X X PS702 8406-71Y + FC 8358 X X PS 701 8406-70Y X X PS 700 8406-71Y X X POWER 6 Model 595 9119-FHA X Model 570 9117-MMA X Model 570 9406-MMA X Model 560 8234-EMA X Model 550 8204-E8A X X Model 550 9409-M50 X X Model 520 8203-E4A X X Model 520 - SB 8261-E4S X X Model 520 9408-M25 X X Model 520 9407-M15 X X Model JS23/43 7778-23X X X Model JS22 7998-61X X X Model JS12 7998-60X X X Note that systems based on POWER5 processors are not supported by the SDMC, including POWER5 I/O Frames connected to a POWER6-based server. Back to top <#ibm-content> Supported firmware and software The firmware for a managed system should be at a supported level before the system is connected to the SDMC. The following table lists SDMC supported firmware and software levels. Supported POWER6 servers POWER7 servers *Operating System Levels* AIX AIX 6.1 TL5 plus SP1 or later AIX 6.1 Technology Level 6 plus SP1 or later AIX 7.1 Technology Level 0 plus SP1 or later IBM i IBM i Version 6.1 GA Level or later SLES SLES 11 SP1 GA Level or later plus latest updates RHEL RHEL 5.5 GA Level or later plus latest updates *Managed system firmware levels* (including Blades) 350_107 or later 730_031 or later for PS703 or PS704 and 730_035 or later for the rest *Virtual I/O Server* Any supported level, but the latest GA level is recommended: VIOS 2.1.3.10 FP23 or later VIOS 2.2.0.10 FP24 or later *Hypervisor* (software appliance only) The following hypervisors are supported: RHEL 5.5 or later, plus the latest yum updates for base and KVM virtualization Or VMWare ESX4/ESXi 4 or later (note: version 4.0.1 is required to use the USB support) *Hardware Management Console* HMC Version 7, Release 7.3.0 or later SDMC for Power Blades support A Power blade can be managed in the same way that a rack-mounted Power Systems server is managed from SDMC. That is, the blade server is managed directly through the Flexible Service Processor (FSP). By default, the FSP is not available on the network. From the AMM, select Blade Tasks -> Configuration -> Management Network Configuration. Enable the FSP on your network. For additional details, refer to Managing POWER blades in the SDMC Information Center. Back to top <#ibm-content> Useful references For more information on the SDMC, refer to the following: * SDMC Redbook * SDMC Developerworks forum * SDMC Developerworks Wiki * SDMC Information Center Package information /Hardware appliance/ Package Name Size Checksum Product ID DVD#1 - director_appliance-rhevhb-hypervisor-1.0.11.iso 207099904 11171 5765-MCH DVD#2 - SDMC_1119B_730_0512_2.iso 4614113280 46799 5765-MCH DVD#3 -SDMC_1119B_730_0512_3.iso 2930663424 59368 5765-MCH /Software appliance/ Package Name Size Checksum Product ID SDMC_1119B_730_0512.ova 7862179840 34656 5765-MCV SDMC_1119B_730_0512.tar.gz 7544010609 36469 5765-MCV NOTE: The software appliance is delivered on 2 DVDs. The files on the DVDs must be combined to create the appropriate install media (.ova or .tar.gz). For information on how to combine the files, see the README.txt file included on the DVD media. /Mandatory fix or PTF/ APAR # PTF # MB03506 MF53082 Back to top <#ibm-content> ------------------------------------------------------------------------ SDMC version information Run the *lsconfig -V* command to get version information. Before applying the mandatory PTF, the output of this command is: *"version= Version: 6 Release: 730 Service Pack: 0 SDMC Build level 1.Thu May 12 10:04:41 CST 2011 PSM Build Level 20110512.1 DPSM Build Level 20110512.1 ","base_version=V6R730 " * After applying the mandatory PTF MF53082, the output of this command is: *"version= Version: 6 Release: 730 Service Pack: 0 SDMC Build level 1.Thu May 12 10:04:41 CST 2011 PSM Build Level 20110607.1 DPSM Build Level 20110607.1 ","base_version=V6R730 " MF53082: Required fix for SDMC V6R730 (06-15-2011) * Back to top <#ibm-content> Installing the Hardware Appliance This installation process can take approximately 1.5 hrs. *Note*: The hardware appliance arrives pre-installed from manufacturing. Follow these instructions only if you need to reinstall the hardware appliance. 1. Insert DVD1 and boot from the DVD drive. The installer copies DVD1 onto the system. (Approximately 30 minutes) Follow these steps: 1. Select "Install SDMC", and then press Enter. 2. If SDMC was previously installed, you are asked if you want to erase all existing data on disk. Select [Y]es. 3. The installer lists the available disks to install the DVD. Select the appropriate device number corresponding to the drive to start the installation, for example, 0) /dev/sda (size : 5000107 MB) 2. After DVD1 is copied, press Enter when you see the "Press Enter to shutdown the system" prompt. This operation can take several minutes. If the screen power saver causes the screen to go blank, do not use the Enter key to wake up the screen. Instead use the Space bar. Otherwise, you could inadvertently power down the appliance. 3. After has system is powered off, turn the system back on and *_immediately_ remove DVD1 from the drive* to complete the installation. (Approx. 10 minutes) It is important to remove DVD1 as soon as the appliance is powered on to avoid a boot of DVD1 from the DVD device. 4. When prompted, insert DVD2, and then press Enter. 5. When prompted, insert DVD3, and then press Enter. After DVD3 is copied, the system reboots, and then you are prompted to configure the keyboard. This operation takes time. Do _NOT_ reboot the SDMC until the login prompt is displayed. 6. After the setup wizard is displayed in the console refer to After the setup wizard is displayed <#wizard> for the remaining setup steps. For more details, refer to Installing the SDMC hardware appliance in the SDMC Information Center. Back to top <#ibm-content> Installing the software appliance This installation process can take approximately 1.5 hrs. *Note*: The following directions are for installing SDMC on a VMWare virtual machine using the CLI ovftool. For information on installing SDMC on a KVM virtual machine, or using another VMWare mechanism, please see the following SDMC Infocenter article: http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp?topic=/dpsm/dpsm_installing/dpsm_installing_installing_configuring_hypervisors.html To accomplish the deployment, this system must have network access from the ovftool system to the target ESX server. OVA file Before you can install SDMC, you must assemble the OVA file from the parts found on the DVDs. Step 1. Combine DVDs into an installable OVA You need a separate x86 Linux or Windows system to run the *ovftool* command, and then deploy the SDMC appliance to the hypervisor. 1. Copy all files from the 1st disk (DVD 1) to a temporary directory 2. Copy all the files from the 2nd disk (DVD 2) to the same directory (from the previous step) 3. On Linux, from the temporary directory, set the execution permissions on the CreateSDMCova.sh command script. Run the script CreateSDMCova.sh to combine the parts chmod 755 ./CreateSDMCova.sh ./CreateSDMCova.sh 4. On Windows, from the temporary directory, run the CreateSDMCova.bat command. CreateSDMCova.bat CreateSDMova builds the OVA image based on the specification from the .ovf file. The resulting OVA file can be deployed using ovftool. Refer to the Deploying <#deploying> section. 5. Compare the checksum of the resultant ova against the files sum or md5sum (depending on which algorithm chosen) on DVD 1 Step 2. Installing the ovftool 1. Download and install the ovftool utility. Windows and x86 Linux versions are available from the VMwareŽ at this location * Open Virtualization Format Free registration for a VMWare account is needed for the first time user 2. Copy the OVA file to the machine where the ovftool is installed. For more information on how to install and use the ovftool see http://www.vmware.com/support/developer/ovf/ovf10/ovftool_10_userguide.pdf Deploying When you are ready to deploy, run the ovftool to deploy the driver. The ovftool command creates a VM instance on the target ESX server. 1. Run the following ovftool command (enter the command as a single line): ovftool --name=[name_of_ vm] --powerOn -ds=[name_of_datastore] [name_of_the_ova_file] vi://[user]:[password]@[name_of_the_esx_host] where *[name_of_ vm]* - Name for the virtual instance on which you deploy the driver *[name_of_ datastore]* - A datastore must be available in the esxserver. If you have only one datastore in the esx server, you can skip this option. The SDMC Software Appliance requires 490 GB of free disk space in the virtual machine datastore. While it is possible to use thin provisioning for the disks, it is not recommended. *Example* ovftool --name=myVM --powerOn -ds=VM_datastore ova_file_name.ova vi://root:passw0rd@destiny Note: Alternatively, you can follow the VMWare instructions to install an ova file by means of the VMWare Infrastructure Client. Disk progress should be indicated on the command line. 2. On the VMWare vSphere Client, you can also monitor the status of the task named "Deploy OVF template" 3. Power on the VM that was just deployed (if you did not select the power-on option during deployment). 4. After the file is deployed, you should see the setup wizard from the VMWare Client Console view. 5. After the setup wizard is displayed in the console refer to After the setup wizard is displayed <#wizard> for the remaining setup steps. Back to top <#ibm-content> After the setup wizard is displayed 1. The setup wizard prompts for a locale. Set the locale to en_US. English is the only language supported for this level of the driver 2. A License panel is displayed. You must accept the license to continue. 3. Leave the firewall setting to the default. 4. For the IBM Systems Director Agent Manager screen, enter the userid of your choice, along with a password. The IBM Systems Director agent user will be used in future SDMC functionality. It is not used in any functionality of the current level SDMC. 5. After the configuration is completed, click "Close". The remaining installation steps are then completed and the SDMC is started. 6. Finally, the wizard displays summary page. Click "Finish". 7. On the confirmation dialog, click "Continue". The initial startup of SDMC may take up to 30 minutes. Back to top <#ibm-content> Installing mandatory SDMC fix MF53082 *Note*: The hardware appliance is pre-installed with this mandatory fix. You only need to perform this step if you have re-installed the hardware appliance. Using SDMC with an Internet connection 1. Log in to the SDMC Console using the sysadmin credentials. 2. Select Inventory -> View and Collect Inventory in the left hand navigation area 3. From the displayed tab, choose "Browse" next to the Target systems dropdown box 4. From the Target systems table, select the target of Operating System type corresponding to the hostname of your SDMC 5. Select "Add", and then OK to return to View and Collect Inventory. 6. Select "Collect Inventory", use the defaults in the Task Launch Dialog, and then select OK. A message is displayed indicating that inventory collection has started. 7. Select "Display Properties", and then wait until Status is Complete. Close the tabs for Active and Scheduled Jobs and View and Collect Inventory. 8. Select Release Management -> Updates in the left hand navigation area, and then choose Check for updates. 9. In the Check for Updates displayed, expand the SDMC node under "Available update types". Select "All", then "Add", and then OK. 10. Use the defaults in the Task Launch Dialog, and then select OK. A message is displayed, indicating that check-for-updates has started. 11. Select "Display Properties", and then wait until Status is Complete. 12. Close the Active and Scheduled Jobs tab to return to the Check for Updates tab, or just switch to the Check for Updates tab. 13. Choose "Browse" next to the "Selected systems" dropdown box 14. In the Systems table displayed, select the target of Operating System type corresponding to the hostname of your SDMC 15. Select "Add", and then OK 16. Select "Show Needed Updates" 17. You should see the PTF MF53082 in the table showing the updates needed by your SDMC. Select this PTF, and then choose "Install" to bring up the Install Wizard. 18. Select "Next" in each page of the wizard until you reach the Summary page, and then select Finish. Keep all default selections unchanged, making sure "Automatically install missing required updates" is checked on the Options page. 19. A message is displayed indicating that update installation has started. Select "Display Properties", and then wait until Status is Complete. 20. Select Welcome in the left hand navigation area 21. Go to the Settings tab 22. Under the desired task, choose either Shut down or Restart IBM Systems Director Management Console. 23. Select OK in the popup dialog 24. Use the defaults in the Task Launch Dialog, and then select OK to restart the Appliance. Log out. 25. Upon reboot, your appliance will be at the latest level. Using Fix Central and manually downloading the fix 1. Go to the Fix Central website. 2. Select 'Power' as Product Group. 3. Select 'Firmware, SDMC and HMC' as Product. 4. Specify your Machine type-model and click 'Continue'. 5. Select 'SDMC Code. Obtain SDMC Update Images, Service packs, Interim fixes, and required Director updates.' and click 'Continue'. 6. Select '6.730.0' as the SDMC firmware release level and click 'Continue' 7. Select 'MF53082' and click 'Continue'. 8. Review the licenses and Select 'I agree'. 9. Select the way you want to obtain the package and click 'Continue'. 10. After the download is complete, copy the mandatory fix to your USB key and follow instructions below in section 9.2.1 Applying Mandatory Fix with USB Key Execute this procedure while running as user: sysadmin Software appliance users must ensure that the USB device is available to the SDMC virtual machine. The hardware appliance comes pre-installed with the mandatory fix. You only need to perform this step if you have re-installed the hardware appliance. 1. Attach the USB key to the appliance 2. Identify the mount point 3. Execute the command: lsmediadev *Sample result* device=/dev/cdrom,mount_point=/media/cdrom,type=1,description=CD/DVD device=/dev/vdh1,mount_point=/media/vdh1,type=3,description=USB flash memory device 4. Mount the USB key using mount_point from the previous command 5. Execute the command: mount /media/vdh1 6. Execute the command: ls /media/vdh1 Verify that you see the list of files you've copied previously. 7. Create an update directory and copy the USB contents to the update directory by running the following commands: mkdir -p updates cp /media/vdh1/ * updates/ umount /media/vdh1 8. Install the mandatory updates by executing the following commands: SYSNAME=`smcli lssys -t OperatingSystem -w "OSType=23"` echo $SYSNAME /(The result should be the hostname of your SDMC appliance)/ smcli collectinv -n $SYSNAME -p "All Inventory" -v smcli importupd -v /home/sysadmin/updates/ smcli installupd -n $SYSNAME -v -u MF53082 smshutdown -t now -r Back to top <#ibm-content>