Alcatel-Lucent 7950 Quality Of Service Manual page 117

be explicitly reclassified to either in-profile or out-of-profile.
Syntax entry entry-id [create]
no entry entry-id
Context config>qos>network>ingress>ip-criteria
config>qos>network>ingress>ipv6-criteria
Description This command is used to create or edit an IP or IPv6 criteria entry for the policy. Multiple entries
can be created using unique entry-id numbers.
The list of flow criteria is evaluated in a top down fashion with the lowest entry ID at the top and
the highest entry ID at the bottom. If the defined match criteria for an entry within the list matches
the information in the ingress packet, the system stops matching the packet against the list and
performs the matching entries reclassification actions. If none of the entries match the packet, the
IP flow reclassification list has no effect on the packet.
An entry is not populated in the list unless the action command is executed for the entry. An entry
that is not populated in the list has no effect on ingress packets. If the action command is executed
without any explicit reclassification actions specified, the entry is populated in the list allowing
packets matching the entry to exit the list, preventing them from matching entries lower in the list.
Since this is the only flow reclassification entry that the packet matched and this entry explicitly
states that no reclassification action is to be performed, the matching packet will not be
reclassified.
The no form of this command removes the specified entry from the policy. Entries removed from
the policy are immediately removed from all services where that policy is applied.
Default
none
Parameters
entry-idThe entry-id, expressed as an integer, uniquely identifies a match criterion and the
corresponding action. It is recommended that multiple entries be given entry-ids in staggered
increments. This allows users to insert a new entry in an existing policy without requiring renumbering
of all the existing entries.
Values
Default
create — Required parameter when creating a flow entry when the system is configured to require the
explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created
when this protection is disabled and an object name is mistyped when attempting to edit the object. This
keyword is not required when the protection is disabled. The keyword is ignored when the flow entry
already exists.
7950 XRS Quality of Service Guide
An entry cannot have any match criteria defined (in which case, everything matches) but
must have at least the keyword action fc fc-name profile {in | out}] for it to be considered
complete. Entries without the action keyword will be considered incomplete and hence
will be rendered inactive.1— 65535
none
entry
Page 117