...
Physical Networking Architecture Considerations
<INSERT DETAILS OF TARGET GEOGRAPHICAL CONSIDERATIONS OF WAN and EDGE SITE LANS TO SUPPORT CENTRALIZED RC AND GEOGRAPHICALLY DISTRIBUTED EDGE PODS>
...
The Network Cloud blueprints deploy Rover and unicycle pods at multiple edge locations driven by a regional controller. As such the networking architecture spans the WAN between the RC and edge pods as well as the edge sites themselves.
Clearly it is not desirable to span L2 broadcast domains over the WAN nor is it desirable to span L2 domains between edge sites. Thus the networking architecture allows for deployment using local isolated L2 domains at each edge site as well as support for IP connectivity only across the WAN.
Layer 2 Architecture
LAG Considerations
The RC (when installed on bare metal, Rover and Unicycle genesis nodes boot via their VLAN tagged 'host' interfaces which are pre-provisioned on the serving TOR switches with LAG bonding. Since booting occurs before the linux kernel can bring up its LAC-P signaling the TOR switches must be configured to pass traffic on their primary (first) link before the LAG bundle is up.
...
| draw.io Diagram | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
DHCP, HTTP PXE and PXE Booting
...