breaking networks, so you don't have to.
This post is a long winded way of telling you how you can select multiple sites to be ingested into Netbox easily so that the amount of data being added to Netbox is small enough to not overload it. The IP Fabric Netbox plugin allows input and comparison of data between the two systems. It... Continue Reading →
Larger Juniper routers have two hardware control planes, known as routing engines. These can be seen on some models as a removable slot in the chassis. Each has its own management IP, storage etc and can be seen as an independant compute node. If one fails, the other takes over. When IP Fabric connects to... Continue Reading →
IP Fabric allows one or more attributes to be assigned to a device. These act like tags in blog posts where certain optional attributes/values can be given to each object. They can be used to filter down devices in all the views of the UI, or via the API. Built in attributes like the site... Continue Reading →
The very talented Alex Gittings from IP Fabric has helped me to understand how to get around the capitalisation issue. In the transform maps you can create a jinja2 template that capitalises a field. So if applied in the device - DCIM|manufacturer map, with source field as vendor and target field as name, it will... Continue Reading →
This post looks at a simple way to download all the settings from IP Fabric and acts as a primer for future IP Fabric API posts. IP Fabric was written from day one with an API First approach. This means that every function/feature is coded as an API in the first instance. The webUI is... Continue Reading →
Constantpinger 