Avaya Diagnostic Server 3.0 Service Pack 2 Release Notes

Transcription

1 Avaya Diagnostic Server 3.0 Service Pack 2 Release Notes Introduction This document provides support information about the Avaya Diagnostic Server 3.0 Service Pack 2 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 Prerequisite for installation... 2 Installing the release... 2 Enhancements... 3 Fixes... 4 Known Issues... 5 Contacting support... 5 Contact Support Checklist... 5 Contact Support Tasks... 5 Installation Required Release Standalone Avaya Diagnostic Server Avaya Diagnostic Server (GA Build) Avaya Diagnostic Server Note: To verify the Avaya Diagnostic Server version, follow the procedure: 1. Log on to the command line interface of the Avaya Diagnostic Server host. 2. View inventory.xml file, 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

2 Prerequisite for installation Please follow the below sequence to upgrade to Service Pack #2: 1. Disconnect and SAL Policy Manager. 2. Upgrade SAL Policy Manger to Service Pack #2. 3. Upgrade to Service Pack # Connect the upgraded and Policy Manager. Note: For optimal performance, don't connect Service Pack # 2 upgraded to the previous version (3.0.0 or 3.0.1) of Policy Manager. Installing the release After successful download of Avaya Diagnostic Server 3.0 Service Pack 2, 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. You cannot apply this service pack using System Platform Patch Utility or Solution Deployment Manager Utility. 2) On OVA, Services-VM platforms, only unattended mode of installation is supported. 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 quits 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. 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. 2

3 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. 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. 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 2. 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 Added ability on to communicate with Avaya Hosted Concentrator for Business Partners by configuring BP Link ID on the. This provides services like Remote Access, Package Deployment, Device Data sync etc. for Business Partners. When BP Link ID is configured on, the spiritagent services are automatically restarted and SAL Gateway is updated. It displays the BP Name for that Link ID.. 3

4 verifies the connectivity of a device being added to the and prompts the user in case there are any connectivity issues with the device. Added health check for Avaya Hosted Concentrator for Business Partners if Link ID it is configured on SAL Gateway. Added the following message on add device pop-up as connectivity check would fail for windows device when doing SSH You may ignore this protocol check if the product does not support SSH, or if you plan on accessing the product through a different protocol. If gateway is managed through a business partner then following changes related to redundancy feature are applicable from this release redundancy (Chapter 7 from SAL Admin Guide ) is controlled by the Avaya Hosted Concentrator. With SAL 2.x technology, only s connected to the Avaya concentrator can operate as a redundant pair, and s connected to BP concentrators cannot. With SAL 3.x technology, the individual BP concentrators are replaced with the Avaya Hosted Concentrator for BPs. 3.0 connects to both the Avaya concentrator and to the hosted concentrator for BPs by administering a BP link ID in the gateway. In this environment, s can operate as a redundant pair when 1. Both s are release 3.0 with SP2 (3.0.2) or later. 2. Both s are administered with the same BP link ID. If release 2.x s are operating as a redundant pair, but after upgrade to they are administered with different BP link IDs, the redundancy will be broken. If release 3.x s are operating as a redundant pair, but later they are administered with different BP link IDs, the redundancy will be broken. SLA Mon Server Fixes Support for the J179 mercury phones and Windows Agent added in SLAMon Server. The Avaya Diagnostic Server 3.0 Service Pack 2 software update includes the following fixes: Fixed an issue related to SNMP Sub-Agent logs on UI. Fixed an issue related to firewall rules Diagnostic reports for RHEL7. Fixed an issue related to getting thread dump for SMNP service when collecting the Vital information. Fixed the incorrect message displayed in logs when restore fails. Fixed the inconsistent behaviour in add/edit managed elements page while changing device SEID more than twice. Fixed an issue related to service status not captured properly under Restore Archive. Fixed issue of irrelevant logs in SALGWDiagnostics report under SPIRIT Versions. Fixed the SAL 3.0 remote access to Aura_Conferencing devices using JAVA ADMIN INTERFACE protocol. Similarly fixed remote access for any other protocols having large number of ports. Fixed an issue related to connectivity from to Avaya Hosted Concentrator. This issue is encountered when (HTTP/Socks) proxy is configured on the and the is unable to directly resolve the concentrator URL. Fixed pull file from & Package deployment for SOCKs proxy where GW is unable to resolve Avaya remote server address directly. Fixed an issue related to Health status icon that shows partly cloudy although all the queried points on showed healthy. Fixed an issue regarding the Package deployment failure on s if /bin/nice is not available on the Gateway. Fixed the issue where name of XML files with size >55 were being truncated when pulled up from using package deployment. 4

5 SLA Mon Server A remoteaccess issue is fixed, where the user was able to take 2 remote sessions of the same device(endpoint) simultaneously. Bulk call feature is disabled for unsupported agents. As a part of security hardening, HTTP TRACE method is disabled for SLA Mon servers. Known Issues SLA Mon Server 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 written 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. Have 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. Contact Support Tasks You might be asked to one or more files to Technical Support for analysis of your application and its environment. 5