---------- Forwarded message ----------
Date: Mon, 2 Dec 1996 10:12:26 -0800 (PST)
From: Steve Waldbusser <stevew at ins.com>
To: Tom Hastings <hastings at cp10.es.xerox.com>
Cc: pwg at pwg.org, Joe_Filion at mc.xerox.com
Subject: Re: PWG> ISSUE: Add hrDeviceIndex as a varBind to the Printer MIB?
On Mon, 2 Dec 1996, Tom Hastings wrote:
> >From the minutes of the New Orleans meeting:
>> The issue was raised (again) regarding the fact that Printer MIB traps do
> not include the hrDeviceIndex. Without the hrDeviceIndex in the trap,
> there is no way to discriminate among multiple printers managed by a
> single SNMP agent. We may need to add another varBind object for
>> ISSUE: Who will submit the draft text for this new (and critical)
> varbind object? (This was not discussed during the meeting??)
>>> I had the action item to try to explain how an NMS could determine which
> device caused a trap from the trap information without having to poll all
> devices supported on the host that trapped. While the trap OID itself
> (printerV2Alert) does not include the hrDeviceIndex, each of the varBinds do.
> So each of the varBinds: prtAlertIndex, prtAlertSeverityLevel,
> prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, and prtAlertCode shall
> contain the
> hrDeviceIndex in them. So an NMS receiving the trap need only remove
> the last arc from the OID for one of them, say the prtAlertIndex, to get
> the next to last OID arc which contains the value for hrDeviceIndex
> that corresponds to the device that generated the trap.
>> Do others agree?
Yes, this is how we designed it in the original RFC.