DC Journey: Day 3 DCCOR — Apply Routing protocol, Multicast

Nexus only supports Sparse mode. Dense-mode and sparse-dense-mode aren't supported.

Multicast Sparse mode

Static randevouz point

#Static RP N7k1's loopback0
ip pim rp-address 10.0.0.71 group-list 224.0.0.0/4

# Interface Lo0 and Uplink
(config-if)# ip pim sparse-mode

#N5K2 
interface lo0
  ip igmp join-group 224.1.1.1

N7K1# show ip pim rp
PIM RP Status Information for VRF "default"
BSR disabled
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None

RP: 10.0.0.71*, (0),
 uptime: 03:00:56   priority: 255,
 RP-source: (local),
 group ranges:
 224.0.0.0/4

N7K1# show ip pim neighbor
PIM Neighbor Status for VRF "default"
Neighbor        Interface            Uptime    Expires   DR       Bidir-  BFD
 ECMP Redirect
                                                         Priority Capable State
    Capable
10.51.71.51     Ethernet1/3          03:03:22  00:01:43  1        yes     n/a
  no
10.52.71.52     Ethernet1/4          03:02:34  00:01:32  1        yes     n/a

N7K1# show ip pim statistics
PIM Global Counter Statistics for VRF:default, last reset: never
  Register processing (sent/received):
    Registers: 5/5, Null registers: 28/28, Register-Stops: 33/33
    Registers received and not RP: 0
    Registers received for SSM/Bidir groups: 0/0
  BSR processing (sent/received):
    Bootstraps: 0/0, Candidate-RPs: 0/0
    BSs from non-neighbors: 0, BSs from border interfaces: 0
    BS length errors: 0, BSs which RPF failed: 0
    BSs received but not listen configured: 0
    Cand-RPs from border interfaces: 0
    Cand-RPs received but not listen configured: 0
  Auto-RP processing (sent/received):
    Auto-RP Announces: 0/0, Auto-RP Discoveries: 0/0
    Auto-RP RPF failed: 0, Auto-RP from border interfaces: 0
    Auto-RP invalid type: 0, Auto-RP TTL expired: 0
    Auto-RP received but not listen configured: 0
  General errors:
    Control-plane RPF failure due to no route found: 2
    Data-plane RPF failure due to no route found: 0
    Data-plane no multicast state found: 0
    Data-plane create route state count: 2
N7K1#

SPT between RP and First Hop Router

# SENDER
N5K1# ping multicast 224.1.1.1 interface ethernet 1/5
PING 224.1.1.1 (224.1.1.1): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=48.791 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=21.176 ms
64 bytes from 10.52.71.52: icmp_seq=2 ttl=253 time=15.156 ms
64 bytes from 10.52.71.52: icmp_seq=3 ttl=253 time=18.921 ms
64 bytes from 10.52.71.52: icmp_seq=4 ttl=253 time=20.4 ms

--- 224.1.1.1 ping multicast statistics ---
5 packets transmitted,
From member 10.52.71.52: 5 packets received, 0.00% packet loss
--- in total, 1 group member responded ---

N5K1# ping multicast 224.1.1.1 interface ethernet 1/6
PING 224.1.1.1 (224.1.1.1): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=41.332 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=44.866 ms
64 bytes from 10.52.72.52: icmp_seq=2 ttl=253 time=24.902 ms
64 bytes from 10.52.72.52: icmp_seq=3 ttl=253 time=53.908 ms
64 bytes from 10.52.72.52: icmp_seq=4 ttl=253 time=32.339 ms

--- 224.1.1.1 ping multicast statistics ---
5 packets transmitted,
From member 10.52.72.52: 3 packets received, 40.00% packet loss
From member 10.52.71.52: 2 packets received, 60.00% packet loss
--- in total, 2 group members responded ---

N5K1# show ip mroute
IP Multicast Routing Table for VRF "default"

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:00:13, pim ip
  Incoming interface: Ethernet1/5, RPF nbr: 10.51.71.51
  Outgoing interface list: (count: 1)
    Ethernet1/5, uptime: 00:00:13, pim, (RPF)

(10.51.72.51/32, 224.1.1.1/32), uptime: 00:00:09, pim ip
  Incoming interface: Ethernet1/6, RPF nbr: 10.51.72.51
  Outgoing interface list: (count: 1)
    Ethernet1/6, uptime: 00:00:09, pim, (RPF)

(*, 232.0.0.0/8), uptime: 03:15:45, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

RP

N7K1# show ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 02:46:59, pim ip
  Incoming interface: loopback0, RPF nbr: 10.0.0.71
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 02:46:59, pim

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:04:49, ip mrib pim
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.71.51, internal
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:04:49, pim

(10.51.72.51/32, 224.1.1.1/32), uptime: 00:04:44, pim mrib ip
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.71.51, internal
  Outgoing interface list: (count: 0)

(*, 232.0.0.0/8), uptime: 02:47:50, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

Receiver

N5K2# sh ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:01:22, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:01:22, igmp

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:00:06, ip mrib pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:00:06, mrib

(10.51.72.51/32, 224.1.1.1/32), uptime: 00:00:11, ip mrib pim
  Incoming interface: Ethernet1/6, RPF nbr: 10.52.72.72
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:00:11, mrib

(*, 232.0.0.0/8), uptime: 00:01:44, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

N5K2#

Because of SPT-threshould is default to zero, Last hop router (LHR) switchover from Shared-tree (*, G) to SPT (S, G).

N5K1 
N5K1# ping multicast 224.1.1.1 interface ethernet 1/5 packet-size 1460 interval 0 timeout 1 df-bit  count 10000
PING 224.1.1.1 (224.1.1.1): 1460 data bytes
1468 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=22.3 ms
1468 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=14.195 ms
1468 bytes from 10.52.71.52: icmp_seq=2 ttl=253 time=20.07 ms

N5K2# sh ip mroute 224.1.1.1 source-tree detail
IP Multicast Routing Table for VRF "default"

Total number of routes: 3
Total number of (*,G) routes: 1
Total number of (S,G) routes: 1
Total number of (*,G-prefix) routes: 1

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:01:33, ip(0) mrib(1) pim(0)
  RPF-Source: 10.51.71.51 [80/110]
  Data Created: Yes
  Locally joined
  Nat Mode: Invalid
  Nat Route Type: Invalid
  Stats: 1029/1531152 [Packets/Bytes], 204.154 kbps
  Stats: Active Flow
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  LISP dest context id: 0  Outgoing interface list: (count: 1) (bridge-only: 0)
    loopback0, uptime: 00:01:33, mrib

N5K2

N5K2# sh ip mroute 224.1.1.1 shared-tree detail
IP Multicast Routing Table for VRF "default"

Total number of routes: 3
Total number of (*,G) routes: 1
Total number of (S,G) routes: 1
Total number of (*,G-prefix) routes: 1

(*, 224.1.1.1/32), uptime: 00:26:49, igmp(1) ip(0) pim(0)
  RPF-Source: 10.0.0.71 [41/110]
  Data Created: No
  Locally joined
  Nat Mode: Invalid
  Nat Route Type: Invalid
  Stats: 4/4548 [Packets/Bytes], 198.400 bps
  Stats: Active Flow
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  LISP dest context id: 0  Outgoing interface list: (count: 1) (bridge-only: 0)
    loopback0, uptime: 00:26:49, igmp

N5K2#

Avoiding SPT switchover, change SPT-threshould to infinity will keeping traffic flow over Shared-tree (*, G). In this topology, spine-leaf shared-tree and source tree will be the same

2026 Feb 12 01:15:51.681579 netstack: [30583] (default) Send packet (mbuf_prty 0): s=10.52.71.52, d=10.51.71.51, proto=1 (icmp), ICMP_ECHOREPLY, tos/dscp=0x0/0x0, ip_len=1488, id=83fc, ttl=255
2026 Feb 12 01:15:51.705268 netstack: [30583] (default) Rcvd packet on Ethernet1/5 (mbuf_prty 0): s=10.51.71.51, d=224.1.1.1, proto=1 (icmp), ICMP_ECHO, tos/dscp=0x0/0x0, ip_len=1488, id=83fd, ttl=253
2026 Feb 12 01:15:51.705537 netstack: [30583] (default) Send packet (mbuf_prty 0): s=10.52.71.52, d=10.51.71.51, proto=1 (icmp), ICMP_ECHOREPLY, tos/dscp=0x0/0x0, ip_len=1488, id=83fd, ttl=255
2026 Feb 12 01:15:51.837572 netstack: [30583] (default) Rcvd packet on Ethernet1/5 (mbuf_prty 0): s=10.51.71.51, d=224.1.1.1, proto=1 (icmp), ICMP_ECHO, tos/dscp=0x0/0x0, ip_len=1488, id=83fe, ttl=253
2026 Feb 12 01:15:51.837928 netstack: [30583] (default) Send packet (mbuf_prty 0): s=10.52.71.52, d=10.51.71.51, proto=1 (icmp), ICMP_ECHOREPLY, tos/dscp=0x0/0x0, ip_len=1488, id=83fe, ttl=255

N5K2(config)# ip pim spt-threshold infinity group-list prefix-list PL-MULTICAST-GROUPS
N5K2(config)# sh ip prefix-list PL-MULTICAST-GROUPS
ip prefix-list PL-MULTICAST-GROUPS: 1 entries
   seq 5 permit 224.1.1.1/32

N5K2# show ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:39:41, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:39:41, igmp

(*, 232.0.0.0/8), uptime: 00:40:03, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

N5K2# sh ip mroute 224.1.1.1 detail
IP Multicast Routing Table for VRF "default"

Total number of routes: 2
Total number of (*,G) routes: 1
Total number of (S,G) routes: 0
Total number of (*,G-prefix) routes: 1

(*, 224.1.1.1/32), uptime: 00:40:11, igmp(1) ip(0) pim(0)
  RPF-Source: 10.0.0.71 [41/110]
  Data Created: No
  Locally joined
  Nat Mode: Invalid
  Nat Route Type: Invalid
  Stats: 15298/22762020 [Packets/Bytes], 609.683 kbps
  Stats: Active Flow
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  LISP dest context id: 0  Outgoing interface list: (count: 1) (bridge-only: 0)
    loopback0, uptime: 00:40:11, igmp

N5K2#

PIM Prune capture

Auto-RedezvousPoint

cisco propriety solution to dynamically set RP.

• N7k1 as candidate-RP, N7K2 as Mapping agent
• Dynamic RPs are preferred over Static RP
• Auto-RP messages are subject to RPF checks
• RP-announcement goes to Mapping agent on multicast group 224.0.1.39
• Map-Agent share RP cache with others PIMs speakers over multicast 224.0.1.40

# Remove static RP in all devices

no ip pim rp-address 10.0.0.71 group-list 224.0.0.0/4

# Enable all switches to listen and fordware AutoRP messages

ip pim auto-rp forward listen

N5K2(config)# do sh ip int eth1/5 | sec multicast
  IP multicast groups locally joined:
      224.0.1.40  224.0.1.39  224.0.0.13  224.0.0.2  224.0.0.1  224.0.0.5
  IP multicast routing: enabled

# Mapping
N5K2(config)# ip pim auto-rp mapping-agent loopback 0

#Candidate-RP
N7K1# ip pim auto-rp rp-candidate loopback0 group-list 224.0.0.0/4

# RP across the network
N5K2# sh ip pim rp
PIM RP Status Information for VRF "default"
BSR disabled
Auto-RP RPA: 10.0.0.72, uptime: 00:16:20, expires: 00:02:23
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None

RP: 10.0.0.71, (0),
 uptime: 00:14:52   priority: 255,
 RP-source: 10.0.0.72 (A),
 group ranges:
 224.0.0.0/4   , expires: 00:02:23 (A)
N5K2#

Auto-RP N7K1 announcement

Auto-RP mapping Advertisement

Sender
N5K1# ping multicast 224.1.1.1 interface eth1/5 count 10
PING 224.1.1.1 (224.1.1.1): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=16.983 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=16.148 ms
64 bytes from 10.52.71.52: icmp_seq=2 ttl=253 time=16.203 ms
64 bytes from 10.52.71.52: icmp_seq=3 ttl=253 time=22.508 ms
64 bytes from 10.52.71.52: icmp_seq=4 ttl=253 time=21.374 ms
64 bytes from 10.52.71.52: icmp_seq=5 ttl=253 time=21.001 ms
64 bytes from 10.52.71.52: icmp_seq=6 ttl=253 time=22.409 ms
64 bytes from 10.52.71.52: icmp_seq=7 ttl=253 time=14.684 ms
64 bytes from 10.52.71.52: icmp_seq=8 ttl=253 time=19.077 ms
64 bytes from 10.52.71.52: icmp_seq=9 ttl=253 time=21.234 ms

--- 224.1.1.1 ping multicast statistics ---
10 packets transmitted,
From member 10.52.71.52: 10 packets received, 0.00% packet loss
--- in total, 1 group member responded ---

N5K1# ping multicast 224.2.2.2 interface eth1/5 count 10
PING 224.2.2.2 (224.2.2.2): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=20.725 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=14.395 ms
64 bytes from 10.52.71.52: icmp_seq=2 ttl=253 time=26.158 ms
64 bytes from 10.52.71.52: icmp_seq=3 ttl=253 time=15.794 ms
64 bytes from 10.52.71.52: icmp_seq=4 ttl=253 time=15.331 ms
64 bytes from 10.52.71.52: icmp_seq=5 ttl=253 time=21.627 ms
64 bytes from 10.52.71.52: icmp_seq=6 ttl=253 time=20.213 ms
64 bytes from 10.52.71.52: icmp_seq=7 ttl=253 time=15.755 ms
64 bytes from 10.52.71.52: icmp_seq=8 ttl=253 time=14.029 ms
64 bytes from 10.52.71.52: icmp_seq=9 ttl=253 time=15.188 ms

--- 224.2.2.2 ping multicast statistics ---
10 packets transmitted,
From member 10.52.71.52: 10 packets received, 0.00% packet loss
--- in total, 1 group member responded ---

N5K1# sh ip mroute
IP Multicast Routing Table for VRF "default"

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:00:35, pim ip
  Incoming interface: Ethernet1/5, RPF nbr: 10.51.71.51
  Outgoing interface list: (count: 1)
    Ethernet1/5, uptime: 00:00:35, pim, (RPF)

(10.51.71.51/32, 224.2.2.2/32), uptime: 00:00:43, pim ip
  Incoming interface: Ethernet1/5, RPF nbr: 10.51.71.51
  Outgoing interface list: (count: 1)
    Ethernet1/5, uptime: 00:00:43, pim, (RPF)

(*, 232.0.0.0/8), uptime: 22:55:32, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

# Receiver

N5K2# sh ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:41:26, igmp pim ip
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:41:26, igmp

(*, 224.2.2.2/32), uptime: 00:17:07, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:17:07, igmp

(10.51.71.51/32, 224.2.2.2/32), uptime: 00:01:11, ip mrib pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:01:11, mrib

(*, 232.0.0.0/8), uptime: 00:41:26, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

N5K2#

No SPT for 224.1.1.1 on N5K2 due to infinity spt-threshold previously done.

BSR

• Open standard solution for same proposal of Auto-RP created by Cisco
• Unicast candidate RP message to BSR
• Candidate BSR (Mapping agent), Candidate RP
• Highest priority became BSR or highest IP as tiebreaker
• BSR reports about itself from 224.0.0.13 with TTL = 1 is re-forward hop-by-hop

Remove old auto-rp parameters
no ip pim auto-rp rp-candidate loopback0 group-list 224.0.0.0/4
no ip pim auto-rp mapping-agent loopback0
no ip pim auto-rp forward listen

# RP NX-OS
ip pim bsr rp-candidate loopback0 group-list 224.0.0.0/4
ip pim bsr forward listen

#BSR Mapping agent
ip pim bsr bsr-candidate loopback0
ip pim bsr forward listen

# Leafs
ip pim bsr forward listen

################
N7K1# show ip pim rp
PIM RP Status Information for VRF "default"
BSR: 10.0.0.72, uptime: 00:07:23, expires: 00:01:30,
     priority: 64, hash-length: 30
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None

RP: 10.0.0.71*, (0),
 uptime: 00:07:21   priority: 192,
 RP-source: 10.0.0.72 (B),
 group ranges:
 224.0.0.0/4   , expires: 00:01:50 (B)
N7K1#

N5K2# show ip igmp groups
IGMP Connected Group Membership for VRF "default" - 1 total entries
Type: S - Static, D - Dynamic, L - Local, T - SSM Translated, H - Host Proxy
      * - Cache Only
Group Address      Type Interface              Uptime    Expires   Last Reporter
224.1.1.1          L   loopback0              02:05:16  never     10.0.0.52

N5K2# sh ip mroute  224.1.1.1 detail
IP Multicast Routing Table for VRF "default"

Total number of routes: 3
Total number of (*,G) routes: 1
Total number of (S,G) routes: 1
Total number of (*,G-prefix) routes: 1

(*, 224.1.1.1/32), uptime: 00:01:30, igmp(1) ip(0) pim(0)
  RPF-Source: 10.0.0.71 [41/110]
  Data Created: No
  Locally joined
  Nat Mode: Invalid
  Nat Route Type: Invalid
  Stats: 0/0 [Packets/Bytes], 0.000   bps
  Stats: Inactive Flow
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  LISP dest context id: 0  Outgoing interface list: (count: 1) (bridge-only: 0)
    loopback0, uptime: 00:01:30, igmp

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:01:30, ip(0) pim(0) mrib(1)
  RPF-Source: 10.51.71.51 [80/110]
  Data Created: Yes
  Locally joined
  Nat Mode: Invalid
  Nat Route Type: Invalid
  Stats: 2949/4388112 [Packets/Bytes], 585.082 kbps
  Stats: Active Flow
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  LISP dest context id: 0  Outgoing interface list: (count: 1) (bridge-only: 0)
    loopback0, uptime: 00:01:30, mrib

Bootstrap run over PIM transport

BSR- RP candidate

BSR Mapping advertisement

Anycast RP and MSDP

Multicast Source Discovery Protocol (MSDP) connects different PIM-SM domain while each domain has its own RP.

• MSDP TCP port 639, keeplive 60sec
• RPs share source information about source usibng Source Active (SA) message. Works like inter-RP PIM register message.
• MDS originally designed for inter-AS multicast but also possible to deploy anycast RP for Intra-AS multicast

1. removed BSR configuration

no ip pim bsr rp-candidate loopback0 group-list 224.0.0.0/4
no ip pim bsr bsr-candidate loopback0
no ip pim bsr forward listen

2. Loopbacks with duplicates IP between RP (1.2.3.4/32)

int lo1
ip address 1.2.3.4 255.255.255.255

3. Advertise lo1 into OSPF and add PIM on it

ip router ospf 1 area 0

4. Set ip pim rp-address 1.2.3.4

ip pim rp-address 1.2.3.4

5. MSDP
  feature MSDP
  int lo1
  ip pim sparse-mode
  ip msdp peer 10.0.0.71 connect-source lo0 (Lo0 underlay ospf and BGP session) 

Anycast RP and anycast PIM

Anycast PIM is only available on NX-OS, this feature allows the deployment of anycast RP without MSDP running on Control plane.

# on both RP
ip pim anycast-rp 1.2.3.4 10.0.0.71
ip pim anycast-rp 1.2.3.4 10.0.0.72
ip pim rp-address 1.2.3.4 group-list 224.0.0.0/4

# on other PIM speakers

ip pim rp-address 1.2.3.4 group-list 224.0.0.0/4

Testing anycast PIM while

• Group 224.1.1.1 won't move to (S,G) because of SPT infinity configuration, and;
• Group 227.1.1.1 must switchover to (S,G)

N5K2(config)# ip pim spt-threshold infinity group-list prefix-list PL-MULTICAST-GROUPS
N5K2(config)# sh ip prefix-list PL-MULTICAST-GROUPS
ip prefix-list PL-MULTICAST-GROUPS: 1 entries
   seq 5 permit 224.1.1.1/32

N5K2# sh run int loopback 0  | in igmp
  ip igmp join-group 224.1.1.1
  ip igmp join-group 227.1.1.1

N5K2# sh ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:00:02, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:00:02, igmp

(*, 227.1.1.1/32), uptime: 00:00:02, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:00:02, igmp

(*, 232.0.0.0/8), uptime: 00:00:02, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

N7k1 has received both PIM Join messages to both groups

N7K1# sh ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:03:28, pim ip
  Incoming interface: loopback1, RPF nbr: 1.2.3.4
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:03:28, pim

(*, 227.1.1.1/32), uptime: 00:03:27, pim ip
  Incoming interface: loopback1, RPF nbr: 1.2.3.4
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:03:27, pim

(*, 232.0.0.0/8), uptime: 00:03:45, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

(*, 239.0.0.1/32), uptime: 00:03:29, pim ip
  Incoming interface: loopback1, RPF nbr: 1.2.3.4
  Outgoing interface list: (count: 0)

N7K1#

after sending traffic from N5k1 on both uplinks, the router only is forwarding traffic if there is an OIL for the group.

N7K1# sh ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:10:41, pim ip
  Incoming interface: loopback1, RPF nbr: 1.2.3.4
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:10:41, pim

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:05:41, ip mrib pim
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.71.51, internal
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:05:41, pim

(10.51.72.51/32, 224.1.1.1/32), uptime: 00:05:37, pim mrib ip
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.71.51, internal
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:05:37, pim

(*, 227.1.1.1/32), uptime: 00:10:40, pim ip
  Incoming interface: loopback1, RPF nbr: 1.2.3.4
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:10:40, pim

(10.51.71.51/32, 227.1.1.1/32), uptime: 00:06:10, ip mrib pim
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.71.51, internal
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:06:10, pim

(10.51.72.51/32, 227.1.1.1/32), uptime: 00:06:06, pim mrib ip
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.71.51, internal
  Outgoing interface list: (count: 0)

(*, 232.0.0.0/8), uptime: 00:10:59, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

N7K2# sh ip mroute
IP Multicast Routing Table for VRF "default"

(10.51.71.51/32, 224.1.1.1/32), uptime: 00:06:00, pim ip
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.72.51, internal
  Outgoing interface list: (count: 0)

(10.51.72.51/32, 224.1.1.1/32), uptime: 00:05:56, ip pim
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.72.51, internal
  Outgoing interface list: (count: 0)

(10.51.71.51/32, 227.1.1.1/32), uptime: 00:06:29, pim ip
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.72.51, internal
  Outgoing interface list: (count: 0)

(10.51.72.51/32, 227.1.1.1/32), uptime: 00:06:25, ip pim
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.72.51, internal
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:06:25, pim

(*, 232.0.0.0/8), uptime: 00:07:38, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

Because of 224.1.1.1 is working only over share-tree, traffic from N5k1 through interface eth1/6 will failed. From N5K2 pespective N7k1 is the current RP (incoming interface).

N5K1# ping multicast 227.1.1.1 interface ethernet 1/5 count 2
PING 227.1.1.1 (227.1.1.1): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=22.059 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=28.962 ms

--- 227.1.1.1 ping multicast statistics ---
2 packets transmitted,
From member 10.52.71.52: 2 packets received, 0.00% packet loss
--- in total, 1 group member responded ---
N5K1# ping multicast 227.1.1.1 interface ethernet 1/6 count 2
PING 227.1.1.1 (227.1.1.1): 56 data bytes
64 bytes from 10.52.72.52: icmp_seq=0 ttl=253 time=13.969 ms
64 bytes from 10.52.72.52: icmp_seq=1 ttl=253 time=10.517 ms

--- 227.1.1.1 ping multicast statistics ---
2 packets transmitted,
From member 10.52.72.52: 2 packets received, 0.00% packet loss
--- in total, 1 group member responded ---
N5K1# ping multicast 224.1.1.1 interface ethernet 1/5 count 2
PING 224.1.1.1 (224.1.1.1): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=23.391 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=21.13 ms

--- 224.1.1.1 ping multicast statistics ---
2 packets transmitted,
From member 10.52.71.52: 2 packets received, 0.00% packet loss
--- in total, 1 group member responded ---
N5K1# ping multicast 224.1.1.1 interface ethernet 1/6 count 2
PING 224.1.1.1 (224.1.1.1): 56 data bytes
Request 0 timed out
Request 1 timed out

--- 224.1.1.1 ping multicast statistics ---
2 packets transmitted,
0 packets received, 100% packet loss
N5K1#

N5K2# sh ip mroute
IP Multicast Routing Table for VRF "default"

(*, 224.1.1.1/32), uptime: 00:07:12, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71 <<<<<<<
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:07:12, igmp

(*, 227.1.1.1/32), uptime: 00:07:12, igmp ip pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:07:12, igmp

(10.51.71.51/32, 227.1.1.1/32), uptime: 00:00:27, ip mrib pim
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:00:27, mrib

(10.51.72.51/32, 227.1.1.1/32), uptime: 00:00:42, ip mrib pim
  Incoming interface: Ethernet1/6, RPF nbr: 10.52.72.72
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:00:42, mrib

(*, 232.0.0.0/8), uptime: 00:07:12, pim ip
  Incoming interface: Null, RPF nbr: 0.0.0.0
  Outgoing interface list: (count: 0)

Source specific Multicast (SSM)

With IGMPv3, the receivers are able to informs which sources they want to receive traffic or which groups of sources they would like to exclude from sender allowed list.

This deployment removes the needs of RP, no Shared-tree (*, G). However, must be configured or anyway from application on host pre-learn sources IPs.

The range 232.0.0.0/8 is reserved to this kind of usage

ip pim ssm range 232.0.0.0/8 << automatic set by 

N5K2#
interface loopback0
  ip igmp version 3
  ip igmp join-group 232.1.2.3 source 10.51.72.51

N5K2# sh ip mroute 232.1.2.3
IP Multicast Routing Table for VRF "default"

(10.51.72.51/32, 232.1.2.3/32), uptime: 00:06:50, igmp ip pim
  Incoming interface: Ethernet1/6, RPF nbr: 10.52.72.72
  Outgoing interface list: (count: 1)
    loopback0, uptime: 00:06:50, igmp

N7K2# sh ip mroute 232.1.2.3
IP Multicast Routing Table for VRF "default"

(10.51.72.51/32, 232.1.2.3/32), uptime: 00:08:36, pim ip
  Incoming interface: Ethernet1/3, RPF nbr: 10.51.72.51
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:08:36, pim

N5K1# sh ip int b | in Eth1/
Eth1/5               10.51.71.51     protocol-up/link-up/admin-up
Eth1/6               10.51.72.51     protocol-up/link-up/admin-up
Eth1/15.51           10.0.51.51      protocol-up/link-up/admin-up

N5K1# ping multicast 232.1.2.3 interface eth1/6 count 2
PING 232.1.2.3 (232.1.2.3): 56 data bytes
64 bytes from 10.52.72.52: icmp_seq=0 ttl=253 time=17.951 ms
64 bytes from 10.52.72.52: icmp_seq=1 ttl=253 time=15.822 ms
^[[A
--- 232.1.2.3 ping multicast statistics ---
2 packets transmitted,
From member 10.52.72.52: 2 packets received, 0.00% packet loss
--- in total, 1 group member responded ---

# Wrong source IP
N5K1# ping multicast 232.1.2.3 interface eth1/5 count 2
PING 232.1.2.3 (232.1.2.3): 56 data bytes
Request 0 timed out
Request 1 timed out

--- 232.1.2.3 ping multicast statistics ---
2 packets transmitted,
0 packets received, 100% packet loss
N5K1#

Bidirectional PIM

Basically oppositive of SSM. Where SSM creates only SPT, Bidir only allowes shared trees that register message aren'’t allowed. Traffic always flows to RP.

This ideal to many-to-many sources where amount of memories consumed by Mroute is a concern.

Bidir PIM is a requirement while deploying VXLAN on Nexus9k

Only Designated forwader (DF) can forward traffic to RP

• Lowest metric to RP
• Highest IP in a tie

# Inform RP bifir to group 229.9.9.9 around the cos topology
ip pim rp-address 10.0.0.71 group-list 229.9.9.9/32 bidir

# Receiver

interface loopback0
  ip igmp join-group 229.9.9.9

N5K2# show ip pim group-range 229.9.9.9
PIM Group-Range Configuration for VRF "default"
Group-range        Action Mode  RP-address      Shrd-tree-range   Origin

229.9.9.9/32       -      Bidir 10.0.0.71       -                 Static

N5K2# sh ip pim rp
PIM RP Status Information for VRF "default"
BSR disabled
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None

RP: 1.2.3.4, (0),
 uptime: 22:00:02   priority: 255,
 RP-source: (local),
 group ranges:
 224.0.0.0/4
RP: 10.0.0.71, (1),
 uptime: 00:16:48   priority: 255,
 RP-source: (local),
 group ranges:
 229.9.9.9/32  (bidir)
N5K2#

N5K2# show ip mroute 229.9.9.9 detail
IP Multicast Routing Table for VRF "default"

Total number of routes: 5
Total number of (*,G) routes: 3
Total number of (S,G) routes: 1
Total number of (*,G-prefix) routes: 1

(*, 229.9.9.9/32), bidir, uptime: 00:14:37, pim(1) ip(0) igmp(1)
  RPF-Source: 10.0.0.71 [41/110]
  Data Created: No
  Locally joined
  Nat Mode: Invalid
  Nat Route Type: Invalid
  Stats: 2037/2964708 [Packets/Bytes], 197.440 kbps
  Stats: Active Flow
  Incoming interface: Ethernet1/5, RPF nbr: 10.52.71.71
  LISP dest context id: 0  Outgoing interface list: (count: 2) (bridge-only: 0)
    loopback0, uptime: 00:07:41, igmp
    Ethernet1/5, uptime: 00:14:37, pim, (RPF)

# Source
N5K1# sh ip pim rp
PIM RP Status Information for VRF "default"
BSR disabled
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None

RP: 1.2.3.4, (0),
 uptime: 21:59:47   priority: 255,
 RP-source: (local),
 group ranges:
 224.0.0.0/4
RP: 10.0.0.71, (1),
 uptime: 00:17:02   priority: 255,
 RP-source: (local),
 group ranges:
 229.9.9.9/32  (bidir)

N5K1# sh ip mroute 229.9.9.9
IP Multicast Routing Table for VRF "default"

(*, 229.9.9.9/32), bidir, uptime: 00:16:10, pim ip
  Incoming interface: Ethernet1/5, RPF nbr: 10.51.71.71
  Outgoing interface list: (count: 1)
    Ethernet1/5, uptime: 00:16:10, pim, (RPF)

N5K1# ping multicast 229.9.9.9 interface eth1/5  count 100 timeout 1 packet-size 14600

--- 229.9.9.9 ping multicast statistics ---
100 packets transmitted,
From member 10.52.71.52: 100 packets received, 0.00% packet loss
--- in total, 1 group member responded ---

# RP 
N7K1#  sh ip mroute 229.9.9.9
IP Multicast Routing Table for VRF "default"

(*, 229.9.9.9/32), bidir, uptime: 00:16:58, pim ip
  Incoming interface: loopback0, RPF nbr: 10.0.0.71
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:09:01, pim

N7K1# sh ip pim rp
PIM RP Status Information for VRF "default"
BSR disabled
Auto-RP disabled
BSR RP Candidate policy: None
BSR RP policy: None
Auto-RP Announce policy: None
Auto-RP Discovery policy: None

Anycast-RP 1.2.3.4 members:
  10.0.0.72  10.0.0.71*

RP: 1.2.3.4*, (0),
 uptime: 21:59:37   priority: 255,
 RP-source: (local),
 group ranges:
 224.0.0.0/4
RP: 10.0.0.71*, (1),
 uptime: 00:17:12   priority: 255,
 RP-source: (local),
 group ranges:
 229.9.9.9/32  (bidir)

No Short path tree on output above.

Phantom RP

Bidir PIM RP there is no a native radudancy like anycast PIM. To solve this, Phantom RP allows active/standby solutions using a longest mask match paradigm.

Examplo from HPE aruba

[embed]Phantom RP The method used to provide RP redundancy for PIM Bidir is known as Phantom RP. It is configured using the existing…arubanetworking.hpe.com

ACI Multipod Fabric: Phantom RP for IPN | Advanced Configuration Guide

[embed]

no ip pim rp-address 10.0.0.71 group-list 229.9.9.9/32 bidir

ip pim rp-address 192.0.2.254 group-list 229.9.9.9/32 bidir

# Active RP N7k1
interface loopback0
  ip address 192.0.2.200/25 secondary
  ip ospf network point-to-point
  ip pim sparse-mode

(*, 229.9.9.9/32), bidir, uptime: 00:13:05, pim ip
  Incoming interface: loopback0, RPF nbr: 192.0.2.254
  Outgoing interface list: (count: 2)
    Ethernet1/4, uptime: 00:10:58, pim
    loopback0, uptime: 00:13:05, pim, (RPF)

# Standby RP N7K2
interface loopback0
  ip address 192.0.2.200/24 secondary
  ip ospf network point-to-point
  ip pim sparse-mode

(*, 229.9.9.9/32), bidir, uptime: 00:12:08, pim ip
  Incoming interface: Ethernet1/4, RPF nbr: 10.52.72.52
  Outgoing interface list: (count: 1)
    Ethernet1/4, uptime: 00:12:08, pim, (RPF)

# Source multicast traffic
192.0.2.0/24, ubest/mbest: 1/0
    *via 10.51.72.72, Eth1/6, [110/41], 00:10:55, ospf-1, intra
192.0.2.128/25, ubest/mbest: 1/0
    *via 10.51.71.71, Eth1/5, [110/41], 00:14:10, ospf-1, intra

# Receiver multicast traffic 
192.0.2.0/24, ubest/mbest: 1/0
    *via 10.52.72.72, Eth1/6, [110/41], 00:11:17, ospf-1, intra
192.0.2.128/25, ubest/mbest: 1/0
    *via 10.52.71.71, Eth1/5, [110/41], 00:14:33, ospf-1, intra

Redundancy validation

# Traffic through N7K1
N5K1# show ip route 192.0.2.254
IP Route Table for VRF "default"

192.0.2.128/25, ubest/mbest: 1/0
    *via 10.51.71.71, Eth1/5, [110/41], 00:01:00, ospf-1, intra
N5K1#
N5K1#
N5K1# ping multicast 229.9.9.9 interface ethernet 1/5 count 3
PING 229.9.9.9 (229.9.9.9): 56 data bytes
64 bytes from 10.52.71.52: icmp_seq=0 ttl=253 time=18.779 ms
64 bytes from 10.52.71.52: icmp_seq=1 ttl=253 time=25.044 ms
64 bytes from 10.52.71.52: icmp_seq=2 ttl=253 time=16.922 ms

--- 229.9.9.9 ping multicast statistics ---
3 packets transmitted,
From member 10.52.71.52: 3 packets received, 0.00% packet loss
--- in total, 1 group member responded ---
N5K1#

# Shutdown uplinks on N7K1

N7K1# conf t
Enter configuration commands, one per line. End with CNTL/Z.
N7K1(config)# show cdp neighbors
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater,
                  V - VoIP-Phone, D - Remotely-Managed-Device,
                  s - Supports-STP-Dispute

Device-ID          Local Intrfce  Hldtme Capability  Platform      Port ID
N5K1(9LA5L4GX3C9)   Eth1/3         132    R S s     N9K-C9500v    Eth1/5
N5K2(9IBCESI8QZX)   Eth1/4         139    R S s     N9K-C9500v    Eth1/5

Total entries displayed: 2
N7K1(config)# int eth1/3-4
N7K1(config-if-range)# shutdown

# Unicast route longest prefix change to N7K2

N5K1# show ip route 192.0.2.254

192.0.2.128/25, ubest/mbest: 1/0
    *via 10.51.72.72, Eth1/6, [110/121], 00:00:04, ospf-1, intra
N5K1# ping multicast 229.9.9.9 interface ethernet 1/5 count 3
PING 229.9.9.9 (229.9.9.9): 56 data bytes
Request 0 timed out
Request 1 timed out
Request 2 timed out

--- 229.9.9.9 ping multicast statistics ---
3 packets transmitted,
0 packets received, 100% packet loss
N5K1#

# Sendin to N7k2 shared-tree could be created while hasn't worked before
N5K1# ping multicast 229.9.9.9 interface ethernet 1/6 count 3
PING 229.9.9.9 (229.9.9.9): 56 data bytes
64 bytes from 10.52.72.52: icmp_seq=0 ttl=253 time=15.653 ms
64 bytes from 10.52.72.52: icmp_seq=1 ttl=253 time=13.523 ms
64 bytes from 10.52.72.52: icmp_seq=2 ttl=253 time=17.753 ms

--- 229.9.9.9 ping multicast statistics ---
3 packets transmitted,
From member 10.52.72.52: 3 packets received, 0.00% packet loss
--- in total, 1 group member responded ---
N5K1#

$WHOAMI

What's next

TBD