JUNIPER ROUTE REFLECTOR HOW TO

The policies will look identical on each ESG with the exception of the BGP neighbor to which the policy is attached. On each ESG we will configure BGP import and export policies. We’ll start by configuring the NSX edge gateways. Although the steps are almost identical for QFX2 and ESG2. This example details the necessary steps for QFX1 and ESG1. They will also be configured to import the default route ( 0.0.0.0/0) received from the QFXs. 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 NSX internal network 10.10.10.0/24. The Juniper QFX switches will be configured to export a default route ( 0.0.0.0/0) towards the NSX Edges. In the following scenario, we’re going to configure BGP import and export policies on Juniper QFX Switches and VMware NSX Edge Gateways.

Readvertise all active BGP routes to all configured BGP neighbors.

Do not advertise routes learned from IBGP neighbors to any other configured IBGP neighbor.

Accept all BGP routes learned from configured BGP neighbors and import them into the relevant routing table.

Here’s a quick reminder of the default behaviours:- Default Import Policy 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. In certain scenarios, you may find that the default BGP import and export behaviour is sufficient. When working with BGP, it’s important to consider how BGP routes are imported and exported.

JUNIPER ROUTE REFLECTOR HOW TO

This time we’ll take a look at how to configure BGP route policy and BGP filters. 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.

Juniper route reflector