switch template

[thomas24]

Hi everyone,

I have a question about monitoring switch interfaces with Zabbix.

On each switch, I need to monitor different interfaces (the ports are not the same from one switch to another). Because of this, it seems like I’m forced to create a separate template for each switch just to select the correct interfaces to monitor.

Is this really the only solution?

1 upvote

[troffasky]

What do you mean by "monitor"?

Low Level Discovery will find interfaces on devices and create data collection items, graphs, triggers, etc.
95% of the switches I monitor, I leave interface discovery disabled, because most of the time I do not need all the data.
The other 5% either has discovery enabled, or, I enable discovery once, then delete all the interface metrics I don't want.

19 upvotes.

[markosa]

You can also define in LLD that you don't want to discover ports which are in admin down state or even oper down state, that way you only have ports which are really in use. Basically you can also define within LLD that if name of interface is like "internet-gw-1", "workstation-1" you could leave those workstation interfaces out from discovery... Theres many ways to filter out stuff in LLD, also template level usermacros are usefull since those can be modified within host-level->different filttering on each host with one template.