All MIBs › Gadz-1-MIB › nlPendingZoneMemberID
nlPendingZoneMemberID
Module: Gadz-1-MIB
OID (symbolic): Gadz-1-MIB::nlPendingZoneMemberID
OID (numeric): 1.3.6.1.4.1.1754.1.1.1.3.9.1.4
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: write-only
Description: Specifies the intrinsic ID of this zone member. To add an entry to the list of zone member names, a write should be done to index 0. If the ZoneMemberType is PortZoneMember, the structure is: BYTE 0: The Proxy Management ID of the InterConnect device that this port belongs to. If 0, then this is a 'phantom' zone member, in that it does not have a corresponding device ID. Essentially, a phantom zone member is a zone member that has been created, but not yet bound to a proxied device. Use bytes 2 and 3 to correctly determine the ID of this zone member. BYTE 1: The Port Number on the InterConnect Device. BYTE 2: The device ID of the chassis that contains the slot that contains this port. (only valid if byte 0 equals 0) BYTE 3: The slot number of the slot that contains this port. (only valid if byte 0 is 0)
If the ZoneMemberType is HardAssignedALPAZoneMember, then the structure is: BYTE 0: The Proxy Management ID of the InterConnect device that this port belongs to. If 0, then this is a 'phantom' zone member, in that it does not have a corresponding device ID. Essentially, a phantom zone member is a zone member that has been created, but not yet bound to a proxied device. Use bytes 3 and 4 to correctly determine the ID of this zone member. BYTE 1: The Port Number on the InterConnect Device. BYTE 2: The hard-assigned AL_PA of the NL_Node. BYTE 3: The device ID of the chassis that contains the slot that contains this port. (only valid if byte 0 equals 0) BYTE 4: The slot number of the slot that contains this port. (only valid if byte 0 is 0)
If the ZoneMemberType is WWNZoneMember, the structure is: BYTE 0 -> size of string : The WWN of the zone member.
What is nlPendingZoneMemberID?
Carries the binary identifier of a staged zone member; its byte layout (proxy device ID, port number, chassis/slot, or AL_PA) depends on the type set in nlPendingZoneMemberType, letting a member be pinned to a specific physical port or loop address.
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.9 | nlPendingZoneMemberTable | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1.1.1.3.9.1 | nlPendingZoneMemberEntry | Gadz-1-MIB |
| 1.3.6.1.4.1.1754.1.1.1.3.9.1.4 | nlPendingZoneMemberID | Gadz-1-MIB |