Avocent 5240 Manuel D’Utilisation
Chapter 3: Web Manager for All Users 49
Go to DirectCommand Interface link
After all DirectCommand connections are terminated, the following occur:
•
The DirectCommand Connected link changes to Direct Command: Idle.
•
The Go to DirectCommand Interface link persists in the Action pull-down menu, and the SSH
tunnel between the user and the MergePoint 5224/5240 SP manager remains active. The user
can select the Go to DirectCommand Interface link to from the Action pull-down menu to
create a new DirectCommand connection without having to relaunch the Java applet.
tunnel between the user and the MergePoint 5224/5240 SP manager remains active. The user
can select the Go to DirectCommand Interface link to from the Action pull-down menu to
create a new DirectCommand connection without having to relaunch the Java applet.
To use DirectCommand to gain native web access to a target device
(Web Manager):
(Web Manager):
1.
Log into the Web Manager as an authorized user.
2.
The first time during a Web Manager login session, click the DirectCommand Enable link in
the Action pull-down menu for the target device on which you want DirectCommand access. A
Java applet launches a window and connects to the device’s native web interface.
the Action pull-down menu for the target device on which you want DirectCommand access. A
Java applet launches a window and connects to the device’s native web interface.
3.
When you are done, always click the Disable link in the target device’s pull-down menu as a
security precaution.
security precaution.
4.
To disconnect from any DirectCommand connections, click Direct Command: Connected. The
dialog displays listing the currently active DirectCommand connections.
dialog displays listing the currently active DirectCommand connections.
5.
Select the desired connection from the list, and then click Disconnect.
6.
To reconnect later in the same Web Manager login session, click the Go to DirectCommand
Interface from the target device’s Action pull-down menu.
Interface from the target device’s Action pull-down menu.
Creating VPN connections for Native IP access
The rules for bringing up the Web Manager for Native IP access through the Target devices screen
differ between IPSec and PPTP VPN connections as indicated in the following list:
differ between IPSec and PPTP VPN connections as indicated in the following list:
•
If the VPN connection is being made using IPSec, the authorized user may use the MergePoint
5224/5240 appliance’s IP address to bring up the Web Manager first and go to the Target
device screen before making the VPN connection. After subsequently making the VPN
connection, the user can reload the form to see the Enable Native IP link active.
5224/5240 appliance’s IP address to bring up the Web Manager first and go to the Target
device screen before making the VPN connection. After subsequently making the VPN
connection, the user can reload the form to see the Enable Native IP link active.
•
If the VPN connection is made using PPTP, the VPN connection must be made before the Web
Manager can be launched, because the Web Manager must be launched using the PPTP
IP address.
Manager can be launched, because the Web Manager must be launched using the PPTP
IP address.
The user obtains the IP address assigned to the PPTP interface by entering the ifconfig or
ipconfig command on the workstation’s command line (which command to use depends on the
operating system). In the command output, the IP address assigned to the connection appears
in the lines following the words PPP adapter, as shown in the following.
ipconfig command on the workstation’s command line (which command to use depends on the
operating system). In the command output, the IP address assigned to the connection appears
in the lines following the words PPP adapter, as shown in the following.
C:\> ipconfig
...