ISSUE with SNMPv3 - USM : not in time window

[CyaNn]

Hello all,

We have an issue with a NMS we interrogate through SNMPv3 driver.
The first connection works fine, but after restarting the SNMPv3 driver, the NMS refuse the connection. The error message is the following : USM Not in time window.

What does it mean and how to fix it, please ?

This strange behavior was only observed with the wincc driver. With mib browser, for example, it's work fine.

[leoknipp]

Hello,

are you talking about WinCC OA or WinCC?
Is the error reported by the SNMP dirver or the NMS device?
If the error is reported by the driver please send us the complete content of the log message. Otherwise please get in contact with the vendor for the NMS.

In case of WinCC OA it would be useful to know which operating system and WinCC OA version you are using.

Best Regards
Leopold Knipp
Senior Support Specialist

[CyaNn]

Hello and thanks for your response.

The problem occured Wincc side and was reported by the SNMP Driver.
The version of the software is WinccOA 3.10
The version of windows is Windows 2008 Server R2 Service Pack 1.

The error was found on the internal DP :
_1_SNMPV3Entity_5.Status.ErrorOID
And the value was :
1.3.6.1.6.3.15.1.1.2.0#A5_1.3.6.1.4.1.23491.1.7.2.0 - error : SNMPv3: USM: Message not in TimeWindow

Thanks a lot in advance.
Regards
Yann

[CyaNn]

Hello there,

Do you have any solution for us ?
We are stuck with this problem.

[CyaNn]

I have made a wireshark capture https://www.winccoa.com/fileadmin/image ... _short.zip of the situation observed in our WinCC Server.
We can see the first problem observed was the lake of engineID, but is is resolved in the second sending of WinCC.
But the engineboots and enginetime parameters sent by WinCC SNMP Driver are wrong (around 0) and maintained wrong; then the NMS refuse the connection.

The problem seems to be in SNMP driver side.
Please, anyone can help us ? Or tell me the support center email to sent them this issue ?