[AGENT++] Timeout seen for GETNEXT when an object is excluded from a view

[Maurice Plunkett]

Hi,

 

Is it possible to make GETNEXT more efficient in the case when the target
object is excluded from a user's view?

 

For example,

If ifTable (1.3.6.1.2.1.2.2) is excluded from view via an entry in the
vacmViewTreeFamilyTable, a GETNEXT request to ifNumber.0 results in the agent
effectively walking the ifTable until it finds the next object after the
ifTable.

 

This may take a relatively short period of time for the ifTable, so the
client may not time-out.

 

However, if larger MIB trees are excluded from a view, such as the Host
Resource MIB or an enterprise MIB, this delay can be too long.  It may also
appear to a client that the agent has died.  It would be best if the client
did not experience such long delays.

 

Perhaps one work-around would be for the agent to do a GET operation on the
object that is lexicographically after the excluded view and start from
there...

 

Regards,

            Maurice.