Cisco Cisco ACE Application Control Engine Module White Paper

Page 15 of 40

Migrate the Production Environment

The last step in the migration process is to replace the Cisco ACE10 or ACE20 modules with the staged Cisco

ACE30 modules. This is a simple process providing a hitless migration for the majority of client connections. Follow

these steps.

Migrate Backup ACE10 or ACE20 to ACE30

Step 1. On the primary (active) Cisco ACE10 or ACE20 module, create a checkpoint for the current configuration.

ACE-pri/Admin# checkpoint create pri-orig

Generating configuration....

Created configuration checkpoint „pri-orig‟

Step 2. If the Admin context on the primary Cisco ACE10 or ACE20 module has preempt configured within its FT

groups, then they must be removed to allow manual context failover and to prevent a premature failover
during the Cisco ACE migration process. The best way to ensure “no preempt” is applied to all ft groups is
to copy the

“show run ft | inc group” output to a editor and append a newline with “no preempt”, then

paste it back into the Admin context. See step 6 in the Stage ACE30a section above for more details.

Step 3. Power-down the backup ACE10 or ACE20 from the secondary Cisco Catalsyt Supervisor Engine 720.

cat6k-sec#show module services

Module

Model Services

---------- ----------------- --------------------

1 ACE10/20-MOD-K9 ACE-16G-LIC ACE-VIRT-250 ACE-SSL-15K-K9

cat6k-sec#conf t

Enter configuration commands, one per line. End with CNTL/Z.

cat6k-sec(config)#no power enable

module 1

%Power admin state updated

Step 4. Physically replace the backup Cisco ACE10 or ACE20 module with the Cisco ACE30b module.

Step 5. Power-on ACE30b. The ACE30b will boot as standby.

cat6k-sec(config)#power enable

module 1

%Power admin state updated

cat6k-sec(config)#exit

Step 6. Once ACE30b is warm perform the ACE10 or ACE20 failover.

cat6k-sec#session

s 1

p 0

The default escape character is Ctrl-^, then x.

You can also type „exit‟ at the remote prompt to end the session