The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The objective of this article is to go over the recommended practices when updating firmware of Cisco Business 250 and 350 series switches from version 3.1 to version 3.2.
Updating the firmware of your device is essential to improve its performance and stability. The firmware update might offer new features, enhanced security or fix a vulnerability that was experienced in the previous version of the software.
For steps to upgrade the firmware of your CBS 250/350 switch, check out the article on Upgrade Firmware on a CBS 250 or 350 Series Switch. You can also check out the article on New to Cisco Business: How to Download and Upgrade Firmware on any Device for additional information.
In this article you will learn about the recommended practices when upgrading the firmware of a CBS250 or CBS350 from version 3.1 to version 3.2.
When updating the firmware of a CBS250/CBS350 switch from version 3.1 to version 3.2, it upgrades the Microcontroller Unit (MCU) code from 0xEE to 0xF0. This process will take time and during this process the switch will be offline.
The firmware upgrade process may take approximately 15 minutes to complete. During this time, the switch may not show any activity. As part of the upgrade process, switch may reboot couple of times. Interrupting the upgrade process may result in permanent damage to the switch and make it unusable.
This is done by monitoring the boot process of a switch and it is important to note that it cannot be found in support files or through a Command Line Interface (CLI) command. You must connect to your switch via a console cable.
The behavior of a failed update can vary. It is dependent on where and how the update was interrupted.
Now you know all about the recommended practices to update your CBS250 or CBS350 switch from version 3.1 to version 3.2.