H3C Technologies H3C Intelligent Management Center - Manual (Page 57)

47
The instruction set specifies the actions to be executed on a packet that matches the flow entry.
The following instructions are in descending order of priority:
− Meter—Forward the packet to a specified meter for processing.
− Apply-Actions—Execute specified actions in the action list.
− Clear-Actions—Clear the action set of the packet.
− Write-Actions—Add specified actions to the action set of the packet. If an action of the
specified type exists in the action set, the added action overrides the original action. For
more information about the action set and the action list, see "
Configuring actions ."
− Write-Metadata—Write metadata into the metadata field of the packet. Metadata transmits
information between flow tables in a switch. It is used in packet matching.
− Goto-Table—Forward the packet to a specified flow table that has a larger ID than the
current flow table. The last flow table in the pipeline does not have this instruction.
Adding a flow entry
1. Access the flow entry list page.
2. In the flow entry list, click Add.
3. Specify the parameters in the Basic Information area:
{
Table ID—Enter the ID of the flow table to which the flow entry is added.
{
Match Field—Select match fields and specify the value of each match field. For more
information about match fields, see "
Match fields ." This parameter is optional.
{
Priority—Enter the priority of the flow entry.
{
Hard Timeout—Enter the lifetime of the flow entry in a flow table.
{
Idle Timeout—Enter the maximum idle time of the flow entry when no traffic matches the flow
entry.
− If the hard timeout is 0 and the idle timeout is set, the flow entry is deleted after the idle
timeout expires.
− If the hard timeout is set and the idle timeout is 0, the flow entry is deleted after the hard
timeout expires.
− If both the hard timeout and the idle timeout are set, the flow entry is deleted after either
timeout expires.
− If both the hard timeout and the idle timeout are 0, the flow entry never expires, but it can
be deleted by a controller.
{
Cookie—Enter a cookie value in hexadecimal format for the flow entry, in the range of 0x0 to
0x7fffffffffffffff. This parameter is optional.
{
Flags—Select flags for the flow entry. This parameter is optional.
− send_flow_rem—Send a notification message when the flow entry is deleted.
− check_overlap—Check for duplicate flow entries.
− reset_counts—Reset flow entry statistics.
− no_packet_counts—Disable the packet counter.
− no_byte_counts—Disable the byte counter.