11-7
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter1 1 CWM to CWM Communica tions Recovering From Degrade Mode
Note An Abnormal Exit happens when a CWM Gateway process is stopped through a non-graceful
shutdown. This includes when a proc ess ha s be en s top ped wi th a process core dump command,
but does not include a power down.
Unexpected Exit of the Primary CWMGateway
The unexpected exit of the Primary CW MGateway will be detected by the Seco n da ry C W M G at eway
through the Orbix callback (CORBA::IT_ I O Ca llb ac k) mechanism, which is invoked when the CORBA
connection between them is broken (provi de d th at the re is IP co nnect ivity between the Primary and the
Secondary). The CWMGateway process w ill automatically be restarted by watchd og up to 5 times. Once
the Primary is restarted it wi ll n ot if y all S ec on d ar ies. Upon receiving this event, a Secon d ar y
CWMGateway will re-register with th e P rim ar y.
If all Secondaries did not receive notification of the Primary restart either due to the Primary CWM’s
failure to restart after five attempts, or beca use IP connectivity was lost betwe en the Secondary and the
Primary, the Secondaries will continue to work as Secondaries with no Primary CWM present, in a
degraded mode of operation.
Unexpected Exit of the Secondary CWMGatewa y
The unexpected exit of a Secondary C W M G ateway wi ll be detected by the Primary C W M G at eway
through the Orbix callback (C OR BA::I T_ IO C al lb ack ) mec hanism. The Primary CWMG at eway will
reassign the priority (decremented by 1) of all Secondary CWMGateways whose priority number was
higher than the priority number of the departed Secondary, and will remove the client entry
corresponding to this Secondary CWMGateway from its list.
Primary CWM has lost IP or physical connectiv i t y t o all S econdary CWMs
–
To recover from this degrade d m od e of operation, re-e s tab li sh IP connectivity on t he Primary
CWM and then all Secondary CW M s w il l au to m at ic ally re-sync their user data tab le s with the
Primary CWM.
–
If you can’t re-establish IP connectivity on the Primary, then eliminate the downed Primary
from the CWM doma in by f ol lowing these steps:
Step 1 Manually remove the dow n ed Primary from all the ot he r CWM’s DomainGatewayList in the
CWMGateway.conf file
The following is an example of a CWMGateway.conf file with a DomainGatewayList consisting of
three CWM workstations named c w mw s 1, cwm w s2 , a nd cwmws3, with cwmws1 ass i gned as th e
Primary and cwmws2 and cwmws3 a s sig ne d as S e co nd arie s:
Debug level 2
DomainGatewayList cwmws1 cwmws2 cwmws3
ForcedSwitchOver
HeartBeatInterval 20