On Fri, 2005-06-24 at 11:55, Jeetendra Singh wrote: > Consider that my agentX master agent is running for *days*. The > sysUpTime accordingly goes into days. I *now* enable my device's port > and the device-up trap is sent by my subagent to the manager via > master agent. > 1. What should be the value of "*LastChange" in this case?
The value of 'sysUpTime' at the time that you enabled the interface. Just as it says in the definition of the LastChange object. > 2. If sysUpTime is agent's time (and in net-snmp it is filled by > master agent), it will be in days in my trap. Correct. > "*LastChange" as per its definition will be > - this sysUpTime value(which is in days) OR > - the uptime of my device's port (which is a few seconds)? The sysUpTime value (in days) - just as it says in the MIB definition. > My master agent is running for days but my application (containing the > subagent) which is currently being tested gets killed and restarted > every now and then. I have observed a very strange reading. My > sysUpTime and *LastChange parameters display same values of timeticks > in all my traps. How can this be possible? Pls note, my master agent > and subagent are two separate processes. But they combine to supply the "network management portion" of the system. So the network management portion *as a whole*, has been running for several days, even if selected bits of it haven't been active all of the time. > As per me, this can only happen if after coming up, the subagent is > asking for the master agents uptime/start-time? Correct. See the AgentX specification for details. > what purpose does *LastChange really solves? It allows the manager to know when that particular interface was last taken up or down (or whatever the LastChange object actually monitors). > Or is it that if the manager wants to know the uptime of my managed > resource, the *LastChange is *not* the right parameter? No - the LastChange object is *not* the right parameter for telling how long the management system as a whole has been running. That's what sysUpTime is for. Neither is it necessarily the right parameter for telling how long a particular subsystem has been running. There would typically be other MIB objects for that, such as the two 'agentx*OpenTime" objects in the AGENTX-MIB (which we don't actually implement!) The LastChange object reports when a particular aspect of a particular subsystem was last *changed*. That's not the same as how long it's been running - it's quite possible to make changes to a running subsystem without taking it down. sysUpTime monitors the uptime of the system. *LastChange monitors when changes are made to a particular subsystem. They both do exactly what it says on the tin. Dave ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
