<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/interface-definitions/system-sflow.xml.in, branch feature/T9082-codeql-cpp</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2023-12-31T22:49:48+00:00</updated>
<entry>
<title>T5474: establish common file name pattern for XML conf mode commands</title>
<updated>2023-12-31T22:49:48+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-12-30T22:25:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=4ef110fd2c501b718344c72d495ad7e16d2bd465'/>
<id>urn:sha1:4ef110fd2c501b718344c72d495ad7e16d2bd465</id>
<content type='text'>
We will use _ as CLI level divider. The XML definition filename and also
the Python helper should match the CLI node.

Example:
set interfaces ethernet -&gt; interfaces_ethernet.xml.in
set interfaces bond -&gt; interfaces_bond.xml.in
set service dhcp-server -&gt; service_dhcp-server-xml.in
</content>
</entry>
<entry>
<title>T5226: Combine ipv4-address and ipv6-address validators</title>
<updated>2023-05-17T04:10:36+00:00</updated>
<author>
<name>Indrajit Raychaudhuri</name>
<email>irc@indrajit.com</email>
</author>
<published>2023-05-17T01:49:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=96d846d27ac818ee9a23bb7194bb58cfb7093387'/>
<id>urn:sha1:96d846d27ac818ee9a23bb7194bb58cfb7093387</id>
<content type='text'>
Use a single ip-address validator to combine and replace ipv4-address
and ipv6-address validators.
</content>
</entry>
<entry>
<title>xml: include building block file name should end with .i and not .in</title>
<updated>2023-04-01T11:14:30+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-04-01T11:14:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=2265bb4dc27965da3dce7e3f476366b7d1e911f3'/>
<id>urn:sha1:2265bb4dc27965da3dce7e3f476366b7d1e911f3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T5086: Add sFlow drop-monitor-limit option</title>
<updated>2023-03-17T12:43:13+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-03-17T12:38:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=57c06dcd78f9b711c4fb46e6657b0a496059a685'/>
<id>urn:sha1:57c06dcd78f9b711c4fb46e6657b0a496059a685</id>
<content type='text'>
hsflowd will export the headers of dropped packets (along with the
name of the function in the Linux kernel where that skb was dropped)
as part of the standard sFlow feed.
This measurement complements the sFlow packet sampling and
counter-telemetry well because it provides visibility into the
traffic that is not flowing.
Very helpful for troubleshooting.
The limit (a rate limit max of N drops per second sent out in the
sFlow datagrams) is the parameter you would set in the CLI.

set system sflow drop-monitor-limit 50
</content>
</entry>
<entry>
<title>T5086: Add sFlow feature based on hsflowd</title>
<updated>2023-03-16T10:17:39+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-03-14T18:45:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=707641f4dc947bce84eeff5499665e1cf76d7806'/>
<id>urn:sha1:707641f4dc947bce84eeff5499665e1cf76d7806</id>
<content type='text'>
Add sFlow feature based on hsflowd
According to user reviews, it works more stable and more productive
than pmacct
I haven't deleted 'pmacct' 'system flow-accounting sflow' yet
It could be migrated or deprecated later

  set system sflow agent-address '192.0.2.14'
  set system sflow interface 'eth0'
  set system sflow interface 'eth1'
  set system sflow polling '30'
  set system sflow sampling-rate '100'
  set system sflow server 192.0.2.1 port '6343'
  set system sflow server 192.0.2.11 port '6343'
</content>
</entry>
</feed>
