Field Notice: FN72292 - Cisco Nexus 92348GC-X Switch Bootflash Size Is Less Than Expected - Workaround Provided

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected

Defect Information

Problem Description

Flash for Cisco Nexus 92348GC-X Switches is not properly partitioned for Cisco NX-OS Software. The bootflash is around 4GB when the size should be 10GB. This could result in the user being unable to save multiple Cisco NX-OS Software images to the bootflash.

Background

On Cisco Nexus 92348GC-X Switches, the bootflash partition is mounted on a 16GB flash storage drive.

A small number of units were not correctly partitioned for Cisco NX-OS Software. As a result, the bootflash size on affected devices is only 4GB when it is expected to be more than 10GB.

Problem Symptom

In the following example, the output indicates that there is less than 10GB of bootflash space:

switch# dir:

Usage for bootflash://
2298146816 bytes used
1795166208 bytes free
4093313024 bytes total 

In the above output example, total space is 4093313024 bytes, which equates to around 4 GB. As a result, you cannot save multiple images on the bootflash.

Also, when trying to copy files to a device bootflash, transfer may fail with the following message:

Switch# copy scp://10.1.1.1/nxos bootflash:
Destination: No space left on device

If the transfer fails, the following syslog will appear:

switch %$ VDC-1 %$ vshd: Copy failed. Device bootflash is full.

Workaround/Solution

There are two solutions to remediate this issue. Option 1 is to reload the SMU to recover the bootflash, and Option 2 is to manually recover the bootflash.

Note: Recovery methods are disruptive and will require the device to be reloaded. For both options, it is recommended to have console access to the device and back up these items outside of this process.

Option 1: Reload the SMU to Recover Bootflash

To reload the SMU, click the link that corresponds to the proper software release. 

The SMU that has been downloaded will attempt to automatically correct the bootflash size. It will then copy the following information from the device:

• Device configuration
• Device boot image
• Device license information
• Installed RPMs

Note: For releases 9.3(1)-9.3(3), the following additional restart SMU must be installed prior to performing remaining recovery steps. Installing the additional SMU will prevent issues with additional patches being able to install after completing this operation.

nxos.CSCvt16565-n9k_ALL-1.0.0-9.3.3.lib32_n9000.rpm

Installing the additional SMU will prevent issues with additional patches being installable after completing this operation. This patch should be installed with the following command after copying to the device bootflash:

Install add bootflash:nxos.CSCvt16565-n9k_ALL-1.0.0-9.3.3.lib32_n9000.rpm activate

To recover the device using the SMU method, follow these steps:

1. Copy the SMU to the device bootflash.
2. Install/activate the SMU on the device with the following command:

Install add bootflash:nxos.CSCwa04181-n9k_ALL-1.0.0-9.3.8.lib32_n9000.rpm activate

The following logs will print on the device with a WARNING prompt and an instruction to select Y to continue installation:

>Adding the patch (/nxos.CSCwa04181-n9k_ALL-1.0.0-9.3.8.lib32_n9000.rpm)

[####################] 100%

Install operation 1 completed successfully at Fri Dec  3 06:12:55 2021

Activating the patch (/nxos.CSCwa04181-n9k_ALL-1.0.0-9.3.8.lib32_n9000.rpm)

 

 

======================================================

!!!WARNING!!

This is a reload patch and system will be reloaded

if you proceed with patch operation.

=======================================================

Do you want to continue (y/n)?: [n] y

At this point, the device will be reloaded. Upon completion of device boot, the bootflash size should be at the expected value as shown in the following output example:

C92348# dir
Usage for bootflash://
2167005184 bytes used
8019759104 bytes free
10186764288 bytes total 

At this time, recover any additional missing files to the bootflash.

When attempting to install the SMU, devices that are running Cisco NX-OS Software releases 10.2(1) – 10.2(5) will undergo two reloads during the recovery operation. For these releases, the SMU will show as Inactive, but the recovery method will complete successfully. The SMU can be removed issuing the install remove inactive command.

Option 2: Manually Recover Bootflash

To perform a manual recovery, complete the following steps from the Cisco NX-OS CLI. Because these steps will re-init the switch and erase all contents of the bootflash, copy the configuration, images, and any other important files that are on the bootflash to a remote server before starting manual recovery.

1. Copy the configuration and boot image to a remote server and verify that the data is correctly backed up:

switch# copy run scp://
switch# copy bootflash:nxos_image scp://

2. Then enter the the following commands:

switch#config t
Switch(config)#no boot nxos
Switch(config)#copy run start
Switch(config)#reload

Completing Step 2 should result in a loader prompt without a break sequence, as shown in the following output:

loader>cmdline force_init_system clear_config  
loader>boot <nxos image>

This solution will repartition, erase the configuration, and load Cisco NX-OS Software. Make sure to copy the NX-OS image before the next reload. Do not reload or power cycle the switch. If the switch is reloaded, it will need either the TFTP boot or the USB boot.

Restore the configuration from the remote server and save it along with the boot variables using the following command:

switch#config t
Switch(config)#boot nxos <nxos-image>
Switch(config)#copy run start

Serial Number Validation

Cisco provides a tool to verify whether a device is impacted by this issue. In order to check the device, enter the device's serial number in the Serial Number Validation Tool.

Note: For security reasons, you must click on the Serial Number Validation Tool link provided in this section to check the serial number for the device. Use of the Serial Number Validation Tool URL external to this field notice will fail.

Revision History

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

• Open a service request on Cisco.com
• By email or telephone

Receive Email Notification For New Field Notices

My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.