Lists and compares how discovered multicast flows and simulated multicast flows are handled within Cisco Crosswork Planning, including creation, pathing, and applicable tables.
How you work with multicast flows within Cisco Crosswork Planning differs depending on whether Cisco Crosswork Planning discovered the multicast flow or you are simulating it (Table 1).
| Discovered multicast flow |
Simulated multicast flow |
|
|---|---|---|
| Creation |
Cisco Crosswork Planning discovers multicast flows—(S,G) pairs)—and multicast traffic is derived from the Multicast Flow Traffic table. |
First, manually create the multicast flow, defining both the source (S) and the destinations (G). Next, create a demand that links the source to these multicast destinations, allowing the routing to be simulated through the network. |
| Hops |
Each discovered multicast flow includes multicast flow hops, which are node-interface combinations through which the multicast path flows. |
When you create a demand, it determines the path to take. |
| External hops |
Cisco Crosswork Planning discovers multicast flow hops on interfaces that are external to the plan file. These are interfaces from a plan node to an external node, or from an external node to a plan node. |
When you create a demand, it determines the path to take, but multicast external flow hops are not identified. |
| Destinations |
Cisco Crosswork Planning does not identify a list of multicast destinations for each flow. |
Specify destinations (nodes, interfaces, external ASes, or external endpoints) when you create multicast flows. When creating multicast demands, specify these as multicast destinations. |
| Applicable tables |
|
|