PATCH 467-004 ----------------------- You may need to apply this patch if: a. You are experiencing problems with an HAL cluster b. Your server is subject to temporary slow-down or hang conditions triggered by clients trying to reach it through a firewall c. You are experiencing problems enrolling licenses when Concurrent-Offline licenses have already been enrolled d. Your end-users cannot give nodelocked-offline licenses back to the server's pool of concurrent-offline licenses. e. You cannot assign authorizations based on group names to use concurrent-offline licenses in offline mode. Defects description ----------------------------- a. If your network is subject to temporary failures, and the number of clients connected to your HAL cluster is not small (e.g. >500), conditions have been identified that can lead to a complete server unavailability over a period of time. The symptom is that the i4lmd process is still present but it is in a hanging state, not responding to i4tv and i4blt commands, and not serving licenses to any LUM enabled application. b. LUM clients are not currently allowed to connect to the license server through a firewall. If you try to violate this restriction by opening the port (1515 by default) on which the server listens for client requests conditions have been identified that can lead to performance degradation or to temporary server unavailability c1. If you are trying to enroll the first license certificate for a given Vendor on a license server where Concurrent-Offline licenses (from other Vendors) were already installed, you may get the following error: "CLN-84 Invalid password or vendor incorrect" c2. If you are trying to enroll a Custom Configuration Concurrent license that is a replacement of an already enrolled Concurrent-Offline license you may get the following error: "CLN-207 Offline period exceeds maximum allowed value" d. With this patch the following constraints in the handback of a previously reserved nodelocked-offline license are being removed: - only the same Windows user ID that reserved the license can hand it back - the IP address of the portable computer must be the same as at the time of the reservation (so that it cannot be configured using DHCP) - the same version of LUM client code (of the LUM-enabled product) must be used to reserve and handback the license. Note that the hostname of the laptop at handback time must still correspond to the hostname that the machine had at reservation time. e. You are trying to define an authorization list for a Dassault product that should be used by a group of users in disconnected mode. The users belong to the same LUM group and you are granting them full access to the concurrent-offline license ("allowed" mode) using the name of the group. Nevertheless the users fail in reserving the license as offline license for their laptops. Note that, while this patch solves this problem, users will still be unable to use the license in normal concurrent mode if the only authorization for them is based on the name of a group. You need to migrate to a LUM 4.6.8 (or later) server to fix this problem too. Installation instructions --------------------------------- Stop the license server (i4cfg -stop) and replace the i4lmd executable with the one provided with this patch. The executable can be found in: /usr/opt/ifor/ls/os/aix/bin (AIX) /opt/lum/ls/os/solaris/bin (Solaris) /opt/lum/ls/os/hpux/bin (HP-UX 11) /opt/lum/ls/os/svr4.sgi/bin (Irix) Restart the license server (i4cfg -start)