topic Event Message in ExtremeWireless (WiNG)

Event Message

ARUN_SHARMA — Tue, 07 Jan 2020 00:06:05 GMT

Hi,

I have configured VX9000 to send email,if any AP go down.I referred below events from GTAC portal to configure this.

event ap adopted-to-controller Access point adopted to controller
event ap adoption-redirected Access point redirected
event ap ap-unadopted Access port unadopted
event ap offline Adopted device is offline
event ap reset Access point reset

But now its sending to much adoption/unadoption mail very frequently.How can I check the issue from log for unadoption issue?

Its sending unadoption mail and within a minute its again sending adoption mail for same AP.And this is very frequent with multiple AP’s.

Kindly suggest to overcome this issue.I want a mail,if AP go down only and not for any state change.

Thanks,

ARUN

Re: Event Message

Madeline — Tue, 07 Jan 2020 14:59:24 GMT

Hi Arun,

For standard deployment, you shouldn't have frequent unadoption, you should check the network stability for mint connection in order to prevent adoption issue.

As for the event log, you can remove the rest except offline event:

If an AP is not seen within 15 minutes (default value, configurable), the controller will deem the AP as offline and thus send an offline event

Unfortunately, we do not have online event

Re: Event Message

ARUN_SHARMA — Tue, 07 Jan 2020 16:50:42 GMT

Hi Madeline,

Thanks for your revert.I am getting below logs in controller.

2019-12-02 07:00:20:Unadopted FC-0A-81-F1-37-2C (1A.F1.37.2C), cfgd not notified
2019-12-02 07:00:20:Unadopting FC-0A-81-F1-37-2C (1A.F1.37.2C) because it is unreachable
2019-12-02 06:57:59:Sending MLCP Reply to (00.00.00.00,8704,0,10.15.58.25:24576/60-00-01-00-0A-0F)
2019-12-02 06:57:56:Adopted FC-0A-81-F1-37-2C (1A.F1.37.2C), cfgd notified
2019-12-02 06:57:54:Sending MLCP Offer to 1A.F1.37.2C (link_level=2, preferred=0, capacity=25564)
2019-12-02 06:54:09:cfgd unadopted 1A.F1.37.2C
2019-12-02 06:54:09:Unadopted FC-0A-81-F1-37-2C (1A.F1.37.2C), cfgd not notified
2019-12-02 06:54:09:Unadopting FC-0A-81-F1-37-2C (1A.F1.37.2C) because it is unreachable
2019-12-02 06:29:13:Sending MLCP Reply to (00.00.00.00,8704,0,10.10.205.215:24576/60-00-01-00-0A-0A)
2019-12-02 06:29:12:Adopted B8-50-01-74-49-8C (1B.74.49.8C), cfgd notified
2019-12-02 06:29:10:Sending MLCP Offer to 1B.74.49.8C (link_level=2, preferred=0, capacity=25564)
2019-12-02 06:24:24:Sending MLCP Reply to (00.00.00.00,8704,0,10.10.144.250:24576/60-00-01-00-0A-0A)
2019-12-02 06:24:20:Adopted 74-67-F7-A5-15-DC (75.A5.15.DC), cfgd notified

How to check the exact reason for disconnection?

Re: Event Message

Madeline — Tue, 07 Jan 2020 16:54:37 GMT

Main reason for un-adoption is a device is unreachable
For remote-site distributed deployment, you can have a look on What is recommended MINT MTU size?

Re: Event Message

Richard_Augusto — Wed, 08 Jan 2020 04:47:12 GMT

Hello!

Check mint MTU in global config on our VX9000.

We have problems in very remote locations and decrease MTU resolve it.