Switch crashing/locking up with editing port descriptions

[Eric Stern]

Was able to look at this today. Turns out the problem was the syslog server. Or more accurately, using a hostname for the remote syslog server.
Because the switch was not connected to the network when you were testing it, it was unable to do a DNS lookup on the hostname for the syslog server. This caused the syslog server to hang waiting for DNS to complete, which in turned caused any other processes (that were trying to log) to hang waiting for the syslog server to respond. If you wait long enough the DNS lookup finally fails which allows the syslog server to do a bit of work, but it almost immediately tries to do the DNS lookup again and hangs again.

So, the quick workaround is to use an IP address for the syslog server instead of a hostname. I will investigate an actual fix.

[jbaird]

Eric - thanks for helping with this! I was going down the same path, but didn't have time to finish testing. I'll re-test and let you know the results.

[jbaird]

Hi - just a confirmation that this fixed the issue we were seeing.

Thanks again.