ExpressRoute Direct を構成する方法How to configure ExpressRoute Direct

ExpressRoute Direct を使用すると、世界中に戦略的に分散されたピアリングの場所で Microsoft のグローバル ネットワークに直接接続できます。ExpressRoute Direct gives you the ability to connect directly into Microsoft’s global network at peering locations strategically distributed across the world. 詳しくは、ExpressRoute Direct の接続に関する記事をご覧ください。For more information, see About ExpressRoute Direct Connect.

リソースを作成するCreate the resource

  1. Azure にサインインしてサブスクリプションを選択します。Sign in to Azure and select the subscription. ExpressRoute Direct リソースおよび ExpressRoute 回線は、同じサブスクリプション内にある必要があります。The ExpressRoute Direct resource and ExpressRoute circuits must be in the same subscription.

    Connect-AzAccount 
    
    Select-AzSubscription -Subscription “<SubscriptionID or SubscriptionName>”
    
  2. ExpressRoute Direct がサポートされるすべての場所を一覧表示します。List all locations where ExpressRoute Direct is supported.

    Get-AzExpressRoutePortsLocation
    

    出力例Example output

    Name                : Equinix-Ashburn-DC2
    Id                  : /subscriptions/<subscriptionID>/providers/Microsoft.Network/expressRoutePortsLocations/Equinix-Ashburn-D
                         C2
    ProvisioningState   : Succeeded
    Address             : 21715 Filigree Court, DC2, Building F, Ashburn, VA 20147
    Contact             : support@equinix.com
    AvailableBandwidths : []
    
    Name                : Equinix-Dallas-DA3
    Id                  : /subscriptions/<subscriptionID>/providers/Microsoft.Network/expressRoutePortsLocations/Equinix-Dallas-DA
                         3
    ProvisioningState   : Succeeded
    Address             : 1950 N. Stemmons Freeway, Suite 1039A, DA3, Dallas, TX 75207
    Contact             : support@equinix.com
    AvailableBandwidths : []
    
    Name                : Equinix-San-Jose-SV1
    Id                  : /subscriptions/<subscriptionID>/providers/Microsoft.Network/expressRoutePortsLocations/Equinix-San-Jose-
                         SV1
    ProvisioningState   : Succeeded
    Address             : 11 Great Oaks Blvd, SV1, San Jose, CA 95119
    Contact             : support@equinix.com
    AvailableBandwidths : []
    
  3. 上記で表示された場所に使用可能な帯域幅があるかどうか確認します。Determine if a location listed above has available bandwidth

    Get-AzExpressRoutePortsLocation -LocationName "Equinix-San-Jose-SV1"
    

    出力例Example output

    Name                : Equinix-San-Jose-SV1
    Id                  : /subscriptions/<subscriptionID>/providers/Microsoft.Network/expressRoutePortsLocations/Equinix-San-Jose-
                         SV1
    ProvisioningState   : Succeeded
    Address             : 11 Great Oaks Blvd, SV1, San Jose, CA 95119
    Contact             : support@equinix.com
    AvailableBandwidths : [
                           {
                             "OfferName": "100 Gbps",
                             "ValueInGbps": 100
                           }
                         ]
    
  4. 上記で選択した場所に基づいて ExpressRoute Direct リソースを作成します。Create an ExpressRoute Direct resource based on the location chosen above

    ExpressRoute Direct では、QinQ と Dot1Q 両方のカプセル化がサポートされます。ExpressRoute Direct supports both QinQ and Dot1Q encapsulation. QinQ を選択した場合、各 ExpressRoute 回線に S-Tag が動的に割り当てられ、ExpressRoute Direct リソース全体で一意になります。If QinQ is selected, each ExpressRoute circuit will be dynamically assigned an S-Tag and will be unique throughout the ExpressRoute Direct resource. 回線上の各 C-Tag はその回線で一意である必要がありますが、ExpressRoute Direct 全体ではありません。Each C-Tag on the circuit must be unique on the circuit, but not across the ExpressRoute Direct.

    Dot1Q カプセル化を選択した場合、ExpressRoute Direct リソース全体で C-Tag (VLAN) が一意になるように管理する必要があります。If Dot1Q encapsulation is selected, you must manage uniqueness of the C-Tag (VLAN) across the entire ExpressRoute Direct resource.

    重要

    ExpressRoute Direct ではカプセル化の種類を 1 つしか選択できません。ExpressRoute Direct can only be one encapsulation type. ExpressRoute Direct を作成した後でカプセル化を変更することはできません。Encapsulation cannot be changed after ExpressRoute Direct creation.

    $ERDirect = New-AzExpressRoutePort -Name $Name -ResourceGroupName $ResourceGroupName -PeeringLocation $PeeringLocationName -BandwidthInGbps 100.0 -Encapsulation QinQ | Dot1Q -Location $AzureRegion
    

    注意

    Encapsulation 属性に Dot1Q を設定することもできます。The Encapsulation attribute could also be set to Dot1Q.

    出力例:Example output:

    Name                       : Contoso-Direct
    ResourceGroupName          : Contoso-Direct-rg
    Location                   : westcentralus
    Id                         : /subscriptions/<subscriptionID>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.Network/exp
                                ressRoutePorts/Contoso-Direct
    Etag                       : W/"<etagnumber> "
    ResourceGuid               : <number>
    ProvisioningState          : Succeeded
    PeeringLocation            : Equinix-Seattle-SE2
    BandwidthInGbps            : 100
    ProvisionedBandwidthInGbps : 0
    Encapsulation              : QinQ
    Mtu                        : 1500
    EtherType                  : 0x8100
    AllocationDate             : Saturday, September 1, 2018
    Links                      : [
                                  {
                                    "Name": "link1",
                                    "Etag": "W/\"<etagnumber>\"",
                                    "Id": "/subscriptions/<subscriptionID>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.
                                Network/expressRoutePorts/Contoso-Direct/links/link1",
                                    "RouterName": "tst-09xgmr-cis-1",
                                    "InterfaceName": "HundredGigE2/2/2",
                                    "PatchPanelId": "PPID",
                                    "RackId": "RackID",
                                    "ConnectorType": "SC",
                                    "AdminState": "Disabled",
                                    "ProvisioningState": "Succeeded"
                                  },
                                  {
                                    "Name": "link2",
                                    "Etag": "W/\"<etagnumber>\"",
                                    "Id": "/subscriptions/<subscriptionID>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.
                                Network/expressRoutePorts/Contoso-Direct/links/link2",
                                    "RouterName": "tst-09xgmr-cis-2",
                                    "InterfaceName": "HundredGigE2/2/2",
                                    "PatchPanelId": "PPID",
                                    "RackId": "RackID",
                                    "ConnectorType": "SC",
                                    "AdminState": "Disabled",
                                    "ProvisioningState": "Succeeded"
                                  }
                                ]
    Circuits                   : []
    

リンクの管理状態を変更するChange Admin State of links

このプロセスは、レイヤー 1 のテストを実施して、各相互接続がプライマリとセカンダリの各ルーターに適切に接続されていることを確認するために使用する必要があります。This process should be used to conduct a Layer 1 test, ensuring that each cross-connection is properly patched into each router for primary and secondary.

  1. ExpressRoute Direct の詳細を取得します。Get ExpressRoute Direct details.

    $ERDirect = Get-AzExpressRoutePort -Name $Name -ResourceGroupName $ResourceGroupName
    
  2. リンクを Enabled に設定します。Set Link to Enabled. この手順を繰り返して、各リンクを有効に設定します。Repeat this step to set each link to enabled.

    Links[0] はプライマリ ポート、Links[1] はセカンダリ ポートです。Links[0] is the primary port and Links[1] is the secondary port.

    $ERDirect.Links[0].AdminState = “Enabled”
    Set-AzExpressRoutePort -ExpressRoutePort $ERDirect
    $ERDirect = Get-AzExpressRoutePort -Name $Name -ResourceGroupName $ResourceGroupName
    $ERDirect.Links[1].AdminState = “Enabled”
    Set-AzExpressRoutePort -ExpressRoutePort $ERDirect
    

    出力例:Example output:

    Name                       : Contoso-Direct
    ResourceGroupName          : Contoso-Direct-rg
    Location                   : westcentralus
    Id                         : /subscriptions/<number>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.Network/exp
                              ressRoutePorts/Contoso-Direct
    Etag                       : W/"<etagnumber> "
    ResourceGuid               : <number>
    ProvisioningState          : Succeeded
    PeeringLocation            : Equinix-Seattle-SE2
    BandwidthInGbps            : 100
    ProvisionedBandwidthInGbps : 0
    Encapsulation              : QinQ
    Mtu                        : 1500
    EtherType                  : 0x8100
    AllocationDate             : Saturday, September 1, 2018
    Links                      : [
                                {
                                  "Name": "link1",
                                  "Etag": "W/\"<etagnumber>\"",
                                  "Id": "/subscriptions/<subscriptionID>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.
                              Network/expressRoutePorts/Contoso-Direct/links/link1",
                                  "RouterName": "tst-09xgmr-cis-1",
                                  "InterfaceName": "HundredGigE2/2/2",
                                  "PatchPanelId": "PPID",
                                  "RackId": "RackID",
                                  "ConnectorType": "SC",
                                  "AdminState": "Enabled",
                                  "ProvisioningState": "Succeeded"
                                },
                                {
                                  "Name": "link2",
                                  "Etag": "W/\"<etagnumber>\"",
                                  "Id": "/subscriptions/<subscriptionID>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.
                              Network/expressRoutePorts/Contoso-Direct/links/link2",
                                  "RouterName": "tst-09xgmr-cis-2",
                                  "InterfaceName": "HundredGigE2/2/2",
                                  "PatchPanelId": "PPID",
                                  "RackId": "RackID",
                                  "ConnectorType": "SC",
                                  "AdminState": "Enabled",
                                  "ProvisioningState": "Succeeded"
                                }
                              ]
    Circuits                   : []
    

    同じ手順を AdminState = “Disabled” について使用して、ポートを停止します。Use the same procedure with AdminState = “Disabled” to turn down the ports.

回線を作成するCreate a circuit

既定では、ExpressRoute Direct リソースがあるサブスクリプション内に 10 個の回線を作成できます。By default, you can create 10 circuits in the subscription where the ExpressRoute Direct resource is. これはサポートによって増やすことができます。This can be increased by support. プロビジョニング済みの帯域幅と使用済みの帯域幅の両方を追跡してください。You are responsible for tracking both Provisioned and Utilized Bandwidth. プロビジョニング済み帯域幅は、ExpressRoute Direct リソース上のすべての回線の帯域幅の合計です。使用済み帯域幅は、基になる物理インターフェイスの物理的な使用量です。Provisioned bandwidth is the sum of bandwidth of all circuits on the ExpressRoute Direct resource and utilized bandwidth is the physical usage of the underlying physical interfaces.

ExpressRoute Direct には、前述したシナリオをサポートするために利用できるだけの追加の回線帯域幅があります。There are additional circuit bandwidths that can be utilized on ExpressRoute Direct only to support the scenarios outlined above. 次のとおりです。40 Gbps と 100 Gbps です。These are: 40Gbps and 100Gbps.

SkuTier には Local、Standard、または Premium を使用できます。SkuTier can be Local, Standard or Premium.

ExpressRoute Direct では無制限がサポートされていないため、SkuFamily には MeteredData のみを使用できます。SkuFamily must be MeteredData only as unlimited is not supported on ExpressRoute Direct.

ExpressRoute Direct リソース上に回線を作成します。Create a circuit on the ExpressRoute Direct resource.

New-AzExpressRouteCircuit -Name $Name -ResourceGroupName $ResourceGroupName -ExpressRoutePort $ERDirect -BandwidthinGbps 100.0  -Location $AzureRegion -SkuTier Premium -SkuFamily MeteredData 

他の帯域幅には、5.0、10.0、および 40.0 が含まれます。Other bandwidths include: 5.0, 10.0, and 40.0

出力例:Example output:

Name                             : ExpressRoute-Direct-ckt
ResourceGroupName                : Contoso-Direct-rg
Location                         : westcentralus
Id                               : /subscriptions/<subscriptionID>/resourceGroups/Contoso-Direct-rg/providers/Microsoft.Netwo
                                 rk/expressRouteCircuits/ExpressRoute-Direct-ckt
Etag                             : W/"<etagnumber>"
ProvisioningState                : Succeeded
Sku                              : {
                                   "Name": "Premium_MeteredData",
                                   "Tier": "Premium",
                                   "Family": "MeteredData"
                                 }
CircuitProvisioningState         : Enabled
ServiceProviderProvisioningState : Provisioned
ServiceProviderNotes             : 
  ServiceProviderProperties        : null
ExpressRoutePort                 : {
                                   "Id": "/subscriptions/<subscriptionID>n/resourceGroups/Contoso-Direct-rg/providers/Micros
                                 oft.Network/expressRoutePorts/Contoso-Direct"
                                 }
BandwidthInGbps                  : 10
Stag                             : 2
ServiceKey                       : <number>
Peerings                         : []
Authorizations                   : []
AllowClassicOperations           : False
GatewayManagerEtag     

次の手順Next steps

ExpressRoute Direct について詳しくは、概要のページをご覧ください。For more information about ExpressRoute Direct, see the Overview.