Installing Service Packs on Avaya Aura Session Manager. Release 1.2 August 2009 Issue 1

Transcription

1 Installing Service Packs on Avaya Aura Session Manager Release 1.2 August 2009 Issue 1 1

2 2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the documents, Avaya Support Notices for Software Documentation, , and Avaya Support Notices for Hardware Documentation, These documents can be accessed on the documentation CD and on the Web site, On the Web site, search for the document number in the Search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this Documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as wel as a civil, offense under the applicable law. Trademarks Avaya, Communication Manager Epress, MultiVantage, and INTUITY are trademarks of Avaya Inc. Some MultiVantage Express applications use the Open Source Indy Sockets library. License terms for this library are available at All non-avaya trademarks are the property of their respective owners. Third-party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avaya s web site at: Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your contact center. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: 2

3 Service Pack Installation This document describes the procedures, components, and requirements that are necessary to upgrade Avaya Aura Session Manager and Avaya Aura System Manager with a new service pack. This is an installation on the top of the current software load. The current service pack and patch running on a system can be determined by looking at the Session Manager version string. The version string has the following format: <major rel #>.<minor rel #>.<service pack #>.<patch #> An example of a version string is This indicates that a Session Manager system is running Release 1.2 with Service Pack number 4 and patch 11. Note: Service Pack 2 can only be installed on systems currently running Service Pack 1. Systems must be upgraded sequentially in the following order: System Manager -> Service Pack 1 Session Manager -> Service Pack 1 System Manager -> Service Pack 2 Session Manager -> Service Pack 2 During System Manager upgrades, Session Manager servers are put in the management disabled state. Session Manager servers are put into the Deny New Service state prior to upgrading a Session Manager instance. Service Pack Installation Requirements A Session Manager installation exists, including a System Manager and one or more Session Manager instances. The System Manager hardware is compliant with the desired upgrade release. Session Manager and System Manager installation scripts for the upgrade release are available on the Avaya Product and Licensing Delivery System PLDS website at It is recommended that a file server be accessible for Session Manager provisioning backups. It is recommended that the upgrade be scheduled during hours of little or no system activity. While it is possible to upgrade Session Manager without affecting service, it takes time for service to be redirected around each Session Manager being upgraded. The length of time increases with system activity. 3

4 Installing a Service Pack The process for installing a Service Pack has the following sequence: 1. Updating Data Retention Values 2. Backing Up Current Administration from System Manager 3. Disabling Management for all Session Manager instances 4. Upgrading System Manager to new Service Pack 5. Enabling Trust Management 6. Denying New Service for a Session Manager instance 7. Upgrading Session Manager to new Service Pack 8. Placing the Upgraded Session Manager Into Service 9. Repeating steps 5-7 as necessary for each additional Session Manager instance. Updating Data Retention Values This is the length of time in days that System Manager will retain log files and alarm data. The recommended value is 30 days. To update the Data Retention values: 1. On the System Manager Common Console, select Settings > Data Retention 2. Select Purge Old Log Records, then select Edit. 3. Change the value from 120 days the desired value and select Update. 4. Select Purge Old Soft-Deleted RTS Records, then select Edit. 5. Change the value from 120 days to the desired value and select Update. 6. Select Purge Old Cleared Alarm Records and select Update. 7. Change the value from 120 days to the desired value and select Update. 8. Select Apply to make the changes take immediate effect, Backing Up Current Administration from System Manager 1. On the System Manager Common Console, select Settings > Backup and Restore. 2. Click Backup to initiate the System Manager backup operation. 3. Select Local or Remote If choosing Local, enter a backup filename If choosing Remote, enter the required scp server access information. The Remote option displays the following information: o SCP Server IP IP address of the remote scp server o SCP Server Port valid scp port on remote server (standard port is 22) o User Name valid user name on the remote SCP server o Password enter the password for the above user access to the SCP server. The user password must be at least 8 characters (lower case, 4

5 o upper case, numeric, alphanumeric). There can be no repeated or sequential characters. File Name enter the full path and filename for the archive 4. When done, choose Now for an immediate backup, or Schedule to create a regular, repeated event. If you choose Schedule, the following fields are displayed: Job Name Generic description of this backup task that you are scheduling Task Time The start date and time for the first job execution Recurrence The frequency (if applicable) that his job will be executed (ie.. only once, once every 7 days, etc.) Range The range of time you would like this job executed (ie.. indefinite, x occurrences, or stop on a specific date) 5. Select Commit when finished. 6. Select Monitoring > Scheduler to check the status of the backup and view pending and completed jobs. Disabling Management for all Session Manager Instances 1. From System Manager, select Session Manager > System State Administration. 2. Select all listed instances. 3. Select Management State > Management Disabled. 4. Select Disable Management Upgrading System Manager to new Service Pack Note: Service Pack 2 can only be installed on systems currently running Service Pack 1. Prior to installing a service pack on System Manager, you need to make note of the alarming product IDs as they will need to be manually entered after the upgrade is complete. Run the following commands on the System Manager server and make note of the IDs (SM, SMELEM, and SpiritAgent) for later use: # getproductid SM # getproductid SMELEM # spiritagentcli (make note of the Alarming Module ID, and type 0 to exit out of the Spirit Agent CLI) There are two ways to upgrade System Manager: using a DVD or using an ISO image. If you download the ISO images of the installer files from PLDS and then copy them to the System Manager server using scp or winscp, you can mount them without copying to physical media. To upgrade System Manager using a DVD: 1. Login to a console on the System Manager server or SSH login with root privilege. 2. Insert the System Manager installation media into the System Manager and mount the drive using the following commands: 5

6 $ mount /dev/cdrom /mnt/ $ cd /mnt/ 3. Execute the install.sh script using the command./install.sh 4. When the upgrade has completed after approximately 90 minutes, eject the installation media with the following commands: $ cd / $ eject 5. After upgrading, execute another backup of the System Manager. See Backing Up Current Administration from System Manager. To upgrade System Manager using an ISO image: 1. Login to a console on the System Manager server or SSH login with root privilege. 2. Transfer the System Manager ISO image to the System Manager server. 3. If you are upgrading to Service Pack 1, enter the following commands on the command line: $ mkdir /iso $ mount o ro,loop /home/craft/avmgmt iso /iso $ cd /iso $ bash install.sh 4. If you are upgrading to Service Pack 2, enter the following commands on the command line: $ mkdir /iso $ mount o ro,loop /home/craft/avmgmt iso /iso $ cd /iso $ bash install.sh 5. When the upgrade has completed, enter the following commands: $ cd / $ umount /iso 6. Execute another backup of the System Manager. See Backing Up Current Administration from System Manager. This completes the installation of the System Manager. At this point you must reset the product ID s that were noted above. Enter the ID s using the following commands, where XXXXXXXXXX represents the 10 digit ID s from the previous commands for SM, SMELEM, and SpiritAgent. The last command (service) will cause current web sessions logged into System Manager to have to re-log in. # setproductid SM XXXXXXXXXX # setproductid SMELEM XXXXXXXXXX # spiritagentcli alarmid XXXXXXXXXX # service jboss restart 6

7 Note: if a web proxy is required to access the internet from the System Manager server, in order for remote alarm notifications to Avaya Services to function, the web proxy will have to be re-enabled in the System Manager Settings -> Service Profile Management -> SPIRIT 1.0 -> DataTransportConfig menu. The Web proxy, port, and UseProxy (true/false) field must be configured for your network to allow http proxy access for alarming. Enabling Trust Management 1. On System Manager, select Security > Trust Management > Enrollment Password. 2. For the Password Expires in field, use the drop-down menu to select the number of hours until expiration. 3. For the Certificate Allowed field, use the drop-down menu to select the number of certificates allowed. Allow at least 10 certificates per Session Manager instance. 4. Enter your chosen password in the Password field or click Generate. Be sure to write it down. This password will be used during the installation/upgrade of Session Manager. 5. Select Done. The password and time left to expiration will be displayed on the screen. Denying New Service for a Session Manager Instance 1. On System Manager, navigate to Session Manager>System State Administration. 2. Select the first Session Manager instance you wish to upgrade. 3. Select Service State > Deny New Service. This system will be referred to as Session Manager Select Deny New Service. Upgrading Session Manager to new Service Pack Note: Service Pack 2 can only be installed on systems currently running Service Pack On System Manager, select Session Manager > System State Administration. 2. Take note of the Active Call Count for Session Manager 1. This number indicates how many calls are still being routed through that Session Manager. These are calls that were already up before Session Manager 1 was placed in the denial state. To avoid negatively impacting the behavior of any calls, wait until this number is zero before proceeding (refresh the page to update the count). At the administrator s discretion, the upgrade may proceed while this number is not zero, with the understanding that in-dialog SIP events will not be processed for the remaining calls. 7

8 3. Upgrade the Session Manager. There are two ways to upgrade Session Manager: using a CD or using an ISO image. If you download the ISO images of the installer files from PLDS and then copy them to the Session Manager server using scp or winscp, you can mount them without copying to physical media. To upgrade Session Manager using a CD: 1. Login to a console on the Session Manager server or SSH login with root privilege. 2. Insert the Session Manager installation media into the Session Manager and mount the drive using the following commands: $ mount /dev/cdrom /mnt/ $ cd /mnt/ 3. Execute the upgrade.sh script. This installation takes approximately 30 minutes. $./upgrade.sh 4. When the upgrade has completed, eject the installation media with the following commands: $ cd / $ eject To upgrade Session Manager to Service Pack 1 using an ISO image: 1. Login to a console on the Session Manager server or SSH login with root privilege. 2. Transfer the Session Manager ISO image to the Session Manager server. 3. Enter the following commands on the command line: $ mkdir /iso $ mount o ro,loop /home/craft/avmgmt installer.iso /iso $ cd /iso 4. Execute the upgrade.sh script. This installation takes approximately 30 minutes. $ bash upgrade.sh 5. When the upgrade has completed, enter the following commands: $ cd / $ umount /iso This completes the upgrade of the Session Manager to Service Pack 1. To upgrade Session Manager to Service Pack 2 using an ISO image: Assuming the Session Manager and System Manager systems have previously been upgraded to Service Pack 1, either the craft or cust accounts may now be used to perform the Session Manager Service Pack 2 upgrade process. 1. Login to a console on the Session Manager server or SSH login with either the craft or cust login. 8

9 2. Copy the Session Manager Service Pack 2 ISO image to the Session Manager server via scp or from a USB thumb drive to your $HOME directory. To copy the ISO image from a USB thumb drive, insert the thumb drive into the USB port on the front of the server and enter the following commands to copy the ISO image to the local disk HOME directory: $ mount /usbthumb $ cp /usbthumb/asm installer.iso $HOME $ cd $HOME $ umount /usbthumb 3. Once the file is copied to the $HOME directory, execute the upgradesm script from the same directory (e.g., /home/cust for the cust login). This installation takes approximately 30 minutes. $./upgradesm $HOME/asm installer.iso 6. When the upgrade has completed, unmount the ISO image that was previously mounted: $ umount /iso This completes the upgrade of the Session Manager to Service Pack 2. Placing Upgraded Session Manager into Service 1. Log into System Manager and navigate to the Session Manager > Maintenance Tests page. 2. Select the newly upgraded system from the drop-down menu and click on Execute All Tests. All tests should pass. 3. Navigate to the Session Manager > Data Replication Status page. 4. Verify that the entry for Session Manager 1 is populated. 5. Wait until the Records Pending Update number is zero. Refresh the page as necessary. 6. Navigate to the Session Manager > System State Administration page. 7. Note that only Session Manager 1 should be in the Management Enabled state. 8. Place Session Manager 1 into the Accept New Service state. At this point, new SIP requests should be able to flow to Session Manager If any SIP Monitoring is provisioned for Session Manager 1, navigate to Session Manager > SIP Monitoring and verify that links are up. It may take up to 15 minutes for data on this page to be updated. Administrators may also wish to perform a test call through Session Manager Verify that Product IDs are correct. See Product IDs for Session Manager and System Manager. Upgrading Remaining Session Managers Once the sanity of the first Session Manager has been verified, notify the Avaya representative or Business Partner to begin the process of updating subsequent Session Managers, repeating 9

10 the process of denying new service to the targeted Session Manager, upgrading targeted Session Manager, and placing the freshly upgraded Session Manager back into service. System State Administration of a Session Manager instance Before you start a maintenance operation such as replacing a server of a Session Manager, you must block new incoming calls but wait for the current calls to terminate. Similarly, after completing the maintenance operation, you must: Verify Data Replication has occurred. Allow incoming calls for processing The System State Administration page enables you to perform some of these operations. In addition, you can use this page to view the following information for each of the configured Session Managers: Current administrative and service states Version information Timestamp of the last state change Call count for currently active calls Viewing the Service and Management State of a Session Manager instance From the navigation panel, select Session Manager > System State Administration. The System State Administration page displays all the configured Session Manager instances, their current administrative and service states, version, last service change, and the active call count. Modifying the Service and Management State of a Session Manager instance 1. From the navigation panel, select Session Manager > System State Administration. 2. Select one or more of the required Session Managers for modifying the service and management state from the Session Manager Instances list. You can use the following options to modify the service and management state of the selected Session Manager instances: Disabling Management of a Session Manager instance Enabling Management of a Session Manager instance Denying New Service for a Session Manager instance Accepting New Service for a Session Manager instance 10

11 Disabling Management of a Session Manager instance This action will sever the management link between System Manager and Session Managers, making administrative changes impossible until the link is re-enabled. 1. From the navigation panel, select Session Manager > System State Administration. 2. To disable administration but to allow call processing for a Session Manager, select the Session Manager from the list and click Management Disabled. 3. On the Management Disabled Confirmation page, click Disable Management. Enabling Management of a Session Manager instance This action will recreate the management link between System Manager and Session Managers, making administrative changes replicate to this Session Manager instance. 1. From the navigation panel, select Session Manager > System State Administration. 2. To enable administration for a Session Manager for which it has been disabled, select the Session Manager from the list and click Management Enabled. 3. On the Management Enabled Confirmation page, click Enable Management. Denying New Service for a Session Manager instance This action will prevent new SIP requests from being routed by that Session Manager. In a properly administered system, this will result in requests being rerouted through other Session Manager instances. SIP Entities which have Entity Links to the Session Manager that is denying new service may alarm that the Session Manager is out of service. This is expected behavior. 1. Select Session Manager > System State Administration. 2. To block incoming calls but to wait for termination of active calls for a Session Manager, select the Session Manager from the list and click Deny New Service. 3. On the Deny New Service Confirmation page, click Deny New Service. Accepting New Service for a Session Manager instance The default state of the Session Manager after installing or upgrading Session Manager software is Deny New Service. In addition, the administrator may intentionally take the system out of service for maintenance. By choosing to Accept New Service, all new requests targeted for this Session Manager will resume routing through this Session Manager instance. 1. Select Session Manager > System State Administration. 2. To allow incoming calls for processing for a Session Manager for which they have been blocked, select the Session Manager from the list and click Accept New Service 3. On the Accept New Service Confirmation page, click Accept New Service 11

12 Restoring the System Manager data 1. From the navigation panel, select Settings > Backup and Restore. 2. Select Restore. 3. Choose the backup file from the drop down list or manually enter the path to the local backup file, or, if remote, enter the scp server access information and path to backup file. 4. If choosing Remote, enter the required scp server access information. The Remote option displays the following information: SCP Server IP IP address of the remote scp server SCP Server Port valid scp port on the remote server (standard port is 22) User Name valid user name on the remote SCP server Password enter the password for the above user access to the SCP server NOTE- the user password must meet the following rules: Min length of 8 Minimum number of character types (lowercase, uppercase, numeric, non-alphanumeric) No repeated and/or sequential characters File Name enter the full path and filename to the archive file 5. Click Restore to initiate the restore of the archived data. The user will receive the following warning: Restore operation will terminate all sessions and no services will be available till the operation completes. Click on Restore to continue or click on cancel to abort the operation. 6. Select Restore to continue or Cancel if you wish to abort the restore operation. 7. An indication will not be given to the user when the restore has been completed. It will appear as if the connection has timed out. You will need to reconnect to the System Manager URL and log in at the prompt (ie

13 Recovery from a Failed Upgrade If at any point an administrator determines that the upgrade has failed and would like to roll back to a previous installation of Session Manager, the following procedures should be used. Failed Upgrade Requirements A system consisting of System Manager and zero or more Session Managers exists and is running a newer software version than the previous version. A backup of system provisioning was created using System Manager before initially upgrading from the desired rollback target release. The backup file must have been made with the previous release. The system hardware is compliant with the previous release. The IP address and host name of the System Manager and managed Session Managers need to have remained the same as what was archived in the backup file being used. Session Manager and System Manager installation scripts for the current release and the previous release are available. It is recommended that the rollback be scheduled during hours of no or little system activity. While it is possible to roll back Avaya Session Manager without affecting service, it takes time for service to be redirected around each Session Manager being downgraded. This time increases with system activity. Disable Management for all Session Manager Instances This action will sever the management link between System Manager and Session Managers, making administrative changes impossible until the link is re-enabled. 1. From System Manager, navigate to Session Manager >System State Administration. 2. Select all listed instances and choose Management Disabled. Uninstall System Manager 1. Change directory to the current System Manager installation directory. Mount the current release installation media if needed $ mount /dev/cdrom /mnt $ cd /mnt 2. Execute the uninstall.sh script. $./uninstall.sh 3. Enter yes when prompted. You will receive an indication when the uninstall process has completed. You will be prompted to log out of the current session and log back in to restore your environment to its state before a System Manager installation was executed. 4. Logout and log back in as instructed. 13

14 5. Unmount and eject the media with the following commands: $ cd / $ eject Downgrade System Manager 1. Insert the previous release System Manager installation media into the System Manager and mount the drive $ mount /dev/cdrom /mnt/ $ cd /mnt/ 2. Execute the install.sh script with the clean option. This installation takes approximately 90 minutes. $./install.sh clean 3. Restore the System Manager using the backup file that was created on this same downgrade release. See Restoring the System Manager data for the procedure. Note: The web browser session will expire after the restore operation begins. You will need to log back into the System Manager after the restore has completed. Downgrade Session Managers Execute the following steps for each Session Manager. Within this section, the specific Session Manager will be referred to simply as Session Manager. If the Session Manager does not need to be downgraded (rollback was initiated before an upgrade was completed), do the following: 1. Log into System Manager and navigate to Session Manager >System State Administration. Verify that the version number in the far right field is the same as the version of System Manager. 2. Enable Management for Session Manager. 3. Navigate to the Session Manager > Data Replication Status page. 4. Verify that the entry for Session Manager is populated. Wait, refreshing the page if necessary, until the Records Pending Update number is zero. 5. Next, navigate to the Session Manager > System State Administration page. Session Manager should be in the Management Enabled state and the Accept New Service state. 6. If any SIP Monitoring is provisioned for Session Manager, navigate to Session Manager > SIP Monitoring and verify that links are up. It may take up to 15 minutes for data on this page to be updated. If possible given administration, administrators may also wish to perform a test call through Session Manager. 14

15 If the Session Manager needs to be downgraded, do the following: 1. Navigate to Session Manager > System State Administration. 2. Select the Session Manager instance you wish to downgrade. 3. Select Deny New Service. Downgrade Session Manager 1. Log in to the newly-downgraded System Manager. 2. Navigate to Session Manager > System State Administration. Take note of the Active Call Count for Session Manager 1. This number indicates how many calls are still being routed through that Session Manager. These are calls that were already up before Session Manager 1 was placed in the denial state. To avoid negatively impacting the behavior of any calls, wait until this number is zero before proceeding (refresh the page to update the count). At the administrator s discretion, the upgrade may proceed while this number is not zero, with the understanding that in-dialog SIP events will not be processed for the remaining calls. 3. When the administrator has determined to proceed, notify the Avaya representative/avaya Business Partner to begin the Session Manager installation of the previous release for the first Session Manager instance. Place Downgraded Session Manager into Service 1. Log into System Manager and navigate to the Session Manager > Maintenance Tests page. Select the newly downgraded system from the drop-down menu and click on Execute All Tests. All tests should pass. 2. Navigate to the Session Manager > Data Replication Status page. 3. Verify that the entry for the Session Manager is populated. Wait, refreshing the page if necessary, until the Records Pending Update number is zero. 4. Next, navigate to the Session Manager > System State Administration page. Place the Session Manager into the Accept New Service state. At this point, new SIP requests should be able to flow to this Session Manager. 5. If any SIP Monitoring is provisioned for the Session Manager, navigate to Session Manager >SIP Monitoring and verify that links are up. It may take up to 15 minutes for data on this page to be updated. If possible given administration, administrators may also wish to perform a test call through this Session Manager. Downgrade Remaining Session Managers When the sanity of the first Session Manager has been verified, begin the process of downgrading subsequent Session Managers, repeating the process of denying new service to the targeted Session Manager, downgrading the targeted Session Manager, and placing the newly downgraded Session Manager back into service. 15

16 Product IDs for Session Manager and System Manager At installation time, the Avaya technician or customer will register the new system using the Functional Location (FL) and product type. At that time Product IDs will be provided for each managed element for the purpose of alarm reporting. Product IDs (or Alarm IDs) are assigned to the various managed elements and used as part of the identification of source of the alarm for each installed server. The CLI commands setproductid and getproductid are used to set and read the product ID for the managed elements. The CLI command spiritagentcli is used for assignment of the resident SAL agent product ID. These CLI commands all require root permission to run. Session Manager Product IDs Each Session Manager requires assignment of a product ID for five different managed elements ASM (Session Manager), ASMAS (SIP A/S), ASM100 (Security Module), ASMPLT( OS/Platform/ThirdParty), and SALASM (SAL Agent) Set Product ID Read Product ID setproductid ASM 8XXXXXXXXX setproductid ASMAS 8XXXXXXXXX setproductid ASM100 8XXXXXXXXX setproductid ASMPLT 8XXXXXXXXX spiritagentcli alarmid 5XXXXXXXXX 1) getproductid ASM getproductid ASMAS getproductid ASM100 getproductid ASMPLT spiritagentcli (menu Note: SALASM product ID starts with 5 and the other managed element will start with 8 System Manager Product IDs Each System Manager requires assignment of a product ID for three different managed elements SM, SMELEM, and SALSM (SAL agent) Set Product ID Read Product ID setproductid SM 8XXXXXXXXX setproductid SMELEM 8XXXXXXXXX SMELEM spiritagentcli alarmid 5XXXXXXXXX 1) getproductid SM getproductid spiritagentcli (menu Note: SALASM product ID starts with 5 and the other managed element will start with. 16

17 Testing the Installation Before running these tests, you must verify that the software is installed and configured properly, and that the servers and applications are communicating before leaving the customer s site. 1. Log on to the System Manager Common Console. 2. Click Session Manager > Maintenance Tests in the left navigation pane. 3. Select the System Manager server in the drop-down list and click Execute All Tests 4. Verify that all tests show Success 5. If the data replication test fails, click Session Manager > Data Replication Status in the left navigation pane to identify which Session Manager is having replication problems. 6. Click Session Manager > Security Module Status to display SM100 card status. 7. Verify that Security Module Deployment is UP for all Session Managers. 8. Click Session Manager > System State Administration in the left navigation pane. 9. Verify that the installed software versions of all Session Managers are the same version and that all Session Manager servers are in the Management Enabled state. 10. Click Session Manager > Maintenance Tests in the left navigation pane. 11. Select each Session Manager instance and click Execute All Tests. 12. Verify that all tests show Success 17