This post follows on from a previous article which detailed how to establish a BGP peering session between Juniper QFX and VMware NSX Edge Gateway. This time we’ll take a look at how to configure BGP route policy and BGP filters.
When working with BGP, it’s important to consider how BGP routes are imported and exported. In certain scenarios, you may find that the default BGP import and export behaviour is sufficient. But more often than not, you will want to implement an import and export policy in order to control how traffic flows through your network. Here’s a quick reminder of the default behaviours:-
Default Import Policy
- Accept all BGP routes learned from configured BGP neighbors and import them into the relevant routing table.
Default Export Policy
- Do not advertise routes learned from IBGP neighbors to any other configured IBGP neighbor. Unless acting as a route reflector.
- Readvertise all active BGP routes to all configured BGP neighbors.
In the following scenario, we’re going to configure BGP import and export policies on Juniper QFX Switches and VMware NSX Edge Gateways. The Juniper QFX switches will be configured to export a default route (0.0.0.0/0) towards the NSX Edges. They will also be configured to import the NSX internal network 10.10.10.0/24. The NSX Edges will be configured to export the NSX internal network 10.10.10.0/24. They will also be configured to import the default route (0.0.0.0/0) received from the QFXs.
Note. This example details the necessary steps for QFX1 and ESG1. Although the steps are almost identical for QFX2 and ESG2.