Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About amartinsbrz
Stats
Member since
06-19-2008
7
Posts
0
Helpful
0
Solutions
07-24-2019
12:53 PM
S1 is in L3 mode so I do believe I need PIM enabled. Also it seems IGMP needs to be enable for PIM to work on Cisco switches.
... View more
07-24-2019
10:09 AM
Hi joseph, Thanks for your answer. In this case both R1 and S1 have PIM (Dense Mode) and IGMPv2 enabled, only IGMP Snooping has been disabled. R1 and S1 have a PIM Neighbor relantionship formed thus S1 can send prune messages to R1. I'm just wondering if flooding will occur on S1 before it gets pruned or not. Thanks again
... View more
07-24-2019
08:58 AM
if S1 (IGMP Snooping Disabled) does not have active listeners and R1 is sending Multicast Traffic, how long before S1 sends a PRUNE msg to R1? Also, Would in this scenario Multicast Packets been flooded to all ports on S1 until the Prune msg is received by R1? or S1 would drop all Multicast traffic because it has no members for that group? Thanks in advance
... View more
07-18-2019
09:17 AM
Hi Joseph, Thanks for your response. That is my understanding as well. Once the Multicast Server (MS) starts streaming, PIM Dense Mode on R1 should flood that Multicast stream down to S1, whether it has listeners or not, or until S1 prunes it. Unfortunately this is not the behavior I'm observing. When I start the multicast stream with iperf, I don't see that stream being flooded by S1, S1 has IGMP Snooping disabled by the way.
... View more
07-18-2019
05:59 AM
Unfortunately the setup I'm troubleshooting requires dense mode. I'd agree that Sparce Mode is more efficient. I've added the bi-dir pim command in a try to see if that would make any difference. I'll remove it. Thanks!
... View more
07-18-2019
05:57 AM
I'll switch to IGMPv2 and give it a try. I was not aware IGMPv3 and PIM dense mode were not compatible. Thanks
... View more
07-17-2019
01:09 PM
I'm trying to get this Multicast scenario to work for a troubleshooting I'm working on but for some reason it is not working as expected, maybe you guys can help me out. I have Pim Dense Mode and IGMP enable on both R1 and S1. I'm using iperf 2.x to send multicast traffic. Multicast Client (MC) is the iperf server subscribing to Multicast Group (MG) 239.2.3.4: [root@MC ~]# iperf -s -u -B 239.2.3.4 -i 1
------------------------------------------------------------
Server listening on UDP port 5001
Binding to local address 239.2.3.4
Joining multicast group 239.2.3.4
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------ When I do that, S1 receives an IGMP Membership Report and creates a IGMP Group on S1 and an entry on PIM mroute table: S1#sh ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.1.1.2 Vlan1 05:08:38 00:04:52 10.0.0.1
239.2.3.4 Vlan1 00:02:03 00:04:51 10.0.0.40
224.0.1.40 Vlan1 23:02:51 00:04:52 10.0.0.1
S1#
S1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.1.1.2), 05:09:14/00:04:16, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan1, Forward/Dense, 05:09:14/stopped
GigabitEthernet1/0/6, Forward/Dense, 05:09:14/stopped
(*, 239.2.3.4), 00:02:39/00:04:15, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan1, Forward/Dense, 00:02:39/stopped
GigabitEthernet1/0/6, Forward/Dense, 00:02:39/stopped
(*, 224.0.1.40), 1d00h/00:04:16, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet1/0/6, Forward/Dense, 05:10:30/stopped
Vlan1, Forward/Dense, 23:03:27/stopped
S1# But that entry does not get propagated to R1: R1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.255.255.250), 05:11:40/00:04:53, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/1, Forward/Dense, 05:11:39/stopped
Ethernet0/0, Forward/Dense, 05:11:40/stopped
(*, 224.0.1.40), 05:11:48/00:04:59, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/1, Forward/Dense, 05:11:39/stopped
Ethernet0/0, Forward/Dense, 05:11:48/stopped
R1# R1 and S1 have formed a neighbor relationship: R1#sh ip pim nei
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
172.17.1.1 Ethernet0/1 05:13:44/00:01:41 v2 1 / S P G
R1#
S1# sh ip pim nei
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,
L - DR Load-balancing Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
172.17.1.2 GigabitEthernet1/0/6 05:14:10/00:01:41 v2 1 / DR S P G
S1# R1 and S1 configs are attached Thanks in advance!
... View more
- Tags:
- Dense Mode
- igmp
- pim
Labels:
Public Statistics
| Date Registered | 06-19-2008 06:11 PM |
| Date Last Visited | 07-26-2019 12:12 AM |
| Total Messages Posted | 7 |
.jpg "VIP Expert"){kind=icon}
