vSphere Patch application guide¶
Index
Introduction¶
Purpose of This Guide¶
Items |
Status |
Applying for ECL2.0 |
Application completion |
Logical Network Menu |
Completed creating total 4 IDs: For vSphere Management data (Data Plane) / For vSphere virtual server transmission data (Data Plane) /For vSphere vMotion(Data Plane) For Storage Connectivity (Storage Plane) |
File Storage |
Connection completion |
Firewall menu (vUTM) |
Completed creating a Firewall |
Inretnet Conectivity Menu |
Completed creating Internet Gateways |
| VMware vSphere ESXi | Settings completed |
| VMware vCenter Server 6.0u2 | Configuration completed |
Preliminary Items Needed¶
•Customers are advised to prepare a ECL2.0 network having access to Internet.
Service Descriptions For Reference¶
Customers are advised to read the following service descriptions for reference:
•Service Description: Baremetal Server
•Service Description: OS
•Service Description: Dedicated Hypervisor vSphere ESXi
At the Usage of This Guide¶
Customers are noted of the following information as they refer to this guide
This document describes the procedure actually used for setup in Service Provider, as an example. The procedure does not necessarily assure that the procedure works for the environment and configuration of a customer.
•This guide focuses on deployment procedure unique to vSphere ESXi configuration in ECL2.0. This guide will not cover general and overall deployment process of vSphere ESXi.
•This guide does not cover general operations or instructions for customers to configure Logical Network , firewall or virtual servers utilized in this guide. For general operations related to these product customers are advised to refer to Enterprise Cloud 2.0 service descriptions and other such tutorials available online.
•Customers are advised that any published details available in this guide can be changed, modified, or revised without prior notice.
Overview¶
This section describes the procedure for applying a patch with VMware vSphere.
The overall flow is as follows.
Version upgrade of Platform Services Controller (hereafter, PSC)
Version upgrade of vCenter Server
Applying the patch to ESXi
Note
The System Administrator privilege is used for this work.
Patch application for dealing with vulnerability
Patch/binary file acquisition¶
Category |
Datacenter / Enterprise Cloud 2.0 Service Providermunications Support /General Inquiry |
Type |
Inquary |
Content |
VMware Patch/binary file provision request |
Service menu |
vSphere |
Tebant ID |
<Corresponding tenant ID> |
Region |
Select a region for use. |
(For failure occurrence) Date when the problem occurred |
No description |
(For failure occurrence) Is the operation history present? |
No description |
(For failure occurrence) Is the problem currently occurring? |
No description |
Details |
Provide the VMware Patch file.
※必要なbuild番号を記述ください。
※ご利用のベアメタルサーバーのフレーバーを記述ください。
Be careful that the patch type to be supplied differs depending on the flavors.
|
Urgency |
Low |
Influence rate |
Normal request |
Attached file |
None |
**For this procedure, the following configuration and file are used. **
Baremetal Flavor：General Purpose 2 v1
- Build：VMware-VIMSetup-all-6.0.0-7977899
Applied Patch：VMware-ESXi-6.5.0-Update1-5969303-HPE-650.U1.10.1.0.14-Jul2017
PSC and vCenter Server version upgrade procedures¶
Save the acquired binary file in Datastore.¶
**On the left pane of vSphere Web Client , select Storage. **
**Select “NFS” created in the previous section, and then select “Browse Files”. **
**After the transition, newly create a folder. Here, “ISO” and “Patch” have been created. **
Select the “Patch” folder created on the middle pane, and then select “Upload a file to The Datastore”.
**Save the acquired binary file in the “Patch” folder. **
**Similarly, save the acquired version upgrade file in the “ISO” folder. **
Stopping vCenter and acquiring a snapshot¶
**On vSphere Client, select vCenter, and then click “Shut down the virtual machine”. **
On vSphere client, select “vCenter” then “Snapshot”.
On the Take Virtual Machine Snapshot screen, enter an arbitrary name for “Name”, and then click “OK”.
**After acquisition of Snapshot, select “vCenter”, and then click “Power On The Virtual machine” on the right pane to boot. **
**After booting, click “Edit Virtual machine settings” on the right pane to start. **
From “Hardware”, select CD/DVD, and then select “Device Type”, “Datastore ISO File”, and “Browse...” in the order.
**Select “Browse Datastore” then “NFS”, and click “Open”. **
**For upgrade of the PSC and vCenter versions, select “ISO” this time, and then click “Open”. **
Select “VMware-VIMSetup...” in the ISO folder, and then click “OK”. **
Log into vCenter, and check that the VIM file previously mounted is present in drive D.
**Expand the file, and then click “autorun”. **
**Select “vCenter Server for Windows”, and then click “Install”. **
**After the installer is opened, click “Next”. **
**After the written consent for use is displayed, confirm the content, check the checkbox, and then click “Next”. **
- **The display is switched to the update screen having a checkbox which asks if backup of vCenter has been taken. Check the checkbox, and then click “Update”. **※現在の6.0のbuild が表示されているのでアップデート後切り替わっているか確認します。
**Update of PSC and vCenter is executed at a time. **
**After “Setup Completed” is displayed, click “Finish”. **
**On vSphere Web Client, select “vCenter” then “summary” to check. If Version Information shows higher built, the update is completed. **
Deleting the snapshot¶
After finishing the updade, on vSphere Web Client, select “Hosts and cluster”, “vesxi-22.osaka...”, “Monitor”, then “All Issue” in the order. Check that no errors are shown, and then delete the snapshot. **
Note
If the snapshot is not deleted and is left, the operation speed can be decreased.
**On vSphere Web Client, select “Hosts and cluster”, and then right-click “vCenter”. Then after clicking “Snapshots”, click “Manage Snapshots...”. **
- **Select the snapshot name created with “Manage VM Snapshots for vCenter”, and then click “Delete”. **※確認画面が表示されますので間違いないかご確認のうえ「Yes」をクリックしてください。
Applying a patch to the host server¶
**Stop or move VM on the host server to which the patch is to be applied. **
**After the completion, right-click the target host, and then select “Maintenance Mode” then “Enter Maintenance Mode” to switch to the maintenance mode. **
**After the confirmation screen is displayed, merely click “OK”. **
**Check that “esxi-22.osaka...” has been switched to the maintenance mode. **
**Connect the work terminal to the terminal placed into the maintenance mode, through SHH (in this configuration, use of putty). **
**The following command also allows to check if switching to the maintenance mode has been made. **
# vim-cmd hostsvc/hostsummary | grep -i mainte
inMaintenanceMode = true,
**Search for the profile of the patch to be applied. **
# vesxcli software sources profile list -d /vmfs/volumes/NFS/Patch/VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip
Name Vendor Acceptance Level
------------------------------------ -------------------------- ----------------
HPE-ESXi-6.0.0-Update3-600.10.2.0.23 Hewlett Packard Enterprise PartnerSupported
Apply the shown patch.
# esxcli software profile update -d /vmfs/volumes/NFS/Patch/VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip -p HPE-ESXi-6.0.0-Update3-600.10.2.0.23
**After a while, the result is displayed. When it is displayed as shown in the red box, the application is completed and reboot is to be performed. **
**After reboot is finished, check that “6921384” is shown as the built version. **
**On vSphere Web Client, exit the maintenance mode. **
For each server, repeat the same work to complete the entire job.