Upgrading Avaya Session Border Controller for Enterprise

Chapter 1: Introduction

This document provides procedures for upgrading Avaya SBCE from Release 6.2, Release 6.3, and Release 7.0 to Release 7.1. It includes an upgrade checklist and upgrade procedures.

The primary audience for this document is anyone involved with upgrading and maintaining Avaya SBCE, including implementation engineers, field technicians, business partners, solution providers, and customers.

Change History

Warranty

Avaya provides a one-year limited warranty on Avaya SBCE hardware and 90 days on Avaya SBCE software. For warranty terms, refer to the sales agreement or applicable documentation. Standard warranty information and support details are available on the Avaya Support website: https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010.

For products acquired from an authorized Avaya Channel Partner outside the United States and Canada, warranty is provided by the partner.

A Hosted Service is an Avaya hosted service subscription. Terms of use for Hosted Services are available on the Avaya website: https://support.avaya.com/licenseinfo.

Chapter 2: Upgrade Overview and Specifications

Avaya Session Border Controller for Enterprise Upgrade Overview

This guide details the procedures for upgrading Avaya SBCE from Release 6.2 and 6.3 to Release 7.0, and from Release 7.0 to Release 7.1. The upgrade procedure depends on the current Avaya SBCE software version.

This guide covers the following upgrade procedures:

• Upgrading Avaya SBCE Release 6.2 to Avaya SBCE Release 7.0.
• Upgrading Avaya SBCE Release 6.3 to Release 7.0.
• Upgrading Avaya SBCE Release 7.0 to Release 7.1.

Perform the appropriate procedure based on your current Avaya SBCE release version.

Supported Hardware

Avaya SBCE Release 7.1 supports the following hardware:

• Dell R210 II
• Dell R210 II XL
• Dell R320
• Dell R330
• Dell R620
• Dell R630
• HP DL360 G8
• HP DL360 G9
• PortWell CAD 0208
• Portwell CAD 0230

For Avaya port matrix information, refer to Avaya Port Matrix: ASBCE.

Determining Whether EMS is Installed on an Amax Server

About this task: On Amax servers, Avaya SBCE does not support upgrades to Release 7.0 or later. Use this procedure to check if EMS is installed on an Amax server.

Procedure:

1. Log in as an 'ipcs' user on the EMS server and type sudo su to get root privileges.
2. Type dmidecode | grep 'Supermicro'.

For an Amax server, the output will be Product Name: Supermicro. For other servers, no data will be displayed.

Next Steps: If you have Avaya SBCE Release 6.2.1Q18 or 6.3, back up the existing configuration and restore it on a new server. Specific steps for HA configurations involving Amax, HP DL360 G7, and Dell servers are detailed in the document.

Determining Whether Avaya SBCE is Installed on an HP DL360 G7 Server

About this task: On HP DL360 G7 servers, Avaya SBCE does not support upgrades to Release 7.0 and later. Use this procedure to check if Avaya SBCE is installed on an HP DL360 G7 server.

Procedure:

1. Log in as an 'ipcs' user on the EMS server and type sudo su to get root privileges.
2. Type dmidecode | grep 'ProLiant DL360 G7'.

For an HP DL360 G7 server, the output will be Product Name: ProLiant DL360 G7. For other servers, no data will be displayed.

Next Steps: If you have Avaya SBCE Release 6.2.1Q18 or 6.3, back up the existing configuration and restore it on a new server. Specific steps for HA configurations involving Amax, HP DL360 G7, and Dell servers are detailed in the document.

Supported Hardware for Moving from HP DL360 G7 and AMAX Servers

Avaya SBCE does not support upgrades to Release 7.0 or later for AMAX and HP DL360 G7 servers. If you use an AMAX or HP DL360 G7 server, back up the existing configuration and deploy it on another server.

Important: If you have Avaya SBCE 6.2.1Q18 or 6.3 on HP DL360 G7 or AMAX servers, back up the existing configuration, restore on a new server, upgrade to Release 7.0, and then Release 7.1.

Snapshots taken on Avaya SBCE can be restored on another device with the same software version. For Amax or HP DL360 G7 servers, choose from the following options:

• AMAX customers: For an EMS-only deployment on an AMAX server, take a snapshot and restore on one of the following servers: Dell R210ii XL with 2 NICs, Dell R320, Dell R620, or VMware (EMS mode only).
• HP DL360 G7: For a standalone SBCE+EMS deployment, take a snapshot and restore on HP DL360 G8.

Specific procedures for HA configurations and moving between server types are detailed.

Changing Serial Number for Avaya SBCE Uninstalled from an Amax Server

About this task: After EMS starts on a new server, uninstall Avaya SBCE instances from the Amax server and add them to the new EMS. Factory resets on Amax servers can generate identical serial numbers for primary and secondary SBCEs, requiring unique serial numbers for registration.

Procedure:

1. Log in to the Avaya SBCE.
2. Type vi /usr/local/ipcs/etc/sysinfo.
3. Change the last character of the serial number for one Avaya SBCE.
4. Change the system STATE parameter to INSTALLED.
5. Restart both Avaya SBCE devices.

Chapter 3: Planning for Upgrade

Prerequisites

Before an upgrade, perform the following:

Upgrade Files

Download the following files from the PLDS website: https://plds.avaya.com/

• For upgrading from Avaya SBCE Release 6.2.x to Release 7.0 using CLI: ipcs_7.0.0.Qxx_<md5sum>.tar.gz (CLI is recommended).
• For upgrading from Avaya SBCE Release 6.2.x to Release 7.0 using DVD: sbce-7.0.0-xx-xxxx.iso.
• For upgrading from Avaya SBCE Release 6.2.x to Release 7.0 using a USB device: sbce-7.0.000-xx-xxxx_<md5sum>.img.
• For upgrading from Release 6.3 to Release 7.0: sbce_7.0.0-xx-xxxx-<md5sum>.tar.gz
• For upgrading from Release 7.0 to Release 7.1: sbce_7.1.0.0-xx-xxxx-<md5sum>.tar.gz

Preparing a USB Device or DVD for Installation or Upgrade

Preparing a USB Device on Windows

Before you begin: Download the image file sbce-7.1.0.0-xx10xxxx_<md5sum>.img from the PLDS website.

About this task: A USB storage device with a minimum capacity of 4 GB can be used for Avaya SBCE installation or upgrade.

Procedure:

1. Download and set up a disk imaging utility like Win32 Disk Imager.
2. Copy the Avaya SBCE 7.1 USB image file to the Windows system.
3. Ensure the checksum matches the calculated checksum.
4. Plug the USB device into the Windows system. If an error indicates the system is in use, format the USB device before using Win32 Disk Imager.
5. In Win32 Disk Imager, specify the image name and the correct USB device, then click Write. Warning: Do not change the filesystem label on the USB drive; the default is SBC_USB.
6. Wait for the image to be written to the USB device.

Preparing a USB Device on Linux

Before you begin: Download the image file sbce-7.1.0.0-xx-xxxx_<md5sum>.img from the PLDS website.

About this task: A USB storage device with a minimum size of 4 GB can be set up for Avaya SBCE installation or upgrade.

Procedure:

1. Copy the Avaya SBCE 7.1 USB image file to the Linux system.
2. Navigate to the location where you copied the image file and type md5sum filename. The system displays an alphanumeric hash followed by the filename.
3. Compare the hash with the checksum value in the filename to ensure integrity.
4. Plug the USB device into the Linux server. The device may be detected as /dev/sda, /dev/sdb, or /dev/sdc. Consult your system administrator if unsure.
5. Run the command: dd if=/path/of/the/SBCE_USB_image_file of=/dev/sdX bs=16M. This command may take up to 10 minutes.

Preparing a DVD

About this task: Use this procedure to prepare a DVD for installing or upgrading Avaya SBCE.

Procedure:

1. Download sbce-7.1.0.0-xx-xxxx.iso from the PLDS website: https://plds.avaya.com/.
2. Insert the DVD into a Windows or Linux system.
3. Burn the ISO image to the DVD.

Chapter 4: Upgrading Avaya SBCE from 6.2 to 7.0

Upgrade from Release 6.2 to Release 7.0

To upgrade to Avaya SBCE Release 7.1, you must first upgrade from Release 6.2 to Release 7.0, and then upgrade to Release 7.1. After purchasing an upgrade license for Release 7.0, you can upgrade from Avaya SBCE Release 6.2 to 7.0 using the Command Line Interface (CLI). The CLI is the only method for upgrading from 6.2 to 7.0, while the CLI or EMS web interface can be used for upgrading from 6.3 to 7.0. A WebLM server is required for upgrading Avaya SBCE Release 6.2 to 7.0.

Before beginning the upgrade:

• Download the license file from PLDS.
• Assign the WebLM server as the license host for the licenses on PLDS.
• Regenerate the license file.
• Ensure Avaya SBCE servers in the deployment have unique hostnames. Change hostnames if necessary before attempting an upgrade. Refer to Troubleshooting and Maintaining Avaya Session Border Controller for more information.
• To continue using encryption for advanced sessions, add a new license for encryption.

Note: For information about the Release 7.0 build, see http://support.avaya.com. You cannot directly roll back from Release 7.0 to Release 6.2; manual installation of Release 6.2 and restoring a prior snapshot is required. Rollback from Release 7.0 to Release 6.3 is possible.

Upgrade Sequence (Multi-server deployment):

1. EMS server with lower node ID
2. EMS server with higher node ID
3. Avaya SBCE pair:
1. Avaya SBCE with lower node ID
2. Avaya SBCE with higher node ID

Node IDs can be found in /usr/local/ipcs/etc/sysinfo. Ensure the EMS or Avaya SBCE with the lower node ID is secondary to avoid losing ongoing calls.

Clearing Ghost Devices in the Database

About this task: Devices not present in the network may exist in the database. To prevent upgrade issues, remove these "ghost" devices before upgrading Avaya SBCE.

Before you begin: Download the fix-orphaned-devices.py script from PLDS using download ID SBCE0000021.

Procedure:

1. Log in as an 'ipcs' user on the EMS server and type sudo su to get root privileges.
2. Type /etc/init.d/ipcs-db start. The system starts the database. The database must be running for the script to execute. If the database is already running, a message will indicate this.
3. Type chmod +x fix-orphaned-devices.py to make the script executable.
4. Type ./fix-orphaned-devices.py.

After the script runs successfully, proceed with the Avaya SBCE upgrade.

Important: If ghost devices are encountered after migrating to Avaya SBCE 7.0, escalate the issue to Tier 4 support.

Upgrading EMS and Avaya SBCE using CLI

Before you begin:

1. Download the Avaya SBCE Release 6.2.1Q18 image file from PLDS and set up a USB flash device with it. This is useful for reinstalling Avaya SBCE Release 6.2.1.
2. From the PLDS website (https://plds.avaya.com/), download the upgrade tar file to your desktop and SFTP it to /home/ipcs on the server. For upgrading from Avaya SBCE 6.2 to Avaya SBCE 7.0, the tar file is named ipcs_7.0.0.Qxx_<md5sum>.tar.gz.

About this task:

Important: During the upgrade process, do not restart applications or run any web interface or CLI commands (like reboot or shutdown). Ensure EMS is reachable from Avaya SBCE.

Procedure:

1. Connect a keyboard and monitor (VGA mode) or a serial cable to the server's serial console port. Important: Do not perform this procedure using an SSH session. If the server is a primary Avaya SBCE server, ensure applications are stopped before starting the upgrade.
2. Log in as an 'ipcs' user and type sudo su to get root privileges.
3. Create a temporary directory: type # mkdir /archive/upgrade_temp. If the directory exists, ensure it is empty by typing # rm -rf /archive/upgrade_temp/*.
4. Move the upgrade tar file (e.g., ipcs-7.0.0*tar.gz) from /home/ipcs to /archive.
5. Verify the image checksum: run the md5sum command on the file and compare the output with the checksum in the filename.
6. Extract the package to the temporary directory:
   • # cd /archive
   • # tar xvzf ipcs_7.0.0.Qnn_<md5sum>.tar.gz -C /archive/upgrade_temp
   Do not extract into the same directory as the tar.gz file.
7. Start the upgrade:
   • cd /archive/upgrade_temp/uber
   • ./ursbce.py --migrate --console=[vga/serial]

Note: For VGA connection, use --console=vga; for serial connection, use --console=serial. The system will display "Start Migrating System." After restarting, the SBC 7.0 migration option is automatically selected. The system backs up data, repartitions, reformats, installs software, and reboots. If prompted, select "Re-initialize all" in the "error processing drive" screen.

Next Steps: In a multi-server deployment, repeat these steps for the secondary and primary Avaya SBCE. Verify the deployment by logging into EMS and checking the Avaya SBCE and EMS versions, or by using the ipcs-version command.

Upgrading EMS and Avaya SBCE using a USB Device or DVD

Before you begin:

• Take a system snapshot and store it on external media. Do not restart applications or run web interface commands during the upgrade.
• Download the .iso or .img file from the PLDS website: https://plds.avaya.com/.
• If using a DVD, burn the *.ISO image and insert it. If using a USB device, save the *.IMG file to it.

About this task: During the upgrade, do not restart applications or run web interface commands. Ensure EMS is reachable from Avaya SBCE.

Procedure:

1. Connect a keyboard and monitor (VGA mode) or a serial cable to the server's serial console port.
2. Boot the system with the DVD or USB device attached.
3. Change BIOS settings to boot from the DVD or USB storage device. Set USB as the first priority and the hard drive as the second. For Dell servers, press F11; for CAD 0208, press Tab or Delete to set boot options.
4. Wait for the message "Found SBC version 6.2.1.Q18 installed on this system."
5. When prompted "Proceed with upgrade? (yes/no)", type Yes. The system will back up data, create new partitions, indicate the connection mode, and prompt for the preferred console. Typing no will initiate a fresh installation.
6. Select the default console type (vga or serial) by typing serial or vga and pressing Enter.
7. If prompted, select "Re-initialize all" in the "error processing drive" screen. This process may take up to 30 minutes.
8. When prompted to reboot, remove the USB device (if used) and press Enter. The system restarts. Eject the DVD if not automatically ejected.
9. After restart, enable WebLM with EMS, EMS+SBCE, or an external device like System Manager.
10. Generate the license file on PLDS and enter the number of purchased sessions. Refer to "Configuring WebLM server IP address on EMS" for details.
11. Log in to the EMS web interface.
12. In the left navigation pane, click System Management.
13. In the Devices tab, locate the upgraded device and click Edit.
14. In the Standard Sessions, Advanced Sessions, and Scopia Video Sessions fields, enter the number of licensed sessions.
15. Click Finish.

Next Steps: In a multi-server deployment, repeat these steps for the secondary and primary Avaya SBCE. Verify the deployment by logging into EMS and checking the Avaya SBCE and EMS versions, or by using the ipcs-version command.

Chapter 5: Upgrading Avaya SBCE from 6.3 and 7.0 to 7.1

Installing GUI Patch for Upgrades from Release 7.0 or Release 6.3.6 to Release 7.1

Before you begin: Download the GUI patch from PLDS:

• For upgrades from Avaya SBCE 7.0 to 7.1, download 7.0-upgrade_regex_patch.tar.
• For upgrades from Avaya SBCE 6.3.6 to 7.1, download 6.3.6-upgrade_regex_patch.tar.

About this task: Avaya SBCE Release 7.0 does not accept upgrade packages with three-digit version numbers. Run the GUI patch before upgrading from Release 7.0 to 7.1, or from Avaya SBCE 6.3.6 to 7.1. This patch is not required if you have already upgraded to Avaya SBCE 7.0.1.

Procedure:

1. Log in to Avaya SBCE as root.
2. Untar the package to /home/ipcs.
3. Type cd upgrade-patch/.
4. Type sh upgrade-regex.sh.

Upgrade from Release 6.3 and Release 7.0

To upgrade from Release 6.3 to Release 7.1, you must first upgrade from Release 6.3 to Release 7.0 if your service pack is earlier than 6.3.6. Follow the same procedure to upgrade from Release 6.3 to 7.0 and from 7.0 to 7.1.

Note: You can directly upgrade Avaya SBCE 6.3.6 to Release 7.1 after applying the GUI patch.

You can upgrade from Release 6.3 to Release 7.0 after purchasing an upgrade license for Release 7.0. Perform all upgrades during a maintenance window. If the system uses 6.2 or an earlier version, follow the upgrade procedures in Chapter 4. For information about the latest Release 7.1 build, see http://support.avaya.com.

Before beginning the upgrade, ensure:

• All debug logs are disabled.
• Avaya SBCE servers in the deployment have unique hostnames. Change hostnames if necessary. Refer to Troubleshooting and Maintaining Avaya Session Border Controller for more information.

Upgrade status can be checked at /archive/log/icu/upgrade.log.

Supported Upgrade Paths from Avaya SBCE 6.3.x

• If you have Avaya SBCE 6.3.5 or earlier, upgrade to Avaya SBCE 6.3.6.
• From Avaya SBCE 6.3.6, you can apply the GUI patch and then upgrade to Avaya SBCE 7.1 without upgrading to Release 7.0 or 7.0.1.
• If you have Avaya SBCE 6.3.3, you can upgrade to Release 7.0, then 7.0.1, and finally 7.1.

Upgrades from Avaya SBCE 6.3.5 and 6.3.6 to Release 7.0 are not supported.

Upgrade Sequence in Multi-Server Deployments

1. EMS server with lower node ID
2. EMS server with higher node ID
3. Avaya SBCE pair:
1. Avaya SBCE with lower node ID
2. Avaya SBCE with higher node ID

Node IDs are in /usr/local/ipcs/etc/sysinfo. Ensure the EMS or Avaya SBCE with the lower node ID is secondary to avoid losing ongoing calls.

Upgrading Primary EMS or Standalone Avaya SBCE

Procedure: Copy the upgrade tar file to the EMS server using one of the following methods:

• Copy the upgrade tar file to the EMS using the web interface.
• Copy the upgrade tar file manually to the EMS server using SFTP or SCP.

Note: The same procedure can be used to upgrade a standalone Avaya SBCE or EMS+Avaya SBCE deployment from Release 6.3 to 7.0 or from 7.0 to 7.1.

Upgrading EMS using a Web Browser

Before you begin: Download the upgrade package to a local or remote PC from Avaya Product Licensing and Delivery System (PLDS).

About this task: Uploading large files via browser can be unreliable. Transfer the file to EMS using SFTP.

Procedure:

1. Log in to the EMS web interface with administrator credentials.
2. In the left navigation pane, click System Management.
3. Click the Updates tab.
4. Click Upgrade from uploaded file.
5. Click the Browse button and navigate to the downloaded upgrade file.
6. Select the upgrade file.
7. Click Upgrade.
8. Click Start Upgrade. The system displays the Upgrade Status screen. Do not reboot during the upgrade. After completion, the system displays "Return to EMS tab."
9. Click Return to EMS to log back in.

Next Steps: Verify the deployment by logging into EMS and checking the Avaya SBCE and EMS versions, or by using the ipcs-version command.

Uploading using SFTP or SCP

Before you begin: Download the tar file from the PLDS website.

Procedure:

1. Log on to the EMS server as an 'ipcs' user using port 222.
2. Upload the upgrade tar file to the EMS server using SFTP or SCP.
3. Copy the file to /home/ipcs.
4. Log in with root privileges and move the file from /home/ipcs to the EMS server folder: /archive/urpackages. Note: If the urpackages folder does not exist, create it.
5. Verify file integrity on the command line by typing md5sum filename and ensuring the result matches the string in the filename.
6. Log on to the EMS web interface.
7. In the left navigation pane, click System Management > Updates.
8. In the Updates tab, under "Upgrade from local file", select the upgrade file.
9. Click Upgrade.
10. Click Start Upgrade. The system displays upgrade progress.
11. Click Return to EMS. The System Management page is displayed.

Next Steps: Verify the deployment by logging into EMS and checking the Avaya SBCE and EMS versions, or by using the ipcs-version command.

Upgrading Secondary EMS

Before you begin: Download the tar file from the PLDS website:

• For upgrading from Release 6.3 to 7.0: sbce-7.0.0-xx-xxxx-<md5sum>.tar.gz.
• For upgrading from Release 7.0 to 7.1: sbce-7.1.0.0-xx-xxxx-<md5sum>.tar.gz.

Procedure:

1. Copy the tar file to the Secondary EMS server using 'ipcs' user on port 222 (SFTP or SCP).
2. Connect to the system using VGA or Serial console.
3. Using root permissions, move the upgrade tar file from the 'ipcs' user home directory to /archive/urpackages.
4. Ensure the md5sum of the upgrade tar file matches the checksum in the filename.
5. Create a temporary directory: type mkdir /archive/temp_upgrade.
6. Remove all content in the temporary directory: type rm -rf /archive/temp_upgrade/*.
7. Extract the upgrade tar file into the temporary directory:
   • For 6.3 to 7.0: tar xvf /archive/sbce-7.0.0-xx-xxxx-<md5sum>.tar.gz -C /archive/temp_upgrade
   • For 7.0 to 7.1: tar xvf /archive/sbce-7.1.0.0-xx-xxxx-<md5sum>.tar.gz -C /archive/temp_upgrade
8. Change directory: cd /archive/temp_upgrade.
9. Make the script executable: chmod +x ursbce.py.
10. Run the upgrade script: ./ursbce.py -U --daemonize. This reboots the system.

Warning: Use the --daemonize option for CLI-based upgrades over SSH. Without it, the upgrade may fail if the user disconnects due to inactivity.

11. Wait for the system to reboot.
12. Verify the system version by typing cat /etc/sbce-version. Upgrade logs are in /archive/log/icu/upgrade.log.

Upgrading HA Pairs

Before you begin: Ensure EMS servers are upgraded before upgrading HA pairs.

About this task: This procedure upgrades Avaya SBCE devices in HA pairs. Repeat for each HA pair.

Procedure:

1. In the Updates tab, click System Management, then click Upgrade. The Upgrade Devices window appears.
2. Select the checkbox next to the Device Name column. The system determines and selects the primary Avaya SBCE.
3. Click Next. The system indicates the device is upgraded.
4. Click Finish. The Upgrade Devices window reappears.
5. Select the checkbox next to the Device Name column for the other Avaya SBCE in the HA pair.
6. Click Next. The system indicates the device is upgraded.
7. Click Finish.

Note: After EMS software upgrade, a message "One or more devices are in an orphan state" may appear. Upgrade these devices or choose to rollback EMS.

HA system pairs and all other Avaya SBCE systems must be upgraded before this message is resolved.

Upgrading Avaya SBCE Servers

Before you begin: Ensure EMS servers are upgraded before upgrading Avaya SBCE servers.

About this task: This procedure upgrades Avaya SBCE servers not in an HA pair. Repeat for each server.

Procedure:

1. In the left navigation pane, click System Management > Upgrade. The Upgrade Devices message box appears.
2. Select the checkbox next to the devices to upgrade. Devices can be upgraded individually or as a group.
3. Click Next. The system indicates the device is upgraded.
4. Click Finish.

Note: After EMS software upgrade, a message "One or more devices are in an orphan state" may appear. Upgrade these devices or choose to rollback EMS.

HA system pairs and all other Avaya SBCE servers must be upgraded before this message is resolved.

Next Steps: Verify the deployment by logging into EMS and checking the Avaya SBCE and EMS versions, or by using the ipcs-version command.

Rolling Back using Web Interface

About this task: Rollback is unavailable for upgrades from Release 6.2 or 6.3. It is available for upgrades from Release 7.0 to 7.1.

Procedure:

1. From the left navigation pane, click System Management.
2. Select the Updates tab. The current EMS version and available upgrade/rollback options are displayed.
3. Click Rollback. The Rollback Status screen appears, followed by the "Return to EMS tab" upon completion.
4. Click the Return to EMS tab to log back into the EMS web interface.

Rolling Back through CLI

Before you begin: Download the Avaya SBCE tar file for the release to which you want to roll back.

About this task: Rollback to the last Avaya SBCE release is possible via CLI. Rolling back from Avaya SBCE 7.1 to 6.3.6 is not supported via the web interface; use CLI for this action.

Procedure:

1. Log on to Avaya SBCE as a super user.
2. Delete existing files from /archive/temp.
3. Untar the package to roll back to in the temp directory.
4. Begin rollback by typing ./ursbce.py --rollback --daemonize. Check rollback logs at /archive/log/icu after completion.

Chapter 6: Licensing Requirements

Avaya SBCE uses WebLM for licensing. Install the Avaya SBCE license file on the Element Management System (EMS) via the System Management page. Ensure the WebLM server license file displays the product code "Session Border Controller E AE". You can view License State, Grace Period State, and Grace Period Expiration Date on the Dashboard page. A 30-day grace period is provided for installing a license on a newly installed or upgraded EMS.

The license file contains:

• Product name
• Supported software version
• Expiration date
• Host ID (primary host ID of WebLM is used)
• Licensed features
• Licensed capacity

Hardware Avaya SBCE devices can use a local WebLM server. For mixed deployments (EMS on VMware, Avaya SBCE on hardware), use a WebLM server installed on VMware or System Manager WebLM.

Avaya SBCE License Features

To use a feature, ensure the uploaded license file has appropriate licenses for it. Features cannot be configured or used if the correct license is missing.

Configuring WebLM Server IP Address on EMS

Before you begin: Install the Avaya SBCE license file on System Manager WebLM, local WebLM, or standalone WebLM server.

Procedure:

1. Log on to the Element Management System web interface with administrator credentials.
2. In the left navigation page, click System Management.
3. On the System Management page, click the Licensing tab.
4. Perform one of the following:
   • For a System Manager WebLM server or standalone server, enter the WebLM Server URL (e.g., https://<SMGR_server_IP>:52233/WebLM/LicenseServer or https://<WEBLM_server_IP>:52233/WebLM/LicenseServer) and click Save.
   • For a local WebLM server, select the "Use local WebLM server" checkbox and click Save.
   If the WebLM server is unreachable, run the command file/usr/local/ipcs/icu/workaround/fixextweblmcert.sh to obtain a license file for EMS.
5. On the Dashboard screen, check the License State field. It should show "OK" if the configuration is successful.
6. Click the Devices tab.
7. Locate the configured Avaya SBCE device and click Edit.
8. In the Standard Sessions, Advanced Sessions, and Scopia Video Sessions fields, enter the number of licensed sessions purchased.
9. Click Finish.

Chapter 7: Resources

Documentation

The following table lists related documents available for download from the Avaya Support website: http://support.avaya.com

Finding Documents on the Avaya Support Website

About this task: Use this procedure to find product documentation on the Avaya Support website.

Procedure:

1. Navigate to the Avaya Support website: http://support.avaya.com/.
2. Enter username and password, then click Login.
3. Hover over "Support by Product".
4. Click "Documents".
5. In the "Enter your Product Here" search box, type the product name and select it from the dropdown.
6. If multiple releases exist, select the appropriate release number.
7. Use the "Content Type" filter or click "Select All" to see available documents.
8. Click Enter.

Training

The following courses are available on the Avaya Learning website: www.avaya-learning.com. Enter the course code or title in the Search field and click Go.

• Course Code: 5U00090E, Course Title: Knowledge Access: Avaya Session Border Controller
• Course Code: 5U00160E, Course Title: Knowledge Collection Access: Avaya Unified Communications Core Support

Viewing Avaya Mentor Videos

Avaya Mentor videos offer technical content on installing, configuring, and troubleshooting Avaya products. They are available on the Avaya Support website (under video document type) and on the Avaya-run channel on YouTube.

• To find videos on the Avaya Support website, go to http://support.avaya.com and search for "Avaya Mentor Videos" or the product name, then select "Video" in the Content Type column.
• To find videos on YouTube, go to www.youtube.com/AvayaMentor and use the search channel or browse playlists.

Note: Videos are not available for all products.

Support

Visit the Avaya Support website (http://support.avaya.com) for the latest documentation, product notices, and knowledge articles. You can also find release notes, downloads, and issue resolutions. Use the online service request system or chat with live agents for support.