Product Support Notice

Transcription

1 PSN # PSN002085u Product Support Notice 2008 Avaya Inc. All Rights Reserved. Original publication date: 10-Oct-08. This is Issue #1, published date: 10- Oct-08. Severity/risk level High Urgency When convenient Name of problem Application Enablement Services Release Notes, R3.1.6 Products affected Application Enablement Services (AES) 3.1.x Problem description Introduction This PSN announces the AES Release It is an update to AES release Notes AES is a bug fix release for AE Services 3.0, 3.1, and 3.1.x. AES is supported on Red Hat Enterprise Linux 3.0 Update 5 AES is compatible with the following Bundled Servers: IBM x306 (S8500B) IBM x306m (S8500C) AES is compatible with the following Communication Manager (CM) releases and platforms: CM 3.0 (G3csi, S8300, S8400, S8500, S87xx) CM 3.1.x (G3csi, S8300, S8400, S8500, S87xx) CM 4.x (S8300, S8400, S8500, S87xx) CM 5.0 (S8300, S8400, S8500, S87xx) CM 5.1 (S8300, S8400, S8500, S87xx) Release History Date Build Change(s) 02/ General Availability R3.1 05/ General Availability R / General Availability R / General Availability R / General Availability R / General Availability R /08 52 General Availability R3.1.6 Software Versions Application Application Enablement Services Server Software for the Software Only Solution Application Enablement Services Server Software for Bundled Solution File Name swonly-r3-1-6-build iso bundled-r3-1-6-build iso Known Issues and Workarounds AES R3.0/R3.0.1 to R3.1.6 Bundled Server Only When upgrading the Bundled Server from the release 3.0 to 3.1.6, an additional step must be taken to create the default server web pages for AES. Once the upgrade is complete and made permanent, issue the following command: rpm -ivh --force /var/disk/rpms/mvap-tomcatconfig noarch.rpm

2 Browser issue with auto-complete For security reasons, the HTML input auto-complete feature is now disabled by default. Once R3.1.6 is installed, you must change your browser settings to disable the browser s Password Management feature. Follow the steps that apply to the browser you are using. For IE: Select Tools > Internet Options > Content > Auto Complete. The Option "User names and passwords on forms" should be unchecked, and if this option was previously selected, then select the button Clear Passwords as well. Select OK on each screen. For Firefox Select Edit > Preferences > Privacy > Saved Passwords. The Option "Saved Passwords" should be unchecked, and if this option was previously selected, then select the button "Clear" as well. Select OK on each screen. Installation null pointer exceptions When the MVAP Service is started for the first time, a "java.lang.nullpointerexception" is printed twice. This happens when the Alarm and Log Web Services are deployed. Both services are deployed correctly and work normally even though the exceptions are triggered. Please ignore the "java.lang" null pointer exceptions. TSAPI clients opening more than 2500 maximum streams can return error If TSAPI clients try to open more than the maximum number of streams (2500), an error will be returned. This is proper behavior. Unfortunately, certain resources are not freed as they should be. If the client applications continue attempts to connect and the resource is exhausted, then the TSAPI service will fail to create new monitors, to accept new connections (even after other streams are closed), and to update TSAPI OAM pages. This will happen after about 1500 such failed requests. The following error log entry indicates that you have exceeded 2500 open streams: ERROR:CRITICAL:TSAPI:TSERVER:DriverService.cpp/ could not register with session manager These error log entries indicate that the resource has been exhausted and the TSAPI service must be restarted: ERROR:WARNING: TSAPI:MVAPLicense::acquireTSAPIUsers:getNumAcquired failed: Internal error:socket() ERROR:CRITICAL:TSAPI:TSERVER:DriverService.cpp/ accept failed:20 ERROR:WARNING:TsrvCmdUtility:main:Receive from server failed rc= 0, errno= 2 ERROR:WARNING:TsrvCmdUtility:main:Receive from server failed rc= -1, errno= 62 http issue When attempting to access the OAM pages, you are automatically switched to use https instead of the regular insecure http protocol. This may cause a problem in which the user is denied access to the tomcat server. The user will see the following error message: - Access Denied (connect_method_denied) - Your request attempted a CONNECT to a port "8443" that is not permitted by default. - This is typically caused by an HTTPS URL that uses a port other than the default of For assistance, contact your network support team. Solution: In order to resolve this issue, the user must turn off the browser s proxy settings or include the IP address or the DNS name of the AE Services server in the "Proxy Exception s box". For IE 6 users 1. Click Tools > Internet Options > Connections > LAN Settings > Advanced. 2. In the "Exception box", enter the full IP address or the DNS root (whichever you use) of the AE Services server. For Firefox users 1. Click "Tools > Options > Advanced> Network >Settings" (for Linux version, click "Edit > Preferences > General > Connection Settings"). 2. In the "No proxy for" box, enter the full IP address or the DNS root (whichever you use) of the AES server Avaya Inc. All Rights Reserved. Page 2

3 Process to Change the Server IP Address If the IP address of an AE Services server is changed without stopping the server, or if the IP address is changed and then an attempt is made to set the new address through the web pages without stopping the server service (which is using the connection), an error message will be displayed. The error message will appear on the Local IP web page and indicate that the database entry for the IP address does not match the IP address configured on the server. The proper procedure to change the IP address is as follows: For AES bundled server 1. Log in as sroot. 2. Issue "service mvap stop" 3. Execute "/opt/mvap/bin/netconfig" to bring up GUI. 4. Enter/Modify IP address (es) per NIC interface (Make sure "Enable" boxes are checked) 5. Save/exit by clicking "OK" button. 6. Re-login as sroot with new IP address if administering remotely. 7. Issue "service network restart" (This step is pre-cautionary). 8. Bring up OAM using new IP address of AES server. 9. Go to "CTI OAM Admin" > "Administration" > "Local IP" and set the new IP address (es) for all "Connectivity" entries. 10. Go to Maintenance > Service Controller and apply "Restart AE Server" button. 11. Make sure all services are in "Running" state and connection state to switch (es) is functional. For AES Software-Only server 1. Log in as root. 2. Issue "/sbin/service mvap stop" 3. Customer is responsible for the change, but highly recommend using Linux utility such as /usr/bin/redhat-config-network if using Redhat Release 3. /etc/hosts file must be updated with new IP address (es). 4. Re-login as sroot with new IP address if administering remotely. 5. Issue "/sbin/service network restart" (This step is pre-cautionary). 6. Bring up OAM using new IP address of AES server. 7. Go to CTI OAM Admin > Administration > Local IP and set the new IP address (es) for all "Connectivity" entries. 8. Go to Maintenance > Service Controller and apply "Restart AE Server" button. 9. Make sure all services are in "Running" state and connection state to switch (es) is functional. Note: Check status of httpd/tomcat5 processes if OAM page cannot be accessed by "/sbin/service httpd status" and "/sbin/service tomcat5 status", and start if not running. Security Updates [RHSA-2008: ] Important: kernel security and bug fix update [RHSA-2008: ] Important: perl security update [RHSA-2008: ] Moderate: net-snmp security update [RHSA-2008: ] Moderate: php security update [RHSA-2007: ] Moderate: php security update Issues resolved from the previous release TSAPI Service Issues Previously, if the TSAPI Service was used to make a predictive call from a routing VDN and the application subsequently took a snapshot of the predictive call, the snapshot did not always include the called party. Previously, if OAM was used to view the User Status of TSAPI Service users, a race condition could cause the OAM command to fail. Logic for the TSAPI User Status OAM command has been changed to eliminate this race condition. Previously, if Avaya CM was not administered to use Universal Call Identifiers (UCIDs), the TSAPI Service would sometimes provide un-initialized UCID data in events. Previously, the TSAPI Service would sometimes provide the wrong cause value in CSTA Connection Cleared events Avaya Inc. All Rights Reserved. Page 3

4 Previously, in some shutdown scenarios the TSAPI Service would access memory that had already been freed. Previously, within the TSAPI Service, memory was sometimes de-allocated in a way that was not compatible with how it had been allocated. Previously, in some scenarios the TSAPI Service would access uninitialized data. Previously, some Unicode device names were not properly formatted in TSAPI Service trace output. Within the TSAPI Service, logic has been modified to prevent invalid memory access. There is improved performance of the TSAPI Service for requests that do not require a TSAPI License. ASAI Link Layer Previously, in some scenarios the ASAI Link layer would access un-initialized data. OAM Command The OAM command for viewing the User Status of TSAPI Service users has been changed to exclude users who have not yet established an authenticated session with the TSAPI Service. Resolution Workaround or alternative remediation Remarks PATCH NOTES The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Download Patch install instructions Verification Failure Patch uninstall instructions Serviceinterrupting? No SECURITY NOTES The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks Avaya Security Vulnerability Classification Not Susceptible Mitigation 2008 Avaya Inc. All Rights Reserved. Page 4

5 For additional support, contact your Authorized Service Provider. Depending on your coverage entitlements, additional support may incur charges. Support is provided per your warranty or service contract terms unless otherwise specified. Avaya Support Contact Telephone U.S. Remote Technical Services Enterprise U.S. Remote Technical Services Small Medium Enterprise U.S. Remote Technical Services BusinessPartners for Enterprise Product BusinessPartners for Small Medium Product Please contact your distributor. Canada Caribbean and Latin America Europe, Middle East, and Africa Asia Pacific Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners Avaya Inc. All Rights Reserved. Page 5