AP7632 can't adopt on specific Remote Site

Richard_Augusto — Tue, 29 Jan 2019 03:47:14 GMT

Hello,

We have swapping AP650 to AP7632 on remote sites, but in one specific site, our ap7632 have problems on provisioning profile. Can adopt on VX9000 but have "config error"

# show adop status

AP-SHOP...A-FUNDO 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:44:04 4 days 01:00:37
AP-CIDA...NQUEDOS 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:43:58 9 days 06:08:12
AP-CIDA...X-FUNDO 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:44:04 8 days 03:25:53
AP-CIDA...-FRENTE 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:43:42 8 days 03:25:49
ap7632-0D9A05 5.9.1.5-001R error Yes VX9000-BEMOL 0 days 00:32:14 0 days 00:35:09
ap7632-0D9A5A 5.9.1.5-001R error Yes VX9000-BEMOL 0 days 00:33:33 0 days 00:35:18
ap7632-0D9A7D 5.9.1.5-001R error Yes VX9000-BEMOL 0 days 00:40:07 0 days 00:42:07
ap7632-0D9A87 5.9.1.5-001R error Yes VX9000-BEMOL 0 days 00:40:01 0 days 00:42:12
AP-BVA-16 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:44:05 34 days 00:16:56
AP-BVA-07 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:44:08 34 days 00:16:56
AP-GRAN...-ESCADA 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:44:02 172 days 12:14:40
AP-BVA-06 5.9.1.5-001R configured No VX9000-BEMOL 0 days 06:44:04 34 days 00:16:47
... more APs

# VX9000-BEMOL*#show adoption log adoptee on ap7632-0D9A87

2019-01-28 18:49:26:Received OK from cfgd, adoption complete to 12.3C.EA.66
2019-01-28 18:49:26:Waiting for cfgd OK, adopter should be 12.3C.EA.66
2019-01-28 18:49:26:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2019-01-28 18:49:26:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2019-01-28 18:49:26:Try to adopt to 12.3C.EA.66 (cluster master 12.3C.EA.66 in adopters)
2019-01-28 18:49:00:Got new value for MTU: 1500 Was: 0
2019-01-28 18:49:00:Sending MLCP_REQUEST to 10.74.1.1:0
2019-01-28 18:48:55:Received MLCP offer from 10.74.1.1:24576 preferred=0 capacity = 25544 (force:0, level 2)
2019-01-28 18:48:55:Sending MLCP_DISCOVER to IP 10.74.1.1, UDP port 0
2019-01-28 18:48:55:Start MLCP IP Discover
2019-01-28 18:48:55:Clearing already existing ipsec secure config for MLCP group 0 candidate 10.74.1.1
2019-01-28 18:48:55:DNS resolution completed, starting MLCP
2019-01-28 18:48:55:Received 1 hostnames through DHCP option 191
2019-01-28 18:48:21:Received 0 hostnames through DHCP option 191
2019-01-28 18:48:21:Adoption state change: 'Disabled' to 'No adopters found'
2019-01-28 18:48:21:DNS resolution completed, starting MLCP
2019-01-28 18:48:21:Adoption enabled due to configuration

Capturing up to 50 packets. Use Ctrl-C to abort.
1 19:21:25.363434 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data length 116, DSCP 0| DGRAM 12.3C.EA.66/0 > 00.00.00.00/12 router HELO from 12.3C.EA.66
2 19:21:29.526125 MINT 94-9B-2C-0D-9A-87 > 01-A0-F8-00-00-00 | DGRAM 2C.0D.9A.87/34 > 00.00.00.00/34 mlcp, discover
3 19:21:29.860055 MINT 94-9B-2C-0D-9A-5A > 01-A0-F8-00-00-00 | DGRAM 2C.0D.9A.5A/34 > 00.00.00.00/34 mlcp, discover
4 19:21:34.086147 MINT 94-9B-2C-0D-9A-05 > 01-A0-F8-00-00-00 | DGRAM 2C.0D.9A.
5 19:21:34.489097 UDP: 10.74.52.51 > 10.74.1.1 ports 24576 > 24576, data length
6 19:21:38.183329 UDP: 10.74.52.51 > 10.74.1.1 ports 24576 > 24576, data length
7 19:21:38.392980 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data length
8 19:21:40.365354 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data length
9 19:21:42.266207 MINT 94-9B-2C-0D-97-03 > 01-A0-F8-00-00-00 | DGRAM 2C.0D.97.
10 19:21:46.809662 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data lengt
11 19:21:49.743254 UDP: 10.74.52.51 > 10.74.1.1 ports 24576 > 24576, data lengt
12 19:21:52.604819 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data lengt
13 19:21:55.515495 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data lengt
14 19:22:04.874410 UDP: 10.74.52.51 > 10.74.1.1 ports 24576 > 24576, data lengt
15 19:22:08.198260 UDP: 10.74.52.51 > 10.74.1.1 ports 24576 > 24576, data lengt
16 19:22:08.403677 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data lengt
17 19:22:10.665609 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data lengt
18 19:22:19.976824 UDP: 10.74.52.51 > 10.74.1.1 ports 24576 > 24576, data lengt
19 19:22:25.693517 UDP: 10.74.1.1 > 10.74.52.51 ports 24576 > 24576, data length 116, DSCP 0| DGRAM 12.3C.EA.66/0 > 00.00.00.00/12 router HELO from 12.3C.EA.66

# ap7632-0D9A87#show adoption status
Adopted by:
Type : VX9000
System Name : VX9000-BEMOL
MAC address : 00-0C-29-3C-EA-66
MiNT address : 12.3C.EA.66
Time : 0 days 00:48:49 ago

Mint ping from AP to VX9000:

MiNT ping 12.3C.EA.66 with 1473 bytes of data.
Response from 12.3C.EA.66: id=16777216 time=4.720 ms
Response from 12.3C.EA.66: id=33554432 time=5.089 ms
Response from 12.3C.EA.66: id=50331648 time=5.722 ms

MiNT ping 12.3C.EA.66 with 1500 bytes of data.
Response from 12.3C.EA.66: id=16777216 time=4.531 ms
Response from 12.3C.EA.66: id=33554432 time=4.667 ms
Response from 12.3C.EA.66: id=50331648 time=4.762 ms

Auto provisioning police - Ok!
Profile ap7632 w/ controller host - Ok
Option 191 - Ok!
Native VLAN for MLCP - Ok!
MTU - Works fine.

Any idea?

Problem w/ this version on AP7632? WiNG Version: 5.9.1.5

I Checked profile, deleted adopted APs, reboot VX9000. Not sucess.

I'm planning to update to 5.9.3.1 04-Feb-2019. I can post feedback here, again.

Thanks

Re: AP7632 can't adopt on specific Remote Site

Aviv_Kedem — Fri, 08 Feb 2019 02:32:19 GMT

Hello Richard,

I saw many bug fixes for ap7632 until 5.9.3.1.
I'll suggest to update, if you can.

Regards,

Aviv

Re: AP7632 can't adopt on specific Remote Site

Richard_Augusto — Sat, 23 Feb 2019 12:39:21 GMT

Hello Aviv,

Version 5.9.3.1 and decrease MTU (1436) in global MiNT MTU solved adoption problem on AP7632!

Thanks!

topic AP7632 can't adopt on specific Remote Site in ExtremeWireless (WiNG)

AP7632 can't adopt on specific Remote Site

Re: AP7632 can't adopt on specific Remote Site

Re: AP7632 can't adopt on specific Remote Site