Wireless Access

Hi All, I'm seeing a strange issue with APs plugged into a HP switch stack on a new installation. The stack has been in production for other devices for some time. Not sure how many members but its a 5130 running Comware 7.1.045 and when I plug an AP315 into it, it gets an IP address and then this happens (it seems to lose power where the line starts [ 78¦) 172.30.30.60 255.255.255.0 172.30.30.1 Running ADP...Done. Master is 172.30.30.244 [ 70.606373] PCI: enabling device 0000:01:00.0 (0140 -> 0142) [ 76.345110] Startup Mode-0 set [ 76.371102] htt_peer_map_timer_init Enter pdev db334000 hrtimer db336790 [ 76.449328] [ 76.449328] htt_alloc_peer_map_mem : Alloc Success : host q vaddr db526000 paddr 5ca26000 [ 76.565979] [ 76.565979] htt_alloc_peer_map_mem : Flush Interval Configured to 256 pkts [ 76.668166] [ 76.668166] SERIAL NUMBER: : wifi0 [ 76.668166] [ 76.815620] wmi_ready_event_rx: WMI UNIFIED READY event [ 76.907622] ol_ath_smart_ant_attach: Firmware doest not support Smart Antenna. [ 76.981661] ol_ath_smart_ant_attach: Hardware doest not support Smart Antenna. [ 77.068134] dfs_attach: event log disabled by default [ 77.131708] bond0 address=00:4e:35:c0:09:32 [ 77.178506] br0 address=00:4e:35:c0:09:32 [ 77.226429] wifi0: AP type AP-315, radio 0, max_bssids 16 [ 77.291065] Resetting spectral chainmask to Rx chainmask [ 77.458263] Resetting spectral chainmask to Rx chainmask [ 77.509715] Init the PCAP for radio0 offload 1. [ 77.563948] PCI: enabling device 0000:03:00.0 (0140 -> 0142) [ 78.868009] Startup Mode-0 set [ 78.894095] htt_peer_map_timer_init Enter pdev db2e4000 hrtimer db2e6790 [ 78.972258] [ 78¦ APBoot 1.5.5.7 (build 56398) Built: 2016-09-08 at 14:21:29 Model: AP-31x DRAM: 491 MB SF: Detected MX25U3235F with page size 64 kB, total 4 MB Flash: 4 MB NAND: 132 MiB PCIE0: link up PCIE1: link up dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3 00 00 168c 0046 00002 00 00000004 00000000 00000000 00000000 dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3 00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000 Power: 802.3af POE In: serial Out: serial Err: serial Net: eth0 Radio: qca9983#0, qca9990#1 Reset: cold FIPS: passed Hit to stop autoboot: 0 I've used another AP in the same switch with the same results - repeated rebooting. I've moved the same AP into another stack that the customer tells me is configured the same and has the same firmware and stack setup and the AP works as expected. Any ideas?

Looks like the power is lost.
Is LLDP enabled on the switch? Is there enough remaining power at switch?

What is exactly the switch type 5130 SI/EI/HI and firmware version?

Not sure on the exact model of switch involved but the firmware is Comware 7.1.045 Release 3113P05.

There is plenty power budget for the device and we have allowed the device to draw as much as it needs.

Logs on the switch shows many PVID mismatches -

LLDP/5/LLDP_PVID_INCONSISTENT: PVID mismatch discovered on GigabitEthernet x/x/x

F-U-5130 LLDP/5/LLDP_PVID_INCONSISTENT: PVID mismatch discovered on GigabitEthernet x/x/x (PVID x) with <ApName> (PVID 0)

Are you able to test the cable? Potential broken pair?

Multiple APs tested with a 1m patch cable plugged directly into the switch with the same result.

I think the PVID mismatch means there is a VLAN mismatch. Are you trunking on either the switchport or the Ap? If so, do the allowed VLANs match on both sides? Same untagged VLAN?

I couldn't tell in your first post, but is there a reason for the reboot shown with this command "show ap debug system-status ap-name <ap-name>"?

 

Edit: typo

The AP reboots before connecting to the controller so no output from controller is available.

If that's the case you will probably need to get on the console and see why it's rebooting. The primary reason for it to keep rebooting is usually because it can't contact the controller. You could also use the "show datapath session table " command on the controller and see if that AP is trying to contact the controller.

If they go on the switch / router can they ping the controller from that subnet? Can they ping the AP on AP's subnet? Can they ping the AP from another subnet?

Ive looked back at the original post and the text doesn't clearly show whats happening so I've attached a screenshot. The issue here is not a connectivity or networking issue. The AP boot is interrupted for some reason you can see this before the line -

APBoot 1.5.5.7 (Build 56398)

the switch is the issue I believe, or the interaction between the AP/switch for some reason.

 

Have you already opened a TAC case?

Yes a TAC case is currently open.

Sorry for confusion, customer has confirmed that the PVID issue is separate issue.