Introduction Software Compatibility
Software Reference for SwitchBlade x3100 Series Switches (Setting Up the Switch)
1-148
CREATE CARD=4 <CFC200> or CREATE CARD=5 <CFC200>
5.
The card is now provisioned in the configuration database, but must change its Admin State to UP to sync
with the active CFC, and to try to go into service. The default for the manual mode is when cards are cre-
ated, ENABLED=UP, so no additional actions are needed. If this has been changed, enter the ENABLE
CARD=INACTCFC command.
6. The newly enabled CFC will boot, sync all of its data with the active CFC (bulk sync), and then bring the
CFC into service (an Operational State of UP, a status of ONLINE, and a state of INACTIVE).
1.10.7.5 Duplex to Simplex (Manual Mode)
In Manual mode, the CFC card can be physically present and the shelf will not try to create and enable the card.
Therefore, the card does not need to be removed before deleting it from the database. Follow these steps:
1. Disable the inactive CFC (DISABLE CARD=INACTCFC).
2. Delete the card from the configuration database (DESTROY CARD=4 or DESTROY CARD=5).
3. Follow antistatic procedures and remove the inactive CFC from its slot and place in an antistatic container.
4. Insert a filler plate into the empty slot for optimum system cooling. (Line Cards are not allowed in the
unused slot in 14.2.)
1.10.8 Software Compatibility
A software release will retain backward compatibility with certain releases that preceded it (i.e., up to one
major release back). Backward compatible means that database data -- that was saved in flash memory using an
older software release -- will be restorable when the newer software release is loaded. This allows for a soft-
ware upgrade to occur without requiring the entire system database to be recreated.
Backward compatible also means that a card using a given software release can communicate with another card
using an older software release.
Caution: The SBx3112 supports restoring the system configuration using the configuration (text) file from an
earlier software release. However, it is only recommended for users that are very knowledgeable
about CLI commands and syntax. Due to differences that may exist between the commands in the
current software release and those of the older release, the configuration file may require editing
before initiating the restore. Otherwise, the restore may result in unpredictable configuration
results.
An understanding of software upgrades and interim upgrades is important to the concept of backward compatibil-
ity. An upgrade where system load files are changed in order to add new, significant feature functionality is
called a software upgrades. For example, an upgrade from release 14.0.0 to 15.0.0. An upgrade where system
load files are changed in order to possibly add minor feature functionality and software fixes is referred to as an
interim upgrade. For example, an upgrade from release 14.1.1 to 14.1.2. During an interim upgrade, no
schema migration is to be performed on the configuration database. Also, during the interim upgrade, no Data-
base in Upgrade alarm is raised.
To Next Page
Loading...
Need help?
General
