access the web on a WS-3650

[Francisco Leon]

Good morning team, how can I access the web on a WS-3650? I've already created users via SSH and it opens properly, but I can't log in via the web.
Could you help me?
Thank you.

[MHM Cisco World]

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/https/configuration/15-sy/https-15-sy-book.html

You to enable http server 

Check this 

MHM

[Richard Burts]

I am a bit confused about the OP which asks " how can I access the web on a WS-3650". Am I correct in understanding that you want to access the web interface to manage the 3650?

The suggestion by MHM that you need to enable the http (or https) server is a good starting point. We also need to know what else you may  have configured, such as authentication for http/https. It would help us give better advice if you would post the current configuration.

[wajidhassan]

Hello @Francisco Leon  ,

To enable web access on your WS-3650, please ensure the HTTP and HTTPS services are enabled with the following commands:

ip http server

ip http secure-server

Additionally, verify that your user account has privilege level 15. If you are using AAA authentication, confirm it is properly configured to allow web-based logins.

Once these settings are in place, you can access the web interface by navigating to https://<switch-ip> in your browser. Please also ensure there are no ACLs or firewall rules blocking HTTP/HTTPS traffic.

I hope this helps.

[Jens Albrecht · Accepted solution]

Hello @Francisco Leon ,

since access via SSH is already working there are only a few steps to access the WebGUI of a 3650 switch:

! Define a user with privilege level 15:
username admin privilege 15 secret MySecretPassword
!
! Enable access via HTTP:
ip http server
!
! Set authentication for HTTP to the local user database:
ip http authentication local

The local user must have privilege level 15 in order to access the WebGUI.
For SSH this is not necessary because you will get into User Exec mode and can then use the enable secret to get into Privilieged Exec mode. However, you can make changes to the config via the WebGUI so that the user must have privilege level 15 to get access and I assume that might be the reason that your current setup is not working.

This basic setup allows access via HTTP which is acceptable for lab purposes but for production networks you want to allow only HTTPS, of course. In that case you also want to limit access to the WebGUI to your management network.

This can be achieved with the following lines:

! Disable HTTP:
no ip http server
!
! Enable HTTPS:
ip http secure-server
!
! Define the ACL for your management network:
access-list 10 permit 10.1.100.0 0.0.0.255
!
! Use the ACL to restrict access to the WebGUI
! ip http access-class 10

HTH!