perfsonar development work

[Jason Zurawski <>]

Rafael & Loukik;

> You can find at 
> http://wiki.perfsonar.net/jra1-wiki/index.php/Request_and_Reply_SNMP-MP 
> the new request and response examples (as we discussed) about a "more 
> complex" get at SNMP MP and NeTraMet Collector integration.

In the first example (Request for key - MetadataKeyRequest) why is there 
a datum element in the sent data trigger?  It has been a while since I 
have looked at these examples and I am not sure why that is needed in a 
key request.

In the NeTraMet examples:

Could you include a little bit more in the descriptions of what each 
example would be used for (use cases or something similar)?

I am still unconvinced to the need for 'type' designations in the 
request file (i.e. <parameter name="OID_Alias" 
type="numeric">sysUpTime</parameter>), but if you are positive you must 
do something like this I would suggest it to be:

<parameters>
 <parameter name="OID_Alias">sysUpTime</parameter>
 <parameter name="OID_Type">timeticks</parameter>
</parameters>

To avoid having a more complex parameter. 

I am guessing that there can be only one item requested per SNMP.Get?  
Otherwise it would be impossible to map your requested type parameters 
to the datum elements returned?

For the ' Request/Response for data request with a "table OID"' example, 
the eventType should be used to indicate you are getting a table instead 
of just a standard get (SNMP.Table or something similar).  Maybe this is 
different in for NeTraMet, but doing 'snmpget ... atTable' fails on my 
systems when 'snmptable ... atTable' will succeed. 

-jason