Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-analytics-dashboard-for-wp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\inetpub\vhosts\gck.org.uk\httpdocs\c7solutions\wp-includes\functions.php on line 6114
Configuring ExpressRoute With NRP Errors – Brian Reid – Microsoft 365 Subject Matter Expert

Configuring ExpressRoute With NRP Errors


I had a scenario where when I ran Get-AzureRmExpressRouteServiceProvider in a new Azure tenant I would get the following error in PowerShell.

Get-AzureRmExpressRouteServiceProvider : Subscription a4ca03ea-42e4-4a18-a50f-79bcc53907e4 is not registered with NRP.
At line:1 char:1
+ Get-AzureRmExpressRouteServiceProvider
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Get-AzureRmExpressRouteServiceProvider], CloudException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Network.GetAzureExpressRouteServiceProviderCommand

This is one of the required cmdlets in configuring ExpressRoute. The fix is to use the following cmdlets to create the required objects that are not mentioned in the ExpressRoute setup article at https://azure.microsoft.com/en-us/documentation/articles/expressroute-howto-circuit-arm/ and then return to this article and complete the rest of the setup.

  1. First, ensure you are logged into Azure PowerShell using the Resource Manager cmdlets (see https://azure.microsoft.com/en-us/blog/azps-1-0/ for steps to install these) and Login-AzureRMAccount to login to the correct tenant
  2. Second, select your subscription with Get-AzureRMSubscription followed by Select-AzureRMSubscription –SubscriptionName “Free Trial”. Replace “Free Trial” with the name of your subscription.
  3. Run Get-AzureRmExpressRouteServiceProvider – you should get the above error. If not then this blog post is not relevant to you
  4. Create a resource group and then create a virtual network inside this resource group. These settings will need to be set to something suitable for your network. Suitable means not overlapping with any subnet on-premises. The AzureRM PowerShell to do this looks like the following:
  5. # Create a VNet with two (or more subnets). First subnet must be named GatewaySubnet and min /28

    $Location = “West Europe”
    New-AzureRmResourceGroup -Name “InternalNetworkResourceGroup” -Location $Location
    $GatewaySubnet = New-AzureRmVirtualNetworkSubnetConfig -Name ‘GatewaySubnet’ -AddressPrefix 192.168.192.0/28
    $LANSubnet1 = New-AzureRmVirtualNetworkSubnetConfig -Name ‘AzureLAN1’ -AddressPrefix ‘192.168.192.16/28’
    New-AzureRmVirtualNetwork -Name AzureInternal -ResourceGroupName “InternalNetworkResourceGroup” -Location $Location -AddressPrefix 192.168.192.0/24 -Subnet $LANSubnet1,$GatewaySubnet

  6. You can now run Get-AzureRmExpressRouteServiceProvider  without error and continue creating your ExpressRoute request and obtain your service key

Posted

in

, ,

by

Tags:

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.