Network Management

 View Only
last person joined: 9 hours ago 

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

interface mgmt

This thread has been viewed 18 times
  • 1.  interface mgmt

    Posted Mar 26, 2024 05:06 PM

    Doc says I should use interface mgmt to configure IP for ssh/https. CMD invalid input mgmt. Also, why does this forum not have a search function? I know this issue has to have been addressed many times since the docs are not accurate. 



  • 2.  RE: interface mgmt

    Posted Mar 26, 2024 05:34 PM

    What equipment model? 

    There is a native search tool - top right hand corner, orange magnifying glass. 

    These forms can also be successfully queries using Google as well. 



    ------------------------------
    If my post was useful, please Accept Solution and Give Kudos.
    ------------------------------
    Zak Chalupka
    Principal Engineer - HPE Aruba
    ACDX | ACMP | ACSP | ACCP
    wifizak@hpe.com
    ------------------------------
    Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
    ------------------------------



  • 3.  RE: interface mgmt

    Posted 30 days ago

    6000 24G Class4 PoE 4SFP 370W Switch

    DT-Retread# show running-config 
    Current configuration:
    !
    !Version ArubaOS-CX PL.10.08.1010
    !export-password: default
    hostname DT-Retread
    user admin group administrators password ciphertext *****************4+fpD1RqjBGbNk2K+WK9OzTS2pX
    ntp server pool.ntp.org minpoll 4 maxpoll 4 iburst
    ntp enable
    !
    !
    !
    !
    !
    !
    ssh server vrf default
    vlan 1
    vlan 2
        voice
    vlan 3-5
    spanning-tree
    interface 1/1/1
        no shutdown
        vlan trunk native 1
     -- MORE --, next page: Space, next line: Enter, quit: q                                                                     vlan trunk allowed all
    interface 1/1/2
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/3
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/4
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/5
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/6
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/7
        no shutdown
     -- MORE --, next page: Space, next line: Enter, quit: q                                                                     vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/8
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/9
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/10
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/11
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/12
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/13
     -- MORE --, next page: Space, next line: Enter, quit: q                                                                     no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/14
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/15
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/16
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/17
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/18
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
     -- MORE --, next page: Space, next line: Enter, quit: q                                                                 interface 1/1/19
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/20
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/21
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/22
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/23
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/24
        no shutdown
        vlan trunk native 1
     -- MORE --, next page: Space, next line: Enter, quit: q                                                                     vlan trunk allowed all
    interface 1/1/25
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/26
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/27
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface 1/1/28
        no shutdown
        vlan trunk native 1
        vlan trunk allowed all
    interface vlan 1
        ip address 192.168.120.15/24
        no ip dhcp
    !
    !
    !
     -- MORE --, next page: Space, next line: Enter, quit: q                                                                 !
    !
    https-server vrf default
       DT-Retread#                                                           exit




  • 4.  RE: interface mgmt

    Posted 30 days ago

    Aruba CX 6000 series switches do not have dedicated management interfaces. 

    Management for these switches would use your Layer3 VLAN Interface IP (SVI)



    ------------------------------
    If my post was useful, please Accept Solution and Give Kudos.
    ------------------------------
    Zak Chalupka
    Principal Engineer - HPE Aruba
    ACDX | ACMP | ACSP | ACCP
    wifizak@hpe.com
    ------------------------------
    Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
    ------------------------------



  • 5.  RE: interface mgmt

    Posted 30 days ago

    We are only using it as an L2 switch. Going from procure to this is going to be a challenge I guess.  Seems like I should be able to access it https/ssh via 192.168.120.15. I cannot. I also have no arp entries even though I am in the same vlan and have internet access. I cannot ping the SonicWall gateway or the switch. Very odd. 




  • 6.  RE: interface mgmt

    Posted 30 days ago

    You may have a port VLAN configuration issue in that case.

    The 6000 switch is an L2 switch. You would not use it to route user/production traffic, that SVI is for management only. 

    There would be no ARP entries on the switch in this topology. Do you see MAC's in the table for VLAN 1 on that switch? Can you ping something on VLAN1 from that switch?



    ------------------------------
    If my post was useful, please Accept Solution and Give Kudos.
    ------------------------------
    Zak Chalupka
    Principal Engineer - HPE Aruba
    ACDX | ACMP | ACSP | ACCP
    wifizak@hpe.com
    ------------------------------
    Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
    ------------------------------



  • 7.  RE: interface mgmt

    Posted 29 days ago

    Found the issue. Made typo when setting up the firewall. It was supposed to be 192.168.120.1  . What it was 192.168.20.1 .  The switch is fine and the config is working. Sorry