Cisco Business Switch SNMP Timeout/Disable

[Ledaf99]

I Have a Switch Business 220 Series, and I want to monitor the device with SNMP. It works for a while, like 1 - 2 hours, but suddenly, the SNMP service is down / timeout when I try to check with snmpwalk. I tried restarting the device many times, and it's still the same, the SNMP service is down every couple of minutes or hours. And of course, I'm updating the firmware to the latest. Did anyone have problem with me ?

[marce1000]

           - Check logs on the device when that happens , 

 M.

[balaji.bandi]

what are you Monitoring, these are basic switches, if you hammering with so many may have issue,i guess, so try polling what required rather all the OID against with switch.

Also see if you can get latest firmware and check if that fix any issue.

what version snmp version, try avoid v1, try v2 or v3 (i suggest v3) - 

https://www.cisco.com/c/en/us/td/docs/switches/lan/csbss/CBS220/Adminstration-Guide/cbs-220-admin-guide/snmp.html?bookSearch=true

[vishalbhandari]

The issue you're facing with SNMP on the Cisco Business 220 Series switch may be due to resource limitations, misconfigurations, or bugs in the firmware. Since you've already updated the firmware, here are additional steps to help diagnose and resolve the issue:

---

1. Verify SNMP Configuration

• Ensure that the SNMP service is correctly configured:

  • Community Strings: Verify the read-only and read-write community strings (e.g., public, private).
  • SNMP Version: Match the version (v1, v2c, or v3) being used by the monitoring tool with the switch configuration.
  • Access Control: Confirm that the allowed IP ranges or SNMP hosts are properly configured.

  Example CLI Commands (if applicable):

  bash

  show snmp show snmp community

---

2. Monitor System Resources

• High CPU or memory usage can cause SNMP to fail intermittently. Check the system resource utilization:
  bash

  show cpu utilization show memory
• If resource usage is high, consider:
  • Reducing polling frequency from your monitoring system.
  • Limiting the number of OIDs being queried.

---

3. Check SNMP Service Logs

• Look for logs related to SNMP or potential errors that might indicate why the service is stopping:
  bash

  show logging
• Search for specific messages about SNMP timeouts or process failures.

---

4. Enable Debugging for SNMP

• Temporarily enable debugging to gather more insights about SNMP operations:
  bash

  debug snmp
  • Check the logs for repeated errors, such as authentication issues or excessive queries from the monitoring tool.

---

5. Modify SNMP Polling Behavior

• Reduce Polling Frequency:
  • High-frequency SNMP polling can overwhelm the switch. Set your monitoring tool to query the device less frequently (e.g., every 5 minutes instead of every 1 minute).
• Limit OIDs Polled:
  • Poll only necessary OIDs instead of querying the entire MIB tree. Excessive or complex queries might cause the SNMP process to crash.

---

6. Validate Firmware and Compatibility

• Although you've updated to the latest firmware, verify the following:
  • The firmware is applied correctly.
  • The release notes of the firmware confirm that it addresses known SNMP issues.
  • The monitoring tool you're using is compatible with the switch's SNMP implementation.

---

7. Restart the SNMP Service

If restarting the entire switch isn't feasible, try restarting the SNMP service alone. Unfortunately, the Business 220 series doesn’t have granular control to restart services via CLI or GUI, but you can:

• Disable and re-enable SNMP in the web GUI or CLI to reset the service.

---

8. Factory Reset and Reconfigure

• If the issue persists, perform a factory reset:
  • Save the current configuration.
  • Reset the device to factory defaults.
  • Reconfigure SNMP settings manually (avoid restoring from a backup to prevent reintroducing configuration issues).

---

9. Open a Cisco TAC Case

If none of the above resolves the issue, this might be a bug or hardware limitation:

• Collect logs and debugging outputs (show tech-support).
• Open a case with Cisco TAC for further analysis.