4.3.6 ESXi and VM Data (OSEE V10)

•
Enable Root Access support (*) - Enables/Disables WebCDC support for Root Access installation scenarios.
NOTE:  All fields below become visible and thus editable by the user only if Enable Root Access support is set to 'yes'.
NOTE:  In case field "Hypervisor Configuration" in tab 'General' is set to "Software only", Root Access support becomes non-editable by the user (greyed-out) and is set to 'no' which consequently means that fields below are not visible in the UI as well.
•
ESXi Host 1 - Data of ESXi Host 1.
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Usernames set must be of a user account with root privileges!
•
ESXi Host 2 - Data of ESXi Host 2.
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Usernames set must be of a user account with root privileges!
NOTE:  The above field is only visible when field "Hypervisor Configuration" in tab 'General' is set to either "2 ESXis" or "3 ESXis".
•
ESXi Host 3 - Data of ESXi Host 3.
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Usernames set must be of a user account with root privileges!
NOTE:  The above field is only visible when field "Hypervisor Configuration" in tab 'General' is set to "3 ESXis".
•
Integrated OSV - Data of the Integrated OSV VM.
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
NOTE:  The above field is only visible for Integrated Simplex OSV scenarios (field "OpenScape Voice Type" set to "Integrated Simplex" in tab 'General').
•
OSV Node 1 - Data of the OSV Node 1 VM.
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
NOTE:  The above field is only visible for Standard Duplex OSV scenarios (field "OpenScape Voice Type" set to "Standard Duplex" in tab 'General').
•
OSV Node 2 - Data of the OSV Node 2 VM.
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
NOTE:  The above field is only visible for Standard Duplex OSV scenarios (field "OpenScape Voice Type" set to "Standard Duplex" in tab 'General').
•
UC - Data of the UC VM (UC / CMP / Composer / IM Server(s)).
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
NOTE:  The above field is only visible for Standard Duplex OSV scenarios (field "OpenScape Voice Type" set to "Standard Duplex" in tab 'General').
•
Composer - Data of the Composer VM (Composer Server (standalone)).
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
NOTE:  The above field is only visible for Integrated Simplex OSV scenarios (field "OpenScape Voice Type" set to "Integrated Simplex" in tab 'General').
•
Windows 1 - Data of the Windows 1 VM (License / (OSCC) / XPR / Concierge Server(s)).
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
•
Windows 2 - Data of the Windows 2 VM (Trace Manager / DLS Server(s) for Standard Duplex or Trace Manager Server for Integrated Simplex OSV scenarios).
All data are optional; if one or more field(s) is/are not set under section "ESXi and VM Data", manual intervention for generated file "esxi_mapping.json" will be required during the installation process for it/them to be set by the user.
IMPORTANT:  Names between VMs must be unique!
OpenScape Solution Set V10, Customer Data Collection with WebCDC V1, Planning Guide, Issue 2, ID: A31003-S11A0-P100-2-76A9
 © 07/2024 Mitel Networks Corporation. -  All rights reserved.
 Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.