crond (pid 9701) is running...
Chain INPUT (policy ACCEPT 9169 packets, 4606K bytes)
 pkts bytes target     prot opt in     out     source               destination        

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination        

Chain OUTPUT (policy ACCEPT 10249 packets, 7082K bytes)
 pkts bytes target     prot opt in     out     source               destination        

Incoming and outgoing ports blocked by default.
Enabled services: CIMSLP VCB swISCSIClient CIMHttpsServer vpxHeartbeats LicenseClient sshServer

Opened ports:

gpm (pid 9623) is running...
ipmi_msghandler module loaded.
ipmi_si_drv module loaded.
ipmi_devintf module loaded.
/dev/ipmi0 exists.
Table: filter
Chain INPUT (policy ACCEPT)
target     prot opt source               destination        

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination        

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        

irqbalance is stopped
iSCSI driver is not loaded
Usage: /etc/init.d/megaraid_sas_ioctl {start|stop|restart}
vmware-hostd (pid 7750) is running...
/etc/init.d/microcode_ctl: reading microcode status is not yet supported
Usage: /etc/init.d/mptctlnode {start|stop|restart}
Configured devices:
lo eth1 eth2 vswif0
Currently active devices:
lo vmnic1 vmnic0 vmnic4 vmnic3 vswif0
rpc.mountd is stopped
nfsd is stopped
rpc.statd is stopped
nscd is stopped
ntpd is stopped
cimserver (pid 9748) is running...
portmap is stopped
The random data source exists
rdisc is stopped
saslauthd is stopped
smartd is stopped
snmpd is stopped
snmptrapd is stopped
sshd (pid 1967 1923) is running...
syslogd (pid 1717) is running...
klogd (pid 1721) is running...
Usage: (halt|reboot|start) {start}
The vmnixmod kernel module is loaded.
The VMkernel is loaded.
vmware-aam is not running[  OK  ]
Usage: vmware-autostart {start|stop|restart}
none
VMware VMkernel authorization daemon is running (pid 9712).
vmware-vpxa is running
webAccess (pid 9650) is running...
winbindd is stopped
openwsmand (pid 9788) is running...
xinetd (pid 9614) is running...
ypbind is stopped
Nightly yum update is disabled.

A．

檢查軟體相容性

vCenter Server軟體版本號必需高於/等於置管ESX的版本 ；

vSphere Client軟體版本號必需高於/等於被訪問的vCenter版本；

vSphere Client軟體版本號必需高於/等於被訪問的ESX版本 ；

在使用Update Manager時必需保持vCenter、vSphere Client、Update Manager這三者的版本是一致的。

更多VI 架構元件的相容性請查閱使用文件與以下軟體相容手冊：

vSphere Compatibility Matrix

VMware Infrastructure Compatibility Matrixes

B．

檢查網路：

1.使用PING命令測試網路連線，如果PING命令測試不成功。請檢查：

vCenter與ESX所在的Vlan

檢查vCenter和ESX的閘道器與網路配置

物理鏈路檢查

2.

檢查虛擬交換機配置

esxcfg-vswitch –l

esxcfg-vswif –l

esxcfg-nics –l

3.

檢查伺服器埠開放情況

檢視ESX防火牆埠開放：esxcfg-firewall –q

檢視伺服器埠使用情況netstat -na

4.

檢查物理交換機QOS配置

5.

vCenter到ESX的網路是否經過NAT地址轉換

C．

檢查儲存狀態，ESX是否BOOT FROM SAN

檢查儲存連線

vSphere Client –Configuration-Storage Adaptes

vSphere Client –Configuration-Storage

執行”esxcfg-mpatch -l”檢視已連線的儲存

執行”esxcfg-scsidevs –l”,檢視已簽名的SCSI裝置

確認儲存空間

在ESX執行”vdf -h”檢查各分割槽儲存使用情況

vSphere 4服務控制檯的檔案系統

檢視存放Service Console的虛擬磁碟

#vsd –l

vsa0:0:0 /dev/sda

查詢Service Console的VMDK路徑

#vsd –g

/vmfs/volumesesxconsole.vmdk

D.

vCenter與ESX配置檢查：

1.

vCenter與ESX系統的配置會影響到程式的正常執行

檢查/etc/hosts檔案的預設記錄是否存在(hosts檔案中127.0.0.1該條系統自帶解析記錄不可刪除)

127.0.0.1 localhost.localdomain localhost

2.

檢視HOSTD與VPXA程序是否正在執行

#ps –ef | grep hostd

#ps –ef | grep vpxa

（如果HOSTD與VPXA程式沒有在執行，可直接執行以下命令啟動：

啟動HOSTD：

# /bin/sh /usr/bin/vmware-watchdog -s hostd -u 60 -q 5 -c /usr/sbin/vmware-hostd-support /usr/sbin/vmware-hostd /etc/vmware/hostd/config.xml –u

啟動VPXA

#/bin/sh /opt/vmware/vpxa/bin/vmware-watchdog -s vpxa -u 30 -q 5 /opt/vmware/vpxa/sbin/vpxa

3.

重新啟動HOSTD與VPXA檢查程式是否異常

#service mgmt-vmware restart

#service vmware-vpxa restart

（重啟如果提示如下，說明重啟服務正常

[[email protected] ~]# service mgmt-vmware restart

Stopping VMware ESX Management services:

VMware ESX Host Agent Watchdog [ OK ]

VMware ESX Host Agent [ OK ]

Starting VMware ESX Management services:

VMware ESX Host Agent (background) [ OK ]

Availability report startup (background) [ OK ]

[[email protected] ~]# service vmware-vpxa restart

Stopping vmware-vpxa: [ OK ]

Starting vmware-vpxa: [ OK ]）

4.

稽核vpxa代理配置檔案：

檔案地址:/etc/opt/vmware/vpxa/vpxa.cfg

5.

稽核hostd配置檔案：

檔案地址:/etc/vmware/esx.conf

6.

在vCenter指定管理ESX的地址

7.

檢查vCenter的SSL驗證

Vi client—login to vCenter—Administration—vCenter Server Settings—SSL Settings—去掉”vCenter requires verified host SSL certificates”的勾選。

綜上：如果仔細檢查並執行以上每一項沒有問題，但是ESX在vCenter中狀態依舊不正常，請執行以下操作：

1. 使用VI Client連線到vCenter

2. 停止該cluster的 HA與DRS

3. 右鍵有故障的ESX -> Disconnect -> 再次右鍵將該ESX從vCenter上移除

4. 使用root使用者登入到ESX執行以下操作

i. 執行命令停止系統管理服務的執行

service mgmt-vmware stop

service vmware-vpxa stop

ii. 刪除vpxa Agent程式

rpm –qa |grep vpxa

rpm –e <上一條指令返回的結果>

iii. 將vpxa舊的配置檔案改名

Esx 3.5 配置檔案的路徑

mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.cfg.old

Esx 4.0 配置檔案的路徑

mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.cfg.old

5. 登入ESX 的命令列終端：

#service iptables stop

# chkconfig --level 35 iptables off

6. service mgmt-vmware start

7. 重新將ESX新增到vCenter

8. 啟用HA與DRS