The information in this Readme contains fix list and other package information about the Systems Director Management Console.

• SDMC Version 6 Release 730 Service Pack 2
• List of fixes
• Known issues
• Additional information
• Installation

Systems Director Management Console (SDMC) V6.730 SP2

This package includes fixes for SDMC Version 6 Release 7.3.0. You can reference this package by APAR MB03580. This service pack should be installed on top of SDMC Version 6 Release 7.3.0 images. APAR MB03506 (PTF MF53082), or later, is a prerequisite.

This package contains the following fixes and enhancements.

General

• Fixes a problem that if the managed system supports more than 254 LPARs, and the user tries to configure a client VSCSI or VFC adapter whose server LPAR ID is greater than 254, the operation will fail with "Invalid remote lpar id specified" error."
• Fixes a problem in which daily utilization data was not collected for servers having huge number of partition.
• Fixes a problem in which mpio and vlanbridge values specified by user during resumption of suspended partition is ignored.
• Prevent the "lshwres --level lpar" command from failing if a partition is deleted after the command is issued but before it completes.
• Fixes a problem in which an lslparutil command cannot start execution until the previous lslparutil command has completed.
• Fixed a problem with using the text "fc" embedded in a Virtual IO server command syntax was causing error HSCL2970 ? command contains illegal data: fc.
• Fixed partition migration platform detected failure messages HSCLA2CF/HSCL365C that can occur when performing a cross HMC/SDMC migration for a partition that has additional VLAN IDs defined for any VETH adapters.
• Fixed issue where RMC return code 1021 is encountered while attempting to perform a hibernate or LPM operation due to a crash in the LparCmdRM process.
• Enhanced the partition migration task to include the name of the partition being migrated.
• Fixed a problem where after a successful partition migration, the status of the migrated partition on the target system remains "UNKNOWN".
• Fixed a problem that can result in recovery state with potential loss of partition configuration information.
• Fixed issue with lslparutil where every 2500th line is missing.
• Fixed a problem where after a successful partition migration the OS version is not refreshed and shows unknown.
• Fixed a problem where the connection monitor attribute on Manage Virtual Server may return an incorrect value.
• Fixed a problem that can result in an "Out of Memory" error after a user attempts to view utilization data for a system with a large amout of data.
• Fixed a no permission issue when a LDAP user tried to create a new user in the Create User Wizard (174121)
• Fixed an issue to prevent the SP1 Update in an HA environment from causing a failover.
• Fixed an issue where changing the clock format on the fluxbox clock hung Xwindows.
• Fix to load the duplicate policy after an update.
• Fix to increase duplicate detection time to 30 days for System x.
• Enhancement to allow 'NA' for the OS field so problems for certain systems will submit from SDMC.
• Fixed an issue where setting SSM as the default startup page cuased issues rendering pages after restart.

Repair and Verify

• Corrected a problem on Initialize Frame(s) procedure where I/O Enclosures are not powered on and the managed system is not able to associate ownership with the I/O Enclosures. This problem was the result of a Service Action (FRU Exchange, FRU Add, or serviceable event Repair) leaving a BPA lock on 9999-999*9999999 held.
• Corrected a problem where the Exchange procedure for the PCI shuttle assembly in a 5796 or 7314 I/O expansion unit fails with the message "HSCL0273 A command that was targeted to the managed system has timed out". Normally this exchange procedure fails if the system configuration includes eight or more I/O expansions units.
• Corrected a problem with a BPC FRU Exchange or Repair displaying the error: "An error occurred while attempting to resynchronize passwords with the BPC".
• Removed extra panel of connecting GX cable in the R & V instructions for installing PUBooks on POWER6 595.
• Fixed an issue where the incorrect number of procs needed to be available for node power down is specified when running CHARM FSP HOT repair during node evacuation step.
• Fixed a PBCmErrorHandlerPanelBean R & V Unknown Modifier error message that may occur when exchanging a SCM/DIMM/TPMD on POWER 795.
• Fixed a problem where the bridged MAC address changes on each SDMC reboot.

Security

• Fixed a security issue with the viosvrcmd.
• Fixed an issue with the certificate used by remote vterm application.
• Fixed an issue where error "HSCL350B The user does not have the appropriate authority" was reported when attempting to use the --filter option with the lshwres command.

This package has the following known issues.

General

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

  Workaround: 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.

• In the Configure Network wizard, some settings may show incorrect current values if the back button is used.

  Workaround: Use cancel button and restart.

• No option available to add additional gateway beyond the default.

  Workaround: No action is needed.

• Remove operation for an unauthenticated host on the DHCP private network will succeed. However, the server will be rediscovered.

  Workaround: 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: 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: Manually reboot from the GUI or CLI.

User management

• SDMC fails to start and goes into error state if it is unable to contact the configured LDAP server.

  Workaround: Verify the LDAP server is operational. Use CLI to remove or repair the LDAP configuration.

• Issues with using LDAP help.

  Workaround: 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.

• The smcli lsuser command incorrectly displays an internal user "ccfw" not available for login.

  Workaround: The ccfw user should be ignored.

• Create User wizard and mkuser command will fail when apostrophe (') is used for description field.

  Workaround: Do not use apostrophe for user account description.

• Unable to remove some user groups (inherited roles) from a user profile.

  Workaround: Delete and recreate the user.

• Incorrect help text for removing a user shows root authority is required.

  Workaround: 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.

• Task items on popup menus may not appear within the scrollable window on the local console.

  Workaround: To ensure all tasks are seen, always scroll down the task list to the bottom to force the window to dynamically scroll.

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

  Workaround: A feature that allows a user to be restricted to viewing only specific resources is being considered for a future release.

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

  Workaround: Login through the command line to be prompted to change the user password after expiration.

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

  Workaround: 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.

  Workaround: Use command line to remove the current configuration, then reconfigure:
  cfgldap -o r

Virtualization

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

  Workaround: You should check via command line if an RMC session is active for the paging space partitions.

• When a user tries to create a shared memory pool and the system does not have sufficient memory an error message is displayed: "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.

  Workaround: 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.

  Workaround: You can use Edit Host to view the memory pool properties subsequently.

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

  Workaround: Increase the virtual processors, then do the move or do a remove followed by an add.

• Manage virtual server panels for physical I/O, network and storage adapter do not indicate if I/O is required or desired.

  Workaround: Look at the last activated profile and then edit the profile to see the adapter settings.

• 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".

  Workaround: The error should read "...between 10 and 200" if the Server is based on POWER6 technology. and "...between 1 and 200" if the Server is based on POWER7 technology.

Miscellaneous

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

  Workaround: The circumvention is to initialize the server, and then recreate the partitions.

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

  Workaround: 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.

• Multiple selections do not work on user interfaces that use the dual tree chooser (e.g. Check for Updates, Customize User Permissions, etc).

  Workaround:
  1. For the numeric keypad not working:
  a. Press shift key, and then the number keys on right side of keyboard.
  b. Hold Shift key and press NumLock twice, and then the number keys on the right side of keyboard should work.
  2. None.

• Keys are not set correctly when the command mkauthkeys is used with -g option.

  Workaround: Set up the migration key pair without using the "-g" option. The mkauthkeys command 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.

  Workaround: 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.

• During repair operations to a node or FSP on POWER6 systems R&V displays message "Unknown Modifier 11" instead of the correct message regarding hardware limitation.

  Workaround: Either message requires that you proceed with a non-concurrent repair.

Updates (Firmware and SDMC)

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

  Workaround: 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."

  Workaround: This message can be ignored and no action needs to be taken by the user. User can continue with the install wizard.

Refresh/Out of Sync

• In some circumstances, user interface displays stale information and does not refresh automatically to reflect the correct status or state after an operation.

  Workaround: Click to another area in the user interface and back again or logout and log back in to view the refreshed status.

Install/Setup

• Startup on boot could have long delays, Director status remains "Starting" for up to an hour.

  Workaround: Check that all interfaces have a link-up and that at least one interface has a valid configuration on the network.

• Message not suppressed during ovftool deployment - Warning: No manifest entry found for: SDMC_xxxxx_xxx_xxxx-diskx.vmdk.## T

  Workaround: This message can be ignored.

• 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: 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.

  Workaround: Cancel the setup wizard, reboot the system, and then restart the setup wizard to reset the subnet mask.

Backup/Restore

• The manual (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.

  Workaround: You can manually remove the previous backup copy if desired.

• Restore function does not work if you have not run the setup wizard and have rebooted at least once.

  Workaround: 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.

  Workaround: Restore Removing and reinserting the USB key will cause detection.

Guided Repair

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

  Workaround: 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.

  Workaround: 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 you execute a Prepare for Hot Repair operation, it takes several minutes for the next panel to be displayed the node is being queried.

  Workaround: None.

• Do not attempt a PUBook Exchange using SDMC.

  Workaround: If needed, use HMC to exchange a PUBook.

Applying the fix pack with the 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.

1. Insert the USB key into the appliance
2. Identify the mount point by running the following 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
3. Mount the USB key by running the following commands. Use the mount_point listed in the lsmediadev command output.
   mount /media/vdh1
   ls /media/vdh1
   
   The ls /media/vdh1 command output should include the following:
   ifixMF54510
   
   (The following step assumes that all of the update files are in the ifixMF54510 directory on the USB key.)
4. Create an update directory and copy the USB contents to the update directory by running the following commands:
   mkdir -p updates
   cp /media/vdh1/ifixMF54510/* updates/
   umount /media/vdh1
5. Install the mandatory updates by executing the following commands:
   SYSNAME=`smcli lssys -t OperatingSystem -w "OSType=23"`
   echo $SYSNAME
     (The output should display the hostname of your SDMC appliance)
   smcli installneeded -n $SYSNAME -v -F /home/sysadmin/updates
   smshutdown -t now -r

Installation instructions for SDMC V6.730 updates and fixes can be found here:

Installation methods for SDMC Version 730 updates and fixes

Installation instructions for SDMC V6.730 can be found here:

Installation or restoring SDMC Version 730