top of page
  • Rajeshkumar M

SRM vRealize/Aria appliance recovery using same network/IP without Stretched Network


To recover VM's with same network without IP change over local non stretched network, i have a T1 Gateway and segments in secondary site same like Primary site and keep it not attached with T0 to isolate the T1 and keep the same network not advertised from secondary site.

My SRM protected VM's are in the network 10.10.10.0/24. I also have other network segment 10.10.20.0/24 which not involved in SRM recovery is connected with same T1 in secondary, site B and that network needs to be advertised.

Now i need to keep the secondary site T1 also attached with T0 then i can create a route advertisement rule in site B T1 to deny that particular network 10.10.10.0/24 being advertised.

When i do the recovery i can make the deny rule in primary site T1 and remove the rule form secondary site, in that way the segment running my SRM protected VM's are advertised from one location.


Fig 1a

Fig 1b

Fig 1a,1b, I have T1 named Site-A-Local-T in primary site A is currently attached with my T0. The T1 is connected with my network 10.10.10.0/24 segment named Site-A-Local-Segment, the same segment Site-A-Local-Segment is where my SRM protected VM's are connected in my primary site.


Fig 2

Fig 2, I have T1 named Site-B-Local-T1 in my secondary site currently not attached with my T0. In this case i can do the SRM recovery and detach the T1 from site A and attach the T1 in Site B to T0 in site B.

Fig 3

Fig 3, whereas Site-B-Local-T1 is connected with two segment Site-B-Local-T1-Segment which is my vRealize appliance network 10.10.10.0/24 to recover vRA VM’s and another network Site-B-Local-non-Recovery-Segment 10.10.20.0/24 it will be used for the VM's not protected with SRM in Site-B.


If I keep the recovery site Site-B-Local-T1 is not connected with T0 then it will make my Site-B-Local-T1 is isolated so the VM’s running on the Site-B-Local-recovery-Segment will lose connectivity.


Fig 4

Fig 5

Fig 4/5, shows the network 10.10.20.0/24 of Site-B-Local-Recovery-Segment is not advertised.


Now I want to keep the network 10.10.10.0/24 is not advertised from Site-B and the Site-B-Local-Recovery-Segment network 10.10.20.0/24 is only getting advertised, to do this I have created a route advertisement rule in Site-B-Local-T1 to deny 10.10.10.0/24 and I can keep the T1 in my secondary site is attached with my T0.


Fig 6

Fig 6, Route advertisement rule created and applied a filter to deny 10.10.10.0/24 network in Site-B-Local-T1.


Fig 7

Fig 8


Fig 7/8, the primary site and secondary site T1’s Site-A-Local-T1 and Site-B-Local-T1 are kept attached with T0.


Fig 9

Fig 10

Fig 9/10, shows the 10.10.20.0/24 network in Site-B-Local-T1 on recovery site is getting advertised and 10.10.10.0/24 is advertised from Site-A-Local-T1. When i do SRM failover the T1 advertisement rule will be swapped and again i will revert this when i fallback.



19 views0 comments

Recent Posts

See All

vSphere Tags to NSX-T Tags

I created a simple powercli script to copy the vSphere Tags to NSX-T, it helped me to copy the NSX-T tags on the recovery VM's in non-federated/local NSX-T managers. Since SRM retain the vSphere TAG's

vIDM Locl user password reset without email link

When resetting config admin or any local user password in VMware identity manager will trigger an email link, if in case the smtp is not working/configured we can use API call to reset the password. Y

Comments


bottom of page