Description

This KB explains the group configuration for routing-instance.

Symptoms

Groups configured at global routing-instance are not inherited in routing-instances

Solution

For the group configs to be inherited, it needs to be called out under the routing-instance specifically.
For eg: if an ISIS parameters needs to be applied on interface under routing instance, then the config should be as follows.
 

set groups <> routing-instances <> protocols isis <>
set groups <> routing-instances <> apply-groups <>
set groups <> routing-instances <> protocols isis interface <*> level 1 disable
set groups <> routing-instances <> protocols isis interface <*> csnp-interval 10
set groups <> routing-instances <> protocols isis interface <*> point-to-point
set groups <> routing-instances <> protocols isis interface <*> family inet bfd-liveness-detection minimum-interval 1000
set groups <> routing-instances <> protocols isis interface <*> family inet bfd-liveness-detection multiplier 3
set groups <> routing-instances <> protocols isis interface <*> family inet6 bfd-liveness-detection minimum-interval 1000
set groups <> routing-instances <> protocols isis interface <*> family inet6 bfd-liveness-detection multiplier 3
set routing-instances <> protocols isis interface <> apply-groups <>

 

 
and to verify if the group configs have been inherited
show routing-instances <> protocols isis interface <> | display inheritance

Modification History

2026-07-08 : Article Created