×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Multicast between subnets

Answered Question
Jul 12th, 2012
User Badges:

We are trying to get multicast to work between two subnets but cannot seem to get it to work  We have the following configuration


multicast video - teradek cube - 10.223.21.101

  multicast - 239.1.254.1

  rtsp://10.223.21.101/stream1

client-a - 10.223.21.100

switch-a - 2960

router-a - 3725 - 10.223.21.1 (fa0/0.1)

fa0/1 - 10.0.10.9

|

|

fa0/1 - 10.0.10.101

router-b - 3725 - 10.223.99.1 (fa0/0.1)

switch-b - 2960

clent-b - 10.223.99.200


Client A and the multicast video server are connected to switch-a

Client B is connected to switch-b


Client A can access the multicast video

Client B cannot access the multicast video


Here is the configs


router-a

!

ip multicast-routing

!

int fa0/0

  no ip addr

!

int fa0/0.1

  desc local network

  encap dot1q 1 native

  ip addr 10.223.21.1 255.255.255.0

  ip pim sparse-mode

!

int fa0/1

  ip addr 10.0.10.9 255.255.255.0

  ip pim sparse-mode

!

ip pim autorp listner

ip pim send-rp-announce fa0/1 scope 8

ip pim send-rp-discovery fa0/1 scope 8

!


================================================


router-b

!

ip multicast-routing

!

int fa0/0

  no ip addr

!

int fa0/0.1

  desc local network

  encap dot1q 1 native

  ip addr 10.223.99.1 255.255.255.0

  ip pim sparse-mode

!

int fa0/1

  ip addr 10.0.10.101 255.255.255.0

  ip pim sparse-mode

!

ip pim autorp listner

!



Any help would be appreciated.

Correct Answer by Edison Ortiz about 5 years 1 month ago

There aren't any joins on the 'B' side. Verify the client's application TTL setting is greater than 1.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
John Blakley Thu, 07/12/2012 - 14:37
User Badges:
  • Purple, 4500 points or more

Can you post a quick diagram of how this is connected?


Also, can you post:


sh ip pim interfa

sh ip pim rp

sh ip mroute 239.1.254.1

sh ip pim rp mapping

sh ip pim autorp


HTH,

John

dtom Fri, 07/13/2012 - 08:17
User Badges:

Here is how things are connected:


router - 10.223.21.1

er-SPARE2#sh ip pim inter

Address          Interface                Ver/   Nbr    Query  DR     DR
                                          Mode   Count  Intvl  Prior
10.223.21.1      FastEthernet0/0.1        v2/S   0      30     1      10.223.21.1
10.0.10.9        FastEthernet0/1          v2/S   1      30     1      10.0.10.101
er-SPARE2#sh ip pim rp
Group: 239.1.254.1, RP: 10.0.10.9, v2, v1, next RP-reachable in 00:01:09
Group: 239.255.255.250, RP: 10.0.10.9, v2, v1, next RP-reachable in 00:00:45
Group: 228.67.43.91, RP: 10.0.10.9, v2, v1, next RP-reachable in 00:01:09

er-SPARE2#sh ip mroute 239.1.254.1
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,
       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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.254.1), 00:00:29/stopped, RP 10.0.10.9, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0.1, Forward/Sparse, 00:00:29/00:02:38

(10.223.21.103, 239.1.254.1), 00:00:27/00:02:58, flags: PT
  Incoming interface: FastEthernet0/0.1, RPF nbr 0.0.0.0
  Outgoing interface list: Null

er-SPARE2#sh ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent (FastEthernet0/1)

Group(s) 224.0.0.0/4
  RP 10.0.10.9 (?), v2v1
    Info source: 10.0.10.9 (?), elected via Auto-RP
         Uptime: 19:09:00, expires: 00:02:59

er-SPARE2#sh ip pim autorp
AutoRP Information:
  AutoRP is enabled.
  AutoRP groups over sparse mode interface is enabled

PIM AutoRP Statistics: Sent/Received
  RP Announce: 5302/4055, RP Discovery: 5345/0


===========================================================================================


router - 10.223.99.1

er-CARVER#sh ip pim inter

Address          Interface                Ver/   Nbr    Query  DR     DR
                                          Mode   Count  Intvl  Prior
10.223.99.1      FastEthernet0/0.1        v2/S   0      30     1      10.223.99.1
10.0.10.101      FastEthernet0/1          v2/S   1      30     1      10.0.10.101

er-CARVER#sh ip pim rp


er-CARVER#sh ip mroute 239.1.254.1
Group 239.1.254.1 not found
er-CARVER#sh ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 10.0.10.9 (?), v2v1
    Info source: 10.0.10.9 (?), elected via Auto-RP
         Uptime: 19:09:03, expires: 00:02:47

er-CARVER#sh ip pim autorp
AutoRP Information:
  AutoRP is enabled.
  AutoRP groups over sparse mode interface is enabled

PIM AutoRP Statistics: Sent/Received
  RP Announce: 0/0, RP Discovery: 0/4081
er-CARVER#

Correct Answer
Edison Ortiz Fri, 07/13/2012 - 08:51
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

There aren't any joins on the 'B' side. Verify the client's application TTL setting is greater than 1.

dtom Fri, 07/13/2012 - 14:57
User Badges:

That was it, the TTL setting.  Thanks.

Actions

This Discussion

Related Content