{"id":38541,"date":"2019-09-10T09:00:27","date_gmt":"2019-09-10T07:00:27","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=38541"},"modified":"2023-04-12T10:53:45","modified_gmt":"2023-04-12T08:53:45","slug":"vsphere-replication-8-x-traffic-isolation-pt-3","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-traffic-isolation-pt-3\/","title":{"rendered":"vSphere Replication 8.x: traffic isolation - pt.3"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-39822 size-full\" title=\"vmware-vsphere-replication-traffic-isolation-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-01.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>In vSphere Replication a network isolation design may be required to <strong>split the traffic<\/strong> from the management network (used by default to transfer data) to avoid network performance issues.<\/p>\n<p>If the traffic is not isolated, during the replication process the appliance consume the management network <strong>limiting the available bandwidth<\/strong> to other applications affecting the overall performance.<!--more-->To optimize the traffic, vSphere Replication can be configured to split the traffic from the <strong>source host to the appliance<\/strong> and from the <strong>appliance to the target host<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Blog series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-deployment-pt-1\/\">vSphere Replication 8.x deployment - pt.1<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-failover-pt-2\/\">vSphere Replication 8.x failover - pt.2<\/a><br \/>\nvSphere Replication 8.x traffic isolation - pt.3<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-seeding-pt-4\/\">vSphere Replication 8.x seeding - pt.4<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Traffic isolation topologies<\/h2>\n<p>To replicate VMs from the production to DR Site, there are different topologies that can be adopted:<\/p>\n<ul>\n<li>Single vCenter Server<\/li>\n<li>Multiple vCenter Servers<\/li>\n<\/ul>\n<p>In a situation with budget constraints, the single <a href=\"https:\/\/nolabnoparty.com\/en\/vcenter-server-6-7-converge-tool-embed-external-psc-into-vcsa\/\">vCenter Server<\/a> approach could be a good compromise.<\/p>\n<p>In addition to the typical scenario with a DR Site, vSphere Replication can be also\u00a0used to <strong>migrate VMs<\/strong> from a data center to another one.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39824 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-02-600x245.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-02\" width=\"600\" height=\"245\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Setup source hosts<\/h2>\n<p>First step of the configuration is the creation of a <strong>dedicated port group<\/strong> in the source hosts network.\u00a0 In the example a <a href=\"https:\/\/www.vmware.com\/at\/products\/vsphere\/distributed-switch.html\" target=\"_blank\" rel=\"noopener noreferrer\">distributed switch<\/a> is used in the network configuration. If a vStandard Switch (vSS) is used instead, the <strong>concept is the same<\/strong> and also in this case you should create a new port group.<\/p>\n<p>&nbsp;<\/p>\n<h4>Create a new Port Group<\/h4>\n<p>Right click the Distributed Switch to use and select <strong>Add new Port Group<\/strong>. When the <strong>New Port Group<\/strong> configuraton has been completed, you will find the new Port Group in the Distributed Switch.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39826 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-03-600x313.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-03\" width=\"600\" height=\"313\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Create a new VMKernel<\/h4>\n<p>In order to separate the Replication traffic, a new VMKernel adapter should be created in the source hosts. Select the first source host of the cluster and go to <strong>Configure<\/strong> tab. Select <strong>VMkernel adapters<\/strong> item under <strong>Networking<\/strong> and click <strong>Add Networking<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39828 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-04-600x278.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-04\" width=\"600\" height=\"278\" \/><\/p>\n<p>Select <strong>VMkernel Network Adapter<\/strong> option and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39830 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-05-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-05\" width=\"600\" height=\"416\" \/><\/p>\n<p>Since a Distributed Switch is used, choose <strong>Select an existing network<\/strong> option and select the previously created Port Group throught the <strong>Browse<\/strong> button. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39832 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-06-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-06\" width=\"600\" height=\"416\" \/><\/p>\n<p>Select <strong>vSphere Replication<\/strong> as service to enable in the host then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39834 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-07-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-07\" width=\"600\" height=\"416\" \/><\/p>\n<p>In the <strong>IPv4 Settings<\/strong>, select <strong>Use static IPv4 settings<\/strong> option to assign an IP address to the VMkernel. Specify the <strong>Port address<\/strong> and the <strong>Subnet mask<\/strong> (192.168.100.10\/24 in the example) then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39836 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-08-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-08\" width=\"600\" height=\"416\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to create the new VMkernel adapter.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39838 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-09-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-09\" width=\"600\" height=\"416\" \/><\/p>\n<p>The new VMkernel adapter has been created successfully.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39840 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-10-600x316.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-10\" width=\"600\" height=\"316\" \/><\/p>\n<p>Now create a new VMkernel in the <strong>second source host<\/strong> member of the cluster by following the same procedure. In the example the VMkernel is configured with address 192.168.100.20\/24.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39842 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-11-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-11\" width=\"600\" height=\"416\" \/><\/p>\n<p>Again, also for the <strong>third source host<\/strong> member of cluster, create a new VMkernel adapter. The VMkernel is configured with address 192.168.100.30\/24.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39844 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-12-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-12\" width=\"600\" height=\"416\" \/><\/p>\n<p>All host members of the cluster have been configured with a new VMkernel adapter configured with the required parameters.<\/p>\n<p>&nbsp;<\/p>\n<h2>Setup target host<\/h2>\n<p>Also in the target host a new VMkernel adapter must be created to separate the traffic from the management network. Access the <strong>Networking<\/strong> area and select the <strong>VMkernel<\/strong> tab. Click <strong>Add networking<\/strong> to create a new VMkernel. In the configuration wizard select <strong>VMkernel Network Adapter<\/strong> option and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39846 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-13-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-13\" width=\"600\" height=\"416\" \/><\/p>\n<p>Because in the example the target host uses Standard Switches, choose <strong>Select an existing standard switch<\/strong> and select the switch to use through the <strong>Browse<\/strong> button. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39848 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-14-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-14\" width=\"600\" height=\"416\" \/><\/p>\n<p>Specify the <strong>Network label<\/strong> and the <strong>VLAN ID<\/strong> used. Enable the <strong>vSphere Replication NFC<\/strong> service and click <strong>Next<\/strong>. The Network File Copy (NFC) is used to <strong>receive the replication data<\/strong> from the source host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39850 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-15-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-15\" width=\"600\" height=\"416\" \/><\/p>\n<p>Specify the <strong>IPv4 address<\/strong> and the <strong>Subnet mask<\/strong> for the VMkernel and click <strong>Next<\/strong>. The VMkernel is configured with address 192.168.101.50\/24.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39852 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-16-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-16\" width=\"600\" height=\"416\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to create the new VMkernel adapter.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39854 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-17-600x416.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-17\" width=\"600\" height=\"416\" \/><\/p>\n<p>The VMkernel has been created successfully in the target host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39856 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-18-600x362.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-18\" width=\"600\" height=\"362\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Configure vSphere Replication NICs<\/h2>\n<p>Once the VMKernel adapters have been created, the appliance's network must be configured accordingly. In order to split the traffic from the management network, we need to add <strong>two additional NICs<\/strong> to the VM. Right click the vSphere Replication appliance and select <strong>Edit settings<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39858 size-full\" title=\"vmware-vsphere-replication-traffic-isolation-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-19.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-19\" width=\"508\" height=\"539\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39860 size-full\" title=\"vmware-vsphere-replication-traffic-isolation-20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-20.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-20\" width=\"516\" height=\"250\" \/><\/p>\n<p>Click <strong>Add New Device<\/strong> and select <strong>Network Adapter<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39866 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-21-600x501.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-21\" width=\"600\" height=\"501\" \/><\/p>\n<p>Assign the <strong>New Network<\/strong> adapter to the network created to transfer data <strong>from source host to the appliance<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39868 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-22-600x501.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-22\" width=\"600\" height=\"501\" \/><\/p>\n<p>Enable the <strong>Connect<\/strong> option to connect the new NIC to the appliance.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39870 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-23-600x501.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-23\" width=\"600\" height=\"501\" \/><\/p>\n<p>Add a second Network Adapter that must be connected to the network used to transfer data <strong>from the appliance to the target host<\/strong>. Ensure the NIC has the option <strong>Connected<\/strong> enabled and click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39872 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-24-600x501.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-24\" width=\"600\" height=\"501\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Configure vSphere Replication network<\/h2>\n<p>In order to<strong> re-direct the traffic<\/strong> to source and target hosts, you need to <strong>assign the correct networks<\/strong> to the appliance and a<strong>\u00a0static route<\/strong> may be required if the source\/target network is not properly routed.<\/p>\n<p>Right click the appliance and select <strong>Power &gt; Power On<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39874 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-25-600x388.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-25\" width=\"600\" height=\"388\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39876 size-full\" title=\"vmware-vsphere-replication-traffic-isolation-26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-26.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-26\" width=\"516\" height=\"250\" \/><\/p>\n<p>From the preferred browser, access the appliance GUI by entering the address <span style=\"color: #0000ff;\">https:\/\/IP_appliance:5480<\/span>. Enter <strong>Username<\/strong> and <strong>Password<\/strong> then click <strong>Login<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39878 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-27\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-27-600x183.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-27\" width=\"600\" height=\"183\" \/><\/p>\n<p>Go to <strong>Network &gt; Adapters<\/strong> area and specify the network parameters for the two added NICs:<\/p>\n<ul>\n<li><strong>eth1<\/strong>: incoming traffic (from source host to appliance)<\/li>\n<li><strong>eth2<\/strong>: outgoing traffic (from appliance to target host)<\/li>\n<\/ul>\n<p>Click <strong>Save Settings<\/strong> when done.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39880 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-28\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-28-600x461.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-28\" width=\"600\" height=\"461\" \/><\/p>\n<p>Go to <strong>VR &gt; Configuration<\/strong> area and enter the IP address assigned to the <strong>eth1<\/strong> network adapter in the <strong>IP address for Incoming Storage Traffic<\/strong> field. This tells the system incoming traffic (from source host) <strong>will arrive on eth1<\/strong>. Click <strong>Apply Network Settings<\/strong> to save the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39882 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-29\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-29-600x406.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-29\" width=\"600\" height=\"406\" \/><\/p>\n<p>The configuration has been applied successfully.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39884 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-30\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-traffic-isolation-30-600x379.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-30\" width=\"600\" height=\"379\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Add a static route<\/h4>\n<p>If the appliance <strong>can't reach source o destination network<\/strong> (it depends where the appliance is placed), you need to add a <strong>static route<\/strong>. To add a static route to the vSphere Replication, you need to <strong>SSH the appliance<\/strong>. By default SSH service is disabled and you need to <strong>enable SSH on the vRA<\/strong>.<\/p>\n<p>Access the vSphere Replication's console via vSphere Client and login as <em>root<\/em>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40142 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-31\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-31-600x50.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-31\" width=\"600\" height=\"50\" \/><\/p>\n<p>From the console, run the following command to enable the SSH service in the appliance:<\/p>\n<p><span style=\"color: #0000ff;\"># \/usr\/bin\/enable-sshd.sh<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40144 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-32\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-32-600x106.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-32\" width=\"600\" height=\"106\" \/><\/p>\n<p>Add the <strong>route details<\/strong> in the file below to make the change persistent across reboots.<\/p>\n<p><span style=\"color: #0000ff;\"># vi \/etc\/systemd\/network\/10-eth2.network<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40146 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-33\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-33-600x87.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-33\" width=\"600\" height=\"87\" \/><\/p>\n<p><strong>Add a new section<\/strong> at the end of the file and add the following\u00a0<strong>route details<\/strong>:<\/p>\n<pre class=\"lang:default decode:true\">[Route]\r\nGateway=192.168.210.1\r\nDestination=192.168.210.0\/24<\/pre>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40148 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-34\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-34-600x214.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-34\" width=\"600\" height=\"214\" \/><\/p>\n<p>Restart network services to enable the changes.<br \/>\n<span style=\"color: #0000ff;\"># systemctl restart systemd-networkd<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40150 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-35\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-35-600x121.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-35\" width=\"600\" height=\"121\" \/><\/p>\n<p>Check if the configuration has been applied in the <strong>routing table<\/strong> running the command:<br \/>\n<span style=\"color: #0000ff;\"># netstat -r<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40152 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-36\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-36-600x235.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-36\" width=\"600\" height=\"235\" \/><\/p>\n<p>The static route has been added successfully.<\/p>\n<p>&nbsp;<\/p>\n<h2>Check appliance's network<\/h2>\n<p>To verify the appliance is reachable from the source host and the traget host, the <strong>vmkping command<\/strong> is what we need.<\/p>\n<p>SSH the source host and run this command to check if the source host is able to reach the vSphere Replication appliance:<\/p>\n<blockquote><p>vmkping -I &lt;VMkernel_assigned_to_replication&gt; &lt;IP_Address_vSphere_Replication_appliance&gt;<\/p><\/blockquote>\n<p><span style=\"color: #0000ff;\"># vmkping -I vmk5 192.168.100.77<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40154 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-37\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-37-600x183.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-37\" width=\"600\" height=\"183\" \/><\/p>\n<p>Now run the following command to verify if the <strong>target host can reach the appliance<\/strong>:<\/p>\n<p><span style=\"color: #0000ff;\"># vmkping -I vmk2 192.168.101.77<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40156 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-38\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-38-600x176.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-38\" width=\"600\" height=\"176\" \/><\/p>\n<p>If a static route has been added, use the <strong>ping command<\/strong> from the appliance to test the <strong>connectivity to target host<\/strong>:<\/p>\n<p><span style=\"color: #0000ff;\"># ping 192.168.101.50<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40158 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-39\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-39-600x167.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-39\" width=\"600\" height=\"167\" \/><\/p>\n<p>Source, target hosts and appliance networks are configured properly.<\/p>\n<p>&nbsp;<\/p>\n<h4>Configure NIOC on the Distributed Switch<\/h4>\n<p>To <strong>limit\/provide the bandwidth<\/strong> assigned for replication, you can use the NIOC feature available for Distributed Switches and configure the appropriate <strong>Shares Value<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40160 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-40\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-40-600x280.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-40\" width=\"600\" height=\"280\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Run the replication job with traffic isolated<\/h2>\n<p>Once the traffic isolation has been configured, run a replication job to check if everything works as expected. A successfully result confirms the replication is working properly and data are transferred over a <strong>dedicated network<\/strong>\u00a0without affecting the production network.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-40162 size-large\" title=\"vmware-vsphere-replication-traffic-isolation-41\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/09\/vmware-vsphere-replication-traffic-isolation-41-600x188.jpg\" alt=\"vmware-vsphere-replication-traffic-isolation-41\" width=\"600\" height=\"188\" \/><\/p>\n<p>Traffic isolation should be the correct approach to use if the replication process affects the production network performance. <a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-seeding-pt-4\/\">Part 4<\/a> will cover the seeding procedure to reduce transferred data over the network and time required to complete the process.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In vSphere Replication a network isolation design may be required to split the traffic from the management network (used by default to transfer data) to avoid network performance issues. If the traffic is not isolated, during the replication process the appliance consume the management network limiting the available bandwidth to other applications affecting the overall performance.<\/p>\n","protected":false},"author":3,"featured_media":39822,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2138,2642],"tags":[2008,2010,582,2009],"class_list":["post-38541","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-vsphere-replication-en","tag-isolation","tag-nfc","tag-replication-en","tag-traffic","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38541","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=38541"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38541\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/39822"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=38541"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=38541"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=38541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}