rpc-bind-protocol-address

Array of Berkeley sockets style protocol addresses used
to bind RPC to a communications protocol family.
Setting an instance of this array object to a zero
length binary value disables the transport protocol
indicated by that instance.  All multi-bytes fields are
in network (or big-endian) order.  Bytes 1 and 2
indicate the transport protocol.  Some of the transport
protocol mapping information can be found in RFC 1010
Assigned Numbers.  A list of interesting transport
protocol number mappings include:  
Protocol | Number   
---------+-------   
 UDP/IP  |  17   
  IPX    |  1000   
  MLC    |  4660   
Bytes 3 and 4 indicate the address family.  The address
family uses the same mapping as the BSD sockets address
family.  A list of interesting address family mappings
include:  
Address Family | Number   
---------------+-------   
    Internet   |   2   
    NetWare    |   6   
    MLC        | 22136   
The format the fifth and following bytes is dependent on
the address family.  For the Internet address family,
bytes 5 and 6 contain the port number, bytes 7 through
10 contain the IP address, and the following eight bytes
are unused.  For NetWare, bytes 5 through 8 are the
network number, bytes 9 through 14 are the node number,
and bytes 15 and 16 are the socket number.
Additional information:
The length of the binary value is zero
if the instance of an object in the rpc-bind-protocol-address
array is not in use.   An unfortunate side effect of the 
implementation is initializing the mass storage device sets this object 
back to the factory default value.  
Returns <noSuchName>
status if attempting to access this object and there
is no storage device is installed.

MIB

HP-LASERJET-COMMON-MIB

OID

.1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1.2

Type

scalar

Access

readwrite

Status

mandatory

Parent

settings-rpc

Siblings

1