Before configuring any connected devices, the OnBoard administrator must plan and implement an IP addressing scheme that reflects the needs of the organization.As illustrated in Recommended Device Configuration the dedicated Ethernet ports on service processors and on other supported types of devices are connected to the private Ethernet ports on the OnBoard. Each connected device’s dedicated Ethernet port needs an internal IP address assigned on the OnBoard and configured for the interface. By implementing an addressing scheme, the administrator creates a pool of internal addresses that can be assigned to the devices’ dedicated Ethernet ports and configured for the device on the OnBoard side.The following IP Addressing Example shows some example IP addresses assigned:
• The OnBoard requires only one managed public IP address assigned to its primary Ethernet port. The OnBoard’s secondary Ethernet port (eth1) can optionally be used as described under Ethernet Ports on the OnBoard.
• A private subnet IP address is assigned to each service processor’s dedicated Ethernet port (192.168.49.60 and 192.168.49.61) from a private subnet network IP range of 192.168.49.0/24.Note: The IP addresses assigned to the servers’ primary Ethernet ports on the production network are not covered in this document; server’s IP addresses can be whatever suits the needs of the servers’ network administrators.
• A private IP address is assigned to the OnBoard from the same range as the devices’ IP addresses: 192.168.49.254.While implementing the addressing scheme, the administrator assigns to the OnBoard itself one or more IP addresses in addition to the OnBoard’s public IP address. The OnBoard’s private IP address or addresses are used by the following:See Address Configuration for Connected Devices for the details needed for planning and implementing IP addresses. The referenced section describes the following topics that the administrator needs to understand: