
196 MergePoint 5224/5240 Service Processor Manager Installer and Administrator Guide
If the SP manager’s administrator sends the relevant portions of the ipsec.conf file from the
appliance’s IPSec configuration, use it to replace the same section in the workstation’s
ipsec.conf file.
• Bring up the IPSec VPN tunnel. For accessing sp1, sp2 or sp3, the user can use the connVirt
connection profile. For accessing sp4, the user uses the connSub2 connection profile.
Enabling native IP and accessing the target device’s native features is the same as described under
Enabling native IP and accessing a target device’s native features using real IP addresses for
example 2 on page 191.
PPTP VPN configuration for example 3
After the private subnets, target device and user account configuration in Virtual network and
target device configuration for example 3 on page 194 is completed, a VPN connection profile
must be defined to create a VPN tunnel to the virtual network.
The steps used for enabling a PPTP VPN connection to the virtual network are the same as in PPTP
VPN configuration for example 2 on page 189, except that, after creating the PPTP VPN tunnel, the
user must create the static route differently to access the virtual network.
This first set of bullets are a review of the steps for obtaining the PPTP address assigned to the SP
manager:
• Enter the ifconfig or ipconfig command on the command line of the user’s workstation to
discover the IP address assigned to the SP manager’s end of the PPTP VPN tunnel.
• Enter the SP manager’s PPTP-assigned address either in a browser or with ssh on the command
line to access the SP manager. In this example the address is 192.168.2.1.
The next bulleted items show how to create an appropriate route to the virtual network.
• Create a static route to inform the workstation that the target devices to be contacted are at the
other end of the point-to-point link.
In this example, to communicate with sp1, sp2 and sp3, a route would needed to the virtual
network whose IP address is 172.20.0.0 as shown below:
To communicate with sp4, because it cannot be contacted through a virtual network IP address,
the same route mentioned in PPTP VPN configuration for example 2 on page 189 would be
needed to sub2, which has the network IP address 192.168.4.1 as shown below:
• Enable native IP and access the target device’s native features.
Enabling native IP and accessing the target device’s native features is the same as described under
Enabling native IP and accessing a target device’s native features using real IP addresses for
example 2 on page 191.
route add -net 172.20.0.0 mask 255.255.0.0 via 192.168.2.1
route add -net 192.168.4.1 mask 255.255.252.0 via 192.168.2.1
Komentáře k této Příručce