The rendezvous point (RP) for the customer (overlay) network can be in any of the three networks (VXLAN, MVPN, or IP multicast).

Follow these guidelines when configuring PIM/IGMP for the handoff node:

• Make sure that the Rendezvous Point (RP) is different for TRM and the MVPN underlay, as shown in the following example.

  ip pim rp-address 90.1.1.100 group-list 225.0.0.0/8 --- TRM Underlay
  ip pim rp-address 91.1.1.100 group-list 233.0.0.0/8 --- MVPN Underlay
  
  

• Use a common RP for overlay multicast traffic.

• The RP can be in static, PIM Anycast, or PIM MSDP mode. The following example shows the RP configuration inside the VRF:

  vrf context vrfVxLAN5001  
    vni 5001                
    ip pim rp-address 111.1.1.1 group-list 226.0.0.0/8
    ip pim rp-address 112.2.1.1 group-list 227.0.0.0/8
  
  

• Enable IGMP snooping for VXLAN traffic using the ip igmp snooping vxlan command.

• Enable PIM sparse mode on all source interfaces and interfaces required to carry PIM traffic.

Follow these guidelines when configuring BGP for the handoff node:

• Add all VXLAN leafs as L2EVPN and TRM neighbors; include the redundant handoff node. If a route reflector is used, add only RR as a neighbor.

• Add all MVPN PEs as VPN neighbors. In MDT mode, add the MVPN PEs as MDT neighbors.

• Import configuration to advertise unicast routes from L2EVPN neighbors to VPN neighbors and vice versa.

• The BGP source identifier can be different or the same as the source interfaces used for the VTEP identifier (configured under the NVE interface)/MVPN PE identifier.

  feature bgp
  address-family ipv4 mdt
  address-family ipv4 mvpn
  
  neighbor 2.1.1.1
    address-family ipv4 mvpn
      send-community extended
    address-family l2vpn evpn
      send-community extended
      import vpn unicast reoriginate
  
  neighbor 30.30.30.30
    address-family vpnv4 unicast
      send-community
      send-community extended
      next-hop-self
      import l2vpn evpn reoriginate
    address-family ipv4 mdt
      send-community extended
      no next-hop-third-party
  
  

• Never use Inter-AS option B between MVPN peers. Instead, configure the no allocate-label option-b command under the VPNv4 unicast address family.

  address-family vpnv4 unicast
      no allocate-label option-b
  
  

• Set maximum paths should be set in EBGP mode.

  address-family l2vpn evpn
      maximum-paths 8
  vrf vrfVxLAN5001
      address-family ipv4 unicast
          maximum-paths 8
  
  

• If handoff nodes are deployed in dual mode, use the route-map command to avoid advertising prefixes associated with orphan hosts under the VPN address family.

  ip prefix-list ROUTES_CONNECTED_NON_LOCAL seq 2 premit 15.14.0.15/32
  
  route-map ROUTES_CONNECTED_NON_LOCAL deny
      match ip address prefix-list ROUTES_CONNECTED_NON_LOCAL
  
  neighbor 8.8.8.8
      remote-as 100
      update-source loopback1
      address-family vpnv4 unicast
        send-community
        send-community extended
        route-map ROUTES_CONNECTED_NON_LOCAL out
  
  

Follow these guidelines when configuring VXLAN for the handoff node:

• Enable the following features:

  feature nv overlay
  feature ngmvpn
  feature interface-vlan
  feature vn-segment-vlan-based
  
  

• Configure the required L3 VNI:

  L3VNIs are mapped to tenant VRF. 
  vlan 2501
    vn-segment 5001 <-- Associate VNI to a VLAN.
  
  

• Configure the NVE interface:

  interface nve1
    no shutdown
    host-reachability protocol bgp
    source-interface loopback1 <-- This interface should not be the same as the MVPN source interface.
    global suppress-arp
  member vni 5001 associate-vrf <-- L3VNI
    mcast-group 233.1.1.1 <-- The underlay multicast group for VXLAN should be different from the MVPN default/data MDT.
  
  

• Configure the tenant VRF:

  vrf context vrfVxLAN5001
    vni 5001 <-- Associate VNI to VRF.
    rd auto
  address-family ipv4 unicast
      route-target both auto
      route-target both auto mvpn
      route-target both auto evpn
  
  interface Vlan2501 <-- SVI interface associated with the L3VNI
    no shutdown
    mtu 9216 <-- The overlay header requires 58 byes, so the max tenant traffic is (Configured MTU – 58).
    vrf member vrfVxLAN5001
    no ip redirects
    ip forward
    ipv6 forward
    no ipv6 redirects
    ip pim sparse-mode <-- PIM is enabled.
  
  interface Vlan2 <-- SVI interface associated with L2 VNI
    no shutdown
    vrf member vrfVxLAN5001
    no ip redirects
    ip address 100.1.1.1/16
    no ipv6 redirects
    ip pim sparse-mode <-- PIM enabled on L2VNI
   fabric forwarding mode anycast-gateway
  
  

Follow these guidelines when configuring MVPN for the handoff node:

• Enable the following features:

  install feature-set mpls
  allow feature-set mpls
  feature-set mpls
  feature mpls l3vpn
  feature mvpn
  feature mpls ldp
  
  

• MPLS LDP Configuration:

  • Enable MPLS LDP (mpls ip ) on all interfaces that are MPLS links.

  • Do not advertise loopback interfaces used for VXLAN as MPLS prefixes.

    • Configure a prefix list that contains IP addresses that identify the MVPN PE node.

      ip prefix-list LDP-LOOPBACK seq 51 permit 9.1.1.10/32
      ip prefix-list LDP-LOOPBACK seq 52 permit 9.1.2.10/32
      
      

    • Configure label allocation only for MVPN PE identifiers.

      mpls ldp configuration
        explicit-null
        advertise-labels for LDP-LOOPBACK
        label allocate global prefix-list LDP-LOOPBACK
      
      

• Tenant VRF Configuration:

  • For the default MDT mode, make the underlay multicast group the same for all tenant multicast traffic under the VRF.

    vrf context vrfVxLAN5001
      vni 5001
      mdt default 225.1.100.1
      mdt source loopback100 <-- If the source interface is not configured, the BGP identifier is used as the source interface.
      mdt asm-use-shared-tree <-- If the underlay is configured in ASM mode
      no mdt enforce-bgp-mdt-safi <-- Enabled by befault but should be negated if BGP MDT should not be used for discovery.
      mdt mtu <mtu-value> <-- Overlay ENCAP Max MTU value
    
    

  • For the data MDT mode, configure a unique multicast group-set for a subset of or all tenant multicast traffic.

    mdt data 229.1.100.2/32 immediate-switch
    mdt data 232.1.10.4/24 immediate-switch
    route-map DATA_MDT_MAP permit 10
      match ip multicast group 237.1.1.1/32
    mdt data 235.1.1.1/32 immediate-switch route-map DATA_MDT_MAP
    
    

• Enable MVPN tunnel statistics.

  hardware profile mvpn-stats module all

Both TRM and MVPN are heavily dependent on the control plane. Make sure to set the CoPP policy bandwidth as per the topology.

The following CoPP classes are used for TRM and MVPN traffic:

• copp-system-p-class-multicast-router (The default bandwidth is 3000 pps.)

• copp-system-p-class-l3mc-data (The default bandwidth is 3000 pps.)

• copp-system-p-class-l2-default (The default bandwidth is 50 pps.)

• copp-class-normal-igmp (The default bandwidth is 6000 pps.)

The following configuration example shows CoPP policies that can be configured to avoid control packet drops with multicast route scale.

Note	The policer values in this example are approximations and might not be optimal for all topologies or traffic patterns. Configure the CoPP policies according to the MVPN/TRM traffic pattern.

copp copy profile strict prefix custom
  policy-map type control-plane custom-copp-policy-strict
    class custom-copp-class-normal-igmp 
      police cir 6000 pps bc 512 packets conform transmit violate drop
  control-plane
    service-policy input custom-copp-policy-strict

copp copy profile strict prefix custom 
  policy-map type control-plane custom-copp-policy-strict 
    class custom-copp-class-multicast-router
      police cir 6000 pps bc 512 packets conform transmit violate drop 
  control-plane 
    service-policy input custom-copp-policy-strict

copp copy profile strict prefix custom
  policy-map type control-plane custom-copp-policy-strict 
    class copp-system-p-class-l3mc-data 
      police cir 3000 pps bc 512 packets conform transmit violate drop
  control-plane
    service-policy input custom-copp-policy-strict

copp copy profile strict prefix custom
  policy-map type control-plane custom-copp-policy-strict
    class custom-copp-class-l2-default
      police cir 9000 pps bc 512 packets conform transmit violate drop
  control-plane
    service-policy input custom-copp-policy-strict