Page History

...

The following paragraphs we will breakdown each of the components and provide a couple graphics to help visualize these relationships.

Multicast Route Table (MRT)

The Multicast Route Table (MRT) which may also be referred to at times as the Multicast Routing Information Base (MRIB), is essentially the repository for Multicast Routes maintained by ONOS.

...

• Active multicast data via ONOS Packet Service
• Interactive operator inputs via ONOS CLI Service
• External applications via the ONOS REST Service
• Future modules include
  • PIM-SSM Emulation
  • IGMPv3 Proxy

Multicast Route Table implementation

The multicast route table is java class defined in the following file exposing the corresponding API:

• McastRouteTable.java
  • Private members:
    • mribv4 - Set of IPv4 routes
    • mribv6 - set
  • McastRouteTable.getInstance() - Single instance of the MRT
  • getMrib4() / getMrib6() - retrieve the actual IPv4 & IPv6 tables
  • storeGroup(McastRouteGroup group) - store a multicast group
  • removeGroup(McastRouteGroup) - remove the associated group
  • addRoute(String source, String group) - store either a (*, G) or (S, G)
  • addRoute(IpPrefix sourcePrefix, IpPrefix groupPrefix) - same as above
  • removeRoute(String source, String group) - remove corresponding route
  • removeRoute(IpPrefix sourcePrefix, IpPrefix groupPrefix) - same as above
  • findMcastGroup(IpPrefix group) - find a specific Mcast Group
  • findMcastSource(IpPrefix source, IpPrefix group) - find a specific (s, g)
  • findBestMatch(IpPrefix source, IpPrefix group) - find the best match
  • printMcastRouteTable() - used by the cli 'mcast-show'
  • toString() - summary string.

Multicast Routes

The multicast routes are divided into two categories: a group route (*, G), also known as Any Source Multicast (ASM). There are also source routes (S, G) also known as Source Specific Multicast (SSM).

...

• McastRoute Interface that defines the public API of all McastRoutes

  • getGaddr() - get the IP multicast address
  • getSaddr() - get the IP unicast address. 0/0 for (*, G)
  • addIngressPoint(ConnectPoint ingress)
  • getIngressPoint()
  • addEgressPoint(ConnectPoint egressPoint) add individual egress points
  • getEgressPoints() - get the set of egress points
  • setIntents(SinglePointToMultipointIntent p2mp, MultipointToSinglePointIntent mp2p) - set the P2MP & MP2P intents
  • getP2MPIntentKey() - gets P2MP the intent
  • getMP2PIntentKey() - get the P2MP intent
  • toString()

• McastRouteBase implements McastRouteBase

  • Implement all of the functionality common to both (*, G) and (S, G) routes.

• McastRouteGroup extends McastRouteBase

  • Implements functionality unique to (*, G) routes
  • private members
    • sources: container for all (S, G) entries that share the same multicast group address G.
  • findSource(IpPrefix saddr) - find a specific source for this group (S, G)
  • getSources() - get all sources that belong to this specific group
  • addSource(McastRouteSource src) - add a new source to this group
  • removeSource(IpPrefix sourcePrefix) - remove a specific source from this group
  • removeSources() - remove all sources from this group.

• McastRouteSource extends McastRouteBase

  • Implements functionality unique to (S, G) entries
  • N/A

How the MRT Stores Multicast routes

The MRT maintains a set of McastRouteGroup groups corresponding to each IPv4 or IPv6 group MFWD is maintaining state for.

The McastRouteGroup serves two purposes, first to maintain forwarding state for (*, G) ASM as well as a parent container for all McastRouteSource (S, G) routes that share the same multicast group address G.

ConnectPoints

ConnectPoints are an ONOS construct consisting of a switch name and port number. For the purpose of multicast we use the ConnectPoints to determine where multicast data enters (ingress) the SDN network, as well as the set of ConnectPoints the multicast data leaves (egress) the network.  Egress ConnectPoints will have a receiver attached to that connect point or forward multicast traffic into a network outside of the given SDN segment.

...

Note: in the case of (*, G) the ingress ConnectPoint maybe NULL due to the fact that, by definition, the source of the multicast group is not known.  How Any Source Multicast is handled is dependent upon the use case and the specific implementation.  Currently we don't have any requirements to provide ASM support, however MFWD was designed as to not preclude ASM support.  

Both McastRouteGroup and McastRouteSource leverage the base class implementation of ingress and egress management functions, both classes provide additional functionality required for their respective needs.

Multicast Intent Manager

The McastIntentManager is responsible for registering with the ONOS IntentService, formulating and changing intents based on specific McastRoute State. The intent manager is also responsible for withdrawing intents and cleaning up after MFWD when the application is deactivated.

Currently the The McastIntentManager will register a SinglePointToMultiPointIntent and a MultipointToSinglePointIntent for each multicast route it installs. The former which is used to forward multicast state, the latter is used to establish a return path from all egress to the ingress ConnectPoint.

...

.

The Intent Manager McastIntentManager relies on the following ONOS services:

...

• McastIntentManager class
  • activate() / deactivate() Karaf / felix components
  • McastIntentManager.getInstance() - get the singleton instance
  • setIntent(McastRouteBase mroute) - create and set intents for this route
  • withdrawIntents(McastRouteBase mroute) - withdraw intents
  • withdrawAllIntents() - clean up all intents when MFWD has been deactivated

Multicast Forwarding

The MulticastForwarding module is responsible for handling live multicast data.  For incoming multicast packets that do not match an existing multicast forwarding entry, the module will create a multicast forwarding entry with the ingress ConnectPoint with no egress ConnectPoints.  The state will be ready when and if receivers indicate interest.

When live multicast data arrives for which an entry does exist, if that entry also has one or more egress ConnectPoints, the entry is completed with the ingress ConnectPoint and handed to the MulticastIntentManager, which subsequently creates a SinglePointToMultiPointIntent that then is used to install the corresponding flow paths through the relevant switches.

flow in the OpenFlow switch and hence are passed upstream to the controller.

...