Image Streamer IPv4 address requirements

When planning for IPv4 subnets and addresses for Image Streamer configurations, consider the following:

For the management network:

  • Reserve six (6) static IP addresses for each Image Streamer pair residing on the network with the HPE OneView user interface IP address.

    As you add Image Streamer appliances over time, add additional IP addresses as needed.

  • Identify a VLAN tag to be used for the management network. A tagged network is highly recommended to facilitate connection to compute modules at a later time.

  • Note that choosing a VLAN for this network does not cause the Frame Link Module connections to the management network to have tagged traffic. (No top-of-rack management switch configuration is required for this VLAN.)

For the Image Streamer deployment network:

The deployment network is an isolated, private network for connecting Image Streamer hosted boot volumes to the compute modules.

As a best practice:

  • While the guideline is to create at least two IP addresses per compute module plus six IP addresses for each pair of Image Streamer devices, plan to define a private subnet with 254 IP addresses in the pool. (e.g. Subnet ID 192.168.12.0; netmask 255.255.255.0; range: 192.168.12.2 - 192.168.12.254; will support 123 compute modules)

  • To support a full 21 frames or 252 compute modules, a larger private subnet needs to be defined. (e.g. Subnet ID 192.168.12.0; netmask 255.255.252.0; range: 192.168.12.2 - 192.168.15.254)

  • Identify the VLAN tag to be used for the deployment network. Any value can be used as long as it is unique and does not conflict with any other VLAN tags used in the data center.

More information