Avaya Solutions Platform 130 & S8300 Series

Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10)

February 2026

Release [Link].0

Rev 5.0
© 2026, Avaya LLC. All Rights Reserved.
Licenses
Notice THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTPS://[Link]/LICENSEINFO, UNDER THE
While reasonable efforts have been made to ensure that the information in
LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya Products)” OR SUCH
this document is complete and accurate at the time of printing, Avaya
SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO
assumes no liability for any errors. Avaya reserves the right to make changes
ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA
and corrections to the information in this document without the obligation to
SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE,
notify any person or organization of such changes.
OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A
COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL
Documentation disclaimer
PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
“Documentation” means information published in varying mediums which
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS
may include product information, operating instructions and performance
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE
specifications that are generally made available to users of products.
OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO
Documentation does not include marketing materials. Avaya shall not be
TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR
responsible for any modifications, additions, or deletions to the original
SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING,
published version of Documentation unless such modifications, additions, or
DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING
deletions were performed by or on the express behalf of Avaya. End User
OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY
agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and
FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE
employees against all claims, lawsuits, demands and judgments arising out
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS
of, or in connection with, subsequent modifications, additions or deletions to
“YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS
this documentation, to the extent made by End User.
AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC.
OR THE APPLICABLE AVAYA AFFILIATE (“AVAYA”). Avaya grants You a
Link Disclaimer
license within the scope of the license types described below, with the
Avaya is not responsible for the contents or reliability of any linked websites
exception of Heritage Nortel Software, for which the scope of the license is
referenced within this site or Documentation provided by Avaya. Avaya is not
detailed below. Where the order documentation does not expressly identify a
responsible for the accuracy of any information, statement or content
license type, the applicable license will be a Designated System License as
provided on these sites and does not necessarily endorse the products,
set forth below in the Designated System(s) License (DS) section as
services, or information described or offered within them. Avaya does not
applicable. The applicable number of licenses and units of capacity for which
guarantee that these links will work all the time and has no control over the
the license is granted will be one (1), unless a different number of licenses or
availability of the linked pages.
units of capacity is specified in the documentation or other materials available
to You. “Software” means computer programs in object code, provided by
Warranty
Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-
Avaya provides a limited warranty on Avaya hardware and software. Refer to
installed on hardware products, and any upgrades, updates, patches, bug
your sales agreement to establish the terms of the limited warranty. In
fixes, or modified versions thereto. “Designated Processor” means a single
addition, Avaya’s standard warranty language, as well as information
stand-alone computing device. “Server” means a set of Designated
regarding support for this product while under warranty is available to Avaya
Processors that hosts (physically or virtually) a software application to be
customers and other parties through the Avaya Support website:
accessed by multiple users. “Instance” means a single copy of the Software
[Link]
executing at a particular time: (i) on one physical machine; or (ii) on one
getGenericDetails?detailId=C20091120112456651010 under the link
deployed software virtual machine (“VM”) or similar deployment.
“Warranty & Product Lifecycle” or such successor site as designated by
Avaya. Please note that if You acquired the product(s) from an authorized
License types
Avaya Channel Partner outside of the United States and Canada, the
Designated System(s) License (DS). End User may install and use each copy
warranty is provided to You by said Avaya Channel Partner and not by
or an Instance of the Software only: 1) on a number of Designated
Avaya. “Hosted Service” means an Avaya hosted service subscription that
Processors up to the number indicated in the order; or 2) up to the number of
You acquire from either Avaya or an authorized Avaya Channel Partner (as
Instances of the Software as indicated in the order, Documentation, or as
applicable) and which is described further in Hosted SAS or other service
authorized by Avaya in writing. Avaya may require the Designated
description documentation regarding the applicable hosted service. If You
Processor(s) to be identified in the order by type, serial number, feature key,
purchase a Hosted Service subscription, the foregoing limited warranty may
Instance, location or other specific designation, or to be provided by End
not apply but You may be entitled to support services in connection with the
User to Avaya through electronic means established by Avaya specifically for
Hosted Service as described further in your service description documents
this purpose.
for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner
(as applicable) for more information.
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by Avaya
Hosted Service
as part of its purchase of the Nortel Enterprise Solutions Business in
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA
December 2009. The Heritage Nortel Software is the software contained
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
within the list of Heritage Nortel Products located at
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR
[Link] under the link “Heritage Nortel
HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE,
Products” or such successor site as designated by Avaya. For Heritage
HTTPS://[Link]/LICENSEINFO UNDER THE LINK “Avaya
Nortel Software, Avaya grants Customer a license to use Heritage Nortel
Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS
Software provided hereunder solely to the extent of the authorized activation
DESIGNATED BY AVAYA AND ARE APPLICABLE TO ANYONE WHO
or authorized usage level, solely for the purpose specified in the
ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR
Documentation, and solely as embedded in, for execution on, or for
USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO,
communication with Avaya equipment. Charges for Heritage Nortel Software
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU
may be based on extent of activation or use authorized as specified in an
ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS
order or invoice.
“YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF YOU ARE
ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER
LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY Copyright
TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT Except where expressly stated otherwise, no use should be made of
HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE materials on this site, the Documentation, Software, Hosted Service, or
TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED hardware provided by Avaya. All content on this site, the documentation,
SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED Hosted Service, and the product provided by Avaya including the selection,
SERVICE. arrangement and design of the content is owned either by Avaya or its
licensors and is protected by copyright and other intellectual property laws
including the sui generis rights relating to the protection of databases. You IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (II)
may not modify, copy, reproduce, republish, upload, post, transmit or DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER
distribute in any way any content, in whole or in part, including any code and ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A
software unless expressly authorized by Avaya. Unauthorized reproduction, VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
transmission, dissemination, storage, and or use without the express written GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
consent of Avaya can be a criminal, as well as a civil offense under the INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE
applicable law. OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://[Link].

Virtualization Compliance with Laws

The following applies if the product is deployed on a virtual machine. Each You acknowledge and agree that it is Your responsibility for complying with
product has its own ordering code and license types. Unless otherwise any applicable laws and regulations, including, but not limited to laws and
stated, each Instance of a product must be separately licensed and ordered. regulations related to call recording, data privacy, intellectual property, trade
For example, if the end user customer or Avaya Channel Partner would like secret, fraud, and music performance rights, in the country or territory where
to install two Instances of the same type of products, then two products of the Avaya product is used.
that type must be ordered.
Preventing Toll Fraud
Third Party Components “Toll Fraud” is the unauthorized use of your telecommunications system by
“Third Party Components” mean certain software programs or portions an unauthorized party (for example, a person who is not a corporate
thereof included in the Software or Hosted Service may contain software employee, agent, subcontractor, or is not working on your company's behalf).
(including open-source software) distributed under third party agreements Be aware that there can be a risk of Toll Fraud associated with your system
(“Third Party Components”), which contain terms regarding the rights to use and that, if Toll Fraud occurs, it can result in substantial additional charges for
certain portions of the Software (“Third Party Terms”). As required, your telecommunications services.
information regarding distributed Linux OS source code (for those products Avaya Toll Fraud intervention
that have distributed Linux OS source code) and identifying the copyright If You suspect that You are being victimized by Toll Fraud and You need
holders of the Third Party Components and the Third Party Terms that apply technical assistance or support, call Technical Service Center Toll Fraud
is available in the products, Documentation or on Avaya’s website at: Intervention Hotline at +1-800-643-2353 for the United States and Canada.
[Link] or such successor site as designated by For additional support telephone numbers, see the Avaya Support website:
Avaya. The open-source software license terms provided as Third-Party [Link] or such successor site as designated by Avaya.
Terms are consistent with the license rights granted in these Software
License Terms, and may contain additional rights benefiting You, such as Security Vulnerabilities
modification and distribution of the open-source software. The Third-Party Information about Avaya’s security support policies can be found in the
Terms shall take precedence over these Software License Terms, solely with Security Policies and Support section of [Link]
respect to the applicable Third-Party Components to the extent that these Suspected Avaya product security vulnerabilities are handled per the Avaya
Software License Terms impose greater restrictions on You than the Product Security Support Flow
applicable Third-Party Terms. ([Link]
The following applies only if the H.264 (AVC) codec is distributed with the
product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT Downloading Documentation
PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR For the most current versions of Documentation, see the Avaya Support
OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) website: [Link] or such successor site as designated by
ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC Avaya.
VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A
CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS Contact Avaya Support
OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC See the Avaya Support website: [Link] for product or
VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY Hosted Service notices and articles, or to report a problem with your Avaya
OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM product or Hosted Service. For a list of support telephone numbers and
MPEG LA, L.L.C. SEE HTTP://[Link]. contact addresses, go to the Avaya Support website:
[Link] (or such successor site as designated by Avaya),
Service Provider scroll to the bottom of the page, and select Contact Avaya Support.
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S HOSTING
OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED Trademarks
SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD- The trademarks, logos and service marks (“Marks”) displayed in this site, the
PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE Documentation, Hosted Service(s), and product(s) provided by Avaya are the
INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD-PARTY registered or unregistered Marks of Avaya, its affiliates, its licensors, its
SUPPLIER. AN AVAYA CHANNEL PARTNER’S HOSTING OF AVAYA suppliers, or other third parties. Users are not permitted to use such Marks
PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF without prior written consent from Avaya or such third party which may own
THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD-PARTY the Mark. Nothing contained in this site, the Documentation, Hosted
SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT Service(s) and product(s) should be construed as granting, by implication,
SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS estoppel, or otherwise, any license or right in and to the Marks without the
REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE express written permission of Avaya or the applicable third party.
AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE, Avaya is a registered trademark of Avaya Inc.
DIRECTLY FROM THE APPLICABLE THIRD-PARTY SUPPLIER. All non-Avaya trademarks are the property of their respective owners. Linux®
is the registered trademark of Linus Torvalds in the U.S. and other countries.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS
HOSTING ANY PRODUCTS THAT USE OR EMBED THE H.264 CODEC
OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES
AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR
ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC)
CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE
FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO
Contents
About this task...................................................................................................................................................... 5
Prerequisites ......................................................................................................................................................... 5
1. Supported Upgrade Path.............................................................................................................................. 6
2. Avaya Solutions Platform 130/S8300 certified images ............................................................................... 6
3. ESXi Host Upgrade to R6.x (KVM on RHEL 8.10).......................................................................................... 7
4. Updating to R6.[Link] (KVM on RHEL 8.10) from R6.[Link] (KVM on RHEL 8.10) ................................... 7
4.1 Transferring R6.x Update Files to The Host ....................................................................................... 7
4.2 Checking Update File integrity ........................................................................................................... 8
4.3 Conducting the KVM on RHEL Host Update ....................................................................................... 9
4.4 Validating the KVM on RHEL Host Update ....................................................................................... 15
5 Licensing Procedure ................................................................................................................................... 16
Finding documents on the Avaya Support website .......................................................................................... 16
Avaya Documentation Center Navigation ......................................................................................................... 17
Support ............................................................................................................................................................... 17

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 4
Version Control Table

Version Author Purpose/Change Date

Number
Rev 1.0 R&D Engineering Team. Initial revision. February 2025
Rev 2.0 R&D Engineering Team. Release of ASP [Link].1 April 2025
Rev 3.0 R&D Engineering Team. Release of ASP [Link].0 June 2025
Rev 4.0 R&D Engineering Team. Release of ASP [Link].0 October 2025
Rev 5.0 R&D Engineering Team. Release of ASP [Link].0 February 2026

About this task

Follow the steps outlined in this document when planning and conducting updates to KVM on RHEL 8.10
hosts running on ASP 130 & S8300E servers using the Avaya certified and approved files.

The content in this documentation is specifically intended for Avaya Solutions Platform 130 and S8300 (ASP
130/ASP S8300) servers. It is not applicable to other ASP server models or series, such as ASP 110, ASP 120 or
ASP 4200.

Avaya will provide a custom update bundle applicable for R660xs, R640 & S8300E servers. This ensures that
all updates are fully compatible with the underlying hardware, firmware and drivers running on supported
ASP servers.

Warning
To ensure the ongoing support, performance, security and reliability of the ASP130/S8300 servers, it is crucial
to only use files and software that have been specifically approved by Avaya. The use of unauthorized files
can expose the servers and applications to potential risks and will result in an unsupported configuration.

Refrain from:

• Downloading software directly from external sites such as those posted in the Red Hat or Dell web
portals.
• Obtaining software from any source other than Avaya-approved channels, to ensure proper
functionality, security, and support.

Prerequisites
• Access to the ASP server over the customer network (MGMT interface) or by directly connecting a
service laptop to the server’s services port.
• Download the following Avaya approved files from PLDS:

➢ ASP 130 download id:

▪ ASP000000051 - [Link]

➢ ASP 8300 download id:

▪ ASP000000138 - [Link]
• Ensure proper application backups have been taken prior to conducting the update activity.
• It is considered best practice to document all hypervisor networking configuration values, including IP
address, subnet mask, default gateway, DNS, NTP, hostname, and FQDN.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 5
 • Before proceeding with the KVM on RHEL 8.10 update activity, ensure that all existing virtual
machines (VMs) running on the server are gracefully shut down and powered off. This step will help
optimize the overall update process. For detailed prerequisites, guidelines, and procedures, refer to
the relevant application documentation.
• custadm credentials. Avaya services account (sroot) via EASG authentication can also be used.

1. Supported Upgrade Path

Reference to the latest Avaya Solutions Platform 130 Release Notes available in
[Link] for detailed supported update paths. If determined that one
or multiple step-up updates are required before a server can be updated to ASP [Link].0
or later, reference to previously released ASP 130 update documents respectively.

• Customers are ONLY allowed to update to ASP [Link].0 or later from ASP [Link].0. Reference to the
latest Avaya Solutions Platform 130/S8300 release notes available in [Link]

2. Avaya Solutions Platform 130/S8300 certified images

Based on RHEL
ASP Release Latest Avaya Certified Image Notes
version
Avaya customized KVM on RHEL 8.10
ASP 130/S8300 R6.0 ASP_R6_all_4.[Link] RHEL 8.10 includes Avaya av-asp-tools-1.2-
1.el8.x86_64 & EASG rpms.
Avaya customized update bundle for KVM
ASP 130/S8300 av-asp-tools-1.5-3.el8.x86_64.rpm
RHEL 8.10 on RHEL 8.10.
R6.[Link] [Link]
Avaya av-asp-tools rpm installs separately.
Avaya customized update bundle for KVM
ASP 130/S8300
[Link] RHEL 8.10 on RHEL 8.10 includes Avaya av-asp-
R6.[Link]
tools-1.6-2.el8.x86_64.rpm.
Avaya customized update bundle for KVM
ASP 130/S8300
[Link] RHEL 8.10 on RHEL 8.10 includes Avaya av-asp-
R6.[Link]
tools-1.7-1.el8.x86_64
Avaya customized update bundle for KVM
on RHEL 8.10 includes:
ASP 130/S8300 • Avaya av-asp-tools-1.8-
[Link] RHEL 8.10
R6.[Link] 1.el8.x86_64
• av-asp-tools-sec-1.1-
1.el8.x86_64
Avaya customized update bundle for KVM
ASP 130/S8300
[Link] RHEL 8.10 on RHEL 8.10 includes:
R6.[Link]
• av-asp-tools-1.11-1.el8.x86_64.rpm

Note: Image information for 5.1.x and earlier releases reference to previously released ASP 130 upgrade
documents.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 6
3. ESXi Host Upgrade to R6.x (KVM on RHEL 8.10)

This upgrade path is not supported. A complete system re-installation is required.

Reference to the latest Avaya Solutions Platform 130 Release Notes available in
[Link] for supported upgrade paths.

4. Updating to R6.[Link] (KVM on RHEL 8.10) from R6.[Link]

(KVM on RHEL 8.10)

Warning: Direct updates to R6.[Link] from [Link].0 or earlier ASP releases are not supported.
Reference to the latest Avaya Solutions Platform 130/S8300 Release Notes available in
[Link] for supported upgrade paths.

Important: The steps documented in this section are only applicable to hosts running the GA version of
ASP R6.[Link] or later.

Prerequisite
• ASP 130 server must be running R6.[Link] (KVM on RHEL 8.10) or later prior to continuing.

Note: If a step-up upgrade is required, reference to previously released ASP 130 Upgrade documents.

New with this image

• Reference to the latest Avaya Solutions Platform 130 Release Notes available in
[Link] for detailed information about fixes, enhancements and known
issues.

4.1 Transferring R6.x Update Files to The Host

Prerequisites

• Ensure there is sufficient space in the system to transfer update files.

• If applicable, remove older images, unnecessary files from previous installations, including
those in staging folder used for VM deployment.

Warning: carefully review the files to be removed, especially those with a QCOW2 extension, to ensure
they are not currently being used by a virtual machine in production.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 7
Procedure

4.1.1 Transfer the previously downloaded update file to the local PC that will be used to access the
hypervisor management interface during the maintenance activity. For detailed file information,
please refer to the Prerequisites section.
4.1.2 ASP R6.[Link] or later ONLY - Using a tool such as WinSCP (not provided by Avaya) transfer
the previously downloaded ASP Service Pack for example: [Link] to the
Host /var/lib/libvirt/stating directory.

Note: Authenticate using the existing custadm credentials.

The following figures are just a representation and should only be used as an example.

ASP R6.[Link] or later Example

4.2 Checking Update File integrity

4.2.1 Log in to the corresponding KVM on RHEL 8.10 host by using a Secure Shell (SSH) client e.g.,
Putty (Not provided by Avaya).
4.2.2 Authenticate using the existing custadm credentials.
4.2.3 Run the following command to ensure files have been transferred to the corresponding location:

ASP R6.[Link] and later

• ls -l /var/lib/libvirt/staging/

Note: The following output is just a representation and should only be used as an example.
[custadm@asp130-r660xs-20841 ~]$ ls -l /var/lib/libvirt/staging/
total 6914282
-rw-r-----. 1 custadm custadm 6914282 Jan 20 06:36 [Link]

4.2.4 Perform sha256 checksums by executing the following cli commands:

Note: If the checksum values do not match those provided on the PLDS and Avaya Support
website, STOP! .The files may have been corrupted during transfer. Attempt to re-download and
transfer the files again. If the issue persists, contact Avaya Support for further assistance.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 8
 ASP R6.[Link] and later
➢ sha256sum /var/lib/libvirt/staging/[Link]

Note: The following output is just a representation and should only be used as an example.
[custadm@asp130-r660xs-20841 ~]$ sha256sum /var/lib/libvirt/staging/update-asp-all-
[Link].[Link]
470fdf377adb6723cca54e441e7ed6995bcf308ef30611493cd91319965c5142
/var/lib/libvirt/staging/[Link]

4.2.5 Verify the current system software version by executing the following command:
swversion

Note: The following output is just a representation and should only be used as an example.
[custadm@asp130-r660xs-20841 ~]$ swversion
Operating System: Linux 4.18.0-553.80.1.el8_10.x86_64
Kernel Build Date: Oct 10 03:51 2025
Distribution: Red Hat Enterprise Linux release 8.10 (Ootpa)

Contains: Avaya Solutions Platform

Release: ASP Release [Link].0
Build Number: 4.6-4.8
Update Version: [Link].0
Update Installation Date: Dec 08 2025 17:32 UTC
SSP Version: 1
SSP Installation Date: Dec 22 2025 21:42 UTC
Virtualization Environment: KVM

====================== Updates Installed in the system ======================

[Link].0
SSP_1

4.3Conducting the KVM on RHEL Host Update

ASP R6.0.0.0 ONLY – Important Consideration:

The update script is not included in the R6.0.0.0 GA software baseline. Therefore, the av-asp-tools
RPM must be updated first before attempting to update the KVM on RHEL host.

4.2.6 If not already, log in to the corresponding KVM on RHEL 8.10 host by using a Secure Shell (SSH)
client e.g., Putty (Not provided by Avaya).
4.2.7 Authenticate using the existing custadm credentials.
4.2.8 Execute the following command to update the KVM on RHEL 8.10 Host:
➢ cd /var/lib/libvirt/staging/
➢ pwd > (Optional) This step helps ensure that the user is in the correct
folder location.
➢ ls -l

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 9
ASP R6.[Link] and later Output Example
[custadm@asp130-r660xs-20841 ~]$ cd /var/lib/libvirt/staging/
[custadm@asp130-r660xs-20841 staging]$ pwd
/var/lib/libvirt/staging
[custadm@asp130-r660xs-20841 staging]$ ls -l
total 6914282
-rw-r-----. 1 custadm custadm 6914282 Jan 20 06:36 [Link]

➢ asp-update-os [Link]
➢ To proceed type: yes

Output Example
[custadm@asp130-r660xs-20841 staging]$ asp-update-os [Link]
Execution logs will be available in: /var/log/asp/update_log_20260120072252.txt
Executing asp-update-os version 2
Temporary work directory used for processing the update bundle:
/var/lib/libvirt/staging/UBInstall_20260120072252
Checking bundle compatibility with current script version
Checking update bundle signature
/var/lib/libvirt/staging/UBInstall_20260120072252/rpms/[Link]: OK
Verified OK
The manifest signature has been verified and confirmed to be signed by Avaya.
Checking update bundle applicability on the system
Update [Link].0 will be installed on the system.
Checking if workspace partition has sufficient space to expand update bundle
Extracting update bundle
Verifying update bundle checksum
Applying the update bundle is a service-disrupting activity and may require the
following actions:
- Shutting down virtual machines (VMs)
- Restarting services
- Rebooting the system
Before proceeding further, please ensure that
- you do not have any other maintenance activity going on, and
- you do not have any other console/ssh session open to this system, and
- you are prepared for service disruption.

Please confirm if you would like to proceed.

Ready to proceed [yes OR no] ?

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 10
Warning: During the update process, the script will check for running virtual machines (VMs) and will
attempt to power them down gracefully. If the script is unable to power off all VMs within the allotted
time frame of 300 seconds per VM, the process will be halted, and manual intervention will be required.
Do not attempt to forcibly shut down VMs unless explicitly instructed by Avaya, as this could result in
data corruption. If the issue persists, we recommend halting the process and contacting Avaya Support
for further assistance.

The example below illustrates an update that was halted due to VMs being unable to power off.

➢ System starts updating.

The example below illustrates an update where the script successfully powered off any running VMs on
the host.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 11
Note: The following examples are provided for illustrative purposes only. Versions, package
labels, sizes, and dependencies may vary with each ASP service pack update.

Ready to proceed [yes OR no] ? yes

Updating MOTD messages to reflect ongoing update
Disabling SIGHUP SIGINT SIGQUIT SIGTERM SIGTSTP during update
Executing Common OS preinstall script
Checking for packages to be pruned from update
Gathering required information for pruning via dnf analysis. This may take a
few minutes.
Checking installation space requirement based on Size field of RPMs
......

Installation size of packages to-be-installed from the update bundle : 8391214

bytes
Installation size of corresponding removable installed packages : 8304297
bytes
Additional space required for update bundle packages installation : 85 K
Available space in root(/) partition: 7553416 K

The currently running virtual machines require to be shut down in order to

apply the update.
Shutting down Fiotester2-RHEL810 (max wait time 300 seconds)
..10
Shutting down Fiotester3-RHEL810 (max wait time 300 seconds)
..10
Shutting down Fiotester1-RHEL810 (max wait time 300 seconds)
..10
Updating the system packages. Please wait.
Dependencies resolved.
===============================================================================
=
Package Arch Version Repository Size
===============================================================================
=
Upgrading:
asp-easg-config noarch 1.0-3.el8 @commandline 23 k
av-asp-tools x86_64 1.11-1.el8 @commandline 94 k
cockpit x86_64 310.5-1.el8_10 @commandline 91 k
cockpit-bridge x86_64 310.5-1.el8_10 @commandline 501 k
cockpit-system noarch 310.5-1.el8_10 @commandline 5.2 M
cockpit-ws x86_64 310.5-1.el8_10 @commandline 983 k

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 12
The example below illustrates an update where the script did not detect any running VMs on the
host.
Ready to proceed [yes OR no] ? yes
Updating MOTD messages to reflect ongoing update
Disabling SIGHUP SIGINT SIGQUIT SIGTERM SIGTSTP during update
Executing Common OS preinstall script
Checking for packages to be pruned from update
Gathering required information for pruning via dnf analysis. This may take a
few minutes.
Checking installation space requirement based on Size field of RPMs
......

Installation size of packages to-be-installed from the update bundle : 8391214

bytes
Installation size of corresponding removable installed packages : 8304297
bytes
Additional space required for update bundle packages installation : 85 K
Available space in root(/) partition: 7553416 K

Updating the system packages. Please wait.

Dependencies resolved.
===============================================================================
=
Package Arch Version Repository Size
===============================================================================
=
Upgrading:
asp-easg-config noarch 1.0-3.el8 @commandline 23 k
av-asp-tools x86_64 1.11-1.el8 @commandline 94 k
cockpit x86_64 310.5-1.el8_10 @commandline 91 k
cockpit-bridge x86_64 310.5-1.el8_10 @commandline 501 k
cockpit-system noarch 310.5-1.el8_10 @commandline 5.2 M
cockpit-ws x86_64 310.5-1.el8_10 @commandline 983 k

➢ Once completed, the system will automatically reboot.

The example below illustrates a complete update where no VMs were running on the host
during the activity.
Installed products updated.

Upgraded:
[Link] av-asp-tools-1.11-1.el8.x86_64
cockpit-310.5-1.el8_10.x86_64 cockpit-bridge-310.5-1.el8_10.x86_64
cockpit-system-310.5-1.el8_10.noarch cockpit-ws-310.5-1.el8_10.x86_64

Complete!
SUCCESS: Update bundle version [Link].0 has been applied successfully.
The system is now being rebooted.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 13
 The example below illustrates an update where VMs were gracefully powered off by the script
during the activity.
Installed products updated.

Upgraded:
[Link] av-asp-tools-1.11-1.el8.x86_64
cockpit-310.5-1.el8_10.x86_64 cockpit-bridge-310.5-
1.el8_10.x86_64
cockpit-system-310.5-1.el8_10.noarch cockpit-ws-310.5-1.el8_10.x86_64

Complete!
SUCCESS: Update bundle version [Link].0 has been applied successfully.
Following virtual machines (VMs) were shut down earlier to apply the
update bundle.
Please ensure that these are powered on after the system has rebooted.
Fiotester2-RHEL810
Fiotester3-RHEL810
Fiotester1-RHEL810
The system is now being rebooted.

Note: Virtual machines (VMs) that are listed must be started manually. The ASP update script does
not preserve the VM’s state prior to the host update. Avaya strongly suggest configuring the auto-
start feature to reduce application down time.

Note: Virtual machines (VMs) that were shut down manually by the user, rather than by the
update script, will not be listed and will not automatically power on unless auto-start has been
configured for them. Avaya strongly suggest configuring the auto-start feature to reduce
application down time.

Warning!
Avaya follows Red Hat’s recommended practice of retaining the two latest kernel versions
after applying a kernel update. Upon Host reboot, the latest kernel becomes the default
and is used to automatically boot Red Hat Enterprise Linux.
Avaya strongly advises against modifying the boot menu or selecting a previous kernel
version during boot, as doing so may result in an unsupported configuration and could
expose the system to security vulnerabilities associated with the older kernel version.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 14
 Screen Example

4.4 Validating the KVM on RHEL Host Update

Note: Allow ~5 mins for ASP Server to fully reboot and be reachable over the network before attempting
to reconnect.

4.4.1 Log in to the corresponding KVM on RHEL 8.10 host by using a Secure Shell (SSH) client e.g., Putty
(Not provided by Avaya). Authenticate using custadm credentials.
4.4.2 Execute the following command to validate system version: swversion
Note: At this stage it is expected to have the KVM on RHEL host updated to the corresponding build
number. If the version on the updated host does not match the intended version STOP! and
restart the update process from the beginning prior to continuing with the next server.

Note: The following output is just a representation and should only be used as an example.

[root@asp130-r660xs-20841 ~]# swversion

Operating System: Linux 4.18.0-553.80.1.el8_10.x86_64
Kernel Build Date: Oct 10 03:51 2025
Distribution: Red Hat Enterprise Linux release 8.10 (Ootpa)
Contains: Avaya Solutions Platform
Release: ASP Release [Link].0
Build Number: 4.6-4.8
Installation Date: Dec 08 2025 17:16 UTC
Update Version: [Link].0
Update Installation Date: Jan 20 2026 14:26 UTC
SSP Version: 1
SSP Installation Date: Dec 22 2025 21:42 UTC
Virtualization Environment: KVM
====================== Updates Installed in the system ======================
[Link].0
SSP_1
[Link].0

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 15
 4.4.3 Execute the following command to validate the Avaya av-asp-tools running on the system:
• rpm -qa | grep av-asp
Note: The following output is just a representation and should only be used as an example.

[root@asp130-r660xs-20841 ~]# rpm -qa | grep av-asp

av-asp-tools-1.12-1.el8.x86_64
av-asp-tools-sec-1.0-3.el8.x86_64

As a good practice, remove any previous and current ASP update bundle files, including av-asp-
tools from the host before disconnecting.
4.4.4 When applicable, repeat entire procedure to the next KVM on RHEL 8.10 host. To minimize
service impact, always conduct system updates with one server at a time.

5 Licensing Procedure
With the introduction of KVM on RHEL 8.10, a specific license key is no longer required, unlike ASP R5.1.x
and earlier versions running ESXi. However, it is crucial for customers to maintain a record in PLDS for
every server, as both customers and Avaya will be subject to audits to ensure that right-to-use royalties
have been paid.

Finding documents on the Avaya Support website

Procedure

1. Go to [Link]
2. At the top of the screen, type your username and password and click Login.
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the list.
5. In Choose Release, select the appropriate release number.
The Choose Release field is not available if there is only one release for the product.
6. In the Content Type filter, click a document type, or click Select All to see a list of all available
documents.
For example, for user guides, click User Guides in the Content Type filter. The list only displays the documents
for the selected category.

7. Click Enter.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 16
 Avaya Documentation Center Navigation
For some programs, the latest customer documentation is now available on the Avaya Documentation Center website at
[Link]

IMPORTANT: For documents that are not available on Avaya Documentation Center, click More Sites > Support
on the top menu to open [Link]
Using the Avaya Documentation Center, you can:
• Search for keywords.
To filter by product, click Filters and select a product.

• Search for documents.

From Products & Solutions, select a solution category and product, and then select the appropriate
document from the list.

• Sort documents on the search results page.

• Click Languages to change the display language and view localized documents.
• Publish a PDF of the current section in a document, the section and its subsections, or the entire
document.
• Add content to your collection using My Docs ( ).
Navigate to the Manage Content > My Docs menu, and do any of the following:

- Create, rename, and delete a collection.

- Add topics from various documents to a collection.
- Save a PDF of the selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive collection that others have shared with you.
• Add yourself as a watcher using the Watch icon ( ).
Navigate to the Manage Content > Watchlist menu, and do the following:

- Enable Include in email notification to receive email alerts.

- Unwatched selected content, all content in a document, or all content on the Watch
list page.
As a watcher, you are notified when content is updated or deleted from a document, or the
document is removed from the website.

• Share a section on social media platforms, such as Facebook, LinkedIn, and X.

• Send feedback on a section and rate the content.

NOTE: Some functionality is only available when you log in to the website. The available functionality
depends on your role.

Support

Go to the Avaya Support website at [Link] for the most up-to-date documentation, product
notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues.
Use the online service request system to create a service request. 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.

February 2025 Updating to R6.[Link] (RHEL 8.10) from R6.[Link] (RHEL 8.10) Rev 5.0 pg. 17