Setting the vlan 1 as the management vlan on the cloud AP in Cloudnet scenario

Null

How to set the vlan 1 as the management vlan on the cloud AP in Cloudnet scenario

First of all, it is not recommended to modify the management VLAN on the cloud AP to another VLAN. Many management mechanisms are based on VLAN 1, and changes may lead to abnormal management packet interactions in certain scenarios, increasing instability factors for network devices. 

The standard configuration method is to change the PVID of the trunk port on the upstream switch to the management VLAN required for the service. This way, the AP still uses interface VLAN 1 to obtain the management address. For the management network, the AP is within the management VLAN.

For certain use cases, when VLAN 1 on the AP must be used as a service VLAN, the recommended configuration is as follows, using management VLAN 111 as an example:

1. The cloud AP still defaults to using VLAN 1 to come online on Cloudnet. The configuration of the downstream port on the upstream switch should be:

#
port trunk permit vlan all
port trunk pvid vlan 1
#  

Ensure that addresses can be obtained and internet can be connected in both VLAN 1 and VLAN 111.

2. After the cloud AP comes online, make the following configuration on Cloudnet:
   Add a management VLAN in the VLAN Setting of the cloud APs, as shown in the figure below for VLAN 111.

Create a new CLI configuration script in the CLI of Cloud APs.

Select the corresponding AP model. As shown in the figure, WA6126.

Note: The following configuration script will briefly take the AP offline.
Specific configuration script:

return
system-view
vlan 111
interface vlan 111
ip address dhcp-alloc
interface vlan 1
shutdown
return  

After the configuration is successfully applied, you can see the record of the successful configuration.

Known existing issue:
The management address on Cloudnet is uploaded via AP using VLAN 1. After modifying the management VLAN, the address does not display correctly.