API Guide

(*, 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
VLT multicast routing
OS10 supports multicast routing in a VLT domain for IPv4 networks. This feature provides resiliency to multicast-routed traffic
when a VLT peer node or the VLTi link goes down.
Multicast routing table synchronization
Multicast routing protocols do not exchange multicast routes between peer VLT nodes. Each VLT node runs the PIM protocol
independent of the peer VLT node. Hence, the PIM states do not synchronize between the nodes. However, OS10 synchronizes
the multicast routing table with routes that the PIM learns on each of the nodes between the peer VLT nodes. Multicast routing
table synchronization:
● Avoids unoptimized forwarding over VLTi links. Table synchronization allows the incoming traffic sent to the wrong peer to
be routed locally within the device.
838
Multicast