Filter
Top Products
11-10
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter11 CWM to CWM Communications
Recovering From Degrade Mode
ForcedSwitchOver
HeartBeatInterval 20
Step 2 Manually remove all the other CWMs from the downed Primary’s DomainGatewayList in the
CWMGateway.conf file
The following is an example of the downed Primary’s DomainGatewayList. Remove all Secondary
CWMs from the downed Primary’s DomainGatewayList leaving the Primary cwmws1 in its own
domain:
Debug level 2
DomainGatewayList cwmws1
ForcedSwitchOver
HeartBeatInterval 20
Step 3 Stop the core on the downed Primary CWM. (This is an optional step).
Step 4 Stop the core on the Secondary CWM that has been selected as the new Primary. In this case, for
example, let’s say that cwmws2 has been selected as the new Primary.
Step 5 Edit the new Primary’s DomainGatewayList so that it only has itself listed. For example:
Debug level 2
DomainGatewayList cwmws2
ForcedSwitchOver
HeartBeatInterval 20
Step 6 To ensure a manual re-sync of user data tables between the downed Primary CWM and the newly
assigned Primary CWM, enter usrtblDBsync <cwmws1> (with “cwmws1” representing the original
Primary CWM).
Step 7 Start the core on the new Primary CWM (in this example it would be cwmws2). A message will appear
on the CWM console announcing it as the new Primary.
Step 8 Stop the core on the Secondary CWM (in this example it would be cwmws3).
Step 9 Edit the Secondary’s DomainGatewayList so that it includes itself and the new Primary. For
example:
Debug level 2
DomainGatewayList cwmws2 cwmws3
ForcedSwitchOver
HeartBeatInterval 20
Step 10 Edit the new Primary’s DomainGatewayList so that it now includes itself and the secondary CWM.
For example:
Debug level 2
DomainGatewayList cwmws2 cwmws3
ForcedSwitchOver
HeartBeatInterval 20
Step 11 Start the core on the Secondary CWM (in this example it would be cwmws3).
Step 12 Repeat steps 7-10 above to include any additional Secondary CWMs in the new domain. The
DomainGatewayList on all of the Secondary CWMs must match the final DomainGatewayList on
the Primary CWM. This list will include the new Primary and all new Secondaries in the new
domain.