Re: IP Multicast----PIM-SM

sameermunj · ‎02-01-2011

Hi Team

I am trting to test multicast between two sites connected over WAN...SIte A is connected to Site B with DS3 link with ethernet output.The DS3 link is connncteted between cisco 2851 router at each end.

At Lan SIde Cisco 2851 router is conncted to Nortel-8600 Switch over ethernet connectivty at both end.PIM is enabled on Nortel-8600 core switch with Sparse mode and multicast is working fine within LAN.Same is the result for both sites.

Now we are trying to make multicast work over wan in which PIM is enabled on both lan & want interafce of cisco router with sparse mode and multicast is enabled globally...now both the routers are making neighbourship with respective lan switches and with each other but multicast traffic is not flowing.In cisco router Mroute is not coming for the multicast group defined in core switch..

Please suggest necessary changes for the same if any...

Note

Multicast is working fine within LAN for each site bbut its not working between 2 lans over wan...

LAN A====Core Switch A==Router A =====Metro Link Router B==Core Switch B==LAN B

we are trying Multicast between LAN A & LAN B...

Edison Ortiz · ‎02-01-2011

Please provide the mroute table.

Did you configure a RP? if so, which site is holding the RP?

Regards,

Edison

sameermunj · ‎02-01-2011

Hi

RP has been configured in both the routers as Vlan io in core switch in which the multicast server is placed.

Please find below the mroute capture form both the routers.

Router A

Router A #show 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

(*, 230.0.0.0), 00:04:21/00:02:35, RP 172.23.80.21, flags: SJCL
Incoming interface: FastEthernet0/0/1, RPF nbr 172.29.1.21
Outgoing interface list:
GigabitEthernet0/0, Forward/Sparse-Dense, 00:04:21/00:02:35

(*, 224.0.1.40), 00:20:33/00:02:37, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
    Loopback42, Forward/Sparse-Dense, 00:20:33/00:00:00
    FastEthernet0/0/0, Forward/Sparse-Dense, 00:20:33/00:00:00
    FastEthernet0/0/1, Forward/Sparse-Dense, 00:20:33/00:00:00
    GigabitEthernet0/0, Forward/Sparse-Dense, 00:20:33/00:00:00

Router A#show 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
10.232.65.21      GigabitEthernet0/0       02:41:15/00:01:36 v2    N /
172.29.1.21       FastEthernet0/0/1        02:37:30/00:01:39 v2    1 / S P G
172.31.1.21       FastEthernet0/0/0        02:37:41/00:01:30 v2    1 / S P G
INVDAB-DS3-RTR01#

Router B==== (Multicast server is in the switch connected to Router B)

Router B#show 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

(*, 230.0.0.0), 00:05:28/00:03:10, RP 172.23.80.21, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0/1, Forward/Sparse-Dense, 00:05:14/00:03:10
GigabitEthernet0/0, Forward/Sparse-Dense, 00:05:28/00:01:50

(*, 224.0.1.40), 00:20:53/00:02:12, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
    Loopback24, Forward/Sparse-Dense, 00:20:53/00:00:00
    FastEthernet0/0/1, Forward/Sparse-Dense, 00:20:53/00:00:00
    FastEthernet0/0/0, Forward/Sparse-Dense, 00:20:53/00:00:00
    GigabitEthernet0/0, Forward/Sparse-Dense, 00:20:53/00:00:00

Router B#show 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.23.80.7       GigabitEthernet0/0       02:38:13/00:01:31 v2    N /
172.23.80.6       GigabitEthernet0/0       02:38:14/00:01:31 v2    N /
172.31.1.22       FastEthernet0/0/0        02:38:28/00:01:19 v2    1 / DR S P G
172.29.1.22       FastEthernet0/0/1        02:38:16/00:01:27 v2    1 / DR S P G

attached is the config for both the routers...Multicast server is placed in the lan where Router B is conncted...

Note

Now Lan Switch A-Router A Router A-Router B RouterB-lan Switch B neighorship formed still traffic not passing..

Edison Ortiz · ‎02-01-2011

I don't see any S,G in your mroute. It seems the source multicast isn't sending anything. Please verify your application.

Often, the application is set to TTL = 1 and the mcast flow will die if the receivers are one hop away or greater.

Regards,

Edison

sameermunj · ‎02-01-2011

Hi Edison

So you want me to concentrate on application...

is the confoguration in the router looks ok any changes required in the same...if the config is ok i will fully concentrate on application..

anyway the receiver is 4 hop away from sender so definately i need to increase the ttl..

i will try the same and tes..

Edison Ortiz · ‎02-02-2011

Your configuration looks fine but I need to see a S,G in your mroute table.

A S,G is created by the server sending the multicast stream.

Without a S,G the receivers don't know where to get the multicast feed from.

Edit: One question, what's ACL 99? This can be blocking the S,G join from the source.

Also, can I see the mroute table from the switches? Are they Cisco switches?

sameermunj · ‎02-02-2011

Hi

Acual server has TTL=2 which we can change during downtime but we tried with a VLC player with higher TTL value but still it didnt worked.

My switches are Nortel(Avaya switches ) switches which are connected to cisco routers..will there be any compatibility issue in the same.

The VLC player multicast works fine for the switch in diffrent vlans...

Edison Ortiz · ‎02-02-2011

Let's see the mroute table when you have the other VLC player actually sending mcast flows.