How to prevent the default route in isis protocol from entering the global routing table?

In the setting of two edge routers and two core routers with mesh connectivity, edge routers have the following configs

set policy prefix-list default-prefix4 description 'Default Route v4'
set policy prefix-list default-prefix4 rule 10 action 'permit'
set policy prefix-list default-prefix4 rule 10 prefix '0.0.0.0/0'

set policy route-map REDIS__DEFAULT4 rule 10 action 'permit'
set policy route-map REDIS__DEFAULT4 rule 10 match ip address prefix-list 'default-prefix4'

set protocols isis default-information originate ipv4 level-2 always
set protocols isis redistribute ipv4 static level-2 route-map 'REDIS__DEFAULT4'

Unfortunately, the default route originated from the edge routers to the core routers comes back to the edge routers and enters the edge routers’ global routing tables. How to prevent it? Thanks!

What about adding filter for “zebra” do not install default route match some route-map?

Thanks @Viacheslav! Would you mind to recommend VyOS sample configs for filtering it out? I was not able to find config commands for using route-map with protocol isis. Thanks!

Check under this path set system ip protocol isis

1 Like

Thanks @Viacheslav! It works. The default route from isis is inactive, still shows up in the global routing table though.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.