Wireless Access

last person joined: 16 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

7210 Controller not seeing AP even though it can ping it!!

This thread has been viewed 9 times
  • 1.  7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 08:00 PM

    Hi forum,

    I know this sounds basic but I can't just find what's wrong!!

    a single 7210 Master controller with 32 AP license installed. it is on VLAN 192 and the APs connected to an aruba switch MS1500 poe on that same vlan. The AP comes up gets it DHCP address, using ADP it discovers the controller's IP address.

    On the AP console I can ping the controller address and from the controller I can ping the AP. control plane security is disabled, tried couple APs but same results (NOTHING on the list when I do SHOW AP DATABASE).

    controller is 7210 running AOS 6.4.2.6

    Access point is AP-225 using eth0 to connect to the aruba switch.

     

    Please help if someone have any ideas.

    thanks,


    #7210
    #AP225


  • 2.  RE: 7210 Controller not seeing AP even though it can ping it!!

    EMPLOYEE
    Posted May 20, 2015 08:02 PM
    Can you run “show log system 50” and see if there are any errors?
    #7210


  • 3.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 08:19 PM

    I see a bunch but nothing about AP discovery/connection.


    #7210


  • 4.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 08:26 PM

    @master-local wrote:

    I see a bunch but nothing about AP discovery/connection.


    Can you share the system log at the time of a discovery/AP boot; what may seem irrelevant may indeed be relevant.  


    #7210


  • 5.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 08:24 PM

    Is the port that VLAN 192 is assigned to trusted?

     

    Can you share the output of the following:

     

    • show controller-ip
    • show ip interface brief
    • show vlan
    • show port status

     


    #7210


  • 6.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 08:29 PM

    Controller interface:

     

    interface port-channel 1
    trusted
    trusted vlan 1-4094
    switchport mode trunk
    switchport trunk allowed vlan 1-4094

     

    #show controller-ip

    Switch IP Address: 10.10.193.161

    Switch IP is configured to be Vlan Interface: 192

     

    #show vlan

    VLAN CONFIGURATION
    ------------------
    VLAN        Description         Ports                           AAA Profile
    ----             -----------              -----                             -----------
    1                Default                GE0/0/2-0/5 Pc0-7     N/A
    192            VLAN0192           Pc1                            N/A

     

     

     

     

    #show port status

    Port Status
    -----------
    Slot-Port PortType adminstate operstate poe Trusted SpanningTree PortMode Speed Duplex
    --------- -------- ---------- --------- --- ------- ------------ -------- ----- ------
    0/0/0 GE Enabled Up N/A Yes Disabled Trunk 100 Mbps Full
    0/0/1 GE Enabled Up N/A Yes Disabled Trunk 100 Mbps Full


    #7210


  • 7.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 08:36 PM

    #show log system 50

    May 20 16:20:17 KERNEL: 1:<6>MVL1422: CUB(2) Port 0 Sys side down
    May 20 16:20:17 KERNEL: 1:Nae: Initializing XAUI port/block 0/0
    May 20 16:20:17 KERNEL: 1:wait_for_lane_sync block 0 lane 0 reg 0 data 851
    May 20 16:20:17 KERNEL: 1:wait_for_lane_sync block 0 lane 1 reg 1 data 851
    May 20 16:20:17 KERNEL: 1:wait_for_lane_sync block 0 lane 2 reg 2 data 851
    May 20 16:20:17 KERNEL: 1:wait_for_lane_sync block 0 lane 3 reg 3 data 851
    May 20 16:20:17 KERNEL: 1:Nae: Lane sync completed for port 0
    May 20 16:20:20 KERNEL: 4:<4>process `trapd' is using obsolete setsockopt SO_BSDCOMPAT
    May 20 16:20:21 :330104: <NOTI> |extifmgr| SAPI sync done with service 8486 at level 3
    May 20 16:20:21 :330103: <NOTI> |extifmgr| SAPI sync (blocking) with service 8405 at level 5
    May 20 16:20:23 :330104: <NOTI> |extifmgr| SAPI sync done with service 8405 at level 5
    May 20 16:20:23 :330102: <NOTI> |extifmgr| SAPI sync with service 8407 at level 5
    May 20 16:20:23 :330103: <NOTI> |extifmgr| SAPI sync (blocking) with service 8212 at level 3
    May 20 16:20:25 :330104: <NOTI> |extifmgr| SAPI sync done with service 8212 at level 3
    May 20 16:20:25 :330101: <NOTI> |extifmgr| set SAPI state for level 5 to Up
    May 20 16:20:25 :309825: <DBUG> |extifmgr| extifmgr: GSM is initialized.
    May 20 16:20:25 :309805: <INFO> |extifmgr| init_extifmgr(): extifmgr process is initialized
    May 20 16:20:25 :306504: <DBUG> |extifmgr| received subscription message from 8214 for service 'IF-MAP status '
    May 20 16:20:25 :309811: <WARN> |extifmgr| ifmap_current_state(): Broadcast IF-MAP Status: CPPM:Inactive.
    May 20 16:20:25 :306502: <DBUG> |extifmgr| Publish service 'IF-MAP status ', object len 1
    May 20 16:20:25 :306504: <DBUG> |extifmgr| received subscription message from 8476 for service 'IF-MAP status '
    May 20 16:20:25 :309811: <WARN> |extifmgr| ifmap_current_state(): Broadcast IF-MAP Status: CPPM:Inactive.
    May 20 16:20:25 :306502: <DBUG> |extifmgr| Publish service 'IF-MAP status ', object len 1
    May 20 16:20:25 :330001: <DBUG> |extifmgr| ncfg_profmgr_recv: Received message type 3 length 58
    May 20 16:20:25 :330001: <DBUG> |extifmgr| ncfg_profmgr_recv_update: Profile type 153 (cppm_prof) inst default state 0
    May 20 16:20:25 :330001: <DBUG> |extifmgr| ncfg_profmgr_recv_update: id 0 num_changed 0
    May 20 16:20:25 :309815: <DBUG> |extifmgr| extif_group_change_notify(): group:"cppm_prof" group_num:0 instance:"default" id:0 changed; refs:0.
    May 20 16:20:25 :309804: <DBUG> |extifmgr| extif_group_change_notify(): group "cppm_prof" group_num 0 instance "default" id 0 changed; refs 0
    May 20 16:20:25 :309811: <WARN> |extifmgr| ifmap_current_state(): Broadcast IF-MAP Status: CPPM:Inactive.
    May 20 16:20:25 :306502: <DBUG> |extifmgr| Publish service 'IF-MAP status ', object len 1
    May 20 16:20:25 :330104: <NOTI> |extifmgr| SAPI sync done with service 8407 at level 5
    May 20 16:20:25 :330001: <DBUG> |extifmgr| ncfg_profmgr_recv: Received message type 3 length 70
    May 20 16:20:25 :330001: <DBUG> |extifmgr| ncfg_profmgr_recv_update: Profile type 154 (pan_prof) inst default state 0
    May 20 16:20:25 :330001: <DBUG> |extifmgr| ncfg_profmgr_recv_update: id 0 num_changed 0
    May 20 16:20:25 :309815: <DBUG> |extifmgr| extif_group_change_notify(): group:"pan_prof" group_num:1 instance:"default" id:0 changed; refs:0.
    May 20 16:20:25 :309804: <DBUG> |extifmgr| extif_group_change_notify(): group "pan_prof" group_num 1 instance "default" id 0 changed; refs 0
    May 20 16:20:25 :306602: <INFO> |extifmgr| Changing the logging level for 6 facilities
    May 20 16:20:25 :309811: <WARN> |extifmgr| ifmap_current_state(): Broadcast IF-MAP Status: CPPM:Inactive.
    May 20 16:20:37 :304001: <ERRS> |stm| Unexpected stm (Station management) runtime error at data_path_handler, 1030, data_path_handler: recv - Network is down
    May 20 16:20:40 :348306: <DBUG> |ipstm| main, Skipping Manual IPSec Creation.
    May 20 16:20:40 :348306: <DBUG> |ipstm| papi_rcv_cb, Recvd PAPI Message, len=80
    May 20 16:20:40 :348306: <DBUG> |ipstm| papi_rcv_cb, Recvd PAPI Message from IKE
    May 20 16:20:40 :348306: <DBUG> |ipstm| papi_rcv_cb, Recvd PAPI Message, len=88
    May 20 16:20:40 :399899: <INFO> |ipstm| sapi_rsp, sapi.c:248: SAPI response service/level lookup failed
    May 20 16:20:40 :348306: <DBUG> |ipstm| papi_rcv_cb, Recvd PAPI Message, len=88
    May 20 16:20:40 :399899: <INFO> |ipstm| sapi_rsp, sapi.c:248: SAPI response service/level lookup failed
    May 20 16:20:40 :348306: <DBUG> |ipstm| papi_rcv_cb, Recvd PAPI Message, len=88
    May 20 16:20:40 :399899: <INFO> |ipstm| sapi_rsp, sapi.c:248: SAPI response service/level lookup failed
    May 20 16:20:42 KERNEL: 0:apsd_porf_getdmamem: physical address 0xB4000000, virtual address c0000000b4000000, size 24117248
    May 20 16:21:21 KERNEL: 0:<4>hrtimer: interrupt took 3037423 ns


    #7210


  • 8.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 09:11 PM

    not sure if it is related, but are those ports set at 100MB intentionally?


    #7210


  • 9.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 09:15 PM

    I think auto-negotiate with the uplink switch being an old cisco 3550 switch.


    #7210


  • 10.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 09:24 PM

    OK, thought you mentioned it was plugged into an Aruba switch (maybe the APs only?).   Could you plug the controller and APs into the same switch to rule out inter-switch issues?


    #7210


  • 11.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 09:31 PM

    You are correct. the AP only is connected to the aruba switch.

    I will try connecting all devices to the same switch and see. although, from basic network perspective if the ping works I don't know why would the discovery wont work. Tha AP console says "running ADP... "and then "Master is 10.10.193.161" so the AP is discovering the controller alright.


    #7210


  • 12.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 20, 2015 09:35 PM

    You're right, but if the controller is not hosting live users, it is worth a shot to rule out other issues.  

     

    On the AP console, after it shows discovering the controller through ADP, are there any other messages?

    Are these new APs?    Have you tried to reset one of the APs?


    #7210


  • 13.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 21, 2015 03:06 AM

    HI.

    Asper my understanding, APs are connected to S1500 poe switch and Controller is uplinked to the S1500 Switch right ? if so check the link between Controller and Switch. ensure the poe ports where APs are connected are trusted and mapped to proper VLAN.

     

    Before testing the above reset APs to factory default.

     

    Please feel free for any further help on this.


    #7210


  • 14.  RE: 7210 Controller not seeing AP even though it can ping it!!

    Posted May 21, 2015 03:09 AM

    HI,

     

    Primarily we need to check whether Controller is receiving PAPI ( UDP 8211 ) traffic from APs for that use " show datapath session " and look for PAPI traffic. also ensure cpsec is disabled or properly configured.


    #7210


  • 15.  RE: 7210 Controller not seeing AP even though it can ping it!!
    Best Answer

    Posted May 21, 2015 03:14 AM

    So the controller is connected to a cisco switch 3550 and the AP ar on another switch(MS1500). what I discovered (even though the ping was working) is that the controller was pointing to the L3 address of the cisco switch as the default-gateway vs. the aruba switch default-gateway is pointing to .1 address of that subnet which sits on a core switch. after I changed the default gateway of the controller to the .1 address it worked great.


    #7210