I've got a Cisco router that I absolutely hate, but I'm forced to work with it.

When using the web interface to make configuration changes about 60-70% of the time I'll get errors on the page. The errors are causing the web forms do not load properly. Re-navigating to the page or simply refreshing (several times) will get rid of them.

I doubt it is a browser security setting, as reloading the page often gets rid of them. It's not isolated to an individual router because I've seen this problem across four routers (same model) now. The errors seem to be totally random as well. Anyone else experience this? Any ideas?

10/11/2007 8:22:37 AM

can't you just use the command line for configuration?

10/11/2007 8:34:42 AM

I have never used the web interface on a cisco router, but... What web browser are you using? Have you tried using a different browser?

10/11/2007 8:41:13 AM

No. I have to prepare a doc for someone that will not be using the command line. So far it reads: "when you get errors, refresh until they no longer appear" and "if you get an error, go back to the home page and re-navigate to the page in question until no errors appear"

Seriously, it's an annoying process.

10/11/2007 8:43:57 AM

the document should read "quit using the goddamned web interface and use the fucking command line, you douche."

10/11/2007 9:42:10 AM

That'd be nice, but not an option in this case.

You'd think the web interface would be up to snuff though. 30-40 minutes to make a few simple changes to the configuration all because the page loads with errors (closer to 90% of the time) is ridiculous.

They'd be better off not including any web interface at all if it's that lousy.

10/11/2007 9:44:10 AM

seriously though, i've never found the web interfaces for any enterprise level cisco any brand equipment to be worth a shit. i've always ended up using the cli

[Edited on October 11, 2007 at 9:46 AM. Reason : x]

10/11/2007 9:46:21 AM

I'll be the first to say that we suck at GUIs and web interfaces.

why isn't the CLI an option for the person you're preparing a doc for?

Also, definitely open a TAC case.

10/11/2007 10:07:38 AM

The people that are asking for the document insist on the web interface. My thought is that if they don't want to move away from using the web interface then they have to be prepared to deal with the problems that creates.

10/11/2007 10:15:10 AM

i just set up a ubuntu server with no gui

the command line takes some getting used to, but im really starting to like it

10/11/2007 10:44:43 AM

1) Code a webpage to have a telnet client.
2) automate connection and authentication to a single submit button (ironically, the hardest part of all this)
3) $profit. A web interface that doesn't suck.

10/11/2007 10:46:10 AM