Verification on FGT4 that the remote subnets from RTR1 and RTR2 are in the routing table and learned with IS-IS

FGT4 # get router info routing-table all

Result:

Codes: K – kernel, C – connected, S – static, R – RIP, B – BGP

O – OSPF, IA – OSPF inter area

N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2

E1 – OSPF external type 1, E2 – OSPF external type 2

i – IS-IS, L1 – IS-IS level-1, L2 – IS-IS level-2, ia – IS-IS inter area

* – candidate default

i L2 10.1.1.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46

i L2 10.2.2.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46

i L2 10.3.3.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46

i L2 10.4.4.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46

i L2 10.10.10.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46

i L2 10.11.11.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46 i L2 10.20.20.0/24 [115/30] via 10.50.50.1, wan1, 00:12:46 i L2 10.30.30.0/24 [115/30] via 10.50.50.1, wan1, 00:13:55 i L2 10.40.40.0/24 [115/20] via 10.50.50.1, wan1, 00:15:30

C 10.50.50.0/24 is directly connected, wan1

C 10.60.60.1/32 is directly connected, loopback

Troubleshooting

The following diagnose commands are available for further IS-IS troubleshooting and will display all IS-IS activity (sent and received packets):

FGT # diagnose ip router isis level info FGT # diagnose ip router isis all enable FGT # diagnose debug enable …to stop the debug type output:

FGT # diagnose ip router isis level none

Output and interpretation depends on the issue faced. You can provide this information to TAC if you open a support ticket.