Check the SNMP log file (radiusdir/snmp/jnprsnmpd.log) for event information related to the SNMP agent.
If the SNMP agent fails to run (that is, you do not see it listed when you run the ps -A -f | grep jnprsnmpd command), review the log file to determine whether another SNMP agent is running.
Two SNMP agents cannot share the same port. If another SNMP that uses the same port (port 161 by default) is running on your system, the Steel-Belted Radius Carrier SNMP agent may fail to start. Review the log file to determine whether a conflict over Port 161 is occurring.
If the Steel-Belted Radius Carrier SNMP agent conflicts with another SNMP agent and you cannot uninstall or disable the other SNMP agent, change the port assignment.
If an SNMP MIB browser or other management station cannot reach the SNMP agent, verify that the agent is running by executing: ps -Af | grep jnprsnmpd. If the agent is listed, run the testagent.sh script to verify the agent is responding.
If the testagent.sh script succeeds, verify that the community strings and access controls configured in the jnprsnmpd.conf file are correct.
If the testagent.sh script fails, verify that the script uses the same port number specified in the jnprsnmpd.conf file (the default is Port 161) and that the jnprsnmpd.conf file grants access to localhost, which testagent.sh requires to function.