Wireless Sub-Package for Switch

Wireless sub-packages

A wireless sub-package is a component within a network architecture that

  • integrates seamlessly with existing network designs such as multitier, Routed Access, and VSS

  • uses LISP for control planes and VXLAN for overlay data planes,

  • maintains wireless control planes through CAPWAP tunnels connecting AP with controllers.

Benefits of the controller

The controller provides these benefits:

  • Centralized Control: Simplified configuration, troubleshooting, and upgrades.

  • Performance: High throughput and distributed forwarding for enhanced network services.

  • Scalability: Facilitates scalable services like AVC without splitting control planes into MC and MA.

Installation and activation process

To install and activate sub-packages:

  1. Identify Targets: Determine specific network nodes needing enhanced wireless capabilities.

  2. Install Sub-package: Deploy the sub-package atop the base image on relevant switches.

  3. Activation: Reload the system to activate the newly installed sub-package.


Note

The sub-package is an optional binary that contains the entire Cisco Catalyst 9800 Series Wireless Controller software.

Deployment considerations

  • Cisco Catalyst 9800 Wireless Controller software on the Cisco Catalyst 9300 switches must be provisioned and deployed on the switch using Cisco DNA Center, and it cannot be configured as a standalone controller. For more details, see Cisco Catalyst 9300 Series Switches Hardware Installation Guide.

  • SNMP Compatibility: Note that SNMP is unsupported on Catalyst 9800 Embedded Wireless Controllers.

  • The sub-package contains the complete Cisco Catalyst 9800 software suite, best deployed via Cisco DNA Center. For more details, see the Cisco Catalyst 9300 Series Switches Hardware Installation Guide.

  • Ensure network configurations and conditions align with operational requirements for optimal performance.

Installing wireless packages

Summary

Installing the wireless package is essential for enabling wireless capabilities on a switch. This process allows the switch to handle wireless access points and manage network traffic efficiently, thereby expanding its functionality within a network environment.

Workflow

The process involves these stages:

  1. Install the base image: load the base image (excluding wireless) onto the switch to prepare it for further installations.
  2. Install the wireless package: add the wireless package to the switch to enable wireless features.
  3. Upgrade the AP image: ensure that the access point image is updated to the latest version for compatibility and performance.
  4. Reload the switch: restart the switch to apply the new settings and updates.
  5. Enable and configure wireless: use the configuration command to activate wireless on the switch and configure the necessary wireless features.

Result

The switch has wireless capabilities enabled, allowing it to manage wireless connections and integrate seamlessly into a wireless network architecture.

Removing wireless package

Summary

Removing a wireless package involves uninstalling it, reloading the switch, and clearing configurations.

Workflow

Perform these steps to remove wireless package

  1. Uninstall: Remove the wireless package from the switch.
  2. Reload: Reboot the switch to refresh system settings.
  3. Clear Configuration: Run the write command to delete wireless settings from startup configuration.

Result

The switch will no longer contain any wireless packages or settings.

Upgrading wireless packages

Summary

This process outlines how to upgrade the wireless software on a switch, ensuring the system runs the latest version.

Workflow

Perform these steps to upgrade wireless packages

  1. Install the base image: Start by setting up the switch with the base software version.
  2. Install the updated wireless package: Load the new wireless version onto the switch.
  3. Reload: Restart the switch to apply changes.
  4. Commit: Finalize the installation to activate the updated package.

Result

The switch successfully runs the upgraded wireless software, improving its capabilities and resolving any prior issues.

Boot in install mode

Switch the boot mode from bundle-mode to install-mode using commands.

Use this procedure to boot the switch in install-mode

Before you begin

The sub-package does not work in bundle-mode. Use the show version command to verify the boot mode.

Procedure

Step 1

install add file image.bin location activate commit .

This command moves the switch from bundle-mode to install-mode. Note that image.bin is the base image.

Step 2

Click yes to all the prompts.

Step 3

Reload the switch.

Device# reboot

Boot from flash:packages.conf. After the reload, the switch will be in install-mode.

Note

 

For image upgrade or downgrade in Install mode, the 'Install add file' command with flash:<file_name> is not supported. Instead of that “bootflash:<filename”> needs to be used. 

Install add file bootflash:file_name  activate commit

After completing this task, the switch will be in install-mode.

What to do next

Verify the boot mode using the show version command.

Install sub-package in a single step (GUI)

The purpose of this task is to install a sub-package using the graphical user interface in a single step.

Procedure

Step 1

Choose Administration > Software Management > Software Upgrade.

Step 2

Choose the upgrade mode from the Upgrade Mode drop-down list, the transport type from the Transport Type drop-down list and enter the Server IP Address (IPv4/IPv6), the File System and choose the location from the Source File Path drop-down list.

Step 3

Click Download & Install.

The sub-package is successfully downloaded and installed, ensuring the software is updated with the latest version.

Install sub-package in a single step

The purpose of this task is to efficiently install a sub-package onto the switch in a single step, streamlining the update or installation process.

Before you begin

  • Ensure that the switch is in install mode.

  • Ensure that you boot only from flash:packages.conf.

Use this procedure to install sub-package in a single step

Procedure

Step 1

install add file flash:<controller>.bin activate commit

Installs the Cisco Catalyst 9800 Wireless Controller for Switch sub-package.

Note

 

The sub-package (flash:<controller>.bin) is available on www.cisco.com. You can also install the sub-package directly from TFTP server.

Step 2

Click yes to all the prompts.

Upon completion, the sub-package will be successfully installed and activated on the switch, ready for its verification and use.

What to do next

Use the show install summary command to verify the installed image or package.

Install multi-step sub-package

This task provides steps to install a multi-step sub-package on a switch.

Before you begin

Ensure that the switch is in install-mode and boot only from flash:packages.conf.

Procedure

Step 1

install add file flash:<controller>.bin

The sub-package is added to the flash and expanded.

Step 2

install activate file flash:<controller>.bin

Installs the sub-package.

Step 3

install commit

Completes the installation by writing the files.

The sub-package installation is completed successfully, and the system is ready for operation.

What to do next

Use the show install summary command to verify the installed image or package.

Install the package on a stack

Use a structured method to install the package on a network stack.

Before you begin

  • Ensure you have the correct permissions.

  • Determine if auto-upgrade is enabled or disabled for any new members.

Procedure

Step 1

Verify the current version running on the stack.

Step 2

Choose the installation method:

Step 3

If a new member joins, there are two possible scenarios.

if auto-upgrade is enabled

confirm the software automatically installs.

if auto-upgrade is disabled

run the install autoupgrade command in EXEC mode manually.

The package is installed, and new stack members are aligned with the current software version, maintaining consistency across the system.

Upgrade to new version of wireless package

Upgrade the wireless package to the latest version by executing specific commands.

Use this procedure to upgrade to the new version of wireless package

Procedure

Step 1

install add file flash:<base-image>.bin

You add the base image (without wireless) to the flash and expand it.

Step 2

install add file flash:<controller-sub-package>.bin

You add the sub-package to the flash and expand it.

Step 3

install active

The system executes the installation of the base image and sub-package, which causes a reload. However, you can also rollback to the previous state after the reload.

Step 4

install commit

Completes the installation by writing the files.

Once you complete the installation, the latest wireless package version runs on your system. You can rollback if necessary.

Deactivate wireless package

You can deactivate the wireless package on a device to ensure it operates without wireless functions through this task.

Follow this procedure to deactivate the wireless sub-package:

Procedure

Step 1

Remove the package and force the switch to reboot

Example:

Device# install deactivate file flash:<controller>.bin

Removes the package and forces the switch to reboot.

Step 2

Commit the switch without wireless package

Example:

Device# install commit

Commits the switch without wireless package.

The device reboots and ensures that only non-wireless functions are available by operating without the wireless package.

Enable or disable auto-upgrade

The purpose of this task is to manage the auto-upgrade capabilities of the software on the device, allowing you to either enable or disable automatic upgrades according to operational needs.

Use this procedure to enable or disable auto-upgrade

Procedure

Step 1

Enable software auto-upgrade

Example:

Device(config)# software auto-upgrade enable

Enables software auto-upgrade.

Step 2

Disable software auto-upgrade

Example:

Device(config)# no software auto-upgrade enable

Disables software auto-upgrade.

The device either automatically updates its software when new firmware is available or remains on its current software version without automatic upgrades, depending on the command executed.