Cisco Systems DOC-7812945= 사용자 설명서
11-9
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
Step 11
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.
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.
One Secondary CWM has lost IP connectivity with the Primary CWM
–
To recover from this degraded mode of operation, re-establish IP connectivity on the Secondary
CWM, and the Secondary CWM will automatically re-sync the user data tables with the Primary
CWM.
CWM, and the Secondary CWM will automatically re-sync the user data tables with the Primary
CWM.
Note
IP Connectivity is still maintained between the Primary CWM and the other Secondary CWMs
in this scenario. Only the Secondary CWM that has lost IP connectivity with the Primary CWM
will be working in the degrade mode until its IP connectivity is re-established.
in this scenario. Only the Secondary CWM that has lost IP connectivity with the Primary CWM
will be working in the degrade mode until its IP connectivity is re-established.
The CWM Gateway process dies on the Primary and is NOT restarted by
watchdog
watchdog
–
To recover from this degraded mode of operation, warm start only on the Primary CWM. In this
case the original Primary CWM is still the designated Primary CWM, and the Secondary CWMs
automatically re-sync user data tables.
case the original Primary CWM is still the designated Primary CWM, and the Secondary CWMs
automatically re-sync user data tables.
Note
User data provisioning is still in progress on the Primary CWM without the CWM Gateway
process running. Additionally, in this case, the Primary CWM still has connectivity with all
Secondary CWMs.
process running. Additionally, in this case, the Primary CWM still has connectivity with all
Secondary CWMs.
–
If a Warm start does not work, then eliminate the downed Primary from the CWM domain by
following these steps:
following these steps:
Step 1
Manually remove the downed Primary from all the other CWM’s DomainGatewayLists in the
CWMGateway.conf file
CWMGateway.conf file
The following is an example of a CWMGateway.conf file with a DomainGatewayList consisting of
three CWM workstations named cwmws1, cwmws2, and cwmws3, with cwmws1 assigned as the
Primary and cwmws2 and cwmws3 assigned as Secondaries:
three CWM workstations named cwmws1, cwmws2, and cwmws3, with cwmws1 assigned as the
Primary and cwmws2 and cwmws3 assigned as Secondaries:
Debug level 2
DomainGatewayList cwmws1 cwmws2 cwmws3
ForcedSwitchOver
HeartBeatInterval 20
The above DomainGatewayList, for example, would need to be edited to show that the downed Primary
has been removed from all the other CWM’s DomainGatewayLists in the CWMGateway.conf file. In
this example, you would remove the downed Primary from both cwmws2 and cwmws3
DomainGatewayLists to include only cwmws2 and cwmws3 Secondaries in the same domain:
has been removed from all the other CWM’s DomainGatewayLists in the CWMGateway.conf file. In
this example, you would remove the downed Primary from both cwmws2 and cwmws3
DomainGatewayLists to include only cwmws2 and cwmws3 Secondaries in the same domain:
Debug level 2
DomainGatewayList cwmws2 cwmws3