Quickstart: Create a Network Function Manager device resource

In this quickstart, you create a Device resource for Azure Network Function Manager (NFM). The Network Function Manager device resource is linked to the Azure Stack Edge resource. The device resource aggregates all the network functions deployed on Azure Stack Edge device and provides common services for deployment, monitoring, troubleshooting, and consistent management operations for all network functions deployed on Azure Stack Edge. You are required to create the Network Function Manager device resource before you can deploy network functions to Azure Stack Edge device.

Prerequisites

Verify the following prerequisites:

• Verify that you have an Azure account with an active subscription. If you need an account, create an account for free.
• You have met all the prerequisites listed in the Prerequisites and requirements article.
• You have the proper permissions assigned. For more information, see Resource Provider registration and permissions.
• Review the Region Availability section before creating a Device resource.
• Verify that you can remotely connect from a Windows client to the Azure Stack Edge Pro GPU device via PowerShell. For more information, see Connect to the PowerShell interface.

Create a device resource

If you have an existing Azure Network Function Manager device resource, you don't need to create one. Skip this section and go to the registration key section.

To create a device resource, use the following steps.

1. Sign in to the Azure portal using your Microsoft Azure credentials.

2. On the Basics tab, configure Project details and Instance details with the device settings.

   When you fill in the fields, a green check mark will appear when characters you add are validated. Some details are auto filled, while others are customizable fields:

   • Subscription: Verify that the subscription listed is the correct one. You can change subscriptions by using the drop-down.
   • Resource group: Select an existing resource group or click Create new to create a new one.
   • Region: Select the location for your device. This must be a supported region. For more information, see Region Availability.
   • Name: Enter the name for your device.
   • Azure Stack Edge: Select the Azure Stack Edge resource that you want to register as a device for Azure Network Function Manager. The ASE resource must be in Online status for a device resource to be successfully created. You can check the status of your ASE resource by going to Properties section in the Azure Stack Edge resource page.

3. Select Review + create to validate the device settings.

4. After all the settings have been validated, select Create.

   Note

   The Network Function Manager device resource can be linked to only one Azure Stack Edge resource. You will be required to create a separate NFM device resource for each Azure Stack Edge resource.

Get the registration key

1. Once your device is successfully provisioned, navigate to the resource group in which the device resource is deployed.

2. Click the device resource. To obtain the registration key, click Get registration key. Ensure you have the proper permissions to generate a registration key. For more information, see the Resource Provider registration and permissions article.

   

3. Make a note of the device registration key, which will be used in the next steps.

   Important

   The registration key expires 24 hours after it is generated. If your registration key is no longer active, you can generate a new registration key by repeating the steps in this section.

Register the device

Follow these steps to register the device resource with Azure Stack Edge.

1. To register the device with the registration key obtained in the previous step, connect to the Azure Stack Edge device via Windows PowerShell.

2. Once you have a PowerShell (minishell) connection to the appliance, enter the following command with the device registration key you obtained from the previous step as the parameter:

   Invoke-MecRegister <device-registration-key>
   

3. Verify that the device resource has Device Status = registered.

   

Next steps