For our new network backbone the configuration of every switch is built from NetBox. Nobody logs in to a switch to change something by hand. This post describes how the pieces fit together. The NetBox Model We keep the model deliberately small: Devices Interfaces VRFs VLAN groups VLANs For the VXLANs we do not use L2VPN objects. A VLAN in NetBox is the L2 segment, and its VNI is derived from the object ID: ...
We are building a new network backbone for Medialine Group. The first big milestone is done: within one week, we deployed 192x 100G and 384x 10/25G ports. Sites The backbone connects three Frankfurt locations in a redundant ring: Equinix FR5 (rack) Telehouse Frankfurt (rack) Equinix FR2 (new cage) ITENOS Frankfurt 1 is currently still the main site. In the future it will only be used for backups, and until then it is connected with 2x 100G via redundant cross-connects. ...
Two years ago, I’ve used multiple Intel X710-DA4 NICs to built an EVPN Setup for my company level66.network. Whilst most of the connections to other peers worked quite well, I’ve had a few links which showed some strange issues. Most commonly the links were reported as flapping from the other peers or they just reported packetloss on their end. After quite some time of troubleshooting, switching optics and using different ports we found the solution. With the default configuration of the Linux driver, the NIC seems to sent out some (maybe malformed) LLDP messages causing issues with some specific networking gear. We were not able to narrow it down to a specific vendor, though. These messages are directly generated on the NIC and are therefore not shown in a tcpdump. That’s why we were not aware of them. ...