> Q1: Which of the following the SNMPv3 engine does: a. If the product > receives response messages, the product shall conduct a timeliness > check on the SNMPv3 message. b. An SNMPv3 engine shall perform time > synchronization using authenticated messages.
Yes, the Net-SNMP implementation does these (as every v3/USM implementation should). > Q2: The SNMPv3 user is created and the user passphrase is localized > using the snmpv3_get_engineID() api and current engine id. If the > snmpEngineID is changed would this require the user to be modified to > have the passphrase to be localized to the new engine id else it will > not work, or it will continue to work with the old localized > passphrase. The users need to be recreated on an engineID change. Generally because of this you should never want to change the engineID. engineID changes are simply a pain, so try to avoid it. > Q3: Is the snmpMessageProcessingModel=3 the messages processing model? Yes. > Q4: Is the following statement true? When using msgID for correlating > Response messages to outstanding Request messages, the SNMPv3 engine > shall use different msgIDs in all such Request messages that it sends > out during a 150 second Time Window That's always a safe thing to do no matter whether using v3 msgIDs or the PDU's request-id. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
