Reference record for OID 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1.1

parent

1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1 (settings-rpc)

node code

1

node name

rpc-test-return-code

dot oid

1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1.1

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) settings-rpc(1) rpc-test-return-code(1)}

{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) settings-rpc(1) rpc-test-return-code(1)}

...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) settings-rpc(1) rpc-test-return-code(1)}

{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) settings-rpc(1) rpc-test-return-code(1)}

{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) settings-rpc(1) rpc-test-return-code(1)}

{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) settings-rpc(1) rpc-test-return-code(1)}

...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) settings-rpc(1) rpc-test-return-code(1)}

{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) settings-rpc(1) rpc-test-return-code(1)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/hp/nm/system/net-peripheral/netdm/dm/device/system/remote-procedure-call/settings-rpc/rpc-test-return-code

/iso/identified-organization/dod/internet/private/enterprise/hp/nm/system/net-peripheral/netdm/dm/device/device-system/remote-procedure-call/settings-rpc/rpc-test-return-code

...skipped...

/iso/org/dod/internet/private/enterprise/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/system/remote-procedure-call/settings-rpc/rpc-test-return-code

/iso/org/dod/internet/private/enterprise/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/device-system/remote-procedure-call/settings-rpc/rpc-test-return-code

/iso/org/dod/internet/private/enterprises/hp/nm/system/net-peripheral/netdm/dm/device/system/remote-procedure-call/settings-rpc/rpc-test-return-code

/iso/org/dod/internet/private/enterprises/hp/nm/system/net-peripheral/netdm/dm/device/device-system/remote-procedure-call/settings-rpc/rpc-test-return-code

...skipped...

/iso/iso-identified-organization/dod/internet/private/enterprises/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/system/remote-procedure-call/settings-rpc/rpc-test-return-code

/iso/iso-identified-organization/dod/internet/private/enterprises/IMPORTS/nm/hpsystem/netPeripheral/netPML/netPMLmgmt/device/device-system/remote-procedure-call/settings-rpc/rpc-test-return-code

iri by oid_info

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

Description by mibdepot

This test object that will not be supported in any
released product. Setting this object allows the next
RPC call return code to be specified. The POS will
specify the binary format.
Additional information:
The format of the binary data is a one
of three formats. The first format is no binary
data, which indicates the next RPC reply should not
be modified. The other two formats are described in
RFC 1057 and encoded using XDR (i.e. the value is
the data used to instead of the actual RPC reply).
The second format is when reply_stat is MSG_ACCEPTED
and accept_stat is something other than SUCCESS.
The third format is when reply_stat is MSG_DENIED.
Notice that all RPC replies that do not contain any
'results' are supported.

Parsed from file LJ5SIMOP.MIB.txt
Company: None
Module: LaserJet5Si-Mopier-MIB

Description by circitor

This test object that will not be supported in any
released product. Setting this object allows the next
RPC call return code to be specified. The POS will
specify the binary format.
Additional information:
The format of the binary data is a one
of three formats. The first format is no binary
data, which indicates the next RPC reply should not
be modified. The other two formats are described in
RFC 1057 and encoded using XDR (i.e. the value is
the data used to instead of the actual RPC reply).
The second format is when reply_stat is MSG_ACCEPTED
and accept_stat is something other than SUCCESS.
The third format is when reply_stat is MSG_DENIED.
Notice that all RPC replies that do not contain any
'results' are supported.

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-test-return-code OBJECT-TYPE
    SYNTAX  OCTET STRING
    ACCESS  write-only
    STATUS  optional
    DESCRIPTION
                "This test object that will not be supported in any
                released product.  Setting this object allows the next
                RPC call return code to be specified.  The POS will
                specify the binary format.
                Additional information:
                The format of the binary data is a one
                of three formats.  The first format is no binary
                data, which indicates the next RPC reply should not
                be modified.  The other two formats are described in
                RFC 1057 and encoded using XDR (i.e.  the value is
                the data used to instead of the actual RPC reply).
                The second format is when reply_stat is MSG_ACCEPTED
                and accept_stat is something other than SUCCESS.
                The third format is when reply_stat is MSG_DENIED.
                Notice that all RPC replies that do not contain any
                'results' are supported."
::= { settings-rpc 1 }

Information by circitor

rpc-test-return-code OBJECT-TYPE
    SYNTAX  OCTET STRING
    ACCESS  write-only
    STATUS  optional
    DESCRIPTION
                "This test object that will not be supported in any
                released product.  Setting this object allows the next
                RPC call return code to be specified.  The POS will
                specify the binary format.
                Additional information:
                The format of the binary data is a one
                of three formats.  The first format is no binary
                data, which indicates the next RPC reply should not
                be modified.  The other two formats are described in
                RFC 1057 and encoded using XDR (i.e.  the value is
                the data used to instead of the actual RPC reply).
                The second format is when reply_stat is MSG_ACCEPTED
                and accept_stat is something other than SUCCESS.
                The third format is when reply_stat is MSG_DENIED.
                Notice that all RPC replies that do not contain any
                'results' are supported."
::= { settings-rpc 1 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.11)

Peterson Tyler

Brothers (1)