Cisco WS-X6066-SLB-APC - Content Switching Module Software Manual page 489

Chapter 22 Configuring Redundancy
•
•
•
Example 3: File not copied, bootstring changed, standby supervisor engine reset
The configuration for example 3 is as follows:
•
•
•
•
Example 4: Oldest bootflash file deleted, bootflash squeezed
The configuration for example 4 is as follows:
•
78-13315-02
The standby supervisor engine configuration is as follows:
Runtime image:
–
bootflash:f2
Boot string:
–
bootflash:f2,1
Bootflash:
–
f2
The time stamp for f1 on the active supervisor engine is not the same as f2 on the standby supervisor
engine.
The expected results are as follows:
The active supervisor engine copies f1 to the standby supervisor engine and renames the file
–
RTSYNC_f1.
The standby supervisor engine bootflash is modified to the following: f2, RTSYNC_f1.
–
The standby supervisor engine bootstring is modified to the following:
–
bootflash:RTSYNC_f1,1;f2,1;.
The standby supervisor engine is reset.
–
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:f2
Boot string:
–
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 runtime 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 boot string is modified to the following: f1,1;f2,1;.
–
The standby supervisor engine is reset.
–
The active supervisor engine configuration is as follows:
Runtime image:
–
bootflash:f1
Boot string:
–
bootflash:f1,1
Bootflash:
–
f1
Catalyst 6000 Family Software Configuration Guide—Releases 6.3 and 6.4
Configuring Redundant Supervisor Engines
22-15