Configuration
Configuring the High Availability Feature
to monitor the X.25 link status. It could be either a script based on x25ifstate or the x25ifstate command directly, depending on your configuration.
Package Control Script Location:
location of the script to start/stop the X.25 link and execute the service(s).
X.25 High Availability Configuration
General Solution for Local and Remote Failover
PKG A Client
PKG B Client
X.25 switch
Package A
Hunt Group
X.25PDN 
Connections
Package B
Hunt Group
Connections
Alternate
Connections
(Idle)
X.25 switch
when package A is functional on system 1, system 2 is on standby for 
package A
DTE | DTE |
| DTE | DTE | DTE | DTE | DTE | DTE |
PKG | PKG |
| PKG | PKG | PKG | PKG | PKG | PKG |
A | A |
| B | B | A | A | B | B |
|
|
|
|
|
|
|
|
|
Package A |
|
|
|
|
| Package B | ||
if package A fails on system 1, system 2 
takes over package A
Example 3-4 One EXAMPLE of Remote Failure
The only file that contains the X.25 commands to run for High
Availability is the /etc./cmcluster/pkg*/control.sh file (one per
X.25 package).
# SERVICE NAMES AND COMMANDS
SERVICE_NAME [0] =pkg1.Service_Name_01 (same SERVICE_NAME as in pkg conf) SERVICE_CMD [0] =”/usr/sbin/x25ifstate
#add below the service names which define the applications that rely on the X.25 card
Chapter 3 | 81 |
