IBM Support

Release Notes for IBM PureApplication System W1500 Version 1.0.0.0

Release Notes


Abstract

IBM PureApplication System W1500 Version 1.0.0.0 is now available. This release notes document addresses system requirements, limitations, and known problems.

Content


The following topic areas are covered in these release notes:





Administering the system:



SNMP forwarded traps do not set a value for UpTime
Problem:SNMP forwarded traps always display the value of UpTime as 0.
Resolution:This is a limitation for this release.


SNMP traps from virtualization system manager are displayed twice in the events list
Problem:Duplicate events (and SNMP traps) are received from the virtualization system manager.
Resolution:These duplicate SNMP traps can be ignored.


Temperature warnings are displayed when the storage controller temperature exceeds 40 degrees Celsius
Problem:A temperature warning indicator is activated on the system console user interface for the IBM Storwize V7000 storage controllers if the temperature exceeds 40 degrees Celsius.
Resolution:The temperatures displayed in the system console represent the ambient temperature and exhaust temperature. The system console reports the following events if the storage device is over the temperature threshold:

010060 E A solid-state drive (SSD) exceeded the warning temperature threshold. 1217
010061 E A solid-state drive (SSD) exceeded the offline temperature threshold. 1218
010062 E A drive exceeded the warning temperature threshold. 1217
045012 W The canister temperature is at the warning level. 1098
045013 W The canister temperature is at the critical level. 1095
045070 W The canister temperature sensor cannot be read. 1034
070528 W The ambient temperature is too high while the system is starting. 1182
528 Ambient temperature is too high during system startup.


High temperature warnings are displayed when attributes are not properly configured
Problem:KQ8_Temperature_High_Critical and KQ8_Temperature_High_Warning situations, when they are started, always indicate an error event regardless of the actual temperatures within the rack. This problem occurs when the Maximum Exhaust Temperature and Maximum Ambient Temperature attributes are not set properly, resulting in zero values being supplied for these attributes.
Resolution:The system administrator should set appropriate values for these two attributes, so that these situations can alert you when the exhaust temperature or the ambient temperature is too high. The administrator can verify these attribute settings in the Temperatures workspace.


Compute node physical memory usage seems larger than the amount allocated
Problem:Physical memory usage displayed on the Hardware > Compute Nodes page might seem larger than the sum of all virtual machine memory usage.
Resolution:The compute node memory usage accounts for any hypervisor overhead as well as the virtual machines present.


No data is displayed in workspaces when they are opened immediately after starting the PureApplication agent
Problem:If you open IBM PureApplication System Monitoring Portal workspaces immediately after starting the PureApplication agent, the workspaces do not display expected data. This problem occurs because the PureApplication agent spends several minutes collecting initial data. Depending on the scale of the cloud, it might take as long as 30 minutes to complete this process.
Resolution:Wait several minutes and then refresh the workspace to display the data.


Error message CWZIP8535W is displayed when adding / removing a user to / from a group
Problem:The following message might be displayed when adding users to, or removing users from, a user group:

CWZIP8535W Unable to modify the user group membership without having all permissions from the user group.
Resolution:Ensure that the administrator has the same permissions for the specified group that are being added or removed for the new user. Note that the administrator does not need all permissions as the message states, only those needed to perform the operation.


Black screen is displayed when connecting to VNC on DB2 9.7.5.0 vSys deployments
Problem:On some DB2 9.7.5.0 virtual system deployments, the VNC service is not started correctly. The user sees a black screen when connecting to VNC using the standard Java applet. This problem occurs when deploying the DB2 9.7.5.0 HA Primary in a separate pattern from the Standby.
Resolution:You can manually reset the VNC service by connecting as root using SSH and issuing the following commands:

su - virtuser -c "vncserver"
su - virtuser -c "vncserver -kill :1"
su - virtuser -c "vncserver -kill :2"
su - virtuser -c "vncserver"


Storage Devices page does not indicate that an IBM Storwize V7000 storage controller is in a degraded state when a storage canister is removed
Problem:In the event that a V7000 storage controller begins operating in a degraded or less than optimal state (such as when a storage canister is removed), there is no notification on the Storage Devices page of the system console to indicate the changed condition.
Resolution:Monitor the System > Events page for errors with storage controllers.


Image name is appended with (2) even though the version is different
Problem:When an image is imported with the same name as a previously imported image, the text string (2)is automatically appended to the name of the new image, even when the version is different.
Resolution:This is a cosmetic issue only and does not affect the usability of the image.


The instance name for certain events might not be included in the event title
Problem:Events (such as power on and power off) that are associated with some instances might not contain the instance name in the event title.
Resolution:Click the event details to display the instance name for that event to see the title and other information.


The deploy number fields on the Compute Nodes page always display a value of zero
Problem:When viewing compute nodes in the Compute Nodes page, the Successful deploy number and Deploy number fields under the Health statistics section are not incremented during deploys and will always contain the value 0.
Resolution:This is a restriction for this release.


Unable to load resource message displayed when launching IBM PureApplication System Monitoring Portal
Problem:When you launch the IBM PureApplication System Monitoring Portal by using the Advanced Monitoring, Monitor, or Endpoint links, the following message is displayed:
Unable to load resource

This problem occurs when the client workstation is unable to resolve the fully-qualified host name of the monitoring server virtual machine.
Resolution:On the client workstation, edit the following file:
- For UNIX or Linux systems: /etc/hosts
- For Windows systems: Windows\System32\drivers\etc\hosts
Change or add an entry with the long host name followed by the short host name, similar to the following format:

<IP address> <long_host_name> <short_host_name>

Using this format:
- <IP address> is the IP address of the monitoring server virtual machine.
- <long_host_name> is its fully-qualified long host name.
- <short_host_name> is its short host name.

Example: 172.113.21.32 myhost.mycompany.com myhost


After you deploy a virtual application, interim fixes that are already installed are still listed as available for installation in the Operation pane within the Virtual Application Console.
Problem:There are two ways to apply an interim fix to a virtual application:
  • Apply the interim fixes to a deployed virtual application instance from the Operation pane in the Virtual Application Console.
  • Include the interim fixes in the virtual application pattern when you create it in the Virtual Application Builder.

If you configure the interim fixes in the Virtual Application Builder and then deploy the virtual application, the URLs of the installed interim fixes are displayed in the Interim Fixes text box as usual, but are also unexpectedly displayed as still available for installation when you click Select. If you select the URL for an interim fix that has already been installed, the second install might fail during the update.
Resolution:To avoid installing an interim fix that is already installed, when you are applying other interim fixes, be sure to clear the check box for the URLs of any installed interim fixes before you click Submit to perform the update.


Virtual Application Builder does not load when using Internet Explorer Version 8
Problem:When you attempt to open the Virtual Application Builder using Windows Internet Explorer 8 as your web browser, the new window opens but does not load the application builder.
Resolution:Refresh the newly opened Virtual Application Builder window.


Virtual Machine Usage report on the Machine Activity page takes too long to generate on Internet Explorer
Problem:When you attempt to generate a Virtual Machine Usage report on the Machine Activity page of the workload console using Internet Explorer, the process takes an excessive amount of time to complete.
Resolution:Continue to wait for the report to be generated.


Entries in part installation logs and role lifecycle script logs for deployed virtual application instances might only display the date but not the time
Problem:You might notice in some logs that the date and time format for some entries display only the date portion, but not the time.
Resolution:Upgrade to IBM PureApplication Systems W1500 version 1.0 Fix Pack 1 or later.



Managing users and passwords:



Internal server error when removing a role from a user group
Problem:When using the command line interface to remove a security role from a user where the role has already been removed from the user, the following error is displayed:

IOError: Internal Server Error
Resolution:Ignore this error. The role has already been removed.


The incorrect status of a deployed System Monitoring service instance might be caused by a password containing characters that are not valid
Problem:The status of a deployed System Monitoring service instance is incorrect, displaying a red exclamation mark beside the instance in the navigator. This problem might be caused by passwords entered during deployment that contain characters that are not valid.
Resolution:Complete the following steps:
1. Stop the System Monitoring service instance.
2. Delete the System Monitoring service instance.
3. Deploy a new System Monitoring service instance. When prompted to enter a password, ensure that only valid characters (A-Z, a-z, and 0-9) are specified.


IBM HTTP Server license usage is not updated after storing a deployment
Problem:After storing a deployment, the count of allocated (active) and reserved licenses is not updated to reflect the current license availability on the license panel for IBM HTTP Server. Both allocated and reserved license availability is displayed as zero.
Resolution:Delete stored IBM HTTP Server virtual machines to restore both allocated and reserved license availability. Alternatively, stop the virtual machines instead of storing them to regain allocated license availability.


User names created with characters that are not valid might not allow the user to log in successfully
Problem:A new user name can be created with one or more characters that are not valid (such as a semicolon), but users might not be able to log in successfully using this name.
Resolution:Create user names only with supported characters.


Users need to restart PureApplication System management software after accepting a new LDAP server X.509 certificate.
Problem:When the LDAP Server certificate is renewed, accepting the new LDAP certificate into the PureApplication System will not take effect until PureApplication System management software is restarted.

LDAP users will experience repeated requests from PureApplication System consoles requiring them to log in.   
Resolution:Restart PureApplication System management software after accepting a new LDAP server X.509 certificate.


Silent failure occurs when attempting to rename the virtuser ID for IBM DB2 parts
Problem:You cannot rename the virtuser ID for DB2 parts when you are creating or editing a custom virtual system pattern. The user ID parameter is reset to virtuser when the virtual system pattern is saved. The update to the user ID can be successfully specified when you deploy that virtual system pattern.
Resolution:To rename the virtuser ID, specify the new value of the user ID at deployment time.


An Administrator cannot delete or stop a shared service if it is deployed by another user
Problem:Users with Workload Administrator permissions, including the admin ID, can access the delete and stop controls for a Shared Service, even though they have not been granted access to the shared service.

If the user does not have access to the shared service, these delete and stop actions do not complete successfully.

- Delete stops the shared service, but does not delete the shared service. Use an ID with access to the shared service to complete the delete operation.

- Stop might stop the shared service, but then the shared service can no longer be stopped or started using any ID. Use an ID with access to the shared service to delete the shared service in this state, and then deploy it again.
Resolution:Users with Workload Administrator permissions can see that they do not have access to a shared service. They can grant access to themselves before attempting to control or modify the shared service.

When a shared service is deployed, grant access to all IDs or groups that will be controlling or modifying the shared service, including the admin ID.

If a shared service is stopped using an ID that did not have access to the shared service, delete the shared service using an ID that has access to the shared service. You can deploy it again using an ID with permission to deploy the shared service.

Shared services can only be deleted by an ID that has access to the shared service.



Connectivity issues:



The command line interface must use -a or -acceptcert option for SSL certification
Problem:The command line interface connects to the system with self-signed certification. When you run the pure command, an SSL handshake error is encountered when attempting to connect to the system.
Resolution:The certificate must be accepted by using the -a or --acceptcert option with the pure command.

Example: From the purescale.cli/bin directory, run the pure command, using the following format with the -a option:

pure -h host -u userid -p password -a


An error occurs when the system cannot connect to a configured LDAP server
Problem:There is no notification issued to indicate that the connectivity to the LDAP server has been lost. If the system is unable to connect to an external LDAP server, users might not be able to authenticate to the PureApplication System.
Resolution:Ensure that the LDAP server is available so that connectivity can be reestablished and user authentication can be resumed. Log in with a user that is not LDAP based to verify the LDAP settings.



Managing virtual systems:



Capturing an image after adding new storage and network configuration does not include the new additions when the captured image is exported
Problem:If you add storage or additional NICs to an image and then capture that image, the new disks or NICs are not recognized as part of the captured image when the captured image is exported.
Resolution:If additional disks or networks are needed for an image that will be exported for use in another system, include them as part of the pattern, and not as a part of the extended image.


Limitations to changing memory sizes for currently running instances
Problem:Changing the memory size without first stopping the instance is limited to a maximum of 3GB for instances that are currently running with less than 3GB. Instances that are currently running with more than 3GB of memory can be resized to 16 times the current memory capacity of the instance.
Resolution:To resize an instance beyond these running limitations, complete the following steps:
1) Stop the instance.
2) Resize the memory to the desired value.
3) Start the instance.


AddNode failure on custom node during dynamic cluster deployment
Problem:After deploying a virtual system using WebSphere Application Server 8.0.0.3 with the Intelligent Management component enabled, the deployment status seems to indicate a successful deployment, but the message server failed to start.
Resolution:This problem rarely occurs, and is likely the result of a network connectivity issue. Redeploy the virtual system.


Parentheses cannot be specified in the Image Construction and Composition Tool virtual application instance name
Problem:Deploying a virtual application instance of Image Construction and Composition Tool with invalid characters "(" or ")" in the instance name is not supported.
Resolution:Delete the failed instance and redeploy with a new instance name that contains valid characters.


Volumes cannot be deleted if they are still attached to an instance
Problem:If you attempt to delete a volume when it is still attached to an instance, no action is taken. There is no notification that the operation failed.
Resolution:Detach the volume from the instance before deleting the volume.


Virtual systems remain in stopping state longer than expected
Problem:Some virtual machines in the virtual system seem to remain in the stopping state, or might have actually stopped but the virtual system state itself remains at stopping.
Resolution:The virtual system should eventually continue to the desired state, but for faster resolution, you can manually force virtual machines to stop by completing the following steps:

1) Navigate to the Instances > Virtual Systems page.
2) Under the Virtual Machines view, click Manage.
3) Click the Delete option to delete the individual virtual machine.
4) After deleting all of the virtual machines in the virtual system, you can delete the virtual system if needed.


When deleting a virtual system, virtual machines are deleted from the hypervisor, but persist in the Node virtual machine list
Problem:If an instance cannot be properly deleted it will be marked as failed.
Resolution:No further action is required. A recurring job periodically checks for instances that are in the failed state and automatically retries deleting the instance.


Email notifications are not submitted when deployments occur
Problem:There are no email notifications for instance deployments.
Resolution:This is a restriction for this release.


Exporting an image allows space characters in exported filenames, but these images cannot be imported without renaming them to remove spaces
Problem:Importing of an image whose name contains blank space characters is not supported.
Resolution:Remove any blank spaces in image names, or convert any spaces in image names to underscores before importing the image.


Virtual system deployments consume more memory than expected
Problem:Virtual system patterns created with exact memory requirements based on past observations are now consuming more memory, which might cause high utilization warnings. This problem is a result of the integrated system monitoring, which adds the workload execution environment and operating system monitoring to all virtual system deployment, along with some deployments, such as WebSphere Application Server, including additional middleware monitoring.
Resolution:When creating your virtual system patterns and determining the memory resources required for each node, include an additional 250 MB for the integrated system monitoring components, and another 100-250MB for any optional middleware monitoring that is enabled.


Importing an image fails, unable to locate the file
Problem:When using the command-line interface to import virtual images, you might encounter an error indicating that the file cannot be located. This problem might occur when using the format:

deployer.virtualimages.import(open('/path/to/foo.ova', 'rb'))
Resolution:Use the following format instead:

deployer.virtualimages.import({'url': 'http://...' })

See the IBM PureApplication System W1500 Information Center for more information about the virtual images command-line interface reference.


Recommended interim fixes for the Intelligent Management component of WebSphere Application Server Hypervisor Edition Version 8.5
Problem:Known limitations in the Intelligent Management component exist.
Resolution:If you are using the Intelligent Management component, download and apply the base cumulative fix for the Intelligent Management component of WebSphere Application Server Hypervisor Edition Version 8.5 before using the virtual image with virtual systems.


Patterns with WebSphere Application Server Hypervisor Edition parts are restricted on deployment to eight virtual CPUs
Problem:The number of virtual CPUs that you can select for WebSphere Application Server Hypervisor parts can either be 1, 2, 4 or 8. You specify the number
of virtual CPUs when you create or deploy a pattern.
Resolution:You can further configure the number of virtual machine CPUs after creation and deployment by selecting System Console > Virtual machines > Configure.


When cloning a custom node that is a member of a dynamic cluster, the custom node is not added to the membership policy of the dynamic cluster.
Problem:This problem occurs when you have a custom node in a node group that is being used as the membership policy of a dynamic cluster.  If you clone the custom node using the PureApplication System console, the new custom node is not added to the existing node group.
Resolution:Complete the following steps to add the new custom node to the membership policy of the dynamic cluster:

1. From the WebSphere Application Server administrative console, navigate to System Administration > Node Groups > node_group_name > Node group members.
2. Click Add.
3. Select the new custom node, and click Add.
4. Save your changes.


When using a translated VNC Desktop, the correct language is not displayed in the administrative console
Problem:When you start the administrative console by using the desktop icon, the console is displayed in English even though the pattern is deployed in a language other than English.
Resolution:Manually stop and restart the VNC server instance to access the translated operating system menus, or use a different browser set to your preferred language setting to use the administrative console.

To restart the VNC server instance, complete the following steps:

1) Log in as the root user ID.

2) Verify that the VNC server is not running, by issuing the following command from the command line:

ps -ef | grep Xvnc

3) If the Xvnc instance is running, issue the following command:

su - virtuser -c "vncserver -kill :1"

4) Start the VNC server by issuing the following command:

su - virtuser -c "vncserver" 


When you stop and restart a WebSphere Application Server Version 8.5 virtual machine, the VNC server does not restart
Problem:If you stop and restart a virtual system pattern that has been deployed in single byte languages, the VNC Server does not restart.
Resolution:Manually restart the VNC server.

To restart the VNC server, complete the following steps:

1) Log in as the root user ID.

2) Verify that the VNC server is not running, by issuing the following command from the command line:

ps -ef | grep Xvnc

3) If the Xvnc instance is running, issue the following command:

su - virtuser -c "vncserver -kill :1"

4) Start the VNC server by issuing the following command:

su - virtuser -c "vncserver"


Create Cluster Advanced Options script failure occurs when using non-ASCII characters
Problem:When you specify non-ASCII characters in the node name, cell name, or cluster name, the Create Cluster Advanced Options script fails. The operation of deploying the pattern is shown as successful, but the PROFILE_HOME/logs/wasHVPatternConfiguration.log file shows that the wsadmin save command failed.
Resolution:Use only ASCII characters for the node name, cell name, and cluster names when you deploy a pattern that contains WebSphere Application Server Version 8.5 parts.

Original Publication Date

07 August 2012

[{"Product":{"code":"SSM8NY","label":"PureApplication System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"1.0","Edition":"All Editions","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2018

UID

swg27027514

Page Feedback