This article applies to PRTG Network Monitor 16.3.25 or later
We have multiple stacks of Cisco 2960 switches across campus that we would like to be monitored in PRTG. The problem is that only the top switch has an IP address. In a stack of 3 switches, only the top switch is being monitored as far as we can see. Is there a way for PRTG to recognize the other 2 switches that reside in the stack?
Monitoring the status of Cisco switches in a Stack
You can easily monitor a stack of Cisco Switches/devices using the device template below.
This device template can be used to automate the deployment of these sensors using auto-discovery. The sensors will report the Stack Unit's status according to the provided lookup file.
Adding Custom Sensors using the Auto-Discovery + Template
You can use the device template that we provide below to automatically create custom sensors with the PRTG auto-discovery.
The metrics that are available can vary. The sensors can monitor the following if the data is available:
- Stack Unit
- State
- Role
The device template creates the available and compatible sensors based on the data at hand. The sensors implement default alerts whenever possible, but you can still fine-tune most channels by defining additional limits in the sensor channels settings or modifying the lookups included by default.
Requirements
- PRTG Network Monitor 16.3.25 or later
- Because the device template relies on the auto-discovery process, the device you want to monitor needs to be reachable via PING.
- SNMP must be enabled and the device must support the CISCO-STACKWISE-MIB.
Known Issues and Limitations
- PRTG shows some of the alerts as reported by the monitored device via SNMP using lookups. If the status is not reported correctly via SNMP, PRTG cannot detect any issues. For additional alerts, please set up limits for additional channels.
- This device template was created based on data collected from other customers, so we cannot guarantee that the sensors described above will work on your systems or that the default thresholds are optimal for your use case. Use these components at your own risk. Please test and validate the sensors in your environment after deploying them.
Deployment and Usage
- Download the required zip archive containing the template's files here.
- Extract the archive to your PRTG program directory. By default, this is %Program Files (x86)%\PRTG Network Monitor\.
- In PRTG, restart the core server: open Setup | System Administration | Administrative Tools | Restart Core Server and click Go!. This ensures that the MIB and lookups are loaded before you run the auto-discovery.
- Create a new device in PRTG with the address (IP or FQDN) of the device that you want to monitor and configure the SNMP credentials accordingly.
- Right-click your new device, select Run Auto Discovery with Template, browse for stack and select the Custom Cisco Stack v0.x template from the list.
Note: Using the auto-discovery with a dedicated device template is convenient here because it automates the creation of the custom sensors in an organized fashion. - The sensors are deployed after a couple of seconds.
- You can adjust the channel limits or lookups to your needs later.
Result
The resulting sensors look like this:
Sensor's Overview
No sensors deployed? :(
Please read ahead for troubleshooting.
Troubleshooting
Have any issues? Please don't hesitate to contact us by replying to this post or via a support ticket. Please make sure to mention this KB post. Please read ahead for troubleshooting steps that you can take in advance.
Auto-Discovery Log
Your auto-discovery log tells you a lot about what went wrong during the sensor's deployment. You can troubleshoot the auto-discovery by inspecting the auto-discovery log. If you get entries like the one below (NOT FOUND), it means that the required protocol or Object Identifier (OID) is not available and the sensors can't be deployed.
[...]
21.08.2017 09:17:17: Template Loaded; Device ID: 22848; Name: Custom Cisco Stack v0.1
21.08.2017 09:17:18: Template Check; Device ID: 22848; Check ID: ping; FOUND
21.08.2017 09:17:19: Template Check; Device ID: 22848; Check ID: snmp; FOUND
21.08.2017 09:17:20: Template Check; Device ID: 22848; Check ID: snmp_cswSwitchInfoTable; NOT FOUND
[...]
In the example above, some sensors were skipped because the device did not respond to the snmp_cswSwitchInfoTable check. This means that this data is probably not available on your device. You can track this data by looking for the name after snmp_. In this case, a search for cswSwitchInfoTable will tell you what OID from what MIB is missing.
You can also use this log to identify if the discovery was interrupted because the device did not respond to PING or to a basic SNMP check.
SNMP Data
If the discovery log is not sufficient, you can review the SNMP data directly from your device. To do so, save the text below (in the white box) as .txt and use it with the Scan Script option in our SNMP Tester. This will allow you to review which SNMP queries succeed and which do not deliver any data. Please have this information at hand when contacting our support team.
--------
Walk Default
--------
hrSystemUptime
walk=1.3.6.1.2.1.25.1.1
--------
MIB-2 System
walk=1.3.6.1.2.1.1
--------
Sensor Specific Queries
----
walk=1.3.6.1.4.1.9.9.500.1.2.1
---
Version History
| Version | Description |
|---|---|
| 0.1 | Initial Release |
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
