Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
ONTAP Select docs (https://docs.netapp.com/us-en/ontap-select/concept_nw_vsphere_vswitch_config.html) states that for a deployment of a 2-node OTS cluster in 25GbE 2-port hosts.. we should use active-active NIC teaming:
But also, there's a table describing active/standby teaming:
So, I guess we should use active/standby and the above picture is wrong (active-active should be replaced by active-standy). Does it make sense?
Kind regards,
Pedro
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @pedro_rocha,
I understand that this can be confusing and I would agree that "Active-Active NIC teaming" is not the best wording, though it is still Active-Active.
Essentially both NICs on the ESXi host are active:
- vmnic0 is active for External 1 and Internal 1, but is standby for Internal 2 and External 2
- vmnic1 is active for Internal 2 and External 2, but is standby for External 1 and Internal 1.
There is not an active/active LAG/Bond/LACP group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
Problem is that it is possible to set the portgroup as active-active (without using LAG/Bond/LACP).
That drawing is misleading the reader as the table is pretty straightforward that the recommendation is active-standby.
For a given portgroup the configuration is active-standby. From the ESXi host perspective, all the NICs are active.