CISCO-ZS-MIB Table View

A table containing information on all
default zones on all VSANs on the local
Zone Server.

A table containing information related to
propagation of zone set information during
Merge/Change protocols on all VSANs on the
local Zone Server.

A table containing information on each Zone
Set which is configured and available on
any VSAN known to the local Zone Server.
The zoneSetTable lists all the zone sets 
configured on all the VSANs configured on the 
local zone server. There could be multiple zone 
sets configured on a VSAN. But only one zone set 
is allowed to be active at a time in each VSAN. A 
Zone Set is a collection of zones.

This table contains atmost one entry for
each VSAN that is configured. These entries
reflect the state of the activation of a 
zone set on the corresponding VSAN.
          
The management station needs to create an
entry in this table on the desired VSAN before
a zone set can be activated on that VSAN.

This table gives information on all the
zones/aliases and lists all their members.

This table gives information on all the aliases and
their members.

This table contains all members of a zone/alias
and information about those members.

A table containing information on all currently
enforced zone sets (active zone sets) on all VSANs.
Only one zone set can be activated per VSAN. The
active zone set is one which is copied from the
zone set database (zoneSetTable) at the time it
was activated. This active zone set is then
enforced on the fabric. This active zone set
cannot be modified.                 
Note that this table will be empty when no zone set
is activated.

This table contains all the zones/aliases that are
present in the active zone sets on all VSANs.

This table contains all members that are part
of a zone/alias and are part of the active zone 
sets on all VSANs.

This table contains one entry for each VSAN
that is configured. These entries provide the
capability to perform operations on the local 
zone server database on a VSAN.

In this table, for each VSAN that is configured,
atmost one entry can be created. These entries 
provide the capability to copy the active zone set 
on a VSAN to a file on the local device and/or to
a remote device over the network.
At any point of time, only one copy operation
can be active for all the VSANs. If a second
copy is attempted, it will result in error.

This table is an extension to the
zoneSetTable defined above. 
The object zoneSetZoneList in zoneSetTable
represents the set of zones that form a 
zoneset. However, this object has the
limitation of being able to represent
only 2048 zones. This table which extends
the zoneSetTable overcomes this limitation
and the number of zones that form a 
zoneset is increased to 16384.

This table is an extension to the
zoneEnforcedZoneSetTable defined above. 
The object zoneEnforcedZoneSetZoneList in 
zoneEnforcedZoneSetTable represents the
set of enforced zones that form an
enforced zoneset. However, this object has the 
limitation of being able to represent
only 2048 zones. This table which extends
the zoneEnforcedZoneSetTable overcomes this 
limitation and the number of enforced zones that 
form an enforced zoneset is increased to
16384.

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.

This table contains statistic counters which are
maintained by the Zone Server. These counters are
maintained per VSAN.

This table contains statistic counters related to
LUNs. These counters are populated by the local 
Zone Server based on SCSI frames that are
forwarded to it because the LUNs being accessed 
have been zoned out from a initiator's list of 
accessible LUNs.
These counters are maintained per VSAN, per SCSI
initiator-target pair, per LUN.

This table contains statistic counter(s) related
to read-only zones which are maintained by the
Zone Server. These counters are maintained per
VSAN, per SCSI initiator target pair, per LUN.