SR troubleshooting in IS-IS environment
- show mpls interface
- show isis adjacency
- show isis database extensive
- show route table inet.3
Ethernet VPN (EVPN) is a new technology that is used to extend Ethernet circuits across Data Center and Service Provider networks. It is expected to succeed other L2VPN transport methods such as BGP-based L2VPN (RFC6624), LDP-Based L2VPN (RFC4906) and VPLS.
EVPN introduces a set of new features that were not available in L2VPN and VPLS environments, most noticeable of which are All-Active Multi-homing across multiple PE devices and more efficient handling of L2 Multicast traffic.
One of the most exciting features of EVPN technology is support for L2 Multi-Homing, where customer CE/Server/VM can be connected to multiple PE devices as depicted below.
EVPN Type 6 Route is defined in IGMP and MLD Proxy for EVPN IETF draft. The purpose of this route is to distribute Host’s or VM’s intent to receive Multicast traffic for a certain Multicast Group (*,G) or Source-Group combination (S,G).
Continue reading “EVPN Type 6 (Selective Multicast Ethernet Tag Route) Explained”
Section 16 of EVPN RFC7432 defines the mechanism for forwarding multicast traffic within EVPN networks. Ingress Replication and/or P2MP LSPs may be used for Multicast forwarding. The major shortcoming of Multicast forwarding approach defined in RFC7432 is the lack of per-group multicast trees, meaning that Multicast traffic is getting forwarded to all PE devices participating in a given EVPN instance, regardless of presence of interested receivers.
Continue reading “Need for IGMP and MLD Proxy in EVPN Environment”
|Route Type||Description||RFC||Route Type Explained|
|1||Ethernet Auto-Discovery (A-D) route||RFC 7432||EVPN Type 1 Explained|
|2||MAC/IP advertisement route||RFC 7432||EVPN Type 2 Explained|
|3||Inclusive Multicast Route||RFC 7432||EVPN Type 3 Explained|
|4||Ethernet Segment Route||RFC 7432||EVPN Type 4 Explained|
|5||IP Prefix Route||draft-ietf-bess-evpn-prefix-advertisement-04||EVPN Type 5 Explained|
|6||Selective Multicast Ethernet Tag Route||draft-ietf-bess-evpn-igmp-mld-proxy-00||EVPN Type 6 Explained|
|7||IGMP Join Synch Route||draft-ietf-bess-evpn-igmp-mld-proxy-00||EVPN Type 7 Explained|
|8||IGMP Leave Synch Route||draft-ietf-bess-evpn-igmp-mld-proxy-00||EVPN Type 8 Explained|
|9||Per-Region I-PMSI A-D route||draft-ietf-bess-evpn-bum-procedure-updates-01|
|10||S-PMSI A-D route||draft-ietf-bess-evpn-bum-procedure-updates-01|
|11||Leaf A-D route||draft-ietf-bess-evpn-bum-procedure-updates-01|
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.
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”
In this article, we will review inter-subnet routing scenarios in EVPN environment. As we will discover, certain topologies might lead to sub-optimal traffic flows within EVPN network.
Our setup will be comprised of three PE and four CE devices as shown below:
Hot Potato and Cold Potato are two practices of exchanging traffic between BGP Peers. The difference in these two methods is in the approaches to how to carry traffic across the network.
Hot Potato vs Cold Potato discussions are only relevant in the scenarios where multiple traffic exchange (peering) points exist between two networks.
In our example, we will use the following diagrams depicting two networks spanning across North America and Europe.
We are interested in the traffic flow that is originated by Customer-NA connected to ISP-BLUE and is destined to Customer-EU connected to ISP-GREEN.
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 184.108.40.206/24 is used on PE-CE interfaces across the entire network. Each CE site is assigned a unique subnet on LAN interface.