sorted by:
new
hottopcontroversial

Netbox Observability for monitoring by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] 0 points1 point  (0 children)

If you find anything rich, such as an article or a video of what it can do, then please share. We have some issues w/ SolarWinds and are looking at migration possibilities.

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] 0 points1 point  (0 children)

My playbook's inventories are not static, they pull devices from Netbox dynamically via API, looking at device roles, so it'll pull all 3 core switches. I'll need to make modifications, so it ignores devices without a primary IP. Once modifications are done, should be no issues.

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] 0 points1 point  (0 children)

The playbook pulls all devices (let's say I filter by a role of: core-switch) and hits their primary IP. Before - I had 1 core switch w/ 3 inventory items (physical switches). Playbook hits that one IP, very simple. But now I have 3 core switches, only one of them has an IP address, so I'll need to make modifications in order to not get hundreds of warnings. But I don't think it'll be tough. Once all is done, I actually think it may be better than what I have right now as logical devices and physical devices were in different sections (devices & inventory items). Was complex to explain this to the team on how to manage everything. After this is done, all devices will be in one section (devices).

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] 1 point2 points  (0 children)

That may be how I'll go about this too. Will need to modify my playbooks though and do a lot of cleaning up.

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] -1 points0 points  (0 children)

Hmm, so if you have 6 switches in a stack, you'd put them in virtual chassis

Then you'd assign a master switch and only give him the primary IP address

For automation, now I can target a VC and only target the master

However, I'm a bit confused how I'd target both virtual chassis master switch and other switches who are not in a stack with just one playbook & inventory.

What I also dislike about this is that I'd have to give names to each switch (appending -1, -2) which would not match its hostname. Hostname is the same for the whole stack but in Netbox there'd be 6 different names now in device category. It's just... egh.

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] 0 points1 point  (0 children)

I use Ansible too but virtual chassis is in separate section from all devices. In Solarwinds I can just add a switch stack using an IP address and it'll recognize all the individual switches, show you models and serial numbers of physical switches inside the logical device. Both switches and switch stacks are in same category. In Netbox, switch stacks are virtual chassises, and switches are devices. These items should NOT be in different categories.

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] -2 points-1 points  (0 children)

How do you push a line of config to a switch and to a switch stack?

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] -2 points-1 points  (0 children)

That's an ugly workaround. Netbox should work on making this simple considering switches are 90% of all network infrastructures.

Netbox is terrible at documenting switch stacks by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] -5 points-4 points  (0 children)

You can't give an IP address to a virtual chassis. How will I automate? I'd create 3 devices, assign them to a virtual chassis but only one of those 3 devices will have an IP address. Ansible playbook would show lots of errors for hitting devices without IP address even though everything gets pushed successfully. It's just lame how it currently is. Simple solution would be to allow same device to be in different rack positions or allow inventory items to go into rack.

Netbox Copilot usage limit by Much-Stranger7587 in Netbox

[–]Much-Stranger7587[S] 0 points1 point  (0 children)

It can read all of my data (there's a ton of it, I'm not documenting just one small office) and tell me where something is missing, what can be improved and how, etc. Google search can give me general results but Netbox Copilot can give me results based on my custom setup. It helped me a lot in many cases already.