Connectivity Guide

Table Of Contents
K - Ack-Pending state
Timers: Uptime/Expires
Interface state: Interface, next-Hop, State/Mode
(*, 224.1.1.1), uptime 00:05:44, expires 00:00:15, RP 182.190.168.224, flags: SCJ
Incoming interface: port-channel12, RPF neighbor 194.1.1.1
Outgoing interface list:
vlan2001 Forward/Sparse 00:05:44/Never
(201.1.1.1, 224.1.1.1), uptime 00:02:58, expires 00:00:31, flags: CT
Incoming interface: port-channel11, RPF neighbor 193.1.1.1
Outgoing interface list:
vlan2001 Forward/Sparse 00:02:58/Never
R4# show ip pim vrf red mcache
PIM Multicast Routing Cache Table
(*, 224.1.1.1)
Incoming interface : port-channel12
Outgoing interface list :
vlan2001
(201.1.1.1, 224.1.1.1)
Incoming interface : port-channel11
Outgoing interface list :
vlan2001
R4# show ip pim vrf red summary
Entries in PIM-TIB/MFC: 3/2
Active Modes:
PIM-SM
Interface summary:
4 active PIM interfaces
0 passive PIM interfaces
2 active PIM neighbor
TIB Summary:
1/1 (*,G) entries in PIM-TIB/MFC
1/1 (S,G) entries in PIM-TIB/MFC
1/0 (S,G,Rpt) entries in PIM-TIB/MFC
1 RP
1 sources
Message Summary:
81268/13033 Joins/Prunes sent/received
0 Null Register messages received
0/0 Register-stop messages sent/received
Data path event summary:
0/0 pim-assert messages sent/received
0/0 register messages sent/received
Multicast support on VLT
OS10 supports multicast in a VLT domain in active-standby mode.
In a VLT domain that is in active-standby mode, the designated router (DR) routes multicast traffic (Layer 3) and the other peer
VLT node switches (Layer 2) incoming multicast traffic over VLTi links.
In last hop router (LHR), the DR is responsible for triggering upstream PIM joins, but the traffic from RP can reach any one of
the VLT peers. For example, if the traffic reaches a peer VLT node that has not triggered the upstream join, it switches the
incoming multicast traffic over VLTi links which will reach the originating LHR-DR node. The traffic then gets routed at this
node. The L3 routed traffic gets replicated over VLTi links for all the receiver VLANs. This traffic is processed by non-DR LHR
node and it forwards it to appropriate receivers based on VLT L2 traffic forwarding rules.
644
Multicast