Neste artigo iremos criar um peering entre Vnet no Azure com gateway e propagação de vnet (uma Vnet será o HUB para conexão em qualquer outra Vnet)
#Subscriptions
export Subscription_01=’Santana-Corp’
#Name Object
export NameObject_01=”${Vnet_01}”-“${Subscription_01}”-“${Environment_01}”
#Peering
export Vnet_Name_01=”vnet-Shared-Prodution”
export Vnet_Name_02=”vnet-databases-Prodution”
export Peering_01=”Peering-vnet-Shared-Prodution”
export Peering_02=”Peering-vdatabases-Prodution-Network”
#Vnet Remote
export Vnet_Remote_01=”/subscriptions/XXXXXXXXXXXXXXXXXX/resourceGroups/databases-Prodution-Network/providers/Microsoft.Network/virtualNetworks/vnet-databases-Prodution”
export Vnet_Remote_02=”/subscriptions/XXXXXXXXXXXXXXXXXX/resourceGroups/Shared-Prodution-Network/providers/Microsoft.Network/virtualNetworks/vnet-Shared-Prodution”
#Selecionar subscription
az account set –subscription “${Subscription_01}”
#Criando Peering
## Vnet Shared Prodution
az network vnet peering create -g “${RG_Name01}” -n “${Peering_01}” –vnet-name “${Vnet_Name_01}” –remote-vnet “${Vnet_Remote_01}” –allow-vnet-access –allow-forwarded-traffic –allow-gateway-transit –allow-vnet-access
## Vnet Shared Prodution
az network vnet peering create -g “${RG_Name02}” -n “${Peering_02}” –vnet-name “${Vnet_Name_02}” –remote-vnet “${Vnet_Remote_02}” –allow-vnet-access –allow-forwarded-traffic –allow-vnet-access –use-remote-gateways
Resultado
Vnet Shared Prodution
Vnet Data Base Prodution
Veja que em nosso gateway de VPN BGP já esta propagando a nova vnet
Em próximo artigo iremos criar o “Local Gateway Network” para nossa conexão BGP com nosso ambiente onpremises.
2 comentários