...
<NETWORKING ARCHITECTURE, L1, L2, L3 and BGP>
LAG Configuration
DHCP, HTTP PXE and PXE Booting
Network Cloud family blueprint deployments involves involve a number of different DHCP servers and http pxe and pxe HTTP PXE and non HTTP PXE booting procedures during the automatic deployment process.
...
When installed on a bare metal server, the RC is configured by the Redfish API calls issued by the Build Server to make DHCP Requests and then HTTP PXE boot over its vlan tagged 'host' network interface. (When installed in a VM the BIOS setting and operating system install and thus these steps are skipped).
The Build Server acts as the DHCP and HTTP PXE boot server for the RC via its own 'host' network interface.
The 'host' network spans must provide connectivity for these processes between the RC and the Build Server.
...
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Rover Deployment
The Rover server is configured by the Redfish API calls issued by the RC to make DHCP Requests and then HTTP PXE boot over its vlan tagged 'host' network interface.
The RC acts as the DHCP and HTTP PXE boot server for the Rover server via its own tagged 'host' network interface.
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 verified as a single L2 broadcast domain.
It is possible to split the 'host' network spanning the WAN into multiple routed L2 domains using functionality such as DHCP helper/relay functionality on the Rover's TOR but this is unverified in R1.
...
The RC acts as the DHCP and HTTP PXE boot server for the Unicycle genesis node via its own tagged 'host' network interface.
The 'host' network spans must provide connectivity across the WAN between the the Unicycle pods's edge site and the RC in a more centralized location.
...