I have two 405f unity and trying to setup replication but facing errors, my current setup is as follows :
First unity
1) Link aggregated of all 4 ethernet ports ( i tried to aggregate 2 ports for NAS server and 2 ports for replication but there was no option to select). all 4 ports are connected in one switch and aggregation is configured.
2) all 4 ports are trunked on switch and has vlan 775 and 560, on unity vlan tagging is done on all ports.
3) NAS server is in vlan 775 with ip 10.10.10.xxx.
Second Unity
1) Link aggregated of all 4 ethernet ports all 4 ports are connected in one switch and aggregation is configured.
2) all 4 ports are trunked on switch and has only 560 vlan. on unity vlan tagging is done on all ports.
3) NAS server and replication interfaces are on 560 vlan.
When i tried to create replication connection, it failed as shown below:
I read the KB but all scenarios mentioned, doesnt apply in my case. i am just trying Synchronous replication with Ethernet ports. Any other suggestions please.
Just to be clear, are you trying to configure aysnc replication or synchronous replication? Sync replication requires a fibre channel link between the source and destination.
I am trying Asynchronization replication with Ethernet ports, there is 4 Ethernet ports available on the box on each SP, these ports are in link aggregation.
Start with basic network troubleshooting: can the replication IPs on Unity 1 reach the replication IPs of Unity 2?
You should use uemcli to check this - either install the package locally on your PC or SSH to the Unity management address using the service user (you might need to activate SSH in the Service Tasks in Unisphere). By default the service user password is the same as for admin.
List network interfaces using this command: uemcli /net/if -type replication show
Each IP has its own interface name (for example: if_6) Note the Interface Names for the replication addresses you have defined on each unity.
Now you can try pinging the target address from the source interface. For Example:
(srcIf has a capital I, not a lower case L, and uemcli commands are case sensitive)
Each source interface needs to be able to ping the target IPs on the other Unity. If these commands fail then it's a network problem. I often find that the tagged/untagged problem crops up. For example, the network ports are defined in a specific VLAN with no tagging, but you put the VLAN ID on the Unity ports. The management IPs of each Unity also need to be able to talk to each other.
DELL-Sam L
Community Manager
•
8056 Posts
•
34380 Points
1108
0
Posted April 6th, 2021 10:00
Hello smrajan78,
Here is a link to a KB that maybe of assistance.
https://dell.to/2PHP3aj