Slipsheet

ATI00684VEN/ ATI00685IEN Call Management System Installation and Maintenance

Document version 1.0

Copyright 2010 Avaya All Rights Reserved 1

Call Management System Installation and Maintenance

Document scope

This slipsheet contains all the added R16.2 features to the existing vILT/ ILT ATI00684VEN/ ATI00685IEN, Call Management System Installation and Maintenance (CMS) course.

Additional resources

You can find additional R16.2 CMS documentation relevant to this slipsheet on the Avaya Support website, http://support.avaya.com.

Copyright 2010 Avaya All Rights Reserved 2

Call Management System Installation and Maintenance

Table of contents
Topic 1: Performance Improvements.................................................................................. 4 Topic 2: Backup Enhancements.......................................................................................... 7 Topic 3: Supervisor Changes .............................................................................................. 9

Copyright 2010 Avaya All Rights Reserved 3

Call Management System Installation and Maintenance

Topic 1: Performance Improvements Topic 1a: Report Limit Administration

Introduction
CMS R16.2 contains two customer administrable report properties. Both have been added to address performance issues that resulted from report queries. 1. A customer administrable flag limits the historical and real time reporting of agent groups to groups of 30 or less. The allowable value set as yes (y) allows the user to create an agent group report of any size. If the allowable value is set as no (n) then the report will be generated only for agent groups having less than 30 members. If the group contains more than 30 members, an error message will be sent to the user. If a report can be run against multiple agent groups, the sum total of the members of all groups in the query must be less than 30 members. 2. A time value can be administered to limit the time the historical database spends on a report query. The allowable values are 3-999 seconds or never (no timeout). When set to never there is no time limit. However, if the user sets a value, a report might fail if the query is not completed within the set time.

ASCII Administration screen shows the new report properties

Copyright 2010 Avaya All Rights Reserved 4

Call Management System Installation and Maintenance The Maintenance selection on the main CMS ASCII screen allows managing the two report limit values. This administration is only available from the CMS ASCII interface and not for the CMS Supervisor interface.

Objectives The new properties of report administration: Allows reporting against agent groups > 30 and applies to the report run from the CMS Supervisor or ASCII. Allows setting the timeout value for historical report queries and applies to the report run from the CMS Supervisor or ASCII.

Resource
To learn more about Report Administration, see: Avaya Call Management System Administration at //support.avaya.com

Copyright 2010 Avaya All Rights Reserved 5

Call Management System Installation and Maintenance

Topic 1b: Report Query Logs

Introduction
Two new report logs are added in CMS 16.2. They are qlog and idbm log. Qlog can be used to track the completion of reports and the idbm log can be used to track the reports that are currently running. The qlog contains the details of the all the queries that are run on the historical database. However, there will be separate idbm logs created for each idbm process running. None of these logs can be used to kill a particular report. Its only for debug information.

Objectives
The entries in a qlog are made upon completion of a query: Applies to historical report queries only. Can show past report execution to determine who ran queries and how long the queries took The qlog entries contain the start time, user, run time, completion status, task ID, and query text. The entries in the idbm log are made based on the current running queries: Applies to historical report queries only. IDBM stands for Informix Database Manager. These are the processes that interface with the historical database. Can be used to determine what queries are running right now. This can be used to determine if a particular query is taking a long time and thus negatively impacting system performance. The idbm log entries contain the start time, user, and query text.

Resource
To learn more about the report query logs, see: Avaya Call Management System Software Installation, Maintenance, and Troubleshooting on //support.avaya.com.

Copyright 2010 Avaya All Rights Reserved 6

Call Management System Installation and Maintenance

Topic 2: Backup Enhancements

Introduction
CMS R16.2 now supports more options for backup/restore than just tape or Tivoli Storage Manager (TSM) LAN backup. It supports tape; LAN backup/restore/migration to TSM Server 5.5 or 6.2.1; LAN backup/restore/migration to Netbackup Server 7.0, USB storage device, and NFS mounted file system. Customers are given the ability to backup/restore/migrate to and from tape, TSM Server, Netbackup Server, USB storage device, and NFS mounted file system. Some partitioning changes are required for LAN backup systems to be used for migrations, as temporary storage area is required.

Objectives
You can see the following backup enhancements in CMS 16.2: Current Tape backup/restore/migration options: o The migratable LAN Backup option to migrate data from TSM LAN backup. o Approve use of TSM 6.2.1 for LAN backup/restore/migration. o The option for defining a directory path on a NFS mount or USB device to store a compressed data backup file is provided for maintenance and cmsadm backups. o The maintenance device menu is modified. Changes during installation: o The display information takes inputs regarding the type of backup device, which could be a directly-connected tape drive or Other. o The cms.inst.skl file also reflects these changes. Approve use of Symantec Netbackup 7.0 for LAN Backup: o This feature provides scripts to perform backup/restore for both Solaris OS and IDS binary database, and the migratable data. Support for USB/NFS backup/restore/migration: o Supports data migrations. o Performs data compression in order to fit backup data on CMS disks for backup/restore/migration. o Changes in the CMS backup/restore device screens to include the option nontape devices as an option. o Changes in the install process to allow setting of default backup device. Copyright 2010 Avaya All Rights Reserved 7

Call Management System Installation and Maintenance o Sets the directory structure for USB/NFS type backups CMSADM and CMS MAINTENANCE under the root file structure.

Support for LAN Migration: o The following table shows the new partitioning scheme and installation instructions:

Slice
0 1

2 3 4 5 6 7

Mount Point / Swap Backup /cms /var /storage /export/home Raw IDS DB

Size(GB) 22 (now includes /opt) 8 Entire disk 10 26 200 32 ~521 (T5220), ~248 (T5120)

o /storage and external USB areas are excluded from CMSADM backups. o Gzip is used to compress backup data only for non-tape devices. Hardware and Software components o CMS R16.2 uses 300GB SAS disks for new T5120 and T5220 CMS servers, and a new partitioning scheme for LAN migration of data. o CMS R16.2 may still use 146GB SAS disks in the T5120 and T5220 CMS servers, and a older partitioning scheme if the customer will not use the LAN migration of data feature. o CMS R16/ R16.1 customers wishing to use the data migration option will require a CUE upgrade to complete the partitioning changes and acquire the larger sized disks.

Resource
To learn more about backup enhancements, see: Avaya Call Management System Software Installation, Maintenance, and Troubleshooting on //support.avaya.com. Avaya Call Management System Platform Upgrade and Data Migration on //support.avaya.com Copyright 2010 Avaya All Rights Reserved 8

Call Management System Installation and Maintenance

Topic 3: Supervisor Changes

Introduction
CMS Supervisor R16.2 now supports the following: 64-Bit Windows 7 64-Bit Windows 2008 Server R2 for Citrix CMS Supervisor R16.2 does not support the following: Windows 2000 OS

Objectives
The supervisor changes of CMS 16.2 are: If using R16.2 Supervisor, it is the ONLY Supervisor software that may reside on the system. Upgrades from Supervisor R12 & R13 to Supervisor R16.2 are not supported. They will need to be uninstalled before installing R16.2. Support for Citrix Xen App 6 on Windows Server 2008 R2 has been added. Support for Windows 7 64bit has been added.

Resources
To learn more about the Supervisor Changes, see: Avaya CMS Supervisor Installation and Getting Started on //support.avaya.com.

Copyright 2010 Avaya All Rights Reserved 9