Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

01- HA High Availability ( Training and Conductor onboarding )

Terraform automarion:  HA Conductor on Azure with Terraform

initialize
node1redo the initialization as HA with Node1 and node2 
node2redo the initialization as HA with Node1 and node2 
Global configCreate two nodes
Clock Synchronizationauthority > router > system > ntp
DNS configStatic DNS ( 1.1.1.1 and 8.8.8.8 )

Management flag = True

( to allow NDS, NTP: "mgt" protocols SNMP, . . . )

HA-Sync Interface

Redundancy link

Option 1: Directly connected ( cable between the two nodes )

only SYNC Interface:  Fabric IF + non-forwarding


https://docs.128technology.com/docs/config_non_forwarding_ha_interfaces
Device-interface:Forwarding = False  ( stay in Linux )


Netw interface

Basic Information, type: Fabric

IP@ / 30

Linux

ifcfg Option: ZONE= trusted

>> allow to conductor to talk to the node, thru the other node

Restart 128T

Option 1: Not-Directly connected ( switch / router between the two nodes )

Shared + non-forwarding



Netw interface


Basic Information, type: Shared

IP@ / 30 or else



HA-Fabric interface:

Option 2: Fabric ( directly connected) + Forwarding

this interface is a forwarding interface between two nodes in a router,



Device-interface:

Forwarding= True

PCI Address:


Netw interfaceBasic Information, type: Fabric

Restart 128T
Clone the node1


Node2 softwaremake sure node has the same software release

WAN LinkOption 1: Shared physical

1- same shared mac address 
2- same global ID
Device-interfacecreate a "Shared physical/ MAC addresses"  ( copy Node 1) 
Network-interface( first node1 ) clear the global id   ( copy Node 1) 
Redundancy Groupredundancy-group configuration

@Router > Redundancy Group>>> Node2,

  • Priority 10 
  • Group members ( all interfaces )
    one redundancy group per network-Interface


WAN LinkOption 2: VRRP

/wiki/spaces/JS/pages/2231238657


LAN Link
device

Device-interface

shared-phys-address 0C:C4:7A:AB:37:8D


Both have exactly the same config

  • No labels