troubleshooting Question

Cisco 4506E IOS-XE Multicast PIM

Avatar of cwtang
cwtang asked on
RoutersSwitches / HubsNetworking
1 Comment1 Solution1442 ViewsLast Modified:
I am trying to setup a Cisco 4506E-Sup7E switch for PIM spare-dense mode. I have enabled ip pim on the interfaces/vlan; however I dont seems to be able to join the multicast group from the client.
When I try to perform a mtrace to the RP/multicast source; I seems to be seeing none [default] on the switch which I dont understand as multicasting routing and PIM has been enabled on the interface. Port 3/1 is the uplink connecting to the network.

interface GigabitEthernet3/1
 no switchport
 ip address 172.21.73.4 255.255.255.240
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 ip pim sparse-dense-mode

I have attached the output for reference:

switch#mtrace 172.31.122.254
Type escape sequence to abort.
Mtrace from 172.31.122.254 to 172.21.73.4 via RPF
From source (?) to destination (?)
Querying full reverse path...
 0  172.21.73.4
-1  172.21.73.4 None  [default]
-2  172.21.73.1 PIM  [172.31.122.254/32]
-3  172.30.5.21 PIM  [172.31.122.0/24]
-4  172.30.122.193 PIM  [172.31.122.0/24]
-5  172.31.122.254

switch#sh ip rpf xxx.xxx.xxx.xxx
RPF information for ? (xxx.xxx.xxx.xxx)
  RPF interface: GigabitEthernet3/1
  RPF neighbor: ? (172.21.73.1)
  RPF route/mask: 0.0.0.0/0
  RPF type: unicast (ospf 1)
  Doing distance-preferred lookups across tables
  RPF topology: ipv4 multicast base, originated from ipv4 unicast base



switch#sh ip pim autorp
AutoRP Information:
  AutoRP is enabled.
  RP Discovery packet MTU is 0.
  224.0.1.40 is joined on GigabitEthernet3/1.
  AutoRP groups over sparse mode interface is enabled

PIM AutoRP Statistics: Sent/Received
  RP Announce: 0/0, RP Discovery: 0/102293


switch#sh ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor          Interface                Uptime/Expires    Ver   DR
Address                                                            Prio/Mode
172.21.73.1       GigabitEthernet3/1       1w4d/00:01:38     v2    1 / S P G
172.21.20.253     Vlan20                   09:51:35/00:01:33 v2    1 / DR S P G
172.21.21.253     Vlan21                   09:51:35/00:01:44 v2    1 / DR S P G
172.17.22.253     Vlan22                   09:51:35/00:01:37 v2    1 / DR S P G


switch#sh ip pim rp
Group: 239.255.255.250, RP: 172.31.122.254, v2, uptime 1w4d, expires 00:02:38
Group: 224.69.252.1, RP: 172.31.122.254, v2, uptime 1w4d, expires 00:02:38
Group: 224.0.1.60, RP: 172.31.122.254, v2, uptime 1w4d, expires 00:02:38

switch#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,
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.255.255.250), 1w5d/00:02:45, RP 172.31.122.254, flags: SP
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list: Null

(*, 224.69.252.1), 00:00:03/00:02:56, RP 172.31.122.254, flags: SP
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list: Null

(*, 224.0.1.60), 1w5d/00:02:09, RP 172.31.122.254, flags: SP
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list: Null

(*, 224.0.1.39), 00:19:25/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Vlan20, Forward/Sparse-Dense, 00:19:25/stopped
    Vlan21, Forward/Sparse-Dense, 00:19:25/stopped
    Vlan22, Forward/Sparse-Dense, 00:19:25/stopped
    GigabitEthernet3/1, Forward/Sparse-Dense, 00:19:25/stopped

(172.31.122.254, 224.0.1.39), 00:19:13/00:01:35, flags: T
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list:
    Vlan20, Forward/Sparse-Dense, 00:19:13/stopped
    Vlan21, Forward/Sparse-Dense, 00:19:13/stopped
    Vlan22, Forward/Sparse-Dense, 00:19:13/stopped

(172.31.111.254, 224.0.1.39), 00:19:25/00:01:23, flags: T
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list:
    Vlan20, Forward/Sparse-Dense, 00:19:25/stopped
    Vlan21, Forward/Sparse-Dense, 00:19:25/stopped
    Vlan22, Forward/Sparse-Dense, 00:19:25/stopped

(*, 224.0.1.40), 00:19:58/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Vlan20, Forward/Sparse-Dense, 00:19:58/stopped
    Vlan21, Forward/Sparse-Dense, 00:19:58/stopped
    Vlan22, Forward/Sparse-Dense, 00:19:58/stopped
    GigabitEthernet3/1, Forward/Sparse-Dense, 00:19:58/stopped

(172.31.111.254, 224.0.1.40), 00:19:13/00:02:33, flags: LT
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list:
    Vlan20, Forward/Sparse-Dense, 00:19:13/stopped
    Vlan21, Forward/Sparse-Dense, 00:19:13/stopped
    Vlan22, Forward/Sparse-Dense, 00:19:13/stopped

(172.31.122.254, 224.0.1.40), 00:19:14/00:02:40, flags: LT
  Incoming interface: GigabitEthernet3/1, RPF nbr 172.21.73.1
  Outgoing interface list:
    Vlan20, Forward/Sparse-Dense, 00:19:14/stopped
    Vlan21, Forward/Sparse-Dense, 00:19:14/stopped
    Vlan22, Forward/Sparse-Dense, 00:19:14/stopped


I am trying to join the group 224.69.252.1. Not too sure what may be the reason for the failure of the multicast.

Any help is appreciated.

Thanks.
ASKER CERTIFIED SOLUTION
cwtang

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 1 Comment.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 1 Comment.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros