Wireless Access

last person joined: 3 hours ago 

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

Remote AP not show in show ap database

This thread has been viewed 13 times
  • 1.  Remote AP not show in show ap database

    Posted Apr 29, 2020 10:28 AM

    Hello,

    We have a cluster of MM with a VRRP address

    We have a MD cluster with a VRRP address

    We are in version 8.6.0.4

    We have NAT the MM cluster VRRP IP with a PUBLIC IP in order to connect a Remote AP303H to it.

    The Remote AP has been added to the Remote AP whitelist

    The Remote AP communicates well with the MM.

    However, we have the following error:

     

    cluster_mgr [4236]: <352302> <6023> <ERRS> | cluster_mgr | cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac <MAC>

     

    Have you ever had this problem ? and do you have a resolution?

    THANK YOU



  • 2.  RE: Remote AP not show in show ap database

    EMPLOYEE
    Posted Apr 29, 2020 11:13 AM

    The RAP needs to talk to the MD's public IP address, not the MM. APs do not terminate directly to the Mobility Master.



  • 3.  RE: Remote AP not show in show ap database

    Posted Apr 29, 2020 11:42 AM

    Hello, Thank you for your response, we have tested both solutions. With the public IP VRRP of the MD and with the public IP VRRP of the MM. We have the same error



  • 4.  RE: Remote AP not show in show ap database

    EMPLOYEE
    Posted Apr 29, 2020 12:00 PM

    For an MD cluster, all nodes in the cluster need to have a public IP. This public IP is defined in the cluster profile. Because the cluster returns a nodelist to the RAP, a single public IP is not supported. Have you done the cluster profile configuration for the MD cluster?



  • 5.  RE: Remote AP not show in show ap database

    Posted Apr 30, 2020 03:54 AM

    Hello,

    At the Managed Network level -> Configuration -> Services -> Cluster, we have a cluster with the 3 Private IP addresses of the 3 MDs. But we did not put a Public IP address. Each MD must with its own Public IP address? So we have to have 1 PUBLIC IP for VRRP, and 3 PUBLIC IP address for MDS?

    THANK YOU



  • 6.  RE: Remote AP not show in show ap database

    MVP EXPERT
    Posted Apr 30, 2020 04:04 AM

    That is correct, see the configuration snipped below where a public IP is defined as part of the cluster configuration:

     

    (host) [cluster] (config) #lc-cluster group-profile rapcluster
    (host) [cluster] (Classic Controller Cluster Profile "rapcluster") controller 10.10.10.1
    rap-public-ip 100.100.100.101
    (host) [cluster] (Classic Controller Cluster Profile "rapcluster")controller 10.10.10.2
    rap-public-ip 100.100.100.102
    (host) [cluster] (Classic Controller Cluster Profile "rapcluster")controller 10.10.10.3
    rap-public-ip 100.100.100.103
    (host) [cluster] (Classic Controller Cluster Profile "rapcluster")controller 10.10.10.4
    rap-public-ip 100.100.100.104


  • 7.  RE: Remote AP not show in show ap database

    Posted Apr 30, 2020 04:11 AM

    Hello, thank you for your answer,

    At the VRRP address (Managed Network -> Configuration -> Reundancy -> L2 redundancy) should I also indicate the PUBLIC IP address? Where should I indicate the PUBLIC IP address of my Private VRRP IP


    THANK YOU



  • 8.  RE: Remote AP not show in show ap database

    MVP EXPERT
    Posted Apr 30, 2020 04:19 AM

    This would be configured as a NAT on your firewall, you do not need to configure the Public IP of the VRRP within the controller.



  • 9.  RE: Remote AP not show in show ap database

    Posted Apr 30, 2020 04:23 AM

    When I modify my cluster configuration (controller 10.xxxx rap-public-ip 1xxxxx), I get the following error:

    Error: RAP public ip not configured for controller 10.xxxx, please configure RAP public IP to all controllers.

     

    thanks for the information Public IP VRRP



  • 10.  RE: Remote AP not show in show ap database

    MVP EXPERT
    Posted Apr 30, 2020 04:25 AM

    You'll need to delete the cluster and re-create it.



  • 11.  RE: Remote AP not show in show ap database

    Posted Apr 30, 2020 04:28 AM
    I have 600 AP in producation in Campus mode.
    what is the impact if i delete it?


  • 12.  RE: Remote AP not show in show ap database

    Posted Jun 29, 2020 04:07 AM

    Hello,

    I made the change: delete / create a cluster with public ip.

    my ap appears in show ap database but down

    and I have the following errors in the logs:

    Jun 24 08:07:38 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.293700] There is no gpio reset info
    Jun 24 08:07:38 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.713650] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 08:07:40 nanny[3576]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted caused by cold HW reset(power loss)
    Jun 24 08:09:01 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:10:32 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:11:42 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:12:52 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:14:13 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:15:33 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:17:04 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:18:14 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:19:25 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:20:35 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:21:45 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:22:56 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:24:06 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:25:37 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:26:57 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:28:18 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:29:38 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:30:59 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:32:09 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:33:19 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:34:30 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:35:50 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:37:01 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:38:11 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:39:32 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:53:26 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.216150] There is no gpio reset info
    Jun 24 08:53:26 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.601603] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 08:53:28 nanny[3576]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted caused by warm reset
    Jun 24 08:54:49 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:56:05 sapd[3631]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 08:56:06 nanny[3576]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 08:56:15 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 08:57:35 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.254356] There is no gpio reset info
    Jun 24 08:57:35 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.253789] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 08:57:38 nanny[3570]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:03:36 PST 1969; SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:01:41 sapd[3625]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4544 error redun_retry_tunnel: Switching to clear. Error:RC_ERROR_TUN_IP_ERR. Ipsec not successful after reboot.
    Jun 24 09:02:06 sapd[3625]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:02:07 nanny[3570]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:02:17 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 09:03:36 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.272573] There is no gpio reset info
    Jun 24 09:03:36 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.286418] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:03:38 nanny[3610]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:28 PST 1969; SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:07:41 sapd[3665]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4539 error redun_retry_tunnel: Ipsec not successful to saved lms. Error:RC_ERROR_TUN_IP_ERR. rebooting.
    Jun 24 09:07:43 nanny[3610]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:07:43 sapd[3665]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: Unable to set up IPSec tunnel to saved lms, Error:RC_ERROR_TUN_IP_ERR
    Jun 24 09:09:12 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.294974] There is no gpio reset info
    Jun 24 09:09:12 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.311347] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:09:14 nanny[3568]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:03 PST 1969; Unable to set up IPSec tunnel to saved lms, Error:RC_ERROR_TUN_IP_ERR
    Jun 24 09:13:16 sapd[3623]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4544 error redun_retry_tunnel: Switching to clear. Error:RC_ERROR_TUN_IP_ERR. Ipsec not successful after reboot.
    Jun 24 09:13:41 nanny[3568]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:13:41 sapd[3623]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:13:51 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 09:15:10 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.279443] There is no gpio reset info
    Jun 24 09:15:10 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.247825] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:15:13 nanny[3574]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:25 PST 1969; SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:19:58 sapd[3629]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4539 error redun_retry_tunnel: Ipsec not successful to saved lms. Error:RC_ERROR_TUN_IP_ERR. rebooting.
    Jun 24 09:20:00 sapd[3629]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: Unable to set up IPSec tunnel to saved lms, Error:RC_ERROR_TUN_IP_ERR
    Jun 24 09:20:01 nanny[3574]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:21:29 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.264871] There is no gpio reset info
    Jun 24 09:21:29 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.242433] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:21:32 nanny[3661]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:46 PST 1969; Unable to set up IPSec tunnel to saved lms, Error:RC_ERROR_TUN_IP_ERR
    Jun 24 09:25:34 sapd[3716]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4544 error redun_retry_tunnel: Switching to clear. Error:RC_ERROR_TUN_IP_ERR. Ipsec not successful after reboot.
    Jun 24 09:25:59 sapd[3716]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:26:00 nanny[3661]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:26:09 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 09:27:29 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.234128] There is no gpio reset info
    Jun 24 09:27:29 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.219479] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:27:31 nanny[3573]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:26 PST 1969; SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:31:33 sapd[3628]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4539 error redun_retry_tunnel: Ipsec not successful to saved lms. Error:RC_ERROR_TUN_IP_ERR. rebooting.
    Jun 24 09:31:35 sapd[3628]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: Unable to set up IPSec tunnel to saved lms, Error:RC_ERROR_TUN_IP_ERR
    Jun 24 09:31:36 nanny[3573]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:33:04 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.235630] There is no gpio reset info
    Jun 24 09:33:04 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.234141] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:33:07 nanny[3568]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:03 PST 1969; Unable to set up IPSec tunnel to saved lms, Error:RC_ERROR_TUN_IP_ERR
    Jun 24 09:37:10 sapd[3626]: <311020> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| An internal system error has occurred at file sapd_redun.c function redun_retry_tunnel line 4544 error redun_retry_tunnel: Switching to clear. Error:RC_ERROR_TUN_IP_ERR. Ipsec not successful after reboot.
    Jun 24 09:37:35 sapd[3626]: <311002> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 sapd| Rebooting: SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)
    Jun 24 09:37:36 nanny[3568]: <303086> <ERRS> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Jun 24 09:37:45 cluster_mgr[4236]: <352302> <6023> <ERRS> |cluster_mgr| cmlb_ap_handle_ap_down_request, No entry in active table in LB-AP thread for AP with mac 20:4c:03:58:dd:c6
    Jun 24 09:39:04 KERNEL(20:4c:03:58:dd:c6@(none)): [ 18.262175] There is no gpio reset info
    Jun 24 09:39:04 KERNEL(20:4c:03:58:dd:c6@(none)): [ 35.233893] uol_init_driver:409 HW offload not applicable, AP will use cutting through path!
    Jun 24 09:39:07 nanny[3574]: <303022> <WARN> |AP 20:4c:03:58:dd:c6@192.168.0.39 nanny| Reboot Reason: AP rebooted Wed Dec 31 16:05:27 PST 1969; SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)


    What can I do?

     

    Thanks