VMware Cloud Community
WarrenB20111014
Contributor
Contributor
‎05-19-2011 12:55 PM

Can not add second nic to vSwitch ESXi 4.1 (Free)

I am trying to add a second nic to a vSwicth, but I keep getting the following error:

Call "HostNetworkSystem.UpdateVirtualSwitch" for object "networkSystem" on ESXi "My IP" failed.
Operation failed, diagnostics report: Error interacting with configuration file /etc/vmware/esx.conf: Write failed during Unlock.  This is likely due to a full or read-only filesystem.  Original Error was: Error interacting with configuration file /etc/vmware/esx.conf: Unable to write to file /etc/vmware/esx.conf.KJ0jZ8 while saving /etc/vmware/esx.conf operation aborted.  It is likely this was caused by a Full Disk.

I have tried to do this in the vSphere client under Configuration>Networking>vSwitch Properties>Network Adapters>Add. I choose the "Unclaimed Adapter" and click next, next and finish. I have also tried the command "esxcfg-vSwitch --server XXX.XXX.XXX.XXX -L vmnic1 vSwitch0" from CLI on my laptop with the following error:

"An error occurred during host configuration"

I have also tried downloading the vMA appliance and I am getting the same error. I have tried repairing the initial host instalation and I am still not able to add the second nic.

The error message seems to be saying that either the disk is full or that the disk is read-only, neither is true. Is there a lock on these files or file permissions are wrong ? I have also tried to create a file named /etc/vmware/esx.conf.KJ0jZ8 and I was able to. I am logged in to the client, cli, vMA and SSH as root. Here is the directory listing for /etc/vmware/ :

drwxr-xr-x    1 root     root                512 May 19 19:20 .
-r--r--r-T    1 root     root                  0 May 18  2010 .#dvsdata.db
-r--r--r-T    1 root     root                  0 May 18  2010 .#esx.conf
-r--r--r-T    1 root     root                170 May 18  2010 .#license.cfg
-r--r--r-T    1 root     root                  0 May 18  2010 .#locker.conf
-r--r--r-T    1 root     root                  0 May 18  2010 .#snmp.xml
-r-------T    1 root     root                 30 May 18  2010 .#vmware.lic
drwxr-xr-x    1 root     root                512 May 19 19:20 ..
-r--r--r--    1 root     root               3077 May 18  2010 BootbankFunctions.sh
-r--r--r--    1 root     root              17704 May 18  2010 UpgradeFunctions.sh
-rw-r--r-T    1 root     root                355 May 18  2010 config
-rw-r--r-T    1 root     root               5819 May 18  2010 configrules
-rw-r--r-T    1 root     root                512 May 19 19:20 dvsdata.db
-rw-------    1 root     root              32217 May 19 15:25 esx.conf
drwxr-xr-x    1 root     root                512 May 19 15:25 esxupdate
-r--r--r--    1 root     root                 58 May 18  2010 ft-vmk-version
-r--r--r--    1 root     root                 59 May 18  2010 ft-vmx-version
drwxr-xr-x    1 root     root                512 May 19 19:20 hostd
drwxr-xr-x    1 root     root                512 May 19 15:25 icu
drwxr-xr-x    1 root     root                512 May 19 15:25 ike
-rw-r--r-T    1 root     root                101 May 18  2010 ima_plugin.conf
drwxr-xr-x    1 root     root                512 May 19 15:25 init
-rw-r--r-T    1 root     root                311 May 19 19:20 license.cfg
-rw-r--r-T    1 root     root                440 May 18  2010 localsas
-rw-r--r-T    1 root     root                 52 May 19 01:46 locker.conf
-r--r--r-T    1 root     root                647 May 18  2010 logfilters
drwxr-xr-x    1 root     root                512 May 19 15:25 microcode
-rw-r--r-T    1 root     root                755 May 18  2010 passthru.map
-rw-r--r-T    1 root     root               4414 May 18  2010 pci.classlist
-rw-------    1 root     root             625864 May 18  2010 pci.ids
-rw-r--r-T    1 root     root            1767254 May 18  2010 pci.xml
drwxr-xr-x    1 root     root                512 May 18  2010 pciid
drwxr-xr-x    1 root     root                512 May 19 15:25 secpolicy
drwxr-xr-x    1 root     root                512 May 19 15:25 service
-rw-r--r-T    1 root     root                  0 May 18  2010 settings
-rw-------    1 root     root              23726 May 18  2010 simple.map
-rw-r--r-T    1 root     root                114 May 19 01:46 snmp.xml
drwxr-xr-x    1 root     root                512 May 19 15:25 ssl
-rw-r--r-T    1 root     root                363 May 18  2010 support
-r--r--r--    1 root     root                101 May 18  2010 sysboot.conf
-rw-------    1 root     root                  0 May 19 15:25 thirdparty.map
-rw-r--r-T    1 root     root             380961 May 18  2010 usb.ids
-r--r--r--    1 root     root                569 May 18  2010 vfat_image_250.dd.gz
drwxr-xr-x    1 root     root                512 May 19 15:25 vm-support
drwxr-xr-x    1 root     root                512 May 19 15:25 vmkiscsid
-rw-------    1 root     root                 29 May 19 15:45 vmware.lic
drwxr-xr-x    1 root     root                512 May 19 15:25 vmwauth
-rw-r--r-T    1 root     root                  0 May 18  2010 welcome

I pulled these entries out of the logs:

May 19 19:36:23 vobd: May 19 19:36:23.565: 15068977692us: [vob.net.pg.uplink.transition.down] Uplink: vmnic1 is down. Affected portgroup: VM Network. 1 uplinks up. Failed criteria: 512.
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.565 30481B90 error 'NetworkProvider' opID=7A6A4F15-0000011D] DoSetVirtualSwitchBridge: Error interacting with configuration file /etc/vmware/esx.conf: Write failed during Unlock.  This is likely due to a fu
May 19 19:36:23 ll or read-only filesystem.  Original Error was: Error interacting with configuration file /etc/vmware/esx.conf: Unable to write to file /etc/vmware/esx.conf.5M5QXU while saving /etc/vmware/esx.conf operation aborted.  It is likely this was caused by a Fu
May 19 19:36:23 ll Disk.
May 19 19:36:23 vobd: May 19 19:36:23.565: 15068977697us: [vob.net.pg.uplink.transition.down] Uplink: vmnic1 is down. Affected portgroup: Management Network. 1 uplinks up. Failed criteria: 512.
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.565 30481B90 info 'App' opID=7A6A4F15-0000011D] AdapterServer caught exception: 0c753408
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.565 30481B90 info 'TaskManager' opID=7A6A4F15-0000011D] Task Completed : haTask-ha-host-vim.host.NetworkSystem.updateVirtualSwitch-435524638 Status error
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.565 30481B90 info 'Vmomi' opID=7A6A4F15-0000011D] Activation [N5Vmomi10ActivationE:0xba21708] : Invoke done [updateVirtualSwitch] on [vim.host.NetworkSystem:networkSystem]
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.565 30481B90 verbose 'Vmomi' opID=7A6A4F15-0000011D] Arg vswitchName:
May 19 19:36:23 Hostd: "vSwitch0"
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.565 30481B90 verbose 'Vmomi' opID=7A6A4F15-0000011D] Arg spec:
May 19 19:36:23 Hostd: (vim.host.VirtualSwitch.Specification) {
May 19 19:36:23 Hostd:    dynamicType = <unset>,
May 19 19:36:23 Hostd:    numPorts = 128,
May 19 19:36:23 Hostd:    bridge = (vim.host.VirtualSwitch.BondBridge) {
May 19 19:36:23 Hostd:       dynamicType = <unset>,
May 19 19:36:23 Hostd:       nicDevice = (string) [
May 19 19:36:23 Hostd:          "vmnic0",
May 19 19:36:23 Hostd:          "vmnic1"
May 19 19:36:23 Hostd:       ],
May 19 19:36:23 Hostd:       beacon = (vim.host.VirtualSwitch.BeaconConfig) null,
May 19 19:36:23 Hostd:       linkDiscoveryProtocolConfig = (vim.host.LinkDiscoveryProtocolConfig) null,
May 19 19:36:23 Hostd:    },
May 19 19:36:23 Hostd:    policy = (vim.host.NetworkPolicy) {
May 19 19:36:23 Hostd:       dynamicType = <unset>,
May 19 19:36:23 Hostd:       security = (vim.host.NetworkPolicy.SecurityPolicy) {
May 19 19:36:23 Hostd:          dynamicType = <unset>,
May 19 19:36:23 Hostd:          allowPromiscuous = false,
May 19 19:36:23 Hostd:          macChanges = true,
May 19 19:36:23 Hostd:          forgedTransmits = true,
May 19 19:36:23 Hostd:       },
May 19 19:36:23 Hostd:       nicTeaming = (vim.host.NetworkPolicy.NicTeamingPolicy) {
May 19 19:36:23 Hostd:          dynamicType = <unset>,
May 19 19:36:23 Hostd:          policy = "loadbalance_srcid",
May 19 19:36:23 Hostd:          reversePolicy = true,
May 19 19:36:23 Hostd:          notifySwitches = true,
May 19 19:36:23 Hostd:          rollingOrder = false,
May 19 19:36:23 Hostd:          failureCriteria = (vim.host.NetworkPolicy.NicFailureCriteria) {
May 19 19:36:23 Hostd:             dynamicType = <unset>,
May 19 19:36:23 Hostd:             checkSpeed = "minimum",
May 19 19:36:23 Hostd:             speed = 10,
May 19 19:36:23 Hostd:             checkDuplex = false,
May 19 19:36:23 Hostd:             fullDuplex = false,
May 19 19:36:23 Hostd:             checkErrorPercent = false,
May 19 19:36:23 Hostd:             percentage = 0,
May 19 19:36:23 Hostd:             checkBeacon = false,
May 19 19:36:23 Hostd:          },
May 19 19:36:23 Hostd:          nicOrder = (vim.host.NetworkPolicy.NicOrderPolicy) {
May 19 19:36:23 Hostd:             dynamicType = <unset>,
May 19 19:36:23 Hostd:             activeNic = (string) [
May 19 19:36:23 Hostd:                "vmnic0",
May 19 19:36:23 Hostd:                "vmnic1"
May 19 19:36:23 Hostd:             ],
May 19 19:36:23 Hostd:          },
May 19 19:36:23 Hostd:       },
May 19 19:36:23 Hostd:       offloadPolicy = (vim.host.NetOffloadCapabilities) {
May 19 19:36:23 Hostd:          dynamicType = <unset>,
May 19 19:36:23 Hostd:          csumOffload = true,
May 19 19:36:23 Hostd:          tcpSegmentation = true,
May 19 19:36:23 Hostd:          zeroCopyXmit = true,
May 19 19:36:23 Hostd:       },
May 19 19:36:23 Hostd:       shapingPolicy = (vim.host.NetworkPolicy.TrafficShapingPolicy) {
May 19 19:36:23 Hostd:          dynamicType = <unset>,
May 19 19:36:23 Hostd:          enabled = false,
May 19 19:36:23 Hostd:          averageBandwidth = <unset>,
May 19 19:36:23 Hostd:          peakBandwidth = <unset>,
May 19 19:36:23 Hostd:          burstSize = <unset>,
May 19 19:36:23 Hostd:       },
May 19 19:36:23 Hostd:    },
May 19 19:36:23 Hostd:    mtu = <unset>,
May 19 19:36:23 Hostd: }
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.566 30481B90 info 'Vmomi' opID=7A6A4F15-0000011D] Throw vim.fault.PlatformConfigFault
May 19 19:36:23 Hostd: [2011-05-19 19:36:23.566 30481B90 info 'Vmomi' opID=7A6A4F15-0000011D] Result:
May 19 19:36:23 Hostd: (vim.fault.PlatformConfigFault) {
May 19 19:36:23 Hostd:    dynamicType = <unset>,
May 19 19:36:23 Hostd:    faultCause = (vmodl.MethodFault) null,
May 19 19:36:23 Hostd:    faultMessage = (vmodl.LocalizableMessage) [
May 19 19:36:23 Hostd:       (vmodl.LocalizableMessage) {
May 19 19:36:23 Hostd:          dynamicType = <unset>,
May 19 19:36:23 Hostd:          key = "com.vmware.esx.hostctl.default",
May 19 19:36:23 Hostd:          arg = (vmodl.KeyAnyValue) [
May 19 19:36:23 Hostd:             (vmodl.KeyAnyValue) {
May 19 19:36:23 Hostd:                dynamicType = <unset>,
May 19 19:36:23 Hostd:                key = "reason",
May 19 19:36:23 Hostd:                value = "Error interacting with configuration file /etc/vmware/esx.conf: Write failed during Unlock.  This is likely due to a full or read-only filesystem.  Original Error was: Error interacting with configuratio
May 19 19:36:23 n file /etc/vmware/esx.conf: Unable to write to file /etc/vmware/esx.conf.5M5QXU while saving /etc/vmware/esx.conf operation aborted.  It is likely this was caused by a Full Disk.
May 19 19:36:23 Hostd: ",
May 19 19:36:23 Hostd:             }
May 19 19:36:23 Hostd:          ],
May 19 19:36:23 Hostd:          message = <unset>,
May 19 19:36:23 Hostd:       }
May 19 19:36:23 Hostd:    ],
May 19 19:36:23 Hostd:    text = "",
May 19 19:36:23 Hostd:    msg = ""
May 19 19:36:23 Hostd: }
May 19 19:36:25 vobd: May 19 19:36:25.566: 15070977689us: [esx.problem.net.redundancy.lost] Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic1 is down. Affected port groups: "VM Network", "Management Network".
May 19 19:36:25 Hostd: [2011-05-19 19:36:25.567 30440B90 info 'ha-eventmgr'] Event 38 : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic1 is down. Affected portgroups:"VM Network", "Management Network".

The above says the second nic is down, but the vSphere client shows it. Please let me know if there are any other logs I should be looking at. I have googled the error above but have not found the solution yet.

Thanks,

Warren Bell

Tags (5)
0 Kudos
3 Replies
paulkdickson
Contributor
Contributor
‎05-19-2011 01:19 PM

"Try turning it off and on again."

Your permissions in /etc/vmware look good, so aside from that, check your disk space.  "df -h"

0 Kudos
WarrenB20111014
Contributor
Contributor
‎05-19-2011 01:46 PM

I have rebooted the host many times. I have completely scratched the host and rebuilt it. There is plenty of space and I can write large files to that directory. I think there is something else wrong and the error message is misleading.

Warren

0 Kudos
WarrenB20111014
Contributor
Contributor
‎05-20-2011 08:07 AM

Got it working. Added the nic at the host console and everything is working ok now. I thought the choice at initial set-up was for one or the other nics not one or the other or both. I guess it would have helped if I read the screens completely before I moved on. I wish the error message would have been a little more informative, it was very misleading. Also, I do not know why the nic even shows up in the vShere client with an option to add it if it was not going to let me add it in the first place.

Thanks,

Warren

0 Kudos