Azure Stack Development Kit – BGP

Now that we have our Azure Stack Development Kit in routing mode, we can also send the BGP information from within the Stack to the Juniper Firewalls (or any FW you have..). This will ensure that the new “external IP addresses” that are assigned to our workloads are accessible via our intranet route information and that we don’t have to manually add the routes and/or new subnets ourselves..

In short, what happens inside the Stack when you create a new workload is:

  • A new IP address from the “private” range is assigned to the workload (external IP address)
  • The public IP address is added to the BGP routing table by the SLB and sent to the BGPNAT router
  • This means the BGPNAT router now knows how to get to the public IP address

All the addresses are added to the BGPNAT router as /32 entries.. so there is not a single /24 subnet or something:

1. Routing table on AzS-BGPNAT

In order to get these to our Juniper, we can do the following:

  • Login to the AzS-BGPNAT VM
  • Open Powershell
    • Add-BgpPeer -Name Juniper -LocalIPAddress -PeerIpAddress -LocalASN 65050 -PeerASN 65050

(replace the ip addresses with the addresses in your environment – is my external IP address for AzS-BGPNAT and is my Juniper)

Next on the Juniper we need to configure the Protocols BGP. I created a new group for it in my BGP tables:

group stack {
type internal;
multihop {
ttl 50;
peer-as 65050;

And that is all you need. When you wait a few minutes you should see the routes coming into your Juniper:

Note: after you see the IP addresses, you will also need to put in a security policy rule, allowing intra-traffic (in my case I added to the Internal zone). You can do this by issuing : set security policies from-zone Internal to-zone Internal policy Allow-Intra match ……. same as you would for any other policy

Tagged ,