Port requirements for Hyperflex native replication

[bezeddin]

Which port should be opened when configuring Hyperflex site to site replication via WAN ?

Regards

Budi

[Kirk J]

Greetings.

Please see https://www.cisco.com/c/dam/en/us/support/docs/hyperconverged-infrastructure/hyperflex-hx-data-platform/HX-Hardening_Guide_v3-0.pdf which lists the TCP ports used as it relates to use with replication.

Cisco HX Platform Hardening Guide Page 20

Port Requirements and Logical Traffic Flow for Replication
The following ports are opened for inter-cluster communications, during cluster-pairing:
9338, 9339, 3049, 9098, 4049, 4059
These are the ports that are used in HX Replication:
• datasvcmgr_peer = 9338
• datasvcmgr = 9339
• scvm (storage controller vm) = 3049
• cmap = 4049
• nrnfs = 4059
• replsvc = 9098
• nr (master for coordination) = 8889
• hypervisorsvc = 9350

Thanks,

Kirk..

[bezeddin]

Kirk,

Thanks for your valuable info

For replication through WAN should we only NAT cluster IP from both side or each controller VM IP's ?

[Kirk J]

From that same section in the hardening guide:

"Firewall entries are made on the source and destination machine during pairing to allow HX Data Platform access to the system(s) bi-directionally. This traffic needs to be allowed on WAN routers for each HXDP node IP address and cluster CIP-M address."

Thanks,

Kirk...

[bezeddin]

Kirk,

As far as I know HX replication require new vlan (not using existing SVM IP) 

Could we use existing vlan instead of creating new ?

[bezeddin]

Kirk,

As far as I know HX replication require new vlan (not using existing SVM IP) 

Could we use existing vlan instead of creating new ?

[sbhadrav@cisco.com]

The Cisco HyperFlex HX Data Platform supports replication of virtual machines or groups of virtual machines to other clusters across a WAN for disaster recovery purposes. The data platform optimizes data transfer using change-block tracking and compression to reduce network impact. Native replication and snapshots built into the HX Data Platform dramatically reduce recovery time objective (RTO) and recovery point objective (RPO) metrics and achieve an RTO of less than 15 minutes for applications and data.

In this post we will learn how to create the replication of virtual machine between two Cisco HyperFlex HX Data Platform.

Environment:
Cisco HyperFlex HX A: hx-cluster-a
Cisco HyperFlex HX B: hx-cluster-b

[bezeddin]

sbhadrav@cisco.com

Regarding HX replication 

Could we use existing vlan instead of creating new ?

[sbhadrav@cisco.com]

First login into Cisco HyperFlex Cluster A/B, go to “Replication” and configure the replication network on each HyperFlex cluster and no need to creating new vlan.