22-16
Catalyst 6000 Family Software Configuration Guide—Releases 6.3 and 6.4
78-13315-02
Chapter 22 Configuring Redundancy
Configuring Redundant Supervisor Engines
•
The standby supervisor engine configuration is as follows:
–
Runtime image:
bootflash:f2
–
Boot string:
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
.
•
The expected results are as follows:
–
The active supervisor engine runtime image is synchronized with the standby supervisor engine.
–
The active supervisor engine attempts to copy its
f1
image to the standby supervisor engine.
–
Because there is not enough space on the standby supervisor engine bootflash, the redundant
synchronization function finds the oldest file, deletes it, and squeezes bootflash.
–
The active supervisor engine copies the
f1
image to the standby supervisor engine and renames
it
RTSYNC_f1
.
–
The standby supervisor engine bootflash is modified to the following:
f3, f4, RTSYNC_f1
.
–
The standby supervisor engine boot string is modified to the following:
RTSYNC_f1,1;f2,1;
.
–
The standby supervisor engine is reset.
Synchronizing the Boot Images on the Active and Standby Supervisor Engines
This section contains four examples in which the bootstrings on the active and standby supervisor
engines are synchronized.
Example 1: Unable to allocate the boot image
The configuration for this example is as follows:
•
The active supervisor engine configuration is as follows:
–
Runtime image:
bootflash:f1
–
Boot string:
bootflash:f1,1;
–
Bootflash:
f1
•
The standby supervisor engine configuration is as follows:
–
Runtime image:
bootflash:f1
–
Boot string:
bootflash:f1,1;
–
Bootflash:
f1
•
The time stamp for
f1
on the active supervisor engine is the same as
f1
on the standby supervisor
engine.
•
The system attempts to modify the active supervisor engine bootstring to the following:
f2,1;
.
•
The expected results are as follows:
–
The active supervisor engine is unable to allocate
f2
, causing the synchronization to fail.
–
An error is recorded in syslog.
