• February 20, 2020, 01:40:57 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Multicast traffic won't traverse core switches  (Read 14191 times)

0 Members and 1 Guest are viewing this topic.

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Multicast traffic won't traverse core switches
« on: January 21, 2010, 06:36:31 PM »
I am stumped at present.

Multicast has stopped working to clients on our edge switches.
We have a pair of 8610's running 3.7.3.0 and edge 5510/20's running a mix of 4.x (Media edge switch), 5.x, and 6.x. The 8610's have an IST between them and normal traffic is fine. I have a 5510 with a trunk (management VLAN) port connected to one of the 8610's and a VLAN for the media servers resides on it. One of the servers serves the Parliament broadcast stream, and we use Multicast internally. The rest of the edge switches are connected similarly, but have dual trunks, one to each core 8610. We use VRRP for redundancy. Snoop is on on the edge switches, and their configuration has not changed.

So, if I start the test broadcast and connect a client to the 5510 (media switch), Mulicast is fine. If I connect to another switch (different VLAN) then I don't get Multicast, it falls back to RTSP. This was working ok until I had to re-create the Media VLAN due to an IP address change.

Under the IGMP tab on the directly connected 8610 I can see the Multicast group in the cache and Interface, but not on the non-connected 8610. The VLAN is applied to both 8610's, however if I try to enable PIM on the non-connected one, it says "the specified IP Address is invalid". I tried to add a second trunk between the 5510 and the second 8610, but that went horribly wrong and took down the segment. First a faulty fibre, then not sure but started dropping packets when using the new trunk. Backed that out of course.

Update: - I have recreated the VRRP on the second switch and now the IGMP shows the Multicast group being cahced on both switches, and the VLAN interface shows in the IGMP group. Sadly, still not Multicast at the edges...
Any help appreciated.
Cheers.
Glenn.
« Last Edit: January 21, 2010, 06:48:20 PM by Trackhappy »


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3841
    • michaelfmcnamara
    • Michael McNamara
Re: Multicast traffic won't traverse core switches
« Reply #1 on: January 21, 2010, 08:35:17 PM »
Hi Glenn,

You need a Multicast routing protocol to route between multiple VLANS. IGMP will only help you when the clients and servers are in the same VLAN. If you want to a Multicast stream to 'jump' between VLANS you need either PIM or DVMRP to facilitate that. I suspect when you deleted the Media VLAN IP interface you inadvertently deleted either the PIM or DVMRP configuration for that VLAN.

Do you have a backup of the configuration before you made that change?

It shouldn't be too hard to figure out if you were using PIM or DVMRP and then just re-enable that protocol on that VLAN IP interface. You might want to check your other ERS 8600 switch and see if you have PIM or DVMRP enabled globally. Then check the VLANs and see what protocols you have enabled on those VLANS (on the other ERS 8600 switch).

Have a look at this blog post for a quick example of how to setup DVMRP;
http://blog.michaelfmcnamara.com/2008/03/multicast-routing-protocol-part-1/

Good Luck!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #2 on: January 21, 2010, 08:40:11 PM »
Thanks Michael.

PIM (SSM) is enabled on the VLAN on both switches and seems to be happy enough. I had kept the old VLAN, but the settings all looked identical as far as I could see.
I will check out the link you have provided. I am upgrading the 5510 to 6.x code shortly just to rule any issues out there.

Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3841
    • michaelfmcnamara
    • Michael McNamara
Re: Multicast traffic won't traverse core switches
« Reply #3 on: January 21, 2010, 08:57:42 PM »
If you are using PIM then look at this blog post;
http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/

Specifically look at the 'show' commands for PIM.

 show ip pim mroute
 show ip pim neighbor
 show ip pim rp-set
 show ip pim candidate-rp
 show ip pim bsr

If you suspect the edge switches just disable IGMP snooping. You should be able to use the commands on the switches to show you which ports as participating in the Multicast stream and troubleshoot that way.

You can also try a tool from Nortel called MC Hammer, you can find more information here.

Good Luck!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #4 on: January 22, 2010, 12:48:29 AM »
Well, I have put almost everything in as per your doco. Fast-joinprune doesn't seem to be recognised (version) and I haven't set ospf.

Still no multicast action on the 205 segment from the 70 segment. Mroute excerpt below.

I am having a long weekend and off in about 15 minutes. Any more comments welcome. Fresh brain on Wednesday.

Have a great weekend all.  :)

10.210.1.242# show ip pim mroute

================================================================================
                                        Pim Multicast Route
================================================================================
 Src: 0.0.0.0       Grp: 239.192.61.124 RP: 10.0.0.16   Upstream: NULL
 Flags: WC RP CACHE MRTF_SMLT_PEER_SG
 Incoming  Port: Vlan0-cpp,
 Outgoing Ports: Vlan70-1/1,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan70-1/1,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    111    0    0       0
 VLAN-Id:    55   102   103   104   110   111   112   113   114    70   203   205
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   206   209   211   212   213   214   215   216   217   218   219   220
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   221   222   223     2
  Join-P:     0     0     0     0
  Assert:     0     0     0     0
 --------------------------------------------------------------------------------
 Src: 10.200.170.201  Grp: 239.192.61.124 RP: 10.0.0.16   Upstream: NULL
 Flags: SPT CACHE SG
 Incoming  Port: Vlan70-1/1,
 Outgoing Ports: Vlan70-1/1,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan70-1/1,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
     57    0    0       0
 VLAN-Id:    55   102   103   104   110   111   112   113   114    70   203   205
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   206   209   211   212   213   214   215   216   217   218   219   220
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   221   222   223     2
  Join-P:     0     0     0     0
  Assert:     0     0     0     0
 --------------------------------------------------------------------------------

Total Num of Entries Displayed 2
Flags Legend:
SPT = Shortest path tree, WC=(*,Grp) entry, RP=Rendezvous Point tree, CACHE=Kernel Cache, ASSERTED=Asse
rted, SG=(Src,Grp) entry, PMBR=(*,*,RP) entry, FWD_TO_RP=Forwarding to RP, FWD_TO_DR=Forwarding to DR,
SG_NODATA=SG Due to Join, CP_TO_CPU=Copy to CPU, STATIC_MROUTE=Static Mroute, MRTF_SMLT_PEER_SG=Peer SG
 On Non-DR For SMLT
--------------------------------------------------------------------------------

10.210.1.242#

« Last Edit: January 22, 2010, 07:30:45 PM by Michael McNamara »

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #5 on: January 26, 2010, 05:16:38 PM »
Here is where we are at on one of the core switches. As these are inside addresses, I haven't bothered anonomising it.

# show ip pim active-rp

================================================================================
                                        Pim Grp->RP Active RP Table
================================================================================
GRPADDR          RP-ADDR          RP-PRIORITY
--------------------------------------------------------------------------------
224.0.1.22        10.0.0.15         0    
224.0.1.60        10.0.0.15         0    
228.200.200.201   10.0.0.15         0    
239.192.61.124    10.0.0.15         0    
239.255.255.250   10.0.0.15         0    
239.255.255.253   10.0.0.15         0    


# show ip pim bsr

================================================================================
                                        Current BootStrap Router Info
================================================================================

Current BSR address: 10.0.0.15
Current BSR priority: 100
Current BSR HashMask: 255.255.255.252
Current BSR Fragment Tag: 6808
Pim Bootstrap Timer : 49


# show ip pim candidate-rp

================================================================================
                                        Pim Candidate RP Table
================================================================================
GRPADDR          GRPMASK          RPADDR          
--------------------------------------------------------------------------------
224.0.0.0        240.0.0.0        10.0.0.15        
239.192.61.124   255.255.255.255  10.0.0.15        


# show ip pim info

================================================================================
                                        Pim General Group
================================================================================
PimStat               : enabled
Mode                  : ssm
Mbr                   : disabled
StaticRP              : disabled
ActivityChkInterval   : 210
BootstrapPeriod       : 60
CRPAdvTimeout         : 60
DiscDataTimeout       : 60
RegSupprTimeout       : 60
UniRouteChangeTimeout : 5
JoinPruneInt          : 60


# show ip pim interface

================================================================================
                                        Pim Interface
================================================================================
IF        ADDR            MASK            MODE       DR              HLINT  JPINT  CBSPR          OPSTAT INTF TYPE
--------------------------------------------------------------------------------
Clip1     10.0.0.15       255.255.255.255 ssm        10.0.0.15       30     60     100(enabled) up     passive
Vlan70    10.200.170.241  255.255.255.0   ssm        10.200.170.242  30     60     -1  (disabled)  up     active
Vlan110   10.200.10.241   255.255.255.0   ssm        10.200.10.242   30     60     -1  (disabled)  up     active
Vlan55    10.55.1.241     255.255.0.0     ssm        10.55.1.242     30     60     -1  (disabled)  up     active
Vlan112   10.200.102.241  255.255.255.0   ssm        10.200.102.242  30     60     -1  (disabled)  up     active
Vlan102   10.102.1.241    255.255.0.0     ssm        10.102.1.242    30     60     -1  (disabled)  up     active
Vlan103   10.103.1.241    255.255.0.0     ssm        10.103.1.242    30     60     -1  (disabled)  up     active
Vlan104   10.104.1.241    255.255.0.0     ssm        10.104.1.242    30     60     -1  (disabled)  up     active
Vlan200   10.200.1.241    255.255.255.0   ssm        0.0.0.0         30     60     -1  (disabled)  down   active
Vlan210   10.210.1.241    255.255.0.0     ssm        0.0.0.0         30     60     -1  (disabled)  down   active
Vlan111   10.200.101.241  255.255.255.0   ssm        10.200.101.242  30     60     -1  (disabled)  up     active
Vlan113   10.200.103.241  255.255.255.0   ssm        10.200.103.242  30     60     -1  (disabled)  up     active
Vlan114   10.200.104.241  255.255.255.0   ssm        10.200.104.242  30     60     -1  (disabled)  up     active
Vlan223   10.200.23.241   255.255.255.0   ssm        0.0.0.0         30     60     -1  (disabled)  down   active
Vlan214   10.200.14.241   255.255.255.0   ssm        10.200.14.242   30     60     -1  (disabled)  up     active
Vlan203   10.200.3.241    255.255.255.0   ssm        10.200.3.242    30     60     -1  (disabled)  up     active
Vlan205   10.200.5.241    255.255.255.0   ssm        10.200.5.242    30     60     -1  (disabled)  up    active
Vlan206   10.200.6.241    255.255.255.0   ssm        10.200.6.242    30     60     -1  (disabled)  up     active
Vlan215   10.200.15.241   255.255.255.0   ssm        10.200.15.242   30     60     -1  (disabled)  up     active
Vlan211   10.200.11.241   255.255.255.0   ssm        10.200.11.242   30     60     -1  (disabled)  up     active
Vlan212   10.200.12.241   255.255.255.0   ssm        10.200.12.242   30     60     -1  (disabled)  up     active
Vlan213   10.200.13.241   255.255.255.0   ssm        10.200.13.242   30     60     -1  (disabled)  up     active
Vlan209   10.200.9.241    255.255.255.0   ssm        10.200.9.242    30     60     -1  (disabled)  up    active
Vlan216   10.200.16.241   255.255.255.0   ssm        10.200.16.242   30     60     -1  (disabled)  up     active
Vlan217   10.200.17.241   255.255.255.0   ssm        10.200.17.242   30     60     -1  (disabled)  up     active
Vlan218   10.200.18.241   255.255.255.0   ssm        10.200.18.242   30     60     -1  (disabled)  up     active
Vlan219   10.200.19.241   255.255.255.0   ssm        10.200.19.242   30     60     -1  (disabled)  up     active
Vlan220   10.200.20.241   255.255.255.0   ssm        10.200.20.242   30     60     -1  (disabled)  up     active
Vlan221   10.200.21.241   255.255.255.0   ssm        10.200.21.242   30     60     -1  (disabled)  up     active
Vlan222   10.200.22.241   255.255.255.0   ssm        10.200.22.242   30     60     -1  (disabled)  up     active
Vlan2     10.200.2.241    255.255.255.0   ssm        10.200.2.242    30     60     -1  (disabled)  up     active
Vlan155   10.200.55.241   255.255.255.0   ssm        0.0.0.0         30     60     -1  (disabled)  down   active


# show ip pim mroute

================================================================================
                                        Pim Multicast Route
================================================================================
 Src: 0.0.0.0       Grp: 224.0.1.22   RP: 10.0.0.15   Upstream: NULL
 Flags: WC RP CACHE
 Incoming  Port: Vlan0-cpp,
 Outgoing Ports: Vlan203-1/3, Vlan205-1/5,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan203-1/3, Vlan205-1/5,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    168    0    0       0
 VLAN-Id:    70   203   110   111   112   113   102   103   104   205   114   206
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   209   211   212   213    55     2   214   215   216   217   218   219
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   220   221   222
  Join-P:     0     0     0
  Assert:     0     0     0
 --------------------------------------------------------------------------------
 Src: 0.0.0.0       Grp: 224.0.1.60   RP: 10.0.0.15   Upstream: NULL
 Flags: WC RP CACHE
 Incoming  Port: Vlan0-cpp,
 Outgoing Ports: Vlan203-1/3, Vlan110-2/3, Vlan112-1/12, Vlan113-1/13, Vlan205-1/5, Vlan206-1/6, Vlan20
9-2/2, Vlan211-2/4, Vlan212-2/5, Vlan213-2/6,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan203-1/3, Vlan110-2/3, Vlan112-1/12, Vlan113-1/13, Vlan205-1/5, Vlan206-1/6, Vlan20
9-2/2, Vlan211-2/4, Vlan212-2/5, Vlan213-2/6,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    200    0    0       0
 VLAN-Id:    70   203   110   111   112   113   102   103   104   205   114   206
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   209   211   212   213    55     2   214   215   216   217   218   219
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   220   221   222
  Join-P:     0     0     0
  Assert:     0     0     0
 --------------------------------------------------------------------------------
 Src: 0.0.0.0       Grp: 228.200.200.201 RP: 10.0.0.15   Upstream: NULL
 Flags: WC RP CACHE MRTF_SMLT_PEER_SG
 Incoming  Port: Vlan0-cpp,
 Outgoing Ports: Vlan205-1/5,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan205-1/5,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    166    0    0       0
 VLAN-Id:    70   203   110   111   112   113   102   103   104   205   114   206
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   209   211   212   213    55     2   214   215   216   217   218   219
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   220   221   222
  Join-P:     0     0     0
  Assert:     0     0     0
 --------------------------------------------------------------------------------
 Src: 10.200.170.201  Grp: 239.192.61.124 RP: 10.0.0.15   Upstream: NULL
 Flags: SPT CACHE SG FWD_TO_DR
 Incoming  Port: Vlan70-1/15,
 Outgoing Ports: Vlan70-1/1,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports:
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    204    0    0       0
 VLAN-Id:    70   203   110   111   112   113   102   103   104   205   114   206
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   209   211   212   213    55     2   214   215   216   217   218   219
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   220   221   222
  Join-P:     0     0     0
  Assert:     0     0     0
 --------------------------------------------------------------------------------
 Src: 0.0.0.0       Grp: 239.255.255.250 RP: 10.0.0.15   Upstream: NULL
 Flags: WC RP CACHE MRTF_SMLT_PEER_SG
 Incoming  Port: Vlan0-cpp,
 Outgoing Ports: Vlan203-1/3, Vlan112-1/12, Vlan205-1/5, Vlan206-1/6,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan203-1/3, Vlan112-1/12, Vlan205-1/5, Vlan206-1/6,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    172    0    0       0
 VLAN-Id:    70   203   110   111   112   113   102   103   104   205   114   206
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   209   211   212   213    55     2   214   215   216   217   218   219
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   220   221   222
  Join-P:     0     0     0
  Assert:     0     0     0
 --------------------------------------------------------------------------------
 Src: 0.0.0.0       Grp: 239.255.255.253 RP: 10.0.0.15   Upstream: NULL
 Flags: WC RP CACHE MRTF_SMLT_PEER_SG
 Incoming  Port: Vlan0-cpp,
 Outgoing Ports: Vlan203-1/3,
 Joined   Ports:
 Pruned   Ports:
 Leaf     Ports: Vlan203-1/3,
 Asserted Ports:
 Prune Pending Ports:
 Assert Winner Ifs:
 Assert Loser Ifs:
TIMERS:
  Entry   JP   RS  Assert
    114    0    0       0
 VLAN-Id:    70   203   110   111   112   113   102   103   104   205   114   206
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   209   211   212   213    55     2   214   215   216   217   218   219
  Join-P:     0     0     0     0     0     0     0     0     0     0     0     0
  Assert:     0     0     0     0     0     0     0     0     0     0     0     0
 VLAN-Id:   220   221   222
  Join-P:     0     0     0
  Assert:     0     0     0
 --------------------------------------------------------------------------------

Total Num of Entries Displayed 6
Flags Legend:
SPT = Shortest path tree, WC=(*,Grp) entry, RP=Rendezvous Point tree, CACHE=Kernel Cache, ASSERTED=Asse
rted, SG=(Src,Grp) entry, PMBR=(*,*,RP) entry, FWD_TO_RP=Forwarding to RP, FWD_TO_DR=Forwarding to DR,
SG_NODATA=SG Due to Join, CP_TO_CPU=Copy to CPU, STATIC_MROUTE=Static Mroute, MRTF_SMLT_PEER_SG=Peer SG
 On Non-DR For SMLT
--------------------------------------------------------------------------------


# show ip pim neighbor

================================================================================
                                        Pim Neighbor
================================================================================
INTERFACE ADDRESS         UPTIME                EXPIRE              
--------------------------------------------------------------------------------
Vlan55    10.55.1.242     0 day(s), 00:42:25    0 day(s), 00:01:23  
Vlan102   10.102.1.242    0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan103   10.103.1.242    0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan104   10.104.1.242    0 day(s), 00:42:25    0 day(s), 00:01:23  
Vlan2     10.200.2.242    0 day(s), 01:00:19    0 day(s), 00:01:38  
Vlan203   10.200.3.242    0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan205   10.200.5.242    0 day(s), 00:06:38    0 day(s), 00:01:25  
Vlan206   10.200.6.242    0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan209   10.200.9.242    0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan110   10.200.10.242   0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan211   10.200.11.242   0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan212   10.200.12.242   0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan213   10.200.13.242   0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan214   10.200.14.242   0 day(s), 00:55:51    0 day(s), 00:01:31  
Vlan215   10.200.15.242   0 day(s), 00:55:51    0 day(s), 00:01:37  
Vlan216   10.200.16.242   0 day(s), 00:55:51    0 day(s), 00:01:43  
Vlan217   10.200.17.242   0 day(s), 00:55:51    0 day(s), 00:01:20  
Vlan218   10.200.18.242   0 day(s), 00:55:51    0 day(s), 00:01:26  
Vlan219   10.200.19.242   0 day(s), 00:55:51    0 day(s), 00:01:32  
Vlan220   10.200.20.242   0 day(s), 00:55:51    0 day(s), 00:01:39  
Vlan221   10.200.21.242   0 day(s), 00:55:51    0 day(s), 00:01:44  
Vlan222   10.200.22.242   0 day(s), 00:55:51    0 day(s), 00:01:16  
Vlan111   10.200.101.242  0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan112   10.200.102.242  0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan113   10.200.103.242  0 day(s), 00:42:25    0 day(s), 00:01:24  
Vlan114   10.200.104.242  0 day(s), 00:42:25    0 day(s), 00:01:23  
Vlan70    10.200.170.242  0 day(s), 00:29:00    0 day(s), 00:01:43  


# show ip pim rp-set

================================================================================
                                        Pim RPSet
================================================================================
GRPADDRESS      GRPMASK         ADDRESS         HOLDTIME   EXPTIME  
--------------------------------------------------------------------------------
224.0.0.0       240.0.0.0       10.0.0.15       150        114      
239.192.61.124  255.255.255.255 10.0.0.15       150        114      


# show ip pim static-rp

================================================================================
                                        Pim Static RP Table
================================================================================
GRPADDR          GRPMASK          RPADDR           STATUS  
--------------------------------------------------------------------------------


# show ip pim virtual-neighbor

================================================================================
                                        Pim Virtual Neighbor
================================================================================
INTERFACE                ADDRESS            
--------------------------------------------------------------------------------

10.210.1.241 (show/ip/pim)#



« Last Edit: January 26, 2010, 07:15:46 PM by Michael McNamara »

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #6 on: January 26, 2010, 06:29:49 PM »
Fixed!!!!! ;D

Thanks for all the great information. The PIM config was tied to the old interface address, which of course is gone. Also, for whatever reason PIM was down globally. After setting up as per your fabulous information and using the diagnostic help you provided, all is well.

I am learning more about theses beasties every day.

Thanks again.
Glenn.

Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3841
    • michaelfmcnamara
    • Michael McNamara
Re: Multicast traffic won't traverse core switches
« Reply #7 on: January 26, 2010, 07:21:10 PM »
That's great news...

I cleaned up the formatting of your CLI output above and was about to ask you for the multicast group address that the application was using.

Happy to hear that your back up and running again!

Cheers!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #8 on: January 26, 2010, 10:16:58 PM »
Out of interest, the last piece of the puzzle was to global enable PIM. From the DM, I couldn't do it. Going through the old config, I copied and pasted the command line and Voila!. Not sure why it had changed though, unless it did it when the Vlan with the PIM interface was removed.

Now, onto that upgrade...

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #9 on: January 28, 2010, 08:19:40 PM »
Well, it was too good to be true. It sometimes works now, but not always. Also, when it does work there is sometimes a delay of 5 -10 seconds until it starts.
I am thinking maybe something to do with having the two 8600's that one has (or should have) priority and that configuration is not right. I really don't understand that part of it and don't know just how to start tracking down the problem. I do know that on the local switch it works ok, so the source is not the problem.

 Edit!!! - PIM was turned off on our management VLAN. I have no idea why it worked at all like that, but I enabled PIM on VLAN 210 on both 8600's and away she went. I don't quite understand why it is need on the management VLAN though.
« Last Edit: January 28, 2010, 09:40:35 PM by Trackhappy »

Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3841
    • michaelfmcnamara
    • Michael McNamara
Re: Multicast traffic won't traverse core switches
« Reply #10 on: January 28, 2010, 10:13:37 PM »
Great catch!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #11 on: January 28, 2010, 10:22:40 PM »
Spoke too soon.  :'(
Worked flawlessy for 10 tries. Came back after lunch and it is defunct again (client times out and fails over to RTSP). Can it maybe work on either 8600,and one of them is not responding to it????

Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3841
    • michaelfmcnamara
    • Michael McNamara
Re: Multicast traffic won't traverse core switches
« Reply #12 on: January 28, 2010, 10:47:35 PM »
You just need to troubleshoot the problem, start at the core and work your way to the edge.

What's the Multicast address the application is using?

Do you see that Multicast address in the output of "show ip pim mroute"? Are the closet links members of that multicast streams? They'll show up as output ports and leafs.

If you are using IGMP (which I believe you where) what does your edge switch say? Has the switch added the edge port in question into the IGMP group? Is the uplink in the IGMP group?

If you suspect IGMP is an issue with the edge switch just disable IGMP Snooping for that VLAN and the switch will now flood the Multicast frames to all devices in that VLAN. You can check the edge switches with the following command;

5520-48T-PWR#show vlan multicast membership <VLAN_ID>

You should do all this checking on the current BSR which is 10.0.0.15.

Multicast can be a little confusing initially but once you've spent some time looking at it there's not that much to it.

Good Luck!

We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #13 on: January 28, 2010, 10:59:42 PM »
Thanks Michael, I will go through that lot. It seems to be that if it gets going, it is fine and quick. If I let it sit (I assume that my edge switch is pruned), then it sometimes will take like 5 seconds and away it will go, or it will just time out (seems to be about 15 seconds). Seems to be no rhyme or reason to whether it will kick in or not.

Anyhow, will update as I go through your suggested tips. 239.192.61.124 is the address.

Cheers.
Glenn.

Edit!!!

First output before I click on the link, second after. Naturally it worked this time. I'll try to catch it when it fails.

10.210.5.1# show vlan multicast membership 205
Multicast Group Address Unit Port
----------------------- ---- ----
239.255.255.250         1    28 
224.0.1.60              1    29 
224.0.1.60              1    35 
224.0.1.60              1    43 
239.255.255.250         2    2   
239.255.255.250         2    5   
239.255.255.250         2    10 
224.0.1.22              2    4   
224.0.1.22              2    17 

10.210.5.1# show vlan multicast membership 205
Multicast Group Address Unit Port
----------------------- ---- ----
239.255.255.250         1    28 
224.0.1.60              1    29 
224.0.1.60              1    35 
224.0.1.60              1    43 
239.192.61.124          1    16 
239.255.255.250         2    2   
239.255.255.250         2    5   
239.255.255.250         2    10 
224.0.1.22              2    4   
224.0.1.22              2    17 
« Last Edit: January 28, 2010, 11:09:14 PM by Trackhappy »

Offline Trackhappy

  • Jr. Member
  • **
  • Posts: 31
Re: Multicast traffic won't traverse core switches
« Reply #14 on: January 28, 2010, 11:30:28 PM »
Well, I clicked on the link, it started off, I saw it join the group, then 85% through buffering, it froze and I re-checked and it had dropped out.
There is another variable here, the source switch is running on a fibre to the other 8600, not the copper link to the closest it was previously. Nothing else is showing issues, but I wonder if TCP is hiding an issue that UDP shows up. Surely I'd see errors on the link and RDP would have issues???
I might fail back to the old link as soon as I can to rule that out before I proceed further.

Edit!!!
Hmmm, I just turned of snoop on my client edge switch, and it fails totally. OK, turn snoop on, but proxy off and works ok and for the last 5 minutes hasn't missed a beat. I wonder if the proxy function has a bug. I'll wait some time before I really admit this is the cure.
« Last Edit: January 28, 2010, 11:44:44 PM by Trackhappy »