Hello
When I execute the command for a multicast address for instance : "get router info multicast PIM dense-mode table 239.2.10.10" the Upstream IF is not what I attend and the the upstream state is pruned.
My logical configuration (see the picture) is composed by 4 nodes (firewall 600D) PIM enabled using between them GRE tunnels in a HUB and SPOKE architecture. Each Spoke send multicast packet to both HUBs by GRE.
The Upstream IF sometime are not the GRE tunnels that the spokes use to send multicast .
Any configuration to force the spokes to use only a specific GRE between spoke to hubs? RPF seems ignore static routing and policies.
Policies and static routing have been configured but RPF neighbor is sometime wrong. What do I need to use? Policy routing?
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hello parbieri,
I hope you are good :)!
Thank you for using the Community Forum.
As usual, I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.
Regards,
Hello parbieri,
I have found this KB article:
Could you please tell me if it is helping?
Regards,
Thank you very much ! Very useful for troubleshooting. I found the solution, the clients was not able to join the multicast group in good manner. PIM was not to work correctly. I forced inside the firewall the instructions to join the group:
config router multicast-flow edit {name} # Configure multicast-flow. set name {string} Name. size[35] set comments {string} Comment. size[127] config flows edit {id} # Multicast-flow entries. set id {integer} Flow ID. range[0-4294967295] set group-addr {ipv4 address any} Multicast group IP address. set source-addr {ipv4 address any} Multicast source IP address. next next end
Hello parbieri,
I hope you are good :)!
Thank you for using the Community Forum.
As usual, I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.
Regards,
Thank you very much ! Very useful for troubleshooting. I found the solution, the clients was not able to join the multicast group in good manner. PIM was not to work correctly. I forced inside the firewall the instructions to join the group:
config router multicast-flow edit {name} # Configure multicast-flow. set name {string} Name. size[35] set comments {string} Comment. size[127] config flows edit {id} # Multicast-flow entries. set id {integer} Flow ID. range[0-4294967295] set group-addr {ipv4 address any} Multicast group IP address. set source-addr {ipv4 address any} Multicast source IP address. next next end
Hello parbieri,
I have found this KB article:
Could you please tell me if it is helping?
Regards,
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1696 | |
1091 | |
752 | |
446 | |
228 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.