FortiGate PIM-SM debugging examples

Viewing the multicast routing table (FGT-2)

If you check the output on FGT-2 there are some small differences:

FGT-2 # get router info multicast pim sparse-mode table

IP Multicast Routing Table

(*,*,RP) Entries: 0 (*,G) Entries: 1 (S,G) Entries: 1 (S,G,rpt) Entries: 1

FCR Entries: 0

(*, 239.255.255.1) RP: 192.168.1.1

RPF nbr: 0.0.0.0

RPF idx: None

Upstream State: JOINED Local:

Joined: external Asserted: FCR:

The *,G entry now has a joined interface rather than local because it has received a PIM join from FGT-3 rather than a local IGMP join.

(10.166.0.11, 239.255.255.1) RPF nbr: 10.130.0.237

RPF idx: internal

SPT bit: 1

Upstream State: JOINED Local:

Joined: external Asserted: Outgoing: external

The S,G entry shows that we have received a join on the external interface and the stream is being forwarded out of this interface.

(10.166.0.11, 239.255.255.1, rpt) RP: 192.168.1.1

RPF nbr: 0.0.0.0

RPF idx: None

Upstream State: PRUNED Local:

Pruned: Outgoing: External

The S,G,RPT is different from FGT-3 because FGT-2 is the RP, it has pruned back the SPT for the RP to the first hop router.

This entry was posted in FortiOS 5.4 Handbook and tagged , , on by .

About Mike

Michael Pruett, CISSP has a wide range of cyber-security and network engineering expertise. The plethora of vendors that resell hardware but have zero engineering knowledge resulting in the wrong hardware or configuration being deployed is a major pet peeve of Michael's. This site was started in an effort to spread information while providing the option of quality consulting services at a much lower price than Fortinet Professional Services. Owns PacketLlama.Com (Fortinet Hardware Sales) and Office Of The CISO, LLC (Cybersecurity consulting firm).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.