Hi, relatively new here.
Curious how many of you are running both NetBox and Zabbix in production?
Have you done any meaningful integration between them (especially keeping Zabbix hosts/templates in sync from NetBox?
We’re working on some tooling in this area and want to understand how common this setup actually is, and what people’s real pain points are.
Does anyone know if I can associate a circuit (id) to a prefix? I'd like to look up a circuit and see which prefixes are assigned by the ISP.
Hi all!
Let me explain my situation and my question:
Until recently, I worked at a company that had 4 racks in 1 data center. It was easy to use Netbox via the UI... just clicking, clicking, and clicking to configure everything.
Now, at my current company, they don’t have DCIM; they use spreadsheets to manage more than 50 racks across 2 data centers.
My idea is to use IaC to deploy and configure Netbox for automatic discovery, control, and management of devices (not just switches and routers, but also physical servers and storage systems).
My question is more related to the initial part of creating tenants, sites, circuits… And how do I manage this configuration using IaC? How does Netbox detect a drift configuration?
Actually, I’m not sure if my question is related to Netbox or to the pipeline itself.
Anyway… I’d appreciate it if you could help me or share your experiences.
Thanks all!
Hello fellow redditor,
I'm looking for some best-practice ideas on how to handle initial network discovery and ongoing inventory reconciliation with NetBox.
I understand that NetBox should be the source of truth and not simply mirror whatever is currently discovered on the network.
However, when initially setting up NetBox, manually adding every existing device seems quite time-consuming. Ideally, I'd like to use some kind of discovery process (SNMP, Nmap, LLDP/CDP, APIs, etc.) to discover existing devices and use that data to build the initial inventory.
For ongoing operations, I was thinking about running discovery periodically, comparing the discovered state against NetBox, and then reviewing the differences manually before making any changes to the NetBox inventory.
Something like:
Network Discovery
Compare with NetBox
Review differences
Update NetBox
Has anyone implemented a workflow like this in practice?
I'm especially interested in what tools/scripts/plugins you use for discovery and comparison, and whether this approach works well for a small IT team.
Thanks in advance :D
Hello!
I've been playing around with netbox for a while, and have a lot of automation experience with mostly APIs (Cisco ACI, Cisco ISE) but am no stranger to the CLI, either.
Anyway, I'm struggling with finding the best approach to automate some GNS3 ios images for my homelab - I'm torn between generating full configs and pushing to the device, partial configs and pushing with a 'no' statement before it, or utilizing ansible cisco.ios.ios_* collection to do it declaratively.
Can anyone share some real world advice? I've created some POC playbooks for each method but am really getting caught up in the pros and cons of them. So, I'm looking for some feedback from someone that's done it in the real world.
One of the headaches I'm dealing with pushing configs is something like prefix-lists. For instance, if I want to change the less than or greater than prefixes while I'm testing things, I'll get errors that the seq number already exists.
I know I can work around it by issuing a NO statement before a block, but for something like prefix-lists, access-lists, and route-maps that really slows down the automation when looping through it.
Thanks, Champions!