Knowledge Base

Starting with the ESX Server 2.5.2 Update Patch 2 release, rebooting your server no longer has the potential to modify persistent bindings. (ESX Server Update Patch 2 has build number 18712. For information on how to determine the build number of your ESX Server installation, see www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=392.)

In prior releases, the /etc/init.d/vmware init script automatically updated the /etc/vmware/pbindings configuration file whenever an ESX Server system rebooted or shut down. In some situations, that behavior was undesirable. (A solution is documented at www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1302.)

Persistent bindings are no longer updated when you reboot your server. As a consequence, you need to update the bindings manually whenever you add a new target to the Fibre Channel SAN. To update your bindings, complete the following steps:

1. Run the cos-rescan.sh command in a shell window, or use the management interface to add the new target to the server.
2. Run the wwpn.pl -v command to display the mappings between the ESX Server vmhba*:* target names and the Fibre Channel WWPN:WWNN names. Verify that the correct mappings are displayed.
3. Run the pbind.pl -A command to store the new mappings in the /etc/vmware/pbindings configuration file.