Cisco Systems DOC-7812945= User Manual
11-13
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter 11 CWM to CWM Communications
Recovering From Degrade Mode
–
To recover from this degraded mode of operation, re-establish IP connectivity on the Primary
CWM and the Secondary CWM will automatically re-sync user data tables with the Primary
CWM.
CWM and the Secondary CWM will automatically re-sync user data tables with the Primary
CWM.
–
If you can’t re-establish IP connectivity on the Primary, then eliminate the downed Primary
from the CWM domain by following these steps:
from the CWM domain by following these steps:
Step 1
Manually remove the downed Primary from the Secondary CWM’s DomainGatewayList in the
CWMGateway.conf file
CWMGateway.conf file
The following is an example of a CWMGateway.conf file with a DomainGatewayList consisting of
two CWM workstations named cwmws1 and cwmws2, with cwmws1 assigned as the Primary and
cwmws2 as the Secondary:
two CWM workstations named cwmws1 and cwmws2, with cwmws1 assigned as the Primary and
cwmws2 as the Secondary:
Debug level 2
DomainGatewayList cwmws1 cwmws2
ForcedSwitchOver
HeartBeatInterval 20
The above DomainGatewayList, for example, would need to be edited to show that the downed Primary
(cwmws1) has been removed from the Secondary CWM’s (cwmws2) DomainGatewayList in the
CWMGateway.conf file. In this example, you would remove the downed Primary from the cwmws2
DomainGatewayList to include only cwmws2:
(cwmws1) has been removed from the Secondary CWM’s (cwmws2) DomainGatewayList in the
CWMGateway.conf file. In this example, you would remove the downed Primary from the cwmws2
DomainGatewayList to include only cwmws2:
Debug level 2
DomainGatewayList cwmws2
ForcedSwitchOver
HeartBeatInterval 20
Step 2
Manually remove the Secondary CWM (cwmws2) from the downed Primary’s DomainGatewayList in
the CWMGateway.conf file
the CWMGateway.conf file
The following is an example of the downed Primary’s DomainGatewayList after removing the
Secondary CWM from the downed Primary’s DomainGatewayList, leaving the Primary cwmws1 in its
own domain:
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.
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 switched over to become
the new Primary CWM of the domain, otherwise the node_id and other user data will become
inconsistent.
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 Secondary CWM and a new Primary
CWM, enter usrtblDBsync <cwmws3> on the new Primary CWM.
CWM, enter usrtblDBsync <cwmws3> on the new Primary CWM.
Step 7
Edit the new Primary’s DomainGatewayList so that it includes itself. For example, let’s say that a
new Primary CWM named cwmws3 has been brought into the domain, its DomainGatewayList
would look like this:
new Primary CWM named cwmws3 has been brought into the domain, its DomainGatewayList
would look like this: