H3C-FC-ZONE-SERVER-MIB :: h3cFcZsActivateFailReason

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsH3C-FC-ZONE-SERVER-MIBh3cFcZsActivateFailReason

h3cFcZsActivateFailReason

Module: H3C-FC-ZONE-SERVER-MIB

OID (symbolic): H3C-FC-ZONE-SERVER-MIB::h3cFcZsActivateFailReason

OID (numeric): 1.3.6.1.4.1.2011.10.2.127.9.1.2.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The reason for the most recent failure of a Zone Set activation or deactivation.

'none' - No activation/deactivation invoked or the result of activation/deactivation is success. 'busy' - The management system is busy in some other process. 'activeZoneSetTooBig' - The Active Zone Set size in packet reached the maximum limit in Basic mode. 'noZoneSet' - No specified Zone Set found. 'noMember' - No port member found in the specified Zone Set.

What is h3cFcZsActivateFailReason?

This reports why the most recent zone-set activation/deactivation failed: none(1, no failure), busy(2, system busy with another operation), activeZoneSetTooBig(3, exceeds packet size limit in Basic mode), noZoneSet(4, the named zone set wasn't found), or noMember(5, the zone set has no port members). Admins check this alongside h3cFcZsActivateResult to diagnose why an activation attempt failed, for example a typo in the zone set name causing noZoneSet.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.127.9.1.2.1.1.4
snmpwalk -v2c -c public <target> H3C-FC-ZONE-SERVER-MIB::h3cFcZsActivateFailReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.127.9.1.2.1.1.4.1
snmpget -v2c -c public <target> H3C-FC-ZONE-SERVER-MIB::h3cFcZsActivateFailReason.1

Start monitoring H3C Fibre Channel SAN switch (Basic/Enhanced Zoning) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the H3C-FC-ZONE-SERVER-MIB::h3cFcZsActivateFailReason OID value, configure state conditions and alerts, and monitor any H3C Fibre Channel SAN switch (Basic/Enhanced Zoning) from a single console.

OID Breakdown

Upper-level ancestors (10 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2011huaweiHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.10h3cHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.10.2h3cCommonHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.10.2.127h3cSanH3C-VSAN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2011.10.2.127.9h3cFcZoneServerH3C-FC-ZONE-SERVER-MIB
1.3.6.1.4.1.2011.10.2.127.9.1h3cFcZoneMibObjectsH3C-FC-ZONE-SERVER-MIB
1.3.6.1.4.1.2011.10.2.127.9.1.2h3cFcZsOperationH3C-FC-ZONE-SERVER-MIB
1.3.6.1.4.1.2011.10.2.127.9.1.2.1h3cFcZsActivateTableH3C-FC-ZONE-SERVER-MIB
1.3.6.1.4.1.2011.10.2.127.9.1.2.1.1h3cFcZsActivateEntryH3C-FC-ZONE-SERVER-MIB
1.3.6.1.4.1.2011.10.2.127.9.1.2.1.1.4h3cFcZsActivateFailReasonH3C-FC-ZONE-SERVER-MIB