IP Multicast Technology and VXLAN - EVPN The Evolution of Overlay Networking

  • เป็นการส่ง Packet จากต้นทางหนึ่งไปยังกลุ่มปลายทางพิเศษ โดยที่กลุ่มปลายทางพิเศษนั้นเป็นการแทนถึงกลุ่มของ Host ใดๆ ที่ต้องการ

    PIM (Protocol Independent Modules):
    เป็น Routing Protocol ที่ใช้ในการ Forward Multicast Traffic และทำการ Maintain Topology ของ Multicast Tree

    IGMP Snooping หากว่า Traffic ที่เป็น Multicast นั้น จำเป็นที่จะต้องเดินทางผ่าน Switch Layer 2 ซึ่งไม่มีความสามารถในการพิจารณา Packet แล้วนั้น มันจำเป็นที่จะต้องใช้ IGMP Snooping และ CGMP (Cisco Proprietary) ในการที่จะ Relay ข้อมูลเกี่ยวกับ Frame และ MAC Address ให้กับ Switch Layer 2 เนื่องจากโดยธรรมชาติแล้ว Switch Layer 2 จะทำการ Flood Packet Multicast ออกไปยังทุกๆ Port ของ VLAN โดยอัตโนมัติ โดยที่ไม่มีการพิจารณา Packet ใดๆ ดังนั้น มันจึงต้องมี CGMP ที่จะทำการ Relay Packet ของ IGMP Snooping ไปยัง Switch Layer 2 ให้ทำการ ADD ข้อมูลลงไปใน CAM Table ของตนเพื่อรับรู้ว่า Packet นั้นๆ เป็นของ Multicast Network ใด
    Cr: MUT

    L2 Multicast:
    • Xconnect by Interface Vlan or Sub Int with L2 ME-3400 Series Not Work
    • VPLS with Interwork Not Work
    • Pass PE is Work Only Xconnect on Physical Int and PC/Laptop Connected with PE if Used SW L2 ME-3400 Series Not Work
    • SW L2 pure configured igmp snooping is work
      [li]xconnect used sub int with L2 7600 series is work[/li][/list]

      Multicast “MPLS” VPNs/L3 Multicast

      VLC Setup for Multicast Test


      Multicast Tutorial


      Test mVPN Configuration Template
      Core Multicast
      • SSM mode
      • Default MDT :
      VRF Multicast
      • Static RP
      • RP address
      PE Configuration
      ip multicast-routing
      ip multicast multipath
      interface lo0
      ip address
      ip pim sparse-mode
      !enable pim on all core facing interfaces
      interface x/y
      description Core-facing-Interface
      ip pim sparse-mode
      !enable SSM
      ip pim ssm range 39
      access-list 39 permit
      !Configure multicast VRF ทำแค่บนตัวที่ต่อกับตัว Decoder
      !Default MDT Configure
      ip vrf IPTV-M
      rd aaa:bbb
      route-target export aaa:bbb
      route-target import aaa:bbb
      mdt default -> สร้าง GRE Tunnel Multicast ต้องมี เป็น mandatory
      ip multicast-routing vrf IPTV-M
      interface x/y.z
      description test IPTV
      encapsulation dot1Q z
      ip vrf forwarding IPTV-M
      ip pim sparse-mode
      ip address
      router bgp aaa
      address-family ipv4 mdt -> ไม่ใส่ pim neighbor ไม่ขึ้น
        neighbor activate
        neighbor VPN-RR send-community both
      ip pim vrf IPTV-M rp-address

      P Configuration
      ! Core-CRS
      multicast-routing address-family ipv4
      interface all enable
      ssm range 39
      ipv4 access-list 39
      10 permit 239 .0.0.0

      RR Configuration
      router bgp aaa
      address-family ipv4 mdt
        neighbor VPN-RR-CLIENT activate
        neighbor VPN-RR-CLIENT send community both
        neighbor VPN-RR-CLIENT route-reflector-client
        neighbor peer-group VPN-RR-CLIENT

      [center]Credit: P'Suwanna@Cisco[/center]
      L2 Configuration
      ip igmp snooping

      Verify MVPN on PE
      • [li]show ip pim vrf IPTV-M neighbor -> จะเห็นทุก PE ที่ configured multicast[/li]
        [li]ip igmp join-group -> บน vrf int ทดสอบเป็น Client โดย router[/li]
        [li]ping ip vrf IPTV-M[/li]
        [li]show ip mroute[/li]
        [li]show ip pim interface[/li]
        [li]show ip pim neighbors[/li]
        [li]show ip pim rp[/li]
        [li]show ip rpf[/li]

      Testing Source Specific Multicast

      Implementing Multicast Routing on Cisco IOS XR Software

      Default MDT and Data MDT Concept

      On  ME-3600X must change sdm to application
      #sdm prefer applications (on EXEC mode)
      show ip mfib count : you can look at mfib count to check the number of packet received and forwarded and the number of drops to check if we can we are forwarding the number of packets received and they are not being dropped this would mean that the multicast stream is a healthy stream. If result is NA you can see by:
      show ip mrib route verbose
      (, RPF nbr: Flags: K DDE
        Tunnel1 Flags: A      Next-hop:  // Flags are same for both mfib and mrib outputs is healthy multicast stream.
        Vlan1914 Flags: F NS
      show ip mfib verbose
      (, Flags: K HW DDE
        SW Forwarding: 0/0/0/0, Other: 0/0/0
        HW Forwarding:  446523184/1891/1360/20107, Other: NA/NA/NA
        Tunnel1, MDT/ Flags: RA A MA
        Vlan1914 Flags: RF F NS

      ip igmp static-group configures a static connected member for a specific group. Traffic to that group will be fast-switched to the interface where this command is configured rather than process switched. This command is usually used to forward mcast traffic down an interface.

      ip igmp join-group causes the router to send an IGMP membership report on the interface where it is configured. The mcast packets will therefore be received and process switched by the router hence more CPU intensive. This command is usually used for test purposes only.

      high CPU 7600 because interface vrf multicast have rp-address is incorrect.

      me360x-universalk9-mz.151-2.EY4.bin can't support multicast vpn. I used another version, The ip pim vrf neighbor is up but when I downgraded to this version not up.

      Multicast Uses:
    • Any applications with multiple receivers
    • One-to-many
    • Many-to-many
    Live video distributionCollaborative groupwarePeriodic data delivery - "push" technology
    • Stock quotes, sports scores, magazines, newspapers, adverts
    Inter-Data Center L2 Underlay
    • VXLAN, etc. for BUM
    Server/Website replicationReducing network/resource overhead
    • More than multiple point-to-point flows
    Resource discoveryDistributed interactive simulation (DIS)
    • War games
    • Virtual reality

    Cable, Satellite, IPTV & OTT Streaming: What the difference?

  • 2 Comments sorted by

  • Multicast Considerations:

    Multicast Is UDP-Based:
    • Best effort delivery: Drops are to be expected; multicast applications should not expect reliable delivery of data and should be designed accordingly; reliable multicast is still an area for much research; expect to see more developments in this area; PGM, FEC, QoS

    • No congestion avoidance: Lack of TCP windowing and "slow-start" mechanisms can result in network congestion; if possible, multicast applications should attempt to detect and avoid congestion conditions

    • Duplicates: Some multicast protocol mechanisms (e.g., asserts, registers, and SPT transitions) result in the occasional generation of duplicate packets; multicast applications should be designed to expect occasional duplicate packets

    • Out of order delivery: Some protocol mechanisms may also result in out of order delivery of packets

    • A unique packet addressed to each destination IP Address.

    • Same packet addressed to "Group" destination address...
    • ..replicated at each node along the tree.

    Multicast Addressing:
    • Source Address Can Never Be Class D Multicast Group Address - (Class A, B, C) - Always the unique unicast origin address of the packet - same as unicast

    • Destination - - (Class D) - Multicast Group Address Range

    Class D Group addresses - 224/4:
    • Multicast Group addresses are NOT in the unicast route table.
    • A separate multicast route table is maintained for active multicast trees.
    • Multicast trees are initiated by receivers signaling their request to join a group.
    • Sources do not need to join, they just send!
    • Multicast routing protocols build the trees:
    • Hop-by-hop, from the receivers (tree leaves) to the source (tree root).
    • Tree path follows the unicast route table backward to the source using source address.
    • i.e. Multicast relies on a dependable unicast infrastructure!

    Core Tree Types:
    • Default MDT
    • Connects all PEs
    • Bidirectional
    • Always present
    • Multi-Directional
    • Inclusive PMSI
    • MI-PMSI

    Data MDT
    • Connects subset of PEs
    • Unidirectional
    • On-demand
    • Selective PMSI
    • S-PMSI

    Partitioned MDT
    • Connects subset of PEs
    • Uni- or Bidirectional
    • On-demand
    • Multidirectional
    • Selective PMSI
    • MS-PMSI
    MDT = Multicast Distribution Tree
    PMSI = Provider Multicast Service Interface

    4 Core Tree Type Constructions: PIM, mLDP, P2MP TE, and IR
    Core Tree Type Construction - PIM

    Core Tree Type Construction - mLDP
    • Full mesh of P2MP mLDP trees = Default MDT or
    • 1 MP2MP mLDP tree = Default MDT
    • 1 P2MP mLDP tree = Data MDT

    Core Tree Type Construction - P2MP TE
    • Full mesh of P2MP TE tunnels = Default MDT
    • 1 P2MP TE tunnel = Data MDT

    Core Tree Type Construction - IR
    • Full mesh of IR LSP sets = Default MDT
    • 1 IR LSP set = Data MDT

    • mcast IP | GRE | mcast IP
    • MPLS Label Stack | mcast IP

    Core Tree - PIM:
    • PIM/IP Multicast as we know it
    • Pretty complex, but well-known
    (*,G) and (S,G) / PIM Sparse Mode, PIM SSM, PIM BiDir
    • PIM for core tree
    • Used for Default Model / Rosen
    • Replication of mcast on the core routers

    • packetpushers.net/using-next-generation-mvpn-optimize-mpls-core-part-1

    • CCDE – Next Generation Multicast – NG-MVPN:

    • Introduction to Next-Gen MVPN:

    • IGMP (Internet Group Management Protocol) - เป็น Protocol ที่ใช้สำหรับสื่อสาร Multicast ระหว่าง:

    • รู้จักกับ Virtual Extensible LAN (VxLAN):


    • คุณประโยชน์และการใช้งาน VxLAN:

    • อบรม IP Multicast Technology and VXLAN - EVPN The Evolution of Overlay Networking:







      แต่ ถ้าใช้ ACI ง่ายกว่า!:

    Data Center 'Fabric' Journey (Standalone): Spanning-Tree > vPC > FabricPath > FabricPath BGP > VXLAN

    VXLAN Configuration - Enable the Feature set:
    • feature nv overlay - VxLAN encapsulation
      feature vn-segment-vlan-based - VXLAN Mode
      feature bgp
      nv overlay vpn - EVPN Control Plane

    What is ... ?:

    • VXLAN
    • Standards based Encapsulation:
      • RFC 7348
      • Uses UDP-Encapsulation
    • Transport Independent:
      • Layer-3 Transport (Underlay)
    • Flexible Namespace:
      • 24-bit field (VNID) provides ~16M unique identifier
      • Allows Segmentations

    • EVPN
    • Standards based Control-Plane:
      • RFC 7432
      • Uses Multiprotocol BGP
    • Uses Various Data-Planes:
      • VXLAN (EVPN-Overlay), MPLS, Provider Backbone (PBB)
    • Many Use-Cases Covered:
      • Bridging, MAC Mobility, First-Hop & Prefix Routing, Multi-Tenancy (VPN)

    Data Centre Interconnect (DCI) evaluating options:
    1. Dark Fiber
    2. C/DWDM
    3. L2 Trunks
    4. L3 PTP Links
    5. MPLS L3VPN
    6. MPLS L2VPN
    7. VPLS
    8. GRE / IPSEC Tunnels
    9. EVPN
    10. VXLAN
    11. OTV
    12. LISP


    Interconnecting multiple Data Centers: VXLAN and Networking Challenges: