Yes 100% correct!
But having only a single switch and LACP/etc. stil is a SPOF on the switch, thus the idea is/was to have the direct linked interfaces too, as we are moving towards a leaf-spline/"CLOS". Even more "fun" is when that swith ports dis connect, you "lose" (interface down) the IP...
yeah, there are a coupld of those that only matches IPv4 (assumptions?) in stead of both IPv6/IPv4, but the "fun" is that (ie. OSPF/BGP IDs) are 32bit, and thus "assumed"/simplified as 4x octets, and then "typically" using the loopback/highest IP as the ID (assumptions) so ... yeah, IPv6...
True,
I'm looking at it from the perspective of a switch/network link failure , so that is an extra link...
Og, OpenFabric routing protocol doesn't work with more than 2 nodes on the same link - design criteria
Question: Have you tested/used OpenFabric with more than 2 nodes on the same interface (ie. a vlan/ethernet switch)? ran into a problem which I suspect makes it outside of OpenFabrics design criteria, so as I've implemented your stuff, it worked, but then found troubles on the links where there...
Something I am missing, is a pre & post FRR config (perhaps templates that have values/numbers filled in from the GUI/SDN configuration like the ISIS process/router name, ASN numbers etc.). Loading those into/via vtysh/yang/etc., would ease custom and north-south configurations and...
Good day,
I have new set of clusters to be deployed in environments where I do have needs for SDN (vxlan-evpn) and loopback routes for CEPH while preparing for IPv6 only networks. Though I did got it going at one stage (IPv4 only), there are still missing pieces/processes that I'm stumbling on...
oh, and there are another "bug" in the parsing/do of the Network ID of the ISIS plugin that fails FRR parsing as the GUI/plugin doesn't parse that before hand and doesn't report that error in the task output ;(
@spirit now for related IPv6 (and perhaps openfabric?) parsing of the interfaces too?
Perhaps enhancing the interface to know/enable IPv6?
https://bugzilla.proxmox.com/show_bug.cgi?id=5343
vlans is separate broadcast domains, in my case I have both a secondary gateway (LTE) that issues DHCP only, as well as a dumb/unmanaged switch on on the same physical interface. So I use it as a secondary/tertiary corosync interface and management, and thus need it stable/fixed, but need the...
problem isn't syncing to a new machine, just stating the obvious that I can today, and especially with the new machine, run multiple vzdumps to PBS server(s) without killing the hypervisor, thus the single global lock for vzdump is a tad..... overkill and causing other problems with the...
I need to find the more relavent thread on this topic, but the problem I'm facing today, is a specific back takes very long time - and now, it's not bottlenecking on anything other than a single CPU given the nature of the PBS setup/operations over HTTPS on this old hardware.
I know I can run...
one reason to NOT install the PBS on the PVE. Reading that I understood it to be a PBS that is close to the S3 storage. Yes it'll be slow, so my advoce would be to NOT use it for the actual PBS of first backup, but rather a PBS that is synchronizing the already backed up stuff, as a DR/failover...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.