hi,
http://www.juniper.net/techpubs/en_US/junos9.6/information-products/topic-collections/swconfig-cli/understanding-the-JUNOS-configuration-groups.html#jd0e15416 says:
You can also use wildcards in a configuration group to allow configuration data to be inherited by any object that matches a wildcard expression
So, you can use wildcards to match any existing object, not to add objects matching wildcard.
As you noticed, your config will not work:
admin@gw# show groups isis-interfaces
protocols {
isis {
interface <fe-0/1/*.*> {
passive;
}
}
}
admin@gw# show protocols isis
apply-groups isis-interfaces;
[edit]
admin@gw#
admin@gw# show protocols isis | display inheritance
[edit]
The same group applied to modified isis configuration, changes configuration of matching interfaces:
admin@gw# show protocols isis
apply-groups isis-interfaces;
interface fe-0/1/2.123;
interface fe-0/1/3.456;
interface fe-1/0/0.789;
[edit]
admin@gw# show protocols isis | display inheritance
interface fe-0/1/2.123 {
##
## 'passive' was inherited from group 'isis-interfaces'
##
passive;
}
interface fe-0/1/3.456 {
##
## 'passive' was inherited from group 'isis-interfaces'
##
passive;
}
interface fe-1/0/0.789;
[edit]
It's possible to use group to add interfaces to isis protocol, but we can't use wildcards in interface names:
admin@gw# show groups isis-add-interfaces
protocols {
isis {
interface fe-0/1/2.222;
interface fe-0/1/3.333;
}
}
[edit]
admin@gw# show protocols isis
apply-groups isis-add-interfaces;
[edit]
admin@gw# show protocols isis | display inheritance
##
## 'fe-0/1/2.222' was inherited from group 'isis-add-interfaces'
##
interface fe-0/1/2.222;
##
## 'fe-0/1/3.333' was inherited from group 'isis-add-interfaces'
##
interface fe-0/1/3.333;
[edit]
admin@gw#
Anyway, I see no gain here and prefer to add the interfaces explicitly under protocol isis and have full control.
It's also possible to add 'interface all' under isis and use group to add 'family iso' only to interfaces matching wildcard.
jtb