Cisco Systems DOC-7812945= 사용자 설명서
11-14
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
Debug level 2
DomainGatewayList cwmws3
ForcedSwitchOver
HeartBeatInterval 20
Step 8
Start the core on the new Primary CWM (in this example it would be cwmws3).
Step 9
Stop the core on the original Secondary CWM (in this example it would be cwmws2).
Step 10
Edit the original Secondary CWM’s DomainGatewayList so that it includes itself and the new
Primary CWM. For example, its DomainGatewayList would look like this:
Primary CWM. For example, its DomainGatewayList would look like this:
Debug level 2
DomainGatewayList cwmws2 cwmws3
ForcedSwitchOver
HeartBeatInterval 20
Step 11
Edit the new Primary CWM’s DomainGatewayList so that it includes itself and the original
Secondary CWM. For example, its DomainGatewayList would look like this:
Secondary CWM. For example, its DomainGatewayList would look like this:
Debug level 2
DomainGatewayList cwmws2 cwmws3
ForcedSwitchOver
HeartBeatInterval 20
Step 12
Start the core on the original Secondary CWM (in this example it would be cwmws2).
Loss of Heartbeat from Primary CWMGateway
A Secondary CWMGateway will consider itself disconnected from the Primary, and in a degraded mode
of operation, if it fails to receive a heartbeat message during two successive heartbeat intervals. There
will be no switchover in this situation. The Secondary CWMGateway will log an L1 message and a print
error message on the console indicating that it has lost connectivity to the Primary CWMGateway. This
will be repeated every 60 seconds. It will go back to the normal mode of operation once the heartbeat
message has been received. The Secondary CWMGateway will work in a degraded mode of operation
until, and unless, the heartbeat is restored from the Primary.
of operation, if it fails to receive a heartbeat message during two successive heartbeat intervals. There
will be no switchover in this situation. The Secondary CWMGateway will log an L1 message and a print
error message on the console indicating that it has lost connectivity to the Primary CWMGateway. This
will be repeated every 60 seconds. It will go back to the normal mode of operation once the heartbeat
message has been received. The Secondary CWMGateway will work in a degraded mode of operation
until, and unless, the heartbeat is restored from the Primary.
Note
The Secondary CWMs will receive heartbeat messages from the Primary CWM as soon as the
connection has been re-established, if either end (Primary or SecondaryGateway) is restarted, or
if the problem for an existing connection has been resolved (i.e. change a broken network cable).
There is no dependency between sending heartbeat messages from the Primary CWM to the
Secondary CWM, and CWM sync-up with the managed network.
connection has been re-established, if either end (Primary or SecondaryGateway) is restarted, or
if the problem for an existing connection has been resolved (i.e. change a broken network cable).
There is no dependency between sending heartbeat messages from the Primary CWM to the
Secondary CWM, and CWM sync-up with the managed network.