Re: nsNotifyRestart trap raised frequently

Bill Fenner <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <CAF4SogZBU_o3jQ9ZGtNchhiDa3ysU84DbsL6KSwz_xi+zbB7xA@mail.gmail.com>
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 <
[email protected]> 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
> [email protected]
> 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
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.