Avaya Diagnostic Server 3.0 Service Pack 3 Release Notes

Transcription

1 Avaya Diagnostic Server 3.0 Service Pack 3 Release Notes Introduction This document provides support information about the Avaya Diagnostic Server 3.0 Service Pack 3 release and supplements other Avaya Diagnostic Server 3.0 documentation. For updated documentation, product support notices, and service pack information, go to the Avaya Support website at Contents Introduction... 1 Contents... 1 Installation... 1 Required Release... 1 Installing the release... 2 Enhancements... 3 Fixes... 4 Known Issues... 4 Contacting support... 4 Contact Support Checklist... 4 Contact Support Tasks... 5 Installation Required Release Avaya Diagnostic Server Avaya Diagnostic Server (GA Build) Avaya Diagnostic Server (Service Pack 1) Avaya Diagnostic Server (Service Pack 2) Note: To verify the Avaya Diagnostic Server version: 1. Log on to the command line interface of the Avaya Diagnostic Server host. 2. View the inventory.xml file, by using the following command: cat /opt/avaya/ads/installdata/inventory.xml 3. Search the tag named ADS, and check the version attribute. It should be or or

2 Installing the release After successful download of Avaya Diagnostic Server 3.0 Service Pack 3, you can install the service pack in two modes: attended or unattended. NOTE: 1) This installation procedure is applicable to all types of Avaya Diagnostic Server deployment, such as OVA, Services-VM, ION, and software only solution. 2) You cannot apply this service pack by using System Platform Patch Utility or Solution Deployment Manager Utility. 3) OVA and Services-VM platforms support the unattended mode of installation only. Installing the service pack in the unattended mode (supported on Services-VM, OVA platforms, systems with SSH access only) 1. Log in as root to the system on which Avaya Diagnostic Server is installed. 2. Create a new directory in your home directory. Download the service pack from PLDS or the Avaya Support website to the new directory. 3. Extract the installer as: tar -xvf ADS-ServicePack tar.gz 4. Change the directory to ADS-ServicePack Open the ADS_Response.properties file in a text editor, and agree to the end user license agreement by changing the value of ADS_AGREELICENSE to y. 6. Run the following command:./install.sh unattended After successful installation of the service pack, the system sends an message indicating the installation status to the administrator. Installing the service pack in the attended mode (supported on GUI based systems) 1. Log in as root to the system on which Avaya Diagnostic Server is installed. 2. Create a new directory in your home directory. Download the service pack from PLDS or the Avaya Support website to the new directory. 3. Extract the installer as: tar -xvf ADS-ServicePack tar.gz 4. Change the directory to ADS-ServicePack Run the following command to start the installation:./install.sh attended 6. When the installer displays the End User License Agreement (EULA) text for Avaya Diagnostic Server, type y to agree to the license, and press Enter. If you type n, the installer ends the installation. The installer runs the prerequisite checks and displays the results. If the host meets the prerequisites, the installer prompts you to install the component through a GUI-based installer. Installing the Service Pack 1. On the Welcome to the installation panel, click Next. 2

3 The system displays the Target Selection panel indicating the path to. 2. Click Next. A pop-up warning message indicating that the directory already exists and the action might override the existing file is displayed. 3. Click YES. The system displays the selection panel. 4. Select the AgentGateway checkbox, and click Next. The system displays the results summary panel indicating the installation status. 5. Click Done to complete the installation. Installing the SLA Mon Service Pack 1. If the SLA Mon component of Avaya Diagnostic Server 3.0 is present on the server, the installer automatically installs the service pack. After successful installation of the service pack, the system displays a message indicating the installation status on the CLI. It also sends an to the administrator indicating the installation status. Using automatic software update will automatically download and apply the service pack when Automatic Software Update is enabled. After downloads the update, you can manually install the update instead of waiting till the scheduled time. 1. Log in to the UI. 2. Navigate to the Automatic Software Update page. 3. Click the Apply Now button next to the update that corresponds to ADS 3.0 Service Pack 3. Note: If SLA Mon is installed as a co-resident with, the automatic update will also apply to the SLA Mon Server. If SLA Mon is installed on a separate server, use the attended or unattended mode to apply the service pack. For information about patches and product updates, see the Avaya Technical Support website Enhancements can now forward alarms to Avaya Hosted Concentrator for Business Partners if the BP Link ID configured on the is entitled for alarm transport. Each Product alarm will be forwarded to Avaya Concentrator as well as Avaya hosted concentrator for Business Partner. Avaya Hosted Concentrator for Business Partners will forward the incoming alarms from s to Configured BP Alarm Receivers. The Alarm entitlement for BP Link ID is automatically refreshed on as soon as the entitlement is changed on Avaya hosted Concentrator by Avaya. BP must have Avaya Delivery Partner (ADP) status to be entitled to use an alarm receiver. The SAL Watchdog functionality is updated in such a way that if faces connectivity issues with Avaya Concentrator, then it should wait for a longer time before starting in minimal mode. The SAL Watchdog functionality is updated in such a way that If is able to communicate even with one Concentrator (Avaya or BP Hosted), then it should not go in to minimal mode. New DigiCert CA certificates added to maintain connectivity between and Avaya Core as the earlier Symantec CA is being sold to DigiCert now. 3

4 Ability to restore from 3.0.0, 3.0.1, and versions backup to is added. Support for Product Initiated Registration is added. now displays APIs for Avaya products to submit registration requests and query their statuses. Once processed successfully, the requests register the product with Avaya and administer them to. Note: Currently APIs are used by Avaya System Manager 8.0 only. For more details about this feature, see the PIR feature guide. support for J139, J169 and B189 Avaya conferencing phones is added. Fixes The Avaya Diagnostic Server 3.0 Service Pack 3 software update includes the following fixes: Fixed the issue of Installation and Uninstallation getting hung when run in the attended mode in a CLI system. When a phone under remote control goes offline, the system displays a pop-up after 30 seconds. The off line remote control agent tab is closed on the pop-up acknowledgement. SLA Mon server now supports only TLS v 1.2 connections with agents. An agent coming online after 12hr of network outage is now included in the synthetic test calls. A previously registered agent will now show a certificate error if the certificate is removed from the phone. In a bulk call scenario, if the destination agent in the first agent pair goes offline, calls can now be established on other phone pairs if they are functional. Known Issues None None Contacting support Contact Support Checklist If you are having trouble with Avaya Diagnostic Server, you must: 1. Retry the action. Carefully follow the instructions in the pdf or online documentation. 2. Check the documentation that came with your hardware for maintenance or hardware-related problems. 3. Note the sequence of events that led to the problem and the exact messages displayed. Ensure that the Avaya documentation available. If you continue to have a problem, log on to the Avaya Technical Support website to: 1. Use the online service request system to create a service request. 2. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise. 4

5 Contact Support Tasks You might be asked to one or more files to Technical Support for analysis of your application and its environment. 5