Sorry I wasn't clear in the first post. The changes I refer to are those made with the NAV Port Admin Tool. The objective being to have the "description" and "switchport access vlan ???" values change on individual ports.

The OID IS different for the new 3850s: 1.3.6.1.4.1.9.1.1745. The older version is: 1.3.6.1.4.1.9.1.1641. I created a new device type in the Seed DB with the existing vendor "cisco", which is the same as the old device type. Is there more I have to do to have NAV recognize the new device type as Cisco?


On Wed, Nov 26, 2014 at 11:57 PM, Morten Brekkevold <morten.brekkevold@uninett.no> wrote:
On Tue, 25 Nov 2014 17:40:58 +0100 (CET) <kentobias@wcn.co> wrote:

> Great work on NAV, appreciate all the hard work.

Hi, and thanks!

> I've added a new group of Cisco 3850s to a network and now changes to
> port information aren't saved. Description information is not saved at
> all.

When you are talking about changes to port information and description,
are you talking about NAV's collection of these, or of configuring these
through NAV's Port Admin tool? I'm guessing the latter...

> VLAN information is changed, but only ephemerally, not in the actual
> port configuration. This means that the VLAN information isn't
> preserved across reloads.

Some operations are vendor proprietary in Port Admin - we use Cisco
proprietary MIBs to achieve VLAN changes to Cisco ports, and also to
instruct the device to perform a "write mem" after changes have been
made.

> The only difference that I can find are the IOS version and VTP. The
> previous 3850s are running 3.3.x and the new 3850s are running 3.6.1.
> The new 3850s are using VTP v3 whereas the current 3850s are not.

Do your new 3850s and your old 3850s share the same device type in NAV?
(Take a look at them in IP Device Info, and click their "Type"
descriptions).

Sometimes, newer software or hardware revisions will have different SNMP
sysObjectID's. If the new devices reported sysObjectID's unknown to NAV,
ipdevpoll will have autocreated new device types for these, attaching
them to the "unknown" vendor id.

There is a pitfall here: Port Admin will look at a device's type's
vendor id to determine which operations to use to perform its work. If
the device type's vendor id is not "cisco", it will not use Cisco
proprietary MIBs to perform its changes.

If this is your problem, you can clean up the type definitions using
SeedDB.

> There are no error messages generated during the port configuration
> that I can find.

I cannot speculate as to why no error messages were generated. I'm not
that familiar with the inner workings of Port Admin - we'd have to do
some testing.


--
Morten Brekkevold
UNINETT