This article explains how to use a Command Line Interface Command (CLI) command to verify indirect-next-hop support on MX Series routers with the MPC card.
By default, the Junos Trio Modular Port Concentrator (MPC) chipset on MX Series routers is enabled with indirectly connected next hops. It cannot be disabled by using the no-indirect-next-hop statement.
no-indirect-next-hop
A hidden command can be used to check that:
user@router-re0> show krt indirect-next-hop Indirect Nexthop: Index: 1048574 Protocol next-hop address: 101.1.1.1 RIB Table: inet.0 Policy Version: 2 References: 3 Locks: 3 0x7c123c0 Flags: 0x2 INH Session ID: 0x147 INH Version ID: 0 Ref RIB Table: unknown Next hop: 172.1.1.2 via xe-0/0/0.0 weight 0x1 Session Id: 0x143 IGP FRR Interesting proto count : 3 Chain IGP FRR Node Num : 1 IGP Resolver node(hex) : 0x44a3670 IGP Route handle(hex) : 0x4452bf0 IGP rt_entry protocol : OSPF IGP Actual Route handle(hex) : 0x0 IGP Actual rt_entry protocol : Any
You can use the show route forwarding-table command to show indirect-next-hop support.
show route forwarding-table
user@router-re0> show route forwarding-table Routing table: default.inet Internet: Enabled protocols: Bridging, Destination Type RtRef Next hop Type Index NhRef Netif default user 0 dscd 34 56 default perm 0 rjct 36 1 0.0.0.0/32 perm 0 dscd 34 56 1.0.0.0/24 user 0 indr 1054808 11236 <<<<<<-this showing that indirect-next-hop support ulst 1059871 2 10.55.40.67 Push 649980 152242 2 xe-1/0/0.0 10.55.40.51 Push 775512 70222 2 xe-1/0/1.0 10.55.40.69 Push 649980 152243 2 xe-2/0/1.0
2021-06-08: Modified Solution section to detail an alternative command that can be used for the same purpose