Filter
Top Products
11-5
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter 11 CWM to CWM Communications
Configuring CWM-CWM Communications
• DomainGatewayList—a list of remote gateways or the other CWM workstations that are part of
this CWM domain. These workstations are either running Release 10 of CWM or will be at some
point in the future. There must be IP connectivity between all of the CWM workstations listed. The
DomainGatewayList parameter lists the CWM workstation hostnames that are part of a given
domain and enables communication between these workstations. It is required that all CWM
workstations in a domain have the same DomainGatewayList in their CWMGateway.conf file. If a
given CWM workstation is the only one managing a network, you do not have to specify this
parameter.
Note The network.conf file does not have to be the same on all CWM stations in the domain as long
as the gateway nodes specified in this file are part of the same network. Even though CWMs that
manage the same network can talk to each other, managing the same network does not require
having identical network.conf files on all Secondary and Primary CWMs.
• Forced Switchover—tells a CWM workstation (if it is Primary) to hand over that role to another
CWM workstation and become a Secondary CWM workstation. The ForcedSwitchOver parameter
indicates a Secondary CWM gateway that assumes the role of Primary CWM gateway when the
Primary releases that role. This parameter is only used by the Primary CWM gateway. The Forced
Switchover hostname field is empty by default.
Three conditions are required for a forced switchover to take effect:
• The local CWM gateway must be running as the Primary
• The remote CWM gateway designated by the ForcedSwitchOver parameter must be up and running
• The remote CWM gateway designated by the ForcedSwitchOver parameter must have IP
connectivity between the Primary CWM gateway and the Secondary CWM gateway
This option is not read at startup or in response to an HUP or USR1 signal, but processed only in response
to a USR2 signal.
To initiate a forced switchover follow these steps:
a. Verify that the nominated Secondary host is in the same domain as the Primary host and that CWM
is up and running
b. Edit the CWMGateway.conf file manually (with vi or another editor) using the ForcedSwitchOver
cwmwsx
command, and set the host name of the nominated Secondary to the ForcedSwitchOver on
the Primary
c. Retrieve the process id (pid) of the CWMGateway on the Primary and send a USR2 signal to the
CWM gateway on the Primary
• Heartbeat Interval—tells the CWM gateway how often to send the heartbeat signal. Values for the
Heartbeat Interval must be the same among all CWM workstations in the same domain.The
Heartbeat Interval indicates the interval at which the Primary CWM will send the heartbeat signal
to the Secondary CWM. If a Secondary CWM fails to detect two consecutive heartbeat signals, it
assumes a loss of connectivity with the Primary CWM. There will be no switchover in this situation.
The Secondary CWM will log an L1 message, and print an error message on the console, indicating
that it has lost connectivity to the Primary CWM. 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
CWM will work in a degraded mode of operation until, and unless, the heartbeat is restored with the
Primary CWM.