Refer to the Exhibit.
In the exhibit, R2 is receiving external routing information for the 192.168.16.0/24 prefix and is
redistributing it into IS-IS. R1 has a policy that leaks the 192.168.16.0/24 route into Area 49.1111.
R3 has a policy that leaks the 192.168.16.0/24 route into Area 49.2222. However, the IS-IS
version of the route does not appear in R2’s routing table.
Why does R3’s route leaking policy appear not to be working?
The Up/Down bit is set to down for the prefix.
The external flag is set for the prefix.
You can only leak routes from Level 2 to Level 1.
R2 already has better routing information for the prefix.