PMP Mail Archive: PMP> RE: Print MIB 09

PMP Mail Archive: PMP> RE: Print MIB 09

PMP> RE: Print MIB 09

From: Bergman, Ron (Ron.Bergman@Hitachi-hkis.com)
Date: Wed Nov 14 2001 - 20:31:58 EST

  • Next message: Bergman, Ron: "PMP> RE: Print MIB 09"

    Bert, David and Juergen,

    Thank you very much for your advice. The WG has reviewed the discussion and
    agrees that the syntax of prtAlertIndex should not change. We will add a
    note to the description clause for printerV2Alert which explains that this
    object is present only for compatibility with RFC 1759. I believe that all
    issues are now resolved and I estimate we will have a revised MIB by early
    next week.

            Ron Bergman
            Hitachi Koki Imaging Solutions

    -----Original Message-----
    From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
    Sent: Wednesday, November 14, 2001 9:22 AM
    To: bwijnen@lucent.com
    Cc: IMcDonald@crt.xerox.com; Ron.Bergman@Hitachi-hkis.com;
    dbh@enterasys.com; bwijnen@lucent.com; Ron.Bergman@Hitachi-hkis.com;
    harryl@us.ibm.com; RCasterline@crt.xerox.com; pmp@pwg.org;
    paf@cisco.com; ned.freed@mrochek.com
    Subject: Re: Print MIB 09

    >>>>> Wijnen, Bert (Bert) writes:

    Bert> It was not clear to me that people had implemented the object
    Bert> read-only. Are you telling me that you can do a GET
    Bert> prtAlertIndex.1 and that it will return the value 1??

    In fact, this would be something like prtAlertIndex.1.1 since the
    first index in the table is the hrDeviceIndex.

    And it is kind of interesting that the notification printerV2Alert
    contains the prtAlertIndex object but not the hrDeviceIndex object -
    so you still have to unpack the instance identifier of one of the
    varbinds to get access to the device index...

    Anyway, I just did a getnext on prtAlertIndex on one of our HP
    printers and I got back a value of prtAlertSeverityLevel.1.4, which is
    how it should be. A get on prtAlertIndex.1.4 gives me a noSuchName
    error. So there seems to be at least one printer which does not
    implement prtAlertIndex read-only (assuming there is no strange
    access control in place ;-).

    /js



    This archive was generated by hypermail 2b29 : Wed Nov 14 2001 - 20:23:41 EST