On 20 May 2010 09:48, Boris Zweimueller <bo...@zweimueller.ch> wrote: > There will be only one management console accessing the device.
Assumptions like this have a tendency to come back and bite you at a later date! Once you've shipped your systems out, you may not have much control over what your customers want to do with them. > It is used just to query and set configuration of the device (e.g. like a > router). Well, a router would typically also report information such as traffic statistics, and maybe environmental information (such as operating temperature or fan speed). If you've got two physical boxes, then the sensor information could easily be different. And traffic statistics could easily be different if the two boxes were queried a short time apart. > I don't understand why for this setting there could be different responses in > normal operation (devices operate correctly) ? SNMP is about more than just configuration settings. (In fact, this is probably the least widely used element!) > I only a problem, when e.g. for a SET command, one device ist doing it, and > the other can not for whatever reason. I'm not sure what to do then. Some > kind of undoing is probably to much work to implement. As far as I know, > SNMP dows not have any undo support? SNMP SET requests are regarded as "atomic" - the assignments should all succeed or all fail. So no - there is no separate UNDO step within the SNMP protocol. But the internal implementation of SET within the Net-SNMP agent (and probably many others) *does* include an UNDO phase. See the documentation on the project web site for details. Dave ------------------------------------------------------------------------------ _______________________________________________ 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
