Wired Intelligent Edge

 View Only
last person joined: 2 days ago 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

change aoscx port number

This thread has been viewed 31 times
  • 1.  change aoscx port number

    Posted May 11, 2022 05:25 PM

    # show version
    Version : Virtual.10.05.0020


    1. change int vrf mgmt ssh port from port 22 to 2222
    2. change https GUI from 443 to 8443


    1. I can't find in pdf on how to do that
    maybe for #1 I can do session remapping like this
    2. https://community.arubanetworks.com/community-home/digestviewer/viewthread?GroupId=13&MID=20666&CommunityKey=ff734391-dcd7-4802-93c6-e0913abba875&tab=digestviewer

    but it seems not the same command in aoscx


    Nawir Bunai

  • 2.  RE: change aoscx port number

    Posted May 12, 2022 07:00 AM
    This is not possible at the moment.
    The workaround with session remapping is for the wireless AOS . The AOS-CX doesn't support session ACLs with destination NAT.

    Please note that there is a new idea in Aruba Innovation Zone which suggests adding this feature in a future release of ArubaOS-CX.
    The idea is from 3 May 2022 and has only 3 votes so far. Feel free to login and vote for the idea so that it gets more visibility.

    Emil Gogushev

  • 3.  RE: change aoscx port number

    Posted 16 days ago
    Hello Emil_G,
    Has there been an update on how to configure the ssh port? I can't seem to find anything in the guide. Not sure why this has been so difficult compared to the 2930 series CLI command structure. I would greatly appreciate the help with this.

  • 4.  RE: change aoscx port number

    Posted 16 days ago
    The  idea in Aruba Innovation Zone has still the status "new idea"
    There are only 7 votes so far.

    This means that there is not really such a big demand for this feature. As mentioned in your new question, there are other, more effective ways to secure the SSH access.​​