ZoneMergeFailCause

  • Base type Enumeration

Specifies the reason for zone merge failure. When the Zone Merge takes place, the local database is compared with the database of the adjacent switch. The following errors/mismatches can take place: other - reason other than those specified below. zoningModeMismatch - mismatch in zoning modes between the 2 switches. qosNotEnabled - qos is not enabled on one of the switches and qos attribute is present in one of the zones. qosConflict - conflict between VSAN based Qos and zone attribute qos. bcastNotEnabled - broadcast service has not been enabled on one of the switches and broadcast attribute is present in one of the zones. mergeCtrlMismatch - there is a mismatch in the merge control flag value. defZoneMismatch - there is a mismatch in the default zone policy. qosAttrMissing - qos attribute is missing. bcastAttrMissing - broadcast attribute is missing. rdonlyAttrMissing - read only attribute is missing. memberMismatch - there is a mismatch in the members. invPayloadFormat - the payload format is invalid. sizeExceeded - the payload exceeded the maximum size. unlicensedMember - a member is unlicensed. nonInteropZoneset - a zone attribute/member which cannot be supported in the current interop mode of the switch.

Possible values

15 objects
Number Name
1 other
2 zoningModeMismatch
3 qosNotEnabled
4 qosConflict
5 bcastNotEnabled
6 mergeCtrlMismatch
7 defZoneMismatch
8 qosAttrMissing
9 bcastAttrMissing
10 rdonlyAttrMissing
11 memberMismatch
12 invPayloadFormat
13 sizeExceeded
14 unlicensedMember
15 nonInteropZoneset