Operating System - HP-UX
1834599 Members
3850 Online
110069 Solutions
New Discussion

snmp.conf filling after installing snmp patch on HP-UX 10.20

 
Rob Fisher
Advisor

snmp.conf filling after installing snmp patch on HP-UX 10.20

On some of the HP-UX 10.20 servers that I have installed the snmp patch bundle , I am starting to have /var and / filled. The two files that are causing this are /var/adm/snmp.log and /etc/SnmpAgent.d/snmp.conf
The snmp.conf file is filling up with messages such as "trap-dest: 191.1.1.101" repeting with the same and other IP addresses. Has anyone else run into this problem on a 10.20 box?
May the winds of life keep you on the right tack
3 REPLIES 3
S.K. Chan
Honored Contributor

Re: snmp.conf filling after installing snmp patch on HP-UX 10.20

I'm not sure about the "trap-dest" message you keep seeing in snmpd.log, until that is figured out what you can do is define size limit to snmpd.log. That way you can buy some time and investigate your snmp configuration.

Say you want to fix the maximum size of snmpd.log to 2MB.
# vi /etc/rc.config.d/SnmpMaster
==> right at the bottom add this 2 lines
SNMP_LOG_SIZE=2000000
export SNMP_LOG_SIZE
# /sbin/init.d/SnmpMaster stop
# /sbin/init.d/SnmpMaster start
# /sbin/init.d/SnmpMib2 start
# /sbin/init.d/SnmpHpunix start
# /sbin/init.d/SnmpTrpDst start
==> stop and start SnmpMaster and start SnmpMib2,SnmpHpunix and SnmpTrpDst
==> From now on snmpd.log gets recycled after 2MB.
U.SivaKumar_2
Honored Contributor

Re: snmp.conf filling after installing snmp patch on HP-UX 10.20

hi,

is your trap-dest reachable by ping ?.
does command "ll snmd.conf" every (say)30 seconds show any file size increase ?.
is your snmpd.conf file is having bad permissions like others writable ?.


regards,
U.SivaKumar
Innovations are made when conventions are broken
Rob Fisher
Advisor

Re: snmp.conf filling after installing snmp patch on HP-UX 10.20

U.SivaKumar,

I checked the IPs and they are all pingable at this time.

I also checked the permissions and the are all set to 400.

I am noticing that ALL of the IPs are within a small range of subnets. Some of these are dial-up IPs. Is there something that I could set to not allow those subnets to connect to snmp on these servers?
May the winds of life keep you on the right tack