cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1033
Views
0
Helpful
11
Replies

ASR 1002 Multicast PIM not working

AmyEST
Level 1
Level 1

Have you enabled PIM Sparse Mode on Cisco ASR 1002? We're having a PIM issue where the traffic was failing unless we statically configure a mcast request or igmp group address. Any help on this, would be heavily appreciated?

ip multicast routing  - enable globally
ip pim sparse-mode - enable on interfaces
Static RP - Configured.


Below the current IOS running? 

Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 15.1(2)S, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 24-Mar-11 23:29 by mcpre


Cisco IOS-XE software, Copyright (c) 2005-2011 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.


ROM: IOS-XE ROMMON

palisades uptime is 1 hour, 36 minutes
Uptime for this control processor is 1 hour, 38 minutes
System returned to ROM by reload
System image file is "bootflash:/asr1000rp1-adventerprisek9.03.03.00.S.151-2.S.bin"
Last reload reason: Reload Command

 

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco ASR1002 (2RU) processor with 1703497K/6147K bytes of memory.
4 Gigabit Ethernet interfaces
3 Ten Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
7798783K bytes of eUSB flash at bootflash:.

 

11 Replies 11

balaji.bandi
Hall of Fame
Hall of Fame

What is your config look like where is your RP?

show interface config also ?

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Thank you for your response on it. Here attached is the config and some show commands. Please know that this config was working with different ASR1K model and IOS XE version . We saw the PIM traffic stop after router replaced, however unicast works fine . Multicast join only work with the igmp join-group. We have multicast routing and/or PIM in place with another ASR model, and Video streaming is working with no issue in the same location. It's just this ASR1002 seems to have problem with PIM.

Any comments ?

Thank you again.

Hi @AmyEST ,

All of the (S,G) entries for 239.255.255.250 in the multicast routing table are in registering state. This generally indicates a communication issue between the first hop router (ASR1002 in this case) and the RP.

You can refer to the following post describing the potential issues that can cause this situation.

https://community.cisco.com/t5/routing/multicast-registering/td-p/1580244

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

What group address are you trying to use?

239.255.255.250 is a plug-n-play mcast group for service discovery like printers, scanners and all of those registering messages are from having the hosts enabled with SSDP service. 

224.0.1.40 is auto-rp for electing an RP in the network. You are using a static RP entry.

Also where is the RP in relation to the sources and receivers? 

239.102.1.235. That seems to be your group of interest. Are there sources registered at the RP. I don't see a *, g entry for that. from what I can tell you don't have a sender for that group and you don't have anything but the router interfaces joined to that group. Your igmp command should show hosts actually registered to receive that group. 



You said it was working with a different router. What was different than the last one, did you change the routers IP address on the subnet and now you have a different igmp querier that is not the replacement device?


You need to go to the RP and see what sources are registered at the RP then work from the receiver to the RP to ensure RPF, PIM, and IGMP are working properly. IGMP on the host interfaces pim on all interfaces to the RP, and RPF is valid. 

 

Only the ASR1K model changed - ASR1K-X. The old router was an ASR1002. We have configured it with the same IP multicast Routing on the ASR with the static RP and PIM sparse mode on each of the VLAN interfaces. All of the enabled interfaces do appear in the show ip pim interface command. We did a bit of wire shark inspection as well, and multicast message was able to registered fine. We were able to see the IGMP group join messages coming from the client and multicast traffic sourced from the RP. MC stream is making it with the ASR1K-X, but no luck with the ASR1002.

thank you again.

Ok thanks all for your support. We replaced the ASR1002 with ASR1000-X using the same config, and this is a weird one but multicast is working. It might be a software issue though.

sp2720401
Level 1
Level 1

Without any configs for the router or the downstream switch it could be the router interface igmp settings, igmp snooping on the downstream switch not working or configured properly, or the host not sending igmp membership to the routers port with the correct versions. 

You also need to show the output of igmp groups and memberships of the router interface you want the traffic to go out. It could be that the interface where you are putting the manual joins is not configured properly to manage the host memberships.

Host sends group membership - router receives it and talks to upstream pim neighbor to add the group to its outgoing pim interface towards the host.

Hello
Using static RP is okay depending how large you MC environment is, Otherwise its to laborious and administrative to change as/when required.

Anyway, Are both Mapping agents and RPs reachable by all rtrs, also Pim requires to be enabled on all rtrs end-to-end along the same igp routing path between the mc source/receivers,

A couple of good things to check would be traceroute/mtrace from FHR/LHR  plus to see if you have mapping agent translation of the RP discovery.

Example:
both traces (ip/mc) need to be the same, if mtrace fails at any point pim is missing,

First Hop Router
traceroute  LHR source FHR numeric
mtrace LHR

LastHop Router
traceroute  FHR source LHR numeric
mtrace FHR

sh ip mroute | in (224.0.1.39,,224,0,1,40)  - EDITED scratch this just realised your using static rp mapping apologies...


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

 

Hello
After re-reading your OP , not sure now I understand your query.


@AmyEST wrote:

unless we statically configure a mcast request or igmp group address.


Why would you need to do this, if you have a MC source on the network ready to service receivers?

Anyhow in your attached file we can see all (S,G) refer to mc host of  (x.x.x.x, 239.255.255.250)
but you show ping working to 239.102.1.235 ?

Also this mc host 239.255.255.250 FHR is stuck registering with the RP > (see below)

(10.66.179.153, 239.255.255.250), 00:01:13/00:02:16, flags: FT
Incoming interface: BDI250, RPF nbr 0.0.0.0, Registering
Outgoing interface list:
TenGigabitEthernet0/1/0, Forward/Sparse, 00:01:13/00:03:16


So as stated check:

  • Pim is enabled on all interfaces
  • Reachability to/from RP and source/destination
  • The correct static RP is enabled on all pim rtrs
  • Access-list negating that address

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

I'm still having troubles with multicast on ASR1002. It works fine with ASR1001 and the same configuration. Do you know what is the recommended Golden release for ASR1002? 

Thank you,

AmyEst.

We don't have ACL blocking it at all. I attempted to test multicast with a pair device. I have feeling that is a software issue or there may be something else required to make it works on ASR1002, that I have missed. However not sure what it could be because as stated before MCAST works prefect with the ASR1001 with the same configuration, no IP blocks changed.  Any ideas or tshoot net steps would be appreciated.

Thank you,

AmyEst.

Review Cisco Networking products for a $25 gift card