RE: nsNotifyRestart trap raised frequently
Hi Bill, Please review the below SNMP configuration in the agent. sysContact IT-IS sysLocation ECM sysName adc001101.engel.int # snmpd Configuration File # # Copy this file to /mpsconfig, and make changes to /mpsconfig/snmpd.conf # Changes in /etc/snmpd.conf will be lost following a reboot. # # The following are example for snmpd.conf. # #SNMP Trap Destination example #trap2sink 1.2.3.4:162 public sysobjectid 1.3.6.1.4.1.5951.6 exactEngineID 0x80001f888026bda253cc8fa856 rocommunity _9TikE06:wvtXG_4X_G 10.19.53.62 trap2sink 10.19.53.62:162 _9TikE06:wvtXG_4X_G rocommunity _9TikE06:wvtXG_4X_G 10.6.53.25 rocommunity _9TikE06:wvtXG_4X_G 10.6.53.26 trap2sink 10.6.53.25:162 _9TikE06:wvtXG_4X_G trap2sink 10.6.53.26:162 _9TikE06:wvtXG_4X_G trap2sink 1.1.1.1:162 public Is there something not obvious/special that could cause the trap being generated ? Thank you Krishna Vivek From: Bill Fenner Sent: 29 April 2019 21:52 To: Krishna Vivek Vitta Cc: net-snmp-users@lists.sourceforge.net Subject: Re: nsNotifyRestart trap raised frequently Hello Krishna, I did a Google search for 'nsNotifyRestart' and one of the results was http://net-snmp.sourceforge.net/wiki/index.php/FAQ:Agent_15 . This page describes when the nsNotifyRestart trap is sent. Bill On Wed, Apr 24, 2019 at 7:28 AM Krishna Vivek Vitta mailto:krishna.vivekvi...@citrix.com>> wrote: Hello experts, We found that nsNotifyRestart is thrown frequently(every 2 hrs) and same has been reported in snmpd.log. There are no changes in snmp configuration in the SNMP manager and process id of SNMP is also not altering. NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted Customer using third party syslog WhatsUpGold. Given below is the TRAP details which customer getting in email: PassiveMonitor.Payload.TrapName=nsNotifyRestart PassiveMonitor.Payload.TrapMajor=6 PassiveMonitor.Payload.TrapMinor=3 PassiveMonitor.Payload.ObjectLong=1.3.6.1.4.1.8072.4 (netSnmpNotificationPrefix) PassiveMonitor.Payload.snmpTrapOID.0=1.3.6.1.4.1.8072.4.0.3 (nsNotifyRestart) PassiveMonitor.Payload.1.3.6.1.2.1.1.3.0=10days 16:00:33.69 PassiveMonitor.Payload.snmpTrapEnterprise.0=1.3.6.1.4.1.8072.4 (netSnmpNotificationPrefix) PassiveMonitor.Payload.Object=netSnmpNotificationPrefix PassiveMonitor.Payload.Timetick=10days 16:00:33.69 PassiveMonitor.Payload.Packet Type=SNMPv2 Trap PassiveMonitor.Payload.1.3.6.1.6.3.1.1.4.1.0=1.3.6.1.4.1.8072.4.0.3 PassiveMonitor.Payload.Protocol Version=SNMPv2 PassiveMonitor.Payload.CommunityName=_9TikE06:wvtXG_4X_G PassiveMonitor.Payload.1.3.6.1.6.3.1.1.4.3.0=1.3.6.1.4.1.8072.4 PassiveMonitor.Payload.sysUpTimeInstance=10days 16:00:33.69 Can you tell on what cases this trap is raised and what are the steps that can be taken to prevent from being raised. Thank you Krishna Vivek ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net<mailto:Net-snmp-users@lists.sourceforge.net> Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
Re: nsNotifyRestart trap raised frequently
Hello Krishna, I did a Google search for 'nsNotifyRestart' and one of the results was http://net-snmp.sourceforge.net/wiki/index.php/FAQ:Agent_15 . This page describes when the nsNotifyRestart trap is sent. Bill On Wed, Apr 24, 2019 at 7:28 AM Krishna Vivek Vitta < krishna.vivekvi...@citrix.com> wrote: > Hello experts, > > > > We found that nsNotifyRestart is thrown frequently(every 2 hrs) and same > has been reported in snmpd.log. There are no changes in snmp configuration > in the SNMP manager and process id of SNMP is also not altering. > > > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > NET-SNMP version 5.5 restarted > > > > Customer using third party syslog WhatsUpGold. > > > > Given below is the TRAP details which customer getting in email: > > > > *PassiveMonitor.Payload.TrapName=nsNotifyRestart* > > *PassiveMonitor.Payload.TrapMajor=6* > > *PassiveMonitor.Payload.TrapMinor=3* > > *PassiveMonitor.Payload.ObjectLong=1.3.6.1.4.1.8072.4 > (netSnmpNotificationPrefix)* > > *PassiveMonitor.Payload.snmpTrapOID.0=1.3.6.1.4.1.8072.4.0.3 > (nsNotifyRestart) PassiveMonitor.Payload.1.3.6.1.2.1.1.3.0=10days > 16:00:33.69* > > *PassiveMonitor.Payload.snmpTrapEnterprise.0=1.3.6.1.4.1.8072.4 > (netSnmpNotificationPrefix) > PassiveMonitor.Payload.Object=netSnmpNotificationPrefix* > > *PassiveMonitor.Payload.Timetick=10days 16:00:33.69 > PassiveMonitor.Payload.Packet Type=SNMPv2 Trap* > > *PassiveMonitor.Payload.1.3.6.1.6.3.1.1.4.1.0=1.3.6.1.4.1.8072.4.0.3* > > *PassiveMonitor.Payload.Protocol Version=SNMPv2 > PassiveMonitor.Payload.CommunityName=_9TikE06:wvtXG_4X_G* > > *PassiveMonitor.Payload.1.3.6.1.6.3.1.1.4.3.0=1.3.6.1.4.1.8072.4* > > *PassiveMonitor.Payload.sysUpTimeInstance=10days 16:00:33.69* > > > > Can you tell on what cases this trap is raised and what are the steps that > can be taken to prevent from being raised. > > > > > > Thank you > > Krishna Vivek > > > ___ > Net-snmp-users mailing list > Net-snmp-users@lists.sourceforge.net > Please see the following page to unsubscribe or change other options: > https://lists.sourceforge.net/lists/listinfo/net-snmp-users > ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
nsNotifyRestart trap raised frequently
Hello experts, We found that nsNotifyRestart is thrown frequently(every 2 hrs) and same has been reported in snmpd.log. There are no changes in snmp configuration in the SNMP manager and process id of SNMP is also not altering. NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted NET-SNMP version 5.5 restarted Customer using third party syslog WhatsUpGold. Given below is the TRAP details which customer getting in email: PassiveMonitor.Payload.TrapName=nsNotifyRestart PassiveMonitor.Payload.TrapMajor=6 PassiveMonitor.Payload.TrapMinor=3 PassiveMonitor.Payload.ObjectLong=1.3.6.1.4.1.8072.4 (netSnmpNotificationPrefix) PassiveMonitor.Payload.snmpTrapOID.0=1.3.6.1.4.1.8072.4.0.3 (nsNotifyRestart) PassiveMonitor.Payload.1.3.6.1.2.1.1.3.0=10days 16:00:33.69 PassiveMonitor.Payload.snmpTrapEnterprise.0=1.3.6.1.4.1.8072.4 (netSnmpNotificationPrefix) PassiveMonitor.Payload.Object=netSnmpNotificationPrefix PassiveMonitor.Payload.Timetick=10days 16:00:33.69 PassiveMonitor.Payload.Packet Type=SNMPv2 Trap PassiveMonitor.Payload.1.3.6.1.6.3.1.1.4.1.0=1.3.6.1.4.1.8072.4.0.3 PassiveMonitor.Payload.Protocol Version=SNMPv2 PassiveMonitor.Payload.CommunityName=_9TikE06:wvtXG_4X_G PassiveMonitor.Payload.1.3.6.1.6.3.1.1.4.3.0=1.3.6.1.4.1.8072.4 PassiveMonitor.Payload.sysUpTimeInstance=10days 16:00:33.69 Can you tell on what cases this trap is raised and what are the steps that can be taken to prevent from being raised. Thank you Krishna Vivek ___ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
