История страницы

...

2. Copy the file to the USB/MMC storage that is currently in use.

...

1. Format USB/MMC partition as FAT32.
2. File with a previously created backup copy of the controller configuration must be placed on the USB/MMC media.
3. Connect the USB/MMC storage to the appropriate ESR WLC slot. 

Copying configuration backup file 

...

2. Copy the file to the USB/MMC storage that is currently in use: 

...

To check the current firmware version and the version of the secondary bootloader (U-boot) in the CLI of the main firmware, execute the 'show version' command: 

...

• Switch the power off and then switch it back on. The interval between switching off and on must be at least 20 seconds. Briefly press the function button F on the front panel of the controller.
• Execute the 'reload system' command in the CLI of the main firmware of the controller. 
  

  Scroll Pagebreak

...

...

...

...

...

...

...

1. After the update it is necessary to edit the configuration according to the changes. The scheme of access point registration on the controller has been changed. Now not only port 8043 but also port 8044 is used. It is necessary to add port 8044 to object-group service sa:

   Блок кода
   object-group service sa port-range 8044 exit

   After the WLC is updated, the APs will be listed in the provisioning service and will be waiting for authorization. To view the list of unauthorized access points, use the command:

   Блок кода
   show wlc service-activator aps

   The following command is used to authorize all AP in the list:

   Блок кода
   join wlc ap

   The following command is used to authorize a specific AP:

   Блок кода
   join wlc ap <MAC_AP>

   It is possible to enable automatic authorization mode in the configuration:

   Блок кода
   wlc# configure wlc(config)# wlc wlc(config-wlc)# service-activator wlc(config-wlc-service-activator)# aps join auto wlc(config-wlc-service-activator)# do commit wlc(config-wlc-service-activator)# do confirm

   Scroll Pagebreak

2. The scheme of SoftGRE tunnels enabling has been changed:

   In 1.15.3 version:

   Client traffic comes from the AP to a gre-tunnel with a specified vlan tag, on the WLC side a separate subgre-tunnel is created for each vlan and included in the specified Bridges, when leaving the subgre the vlan tag is removed. With this implementation, a subgre-tunnel must be created for each vlan and included in one of the Bridges. WLC does not know vlans that are issued at the moment of radius authorization (if c-vlans with external radius server are used), and cannot raise tunnels for such clients. 

   draw.io Diagram
   border true viewerToolbar true fitWindow false diagramName gre_1.15.3 simpleViewer false width diagramWidth 798 revision 2

   
   In 1.19.0 version:

   The logic of SoftGRE tunnels operation in wlc mode has been changed. Previously subgre was unconditionally included in Bridge by WLC configuration, in the new implementation subgre tunnels are absent. Vlan specified in SSID configuration is included in WLC without sub-tunnel termination in Bridge. The use of c-vlan in client traffic tunneling scheme is supported. For correct operation, the vlan must be created in the WLC settings and must be a member of the Bridge or interface.
   

   draw.io Diagram
   border true viewerToolbar true fitWindow false diagramName gre_1.19.0 simpleViewer false width diagramWidth 798 revision 2

   
   
   

   Scroll Pagebreak

3. To raise tunnels, the location parameter, which was previously set on Bridge and in ap-location for SSIDs, is no longer used. Instead, you must enable tunnel mode in ap-location. The vlan-id in ssid-profile must match the vlan-id in bridge users.

   Firmware version 1.15.3	Firmware version 1.19.0
   bridge 3   security-zone users   ip address 192.168.2.1/24   location default   enable exit	bridge 3   vlan 3 (=vlan-id в SSID-profile)   mtu 1458   security-zone users   ip address 192.168.2.1/24   enable exit
   ap-location default-location   description default-location   board-profile WEP-1L default_wep-1l_profile   board-profile WEP-20L default_wep-20l_profile   board-profile WEP-2L default_wep-2l_profile   board-profile WEP-3ax default_wep-3ax_profile   board-profile WEP-3ax-Z default_wep-3ax-z_profile   board-profile WOP-20L default_wop-20l_profile   board-profile WOP-2L default_wop-2l_profile   board-profile WOP-3ax default_wop-3ax_profile   ssid-profile default-ssid default exit	ap-location default-location   description default-location   mode tunnel   ap-profile default-ap   board-profile WEP-1L default_wep-1l_profile   board-profile WEP-200L default_wep-200l_profile   board-profile WEP-20L default_wep-20l_profile   board-profile WEP-2L default_wep-2l_profile   board-profile WEP-30L default_wep-30l_profile   board-profile WEP-3ax default_wep-3ax_profile   board-profile WEP-3ax-Z default_wep-3ax-z_profile   board-profile WOP-20L default_wop-20l_profile   board-profile WOP-2L default_wop-2l_profile   board-profile WOP-30L default_wop-30l_profile   board-profile WOP-3ax default_wop-3ax_profile   ssid-profile default-ssid exit
   	vlan 3   force-up exit

   
   

4. Wireless-controller is renamed to softgre-controller:

   Firmware version 1.15.3	Firmware version 1.19.0
   wireless-controller   nas-ip-address 127.0.0.1   data-tunnel configuration wlc   aaa radius-profile default_radius   keepalive-disable   enable exit	softgre-controller   nas-ip-address 127.0.0.1   data-tunnel configuration wlc   aaa radius-profile default_radius   keepalive-disable   enable exit

   Scroll Pagebreak

5. WLC monitoring commands have been changed:

   In 1.15.3 version	In 1.19.0 version	Command description
   show wlc connected-ap	show wlc ap	View the list of access points monitored by the controller
   show wlc connected-ap detailed	sh wlc ap detailed	View detailed information on all authorized access points
   show wlc connected-ap detailed <MAC_AP>	sh wlc ap detailed <MAC_AP>	View detailed information on one of the authorized access points
   show wlc connected-ap-clients <MAC_AP>	sh wlc clients ap <MAC_AP>	View information about the wireless client connections of a specific access point
   show wlc connected-ap-clients <MAC_AP> detailed	sh wlc clients ap <MAC_AP> detailed	View detailed information about the wireless client connections of a specific access point
   show wlc connected-client <MAC_STA>	sh wlc clients <MAC_STA>	View wireless client connection information by its MAC address
   show wlc connected-client <MAC_STA> detailed	sh wlc clients <MAC_STA> detailed	View detailed connection information of a wireless client by its MAC address
   show wlc connected-ap-interfaces <MAC_AP>	show wlc ap interfaces <MAC_AP>	View information and counters on access point interfaces
   show wlc connected-ap-radios <MAC_AP>	show wlc ap radios <MAC_AP>	View the basic parameters of the access point's radio interfaces

...

1. Start the corresponding server on the network (tftp/ftp/sftp/http/https/scp).
2. Copy the firmware file (<firmware-file>) to the working directory of the remote file copy server. The names of the required files depending on the model and hardware version of the device are listed in the  section section Files used for the update.
3. Provide IP connectivity between the upddated WLC controller and the remote file copy server (routing). 
4. Ensure operation of the remote copy protocol between the WLC and the remote file copy server (intermediate firewalls). 
5. If necessary (for ftp, sftp, scp, http, https protocols), find out the username and password to write the required file. 

...

The rules for using firmware files for the different models are described in the section Files used for the updateFiles used for the upgrade.

Using USB/MMC media 

1. Define the volume label of the connected USB/MMC storage: 

...