All MIBs › Gadz-1-MIB › nlZoningPolicyControl
nlZoningPolicyControl
Module: Gadz-1-MIB
OID (symbolic): Gadz-1-MIB::nlZoningPolicyControl
OID (numeric): 1.3.6.1.4.1.1754.1.1.1.3.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The control of the current zoning policy configuration. The procedure for zoning policy configuration is as follows: - user reads nlActiveZoneTable AND/OR nlActiveZoneMemberTable to determine current zone configuration and makes any local edits. - user continually reads back nlZoningPolicyStatus until 'no_current_owner' is received. - user writes its address to nlZoningPolicyControlOwner in order to lock zoning control and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user can validate that it has successfully locked zone policy control by reading back its own address from nlZoningPolicyControlOwner. - user (optionally) writes timeout value to nlZoningPolicyTimeout, and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user writes 'clear-zoning-configuration' to nlZoningPolicyControl to clear existing ta nlZoningPolicyControl to clear existing table and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user continually adds zone OR zone member entries by writing to the appropriate objects using index 0 of the table, and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - after the last entry is made, user writes 'create_table' to nlZoningPolicyControl, and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - OR the user writes 'default-zoning-configuration' to load the default zoning configuration and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user writes 'clear_owner' to nlZoningPolicyControl (or waits for the zoning timeout to occur) to release ownership of zoning policy configuration.
What is nlZoningPolicyControl?
Drives the multi-step zoning workflow: after locking control via nlZoningPolicyControlOwner, an admin writes clear-zoning-configuration to wipe the existing zone table, stages new zone and member rows, then writes create-table to activate them (or default-zoning-configuration to reload the factory default set), and finally clear-owner to release the lock.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1754.1.1.1.3.4 snmpwalk -v2c -c public <target> Gadz-1-MIB::nlZoningPolicyControl
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1754.1.1.1.3.4.1 snmpget -v2c -c public <target> Gadz-1-MIB::nlZoningPolicyControl.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.1754.1.1.1.3.4.1 i <value>
Start monitoring Gadzoox Networks network device (basic system management) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Gadz-1-MIB::nlZoningPolicyControl OID value, configure state conditions and alerts, and monitor any Gadzoox Networks network device (basic system management) 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.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1754 | gadzoox | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1 | netMgmt | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1.1 | common | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1.1.1 | system | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1.1.1.3 | zoning | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1.1.1.3.4 | nlZoningPolicyControl | Gadz-1-MIB |