Known limitations for IBM Workload Deployer Version 3.1.0.1 Limitations with high availability appliances having two cable configurations Problem: When you set up high availability appliances with two cable configurations, one of which is a dedicated data link connection, the following limitations exist: The Ethernet configuration of the master interface must not be updated by running the netif set command or by selecting System > Settings > EthernetSettings > interface_used_by_primary. Multiple network configurations are not supported for the Ethernet interface of the primary appliance with a two cable configuration. For example, if you configure an IPv4 floating IP address for the interface that is used by the primary appliance, an IPv6 floating IP address cannot be configured with the IPv4 IP address. Resolution: Enable the disabled data sync link on the appliance and reboot both appliances and set up HA again. Make sure that there is one master and one slave. Also, if A1 was master and A2 is slave when the problem occurred, it is better to make A1 as master and A2 as slave. Licenses are not displayed on the license panel Problem: Licenses are not displayed on the license panel for some types of virtual images. Resolution: When accepting the license agreements, you must manually add the product IDs for each of the WebSphere components: Administrative agents Custom nodes Deployment manager IBM HTTP Server The product ID for each component is displayed in the following table. Depending on the operating system of the virtual image, the product ID is different: WebSphere component SuSE Enterprise Linux Red Hat Enterprise Linux Administrative agents 5725-D29 5725-A11 Custom nodes 5725-D29 5725-A11 Deployment manager 5725-D29 5725-A11 IBM HTTP servers 5725-D30 5725-C02 Auto failover has limitations when data sync link is disabled Problem: If a data sync link cable is not firmly connected and enabled for High Availability (HA) there are issues with auto failover. Or, if one of the data link cables is disabled, both appliances are in master state. Resolution: Enable the disabled data sync link on the appliance and reboot both appliances and set up HA again. Make sure that there is one master and one slave. Also, if A1 was master and A2 is slave when the problem occurred, it is better to make A1 as master and A2 as slave. Using LDAP with an SSL connection in a HA environment causes invalid LDAP SSL certificateProblem: In a Workload Deployer High Availability (HA) environment, when you use LDAP with an SSL connection, the LDAP SSL certification becomes invalid after each failover. Resolution: Use the console to update the security configurations. 1. Click System > Security. The Security panel displays. 2. Change the LDAP setting to a Non-SSL connection. Then change the LDAP setting back to an SSL connection and accept the security certificate. 3. Create a new LDAP user. Command-line directory path name must be in ASCII characters Problem: When the Workload Deployer command-line interface is started, an exception occurs if the command-line interface is unzipped to a directory with a path name that includes non-ASCII characters, for example, English characters are ASCII. The most common exception is "ImportError: No module named os". Resolution: Unzip the command-line interface to a directory with a path name that consists entirely of ASCII characters, or to the root directory of a drive, for example, C:\. Known issues during appliance upgrades when High Availability is enabled Problem: There are several known issues when upgrading an appliance that has High Availability (HA) enabled, including: Upgrading the HA appliance on the master appliance does not upgrade the Web user interface version number, for example, if you upgrade to V3.1.0.1, the version number remains at V3.1.0. Upgrading a HA appliance pair from the user interface does not guarantee minimal downtime. Resolution: Complete the HA pair upgrade (firmware upgrade) using appliance console commands. Firmware upgrade commands: console> file get <...> newimage console> firmware upgrade new image With following orders : 1. manual failover on master appliance console> failover and then manual failover on slave appliance console> failover Write down HA configuration information. This information is the output from master's configureHA. You need this information so that you know which is the master appliance, which is the idle appliance and the related IP configurations. 2. Upgrade with the above firmware upgrade commands on the idle appliance. 3. Upgrade with the above firmware upgrade commands on the master appliance. All the appliances show standalone status after the appliance reboots. Due to some existing defect, upgrade on master appliance might not get IWD console webui version updated, and there might be problem with downloading IWD cli zip file So please make sure to check IWD webui version after upgrade -- if it is not upgraded please repeat firmware upgrade commands on the appliance 4. Put the pair back into the HA pair: On the original master appliance: Login to appliance console> startHA -mode=master .... On the original idle appliance: Login to appliance console> startHA -mode=slave .... Upgrading the HA firmware pair with this method minimizes down time. Attention: This release note is only needed if two appliances are in a HA pair. This is not an issue with a standalone appliance.