11-4
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter11 CWM to CWM Communications
Configuring CWM-CWM Com m u n ications
to take over as the new primary. The Secondary CWMGateway with priority number 1 (SP1) will now
take over as the new Primary, and any remaining CWMGateways will s ubsequently register with the new
Primary CWM. The new CWMGateway prior ity numbers will be based on “first-c ome-first-serve” logic.
Note If the Primary CWM is not shut down gracefully, then the S ec ond ary CWM c ou ld go i nt o d egr ad e mod e.
In this case, the user will ne ed to r es t ar t t he P rim a ry C W M to r e- est ablish the connection between t he
Primary and Secondary CWMs. The Secondary CWM will then re-sync the user data tables with the
restarted Primary CWM as soon as the connection has been re-established.
Note Re-sync between the Secondary CWM and Primary CWM does not depend on how fast the Primary
CWM can re-sync with the network after restart. If the Primary CWM has previously discovered all of
the nodes in the network, and popul ated i ts node _info ta ble with all net work no de data , it is not nece ssary
for the Secondary CWMs t o wai t for the Primary CWM to re -sy n c w i th the entire network. This
capability gives Secondary CWMs in a ne twork the ability to access use r da ta much faster than if they
had to wait for the Primary CWM to re-sync with the entire network.

Secondary CWM Graceful Shu t down

A Secondary CWMGateway will notify its primary counterpart before it’s shutdown gracefully. The
primary CWMGateway will assign a new priority number to the remaining Secondary CWMGateway
whose priority number is greater than the priority number of the CWMGateway that has just gone away.
The new priority number is one less than the previously assigned priority number. For example, if the
CWMGateway with priority number 1 has gone aw ay, the CWMGateway with priority number 2 will be
changed to 1 so that it becomes next in line to take over the role of the primary CWM when the current
primary CWM goes away.
Configuring CWM-CWM Communications
When a CWM workstation launch es, it reads a configuration file c alled CWMGateway.conf to determine
its initial setup and default configur ati o ns . Foll owing is an example of a CWMGateway.conf file with a
DomainGatewayList of a d om a in consisting of four CWM wo r ks t at io ns named cwmws1, cwmw s2 ,
cwmws3, and cwmws4:
Debug level 2
DomainGatewayList cwmws1 cwmws2 cwmws3 cwmws4
ForcedSwitchOver cwmws2
HeartBeatInterval 20
Parameters in this CWMGateway.conf file must be specified to enable inter-CW M communication; it is
the only list of other CWM gateway s availa bl e to this local host. Each host or CW M workstation listed
in the DomainGatewayList must be reachable from the local host. Confirm this by using th e Unix “ping”
command. The host na mes listed in the Do ma i nG a t ewa y Lis t can be presented in a ny order.
The CWMGateway.conf file in /usr/user s /sv p lu s /co n fig / sp ec ifies the following parameters:
•Debug level—tells the CWM gateway how much debugging information to generate. The valid
range for this value is 1 -5. In a production e nvironment, do not raise this value above 2. The De bug
Level is primarily used in engineering development or in a troubleshooting environment with the
assistance of technical support.