https://github.com/vyos/vyos-1x/pull/243

PR https://github.com/vyos/vyos-1x/pull/242

from https://www.zabbix.com/documentation/current/manual/appendix/config/zabbix_agentd

Main question is how should the CLI be designed?

Added in commit https://github.com/vyos/vyatta-cfg-system/commit/0beae43d41a6bd8e1997c7a0013fb9263d7774f9 and then migrated to the XML/Python representation

Template for zabbix-server on base zabbix-agent checks (without SNMP).
Dynamically creates items and some graphs for:

• CPU
• Memory
• Cpu Cores
• Interfaces rate bps/pps
• Interfaces drops/errors
• State some services (OpenVPN/VRRP)
• Conntrack entries (used for nat)

Hi All, is there any movement on a fix for this? It would be great to get netflow data out of my PPPoE interfaces - happy to run any tests for you

PR https://github.com/vyos/vyatta-cfg-quagga/pull/44

We have this feature but with wrong logic.
https://github.com/vyos/vyatta-cfg-quagga/blob/current/scripts/bgp/vyatta-bgp.pl#L723

Related https://github.com/vyos/vyos-1x/pull/241

Having this feature would eliminate any use of vyatta-postconfig-bootup.script for me, which would lead to a "clean" vyos installation again.

Adding a dummy interface to VRF:

Adding interfaces to VRFs seems to be a bit of a hazzle:

Hi @rps ,
Very good summary of what is needed. I think what you state fits perfectly in our (and most) uses cases. We need to sync RAs with VRRP state, and we would need to use a "virtual IP" like fe80::1 to be announced to neighbors as the default gateway.
So for me makes absolutely sense, thanks for your effort!
If you need any help defining/testing, just let me know!

Quick win :) - you find the latest rolling to be fixed

thanks for the quick fix!

Issue introduced in T640 when we removed recommended packages. vyatta-op had a missing dependency on rsync.

@c-po can you look https://github.com/vyos/vyos-1x/pull/236

To dust off this one...

@Lochnair any chance you can translate this into Linux tc syntax?

Thanks! As an additional note from my testing: the check for DHCP settings in the config always returns false, even if the interface uses DHCP. This could easily be fixed by checking if the values of the node contain DHCP, but if we skip this interface it won't be brought back up, so I believe the current solution is the best, even though the DHCP check line is now redundant (I noticed you removed the check itself).

good point,
probably need to handle this via excluding such interfaces

@syncer One thing to consider. If dynamic interfaces are used and there are several thousand of them (ipoe/ppp), this will kill the server, if we try to pull this data.

Should be pretty straight forward once we have migrated vyatta-nat to XML/Python. On first glance the rewrite looks easy as it just operates on the NAT table.

@Viacheslav let's discuss
I think we need to implement template for the server (both SNMP based and agent-based)
Need to decide what we expose, but most likely, interfaces, VRRP, VPN metrics, etc
I also add this to collect user feedback

@dirkjanm added that script - it will be shipped with next rolling

One of the offeners is