advertisement
VMware EVO:RAIL
Management and Maintenance
User Guide
EVO:RAIL Release 1.1.0 and 1.2.x
Document Revision: 1.1.0-6 (October 22, 2015)
Copyright © 1998-2015 VMware, Inc. All rights reserved.
Copyright, trademark, and patent information: http://pubs.vmware.com/copyright-trademark.html
.
EVO:RAIL Management and Maintenance User Guide
Table of Contents
Add EVO:RAIL Appliances to an EVO:RAIL Cluster .................................................. 8
Appendix B: EVO:RAIL Cluster Shutdown/Restart Procedures .................................... 16
EVO:RAIL Single Appliance Shutdown Procedure .................................................. 21
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1
EVO:RAIL Management
Once your initial EVO:RAIL Appliance is deployed and configured, EVO:RAIL Management is where you will perform your day-to-day tasks such as:
•
Create virtual machines (VMs)
•
Monitor virtual machines (VMs)
•
Monitor the status of an EVO:RAIL cluster, appliances, and nodes
•
Add EVO:RAIL appliances
•
Enter appliance license(s)
•
Choose localization setting
•
Update EVO:RAIL software components
Access EVO:RAIL Management
To access EVO:RAIL Management:
•
From your EVO:RAIL workstation/laptop browse to the EVO:RAIL IP address https://<evo:rail-ip-address>:7443 .
•
Log in with username:
and the password specified during EVO:RAIL Initial
Configuration.
The latest versions of Firefox, Chrome, and Internet Explorer 10+ are all supported. The minimum recommended screen resolution is 1280x1024.
Create Virtual Machines
EVO:RAIL Management streamlines the creation of virtual machines with simple selections for:
•
Guest operating system
•
Virtual machine size
•
Network segment (VLAN)
•
Security options
In EVO:RAIL Management, use the following procedure to create a VM:
Step 1.
Click Create VM on the left sidebar to begin the virtual machine creation process. Once you begin the process you will have the option to either Cancel or Go Back to a previous step.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 3
Step 2.
In the Create VM called text box, type a name for your virtual machine.
Step 3.
To load your ISO image file to be used for your Guest OS, follow one of these procedures: a. If you are uploading the ISO image file for local storage, click Upload Image. i. Click Choose File to open the standard file selection pop-up. ii. Locate the ISO image file on your local file system and select it. iii. Click Open to return to EVO:RAIL Management. iv. Click Upload Image. At this point the ISO image will be copied to the Virtual SAN datastore.
NOTE:
If the file is too large to upload, see the resolution section of
VMware Knowledge Base Article
2109915.
b. If you are uploading the ISO image file from a network drive, click Mount NFS/CIFS. i. Click the protocol of the network drive you are accessing: NFS or CIFS ii. Enter the URL <format:[protocol]:/[host]/path/to/file.iso> iii. Click Mount Remote Image. At this point the ISO image will be copied to the Virtual SAN datastore. c. If you are using a previously uploaded guest OS, you will be able to re-use an existing image by clicking on its name.
NOTE:
EVO:RAIL Management does not support importing existing pre-built copies of virtual machines in OVA/OVF format. To work around this, use the vSphere Web Client interface to create virtual machines from an existing OVA/OVF format. The template can then be viewed in EVO:RAIL
Management as a VM, which you can use to clone in order to make a VM from the template.
Step 4.
Confirm the Guest OS Version that was loaded from the dropdown menu, click Continue.
Step 5.
Select a VM size: Small, Medium or Large.
NOTE:
EVO:RAIL has a set of predefined virtual machine sizes based on standard VMware
recommendations for each Guest OS. See Appendix A .
Step 6.
Click Select VM Size.
Step 7.
Select one or more network segments the VM should connect to.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 4
Step 8.
Click Select VM Networks.
Step 9.
Select the security policy: No Policy, Risk Profile 3, Risk Profile 2, or Risk Profile 1.
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.
•
No Policy means that no security configuration options are applied to the virtual machine.
•
Risk Profile 3, which specifies guidelines that should be implemented in all environments. These are
VMware best practices for all data centers.
•
Risk Profile 2, which specifies guidelines for more sensitive environments or small/medium/large enterprises that are subject to strict compliance rules.
•
Risk Profile 1, which 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.
NOTE:
By selecting a more secure policy, you will lose some virtual machine functionality, such as automated tools, inability to shrink virtual machine disks, persistent mode only, no logging and performance information, blocked device interactions, and limited remote console connections.
See the hardening guides for more details.
Step 10. Click Create and Start a New VM.
Step 11. After the virtual machine is created, the EVO:RAIL Management interface will be displayed.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 5
Monitor Virtual Machines
EVO: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 virtual machines. Use the Search box to find virtual machines by name.
The following table describes which options are available when the VM is powered on and when it is powered off.
VM Options Available
Install VMware Tools
Rename VM
Eject ISO
Open Console
Clone VM
Suspend/Resume VM
Delete VM
Power Off/On
Yes
Yes
No
Yes
VM Powered On
Yes
See Note below
Yes
Yes and an ISO is mounted
Yes
VM Powered Off
No
Yes
No
No
Yes
No
Yes
Yes
NOTE:
To install VMware Tools your guest OS must already be installed on your virtual machine, and the guest OS ISO image must be ejected from the virtual CD drive. When the VM is powered on and the
ISO is unmounted, this option is active. When the VM is powered on and the ISO is mounted, this option will be disabled, but hovering over it will display the message ‘VMware Tools have been successfully mounted…”. Once VMware tools is installed this icon will not appear.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 6
Monitor Appliance Health
EVO:RAIL Management simplifies live compute management with health monitors for CPU, memory, storage, and virtual machine usage for an entire EVO:RAIL cluster, individual appliances, and individual nodes.
•
Click Health on the left sidebar
Status is displayed on the appliance health page nodes, HDD, SSD, ESXi device and NIC. If everything is normal a green checkmark is displayed; if there is a warning a yellow triangle is displayed. A critical alarm is indicated with a red triangle. All alarms and warnings are from vCenter Server.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 7
The overall health of the EVO:RAIL cluster is displayed. The status is displayed for storage IOPS, CPU usage and memory usage as follows:
Color
Red
Yellow
Green
Description
•
Over 85% storage usage used.
•
Over 85% CPU utilization used.
•
Over 85% memory usage used.
•
There is 75% to 85% storage usage used.
•
There is 75% to 85% CPU utilization used.
•
There is 75% to 85% memory usage used.
•
There is below 75% storage usage used.
•
There is below 75% CPU utilization used.
•
There is below 75% memory usage used.
The total storage information for the EVO:RAIL cluster is also shown: total capacity, amount used, amount free, and amount provisioned. Each EVO:RAIL appliance in the cluster is shown with a simple red, yellow, or green status. You can click on the EVO:RAIL appliance tabs on the top of screen to drill down to the details for that appliance. You can return to the Overall System, by clicking on that tab on the top of the screen.
For each EVO:RAIL appliance you can see the status of the items above and each node, HDD, SSD, ESXi boot disk and NIC. If everything is normal a green checkmark is displayed; if there is a warning a yellow triangle is displayed. A critical alarm is indicated with a red triangle. All alarms and warnings are from vCenter Server.
Add EVO:RAIL Appliances to an EVO:RAIL Cluster
EVO: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.
Prerequisites
We recommend that all VMware components (ESXi, vCenter Server, and EVO:RAIL) are the same version on all
EVO:RAIL appliances in an EVO:RAIL cluster. See Appendix A in the EVO:RAIL Customer Release Notes for supported configurations.
Procedure
Whenever EVO:RAIL detects a new appliance the following message and button are displayed on the EVO:RAIL
Management page:
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 8
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.
CAUTION: 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.
To add an EVO:RAIL appliance follow these steps:
Step 1.
Click Add EVO:RAIL Appliance.
Step 2.
If additional IP addresses are not required the input areas will be grayed out. If you are required to enter IP addresses, you must make sure that none of them conflict with existing IP addresses in your network. a. Enter the New Starting and Ending addresses for the ESXi IP Pool for the new appliance. b. Enter the New Starting and Ending addresses for the vMotion IP Pool for the new appliance. c. Enter the New Starting and Ending addresses for the Virtual SAN IP Pool for the new appliance.
Step 3.
Enter the Appliance ESXi Password.
Step 4.
Enter the Appliance vCenter Server Password.
Step 5.
Click Add EVO:RAIL Appliance.
Step 6.
When the process is complete, click Finish.
Ongoing Configuration
The ongoing configuration tasks in EVO:RAIL Management include licensing, localization and updates. All of these can be found when you click Config on the left sidebar.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 9
Activating EVO:RAIL Licenses
To license your EVO:RAIL Appliance, follow these steps:
Step 1.
Get your Partner Activation Code (PAC) from your Qualified EVO:RAIL Partner (QEP).
Step 2.
Go to your QEP’s activation portal to enter your PAC(s).
Step 3.
You will receive an email with your license key(s).
Step 4.
Click Config on the left sidebar.
Step 5.
Under the Licensing tab, enter your license key(s):
Step 6.
Click License Appliance.
Step 7.
If the license is part of the vSphere Loyalty Program in EVO:RAIL Release 1.2, the following steps are needed: a. Go to MyVMware to group the required set of licenses into a single license key. i. Create a folder within MyVMware with the licenses called “EVORAIL” ii. Send a service request to the VMware license team with the license keys you need combined into a single license key. b. Enter the single license key obtained above, then click License Appliance. c. Confirm you want to you use this license, then click License Appliance. d. No other licenses are needed – your EVO:RAIL appliance is now fully licensed.
Localizing the User Interface
EVO:RAIL Management is available in English, French, German, Japanese, Korean, Simplified Chinese, and
Traditional Chinese. To choose your language, follow these steps:
Step 1.
Click Config on the left sidebar.
Step 2.
Under the General tab, Choose your Language section, click on your selection.
Updating Appliance Software
EVO:RAIL supports vCenter, ESXi, and EVO:RAIL software patch and upgrade. With a minimum of four independent
ESXi hosts in an EVO:RAIL cluster, updates are non-disruptive and require zero downtime.
Refer to the EVO:RAIL release notes from your QEP to verify what components need to be updated.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 0
The EVO:RAIL Management update interface CANNOT be used to update an EVO:RAIL Release
1.x appliance/cluster to EVO:RAIL Release 2.x. Attempting to use it will result in a loss of data.
Contact your EVO:RAIL partner for the update process.
Prerequisites
•
Create a snapshot or backup copy of the vCenter Server virtual appliance. This can be accomplished by connecting to VMware vSphere Web Client via https://<hostname>:9443, where <hostname> is the IP address or hostname of EVO:RAIL
•
All files must be uploaded from http://my.vmware.com
into a directory accessible from your EVO:RAIL
Management workstation/laptop. See the Release Notes for updated files list.
Follow these update steps in order.
Step 1.
Update the <vmware-marvin-release-build.rpm> component first: a. Click the Updates tab b. Click Upload, and browse to the directory with the components you will be updating: c. Select <vmware-marvin-release-build.rpm>, click Open.
Step 2.
Click Check now. If the EVO:RAIL check succeeds, the Offline Updates box adds a switch for you to activate to perform the update.
Step 3.
Click the Offline Updates switch from No to Yes for <vmware-marvin-release-build.rpm>.
Step 4.
Click Update.
After the update is complete, you will receive a notification that you were disconnected from EVO:RAIL
Management. It can take up to 5 minutes for the new EVO:RAIL RPM to initialize. After EVO:RAIL
Management restarts, you will be prompted to log in.
NOTE:
If EVO:RAIL Management is not fully present after the automatic restart, refresh the web browser.
See VMware Knowledge base article 2101828 for details.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 1
Step 5.
Update the other components. a. Click the Updates tab. b. Click Upload and browse to the directory with the components you will be updating.
<EVO_RAIL_release-build.>.zip
<VMware-vCenter-Server-Appliance-release-build-updaterepo>.zip (if applicable)
<ESXI-release-build>.zip (if applicable) c. Select a file, click Open. d. If applicable, repeat for each component in the EVO:RAIL release.
Step 6.
Click Check now. If the EVO:RAIL check succeeds, the Offline Updates box adds a switch for you to activate to perform the update.
Step 7.
Click the Offline Updates switch from No to Yes for each component you uploaded.
Step 8.
Click Update.
NOTE:
It can take up to 15 minutes for the vCenter Server to reboot and for all of services to initialize.
The update time for ESXi depends on the quantity of virtual machines and might take a few hours to complete; however, the appliance will function as normal during that time.
EVO:RAIL Maintenance
EVO:RAIL has provided many facilitated maintenance procedures. This section describes the EVO:RAIL maintenance procedures such as:
•
Access vSphere Web Client
•
Logging and Events
•
Hardware Replacement
•
Appliance Shutdown
Access vSphere Web Client
EVO:RAIL Management allows you to access the vSphere Web Client to perform more complicated tasks than those found in the streamlined EVO:RAIL interface.
Step 1.
Click the VMware vSphere Web Client icon in the upper right corner of the EVO:RAIL Management
VMS page
Step 2.
Log in with the administrator login and password you setup during EVO:RAIl Configuration.
NOTE:
From vSphere Web Client, do not use service datastores when creating or moving VMs. These datastores are only to be used by your QEP for serviceability.
NOTE:
If you use the vSphere Web Client to perform tasks that are automated by EVO:RAIL you may run into situations where the automated flow does not work properly.
Logging and Events
EVO:RAIL Management provides several ways to access log information:
•
Events - displays EVO:RAIL tasks and critical alarms in the EVO:RAIL Management interface.
•
VMware vCenter Log Insight – provides access to the default EVO:RAIL logging mechanism. You may alternately select an existing third-party syslog server during initial configuration.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 2
•
Support Logs - combines diagnostic information for vCenter Server, ESXi, and EVO:RAIL into one bundle to send to support.
Events
EVO:RAIL Management provides you access to the list of events occurring in EVO:RAIL Management, either initiated by EVO:RAIL or by the user. This is available from Events on the left sidebar. Events can be organized by Critical and Most Recent.
vCenter Log Insight
EVO:RAIL is deployed with vCenter Log Insight. However, you may choose to use your own third-party syslog server(s). 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.
See VMware vCenter Log Insight Documentation.
If you configured an existing third-party syslog server, follow the instructions supplied with that product.
Support Logs
EVO:RAIL Management combines diagnostic information for vCenter Server, ESXi, and EVO:RAIL into one log bundle. This log bundle can be uploaded to technical support as part of a support request (SR). To gather the log information from your EVO:RAIL appliance, follow these steps:
Step 1.
Click Config on the left sidebar.
Step 2.
Under the Support tab, click Generate Support Bundle.
NOTE:
This process can take from 20 minutes to several hours. It is run in the background, so you can continue to use EVO:RAIL Management.
Step 3.
After the Support Log is generated, click Download Support Bundle.
The .zip file will be downloaded to your workstation.
Live Logging
EVO:RAIL Management provides you access to a live stream of EVO:RAIL log messages as each message is created. To access this feature:
Step 1.
Click Config on the left sidebar
Step 2.
Under the Support tab, click Show EVO:RAIL Live Logging.
Step 3.
This opens a window at the bottom of the EVO:RAIL Management interface. You have the ability to search for key words, show only alarms, only errors, or all message. The arrows can be used to expand or collapse the viewer.
To turn off live logging:
Step 1.
Click Config on the left sidebar.
Step 2.
Under the Support tab, click Hide EVO:RAIL Live Logging.
Hardware Replacement
EVO:RAIL supports the replacement of the following Field Replacement Units (FRUs): node, CPU, motherboard, memory, storage adapter, ESXi boot device, HDD, SSD and the power supply. Contact your QEP for specific hardware replacement procedures. Do not use the Hardware Replacement or Add EVO:RAIL Node automated processes unless directed to by your QEP. These processes are documented in a EVO:RAIL Hardware Replacement
Guide.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 3
Appliance Shutdown
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 4
Appendix A – Virtual Machine Size by Guest OS
Guest OS
Red Hat Enterprise Linux 7 (64-bit)
Red Hat Enterprise Linux 6 (64-bit)
Red Hat Enterprise Linux 5 (64-bit)
Ubuntu Linux (64-bit)
CentOS 4/5/6 (64-bit)
Guest OS
Microsoft Windows Server 2012 (64-bit)
Microsoft Windows Server 2008 (64-bit)
Guest OS
Microsoft Windows Server 2003 (64-bit)
EVO:RAIL Size
Small
Medium
Large
EVO:RAIL Size
Small
Medium
Large
EVO:RAIL Size
Small
Medium
Large
vDisk vCPU
16 GB 1
24 GB 2
32 GB 4
vDisk vCPU
40 GB 1
60 GB 2
80GB 4
vDisk vCPU
16 GB 1
32 GB 2
60 GB 4
Core
1
1
1
Core
1
1
1
Core
1
1
1
vMEM
1 GB
2 GB
6 GB
vMEM
1 GB
4 GB
8 GB
vMEM
1 GB
4 GB
8 GB
Guest OS
Microsoft Windows 8 (64-bit)
EVO:RAIL Size
Small
Medium
Large
vDisk vCPU
32 GB 1
40 GB 2
60 GB 2
Core
1
1
1
vMEM
2 GB
4 GB
8 GB
Guest OS
Microsoft Windows 7 (64-bit)
EVO:RAIL Size
Small
Medium
Large
vDisk vCPU
32 GB 1
40 GB 2
60 GB 2
Core
1
1
1
vMEM
1 GB
4 GB
8 GB
Guest OS
Microsoft Windows XP
EVO:RAIL Size
Small
Medium
Large
vDisk vCPU
16 GB 1
32 GB 2
60 GB 2
Core
1
1
1
vMEM
1 GB
2 GB
4 GB
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 5
Appendix B: EVO:RAIL Cluster Shutdown/Restart
Procedures
The following are manual procedures to Shutdown/Restart an EVO:RAIL cluster, with one or multiple appliances.
For these procedures there are two categories of virtual machines (VMs):
System: comprised of VMware vCenter Server Appliance, VMware vCenter Log Insight, and any QEP
Solution virtual machines
Client: comprised of all other virtual machines.
EVO:RAIL Cluster Shutdown Procedure
The following manual procedure is for graceful cluster shutdown of a complete cluster (single or multiple appliances):
Step 1.
From EVO:RAIL Management, click VMS on the left sidebar.
Step 2.
Power off all client VMs with the following steps: a. If a VM is on, click Power Off/Shutdown. b. A confirmation message will appear, click Confirm Shutdown. c. Repeat for each VM.
NOTE:
Do not power off any QEP Specific virtual machines.
Step 3.
Click the VMware vSphere Web Client icon , and login with administrator privileges.
Step 4.
Click vCenter in the left pane and you will be in vCenter Home.
Step 5.
Migrate all the system VMs (VMware vCenter Server Appliance, VMware vCenter Log Insight, and any
QEP Solution VMs) with the following steps: a. From Inventory Trees, select Virtual Machines. b. Right-click the virtual machine and select Migrate. c. For Select Migration Type, select Change host, then click Next. d. For Select Destination Resource, select Marvin-Virtual-SAN-Cluster-<id>, then click Next. e. For Select Host, select the first ESXi host, such as esxi-node01.vm.vmworld.local, and then click
Next. f. For Select vMotion Priority, select Reserve CPU for optimal vMotion performance
(Recommended), then click Next. g. Review all information and click Finish. h. Repeat for all system VMs. (VMware vCenter Server Appliance, VMware vCenter Log Insight, and any QEP Solution virtual machines)
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 6
Step 6.
Enable Maintenance Mode on all but the first ESXi host with the following steps: a. Return to vCenter Home. b. From Inventory Trees, select Hosts. c. For each ESXi host 02, 03, 04, etc. right-click and select Enter Maintenance Mode. d. Select the check box for Move powered-off and suspended virtual machines to other hosts in the
cluster. e. Select No data migration from the Virtual SAN data migration dropdown. f. Click OK.
Step 7.
Disable High Availably with the following steps: a. Return to vCenter Home. b. From the Inventory Trees, select Clusters. c. Select MARVIN-Virtual-SAN-Cluster-id in either the left or center panes. d. Select Manage, then Settings in the center pane. e. Under Services, select vSphere HA.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 7
f. If the center pane says vSphere HA is Turned ON, click Edit. g. Uncheck Turn ON vSphere HA. h. Click OK.
Step 8.
Enable automatic start for all system VMs (VMware vCenter Server Appliance, VMware vCenter Log
Insight, and any QEP Solution VMs) with the following steps: a. Return to vCenter Home. b. From Inventory Trees, select Hosts. c. Select the first ESXi host, such as esxi-node01.vm.vmworld.local. d. Select Manage, then Settings in the center pane. e. Under Virtual Machines select VM Startup/Shutdown. f. Click Edit in the center pane. g. Select Automatically start and stop the virtual machines with the system. h. Select each system VM, use the Up arrow to move each to the Automatic Startup section in the following required order: i. VMware vCenter Server Appliance (Set the Startup Delay to 30 seconds) ii. VMware vCenter Log Insight iii. QEP Solution VM(s), if any are present i. Click OK.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 8
Step 9.
Power off all system VMs (VMware vCenter Server Appliance, VMware vCenter Log Insight, and any QEP
Solution VMs) with the following steps: a. Return to vCenter Home. b. From Inventory Trees, select Virtual Machines. c. Right-click the system virtual machine and select Shut Down Guest OS. d. A message will appear asking to confirm power off, click Yes. e. Repeat until all system VMs are powered off.
Step 10. For each appliance, power off all nodes; at this point since the vSphere Web Client is no longer accessible so your options are: a. Press the power button on each EVO:RAIL node, or b. Use out-of-band management if ACPI is available, or
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 1 9
c. Use the vSphere Client to connect to each node and use the shutdown command.
EVO:RAIL Cluster Restart Procedure
The cluster is restarted in the reverse order:
Step 1.
Power on each EVO:RAIL appliance. Power on Node 1, last.
NOTE:
It may take up to 15 minutes for all services to be fully restored and for EVO:RAIL Management to be accessible.
Step 2.
Log in to vSphere Web Client using an account with administrator privileges.
Step 3.
Click vCenter in the left pane and you will be directed to vCenter Home.
Step 4.
Enable High Availably with the following steps: a. From the Inventory Lists, select Clusters. b. Select MARVIN-Virtual-SAN-Cluster-id in either the left or center panes. c. Select Manage, then Settings in the center pane. d. Under Services, select vSphere HA. e. If the center pane says vSphere HA is Turned OFF click Edit. f. Check Turn ON vSphere HA. g. Click OK.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 2 0
Step 5.
Exit Maintenance Mode on the all the ESXi hosts 02 and beyond with the following steps: a. Return to vCenter Home. b. From Inventory Trees, select Hosts. c. Right-click the ESXi host and select Exit Maintenance Mode.
Step 6.
From EVO:RAIL Management, click VMS on the left side bar.
Step 7.
For each client VM, click Power On.
EVO:RAIL Single Appliance Shutdown Procedure
The following manual procedure is for graceful cluster shutdown of a single appliance in a multi appliance cluster:
Identify the Appliance ID on the Asset Tag sticker on the physical appliance.
From EVO:RAIL Management, identify the ESXi hostnames on the appliance that will be shutdown with the following steps: a. Click the Health Icon on the left sidebar. b. Click the Appliance ID from Step 1. c. Identify the ESXi hostnames on the four nodes on the appliance you are shutting down.
Click the VMware vSphere Web Client icon , and login using administrator privileges.
Enable Maintenance Mode on the four ESXi hosts identified in Step 2 with the following steps: a. Click vCenter in the left pane and you will be in vCenter Home. a. From Inventory Trees, select Hosts. b. For each of the four ESXi hosts, right-click and select Enter Maintenance Mode. c. Select the check box for Move powered-off and suspended virtual machines to other hosts in the
cluster. d. Select Full data migration from the Virtual SAN data migration dropdown. e. Click OK.
Do one ESXi host at a time. Wait until the ESXi host has entered maintenance mode before proceeding to the next. Full Data Migration can take a long time. See Place a Member of
Virtual SAN Cluster in Maintenance Mode and Virtual SAN – Maintenance Mode Monitoring for more details.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 2 1
Power off the four ESXi hosts with the following steps: a. From Inventory Trees, select Hosts. b. Right-click on the ESXi host and select Shut Down. c. Enter the reason for the shut down and click OK. d. Repeat for each ESXi host.
EVO:RAIL Single Appliance Restart Procedure
The appliance is restarted in the reverse order:
Power on the EVO:RAIL appliance.
Log in to vSphere Web Client using an account with administrator privileges.
Click vCenter in the left pane and you will be directed to vCenter Home.
Exit Maintenance Mode on the four ESXi hosts with the following steps: a. Return to vCenter Home. b. From Inventory Trees, select Hosts. c. Right-click the ESXi host and select Exit Maintenance Mode. d. Repeat for each ESXi host.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 2 2
Appendix C: Document Change History
The following is the list of changes for Document Revision 1.1.0-6
•
Removed Appendix B, Security Profile Details. Security profiles will be documented in EVO:RAIL Release 2.0
Documentation.
•
Renamed Appendix C, EVO:RAIL Cluster Shutdown, to Appendix B.
•
Changed the name from vRealize Log Insight to VMware vCenter Log Insight.
•
Added more information to Monitor Virtual Machines.
•
Added more information to Monitor Appliance Health.
The following is the list of changes for Document Revision 1.1.0-5
•
Changed Updating Appliance Software. Previously this section instructed a user to upload all the files at once.
The following is the list of changes for Document Revision 1.1.0-4
•
Changed Appendix D: EVO:RAIL Cluster Shutdown/Restart. Previously this section was specifically for a single appliance and now has been expanded to a complete Cluster. The procedure was updated to include a startup delay on vCenter Server Appliance. In addition, a new procedure was added to shutdown/restart a single appliance in a multi appliance cluster.
•
Changed title to EVO:RAIL Release 1.2.x (instead of 1.2.0). It covers both cases.
The following is the list of changes for Document Revision 1.1.0-3
•
In Appliance Restart Procedure, a step was added to enable high availability.
E V O : R A I L M A N A G E M E N T A N D M A I N T E N A N C E U S E R G U I D E 2 3
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project