Built-in Monitoring Packs
GridNMS ships with ready-made monitoring packs so that monitoring works the moment a device lands in the right class. A pack bundles the data points to collect (SNMP values, on a timer) and the tabs they add to the device detail page.
This page is a reference for the Core bundle that ships out of the box: vendor-neutral monitoring for routers, switches, servers, printers, and UPSs — nothing to download, nothing to install. For specific vendors — Cisco, Juniper, Fortinet, Palo Alto, Aruba, APC, and dozens more, plus an API-based integration for Cisco Meraki — download a vendor pack bundle instead.
Polling intervals below are how often each value is read. Counters (bytes, packets, errors) are turned into per-second rates, with interface byte counters read most often; descriptive values (system description, VLAN list) are read less often.
Core bundle
Section titled “Core bundle”Vendor-neutral packs built on standard SNMP MIBs, so they work across most enterprise network gear.
| Pack | Target class | Monitors | Adds tabs |
|---|---|---|---|
| Core Network | Network Devices, Printer | Interfaces, traffic, errors, neighbors | Interfaces · Neighbors · System Info |
| Core Router | Router | ARP, routes, BGP/OSPF peers, L2 neighbors | ARP · Neighbors · BGP · OSPF · Routes |
| Core Switch | Switch | MAC address table, VLANs | MACs · VLANs |
| Core Server | Servers | CPU, memory, disk | Resources |
| Core UPS | UPS | Battery status, runtime | UPS Status |
| Core Printer | Printer | Supply levels, trays, output bin, page counts, cover/marker status | Supplies · Trays · Output & Covers · Usage · Status |
Core Network
Section titled “Core Network”The foundation pack for any SNMP device — per-interface throughput, packets, and errors, plus topology neighbor discovery.
A new account gets it attached to the Network Devices class (which its subclasses inherit) and to Printer, because the Core Printer pack builds on it. Classes you create or move yourself are your own to arrange: GridNMS never attaches or removes a pack on an existing account’s classes, so to give a server or appliance class interface metrics, attach Core Network to that class (or to All Classes) from the Packs tab. The data points below come from standard MIB-2, which effectively every SNMP device implements — including printers, servers, and appliances that have no vendor pack of their own.
| Data point | Type | OID | Interval |
|---|---|---|---|
| System Description | SNMP get | 1.3.6.1.2.1.1.1.0 |
5 min |
| System Uptime / Name / Contact / Location | SNMP get | 1.3.6.1.2.1.1.3.0 / .5.0 / .4.0 / .6.0 |
5 min |
| Interface Rx/Tx Bytes (64-bit) | SNMP walk | 1.3.6.1.2.1.31.1.1.1.6 / .10 |
1 min |
| Interface Rx/Tx Unicast Packets (64-bit) | SNMP walk | 1.3.6.1.2.1.31.1.1.1.7 / .11 |
5 min |
| Interface Rx/Tx Errors | SNMP walk | 1.3.6.1.2.1.2.2.1.14 / .20 |
5 min |
| Interface Rx/Tx Discards | SNMP walk | 1.3.6.1.2.1.2.2.1.13 / .19 |
5 min |
| Interface Speed | SNMP walk | 1.3.6.1.2.1.31.1.1.1.15 |
1 hour |
| Interface MAC Address | SNMP walk | 1.3.6.1.2.1.2.2.1.6 |
5 min |
| Interface Rx/Tx Bytes (32-bit) — off by default | SNMP walk | 1.3.6.1.2.1.2.2.1.10 / .16 |
5 min |
| Config Backup — off by default | SSH | — | 1 day |
| CDP Neighbors | SNMP walk | 1.3.6.1.4.1.9.9.23.1.2.1.1 |
5 min |
| LLDP Neighbors | SNMP walk | 1.0.8802.1.1.2.1.4.1.1 |
5 min |
Discovered CDP/LLDP neighbors feed the Topology & Neighbors views.
Core Router
Section titled “Core Router”Layer-3 visibility on top of Core Network: the ARP and routing tables plus dynamic routing-protocol peers.
| Data point | Type | OID | Interval |
|---|---|---|---|
| ARP Table | SNMP walk | 1.3.6.1.2.1.4.35.1 |
5 min |
| Routes | SNMP walk | 1.3.6.1.2.1.4.21.1 |
5 min |
| BGP Peers | SNMP walk | 1.3.6.1.2.1.15.3 |
1 min |
| OSPF Neighbors | SNMP walk | 1.3.6.1.2.1.14.10 |
1 min |
| LLDP Neighbors | SNMP walk | 1.0.8802.1.1.2.1.4.1.1 |
5 min |
| CDP Neighbors | SNMP walk | 1.3.6.1.4.1.9.9.23.1.2.1.1 |
5 min |
Core Switch
Section titled “Core Switch”Layer-2 tables for switches.
| Data point | Type | OID | Interval |
|---|---|---|---|
| MAC Address Table | SNMP walk | 1.3.6.1.2.1.17.4.3.1 |
5 min |
| VLANs | SNMP walk | 1.3.6.1.2.1.17.7.1.4.3 |
5 min |
Core Server
Section titled “Core Server”Host resource monitoring via the standard UCD-SNMP MIB (Net-SNMP).
| Data point | Type | OID | Interval |
|---|---|---|---|
| CPU Load | SNMP get | 1.3.6.1.4.1.2021.10.1.3.1 |
1 min |
| Memory Free | SNMP get | 1.3.6.1.4.1.2021.4.6.0 |
1 min |
| Disk Free Space | SNMP get | 1.3.6.1.4.1.2021.9.1.7.1 |
5 min |
Core UPS
Section titled “Core UPS”Battery health via the standard UPS MIB.
| Data point | Type | OID | Interval |
|---|---|---|---|
| Battery Status | SNMP get | 1.3.6.1.2.1.33.1.2.1.0 |
2 min |
| Runtime Remaining | SNMP get | 1.3.6.1.2.1.33.1.2.3.0 |
2 min |
Core Printer
Section titled “Core Printer”Standards-based monitoring for any network printer — HP, Brother, Canon, Xerox, and generally any make or model that speaks the Printer MIB (RFC 3805) and Host Resources MIB, which is nearly all of them. There’s no vendor-specific bundle to download for printers; this is the whole story.
| Data point | Type | OID | Interval |
|---|---|---|---|
| Printer Status | SNMP walk | 1.3.6.1.2.1.25.3.5.1.1 |
2 min |
| Device Status | SNMP walk | 1.3.6.1.2.1.25.3.2.1.5 |
2 min |
| Supply Name / Level | SNMP walk | 1.3.6.1.2.1.43.11.1.1.6 / .9 |
5 min |
| Supply Max Capacity | SNMP walk | 1.3.6.1.2.1.43.11.1.1.8 |
10 min |
| Input Tray Name / Media / Level / Max Capacity / Status | SNMP walk | 1.3.6.1.2.1.43.8.2.1.13 / .12 / .10 / .9 / .11 |
5 min |
| Output Bin Max / Remaining Capacity / Status | SNMP walk | 1.3.6.1.2.1.43.9.2.1.4 / .5 / .6 |
5 min |
| Cover Status | SNMP walk | 1.3.6.1.2.1.43.6.1.1.3 |
2 min |
| Marker Status | SNMP walk | 1.3.6.1.2.1.43.10.2.1.15 |
2 min |
| Lifetime Page Count | SNMP walk | 1.3.6.1.2.1.43.10.2.1.4 |
5 min |
| Power-On Page Count | SNMP walk | 1.3.6.1.2.1.43.10.2.1.5 |
10 min |
| Console Alert Lights | SNMP walk | 1.3.6.1.2.1.43.17.6.1.4 |
2 min |
Supply levels report per cartridge (toner, ink, drum, and so on — however many the printer has), so a multi-color printer reports each color separately. Trays and output bins are the same shape: one reading per physical tray or bin the printer reports. Interface traffic for a printer’s network port comes from Core Network, which every class inherits automatically.
Customizing or extending
Section titled “Customizing or extending”Built-in packs are a starting point, not a limit. You can:
- Tune any data point’s interval or disable it per class — see Enabling & Disabling Data Points.
- Add a vendor — import a ready-made bundle for Cisco, Juniper, Fortinet, Palo Alto, MikroTik, F5, Synology, and dozens more — including an API-based bundle for Cisco Meraki — see Vendor Pack Bundles.
- Build your own pack for hardware not covered here — see Building a Monitoring Pack.
- Set thresholds on any collected metric to raise events — see Events & Alerts.
docs built 2026-11-12 · 945a2dec2