★ iMC EIA 802.1x authentication cannot receive accounting messages
2023-09-27 17:18:27
Published
- 0 Followed
- 0Collected ，5020Browsed
Network Topology
None
Problem Description
IMC EIA performs 802.1x authentication. By capturing packets on the imc server side, it is found that the device has sent the corresponding accounting start message (code=4) to imc. However, the accounting start message sent by the device is not found in the uam debug log. message (code=4).
Process Analysis
Checking looked at the debug log of uam and found that after the imc server responded with the code=2 authentication pass message, it received an unrecognizable message from the device:
%% 2020-11-03 09:52:58.404 ; [LDBG] ; [459269888] ; DataSynTaskMgr ; creatTask: received an unknown message, command id: 21703%% 2020-11-03 09:52:58.421 ; [LDBG] ; [2204100352] ; rcv ; Received a packet (size:356) from host x.x.x.x:
...
%% 2020-11-03 09:52:58.421 ; [WARN] ; [2306848512] ; radDispatcher ; chkMsgHeader: Invalid Message Authenticator(from x.x.x.x).
%% 2020-11-03 09:52:58.444 ; [LDBG] ; [4227856128] ; DataSynTaskMgr ; creatTask: received an unknown message, command id: 21703
%% 2020-11-03 09:52:58.463 ; [LDBG] ; [4206876416] ; AsynDbSynTsk ; doAsynTask: to deal new task.
Solution
The reason is that the key for accounting packets configured on the device is inconsistent with that configured on the imc, causing the imc to be unable to recognize the corresponding packets.