Cisco switches and routers are supported through standard SNMP, the same as any other network device (see SNMP Monitoring), but Cisco's own MIBs expose extra detail that's worth adding once basic connectivity is confirmed.
Beyond generic interface monitoring
- Device CPU and memory — Cisco exposes these through its own process and memory MIBs, giving a more accurate read on device load than generic SNMP alone.
- Per-port status and speed/duplex — useful for spotting a port that's negotiated an unexpectedly low speed or a duplex mismatch, both common causes of intermittent performance problems.
- VLAN information — which ports belong to which VLAN, useful context when troubleshooting a connectivity issue that's isolated to one segment.
- Environmental sensors, on devices that expose them — temperature and power supply status, which matter a great deal in a rack environment.
Setup notes specific to Cisco
- Use a read-only SNMP community (or an SNMPv3 read-only user) — Cisco devices support fine-grained SNMP view restrictions, and monitoring should never need write access.
- If the device has an SNMP access list, explicitly permit the iPM server's IP address, since Cisco devices commonly ship with SNMP locked down by default on anything beyond the local subnet.
- Auto Discovery generally identifies Cisco devices automatically during a scan, based on their SNMP sysObjectID, and can pre-populate the more detailed Cisco-specific checks alongside the generic ones.
Cisco gear is frequently core infrastructure — switches and routers everything else depends on — so it's worth adding the fuller set of checks here rather than relying on ping and basic interface status alone.