Verification
Once the network has been configured, you need to test that it works as expected. Use the following CLI commands on the devices indicated.
Verifying if RTR1 receives loopback subnet of FGT4
(RTR1) # get router info routing-table all
Result:
C 10.1.1.0/24 is directly connected, vlan1
C 10.2.2.0/24 is directly connected, vlan2
C 10.10.10.0/24 is directly connected, dmz1
R 10.40.40.0/24 [120/2] via 10.10.10.1, dmz1, 00:04:07
R 10.50.50.0/24 [120/2] via 10.10.10.1, dmz1, 00:04:07
R 10.60.60.1/32 [120/2] via 10.10.10.1, dmz1, 00:04:07
(*) If required, filtering out 10.50.50.0 and 10.40.40.0 from the routing table could be done with a route-map.
Verification on FGT2, which is the border between L1 and L2 routing levels; looking at IS-IS information
FGT2 # get router info isis interface
Result:
FGT2 # get router info isis neighbor
Result:
Verification on FGT3, which is border between 2 areas; looking at IS-IS information
IS-IS router CLI commands available:
FGT3 # get router info isis ?
Result:
interface show isis interfaces
neighbor show CLNS neighbor adjacencies
is-neighbor show IS neighbor adjacencies
database show IS-IS link state database
route show IS-IS IP routing table
topology show IS-IS paths
Example of interface status and neighbors:
FGT3 # get router info isis interface
Result:
FGT3 # get router info isis neighbor
Result:
1721.0160.1004 ...dmz1 ......0009.0f52.7704 . . ..Up ..8 ............L2 .....IS-IS
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: