CISCO-ZS-EXT-MIB
AI MIB Summary
The CISCO-ZS-EXT-MIB manages Fibre Channel zoning configurations for Cisco Zoning Servers supporting FC-GS4/SW3 standards, specifically tracking active configuration sessions, copy versus effective database states, and commit/clear operations within a VSAN. This module enforces single-session concurrency across the fabric to ensure atomic updates to the zone server's effective database before propagating changes to all connected devices.
The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the FC-GS4/SW3 requirements for Zone Server. This MIB is an extension to the CISCO-ZS-MIB, which is for managing zoning conforming to FC-GS3/SW2. The FC-GS4 specification is Fibre-Channel - Generic Services - 4 T11/ Project 1505-D/Rev 7.8. The SW3 specification is Fibre-Channel - Switch Fabric - 3 T11/Project 1508- D/Rev 6.6.
GS4/SW3 allows zoning to operate in either basic or enhanced mode of operation. Basic mode is essentially GS3/SW2 compatible mode (as modelled by CISCO-ZS-MIB). Enhanced mode of operation provides additional capabilities. In enhanced mode of operation, all the configuration should be done within the scope of a session.
The current 'Running Configuration' on the local device for zone server is called the 'effective' database. When the first configuration command on the zone server data is received, a snapshot of the current 'effective database' is taken on the local device. This snapshot is called the 'copy' database. An implicit session is started by the Zone Server on the local device and all subsequent SET operations take place in the context of this session. The 'copy' database is used for all further modifications in the session. There can be only one session active in the entire Fibre Channel fabric. The user who initiates the creation of this 'copy', is called the owner of session. When a session has been created on a device in the Fibre Channel fabric, if an attempt is made to start a session from any other device in the fabric, it results in error.
Once the modifications to the 'copy' are done, a 'commit' operation can be done. The 'commit' done on the local device, results in the local 'effective database' being overwritten with the 'copy' and then the new local 'effective database' is distributed to all other devices in the Fibre Channel fabric. The successful 'commit' operation also results in destroying the 'copy' on the local device. The 'commit' can only be performed by the owner of the session.
The 'copy' can optionally be destroyed without any distribution. This can be done by performing a 'clear' operation.
Glossary of terms used in this MIB
VSAN - Virtual Storage Area Network.
Main OID:
ciscoZsExtMIB.1.3.6.1.4.1.9.9.427
27
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
ciscoZsExtMIBThe MIB module for the management of zoning within
the framework of Cisco's Zoning Server (ZS) Archi-
tecture which realizes the FC-GS4/SW3 requirements
for Zone Server. This MIB is an extension to the
CISCO-ZS-MIB, which is for managing zoning
conforming to FC-GS3/SW2. The FC-GS4 specification
is Fibre-Channel - Generic Services - 4 T11/
Project 1505-D/Rev 7.8. The SW3 specification is
Fibre-Channel - Switch Fabric - 3 T11/Project 1508-
D/Rev 6.6.
GS4/SW3 allows zoning to operate in either basic
or enhanced mode of operation. Basic mode is
essentially GS3/SW2 compatible mode (as modelled
by CISCO-ZS-MIB). Enhanced mode of operation
provides additional capabilities. In enhanced mode
of operation, all the configuration should be
done within the scope of a session.
The current 'Running Configuration' on the local device
for zone server is called the 'effective' database.
When the first configuration command on the zone server
data is received, a snapshot of the current 'effective
database' is taken on the local device. This
snapshot is called the 'copy' database. An implicit
session is started by the Zone Server on the local
device and all subsequent SET operations take place
in the context of this session. The 'copy' database
is used for all further modifications in the
session. There can be only one session active in the
entire Fibre Channel fabric. The user who initiates
the creation of this 'copy', is called the owner of
session. When a session has been created on a device
in the Fibre Channel fabric, if an attempt is made
to start a session from any other device in the
fabric, it results in error.
Once the modifications to the 'copy' are done, a
'commit' operation can be done. The 'commit' done
on the local device, results in the local 'effective
database' being overwritten with the 'copy' and
then the new local 'effective database' is
distributed to all other devices in the Fibre Channel
fabric. The successful 'commit' operation also results
in destroying the 'copy' on the local device. The
'commit' can only be performed by the owner of the
session.
The 'copy' can optionally be destroyed without any
distribution. This can be done by performing a
'clear' operation.
Glossary of terms used in this MIB
VSAN - Virtual Storage Area Network. MODULE-IDENTITY .1.3.6.1.4.1.9.9.427 |
ciscoZsExtMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.0 |
ciscoZsExtMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.1 |
czseConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.1.1 |
czseCapabilityTableThis table lists the capabilities of the
Zone Server on the local device. This
information is maintained on a per VSAN
basis. SEQUENCE OF CzseCapabilityEntry .1.3.6.1.4.1.9.9.427.1.1.1 |
czseCapabilityEntryAn entry represents the capability of the
Zone Server on the local device on a VSAN. CzseCapabilityEntry .1.3.6.1.4.1.9.9.427.1.1.1.1 |
czseCapabilityObjectThis bitmap represents the capability of the
local Zone Server on this VSAN.
If 'enhancedMode(0)' bit is set, the local
Zone Server is capable of supporting enhanced
Zoning mode of operation. If this bit is reset,
it does not have this capability.
If 'zsetDb(1)' bit is set, the local Zone Server
supports maintaining of zoneset database. If this
bit is reset, the local Zone Server does not
allow maintaining of zoneset database.
If 'dirAct(2)' bit is set, the local Zone Server
supports direct activation command. If this bit
is reset, the local Zone Server does not support
this.
If 'hardZoning(3)' bit is set, the local Zone
Server supports hard zoning. If this bit is reset,
the local Zone Server does not support hard
zoning.ro Bits .1.3.6.1.4.1.9.9.427.1.1.1.1.1 |
czseModeTableA table containing information on the
mode of operation of the zone server on
all VSANs on the local device. SEQUENCE OF CzseModeEntry .1.3.6.1.4.1.9.9.427.1.1.2 |
czseModeEntryAn entry represents the mode of operation
of the local zone server on a VSAN. The mode
can be modified on a VSAN and the outcome
of the operation obtained. CzseModeEntry .1.3.6.1.4.1.9.9.427.1.1.2.1 |
czseOperationModeThis object when set to 'basic(1)', results in
the zone server operating in the basic mode
as defined by FC-GS4 standards.
This object when set to 'enhanced(2)', results in
the zone server operating in the enhanced mode
as defined by FC-GS4 standards.
The local zone server can move to the enhanced
mode of operation only if all devices in the
Fibre Channel fabric are capable of working in
enhanced mode.
Otherwise, the set operation trying to set this
object to 'enhanced(2)' will fail.rw Enumeration .1.3.6.1.4.1.9.9.427.1.1.2.1.1 |
czseOperationModeResultThe outcome of setting the mode of operation of
the local Zone Server on this VSAN.ro Enumeration .1.3.6.1.4.1.9.9.427.1.1.2.1.2 |
czseReadFromThis object specifies whether the management station
wishes to read from the 'effective database' or from
the 'copy' database.rw Enumeration .1.3.6.1.4.1.9.9.427.1.1.3 |
czseSessionTableA table containing information on sessions on
the local device on all VSANs. Operations are
permitted on this table only when the zone server
is running in 'enhanced' mode. SEQUENCE OF CzseSessionEntry .1.3.6.1.4.1.9.9.427.1.1.4 |
czseSessionEntryAn entry contains information on the owner of
a session on a VSAN. It also assists in performing
commit/clear operations on the session. CzseSessionEntry .1.3.6.1.4.1.9.9.427.1.1.4.1 |
czseSessionOwnerTypeThis object specifies the owner type
for this session.ro CzseSessOwnerType .1.3.6.1.4.1.9.9.427.1.1.4.1.1 |
czseSessionOwnerThis object specifies the owner for this
session.
If the value of the corresponding instance
of czseSessionOwnerType object is 'cli', this
object will contain the user name of the CLI
(Command Line Interface) user, who is the
owner of the session on this VSAN.
If the value of the corresponding instance
of czseSessionOwnerType is 'gs4client', this
object will contain the FCID of the GS4
management station, which is the owner of the
session on this VSAN.
If the value of the corresponding instance
of czseSessionOwnerType is 'snmp', this object
will contain the IP address of the management
station, which is the owner of the session on
this VSAN.ro OCTET STRING .1.3.6.1.4.1.9.9.427.1.1.4.1.2 |
czseSessionCntlThis object assists in committing or clearing
the contents of the 'copy' database on this
session.
No action is taken if this object is set to
'noop(3)'.
The value of this object when read is always
'noop(3)'.
The above operation can only be performed by
the owner of the session.rw Enumeration .1.3.6.1.4.1.9.9.427.1.1.4.1.3 |
czseSessionCntlResultThis object indicates the outcome of setting
the corresponding instance of czseSessionCntl
object to 'commitChanges(1)'.ro Enumeration .1.3.6.1.4.1.9.9.427.1.1.4.1.4 |
czseMergeControlTableA table containing information on zone
merge control policy on all VSANs in the
entire fabric. Operations on this table
are permitted only when the zone server
is running in 'enhanced' mode. SEQUENCE OF CzseMergeControlEntry .1.3.6.1.4.1.9.9.427.1.1.5 |
czseMergeControlEntryAn entry contains information on the
Merge Control policy on a VSAN. The policy
can be modified on a per VSAN basis by
making use of czseMergeContolRestrict object. CzseMergeControlEntry .1.3.6.1.4.1.9.9.427.1.1.5.1 |
czseMergeControlRestrictThis object controls the zone merge behavior.
If this object is set to 'allow', then the merge
takes place according to the merge rules.
If this object is set to 'restrict', then if the
merging databases are not exactly identical, the
Inter-Switch Link (ISL) between the devices is
isolated.rw Enumeration .1.3.6.1.4.1.9.9.427.1.1.5.1.1 |
czseGlobalDefaultZoneBehaviourThis object represents the initial
value for default zone behaviour
on a VSAN when it is created.
If a VSAN were to be deleted and
re-created again, the default zone
behaviour will be set to the value
specified for this object.
The semantics of setting this object
to 'permit' or 'deny' are described
in the description for
zoneDefaultZoneBehaviour object in
CISCO-ZS-MIB.
After a VSAN has been created, if
the value for default zone behaviour
for that VSAN has to be changed, the
zoneDefaultZoneBehaviour object in
CISCO-ZS-MIB has to be used.rw Enumeration .1.3.6.1.4.1.9.9.427.1.1.6 |
czseGlobalPropagationModeThis object represents the initial
value for zone set propagation mode
on a VSAN when it is created.
If a VSAN were to be deleted and
re-created again, the zone set
propagation mode will be set to the
value specified for this object.
The semantics of setting this object
to 'fullZoneset' or 'activeZoneset'
are described in the description for
zoneSetPropagationMode object in
CISCO-ZS-MIB.
After a VSAN has been created, if
the value for zone set propagation
mode has to be changed for that
particular VSAN, the
zoneSetPropagationMode object
in CISCO-ZS-MIB has to be used.rw Enumeration .1.3.6.1.4.1.9.9.427.1.1.7 |
czseStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.1.2 |
ciscoZsExtMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.2 |
ciscoZsExtMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.2.1 |
ciscoZsExtMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.427.2.2 |