Lab Objective
Observe the default SPT switchover behavior on R3 (the last-hop router from the previous lab), confirming it initially forwards traffic via the shared tree through the RP, then automatically switches to a direct shortest-path tree toward the source once the default SPT threshold is exceeded.
Lab Purpose
The previous lab established basic shared-tree forwarding through the RP. In real deployments, routing all traffic through the RP indefinitely is often suboptimal if the RP is not on the most direct path between source and receiver — PIM Sparse Mode's default behavior automatically optimizes this by switching the last-hop router to a direct path once traffic volume justifies the switch.
Lab Topology
Same topology as the previous lab:
Source ---- R1 ---- R2 (RP) ---- R3 ---- Receiver
Default SPT threshold is 0 kbps on
Cisco IOS, meaning the switchover happens
almost immediately upon the first packet
in many implementations -- this lab
demonstrates the mechanism explicitlyTask 1: Confirm the Initial Shared-Tree Forwarding State
Immediately after multicast traffic starts, examine R3's mroute table for evidence of shared-tree forwarding.
Task 2: Verify the SPT Switchover Occurs
After traffic has been flowing briefly, re-examine R3's mroute table for a new source-specific entry indicating a direct path has been built.
Task 3: Compare the RPF Interface Before and After Switchover
Confirm the RPF (Reverse Path Forwarding) interface for the source-specific entry differs from the shared-tree entry's incoming interface, if the direct path differs from the RP path.
Task 4: Verify the Shared Tree Entry Persists Alongside the New SPT Entry
Confirm the original (*, G) entry remains present even after the switchover, still used for signaling purposes.
Task 5: Understand the Flag Indicating SPT Status
Examine the flags on the mroute entries that specifically indicate SPT-related state.
Solution and Verification
Source> [begins sending multicast traffic
to 239.1.1.1]
-- Immediately after traffic starts:
R3# show ip mroute 239.1.1.1
(*, 239.1.1.1), uptime 00:05:20, RP is 2.2.2.2
Incoming interface: GigabitEthernet0/0
Outgoing interface list:
GigabitEthernet0/1, Forward
(Source-IP, 239.1.1.1), uptime 00:00:02
Incoming interface: GigabitEthernet0/0
Outgoing interface list:
GigabitEthernet0/1, Forward
-- Both entries already present -- since
-- the source and RP happen to be reached
-- via the same interface in this topology,
-- the switchover is not visually obvious
-- from the interface alone yetR3# show ip mroute 239.1.1.1 | include Flags
(*, 239.1.1.1), ..., flags: SJC
(Source-IP, 239.1.1.1), ..., flags: SJT
-- The "T" flag on the (S, G) entry
-- specifically indicates this entry is
-- using the Shortest-Path Tree -- its
-- absence on the (*, G) entry confirms
-- that one remains the shared-tree entryR1# show ip mroute 239.1.1.1
(Source-IP, 239.1.1.1), uptime 00:00:03, flags: FT
Incoming interface: GigabitEthernet0/0
Outgoing interface list:
GigabitEthernet0/1, Forward
-- R1 also shows the "T" flag, confirming
-- SPT forwarding is active along the path
-- closest to the source as wellR3# show ip mroute 239.1.1.1
(*, 239.1.1.1), uptime 00:10:45, RP is 2.2.2.2
Incoming interface: GigabitEthernet0/0
Outgoing interface list:
GigabitEthernet0/1, Forward
(Source-IP, 239.1.1.1), uptime 00:05:27, flags: JT
Incoming interface: GigabitEthernet0/0
Outgoing interface list:
GigabitEthernet0/1, Forward
-- The (*, G) shared-tree entry is STILL
-- present well after the switchover --
-- it remains for signaling purposes (a new
-- receiver joining would still need it),
-- while the (S, G) entry now actively
-- carries the real traffic via the SPTKey Takeaway
The "T" flag on an (S, G) mroute entry is the definitive indicator that traffic for that source is now forwarded via the Shortest-Path Tree rather than the RP-rooted shared tree — this switchover happens automatically and by default on Cisco IOS, and the persistence of the (*, G) entry afterward is not a leftover artifact but an intentional part of the design, since it continues serving any future receiver that joins the group through the shared tree before potentially triggering its own SPT switchover.