It is true that the startup config is the non-volatile version of the config that will be loaded after a reboot or power fail. However all changes are first stored in volatile storage in the running config. A write mem copies the running config to the startup config. If the change isn't in the running config before a write mem, it's not going to be in the startup config after a write mem. This is why I brought it up. If the setting of the values was successful but the write mem was not, it should show up in the running config but not the startup config. This implies that the values were never effectively set in the running config. I've read about dynamic VLANs that are set at run time based on policy. They don't show up in the running config or startup config to the best of my knowledge. That is the only scenario I can think of that would result in a port being added to the vlan tables but not the config file. If we are using the "old Cisco MIB", maybe Cisco changed the default function of that OID to map to dynamic VLAN changes instead of static. Are there more current OIDs that let you choose which type of setting is preferred? Just a guess as this is not my specialty. I did a little looking around in the MIB and there are indeed other/newer OIDs for this, but I couldn't get them to work properly with snmpget and snmpset.
On Fri, Dec 5, 2014 at 12:42 AM, John Magne Bredal <john.m.bredal@uninett.no
wrote:
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
-- John Magne Bredal john.m.bredal@uninett.no +4791897366
Abels gt. 5- Teknobyen NO-7465 Trondheim