Appendices : Device Configuration : Routing requirements for native IP access

Routing requirements for native IP access
As documented in the Cyclades OnBoard Service Processor Manager User Guide, users who are authorized for native IP access need to create a IPSec or PPTP VPN connection before gaining native IP access.
Any routes needed for IPSec VPN can be configured as part of the IPSec connection by setting the nexthop to the IP address of the desired network or host route and setting the boot action to Add and route.
Any route(s) needed for PPTP must be configured manually.
See IPSec VPN configuration for example 2, PPTP VPN configuration for example 2, IPSec VPN configuration for example 3 and PPTP VPN configuration for example 3, which discuss routing requirements for the two types of VPN connections and show example routes.
Example 1: Private Subnet Configuration
Figure D.1 shows a private subnet configuration example.
Example 1: Private Subnet
In Figure D.1, two devices are connected to the OnBoard appliance. The public Ethernet port on the OnBoard appliance has a public IP address of 203.1.2.3. The administrator plans to assign the following:
Two private IP addresses within the 192.168.49.0 network range to the devices on the OnBoard appliance’s private network: 192.168.49.60 and 192.168.49.61,
Figure D.2 shows the values the administrative user would enter in the Web Manager to configure the private subnet shown in Figure D.1.
Private Subnet Configuration Example
Figure D.2 shows the following values entered in the dialog that appears when the Add Subnet button is clicked on the Network-Private subnets screen:
The private subnet address derived from the configuration in Figure D.2 is 192.168.49.0. For this network IP address, the conventional broadcast address is 192.168.49.255. Because the OnBoard’s address is 192.168.49.254, the administrator can assign any remaining IP address between 192.168.49.1 and 192.168.49.253 when configuring a connected device.
The following figure shows these values: Private subnet privnet and Device IP address 192.168.49.61 assigned to the device rack1_dev2_compaq_ilo on the Web Manager-Config Devices screen, as part of the implementation of the configuration shown in Figure D.1.
Example 1: Device Configuration Example
As shown in the following example, the new private subnet name and the OnBoard appliance-side IP address and subnet mask from Figure D.2 are assigned to the priv0 interface.
Example 2: Two Private Subnets and VPN Configuration
Figure D.4 shows an example with four devices. Two subnets must be created because the devices sp3 and sp4 have IP addresses that cannot be changed, and their addresses are not in the same network range as the other two devices. Configuration details follow, including how to set up VPN connections.
Example 2: Two Private Subnets