[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Global Classifiers and Wildcard Routing Instances

To configure a global routing instance classifier, include the all statement at the [edit class-of-service routing-instances] hierarchy level:



[edit class-of-service routing-instances]
all {



classifiers {

exp classifier-name;
}


}

For routing instances associated with specific classifiers, the global configuration is ignored.

To use a wildcard in the routing instance classifier configuration, include an asterisk (*) in the name of the routing instance:



[edit class-of-service routing-instances]

instance-name* {



classifiers {

exp classifier-name;
}


}

The wildcard configuration follows the longest match. If there is a specific configuration, it is given precedence over the wildcard configuration.

Note: Wildcards and the all keyword are supported at the [edit class-of-service routing-instances] hierarchy level but not at the [edit routing-instances] hierarchy level.

If you configure a routing instance at the [edit routing-instances] hierarchy level with, for example, the name vpn*, the JUNOS software treats vpn* as a valid and distinct routing instance name. If you then try to apply a classifier to the vpn* routing instance at the [edit class-of-service routing-instances] hierarchy level, the JUNOS software treats the vpn* routing instance name as a wildcard, and all the routing instances that start with vpn and do not have a specific classifier applied receive the classifier associated with vpn*. This same behavior applies with the all keyword.

[Contents] [Prev] [Next] [Index] [Report an Error]