| OID symbolic | OID numeric | Type | Access | Description |
|---|
| t11FabricLockMIB | 1.3.6.1.2.1.159 | | | The MIB module for the management of locks on a Fibre
Channel Fabric. A Fibre Channel Fabric lock is used to
ensure serialized access to some types of management data
related to a Fabric, e.g., the Fabric's Zoning Database.
Some (managing) applications generate Fabric locks by
initiating server sessions. Server sessions are
defined generically in FC-GS-5 to represent a collection of
one or more requests to the session's server, e.g., to the
Zone Server. Such a session is started by a Server Session
Begin (SSB) request, and terminated by a Server Session End
(SSE) request. The switch receiving the SSB is called the
'managing' switch. Some applications require the
'managing' switch to lock the Fabric for the particular
application, e.g., for Enhanced Zoning, before it can
respond successfully to the SSB. On receipt of the
subsequent SSE, the lock is released. For this usage, the
managing switch sends an Acquire Change Authorization (ACA)
request to other switches to lock the Fabric.
For some other applications, a managing switch locks the
Fabric using an Enhanced Acquire Change Authorization (EACA)
request, which identifies the application on whose behalf
the Fabric is being locked with an Application_ID.
Fabric locks can also be requested more directly, e.g.,
through the use of this MIB. In these situations, the term
'managing' switch is used to indicate the switch that
receives such a request and executes it by issuing either
ACA or EACA requests to other switches in the Fabric.
This MIB module defines information about the 'managing'
switch for currently-active Fabric locks.
Copyright (C) The IETF Trust (2007). This version
of this MIB module is part of RFC 4936; see the RFC
itself for full legal notices. |
| t11FLockMIBNotifications | 1.3.6.1.2.1.159.0 | | | |
| t11FLockMIBObjects | 1.3.6.1.2.1.159.1 | | | |
| t11FLockConfiguration | 1.3.6.1.2.1.159.1.1 | | | |
| t11FLockTable | 1.3.6.1.2.1.159.1.1.1 | | not-accessible | A table containing information about the 'managing'
switch of each current Fabric lock, e.g., for the
types of Servers defined in FC-GS-5.
Each entry in this table represents either:
1) a current Fabric lock,
2) an in-progress attempt, requested via SNMP, to set up
a lock, or
3) a failed attempt, requested via SNMP, to set up a lock.
If an entry is created via t11FLockRowStatus, but the
attempt to obtain the lock fails, then the entry continues
to exist until it is deleted via t11FLockRowStatus, or
it is overwritten by the lock being established via
a means other than SNMP. However, rows created via
t11FLockRowStatus are not retained over restarts. |
| t11FLockEntry | 1.3.6.1.2.1.159.1.1.1.1 | | not-accessible | Each entry contains information specific to a current
Fabric lock set up by a particular 'managing' switch on a
particular Fabric. The 'managing switch' is identified by
values of fcmInstanceIndex and fcmSwitchIndex.
Server sessions for several different types of servers
are defined in FC-GS-5. The behavior of a server with
respect to commands received within a server session is
specified for each type of server. For some types,
parameter changes can only be made within the context of a
session, and the setting up of a session requires that the
Fabric be locked. A Fabric is locked by one switch, called
the 'managing' switch, sending Acquire Change Authorization
(ACA) requests to all other switches in the Fabric.
For other applications, a Fabric lock is established by the
'managing' switch sending Enhanced Acquire Change
Authorization (EACA) requests to other switches in the
Fabric. Each EACA request includes an Application_ID
value to identify the application requesting the lock.
For the benefit of this MIB module, a distinct value of
Application_ID has also been assigned/reserved (see
ANSI INCITS T11/06-679v0, titled 'FC-SW-5 Letter to
T11.5') as a means of distinguishing locks established via
Acquire Change Authorization (ACA) requests. This
additional assignment allows an Application_ID to be used to
uniquely identify any active lock amongst all those
established by either an EACA or an ACA.
Whenever a Fabric is locked, by the sending of either an ACA
or an EACA, a row gets created in the representation of this
table for the 'managing' switch.
In order to process SNMP SetRequests that make parameter
changes for the relevant types of servers (e.g., to the
Zoning Database), the SNMP agent must get serialized access
to the Fabric (for the relevant type of management data),
i.e., the Fabric must be locked by creating an entry in
this table via an SNMP SetRequest. Creating an entry in
this table via an SNMP SetRequest causes an ACA or an EACA
to be sent to all other switches in the Fabric. The value
of t11FLockApplicationID for such an entry determines
whether an ACA or an EACA is sent.
If an entry in this table is created by an SNMP SetRequest,
the value of the t11FLockInitiatorType object in that entry
will normally be 'snmp'. A row for which the value of
t11FLockInitiatorType is not 'snmp' cannot be modified
via SNMP. In particular, it cannot be deleted via
t11FLockRowStatus. Note that it's possible for a row to be
created by an SNMP SetRequest, but for the setup of the lock
to fail, and immediately thereafter be replaced by a lock
successfully set up by some other means; in such a case, the
value of t11FLockInitiatorType would change as and when the
lock was set up by the other means, and so the row could
not thereafter be deleted via t11FLockRowStatus.
FC-GS-5 mentions various error situations in which a
Fabric lock is released so as to avoid a deadlock. In
such situations, the agent removes the corresponding row
in this table as and when the lock is released. This can
happen for all values of t11FLockInitiatorType. |
| T11 t11FLockFabricIndex | 1.3.6.1.2.1.159.1.1.1.1.1 | T11FabricIndex | not-accessible | A unique index value that uniquely identifies a
particular Fabric.
In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics
can operate within one (or more) physical infrastructures,
and this index value is used to uniquely identify a
particular (physical or virtual) Fabric within a physical
infrastructure.
In a Fabric conformant to versions earlier than FC-SW-4,
only a single Fabric could operate within a physical
infrastructure, and thus, the value of this Fabric Index
was defined to always be 1. |
| OCT t11FLockApplicationID | 1.3.6.1.2.1.159.1.1.1.1.2 | OCTET STRING | not-accessible | The Application_ID value that identifies the type of
application for which the Fabric is locked.
A lock established via Acquire Change Authorization (ACA)
does not, strictly speaking, have an Application_ID value.
However, the value 'FF'h (255 decimal) has been reserved
by T11 to be used as the value of this MIB object as and
when a lock is established by an ACA. This value was
initially documented in a letter from the FC-SW-5 Editor
to T11.5, which was approved by the T11 and T11.5 plenary
meetings on October 5, 2006. |
| INT t11FLockInitiatorType | 1.3.6.1.2.1.159.1.1.1.1.3 | INTEGER | read-only | This object specifies what type of initiator generated
the request that caused this lock to be established:
other - none of the following.
ssb - this lock was established due to the
receipt of an SSB, e.g., from a GS-5
client.
cli - this lock was established in order
to process a Command Line Interface
(CLI) command.
snmp - this lock was established as a result
of an SNMP SetRequest. |
| OCT t11FLockInitiator | 1.3.6.1.2.1.159.1.1.1.1.4 | OCTET STRING | read-only | This object specifies the initiator whose request
caused this lock to be established.
If the value of the corresponding instance
of t11FLockInitiatorType is 'ssb', this
object will contain the FC_ID of the client
that issued the Server Session Begin (SSB)
that required the lock to be established.
If the value of the corresponding instance
of t11FLockInitiatorType object is 'cli', this
object will contain the user name of the CLI
(Command Line Interface) user on whose behalf
the lock was established.
If the value of the corresponding instance of
t11FLockInitiatorType is 'snmp', this object
will contain the SNMP securityName used by the
SNMPv3 message containing the SetRequest that
created this row. (If the row was created via
SNMPv1 or SNMPv2c, then the appropriate value of
the snmpCommunitySecurityName is used.) |
| IPt t11FLockInitiatorIpAddrType | 1.3.6.1.2.1.159.1.1.1.1.5 | InetAddressType | read-only | This object specifies the type of IP address contained
in the corresponding instance of t11FLockInitiatorIpAddr.
If the IP address of the location of the initiator is
unknown or not applicable, this object has the value:
'unknown'. |
| IP t11FLockInitiatorIpAddr | 1.3.6.1.2.1.159.1.1.1.1.6 | InetAddress | read-only | This object specifies the IP address of the location
of the initiator that established this lock via a
request of the type given by the corresponding instance
of t11FLockInitiatorType. In cases where the
corresponding instance of t11FLockInitiatorIpAddrType has
the value: 'unknown', the value of this object is the
zero-length string. |
| INT t11FLockStatus | 1.3.6.1.2.1.159.1.1.1.1.7 | INTEGER | read-only | This object gives the current status of the lock:
'active' -- the lock is currently established.
'settingUp' -- the 'managing' switch is currently
attempting to set up the lock, e.g.,
it is waiting to receive Accepts
for ACAs from every switch in the
Fabric.
'rejectFailure' -- the 'managing' switch's attempt to
set up the lock was rejected with
the reason codes given by:
t11FLockRejectReasonCode,
t11FLockRejectReasonCodeExp and
t11FLockRejectReasonVendorCode.
'otherFailure' -- the 'managing' switch's attempt
to set up the lock failed (but no
reason codes are available).
For values of t11FLockInitiatorType other than 'snmp',
a row is only required to be instantiated in this table
when the value of this object is 'active'.
If the value of the corresponding instance of
t11FLockInitiatorType is 'snmp', the initial value of this
object when the row is first created is 'settingUp'. As
and when the setup succeeds, the value transitions to
'active'. If the setup fails, the value transitions to
either 'rejectFailure' or 'otherFailure'. Note that such a
failure value is overwritten on the next attempt to obtain
the lock, which could be immediately after the failure,
e.g., by a GS-5 client.
When the value of this object is 'rejectFailure', the
rejection's reason codes are given by the corresponding
values of t11FLockRejectReasonCode,
t11FLockRejectReasonCodeExp and
t11FLockRejectReasonVendorCode. |
| T11 t11FLockRejectReasonCode | 1.3.6.1.2.1.159.1.1.1.1.8 | T11NsGs4RejectReasonCode | read-only | When the value of the corresponding instance of
t11FLockStatus is 'rejectFailure', this object contains
the rejection's reason code. |
| OCT t11FLockRejectReasonCodeExp | 1.3.6.1.2.1.159.1.1.1.1.9 | OCTET STRING | read-only | When the value of the corresponding instance of
t11FLockStatus is 'rejectFailure', this object contains
the rejection's reason code explanation. |
| OCT t11FLockRejectReasonVendorCode | 1.3.6.1.2.1.159.1.1.1.1.10 | OCTET STRING | read-only | When the value of the corresponding instance of
t11FLockStatus is 'rejectFailure', this object contains
the rejection's vendor-specific code. |
| ROW t11FLockRowStatus | 1.3.6.1.2.1.159.1.1.1.1.11 | RowStatus | read-create | The status of this conceptual row.
A row in this table can be modified or deleted via
this object only when the row's value of
t11FLockInitiatorType is 'snmp'. |
| t11FLockMIBConformance | 1.3.6.1.2.1.159.2 | | | |
| t11FLockMIBCompliances | 1.3.6.1.2.1.159.2.1 | | | |
| t11FLockMIBCompliance | 1.3.6.1.2.1.159.2.1.1 | | | The compliance statement for entities that support
Fabric locks in support of GS-5 Server applications. |
| t11FLockMIBGroups | 1.3.6.1.2.1.159.2.2 | | | |
| t11FLockActiveGroup | 1.3.6.1.2.1.159.2.2.1 | | | A collection of objects containing information
about current Fabric locks. |
