The virtualHubs/bgpConnections resource type can be deployed with operations that target:
For a list of changed properties in each API version, see change log.
To create a Microsoft.Network/virtualHubs/bgpConnections resource, add the following JSON to your template.
{
"type": "Microsoft.Network/virtualHubs/bgpConnections",
"apiVersion": "2023-04-01",
"name": "string",
"properties": {
"hubVirtualNetworkConnection": {
"id": "string"
},
"peerAsn": "int",
"peerIp": "string"
}
}
Name | Description | Value |
---|---|---|
type | The resource type | 'Microsoft.Network/virtualHubs/bgpConnections' |
apiVersion | The resource api version | '2023-04-01' |
name | The resource name See how to set names and types for child resources in JSON ARM templates. |
string (required) |
properties | The properties of the Bgp connections. | BgpConnectionProperties |
Name | Description | Value |
---|---|---|
hubVirtualNetworkConnection | The reference to the HubVirtualNetworkConnection resource. | SubResource |
peerAsn | Peer ASN. | int |
peerIp | Peer IP. | string |
Name | Description | Value |
---|---|---|
id | Resource ID. | string |
The following quickstart templates deploy this resource type.
Template | Description |
---|---|
Create a Route Server in a New Subnet |
This template deploys a Route Server into a subnet named RouteServerSubnet. |
Azure Route Server in BGP peering with Quagga |
This template deploys a Router Server and Ubuntu VM with Quagga. Two external BGP sessions are established between the Router Server and Quagga. Installation and configuration of Quagga is executed by Azure custom script extension for linux |