Wireless Access

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

Original Message:
Sent: 9/29/2022 9:02:00 AM
From: EyadMSubeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

Both APs are 335
AOS version: 8.6.0.11
The working AP is upgraded when its connected to the Mobility controller.
The Non working AP couldn't even be visible by the controller, so it didn't upgrade from version 6.5.0.0 to 8.6.0.11

------------------------------
Eyad Subeh
------------------------------

Original Message:
Sent: Sep 29, 2022 09:14 AM
From: rashed basuleman
Subject: AP can't find Master IP

This is due to non compatibility of the APs with your AOS Code, please let me know your AIs Version and APs Model ..

Best Regards,

Rashed Basuleman


 

Original Message:
Sent: 9/29/2022 9:02:00 AM
From: EyadMSubeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

Plug the not-working AP into enet0 and try again.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Sep 29, 2022 09:32 AM
From: Eyad Subeh
Subject: AP can't find Master IP

Both APs are 335
AOS version: 8.6.0.11
The working AP is upgraded when its connected to the Mobility controller.
The Non working AP couldn't even be visible by the controller, so it didn't upgrade from version 6.5.0.0 to 8.6.0.11

------------------------------
Eyad Subeh

Original Message:
Sent: Sep 29, 2022 09:14 AM
From: rashed basuleman
Subject: AP can't find Master IP

This is due to non compatibility of the APs with your AOS Code, please let me know your AIs Version and APs Model ..

Best Regards,

Rashed Basuleman


 

Original Message:
Sent: 9/29/2022 9:02:00 AM
From: EyadMSubeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

Already tried, same output.

------------------------------
Eyad Subeh
------------------------------

Original Message:
Sent: Sep 29, 2022 09:58 AM
From: Colin Joseph
Subject: AP can't find Master IP

Plug the not-working AP into enet0 and try again.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Sep 29, 2022 09:32 AM
From: Eyad Subeh
Subject: AP can't find Master IP

Both APs are 335
AOS version: 8.6.0.11
The working AP is upgraded when its connected to the Mobility controller.
The Non working AP couldn't even be visible by the controller, so it didn't upgrade from version 6.5.0.0 to 8.6.0.11

------------------------------
Eyad Subeh

Original Message:
Sent: Sep 29, 2022 09:14 AM
From: rashed basuleman
Subject: AP can't find Master IP

This is due to non compatibility of the APs with your AOS Code, please let me know your AIs Version and APs Model ..

Best Regards,

Rashed Basuleman


 

Original Message:
Sent: 9/29/2022 9:02:00 AM
From: EyadMSubeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

I would do a packet captures of the DHCP packets and notice any differences.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Sep 29, 2022 10:37 AM
From: Eyad Subeh
Subject: AP can't find Master IP

Already tried, same output.

------------------------------
Eyad Subeh

Original Message:
Sent: Sep 29, 2022 09:58 AM
From: Colin Joseph
Subject: AP can't find Master IP

Plug the not-working AP into enet0 and try again.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Sep 29, 2022 09:32 AM
From: Eyad Subeh
Subject: AP can't find Master IP

Both APs are 335
AOS version: 8.6.0.11
The working AP is upgraded when its connected to the Mobility controller.
The Non working AP couldn't even be visible by the controller, so it didn't upgrade from version 6.5.0.0 to 8.6.0.11

------------------------------
Eyad Subeh

Original Message:
Sent: Sep 29, 2022 09:14 AM
From: rashed basuleman
Subject: AP can't find Master IP

This is due to non compatibility of the APs with your AOS Code, please let me know your AIs Version and APs Model ..

Best Regards,

Rashed Basuleman


 

Original Message:
Sent: 9/29/2022 9:02:00 AM
From: EyadMSubeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

Hi,  just to be sure, You did configure option 60 as well, rigth?

Hope this helps
Original Message:
Sent: Sep 29, 2022 09:02 AM
From: Eyad Subeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------

We had the same issue with the 315's 
https://community.arubanetworks.com/discussion/315-will-not-phone-home-to-the-conductor-version-6500?ReturnUrl=%2fcommunity-home%2fdigestviewer%3fcommunitykey%3d867d34a4-1e6a-4b9a-9349-df7b4c84b3cb

The AP versions will not talk to the controllers unless you upgrade your AP's first. something with the 6.5.0.0 and controllers being in the 8.x.x.x
Original Message:
Sent: Sep 29, 2022 09:02 AM
From: Eyad Subeh
Subject: AP can't find Master IP

Hello,

We are facing an issue that even TAC engineers are having trouble with it.

We have Mobility controller connected to a CORE switch, the CORE is connected to DHCP server AND Access switch, the access switch connected to APs.
On DHCP, we configured the scope and option 43 is enabled.
but for some reason, not all the APs are coming up, when we console the non working AP, we can see that it's not taking Master-IP and keeps rebooting.

switches have same config on the ports and same VLAN, The working AP will behave normally, while on the same port, the non working AP will as mentioned above keep rebooting and can't find master IP.

anyone faced the same issue?

Attached "NOT working AP Boot.txt" on line 143
Attached "Working AP Boot.txt" on line 103

------------------------------
Eyad Subeh
------------------------------