- Microsoft Windows Server 2008 R2 (64-bit standard and enterprise editions) SP1 and Red Hat Enterprise Linux (RHEL) v5.6 and v5.7 (both 64 bit) are supported.
- Virtual Machine Host: ESXi 5.0 and up to v5.5 is required. Support for ESXi 4. x is discontinued.
- Physical Memory--> COM: 8GB, COM+VPS: 10GB
- CPU--> Quad Core 2GHz
- Disk Space--> COM: 80GB, COM+VPS: 100GB
NOTE: The server requirements apply to a new installation of COM Release 3.1 and to an upgrade to COM 3.1.
- If installing on pre-existing COM Server, ensure to delete old COM files and folders from the drive and remove Registry entries with keyword 'Avaya'.
- Ensure that a valid COM license is present. If not note down the MAC address in case of a physical server and IP address and Notice field information in case of a VM to generate a new license.
- Ensure that the server has a COM software downloaded. It is available on the Installation CD or it can be downloaded from the Extreme Networks Support Portal.
- If using Windows Platform, the user has to be logged in as a local administrator and not as a user with administrator privileges.
- Extreme Networks recommends disabling any firewalls running on the server.
- Ensure that no anti-virus application is installed on the server.
- The COM installer is available in English only. The installation or upgrade works only when the language on the system is configured to English(US). Also, ensure the system locale is set to "US".
- Always include the FQDN details rather than the IP Address in the COM URL to launch the application.
INSTALLING COM ON A WINDOWS SERVER:
- Start the COM installer. The COM installer prepares for installation and displays the License Agreement dialog box.
- Review the terms of the license agreement and if agree, select 'I accept the terms of the License Agreement'
- Click next, the Installation Folder page displays.
- Click Choose to specify a location, or use the default location provided. Ensure there are no spaces in the path name.
- Review the port information for the Web Server Configuration, and then click Next. The Security Server Mode page displays.
- Select COM to be installed as Primary Security Server. Note: Client Security Server is not supported in COM Release 3.1.
- Click next, the Configuration and Orchestration Manager window displays.
- Click Choose to browse to the location of the license file.
- Click next, the Executing Pre-Install Checks window displays.
- 1If there are no errors in the pre-install report, click Install.
- If there are errors in the pre-install report, an error dialog box will be displayed and installation will be paused.
NOTE: With respect to the pre-check phase of COM installation, Critical or Error indicates a failure to meet the minimum requirements to install COM. The warning indicates the minimum requirements to successfully install COM. Success indicates requirements that Avaya recommends for a successful COM installation.
- In the Error dialog box, click OK.
- In the Executing Pre-Install checks window, click Rerun Checks to run the script again, or click Open Log to view the log file.
- Review the information and click Install.
- The Installing Configuration and Orchestration Manager dialog box displays.
- After the installation completes, click Done.
- Wait for about Fifteen minutes.
- Enter FQDN in the address bar of Windows internet explorer.
- Login with default username(admin) and password(admin123).
The installation process on Linux is also quite similar. Refer to this guide
for detailed instructions.
- If running COM on versions 2.3 or 2.3.1 first upgrade to COM 3.0 or 3.0.2 as primary.
- If running COM version older than COM 2.3 or 2.3.1, uninstall the application and then install COM 3.1.
- The Linux bin file needs to have full permissions before installing. Use the command: chmod 777 before executing the Linux installer. Sample below:
chmod 777 <filename>.bin
- For Data Migration from COM 3.0.x to 3.1.3 or any further install instructions, download the release notes of COM 184.108.40.206 using this link.
- For OVA based deployment refer to this document.