Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 13 of 13
  1. #1

    WA901ND v3: Invalid sysUpTime

    Model :

    Hardware Version : Not Clear

    Firmware Version :

    ISP : [/COLOR]

    Hello there.

    If I log in to the WA901ND admin page it shows me at the bottom of the page the System Up Time like 22 days 18:24:57 what corrosponds with the systems logfile and is the real uptime of the system.
    If I do an SNMP get to OID .iso.org.dod.internet.mgmt.mib-2.system.sysUpTime (.1.3.6.1.2.1.1.3) I get as response 367 days, 15 hours, 46 minutes, 57 seconds...

    root@SR09P1:~# snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (3176588791) 367 days, 15:51:27.91

    Is there a different unterstanding of the OID or an other OID to read the correct sysUpTime?

    Thanks in advance
    Stefan

  2. #2
    SysUpTime in TL-WA901ND is the running time since the device is powered.
    While using SNMP it means the SNMP Agent's running time, in another word, the monitoring time.

  3. #3
    So far so good. The funny thing is that the last power off was 22 days ago ... and I'm shure, the SNMP agent was down too at this moment

  4. #4
    Can you reboot the device and obtain again of the SysUpTime via SNMP to see if the value is still fabulous?

  5. #5
    Indeed, they are. I've powerd down the device again and have monitored the sysUpTime while the devices was comming up again:


    root@SR09P1:~#
    root@SR09P1:~# while [ 1 ] ; do date; echo $cmd; $cmd; echo ""; sleep 1; done
    Tue Jan 5 10:12:11 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    Timeout: No Response from 192.168.6.250.

    ...

    Tue Jan 5 10:12:46 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (97) 0:00:00.97

    Tue Jan 5 10:12:49 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (200) 0:00:02.00

    Tue Jan 5 10:12:50 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (303) 0:00:03.03

    ...

    Tue Jan 5 10:13:35 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (4770) 0:00:47.70

    Tue Jan 5 10:13:36 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (3191887182) 369 days, 10:21:11.82

    Tue Jan 5 10:13:37 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (3191887286) 369 days, 10:21:12.86

    Tue Jan 5 10:13:38 GMT 2016
    snmpget -v 2c -c public 192.168.6.250 .1.3.6.1.2.1.1.3.0
    iso.3.6.1.2.1.1.3.0 = Timeticks: (3191887390) 369 days, 10:21:13.90

    ^C
    root@SR09P1:~#

    As you can see in the log above the sysUpTime starts correctly and changes to an invalid value after 47 seconds. This behavior looks like a bug to me.

    By the way the device is
    Firmware Version: 3.16.9 Build 150409 Rel.60640n
    Hardware Version: WA901ND v3 00000000

  6. #6
    It is not the only bug in the 901ND Access Point. Even the emailing of the syslog does not work at all.
    If someone has managed to email the syslog, please ... show up and ... provide evidence!!!

  7. #7
    Quote Originally Posted by torque View Post
    As you can see in the log above the sysUpTime starts correctly and changes to an invalid value after 47 seconds. This behavior looks like a bug to me.

    By the way the device is
    Firmware Version: 3.16.9 Build 150409 Rel.60640n
    Hardware Version: WA901ND v3 00000000

    I borrow a 901V3 and do the test but didn't meet your situation. I use MIB Broswer with SNMPv2C as yours. You can see the below log that when in 1min the time is still correct:

    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50941 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:32s.96th (9296)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50943 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:34s.77th (9477)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50945 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:36s.10th (9610)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50947 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:37s.27th (9727)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50949 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:38s.96th (9896)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50951 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:40s.26th (10026)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50953 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:41s.12th (10112)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50955 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:41s.99th (10199)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50957 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:42s.83th (10283)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50959 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:43s.74th (10374)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50961 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:44s.93th (10493)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 50963 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:45s.79th (10579)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 49295 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:46s.71th (10671)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 49297 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:47s.64th (10764)


    Remote address: 192.168.0.254 port: 161 transport: IP/UDP
    Local address: 192.168.0.11 port: 49299 transport: IP/UDP
    Protocol version: SNMPv2c
    1: sysUpTimeInstance (timeticks) 0 days 00h:01m:48s.79th (10879)
    Last edited by stupidbird; 01-07-2016 at 02:31.

  8. #8
    Quote Originally Posted by aster1x View Post
    It is not the only bug in the 901ND Access Point. Even the emailing of the syslog does not work at all.
    If someone has managed to email the syslog, please ... show up and ... provide evidence!!!
    Would you please share us with your syslog? I've try this function on my 901ND V4 and it works. The below you should pay attention:
    1. Username/Password of the E-Mail should be correct. Double check.
    2. The device should be able to access internet.
    3. Gateway is needed to setup.
    4. Which E-Mail do you use? This function doesn't support SSL/TLS encryption mailbox.

  9. #9
    Sending syslog via email works fine on my device. The destination is a local account in my network and every day at scheduled time the logfile is mailed. Every logitem has a correct timestamp.

  10. #10
    @stupidbird
    Can you suggest a public email provider who does not require somekind of mailbox encryption? Gmail for one, requires TLS encryption.

  11. #11
    @ torque
    Which email provider do you use to send the email for the syslog?
    Also which hardware version and which firmware version do you have?

  12. #12
    I send it to my internal mail system hosted on a Synology NAS. The account is a SMTP with authentication but without encryption.
    Maybe the reason emailing didn't work is that the provider has establishd SSL/TSL for client access... and you can't set up security acces for SMTP nor the port to use.
    An other reason could be that the provider identified the mail as spam and dropped it.

    My device states like
    Firmware Version: 3.16.9 Build 150409 Rel.60640n
    Hardware Version: WA901ND v3 00000000

  13. #13
    Did anyone find a resolution to this? We have a large number of these devices which yesterday suddenly all started reporting the wrong uptime. The behaviour is exactly the same as that described above - the uptime is correct until about 47 seconds after booting up and then changes to around 196 days.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.