Example: Continue rules in engine Access rules
An example of using Continue rules to set default options for several Engine Access rules.
Company B has decided to implement QoS Policies. The administrators want to set the QoS Class for traffic using a classification of high, medium, and low for all traffic depending on the sender. High priority is assigned to a few hosts in different networks, medium priority to one internal network, and low priority to all other hosts. The administrators want to follow how much traffic is allowed using the highest priority. Because of this, they also want to make sure that this traffic is logged with the accounting option turned on. They decide that the lower priorities of traffic don't need to be permanently logged at this point, so the administrators:
- Configure the QoS features.
- Create elements for all high-priority hosts.
- Add the following Access rules to the top of their policy:
Table 1. Continue rules for Logging and QoS Class Source Destination Service Action Logging QoS Class Important Hosts ANY ANY Continue Stored with accounting High priority Network element for Important Network ANY ANY Continue Transient Medium priority All other Hosts ANY ANY Continue Transient Low priority After adding these rules, individual rules can override the settings as needed. However, most of the existing rules governing access from internal networks to the Internet now use the QoS Class and Logging options as set in these rules.
- Transfer the policy to the engine.