What could be the problem?

After an upgrade from ESX/ESXi 4.1 to ESXi 5.0, your monitoring department are reporting that they have stopped receiving Syslog data from all of the ESXi hosts. What could be the problem?

After an upgrade from ESX/ESXi 4.1 to ESXi 5.0, your monitoring department are reporting that they have stopped receiving Syslog data from all of the ESXi hosts. What could be the problem?

A.
Tech Support Mode is disable by default after an upgrade to ESXi 5.0 stopping all traffic on all ports

B.
Custom ports that were opened by using the ESX/ESXi 4.1 esxcfg-firewall command do not get copied during the upgrade to ESXi 5.0.

C.
ESXi 5.0 cannot send logs to Syslog servers.

D.
Custom ports that were opened by using the ESX/ESXi 4.1 esxcfg-firewall command do not remain open after the upgrade to ESXi 5.0



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Silencioso

Silencioso

The host firewall configuration is affected. When you migrate from ESX 4.x to ESXi 5.0, the ESX 4.x rule sets list is replaced by the new rule sets list in ESXi 5.0. However, the migration preserves the status of services (enabled/disabled) and the list of allowed IP addresses that were added by the ESX firewall configuration tool, esxcfg-firewall. Customized firewall rules that were created in ESX 4.x. are not preserved after the upgrade. Custom ports that were opened by using the ESX 4.x esxcfg-firewall command do not remain open after the upgrade to ESXi 5.0.
VMware vSphere 5.0 What’s New page 34