Welcome!

Related Topics: SDN Journal, Java IoT, Linux Containers, Containers Expo Blog, @CloudExpo, Cloud Security

SDN Journal: Blog Post

What SDN Can Do for Multicast Topologies

IP Multicast is one of those technologies that most everyone loves to hate

IP Multicast is one of those technologies that most everyone loves to hate. It’s almost the perfect example of how complicated we have made networking. Getting IP Multicast to run depends on several protocols that are all somewhat intertwined or dependent on each, their relationship sometimes explicit, sometimes implicit.

Even trying to describe the basic operation is complicated.

When an application or service provides information using IP multicast, it simply starts sending it onto a specific multicast group. The multicast router for the subnet of the sender sees the incoming multicast packet and will initially have no forwarding information for that stream in its forwarding hardware. The packet is passed onto the CPU of that router, which will encapsulate this packet and send it towards a special multicast router designated the Rendez-vous Point (RP). When the RP has installed the multicast routes for this group, it will tell the multicast router on the sender’s segment to stop sending. When it does, this router installs its own multicast routes for the source tree (the tree specific to this sender) and the shared tree (the one towards the RP) without any outgoing interfaces, and the traffic is dropped at this first router. But, the network (well at least the part between the sender and the RP) is now aware of this multicast stream. And who is sending.

Now when we want to join this IP Multicast group, the first action is send an IGMP join out on the subnet you are attached to. The IP Multicast router that serves this subnet sees the join and determines where RP can be found. It takes the client join, and sends it towards the RP, using the unicast routing table as its guide. Every multicast router along the way registers that there is a listener on the interface this join came in on and passes it along towards the IP. All along this path, the unicast routing entry for the RP is used to create the tree towards the listener.

Once received by the RP, the shared tree and the source tree towards the sender have been joined. We have an end to end path between sender and receiver, with the RP in the middle of it all. All that is left is to send a join from the RP towards the router on the sender’s subnet to essentially tell it to start passing the actual multicast along the path towards the RP (the source tree), where the RP will then push it out onto the shared tree towards the destination. Voila, it’s as simple as that.

But wait, we are not done. Once the packets start to flow from source to destination, the multicast router closest to the destination will send another join message for this group, but this time towards the sender. It is only now that it can do this because those first few data packets actually indicate who the sender is. That join is passed router to router to router towards the router on the sender’s subnet, and once arrived, that router will now also start sending the multicast data along that path towards the receiver. The receiving subnet router sees that stream appearing and will now send a prune message onto the shared tree towards the RP, indicating it no longer needs the multicast stream through the RP.

If you are not familiar with IP Multicast and after reading the above are not confused, congratulations, your brain is very well wired for complex networking.

If you step away from how IGMP and PIM implement this today as above, the most fundamental of IP multicast topologies is that you need to build a forwarding tree that is rooted in the source, with the destinations as its leaves. At each intermediate node in the tree, the packets are replicated to its branches, therefore creating the least amount of duplication. And by using a tree, it is loop free, packets won’t swirl around the network bringing it to its knees.

The challenging part though is that the tree is based on the unicast forwarding topology. From a leaf on this tree towards the sender, each step is identical to how a unicast IP packet would be forwarded. The forwarding topologies are connected and dependent on each other. IP Multicast is built on top of a unicast routed infrastructure, and unicast routing changes can have dramatic impacts to the multicast forwarding topologies.

I mentioned here before that I once spent a wonderful 2 weeks in Delhi working on a network where surveillance cameras created an aggregate 8Gbit/sec worth of multicast data, with a requirement that any unicast change would have limited impact to these streams. Believe me, it is extremely hard to engineer and tune, and we had the luxury of hijacking a really large network night after night to simulate failures.

SDN based architectures have the opportunity to change all this. Multicast forwarding was designed the way it was designed to work on arbitrary network topologies, with random senders and receivers coming and going. It builds trees on the fly and on demand. For many networks, topologies are not arbitrary, and those applications that consume/produce lots of multicast do not have randomly placed senders and receivers that come and go as they please.  Many of them are well known or placed in fairly static and fixed topologies.

A controller with a global view of the network can create multicast topologies ahead of time. It knows all possible replication points and can create distribution trees among them. It can create different distribution trees for different multicast groups. It can create them independent of the unicast forwarding. It can calculate backup topologies in case portions of the tree fail. And it can do all of that guaranteeing there are no loops and optimal replication. When applications indicate their participation in specific multicast streams as senders or listeners to this controller, it can optimize very specifically based on those participants. The possibilities are endless.

We had a customer visit us yesterday that has very significant multicast needs and we walked him through some of these possibilities. He left with a huge smile on his face. And that smile on his face was not because he really liked what we built (even though he did), but it was because we showed him that if you remove legacy network thinking and constraints, networking can yet again be extremely exciting and creates solutions that he did not think were possible, in a fairly simple and straightforward way. And that, in turn, is truly exciting to us.

The post What SDN can do for Multicast Topologies appeared first on Plexxi.

Read the original blog entry...

More Stories By Marten Terpstra

Marten Terpstra is a Product Management Director at Plexxi Inc. Marten has extensive knowledge of the architecture, design, deployment and management of enterprise and carrier networks.

Latest Stories
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addres...
You think you know what’s in your data. But do you? Most organizations are now aware of the business intelligence represented by their data. Data science stands to take this to a level you never thought of – literally. The techniques of data science, when used with the capabilities of Big Data technologies, can make connections you had not yet imagined, helping you discover new insights and ask new questions of your data. In his session at @ThingsExpo, Sarbjit Sarkaria, data science team lead ...
Extracting business value from Internet of Things (IoT) data doesn’t happen overnight. There are several requirements that must be satisfied, including IoT device enablement, data analysis, real-time detection of complex events and automated orchestration of actions. Unfortunately, too many companies fall short in achieving their business goals by implementing incomplete solutions or not focusing on tangible use cases. In his general session at @ThingsExpo, Dave McCarthy, Director of Products...
Ixia (Nasdaq: XXIA) has announced that NoviFlow Inc.has deployed IxNetwork® to validate the company’s designs and accelerate the delivery of its proven, reliable products. Based in Montréal, NoviFlow Inc. supports network carriers, hyperscale data center operators, and enterprises seeking greater network control and flexibility, network scalability, and the capacity to handle extremely large numbers of flows, while maintaining maximum network performance. To meet these requirements, NoviFlow in...
"delaPlex is a software development company. We do team-based outsourcing development," explained Mark Rivers, COO and Co-founder of delaPlex Software, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
WebRTC is bringing significant change to the communications landscape that will bridge the worlds of web and telephony, making the Internet the new standard for communications. Cloud9 took the road less traveled and used WebRTC to create a downloadable enterprise-grade communications platform that is changing the communication dynamic in the financial sector. In his session at @ThingsExpo, Leo Papadopoulos, CTO of Cloud9, discussed the importance of WebRTC and how it enables companies to focus...
The competitive landscape of the global cloud computing market in the healthcare industry is crowded due to the presence of a large number of players. The large number of participants has led to the fragmented nature of the market. Some of the major players operating in the global cloud computing market in the healthcare industry are Cisco Systems Inc., Carestream Health Inc., Carecloud Corp., AGFA Healthcare, IBM Corp., Cleardata Networks, Merge Healthcare Inc., Microsoft Corp., Intel Corp., an...
Is your aging software platform suffering from technical debt while the market changes and demands new solutions at a faster clip? It’s a bold move, but you might consider walking away from your core platform and starting fresh. ReadyTalk did exactly that. In his General Session at 19th Cloud Expo, Michael Chambliss, Head of Engineering at ReadyTalk, will discuss why and how ReadyTalk diverted from healthy revenue and over a decade of audio conferencing product development to start an innovati...
Continuous testing helps bridge the gap between developing quickly and maintaining high quality products. But to implement continuous testing, CTOs must take a strategic approach to building a testing infrastructure and toolset that empowers their team to move fast. Download our guide to laying the groundwork for a scalable continuous testing strategy.
Early adopters of IoT viewed it mainly as a different term for machine-to-machine connectivity or M2M. This is understandable since a prerequisite for any IoT solution is the ability to collect and aggregate device data, which is most often presented in a dashboard. The problem is that viewing data in a dashboard requires a human to interpret the results and take manual action, which doesn’t scale to the needs of IoT.
SYS-CON Events announced today that 910Telecom will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Housed in the classic Denver Gas & Electric Building, 910 15th St., 910Telecom is a carrier-neutral telecom hotel located in the heart of Denver. Adjacent to CenturyLink, AT&T, and Denver Main, 910Telecom offers connectivity to all major carriers, Internet service providers, Internet backbones and ...
“Being the one true cloud-agnostic and storage-agnostic software solution, more and more customers are coming to Commvault and saying ' What do you recommend? What's your best practice for implementing cloud?” explained Randy De Meno, Chief Technologist at Commvault, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
CenturyLink has announced that application server solutions from GENBAND are now available as part of CenturyLink’s Networx contracts. The General Services Administration (GSA)’s Networx program includes the largest telecommunications contract vehicles ever awarded by the federal government. CenturyLink recently secured an extension through spring 2020 of its offerings available to federal government agencies via GSA’s Networx Universal and Enterprise contracts. GENBAND’s EXPERiUS™ Application...
Security, data privacy, reliability and regulatory compliance are critical factors when evaluating whether to move business applications from in-house client hosted environments to a cloud platform. In her session at 18th Cloud Expo, Vandana Viswanathan, Associate Director at Cognizant, In this session, will provide an orientation to the five stages required to implement a cloud hosted solution validation strategy.
As companies gain momentum, the need to maintain high quality products can outstrip their development team’s bandwidth for QA. Building out a large QA team (whether in-house or outsourced) can slow down development and significantly increases costs. This eBook takes QA profiles from 5 companies who successfully scaled up production without building a large QA team and includes: What to consider when choosing CI/CD tools How culture and communication can make or break implementation