Updated for 9.1
This is not intended to be the only document needed for implementation, but merely to spell out the general steps needed to begin deployment.
The first benefit of Virtualized Server Edition, is that there is no hardware or server to purchase. You can have an SCN of any mixture of virtual, server based or IP500 appliances in that SCN.
For EVERY virtual server edition, you will need a “Virtual Server Edition” license (275694-IPO R9 VRTULZD SE ADI LIC) and for every server based and/or IP500 appliance, you will need a “Server Edition” license (275658-IPO R9 SE ADI LIC).
1. So, once you purchase the licenses, the distributor is going to need the SID, or System ID. This can ONLY be done, once the installer, installs the Virtual Machine into the VMWare architecture, and runs through the ignition process.
2. Download or purchase the ova files. You can download the .ova file (4.7G) for use with VMware from the support site here. Or you can order the DVD from your distributor (700507516)
3. The VMWare installer will need to transfer the .ova to the VMWare hardware server. (see Deploying Server Edition Servers as Virtual Machines)
3A. Once software is transferred, we need to set the IP address of the Virtual Machine. See section 2.6.1 in the Deploying Server Edition Servers as Virtual Machines manual. Once IP address is set, the Avaya partner can run the ignition process just as if this was a DL360 or DL120.
4. Browse to the IP of the Virtual IPO (EX: In the ignition process, the following information will be set that will dictate the SID of the Virtual Machine (among other settings critical to the installation)
- IP Address (LAN1 AND LAN2)
- Time Zone
If any of these pieces of information change, your SID will change. In reference to item 2, this is particularly important. The hostname of the IPO needs to match that of your FQDN, in the event you are going to set up One-X Portal for IP Office as well as Preferred Mobility. If you anticipate this set up, it is easiest to have the FQDN now, so you wont change the SID down the road.
If the SID does change because the items above were modified after implementation, there is a 30 day grace period, before the license will go invalid.
**NOTE** Since the only error that is produced from a licensing failure, is inside System Status, it is recommended that you set up email alerts and select to receive them, in event of a license failure. (System>Events>Alarms)
5. Now you can browse to the web manager and click Platform>Settings>System and at the bottom will be the SID. Also, you can open a config with Manager or Manager Lite and get the SID from there. Send that SID to the distributor so they can process your licenses.
IPOSS Notes – Here is a document to discuss the software support for a Virtualized Server Edition. IPOSS Additional Coverage Scenarios: https://avaya.my.salesforce.com/sfc/servlet.shepherd/document/download/069a00000021XXcAAM?doc_type=Offer Definition (you will need to log into the sales portal BEFORE clicking this link)
IPOSS coverage will be the base offer, Software support with upgrades. Parts coverage will not be provided (will be covered by VM Ware if there is a VMWare service agreement).
For ordering purposes, order the DL120, software only support.
Example: IPO RTS 24X7 – DL120G7 – Material Code-271607
Some of the links above may not work, UNLESS you are already logged into the sales portal.
Below is a quick table on required resources for a Virtual deployment.
(Click the picture to enlarge)
Also, the default OVA settings are:
Hard Disk: 100GB
Network Ports: Dual Gigabit
After deployment of a virtual machine, you can optimize the resources allocated to meet the actual requirements of the virtual machine. For example, if the virtual machine will only support 50 users, you can reduce the allocated processor and RAM memory. This allows for the best use of the overall resources provided by the virtual server platform.