T11-FC-SP-ZONING-MIB :: t11FcSpZoneSetHashStatus

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › T11-FC-SP-ZONING-MIB › t11FcSpZoneSetHashStatus

t11FcSpZoneSetHashStatus

Module: T11-FC-SP-ZONING-MIB

OID (symbolic): T11-FC-SP-ZONING-MIB::t11FcSpZoneSetHashStatus

OID (numeric): 1.3.6.1.2.1.177.1.1.1.1.3

Node type: OBJECT-TYPE

Type: T11FcSpHashCalculationStatus

Access: read-write

Description: When read, the value of this object is either:

correct -- the corresponding instances of both t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash contain the correct hash values; or stale -- the corresponding instances of t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash contain stale (possibly incorrect) values;

Writing a value of 'calculate' is a request to re-calculate and update the values of the corresponding instances of both t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash. Writing a value of 'correct' or 'stale' to this object is an error (e.g., 'wrongValue').

When the Active Zone Set and/or the Zone Set Database are updated, it is common that multiple changes need to be made at the same time. In such circumstances, the use of this object allows the hash values to be updated only once after all changes, rather than repeatedly/after each individual change.

If and when the corresponding instance of t11ZsServerDatabaseStorageType has the value 'permanent(4)', then if write access is supported to any instance of a read-write object in any row of any table governed by the 'permanent' value of t11ZsServerDatabaseStorageType, then

write access to the corresponding instance of this object must also be supported.

What is t11FcSpZoneSetHashStatus?

This object reports whether the hash values in t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash are correct, meaning up to date, or stale, meaning possibly outdated, for the current zone set and zone database. After making multiple zoning changes, an admin writes the value 'calculate' to force the Zone Server to recompute both hashes just once rather than after each individual edit; writing 'correct' or 'stale' directly is rejected as an error. If this reads stale after a batch of zone edits, the admin writes 'calculate' to refresh both hash values before relying on them to detect tampering.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.177.1.1.1.1.3
snmpwalk -v2c -c public <target> T11-FC-SP-ZONING-MIB::t11FcSpZoneSetHashStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.177.1.1.1.1.3.1
snmpget -v2c -c public <target> T11-FC-SP-ZONING-MIB::t11FcSpZoneSetHashStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.177.1.1.1.1.3.1 s <value>

Start monitoring Fibre Channel switches and directors with FC-SP zoning support (secure zoning capability/hash-integrity status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the T11-FC-SP-ZONING-MIB::t11FcSpZoneSetHashStatus OID value, configure state conditions and alerts, and monitor any Fibre Channel switches and directors with FC-SP zoning support (secure zoning capability/hash-integrity status) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.177t11FcSpZoningMIBT11-FC-SP-ZONING-MIB
1.3.6.1.2.1.177.1t11FcSpZsMIBObjectsT11-FC-SP-ZONING-MIB
1.3.6.1.2.1.177.1.1t11FcSpZsConfigurationT11-FC-SP-ZONING-MIB
1.3.6.1.2.1.177.1.1.1t11FcSpZsServerTableT11-FC-SP-ZONING-MIB
1.3.6.1.2.1.177.1.1.1.1t11FcSpZsServerEntryT11-FC-SP-ZONING-MIB
1.3.6.1.2.1.177.1.1.1.1.3t11FcSpZoneSetHashStatusT11-FC-SP-ZONING-MIB