This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

APs do not preserve a new profile upon restart

APs do not preserve a new profile upon restart

Tiago_Juliano_F
New Contributor

‎10-25-2018 12:10 PM

Hello! I need to migrate APs from one native Vlan to another (from VLAN 1 to 10). I make the settings for Wing 5.8 by creating a new profile (ap-7532-new) and setting the VLAN settings. Everything seems to work, the AP adopts the correct IP but when it restarts it goes back to the previous profile (default-ap3572).

I make sure I commit and save but still do not maintain the new Profile settings.

Procedures:

- I created the new profile in Configuration-Profiles
- I set Ethernet Ports and Virtual Lan for my scenario
- In the specific Device I set the Profile

Did I forget something?

49787eda74244b2887102e59543bee33_RackMultipart20181025-94537-1ylpiu9-wing-profile_inline.png



0 Kudos
23 REPLIES 23

Tiago_Juliano_F
New Contributor
In response to Tomasz

‎10-25-2018 04:05 PM

Was this due to something you were doing on those days?
Yes! I set up a testing environment with this AP and have been trying to modify the native Vlan ever since.

Apparently the routing between Van911 and Vlan1 is OK since AP receives an IP in the range of Vlan911 when commit write.

Set this again

interface vlan911
ip address dhcp
ip dhcp client request options all

Now I connected the AP directly to a POE port on the Controller. I tried to redo the settings on the specific port (ge2) and had the following error:

commit write
% Error: Commit failed for the following reasons:

[device '5C-0E-8B-19-DB-D3'] Only one interface can be configured for ip dhcp client request options all.
[device 'B4-C7-99-6E-2F-83'] Only one interface can be configured for ip dhcp client request options all.
[device '5C-0E-8B-19-DB-D3'][] Only one interface can be configured for ip dhcp client request options all.

0 Kudos

ckelly
Extreme Employee
In response to Tomasz

‎10-25-2018 04:05 PM

Okay...first, cluster looks good!

This AP is seeing 44 other APs using VLAN-1 and seeing both rfs controllers using VLAN-1.

On the reboot history:
Looks like there were a number of reboots on the 25th and 26th (and 2 yesterday) (user 'admin' issued a reload to the AP). Was this due to something you were doing on those days?

So I'm wondering now about the whole migration to VLAN-911. Bottom line, is the controller cluster reachable by an AP that is on VLAN-911 ?

Also, I didn't really see anything regarding the configuration for VLAN-911 in the config. is this somewhere in the new config?
interface vlan911
ip address dhcp
ip dhcp client request options all

**I'm still thinking this is an issue where the AP is losing connection ability to the controller once it receives the new config push.
Do you have an AP that you could test with that you can plug in somewhere handy and be able to console connect to it? The thought hear would be to use that AP to push the NEW config to it...and then from the console connection you can verify things in the CLI. (IP address, MiNT connectivity to the controller, the config that it received looks correct, etc)
0 Kudos

Tiago_Juliano_F
New Contributor
In response to Tomasz

‎10-25-2018 04:05 PM

Thank you Chris!

show cluster status

Cluster Runtime Information
Protocol version : 1
Cluster operational state : active
AP license : 32
AAP license : 16
AP count : 0
AAP count : 46
Max AP adoption capacity : 256
Number of connected member(s): 1

show cluster members
------------------------------------------------------------------------------------------
HOSTNAME MEMBER-ID MAC MASTER OPERATIONAL-STATE LAST-SEEN
------------------------------------------------------------------------------------------
rfs01 0B.19.DB.D3 5C-0E-8B-19-DB-D3 True active self
rfs02* 19.6E.2F.83 B4-C7-99-6E-2F-83 False standby 00:01:35 ago


service show reboot-history
Configured size of reboot history is 50

Date & Time Event
=====================================================
Oct 29 16:18:43 2018 startup 5.8.6.9-003R
Oct 29 16:18:14 2018 shutdown (graceful:'reload' command issued from CLI (user: admin))
Oct 29 15:20:26 2018 startup 5.8.6.9-003R
Oct 29 13:19:56 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 26 13:34:25 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Oct 26 13:34:24 2018 startup 5.8.6.9-003R
Oct 26 11:33:56 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 26 14:16:54 2018 startup 5.8.6.9-003R
Oct 26 12:16:25 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 26 11:27:45 2018 startup 5.8.6.9-003R
Oct 26 11:27:16 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 25 16:26:22 2018 startup 5.8.6.9-003R
Oct 25 16:25:53 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 25 16:01:59 2018 startup 5.8.6.9-003R
Oct 25 16:01:29 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 25 15:53:21 2018 startup 5.8.6.9-003R
Oct 25 15:52:53 2018 shutdown (graceful:reload by user (user: admin @ rfs02))
Oct 25 13:32:21 2018 startup 5.8.6.9-003R
Oct 25 13:31:52 2018 shutdown (graceful:reload by user (user: admin @ rfs02))
Oct 25 11:47:09 2018 startup 5.8.6.9-003R
Oct 25 11:46:39 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 25 10:59:16 2018 startup 5.8.6.9-003R
Oct 25 10:58:47 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 25 12:16:49 2018 startup 5.8.6.9-003R
Oct 25 10:16:20 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 24 19:29:28 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Oct 24 19:29:27 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Oct 24 17:29:27 2018 startup 5.8.6.9-003R
Oct 24 17:28:58 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 24 17:14:37 2018 startup 5.8.6.9-003R
Oct 24 17:14:09 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Oct 24 16:59:50 2018 startup 5.8.6.9-003R
Oct 24 16:59:22 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Sep 03 11:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
- - - shutdown (ungraceful:unexpected cold restart)
Sep 03 14:50:29 2018 startup 5.8.6.9-003R
Sep 03 11:50:01 2018 shutdown (graceful:reload by user (user: admin @ rfs01))
Sep 03 14:45:29 2018 startup 5.8.6.9-003R
Sep 03 14:45:01 2018 shutdown (graceful:Upgrade done, reloading... (user: system @ rfs01))
Jan 01 00:00:00 2015 startup 5.8.0.0-050R
- - - shutdown (ungraceful:unexpected cold restart)
Jan 01 00:00:00 2015 startup 5.8.0.0-050R
- - - shutdown (ungraceful:unexpected cold restart)
Jan 01 00:00:00 2015 startup 5.8.0.0-050R
- - - shutdown (ungraceful:unexpected cold restart)
Jan 01 00:00:00 2015 startup 5.8.0.0-050R
- - - shutdown (ungraceful:unexpected cold restart)
Jan 01 00:00:00 2015 startup 5.8.0.0-050R
- - - shutdown (ungraceful:unexpected cold restart)

show mint neighbors
46 mint neighbors of 75.03.33.F8:
0B.19.DB.D3 (rfs01) at level 1, 2 adjacencies, 2 UP adjacencies, best adjacency vlan-1
0B.E8.4B.04 (ap-Zootecnia2-Suinos) at level 1, best adjacency vlan-1
0B.E9.A1.C1 (ap-PredioB-Inferior) at level 1, best adjacency vlan-1
0B.E9.A2.21 (ap-Equoterapia) at level 1, best adjacency vlan-1
0B.E9.A7.C7 (ap-PredioB) at level 1, best adjacency vlan-1
0B.E9.A8.A5 (ap-ctAdm02) at level 1, best adjacency vlan-1
0B.E9.AB.07 (ap-Zootecnia1-Avicultura) at level 1, best adjacency vlan-1
0B.E9.AB.15 (ap-Cooperativa) at level 1, best adjacency vlan-1
0B.E9.AB.69 (ap-Garagem) at level 1, best adjacency vlan-1
0B.E9.AB.99 (ap-Pousada) at level 1, best adjacency vlan-1
0B.E9.AB.E1 (ap-Biblio) at level 1, best adjacency vlan-1
0B.E9.AC.05 (ap-Sala-Prof-Predio-Central) at level 1, best adjacency vlan-1
0B.E9.AC.09 (ap-LabFito) at level 1, best adjacency vlan-1
0B.F4.CE.30 (ap-Refeitorio) at level 1, best adjacency vlan-1
0B.F4.CE.3A (ap621-F4CE3A) at level 1, best adjacency vlan-1
0B.F4.CE.A4 (ap-Ginasio-Quadra) at level 1, best adjacency vlan-1
0B.F4.CE.B8 (ap-Zootecnia3-Bovinos1) at level 1, best adjacency vlan-1
0B.F4.CE.BE (ap-subsolo-biblio) at level 1, best adjacency vlan-1
0B.F4.CE.CC (ap-Agri2-CultAnuais) at level 1, best adjacency vlan-1
0B.F4.CE.DA (ap-Zootecnia3-Bovinos2) at level 1, best adjacency vlan-1
0B.F4.CE.FA (ap-Corredor-DEX-02) at level 1, best adjacency vlan-1
0B.F4.CE.FC (ap-aloj2) at level 1, best adjacency vlan-1
0B.F4.CF.00 (ap-Aloj3-Rad2) at level 1, best adjacency vlan-1
0B.F4.CF.12 (ap-Aloj1Rad2) at level 1, best adjacency vlan-1
0B.F4.CF.16 (ap-Corredor-DAE) at level 1, best adjacency vlan-1
0B.F4.CF.1E (ap-Aloj3Rad1) at level 1, best adjacency vlan-1
19.6E.2F.83 (rfs02) at level 1, best adjacency vlan-1
1A.41.B1.18 (ap-CorredorBiotecnologia) at level 1, best adjacency vlan-1
1A.41.B1.1A (ap-Agroindustria) at level 1, best adjacency vlan-1
1A.41.B2.5A (ap-AlojamentoFeminino) at level 1, best adjacency vlan-1
1A.41.B3.52 (ap-Mecanica) at level 1, best adjacency vlan-1
1A.42.02.F6 (ap-Agri1-Olericultura-novo) at level 1, best adjacency vlan-1
75.03.25.78 (ap7532-A13-Sup-Fundos) at level 1, best adjacency vlan-1
75.03.25.C0 (ap7532-A13-Inf-Centro) at level 1, best adjacency vlan-1
75.03.26.74 (ap7532-A13-Sup-Cenrto) at level 1, best adjacency vlan-1
75.03.33.DC (ap7532-SalaA104-PCentral) at level 1, best adjacency vlan-1
75.03.33.EC (ap7532-A13-Inf-Fundos) at level 1, best adjacency vlan-1
75.03.34.04 (ap7532-Auditorio-Central) at level 1, best adjacency vlan-1
75.03.34.14 (ap7532-SalaA102-PCentral) at level 1, best adjacency vlan-1
75.03.34.38 (ap7532-CTI) at level 1, best adjacency vlan-1
75.03.35.00 (ap7532-AlojamentoHorta) at level 1, best adjacency vlan-1
75.03.35.0C (ap7532-SaguaoTI-Sup) at level 1, best adjacency vlan-1
75.03.35.10 (ap7532-Auditorio-Adm) at level 1, best adjacency vlan-1
75.03.35.28 (ap7532-ArtesCultura) at level 1, best adjacency vlan-1
75.03.37.40 (ap7532-A13-Inf-Frente) at level 1, best adjacency vlan-1
75.03.3A.F8 (ap7532-A13-Sup-Frente) at level 1, best adjacency vlan-1

0 Kudos

ckelly
Extreme Employee
In response to Tomasz

‎10-25-2018 04:05 PM

Based on the config and what I'm seeing here, you have a cluster of controllers (.15.1 and .15.2 ?)
Can you confirmed that the two controllers have successfully established a cluster?
#show cluster status
#show cluster members

Also, I don't *think* that the AP should be rebooting when it receives this new configuration (only when it gives up and reverts to previous config).
What is the status of the query on the AP:
#service show reboot-history

And to help to better see what is happening in the logs, run this on the AP:
#show mint neighbors

Sorry for requesting all the info. There's something here that I'm not seeing. In the end, this is GOING to be something simple. 🙂

0 Kudos

Tiago_Juliano_F
New Contributor
In response to Tomasz

‎10-25-2018 04:05 PM

It did not work even by setting DHCP. The AP receives the IP in the new Vlan but when restart everything undoes.

show adoption log adoptee
2018-10-29 14:42:42:Received 0 hostnames through DHCP option 191
2018-10-29 14:41:37:Received 0 hostnames through DHCP option 191
2018-10-29 13:22:08:Received 0 hostnames through DHCP option 191
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:MLCP created VLAN link on VLAN 1, offer from 5C-0E-8B-19-DB-D3
2018-10-29 13:21:05:MLCP VLAN link already exists
2018-10-29 13:21:05:Sending MLCP Request to 5C-0E-8B-19-DB-D3 vlan 1
2018-10-29 13:21:05:Received 0 hostnames through DHCP option 191
2018-10-29 13:21:02:Received OK from cfgd, adoption complete to 0B.19.DB.D3
2018-10-29 13:21:00:Sending MLCP_DISCOVER to IP 172.16.15.1, UDP port 0
2018-10-29 13:21:00:Sending MLCP_DISCOVER to IP 172.16.15.2, UDP port 0
2018-10-29 13:20:59:Waiting for cfgd OK, adopter should be 0B.19.DB.D3
2018-10-29 13:20:59:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:59:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2018-10-29 13:20:59:Try to adopt to 0B.19.DB.D3 (cluster master 0B.19.DB.D3 in adopters)
2018-10-29 13:20:58:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 0B.19.DB.D3
2018-10-29 13:20:58:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:58:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2018-10-29 13:20:58:Try to adopt to 19.6E.2F.83 (cluster master 0B.19.DB.D3 not in adopters)
2018-10-29 13:20:57:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 0B.19.DB.D3
2018-10-29 13:20:57:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:57:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2018-10-29 13:20:57:Try to adopt to 19.6E.2F.83 (cluster master 0B.19.DB.D3 not in adopters)
2018-10-29 13:20:56:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 0B.19.DB.D3
2018-10-29 13:20:56:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:56:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2018-10-29 13:20:56:Try to adopt to 19.6E.2F.83 (cluster master 0B.19.DB.D3 not in adopters)
2018-10-29 13:20:56:Got new value for MTU: 1500 Was: 0
2018-10-29 13:20:56:MLCP created VLAN link on VLAN 1, offer from 5C-0E-8B-19-DB-D3
2018-10-29 13:20:56:MLCP VLAN link already exists
2018-10-29 13:20:56:Sending MLCP Request to 5C-0E-8B-19-DB-D3 vlan 1
2018-10-29 13:20:55:Sending MLCP_DISCOVER to IP 172.16.15.1, UDP port 0
2018-10-29 13:20:55:Sending MLCP_DISCOVER to IP 172.16.15.2, UDP port 0
2018-10-29 13:20:50:Sending MLCP_DISCOVER to IP 172.16.15.1, UDP port 0
2018-10-29 13:20:50:Sending MLCP_DISCOVER to IP 172.16.15.2, UDP port 0
2018-10-29 13:20:50:Start MLCP IP Discover
2018-10-29 13:20:50:Clearing already existing ipsec secure config for MLCP group 0 candidate 172.16.15.2
2018-10-29 13:20:50:Clearing already existing ipsec secure config for MLCP group 0 candidate 172.16.15.1
2018-10-29 13:20:50:DNS resolution completed, starting MLCP
2018-10-29 13:20:50:Received 0 hostnames through DHCP option 191
2018-10-29 13:20:50:Adoption state change: 'Disabled' to 'No adopters found'
2018-10-29 13:20:50:DNS resolution completed, starting MLCP
2018-10-29 13:20:50:Adoption enabled due to configuration

show mint mlcp history
2018-10-29 14:42:42:Received 0 hostnames through DHCP option 191
2018-10-29 14:41:37:Received 0 hostnames through DHCP option 191
2018-10-29 13:22:08:Received 0 hostnames through DHCP option 191
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING
2018-10-29 13:21:05:MLCP created VLAN link on VLAN 1, offer from 5C-0E-8B-19-DB-D3
2018-10-29 13:21:05:MLCP VLAN link already exists
2018-10-29 13:21:05:Sending MLCP Request to 5C-0E-8B-19-DB-D3 vlan 1
2018-10-29 13:21:05:Received 0 hostnames through DHCP option 191
2018-10-29 13:21:02:Received OK from cfgd, adoption complete to 0B.19.DB.D3
2018-10-29 13:21:00:Sending MLCP_DISCOVER to IP 172.16.15.1, UDP port 0
2018-10-29 13:21:00:Sending MLCP_DISCOVER to IP 172.16.15.2, UDP port 0
2018-10-29 13:20:59:Waiting for cfgd OK, adopter should be 0B.19.DB.D3
2018-10-29 13:20:59:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:59:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2018-10-29 13:20:59:Try to adopt to 0B.19.DB.D3 (cluster master 0B.19.DB.D3 in adopters)
2018-10-29 13:20:58:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 0B.19.DB.D3
2018-10-29 13:20:58:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:58:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2018-10-29 13:20:58:Try to adopt to 19.6E.2F.83 (cluster master 0B.19.DB.D3 not in adopters)
2018-10-29 13:20:57:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 0B.19.DB.D3
2018-10-29 13:20:57:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:57:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2018-10-29 13:20:57:Try to adopt to 19.6E.2F.83 (cluster master 0B.19.DB.D3 not in adopters)
2018-10-29 13:20:56:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 0B.19.DB.D3
2018-10-29 13:20:56:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2018-10-29 13:20:56:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2018-10-29 13:20:56:Try to adopt to 19.6E.2F.83 (cluster master 0B.19.DB.D3 not in adopters)
2018-10-29 13:20:56:Got new value for MTU: 1500 Was: 0
2018-10-29 13:20:56:MLCP created VLAN link on VLAN 1, offer from 5C-0E-8B-19-DB-D3
2018-10-29 13:20:56:MLCP VLAN link already exists
2018-10-29 13:20:56:Sending MLCP Request to 5C-0E-8B-19-DB-D3 vlan 1
2018-10-29 13:20:55:Sending MLCP_DISCOVER to IP 172.16.15.1, UDP port 0
2018-10-29 13:20:55:Sending MLCP_DISCOVER to IP 172.16.15.2, UDP port 0
2018-10-29 13:20:50:Sending MLCP_DISCOVER to IP 172.16.15.1, UDP port 0
2018-10-29 13:20:50:Sending MLCP_DISCOVER to IP 172.16.15.2, UDP port 0
2018-10-29 13:20:50:Start MLCP IP Discover
2018-10-29 13:20:50:Clearing already existing ipsec secure config for MLCP group 0 candidate 172.16.15.2
2018-10-29 13:20:50:Clearing already existing ipsec secure config for MLCP group 0 candidate 172.16.15.1
2018-10-29 13:20:50:DNS resolution completed, starting MLCP
2018-10-29 13:20:50:Received 0 hostnames through DHCP option 191
2018-10-29 13:20:50:Adoption state change: 'Disabled' to 'No adopters found'
2018-10-29 13:20:50:DNS resolution completed, starting MLCP
2018-10-29 13:20:50:Adoption enabled due to configuration

0 Kudos
GTM-P2G8KFN