I had originally modified the auto-created "unknown" type to be the new 3850 type. There is no "unknown" type in the DB.

I have upgraded NAV to 4.2.1 and I now get one the following errors (randomly) on the port configuration page when attempting to set the VLAN / description on a port on the new 3850:

Error setting vlan: SNMP Error: wrongType (The set datatype does not match the data type the agent expects)

Error setting vlan: Timed out waiting for SNMP response: Timeout

Error setting ifalias: Timed out waiting for SNMP response: Timeout

Thanks!

On Fri, Nov 28, 2014 at 1:26 AM, Morten Brekkevold <morten.brekkevold@uninett.no> wrote:

On Thu, 27 Nov 2014 08:47:02 -0800 Ken Tobias <kentobias@wcn.co> wrote:

> 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?

If you manually created a device type with this sysObjectID after my
last post, you will have created a duplicate (not sure how you were able
to, though - maybe because the sysObjectIDs are normally stored with a
preceding dot?).

ipdevpoll will have automatically created a new type for
.1.3.6.1.4.1.9.1.1745 as soon as it was seen. This type will have that
very same value (.1.3.6.1.4.1.9.1.1745) as its typename, and the sysDecr
value of the device it was first discovered on will have been used as
its description. "unknown" will be the vendor.

You need to find this auto-created type using the SeedDB tool. Edit its
name and description into something more useful, and change its vendor
from "unknown" to "cisco". That should be all you need to do for Port
Admin to use the proper Cisco MIBs for configuring VLANs on your new
3850s.

--
Morten Brekkevold
UNINETT