Tag: Configuration

Next Generation Multicast VPN (NG-MVPN) configuration example

Next Generation Multicast VPN (NG-mVPN)

NG-mVPN is a next-generation multicast distribution technology that is predominantly used in service provider networks and addresses scalability and manageability issues associated with the previous generation of SP Multicast VPN (Draft Rosen).

In this article, we will go through configuration steps you’d need to undertake to configure NG-mVPN in a Juniper environment. We will also discuss BGP advertisements that are associated with multicast sources and receivers connected to the network.
Continue reading “Next Generation Multicast VPN (NG-MVPN) configuration example”

EVPN MPLS Port-Based VLAN-Aware Bundle Service

In this article, we will review EVPN MPLS Port-Based VLAN-Aware Bundle Service  configuration example using Juniper MX devices. As per Port-Based VLAN-Aware service definition in RFC7432, all of the VLANs on the port are part of the same service and are mapped to a single bundle without any VID translation.

EVPN VLAN-Aware Bundle Service
EVPN VLAN-Aware Bundle Service

In our sample, we will add L3 IRB interfaces to VLANs, simulating L3 Default Gateways.
Continue reading “EVPN MPLS Port-Based VLAN-Aware Bundle Service”

EVPN Type 5 Configuration Example – Juniper MX

Introduction

In this example, we will show how to configure L2 and L3 EVPN service on Juniper MX devices.

If you are not familiar with EVPN, please review our introductory articles on EVPN.

In this lab, we will leverage our previous example, where we delivered L2 connectivity between multiple sites, and will augment it with L3 site-to-site connectivity options.

One shared broadcast domain with IP range 1.1.1.0/24 is used on PE-CE interfaces across the entire network. Each CE site is assigned a unique subnet on LAN interface.

EVPN Type 5 Lab Topology
EVPN Type 5 Lab Topology

Continue reading “EVPN Type 5 Configuration Example – Juniper MX”

MPLS VPN Service with Segment Routing

MPLS VPN Configuration example with IS-IS based Segment Routing (SPRING) on Juniper QFX5100 devices. The purpose of this lab is to demonstrate what LDP or RSVP-TE can be easily replaced with SR.

Complete Configuration Repository on GitHub:

https://github.com/bgphelp/blueprints/tree/master/SR/MPLS-VPN-SR-QFX5100

 
Continue reading “MPLS VPN Service with Segment Routing”

Segment Routing Cisco – Juniper Interop Design

Cisco and Juniper Segment Routing Interoperability design with configuration examples.  IS-IS based IGP topology.

Complete configuration repository on GitHub: https://github.com/bgphelp/blueprints/tree/master/1-SR-Cisco-Juniper

 

Continue reading “Segment Routing Cisco – Juniper Interop Design”

LDP to Segment Routing (also known as SR and SPRING) Migration Steps

Step-by-step migration from LDP-based design to Segment Routing topology in Juniper environment.  In this example, we will be using IS-IS as IGP protocol. 
Continue reading “LDP to Segment Routing (also known as SR and SPRING) Migration Steps”

Migrating to BGP-Free Core in Juniper Environment

Discussion on how to migrate to BGP-Free Core by deploying MPLS as network tunneling mechanism. Document provides step-by-step migration steps for a Juniper-based network.  
Continue reading “Migrating to BGP-Free Core in Juniper Environment”

Juniper High Availability Customer Site using AS-Prepend

Configuring Dual-CE BGP High Availability Site. This article provides Juniper Configuration Example that uses BGP AS-Prepend to identify primary and secondary paths.
Continue reading “Juniper High Availability Customer Site using AS-Prepend”

Advertising Aggregates Routes

As a BGP admin, you will often need to make decisions on the ways to partition your IP Space, which routes to advertise to the Internet and which routes to suppress.

Ideally, you’d want to aggregate your IPv4/IPv6 Space as much as possible, by only advertising aggregate prefixes (also known as supernets and summary routes) to the Internet. Practically, this would mean that your Autonomous System (AS) will originate IP prefixes assigned to you by Regional Internet Registries (RIRs) or delegated to you by Upstream Providers, while suppressing all other advertisements. If everybody were to follow this rule, the Internet routing table would be much smaller and we would not have issues with FIB exhaustion.
Continue reading “Advertising Aggregates Routes”