I believe the "conductor" alias there is supposed to serve that purpose.
Please open a case with TAC on this.
Original Message:
Sent: Feb 27, 2024 10:40 AM
From: alexb
Subject: AMON messages not received for switch
Hello Carson,
I already upgraded to from 8.10.0.8 to 8.10.0.10 last week.
This is what I have in all my MDs
mgmt-server primary-server 10.8.36.68 profile default-amp transport udp
mgmt-server primary-server conductor profile default-controller transport udp
Does that mean I have to add the Mobility Conductor instead of the Airwave as the 'mgmt-server primary-server'?
Original Message:
Sent: Feb 27, 2024 10:23 AM
From: chulcher
Subject: AMON messages not received for switch
Upgrade to 8.10.0.9, 8.11.2.1, or newer for a bug fix related to this message. If that doesn't fix, there is a possibility that adding the IP address of the MCR to 'mgmt-server primary-server <ip>' for the MD config will fix.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Feb 27, 2024 10:04 AM
From: alexb
Subject: AMON messages not received for switch
Anyone know what these messages mean?
Feb 26 00:29:46 mcfc1 AirMatch[21627]: <356301> <21627> <ERRS> <mcFC1 10.8.36.70> mcell_recv :AMON messages not received for switch IP: 10.1.1.75
Feb 26 00:29:46 mcfc1 AirMatch[21627]: <356301> <21627> <ERRS> <mcFC1 10.8.36.70> mcell_recv :AMON messages not received for switch IP: 10.1.1.74
Controllers are part of a 3-device cluster, currently both dont have APs
Tried to search for some meaning online but couldnt find any.
Thanks!
Alex