Cisco CW9800L：通过 GUI 升级无线控制器

Cisco CW9800L：通过 GUI 升级无线控制器

GUI instructionsGUI 指令

If you want to upgrade the wireless controller using the GUI, you can go to Administration > Software Upgrade and configure the upgrade parameters. You can choose to upload the .bin file directly from your desktop or load it from a TFTP/SFTP/FTP server. You can also choose to pre-download the APs or not. Once everything is configured, you can click on “Download and Install”, which corresponds to step 1-3 stated previously. Optionally, you can also click on the “Remove Inactive Files” button to remove unused file before uploading the new image. This corresponds to the optional step 0.

如果要通过 GUI 升级无线控制器，您可以转到管理 > 软件升级并配置升级参数。您可以选择直接从本地桌面上传 .bin 文件，或从 TFTP/SFTP/FTP 服务器加载该文件。您还可以选择是否预先下载 AP。配置完成后，您可以点击“下载并安装”，这对应于前面所述的第 1 至 3 步。此外，您也可以选择点击“移除未使用文件”按钮，在上传新镜像之前删除不再使用的文件。这对应于可选步骤0。

You can monitor the progress of the AP pre-download by clicking on the “Show logs” button under the status section on right hand side.

您可以通过点击右侧状态栏下的“显示日志”按钮，来监控AP预下载的进度。

Once the image upload and install of the image is done, you can click on “Save configuration & Activate” button. This saves the configuration and start the upgrade of the controller. This corresponds to step 4.

镜像上传并安装完成后，您可以单击“保存配置并激活”按钮。这将保存配置并启动控制器的升级过程，对应于步骤4。

Once the session has timed out, you can login again to the controller, navigate to Administration > Software Upgrade and click on the “Commit” button that is now available. This corresponds to step 5.

会话超时后，您可以重新登录控制器，导航至管理 > 软件升级，并单击此时已启用的“提交”按钮。这对应于步骤5。

Once the APs detect the controller is reachable again, they start to reload on the backup partition and join the controller running on the new version.

一旦AP检测到控制器重新可达，它们便会开始从备份分区重新加载，并加入运行新版本的控制器。

Controllers in High Availability (HA)高可用性（HA）中的控制器

Wireless controllers have multiple ways to be redundant. You can have an HA SSO (Stateful Switch Over) pair, a N+1 redundancy, or both.

无线控制器具备多种冗余方式。您可以采用 HA SSO（状态切换）双机热备、N+1 冗余，或同时采用这两种方式。

HA SSO: there is an active and standby controller with continuous synchronization between the WLCs.

HA SSO：存在一台主控制器和一台备用控制器，且两台无线控制器之间保持持续同步。

N+1: there is a primary and secondary controller, but they are not interconnected. Both controllers must be running the same version and must be configured identically for this to work seamlessly. APs are joined to the primary controller and falls back to the secondary controller in case of failure of the primary controller. 

N+1：存在主控制器和备控制器，但二者之间未实现互连。为确保系统无缝运行，两台控制器必须运行相同版本且配置完全一致。AP 首先接入主控制器，一旦主控制器发生故障，则自动切换至备控制器。

Stateful Switch Over (SSO) redundancy有状态切换（SSO）冗余

When controllers are in HA SSO mode, you have 2 mains ways to upgrade them. You can either do a “classic” upgrade or an ISSU (In-Service Software Upgrade).

当控制器处于 HA SSO 模式时，您有两种主要的升级方式。您可以选择“经典”升级，也可以选择 ISSU（在服务中软件升级）。

“Classic” upgrade: this is the same upgrade process explained previously for standalone controllers. Both controllers reload at the same time, and APs reload on the new version. You can decide to pre-download the AP image or not. Total downtime for this upgrade: controller reload + AP reload time. It does not take any more time than upgrading a single standalone controller

“经典”升级：此升级流程与此前针对独立控制器的说明相同。两台控制器将同时重启，AP 也会在新版本下重新加载。您可以选择是否预先下载 AP 镜像。此次升级的总停机时间为：控制器重启时间 + AP 重启时间。这并不比升级单个独立控制器花费更多时间

ISSU upgrade: this is a zero-downtime upgrade. The standby controller upgrades, there is a switchover, then the (old) active controller upgrades, and finally APs upgrade in staggered manner. Ideal for 24/7 environment where downtime must be as minimal as possible.

ISSU升级：这是一种零停机时间的升级方式。首先由备用控制器完成升级，随后发生主备切换，接着（旧的）主控制器进行升级，最后AP设备以交错方式依次升级。非常适合对停机时间要求极低的全天候运行环境。

Classic upgrade经典升级

Please refer to the previous section under the “Standalone Controllers” section. The steps are the exact same ones. Image is copied from the active to the standby controller automatically and both controllers upgrade at the same time. Once the controllers are upgraded, the APs either swap their partition if you pre-downloaded the images to the APs, or download the new image if the pre-download was not done. 

请参阅“独立控制器”部分中的上一节。操作步骤完全相同。镜像会自动从活动控制器复制到待机控制器，且两台控制器将同时升级。控制器升级完成后，如果此前已将镜像预下载至AP，则AP会交换其分区；若未进行预下载，则AP将下载新的镜像。

Note: make sure that both controllers are in ACTIVE/STANDBY-HOT state before proceeding to the upgrade (using the “show redundancy” command).

注意：在继续升级之前，请确保两个控制器均处于ACTIVE/STANDBY-HOT状态（使用“show redundancy”命令）。

ISSU upgradeISSU升级

The ISSU feature allows you to reduce the downtime during an upgrade. Controllers upgrade one by one, and APs reload in staggered manner. The wireless client is able to roam between APs if there is sufficient coverage. If an AP is isolated, then there is a downtime for clients connected to such AP (the AP reload time).

ISSU 功能可帮助您缩短升级过程中的停机时间。控制器逐台升级，接入点则采用交错式重启。在覆盖范围充足的情况下，无线客户端可在各接入点之间实现漫游。若某个接入点被隔离，则连接该接入点的客户端将出现短暂的停机（即接入点的重启时长）。

This upgrade takes a much longer time in total since both controllers upgrade one at a time and APs reboot and upgrade in a staggered and controlled manner which leads to a longer total maintenance window however with no perceived downtime by the clients.

由于两个控制器每次仅升级一个，且AP以交错且受控的方式重启并升级，因此此次升级的总时长显著延长，导致整体维护窗口相应拉长，但客户端并未感知到任何停机时间。

There are a few things to consider when doing an ISSU upgrade (limitations, precautions to take and so on) for example, the fact it is only available in INSTALL mode and not in BUNDLE mode. For a complete explanation of the ISSU procedure (with instructions and commands), please refer to this document.

在执行 ISSU 升级时，有几点需要考虑（如限制条件、注意事项等），例如，该功能仅支持 INSTALL 模式，而不支持 BUNDLE 模式。有关 ISSU 流程的完整说明（包含操作步骤与相关命令），请参阅本文档.

N + 1 redundancyN+1 冗余

N+1 redundancy is when you have a set of 2 controllers that are not direclty connected to each other, but are configured exaclty the same and are running the same version. In this case, we have one "primary" controller (where all the APs are joined) and a "secondary" controller, which can be used as a backup in case of primary controller failure. When you want to proceed to an upgrade, it is as if you had 2 "standalone" controllers. However, having this kind of redundancy has a big advantage, because there is a way to reduce the downtime compared to a classic upgrade using the "N+1 Hitless Rolling AP Upgrade" feature. This allows you to perform a staggered upgrade of the APs while moving them to a secondary, upgraded controller. This limits the downtime since only a small subset of APs are reloaded at the same time. 

N+1 冗余是指一组由两台控制器组成的配置，这两台控制器之间并未直接互联，但其配置完全相同且运行同一版本的软件。在这种情况下，我们有一台“主用”控制器（所有 AP 均接入该控制器），以及一台“备用”控制器，可在主用控制器发生故障时作为备份使用。当您准备进行升级时，系统仿佛拥有两个“独立”的控制器。然而，这种冗余设计具有显著优势，因为与传统的升级方式相比，借助“N+1 无中断滚动 AP 升级”功能，可以有效缩短停机时间。这使您能够在将 AP 迁移到已升级的备用控制器的同时，对其进行分批升级。由于每次仅重新加载一小部分 AP，因此可有效缩短停机时间。

Here is the flow for this type of upgrade :

以下是此类升级的流程：

Upgrade the secondary controller to the target release. This can be done with a classic upgrade, without AP pre-download since there are no APs connected to it. At that stage, primary is running V1, while secondary is running V2. 

将辅助控制器升级到目标版本。此操作可通过经典升级方式完成，由于未连接任何接入点，无需预先下载接入点固件。此时，主控制器运行V1，而辅助控制器运行V2。

Install the target image (V2) on the primary controller, but do not activate. This allows you to pre-download the V2 image to the APs.

在主控制器上安装目标镜像（V2），但暂不激活。这使您能够预先将V2镜像下载到AP上。

Once the pre-download is finished, initiate the AP staggered upgrade using the "ap image upgrade destination" command. This triggers the staggered AP upgrade and APs reload on the V2 image and join the secondary WLC.

预下载完成后，使用“ap image upgrade destination”命令启动 AP 的错峰升级。这将触发 AP 的错峰升级，使 AP 重新加载 V2 镜像并加入备选 WLC。

Once all APs are joined to the secondary WLC, upgrade the primary controller to V2. 

待所有 AP 均加入辅助 WLC 后，请将主控制器升级至 V2 版本。

Once done, if needed, you can easily move the APs back to the primary controller, at your own pace. Note that this does not require a reload of the APs since both WLCs are on the same V2 version. Only a CAPWAP restart is required and this takes less than a minute.  

完成后，如有需要，您可以按自己的节奏轻松将AP迁移回主控制器。请注意，由于两台WLC均运行同一V2版本，此操作无需重启AP，仅需执行一次CAPWAP重启，整个过程不到一分钟。

For a complete explanation of the "N+1 Hitless Rolling AP Upgrade" procedure (with instructions and commands), please refer to this document.

有关“N+1 无中断滚动 AP 升级”流程的完整说明（含操作步骤与命令），请参阅本文档.

What if you have SMUs or APSPs current installed ?如果当前已安装 SMU 或 APSP，该怎么办？

You do not need to remove any SMU or APSP patch currently installed before upgrading to the next release.

在升级到下一版本之前，您无需卸载当前已安装的任何 SMU 或 APSP 补丁。

Is it mandatory to upgrade the ROMMON each time ?每次是否都必须升级 ROMMON？

ROMMON versions do not relate to IOS-XE versions and are less common. Changes in ROMMON are documented in https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_upgrade_fpga_c9800.html#id_132283

ROMMON 版本与 IOS-XE 版本无关，且较为少见。ROMMON 的变更记录在https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_upgrade_fpga_c9800.html#id_132283

Upgrading the ROMMON is not mandatory for upgrading IOS-XE. However, it is required to run ROMMON 17.7 or later in order to install new IOS-XE releases. Older ROMMON can potentially not work if you upgrade to a recent IOS-XE release.

升级 ROMMON 并非升级 IOS-XE 的必要条件。然而，若要安装新的 IOS-XE 版本，则必须使用 ROMMON 17.7 或更高版本。如果升级到较新版本的 IOS-XE，旧版 ROMMON 可能无法正常运行。

It is to be noted that not all changes in ROMMON versions are documented in resolved caveats as there are undocumented internal enhancements and fixes.

需要注意的是，ROMMON版本中的并非所有变更都会在已解决的注意事项中予以记录，因为其中还包含未公开的内部增强与修复。