Advanced Device Configuration > Address Configuration for Connected Devices > Example 3: Virtual Network With Two Private Subnets and VPN Configuration > Enabling Native IP and Accessing a Device’s Native Features Using Virtual Network Addresses for Example 3

Enabling Native IP and Accessing a Device’s Native Features Using Virtual Network Addresses for Example 3
After creating the VPN tunnel as described in IPSec VPN Configuration for Example 3 or PPTP VPN Configuration for Example 3, the user enables native IP and accesses a device’s native features.
In this example, to access “sp4,” which is a type of service processor that does not work with virtual network addresses because it is not compatible with DNAT, the user would enter the OnBoard’s real address, as described in Enabling Native IP and Accessing a Device’s Native Features Using Real IP Addresses for Example 2.
Enabling Native IP Access for Example 3
In this example, to enable native IP access to “sp1,” “sp2,” or “sp3,” the user would enter the OnBoard’s virtual IP address, which is 172.20.0.1, in one of the two following ways:
Use ssh to connect to the OnBoard’s console and to access the rmenush menu in one of the following ways:
ssh username :@172.20.0.1
ssh -t username :@172.20.0. menu
OR
Use ssh to execute the nativeipon command directly using the device alias:
ssh username : device_alias @172.20.0.1 nativeipon
Accessing Native Features for Example 3
After enabling native IP access, the user can access one of the desired native features that may be available on the device, including:
In the Web Manager on the OnBoard, clicking the “Go to native web interface” link on the Access Devices screen.
On the user’s workstation, on the command line, entering the ssh command with the name/alias of the device along with the virtual IP address of the OnBoard.
For example, see the following ssh command line entered by the user named “allSPs” to access “sp2” using the OnBoard’s virtual IP address 172.20.0.1.
ssh -t allSPs:sp2@172.20.0.1
A management application, which may be accessed in one of the following ways, depending whether the application is a client on the user’s workstation or resides on the service processor:
If the management application resides on the service processor, and is an executable that can be invoked on the command line, by accessing the service processor’s console first in one of the following two ways:
Invoking ssh with the spconsole command in the following format
ssh -t allSPs:sp2@172.20.0.1 spconsole
OR
In the Web Manager on the OnBoard, clicking the “Service Processor Console” link on the Access Devices screen.
AND
Invoking ssh with the devconsole command in the following format
ssh -t allSPs:sp2@172.20.0.1 devconsole
OR

Advanced Device Configuration > Address Configuration for Connected Devices > Example 3: Virtual Network With Two Private Subnets and VPN Configuration > Enabling Native IP and Accessing a Device’s Native Features Using Virtual Network Addresses for Example 3