Geo Replication
Geo replication is used for inter-rack/site communication and for POD/VIP/BFD monitoring within the rack. In Geographic Redundancy,
-
Two instances of Geo pods are running for each rack/site.
-
Two Geo pods functions in Active-Standby mode.
-
Each Geo pod instance is spawned on different Proto node/VM.
-
Geo pod running on the Proto node/VM having VIP is Active Geo pod.
-
In the event of Active Geo pod restart, VIPs are switched to other Proto node/VM and Standby Geo pod running on the other Proto node/VM becomes active.
-
Geo pod uses host networking mode (similar to UDP-Proxy).
-
Geo pod uses two VIPs:
-
Internal-VIP for Inter-POD communication (within the rack)
-
External-VIP for Inter-Rack Geo pod communication. Configure only on Proto Nodes on L2 Subnet. This is used to communicate across the racks. This node has external connectivity to other Rack.
-
-
Logical-NF-InstanceID should be configured same for both cnSGW-CsSMFs in GR-Pair
-
For KeepAliveD monitoring,
-
Geo pod uses base port as: 15000+(Logical-NF-InstanceID * 32) + 4
Geo pod base port should be different than BGP speaker pod port.
-
Default port (without logical cnSGW-CSMF) would be: 15004
-
For Logical cnSGW-CSMF configured with logical-nf-instance-id as 1, the port would be: 15036
-
-
UDP-Proxy pod uses base port as : 28000+Logical-NF-InstanceID
-
Default port (without logical cnSGW-CSMF) would be: 28000
-
For Logical cnSGW-CSMF configured with logical-nf-instance-id as 1, the port would be: 28001
-
-
BGPSpeaker-pod uses default base port as: 20000+(Logical-NF-InstanceID * 32)+4
-
Default port (without logical cnSGW-CSMF) would be: 20004
-
For Logical cnSGW-CSMF configured with logical-nf-instance-id as 1, the port would be: 20036
-
-
Note | Only ETCD and cachepod data is replicated to standby rack. |