Second NIC interface on the Configuration Server for Azure Site Recovery

%3CLINGO-SUB%20id%3D%22lingo-sub-1331616%22%20slang%3D%22en-US%22%3ESecond%20NIC%20interface%20on%20the%20Configuration%20Server%20for%20Azure%20Site%20Recovery%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1331616%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20deploying%20Azure%20Site%20Recovery%20for%20an%20on-premises%20environment%20running%20about%2015-20%20VMware%20servers%20(Windows%20and%20Linux).%3C%2FP%3E%3CP%3EI%20will%20use%20a%20Hub%20%26amp%3B%20Spoke%20architecture%20on%20Azure.%20One%20spoke%20will%20only%20be%20peered%20with%20the%20hub%20in%20real%20DR%20scenario%20because%20I%20will%20use%20a%20VNet%20CIDR%20equivalent%20as%20the%20on-premises.%20The%20second%20spoke%20will%20be%20peered%20to%20the%20hub%20and%20will%20be%20used%20for%20recovery%20drills.%3C%2FP%3E%3CP%3EThere%20will%20be%20a%20S2S%20VPN%20connection%20between%20the%20on-premises%20and%20Azure%20environments.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20read%20through%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fvmware-azure-deploy-configuration-server%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edeployment%20instructions%20%3C%2FA%3Efor%20the%20configuration%20server%20and%20it%20states%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fvmware-azure-deploy-configuration-server%23add-an-additional-adapter%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20that%20a%20second%20NIC%20is%20required%20if%20we%20want%20to%20keep%20the%20source%20IP%20addresses%20in%20Azure%20and%20if%20we%20want%20to%20failback.%3C%2FP%3E%3CP%3EThe%20statement%20is%20%22%3CEM%3EOne%20NIC%20is%20connected%20to%20source%20machines%2C%20and%20the%20other%20NIC%20is%20used%20for%20Azure%20connectivity%3C%2FEM%3E%22%20but%20I'm%20not%20sure%20to%20understand%20this%20part.%20One%20NIC%20will%20be%20on%20the%20local%20(on-premises)%20network%20but%20what%20about%20the%20second%20NIC%20%3F%3C%2FP%3E%3CP%3EIf%20there%20is%20a%20VPN%20connection%2C%20on%20what%20VNet%2Fsubnet%20CIDR%20this%20second%20NIC%20has%20to%20be%20connected%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20help%3C%2FP%3E%3CP%3ENicolas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1331616%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Site%20Recovery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi,

 

I'm deploying Azure Site Recovery for an on-premises environment running about 15-20 VMware servers (Windows and Linux).

I will use a Hub & Spoke architecture on Azure. One spoke will only be peered with the hub in real DR scenario because I will use a VNet CIDR equivalent as the on-premises. The second spoke will be peered to the hub and will be used for recovery drills.

There will be a S2S VPN connection between the on-premises and Azure environments.

 

I read through the deployment instructions for the configuration server and it states here that a second NIC is required if we want to keep the source IP addresses in Azure and if we want to failback.

The statement is "One NIC is connected to source machines, and the other NIC is used for Azure connectivity" but I'm not sure to understand this part. One NIC will be on the local (on-premises) network but what about the second NIC ?

If there is a VPN connection, on what VNet/subnet CIDR this second NIC has to be connected ?

 

Thanks for your help

Nicolas

0 Replies