Avocent 5240 - Manual (Page 20)

8 MergePoint 5224/5240 Service Processor Manager User Guide
Native IP requirements
Native IP access requires a pre - existing secure tunnel between the user’s workstation and the
MergePoint 5224/5240 SP manager. Table 1.5 shows the native IP parameters and command
names available when you are logged into the Web Manager, when you have selected a target
device from the spshell menu on the MergePoint 5224/5240 SP manager console and when you are
entering the ssh command on a remote workstation.
After an authenticated and authorized user establishes a secure tunnel and selects the Native IP
option, the user can bring up a native web interface or launch a native web management application
from where it resides on the user's workstation or from the SP’s console.
Native IP access depends on the following being true:
• The SP must provide the desired native management functionality. For example, SPs using
IPMI protocols do not provide native web access.
• The user is authorized to access the Native IP option on an SP.
• The user has created a secure tunnel to the MergePoint 5224/5240 SP manager. An SSH tunnel
gives access to native web applications only while a VPN tunnel gives access to both native
web and native management applications.
Tasks for creating secure tunnels and obtaining native IP access
See Chapter 2 for creating information on creating secure tunnels and obtaining Native IP access.
Table 1.5: Native IP Management Options
Method Parameter or Command Name
Web Manager Native IP
spshell menu in the MergePoint 5224/5240 SP manager
console • Enable native IP
• Disable native IP
ssh command • nativeipon
• nativeipoff