book
Article ID: CTX270917
calendar_today
Updated On:
Description
This article describes how to avoid configuration mismatch or lose, which is triggered by exceptional use cases, in ADC HA system.
Instructions
Exceptional cases
- secondary node is recovered from sometime down during which some configuration has been modified or new settting has been configured on primary node
- device replacement
Steps to be executed one by one 1. wait until HA replication status is good after system recovers from exceptional cases
following is a sample which indicate the status is ok
> show ha node
1) Node ID: 0
IP: 1.1.1.1 (12.1-51.19-1)
Node State: UP
Master State: Primary
Fail-Safe Mode: OFF
INC State: DISABLED
Sync State: ENABLED
Propagation: ENABLED
Enabled Interfaces : 1/1
Disabled Interfaces : None
HA MON ON Interfaces : 1/1
HA HEARTBEAT OFF Interfaces : None
Interfaces on which heartbeats are not seen : None
Interfaces causing Partial Failure: None
SSL Card Status: NOT PRESENT
Hello Interval: 200 msecs
Dead Interval: 3 secs
Node in this Master State for: 0:1:3:38 (days:hrs:min:sec)
2) Node ID: 2
IP: 1.1.1.2
Node State: UP
Master State: Secondary
Fail-Safe Mode: OFF
INC State: DISABLED
Sync State: SUCCESS
Propagation: ENABLED
Enabled Interfaces : 1/1
Disabled Interfaces : None
HA MON ON Interfaces : 1/1
HA HEARTBEAT OFF Interfaces : None
Interfaces on which heartbeats are not seen : None
Interfaces causing Partial Failure: None
SSL Card Status: NOT PRESENT
Local node information:
Critical Interfaces: 1/1
Done
2. run following command from any of node to synchronize files related to system configuration from the primary node to the secondary one
sync HA files all
3. run following command from any of node to copy all system configuration from the primary node to the secondary one
force HA sync -force -save yes