All MIBs › T11-FC-FABRIC-LOCK-MIB › t11FLockStatus
t11FLockStatus
Module: T11-FC-FABRIC-LOCK-MIB
OID (symbolic): T11-FC-FABRIC-LOCK-MIB::t11FLockStatus
OID (numeric): 1.3.6.1.2.1.159.1.1.1.1.7
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: 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.
What is t11FLockStatus?
This value reports the current status of the fabric lock: active (currently established), settingUp (the managing switch is waiting for Accepts from every switch in the fabric), rejectFailure (setup was rejected, with reason codes in the accompanying objects), or otherFailure (setup failed without available reason codes); for SNMP-initiated locks the row starts at settingUp and transitions from there, with failure states overwritten by the next lock attempt. Admins monitor it to see whether a fabric-wide configuration lock they requested actually succeeded, is still being negotiated across switches, or failed. A status of rejectFailure would prompt the admin to check t11FLockRejectReasonCode to understand why the fabric refused to grant the lock.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.159.1.1.1.1.7 snmpwalk -v2c -c public <target> T11-FC-FABRIC-LOCK-MIB::t11FLockStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.159.1.1.1.1.7.1 snmpget -v2c -c public <target> T11-FC-FABRIC-LOCK-MIB::t11FLockStatus.1
Start monitoring Fibre Channel SAN switches/fabrics, vendor-neutral standards-based MIB (fabric-lock contention/rejection status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the T11-FC-FABRIC-LOCK-MIB::t11FLockStatus OID value, configure state conditions and alerts, and monitor any Fibre Channel SAN switches/fabrics, vendor-neutral standards-based MIB (fabric-lock contention/rejection status) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.159 | t11FabricLockMIB | T11-FC-FABRIC-LOCK-MIB |
| 1.3.6.1.2.1.159.1 | t11FLockMIBObjects | T11-FC-FABRIC-LOCK-MIB |
| 1.3.6.1.2.1.159.1.1 | t11FLockConfiguration | T11-FC-FABRIC-LOCK-MIB |
| 1.3.6.1.2.1.159.1.1.1 | t11FLockTable | T11-FC-FABRIC-LOCK-MIB |
| 1.3.6.1.2.1.159.1.1.1.1 | t11FLockEntry | T11-FC-FABRIC-LOCK-MIB |
| 1.3.6.1.2.1.159.1.1.1.1.7 | t11FLockStatus | T11-FC-FABRIC-LOCK-MIB |