утилита трассировки логической сети Open Virtual Network (Open Virtual Network logical network tracing utility)
STATEFUL ACTIONS
Some OVN logical actions use or update state that is not
available in the southbound database. ovn-trace
handles these
actions as described below:
ct_next
By default ovn-trace
treats flows as ``tracked''
and ``established.'' See the description of the
--ct
option for a way to override this behavior.
ct_dnat
(without an argument)
Forks the pipeline. In one fork, advances to the
next table as if next;
were executed. The packet is
not changed, on the assumption that no NAT state
was available. In the other fork, the pipeline
continues without change after the ct_dnat
action.
ct_snat
(without an argument)
This action distinguishes between gateway routers
and distributed routers. A gateway router is
defined as a logical datapath that contains an
l3gateway
port; any other logical datapath is a
distributed router. On a gateway router, ct_snat;
is treated as a no-op. On a distributed router, it
is treated the same way as ct_dnat;
.
ct_dnat(
ip)
ct_snat(
ip)
Forks the pipeline. In one fork, sets ip4.dst
(or
ip4.src
) to ip and ct.dnat
(or ct.snat
) to 1 and
advances to the next table as if next;
were executed.
In the other fork, the pipeline continues without
change after the ct_dnat
(or ct_snat
) action.
ct_lb;
ct_lb(
ip[:
port]...);
Forks the pipeline. In one fork, sets ip4.dst
(or
ip6.dst
) to one of the load-balancer addresses and
the destination port to its associated port, if any,
and sets ct.dnat
to 1. With one or more arguments,
gives preference to the address specified on
--lb-dst
, if any; without arguments, uses the address
and port specified on --lb-dst
. In the other fork,
the pipeline continues without change after the ct_lb
action.
ct_commit
put_arp
put_nd
These actions are treated as no-ops.