How to troubleshoot NetSNMP agent communications with Netops applications.

Products

• Network Observability

Issue/Introduction

You are trying to set up resource monitoring of the NetOps servers from Spectrum but cannot get NEtSNMP agent to work. 

Environment

 

• OS: Linux (RHEL/CentOS/Systemd based)

• App Server: Netops SpectroSERVER (SS)

• Protocol: NetSNMP Agent

 

Cause

Standard NetSNMP is an open-source tool that may lack the specialized integration and support features required for high-performance monitoring in DX NetOps.

Utilizing the native SystemEdge agent ensures full compatibility and enhanced management capabilities

Resolution

PREREQUISITES:

• SSH access to SpectroSERVERs

• Access to the SPECROOT/bin directory

• Correct SNMP community string (e.g., public)

STEPS:

1. VERIFY SNMPD PROCESS: Check if the SNMP daemon is running.

   Command: ps -ef | grep -i snmpd

   EXPECTED: The snmpd process appears in the process list.

2. CHECK SERVICE STATUS: Use systemctl to verify the operational state of the service.

   Command: service snmpd status

   EXPECTED: Output shows "Active: active (running)".

3. START SERVICE: If the daemon is not active, initialize the service.

   Command: service snmpd start

   EXPECTED: Service starts without errors.

4. PERFORM LOCAL TEST: Run a local snmpwalk to ensure the agent responds to local requests.

   Command: snmpwalk -v2c -c [community-string] localhost system

   EXPECTED: System MIB information is returned.

5. PERFORM REMOTE VALIDATION: Test connectivity from a different SpectroSERVER using sapwalk2.

   Path: SPECROOT/bin/

   Command: ./sapwalk2 -i [IP-address] -v v2c -s 1.3.6.1 -c [community-string] -o NetSNMP.walk

   EXPECTED: Walk file "NetSNMP.walk" is generated with remote agent data.

VERIFY SUCCESS:

• Service status shows as active on all servers.

• Local snmpwalk returns valid MIB data.

• Remote sapwalk2 successfully retrieves data from secondary servers.

Additional Information

ROOT CAUSE: Communication issues often stem from an inactive snmpd service or network restrictions preventing remote polling between SpectroSERVER nodes.

• Check NetSNMP Community Strings Configuration

• Documentation: sapwalk2 Command Reference

KNOWN LIMITATIONS:

• Local firewall (iptables/firewalld) may block port 161 even if the service is running.

VERSION NOTES:

• Systemd: Use "systemctl" commands for service management on modern Linux versions.

PREVENTION: Ensure snmpd is enabled to start on boot: "systemctl enable snmpd".