[VMware] How to install vCSA 6.5 & 6.7 on Workstation

step01. extract vCSA iso , into \vcsa\VMware-vCenter-Server-Appliance-6.7.0.12000-8832884_OVF10.ova

step02. Workstation open %\vcsa\VMware-vCenter-Server-Appliance-6.7.0.12000-8832884_OVF10.ova

step03.
匯入好之後暫不要開機

step04.
編輯 .vmx加入
——————————————————————————————-
guestinfo.cis.appliance.net.addr.family = “ipv4″
guestinfo.cis.appliance.net.mode = “static"
guestinfo.cis.appliance.net.pnid = “vcsa67.homelab.local"
guestinfo.cis.appliance.net.addr = “10.1.110.88″
guestinfo.cis.appliance.net.prefix = “24″
guestinfo.cis.appliance.net.gateway = “10.1.110.253″
guestinfo.cis.appliance.net.dns.servers = “10.1.130.1″
guestinfo.cis.appliance.root.passwd = “P@ssw0rd"
guestinfo.cis.appliance.ssh.enabled = “True"
guestinfo.cis.deployment.autoconfig = “True"
guestinfo.cis.appliance.ntp.servers = “time4.google.com"
guestinfo.cis.vmdir.password = “P@ssw0rd"
guestinfo.cis.vmdir.site-name = “default-site"
guestinfo.cis.vmdir.domain-name = “homelab.local"
——————————————————————————————-
PS: 發現以上有餵食失敗幾行 e.g.
guestinfo.cis.appliance.root.passwd = “P@ssw0rd"
guestinfo.cis.vmdir.password = “P@ssw0rd"
在開機後會發現密碼無法登入需重新reset

step05.Power-on vCSA

step06.Waiting os enter success

step07.Reset root password

step08.登入時看到畫面按下 ‘e’

step09.在 Linux開頭最後面按下 end 跳到後面 加入 rw init=/bin/bash

step10.按下 ‘F10’ boot

step11. // 建議作一下免後重置密碼無效
> ls -sh /var/log/audit
rm /var/log/audit/*.log

step12.
> whoami // check account is root
> passwd

step13.
umount /

step14.
reboot -f

step15.
confirm root account can login

step17.
https://10.1.110.88:5480 // start initiate

step18.
需調入 SSO domain , 最後即需一段時間即完成stage2

Done.


Reference:

  1. vmwarearena – How to Deploy vCenter Server appliance 6.5 on VMware Workstation 14
  2. enterprisedaddy – Deploy VCSA 6.5 on Workstation
  3. VMware KB: 2147144 – How to reset the lost or forgotten root password in vCenter Server Appliance 6.5

[VMware] import VDP 6.1.x error ‘The OVF package is signed with an invalid certificate ( 簽署 OVF 套件所用的憑證無效 )

在滙入 vDP 6.1.4時發生如下畫面錯誤訊息 " The OVF package is signed with an invalid certificate ( 簽署 OVF 套件所用的憑證無效 ) "

試解無效:

1.匯入"Publisher EMC Corporation"提供憑證也無解

2.匯入vCenter提供也是不行.

尋求Google大神總結有三個方式

vdp-error-invalid-certificate.jpg

Method#1. 改用 HTML5方式來匯入是最快方式

Method#2. 用7-zip 打開 .ova刪除裡頭的 .mf檔案

Method#3. 利用 ovftool工具轉換 , 載點
ovftool.exe –skipManifestCheck c:\tmp\vSphereDataProtection-6.1.5.ova c:\vdpfix.ova

[VMware] Cannot power-on VM ‘A general system error occurred: No connection could be made because the target machine actively refused it(發生一般系統錯誤:無法連線,因為目標電腦拒絕連線)

有人反應一台虛擬機器匯人後無法開機,會出現如下錯誤訊息

Solution:

~vCS~

services.msc > VMware vCenter workflow manager service > Start

~vCSA~
> service vmware-vpx-workflow restart

> shell.set –enabled true
> service-control –status vmware-vpx-workflow // check status
> service-control –start vmware-vpx-workflow

最後再試著Power-on VM , enjoy


Reference:

  1. VMware KB 2118319 : A general system error occurred: No connection could be made because the target machine actively refused it” error when powering on VMs on vCenter Server 6.0
  2. ISHM Blog : VM 在 vCenter 6 無法開機,發生 A general system error occurred: Connection refused

[VMware] VDP change backup transport method

VDP預設 transport method優先順序是先採用 1.Hot-Add 接著是 2.NBDSSL ,其次是 3.NBD

~Solution~

step01. vi /usr/local/avamarclient/var/avvcbimage.cmd

step02. add as below , 利用":"來區隔開
————————————————–
–transport=hotadd:nbd:nbdssl
————————————————–

step03. restart service
service avagent restart // VDP 5.x
service avagent-vmware restart  // VDP 6.x


Reference :
VMware KB: 2061083 – Changing the default and alternate transport methods in vSphere Data Protection (VDP)

[VMware] How to Enable VMs eachother Clipboard Copy and Paste function

Solution#1 for A-VM with B-VM eachother

Modify 2 VMs .vmx add as below
————————————————————————
isolation.tools.copy.disable   FALSE
isolation.tools.paste.disable FALSE
————————————————————————

Solution#2 for All VMs of the Hosts

step01. login ESX/ESXi host

step02. cp /etc/vmware/config /etc/vmware/config.bak // before modify to backup it!

step03. vi /etc/vmware/config , Add these entries to the file
——————————————————————————————–
isolation.tools.copy.disable="FALSE"
isolation.tools.paste.disable="FALSE"
——————————————————————————————–

 


 

Reference :
VMware KB 1026437 – Clipboard Copy and Paste does not work in vSphere Client 4.1 and later

[VMware] Automatic Install VMware-Tools like unattached mode

若在作LAB是Linux environment時,除了template virtual machine  或 .ova/ovf 檔案匯入;安裝Linux後免不了要手動安裝vmware-tools.pl 一直按enter什麼都不想改是可以安裝完畢。但懶人法解開VMwareTools-x.x.x-xxxxxxx.tar.gz後執行

# ./vmware-install.pl -d default


 

Reference :
1. virtuallyGhetto – Automating silent installation of VMware Tools on Linux w/Automatic Kernel Modules

[VMware] Consolidation failed for disk node ‘scsi0:0’:5 (Input/output error)

當客戶反應說他們因儲存設備某一個LUN有問題;需立即將某台虛擬機器搬離這個有問題的LUN。但卻無法搬離開且有些怪異現象出現!

狀況查看:
1.  該台VM service運作正常。
2. 但用備份方式是都有錯誤狀況. e.g.
# use export to .ova/ovf > 失敗 (Failed to eport Virtual Machine: Unable to read data from the transport connection: The connection was closed.)
# use vmkfstools clone vmdk > 失敗 ( clone: 100% done.Failed to clone disk: Input/output error (327689).)
# use Backup (HPE VM explorer) > 失敗 (Failed: <VM/VM-000005-deltavmdk cannot be downloaded. ‘HTTP/1.1500 internal Server error’)
# use VMware Data Protect backup > 失敗 (整併磁碟節點 ‘scsi0:0’ 失敗:5 (input/output error).)
# 該VM瀏覽Datastore會發現大量 vm-000001.vmdk 增長到vm-000009.vmdk(快照檔案) ; 但由snapshot manager查看是無任何快照記錄.
# vMotion 搬移失敗.
# 指令 ‘esxcli storage core path stats get‘ 查看到僅有對應有問題的LUN,有所謂(Failed Read Operations: 74 / Failed Write Opterations: 2 )

由以上種種現象來看確實Storage volume有些狀況;但FibreChannel Switch & HBA是沒什麼問題.

最後解決客戶這問題僅能有OS level來處理;我則是用Acronis 11.7 offline backup all disk (ignore error才能成功) , then Create new VM and rexovery that image .

Done.

 

[VMware] vSphere ESXi 6.5 Host or under VMs network lost ?!

客戶前一陣子打電話來問他VMware vCenter Server 6.0 底下有一台Host無緣無故 Lost connect ,且每一個vmkernel IP都掛點;此外,虛擬機器(VMs)網路都不通也無法運作!

礙於公司壓力下他只有唯一選擇"重開機"主機 ;好景不常..這問題隔日又發生。

這情況讓我想到Microsoft windows Server 2012 / 2012 R2 Hyper-V 搭配上 Broadcom NetXtreme (e.g. BCM5719 ..) 遇上開啟VMQ Bug (PS:驅動程式若是 v16.8.0.4 此版或更早都會受影響;解法是更新驅動程式停用VMQ { Set-NetAdapterVmq -Name “NIC 1″ -Enabled $False }

(註) Microsoft KB : Virtual machines lose network connectivity when you use Broadcom NetXtreme 1-gigabit network adapters

OK!回到正題…請客戶先調出他主機到底是用那一家網卡及驅動程式版本 & 韌體 ? 及 vSphere ESXi 6.5 build number ?

Ans :
> Broadcom 5719
> ESXi 6.5.0 build no.4564106 ( ESXi 6.5 GA )

step01. esxcli network nic get -n vmnic{x}

vmware-bug-kb-2150728

由以上資訊估狗大神keyword一搜,還真的是Bug….. Orz

This is a known issue with ntg3 driver version 4.1.0.0, bundled in ESXi 6.5 GA.

To fix this issue upgrade to latest ntg3 driver version 4.1.2.0 or newer To download latest version of ntg3 see VMware Download Center.

就是更新驅動程式到 v4.1.2.0以上版本就搞定啦 ^O^

Reference :

VMware KB : 2150728 – NICs using ntg3 driver may experience loss of connectivity

[VMware] Recovering from the configured recovery point objective (RPO) is lower than what the host can support error

客戶反應一台VDP 6.x在測試還原一台機器後,開機還原測試機無法開機,

error message :

Recovering from the configured recovery point objective (RPO) is lower than what the host can support error

這大多是VDP backup source VM曾是或正是VMware Replication 抄寫過!

Solution#1 (效率快,原廠提供方式)

step01. backup VDP restore VM 該機器 .vmx

step02. vi /vmfs/volumes/{storage}/VM/VM.vmx

step03. 將以下的註解不用及存檔
————–未修改前——————

hbr_filter.configGen = “"
hbr_filter.rpo = “"
hbr_filter.destination = “"
hbr_filter.port = “0″
hbr_filter.gid = “"
hbr_filter.protocol = “"
hbr_filter.quiesce = “true"
hbr_filter.opp = “true"
hbr_filter.pause = “true"
scsi0:0.hbr_filter.rdid = “"
scsi0:0.hbr_filter.persistent = “"
——————————————–

>>
————–已修改後——————

#hbr_filter.configGen = “"
#hbr_filter.rpo = “"
#hbr_filter.destination = “"
#hbr_filter.port = “0″
#hbr_filter.gid = “"
#hbr_filter.protocol = “"
#hbr_filter.quiesce = “true"
#hbr_filter.opp = “true"
#hbr_filter.pause = “true"
#scsi0:0.hbr_filter.rdid = “"
#scsi0:0.hbr_filter.persistent = “"
——————————————–

step04.
vim-cmd vmsvc/getallvms | grep -i to find the vmid  // 最前面的數字即是 vmid

step05.
vim-cmd vmsvc/reload  {vmid}  // 重新載入該VM config

step06.
try Power-On VDP restore VM

Done & Enjoy ^O^

solution#2 (厚功)

step01.砍掉無法開機VDP restore VM

step02.重新source VM reconfig vSphere Replication

step03.

Recovery settings 裡的Point in time instances
(V) Enable
Keep {x} instances per day for the last {y} days (24total)

Done.

 


Reference:

1.Recovering from the configured recovery point objective (RPO) is lower than what the host can support error. (2123433)

[VMware] ESXi 5.5 upgrade to 6.0U2 DependencyError issue

今日作ESXi 5.5U2 upgrade to ESXi 6.0U2 使用ESXi CLI update happen some issue , messages as below

[DependencyError]
 VIB VMware_bootbank_esx-base_6.0.0-2.34.3620759 requires vsan >= 6.0.0-2.34, but the requirement cannot be satisfied within the ImageProfile.
 VIB VMware_bootbank_esx-base_6.0.0-2.34.3620759 requires vsan << 6.0.0-2.35, but the requirement cannot be satisfied within the ImageProfile.
 Please refer to the log file for more details.

solution for ESXi CLI

step1.
# esxcli software sources profile list -d /path/Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1-Bundle.zip
display profile information 記得下它

Name                                                                                        Vendor    Acceptance Level
————————————————————————    ———-   ————————
Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1     Cisco      PartnerSupported

step2.

# esxcli software profile update -p Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1 -d /path/Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1-Bundle.zip

step3.
# esxcli software vib install -n esx-base -n vsan -n vsanhealth -d /path/Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1-Bundle.zip

step4.
Reboot apply new esxi version

後記:
若是用vSphere Update Manager (VUM) 或是 放置ISO方式(pre-boot)是不會有以上產牛相依性這類狀況唷!!


Reference :

VMware KB 2144595 ( Dealing with vSAN VIB issues in ESXi 6.0 Update 2 and later releases )