The IBM SmartCloud Entry 2.3.0.3 Interim Fix 1 for Fix pack 3 Readme
Readme file for:IBM SmartCloud Entry Interim Fix 1 for Fix pack 3
Product/Component Release:2.3.0.3
Update Name:Interim Fix 1 for Fix pack 3
Fix ID:2.3.0.3-IBM-SCE-IF001
Publication Date:2012-11-20
Last modified date:2012-11-20
Online version of the readme file:http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400001388
Important: The most current version of the readme file can always be found online.
Contents
Download location
Prerequisites and co-requisites
Known issues
Known limitations
Installation information
Prior to installation
Installing
Performing the necessary tasks after installation
Uninstalling if necessary
List of fixes
Copyright and trademark information
Download location
Download updates for IBM SmartCloud Entry from the following location:
http://www.ibm.com/eserver/support/fixes/
Below is a list of components, platforms, and file names that apply to this Readme file.
Fix Download for AIX
Fix Download for AIX
Fix Download for Linux
Fix Download for Linux
Fix Download for Windows
Fix Download for Windows
Fix Download for Others
Fix Download for Others
Prerequisites and co-requisites
Please see the IBM SmartCloud Entry Administrators Guide 2.3 for a description of required products and fixes you need to install prior to running IBM SmartCloud Entry.
No prerequisite or co-requisite IBM SmartCloud Entry fixpacks are required for this update. IBM SmartCloud Entry fix packs are cumulative, so you only need to install the latest version to pick up all the available fixes.
If you are using IBM SmartCloud Entry to manage provisioning via IBM Systems Director 6.3.1 running VMControl version 2.4.1.1, you should install the vmc-update.2.4.1.1-20121019-LAFix.zip updates along with this SmartCloud Entry interim fix or fix pack. Use the instructions located in the IBM SmartCloud Entry Administrator Guide 2.3, Chapter 4, section 'Applying prerequisite fixes for IBM Systems Director 6.3.x and VMControl 2.4.x'. Follow the instructions outlined in the 'Procedure' section, replacing the fix name 'vmc-update.2.4.1.0-iFix' with the current fix name 'vmc-update.2.4.1.1-LAFix'.
Known issues
No known issues have been identified.
Known limitations
No known limitations have been identified.
Installation information
IBM SmartCloud Entry has a Command Line Interface (CLI) which is used to update the application.
The CLI is available from the OSGi console which is opened when starting the application -- commands
are typed into the console to perform update operations.
Updates for the application are stored in repositories. Repositories are either URLs for
remotely installing/updating packages, or local file system directories. Updates via remote (URL based)
or local file system (directory) repositories are performed in the same manner, the only difference
being the format the repository specified on the CLI.
URL based repositories are of the form http://UPDATE_REPOSITORY
, while local file system (directory)
repostiories have the form file:PATH_TO_DIRECTORY
. When using a local file system repository, the full
path to the local directory must be given using forward slashes.
The following update commands are available via the CLI:
version
- Returns the current product version.
showrepos
- Returns a list of the update repositories associated with the product.
addrepo [url]
- Adds a repository to the product from the given file or remote URL.
delrepo [url]
- Removes a repository (*
for all repositories) from the product.
checkupdates
- Returns a list of the current updates available.
installupdates
- Installs the available updates to the product.
updatetimestamps
- Returns a list of the product's update timestamps.
rollbackupdates [timestamp]
- Rolls back to the given timestamp. If no timestamp is given the
rollback is to the previous timestamp.
Prior to installation
Installation of the fixes will require stopping and restarting the application.
Installing
- Download the update package (zip file) from IBM Fix Central to the computer running the IBM SmartCloud Entry application.
- Create a directory on the local file system of the computer running the IBM SmartCloud Entry application. For example,
C:\temp\repository
- Extract the update package (zip) to the directory created in the previous step.
- From the IBM SmartCloud Entry OSGi console, type:
addrepo file:PATH_TO_DIRECTORY
Where PATH_TO_DIRECTORY
is the full file path to the directory the update zip was extracted to. For
example: addrepo file:C:/temp/repository
**Note the use of forward slashes.
- Type
installupdates
- The CLI output from the
installupdates
command should indicate installation success.
Performing the necessary tasks after installation
After installing updates to the application, IBM SmartCloud Entry should be restarted.
To restart:
- Type
close
into the OSGi console in which the application is running.
- When the application ends, the console window will close indicating the application has stopped.
- Restart IBM SmartCloud Entry.
The installed fixes should now be active.
Uninstalling if necessary
To uninstall previously installed updates, use the rollbackupdates
command.
When this command is run with no parameters, the most recent update applied will be uninstalled.
To rollback to an earlier level, first use the updatetimestamps
command to display a list of update timestamps, then use the rollbackupdates
command with the desired level timestamp as a parameter.
List of fixes
2.3.0.1 FP1
104022: The get customization call takes 200+ seconds at large scale
104799: Error completing database operation when test billing
104932: getVS call consumes excessive resource (CPU) from FSM
104997: Metering showing UNKNOWN [IP:10.1.22.102} for name being metered
105037: Typo in usage metering page
105042: Restore failure
105113: The height of the collapse column is not the same as the layout height
105203: The backup image remains in deleting state after the msg was sent to show success
105288: After two failed storage adds, a third attempt will report error
105336: Lost the workloads IP and failed to do capture after database migration
105341: Item cannot be selected if there are too many items on a page in Chrome browser
105344: Define a length limit on the name of the storage
105389: Captures failed because SCE discovery timeout value is too small
105438: Capture: says workload is not capturable while VMC says it is captureable
105609: When upgrading from Derby->DB2- CLI migrateDatabase Failed
105638: Restore failed with DNZIMC020E error msg
105640: Can't approve restore 2nd backup image request while delete the 1st backup image
105739: The "Move To Project" button not displayed correctly
105746: After restore, the former deployment is not deleted in SCE (poll mode)
105805: Configuring Appliance for AME fails
106295: CPU and Memory settings are not displayed by default when do basic deploy
106304: Snapshot of the workload shown as unknown in workload list during capture 10 workloads in a time
106351: Migration - Cannot deploy from SCE 2.3 after migration
106485: The storage pool configured in appliance does not take effect
106844: IPs in use after workloads deleted
107252: Workaround VMC Discovery defect for Capture
107394: Failed to test connection before saving cloud connection info
107634: The disk name changed after adding storage successfully
107703: Unable to deploy virtual appliances in image repository
107793: Appliance is shown for unauthenticated end user
107812: Delete save image successful of workload, display exception info on the SCE console
107822: The disk info is not correct in SCE after restore image
107904: Architecture column on Workloads and Appliances tab should be configurable
107909: Matching Vcenter template name and workload name creates failed workload
107941: Change network configuration to include Domain name in the case of no DNS feature
107972: Multiple JMS connection resets causes multiple SCE refresh tasks to fire up
108041: Login should return a user to his own last page, not the last page of another user
108071: Network Properties showing up under system settings are confusing to users
108174: Checkbox labels and buttons should not end with a period
108186: Min/Max values can be changed on Power Configure appliance page which should not be allowed
108222: If a user is not specified in Request.createUrl, the url returned is malformed
108263: Workload shows as deleting although workload has been deleted
108463: Resized VS loses resize info after restart
2.3.0.1 IF1
111152: PMR 846851 SCE doesn't synch VM info from VCenter
2.3.0.2 FP2
106431: VMware - network label is not picking up changes
107811: Can't restore the 2nd backup image in polling mode
108151: Padding around message box is incorrect
108164: Virtual server in unknown state in SCE due to cloud
108771: Add a message to diagnose invalid characters used in the storage volume name
108855: Display confirmation dialog when a user with admin rights tries to delete itself
109406: Appliance can not be deployed after changing the image target
110073: Currency unit in the configuration file doesn't take effect on VMware
110160: On Flex, workload created without cloud association
111189: Workload in NEW state is changed to DRAFT state before the user saves it
111425: Backup appears in Appliance tab in push mode
111902: Add ICON on Home Screen for tablet application
2.3.0.2 IF1
109472: Max storage size must be larger than min for resize on VMware
112401: Property 'Use DHCP for network adapter' is not required for VMware
113902: Too many workload change events generated for VMware mock mode
115418: Deploys fail on single gateway, multiple adapter environments
115559: PMR 41692 Deploy fails with shared processing units of .3 requested
115884: SCE should use network mapping from VMControl REST API
116133: Problem updating appliance on PureFlex Power cloud
2.3.0.3 FP1
99643: Derby db size is too large
115818: All workloads are listed as capture candidates
117540: Storage grid UI displays an extra column
117750: Security: LDAP.xml misconfiguration allows authentication
119205: Appliance name sequence is not correct
119208: Fix refresh function from appliance tab
119550: Support for VMC 2.4.1.x
119565: Maximum of virtual processors changed after modifying the CPU in basic deploy
120217: Incorrect message regarding supported cloud levels
120227: Display correct supported cloud levels in pulldown
120236: Deployment problem using VMC 2.4.1.0
2.3.0.3 IF1
118550: Show rejected deployment requests as “Rejected” when admin rejects approval request
120394: SmartCloud Entry 2.3 security update
121444: Capture and VMC 2.4.1.1
124734: IP address does not release when deploy failed
124987: Empty hostname on workload deployment using a network configuration
Copyright and trademark information
This fix is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the fix. You are not authorized to install or use the fix except as part
of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
By furnishing this document, IBM grants no licenses to any related patents or copyrights.
The applicable license agreement may have been provided to you in printed form and/or may be viewed at http://www-03.ibm.com/software/sla/sladb.nsf/viewbla/.
Copyright © IBM Corporation 2012