Configuration File Syntax
•Numeric attributes must be valid numbers for their presumed radix, and must be within the allowable range for the specific attribute.
•Host names must resolve to IP addresses.
•Blocks cannot be nested. The appearance of the keyword (adapter, policy, filter) that begins a block also implicitly terminates the previous block.
•Adapter names must correspond to PPA names that can be listed by the lanscan command at the time
•Filter and policy names must contain only letters, digits, and underscores.
•Filter names must be unique. No two filters can have the same name.
•Policy names must be unique. No two policies can have the same name.
•Filter and policy names are case sensitive. For example, if you defined a filter called filter1, you cannot refer to the filter as Filter1 in a policy. Filter1 is not equivalent to nor recognized as filter1.
•The maximum length for filter and policy names is 32 characters.
•You cannot refer to a filter or policy before that object has been defined. That is, forward referencing is not allowed.
•It is important to assign priorities to filters. Doing so ensures that, in cases where a packet matches the traffic class specified by more than one filter, the correct filter preference, indicated by the higher priority assignment, is applied.
•A filter can be attached to multiple policies, but can only be attached to one policy per adapter.
Since policies cause actions on filters’ traffic classes, only one action (policy) can be applied to a given traffic class (filter). In other words, there cannot be any ambiguity as to which policy applies to any packet transmitted from a specific adapter. Specifically, it is important to remember:
—A filter name can be referenced in multiple policies, but never more than once in a specific policy.
—A policy name can be referenced on multiple adapters, but never more than once for a specific adapter.
—No filter can be named in more than one of the policies that any adapter uses.
60 | Chapter 4 |