ovn-detrace(1)

πŸ’– ovn-detrace β€” the manual page, but make it make sense πŸ’–

okay bestie, gather round, because this is the ovn-detrace page from the OVN Manual and it's genuinely one of the most useful little tools in the whole OVN cinematic universe. no cap. πŸ¦‹


✨ NAME ✨

ovn-detrace β€” the icon that converts ovs-appctl ofproto/trace output so it also shows you the OVN logical flow info. it's giving translator. it's giving "let me explain what that trace actually meant". πŸ’…


🌸 SYNOPSIS 🌸

ovn-detrace < file

and the common options, which are basically the standard little duo everyone gets:

[-h | --help] [-V | --version]

πŸ’œ DESCRIPTION πŸ’œ

so here's the vibe. ovn-detrace reads ovs-appctl ofproto/trace output from stdin, and it goes looking for flow cookies. πŸͺ for every cookie it finds, it shows you the OVN southbound records that contributed to that cookie being created. like, it does the detective work so you don't have to.

and it doesn't stop there β€” when it applies, it also shows you the related north-bound information. for example: the ACL that generated the logical flow, which then got translated into an OpenFlow rule with a given cookie. so you can trace the whole glow-up from the ACL all the way down. πŸ”₯

it's literally the plot of a mystery novel but the detective is you and the mystery is your own flow tables.


πŸ‘‘ OPTIONS πŸ‘‘

  • -h, --help β€” prints a brief help message to the console. short, sweet, helpful. the bare minimum and we respect it. πŸŽ€
  • -V, --version β€” prints version information to the console. iykyk.
  • --ovnsb=server β€” the OVN Southbound DB remote to contact. if the OVN_SB_DB environment variable is set, its value gets used as the default. otherwise the default is unix:@RUNDIR@/ovnsb_db.sock, **but heads up: that default is unlikely to be useful outside of single-machine OVN test environments. so don't be surprised when it doesn't magically find your cluster, bestie. πŸ™ˆ
  • *--ovnnb=server* β€” the OVN Northbound DB remote to contact. if the OVN_NB_DB environment variable is set, its value gets used as the default. otherwise the default is unix:@RUNDIR@/ovnnb_db.sock, and again β€” that default is unlikely to be useful outside of single-machine OVN test environments. same energy, other database. ✨
  • --ovs β€” also decode flow information (like OVS ofport) from the flows by connecting to the OVS DB. basically: more info, more context, more slay. 🌈
  • --no-leader-only β€” connect to any cluster member, not just the leader. this option works for the OVN Southbound DB and the OVN Northbound DB. so if you're not feeling picky about who you talk to, this is your girl. πŸ’«
  • --ovsdb=server β€” the OVS DB remote to contact **if --ovs is present. if the OVS_RUNDIR environment variable is set, its value gets used as the default. otherwise the default is unix:@RUNDIR@/db.sock, but (say it with me) that default is unlikely to be useful outside of single-machine OVN test environments. πŸ’€
  • -p privkey.pem, *--private-key=privkey.pem* β€” specifies a PEM file containing the private key used as ovn-detrace's identity for outgoing SSL/TLS connections. it's her little ID card. 🫢
  • -c cert.pem, --certificate=cert.pem β€” specifies a PEM file containing a certificate that certifies the private key specified on -p or --private-key to be trustworthy. that certificate **must be signed by the certificate authority (CA) that the peer in SSL/TLS connections will use to verify it. no shortcuts, the CA said what it said. πŸ“œ
  • -C cacert.pem, *--ca-cert=cacert.pem* β€” specifies a PEM file containing the CA certificate that ovn-detrace should use to verify certificates presented to it by SSL/TLS peers. (this may be the same certificate that SSL/TLS peers use to verify the certificate specified on -c or --certificate, or it may be a different one β€” it all depends on the PKI design in use.) flexible, but on purpose. 🧚

🌟 SEE ALSO 🌟

ovs-appctl(8), ovn-sbctl(8), ovn-nbctl(8), ovn-trace(8)

go read those too, they're the supporting cast and honestly? they ate. πŸ’–


ngl, remember: the whole thing reads from stdin, so pipe that trace in. ovn-detrace < file is the whole assignment. 🎯

okay that's the page!! and for the cute sign-off: this one's from OVN, version 26.09.1, dated 26.09.1 β€” so go forth and trace your flows, main character. πŸ’…βœ¨πŸ¦‹πŸŒΈπŸ‘‘

πŸ“¦ where this page comes from
  • fedora 44: ovn 26.09.0-33.fc44 Β· Apache-2.0 AND LGPL-2.1-only AND SISSL
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms