Fix the ESXi not responding problem

~ allen ~ Leave a comment

Situation:

A “not responding” are displayed after all esxi hypervisor shown in vsphere client which linked to the vcenter. Right click any of the esxi and select “Connect” will bring it back. But after a short while, no more than 90 secs, it will be back to not responding status.

Solution:

1 In vShpere client, open menu “Administration” — “vCenter Server Settings”, click “Runtime Settings” from the left panel, make sure that all IP and server name are correct. If not, re-enter it. Close and reopen your vSphere client — This is important.

2 Try to ping from your vCenter, not the vSphere client, to each of esxi hypervisors.

3 If you are using Windows Server 2008/R2 or any OS with firewall for vCenter, you need to add or change some firewall rules:

change:

Enable the “File and Printer Sharing (Echo Request – ICMPv4-In)”

Enable the “File and Printer Sharing (Echo Request – ICMPv6-In)”

Add a rule to allow TCP 903 income for ESXi heartbeat.

Add a rule to allow UDP 902 income for ESXi heartbeat.

4 Try to reconnect all ESXi hypervisors.

 

If the problem still exists, you have to google it again.

Chorus本地模式版已经发布

~ allen ~ Leave a comment

Chorus是一个框架，它实现了多个部件之间的通讯功能。在它的协助下，软件系统中的每个部件可以自由通讯，而不论这些部件运行在同一个程序，同一台计算机，还是在世界的任何角落。

Chorus是一种模型，它展示了软件系统内部的物理结构。在它的支持下，软件系统中的每个部件可以随心拼装，而不论这些部件构造于您的产品，您的企业，还是获取自其他供应商。

Chorus是一份标准，它定义了每个程序部件的接口规格。在它的规范下，软件系统中的每个部件可以严格定义，而不论这些部件开发于同一个员工，同一个小组，还是来自外包公司。

 

当前已经发布本地模式版，实现同一个应用程序内部的通讯功能。

您有兴趣了解吗？请访问Chorus发布页。