Re: Disman events and sysName under Solaris 10
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 30/03/07, Ward, Martin <[email protected]> wrote: > monitor -r 30 -o sysName.0 -o laNames -o laErrMessage > "laTable" laErrorFlag != 0 > If I take the sysName bit out... > It works OK. That makes sense. This is a wildcarded monitor entry, so it will match any row where laErrorFlag.X is non-zero. It will then use the matching index (X) when constructing the trap. You've told it to add three varbinds - sysName.0, laNames and laErrorMessage. All of these are specfied as objects, so the agent will add the matching index value X, to give sysName.0.X laNames.X laErrorMessage.X laNames.X and laErrorMessage.X are fine, but sysName.0.X is bogus, so the agent can't construct the varbind list for the trap. Since this is already an exact instance, the agent doesn't need to add the index value. But you need to tell it that this *is* an exact instance. Try monitor -r 30 -i sysName.0 -o laNames -o laErrMessage "laTable" laErrorFlag != 0 Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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