IBM 8265 Nways ATM Switch, User Manual, Page: 147 / 192

Control Point and Switch Module Problems
Standby Control Point and Switch Module Does Not Mirror Active Control Point and Switch Module
Explanation: In normal operation, the standby Control Point and Switch module should continually mirror any
changes made to the active Control Point and Switch module.
If this is not being done, this is because the microcode versions are not the same on both Control Point and Switch
modules.
Steps to Take: There are two cases to consider:
1. The active Control Point and Switch is at an older level than the standby Control Point and Switch module.
Perform the following steps:
a. Download inband the new microcode from a TFTP server, by following the installation instructions associated
with the new microcode.
b. At maintenance time, swap the microcode on the active Control Point and Switch module.
2. The active CPSW module microcode is at a newer level than the standby Control Point and Switch module.
Perform the following steps:
a. On the standby Control Point and Switch module, force the maintenance mode (by issuing the command
MAINTAIN force).
b. On the standby Control Point and Switch module, download out-of-band the microcode (providing the
out-of-band download is allowed in the installation instructions).
c. If the out-of-band download is NOT allowed, you need to plan a maintenance period (of at least one hour)
where you will:
Ÿ Manually copy the TCP/IP and port configuration of the active Control Point and Switch module to the
standby Control Point and Switch module.
Ÿ Remove the active Control Point and Switch module from the 8265.
Ÿ
Enter the right TFTP parameters on the remaining Control Point and Switch console, in order to download
the new microcode.
Ÿ
Download the new microcode.
Ÿ Swap the microcode.
Ÿ Remove the Control Point and Switch module from the 8265 (non are installed now).
Ÿ Reinsert the original CPSW module.
Ÿ Reinstall the second CPSW module, which will copy all the configuration parameters of the active one.
Appendix A. Troubleshooting
131