Larry, you are correct. The use of hrMIB was rather unfortunate in that it
forced the munging of local resource indexing onto a networked device. For
all intents and purposes, in the embedded network printer, the "host" IS
the printer controller (there may still be implementations where the host
is the NIC). The hrMIB is still useful in this context for helping
distinguish internal printer resources like a storage device, for example.
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
"Larry R. Walsh" <larrywalsh@chateausystems.com>
07/26/2004 03:29 PM
Please respond to
larrywalsh
To
Harry Lewis/Boulder/IBM@IBMUS
cc
Subject
Question Re intended agent support for RFC3805
Hello Harry,
RFC3805 appears to be clearly intended to be supported by an agent on a
platform with attached printers ? as evidenced by using the index
?hrDeviceIndex? in its tables.
Is it also intended for implementation as an embedded agent within a
printer? If so, then I would assume that ?hrDeviceIndex? takes on one
value that is local to the printer, and that value has nothing to do with
the host resource index on the platform. Right?
Thanks for any insights you can provide.
Best Regards, Larry
Larry R. Walsh
SNMP Training & SNMP Development
Embedded Systems Software Development
360 862-1154
larrywalsh@chateausystems.com
www.chateausystems.com
This archive was generated by hypermail 2b29 : Thu Aug 12 2004 - 18:56:38 EDT