Dynamic Redundancy (BGP)
In this deployment example, we will configure the Anapaya EDGE to dynamically advertise routes that are reachable.
IP prefixes that are learned from the SCION network are advertised to the LAN via BGP, conversely, IP prefixes that are reachable in the LAN need to be advertised to the EDGE appliances via BGP as well. When an IP prefix is no longer reachable via the SCION network, it is retracted from BGP and the LAN will no longer use that EDGE appliance to reach the SCION network.
In the dynamic redundancy setup both EDGE appliances can be used for outgoing traffic simultaneously, this can be influenced by the operator of the LAN side BGP router.
Refer to the Getting Started Setup guide for step-by-step instructions on how to interact with the Anapaya appliance.
Information
The configuration examples below are based on the disconnected EDGE setup and need to be adapted to your specific setup.
Additional information provided by the customer
| BGP Router | Router IP | ASN |
|---|---|---|
| EDGE 1 | 10.11.0.6 | 65011 |
| EDGE 2 | 10.12.0.6 | 65012 |
| LAN side 1 | 10.11.0.5 | 65001 |
| LAN side 2 | 10.12.0.5 | 65002 |
BGP
The following BGP section is added to configure the eBGP session between the EDGE appliances and their respective BGP router in the internal network.
- EDGE 1
- EDGE 2
IP-in-SCION tunneling
The IP-in-SCION tunneling
section needs to be adjusted.
The static_announcements list is no longer required. Instead, the EDGE appliances propagate the IP
prefixes that are received via BGP from the LAN side routers to the SCION network. The rest of the
IP-in-SCION tunneling configuration remains the same as in the disconnected EDGE setup
example.
- EDGE 1
- EDGE 1 (diff)
- EDGE 2
- EDGE 2 (diff)
Complete configuration
For completeness, we provide the full configuration of the EDGE appliance:
- EDGE 1
- EDGE 1 (diff)
- EDGE 2
- EDGE 2 (diff)