Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
8629
Views
0
Helpful
48
Replies

Strange multicast problem when using Alteris Deployment Server

cbeswick
Level 1
Level 1

‎05-11-2010 07:07 AM - edited ‎03-06-2019 11:02 AM

Hi,

We use the PXE boot funtion on our desktop PCs and laptops. Multicast TFTP is enabled within the BIOS to grab a boot file and only recently we have been witnessing an "Open TFTP Timeout" during the bootup process.

I have checked over the IGMP / IP PIM configuration across our network and everything looks fine. However when I check the IGMP group that the client is trying to join I see address 224.1.1.2. Yet when I look at the IGMP group on the port to which the Altiris Deployment server connects I only see group 225.1.2.3.

A colleague has shown me the configuration for the MTFTP server on the deployment server and the group address is set at 224.1.1.0.

Shouldn't the group address on the Altiris deployment server also be 224.1.1.2 or is the 225.1.2.3 address within the 224.1.1.0 IGMP group and the problem is in fact something to do with the network ?

Any help would be appreciated.

Chris

Labels:
0 Helpful
48 Replies 48

cbeswick
Level 1
Level 1
In response to Mohamed Sobair

‎06-10-2010 07:13 AM

Hi Mohamed,

Output of the "sh ip mroute 224.0.1.39" and "sh ip mroute 224.0.1.40" below. I didn't put this in before as I was just checking the 227.1.1.3 group. Auto RP seems to working fine.

I can see the source of the multicast tree fine on the Server farm. It is only when I look at the distribution switches to which end clients are connected that the problems occur.

ci_t1_3a1_dist_sw1#sh ip mroute 224.0.1.40
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
       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

(*, 224.0.1.40), 2d21h/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Vlan89, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan70, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan64, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan94, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan90, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan65, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan95, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan98, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan67, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan93, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan91, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan73, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan97, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan99, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan8, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan27, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan82, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan106, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan74, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan71, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan66, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan96, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan84, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan88, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan102, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan72, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan10, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan25, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan85, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan69, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan83, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan5, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan7, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan92, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan105, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan6, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan4, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan76, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan20, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan2, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan3, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan18, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan104, Forward/Sparse-Dense, 2d21h/00:00:00
    Loopback0, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan223, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan224, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan68, Forward/Sparse-Dense, 2d21h/00:00:00

(172.16.255.3, 224.0.1.40), 2d21h/00:03:02, flags: LT
  Incoming interface: Vlan223, RPF nbr 172.16.223.250
  Outgoing interface list:
    Vlan89, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Vlan70, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Vlan64, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Vlan94, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Vlan90, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Vlan65, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Loopback0, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan104, Prune/Sparse-Dense, 00:00:01/00:02:59, A
    Vlan18, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan3, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan2, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan20, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan76, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan4, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan6, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan105, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan92, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan7, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan5, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan83, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan69, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan85, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan25, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan10, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan72, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan102, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan88, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan84, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan96, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan66, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan71, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan74, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan106, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan82, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan27, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan8, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan99, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan97, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan73, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan91, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan93, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan67, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan98, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan95, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan224, Prune/Sparse-Dense, 00:00:04/00:02:56, A
    Vlan68, Prune/Sparse-Dense, 00:00:04/00:02:56, A

ci_t1_3a1_dist_sw1#sh ip mroute 224.0.1.39
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
       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

(*, 224.0.1.39), 2d21h/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Vlan89, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan70, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan64, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan94, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan90, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan65, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan95, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan98, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan67, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan93, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan91, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan73, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan97, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan99, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan8, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan27, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan82, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan106, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan74, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan71, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan66, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan96, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan84, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan88, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan102, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan72, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan10, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan25, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan85, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan69, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan83, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan105, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan104, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan92, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan76, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan20, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan18, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan7, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan6, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan5, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan4, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan3, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan2, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan223, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan224, Forward/Sparse-Dense, 2d21h/00:00:00
    Vlan68, Forward/Sparse-Dense, 2d21h/00:00:00

(172.16.255.4, 224.0.1.39), 1d07h/00:02:23, flags: T
  Incoming interface: Vlan224, RPF nbr 172.16.224.250
  Outgoing interface list:
    Vlan2, Prune/Sparse-Dense, 00:00:38/00:02:21, A
    Vlan3, Prune/Sparse-Dense, 00:00:38/00:02:22, A
    Vlan4, Prune/Sparse-Dense, 00:00:38/00:02:21, A
    Vlan5, Prune/Sparse-Dense, 00:00:38/00:02:22, A
    Vlan6, Prune/Sparse-Dense, 00:00:38/00:02:21, A
    Vlan7, Prune/Sparse-Dense, 00:00:38/00:02:22, A
    Vlan18, Prune/Sparse-Dense, 00:00:38/00:02:21, A
    Vlan20, Prune/Sparse-Dense, 00:01:38/00:01:22, A
    Vlan76, Prune/Sparse-Dense, 00:00:38/00:02:21, A
    Vlan92, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan104, Prune/Sparse-Dense, 00:00:40/00:02:19, A
    Vlan105, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan83, Prune/Sparse-Dense, 00:00:40/00:02:19, A
    Vlan69, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan85, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan25, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan10, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan72, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan102, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan88, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan84, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan96, Prune/Sparse-Dense, 00:02:41/00:00:19, A
    Vlan66, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan71, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan74, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan106, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan82, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan27, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan8, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan99, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan97, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan73, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan91, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan93, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan67, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan98, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan95, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan65, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan90, Prune/Sparse-Dense, 00:01:40/00:01:20, A
    Vlan94, Prune/Sparse-Dense, 00:00:40/00:02:19, A
    Vlan64, Prune/Sparse-Dense, 00:00:40/00:02:19, A
    Vlan70, Prune/Sparse-Dense, 00:00:40/00:02:19, A
    Vlan89, Prune/Sparse-Dense, 00:00:40/00:02:19, A
    Vlan223, Forward/Sparse-Dense, 1d07h/00:00:00, A
    Vlan68, Prune/Sparse-Dense, 00:00:40/00:02:19, A

(172.16.255.3, 224.0.1.39), 2d02h/00:02:11, flags: PTX
  Incoming interface: Vlan223, RPF nbr 172.16.223.250
  Outgoing interface list:
    Vlan2, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan3, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan4, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan5, Prune/Sparse-Dense, 00:04:55/00:01:04, A
    Vlan6, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan7, Prune/Sparse-Dense, 00:04:55/00:01:04, A
    Vlan18, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan20, Prune/Sparse-Dense, 00:00:55/00:02:04, A
    Vlan76, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan92, Prune/Sparse-Dense, 00:00:55/00:02:04, A
    Vlan104, Prune/Sparse-Dense, 00:01:55/00:01:04, A
    Vlan105, Prune/Sparse-Dense, 00:04:55/00:01:04, A
    Vlan83, Prune/Sparse-Dense, 00:02:55/00:00:04, A
    Vlan69, Prune/Sparse-Dense, 00:03:55/00:02:04, A
    Vlan85, Prune/Sparse-Dense, 00:02:55/00:00:04, A
    Vlan25, Prune/Sparse-Dense, 00:02:55/00:00:04, A
    Vlan10, Prune/Sparse-Dense, 00:02:55/00:00:05, A
    Vlan72, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan102, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan88, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan84, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan96, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan66, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan71, Prune/Sparse-Dense, 00:03:55/00:02:04, A
    Vlan74, Prune/Sparse-Dense, 00:05:55/00:00:04, A
    Vlan106, Prune/Sparse-Dense, 00:03:55/00:02:04, A
    Vlan82, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan27, Prune/Sparse-Dense, 00:04:57/00:01:02, A
    Vlan8, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan99, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan97, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan73, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan91, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan93, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan67, Prune/Sparse-Dense, 00:03:57/00:02:02, A
    Vlan98, Prune/Sparse-Dense, 00:04:57/00:01:02, A
    Vlan95, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan65, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan90, Prune/Sparse-Dense, 00:05:57/00:00:02, A
    Vlan94, Prune/Sparse-Dense, 00:02:57/00:00:02, A
    Vlan64, Prune/Sparse-Dense, 00:02:57/00:00:02, A
    Vlan70, Prune/Sparse-Dense, 00:02:57/00:00:02, A
    Vlan89, Prune/Sparse-Dense, 00:02:57/00:00:02, A
    Vlan224, Prune/Sparse-Dense, 00:03:57/00:02:02, A
    Vlan68, Prune/Sparse-Dense, 00:02:57/00:00:02, A

ci_t1_3a1_dist_sw1#

0 Helpful

Mohamed Sobair
Level 7
Level 7

‎06-10-2010 12:50 PM

Hi Chris,

Ok, could you post (sh ip route 172.16.192.49) from the distribution switch? Is it reachable? If so, what is the next hop address for it?

HTH

MOhamed

0 Helpful

cbeswick
Level 1
Level 1
In response to Mohamed Sobair

‎06-11-2010 12:10 AM

Hi Mohamed,

ci_t2_65_c200_core2#sh ip route 172.16.192.49
Routing entry for 172.16.192.0/24
  Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric 1
  Last update from 172.16.227.251 on Vlan227, 3d14h ago
  Routing Descriptor Blocks:
  * 172.16.228.251, from 172.16.255.1, 3d14h ago, via Vlan228
      Route metric is 20, traffic share count is 1
    172.16.227.251, from 172.16.255.2, 3d14h ago, via Vlan227
      Route metric is 20, traffic share count is 1

These routes point to the Server farm Distribution layer which contain the default gateway (HSRP) for Vlan 192 in which the server resides.

The incoming Interface on the previous output (Core 2) for group 227.1.1.3 is Vlan 228 which also correlates with the above.

I have also copied in a "sh ip mroute 227.1.1.3" for the active gateway for this Vlan:

ci_t1_c050_sfdist_sw1#sh ip mroute 227.1.1.3
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
       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

(*, 227.1.1.3), 1d19h/stopped, RP 172.16.255.4, flags: SP
  Incoming interface: Vlan228, RPF nbr 172.16.228.250, RPF-MFD
  Outgoing interface list: Null

(172.16.192.49, 227.1.1.3), 1d19h/00:03:20, flags: T
  Incoming interface: Vlan192, RPF nbr 0.0.0.0, RPF-MFD
  Outgoing interface list:
    Vlan228, Forward/Sparse-Dense, 1d19h/00:02:52, H

As you can see the group has the correct outgoing interface (Vlan 228) which takes the stream up to the RP on Core 2. This is final hop before it gets to the server at layer 2. The only switch it traverses after this one is a Cisco 2960G which has igmp snooping enabled by default.

0 Helpful

Mohamed Sobair
Level 7
Level 7

‎06-12-2010 04:18 AM

Hi Chris,

Thats fine, could you just post the result for the output from (sh ip route 172.16.192.49) from this switch: ((ci_t1_c050_sfdist_sw1))

Thanks,

Mohamed

0 Helpful

cbeswick
Level 1
Level 1
In response to Mohamed Sobair

‎06-14-2010 12:29 AM

Hi Mohamed,

ci_t1_c050_sfdist_sw1#sh ip route 172.16.192.49
Routing entry for 172.16.192.0/24
  Known via "connected", distance 0, metric 0 (connected, via interface)
  Redistributing via ospf 1
  Advertised by ospf 1 subnets
  Routing Descriptor Blocks:
  * directly connected, via Vlan192
      Route metric is 0, traffic share count is 1

I have also copied in the configuration of the SVI on this switch;

interface Vlan192
description VL192_SF_MA
ip address 172.16.192.251 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
ip pim dr-priority 2
ip pim sparse-dense-mode
ip pim snooping
ip igmp snooping fast-leave
standby 1 ip 172.16.192.254
standby 1 timers msec 250 msec 750
standby 1 priority 200
standby 1 preempt delay minimum 240
end

I have forced the interface to be the DR for the Vlan as this switch is the active gateway for the HSRP group.

0 Helpful

Mohamed Sobair
Level 7
Level 7

‎06-14-2010 02:32 AM

Hi Chris,

Apologize for this,

Vlan 68 is where you reciever is located right? if so, please post the output of (sh ip route 172.16.255.4) and (sh ip mroute 227.1.1.3) from this switch: ci_t1_3a1_dist_sw1

For Vlan 68, do you have HSRP configured?

HTH


Mohamed

0 Helpful

cbeswick
Level 1
Level 1
In response to Mohamed Sobair

‎06-14-2010 07:56 AM

Hi Mohamed,

Yes, the receivers are on Vlan 68 (and a few others):

ci_t1_3a1_dist_sw1#sh ip route 172.16.255.4
Routing entry for 172.16.255.4/32
  Known via "ospf 1", distance 110, metric 2, type intra area
  Last update from 172.16.224.250 on Vlan224, 6d22h ago
  Routing Descriptor Blocks:
  * 172.16.224.250, from 172.16.255.4, 6d22h ago, via Vlan224
      Route metric is 2, traffic share count is 1

ci_t1_3a1_dist_sw1#sh ip mroute 227.1.1.3
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
       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

(*, 227.1.1.3), 05:58:50/00:02:54, RP 172.16.255.4, flags: SJC
  Incoming interface: Vlan224, RPF nbr 172.16.224.250, Partial-SC
  Outgoing interface list:
    Vlan68, Forward/Sparse-Dense, 00:02:11/00:00:48, H
    Vlan6, Forward/Sparse-Dense, 05:58:28/00:02:54, H

0 Helpful

Giuseppe Larosa
Hall of Fame
Hall of Fame
In response to cbeswick

‎06-14-2010 11:20 AM

Hello Mohamed, Chris,

the strange part that we had noticed in first posts is that the mroute is stucked in

Partial-SC

and the flags

SJC

meaning that the switch is attempting to join (J) the SPT but it is not able to complete this phase.

in first posts there are also examples of debug output showing the PIM activity for the group.

At least one device of the two providing unicast and multicast routing to vlan68 should be able to complete the join to SPT.

Chris had already tried to change pim dr-priority, to clear the mroute table, even to reload the system (ar least one ) with no results.

Chris has also mentioned that the two devices had another IOS image before and they were working for this vlan68 with multicast traffic.

I searched bug toolkit but I couldn't find a good match for this issue among bugs related to PIM.

Hope to help

Giuseppe

0 Helpful

Mohamed Sobair
Level 7
Level 7

‎06-14-2010 11:28 AM

Hi Chris,

Ok then, what I meant is to make vlan 68 on this switch((ci_t1_3a1_dist_sw1)) the active DR for vlan 68, not vlan 192.

On this switch ci_t1_3a1_dist_sw1, make interface Vlan 68 the Active Pim DR by changing its DR priority.

after that , please post back the (sh ip mroute 227.x.x.x) from the same switch ci_t1_3a1_dist_sw1)) as well as (sh ip igmp groups).

let us see if the problem resolved or not,

Mohamed

0 Helpful

cbeswick
Level 1
Level 1
In response to Mohamed Sobair

‎06-15-2010 02:18 AM

Hi Mohamed,

The switch in question (ci_t1_3a1_dist_sw1) is the active PIM DR for Vlan 68.

The output of the "sh ip igmp groups" is below. Please note that the Server team have changed the Multicast network back to 225.1.1.0 on the Alteris PXE server. The server has chosen address 225.1.1.6 as the new multicast address. Everything is as before but with a different multicast group address. The entry for Vlan 68 is mid table:

IGMP Connected Group Membership
Group Address    Interface                Uptime    Expires   Last Reporter   Group Accounted
239.192.1.0      Vlan10                   1w0d      00:02:43  172.16.10.3
239.255.255.253  Vlan6                    01:16:09  00:02:52  172.16.6.243
239.255.255.253  Vlan82                   02:00:18  00:02:46  172.16.82.226
239.255.255.250  Vlan85                   2d11h     00:02:48  172.16.85.126
239.255.255.250  Vlan73                   1w0d      00:02:43  172.16.73.47
239.255.255.250  Vlan94                   1w0d      00:02:03  172.16.94.74
239.255.255.250  Vlan64                   1w0d      00:02:18  172.16.64.36
239.255.255.250  Vlan70                   1w0d      00:02:34  172.16.70.24
239.255.255.250  Vlan89                   1w0d      00:02:20  172.16.89.82
239.255.255.250  Vlan65                   1w0d      00:02:57  172.16.65.51
239.255.255.250  Vlan98                   1w0d      00:02:57  172.16.98.59
239.255.255.250  Vlan95                   1w0d      00:02:43  172.16.95.54
239.255.255.250  Vlan67                   1w0d      00:02:03  172.16.67.29
239.255.255.250  Vlan93                   1w0d      00:02:46  172.16.93.54
239.255.255.250  Vlan91                   1w0d      00:02:43  172.16.91.73
239.255.255.250  Vlan88                   1w0d      00:02:48  172.16.88.72
239.255.255.250  Vlan99                   1w0d      00:02:45  172.16.99.52
239.255.255.250  Vlan97                   1w0d      00:02:43  172.16.97.96
239.255.255.250  Vlan27                   1w0d      00:02:04  172.16.27.9
239.255.255.250  Vlan8                    1w0d      00:02:13  172.16.8.34
239.255.255.250  Vlan82                   1w0d      00:02:41  172.16.82.69
239.255.255.250  Vlan74                   1w0d      00:02:18  172.16.74.24
239.255.255.250  Vlan66                   1w0d      00:02:47  172.16.66.21
239.255.255.250  Vlan71                   1w0d      00:02:57  172.16.71.45
239.255.255.250  Vlan72                   1w0d      00:02:42  172.16.72.25
239.255.255.250  Vlan102                  1w0d      00:02:41  172.16.102.1
239.255.255.250  Vlan96                   1w0d      00:02:55  172.16.96.65
239.255.255.250  Vlan68                   1w0d      00:02:02  172.16.68.33
239.255.255.250  Vlan69                   1w0d      00:02:03  172.16.69.50
239.255.255.250  Vlan7                    1w0d      00:02:41  172.16.7.57
239.255.255.250  Vlan5                    1w0d      00:02:43  172.16.5.52
239.255.255.250  Vlan4                    1w0d      00:02:49  172.16.4.25
239.255.255.250  Vlan6                    1w0d      00:02:43  172.16.6.5
239.255.255.250  Vlan3                    1w0d      00:02:43  172.16.3.21
239.255.255.250  Vlan92                   1w0d      00:02:30  172.16.92.70
239.255.255.250  Vlan2                    1w0d      00:02:42  172.16.2.221
239.255.255.250  Vlan76                   1w0d      00:02:43  172.16.76.201
239.255.255.250  Vlan104                  1w0d      00:02:44  172.16.104.147
239.220.200.201  Vlan92                   00:01:52  00:02:38  172.16.92.52
239.220.200.201  Vlan68                   00:03:17  00:02:10  172.16.68.235
225.86.67.83     Vlan68                   3d17h     00:02:13  172.16.68.235
225.86.67.83     Vlan74                   1w0d      00:02:17  172.16.74.221
224.0.23.12      Vlan83                   1w0d      00:02:42  172.16.83.36
224.1.23.12      Vlan83                   1w0d      00:02:45  172.16.83.32
239.192.8.3      Vlan74                   6d22h     00:02:17  172.16.74.10
224.0.5.128      Vlan71                   1w0d      00:02:04  172.16.71.15
234.56.93.162    Vlan6                    3d21h     00:01:49  172.16.6.11
234.56.93.162    Vlan90                   1w0d      00:02:12  172.16.90.53
234.56.93.162    Vlan89                   1w0d      00:02:19  172.16.89.66
234.56.93.162    Vlan94                   1w0d      00:02:02  172.16.94.80
234.56.93.162    Vlan98                   1w0d      00:02:58  172.16.98.53
234.56.93.162    Vlan95                   1w0d      00:02:43  172.16.95.55
234.56.93.162    Vlan93                   1w0d      00:02:46  172.16.93.55
234.56.93.162    Vlan91                   1w0d      00:02:43  172.16.91.136
234.56.93.162    Vlan99                   1w0d      00:02:45  172.16.99.52
234.56.93.162    Vlan97                   1w0d      00:02:43  172.16.97.51
234.56.93.162    Vlan68                   1w0d      00:02:06  172.16.68.83
234.56.93.162    Vlan96                   1w0d      00:02:58  172.16.96.68
234.56.93.162    Vlan88                   1w0d      00:02:48  172.16.88.51
234.56.93.162    Vlan92                   1w0d      00:02:31  172.16.92.53
225.1.1.6        Vlan84                   00:00:03  00:02:56  172.16.84.157
225.1.1.6        Vlan68                   00:00:05  00:02:54  172.16.68.93
225.1.1.6        Vlan6                    1d00h     00:02:29  172.16.6.3
224.0.255.135    Vlan2                    6d02h     00:02:46  172.16.2.24
224.0.255.135    Vlan73                   1w0d      00:02:43  172.16.73.42
224.0.255.135    Vlan64                   1w0d      00:02:17  172.16.64.36
224.0.255.135    Vlan94                   1w0d      00:02:01  172.16.94.107
224.0.255.135    Vlan70                   1w0d      00:02:33  172.16.70.24
224.0.255.135    Vlan89                   1w0d      00:02:18  172.16.89.80
224.0.255.135    Vlan65                   1w0d      00:02:56  172.16.65.57
224.0.255.135    Vlan98                   1w0d      00:02:56  172.16.98.79
224.0.255.135    Vlan95                   1w0d      00:02:44  172.16.95.52
224.0.255.135    Vlan67                   1w0d      00:02:02  172.16.67.32
224.0.255.135    Vlan99                   1w0d      00:02:44  172.16.99.52
224.0.255.135    Vlan93                   1w0d      00:02:42  172.16.93.62
224.0.255.135    Vlan91                   1w0d      00:02:42  172.16.91.75
224.0.255.135    Vlan97                   1w0d      00:02:47  172.16.97.87
224.0.255.135    Vlan27                   1w0d      00:02:02  172.16.27.6
224.0.255.135    Vlan8                    1w0d      00:02:12  172.16.8.45
224.0.255.135    Vlan82                   1w0d      00:02:40  172.16.82.246
224.0.255.135    Vlan71                   1w0d      00:02:56  172.16.71.45
224.0.255.135    Vlan74                   1w0d      00:02:16  172.16.74.5
224.0.255.135    Vlan102                  1w0d      00:02:42  172.16.102.1
224.0.255.135    Vlan72                   1w0d      00:02:42  172.16.72.1
224.0.255.135    Vlan66                   1w0d      00:02:43  172.16.66.23
224.0.255.135    Vlan88                   1w0d      00:02:47  172.16.88.77
224.0.255.135    Vlan96                   1w0d      00:02:55  172.16.96.58
224.0.255.135    Vlan68                   1w0d      00:02:02  172.16.68.15
224.0.255.135    Vlan69                   1w0d      00:02:04  172.16.69.50
224.0.255.135    Vlan7                    1w0d      00:02:40  172.16.7.57
224.0.255.135    Vlan5                    1w0d      00:02:42  172.16.5.26
224.0.255.135    Vlan4                    1w0d      00:02:50  172.16.4.25
224.0.255.135    Vlan92                   1w0d      00:02:29  172.16.92.70
224.0.255.135    Vlan3                    1w0d      00:02:42  172.16.3.21
224.0.255.135    Vlan6                    1w0d      00:02:42  172.16.6.30
224.0.255.135    Vlan76                   1w0d      00:02:40  172.16.76.105
224.0.1.1        Loopback0                1w0d      00:02:04  172.16.255.6
225.168.0.150    Vlan74                   4d22h     00:01:23  172.16.74.223
224.0.1.60       Vlan2                    1d20h     00:02:47  172.16.2.223
224.0.1.60       Vlan71                   5d00h     00:02:56  172.16.71.225
224.0.1.60       Vlan64                   1w0d      00:02:24  172.16.64.227
224.0.1.60       Vlan65                   1w0d      00:02:02  172.16.65.223
224.0.1.60       Vlan67                   1w0d      00:02:09  172.16.67.222
224.0.1.60       Vlan68                   1w0d      00:02:08  172.16.68.222
224.0.1.60       Vlan8                    1w0d      00:02:14  172.16.8.221
224.0.1.60       Vlan82                   1w0d      00:02:42  172.16.82.225
224.0.1.60       Vlan66                   1w0d      00:02:49  172.16.66.228
224.0.1.60       Vlan5                    1w0d      00:02:47  172.16.5.242
224.0.1.60       Vlan7                    1w0d      00:02:47  172.16.7.221
224.0.1.60       Vlan6                    1w0d      00:02:42  172.16.6.222
224.0.1.39       Vlan223                  1w0d      00:02:16  172.16.223.250
224.0.1.40       Loopback0                1w0d      00:02:57  172.16.255.6
224.0.1.84       Vlan83                   1w0d      00:02:45  172.16.83.33

0 Helpful

Giuseppe Larosa
Hall of Fame
Hall of Fame
In response to cbeswick

‎06-15-2010 03:29 AM

Hello Chris,

with this change of multicast address used by the server, do you see any changes?

225.1.1.6        Vlan68                   00:00:05  00:02:54  172.16.68.93

is the group able to be stable in the show ip igmp group?

Hope to help

Giuseppe

0 Helpful

cbeswick
Level 1
Level 1
In response to Giuseppe Larosa

‎06-15-2010 03:54 AM

Hi Giuseppe,

Unfortunately no change. I can see the *,G and S,G information from the server farm distribution switch to the core / RP, but the distribution switches which contain the receivers just don't join the shared tree and show the "partial-sc" message with just the *,G.

0 Helpful

Giuseppe Larosa
Hall of Fame
Hall of Fame
In response to cbeswick

‎06-15-2010 08:08 AM

Hello Chris,

what if in a maintanance window you shut the SVI Vlan68 on one of the two switches?

this is a test that can tell us if the presence of both devices create some confusion, as final check to decide if this is strange but working devices or you are really facing a software issue.

also it is important to check the following

sh ip rpf

sh ip rpf

because all the game of switching to source based tree is based on this check, a sort of dead lock could be caused if distrib1 has the better path to group source address and the other device distrib2 has the best path to RP address.

Hope to help

Giuseppe

0 Helpful

cbeswick
Level 1
Level 1
In response to Giuseppe Larosa

‎06-24-2010 04:19 AM

Hi,

Just to give you an update. I have a change raised today to change our multicast configuration. I am changing all layer 3 SVIs to "pim sparse-mode" and will use the "ip pim autorp listener" command to allow auto rp to still function. I will also be applying a whole host of commands that are highlighted in the best practices guide for multicasting using the "Any Soure Mutlicast" guide.

I will let you know how I get on.

0 Helpful

cbeswick
Level 1
Level 1
In response to cbeswick

‎06-24-2010 07:12 AM

Success!!

I can now see the routers joining the Source / Group and the stream is being fully hardware switched (RPF-MFD). I had to do a lot of reading to get back up the speed and have learnt a lot as a result of this problem. Thanks to Giuseppe and Mohamed for all your help.

ci_t1_3a1_dist_sw1#sh ip mroute 225.1.1.6

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

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

(*, 225.1.1.6), 00:23:56/stopped, RP 172.16.255.4, flags: SJC

Incoming interface: Vlan224, RPF nbr 172.16.224.250, Partial-SC

Outgoing interface list:

Vlan68, Forward/Sparse, 00:01:01/00:02:27, H

Vlan84, Forward/Sparse, 00:04:18/00:01:09, H

Vlan6, Forward/Sparse, 00:23:56/00:02:49, H

(172.16.192.49, 225.1.1.6), 00:23:56/00:02:50, flags: JT

Incoming interface: Vlan224, RPF nbr 172.16.224.250, RPF-MFD

Outgoing interface list:

Vlan68, Forward/Sparse, 00:01:01/00:02:27, H

Vlan84, Forward/Sparse, 00:04:18/00:01:09, H

Vlan6, Forward/Sparse, 00:23:56/00:02:49, H

0 Helpful
Customers Also Viewed These Support Documents