Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

What is the log of snmp[1606]: PAPI_Send: To: 7f000001:8366 Type0x4 Time out

This thread has been viewed 1 times

  • 1.  What is the log of snmp[1606]: PAPI_Send: To: 7f000001:8366 Type0x4 Time out

    Posted Apr 10, 2014 03:18 AM

    What is the log of snmp[1606]: PAPI_Send: To: 7f000001:8366 Type0x4 Time out

     

    Sometimes it will send the log. Is it regarding for the AP?



  • 2.  RE: What is the log of snmp[1606]: PAPI_Send: To: 7f000001:8366 Type0x4 Time out

    EMPLOYEE
    Posted Apr 15, 2014 12:42 AM

    Hello,

    this specific error (port 8366) represents the hardware monitor, in this case the error is saying that some snmp query tried to talk to the hardware monitor and it timed out - by any chance is this a 600 series controller ?

    regards

    -jeff



  • 3.  RE: What is the log of snmp[1606]: PAPI_Send: To: 7f000001:8366 Type0x4 Time out

    Posted Apr 15, 2014 12:45 AM

    Yes, the device is Aruba 650 Controller.



  • 4.  RE: What is the log of snmp[1606]: PAPI_Send: To: 7f000001:8366 Type0x4 Time out

    EMPLOYEE
    Posted Apr 15, 2014 12:57 AM
    @HandSome123 wrote:

    Yes, the device is Aruba 650 Controller.

    ok, there is a known issue tracked as bug 87717 (it's missing from the known issues in release notes but I have just emailed the Technical Publications team to have it added).

     

    The issue is basically summarised as follows:

    1. 6xx controller performs a sleep when accessing a certain hardware device during periodic hardware monitoring

    2. if at that same time there is an incoming SNMP query for the OID wlsxSysExtCpuUsedPercent then the SNMP query times out before the sleep has finished.

    3. The issue is mostly cosmetic, it doesn't represent anything serious operationally, only that there is a random chance where wlsxSysExtCpuUsedPercent will return 0 due to collision between SNMP and this sleep mentioned in point 1).

    There is no ETA for the fix at this stage and it only affects the 6xx platform.

     

    regards

    -jeff