https://community.extremenetworks.com/t5/faqs/snmp-informs-no-longer-received-after-netsight-atlas-console/m-p/48472#M529 Article ID: 10008 <BR /> <BR /> <B>Products</B><BR /> NetSight Atlas Console <BR /> <BR /> <B>Changes</B><BR /> NetSight was installed an another system, which changed its SNMP engineID. <BR /> <BR /> <B>Symptoms</B><BR /> SNMP Inform messages from network switches are no longer accepted by the NetSight server machine. <BR /> <BR /> <B>Cause</B><BR /> The (Inform receiver's, i.e. NetSight's) SNMP engineID (unique to each NetSight server machine) that is configured on the switches (<A href="http://bit.ly/1c2NN3S" target="_blank" rel="nofollow noreferrer noopener">5390</A>) must match the one that is configured on the NetSight server - or the messages will be dropped. <BR /> <BR /> <B>Solution/Workaround</B><BR /> To change the configured engineID on the NetSight server:<BR /> <OL> <LI>Stop the SNMPtrap service.<UL>Windows: Use the NetSight Service Manager icon in the Desktray to stop the SNMPtrap service.<UL>Linux: /etc/rc2.d/S99nssnmptrapd stop</UL> <LI>Edit the following snmptrapd.conf file:<UL><I>\NetSight\services\snmptrapd.conf</I></UL> </LI><LI>Modify the oldEgineId line to reflect the engineID that is currently configured on the switch.<BR /> </LI><LI>Start the snmptrap service again.<UL>Windows: Use the NetSight Service Manager icon in the Desktray to start the SNMPtrap service.</UL><UL>Linux: /etc/rc2.d/S99nssnmptrapd start</UL></LI></UL>See also: <A href="http://bit.ly/1cxxLx4" target="_blank" rel="nofollow noreferrer noopener">9923</A>.</LI></OL> Thu, 05 Sep 2013 06:02:00 GMT FAQ_User 2013-09-05T06:02:00Z https://community.extremenetworks.com/t5/faqs/snmp-informs-no-longer-received-after-netsight-atlas-console/m-p/48472#M529 Article ID: 10008 <BR /> <BR /> <B>Products</B><BR /> NetSight Atlas Console <BR /> <BR /> <B>Changes</B><BR /> NetSight was installed an another system, which changed its SNMP engineID. <BR /> <BR /> <B>Symptoms</B><BR /> SNMP Inform messages from network switches are no longer accepted by the NetSight server machine. <BR /> <BR /> <B>Cause</B><BR /> The (Inform receiver's, i.e. NetSight's) SNMP engineID (unique to each NetSight server machine) that is configured on the switches (<A href="http://bit.ly/1c2NN3S" target="_blank" rel="nofollow noreferrer noopener">5390</A>) must match the one that is configured on the NetSight server - or the messages will be dropped. <BR /> <BR /> <B>Solution/Workaround</B><BR /> To change the configured engineID on the NetSight server:<BR /> <OL> <LI>Stop the SNMPtrap service.<UL>Windows: Use the NetSight Service Manager icon in the Desktray to stop the SNMPtrap service.<UL>Linux: /etc/rc2.d/S99nssnmptrapd stop</UL> <LI>Edit the following snmptrapd.conf file:<UL><I>\NetSight\services\snmptrapd.conf</I></UL> </LI><LI>Modify the oldEgineId line to reflect the engineID that is currently configured on the switch.<BR /> </LI><LI>Start the snmptrap service again.<UL>Windows: Use the NetSight Service Manager icon in the Desktray to start the SNMPtrap service.</UL><UL>Linux: /etc/rc2.d/S99nssnmptrapd start</UL></LI></UL>See also: <A href="http://bit.ly/1cxxLx4" target="_blank" rel="nofollow noreferrer noopener">9923</A>.</LI></OL> Thu, 05 Sep 2013 06:02:00 GMT https://community.extremenetworks.com/t5/faqs/snmp-informs-no-longer-received-after-netsight-atlas-console/m-p/48472#M529 FAQ_User 2013-09-05T06:02:00Z