Ok... here's the situation.
ESX 3.5 Virtual machine network doesn't connect to vm network on start as configured.
I haven't seen this behavior before this release. Any work arounds or patches?
There is a patch( ESX350-200712401-BG) available for update of bnx2 driver to address the following issues:
An issue with the BCM5709 firmware where ping requests sometimes fail after loading and unloading the bnx2 driver.
An issue with the bnx2 driver where a device using the bnx2 driver fails to connect to the a 100 Mbps network during the network autonegotiation period after system boot.
Link for ESX 3.5 patches:
Link for the related kb:
Note: Patch bundle ESX350-200712407-BG must be installed prior to installing this patch. The esxupdate utility will check to ensure that ESX350-200712407-BG is installed before proceeding with installation of this patch.
See if this solves your problem.
If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points
Here's the answer...
My customer had Virtual Machine Port Groups with the following naming standard: VLAN-500-192.168.140.0/28
VirtualCenter 2.5 does not like the forward slash in the name. Once we changed to VLAN-500-192.168.140.0-28, All was good!
Hopefully this will save someone some time.