Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Can't attach Azure NIC to the Kemp VM

 

Information

 

Summary:

This article will cover the pre-requisites to ensure a NIC can be properly attached to a VM in Azure.

Environment:

Product: LoadMaster

Version: Any

Platform: Azure

Application: Any

Question/Problem Description:

Trying to deploy a loadmaster in Azure. This is in its own resource group(RG) and will front servers in a different resource group. Both RG's are in the same geographical area. Multiple vnets due to IP range overlap is not wanted. An acceptable configuration is to use a network interface in the Kemp RG to uses an IP address range in the server RG.  But in the attached it to the Kemp VM it does not show up as an option. Was a step missed somewhere?

Steps to Reproduce:  
Error Message:  
Defect Number:  
Enhancement Number:  
Cause:  
Resolution:

The NIC needs to be in the same Resource Group as the Kemp VM.

A separate VNET should be attached to the new NIC to ensure no subnet overlap occurs with the existing VNET.

Workaround:  
Notes:

https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm


Was this article helpful?
0 out of 0 found this helpful

Comments