Setup guides / Zabbix
← Back to LabZabbix setup guide
ValidatedTested with 7.0.30
Zabbix polls this device with its bundled generic SNMP template. These steps mirror the M2E validation run.
Router (generic-router-v1)
SNMP v2c · 8 interfaces
- sysName / sysUpTime
- ifNumber = 8
- Per-interface status
- 64-bit octet counters
Run high_cpu → CPU reads ~95% → your alert should fire.
Connection
- Host
- snmp-test.bonguides.com
- Port
- 161
- Version
- SNMP v2c
- Community
- generated per device
The community is generated per device and shown only in your lab — treat it as a throwaway secret and do not reuse it. SNMP v2c is cleartext.
1. Create the device
- In the lab, create a Router (generic-router-v1) and copy its Host, Port, SNMP version and Community.
- Host is snmp-test.bonguides.com, port 161, SNMP v2c. The community is generated per device — treat it as a throwaway secret.
- Expect 8 interfaces (GigabitEthernet0/1–8), plus system uptime, CPU and memory over standard MIBs.
2. Configure Zabbix
Add the host
Create a host with an SNMP interface pointing at snmp-test.bonguides.com:161, set the {$SNMP_COMMUNITY} macro to the generated community, and link the "Network Generic Device by SNMP" template.
Expected data
sysName, sysUpTime, ifNumber (8), per-interface status and 64-bit octet counters populate in Latest data. CPU can be added explicitly (see caveats).
3. Run the fault scenarios
Trigger these from the device page in the lab, then watch Zabbix react. Each has a recovery action that restores the baseline.
- high_cpu — an item on hrProcessorLoad reads 95.
- interface_down — ifOperStatus.1 becomes down (2).
- snmp_down — the SNMP interface is marked unavailable, then recovers.
Caveats
- The generic SNMP template does not create a CPU item. Add an explicit SNMP item on 1.3.6.1.2.1.25.3.3.1.2.1 (HOST-RESOURCES-MIB hrProcessorLoad) — the OID is standard and valid.