OID reference

zoneCompactTable

1.3.6.1.4.1.9.9.294.1.1.40

Description

The zoneSetZoneList object and the zoneSetZoneListTable allow upto 8192 zones to be associated with a zoneset. This is done with the help of 4 bitmaps each of which represent 2048 zones. There may exist a situation where the 'lowest' bitmap may not be fully populated but 'higher' bitmaps may have bits set in them. Sem…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.9.9.294.1.1 (zoneConfiguration)
Node code
40
Node name
zoneCompactTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.9.9.294.1.1.40
URN notation
urn:oid:1.3.6.1.4.1.9.9.294.1.1.40
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 9 9 294 1 1 40}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoZsMIB(294) ciscoZoningMIBObjects(1) zoneConfiguration(1) zoneCompactTable(40)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/294/1/1/40
  • /ISO/Identified-Organization/6/1/4/1/9/9/294/1/1/40
  • /ISO/3/6/1/4/1/9/9/294/1/1/40
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoZsMIB/ciscoZoningMIBObjects/zoneConfiguration/zoneCompactTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF ZoneCompactEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — Cisco, Cisco MIB copies (LibreNMS/Observium Community), and others

Value type
SEQUENCE OF ZoneCompactEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Variant 2 — Cisco SMIv1

Value type
SEQUENCE OF ZoneCompactEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

zoneCompactTable OBJECT-TYPE
    SYNTAX          SEQUENCE OF ZoneCompactEntry 
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "The zoneSetZoneList object and the
        zoneSetZoneListTable allow upto 16384
        zones to be associated with a zoneset.
        This is done with the help of 8 bitmaps
        each of which represent 2048 zones. There
        may exist a situation where the 'lowest'
        bitmap may not be fully populated but
        'higher' bitmaps may have bits set in them.
        Semantically what this means is: the lowest
        8192 zones have not been fully associated,
        but zones with higher ids have been
        associated. This kind of a situation causes
        problems for management stations which are
        only aware of older versions of this MIB. They
        are only aware of zoneSetZoneList object and
        hence only the 'lowest' 8192 zones that are
        associated with a zoneset. In the above
        situation, the total number of zones
        associated with the zoneset could be less
        than 8192. But by virtue of being distributed
        in the 'higher' bitmaps, those zones will
        not be seen by those management stations as
        they are not aware of the new objects in
        zoneSetZoneListTable. In such a situation,
        a management station which is aware of this
        version of the MIB, can choose to compact
        the zones associated with zonesets on a 
        VSAN, so that the holes in the lowest 8192
        zones are filled.

        Note that this table facilitates compaction
        of only the first 8192 zones and not zones
        belonging to 'higher' bitmaps."
    ::= { zoneConfiguration 40 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

The zoneSetZoneList object and the
zoneSetZoneListTable allow upto 8192
zones to be associated with a zoneset.
This is done with the help of 4 bitmaps
each of which represent 2048 zones. There
may exist a situation where the 'lowest'
bitmap may not be fully populated but
'higher' bitmaps may have bits set in them.
Semantically what this means is: the lowest
2048 zones have not been fully associated,
but zones with higher ids have been
associated. This kind of a situation causes
problems for management stations which are
only aware of older versions of this MIB. They
are only aware of zoneSetZoneList object and
hence only the 'lowest' 2048 zones that are
associated with a zoneset. In the above
situation, the total number of zones
associated with the zoneset could be less
than 2048. But by virtue of being distributed
in the 'higher' bitmaps, those zones will
not be seen by those management stations as
they are not aware of the new objects in
zoneSetZoneListTable. In such a situation,
a management station which is aware of this
version of the MIB, can choose to compact
the zones associated with zonesets on a
VSAN, so that the holes in the lowest 2048
zones are filled.

Note that this table facilitates compaction
of only the first 2048 zones and not zones
belonging to 'higher' bitmaps.
Sources for this description

Circitor

Parsed from CISCO-ZS-MIB.mib · CISCO-ZS-MIB

Source file: Download CISCO-ZS-MIB.mib

Browse all files from Circitor

Cisco

Cisco SMIv1

Source file: Download CISCO-ZS-MIB-V1SMI.my · Publisher's file

Source file: Download CISCO-ZS-MIB-V1SMI.my.txt

Browse all files from Cisco SMIv1

MIBdepot

Source file: Download CISCO-ZS-MIB.my.txt

Browse all files from MIBdepot

Description 2

The zoneSetZoneList object and the zoneSetZoneListTable allow upto 16384 zones to be associated with a zoneset. This is done with the help of 8 bitmaps each of which represent 2048 zones. There may exist a situation where the 'lowest' bitmap may not be fully populated but 'higher' bitmaps may have bits set in them. Semantically what this means is: the lowest 8192 zones have not been fully associated, but zones with higher ids have been associated. This kind of a situation causes problems for management stations which are only aware of older versions of this MIB. They are only aware of zoneSetZoneList object and hence only the 'lowest' 8192 zones that are associated with a zoneset. In the above situation, the total number of zones associated with the zoneset could be less than 8192. But by virtue of being distributed in the 'higher' bitmaps, those zones will not be seen by those management stations as they are not aware of the new objects in zoneSetZoneListTable. In such a situation, a management station which is aware of this version of the MIB, can choose to compact the zones associated with zonesets on a VSAN, so that the holes in the lowest 8192 zones are filled. Note that this table facilitates compaction of only the first 8192 zones and not zones belonging to 'higher' bitmaps.

Sources for this description

CiscoCisco MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 2Cisco, Cisco MIB copies (LibreNMS/Observium Community), and others1 record · 3 sources

Description 2

zoneCompactTable · currentCisco, Cisco MIB copies (LibreNMS/Observium Community), and others3 sources

Status in source: current.

Names: zoneCompactTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zoneCompactTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "ZoneCompactEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The zoneSetZoneList object and the zoneSetZoneListTable allow upto 16384 zones to be associated with a zoneset. This is done with the help of 8 bitmaps each of which represent 2048 zones. There may exist a situation where the 'lowest' bitmap may not be fully populated but 'higher' bitmaps may have bits set in them. Semantically what this means is: the lowest 8192 zones have not been fully associated, but zones with higher ids have been associated. This kind of a situation causes problems for management stations which are only aware of older versions of this MIB. They are only aware of zoneSetZoneList object and hence only the 'lowest' 8192 zones that are associated with a zoneset. In the above situation, the total number of zones associated with the zoneset could be less than 8192. But by virtue of being distributed in the 'higher' bitmaps, those zones will not be seen by those management stations as they are not aware of the new objects in zoneSetZoneListTable. In such a situation, a management station which is aware of this version of the MIB, can choose to compact the zones associated with zonesets on a VSAN, so that the holes in the lowest 8192 zones are filled. Note that this table facilitates compaction of only the first 8192 zones and not zones belonging to 'higher' bitmaps.\"",
    "::=",
    "{",
    "zoneConfiguration",
    "40",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "ZoneCompactEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The zoneSetZoneList object and the zoneSetZoneListTable allow upto 16384 zones to be associated with a zoneset. This is done with the help of 8 bitmaps each of which represent 2048 zones. There may exist a situation where the 'lowest' bitmap may not be fully populated but 'higher' bitmaps may have bits set in them. Semantically what this means is: the lowest 8192 zones have not been fully associated, but zones with higher ids have been associated. This kind of a situation causes problems for management stations which are only aware of older versions of this MIB. They are only aware of zoneSetZoneList object and hence only the 'lowest' 8192 zones that are associated with a zoneset. In the above situation, the total number of zones associated with the zoneset could be less than 8192. But by virtue of being distributed in the 'higher' bitmaps, those zones will not be seen by those management stations as they are not aware of the new objects in zoneSetZoneListTable. In such a situation, a management station which is aware of this version of the MIB, can choose to compact the zones associated with zonesets on a VSAN, so that the holes in the lowest 8192 zones are filled. Note that this table facilitates compaction of only the first 8192 zones and not zones belonging to 'higher' bitmaps."
    ],
    null,
    null,
    null,
    null
  ]
}

Historical records

Additional source information

Information from Circitor 
zoneCompactTable OBJECT-TYPE
        SYNTAX        SEQUENCE OF ZoneCompactEntry
        MAX-ACCESS    not-accessible
        STATUS        current
        DESCRIPTION
                "The zoneSetZoneList object and the
                 zoneSetZoneListTable allow upto 8192
                 zones to be associated with a zoneset.
                 This is done with the help of 4 bitmaps
                 each of which represent 2048 zones. There
                 may exist a situation where the 'lowest'
                 bitmap may not be fully populated but
                 'higher' bitmaps may have bits set in them.
                 Semantically what this means is: the lowest
                 2048 zones have not been fully associated,
                 but zones with higher ids have been
                 associated. This kind of a situation causes
                 problems for management stations which are
                 only aware of older versions of this MIB. They
                 are only aware of zoneSetZoneList object and
                 hence only the 'lowest' 2048 zones that are
                 associated with a zoneset. In the above
                 situation, the total number of zones
                 associated with the zoneset could be less
                 than 2048. But by virtue of being distributed
                 in the 'higher' bitmaps, those zones will
                 not be seen by those management stations as
                 they are not aware of the new objects in
                 zoneSetZoneListTable. In such a situation,
                 a management station which is aware of this
                 version of the MIB, can choose to compact
                 the zones associated with zonesets on a 
                 VSAN, so that the holes in the lowest 2048
                 zones are filled.

                 Note that this table facilitates compaction
                 of only the first 2048 zones and not zones
                 belonging to 'higher' bitmaps."
        ::= { zoneConfiguration 40 }
Information from Cisco SMIv1 
zoneCompactTable OBJECT-TYPE
    SYNTAX SEQUENCE OF ZoneCompactEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "The zoneSetZoneList object and the
         zoneSetZoneListTable allow upto 8192
         zones to be associated with a zoneset.
         This is done with the help of 4 bitmaps
         each of which represent 2048 zones. There
         may exist a situation where the 'lowest'
         bitmap may not be fully populated but
         'higher' bitmaps may have bits set in them.
         Semantically what this means is: the lowest
         2048 zones have not been fully associated,
         but zones with higher ids have been
         associated. This kind of a situation causes
         problems for management stations which are
         only aware of older versions of this MIB. They
         are only aware of zoneSetZoneList object and
         hence only the 'lowest' 2048 zones that are
         associated with a zoneset. In the above
         situation, the total number of zones
         associated with the zoneset could be less
         than 2048. But by virtue of being distributed
         in the 'higher' bitmaps, those zones will
         not be seen by those management stations as
         they are not aware of the new objects in
         zoneSetZoneListTable. In such a situation,
         a management station which is aware of this
         version of the MIB, can choose to compact
         the zones associated with zonesets on a 
         VSAN, so that the holes in the lowest 2048
         zones are filled.
        
         Note that this table facilitates compaction
         of only the first 2048 zones and not zones
         belonging to 'higher' bitmaps."
    ::= { zoneConfiguration 40 }
Information from OID Repository
Vendor: Cisco
Module: CISCO-ZS-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot 
zoneCompactTable OBJECT-TYPE
        SYNTAX        SEQUENCE OF ZoneCompactEntry
        MAX-ACCESS    not-accessible
        STATUS        current
        DESCRIPTION
                "The zoneSetZoneList object and the
                 zoneSetZoneListTable allow upto 8192
                 zones to be associated with a zoneset.
                 This is done with the help of 4 bitmaps
                 each of which represent 2048 zones. There
                 may exist a situation where the 'lowest'
                 bitmap may not be fully populated but
                 'higher' bitmaps may have bits set in them.
                 Semantically what this means is: the lowest
                 2048 zones have not been fully associated,
                 but zones with higher ids have been
                 associated. This kind of a situation causes
                 problems for management stations which are
                 only aware of older versions of this MIB. They
                 are only aware of zoneSetZoneList object and
                 hence only the 'lowest' 2048 zones that are
                 associated with a zoneset. In the above
                 situation, the total number of zones
                 associated with the zoneset could be less
                 than 2048. But by virtue of being distributed
                 in the 'higher' bitmaps, those zones will
                 not be seen by those management stations as
                 they are not aware of the new objects in
                 zoneSetZoneListTable. In such a situation,
                 a management station which is aware of this
                 version of the MIB, can choose to compact
                 the zones associated with zonesets on a 
                 VSAN, so that the holes in the lowest 2048
                 zones are filled.

                 Note that this table facilitates compaction
                 of only the first 2048 zones and not zones
                 belonging to 'higher' bitmaps."
        ::= { zoneConfiguration 40 }
Information from Cisco 
zoneCompactTable OBJECT-TYPE
        SYNTAX        SEQUENCE OF ZoneCompactEntry
        MAX-ACCESS    not-accessible
        STATUS        current
        DESCRIPTION
                "The zoneSetZoneList object and the
                 zoneSetZoneListTable allow upto 8192
                 zones to be associated with a zoneset.
                 This is done with the help of 4 bitmaps
                 each of which represent 2048 zones. There
                 may exist a situation where the 'lowest'
                 bitmap may not be fully populated but
                 'higher' bitmaps may have bits set in them.
                 Semantically what this means is: the lowest
                 2048 zones have not been fully associated,
                 but zones with higher ids have been
                 associated. This kind of a situation causes
                 problems for management stations which are
                 only aware of older versions of this MIB. They
                 are only aware of zoneSetZoneList object and
                 hence only the 'lowest' 2048 zones that are
                 associated with a zoneset. In the above
                 situation, the total number of zones
                 associated with the zoneset could be less
                 than 2048. But by virtue of being distributed
                 in the 'higher' bitmaps, those zones will
                 not be seen by those management stations as
                 they are not aware of the new objects in
                 zoneSetZoneListTable. In such a situation,
                 a management station which is aware of this
                 version of the MIB, can choose to compact
                 the zones associated with zonesets on a 
                 VSAN, so that the holes in the lowest 2048
                 zones are filled.

                 Note that this table facilitates compaction
                 of only the first 2048 zones and not zones
                 belonging to 'higher' bitmaps."
        ::= { zoneConfiguration 40 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.294.1.1.40.1 zoneCompactEntry22 An entry allows compaction to be carried
out on a VSAN.

Siblings (43)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.294.1.1.1 zoneDefaultZoneTable16 A table containing information on all
default zones on all VSANs on the local
Zone Server.
1.3.6.1.4.1.9.9.294.1.1.2 zoneSetPropagationTable12 A table containing information related to
propagation of zone set information during
Merge/Change protocols on all VSANs on the
lo…
1.3.6.1.4.1.9.9.294.1.1.3 zoneSetNumber11 The number of entries currently present in the
zoneSetTable.
1.3.6.1.4.1.9.9.294.1.1.4 zoneSetTable17 A table containing information on each Zone
Set which is configured and available on
any VSAN known to the local Zone Server.
The …
1.3.6.1.4.1.9.9.294.1.1.5 zoneSetActivateTable17 This table contains atmost one entry for
each VSAN that is configured. These entries
reflect the state of the activation of a
zone…
1.3.6.1.4.1.9.9.294.1.1.6 zoneNumber11 The number of entries currently present in the
zoneTable.
1.3.6.1.4.1.9.9.294.1.1.7 zoneTable113 This table gives information on all the
zones/aliases and lists all their members.
1.3.6.1.4.1.9.9.294.1.1.8 zoneAliasNumber11 The number of entries currently present in the
zoneAliasTable.
1.3.6.1.4.1.9.9.294.1.1.9 zoneAliasTable17 This table gives information on all the aliases and
their members.
1.3.6.1.4.1.9.9.294.1.1.10 zoneMemberNumber11 The number of entries currently present in the
zoneMemberTable.
1.3.6.1.4.1.9.9.294.1.1.11 zoneMemberTable19 This table contains all members of a zone/alias
and information about those members.
1.3.6.1.4.1.9.9.294.1.1.12 zoneEnforcedZoneSetNumber11 The number of entries currently present in the
zoneEnforcedZoneSetTable.
1.3.6.1.4.1.9.9.294.1.1.13 zoneEnforcedZoneSetTable14 A table containing information on all currently
enforced zone sets (active zone sets) on all VSANs.
Only one zone set can be acti…
1.3.6.1.4.1.9.9.294.1.1.14 zoneEnforcedZoneNumber11 The number of entries currently present in the
zoneEnforcedZoneTable.
1.3.6.1.4.1.9.9.294.1.1.15 zoneEnforcedZoneTable110 This table contains all the zones/aliases that are
present in the active zone sets on all VSANs.
1.3.6.1.4.1.9.9.294.1.1.16 zoneEnforcedZoneAliasNumber11 The number of entries currently present in the
zoneEnforcedZoneAliasTable.
1.3.6.1.4.1.9.9.294.1.1.17 zoneEnforcedZoneAliasTable13 This table contains all the aliases that
are a part of active zone sets on all VSANs.
1.3.6.1.4.1.9.9.294.1.1.18 zoneEnforcedZoneMemberNumber11 The number of entries currently present in the
zoneEnforcedZoneMemberTable.
1.3.6.1.4.1.9.9.294.1.1.19 zoneEnforcedZoneMemberTable15 This table contains all members that are part
of a zone/alias and are part of the active zone
sets on all VSANs.
1.3.6.1.4.1.9.9.294.1.1.20 zoneMergeFailRecoverSpinLock11 This object is used to facilitate modification
of zoneMergeFailRecoverInterface,
zoneMergeFailRecoverVsan and
zoneMergeFailRecover…
1.3.6.1.4.1.9.9.294.1.1.21 zoneMergeFailRecoverInterface11 The interface on which the Merge Failure Recovery
needs to be carried out. The value of this object
before the first set operatio…
1.3.6.1.4.1.9.9.294.1.1.22 zoneMergeFailRecoverVsan11 The VSAN on which the Merge Failure Recovery
needs to be carried out.
1.3.6.1.4.1.9.9.294.1.1.23 zoneMergeFailRecoverOper11 The operation to be carried out.

If this object is set to 'import', then the
Active Zone Set from across the isolated link
is impo…
1.3.6.1.4.1.9.9.294.1.1.24 zoneMergeFailRecoverResult11 The result of the last Merge Failure Recovery
operation that was attempted.

If the value of this object is 'success', then
the mer…
1.3.6.1.4.1.9.9.294.1.1.25 zoneCopyActiveToFullOnVsan11 The VSAN on which the enforced zone set
(active zone set) needs to be copied to the
zone set database (full zone set). Setting
thi…
1.3.6.1.4.1.9.9.294.1.1.26 zoneServiceReqRejNotifyEnable11 This object specifies if the Zone Server should
issue a 'zoneServiceReqRejNotify' notification.

If the value of this object is 't…
1.3.6.1.4.1.9.9.294.1.1.27 zoneMergeFailureNotifyEnable11 This object specifies if the zone server should
issue a zoneMergeFailureNotify notification.

If the value of this object is 'true…
1.3.6.1.4.1.9.9.294.1.1.28 zoneMergeSuccessNotifyEnable11 This object specifies if the zone server should
issue a zoneMergeSuccessNotify notification.

If the value of this object is 'true…
1.3.6.1.4.1.9.9.294.1.1.29 zoneDefZoneBehvrChngNotifyEnable11 This object specifies if the zone server should
issue a zoneDefZoneBehaviourChngNotify
notification.

If the value of this object i…
1.3.6.1.4.1.9.9.294.1.1.30 zoneDbTable14 This table contains one entry for each VSAN
that is configured. These entries provide the
capability to perform operations on the…
1.3.6.1.4.1.9.9.294.1.1.31 zoneCopyTable111 In this table, for each VSAN that is configured,
atmost one entry can be created. These entries
provide the capability to copy th…
1.3.6.1.4.1.9.9.294.1.1.32 zoneUnsuppMemInIntOpNotifyEnable11 This object specifies if the zone server should
issue a zoneUnsuppMemInIntOpModeNotify
notification.

If the value of this object i…
1.3.6.1.4.1.9.9.294.1.1.33 zoneVsanId11 This object represents the VSAN id on which a
mismatch between the operating mode of the local
switch and the type of zone member…
1.3.6.1.4.1.9.9.294.1.1.34 zoneZoneSetDistributeVsan11 This object represents the VSAN on which the
full zoneset information needs to be
distributed throughout the fabric. Setting this
…
1.3.6.1.4.1.9.9.294.1.1.35 zoneZoneSetDistributeResult11 The outcome of the full zoneset distribute
operation on the VSAN indicated by
zoneZoneSetDistributeVsan object.
1.3.6.1.4.1.9.9.294.1.1.36 zoneZoneSetDistributeFailReason11 If the outcome of distributing the full
zoneset on a VSAN is failure, then this
object will contain the reason for the
failure. In…
1.3.6.1.4.1.9.9.294.1.1.37 zoneSwitchWwn11 This object represents the WWN of the
local device. It is used in the
notification zoneActivateNotify.
1.3.6.1.4.1.9.9.294.1.1.38 zoneSetZoneListTable18 This table is an extension to the
zoneSetTable defined above.
The object zoneSetZoneList in zoneSetTable
represents the set of zon…
1.3.6.1.4.1.9.9.294.1.1.39 zoneSetEnforcedZoneListTable18 This table is an extension to the
zoneEnforcedZoneSetTable defined above.
The object zoneEnforcedZoneSetZoneList in
zoneEnforcedZo…
1.3.6.1.4.1.9.9.294.1.1.41 zoneCompactVsan11 This object represents the VSAN on which
a successful zone compaction has taken place.
It is used in the notification
zoneCompactN…
1.3.6.1.4.1.9.9.294.1.1.42 zoneCopyActToFullSpinLock11 This object is used to facilitate modification
of zoneCopyActToFullMode and zoneCopyActToFullOnVsan
by multiple managers.
The proc…
1.3.6.1.4.1.9.9.294.1.1.43 zoneCopyActToFullMode11 Setting this object to 'includeAutoZones', results
in certain internal zones created by Zone Server being
copied along with the e…
1.3.6.1.4.1.9.9.294.1.1.44 zoneCopyActToFullVsan11 The VSAN on which the enforced zone set
(active zone set) needs to be copied to the
zone set database (full zone set). Setting
thi…