Wireless Access

Hi all,

I'm wondering if someone can supply the command(s) to enable or open up the 160 MHz Frequency in Wi-Fi 6 while I wait for my AP Instance console cable to arrive.

Sincere gratitude in advance

Loni 

using Aruba Central managing an Instant AP,



------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: 10/4/2022 6:03:00 AM
From: ariyap
Subject: RE: 160 MHz enable

using Aruba Central managing an Instant AP,



------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Can you share a screenshot of what you see on your system? Also, what version of software are you running?

------------------------------
Dustin Burns

Lead Mobility Engineer @Worldcom Exchange, Inc.

ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
If my post was useful accept solution and/or give kudos
------------------------------

Original Message:
Sent: Oct 04, 2022 06:56 AM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thanks for the effort but my AP GUI doesn't have the 160 MHz support button, it is only 80 MHz. 

Original Message:
Sent: 10/4/2022 6:03:00 AM
From: ariyap
Subject: RE: 160 MHz enable

using Aruba Central managing an Instant AP,



------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

what AP model are you using also tell us your firmware version?

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 04, 2022 07:06 AM
From: Dustin Burns
Subject: 160 MHz enable

Can you share a screenshot of what you see on your system? Also, what version of software are you running?

------------------------------
Dustin Burns

Lead Mobility Engineer @Worldcom Exchange, Inc.

ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
If my post was useful accept solution and/or give kudos
------------------------------


Original Message:
Sent: Oct 04, 2022 06:56 AM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thanks for the effort but my AP GUI doesn't have the 160 MHz support button, it is only 80 MHz. 

Original Message:
Sent: 10/4/2022 6:03:00 AM
From: ariyap
Subject: RE: 160 MHz enable

using Aruba Central managing an Instant AP,



------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

I'm using Aruba AP -555 (RW) Unified AP. Attached is a CLI using putty software but the commands I used didn't work as you see on the screenshot. Commands are as follows;

*show ap allowed-channels 64 New Zealand ap-type ap-555
*config arm 160mhz-support
*conf t arm 160mhz-support exit exit commit



Original Message:
Sent: Oct 05, 2022 12:48 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

what AP model are you using also tell us your firmware version?

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 04, 2022 07:06 AM
From: Dustin Burns
Subject: 160 MHz enable

Can you share a screenshot of what you see on your system? Also, what version of software are you running?

------------------------------
Dustin Burns

Lead Mobility Engineer @Worldcom Exchange, Inc.

ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
If my post was useful accept solution and/or give kudos


Original Message:
Sent: Oct 04, 2022 06:56 AM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thanks for the effort but my AP GUI doesn't have the 160 MHz support button, it is only 80 MHz. 

Original Message:
Sent: 10/4/2022 6:03:00 AM
From: ariyap
Subject: RE: 160 MHz enable

using Aruba Central managing an Instant AP,



------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is the putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply


Original Message:
Sent: Oct 04, 2022 07:06 AM
From: Dustin Burns
Subject: 160 MHz enable

Can you share a screenshot of what you see on your system? Also, what version of software are you running?

------------------------------
Dustin Burns

Lead Mobility Engineer @Worldcom Exchange, Inc.

ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022
If my post was useful accept solution and/or give kudos
------------------------------


Original Message:
Sent: Oct 04, 2022 06:56 AM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thanks for the effort but my AP GUI doesn't have the 160 MHz support button, it is only 80 MHz. 

Original Message:
Sent: 10/4/2022 6:03:00 AM
From: ariyap
Subject: RE: 160 MHz enable

using Aruba Central managing an Instant AP,



------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

Original Message:
Sent: 10/12/2022 12:25:00 AM
From: ariyap
Subject: RE: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

you dont need to be in config mode. so exit out of there.
run these two commands.

PS-Lvl1-bb:bb# sh ap bss-table

PS-Lvl1-bb:bb# sh ap allowed-channels

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 12, 2022 09:15 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

Original Message:
Sent: 10/12/2022 10:15:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you dont need to be in config mode. so exit out of there.
run these two commands.

PS-Lvl1-bb:bb# sh ap bss-table

PS-Lvl1-bb:bb# sh ap allowed-channels

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 09:15 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Oct 12, 2022 10:14 PM
From: Ariya Parsamanesh
Subject: 160 MHz enable

you dont need to be in config mode. so exit out of there.
run these two commands.

PS-Lvl1-bb:bb# sh ap bss-table

PS-Lvl1-bb:bb# sh ap allowed-channels

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 09:15 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

earlier you mentioned, you had disabled 80MHz, please re-enable it
Also ensure your "160mhz-support" is set to auto
once you do these changes then send us the output "sh ap bss-table" and " sh ap allowed-channels"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Oct 12, 2022 10:56 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Here is the list of available channels

Original Message:
Sent: Oct 12, 2022 10:14 PM
From: Ariya Parsamanesh
Subject: 160 MHz enable

you dont need to be in config mode. so exit out of there.
run these two commands.

PS-Lvl1-bb:bb# sh ap bss-table

PS-Lvl1-bb:bb# sh ap allowed-channels

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 09:15 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 11, 2022 10:36 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

I'm using Aruba AP -555 (RW) Unified AP
802.11ax . Using putty connect to the AP console to do the configuration through CLI. Below is putty screen and it didn't work with the following command;
config t arm 160mhz- support commit apply

Original Message:
Sent: 10/13/2022 8:10:00 AM
From: ariyap
Subject: RE: 160 MHz enable

earlier you mentioned, you had disabled 80MHz, please re-enable it
Also ensure your "160mhz-support" is set to auto
once you do these changes then send us the output "sh ap bss-table" and " sh ap allowed-channels"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 10:56 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Here is the list of available channels

Original Message:
Sent: Oct 12, 2022 10:14 PM
From: Ariya Parsamanesh
Subject: 160 MHz enable

you dont need to be in config mode. so exit out of there.
run these two commands.

PS-Lvl1-bb:bb# sh ap bss-table

PS-Lvl1-bb:bb# sh ap allowed-channels

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 09:15 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: 10/13/2022 8:10:00 AM
From: ariyap
Subject: RE: 160 MHz enable

earlier you mentioned, you had disabled 80MHz, please re-enable it
Also ensure your "160mhz-support" is set to auto
once you do these changes then send us the output "sh ap bss-table" and " sh ap allowed-channels"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------


Original Message:
Sent: Oct 12, 2022 10:56 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Here is the list of available channels

Original Message:
Sent: Oct 12, 2022 10:14 PM
From: Ariya Parsamanesh
Subject: 160 MHz enable

you dont need to be in config mode. so exit out of there.
run these two commands.

PS-Lvl1-bb:bb# sh ap bss-table

PS-Lvl1-bb:bb# sh ap allowed-channels

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 09:15 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Original Message:
Sent: Oct 12, 2022 09:09 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Current version: 8.7.1.3_79817 (Digitally Signed - Production Build)

I run " show ap bss-table" and it says Parse error ( point to the word " show")

Original Message:
Sent: 10/12/2022 8:58:00 PM
From: ariyap
Subject: RE: 160 MHz enable

what is the firmware version you are running on your AP-555? also can you paste the output "show ap bss-table"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 07:38 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

Thank you again, I run this command, "160mhz-support  contiguous-only" and exit and then run "commit apply". It seems it s working as it says, "config committed". but when I check on the AP GUI, AP still broadcast in 36E (80mhz). I disable 80mhz as well as changed the channel to 36S (160mhz) as shown in the attached screenshot. However, the RF didn't allow the change I made even though I did the config on CLI. Even after rebooting my AP, it doesn't change anything.

Thanks 

loni 

Original Message:
Sent: 10/12/2022 5:40:00 PM
From: ariyap
Subject: RE: 160 MHz enable

you know you can do question mark and it will give you further options

PS-Lvl1-bb:bb (ARM) # 160mhz-support ?
<mode> mode{none|auto|contiguous-only|non-contiguous-only}

PS-Lvl1-bb:bb (ARM) #

if it is easier for you, do it through the WebUI.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.


Original Message:
Sent: Oct 12, 2022 05:25 PM
From: Maloni Tu'itupou
Subject: 160 MHz enable

As you may see in this screenshot when I run the command, " 160mhz-support" it says, "incomplete command". Any idea why or what I did wrong here?

Thank you for all the assistance and I do appreciate it so much.

Loni 

Original Message:
Sent: Oct 12, 2022 12:24 AM
From: Ariya Parsamanesh
Subject: 160 MHz enable

The correct commands are
- show ap allowed-channels

while in config mode, you should first type "arm" and then enter and then 160M command

PS-Lvl1-b2:5b# conf t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
PS-Lvl1-b2:5b (config) # arm
PS-Lvl1-b2:5b (ARM) # 160mhz-support

and then once you are out of the config mode, to save the changes use "commit apply"

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.