Header Only - DO NOT REMOVE - Extreme Networks

AP7522 POE issue



Show first post

38 replies

I've just checked, i misread the LLDP the AP it isn't getting an IP address. tried a reboot several time but nothing.
Userlevel 3
How is the AP discovering the controller? DHCP options, or something else?
APs are discovered by DHCP options
Userlevel 3
If the AP is not getting an IP address, this indicates a Layer 2 issue between the DHCP server and the AP.

This is typically cased by a VLAN mismatch.
I have 10 of these access points 3 on one vlan and 7 on another all of this aps are configured the same and 9 of the 10 have been adopted and are functioning correctly​ The switchport config is Switchport mode trunk Switchport trunk native vlan 4 This access point isn't getting a lease from DHCP no matter which vlan I put it in. Thanks
Userlevel 4
Native vlan is 4 and DHCP is vlan 1? The AP need a untag VLAN to get a IP address, if it's a clean AP. Do you have free DHCP IPs?

Check for the right VLAN as untag and available DHCP address. If this are booth right, the AP is damage.
DHCP is Vlan 4 and switchport is trunking Vlan 4, plenty of DHCP leases available within the scope, do we agree this AP is faulty?

Thanks for everyone's help so far, it's been really helpful!
Userlevel 3
The fact that you are seeing LLDP info on the switch port indicates that a) the AP booted up OK; b) there is nothing physically wrong with the interface. Both of these facts point to a configuration mismatch of some sort.

I've seen many instances where the AP has been configured incorrectly either by accident (typos) or due to unintentional behavior caused by profile overrides. The AP's configuration ends up such that the network interface does not match the switch port setting.

Please post the output of the AP's exected interface config. You can do this from the controller CLI with "show run device device_mac_address" and include all the lines for "interface ge1, interface vlan, etc".

Also include the switch's interface config for that interface.
AP interface config:

interface ge1
switchport mode trunk
switchport trunk native vlan 4
no switchport trunk native tagged
switchport trunk allowed vlan 1-4094
interface vlan4
description
ip address XX.XXX.XX.XX/XX
ip dhcp client request options all
ip helper-address XX.XXX.XX.XX

Switchport config:

interface FastEthernet2/0/23
description Link to APXX
switchport trunk encapsulation dot1q
switchport trunk native vlan 4
switchport mode trunk
no lldp med-tlv-select power-management
end

Thanks
Userlevel 3
A couple comments on the config:

  • It appears that the switch port vlan 4 config is consistent, the problem lies elsewhere.
  • Why is there an IP address listed in interface vlan 4? If you are using dhcp, it should read "ip address dhcp"
  • The DHCP helper is usually configured on the switch, not on the AP. Only the switch has the switch virtual interface (SVI) for vlan 4 should have this configured.
  • "allowing" all VLANs into the AP can cause issues if there are APs on the other VLANs that could be visible over layer 2.
A couple comments on the config:

  • It appears that the switch port vlan 4 config is consistent, the problem lies elsewhere.
  • Why is there an IP address listed in interface vlan 4? If you are using dhcp, it should read "ip address dhcp"
  • The DHCP helper is usually configured on the switch, not on the AP. Only the switch has the switch virtual interface (SVI) for vlan 4 should have this configured.
  • "allowing" all VLANs into the AP can cause issues if there are APs on the other VLANs that could be visible over layer 2.

  • The APs IP addresses are Static they will be assigned the IP listed under that VLAN
  • DHCP helper address is configured on the SVI of the switch as well as in the profile just for peace of mind at the moment.
I believe the AP is faulty I have a total of 200 APs on multiple sites all with similar if not the same configuration, they all function correctly. The 10 on this site are all up and functioning correctly with the same configuration listed above, but this one just doesn't obtain an IP address ever.
Userlevel 3
One last thing that I'd try, assuming there are other APs at that site that are functioning.:

  1. connecting to a working remote AP at the site via ssh/telnet.
  2. use the command "show mint neighbors" - You will see all APs on the same Layer2 and maybe some Layer 3 neighbors depending on how your config is setup. The Mint-ID which is XX.XX.XX.XX contains part of the MAC address of the AP (the last 3 digits); eg MAC address 5C-0E-8B-11-22-33 will show up as Mint ID: 0B.11.22.33. If it doesn't show up, then the AP is probably hosed.
  3. Try pinging the mint address using the command: "mint ping XX.XX.XX.XX" if you get a response continue to next step.
  4. Now the cool part: use the command: "connect mint-id XX.XX.XX.XX" - This will open a Layer 2 CLI session with the target AP. This is especially useful to get into an AP that doesn't get an IP address for some reason.
  5. You can now troubleshoot / factory default the problem AP.
Thanks, I already checked this and I couldn't see anything I have double checked again still nothing I tried to ping the MINT ID but still no response.

I will proceed with getting the AP replaced.

Thank you for all your help!

Reply