[SNMP4J] Usm_Stats_Not_In_Time_Window problem in SNMP4j

Jigar Shah jigarshah5124 at yahoo.co.in
Tue Nov 16 17:05:53 CET 2010


Hi,

Thanks and sorry to ask you so many questions as I am new to SNMP.

Sorry I forgot to mention one thing here...I am using NESIM...I can see report in Ethereal file frm NE (Agent ) to EMS (Mgr)....so agent developer side everything should be fine.

 And second time means after both Mgr and Agent in sync, m reducing time of NESIM, So NESIM will send report saying usmStatsOutofTImeWindow after getting SET or GET request. 

I can see this report in Ethereal, but ReportHandler doesn't get invoke.

And One more thing I want to ask is if I dont override my own ReportHandler then default ReportHandler gets invoke on getting each Report from agent side to Mgr.

Regards
Jigar Shah 



--- On Tue, 16/11/10, Jochen Katz <katz at agentpp.com> wrote:

From: Jochen Katz <katz at agentpp.com>
Subject: Re: [SNMP4J] Usm_Stats_Not_In_Time_Window problem in SNMP4j
To: snmp4j at agentpp.org
Date: Tuesday, 16 November, 2010, 7:35 PM

Hi,

> I have written my own ReportHandler to handle usmStatsNotInTimeWindow.

> 2) Now communication is going smoothely as both r in sync. But if I
> change the time of NESIM (Decrease system time), so both wont be in sync.
> 
> -> now when manager sends SET or GET request to NE, NE will reply back
> with Report (usmStatsNotInTimeWindow), bcz manager has higher value of
> NE Boot or time diff is more than 150.
> 
> -> here m facing problem...On getting this Report my handler doesn't get
> invoke.

the report handler is not invoked, as the report is thrown away, because
it is too old.

If this happens, you have two options:
- Blame the developer of the agent and ask him to fix it
- Add some code to your application that resets time information for
those buggy agents (but only those) if you do not get a response any more.

Regards,
  Jochen
_______________________________________________
SNMP4J mailing list
SNMP4J at agentpp.org
http://lists.agentpp.org/mailman/listinfo/snmp4j





More information about the SNMP4J mailing list