02-04-2023 03:44 PM
First time setting up multicast routing and I'm having some trouble getting multicast traffic to route between VLANs. I'm trying to use PIM SSM on a Nexus 5500 platform running 7.3(8)N1(1). Use case is a Grandstream VOIP PBX (UCM6304) sending a multicast page to a VOIP phone/intercom. Below is a diagram of my setup:
Lots of confusion on my part when reading through documentation regarding limitations in vPC domains. Below is a screenshot of my PIM configuration thus far:
Here is a screenshot of my interface configurations. Note that I enabled igmp version 3 on the SVI's and L3 interfaces since that seemed to be recommended.
Next screenshot shows the PIM neighbors, but a "show ip mroute 232.0.1.100" does not indicate any Outgoing interfaces for the SSM network segment. I assume this is a problem and is why I'm not seeing multicast traffic outside the originating VLAN.
Last set of screenshots show the pim interfaces:
Any help would be greatly appreciated. The Nexus docs I found here would seem to suggest no further configuration is required for PIM SSM- which makes me think I might be in an unsupported configuration (possibly the vPC domain?).
02-05-2023 02:41 AM
- Verify these items : show ip mroute , look for outgoing interfaces and or presence of vlans
Also check : "show ip pim interface", "show ip pim rpf" and "show ip pim join".
M.
02-05-2023 08:23 AM
See below for the output of show up mroute. I don't see any interfaces listed in the outgoing interface list, which I think is part of the problem. I have not idea how to make the SVI populate under the SSM range (232.0.0.0/8). I can confirm the sender and receiver are on the same SSM range (232.0.0.0/8). I can also confirm multicast listeners within the same vlan (VLAN10 in this case) are able to receive multicast traffic. Listeners in VLAN 40 can not.
5k-1# show ip mroute (*, 224.0.1.60/32), uptime: 2d13h, igmp ip pim (*, 224.0.1.75/32), uptime: 2d13h, igmp ip pim (*, 224.0.1.116/32), uptime: 2d13h, ip pim igmp (*, 224.0.1.187/32), uptime: 01:14:19, ip pim igmp (*, 232.0.0.0/8), uptime: 2d13h, pim ip (*, 233.89.188.1/32), uptime: 2d13h, igmp ip pim (192.168.10.116/32, 233.89.188.1/32), uptime: 2d13h, ip pim mrib (*, 239.255.255.250/32), uptime: 2d13h, igmp ip pim (192.168.10.116/32, 239.255.255.250/32), uptime: 2d13h, ip mrib pim (192.168.40.36/32, 239.255.255.250/32), uptime: 00:19:12, ip mrib pim (192.168.40.38/32, 239.255.255.250/32), uptime: 2d13h, ip mrib pim (192.168.40.39/32, 239.255.255.250/32), uptime: 00:36:03, ip mrib pim (192.168.40.101/32, 239.255.255.250/32), uptime: 2d13h, ip mrib pim | 5k-2# show ip mroute (*, 224.0.1.60/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.75/32), uptime: 2d13h, igmp ip pim (*, 224.0.1.116/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.187/32), uptime: 01:14:36, pim ip igmp (*, 232.0.0.0/8), uptime: 2d13h, pim ip (*, 233.89.188.1/32), uptime: 2d13h, igmp ip pim (*, 239.255.255.250/32), uptime: 2d13h, igmp ip pim
|
5k-1# show ip pim interface | 5k-2# show ip pim interface |
5k-1# 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 | 5k-2# 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 |
5k-1(config)# show ip pim fabric info Fabric Multicast Forwarding is DISABLED | 5k-2(config)# show ip pim fabric info Fabric Multicast Forwarding is DISABLED |
02-06-2023 12:56 AM
Hello
Have you tried ASM instead of SSM?
Both nexus
no ip pim ssm range 232.0.0.0/8
ip pim rp-address <loopback 0> group-list x.x.x.x
02-07-2023 08:55 PM
Hi Paul,
I have a ASM anycast-rp setup now but I'm still running into issues. See my reply below for more info on the setup.
Thanks - Bryan
02-05-2023 02:59 AM
is the both VLAN not working or any one of the vlan working as expected : (some how not able to read as expected the images, if you can post all in text file will be easy to review)
what nexus OS running :
refer new 7.x code config guide :
02-05-2023 08:08 AM
I don't have any VLAN's that can route multicast traffic between them. Multicast does work within the same VLAN. For example, a multicast listener in VLAN10 can receive multicast traffic from a sender that is also in VLAN10. Nexus version is 7.3(8)N1(1) and I copied the cmd output into tables below for easier reading. Switch 5k-1 is on the left, 5k-2 is on the right.
5k-1# show running-config pim !Command: show running-config pim version 7.3(8)N1(1) ip pim log-neighbor-changes
interface Vlan40 interface port-channel2 | 5k-2# show running-config pim !Command: show running-config pim version 7.3(8)N1(1) ip pim log-neighbor-changes
interface Vlan40 interface port-channel2 |
5k-1# show running-config interface vlan 10 !Command: show running-config interface Vlan10 version 7.3(8)N1(1) interface Vlan10 5k-1# show running-config interface vlan 40 !Command: show running-config interface Vlan40 version 7.3(8)N1(1) interface Vlan40 5k-1# show running-config interface port-channel 2 !Command: show running-config interface port-channel2 version 7.3(8)N1(1) interface port-channel2 | 5k-2# show running-config interface vlan 10 !Command: show running-config interface Vlan10 version 7.3(8)N1(1) interface Vlan10 5k-2# show running-config interface vlan 40 !Command: show running-config interface Vlan40 version 7.3(8)N1(1) interface Vlan40 5k-2# show running-config interface port-channel 2 !Command: show running-config interface port-channel2 version 7.3(8)N1(1) interface port-channel2 |
5k-1# show ip pim neighbor (*, 224.0.1.60/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.75/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.116/32), uptime: 2d12h, ip pim igmp (*, 224.0.1.187/32), uptime: 01:04:20, ip pim igmp (*, 232.0.0.0/8), uptime: 2d12h, pim ip (*, 233.89.188.1/32), uptime: 2d12h, igmp ip pim (192.168.10.116/32, 233.89.188.1/32), uptime: 2d12h, ip pim mrib (*, 239.255.255.250/32), uptime: 2d12h, igmp ip pim (192.168.10.116/32, 239.255.255.250/32), uptime: 2d12h, ip mrib pim (192.168.40.36/32, 239.255.255.250/32), uptime: 00:09:13, ip mrib pim (192.168.40.38/32, 239.255.255.250/32), uptime: 2d12h, ip mrib pim (192.168.40.39/32, 239.255.255.250/32), uptime: 00:26:04, ip mrib pim (192.168.40.101/32, 239.255.255.250/32), uptime: 2d12h, ip mrib pim | 5k-2# show ip pim neighbor (*, 224.0.1.60/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.75/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.116/32), uptime: 2d12h, igmp ip pim (*, 224.0.1.187/32), uptime: 01:03:30, pim ip igmp (*, 232.0.0.0/8), uptime: 2d12h, pim ip (*, 233.89.188.1/32), uptime: 2d12h, igmp ip pim (*, 239.255.255.250/32), uptime: 2d12h, igmp ip pim |
5k-1# show ip pim interface PIM Interface Status for VRF "default" Vlan10, Interface status: protocol-up/link-up/admin-up IP address: 192.168.10.2, IP subnet: 192.168.10.0/24 PIM DR: 192.168.10.3, DR's priority: 1 PIM neighbor count: 1 PIM hello interval: 30 secs, next hello sent in: 00:00:28 PIM neighbor holdtime: 105 secs PIM configured DR priority: 1 PIM configured DR delay: 3 secs PIM border interface: no PIM GenID sent in Hellos: 0x116be5bd PIM Hello MD5-AH Authentication: disabled PIM Neighbor policy: none configured PIM Join-Prune inbound policy: none configured PIM Join-Prune outbound policy: none configured PIM Join-Prune interval: 1 minutes PIM Join-Prune next sending: 1 minutes PIM BFD enabled: no PIM passive interface: no PIM VPC SVI: yes PIM Auto Enabled: no PIM vPC-peer neighbor: 192.168.10.3 PIM Interface Statistics, last reset: never General (sent/received): Hellos: 5348/5348 (early: 0), JPs: 14/0, Asserts: 0/0 Grafts: 0/0, Graft-Acks: 0/0 DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0 Errors: Checksum errors: 0, Invalid packet types/DF subtypes: 0/0 Authentication failed: 0 Packet length errors: 0, Bad version packets: 0, Packets from self: 0 Packets from non-neighbors: 0 Packets received on passiveinterface: 0 JPs received on RPF-interface: 0 (*,G) Joins received with no/wrong RP: 0/0 (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0 JPs filtered by inbound policy: 0 JPs filtered by outbound policy: 0 Vlan40, Interface status: protocol-up/link-up/admin-up IP address: 192.168.40.2, IP subnet: 192.168.40.0/24 PIM DR: 192.168.40.3, DR's priority: 1 PIM neighbor count: 1 PIM hello interval: 30 secs, next hello sent in: 0.009527 PIM neighbor holdtime: 105 secs PIM configured DR priority: 1 PIM configured DR delay: 3 secs PIM border interface: no PIM GenID sent in Hellos: 0x1199052f PIM Hello MD5-AH Authentication: disabled PIM Neighbor policy: none configured PIM Join-Prune inbound policy: none configured PIM Join-Prune outbound policy: none configured PIM Join-Prune interval: 1 minutes PIM Join-Prune next sending: 1 minutes PIM BFD enabled: no PIM passive interface: no PIM VPC SVI: yes PIM Auto Enabled: no PIM vPC-peer neighbor: 192.168.40.3 PIM Interface Statistics, last reset: never General (sent/received): Hellos: 5347/5345 (early: 0), JPs: 3/0, Asserts: 0/0 Grafts: 0/0, Graft-Acks: 0/0 DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0 Errors: Checksum errors: 0, Invalid packet types/DF subtypes: 0/0 Authentication failed: 0 Packet length errors: 0, Bad version packets: 0, Packets from self: 0 Packets from non-neighbors: 0 Packets received on passiveinterface: 0 JPs received on RPF-interface: 0 (*,G) Joins received with no/wrong RP: 0/0 (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0 JPs filtered by inbound policy: 0 JPs filtered by outbound policy: 0 port-channel2, Interface status: protocol-up/link-up/admin-up IP address: 192.168.0.33, IP subnet: 192.168.0.32/30 PIM DR: 192.168.0.34, DR's priority: 1 PIM neighbor count: 1 PIM hello interval: 30 secs, next hello sent in: 00:00:14 PIM neighbor holdtime: 105 secs PIM configured DR priority: 1 PIM configured DR delay: 3 secs PIM border interface: no PIM GenID sent in Hellos: 0x113f2073 PIM Hello MD5-AH Authentication: disabled PIM Neighbor policy: none configured PIM Join-Prune inbound policy: none configured PIM Join-Prune outbound policy: none configured PIM Join-Prune interval: 1 minutes PIM Join-Prune next sending: 1 minutes PIM BFD enabled: no PIM passive interface: no PIM VPC SVI: no PIM Auto Enabled: no PIM Interface Statistics, last reset: never General (sent/received): Hellos: 5345/5347 (early: 0), JPs: 0/0, Asserts: 0/0 Grafts: 0/0, Graft-Acks: 0/0 DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0 Errors: Checksum errors: 0, Invalid packet types/DF subtypes: 0/0 Authentication failed: 0 Packet length errors: 0, Bad version packets: 0, Packets from self: 0 Packets from non-neighbors: 0 Packets received on passiveinterface: 0 JPs received on RPF-interface: 0 (*,G) Joins received with no/wrong RP: 0/0 (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0 JPs filtered by inbound policy: 0 JPs filtered by outbound policy: 0 | 5k-2# show ip pim interface PIM Interface Status for VRF "default" Vlan10, Interface status: protocol-up/link-up/admin-up IP address: 192.168.10.3, IP subnet: 192.168.10.0/24 PIM DR: 192.168.10.3, DR's priority: 1 PIM neighbor count: 1 PIM hello interval: 30 secs, next hello sent in: 00:00:11 PIM neighbor holdtime: 105 secs PIM configured DR priority: 1 PIM configured DR delay: 3 secs PIM border interface: no PIM GenID sent in Hellos: 0x31e30a19 PIM Hello MD5-AH Authentication: disabled PIM Neighbor policy: none configured PIM Join-Prune inbound policy: none configured PIM Join-Prune outbound policy: none configured PIM Join-Prune interval: 1 minutes PIM Join-Prune next sending: 1 minutes PIM BFD enabled: no PIM passive interface: no PIM VPC SVI: yes PIM Auto Enabled: no PIM vPC-peer neighbor: 192.168.10.2 PIM Interface Statistics, last reset: never General (sent/received): Hellos: 5348/5346 (early: 0), JPs: 0/14, Asserts: 0/0 Grafts: 0/0, Graft-Acks: 0/0 DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0 Errors: Checksum errors: 0, Invalid packet types/DF subtypes: 0/0 Authentication failed: 0 Packet length errors: 0, Bad version packets: 0, Packets from self: 0 Packets from non-neighbors: 0 Packets received on passiveinterface: 0 JPs received on RPF-interface: 0 (*,G) Joins received with no/wrong RP: 0/0 (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0 JPs filtered by inbound policy: 0 JPs filtered by outbound policy: 0 Vlan40, Interface status: protocol-up/link-up/admin-up IP address: 192.168.40.3, IP subnet: 192.168.40.0/24 PIM DR: 192.168.40.3, DR's priority: 1 PIM neighbor count: 1 PIM hello interval: 30 secs, next hello sent in: 00:00:27 PIM neighbor holdtime: 105 secs PIM configured DR priority: 1 PIM configured DR delay: 3 secs PIM border interface: no PIM GenID sent in Hellos: 0x3209189c PIM Hello MD5-AH Authentication: disabled PIM Neighbor policy: none configured PIM Join-Prune inbound policy: none configured PIM Join-Prune outbound policy: none configured PIM Join-Prune interval: 1 minutes PIM Join-Prune next sending: 1 minutes PIM BFD enabled: no PIM passive interface: no PIM VPC SVI: yes PIM Auto Enabled: no PIM vPC-peer neighbor: 192.168.40.2 PIM Interface Statistics, last reset: never General (sent/received): Hellos: 5345/5346 (early: 0), JPs: 0/3, Asserts: 0/0 Grafts: 0/0, Graft-Acks: 0/0 DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0 Errors: Checksum errors: 0, Invalid packet types/DF subtypes: 0/0 Authentication failed: 0 Packet length errors: 0, Bad version packets: 0, Packets from self: 0 Packets from non-neighbors: 0 Packets received on passiveinterface: 0 JPs received on RPF-interface: 0 (*,G) Joins received with no/wrong RP: 0/0 (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0 JPs filtered by inbound policy: 0 JPs filtered by outbound policy: 0 port-channel2, Interface status: protocol-up/link-up/admin-up IP address: 192.168.0.34, IP subnet: 192.168.0.32/30 PIM DR: 192.168.0.34, DR's priority: 1 PIM neighbor count: 1 PIM hello interval: 30 secs, next hello sent in: 00:00:05 PIM neighbor holdtime: 105 secs PIM configured DR priority: 1 PIM configured DR delay: 3 secs PIM border interface: no PIM GenID sent in Hellos: 0x31b35c9e PIM Hello MD5-AH Authentication: disabled PIM Neighbor policy: none configured PIM Join-Prune inbound policy: none configured PIM Join-Prune outbound policy: none configured PIM Join-Prune interval: 1 minutes PIM Join-Prune next sending: 1 minutes PIM BFD enabled: no PIM passive interface: no PIM VPC SVI: no PIM Auto Enabled: no PIM Interface Statistics, last reset: never General (sent/received): Hellos: 5347/5344 (early: 0), JPs: 0/0, Asserts: 0/0 Grafts: 0/0, Graft-Acks: 0/0 DF-Offers: 0/0, DF-Winners: 0/0, DF-Backoffs: 0/0, DF-Passes: 0/0 Errors: Checksum errors: 0, Invalid packet types/DF subtypes: 0/0 Authentication failed: 0 Packet length errors: 0, Bad version packets: 0, Packets from self: 0 Packets from non-neighbors: 0 Packets received on passiveinterface: 0 JPs received on RPF-interface: 0 (*,G) Joins received with no/wrong RP: 0/0 (*,G)/(S,G) JPs received for SSM/Bidir groups: 0/0 JPs filtered by inbound policy: 0 JPs filtered by outbound policy: 0 |
02-05-2023 11:21 AM
Hello!
It's not completely clear where the Grandstream VOIP PBX is connected in your topology, but it may be worth configuring the vpc bind-vrf default vlan {vlan-id} command to see if that alleviates the issue. I recommend reviewing the Important Notes and Caveats section of the Create Topologies for Routing over Virtual Port Channel document for more information about this command and its usage, alongside the Binding a VRF Instance to a vPC section of the Cisco Nexus 5500 Series NX-OS Interfaces Configuration Guide, Release 7.x document.
Note that the VLAN bound to the default VRF (as well as any other non-default VRF) through this command must be a unique VLAN used solely for this purpose. I would not advise using an existing VLAN that carries production traffic.
I hope this helps - thank you!
-Christopher
02-05-2023 11:42 AM
Hi Christopher,
Thanks for the pointer - I'll read through the docs and try what you suggest. I setup a L3 link between the Nexus 5k's and set ip pim sparse-mode on both ends thinking that would be needed for pim/multicast traffic between the switches. Early documentation (Nexus version 5.x) seemed to suggest this was needed. As for where the Grandstream PBX is, it is hanging off the 2248TP FEX on an access port in VLAN10 (indicated by the phone on the left in the diagram.) The receiver of the multicast traffic is a phone/intercom listening in VLAN 40 (access port on the same FEX).
Thanks again - Bryan
02-07-2023 08:53 PM
I've given up on PIM SSM for the time being and am now trying PIM ASM with anycast-rp. Below is my updated configuration:
5k-1(config)# show running-config interface loopback 0 !Command: show running-config interface loopback0 version 7.3(8)N1(1) interface loopback0 5k-1(config)# show running-config interface loopback 1 !Command: show running-config interface loopback1 version 7.3(8)N1(1) interface loopback1 5k-1(config)# show running-config pim !Command: show running-config pim version 7.3(8)N1(1) ip pim rp-address 192.168.0.28 group-list 224.0.0.0/4
interface loopback1 interface Vlan10 interface Vlan40 interface port-channel2 5k-1(config)# show ip pim rp Anycast-RP 192.168.0.28 members: RP: 192.168.0.28*, (0), 5k-1(config)# show ip igmp groups 224.0.100.117 | 5k-2# show running-config interface loopback 0 !Command: show running-config interface loopback0 version 7.3(8)N1(1) interface loopback0 5k-2# show running-config interface loopback 1 !Command: show running-config interface loopback1 version 7.3(8)N1(1) interface loopback1 5k-2# show running-config pim !Command: show running-config pim version 7.3(8)N1(1) ip pim rp-address 192.168.0.28 group-list 224.0.0.0/4 interface loopback0 interface loopback1 interface Vlan10 interface Vlan40 interface port-channel2 5k-2# show ip pim rp Anycast-RP 192.168.0.28 members: RP: 192.168.0.28*, (0), 5k-2# show ip igmp groups 224.0.100.117 |
When I start a multicast page, I see the following change in the mroute table:
BEFORE MULTICAST TRAFFIC 5k-1(config)# show ip mroute 224.0.100.117 (*, 224.0.100.117/32), uptime: 1d02h, igmp ip pim AFTER MULTICAST TRAFFIC STARTS
5k-1(config)# show ip mroute 224.0.100.117 (*, 224.0.100.117/32), uptime: 1d02h, igmp ip pim (192.168.10.120/32, 224.0.100.117/32), uptime: 00:00:09, ip mrib pim
| BEFORE MULTICAST TRAFFIC 5k-2# show ip mroute 224.0.100.117 (*, 224.0.100.117/32), uptime: 1d02h, igmp pim ip AFTER MULTICAST TRAFFIC STARTS
5k-2# show ip mroute 224.0.100.117 (*, 224.0.100.117/32), uptime: 1d02h, igmp pim ip |
I see that I get a S,G entry in the mroute table with the source coming from VLAN 10 (the GrandStream PBX's IP is 192.168.10.120). Outgoing interfaces are VLAN10 and VLAN40 - but I would expect it to also use my L3 link port-channel 2 to send to the other RP on 5k-2. So no traffic is flowing over to 5k-2 and I don't understand why. Also note that I have (4) listening devices show in the mroute table. All are Grandstream GSC3516 intercoms that are configured to listen for multicast traffic on 224.0.100.117. (2) are in VLAN10 and (2) are in VLAN40. The VLAN10 devices will always work since they are in the same broadcast domain (VLAN) as the PBX. The devices in VLAN 40 never receive the multicast traffic.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide