11-13
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter1 1 CWM to CWM Communica tions Recovering From Degrade Mode
–
To recover from this degrade d m od e of operation, re-e s tab li sh IP connectivity on t he Primary
CWM and the Secondary CW M will automatically re-sy n c u s er d ata tables with the Prima ry
CWM.
–
If you can’t re-establish IP connectivity on the Primary, then eliminate the downed Primary
from the CWM doma in by f ol lowing these steps:
Step 1 Manually remove the downed Primary from the Secondary CWM’s DomainGatewayList in the
CWMGateway.conf file
The following is an example of a CWMGateway.conf file with a DomainGatewayList consisting of
two CWM workstations named cw m w s1 an d cw m ws 2 , w i th cw mw s 1 as s ig ne d a s th e Primary and
cwmws2 as the Secondary:
Debug level 2
DomainGatewayList cwmws1 cwmws2
ForcedSwitchOver
HeartBeatInterval 20
The above DomainGatewayList, for example, would n eed to b e edit ed to sho w that the do wne d Primar y
(cwmws1) has been removed from the Secondary CWM’s (cwmws2) DomainGatewayList in the
CWMGateway.conf file. In this example, you would remove th e d owned Primary from the cwmws 2
DomainGatewayList to include only cwmws2:
Debug level 2
DomainGatewayList cwmws2
ForcedSwitchOver
HeartBeatInterval 20
Step 2 Manually remove the Secondary CWM (c wm ws2) from the downed Primary’s DomainGatewayList in
the CWMGateway.conf file
The following is an example of the downe d P ri mar y ’s DomainGatewayList after removing the
Secondary CWM 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.
Step 4 Start the core on the downed Primary CWM (this is an optional step).
Step 5 Add another workstation (for example, cwmws3) to serve as the new Primary CWM. Install CWM on
this workstation if it is not already installed, or cold start -F if CWM is already installed on this new
workstation.
Note Do not cold start -F without first verifying that a Secondary CWM has s witched over to become
the new Primary CWM of the domain, otherwise the node_id and other user data will become
inconsistent.
Step 6 To ensure a manual re-sync of user data tables between the original S econdary CWM and a new Primary
CWM, enter usrtblDBsync <cwmws3> on the new Primary CWM.
Step 7 Edit the new Primary’s DomainGat ew a yL is t so that it includes it sel f. For example, let’s say that a
new Primary CWM named cwmws3 has been brought into the domain, its DomainGatewayList
would look like this: