◦ The choice operator “|” to express multiple match expressions within a regular expression is not
supported. For example, these expressions are not supported:
Gig.*|Gig.*\..*—To match on either Gigabit Ethernet main interfaces or Gigabit Ethernet
sub-interfaces.
Gig.*0/0/0/[1-5]|Gig.*0/0/0/[10-20]—To match on either Gig.*0/0/0/[1-5] or
Gig.*0/0/0/[10-20].
'TenGigE.*|POS.*—To match on either TenGigE.* or POS.* .
•
Commands that require a node identifier for the location keyword are not supported. For example, this
configuration is not supported:
lpts pifib hardware police location 0/0/CPU0
•
Overlapping regular expressions within a configuration group for the same configuration are not supported.
For example:
group G-INTERFACE
interface 'gig.*a.*'
mtu 1500
!
interface 'gig.*e.* '
mtu 2000
!
end-group
interface gigabitethernet0/4/1/0
apply-group G-INTERFACE
This configuration is not permitted because it cannot be determined whether the interface
gigabitethernet0/4/1/0 configuration inherits mtu 1500 or mtu 2000. Both expressions in the
configuration group match gigabitethernet0/4/1/0.
•
Up to eight configuration groups are permitted on one apply-group command.
Configuring a Configuration Group
A configuration group includes a series of configuration statements that can be used in multiple hierarchical
levels in the router configuration tree. By using regular expressions in a configuration group, you can create
generic commands that can be applied in multiple instances.
Use this task to create and use a configuration group.
Flexible CLI configurations are not available through the XML interface.Note
Cisco ASR 9000 Series Aggregation Services Router System Management Configuration Guide, Release 5.1.x
131
Configuring Flexible Command Line Interface Configuration Groups
Configuring a Configuration Group