replication ports 6 VMkernel vSphere

Thanks to Jeff Hunter for his recent updates and documentation on vSphere for replication 6.0.  Read the docs online, I have a few questions on the vSphere newly supported, dedicated replication VMkernel profits.

Here (vSphere replication 6.0 Documentation Center) and here (vSphere replication 6.0 Documentation Center) are notes on configuring the VMkernel ports dedicated to the RV on a source host and RV traffic on a target host (one for the VR traffic and another for VR NFC traffic, respectively).

Considering that it is probably a common practice to use VR as the replication engine with SRM with the intention to fail on the original production site, what is the value in the configuration of two ports VMkernel for VR?

On the protected Site, you configure a VR VMkernel port to send traffic.  He sends the replicated data from VM for device of recovery of the RV Site, who turns and sends that data replicated for recovery Site ESXi hosts VR NFC VMkernel ports.

To not return, then the recovery Site can (should?) have an additional port of VR VMkernel, which sends the data replicated VM for device of original VR protected site, which in turn sends the data replicated to the ports of VR NFS VMkernel from the original host protected Site ESXi.

This looks like it may or must be a distinction between the traffic between the sites and traffic of VR NFC within a site since there are two types of traffic for VMkernel (VR and VR NFC) VR.

What is this distinction that guarantees a dedicated RV NFC VMkernel port? Why not just use VR VMkernel port? Thank you!

Edit: I consider these types of traffic to be at the same level of importance and safety.  I have no problem to put two VMkernel ports in the same VLAN.  If I did this, it would put two VMkernel ports per host, in the same network segment.  I wonder why I don't want to do that rather than just use a single VMkernel port or multiple VLANs.

Post edited by: Mike Brown

I think it boils down essentially to the options. you don't have to do that, but based on the reviews, it has been estimated that US aircraft enough requests from customers to provide a mechanism which not only allows you to control the path allows the replication traffic (incoming and outgoing) (the source host and VR target devices), and routes it takes on the network but also control the card used for the VR NFC traffic on the target sites. As you RV relies on the NFC to push the data down to the storage of data target on the target sites and some desired customers be able to separate this circulation as well.

So in the case of the NFC, you can if you want things together (optional) upwards so that the traffic is storage hosts (and I mean here the hosts VR has determined have access to data target stores) can be sent on a physical LAN separated if you wanted that... and a lot of people have asked that flexibility. Allows customers to isolate the common VR NFC (and traffic pass VR) of management traffic not VR "regular".

Once VRM note that a host has a vmknic marked as RV NFC, only this address is reported on the VR server, which means when it comes to this host in the future that we will only use this address for traffic from VR NFC.

just my 2cents on why we did it.

Tags: VMware

Similar Questions

  • How to use the VMKernel vSphere replication traffic

    I'm trying to set up my host with my camera of replication with a stand-alone VMKernal with activated on its own virtual replication traffic vSphere VLAN.

    After that I have it set to 2 guests (each with local data warehouses) and tried to replicate a virtual machine from one host to the host with the VR device, traffic goes out on the management vlan / network card on the host of the virtual machine is received on the host with the device (where I'm storing data) on the VM nic inbound / vlan.

    I want 100% of my replication traffic off the coast of the management and the network of the VM, just as I did with vmotion.

    Hello

    On the establishment of the vmkernel to tag in ESXi 5.0.x and 5.1.x replication traffic is an experimental feature and still not officially supported.

    You have to somehow router ports of replication traffic. Some people use solutions WAN optimizer (Riverbed or similar).

    The VR device must be have access to vCenter Server and the hosts that can be used to write to data warehouses target. Link to article with the correct port numbers should be present in the Administrator's guide.

    Kind regards

    Martin

  • vSphere replication ports

    Hi guys

    We will be deploying vsphere replication between 2 sites that are geographically far apart.

    My question is to confirm if only this 2 ports must be open for replicatio to work?

    Port of 44046 31031

    any other port?

    I found this for Site Recovery manager

    http://pubs.VMware.com/SRM-51/index.jsp?topic=%2Fcom.VMware.SRM.install_config.doc%2FGUID-019985CE-1024-47B0-80AF-B96D1837916A.html

    Ports.jpg

    Thank you very much

    Hello

    This is the same topic as part of vSphere documentation Replication - http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.replication_admin.doc/GUID-88B96DAB-8389-40A5-849B-D94ED5A3C4AD.html - in case you are using vSphere replication without SRM.

    The ports listed by you are for replication traffic and the source host must have access to these ports on the secondary site server VR devices to send deltas of the replica.

    VRMS uses the reverse proxy Server vCenter and management traffic to the other VRM through port 80 between the tunnels sites.

    In order to have 31031, 44046 ports and port 80 should be sufficient.

    I have not checked the c# Client UI SRM - I see that direct access to the port remote VRM 8043 was explicitly mentioned. It might be useful to check if it is really necessary in 5.1.

    The plugin of vSphere in vSphere client Web replication does not need to directly access the 8043 remote site port, it uses the vCenter Server proxy port 80.

    Kind regards

    Martin

  • The ACS replication ports

    Hello all, I have two ACS 3.3 and I try to replicate but it does not work. The topology is something like this:

    ACS1<->PIX525<->RouterTelmex - Internet - RouterTelmex<->ASA5540<->ACS2

    I test a lot of things, and I guess that the problem is in ASA5540. So the question is: is anyone know which ports need to be opened in ASA5540 to allow replication? I know there must be opening of port 2000, but I think there must be some ports more.

    Thank you very much.

    Gabriel

    Hello Gabriel,

    I know, you only need port 2000 to open for replication of the ACS.

    BTW, did you skinny inspection enabled on the ASA. The ACS replication is running on port 2000 who also happens be the same port as the Skinny Protocol. Make sure that he lean on the two firewall inspection is disabled and see if you can get the replication.

    no correction protocol 2000 skinny

    I hope it helps.

    Kind regards

    Arul

    * Please note all useful messages *.

  • Isolate the port on a vSphere standard switch traffic

    Hello

    I deploy an environment where I have a pool of 100 virtual machines that live on a switch standard vSphere isolated. The virtual machines to communicate with the rest of the world through a virtual double-NIC machine. This configuration does not work as expected, but I would go a little further and to isolate the connectivity network, such as each virtual machine can communicate with the system of double-NIC and not each other. The switch standard vSphere, the pool of 100 virtual machines are all located on the same VLAN and group ports. I spent some research time through documentation, but I did find a clean way to implement what I want. The best I can get to each of the virtual machines 100 puts their own VIRTUAL LAN, but it is ugly and will be difficult to maintain. Is there something easier that I missed?

    Thank you

    Steve

    PVLAN, but you will need the distributed virtual switch.

  • replication target versions support vSphere

    Hello

    I could not find if there is limitation between the versions of the unit of replication when I defined the target sites.

    I am creating the target between 5.8.1.10254 2915556 build and 6.0.0.1 build 2718739, it gives a generic error.

    Y at - it limitation?

    Jonathan

    Hello

    With all the RV releases so far, for vCenter for vCenter replications, VRMS version must match the source and target site (only this configuration is officially tested and supported), for example:

    1.0.x <->1.0.x.

    5.1.x <->5.1.x.

    5.5.x <->5.5.x.

    5.6.x <->5.6.x.

    5.8.x <->5.8.x.

    6.0.x <->6.0.x.

    6.1.x <->6.1.x.

    For vCenter to vCloud Air DRaaS replication, there is no such restriction.

    For the two vCenter vCenter and vCenter to vCloud Air DRaaS, based on source ESXi version target VR version features and different replication server are supported.

    Kind regards

    Martin

  • vSphere replication traffic

    vSphere replication traffic is sent which vmkernel port?

    vSphere replication traffic is sent to the direction of vmkernel NIC for more information, see:

    http://blogs.VMware.com/vSphere/2011/10/How-does-vSphere-replication-work.html

  • SRM vSphere possible replication or SAN?

    Hello


    Just curious to know if you can configure the replication SAN with the SRA to who is matched (1 site, Site 1DR) and then also configure Replicator Vmware for SAN systems who don't not have built in replication.


    Is it possible to install?  Let me know?

    VMware and vSphere replication port replicator?

    Use vSphere replication, you must deploy the unit of replication vSphere on each site, and you can use the same server of MRS. along the coast with SRA.

    Combined based on the Bay and vSphere replication of the limits of Protection with SRM

    With MRS, you can run groups of protection based on the Bay alongside vSphere protection groups on the same SRM Server replication. However, the total number of protection groups cannot exceed 250. For example, you cannot create 150 groups of protection based on the Bay and then create 250 vSphere replication protection associations, because this creates 400 total protection groups. If you have 150 groups of protection based on the Bay, you can create an additional 100 vSphere protection of the replication groups, for a total of 250 groups of protection.

    VMware KB: Operating for SRM and vSphere replication limits

  • Access NAS storage of ESXi Server using VMKernel Port?

    Hello

    I would like to know the best procedure to connect to the NAS storage of ESXi host 5. I am able to connect to the NAS storage according to the screenshots listed in the link below.

    http://www.tintri.com/blog/2011/11/connecting-vSphere-to-NFS-the-easy-way/

    But, I saw different configurations in the past where port dedicated VMkernel is assigned to NAS and all storage goes into network 10 G. I try to do the same and created a VMkernel for NAS port. But I don't think that traffic is going over there as it is not used at all.

    I gave the IP address of the ESXi server on the NAS box to get access. I couldn't give address IP VMkernel sideways NAS. How can I make use of this IP VMKernel dedicated NFS storage?

    I want to implement the best way to pass NAS 10 G network traffic. In addition, How can I test if storage traffic crosses VMkernel port?

    Suggestions needed.

    Virtualinfra is right that you must use a different subnet for NFS traffic. You masked the IP range, so I don't see what you use, but make sure that the vmkernel and storage using a single subnet, not the management subnet. If you get an error, your use of a subnet that goes out the default gateway of the management port, or that you are using the same subnet.

    I wrote a few articles on the use of NFS with vSphere: http://wahlnetwork.com/2012/04/19/nfs-on-vsphere-a-few-misconceptions/

    Also, make sure that the vmnic can route traffic on that subnet, as in the case of the use of VLANs.

  • Is ACS 4.2 - possible to change the port of replication?

    Hello

    try to find out if she some tweek to change the port of TCP/2000 ACS replication to something else.

    I know that it is possible to make a different map policy or not to inspect the skinny Protocol in order to avoid the conflict, but not the solution I'm looking for. I was wondering if anyone knows of a different way to change the port of 4.2 ACS replication.

    Hello

    What is the version of the CSA, you run?

    If you then run ACS 4.2.1.15

    Problem : ========= ACS replication port re-configuration. Resolution : ============ Please follow the following steps: 1.       Interface configuration > Advanced Options > Check the checkbox ACS Communication Port Configuration. 2.       System Configuration > service control > Configure the Port to be used for the ACS Internal Communication (choose any port between 2010 to 2025)
    

    Regards,
    
Anisha
    

    P.S.: please mark this thread as resolved if you think your query is answered.

  • Vsphere-Windows failover cluster replication

    Hello

    Need help to replicate Microsoft cluster at 2 knots.  I know that vSphere replication is compatible with virtual RDM so will change to virtual RDM physica, but the controller SCSI ROW of nodes have buses sharing (Physics) is enabled. How to reproduce these groupings with SCSI bus sharing enabled, since vsphere replication does not support sharing of bus

    Thanks, waiting for some thoughts/work around

    vSphere replication doesn't support MSCS, see: KB VMware: vSphere Replication FAQ

    Is VSphere replication supported MSCS clusters?

    vSphere replication does not work with virtual disks open mode "multi-writer". Virtual machines MSCS cluster are configured with virtual disks open mode "multi-writer", so vSphere replication will not work with MSCS configuration.

  • VWC plugin using sdk 5.1 is broken if running on the web client 6.0 with port 9443 - out could not connect to the Web Client vSphere. Contact your administrator to resolve this problem.

    We did a vwc with sdk 5.1 plugin, now, we want to make it work on the web client 6.0. before the race, we have changed the MANIFESTO. MF and services-config. XML responses such as the following:

    2 important reminders for your plugin 5.5 is compatible with the Web Client 6.0

    After that, we deployed our plugin on web client 6.0

    If access us using the URL with port: https:// < ipaddress >: client/vsphere-9443 /? csp, our plugin arises, our plugin function is also ok.

    If access us using the URL without port: https://< ipaddress > / vsphere client /? csp, our plugin is present, the function is broken (error occurred when flex user interface by calling the java service: "Could not connect to vSphere Web Client.) Contact your administrator to resolve this problem. »).

    Thank you very much

    Please change the CHANNEL_URL in your proxy classes to use 'amf' instead of 'amfsecure '.

    private static const CHANNEL_URI:String = "/" + YOUR_MODULE.contextPath + "/messagebroker/amf"

    This should solve your problem.

  • VSphere 6.0 backward compatible with vCenter 5.5 replication is?

    At one point, the vSphere replication 6.0 compatibility matrix said that it is compatible with vCenter 5.5.  I think it was around mid-March.  Now, he seems to have changed and says vSphere 6.0 replication is only compatible with vCenter 6.0.  Is this true?  Are there plans to make vSphere replication 6.0 backward compatible with vCenter 5.5?

    Bill,

    A decision was made not to support backward compatibility between replication 6.0 vSphere and vCenter Server 5.5 going forward.  This is the result extended and careful considerations affecting the provision of quality and consistent user experience for our customers using vSphere 6.0 replication.

    Thus, vSphere 6.0 replication is officially supported with vCenter Server 6.0 only (SSO 6.0, 6.0 PC, Web Client 6.0).  This resulted therefore in the interoperability of public VMware product matrix.

  • VMkernel Port Configuration using Powershell.

    Hello

    I was playing in my test environment with the creation of the virtual switches and powerCLI port groups.

    I created a port group VMkernel using the following command line

    Get-vmhost $vmhost.

    new-vmhostnetworkadapter - portgroup VMkernel - virtualswitch (get-vmhost $vmhost------)

    Get - virtualswitch - name "vSwitch1") - 192.168.1.16 - netmask 255.255.255.0 - VmotionEnabled ip: $true

    My question is how can I set the powerCLI VMkernel default gateway?

    I ran the command above on two hosts configured identically using a startup script. On hosts, I get an error message (sorry forgot it exactly) who said something along the lines of:

    Hot migration not enabled for this host, use the following command to active:

    game-VMHostAdvancedConfiguration-name "Migrate.Enabled" - value 1

    When I watched the Group of ports, vMotion was checked so don't know why this line was necessary. Is this something that I have to run on all hosts?

    Kind regards

    Roger.

    To set the VMKernel default gateway, you use the UpdateIpRouteConfig method.

    Something like that

    $netMgr = Get-View (Get-VMHost  | Get-View).ConfigManager.NetworkSystem

$iproute = New-Object VMware.Vim.HostIpRouteConfig
$iproute.defaultGateway = ""

$netMgr.UpdateIpRouteConfig($iproute)

    I don't know why you're going to the message about the missing advanced configuration.

  • VMkernel traffic

    I just read, marking VMkernel traffic Types using ESXCLI 5.1 | VMware vSphere Blog - VMware Blogs and it says that the vmkernel supports the types of traffic are Fault Tolerant replication, management, vMotion and vSphere.  However, when I do my lab and traffic options when I look to add a port of vmkernal vSphere vMotion, iSCSI, NFS and management host.  Which is OK if requested for the consideration of PVC?

    The books you mentioned are based on vSphere 5.0 and vSphere replication has been introduced with vSphere 5.1. What traffic VMkernel helps is:

    • Management
    • vMotion
    • Fault tolerance
    • vSphere replication
    • Network storage (iSCSI, for example)

    Note that for storage networks, there is no explicit option, you need to check/enable, i.e. to leave all the options not controlled.

    André

Maybe you are looking for