SRM Configure Network Mapping

Share on facebook
Share on google
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email
Table of Contents

introduction

In the previous two articles , we have discussed  Configuring SRM folder mapping as well as resource mapping .

 In this article , we will discuss   SRM network mapping.

 One of the important step in SRM inventory mappings.

 Network mapping needs to configured properly. If you don’t get this configured correctly, the VMs that are powered on at the Recovery Site might not be accessible across the network.  

SRM Network mapping can only be related to Virtual machine port groups.

You cannot map management network or VMkernel port groups

Here in network pioneers [pioneers.lab] for example : we have 6 port group , But only one port group for VM traffic , which called [ VM network ]

We  recommend you to create the similar Port groups names  . It will help you to easily configure the network mappings.

Configuring SRM Network Mapping

To configure the Folder mapping :

Login to your Protected site vCenter server VCSA-prod-155  using vSphere web client. 

https://vcsa-prod-155.pioneers.lab/

Click on SRM plugin -> Select Protected site vCenter and Click on  Create Folder mapping under inventory mappings.

 

For Better View > Open Image in different TAB
open vcenter > home > site recovery > open site recovery
select network mapping > new
we recommend to select auto creation mode
we have only one port group for VM traffic in each site which called [VM network] > select add mapping
SRM discover 1 port group
port group added
select reverse mapping
SRM will create test network in DR to isolate VM from real working VM
review and finished
Network mapping from production site
Network mapping from DR site

Conclusion

 The virtual machines would certainly boot and be configured the way they were configured in the production site with the same static IPs, etc. 

However, keep in mind the virtual machine would need all the same network infrastructure in place before it would truly be able to communicate, including the same gateway and DNS server addresses

Generally speaking, most recovery or DR sites are not running the same internal LAN subnet as exists for the production subnet as this would result in overlapping subnets and routing issues.

 

VMware’s Site Recovery Manager includes some really great functionality that helps to consider  for the network differences that exist in the protected site vs the network configuration that may exist in the recovery site. 

This allows SRM to reconfigure the recovered virtual machine (replicated virtual machine) with the corresponding network settings that are appropriate for the recovery site.

The solution is simply : SRM  Network Mappings 

As explained above . 

Share this post
Share on facebook
Share on google
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email

About Me

Our Power in Numbers

 17 

Courses

321

Articles

3,882

Images
and All configurations images are proudly made in Pioneers Lab

Articles By Course

Recent Articles

Subscribe

Contact us

have a challenge ? don’t hesitate to contact us