IBM Support

Release notes for IBM PureApplication System W1500 Version 1.0.0.4

Release Notes


Abstract

This release notes document lists known issues in this release.

Content

The following issues are known in this release.

  • Using Java 7 with your browser client in the PureApplication System Monitoring Portal is currently not supported in IBM PureApplication System.




Administering the System:


Critical events are occurring during rack shutdown or startup
Problem:Critical events are generated by PureSystems Manager during rack shutdown and/or startup
Resolution:During rack shutdown, you can ignore critical events, such as:
  • Unable to communicate with the virtual management software using IPv6 address...

During rack startup you can ignore the following error type:
  • CWZIP9001E: An unexpected internal error [ ] has occurred


Database monitoring is disabled after upgrade
Problem:After upgrading, the following database monitoring issues occur:
  • The database monitoring status is in the Configured-Disabled state, meaning that the database is not being monitored.
  • The Monitor links fail to appear.
  • The Middleware page (Manage > Monitoring > Middleware) fails to show the database that is being monitored.
Resolution:From the Databases menu item under Virtual Applications click:

Instances > Virtual Applications > {application} > Manage > Operations > {database} > Database Performance Monitoring > Start database monitoring > Submit

From the Databases menu item under Database instances click:

Instances > Databases > {database} > Manage > Operations > {database} > Database Performance Monitoring > Start database monitoring > Submit


Database monitoring is not available even when the Database Performance Monitoring service is running
Problem:When running the Database Performance Monitoring service, the Monitor link is not displayed beside the DB2 database virtual machine on the Virtual Application Instance page. In addition, the log file that is associated with the database virtual machine contains a 404 Not Found error message.
Resolution:Restart the Database Performance Monitoring service. From the workload console, click

Instances > Shared Services > Database Performance Monitoring > Manage > Operations > Database-Performance-Monitor.OPM > Restart > Submit.

After ensuring that the service restarts successfully, wait approximately one hour and confirm that the Monitor link is displayed beside the DB2 virtual machine on the Virtual Application Instance page.


All CPU cores are assigned to first Non-Uniform Memory Access (NUMA) node
Problem:When the virtual machine has more than 8 virtual CPUs all CPU cores are assigned to first NUMA node. This behavior causes memory reads to take longer and thus introduces performance issues.
Resolution:Configure the virtual machine to use 8 or less virtural CPUs


Error: CWZIP4643W exception thrown by LdapService e=javax.naming.CommunicationException
Problem:When a host name and port that cannot be resolved are provided for the LDAP Provider URL on the "Security settings" page, the following message is displayed:

CWZIP4643W exception thrown by LdapService e=javax.naming.CommunicationException : <IP address:port>
Resolution:Enter a correct hostname:port for the LDAP Provider URL


After upgrading to Version 1.0.0.3, an instance of the System Monitoring service does not function properly
Problem:When a System Monitoring service instance that has assumed the upgrade path from Version 1.0.0.1 to 1.0.0.2, and has more than one remote monitoring server, is upgraded to Version 1.0.0.3 it becomes unusable and cannot be recovered.
Resolution:Delete the existing instance and redeploy a version 1.0.0.3 System Monitoring service with the same configuration.


A connection to the database server failed
Problem:Cannot create new cloud groups when the PureSystems Manager is powered off or unavailable
Resolution:Determine if the database is down by running the following command:

<sudo dmidecode | grep "System Inf" -A 4 | grep "Serial Number" | awk '{print $3}' | grep -c $(sudo head /data/config/informix/informix.config -n 1 | cut -d"\"" -f2 | cut -d"x" -f2)> 

If the database is determined to be down, restart the database.


A black screen is displayed when connecting to VNC on DB2 9.7.5.0 virtual system deployments
Problem:On some DB2 9.7.5.0 virtual system deployments, the VNC service is not started correctly. You see 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"


Backup and Restore:


A system cannot be restored if the same SSH server credentials are not used to configure both the certificate and private key location and the backup image location
Problem:Backup images cannot be recovered and the system cannot be restored by IBM service if you specify different values for the following fields when you configure the storage locations of the certificate and private key and the backup images:
  • Host: Enter the host name of the SSH server that is used to store your certificate, private key, and backup images
  • Path: Enter the full path to the directory in which the certificate, private key, and backup images are stored
  • User name: Enter the ID of the user connecting to the SSH server
  • Password: Enter the password of the user connecting to the SSH server
Resolution:Contact IBM to request that a service representative perform the procedure for recovering the configuration and restoring the system.
  • In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). Select the second VRU option for software.
  • To locate a global IBM support contact, see the Directory of worldwide contacts at http://www.ibm.com/planetwide/. Select the contact number or VRU option for software.


Connectivity Issues:


Email notifications are not submitted when deployments occur
Problem:Email notifications for instance deployments are not sent.
Resolution:This is a known limitation in this release.


A VLAN was removed from the system but it is still visible
Problem:While managing the network configurations of your system, when you choose to remove a VLAN from the system, you might only select the VLAN from the VLAN Information section of the "Customer Network Configuration" page of the system console. This action does not fully remove the VLAN.
Resolution:There are two places on the "Customer Network Configuration" page that show the VLANs that are in use by the system. To fully remove a VLAN from the page, you must remove it from both the VLAN Information section and the Link Configuration section.

See the information center for details on managing VLANs in your network configurations.


High availability:


The primary PureSystems Manager always pushes workload data to overwrite the secondary PureSystems Manager
Problem:If the primary PureSystems Manager goes down, the secondary PureSystems Manager automatically takes over as the primary PureSystems Manager. When workload changes occur (such as deploying new workloads) during this time, only the secondary PureSystems Manager knows about the new workload changes. 

If the secondary PureSystems Manager goes down, and if the original PureSystems Manager then recovers and resumes its role as the primary, it might then overwrite the secondary PureSystems Manager data with older information. As a result, any workload changes that were made during the outage might be lost.
Resolution:If both PureSystems Managers are down, start the PureSystems Manager that was most recently functional first.


IBM Image Construction and Composition Tool:


Bundles are not added to new images in Image Construction and Composition Tool
Problem:When creating an image from a template, bundles that do not have an installation step defined are not added to the new image.
Resolution:After you create a new image from a template, use the regular procedure to add additional bundles to the image.


The Revert function does not work after the virtual application upgrade
Problem:After upgrading the virtual application, the Revert function does not work from the virtual application detail web page.
Resolution:Connect to the virtual machine manually and use the IBM Installation Manager silent mode function to complete the rollback of the virtual application.


Managing virtual systems and virtual applications:



WebSphere Application Server hypervisor image hangs on capture
Problem:While capturing a WebSphere Application Server virtual image, you might encounter a process hang if you wait more than 60 minutes to capture the image after the initial
extend has completed.
Resolution:Perform the image capture within 60 minutes after you extend the image.



The Health status of virtual systems display the message, "Running but with error"
Problem:When virtual systems are deployed all virtual machines in the pattern deploy and reach running status. All virtual machines are running correctly but the health status in the virtual system details display the "Running but with error" message.
Resolution:The health status error message can be ignored.


Incorrect values for the virtual CPU in-use limits in the environment profile
Problem:If a virtual machine is reconfigured to increase the size of the virtual CPU count while the virtual machine is in the Started state, the CPU in-use limit in the environment profile is not incremented to reflect the new size of the virtual CPU. This causes the CPU in-use limits to be incorrect. In some cases the CPU in-use limit might be negative as the value is decremented by the new size of the virtual CPU count when the virtual machine is stopped or destroyed. As a result of the incorrect CPU in-use limits, deployments exceeding the configured limits of the environment profile are not enforced correctly.
Resolution:Discontinue use of the existing environment profile with the incorrect values, create a new environment profile and redeploy the instances to the new environment profile.


Parentheses cannot be specified in a virtual application instance name
Problem:Deploying a virtual application instance with invalid characters "(" or ")" in the instance name is not supported.
Resolution:Delete the failed instance and redeploy with a new instance name that does not contain parentheses.


Deployments might time out and fail while a backup job is running
Problem:Group deployments might time out and fail while a management system backup is running on the system. The backup prevents all other work from running while it backs up the system. As a result a multi-deploy pattern might have a number of deployments held up by the backup job as it runs, and might cause the overall group deployment to time out and fail.
Resolution:Remove the existing failed group deployment and retry the group deployment when the management system backup has completed.


Increasing the number of CPUs for deployed patterns causes WebSphere Application Server service to stop responding
Problem:If you deploy a virtual application pattern or virtual system pattern that is configured with one CPU, and later increase the number of CPUs, WebSphere Application Server stops responding to requests.
Resolution:To work around the problem, choose one of the following options:
  • Ensure that you deploy the instance with at least two CPUs configured.
  • Stop the virtual machine and then increase the number of CPUs.

    • Related:
    List of fixes in IBM PureApplication System Version 1.0 Fix Pack 4
    IBM PureApplication System release notes by version

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

    Document Information

    Modified date:
    17 June 2018

    UID

    swg27037827

    Page Feedback