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.
Parsed from file gadz.mib.txt
Company: None
Module: Gadz-1-MIB
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.
Parsed from file Gadz-1-MIB.mib
Module: Gadz-1-MIB
Vendor: Gadzoox Microsystems Inc.
Module: Gadz-1-MIB
[Automatically extracted from oidview.com]
nlZoningPolicyControl OBJECT-TYPE SYNTAX INTEGER { clear-owner(0), create-table(1), clear-zoning-configuration(2), default-zoning-configuration(3) } ACCESS read-write STATUS mandatory 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. " ::= { zoning 4}
nlZoningPolicyControl OBJECT-TYPE SYNTAX INTEGER { clear-owner(0), create-table(1), clear-zoning-configuration(2), default-zoning-configuration(3) } ACCESS read-write STATUS mandatory 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. " ::= { zoning 4}
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1754.1.1.1.3.1 | nlZoningPolicyControlOwner | 0 | 0 | The entity that last configured, or is currently configuring the zoning policy. |
| 1.3.6.1.4.1.1754.1.1.1.3.2 | nlZoningPolicyTimeout | 0 | 0 | The timeout value to be used in configuring the zoning agent. The default value is 30 seconds. |
| 1.3.6.1.4.1.1754.1.1.1.3.3 | nlZoningPolicyStatus | 0 | 0 | The status of the current zoning policy configuration. |
| 1.3.6.1.4.1.1754.1.1.1.3.5 | nlZoningPolicyLastError | 0 | 0 | The last error condition string returned from the zoning agent. |
| 1.3.6.1.4.1.1754.1.1.1.3.6 | nlPendingZoneCount | 0 | 0 | Number of Pending configured zones for this proxied domain |
| 1.3.6.1.4.1.1754.1.1.1.3.7 | nlPendingZoneTable | 1 | 6 | The Pending Zone Table. - this is the zone table the NMS is building up in the proxy domain, before activating it. |
| 1.3.6.1.4.1.1754.1.1.1.3.8 | nlPendingZoneMemberCount | 0 | 0 | Number of pending zone members for this proxied domain |
| 1.3.6.1.4.1.1754.1.1.1.3.9 | nlPendingZoneMemberTable | 1 | 5 | Pending Zone Member Table. This table keeps track of the pending zone members that the current snmp zone configuration session ha… |
| 1.3.6.1.4.1.1754.1.1.1.3.10 | nlActiveZoneCount | 0 | 0 | Number of active configured zones for this proxied domain. When this object is read the 'Zoning Configuration Event' bit in the d… |
| 1.3.6.1.4.1.1754.1.1.1.3.11 | nlActiveZoneTable | 1 | 7 | Active Zone Table. |
| 1.3.6.1.4.1.1754.1.1.1.3.12 | nlActiveZoneMemberCount | 0 | 0 | Number of configured zone members for this proxied domain |
| 1.3.6.1.4.1.1754.1.1.1.3.13 | nlActiveZoneMemberTable | 1 | 5 | Active Zone Member Table. |