03-04-2010 04:35 PM - edited 03-06-2019 10:00 AM
I have several Cisco 2950 switches recently updated to IOS 12.1(22)EA13 and am unable to access the web-based device manager on any of them.
1. The Device Manager is installed on the switches from the tar file.
2. The switches are configured with an ip address on the management vlan as well as a default gateway.
3. The switches are configured as an http server.
4. I can successfully ping the switches as well as around my network from the switches.
Any help would be greatly appreciated!
Thanks!
Solved! Go to Solution.
03-04-2010 06:21 PM
Hi,
Take a look at the release notes (below) to see any of these restriction applies to you devices
Also take a look at the resolved caveats section:
Both the Cisco IOS HTTP server and the Cisco IOS HTTPS server use the locally configured enable password (configured by using the enable password or enable secretcommands) as the default authentication mechanism for any request received. Other mechanisms can also be configured to authenticate requests to the HTTP or HTTPS interface. Some of those mechanisms are the local user database, an external RADIUS server or an external TACACS+ server.
HTH
Reza
03-04-2010 05:45 PM
Hi,
Can you post the IOS name you downloaded?
Reza
03-04-2010 05:50 PM
Reza, it was c2950-i6k2l2q4-tar.121-22.EA13.tar
Thanks!
03-04-2010 06:21 PM
Hi,
Take a look at the release notes (below) to see any of these restriction applies to you devices
Also take a look at the resolved caveats section:
Both the Cisco IOS HTTP server and the Cisco IOS HTTPS server use the locally configured enable password (configured by using the enable password or enable secretcommands) as the default authentication mechanism for any request received. Other mechanisms can also be configured to authenticate requests to the HTTP or HTTPS interface. Some of those mechanisms are the local user database, an external RADIUS server or an external TACACS+ server.
HTH
Reza
03-04-2010 10:13 PM
Reza,
I'm ashamed to say that I had already seen most of that, including the password info (which I had for some reason chosen to ignore). The password was indeed my problem.
Thank you for gracefully pointing out the error of my ways. :-)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: