Re: Regarding traps

> I am monitoring free radius server, so when I shutdown radius server in
> the manager side I am getting the following traps. I am not
> understanding these terminologies whether these traps received are
> correct or not.

This looks OK to me.


> Minor    10/06/2006 12:45:01 10.0.0.2  mteTriggerFired
      The name of the trap - i.e. telling you that a trigger has fired.
Followed by a description of this trigger:

>      [1] mteHotTrigger.0 (DisplayString): Process radiusd
>      [2] mteHotTargetName.0 (DisplayString):
>      [3] mteHotContextName.0 (DisplayString):
>      [4] mteHotOID.0 (Object ID): prErrorFlag.1
>      [5] mteHotValue.0 (Integer): 1

[1] is the description from the trigger that's fired
[4] is the instance that's being watched, and [5] is the value of this instance

So this is telling you that peErrorFlag.1 has the value 1

The final two varbinds are extra ones, added by the agent to help
describe this trigger:

>      [6] prNames.1 (DisplayString): radiusd
>      [7] prErrMessage.1 (DisplayString): Too few radiusd running (# = 0)

[6] is the name from the "proc" entry that caused the trigger to fire, and
[7] is the error messsage from this entry.


OK?

Dave

-------------------------------------------------------------------------
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=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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