No document that I know of, but you pretty much nailed the 2 main points. These points apply to a VSAN...not the entire fabric as a whole. It is possible for some VSANs to merge okay across an TE-ISL, while other VSANs on the same TE-ISL end up isolated. Check the 'show interface fc x/y' display via the CLI once you bring up both sides.
- Unique Domain IDs
- Zone names must be unique...or if the zonename does exist on both sides, it must contain the exact same members
- Zone mode, either basic or enhanced, but be the same.
If would also be good to ensure that both sides have the same 'default zone' policy of permit or deny. This is seen on the CLI display 'show zone policy vsan x' display.
I believe that this also a tool in FM that lets you can use to perform a zone merge analysis. Check under Zone->Tools or Tools->Zone.
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...
RBAC users like email@example.com may fail HX Connect login. At that time, "Incorrect user name or password(100005)" is shown as a failure reason.
RBAC users can login to vCenter server. So, RBAC username and passwo...