Concerning the network interface and ip needs – support portal

Network Interface Needs

All the network interfaces on every server (WAN, LAN, iLO) are 1Gbit Ethernet interfaces which are configured to auto-negotiate both speed and duplex setting.
The network devices the interfaces are now being linked to must similarly get their port speeds configured to auto-negotiate both speed and duplex setting.
You should ensure you will find sufficient spare physical network ports for connecting the server towards the WAN and LAN systems – additional network switches might be needed.
The WAN and LAN IP addresses Should be on the different subnets.

Ip Needs

The next IP addresses are needed for connecting the server towards the WAN and LAN:

one IP for that WAN connection
one IP for that LAN connection
one IP for that iLO connection of every server. For those who have a HA cluster, there’s two servers which means you require an Ip for every iLO. (therefore as many as 2 IP addresses needed)

Network Interface Needs

All the network interfaces on every server (WAN, LAN, iLO) are 1Gbit Ethernet interfaces which are configured to auto-negotiate both speed and duplex setting.
The network devices the interfaces are now being linked to must similarly get their port speeds configured to auto-negotiate both speed and duplex setting.
You should ensure you will find sufficient spare physical network ports for connecting the server towards the WAN and LAN systems – additional network switches might be needed.
The WAN and LAN IP addresses Should be on the different subnets.

Ip Needs

The next IP addresses are needed for connecting the server towards the WAN and LAN:

one IP for that WAN connection
one IP for that LAN connection
one IP for that iLO connection of every server. For those who have a HA cluster, there’s two servers which means you require an Ip for every iLO. (therefore as many as 2 IP addresses needed)

The Ip for that LAN connection ought to always be a personal, static IPv4 address. The IP addresses for that WAN and iLO connections should be IPv4 addresses however these might be private or public with respect to the selected deployment scenario.

All public IP addresses utilized by the server should be routing IPv4 addresses having a router default gateway within the same public subnet.
They shouldn’t be bridged, dynamic or PPPoE/PPPoA and shouldn’t have any NAT, QoS, inbound or outbound firewall rules or any other traffic management.

Note – you can find more choices for the iLO IP, including getting it left unpatched unless of course needed, by which situation it may share the WAN IP – make reference to this short article to learn more