<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open vSwitch on Netdata</title><link>https://www.netdata.cloud/tags/open-vswitch/</link><description>Recent content in Open vSwitch on Netdata</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.netdata.cloud/tags/open-vswitch/index.xml" rel="self" type="application/rss+xml"/><item><title>Open vSwitch Monitoring</title><link>https://www.netdata.cloud/monitoring-101/openvswitch-monitoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/monitoring-101/openvswitch-monitoring/</guid><description>&lt;h2 id="open-vswitch-monitoring"&gt;Open vSwitch Monitoring&lt;/h2&gt;&#10;&lt;h3 id="what-is-open-vswitch"&gt;What Is Open vSwitch?&lt;/h3&gt;&#10;&lt;p&gt;Open vSwitch (OVS) is a multilayer software switch used in virtualized environments to manage network traffic. It is designed to enable network automation through programmatic extensions, while supporting standard management interfaces. OVS plays a significant role in creating highly scalable distributed networking environments.&lt;/p&gt;&#10;&lt;h3 id="monitoring-open-vswitch-with-netdata"&gt;Monitoring Open vSwitch With Netdata&lt;/h3&gt;&#10;&lt;p&gt;Monitoring Open vSwitch with Netdata is a straightforward process which can greatly enhance your understanding of network performance and reliability. Netdata utilizes an &lt;a href="https://github.com/digitalocean/openvswitch_exporter"&gt;OpenMetrics (Prometheus) exporter&lt;/a&gt; specifically designed for Open vSwitch, allowing users to collect and visualize key network metrics in real-time. Notably, Netdata does not require a separate Prometheus server or Grafana, simplifying the deployment process. Once data is collected, users receive automated dashboards and alerts, enabling proactive troubleshooting and network optimization.&lt;/p&gt;</description></item><item><title>Stale FDB/MAC tables: why endpoint location is wrong</title><link>https://www.netdata.cloud/guides/network/network-fdb-mac-staleness/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/guides/network/network-fdb-mac-staleness/</guid><description>&lt;p&gt;Your topology platform says endpoint &lt;code&gt;aa:bb:cc:dd:ee:ff&lt;/code&gt; is on switch port &lt;code&gt;Gi1/0/24&lt;/code&gt;. Your security team sends someone to that port. The endpoint is not there. It moved hours ago, or it went offline, or it vMotioned to a different host. The FDB entry was stale and the platform presented it as current.&lt;/p&gt;&#10;&lt;p&gt;The Forwarding Database (FDB), also called the MAC address table or CAM table, maps MAC addresses to switch ports. Topology inference engines use FDB data, cross-referenced with ARP tables and CDP/LLDP neighbor data, to deduce where endpoints are physically connected. The inference is probabilistic. It degrades as input data freshness degrades.&lt;/p&gt;</description></item></channel></rss>