You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »


<NETWORKING ARCHITECTURE, L1, L2, L3 and BGP>


LAG Configuration



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.

Regional Controller Deployment

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 must provide connectivity for these processes between the RC and the Build Server. 

In R1 the 'host' network is verified as a single L2 broadcast domain.

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 DHCP helper/relay functionality on the Rover's TOR but this is unverified in R1.

Unicycle Pod Deployment

A Unicycle pod's genesis node 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 Unicycle genesis node via its own tagged 'host' network interface.

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 verified as a single L2 broadcast domain.

Unicycle masters and workers (all unicycle nodes other than genesis), make DHCP Requests on the edge site's local 'pxe' network's L2 broadcast domain. The genesis node's MaaS acts as the DHCP server.

Unicycle masters and workers (all unicycle nodes other than genesis) are configured by the MaaS server running on the genesis node to PXE boot over the remote site's 'pxe' network.

It is possible to split the 'host' network spanning the WAN into multiple routed L2 domains using functionality such as DHCP helper/relay but this is unverified in R1.









  • No labels