Wireless Access

last person joined: 21 hours ago 

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

PAPI_Send: sendto RF Client Failed message

This thread has been viewed 4 times

  • 1.  PAPI_Send: sendto RF Client Failed message

    MVP
    Posted Nov 01, 2016 10:49 AM

    Good morning everyone,

     

    Worked with a customer recently who did not have CPSec enabled. Due to the security risk, we enabled it with Auto Cert Provisioning enabled as to not affect his AP deployments. He just reached out and saw these errors showing in the logs:

     

    PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 4711

    PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 4712

    PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 4711

    PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 4712

    PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 4711

    PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 4712

     

    Is this anything to be concerned about? He is not reporting any connectivity or communication issues, just wanted to make sure this wasn't something that needed to be checked out further.

     

    Thanks.



  • 2.  RE: PAPI_Send: sendto RF Client Failed message

    Posted Nov 21, 2016 05:25 PM

    Hello,

     

    I'm having the same sort of messages in Process Logs.

     

    My test setup is a Aruba 620 controller running AOS 6.4.4.9 and 3x AP105, 1x AP125 and a AP275. I'm trying to setup a mesh network to prepare before going to customer site. Suddenly the system got non-responsive for a few minutes and then all mesh-point APs were rebooting. The mesh portal stayed online. Little problem I have is not enough licences on the controller but that doesn't seem to matter as long as you don't broadcast an SSID.

    Nov 21 13:48:40sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:48:45sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:48:45sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:48:50sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:48:50sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:48:55sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:48:55sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:49:00sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:49:00sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:49:05sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:49:05sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:49:10sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:49:10sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:49:15sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:49:15sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:49:20sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 9
    Nov 21 13:49:20sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 12
    Nov 21 13:49:25sapd[805]: <311020> <ERRS> |AP AP125-c9:e0:1a@172.16.11.24 sapd| An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1003 arg 0x649324.
    Nov 21 13:49:25sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:25sapd[805]: <311020> <ERRS> |AP AP125-c9:e0:1a@172.16.11.24 sapd| An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1005 arg 0x64933c.
    Nov 21 13:49:25sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:49:30sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:30sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:49:35sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:35sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:49:40sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:40sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:49:45sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:45sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:49:50sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:50sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:49:55sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:49:55sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:50:00sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:50:00sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:50:05sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:50:05sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:50:10sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:50:10sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:50:14webui[1587]: USER:admin@172.16.11.26 COMMAND:<clear provisioning-ap-list > -- command executed successfully
    Nov 21 13:50:14webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap read-bootinfo ap-name "AP125-c9:e0:1a" > -- command executed successfully
    Nov 21 13:50:14sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 15
    Nov 21 13:50:14sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 16
    Nov 21 13:50:19sapd[805]: <311020> <ERRS> |AP AP125-c9:e0:1a@172.16.11.24 sapd| An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1003 arg 0x649324.
    Nov 21 13:50:19sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 17
    Nov 21 13:50:19sapd[805]: <311020> <ERRS> |AP AP125-c9:e0:1a@172.16.11.24 sapd| An internal system error has occurred at file sapd_msg.c function sapd_papi_snd_cb line 1484 error Message to 127.0.0.1:RF Client failed: err Connection timed out msgcode 1005 arg 0x64933c.
    Nov 21 13:50:19sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 18
    Nov 21 13:50:24sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 17
    Nov 21 13:50:24sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 18
    Nov 21 13:50:29sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 17
    Nov 21 13:50:29sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 18
    Nov 21 13:50:34sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 17
    Nov 21 13:50:34sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 18
    Nov 21 13:50:39sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1003 Sequence Num is 17
    Nov 21 13:50:39sapd[805]: PAPI_Send: sendto RF Client failed: No such file or directory Message Code 1005 Sequence Num is 18
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap copy-provisioning-params ap-name "AP125-c9:e0:1a" > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap installation default > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap no external-antenna > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap server-name "aruba-master" > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap ap-group "Outdoor" > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap ap-name "AP125-OutdoorMeshPoint04" > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap no syslocation > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap mesh-role mesh-point > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap no remote-ap > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<provision-ap reprovision ap-name "AP125-c9:e0:1a" > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<clear provisioning-ap-list > -- command executed successfully
    Nov 21 13:50:42webui[1587]: USER:admin@172.16.11.26 COMMAND:<clear provisioning-params > -- command executed successfully
    Nov 21 13:50:49sapd[805]: <311002> <WARN> |AP AP125-c9:e0:1a@172.16.11.24 sapd| Rebooting: SAPD: Rebooting after provisioning
    Nov 21 13:50:50nanny[746]: <303086> <ERRS> |AP AP125-c9:e0:1a@172.16.11.24 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Nov 21 13:50:54System log daemon exiting.

    Might not be releated though....:-)

     

     



  • 3.  RE: PAPI_Send: sendto RF Client Failed message

    EMPLOYEE
    Posted Nov 21, 2016 06:03 PM

    What are the mesh points connected to?