How to troubleshoot SNMP on ICX switches.
Summary
Simple Network Management Protocol (SNMP) is a key tool for managing and monitoring network devices like routers and switches. It helps administrators collect performance data and monitor device health using Management Information Bases (MIBs) on 10.0.10 family software. SNMP Versions: SNMP v1: Basic features, limited security. SNMP v2: Improved performance with bulk data transfers but weak security. SNMP v3: Adds encryption, authentication, and role-based access control for enhanced security. Uses of SNMP: Device Monitoring: Track device health and performance. Configuration Management: Remotely update settings and firmware. Alerts (Traps): Receive real-time notifications for critical events like failures or warnings. SNMP is essential for efficient network management, with SNMPv3 offering a secure, modern solution.Question
How to troubleshoot SNMP communication issues on RUCKUS ICX switches on 10.0.10 family software?Customer Environment
RUCKUS ICX 7150, 7250, 7450, 7550, 7650, 7750, 7850 switches SNMP-based monitoring tools (e.g., SolarWinds, Nagios, PRTG)Symptoms
- Configure SNMP V2 and V3
- Unable to retrieve SNMP data from the switch
- SNMP timeouts or connection errors in monitoring tools
- Missing or delayed SNMP traps
- Authentication errors in SNMP logs
Root Cause
SNMP-related communication issues are commonly caused by: Misconfiguration of SNMP community strings or user credentials Network connectivity problems Firewall or ACL blocking SNMP traffic (UDP ports 161 and 162) Version mismatch between SNMP manager and switch (SNMPv1, v2c, or v3)Troubleshooting Steps
1. Verify SNMP Configuration
Check the current SNMP configuration on the switch:
- Ensure SNMP is enabled.
- Verify SNMP community strings for SNMPv1/v2c and user authentication for SNMPv3.
CLI Commands:
device# show snmp community
device# show snmpv3 user
device# show running-config | include snmp
device# show snmp
device# show log
2. Check Network Connectivity
Ensure that the management interface can reach the SNMP manager.
- Use ping and traceroute to check connectivity.
- Verify firewall/ACL rules are not blocking UDP ports 161 and 162.
CLI Command Example:
device# ping <SNMP Manager IP>
device# traceroute <SNMP Manager IP>
3. Validate SNMP Version Compatibility
Ensure the SNMP version used by the monitoring tool matches the configuration on the switch.
- SNMPv1 and v2c are simpler but lack security features.
- SNMPv3 offers encryption and authentication.
4. Review SNMP Logs and Traps
Check logs for SNMP-related errors or warnings:
device# show log | include SNMP
Ensure traps are being sent to the correct destination:
device# show snmp server
device# show run | in snmp-server host
5. Common Issues and Resolutions
- SNMP Timeout: Check connectivity and verify the SNMP manager's IP address.
- Authentication Errors: Revalidate community strings or SNMPv3 credentials.
- No Traps Received: Ensure the trap destination is correctly configured and reachable
To expedite resolution, please collect and provide the following details:
- Configuration: Full SNMP configuration (
show running-config | include snmp
) - Device Information: Switch model, software version (
show version
) - Network Details: Topology diagram, SNMP manager IP address, and versions used
- Logs: SNMP logs (
show log | include SNMP
) - Packet Captures: If possible, capture SNMP traffic on UDP ports 161 and 162
- SNMP V2
device# enable
device# configure terminal
device# snmp-server community ASCII string ro/rw
// ro (Read-only)
// rw ( Read-write)
device# wr mem
https://www.youtube.com/watch?v=x_BDNSZJAaY
https://docs.commscope.com/bundle/fastiron-08095-managementguide/page/GUID-FD9AC4AE-D01D-48E7-B06D- 7A85DFB0A60C.html
- SNMP V3
device# enable
device# configure terminal
device# enable snmp-server group admin v3 priv read all
device# enable snmp-server user test Ruckus v3 auth sha Ruckus123 priv des Ruckus123
device# wr mem
https://www.youtube.com/watch?v=zv_csSF_A6k
https://docs.commscope.com/bundle/fastiron-08095-managementguide/page/GUID-24269738-786C-4A93-B065-B7D8E8C2F678.html
6. Output examples
- Verify SNMP Service Status
If SNMP is running, it would show output like this:
device# show snmp
SNMP Statistics
Receive Statistics
0 bad versions, 0 bad community names
0 bad community uses, 0 asn parse errors, 0 memory errors
0 too bigs, 0 no such names, 0 bad values
0 read onlys, 0 general errors, total request variables
0 total set variables, get requests, get next requests
get bulk requests, 0 set requests, 0 get responses, 0 traps
If SNMP is not running, the output would be:
Device(config)#show snmp
SNMP is disabled, please enable SNMP to run show snmp commands
- Check SNMP Service and Trap Configuration
Device(config)#show snmp ser
Status: Enabled
Contact:
Location:
Community(rw): $U2kyXj1k
Max Ifindex per module: 64
Traps
Cold start: Enable
Link up: Enable
Link down: Enable
Authentication: Enable
Power supply failure: Enable
Fan failure: Enable
Fan speed change: Enable
Module inserted: Enable
Module removed: Enable
Temperature warning: Enable
STP new root: Enable
STP topology change: Enable
MAC notification: Enable
MAC-AUTH notification: Enable
OSPF: Enable
BGP: Enable
VRRP: Enable
VSRP: Enable
MRP: Enable
UDLD: Enable
link-oam: Enable
BFD: Enable
syslog: Disable
entity-cfg-change: Enable
Total Trap-Receiver Entries: 0
- Validate SNMP Community Strings or SNMPv3 User Credentials
To view SNMPv3 user information:
Device # show snmp user
username = test
group = RUCKUS
security model = v3
authtype = sha
authkey = a0fe4df3197016b21c528f7a1f4c9a3d514da2e1
privtype = des
privkey = a0fe4df3197016b21c528f7a1f4c9a3d
engine ID = 800007c70338453b3cdb42
- Check the SNMP Configuration
Device(config)#show run | include snmp
snmp-server community 2 $U2kyXj1k rw
snmp-server group admin v3 priv read all
snmp-server user test RUCKUS v3 encrypted auth sha a0fe4df3197016b21c528f7a1f4c9a3d514da2e1 priv encrypted des a0fe4df3197016b21c528f7a1f4c9a3d
Resolution
-
Check and Correct SNMP Configuration
Ensure the correct community strings, SNMP versions, and trap destinations are configured. -
Network Verification:
Ensure there are no connectivity issues, and UDP ports 161 and 162 are open. -
Review Documentation:
Refer to the RUCKUS Support Portal for known issues and additional guidance. -
Contact RUCKUS Support:
If the issue persists, contact RUCKUS Support with the information gathered.
Article Number:
000014699
Updated:
May 29, 2025 12:20 PM (26 days ago)
Tags:
Troubleshooting, Ruckus ICX Switches
Votes:
0
This article is:
helpful
not helpful