System information

Appendix A: Advanced Device Configuration 403
Address Configuration for Connected Devices
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:
• A native web application, which may be accessed in one of the following
ways:
• 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 virtual IP address 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 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 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:
• 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