WIMS> SendReport - multiple legacy devices

WIMS> SendReport - multiple legacy devices

WIMS> SendReport - multiple legacy devices

McDonald, Ira imcdonald at sharplabs.com
Thu Aug 12 10:08:21 EDT 2004


Hi Harry,
 
You didn't read your change logs.  SendReport has been renamed
to SendReports (plural) and sends a _sequence_ of Report instances,
one for _each_ value of ActionTargetURIs.  Each Report instance
contains the PlanStatus element, which contains PlanLastError,
which is the exact full set of SNMPv2/v3 error codes (e.g., 
'ReadOnly' or 'WrongEncoding').  One of the values of is also
'NoError' (i.e., success).  Either the presence of the optional element
PlanLastError with 'NoError' or the absence of PlanLastError indicates
success of the action for the particular target agent URI.
 
OK?
 

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com 

-----Original Message-----
From: owner-wims at pwg.org [mailto:owner-wims at pwg.org]On Behalf Of Harry Lewis
Sent: Wednesday, August 11, 2004 2:26 PM
To: wims at pwg.org
Subject: WIMS> SendReport - multiple legacy devices



Question related to constructing SendReport for more than one legacy device
by the WIMS proxy... 
Using Ira's Schedule example, below... 

To find out the status of a print device with a legacy
SNMP manager using a WIMS Proxy, specify in a Schedule
a GetElements action as follows:

ActionTargetURIs = "snmp://example.com"

ActionTargetObjects = (sequence of)

 ActionManagedEntityType = "Device"
   (generic Device object planned for WIMS)
 ActionManagedEntityURI = "*" 
   (wildcard for any device at target agent)

ActionRequestedElements = (sequence of)

 ActionRequestedElement = "pwg-sm:PrtViewDeviceStatus"
   (includes every interesting HR MIB state attribute)

 ActionRequestedElement = "pwg-sm:PrtViewGeneralStatus"
   (interesting state attributes from PrtGeneralTable)

ActionParameters (omitted, no vendor extensions needed) 

1. Assume ActionTargetUIRs is a LIST? 
    ActionTargetURIs = "snmp://example1.com"; "snmp://example2.com";
"snmp://example3.com"... 

2. Then, in the SendReport... how is the status (what we are monitoring in
this example) of device "example1" distinguished from the status of device
"example2 or 3"? 
    Is it simple by the ReportSourceURI (multiple - 3 in this case) reports
are returned in the SendReport... each with a different source URI
(snmp://examplex.com) 
    or is the ReportSequenceNumber supposed to correlate, somehow to the
Schedule in helping correlate values to a particular TargetURI (monitored
device)? 

An example of very basic Schedule and SendReport for WIMS Proxy monitoring 3
devices for one or two elements would be very useful! 
---------------------------------------------- 
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
---------------------------------------------- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20040812/0aa69ae8/attachment-0001.html


More information about the Wims mailing list