23-17
Catalyst 6500 Series Switch Software Configuration Guide—Release 8.7
OL-8978-04
Chapter 23 Configuring Redundancy
Configuring Redundant Supervisor Engines on the Switch
Example 3: File not copied, bootstring changed, standby supervisor engine reset
The configuration for example 3 is as follows:
•
The active supervisor engine configuration is as follows:
–
Run-time image:
bootflash:f1
–
Bootstring:
bootflash:f1,1
–
Bootflash:
f1
•
The standby supervisor engine configuration is as follows:
–
Run-time image:
bootflash:f2
–
Bootstring:
bootflash:f2,1
–
Bootflash:
f1,f2
•
The time stamp for
f1
on the active supervisor engine is the same as
f1
on the standby supervisor
engine but is not the same as
f2
on the standby supervisor engine.
•
The expected results are as follows:
–
The active supervisor engine run-time image is synchronized to the standby supervisor engine.
–
The active supervisor engine
f1
image is not copied to the standby supervisor engine.
–
The standby supervisor engine bootstring is modified to the following:
f1,1;f2,1;
.
–
The standby supervisor engine is reset.
Example 4: Oldest bootflash file deleted, bootflash squeezed
The configuration for example 4 is as follows:
•
The active supervisor engine configuration is as follows:
–
Run-time image:
bootflash:f1
–
Bootstring:
bootflash:f1,1
–
Bootflash:
f1
•
The standby supervisor engine configuration is as follows:
–
Run-time image:
bootflash:f2
–
Bootstring:
bootflash:f2,1;
–
Bootflash:
f2, f3, f4
(less than 1 MB left on device)
•
The time stamp for
f1
on the active supervisor engine is not the same as
f2
on the standby supervisor
engine. The
f2
time stamp is older than
f3
, and the
f3
time stamp is older than
f4
.
