Hi,
We are trying to configure SNMP on SBR ver 7.3.1
I loaded jnprsnmpd.conf file at /opt/JNPRsbr/radius/snmp/conf
And I got below error at jnprsnmpd.log
Error opening specified endpoint "162"
Server Exiting with code 1
please advise.
Solved! Go to Solution.
Hi,
I suspect the port 162 is already in use and hence we are seeing this error.
May be you need to try with a different port like 166 or 167 etc,
Replace the port# 162 with 166 or 167 in the jnprsnmpd.conf, then check snmp traps and logs.
Regards,
Kannan
Seems like SNMP utility in SBR is unable to bind to port 162.
Can you validate whether the port has been already used by any other process in the server.
Typically I have seen such conflicts with OS SNMP utilities itself.
Thanks
Hi Ashish,
Hope you are doing well.
please check the below, it seems that no other SNMP agent daemon running execpt for SBR
bash-3.00# ps -ef | grep snmp
root 555 1 0 Oct 05 ? 6:22 /usr/sfw/sbin/snmpd
root 3506 1 0 Jan 09 ? 0:19 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 549 1 0 Oct 05 ? 0:07 /usr/lib/snmp/snmpdx -y -c /etc/snmp/conf
root 16378 1 0 09:41:34 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 618 1 0 Oct 05 ? 0:00 /usr/lib/dmi/snmpXdmid -s radiusvfe1
root 19556 1 0 11:40:08 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 17080 1 0 10:05:24 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 16700 1 0 09:46:34 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 19914 1 0 11:47:12 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 19624 1 0 11:43:00 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 17164 1 0 10:09:48 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 17220 1 0 10:11:00 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 16684 1 0 09:45:38 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 16424 1 0 09:43:23 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 15803 1 0 09:30:17 ? 0:00 snmpwatch /opt/JNPRsbr/radius/snmp/bin/jnprsnmpd -f -c /opt/JNPRsbr/radius/snmp
root 20394 19441 0 11:50:52 pts/1 0:00 grep snmp
Hi Hany,
The output pasted by you, confirms that multiple snmpd daemon are running on the machine and could be causing the conflicts.
Can you try and use a free port.
You could netstat -a to identify active network connections
Thanks