---

   ovs-actions    ( 7 )

---

OTHER ACTIONS

The conjunction action Syntax: conjunction(id, k/n)

This action allows for sophisticated ``conjunctive match'' flows. Refer to ``Conjunctive Match Fields'' in ovs-fields(7) for details.

A flow that has one or more conjunction actions may not have any other actions except for note actions.

Conformance:

Open vSwitch 2.4 introduced the conjunction action and conj_id field. They are Open vSwitch extensions to OpenFlow.

The note action Syntax: note:[hh]...

This action does nothing at all. OpenFlow controllers may use it to annotate flows with more data than can fit in a flow cookie.

The action may include any number of bytes represented as hex digits hh. Periods may separate pairs of hex digits, for readability. The note action's format doesn't include an exact length for its payload, so the provided bytes will be padded on the right by enough bytes with value 0 to make the total number 6 more than a multiple of 8.

Conformance:

This action is an extension to OpenFlow introduced in Open vSwitch 1.1.

The sample action Syntax: sample(argument...)

Samples packets and sends one sample for every sampled packet.

The following argument forms are accepted:

probability=packets The number of sampled packets out of 65535. Must be greater or equal to 1.

collector_set_id=id The unsigned 32-bit integer identifier of the set of sample collectors to send sampled packets to. Defaults to 0.

obs_domain_id=id When sending samples to IPFIX collectors, the unsigned 32-bit integer Observation Domain ID sent in every IPFIX flow record. Defaults to 0.

obs_point_id=id When sending samples to IPFIX collectors, the unsigned 32-bit integer Observation Point ID sent in every IPFIX flow record. Defaults to 0.

sampling_port=port Sample packets on port, which should be the ingress or egress port. This option, which was added in Open vSwitch 2.5.90, allows the IPFIX implementation to export egress tunnel information.

ingress egress Specifies explicitly that the packet is being sampled on ingress to or egress from the switch. IPFIX reports sent by Open vSwitch before version 2.5.90 did not include a direction. From 2.5.90 until 2.6.90, IPFIX reports inferred a direction from sampling_port: if it was the packet's output port, then the direction was reported as egress, otherwise as ingress. Open vSwitch 2.6.90 introduced these options, which allow the inferred direction to be overridden. This is particularly useful when the ingress (or egress) port is not a tunnel.

Refer to ovs-vswitchd.conf.db(5) for more details on configuring sample collector sets.

Conformance:

This action is an OpenFlow extension added in Open vSwitch 2.4.