Enabling Native IP and Accessing a Device’s Native Features Using Real IP Addresses for Example 2After creating the VPN tunnel as described in IPSec VPN Configuration for Example 2 or PPTP VPN Configuration for Example 2, the user uses the OnBoard side IP address configured for the appropriate private subnet to access the OnBoard, and then enables Native IP access to the desired device.In this example, to enable native IP access on “sp1” or “sp2” on “sub1,” the user would enter the OnBoard side IP address for “sub1” (which is 192.168.1.1) in one of the two following ways:
• Bring up the Web Manager using http://192.168.1.1.
• Use ssh to connect to the OnBoard’s console and to access the rmenush menu in one of the following ways:
• Select “Enable native IP” from the list of management actions the user is authorized to perform on the device.
• 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, entering the IP address or DNS-resolvable name of the device in a browser.
• On the user’s workstation, on the command line, entering the ssh command with the name/alias of the device along with the IP address of the OnBoard side address for the subnet where the device resides.For example, see the following ssh command line entered by the user named “allSPs” to access “sp2” on the private subnet whose OnBoard side IP address is 192.168.1.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 user's workstation, by bringing it up from there.
• 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:
•
• In the Web Manager on the OnBoard, clicking the “Service Processor Console” link on the Access Devices screen.
• Bringing the management application up from the service processor’s command line.
• The console of the server on which the service processor resides, in one of the following two ways:.
•
• In the Web Manager on the OnBoard, clicking the “Device Console” link on the Access Devices screen.