On 05. des. 2014 17:24, Ken Tobias wrote:
> 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.
Agree.
> 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.
That is interesting.
> 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.
>
We are very interested in the OIDs you found. One problem we have at the
moment is that we have no way of testing this in an exact matter as we
have no 3850.
I have asked around some and am expecting some feedback shortly. I will
let you know what we discover.