• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

multi-honed Plesk, two eth cards

H

hackhawk

Guest
Hello,

I was unable to find any information in the forums on this topic, so I thought I'd post what I'm doing.

Basically I'm migrating a Plesk server from one physical sub-net to another on a completely different switch and sub-net. The switches are physically close enough that I can use both Eth cards on the Plesk server to allow access to both subnets at the same time. The reason for this is to limit downtime during the migration as some visitors may have the old (DNS) address cached.

There are two obstacles to overcome.

1) Setting up Linux to be Multihoned
2) Setting up Plesk to use both IP's

I'm not entirely finished trying #2 yet, but it seems to be working.

--- Here's what I've done -----

1) Setup Linux to be Mulit-honed

Code:
a) edit /etc/sysconfig/network-scripts/
       ifcfg-eth0 & ifcfg-eth1
       Assuming you're migrating to the
       subnet on eth1, eth1 will be your
       primary outbound interface.
Code:
b) add the following two lines to
      /etc/iproute2/rt_tables

      200     T1
      201     T2
Code:
c) setup the following file to run at startup.
       ensure UPPERCASE variables are
       replaced by the correct information.
       /etc/rc.d/init.d/iproute

       #!/bin/sh
       ip route add NEW_IP_NET dev eth1 src NEW_IP_ADDR table T1
       ip route add default via NEW_IP_GATEWAY table T1
       ip route add OLD_IP_NET dev eth0 src OLD_IP_ADDR table T2
       ip route add default via OLD_IP_GATEWAY table T2
       ip route add NEW_IP_NET dev eth1 src NEW_IP_ADDR
       ip route add OLD_IP_NET dev eth0 src OLD_IP_ADDR
       ip route del default via OLD_IP_GATEWAY
       ip route add default via NEW_IP_GATEWAY
       ip rule add from NEW_IP_ADDR table T1
       ip rule add from OLD_IP_ADDR table T2
Code:
d) Run (service network restart)
Code:
e) Run (/etc/rc.d/init.d/iproute)

2) Setting up Plesk to use both IP's

I couldn't locate anywhere within plesk to change the IP address of the Virtual/Shared Hosts to use the new IP/Interface. Someone please correct me if there is a way to do this.

Code:
a) You need to edit the files located at...

       /var/www/vhosts/SITENAME/conf/httpd.include

Duplicate all of the references in the 
VirtualHost area and reference the new IP 
Address for the duplicated section.

Code:
b) Run (service restart httpd)

Hope this helps if anyone is looking to do the same thing. And if I've done something that's incompatible with Plesk, please speak up. ;)
 
Back
Top