Wireless Access

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

Thank you for your quick reply.

But a factory default is somewhat troublesome, as they come up and down all over the place...in a mix of switchers and OSes. 

I have re-provisioned.

Time with TAC later today.. (again!) If it doesn't work out today I have to roll back. (again!)

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

Controller was reloaded with "old", image, but not Conductor, and then the unwanted behavior stopped.

I'm waiting for the next stable release while TAC examines logs.

Thank you for your quick reply.

But a factory default is somewhat troublesome, as they come up and down all over the place...in a mix of switchers and OSes. 

I have re-provisioned.

Time with TAC later today.. (again!) If it doesn't work out today I have to roll back. (again!)

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.2_87606 AP reports Down

same behavior as in the previous two attempts despite the fix,:

Table 6: Resolved Issues in ArubaOS 8.11.1.2

AOS-243042
AOS-245983
AOS-245834
AOS-244676
AOS-243499
Some access points running ArubaOS 8.11.1.0 or later versions
crashed and rebooted unexpectedly. The crash logs listed the
reason for the error as BadPtr: 00000050 PC: anul_aon_flow_
ageout+0xac/0x180 [anul] Warm-reset.

The fix ensures APs work as expected.

Table 6: Resolved Issues in ArubaOS 8.11.1.2

Please anyone, TAC has been unresponsive for 6 month

Controller was reloaded with "old", image, but not Conductor, and then the unwanted behavior stopped.

I'm waiting for the next stable release while TAC examines logs.

Thank you for your quick reply.

But a factory default is somewhat troublesome, as they come up and down all over the place...in a mix of switchers and OSes. 

I have re-provisioned.

Time with TAC later today.. (again!) If it doesn't work out today I have to roll back. (again!)

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

Yes, thanks, 
and it keeps going on and on, and the error is moved forward all the way trough:
8.11.1.0
8.11.1.1 
8.11.1.2
and up to now 8.11.2.0.
It is unclear why the fine core of Aruba engineers is not engaged into this,?
Aruba TAC is not engaged in a proper manner, making this still unresolved.
The case has not even been giving its Defect ID !

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.2_87606 AP reports Down

same behavior as in the previous two attempts despite the fix,:

Table 6: Resolved Issues in ArubaOS 8.11.1.2

AOS-243042
AOS-245983
AOS-245834
AOS-244676
AOS-243499
Some access points running ArubaOS 8.11.1.0 or later versions
crashed and rebooted unexpectedly. The crash logs listed the
reason for the error as BadPtr: 00000050 PC: anul_aon_flow_
ageout+0xac/0x180 [anul] Warm-reset.

The fix ensures APs work as expected.

Table 6: Resolved Issues in ArubaOS 8.11.1.2

Please anyone, TAC has been unresponsive for 6 month

Controller was reloaded with "old", image, but not Conductor, and then the unwanted behavior stopped.

I'm waiting for the next stable release while TAC examines logs.

Thank you for your quick reply.

But a factory default is somewhat troublesome, as they come up and down all over the place...in a mix of switchers and OSes. 

I have re-provisioned.

Time with TAC later today.. (again!) If it doesn't work out today I have to roll back. (again!)

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

Did you ask them to escalate the issue?

Yes, thanks, 
and it keeps going on and on, and the error is moved forward all the way trough:
8.11.1.0
8.11.1.1 
8.11.1.2
and up to now 8.11.2.0.
It is unclear why the fine core of Aruba engineers is not engaged into this,?
Aruba TAC is not engaged in a proper manner, making this still unresolved.
The case has not even been giving its Defect ID !

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.2_87606 AP reports Down

same behavior as in the previous two attempts despite the fix,:

Table 6: Resolved Issues in ArubaOS 8.11.1.2

AOS-243042
AOS-245983
AOS-245834
AOS-244676
AOS-243499
Some access points running ArubaOS 8.11.1.0 or later versions
crashed and rebooted unexpectedly. The crash logs listed the
reason for the error as BadPtr: 00000050 PC: anul_aon_flow_
ageout+0xac/0x180 [anul] Warm-reset.

The fix ensures APs work as expected.

Table 6: Resolved Issues in ArubaOS 8.11.1.2

Please anyone, TAC has been unresponsive for 6 month

Controller was reloaded with "old", image, but not Conductor, and then the unwanted behavior stopped.

I'm waiting for the next stable release while TAC examines logs.

Thank you for your quick reply.

But a factory default is somewhat troublesome, as they come up and down all over the place...in a mix of switchers and OSes. 

I have re-provisioned.

Time with TAC later today.. (again!) If it doesn't work out today I have to roll back. (again!)

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?

Hope they do

Did you ask them to escalate the issue?

Yes, thanks, 
and it keeps going on and on, and the error is moved forward all the way trough:
8.11.1.0
8.11.1.1 
8.11.1.2
and up to now 8.11.2.0.
It is unclear why the fine core of Aruba engineers is not engaged into this,?
Aruba TAC is not engaged in a proper manner, making this still unresolved.
The case has not even been giving its Defect ID !

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.2_87606 AP reports Down

same behavior as in the previous two attempts despite the fix,:

Table 6: Resolved Issues in ArubaOS 8.11.1.2

AOS-243042
AOS-245983
AOS-245834
AOS-244676
AOS-243499
Some access points running ArubaOS 8.11.1.0 or later versions
crashed and rebooted unexpectedly. The crash logs listed the
reason for the error as BadPtr: 00000050 PC: anul_aon_flow_
ageout+0xac/0x180 [anul] Warm-reset.

The fix ensures APs work as expected.

Table 6: Resolved Issues in ArubaOS 8.11.1.2

Please anyone, TAC has been unresponsive for 6 month

Controller was reloaded with "old", image, but not Conductor, and then the unwanted behavior stopped.

I'm waiting for the next stable release while TAC examines logs.

Thank you for your quick reply.

But a factory default is somewhat troublesome, as they come up and down all over the place...in a mix of switchers and OSes. 

I have re-provisioned.

Time with TAC later today.. (again!) If it doesn't work out today I have to roll back. (again!)

I upgraded several smaller clusters to 8.11.1.1 without any issues. But have very similar issue when migrating from 8.9.1.7 to 10.4.0.1. Upgrade to 10.4.0.2 resolve my issue.

Did you try factory reset APs in reboot loop?

Best, Gorazd

About 5% of AP-535 & 635, do not get their own config after upgrade and restart constantly, same events as with 8.11.1.0 SSR_86591.

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down | Wireless Access (arubanetworks.com)

Anyone ?