Wireless Access

 View Only
  • 1.  SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.

    Posted Dec 29, 2023 08:42 AM

    Seeing this in all MC/WC devices and would like to understand what is going on and how to resolve the problem.

    MC/WC devices are all provisioned in Airwave.

    Dec  4 07:27:15 2023  snmp[3845]: <301135> <3845> <WARN> |snmp|  SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.
    Dec  4 07:29:19 2023  snmp[3845]: <301135> <3845> <WARN> |snmp|  SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.
    Dec  4 07:30:28 2023  snmp[3845]: <301135> <3845> <WARN> |snmp|  SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.

    Happy New Year



  • 2.  RE: SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.

    Posted Jan 02, 2024 08:15 AM

    The message 'Not in life time window' would suggest me to have a look at the time on all of your devices. It's recommended to use NTP to synchronize the device clock to the same time source.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.

    Posted Jan 02, 2024 02:46 PM

    Thanks Herman.

    I re-checked and all NTP configs and reachability are good, and devices are all in sync.

    Curious about the 'WARNING' regarding the local-interface.

    =====================

    [mynode] #show ntp servers
    NTP version is ntp-4.2.8p15.
    NTP Server Table Entries
    ------------------------
    Flags:     * Selected for synchronization
               + Included in the final selection set
               # Selected for synchronization but distance exceeds maximum
               - Discarded by the clustering algorithmn
               = mode is client

      remote                                  local                                    st   poll   reach    delay     offset      disp
    =========================================================================================================================================
    =14@.@@@.@@@.14                           10.8.36.70                                1 1024     377    0.00021    +0.000097    0.01074
    *14@.@@@.@@@.238                          10.8.36.70                                1 1024     377    0.00258    +0.000058    0.00871
    =14@.@@@.@@@.254                          10.8.36.70                                1 1024     377    0.01141    +0.000046    0.01030
    =14@.@@@.@@@.142                          10.8.36.70                                1 1024     377    0.00174    +0.000092    0.00905
    :-WARNING-:
    Upstream NTP Server(s) are configured, but NOT reachable via local-interface!




  • 4.  RE: SNMP V3 Message parse error: Not in life time window failure in case of authoritative local engine id.

    Posted Jan 03, 2024 04:40 AM

    I checked internally and found that this message can be because SNMP traps cannot be sent, like the trap destination is not reachable.

    And for Airwave managed controllers/conductors this message is expected and can be ignored:

    "Airwave does send an empty get request every time a session is created. In this case, during the unresponsive state of the controller, airwave is trying to create a session and sending an empty get request message. That is why the controller is replying with this report message and hence we are throwing this warning message."

    It may be good to open a TAC case to get a confirmation if this is the case in your situation as well.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------