| Constants |
| not-applicable |
0ull |
N/A |
NO COMMENTS
|
| san-boot-validation-failed |
16ull |
Vfc cannot be deployed both on the port channel and its member ports |
NO COMMENTS
|
| insufficient-resources |
1ull |
insufficient-resources |
overall there are not enough resources
|
| invalid-vsan |
2ull |
Invalid VSAN Configuration |
Invalid VSAN Configuration
The domain associated with the EPg is not allowed to use the specified encap. Check the Attachable Profile,
VsanAttrP and VSAN Namespace (fvns:VsanInstP) configurations associated with the domain.
|
| native-vsan-failure |
4ull |
Only One Native Vsan Allowed on Interface |
Native/Untagged Vsan Validation
You are trying to configure two different vsans as native on the path (i.e. port/port-channel).
Check the "mode" type set on the relations between the EPg and the fabric:Path.
|
| another-encap-for-bd-in-use |
8ull |
BD is assigned another encap |
Vsan Encap validation
If a vsan is already attached to BD, another vsan can not be attached.
|
| encap-already-in-use |
8ull |
Encap Already Used in Another EPG |
Vsan Encap validation
On a node, an encap (VSAN) can be used by only 1 EPg or BD at a time.
|
| DEFAULT |
not-applicable(0ull) |
N/A |
NO COMMENTS
|