Got it

Multicast Routing support Over DSVPN

Latest reply: Feb 13, 2020 08:47:45 963 15 0 0 0
This post was last edited by jumbox at 2018-12-11 14:28. Hi,
CASE:
Network - AR3200 - RE:Multicast support over DSVPN


HUAWEI ANSWERED:
RiskofSolution:Non-RiskOperation
We talked to R&D. We can not provide.



Why Not? You have solved split horizon issues over DSVPN, why not about PIM? Because of this issue instead using DSVPN, we have to create over hundred of thousands individual P2P GRE tunnels.
Thanks

jumbox
jumbox Created Dec 14, 2018 07:13:57 (0) (0)
Other well known vendors have solved this cavitie with solution of "pim nbma mode". The other problem is that, Huaweis answer is not explanatory. In Hub&Spoke topology where the problem is about PIM, they have to explained it well. Instead  
Nice idea
View more
  • x
  • convention:

No idea
View more
  • x
  • convention:

Its useful
View more
  • x
  • convention:

This post was last edited by jumbox at 2018-12-24 12:01. I was expecting more explanation from huawei multicast support over DSVPN but they just said that we dont support. But I ve tested the stuation and find out hub<->spoke multicast stream bidirectionaly working fine. In additionaly spoke<->spoke multicast is not working meanning not supported. For testing i did used ping and along side NTP Multicast Mode to distribute ntp information entire network.

As a summary huawei does support multicast over DSVPN between hub and spokes but not spoke to spoke.
 
From now Case solved and closed. In the future expecting that huawei to solve and implement spoke to spoke multicast support.

Thanks for yor deep knowledge and sharing it with us dear HUAWEİ :(
View more
  • x
  • convention:

Thanks you
View more
  • x
  • convention:

Great
View more
  • x
  • convention:

Good
View more
  • x
  • convention:

You have solved split horizon issues over DSVPN, why not about PIM? Because of this issue instead using DSVPN,Can you provide a more detailed explanation?
View more
  • x
  • convention:

jumbox
jumbox Created Jan 2, 2019 07:12:08 (0) (0)
Over hub and spoke topologies routing(RIP...vs) has problem which is the interface you received routing updates dont send them back to same interface split horizon rule. So hub & spoke enviroment for spoke to spoke conversation splithorizon has to be 
jumbox
jumbox Reply jumbox  Created Jan 2, 2019 10:15:01 (0) (0)
So hub & spoke enviroment for spoke to spoke conversation splithorizon has to be disabled.
Same case apply for multicast routing and traffic. So when hub receives multicast rp&ma updates or traffic, it will not send it back to through same interf 
jumbox
jumbox Reply jumbox  Created Jan 2, 2019 10:19:20 (0) (0)
There has to be mechanism to enable receiving and sending updatest or traffic on same interface back and forward like nbma mode does...  
Posted by jumbox at 2018-12-24 11:57 I was expecting more explanation from huawei multicast support over DSVPN but they just said that we ...
Hi @jumbox
the static mGRE tunnel established between hub and spoke, the multicast stream bidirectionaly could work fine on such tunnel due to the GRE tunnel could carry multicast traffic. But for mGRE tunnel established between spoke and spoke, it's no longer a static mGRE instead of dynamic mGRE tunnel, so, I would be more inclined to the multicast cannot transceived on the dynamic mGRE tunnel rather than the horizon-split causing the multicast traffic discarded.
As you know, in DSVPN network, the traffic between two spoke sites are transceived on the temporary dynamic mGRE tunnel, they wouldn't be sent to hub site, so your explanation about the reason of multicast traffic discarded between two spoke sites are the horizon split might be incorrect.
View more
  • x
  • convention:

jumbox
jumbox Created Oct 11, 2021 12:15:58 (0) (0)
Thanks for your explanation @chenhui. But This answer and explanation came out too late for me. Because of your support told us multicast is not supported over dsvpn, along the side we already deployed the network with p2p gre. However ive tested dsvpn supportion of multicast, and success.
Spoke-to-spoke doesnt work because there is no direct connection between spokes. So whenever L3 to L2 resolution happens it fails because spokes doesnt directly connected.  
jumbox
jumbox Created Oct 11, 2021 12:19:15 (0) (0)
So we only needed to hub and spoke multicast of course it depends how you design Mapping Agent and Randevu Point..If you put both role on hub everything works fine...
take care  

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.