Network Management

 View Only
last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

Aruba 2930 no web interface

This thread has been viewed 7 times
  • 1.  Aruba 2930 no web interface

    Posted 5 hours ago

    Hi, everything I have read tells me the web interface should be enabled by default, but it is not working.

    I can ssh to the switches, if I go onto the switch and run "telnet <localIP> 22" I get the ssh banner, if I do the same test on port 80 and 443 it just times out. sh run | i http and sh run | i web doesn't bring up any results.

    Its just a basic switch single mgmt Ip, no vrfs's in fact I have 10 of them none of them have a responding web interface and they are on varying firmware's. Is it something to do with password manager?

      



  • 2.  RE: Aruba 2930 no web interface

    EMPLOYEE
    Posted 5 hours ago

    I have the following configuration in my switch:

    no web-management
    web-management ssl

    You may try to run: 'web-management ssl' or 'web-management plaintext' to explicitly enable https (or plaintext = http) and see if an error shows up indicating why it may not have been enabled. I can imagine that you need to set a manager password before you can enable the web-management, but not sure. Setting a manager password: "password manager".



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: Aruba 2930 no web interface

    Posted 4 hours ago

    Ok my apologies, seems port 80 was open it was a firewall block! even though no response on port 80 using the built in telnet client, maybe that's just how it is.