cancel
Showing results for 
Search instead for 
Did you mean: 

'Adoption failed': Connection error 145

'Adoption failed': Connection error 145

Tomasz_Fajga
New Contributor

Hello,

I have VX9000E and about 40 AP6521 connected to it. After changing switches to Aruba I have an issue with adoption this AP by controller.

AP has IP link with controller but is not adopting. It happend only on few AP, most of AP are adopted. For example I have 4 AP connected to the same switch and 2 of them are adopted by controller, 2 not adopted.

I checked configuration of switch but I do not see any "strange things".

Maybe somebody has the same problem and solution?

2022-11-16 08:42:33:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:42:07:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:42:07:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:41:37:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:41:12:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:41:12:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:40:42:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:40:16:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:40:16:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:39:46:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:39:20:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:39:20:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:38:50:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:38:25:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:38:25:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:37:55:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:37:29:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:37:29:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:36:59:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:36:34:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-11-16 08:36:34:Try to adopt to 12.00.8E.05 (cluster master 00.00.00.00 in adopters)
2022-11-16 08:36:04:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2022-11-16 08:35:38:Adoption state change: 'Adoption failed' to 'Connecting to adopter'

3 REPLIES 3

Christoph_S
Extreme Employee

Hello Tomasz,

The easiest way to test this, is to plug one of the unadopted APs into the switchport of an adopted one and and vice versa, plug an adopted AP into the switchport of an unadopted one. If the issue follows the AP then issue on AP side and if not then issue is on the switch side. 

A place to start. 

BR,

Christoph S.

Hello Christoph,

I have tested it this way. Changing switchport of unadopted AP doesn't help. When I reload VX9000 I see only 6 AP adopted, which are on different location and connected throw VPN. When I leave VX9000 running few hours some ofe the local AP adopts. Sometimes it adopts 20 AP, sometimes 24. I do not know what it depends on. Maybe the problem is on the main switch??? I found out recently that this customer has also changed hardware of server, where VX9000 is running. Can it be also problem with configuration of virtual machine?

Tomasz_Fajga
New Contributor

Firmware version is 5.9.1.5-001R

GTM-P2G8KFN