Hello Dave,

> OK - try the following:
>
> In /var/net-snmp/snmpd.conf:
> createUser internal MD5 "some password"
>
> In /usr/local/share/snmp/snmpd.conf: (or wherever your snmpd.conf file

is):
> trap2sink {monitorHost} public
> rouser internal
> monitor -u internal "inSync" .1.3.6.1.4.1.17887.7.6.1.2 == 1
> monitor -u internal "outSync" .1.3.6.1.4.1.17887.7.6.1.2 == 2
>
> That should generate a trap whenever any of the RTS-MIB::Pair1Local
> objects takes the value 1 or 2
>
> If you need to cover the other link values as well (i.e. Pair2Local, and
> Pair{1,2}Remote), then try:
> monitor -u internal "inSync" .1.3.6.1.4.1.17887.7.6.1 == 1
> monitor -u internal "outSync" .1.3.6.1.4.1.17887.7.6.1 == 2



This seems to be Fine

And the problem here is I am not sure that who all use these Boards will use
Net-Snmp as a Manager

If they are using any other properitary SNMP Manager then the above setup
will not work na

please clarify this confusion

thanks
santhosh



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642
_______________________________________________
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/...net-snmp-users