Overview

    Since Zabbix 3.4 templates for many families of network devices are provided. All templates cover (where possible to get these items from the device):

    • Chassis fault monitoring (power supplies, fans and temperature, overall status)

    • Chassis performance monitoring (CPU and memory items)

    • Chassis inventory collection (serial numbers, model name, firmware version)

    These templates are available:

    • In new installations - in Configuration → Templates;

    • If you are upgrading from previous versions, you can find these templates in the directory of the downloaded latest Zabbix version. While in Configuration → Templates you can import them manually from this directory.

    to filter out loopbacks and null interfaces on most systems.

    Devices

    List of device families for which templates are available:

    Template design

    Templates were designed with the following in mind:

    • User macros are used as much as possible so triggers can be tuned by the user;

    • Low-level discovery is used as much as possible to minimize the number of unsuppported items;

    • All templates depend on Template ICMP Ping so all devices are also checked by ICMP;

    • Items don’t use any MIBs - SNMP OIDs are used in items and low-level discoveries. So it’s not necessary to load any MIBs into Zabbix for templates to work;

    • Loopback network interfaces are filtered when discovering as well as interfaces with ifAdminStatus = down(2)

    • All discovered network interfaces have a trigger that controls its operational status(link).

      • If you do no want to monitor this condition for a specific interface create a user macro with context with the value 0. For example:

    where Gi0/0 is {#IFNAME}. That way the trigger is not used any more for this specific interface.

    • You can also change the default behavior for all triggers not to fire and activate this trigger only to limited number of interfaces like uplinks

    Tags

    • Performance – device family MIBs provide a way to monitor CPU and memory items;

    • Fault - device family MIBs provide a way to monitor at least one temperature sensor;

    • Inventory – device family MIBs provide a way to collect at least the device serial number and model name;

    • Certified – all three main categories above are covered.