How do I keep NetBox updated?
Asked by
CuriousCoder87
I ran into a frustrating issue today with our NetBox system. I got a simple ticket for a new port for a host and checked NetBox, which indicated that port 15 was free. However, when I went to the rack, I found a cable connected to that port, and it turned out to be live and linked to a firewall that was never documented! I checked another port in NetBox that was supposed to be free, and found a cable plugged into a server we decommissioned six months ago. This simple task ended up taking an hour of tracing cables, and now I need to update NetBox for three different ports just to close one ticket. It's really frustrating because it feels like the documentation is useless when no one has the time to keep it updated properly. How are you all managing to keep your NetBox synced? Are you using scripts to sync switch configurations back to it or something?
Answers
NetBox is supposed to be the source of truth. If there are cables connected that aren't documented, those need to be disconnected unless absolutely necessary. It looks like the real issue is that people aren’t following processes. You might want to establish a stricter documentation procedure.
Reply to this answer
Garbage in, garbage out, right? If the data isn’t good to start with, you can’t expect great results. It’s frustrating how often we deal with this due to poor documentation.
Reply to this answer
The key is making sure that NetBox controls your switch configuration. It shouldn’t be an issue having a cable plugged in, as long as your port isn’t live until it’s updated in NetBox first.
Reply to this answer
I feel you on the frustration! I’ve had similar experiences in my jobs. I started adding a 'last reviewed' custom field in our inventory systems, so I can flag devices that need a physical check. It helps keep things accurate with what we have.
Reply to this answer
It sounds like your setup just needs some process alignment. Make sure you’re marking any changes in NetBox: connect the cable in the system first, then physically connect it. If coworkers aren't following this method, it's a broader issue at the workplace, not a NetBox problem.
Reply to this answer
Add your answer
Answers are reviewed before publication.
TechieTim42: Absolutely! Whoever is making changes without documentation needs to face some consequences. This extra work you just experienced highlights the waste that comes from poor practices.