topic RE: XMC Alarm EAC "Access Control Lost Contact with Switch" in ExtremeCloud IQ- Site Engine Management Center

XMC Alarm EAC "Access Control Lost Contact with Switch"

EF — Mon, 26 Nov 2018 17:25:00 GMT

Hi guys,

XMC running release 8.1.5.22 is showing constantly an alarm in EAC "Access Control Lost Contact with Switch" with one stack ERS4900, but this stack is configured with 802.1X and the users have no problems to authenticated, so the stack is able to send the EAP request to the EAC without problem.

I don´t know what is the meaning of this alarm and how to solve it.

Regards,

EF

RE: XMC Alarm EAC "Access Control Lost Contact with Switch"

Ronald_Dvorak — Mon, 26 Nov 2018 17:30:00 GMT

You get that error e.g. if the switch is down - so it looks like that XMC has issues to communicate all the time with the switch.
Is the switch green/reachable in XMC all the time or do you get a SNMP timeout ?

RE: XMC Alarm EAC "Access Control Lost Contact with Switch"

EF — Mon, 26 Nov 2018 17:44:00 GMT

The switch is allways in green status on XMC and as I told you the switch is able to comunicate with the EAC.

RE: XMC Alarm EAC "Access Control Lost Contact with Switch"

EF — Mon, 26 Nov 2018 18:14:00 GMT

The RW community was wrong, but the switch status in XMC was always green, maybe with the RO is enough to show it.

solved.

Regards,

EF

RE: XMC Alarm EAC "Access Control Lost Contact with Switch"

Tomasz — Mon, 26 Nov 2018 20:17:00 GMT

Hi,

XMC green icon is when XMC itself reaches the gateway or switch or else, but for NAC connectivity you should take a look at it from NAC point of view (e.g. pings from NAC appliance). But if it's running authentication smoothly, maybe the alarm just wasn't cleared? Some alarms in XMC are cleared automatically (with other type of alarms) and some have to be cleared manually by default.

HTH,
Tomasz

RE: XMC Alarm EAC "Access Control Lost Contact with Switch"

EF — Mon, 26 Nov 2018 20:29:00 GMT

HI Tomasz,

this alarm is configured to be cleared automatically, and I creared it several times before, but the alarm apears again, the problem was that the RW SNMP community was wrong.

Regards

EF