Reference record for OID 1.3.6.1.4.1.1754.1.1.1.3.9.1.4



parent
1.3.6.1.4.1.1754.1.1.1.3.9.1 (nlPendingZoneMemberEntry)
node code
4
node name
nlPendingZoneMemberID
dot oid
1.3.6.1.4.1.1754.1.1.1.3.9.1.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) gadzoox(1754) netMgmt(1) common(1) system(1) zoning(3) nlPendingZoneMemberTable(9) nlPendingZoneMemberEntry(1) nlPendingZoneMemberID(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) gadzoox(1754) netMgmt(1) common(1) system(1) zoning(3) nlPendingZoneMemberTable(9) nlPendingZoneMemberEntry(1) nlPendingZoneMemberID(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) gadzoox(1754) netMgmt(1) common(1) system(1) zoning(3) nlPendingZoneMemberTable(9) nlPendingZoneMemberEntry(1) nlPendingZoneMemberID(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gadzoox(1754) netMgmt(1) common(1) system(1) zoning(3) nlPendingZoneMemberTable(9) nlPendingZoneMemberEntry(1) nlPendingZoneMemberID(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) gadzoox(1754) netMgmt(1) common(1) system(1) zoning(3) nlPendingZoneMemberTable(9) nlPendingZoneMemberEntry(1) nlPendingZoneMemberID(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) gadzoox(1754) netMgmt(1) common(1) system(1) zoning(3) nlPendingZoneMemberTable(9) nlPendingZoneMemberEntry(1) nlPendingZoneMemberID(4)}
    • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/gadzoox/netMgmt/common/system/zoning/nlPendingZoneMemberTable/nlPendingZoneMemberEntry/nlPendingZoneMemberID
  • /iso/identified-organization/dod/internet/private/enterprises/gadzoox/netMgmt/common/system/zoning/nlPendingZoneMemberTable/nlPendingZoneMemberEntry/nlPendingZoneMemberID
  • /iso/org/dod/internet/private/enterprise/gadzoox/netMgmt/common/system/zoning/nlPendingZoneMemberTable/nlPendingZoneMemberEntry/nlPendingZoneMemberID
  • /iso/org/dod/internet/private/enterprises/gadzoox/netMgmt/common/system/zoning/nlPendingZoneMemberTable/nlPendingZoneMemberEntry/nlPendingZoneMemberID
  • /iso/iso-identified-organization/dod/internet/private/enterprise/gadzoox/netMgmt/common/system/zoning/nlPendingZoneMemberTable/nlPendingZoneMemberEntry/nlPendingZoneMemberID
  • /iso/iso-identified-organization/dod/internet/private/enterprises/gadzoox/netMgmt/common/system/zoning/nlPendingZoneMemberTable/nlPendingZoneMemberEntry/nlPendingZoneMemberID
    • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/1754/1/1/1/3/9/1/4

    Description by mibdepot

    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.

    Parsed from file gadz.mib.txt
    Company: None
    Module: Gadz-1-MIB

    Description by circitor

    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.

    Parsed from file Gadz-1-MIB.mib
    Module: Gadz-1-MIB

    Information by oid_info

    Vendor: Gadzoox Microsystems Inc.
    Module: Gadz-1-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    nlPendingZoneMemberID OBJECT-TYPE
           SYNTAX    OCTET STRING
           ACCESS    write-only
           STATUS    mandatory
           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." 
            ::= { nlPendingZoneMemberEntry 4 }

    Information by circitor

    nlPendingZoneMemberID OBJECT-TYPE
           SYNTAX    OCTET STRING
           ACCESS    write-only
           STATUS    mandatory
           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." 
            ::= { nlPendingZoneMemberEntry 4 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.1754)

    Banker Kim

    Brothers (3)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.1754.1.1.1.3.9.1.1 nlPendingZoneMemberIndex 0 0 An identifier which uniquely identifies a zone member.
    1.3.6.1.4.1.1754.1.1.1.3.9.1.2 nlPendingZoneMemberName 0 0 Specifies the name of the zone member.
    To add an entry to the list of zone member names, a write
    should be done to index 0.
    1.3.6.1.4.1.1754.1.1.1.3.9.1.3 nlPendingZoneMemberType 0 0 Specifies the type of this zone member. The type of the
    zone member dicates the structure of the PendingZoneMemberID.
    To add an …