ACSBI Customer User Guide

- version 1.1

ACSBI Program Overview The Avaya Client Services Business Intelligence (ACSBI) Portal provides Avaya, its Customers and Partners, a platform for decision making by managing business data and providing historical, current, and future views of service delivery and customer trends.

ACSBI Direct Access URL: https://acsbi.avaya.com/ ACSBI information Portal: https://support.avaya.com/acsbi Table of Contents ACSBI Program Overview ......................................................................................................................... 1 1

Avaya Software Compatibility Audit tool and report (ASCA) ............................................................. 2 1.1

Introduction ............................................................................................................................. 2

1.2

How to generate an ASCA report? ............................................................................................ 2

1.3

Understanding Avaya Software Compatibility Report ............................................................... 8

1.4

Avaya Software Compatibility Report Terms and Definitions .................................................... 8

1.4.1

Main, ESS, and LSP Servers ............................................................................................... 8

1.4.2

Gateways ......................................................................................................................... 9

1.4.3

Circuit Packs ................................................................................................................... 10

1.4.4

DCP and IP Endpoints ..................................................................................................... 10

1 Avaya Software Compatibility Audit tool and report (ASCA) 1.1 Introduction This document describes the Avaya Software Compatibility Audit tool (ASCA). This document is intended for Avaya customers, Business Partners, and Avaya technicians who can use the tool to generate a report to view the hardware, software, and firmware versions of all the products that can be upgraded in Communication Manager. This report also contains information about the latest versions available for those products. ASCA can be used to generate a report for hardware, software, and firmware that includes servers, gateways, Local Survivable Processors (LSPs), Enterprise Survivable Processors (ESS), boards and modules, and DCP/ IP endpoints.

1.2 How to generate an ASCA report? There are two ways to access ASCA. Traditionally, business partner and customer access it via the “Tools” section in the footer of the support.avaya.com by clicking on the “Software Compatibility Audit” link as shown below and skip to step 4.

Alternatively, the ASCA user can access it from ASCBI portal page as shown below. 1. Login to ACSBI at https://acsbi.avaya.com using your Avaya user SSO username and password. 2. Click on “Application and Surveys” icon.

3. Click on “Avaya Software Compatibility Audit” under ‘Applications’

4. Click on “New ACSA Report Request”

5. If you have a list of FL’s that you want to enter manually or if you have copied your FL list and are ready to paste, click on “Search by FL’s”

a. Enter the FL numbers, each on a line or paste them into the box below, and click on “Get ASCA Products”. The ASCA applicable SEID’s are then displayed below the “Get ASCA Products” button. Note: If the FL’s do not exist, do not belong to you, do not have the required Customer Authorization Tool (CAT) permissions a message will be displayed explaining why. If there are no applicable ASCA products for the specified FL(s) then no SEIDs will be displayed.

b. Select one or more of the ASCA-applicable products using the checkboxes in the ‘Request’ column and click on “Create an ASCA Report”.

6. If you want to search for FL’s using other criteria like customer name or address, click on “Search by Customer”

a. Enter values into one or more of the filter boxes and click on “Get ASCA Products”. The search engine is not case sensitive. The ACSA applicable Solution Element ID’s (SEIDs) are then displayed below the “Get ASCA Products” button. Select one or more of the ASCA-applicable products using the checkboxes in the Request column and click on “Create an ASCA Report”

7. Enter “Report Title”. This is a mandatory field and it is recommended the report name as well as the customer name and or FL is included in the title for easy identification within the tool. Select the “Report Sections” of interest.

8. The most recent ASCA report request will show up at the top of the list of all reports requested. The column labeled “View” provides a status while the reports are being prepared. The status will change from “Report Pending” to “View” once the report is ready. In addition an email notification is sent indicating the report is ready to be viewed. Note: The page has to be refreshed to see the status change.

9. Clicking on “View” will open an Excel file that contains the ASCA report; each section of the report will be in a separate tab.

1.3 Understanding Avaya Software Compatibility Report There are seven (7) report sections, or tabs, in the ASCA report. The Main, ESS, and LSP servers sections (tabs) have the same set of columns. The Gateways, Circuit Packs, and DCP or IP Endpoints sections (tabs), each has a different set of columns. The DCP Endpoints and IP Endpoints sections (tabs) have the same set of columns. The following sections explain these columns. Each active main server may have associated with it, a duplicated inactive and standby server. If this is the case, both of them are reported. Each main server can utilize more than one gateway through IP or other legacy communication methods. A gateway itself has a software server and a set of media module (cards) and optionally a set of stack modules (cards) plugged into it. Each circuit pack, media module, or stack module has ports to connect DCP and IP phone stations as well as other communication systems. The stations are registered to the gateways and the gateways in turn are registered to the main server. The main server has ability to query the components described above to gather data for the ASCA report.

1.4 Avaya Software Compatibility Report Terms and Definitions 1.4.1

Main, ESS, and LSP Servers 1. Server Name: The human-assigned DNS name of the server

2. Server IP Address: The IP address of the server 3. Platform Type: The Avaya S8* hardware platform type - S8300, S8400, S8500, S8700, and S8800 4. Operating System (OS): The computer operating system name, release, version, and build load number. 5. OS Build Date: The build date of the OS above 6. Platform/Security Updates Currently Installed: Avaya-maintained security update currently installed in the OS 7. Platform/Security Updates Currently Installed: The latest Avaya-maintained security update that can be installed in the OS 8. CM Software Version: The CM software release string 9. CM Updates Currently Installed: The software update currently installed for the specific CM software version 10. CM Updates Latest Available: The latest CM software update for the given CM software version 11. SES Service Pack (SP) Currently Installed: The SES SP currently installed in the CM 12. SES Service Pack (SP) Latest Available: The latest SES SP available 13. Alarm ID: The service alarm ID created by product registration 14. SAMP/MPC FW Version Currently Installed: The firmware version currently installed in the SAMP/MCP card 15. SAMP/MPC FW Version Latest Available: The latest firmware version that can be installed in the SAMP/MCP card 1.4.2

Gateways The report for gateways contains three (3) parts: gateway software server, media modules, and/or stack modules. Note that each module is a gateway translating specific communication protocols and thus has its own name and IP address.

1.4.2.1 Servers 1. Gateway Name: The human-assigned DNS name of the gateway server 2. Gateway IP Address: The IP address of the gateway server 3. Platform Type: The Avaya gateway platform type - G250, G350, G430, G450, and G650 4. Serial Number: The serial number of the gateway product 1.4.2.2 Media Modules 1. Gateway Name : The human-assigned DNS name of the media module server 2. Gateway IP Address: The IP address of the media module server 3. Slot: The slot of the gateway backplane into which the media module is plugged 4. Type: The media module type 5. Code: The media module code 6. Suffix: The media module suffix 7. HW Vintage: The media module hardware vintage 8. FW Vintage Currently Installed: The firmware vintage currently installed in the media module 9. FW Vintage Latest Available: The latest firmware vintage that can be installed in the media module 10. VOIP FW Currently Installed: The VOIP firmware currently installed 11. VOIP FW Latest Available: The latest VOID firmware that can be installed

1.4.2.3 Stack Modules 1. Gateway Name: The human-assigned DNS name of the stack module server 2. Gateway IP Address: The IP address of the stack module server 3. Slot: The slot of the gateway backplane into which the stack module is plugged 4. Bank A Currently Installed: The firmware currently installed in Bank A 5. Bank A Latest Available: The latest firmware that can be installed in Bank A 6. Bank B Currently Installed: The firmware currently installed in Bank B 7. Bank B Latest Available: The latest firmware that can be installed in Bank B 8. Embedded Web Currently Installed: The web embedded software currently installed on the stack module 9. Embedded Web Latest Available: The latest web embedded software that can be installed on the stack module 1.4.3

Circuit Packs 1. Location: The cabinet location where the pack resides. 2. Type: The type of the pack 3. Suffix: The suffix of the pack 4. HW Vintage Currently Installed: The hardware vintage currently installed 5. HW Vintage Latest Available: The latest hardware vintage that can be installed 6. FW Vintage Currently Installed: The firmware vintage currently installed 7. FW Vintage Latest Available: The latest firmware vintage that can be installed

1.4.4

DCP and IP Endpoints 1. Extension: The extension of the phone 2. Admin Phone Type: The type of the phone being administered 3. FW Version Currently Installed: The firmware currently installed in the phone set 4. FW Version Latest Available: The latest firmware that can be installed in the phone set