topic Re: vx9000 issue - CONFIG_REVISION Configuration revision updated in ExtremeWireless (WiNG)

vx9000 issue - CONFIG_REVISION Configuration revision updated

marconet_22 — Fri, 02 Jan 2026 23:10:11 GMT

I have vx9000 as virtual controller to multisite, release 7.7.1.3-005R, various APs type

One site, AP305cx, every first of the mounth every APs reboot or disconnect from controller and re-adopt disconnect and re-adopt many time for 20 minutes.

From event history i see many log like this:

CONFIG_REVISION Configuration revision updated to 11 from 12
2026-01-02 02:44:04 AP42-Mag-Vercelli SYSTEM CONFIG_REVISION Configuration revision updated to 11 from 11
2026-01-02 02:44:04 AP06-Mag-Vercelli SYSTEM CONFIG_COMMIT Configuration commit by user 'cfgd' (update own config) from '127.0.0.1'
2026-01-02 02:44:04 AP42-Mag-Vercelli SYSTEM CONFIG_COMMIT Configuration commit by user 'cfgd' (update own config) from '127.0.0.1'
2026-01-02 02:44:04 AP06-Mag-Vercelli CFGD ACL_RULE_ALTERED USER: cfgd session 87: ACL BROADCAST-MULTICAST-CONTROL rule is getting altered
2026-01-02 02:44:04 AP42-Mag-Vercelli CFGD ACL_RULE_ALTERED USER: cfgd session 23: ACL BROADCAST-MULTICAST-CONTROL rule is getting altered
2026-01-02 02:44:04 AP06-Mag-Vercelli DEVICE ADOPTED_TO_CONTROLLER Joined successfully with controller 'ARSBARWARECTL'(12.BA.08.E9)
2026-01-02 02:44:04 AP42-Mag-Vercelli DEVICE ADOPTED_TO_CONTROLL

Issue resolved without any action to the vx9000.

What can i check?

Re: vx9000 issue - CONFIG_REVISION Configuration revision updated

Angelo_Cargnel — Sun, 04 Jan 2026 11:21:30 GMT

This issue sounds very familiar to me.
There is some error in the AP configuration on the controller, which will break the adoption once the AP receives it's configuration from the controller.
What happens?

The AP "AP42-Mag-Vercelli" adopts to the VX9000 (Configuration is on revision 11).
The VX9000 will send the configuation to the AP (Configuration revision updated to 11 from 12).
The AP will update it's configuration due to to this.
After implementing the configuration changes, the adoption of the AP gets lost.
The AP will recognize the loss of the adoption to the controller and revert back to the "good known working configuration" (Configuration revision updated to 11 from 11 and Configuration commit by user 'cfgd' (update own config) from '127.0.0.1').
The AP performs a warm boot, re-adopts and the loop starts again (for ever).

To proof my guess please use the CLI command "show adoption config-errors AP42-Mag-Vercelli" in the VX9000.
You should some error messages.
Please post those together with the AP profile and the AP override and I will have a look for the configuration error.

Re: vx9000 issue - CONFIG_REVISION Configuration revision updated

marconet_22 — Wed, 07 Jan 2026 08:02:04 GMT

Hi Angelo

this is resul of show adoption .. command

AP Profile

profile ap305cx AP305CX-MAG-Vercelli-Omni
ip default-gateway 10.58.119.254
no autoinstall configuration
no autoinstall firmware
antenna-id external group-1 ml-2452-pta4m4-036
antenna-id external group-2 ml-2452-pta4m4-036
crypto ikev1 policy ikev1-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ikev2 policy ikev2-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ipsec transform-set default esp-aes-256 esp-sha-hmac
crypto ikev1 remote-vpn
crypto ikev2 remote-vpn
crypto auto-ipsec-secure
crypto load-management
crypto remote-vpn-client
interface radio1
wlan WIFI-MAG-RF-Vercelli bss 1 primary
wlan WLAN-DNOWPA2-Mag-VLAN22 bss 2 primary
no 11axSupport
interface radio2
wlan WIFI-MAG-RF-Vercelli bss 1 primary
wlan WLAN-DNOWPA2-Mag-VLAN22 bss 2 primary
no 11axSupport
interface bluetooth1
shutdown
mode le-sensor
interface ge1
switchport mode trunk
switchport trunk allowed vlan 1-4094
switchport trunk native vlan 603
interface vlan603
description DNO-VC-NETMGMT
ip address dhcp
ip dhcp client request options all
interface pppoe1
interface usb0
use firewall-policy default
logging on
controller host xx.xx.xx.xx pool 1 level 2
service pm sys-restart
router ospf
adoption-mode controller

OVERRIDE

There is no override

SHOW LOGGING, the issue is on the 2nd January

AP42-Mag-Vercelli#show logging

Logging module: enabled
Aggregation time: disabled
Console logging: level warnings
Monitor logging: disabled
Buffered logging: level warnings
Syslog logging: level warnings
Facility: local7

Log Buffer (3419 bytes):

Jan 07 06:59:16 2026: %DATAPLANE-4-DOSATTACK: BAD_PACKET: Bcast/Mcast ICMP not allowed : Src IP : 10.58.114.20, Dst IP: 10.58.115.255, Src Mac: 48-9E-BD-31-05-BF, Dst Mac: FF-FF-FF-FF-FF-FF, ICMP type = 3, ICMP code = 3, Proto = 1
Jan 07 06:59:16 2026: %KERN-4-WARNING: [446541.485440]
Jan 07 03:06:31 2026: %KERN-4-WARNING: [432576.099439] PRNG seed file updated
Jan 06 23:26:48 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 06 15:05:36 2026: %KERN-4-WARNING: [389322.348439] PRNG seed file updated
Jan 06 03:04:43 2026: %KERN-4-WARNING: [346068.595441] PRNG seed file updated
Jan 05 23:31:39 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 05 18:10:47 2026: %DATAPLANE-4-DOSATTACK: BAD_PACKET: Bcast/Mcast ICMP not allowed : Src IP : 10.58.114.8, Dst IP: 10.58.115.255, Src Mac: 48-9E-BD-31-07-97, Dst Mac: FF-FF-FF-FF-FF-FF, ICMP type = 3, ICMP code = 3, Proto = 1
Jan 05 18:10:47 2026: %KERN-4-WARNING: [314033.307443]
Jan 05 15:03:49 2026: %KERN-4-WARNING: [302814.790440] PRNG seed file updated
Jan 05 03:02:55 2026: %KERN-4-WARNING: [259561.069444] PRNG seed file updated
Jan 04 15:02:01 2026: %KERN-4-WARNING: [216307.368444] PRNG seed file updated
Jan 04 03:01:07 2026: %KERN-4-WARNING: [173053.563440] PRNG seed file updated
Jan 04 01:12:34 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 03 15:00:13 2026: %KERN-4-WARNING: [129799.817446] PRNG seed file updated
Jan 03 02:59:19 2026: %KERN-4-WARNING: [86546.028447] PRNG seed file updated
Jan 02 14:58:26 2026: %KERN-4-WARNING: [43292.297442] PRNG seed file updated
Jan 02 06:02:47 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 05:58:36 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 05:52:17 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 05:50:29 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 05:38:00 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 05:30:37 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: [Errno 104] Connection reset by peer
Jan 02 05:30:03 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 04:20:58 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 04:03:47 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 04:00:10 2026: %USER-3-ERR: main.pyo: * * ERROR: lost connectivity with adopter after config update; 1 other adopters still available; do not reload older config at this time
Jan 02 04:00:10 2026: %USER-3-ERR: main.pyo: * * ERROR: check config failed; error : not-adopted
Jan 02 03:52:25 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:46:45 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:45:06 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:25:36 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:12:04 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:10:31 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:08:03 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
Jan 02 03:03:44 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out
AP42-Mag-Vercelli#

Re: vx9000 issue - CONFIG_REVISION Configuration revision updated

Angelo_Cargnel — Thu, 08 Jan 2026 15:18:48 GMT

As already assumed, the controller is sending a config update to the AP and due to this update, the AP is dropping it's adoption.
"Jan 06 23:26:48 2026: %USER-3-ERR: main.pyo: * * ERROR: receive update error: timed out"
"Jan 02 04:00:10 2026: %USER-3-ERR: main.pyo: * * ERROR: check config failed; error : not-adopted"

This may have several reasons.
If you like you can attach the full VX9000 config to this thread and I will have a look.
But you should remove or hide any passworts, keys, etc...

Actually my best guess is a wrong configured firewall policy (Jan 07 06:59:16 2026: %DATAPLANE-4-DOSATTACK: BAD_PACKET: Bcast/Mcast ICMP not allowed : Src IP : 10.58.114.20, Dst IP: 10.58.115.255, Src Mac: 48-9E-BD-31-05-BF, Dst Mac: FF-FF-FF-FF-FF-FF, ICMP type = 3, ICMP code = 3, Proto = 1) or wrong IP settings (ip default-gateway 10.58.119.254).

But the full config would be the best.

Re: vx9000 issue - CONFIG_REVISION Configuration revision updated

marconet_22 — Fri, 09 Jan 2026 14:15:17 GMT

Little update, I discovered that these APs (Type A-Warehouse) are in the same area of other Extreme APs (Type B-Office).

Type A have native vlan 603, all other vlans allowed on interface

Type B have native vlan 14, all other vlans allowed on interface

Type A and Type B can see together in VLAN1 and i think that this is the first issue because mint protocol works in L2 in ISO-OSI pile.

In 07/01/2026 I deleted VLAN1 from allowed vlan on both profile and they can't see each other.

Tonight APs reboot again, and the last thing to have is delete all vlans that i don't use with SSID or management of Access Point.

I think that ethernet cable interface of AP opened to all vlans is not good practice because it can listen to all vlan broadcast domains.

Don't you agree?

Re: vx9000 issue - CONFIG_REVISION Configuration revision updated

Angelo_Cargnel — Mon, 12 Jan 2026 11:53:36 GMT

I totally agree.
Get your VLAN's sorted and all should work well.

I was already wondering why the default gateway in your AP profile shows as "10.58.119.254" and the event history was showing firewall error with "Dst IP: 10.58.115.255"...

Good luck!