...
<NETWORKING ARCHITECTURE, L1, L2, L3 and BGP>
LAG Configuration
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.
The switch configuration for the network bond for the 'host' interfaces must be set to bring up the bond on the first interface prior to lacp completing negotiation.
- For Junos OS this option is typically called force-up and should be set on the first interface in the bond.
- For Arista, this option is typically called lacp fallback.
- Please ensure any TOR switch that is to be used supports this functionality and then refer to your network switch documentation to determine the correct configuration.
The 'host' network interfaces on all DHCP clients and servers must be located on the same L2 network so that the DHCP Request messages broadcast from the client reach the server and vice versa. Alternatively DHCP helper/relay functionality may be implemented on the TOR to which the DHCP clients are attached to allow inter subnet DHCP operation between DHCP client and server.
<Update to show RC, Rover, Genesis as Clients and Build server and RC as servers>
DHCP, HTTP PXE and PXE Booting
Network Cloud family blueprint deployments involve a number of different DHCP servers and HTTP PXE and non HTTP PXE booting procedures during the automatic deployment process.
...
The 'host' network must provide connectivity for these processes between the RC and the Build Server.
In R1 the 'host' network is has been verified as a single L2 broadcast domain.
...
The 'host' network must provide connectivity across the WAN between the Rover edge site and the RC in a more centralized location.
In R1 the 'host' network is has been verified as a single L2 broadcast domain.
...
The 'host' network must provide connectivity across the WAN between the Unicycle pods's edge site and the RC in a more centralized location.
In R1 the 'host' network is has been verified as a single L2 broadcast domain.
...