Using separate interface for replication

Rushdi Lv1Posted 2026-Aug-24 15:29

I have 1 ip on either site to use as a replication link. I have 2 nodes in primary site and 1 node in secondary site. There is no issue creating a replication link at DR site but in Primary site having 2 nodes to select one ip to replicate is a challenge I have.

By solving this question, you may help 875 user(s).

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Rushdi Lv1Posted 2026-Aug-24 17:51
  
The challenge is we need to use the same VLAN and the subnet as the management interface.
Humayun Ahmed Lv4Posted 2026-Aug-24 18:16
  
If you cannot create another VLAN/subnet, I would configure it like this:

Site        Node        Management IP        DR Role
Primary        Node 1        10.x.x.11        DR Transmission / Controller
Primary        Node 2        10.x.x.12        DR Proxy
DR        Node 3        10.x.x.21        DR Transmission

The exact IPs are only examples.

The important thing is:

Do not try to assign the same DR IP to both Primary nodes. Each node already has its own Management IP. The DR mechanism can use the controller's transmission interface/IP while the second node uses the DR proxy mechanism.
Newbie565333 Lv1Posted 2026-Aug-24 18:19
  
i agree, it's for better and for easy access and management purpose, it help my organization a lot, especially in replica and redundant site
Rushdi Lv1Posted 2026-Aug-24 18:29
  
So hypothetically lets say the IP layout is as follows. 2 nodes in primary 1 node in DR.
The NOC team has provided 1 ip from each site which shares the same subnet and vlan ID.

Primary - 10.10.50.50 with VLAN ID - 50
DR - 10.20.50.50 with VLAN ID - 50

Will this work?


        Primary Site        DR Site
GW        10.10.50.1        10.20.50.1
Node1        10.10.50.3        10.20.50.3
Node2        10.10.50.4       
Cluster        10.10.50.2       
SCP        10.10.50.6        10.20.50.6
               
VLAN ID        50        50
Subnet         /26        /26
Rushdi Lv1Posted 2026-Aug-24 18:46
  
Just an update tried configuring the IP at DR site and got this error message. The node's interface channel1 ip address is conflicting. Please modify it and try again. Error code: B1400604
AR Lv3Posted 2026-Aug-24 19:41
  
I would set it up like this if you are unable to make another VLAN or subnet:

Site,           Node,          Management IP,     DR Role,
Primary      Node 1,      10.x.x.11,                 DR Transmission/Controller,
Primary      Node 2,      10.x.x.12,                 DR Proxy,
DR,             Node 3,      10.x.x.21,                 DR Transmission

The specific IPs are merely illustrations.

What matters is:

Never attempt to give both primary nodes the same DR IP. Every node has a management IP already. While the second node employs the DR proxy method, the DR mechanism can make use of the transmission interface/IP of the controller.
Rushdi Lv1Posted 2026-Aug-24 19:45
  


Solvia confirms that same subnet/vlan as management interface could not be used for another interface on the same host.
Newbie900829 Lv1Posted 2026-Aug-24 20:38
  
Let's assume that the IP layout is as follows. One DR node and two primary nodes.
One IP address from each site that has the same subnet and vlan ID has been provided by the NOC team.

VLAN ID: 50; primary: 10.10.50.50
DR: 10.20.50.50 and VLAN ID: 50

Does this work? GW 10.10.50.1 10.20.50.1 Primary Site DR Site Node1 10.10.50.3 10.20.50.3 Node2 10.10.50.4 Cluster 10.10.50.2 SCP 10.10.50.6 10.20.50.6
Prosi Lv4Posted 2026-Aug-25 15:48
  
Hi,

Yes—there are two nodes at the Primary site with a single IP address available for use as the replication endpoint, whereas the Secondary/DR site has only one node.
Given that only one physical IP address is available at the Primary site, a Virtual IP (VIP) or a different replication architecture is required, depending on the specific Sangfor features and version. However, using a VIP alone does not necessarily resolve the inter-node replication issue, as the replication service may require each physical node to have its own accessible address.

I Can Help:

Change

Board Leaders

YerkoUm...

Weekly Sharers

Eduardo...

Weekly Questioners