vmware evo: rail - viktorious.nlreserve 4 ip addresses for vmware vsphere® vmotion® for each evo:...

VMware EVO: RAILU S E R G U I D E

VMware EVO: RAIL

U S E R G U I D E / 2

Table of Contents

EVO: RAIL Setup Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

EVO: RAIL Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Top-of-Rack Switch and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Out-of-Band Management (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Workstation/Laptop (for configuration and management) . . . . . . . . . . . . . . . . . . . . . . . .5

Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

IP Addresses and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Logging and Log Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Automatic Scale-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Fault Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Networking Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Deployment, Configuration, Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

EVO: RAIL Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

EVO: RAIL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Just Go! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Customize Me! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Upload Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Configuration Walk-Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

EVO: RAIL Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Adding Appliances to an EVO: RAIL Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Creating Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Security Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Monitoring Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Monitoring Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Logging, Licensing, Updating, and Language Choice . . . . . . . . . . . . . . . . . . . . . . 17

Appendix A: Network Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Template for your network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

EVO: RAIL default configuration table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

JSON configuration file format and valid values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Appendix B: Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Appendix C: Physical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Customer Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Modifying BMC Interface IP Address in the BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


VMware EVO: RAIL

EVO: RAIL Setup Checklist

CATEGORY DETAILS

Hardware See Hardware, page 4

EVO: RAIL appliance One to four EVO: RAIL appliances

Top-of-rack (TOR) switch IPv6 enabled on all ports

8 ports for RJ-45 or SFP+ for each EVO: RAIL appliance

1 port for a workstation/laptop for access to EVO: RAIL

IPv4 and IPv6 multicast must be enabled on the VMware Virtual SAN™ and management network segments

Out-of-band management switching (optional)

a separate 1GbE switch or enough extra capacity (4 extra ports per EVO: RAIL appliance) on the TOR switch

Username: UserId Password: Passw0rd!

Workstation/Laptop Access to a browser for EVO: RAIL configuration and management

Physical See Appendix C: Physical Requirements for details

Power

Dimensions

Environmental

2 power cords for redundancy; power specs may vary by vendor (see the appendix)

2U rack space in a 19x30-inch cabinet, installed with a rail kit

Operating conditions and customer configuration options are listed

Networking See Networking, page 6

IP Addresses and VLANs: Fill in the Network Configuration Table in Appendix A, page 19

Reserve 1 IP address for EVO: RAIL/vCenter Server™

Reserve 4 IP addresses for ESXi™ hosts for each EVO: RAIL appliance (must be contiguous)

Reserve 4 IP addresses for Virtual SAN for each EVO: RAIL appliance (must be contiguous)

Reserve 4 IP addresses for VMware vSphere® vMotion® for each EVO: RAIL appliance (must be contiguous)

Optional: Reserve at least 4 VLANs for vSphere vMotion, Virtual SAN, a VM Network, and the management VLAN for ESXi and EVO: RAIL

Optional: Reserve 1 additional VLAN for out-of-band management plus 4 IP addresses for BMC on each EVO: RAIL appliance

DNS Server(s)

NTP Server(s)

Proxy Server

Recommended (EVO: RAIL will provide DNS service when it is not otherwise available)

Recommended

Optional

Logging VMware vCenter™ Log Insight™ or an external third-party syslog server

Active Directory Optional

Deployment, Configuration, Management

See Deployment, Configuration, Management, page 8

EVO: RAIL Deployment Rack and cable

EVO: RAIL Configuration Customize Me! or Just Go! or Upload Configuration File

EVO: RAIL Management Capabilities: create VMs, monitor system, collect logs, choose language, view tasks, upgrade software, add new EVO: RAIL appliances

Table 1. EVO: RAIL pre-installation checklist


VMware EVO: RAIL

EVO: RAIL Appliance VMware® EVO: RAIL™ is the first hyper-converged infrastructure appliance powered 100% by VMware’s compute, networking, storage, and management software. EVO: RAIL Deployment, Configuration, and Management streamlines initial setup and ongoing operations including updates with zero downtime and automatic scale-out. EVO: RAIL is fully deployed in minutes, once racked, cabled and powered on.

To ensure the correct functioning of EVO: RAIL and an optimal end-to-end user experience, understanding the recommendations and requirements in this User Guide is essential.

Availability of resources and workload is critical for any environment, but even more so in a hyper-converged environment as compute, networking, storage, and management are provided on the same platform.

Hardware EVO: RAIL consists of four nodes. Figure 1 shows an example of the physical appliance and simple network setup. The exact appliance configuration will vary depending on the EVO: RAIL qualified partner that is selected.

EVO: RAIL ships with either eight RJ-45 or SFP+ NIC ports. Eight corresponding ports are required for each EVO: RAIL appliance on the top-of-rack (TOR) switch(es). One port, either on the TOR switch or on a management VLAN that can reach the TOR network, is required for a workstation/laptop with a web browser for EVO: RAIL configuration and management. Any other 1GbE ports on the appliance will be covered and disabled.

Please review Appendix C to understand the physical power and cooling facilities provided for the expected resiliency level of the appliance.

Figure 1 . Rear view of one deployment of EVO: RAIL to a top-of-rack switch (varies by appliance vendor)


VMware EVO: RAIL

Top-of-Rack Switch and VLANsA 10GbE TOR switch that supports IPv4 and IPv6 multicast is required. The network can be configured flat or with VLANs.

• IPv4 and IPv6 multicast must be enabled on all ports on the TOR switch. When using multiple TOR switches, ISL multicast traffic for IPv4 and IPv6 must be able to communicate between the switches.

• Configure a management VLAN on your TOR switch(es) and set it to allow multicast traffic to pass through.

• To allow multicast traffic to pass through, you have 2 options for either all EVO: RAIL ports on your TOR switch or for the Virtual SAN and management VLANs (if you have VLANs configured):

1) Enable IGMP Snooping on your TOR switch(es) AND enable IGMP Querier. By default, most switches enable IGMP Snooping, but disable IGMP Querier.

2) Disable IGMP Snooping on your TOR switch(es). This option may lead to additional multicast traffic on your network.

NOTE: IGMP Snooping software examines IGMP protocol messages within a VLAN to discover which interfaces are connected to hosts or other devices interested in receiving this traffic. Using the interface information, IGMP Snooping can reduce bandwidth consumption in a multi-access LAN environment to avoid flooding an entire VLAN. IGMP Snooping tracks ports that are attached to multicast-capable routers to help manage IGMP membership report forwarding. It also responds to topology change notifications. For IPv6, MLD (Multicast Listener Discovery) is essentially the same as IGMP (Internet Group Management Protocol) in IPv4.

Out-of-Band Management (optional)Remote/lights out management is available on each node through a 1GbE IPMI port that can connect to a management network. Additional network ports are needed for out-of-band management.

• There is one BMC 1GbE port on each node for out-of-band management.

• If you want to use out-of-band management, connect this port either to a separate 1GbE switch or use four additional ports on your TOR switch. Username: UserId Password: Passw0rd!

When EVO: RAIL is shipped, the BMC ports are preconfigured for DHCP as follows (the [APPLIANCE_ID] can be found on a pull out tag located in front of the physical appliance):

BMC interface node 1: configured via DHCP, hostname = [APPLIANCE_ID]-01




The BMC interface IP addresses and login/password can be modified, according to directions by the hardware vendor. Instructions for BIOS changes on Intel-based appliances are found in Appendix C.

Workstation/Laptop (for configuration and management)A configuration and management workstation/laptop with a web browser is required. It must be either plugged into the TOR switch or able to logically reach the TOR switch.

A browser is used with EVO: RAIL to deploy, configure, and manage the network resources. The latest versions of Firefox, Chrome, and Internet Explorer 10+ are all supported. However, for Internet Explorer, after you browse to the appliance IP address, you must go to IE settings.

1) Select Compatibility View settings and uncheck both boxes for the web addresses corresponding to EVO: RAIL / vCenter Server; for example, 192.168.10.200.

2) Select Internet options, select the Security tab, select Local intranet, and click the Sites button. Make sure all boxes are unchecked and click OK. Then click OK to exit Internet options.


VMware EVO: RAIL

NetworkingIP Addresses and VLANsWhen EVO: RAIL ships, it is preconfigured for your network, based on the Network Configuration Table you filled out at the time of order. Before powering on EVO: RAIL, validate that these IP addresses do not collide with any IP addresses used in your local network.

EVO: RAIL / vCenter ServerIP address is required

Netmask and gateway are automatically set to the same as the ESXi hosts

ESXi hostsContinuous IP range is required, with a minimum of 4 IPs

Netmask and gateway are required

vSphere vMotionContinuous IP range is required, with a minimum of 4 IPs

Isolated VLAN preferred (network is not routable)

Virtual SANContinuous IP range is required, with a minimum of 4 IPs

Isolated VLAN preferred (network is not routable)

Virtual Machine Network Dedicated VLAN(s) preferred

Table 2. IP address and VLAN requirements

Network ServicesNTP and DNS server(s): An external DNS server and an NTP server are not required, but they are recommended. Although EVO: RAIL can provide DNS functionality, an external DNS avoids the dependency between DNS availability and other services running on EVO: RAIL. If you do not provide a NTP server, EVO: RAIL uses the time that is set on ESXi host #1 (regardless whether this time is correct).

Active Directory: (Optional) To use Active Directory, enter the AD username, AD password, and AD domain. In EVO: RAIL Version 1.0, this does not fully configure Active Directory. You must perform additional steps1 on the vSphere Web Client.

Logging and Log BundlesLogging combines information for auditing and to track the functionality of EVO: RAIL, vCenter, and ESXi. By default, logging is set to vCenter Log Insight. You may alternately select an existing third-party syslog server. To use vCenter Log Insight, point your browser to the configured IP address; the username is admin. If you ssh to Log Insight, the username is root. The password in either case is the one you specified for vCenter Server.

Log Bundles combine diagnostic information for vCenter Server, ESXi, and EVO: RAIL. They are generated from the EVO: RAIL Management Config screen. A log bundle can be uploaded to technical support as part of a support request.

Automatic Scale-OutEVO: RAIL provides automated scale-out functionality by detecting new EVO: RAIL appliances on the network. When a new EVO: RAIL appliance is powered on, the customer can either add it to an existing EVO: RAIL cluster or create a new EVO: RAIL cluster. Configuration is handled with minimal user input. See Adding Appliances to an EVO: RAIL Cluster on page 13.

1 http://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.install.doc/GUID-B23B1360-8838-4FF2-B074-71643C4CB040.html


VMware EVO: RAIL

Fault ToleranceEVO: RAIL conforms to standard Virtual SAN policy, one failure. Tolerance of more than one failure is not supported in EVO: RAIL Version 1.0. On EVO: RAIL, an entire node can fail and the system will continue to function. One SSD can fail or one to three HDDs on the same node can fail. Disk failures cannot affect more than one node, and the node will still function with one or two HDD failures. One network port on any node can fail without affecting the node.

EVO: RAIL Version 1.0 does not support ether-channels (LACP / IP Hash). Network fail-over is achieved through the virtual switch configuration in ESXi, which is automatically configured by EVO: RAIL during initial setup.

Networking Best Practices• All network traffic (except for out-of-band management) is on the 10GbE NICs. Each node in an EVO: RAIL

appliance has two 10GbE network ports. Each port must be connected to a 10GbE switch that supports IPv4 and IPv6 multicast.

• EVO: RAIL supports four types of traffic: Management, vSphere vMotion, Virtual SAN, and Virtual Machine. Traffic isolation on separate VLANs is recommended. EVO: RAIL Version 1.0 traffic is separated as follows:

NETWORK VMNIC0 VMNIC1

vSphere vMotion Active Standby

Virtual SAN Standby Active

Virtual Machines Active Standby

EVO: RAIL management Active Standby

vCenter Server/ESXi management Active Standby

Table 3. Interfaces for traffic

• To ensure vSphere vMotion traffic does not consume all available bandwidth on the 10GbE port, EVO: RAIL limits vMotion traffic to 4Gbps.

• If you plan to scale out to four EVO: RAIL appliances in a cluster over time, allocate all 16 IP addresses for the ESXi, vMotion, and Virtual SAN IP pools when you configure the first appliance. This will make configuring subsequent appliances even easier. See Appendix B for sample EVO: RAIL configurations.

• It is recommended to use a redundant switching solution for high-availability. When using multiple TOR switches, multicast traffic for IPv4 and IPv6 must be forwarded between the switches.

• It is not required for your complete network to support IPv6. This requirement only applies to switches connected to EVO: RAIL.

• Various network topologies for TOR switch(es) and VLANs are possible with EVO: RAIL. The following sample scenarios are provided in order of complexity, starting with the simplest:

1. One TOR switch on a flat network (no VLANs)2. One TOR switch and multiple VLANs3. Two TOR switches on a flat network (no VLANs)4. Multiple TOR switches and multiple VLANs5. Complex production environment with core switches in addition to multiple TOR switches and VLANs


VMware EVO: RAIL

Deployment, Configuration, ManagementEVO: RAIL DeploymentEVO: R5L deployment is simple, with just four steps:

Step 1. Decide on EVO: RAIL network configuration using information in this user guide.

• Configure the top-of-rack (TOR) switch with instructions from your network administrator. The TOR switch must enable IPv4 and IPv6 multicast.

• Configure a management VLAN on your TOR switch(es) and set it to allow multicast traffic to pass through.• To allow multicast traffic to pass through, you have 2 options for either your entire TOR switch or for

the Virtual SAN and management VLANs (if you have VLANs configured):1. Enable IGMP Snooping on your TOR switch(es) AND enable IGMP Querier. By default, most switches

enable IGMP Snooping, but disable IGMP Querier. 2. Disable IGMP Snooping on your TOR switch(es). This option may lead to additional multicast traffic

on your network.

Step 2. Rack and cable: connect the 10GbE adapters on EVO: RAIL to the TOR switch.

Step 3. Power on EVO: RAIL.

Step 4. Connect a client workstation/laptop to the TOR switch and configure the network address to talk to EVO: RAIL/vCenter Server. For example: IP address: 192.168.10.210; netmask: 255.255.255.0; gateway: 192.168.10.254

Then browse to the EVO: RAIL IP address; for example https://192.168.10.200:7443. If you encounter a browser message about certificates, click Proceed anyway. The latest versions of Firefox, Chrome, and Internet Explorer 10+ are all supported. However, for Internet Explorer, after you browse to the appliance IP address, you must go to IE settings:

• Select Compatibility View settings and uncheck both boxes for the web addresses corresponding to EVO: RAIL / vCenter Server; for example, 192.168.10.2002.

• Select Internet options, select the Security tab, select Local intranet, and click the Sites button. Make sure all boxes are unchecked and click OK. Then click OK to exit Internet options.

EVO: RAIL ConfigurationEVO: RAIL Configuration has the following parameters:

• Hostnames for vCenter Server and ESXi host naming scheme• Networking (IP ranges and/or VLAN ID): ESXi, Virtual SAN, vSphere vMotion, vCenter Server, VM Networks• Passwords: ESXi hosts and vCenter Server; optional Active Directory authentication• Globals: Time zone; your existing NTP, DNS, and Proxy servers; logging: vCenter Log Insight or third-party

syslog server

2 If you change the IP address of vCenter Server during configuration, you will need to repeat this step for the new address.

Figure 2 . Initial user interface


VMware EVO: RAIL

Custom networking is easy with EVO: RAIL. You simply specify the IP and/or VLAN details for each network type: ESXi hosts, Virtual SAN, vSphere vMotion, vCenter Server, and VM Networks.

NOTE: It is recommended that you allocate enough IP addresses for all the EVO: RAIL appliances you plan to add over time. In EVO: RAIL Version 1.0, allocate 16 addresses in each IP pool to make subsequent appliance configuration even easier!

EVO: RAIL Configuration has three options:

• Just Go! • Customize Me! • Upload Configuration File

Just Go! With Just Go!, EVO: RAIL automatically configures the IP addresses and hostnames that you specified when you ordered EVO: RAIL. Configure your TOR switch and click the Just Go! button. All you have to create are two passwords.

Customize Me! When you customize EVO: RAIL, all required configuration parameters are supplied for you by default, except for ESXi and vCenter Server passwords. Customize Me! allows you to easily change the defaults.

Upload Configuration FileWith Upload Configuration File, an existing json configuration file can be selected and uploaded. The Upload Configuration File button is shown in the lower right corner of Figure 4. See Appendix A for format and valid values.

EVO: RAIL verifies the configuration data, and then builds the appliance. EVO: RAIL implements data services, creates the new ESXi hosts, and configures the vCenter Server. The final screen contains the link to EVO: RAIL Management.

Configuration Walk-ThroughStep 1. Click the Yes, Let’s Go! button. Then if you agree, accept the EVO: RAIL End-User License Agreement (EULA).

Step 2. Typically you will click Just Go! to configure EVO: RAIL according to the order you placed and then skip to Step 11. If you click the Customize Me! button you can configure hostnames, IP addresses, VLAN IDs, and passwords. Most fields have default values to make configuration quick and easy.

Note: There is no Save option in EVO: RAIL configuration. All configuration changes are automatically validated and saved when changing between fields or screens.

Figure 3 . Let’s get started

U S E R G U I D E / 1 0

VMware EVO: RAIL

Step 3. To customize EVO: RAIL, first click Hostnames to define a naming scheme for your ESXi hosts. The hostname consists of an ESXi hostname prefix, a Separator, an Iterator, and a Top-level domain. The Preview field shows an example of the result of the first ESXi host, as illustrated in the screenshot.

• Enter the ESXi hostname prefix.

• Select the Separator (“None” or a dash ”-“) and the Iterator (Alpha, Num X, or Num 0X).

• Enter the Top-level domain name.

• Enter the vCenter Server hostname. The top-level domain is automatically applied to the vCenter Server hostname.

Step 4. Click Networking to specify IP and/or VLAN details for each network type: ESXi hosts, Virtual SAN, vSphere vMotion, vCenter Server, and VM Networks.

• In ESXi hosts, enter the Starting and Ending address for IP pool, Netmask, and Default gateway. The VLAN ID can only be configured at the factory.

• Click vMotion and enter the Starting and Ending address for IP pool, the vSphere vMotion VLAN ID, and the Netmask.

• Click Virtual SAN and enter the Starting and Ending address for IP pool, the Virtual SAN VLAN ID, and the Netmask.

Step 5. Optional: Click vCenter Server to change the IP address for EVO: RAIL Management and vCenter Server. Enter the new IP address. The Netmask and Default gateway are automatically copied from the ESXi hosts form.

• If you change the vCenter Server IP address, EVO: RAIL will automatically reconfigure and tell you its new IP address, as described in Step 10.

• If you change the IP address of vCenter Server, you have to change the IP address of vCenter Log Insight (in Step 8, Globals) to be on the same subnet.

• Port numbers remain the same. EVO: RAIL – 7443 and vSphere Web Client – 9443.

• If you are using Internet Explorer as your browser, you will need to select Compatibility View settings and uncheck both boxes for the new web address.

Figure 4 . Configure hostnames

U S E R G U I D E / 1 1

VMware EVO: RAIL

Step 6. Click VM networks to configure virtual machine networks. Enter a VM Network Name and VM Network VLAN ID. Click the Add a VM network button to add more networks.

Step 7. Click Passwords to specify the passwords for the ESXi hosts and vCenter Server. Enter and confirm the ESXi hosts root password and the vCenter Server admin password.

These passwords must contain between 8 and 20 characters, with at least one uppercase, one lower case, and one special character. It cannot have any character repeated 3 times in a row.

Optional: To use Active Directory for authentication, enter the AD username, AD password, and AD domain. In EVO: RAIL Version 1.0, this does not fully configure Active Directory. You must perform additional steps3 on the vSphere Web Client.

Figure 5 . Configure networking

Figure 6 . Configure administrative passwords and Active Directory (optional)

3 http://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.install.doc/GUID-B23B1360-8838-4FF2-B074-71643C4CB040.html

U S E R G U I D E / 1 2

VMware EVO: RAIL

Step 8. Click Globals to specify the Time zone, logging, and any existing DNS, NTP, or Proxy servers on your network. If you have multiple servers, please separate them with commas. EVO: RAIL will configure each of these services, as needed. For example, all ESXi hosts and the vCenter Server are configured with the specified NTP server when this field is filled out.

If you do not supply a DNS server, EVO: RAIL provides this service from the vCenter Server. If you do not provide a NTP server, EVO: RAIL uses the time that is set on ESXi host #1 (regardless whether this time is correct).

Logging combines information for auditing and to track the functionality of EVO: RAIL, vCenter, and ESXi. By default, logging is set to vCenter Log Insight. You may alternately select an existing third-party syslog server. To use vCenter Log Insight, point your browser to the configured IP address; the username is admin. If you ssh to Log Insight, the username is root. The password in either case is the one you specified for vCenter Server.

NOTE: The default IP address for vCenter Log Insight is pre-configured; for example, 192.168.10.201. If you change the IP address of vCenter Server in Step 5, you have to change the IP address of vCenter Log Insight to be on the same subnet.

Step 9. Click the Validate button. EVO: RAIL verifies the configuration data, checking for conflicts. After validation is successful, click the Build Appliance button.

Step 10. This step is only necessary if you change the IP address of vCenter Server!

If you set a new IP address for vCenter Server / EVO: RAIL in Step 5, you will see the following screen. Before you proceed, you must manually change the IP address of your client workstation/laptop to a new address on the same subnet as the new management IP address. (For example, if the new management IP address is 10.10.10.200, you could set your client laptop to 10.10.10.210) Then return to the browser window and click the Take me to it! button. If you encounter a browser message about certificates, click Proceed anyway.

If you click the button before you reconfigure your client laptop, your browser will not be able to find EVO: RAIL. If you close your browser and later want to go to EVO: RAIL, point to the IP address you wrote down with port 7443. (for example, https://10.10.10.200:7443)

Figure 7 . Configure globals

U S E R G U I D E / 1 3

VMware EVO: RAIL

Step 11. Finishing up: Building your appliance!

EVO: RAIL implements data services, creates the new ESXi hosts, and configures the vCenter Server. (Progress is displayed.) When you see the Hooray! Screen, click the IP address to continue to EVO: RAIL Management.

EVO: RAIL ManagementEVO: RAIL Management consists of the VMS and Create VM in the left sidebar to view and manage virtual machines. Users visualize the current status and tasks in the EVO: RAIL system with Health and Tasks in the left sidebar. Config controls logging, licensing, updates, and language choice. Click on the icons in the left sidebar to reach these features.

EVO: RAIL Management handles automatic scale-out with Add EVO: RAIL Appliance whenever a new appliance is detected.

Adding Appliances to an EVO: RAIL ClusterEVO: RAIL Management revolutionizes scale-out. Increasing compute, network, and storage resources is as easy as powering up a new appliance to join an existing EVO: RAIL cluster.

Whenever EVO: RAIL detects a new appliance the following message and button are displayed in a management screen. Click Add EVO: RAIL Appliance.

EVO: RAIL automatically distributes the configuration to seamlessly add new appliances with zero additional configuration. All you do is supply the passwords you created in EVO: RAIL Configuration; the other fields are greyed-out if you’ve configured enough IP addresses as shown in the following figure.

NOTE: In EVO: RAIL Version 1.0, only one appliance can be added at a time. To add multiple appliances, power on one at a time, making sure that each is properly configured before powering on the next appliance.

Figure 8 . New IP address for management, if you change the IP address of vCenter Server

Figure 9 . Finished configuration

Figure 10 . A new appliance is detected

U S E R G U I D E / 1 4

VMware EVO: RAIL

Creating Virtual MachinesBefore you can see any VMs, please click Create VM to add one or more VMs to EVO: RAIL.

EVO: RAIL streamlines virtual machine creation. Users create virtual machines with only a few clicks to select the guest operating system, VM size, network segment, and security options EVO: RAIL simplifies virtual machine sizing by offering single-click small, medium, and large configurations optimized for each guest OS, as well as a single-click security policy.

Figure 11 . EVO: RAIL Add Appliance screen during scale-out

Figure 12 . Streamlined VM creation options (small, medium, large) and connecting to a network segment

U S E R G U I D E / 1 5

VMware EVO: RAIL

Security PoliciesWithout EVO: RAIL, users must manually go through a long list of options to secure a Virtual Machine. EVO: RAIL streamlines this process with three pre-defined Risk Profiles to choose from at the time of VM provisioning.

These profiles are a collection of Virtual Machine Advanced Settings, based on a particular Risk Profile from the vSphere 5.5 Security Hardening Guide, http://vmware.com/security/hardening-guides.

By selecting a more secure policy, you will lose some VM functionality, such as automated tools, inability to shrink VM disks, persistent mode only, no logging and performance information, blocked device interactions, and limited remote console connections. See the hardening guides for more details.

• Risk Profile 3 specifies guidelines that should be implemented in all environments. These are VMware best practices for all data centers. When creating a VM in EVO: RAIL, select the Default Policy.

• Risk Profile 2 specifies guidelines for more sensitive environments or small/medium/large enterprises that are subject to strict compliance rules. When creating a VM in EVO: RAIL, select the Basic Policy.

• Risk Profile 1 specifies guidelines for the highest security environments, such as top-secret government or military installations, or anyone with extremely sensitive data or in a highly regulated environment. When creating a VM in EVO: RAIL, select the Secure Policy.

• When creating a VM in EVO: RAIL, selecting No Policy means that no security configuration options are applied to the VM.

Monitoring Virtual MachinesEVO: RAIL Management allows users to view all virtual machines in a grid. Use the Filter By and Sort By menus in the upper right corner to arrange the VMs. Use the Search box to find VMs by name.

In the upper right corner is the vSphere Web Client logo. Click it to bring up the vSphere Web Client in a separate browser window. Login with the username, root, and the password you configured for vCenter Server.

Figure 13 . Selecting security options

U S E R G U I D E / 1 6

VMware EVO: RAIL

The figure below shows a list of VMs. The icons at the bottom of each VM allow you to open the VM console, clone the VM, and power on or off the VM. When a VM is powered on, click the open console icon, go to the console, and install the guest OS you uploaded when you created the VM.

Click on one of the VMs (Production VM1 in the figure) to access a full set of VM options:

• install VMware Tools

• rename VM

• eject ISO

• open console

• clone VM

• suspend VM

• delete VM

• power on/off

NOTE: To install VMware Tools, your guest OS must already be installed on your VM, and the guest OS ISO disk must be unmounted/ejected from the virtual CD drive.

Monitoring HealthEVO: RAIL Management simplifies live compute management with health monitors for CPU, memory, storage, and VM usage for entire EVO: RAIL clusters, individual appliances, and individual nodes.

• Cluster information: Click on Overall System.

• Appliance information: Click on an appliance - either in the menubar in the top of the window or in the list of EVO: RAIL Appliances below the Live Usage Statistics.

• Node information: To view information about a specific node, click the appliance first and then the node.

Figure 14 . EVO: RAIL Management dashboard

U S E R G U I D E / 1 7

VMware EVO: RAIL

Logging, Licensing, Updating, and Language ChoiceEVO: RAIL Management streamlines log collection, licensing, and software updates, and offers language choice for globalization. It also provides notifications and tracks tasks.

About shows the build numbers for vCenter Server, ESXi, and EVO: RAIL software.

Log Collection allows you to generate a log bundle that combines diagnostic information for vCenter Server, ESXi, and EVO: RAIL. This bundle can be uploaded to technical support as part of a Support Request (SR).

Figure 15 . EVO: RAIL Management health

U S E R G U I D E / 1 8

VMware EVO: RAIL

In Licensing enter or view your VMware EVO: RAIL license.

Choose Your Language supports globalization for the EVO: RAIL user interface.

EVO: RAIL Management allows users to check for vCenter, ESXi, and EVO: RAIL software upgrades. EVO: RAIL downloads and installs any patches for these VMware products. With a minimum of four independent ESXi hosts in an EVO: RAIL cluster, updates are non-disruptive and require zero downtime.

NOTE: In EVO: RAIL Version 1.0, vCenter Log Insight must be updated separately.

Figure 16 . EVO: RAIL Management configuration

U S E R G U I D E / 1 9

VMware EVO: RAIL

Appendix A: Network Configuration TableTemplate for your network configurationCustomize EVO: RAIL by completing the following table:

NETWORK VLAN ID

IP ADDRESS HOSTNAME/NAMING SCHEME

NETMASK GATEWAY

Client workstation/laptop for EVO: RAIL configuration and anagement (you must configure this on your laptop)

vCenter Server (port 9443)

EVO: RAIL (port 7443)

ESXi starting IP address

ESXi ending IP address

Allocate 4, 8, 12, or 16 IP addresses, depending on how many EVO: RAIL appliances you plan to have

vSphere vMotion starting IP address

Not applicableNot applicable (not a routable table)

vSphere vMotion ending IP address


Virtual SAN starting IP address

Not applicableNot applicable (not a routable table)

Virtual SAN ending IP address


VM NETWORKS VLAN ID

VM NETWORK NAME

Across all EVO: RAIL appliances Not applicable Not applicable Not applicable

NETWORK SERVICES

DNS server

N/A Not applicable Not applicable Not applicable

NTP server

Time zone

Logging:

Active Directory

OUT-OF-BAND MANAGEMENT

BMC node 1

BMC node 2

BMC node 3

BMC node 4

Table 4. Network Configuration Table

U S E R G U I D E / 2 0

VMware EVO: RAIL

EVO: RAIL default configuration tableDefault values are used in Just Go! configuration, and they are used to pre-populate fields in Customize Me! configuration. They are stored in the default configuration file that is a part of the EVO: RAIL distribution, default-config-static.json.

A VMware qualified partner will replace the default values on your system with the values you specified when you ordered EVO: RAIL. The following Network Configuration Table shows the example configuration that we used for this guide. Resources are allocated for one EVO: RAIL appliance:

• We reserved 4 IP addresses for ESXi, Virtual SAN, and vSphere vMotion.

• The naming scheme for the ESXi hosts is: prefix=host, separator=None, iterator=Num0X, top-level domain=local. Thus, the hostnames will be from host01.local through host04.local

• We used five VLANs: 20, 30, 110, 120, and a VLAN configured as a native VLAN. These need to be configured on the TOR switch(es) before configuring EVO: RAIL.

• Logging is configured to “vCenter Log Insight” at IP address 192.168.10.201. There is no DNS server configured, so vCenter Server will supply DNS service.

• In the examples in this guide, the client workstation/laptop for EVO: RAIL is configured by the customer to 192.168.10.210 (netmask: 255.255.255.0, gateway: 192.168.10.254)

Default configuration:

NETWORK VLAN ID


NETMASK GATEWAY

Client workstation/laptop for EVO: RAIL configuration and management (you must configure this on your laptop)

192.168.10.210 255.255.255.0 192.168.10.254

vCenter Server (port 9443) EVO: RAIL (port 7443)

0

192.168.10.200 vcenter.local

255.255.255.0 192.168.10.254ESXi starting IP address 192.168.10.1 host01.local

…

host04.localESXi ending IP address 192.168.10.4

vSphere vMotion starting IP address20

192.168.20.1Not applicable 255.255.255.0

Not applicable (not a routable table)

vSphere vMotion ending IP address 192.168.20.4

Virtual SAN starting IP address30

192.168.30.1Not applicable 255.255.255.0


Virtual SAN ending IP address 192.168.30.4

VM NETWORKS VLAN ID

VM NETWORK NAME

Across all EVO: RAIL appliances110

Not applicableVM Network A

Not applicable Not applicable120 VM Network B

NETWORK SERVICES

DNS server

N/A

192.168.10.200

Not applicable Not applicable Not applicable

NTP server Not set

Time zone: UTC N/A

Logging: vCenter Log Insight 192.168.10.201

Active Directory none

U S E R G U I D E / 2 1

VMware EVO: RAIL

NETWORK VLAN ID


NETMASK GATEWAY


BMC node 1

0

Provided by DHCP (default) or manually configured by end user

<ApplianceID>-01Provided by DHCP (default) or manually configured by end user


BMC node 2 <ApplianceID>-02



Table 5. Just Go! Network Configuration Table .

JSON configuration file format and valid valuesThe configuration file used for Just Go!, default-config-static.json, is part of the EVO: RAIL distribution. As an alternative to Customize Me!, you could upload a json configuration file using the Upload Configuration File button in EVO: RAIL Configuration.

EVO: RAIL Version 1.0 does not validate your json file. It must be properly formatted and the values must be valid for EVO: RAIL. The following list contains the field restrictions:

• minIP, maxIP, netmask, gateway: valid IP addresses and netmask in your network

• vlanId: valid numeric VLAN ID, configured on your top-of-rack switch

• name: alphanumeric string to identify a VM network segment

• prefix: alphanumeric string for the first part of an ESXi hostname

• separator: “”, “-“

• iterator: “NUMERIC_N”, “NUMERIC_NN”, “ALPHA”

• tld: valid top-level domain name in your network

• vcenter: alphanumeric string for the vCenter Server hostname

• passwords: clear text password containing between five and 20 characters, at least one of which must be a special character. It cannot have any character repeated three or more times in a row. (Please be aware that filling out a password in clear text in a configuration file is not secure.)

• logging: “LOGINSIGHT”, “SYSLOG”

• timezone: “UTC”

• other fields: alphanumeric strings

U S E R G U I D E / 2 2

VMware EVO: RAIL

The default configuration file that is a part of the EVO: RAIL distribution, default-config-static.json, is shown below:

{ “network”: { “dhcp”: false, “hosts”: { “management”: { “pools”: [{ “minIp”: “192.168.10.1”, “maxIp”: “192.168.10.4” }], “netmask”: “255.255.255.0”, “gateway”: “192.168.10.254”, “vlanId”: null }, “vsan”: { “pools”: [{ “minIp”: “192.168.30.1”, “maxIp”: “192.168.30.4” }], “netmask”: “255.255.255.0”, “vlanId”: 30 }, “vm”: [{ “name”: “VM Network A”, “vlanId”: 110 }, { “name”: “VM Network B”, “vlanId”: 120 }], “vmotion”: { “pools”: [{ “minIp”: “192.168.20.1”, “maxIp”: “192.168.20.4” }], “netmask”: “255.255.255.0”, “vlanId”: 20 } }, “vcenter”: { “ip”: “192.168.10.200” } }, “hostnames”: { “hosts”: { “prefix”: “host”, “separator”: “”, “iterator”: “NUMERIC _ NN” }, “tld”: “localdomain.local”, “vcenter”: “vcserver” },

U S E R G U I D E / 2 3

VMware EVO: RAIL

“passwords”: { “esxiPassword”: null, “esxiPasswordConfirm”: null, “vcPassword”: null, “vcPasswordConfirm”: null, “activeDirectoryDomain”: “”, “activeDirectoryUsername”: “”, “activeDirectoryPassword”: “”, “activeDirectoryPasswordConfirm”: null }, “global”: { “logging”: “LOGINSIGHT”, “timezone”: “UTC”, “loginsightServer”: “192.168.10.201”, “loginsightHostname”: “loginsight”, “ntpServerCSV”: “”, “syslogServerCSV”: “”, “dnsServerCSV”: “”, “proxyServer”: “”, “proxyPort”: “”, “proxyUsername”: “”, “proxyPassword”: “” } }

U S E R G U I D E / 2 4

VMware EVO: RAIL

Appendix B: Configuration ExamplesExample configuration for one EVO: RAIL appliance in a flat networkThe following Network Configuration Table is an example of an initial recommended configuration with no VLANs set.

For this example:

• We reserved four IP addresses for ESXi, Virtual SAN, and vSphere vMotion. • The naming scheme we used for the ESXi hosts is: prefix=host, separator=None, iterator=Num0X,

top-level domain=local. Thus, the hostnames will be from host01.local through host04.local

Example configuration for one EVO: RAIL appliance in a flat network (no VLANs):

NETWORK VLAN ID


NETMASK GATEWAY



0


255.255.255.0 192.168.10.254

ESXi on node 1 192.168.10.1 host01.local




vSphere vMotion on node 1

0

192.168.10.5

Not applicable 255.255.255.0Not applicable (not a routable table)

vSphere vMotion on node 2 192.168.10.6



Virtual SAN on node 1

0

192.168.10.9

Not applicable 255.255.255.0Not applicable (not a routable table)

Virtual SAN on node 2 192.168.10.10



VM NETWORKS VLAN ID

VM NETWORK NAME

Across all EVO: RAIL appliances

0

Not applicable

VM Network 1

Not applicable Not applicable0 VM Network 2

0 VM Network 3

NETWORK SERVICES

DNS server

N/A

192.168.10.200


NTP server Not set

Time zone: UTC N/A




BMC node 1

0


<ApplianceID>-01Provided by DHCP (default) or manually configured by end user





Table 6. Sample Network Configuration Table for a one EVO: RAIL appliance in a flat network (no VLANs) .

U S E R G U I D E / 2 5

VMware EVO: RAIL

Example configuration for four EVO: RAIL appliances fully scaled-outThe following Network Configuration Table is an example of what a fully scaled-out EVO: RAIL network with VLANs could look like. We allocated resources for four EVO: RAIL appliances.

For this example:

• We reserved 16 IP addresses for ESXi, Virtual SAN, and vSphere vMotion.

• The naming scheme we used for the ESXi hosts is: prefix=host, separator=None, iterator=Num0X, top-level domain=local. Thus, the hostnames will be from host01.local through host16.local

• We used six VLANs: 10, 20, 30, 110, 120, 130. These need to be configured on the top-of-rack (TOR) switch before configuring EVO: RAIL.

• The BMC node hostnames reflect that the four EVO: RAIL appliances have unique appliance IDs, denoted by <ApplianceID_1>, <ApplianceID_2>, <ApplianceID_3>, and <ApplianceID_4>.

Example configuration for one EVO: RAIL appliance in a flat network (no VLANs):

NETWORK VLAN ID


NETMASK GATEWAY



10


255.255.255.0 192.168.10.254ESXi starting IP address 192.168.10.1 host01.local

…

host16.localESXi ending IP address 192.168.10.16

vSphere vMotion starting IP address20

192.168.20.1Not applicable 255.255.255.0


vSphere vMotion ending IP address 192.168.20.16

Virtual SAN starting IP address30

192.168.30.1Not applicable 255.255.255.0


Virtual SAN ending IP address 192.168.30.16

VM NETWORKS VLAN ID

VM NETWORK NAME

Across all EVO: RAIL appliances

110

Not applicable

VM Network 1

Not applicable Not applicable120 VM Network 2

130 VM Network 3

NETWORK SERVICES

DNS server

N/A

192.168.10.200


NTP server Not set

Time zone: UTC N/A




BMC node 1

0


<ApplianceID_1>-01Provided by DHCP (default) or manually configured by end user


BMC node 2 <ApplianceID_1>-02

… …

BMC node 16 <ApplianceID_4>-16

Table 7. Sample Network Configuration Table for a scaled-out EVO: RAIL network with VLANs .

U S E R G U I D E / 2 6

VMware EVO: RAIL

Appendix C: Physical RequirementsThe following requirements are for Intel-based appliances. Specifications may vary by vendor.

Reference: Intel® Server System H2000WP Family Technical Product Specification http://download.intel.com/support/motherboards/server/sb/g52418006_h2000wp_tps_r1_6.pdf

Power Redundant AC power supplies:

Wattage 1600 W (Energy Smart)

Voltage 90 – 264 VAC, Auto-ranging, 47 Hz-63 Hz

Heat Dissipation 2560 BTU/hr

Maximum Inrush CurrentUnder typical line conditions and over the entire system ambient operating range, the inrush current may reach 65 A per power supply for 5 ms

80 Plus rating Platinum

Climate Saver (CS) rating Platinum

Table 8. Power supply specifications

AC power inlet:The power supply has an internal IEC320 C14 power inlet. The inlet is rated for a minimum of 10A at 250VAC.

AC power cord:

Cable Type SJT

Wire Size SJT

Temperature Rating 105 °C

Amperage Rating 13A

Cable Type SJT

Table 9. Power cord specifications

System behavior with one power supply failure:

INTEL® SERVER SYSTEM H2000 LOAD WITH 2X 1600W SUPPLIES

SYSTEM POWER REDUNDANCY MODE

SYSTEM BEHAVIOR WITH ONE PSU AC LOST OR FAILED

<1600W Unconstrained Redundant Mode No system throttling. All 4 nodes work normally

1600W < current load < 2160WOptimal Redundant Mode All nodes in the system are throttled to maintain

power, however, this may lower performance

>2160W Non-Redundant Mode All nodes in the system may shutdown

Table 10. System behavior during power supply failure

U S E R G U I D E / 2 7

VMware EVO: RAIL

Power recommendations:EVO: RAIL has redundant power supplies and cooling fans. Each power supply should be connected to a different power distribution unit (PDU), and each PDU should be connected to a different UPS or to a resilient data center-scale UPS. A PDU with dual input cords and Automatic Transfer Switching (ATS) is recommended to switch between power sources based on stability and availability. VMware recommends discussing the options with your data center power provider to ensure stability and resiliency.

DimensionsThe chassis supports 19-inch wide by 30-inch deep server cabinets.

Chassis dimensions:

Height 87.9 mm 3.46 inches

Width 438 mm 17.24 inches

Depth 733 mm 28.86 inches

Weight 32 kg 70.55 lbs

Table 11. Chassis dimensions

EnvironmentEnvironmental limits:

TemperatureOperating

ASHRAE Class A2 – Continuous Operation. 10ºC to 35ºC (50ºF to 95ºF) with the maximum rate of change not to exceed 10ºC per hour

ASHRAE Class A3 – Includes operation up to 40ºC for up to 900 hours per year

ASHRAE Class A4 – Includes operation up to 45ºC for up to 90 hours per year

Shipping -40ºC to 70ºC (-40ºF to 158ºF)

Humidity Non-operating 50% to 90%, non-condensing with a maximum wet bulb of 28°C (at temperatures from 25°C to 35°C)

Altitude

Operating 16 to 3048 m (-50 to 10,000 ft) Note: For altitudes above 2950 feet, the maximum operating temperature is derated 1°F/550 feet

Storage -16 to 10,600 m (-50 to 35,000 ft)

Air flow Operating H2216xxKR: 8 to 61 CFM per node

Table 12. Environmental limits

Customer Configuration OptionsAltitude This option is used to select the proper altitude that the system will be used in. Available settings include: [300m or less], [301m-900m], [901m-1500m], [Above 1500m]. EVO: RAIL is set to [301m-900m] by default.

Selecting an altitude range that is lower than the actual altitude the system will be operating at, can cause the fan control system to operate less efficiently, leading to higher system thermals and lower system performance. If the altitude range selected is higher than the actual altitude the system will be operating at, the fan control system may provide better cooling but with higher acoustics and higher fan power consumption. If the altitude is not known, selecting a higher altitude is recommended in order to provide sufficient cooling.

U S E R G U I D E / 2 8

VMware EVO: RAIL

Set Fan Profile This option is used to set the desired Fan Profile. Available settings include: [Performance] and [Acoustic]. EVO: RAIL is set to [Performance] by default.

The Acoustic mode offers the best acoustic experience and appropriate cooling capability covering the mainstream and the majority of the add-in cards used. Performance mode is designed to provide sufficient cooling capability covering all kinds of add-in cards on the market.

Fan PWM Offset This option is reserved for manual adjustment to the minimum fan speed curves. The valid range is from [0 to 100] which stands for 0% to 100% PWM adding to the minimum fan speed. This feature is valid when Quiet Fan Idle Mode is at Enabled state. EVO: RAIL is set to [0] by default.

Quiet Fan Idle Mode This feature can be [Enabled] or [Disabled]. If enabled, the fans will either shift to a lower speed or stop when the aggregate sensor temperatures are satisfied, indicating the system is at ideal thermal/light loading conditions. When the aggregate sensor temperatures are not satisfied, the fans will shift back to normal control curves. If disabled, the fans cannot shift to a lower speed or stop, regardless of whether aggregate sensor temperatures are satisfied. The default setting is [Disabled].

Note: The above feature may or may not be in effect, depending on the actual thermal characteristics of the system.

Modifying BMC Interface IP Address in the BIOSThe BMC interface IP addresses can be modified in the BIOS on an Intel-based appliance as follows:

1) Navigate to the Server Management tab and then scroll down to BMC LAN Configuration. Press <Enter>.

2) Scroll down to Intel® RMM4 IPv4 LAN configuration > IP source and select either Static or Dynamic. The default is Dynamic and the BMC interfaces obtain their IP address through DHCP. If you select Static, you will need to set the IP address, Netmask, and Gateway IP.

3) Optionally set the User ID, User status, User name, and User password.

4) Press <F10> and select save and exit. Your server will reboot with the new settings.

Default Username: UserId

Default Password: Passw0rd!

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www .vmware .comCopyright © 2014 VMware, Inc . All rights reserved . This product is protected by U .S . and international copyright and intellectual property laws . VMware products are covered by one or more patents listed at http://www .vmware .com/go/patents . VMware is a registered trademark or trademark of VMware, Inc . in the United States and/or other jurisdictions . All other marks and names mentioned herein may be trademarks of their respective companies . Item No: VMW-UG-EVO-RAIL-USER-GUIDE-USLET-106 .indd 08/14

vmware evo: rail - viktorious.nlreserve 4 ip addresses for vmware vsphere® vmotion® for each evo:...

Documents