6 Replies Latest reply on May 20, 2010 8:46 AM by khughes

    New ESX4 build causing alarms on 100MB/Full nics

    khughes Virtuoso

      I'm in the process of upgrading our hosts from 3.5 to 4.0U1, doing clean installs but running into a networking problem.  I have had no issue with my configuration from the origional setup three years ago with 3.0.2 to 3.5. We have a stand alone nic with 2 ports that go directly to a dedicated 10/100 Cisco switch which is in the DMZ.  Those two pNICs are assigned to a DMZ portgroup, and also configured 100MB/Full since the physical switch has the ports configured at 100MB/Full.  When I have a web server on one of the newly built out 4.0 hosts, I start to get the following alarms / warning messages:

       

      Lost uplink redundancy on virtual switch "vSwitch1". Physical NIC vmnic5 is down. Affected portgroups:"DMZ".

      warning - 4/15/2010 3:21:12 PM

      Alarm 'Network uplink redundancy lost' on esx03 changed from Gray to Red

      info - 4/15/2010 3:20:17 PM

      Lost uplink redundancy on virtual switch "vSwitch1". Physical NIC vmnic4 is down. Affected portgroups:"DMZ".

      warning - 4/15/2010 3:20:09 PM

       

      After talking with VMware support they weren't too helpful siting that it could be a configuration problem, "not being best practices" when its worked for 3 years until upgrading to 4.0.  I hoped it might have been just a bad NIC on one of the hosts and moved the webserver to another host I just updated but the same thing happened there too a couple minutes later.  Currently there are no servers sitting on the DMZ portgroup on either of the 4.0 hosts and haven't had an alarm or warning message yet so I'm assuming its something in 4.0 and either hard set 100MB/Full or just 100MB connections period.  Our production network which is on gig switches and auto neg have no issues period.

       

      Anyone have any ideas or insight into what might be going on?

       

       

      • Kyle