I will give this a try today.

As a footnote. On a 3850 stack,  A "write mem" takes quite a while as it replicates the command across each device since each one can become that active stack controller. From the IOS CLI it can take 5-10 seconds normally.




On Thu, Dec 4, 2014 at 2:35 AM, John Magne Bredal <john.m.bredal@uninett.no> wrote:
On 03. des. 2014 21:53, Ken Tobias wrote:
> Here is the screen clip.
>
> Inline image 1

Thank you. That looks quite correct.

>
> This is the text from /var/log/apache2/error.log
>
> [Wed Dec 03 12:49:04 2014] [error] [Wed Dec 03 12:49:04 2014] [INFO]
> [pid=2347 nav.web.portadmin] ktobias: wladc-acc-sw-01:Gi2/0/2 - vlan set
> to 1251
> [Wed Dec 03 12:49:08 2014] [error] [Wed Dec 03 12:49:08 2014] [ERROR]
> [pid=2347 nav.web.portadmin] Error doing write mem on wladc-acc-sw-01:
> Timed out waiting for SNMP response: Timeout
>
> No other log has error data. other_vhosts_access.log has a record of my
> "POST".
>
> Let me know if there is other data I can pull.

This was helpful, thanks.

I think we're down to testing SNMP commands from cli now unfortunately.
The object we use to do a write memory on Cisco devices is
OLD-CISCO-SYS-MIB::writeMem (1.3.6.1.4.1.9.2.1.54) .

If you could try something like this to verify that this fails (this
tries to do a 'write mem' on the device):

snmpset -c <write-community> -v2c wladc-acc-sw-01 1.3.6.1.4.1.9.2.1.54.0 i 1

The interesting part is if adjusting the timeout with -t <seconds> helps
in any way. Try for instance to set the timeout to 5 or 10 seconds.



> On Wed, Dec 3, 2014 at 5:15 AM, John Magne Bredal
> <john.m.bredal@uninett.no <mailto:john.m.bredal@uninett.no>> wrote:
>
>     Hi Ken!
>
>
>     On 01. des. 2014 20:01, Ken Tobias wrote:
>     > I had originally modified the auto-created "unknown" type to be the new
>     > 3850 type. There is no "unknown" type in the DB.
>
>     Just to be absolutely sure that we are understanding each other we would
>     like you to attach a screenshot of the type you edited. Just edit the
>     type again and take a screenshot of the form.
>
>     > 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:
>
>     Random errors are the worst! However, some of the actions in PortAdmin
>     are logged to the Apache error log. If you could post what the logs say
>     when the errors occur, that would perhaps help us.
>
>
>
>     --
>     John Magne Bredal
>     john.m.bredal@uninett.no <mailto:john.m.bredal@uninett.no>
>     +4791897366 <tel:%2B4791897366>
>
>     Abels gt. 5- Teknobyen NO-7465 Trondheim
>
>


--
John Magne Bredal
john.m.bredal@uninett.no
+4791897366

Abels gt. 5- Teknobyen NO-7465 Trondheim