★ The configuration of the cloud AP is cleared after it goes online on cloudnet

2023-06-30 01:28:34 Published
  • 0 Followed
  • 0Collected ,745Browsed

Network Topology

Not involving

Problem Description

Basis: WA530-WW is imported on Cloudnet platform with default configuration, and working normally.

It is needed to manage APs through vlan 80 untagged (or any other), not vlan 1 as usual. So we configure through CLI Bulk config a template with other requirements, as below.

#

return

system-view

vlan 80

name GESTIOAP

quit

interface Vlan-interface80

ip address dhcp-alloc

mtu 1400

quit

interface GigabitEthernet1/0/1

port trunk pvid vlan 80

quit

#

There are several other wireless profiles, each one through different vlan, including vlan 1.

 

Result after apply: It works correctly and the AP is working as expected. But after few minutes, some items related to that vlan 80 stop working, and AP lost IP connectivity. When reviewing on AP console port appears that:

Øvlan 80 was removed, so vlan-interface goes down.

Or

Øvlan PVID 80 on interface GigabitEthernet1/0/1 was removed, changed to vlan 1:

 

Configuration after AP loses connection:                                                                                                                                              

[AP2]inter g1/0/1                                                              

[AP2-GigabitEthernet1/0/1]disp this                                            

#                                                                               

interface GigabitEthernet1/0/1                                                 

 port link-type trunk                                                          

 port trunk permit vlan 1 to 4000                                               

 port-isolate enable                                                           

#                                                                              

return                                                                          

[AP2-GigabitEthernet1/0/1]quit                                                                                                                    

sys                                                                       

System View: return to User View with Ctrl+Z.                                  

[AP2]dis ip inter b                                                             

*down: administratively down                                                   

(s): spoofing  (l): loopback                                                   

Interface                Physical Protocol IP Address      Description         

Vlan1                    *down    down     --              --                  

Vlan80                   up       up       192.168.80.97   --                  

Vlan4071                 down     down     10.40.71.1      --                  

Vlan4094                 down     down     10.40.94.1      --                  

 

 

Process Analysis

After confirming with R&D, the cause of the problem is:

After the cloud AP is online on the cloudnet and the cloud synchronization function is enabled, the implementation method of obtaining the IP address is shown in the figure below, and the management vlan only supports vlan 1, so the configuration of changing the management vlan to another vlan will be cleared. It also doesn"t work if a static IP is configured.

 

The way APs get their addresses:

 

VLAN interfaces used

Port Type

DHCP allocation

Interface vlan1

All uplink ports

Trunk vlan 1-4000, pvid1

Static IP

Interface 4093 (Reserved VLAN)

G1/0/1

Trunk vlan 1-4000 4093, pvid 4093

PPPoE

Interface 4093 (Reserved VLAN)

G1/0/1

Trunk vlan 1-4000 4093, pvid 4093

VLAN management:

·           User management range: 1-4000 (vlan 1 cannot be deleted)

·           Does not support enabling layer 3 route ports

 


Cloud Sync On:

The device synchronizes the configuration from the cloud periodically, with the cloud configuration taking priority, every 12 hours.

Cloud Sync Off:

The synchronization of configurations is canceled and the device"s local configuration takes precedence, but it can still use batch configuration templates or CLI Helper to send configurations to the device that will not be synchronized by the cloud.


Solution

1.       Turn off the cloud synchronization function, because the cloud AP will synchronize the configuration to the cloudnet wireless configuration page after it is turned on. Once a configuration different from this page is found, it will be synchronized by cloudnet and the configuration will be lost.

2.       If the cloud synchronization function cannot be disabled, you can add the relevant vlan configuration on the cloud AP wireless configuration page, configure a service template that references other vlans and enable it, so as to ensure that the vlan will not be deleted. The specific method is as follows:

·           Select a service template on cloudnet and configure vlan 80. SSID can be hidden. Make sure cloudnet will not delete vlan 80 related configuration.

·           Configure pvid 1 on the AP uplink port to allow vlan 80 to pass. Configure pvid 1 on the downlink interface of the switch and permit vlan 80. Let the management vlan go in and out of the device with vlan tags, and the business vlan 1 strips the vlan tags in and out of the device.

Please rate this case:   
0 Comments

No Comments

Add Comments: