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.
Expand all | Collapse all

RAP not connecting to controller

This thread has been viewed 14 times
  • 1.  RAP not connecting to controller

    Posted May 16, 2016 07:59 AM

    Hi All,

     

    Trying my luck here. I recently moved our controller within our infrastructure and it resulted in, among other things, that the RAP will communicate with the controller using a new public IP (announced through DNS). I have verified that UDP4500 is passed to the controller. I have also checked the security log on the controller and it seems the RAP traffic reach the controller. 

     

    However, I also noticed an error message (in the log) that I haven't been able to decipher nor find any posts on. Perhaps you could give me a hint on what is causing this error or how to continue my quest to get the RAP to connect?

     

    Note: Please note that I have masked the external IP address (1.2.256.256)

    Note: Please note that I have masked the internal (controller) IP address (192.168.1.10). There is a static NAT in the firewall to the internal IP of the controller. 

     

    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> #RECV 423 bytes from 1.2.256.256(55067) at 192.168.1.10 (3561611.448)
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> spi={3d00656522f9c1dc 0000000000000000} np=SA
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> exchange=IKE_SA_INIT msgid=0 len=419
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> check_aruba_ap_vid: aruba ap eth0 mac address 000b8682ea64 vidLen = 26
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> IKE2_checkCookie notify-cookie ip:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> IPSEC_findSaByIP addr:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> IPSEC_findSaByIP pxSa:(nil) status:0
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> IPSEC_findSaByIP finished with pxSa:(nil) status:0
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> IKE2_checkCookie finished with ipsecSa:(nil) status:0
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> delete_cp_route entered with ip:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> controlplaneRouteModify entered with ip:4e4622dc/ffffffff
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> controlplaneRouteModify after socket:35 with ip:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> controlplaneRouteModify socket:35 request:35084 dev:tsgw rtflags:0 with ip:1.2.256.256
    May 16 13:37:27 :103060: <DBUG> |ike| 1.2.256.256:55067-> ipc.c:controlplaneRouteModify:5187 Failed to Delete Route in Kernel: error:No such process
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> controlplaneRouteModify after ioctl sock:35 with ip:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> controlplaneRouteModify after close sock:35 with ip:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> delete_cp_route finished with ip:1.2.256.256
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> OutInfo notify-cookie
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> OutCp entered
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> <-- R Notify: COOKIE#SEND 60 bytes to 1.2.256.256(55067) (3561611.455)
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> cleanup_and_free_context delete ctx memory
    May 16 13:37:27 :103063: <DBUG> |ike| 1.2.256.256:55067-> udp_encap_handle_message IKEv2 pkt status:0

     

    Best regards,

    Fredrik 

     



  • 2.  RE: RAP not connecting to controller

    EMPLOYEE
    Posted May 16, 2016 08:03 AM

    That message is not conclusive.

     

    Do you have a static nat between your firewall and your controller?



  • 3.  RE: RAP not connecting to controller

    Posted May 16, 2016 08:08 AM

    Thanks Collin! My mistake not to point that out in the post. I have made an edit, yes there is a static nat between firewall and your controller.

     

    Fredrik



  • 4.  RE: RAP not connecting to controller

    EMPLOYEE
    Posted May 16, 2016 09:32 AM

    Check to make sure that in the AP-Group of the RAPs in the AP System Profile, there is NO lms-ip...



  • 5.  RE: RAP not connecting to controller

    Posted May 16, 2016 10:20 AM

    Did the controller perhaps move to a new subnet with a new default gateway? And did you in that case update the default gateway of the controller?

     

    Could you double check this command for a know public IP of one of your RAPs trying to connect:

    show datapath session table <public IP of RAP>

     

    Cheers,



  • 6.  RE: RAP not connecting to controller

    Posted May 16, 2016 04:13 PM

    Hi Christoffer. No, could have been the gateway. Verififed again to make sure and its configured with the correct GW. Also, see below for output from command you suggested.

     

    Many thanks,

    Fredrik

     

    Source IP       Destination IP  Prot SPort DPort  Cntr    Prio ToS Age Destination TAge Packets    Bytes      Flags
    --------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- ---------  --------- ---------------
    10.46.10.204    1.2.256.256    17   4500  18316  0/0     0    0   1   1/0         26   0          0          F
    10.46.10.204    1.2.256.256    17   4500  18321  0/0     0    0   0   1/0         11   3          264        F
    1.2.256.256    10.46.10.204    17   18316 4500   0/0     0    0   1   1/0         26   0          0          FC
    1.2.256.256    10.46.10.204    17   18321 4500   0/0     0    0   0   1/0         11   3          1353       FC



  • 7.  RE: RAP not connecting to controller

    Posted May 16, 2016 04:11 PM
      |   view attached

    Hi! Thanks for your response! I believe I was able to verify that no LMS IP was present. See attachment.

     

    Best regards,

    Fredrik



  • 8.  RE: RAP not connecting to controller

    Posted May 16, 2016 03:43 PM

    Hi Fredrik,

     

    As Colin mentioned, please make sure we are not pointing the RAP to an LMS which is not reachable.

     

    Also, get the below outputs;

     

    show datapath session table <RAP's public IP>

    show user-table verbose | include <RAP's MAC address>

    show crypto isakmp sa peer <RAP's public IP>

    show crypto ipsec sa peer <RAP's public IP>

     

    Article below provides basic information on RAP troubleshooting;

     

    http://community.arubanetworks.com/t5/Controller-Based-WLANs/How-do-I-troubleshoot-RAP-in-ArubaOS/ta-p/178634

     

    Regards,

     

    Karthikeyan



  • 9.  RE: RAP not connecting to controller

    Posted May 16, 2016 04:23 PM

    Hi Karthikeyan!

     

    Output from ISAKMP and IPSEC SA commands is:

     

    % No active ISAKMP SA for 1.2.256.256

    % No active IPSEC SA for 1.2.256.256

     

    show user-table verbose | include <public-ip> results in no output. Is it because I don't have the correct logging levels? I have since previously changed into debug logging as per the artice you mentioned, but only for ISAKMP and IPSEC.

     

    Thanks for your efforts to help! Please le me know if you come up with something else for me to try!

     

    Best regards,

    Fredrik



  • 10.  RE: RAP not connecting to controller

    Posted May 16, 2016 04:30 PM

    Hi Fredrik,

     

    Logging is not needed for the AP to show in user-table verbose.

     

    Was there any recent change apart from the one mentioned by you in this thread?

    What setup is this?

    What is the role of this controller?

    How the RAP is authenticated? cert or PSK?

    Is there any RAP up on this controller?

    Do you have a TAC case open?

     

    Provide below outputs;

     

    show user-table verbose | include <RAP's MAC>

    show aaa authentication vpn default-rap

    show log security 100 | include <RAP's public IP>

    show tpm errorlog

     

    I believe no configuration change was done on controller during the course of the event.

     

    Thanks.

     



  • 11.  RE: RAP not connecting to controller

    Posted May 17, 2016 02:53 AM

    Thanks! Appreciate you taking the time! Will provide additional information below.

     

    No recent change apart from the physical move of controller within infrastructure. The controller retained its IP-address, but is now communicating through a different firewall (MAC).

     

    I had a few sample/test RAPs deployed previously, but neither is currently working.

     

    The RAP is communicating through a NAT-device at its current location.

     

    If by role of controller you mean master/slave. This is the master - no cluster deployment. This is the single controller in production.

     

    I believe the RAP is authenticated using cert, but hope to be able to confirm. Perhaps you can judge by output from the aaa auth profile?

     

    No TAC case. If this all turns out to be too big a deal I will seek some on-site assistance, but wanted to run it by the forum first :)

     

    ------------

    VPN Authentication Profile "default-rap" (Predefined (changed))
    ---------------------------------------------------------------
    Parameter                                         Value
    ---------                                         -----
    Server Group                                      default
    RADIUS Accounting Server Group                    N/A
    Max Authentication failures                       0
    Check certificate common name against AAA server  Enabled
    Export VPN IP address as a route                  Enabled
    User idle timeout                                 N/A
    PAN Firewall Integration                          Disabled

     

    -------

    (Aruba3200) #show user-table verbose | include 000b8682ea64

    <no output>

     

    -------

     

    show log security 100 | include <RAP public IP-address>

    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> #RECV 423 bytes from 78.70.34.220(34070) at 192.168.1.10 (3629731.765)
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070->  spi={30ed14eb18ddd12a 0000000000000000} np=SA
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070->  exchange=IKE_SA_INIT msgid=0 len=419
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070->   check_aruba_ap_vid: aruba ap eth0 mac address 000b8682ea64 vidLen = 26
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE2_checkCookie notify-cookie ip:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP addr:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP pxSa:(nil) status:0
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP finished with pxSa:(nil) status:0
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE2_checkCookie finished with ipsecSa:(nil) status:0
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> delete_cp_route entered with ip:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify entered with ip:4e4622dc/ffffffff
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after socket:35 with ip:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify socket:35 request:35084 dev:tsgw rtflags:0 with ip:78.70.34.220
    May 17 08:32:48 :103060:  <DBUG> |ike|  78.70.34.220:34070-> ipc.c:controlplaneRouteModify:5187 Failed to Delete Route in Kernel: error:No such process
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after ioctl sock:35 with ip:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after close sock:35 with ip:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> delete_cp_route finished with ip:78.70.34.220
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> OutInfo notify-cookie
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> OutCp entered
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070->   <-- R   Notify: COOKIE#SEND 60 bytes to 78.70.34.220(34070) (3629731.772)
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> cleanup_and_free_context delete ctx memory
    May 17 08:32:48 :103063:  <DBUG> |ike|  78.70.34.220:34070-> udp_encap_handle_message IKEv2 pkt status:0
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> udp_encap_handle_message ver:2 serverInst:0 pktsize:423
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE_EXAMPLE_IKE_msgRecv: ip:4e4622dc  port:34070  server:0   len:423  numSkts:6
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070->
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> #RECV 423 bytes from 78.70.34.220(34070) at 192.168.1.10 (3629736.765)
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070->  spi={30ed14eb18ddd12a 0000000000000000} np=SA
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070->  exchange=IKE_SA_INIT msgid=0 len=419
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070->   check_aruba_ap_vid: aruba ap eth0 mac address 000b8682ea64 vidLen = 26
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE2_checkCookie notify-cookie ip:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP addr:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP pxSa:(nil) status:0
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP finished with pxSa:(nil) status:0
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE2_checkCookie finished with ipsecSa:(nil) status:0
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> delete_cp_route entered with ip:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify entered with ip:4e4622dc/ffffffff
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after socket:35 with ip:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify socket:35 request:35084 dev:tsgw rtflags:0 with ip:78.70.34.220
    May 17 08:32:53 :103060:  <DBUG> |ike|  78.70.34.220:34070-> ipc.c:controlplaneRouteModify:5187 Failed to Delete Route in Kernel: error:No such process
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after ioctl sock:35 with ip:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after close sock:35 with ip:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> delete_cp_route finished with ip:78.70.34.220
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> OutInfo notify-cookie
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> OutCp entered
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070->   <-- R   Notify: COOKIE#SEND 60 bytes to 78.70.34.220(34070) (3629736.772)
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> cleanup_and_free_context delete ctx memory
    May 17 08:32:53 :103063:  <DBUG> |ike|  78.70.34.220:34070-> udp_encap_handle_message IKEv2 pkt status:0
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> udp_encap_handle_message ver:2 serverInst:0 pktsize:423
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE_EXAMPLE_IKE_msgRecv: ip:4e4622dc  port:34070  server:0   len:423  numSkts:6
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070->
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> #RECV 423 bytes from 78.70.34.220(34070) at 192.168.1.10 (3629741.767)
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070->  spi={30ed14eb18ddd12a 0000000000000000} np=SA
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070->  exchange=IKE_SA_INIT msgid=0 len=419
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070->   check_aruba_ap_vid: aruba ap eth0 mac address 000b8682ea64 vidLen = 26
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE2_checkCookie notify-cookie ip:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP addr:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP pxSa:(nil) status:0
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IPSEC_findSaByIP finished with pxSa:(nil) status:0
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> IKE2_checkCookie finished with ipsecSa:(nil) status:0
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> delete_cp_route entered with ip:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify entered with ip:4e4622dc/ffffffff
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after socket:35 with ip:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify socket:35 request:35084 dev:tsgw rtflags:0 with ip:78.70.34.220
    May 17 08:32:58 :103060:  <DBUG> |ike|  78.70.34.220:34070-> ipc.c:controlplaneRouteModify:5187 Failed to Delete Route in Kernel: error:No such process
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after ioctl sock:35 with ip:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> controlplaneRouteModify after close sock:35 with ip:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> delete_cp_route finished with ip:78.70.34.220
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> OutInfo notify-cookie
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> OutCp entered
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070->   <-- R   Notify: COOKIE#SEND 60 bytes to 78.70.34.220(34070) (3629741.774)
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> cleanup_and_free_context delete ctx memory
    May 17 08:32:58 :103063:  <DBUG> |ike|  78.70.34.220:34070-> udp_encap_handle_message IKEv2 pkt status:0

     

    --------

     

    (Aruba3200) #show tpm errorlog
    Could not find any Error Logs for TPM and Certificates.

     

     

     



  • 12.  RE: RAP not connecting to controller

    Posted May 17, 2016 03:26 AM
    Hi,

    From logs, I don't see any auth information.

    To verify the issue is not related to firewall, can you bring up the rap from local intranet avoiding any firewall?


  • 13.  RE: RAP not connecting to controller

    Posted May 19, 2016 04:58 AM

    Hi!

     

    Sorry about the delay - had to fetch the RAP in order to try :) You were right in your assertion, bringing the RAP to the office and connecting to intranet made it connect successfully! My quest continues in trying to determine what differs - apart from the obvious a NAT from controllers public to private address when the RAP is local remotely (outside intranet).

     

    Best regards,

    Fredrik



  • 14.  RE: RAP not connecting to controller
    Best Answer

    Posted May 19, 2016 05:16 AM
    Hi,

    Is there asymmetric routing?


  • 15.  RE: RAP not connecting to controller

    Posted Jun 23, 2016 08:57 AM

    Took some time to verify, but it turned out to be assymetric routing (of sorts) involved. The response to the RAP from the controller ended up being routed over a secondary Internet connection :( I simplified the NAT configuration (in firewall) and resolved the problem.

     

    Best regards,

    Fredrik



  • 16.  RE: RAP not connecting to controller

    Posted Jun 23, 2016 09:13 AM
    Thank you for sharing the solution with community.


  • 17.  RE: RAP not connecting to controller

    EMPLOYEE
    Posted Jun 27, 2018 02:17 PM

    Hi Keya,

     

    How come you can find out it related to asymmetric routing?

     

    I had the same issue and similar log output, did you found out it from any suspect log?

     

    Thank you,

    Manal



  • 18.  RE: RAP not connecting to controller

    Posted Mar 16, 2020 07:15 AM

    hi,

     

    I have two 7205.

    I migrated one of them to 8.5.0 with MM.

    MM is connected to 7205 (UP).

     

    When I want to reconnect my RAP from 7205 (6.5) to migrated one RAP is not getting UP. Logs below:

    Mar 16 06:47:57 :399838:  <5787> <WARN> |fpapps|  Received non LOAD_BALANCE MAP_ADD from IKE for default-local-master-ipsecmap213.241.33.26 mapid 4621 vlanid 0 flags 0x0; ignored

    Mar 16 06:47:57 :399838:  <5787> <WARN> |fpapps|  Received TUN_UP from IKE for default-local-master-ipsecmap213.241.33.26 mapid 17953, vlanid 0, ip 213.241.33.26, src_ip 62.244.133.33, peer_ip 213.241.33.26, gw 213.241.33.26, flags 0x0 uplink_prio 0

    Mar 16 08:45:28 :399838:  <5787> <WARN> |fpapps|  Received MAP_ADD from IKE for default-local-master-ipsecmap213.241.33.26 (gw 213.241.33.26) mapid 4621 vlanid 0 ip 213.241.33.26 mask 255.255.255.255 src_ip 62.244.133.33 peer_ip 213.241.33.26 uplink_ip 0.0.0.0 flags 0x0

    Mar 16 08:45:28 :399838:  <5787> <WARN> |fpapps|  Received non LOAD_BALANCE MAP_ADD from IKE for default-local-master-ipsecmap213.241.33.26 mapid 4621 vlanid 0 flags 0x0; ignored

    Mar 16 08:45:28 :399838:  <5787> <WARN> |fpapps|  Received MAP_ADD from IKE for default-local-master-ipsecmap213.241.33.26 (gw 213.241.33.26) mapid 4621 vlanid 0 ip 213.241.33.26 mask 255.255.255.255 src_ip 62.244.133.33 peer_ip 213.241.33.26 uplink_ip 0.0.0.0 flags 0x0

    Mar 16 08:45:28 :399838:  <5787> <WARN> |fpapps|  Received non LOAD_BALANCE MAP_ADD from IKE for default-local-master-ipsecmap213.241.33.26 mapid 4621 vlanid 0 flags 0x0; ig