- play_arrow Overview
- play_arrow Managing Group Membership
- play_arrow Configuring IGMP and MLD
- play_arrow Configuring IGMP Snooping
- IGMP Snooping Overview
- Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN Environment
- Configuring IGMP Snooping on Switches
- Example: Configuring IGMP Snooping on Switches
- Example: Configuring IGMP Snooping on EX Series Switches
- Verifying IGMP Snooping on EX Series Switches
- Changing the IGMP Snooping Group Timeout Value on Switches
- Monitoring IGMP Snooping
- Example: Configuring IGMP Snooping
- Example: Configuring IGMP Snooping on SRX Series Devices
- Configuring Point-to-Multipoint LSP with IGMP Snooping
- play_arrow Configuring MLD Snooping
- Understanding MLD Snooping
- Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)
- Configuring MLD Snooping on a Switch VLAN with ELS Support (CLI Procedure)
- Example: Configuring MLD Snooping on EX Series Switches
- Example: Configuring MLD Snooping on SRX Series Devices
- Configuring MLD Snooping Tracing Operations on EX Series Switches (CLI Procedure)
- Configuring MLD Snooping Tracing Operations on EX Series Switch VLANs (CLI Procedure)
- Example: Configuring MLD Snooping on EX Series Switches
- Example: Configuring MLD Snooping on Switches with ELS Support
- Verifying MLD Snooping on EX Series Switches (CLI Procedure)
- Verifying MLD Snooping on Switches
- play_arrow Configuring Multicast VLAN Registration
-
- play_arrow Configuring Protocol Independent Multicast
- play_arrow Understanding PIM
- play_arrow Configuring PIM Basics
- Configuring Different PIM Modes
- Configuring Multiple Instances of PIM
- Changing the PIM Version
- Optimizing the Number of Multicast Flows on QFabric Systems
- Modifying the PIM Hello Interval
- Preserving Multicast Performance by Disabling Response to the ping Utility
- Configuring PIM Trace Options
- Configuring BFD for PIM
- Configuring BFD Authentication for PIM
- play_arrow Routing Content to Densely Clustered Receivers with PIM Dense Mode
- play_arrow Routing Content to Larger, Sparser Groups with PIM Sparse Mode
- Understanding PIM Sparse Mode
- Examples: Configuring PIM Sparse Mode
- Configuring Static RP
- Example: Configuring Anycast RP
- Configuring PIM Bootstrap Router
- Understanding PIM Auto-RP
- Configuring All PIM Anycast Non-RP Routers
- Configuring a PIM Anycast RP Router with MSDP
- Configuring Embedded RP
- Configuring PIM Filtering
- Examples: Configuring PIM RPT and SPT Cutover
- Disabling PIM
- play_arrow Configuring Designated Routers
- play_arrow Receiving Content Directly from the Source with SSM
- Understanding PIM Source-Specific Mode
- Example: Configuring Source-Specific Multicast
- Example: Configuring PIM SSM on a Network
- Example: Configuring an SSM-Only Domain
- Example: Configuring SSM Mapping
- Example: Configuring Source-Specific Multicast Groups with Any-Source Override
- Example: Configuring SSM Maps for Different Groups to Different Sources
- play_arrow Minimizing Routing State Information with Bidirectional PIM
- play_arrow Rapidly Detecting Communication Failures with PIM and the BFD Protocol
- play_arrow Configuring PIM Options
- play_arrow Verifying PIM Configurations
-
- play_arrow Configuring Multicast Routing Protocols
- play_arrow Connecting Routing Domains Using MSDP
- play_arrow Handling Session Announcements with SAP and SDP
- play_arrow Facilitating Multicast Delivery Across Unicast-Only Networks with AMT
- play_arrow Routing Content to Densely Clustered Receivers with DVMRP
-
- play_arrow Configuring Multicast VPNs
- play_arrow Configuring Draft-Rosen Multicast VPNs
- Draft-Rosen Multicast VPNs Overview
- Example: Configuring Any-Source Draft-Rosen 6 Multicast VPNs
- Example: Configuring a Specific Tunnel for IPv4 Multicast VPN Traffic (Using Draft-Rosen MVPNs)
- Example: Configuring Source-Specific Draft-Rosen 7 Multicast VPNs
- Understanding Data MDTs
- Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode
- Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode
- Examples: Configuring Data MDTs
- play_arrow Configuring Next-Generation Multicast VPNs
- Understanding Next-Generation MVPN Network Topology
- Understanding Next-Generation MVPN Concepts and Terminology
- Understanding Next-Generation MVPN Control Plane
- Next-Generation MVPN Data Plane Overview
- Enabling Next-Generation MVPN Services
- Generating Next-Generation MVPN VRF Import and Export Policies Overview
- Multiprotocol BGP MVPNs Overview
- Configuring Multiprotocol BGP Multicast VPNs
- BGP-MVPN Inter-AS Option B Overview
- ACX Support for BGP MVPN
- Example: Configuring MBGP MVPN Extranets
- Understanding Redundant Virtual Tunnel Interfaces in MBGP MVPNs
- Example: Configuring Redundant Virtual Tunnel Interfaces in MBGP MVPNs
- Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider Tunnels
- Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider Tunnels
- Example: Configuring Sender-Based RPF in a BGP MVPN with MLDP Point-to-Multipoint Provider Tunnels
- Configuring MBGP MVPN Wildcards
- Distributing C-Multicast Routes Overview
- Exchanging C-Multicast Routes
- Generating Source AS and Route Target Import Communities Overview
- Originating Type 1 Intra-AS Autodiscovery Routes Overview
- Signaling Provider Tunnels and Data Plane Setup
- Anti-spoofing support for MPLS labels in BGP/MPLS IP VPNs (Inter-AS Option B)
- BGP-MVPN SD-WAN Overlay
- play_arrow Configuring PIM Join Load Balancing
- Use Case for PIM Join Load Balancing
- Configuring PIM Join Load Balancing
- PIM Join Load Balancing on Multipath MVPN Routes Overview
- Example: Configuring PIM Join Load Balancing on Draft-Rosen Multicast VPN
- Example: Configuring PIM Join Load Balancing on Next-Generation Multicast VPN
- Example: Configuring PIM Make-Before-Break Join Load Balancing
- Example: Configuring PIM State Limits
-
- play_arrow Troubleshooting
- play_arrow Knowledge Base
-
- play_arrow Configuration Statements and Operational Commands
IS-IS extension for BIER
The IS-IS extension for BIER is defined via RFC 8401.
Junos OS Evolved supports the advertisement of BIER information of one or more BIER sub-domains using IS-IS as the IGP underlay. Key BIER information like BFR-IDs and BFR-Prefixes in each sub-domain are flooded through the IS-IS domain to generate the BIER forwarding table.
Advertising BIER Info sub-TLV in IS-IS
The BIER info sub-TLV carries BIER sub-domain information. This sub-TLV advertises a single <MT,SD> (multi-topology/sub-domain) combination followed by optional sub-sub-TLVs as described in the next section. Junos OS Evolved supports IPv4-unicast and IPv6-unicast IS-IS topologies.
Multi-topology scenarios are not supported.
The figure below illustrates the BIER info sub-TLV.
IS-IS carries BIER info sub-TLV within IS-IS TLVs 135, 236 or 237.
IS-IS advertises BIER info sub-TLV in TLV 135 for BIER sub-domains with BFER-Prefix (IPv4) and IS-IS default topology.
IS-IS advertises BIER info sub-TLV in TLV 236 for BIER sub-domains with BFER-Prefix (IPv6) and IS-IS default topology.
IS-IS advertises BIER info sub-TLV in TLV 237 for BIER sub-domains with BFER-Prefix (IPv6) and IS-IS IPv6 unicast topology.
Advertising BIER MPLS Encapsulation sub-sub-TLV in IS-IS
This sub-sub-TLV carries the information for the BIER MPLS encapsulation including the label range for a specific BitStringlength for a certain <MT,SD> tuple. The sub-sub-TLV is advertised within the BIER info sub-TLV and may appear multiple times within a single BIER info sub-TLV.
The figure below illustrates the BIER info sub-sub-TLV.
The Max SI value is the set-identifier and is configured under
number-sets. For example in the snippet below:
sub-domain 32 {
encapsulation mpls bitmask-length 256 number-sets 4
}
The number-sets is set to 4. The range is 1-16. Based on this value BIER
assigns four contiguous labels from the dynamic pool, for example, labels L1 to L4. L1
belongs to SI=0, L2 to S1=1 and so on. With the above configuration example, IS-IS sub-TLV
advertises with Max SI=4 and label as L1.
Advertising BIER-Prefix in IS-IS
BIER sub-domain related configuration parameters are set under protocols
bier.
To include the BIER sub-domain in the IS-IS sub-TLVs, configure them under
protocols isis:
protocols isis {
bier-sub-domain 32
}A BFR’s BFR-Prefix is an IP address (IPv4 or IPv6) which is generally the loopback IP address of the BIER router. Typically, IS-IS advertises the BFR-Prefix in one of the TLVs 135/236/237 depending on the IS-IS topology.
When bier-sub-domain is configured under protocols isis,
the information of the BIER sub-domain (BIER info sub-TLV + BIER MPLS Encapsulation
sub-sub-TLV) is advertised inside the IS-IS prefix TLV to extend BIER functionality.
Multiple sub-domains can advertise with the same loopback address.
IS-IS TLVs have a maximum length of 255 bytes. When the maximum number of sub-domains that can be supported is exceeded, another loopback IP address must be configured.
Installing BFR-Prefix to the BIER Routing Table
IS-IS routers advertise the BFR-Prefix and sub-domain information using the sub-TLV. IS-IS floods this BIER information throughout the IS-IS domain. This allows the IS-IS nodes build the prefix and associated next-hop information to install the BIER route to the routing information base (RIB) table. On the receiver side, IS-IS nodes parse this BIER sub-domain information associated with the BFR-Prefix and derive the route and next-hop information. IS-IS then installs this BIER route in the BIER routing table (BIRT).
For this implementation, it is assumed that all IS-IS nodes are BIER enabled.
BIER protocol and IS-IS interactions
IS-IS downloads the BIER route to the BIER routing table (BIRT). BIRT routes do not go directly to the forwarding table. These routes are consumed by the BIER module by listening to the route’s updates from the BIRT table. The module then derives the new route and next-hop information from the BIRT route and eventually downloads it to the PFE for data forwarding.
The BIFT route table name is in the format: bier-<subdomain-id>-<set-id>.bier.0.
