Reference record for OID 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2.3

parent

1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2 (status-rpc)

node code

3

node name

rpc-bound-protocol-address

dot oid

1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2.3

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) nm(2) system(3) net-peripheral(9) netdm(4) dm(2) device(1) system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) nm(2) system(3) net-peripheral(9) netdm(4) dm(2) device(1) device-system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

...skipped...

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) IMPORTS(11) nm(2) hpsystem(3) netPeripheral(9) netPML(4) netPMLmgmt(2) device(1) system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) IMPORTS(11) nm(2) hpsystem(3) netPeripheral(9) netPML(4) netPMLmgmt(2) device(1) device-system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) nm(2) system(3) net-peripheral(9) netdm(4) dm(2) device(1) system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) nm(2) system(3) net-peripheral(9) netdm(4) dm(2) device(1) device-system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

...skipped...

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) IMPORTS(11) nm(2) hpsystem(3) netPeripheral(9) netPML(4) netPMLmgmt(2) device(1) system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) IMPORTS(11) nm(2) hpsystem(3) netPeripheral(9) netPML(4) netPMLmgmt(2) device(1) device-system(1) remote-procedure-call(13) status-rpc(2) rpc-bound-protocol-address(3)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/hp/nm/system/net-peripheral/netdm/dm/device/system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

/iso/identified-organization/dod/internet/private/enterprise/hp/nm/system/net-peripheral/netdm/dm/device/device-system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

...skipped...

/iso/org/dod/internet/private/enterprise/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

/iso/org/dod/internet/private/enterprise/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/device-system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

/iso/org/dod/internet/private/enterprises/hp/nm/system/net-peripheral/netdm/dm/device/system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

/iso/org/dod/internet/private/enterprises/hp/nm/system/net-peripheral/netdm/dm/device/device-system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

...skipped...

/iso/iso-identified-organization/dod/internet/private/enterprises/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

/iso/iso-identified-organization/dod/internet/private/enterprises/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/device-system/remote-procedure-call/status-rpc/rpc-bound-protocol-address

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/11/2/3/9/4/2/1/1/13/2/3

Description by mibdepot

An array of Berkeley sockets style protocol addresses
that the NFS service has been bound to successful. The
format is that same as the array of RPC-BIND-PROTOCOL-
ADDRESS of objects.
Additional information:
Returns
status if attempting to access this object and there
is no storage device is installed.

Parsed from file lj4100mfp_beta.mib.txt
Company: None
Module: LJ4100mfp-MIB

Description by circitor

An array of Berkeley sockets style protocol addresses
that the NFS service has been bound to successful. The
format is that same as the array of RPC-BIND-PROTOCOL-
ADDRESS of objects.
Additional information:
Returns
status if attempting to access this object and there
is no storage device is installed.

Parsed from file LaserJet5Si-MIB.mib
Module: LaserJet5Si-MIB

Information by oid_info

Vendor: Hewlett-Packard
Module: HP-LASERJET-COMMON-MIB

[Automatically extracted from oidview.com]

Information by mibdepot

rpc-bound-protocol-address OBJECT-TYPE
    SYNTAX  OCTET STRING
    ACCESS  read-only
    STATUS  optional
    DESCRIPTION
                "An array of Berkeley sockets style protocol addresses
                that the NFS service has been bound to successful.  The
                format is that same as the array of RPC-BIND-PROTOCOL-
                ADDRESS of objects.
                Additional information:
                Returns 
                status if attempting to access this object and there
                is no storage device is installed."
::= { status-rpc 3 }

Information by circitor

rpc-bound-protocol-address OBJECT-TYPE
    SYNTAX  OCTET STRING
    ACCESS  read-only
    STATUS  optional
    DESCRIPTION
                "An array of Berkeley sockets style protocol addresses
                that the NFS service has been bound to successful.  The
                format is that same as the array of RPC-BIND-PROTOCOL-
                ADDRESS of objects.
                Additional information:
                Returns 
                status if attempting to access this object and there
                is no storage device is installed."
::= { status-rpc 3 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.11)

Peterson Tyler

Brothers (2)