How to create vmkernel adapter in custom TCP/IP stack to avoid adding static routes in vSphere Replication environment
search cancel

How to create vmkernel adapter in custom TCP/IP stack to avoid adding static routes in vSphere Replication environment

book

Article ID: 408725

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

  • In vSphere Replication environment, static routes are added on ESXi hosts to allow for bidirectional traffic between the Management and vSphere Replication networks.

  • This enables same default gateway to be used for Management as well as vSphere Replication (and vSphere Replication NFC) vmkernel adapters.

  • In case if there is a need to avoid using static routes, a custom TCP/IP stack can be used for vmkernel adapters of vSphere Replication and vSphere Replication NFC traffic. 

  • This is to be configured on ESXi hosts at Source and Target sites both.

Environment

vSphere Replication 8.x

vSphere Replication 9.x

Resolution

Steps to create vmkernel adapter for vSphere Replication and vSphere Replication NFC on custom TCP/IP stack:

  1. Add custom TCP/IP stack running following command in ESXi shell:
    # esxcli network ip netstack add -N="stack_name"

  2. Create a new vmkernel adapter through vSphere client (delete old one if already created for vSphere Replication and vSphere Replication NFC traffic) using the newly created custom TCP/IP stack.

  3. Tag vSphere Replication and vSphere Replication NFC traffic on newly created vmkernel adapter running following command in ESXi shell:
    # esxcli network ip interface tag add -i vmkX -t vSphereReplication
    # esxcli network ip interface tag add -i vmkX -t vSphereReplicationNFC
Powered by Wolken Software