- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Generally, both in my experience and those of other experts over the years with whom I've consulted, the demand for using LAG/LACP is usually the following (ranked in order of most prevalent to least):
- Customer doesn't know how vSphere works and what features it has with networking.
- Ignorance that LAG/LACP is the only method to ensure concurrent link utilization and fail-over capabilities (linked with #1).
- Networking team thinks vSphere/ESXi is just like every other physical server / don't want to learn new features.
- Company standardization on LAG/LACP based on pre-virtualization technology.
- Existing vendor infrastructure/solution requires it (rare; archaic today)
Either #1-3 above is likely to be the reason for the mandate for LAG/LACP if it's coming from the networking team.