Design & Build

Best Practice: Configure Brocade NetIron Routers with PIM Anycast RP

by Brook.Reams_1 on ‎01-16-2013 02:12 PM - edited on ‎04-09-2014 11:50 AM by Community Manager (46 Views)

Synopsis: Best practices for configuring Multicast PIM with Anycast RP for fast convergence with Brocade NetIron Family of routers.

 

Contents

Introduction

IP multicast is deployed as an integral component in mission-critical networked applications throughout the world. These applications must be robust, hardened, and scalable to deliver the reliability that users demand.

Anycast Rendezvous Point (RP) is a mechanism that ISP or Enterprise backbones use to get fast convergence when a RP router fails since it provides load sharing and redundancy in Protocol Independent Multicast—Sparse Mode (PIM-SM) networks. Anycast RP allows two or more RPs to share the load for source registration and the ability to act as hot backup routers for each other. To allow receivers and sources to Rendezvous to the closest RP, the packets from a source need to get to all RPs to find joined receivers.

Prior to Anycast RP using the PIM mechanism, MSDP (Multicast Source Discovery Protocol) was deployed to provide a method receivers can use to find sources.  Running MSDP adds more complexity with more protocol machinery from an operations perspective.  To retain the Anycast RP benefits with less protocol machinery and eliminate the use of MSDP, PIM Anycast RP extends the Register mechanism in PIM so Anycast RP functionality has no dependency on MSDP.

 

Related Documents

The following documents are valuable resources for the designer. In addition, any Brocade release notes that have been published for NOS, FOS and the MLX NetIron should be reviewed.

 

References

 

Document History

Date                  Version        Description

2013-01-16          1.0               Initial Version

 

About Brocade

Brocade® (NASDAQ: BRCD) networking solutions help the world’s leading organizations transition smoothly to a world where applications and information reside anywhere. This vision is designed to deliver key business benefits such as unmatched simplicity, non-stop networking, application optimization, and investment protection.

Innovative Ethernet and storage networking solutions for data center, campus, and service provider networks help reduce complexity and cost while enabling virtualization and cloud computing to increase business agility.

To help ensure a complete solution, Brocade partners with world-class IT companies and provides comprehensive education, support, and professional services offerings. (www.brocade.com)

 

Key Contributors

The content in this guide was provided by the following key contributors.

 

Test Architect:Chris Yoon

 

PIM Anycast RP Mechanism

  • A shared unicast IP address is chosen to use as the RP address. This shared address is statistically configured, or distributed as RP address using a dynamic protocol, to all PIM routers throughout the domain.
  • As set of routers in the domain is chosen to act as RPs for this shared RP address, and these routers are called the Anycast RP set.
  • Each router in the Anycast RP set is configured with a loopback interface using the shared RP address.
  • Each router in the Anycast RP set also needs a separate IP address, to be used for communication (that is, Anycast RP peering) between the RPs.
  • The RP address, or a prefix that covers the RP address, is injected into the unicast routing system inside of the domain.
  • Each router in the Anycast RP set is configured with the addresses of all other routers in Anycast RP set. This must be consistently configured in all RPs in the set.

PIM Register Mechanism of PIM Anycast RP

When the source is activated in a PIM Anycast RP domain, the PIM First Hop router will register the source to the closet PIM RP. The PIM RP router will decapsulate the packet and create the (S,G) state. Since there are peers in the Anycast RP set, the PIM RP will re-encapsulate the packet as a PIM register packet with the local peering address as the source address of the encapsulation.

The PIM RP router uses unicast to send the PIM register packet to all Anycast RP peers. Once an Anycast RP peer receives the packet, it is de-capsulated and the (S,G) state is created. The PIM register packets ensures source state distribution to all RPs in a multicast domain.

 

Figure-1a.jpg

Figure 1a. PIM Register machanism with two PIM Anycast RP

 

Figure-1b.jpg

Figure 1b.   PIM register mechanism with two PIM Anycast RP

 

image003.png

Figure 2: PIM register mechanism with three PIM Anycast RPs

 

Jumbo Frame PIM Register Packet

On CER/CES with NetIron 5.2 code running, with default MTU frame size (that is, 1548 bytes) configured, fragmentation for jumbo frame size’ PIM register packet was tested with two Anycast RPs set configured. 1548 bytes’ data multicast packet was sent by Tester, PIM register packet (that is, 1548 bytes + 28 bytes) generated by FH (First Hop) router was fragmented and forwarded to a close router in Anycast RP set.  The router de-capsulated the fragmented PIM register packets, encapsulated as data multicast packet, and forward it to the shared tree. Then it re-encapsulated the packets as PIM register packet (that is, 1548 bytes +28 bytes) with its own address as source address, and then sends it to the other router in Anycast RP set.

 

With max frame size 9216 bytes configured, the same test was done for 9216 bytes’ data multicast packet.

 

Configuration of PIM Anycast RP

 

Below is a PIM Anycast RP configuration with two RPs, RP1 and RP2:

 

image004.png

Figure 3. PIM Anycast RP configuration

 

The best practice for configuring PIM Anycast RP is below:

  • Anycast RP address must not be the IGP router-id. Hence, do not use loopback 1 since the loopback 1 could be used as a router-id.
  • Use loopbacks for Anycast RP and peering address assignments.

 

PIM Anycast RP Set’s Load Share

If there are scalable multicast groups, you can configure separate Anycast RP sets for different multicast groups. This provides load sharing for the Anycast RP sets per multicast group. In the following configuration, RP1 & RP2 are an Anycast RP set for the multicast group 225.0.0.0/24, and RP3 & RP4 are an Anycast RP set for the multicast group 225.1.1.0/24.

 

image005.png

Figure 4.  PIM Anycast RP Set Load Sharing

 

IPV4/IPV6, Supported Platform, and Supported RFCs

 

PIM Anycast RP is supported in both IPv4 and IPv6. The following Brocade platforms support PIM Anycast RP:

  • NetIron XMR series
  • NetIron MLX series
  • NetIron CES 2000 Series ME_PREM package
  • NetIron CES 2000 Series L3_PREM package
  • NetIron CER 2000 Series Base package
  • NetIron CER 2000 Series Advanced Service package

This feature supports RFC 4610: Anycast-RP Using Protocol Independent Multicast (PIM).

Comments
by wherr on ‎03-20-2013 11:54 AM

The Reference Link to MLX Series Configuration Guide R5.3.00a is broken.

http://www.brocade.com/downloads/documents/product_manuals/B_NetIron/NetIronUnfied_05300a_ConfigGuid...

by Brook.Reams_1 on ‎03-20-2013 01:25 PM

Wherr,

Thanks for letting us know. All better now.

Best

Brook

Contributors