Got it

S67xx Multicast PIM

Created: May 5, 2021 08:58:50Latest reply: May 6, 2021 01:58:44 390 8 0 0 0
  HiCoins as reward: 1 (problem unresolved)
Hello

I'm looking for help with setting multicast PIM policy.

Scenario: 2 multicast PIM sources.
Source 1 distributes:
239.254.0.1 - 239.254.255.254
224.2.2.0/24

Source 2 distributes:
239.254.0.1 - 239.254.127.254
224.2.2.0/24

I would like to use source 2 as priority for 239.254.0.1/17
and use source 1 for other half (as they overlap)
Also I would like to block source 2 from any use of 224.2.2.0/24 (no matter if source 1 is
available or not). Both sources are sending groups statically.

Anyone one know how to configure it  (I don't have access to source 1,2 switches)


vlan 3000
 description MulticastS1
vlan 3500
 description MulticastS2

interface Vlanif3210
 ip address 192.168.70.254 255.255.0.0
 ip address 192.168.90.254 255.255.255.252 sub
 pim sm
#
interface Vlanif3771
 ip address 192.168.50.254 255.255.252.0
 ip address 192.168.60.122 255.255.255.248 sub
 pim sm

pim
 static-rp 10.90.190.1



Featured Answers

Recommended answer

chenhui
Admin Created May 6, 2021 01:58:44

Hello Rafalg,
If you mean the PIM router hot backup, like the VRRP multi-process, the answer is no. The forwarding router in the same network will be elected by the PIM(Suppose the PIMv4 is implemented), and the elected PIM DR will forward the traffic, but the DR priority value cannot be set differently according to the ACL or multicast group.
For the last question, use the PIM source policy to deny the multicast source 224.2.2.0/24, please refer to https://support.huawei.com/hedex/hdx.do?docid=EDOC1100126530&id=EN-US_TASK_0177106489&lang=en
View more
  • x
  • convention:

All Answers

Hello,
Are the S67xx switches connect to the multicast client directly? Or are the switches working as the PIM router?

View more
  • x
  • convention:

Rafalg
Rafalg Created May 5, 2021 12:36:27 (0) (0)
Reply in last message. They are working only to transmit multicast over igmp snooping vlan, trunk port and this is connected to another network devices which does support igmp snooping, and at last one there is access port type where multicast if delivered.  
Rafalg
Rafalg Created May 5, 2021 12:36:40 (0) (0)
Reply in last message. They are working only to transmit multicast over igmp snooping vlan, trunk port and this is connected to another network devices which does support igmp snooping, and at last one there is access port type where multicast if delivered.  
Can you please explain how switches are connected?
View more
  • x
  • convention:

Rafalg
Rafalg Created May 5, 2021 12:34:23 (0) (0)
Theres igmp snooping enabled on some vlans to distribute milticast

vlan 2010
description Stream1
igmp-snooping enable

#
interface Vlanif2010
ip address 192.168.246.1 255.255.255.0
pim silent
pim sm
igmp enable
#


vlan 2010
description Stream1
igmp-snooping enable

#
interface Vlanif2011
ip address 192.168.247.1 255.255.255.0
pim silent
pim sm
igmp enable
#
vlan 2011
description Stream2
igmp-snooping enable

Clients are not directly connected. port  
Well, I think you need the IGMP snooping priority to control the switch to forward the multicast traffic.
For example, configure the SW1 a higher priority for some multicast group so that it could forward these multicast traffic.
Please refer to https://support.huawei.com/hedex/hdx.do?docid=EDOC1100126530&id=EN-US_TASK_0177107048&lang=en
View more
  • x
  • convention:

Rafalg
Rafalg Created May 5, 2021 16:45:48 (0) (0)
Thanks. My problem is resolved now partially. I can set like
acl number 2000
rule 5 deny source 225.1.1.4 0
rule 10 deny source 225.1.1.5 0
igmp-snooping group-policy 2000

But this doesn't priority source 1 or 2. Deny 224.2.2.0/24 would block both sources there, any trick to make it only for specific source only ?
Can you point me how to set "block source 2 from any use of 224.2.2.0/24 (no matter if source 1 is
available or not)"  
Hello Rafalg,
If you mean the PIM router hot backup, like the VRRP multi-process, the answer is no. The forwarding router in the same network will be elected by the PIM(Suppose the PIMv4 is implemented), and the elected PIM DR will forward the traffic, but the DR priority value cannot be set differently according to the ACL or multicast group.
For the last question, use the PIM source policy to deny the multicast source 224.2.2.0/24, please refer to https://support.huawei.com/hedex/hdx.do?docid=EDOC1100126530&id=EN-US_TASK_0177106489&lang=en
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.