lynchc
Contributor
Contributor

Cross vCenter NSX with SRM Auto Mapping Fails

Jump to solution

I have a cross vCenter NSX 6.2.4 implementation using SRM 6.1, the issue I am having is the full name of the virtualwire in each vCenter is different (see below) the difference is the MoRef of the vDS.

in all examples I can find on-line, the full name of the virtual wire is identical, including the MoRef of the vDS.

So SRM is not automapping the networks as  it looks to match the whole vDS port-group name, not just the universal logical switch portion, I don't really want to have to map these networks manually as it should work fine with automapping.

Using storage policy protection groups,

Site 1, vCenter 1

vxw-dvs-102-universalwire-47-sid-900012-colin-test

Site 2, vCenter 2

vxw-dvs-63-universalwire-47-sid-900012-colin-test

vxw                                 -> VXLAN-VirtualWire to distinguish the port-group that it was created by NSX

dvs-22                           -> MoRef* of the vDS (check in mob: https://<vcenter>/mob/ )

universalwire-47           -> universal vwire id within NSX

sid-900012                   -> segment id what this wire is using (VXLAN VNI)

colin-test                      -> name of the logical switch

*A Managed Object Reference ID also known just as MoRef ID

Anyone seen this before?

1 Solution

Accepted Solutions
rbudavari
VMware Employee
VMware Employee

The MoRef of the backing dvPortgroup can be different - as SRM matches the network for a universal logical switch using VNI, however this automapping only works with vSphere Replication currently. Are you using Array based replicaiton with SRM ? if so that would explain why the mapping is not working.

View solution in original post

2 Replies
rbudavari
VMware Employee
VMware Employee

The MoRef of the backing dvPortgroup can be different - as SRM matches the network for a universal logical switch using VNI, however this automapping only works with vSphere Replication currently. Are you using Array based replicaiton with SRM ? if so that would explain why the mapping is not working.

View solution in original post

raisalkh
Contributor
Contributor

Hi

I have got some solution for it. MOREF is created in serial order, so you can match it by creating objects where has lower  value.

example: one vcenter for me was giving moref id for dvs to dvs-70 and other was dvs-71 and there will moref for prort goup aswell so next switch moref will be dvs-73 for first and dvs-74 for second one. but you can bring the number to same order by creating additional portgroup in first switch before creating new switch

https://vcenter-dc.vcp.local/mob/?moid=dvs-70

pastedImage_1.png

https://vcenter-dc.vcp.local/mob/?moid=dvs-75

pastedImage_2.png

0 Kudos