An administrator creates a custom ESXi firewall rule using an XML file, however the rules do not appear in the vSphere Web Client. Which action should the administrator take to correct the problem?

Question

Accepted Answer

B. Load the new rules using esxcli network firewall refresh. Running esxcli network firewall refresh causes ESXi to re-read all XML rule definition files from the firewall configuration directory and apply any new or changed entries immediately. This is the correct and non-disruptive method for activating newly placed custom firewall XML rules so they appear in the vSphere Web Client.

Answer

A. Load the new rules using esxcli network firewall reload. esxcli network firewall reload reloads the firewall module and its currently cached configuration but does not re-read or pick up newly added XML rule definition files.

Answer

C. Verify the entries in the XML file and then reboot the ESXi host. A full host reboot is unnecessary because the esxcli refresh command is designed to apply new rules on a running host without downtime.

Answer

D. Remove the ESXi host from the inventory and add it back. Removing and re-adding the host from inventory is a disruptive administrative action with no effect on loading local firewall rule XML files.

An administrator creates a custom ESXi firewall rule using an XML file, however the rules do not appear in the vSphere Web Client. Which action should the administrator take to correct the problem?

Question

Options

How the community answered

Why each option

Topics

Community Discussion