At least one private subnet must be defined on the OnBoard for the following purposes:
• To define a private OnBoard address for the OnBoard and connected devices to use when communicating.
• To enable communications between remote user’s workstations on the Internet or local user’s on the same LAN and connected devices on the private management network, via the OnBoard’s Native IP access facility.The private Ethernet ports are accessed through the priv0 interface on the OnBoard, which interacts with connected devices through an internal switch.The OnBoard attempts to reach a device that does not have a private subnet assigned by attempting to contact it through the OnBoard’s default route. Therefore, unless the OnBoard administrator defines a private subnet and assigns it to each device, the device cannot be reached unless the device is on the public side of the OnBoard. In almost all cases, devices are on the private side of the OnBoard and therefore they are unreachable without a private subnet.
• When the connected devices’ addresses are all within the same range, only one private subnet is required.
• The administrator should assign IP addresses to all service processors from the same block of addresses, if possible, to make it possible to administer the IP addresses using only a single private subnet.
• When the connected devices’ addresses are already configured in multiple ranges and the addresses cannot be changed, or when for some other reason, connected devices must have addresses in multiple address ranges, multiple private subnets must be created. (To simplify routing for PPTP VPN connections, multiple private subnets may also require configuration of a virtual network, as described in Why Define Virtual (DNAT) Addresses?.)
• The priv0 interface, which is used for all the private Ethernet ports, is not assigned an IP address unless a private subnet is configured.The following screen example shows the default ifconfig output for priv0., which shows no IP address.
The OnBoard administrator must define IP address or addresses for priv0 by defining private subnet(s). When multiple private subnets exist, their IP addresses are assigned to aliases of priv0, such as priv0:sub1 and priv0:sub2.