On 04. des. 2014 19:10, Ken Tobias wrote:
The output of the "snmpset" command with "-t <#>" values ranging from 1-30 seconds is:
iso.3.6.1.4.1.9.2.1.54.0 = INTEGER: 1
It returns without any noticeable delay no matter what the timeout value is.
Ok, thanks for testing that.
I don't know if this is relevant but when the port config changes are "saved" from NAV the result is often that the values are set in some ephemeral way, just not in the config file. For example, doing a "sh vlan" will show the ports in question being in the desired VLAN after the "save" despite the running config not reflecting the change.
As far as I know the running config is the non-persistent config, and the startup config is the persistent config. So what you say is that the result of the command 'show run' and 'show vlan' does not display the same information, and for that I have no real explanation. I will ask around and see if anyone else have experienced this.
The timeout responses occur when trying to set multiple values (e.g. description and VLAN, or multiple port VLAN changes) or when executing multiple changes in a short time frame. Are there multiple OIDs for setting values permanently vs. temporarily?
I see. Looking through the code it seems that a write mem is done for each changed interface. This is clearly a bad way of doing it, and also explains some of your issues.
I have created an issue and a patch for this that can be found at https://bugs.launchpad.net/nav/+bug/1399558