Administrator Guide

○ RPM1 line-card processor: linecard 11
● The rows linecard 0 through linecard 9 list the system images for each line card installed in chassis slots 0 to 9.
Dell#show boot system all
Current system image information in the system:
===============================================
Type Boot Type A: B:
----------------------------------------------------------------
rpm 0 (CP) FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
rpm 1 (CP) FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
rpm 0 (RP) FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
rpm 1 (RP) FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
linecard 0 FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
linecard 1 FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
linecard 2 FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
linecard 3 is not present.
linecard 4 is not present.
linecard 5 is not present.
linecard 6 is not present.
linecard 7 is not present.
linecard 8 is not present.
linecard 9 is not present.
linecard 10 FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
linecard 11 FLASH BOOT 1-0(0-4243)[boot] 1-0(0-4226)
When System Images on C9010 Components Do Not Match
You normally upgrade system images on all installed components at the same time by entering the upgrade system-image
all command; for example: upgrade system-image all flash://FTOS-C9000-9.9.0.0.bin {A: | B:}
command. For information about this upgrade procedure, see the C9010 and C1048P Release Notes.
By upgrading all C9010 components at the same time, you ensure that all system images match. However, sometimes the loaded
system images do not match as a result of booting off a system image stored on a network server or installing an additional line
card or RPM.
When system images on C9010 components do not match, the RPM CP may not be able to manage them. For example, if the
RPM RP image does not match the RPM CP image, the console port of the RPM CP may not fully come up. As a result, the
command-line prompt may not appear on the C9010 console.
When the system detects an image mismatch, it automatically performs a firmware synchronization to ensure that all C9010
component images are the same as the RPM CP image; for example:
%RPM0-P:CP %DOWNLOAD-6-VERSION_MISMATCH_INFO: Received checkin from linecard 0. Expected
version = 1-0(0-4243) checkin version = 1-0(0-4226)
%RPM0-P:CP %DOWNLOAD-6-UPGRADE_PROGRESS: Linecard 0 firmware auto sync is in progress.
If the automatic synchronization of component images fails or if the RPM CP cannot read line-card firmware, you can manually
reset the system image on an individual component.
Manually Resetting the System Image on a C9010 Component
If the image running on the RPM CP does not match the image on a C9010 component, you can manually recover from the
mismatch as follows:
1. Log in to the virtual console of the C9010 component as described in Logging in to the Virtual Console of a C9010
Component.
2. Display the boot variables that you need to configure so that the component boots from the RPM CP image by entering the
show bootvar command at the BOOT_USER# prompt.
show bootvar
See Configuring C9010 Components to Boot from the RPM CP Image for examples.
3. Reconfigure the boot variables of the component by entering the boot change command at the BOOT_USER# prompt.
boot change {primary | secondary | default}
80
Switch Management