LACP cannot be enabled

Products

• VMware vSphere ESXi

Issue/Introduction

When you enable LACP using the CLI, the command errors out. For example, enable lacp <dvs-name> produces an error. The errors occur for different reasons, as outlined below.

• vob.net.lacp.enable = "LACP for VDS {1} is enabled." - This is for information only.
• vob.net.lacp.disable = "LACP for VDS {1} is disabled." -- If you do not explicitly disable it from the CLI, you can disable it from the LACP module. The following vobs are a cause of this error:
  • vob.net.lacp.policy.incompatible = "Lacp error: Current teaming policy for VDS {1} is incompatible, supported is IP hash only."
  • vob.net.lacp.uplink.inactive = "Lacp error: All uplinks on VDS {1} must be active."
  • vob.net.lacp.uplink.fail.speed = "Lacp error: Speed across all uplinks must be same, VDS {1} uplink {2} has different speed."
  • vob.net.lacp.uplink.fail.duplex = "Lacp error: Duplex mode across all uplinks must be full, VDS {1} uplink {2} has different duplex modes."
  • vob.net.lacp.peer.noresponse = "Lacp error: No peer response on upLink {1} for VDS {2}."

The vobs below are warnings or information only when the you try to change an uplink property, such as moving the uplink to a blocked state,shutting it down, or pulling the cable, etc.

• vob.net.lacp.uplink.transition.down = "Lacp warning: Uplink {1} on VDS {2} moved out of link aggregation group."
• vob.net.lacp.uplink.transition.up = "Lacp info: Uplink {1} on VDS {2} moved into link aggregation group."
• vob.net.lacp.uplink.blocked = "Lacp warning: Uplink {1} on VDS {2} is blocked."
• vob.net.lacp.uplink.unblocked = "Lacp info: Uplink {1} on VDS {2} is unblocked."
• vob.net.lacp.uplink.disconnected = "Lacp warning: Uplink {1} on VDS {2} got disconnected."
• vob.net.lacp.uplink.connected = "Lacp info: Uplink {1} on VDS {2} got connected."

Environment

VMware vSphere ESXi 5.1

Resolution

For each vob message you see, the solution is listed below:

• vob.net.lacp.disable = "LACP for VDS {1} is disabled." - Check the following vob messages for this action if you have not explicitly disabled the LACP:
  • vob.net.lacp.policy.incompatible - Check to see if any of the distributed port groups have the teaming policy set to anything other than IP hash.
  • vob.net.lacp.uplink.inactive - Check to see if any of the uplinks are in other lists than active.
  • vob.net.lacp.uplink.fail.speed - Check the local speed setting on the uplink as well as the peer switch.
  • vob.net.lacp.uplink.fail.duplex - Check to see if the local duplex setting as well as peer switch setting is full duplex.
  • vob.net.lacp.peer.noresponse - Check to see why the peer is not responding.

There is no actions to take for the following vobs as they are for information purposes:

• vob.net.lacp.uplink.transition.down
• vob.net.lacp.uplink.transition.up
• vob.net.lacp.uplink.blocked
• vob.net.lacp.uplink.unblocked
• vob.net.lacp.uplink.disconnected
• vob.net.lacp.uplink.connected