• All
  • Test
  • Startup
  • Experience Case
  • FAQ
Product line
Search
Cancel
Documents type
Author
Time
Search

DR2000 EIA dot1x authentication failed

2021-12-22 20:09:37 Published
  • 0Followed
  • 0Collected ,324Browsed
fans:0 follow:0

Network Topology

Topology


Problem Description

A site reported that the ADCampus (virtual machine deployment) user dot1x authentication failed, and the iNode client showed that the connection failed.


Process Analysis

The ADCampus packet capture shows that there is only one access request packet from a device to the Campus, and no response to the leaf device's access-accept packet.


In the debug level log of the ADEIA component, the relevant error is seen as:

%% 2021-11-19 11:45:05.217 ; [ERR] ; [7936] ; radEnt ; chkMsgAttr: Invalid Msg-Authenticator received from 192.168.40.2

After communicating with IMC experts, they reported that this error was a verification error. Check whether the RADIUS KEY configured on the device is consistent with the access device secret key on the EIA.

But we confirm that the shared key (12345) between the device and the EIA side has been reconfigured and is consistent.

In business parameter configuration-system configuration-system parameter configuration, change the "key display mode" to plain text, and then look at the shared key value corresponding to 192.168.40.2 in the access device on the iMC.



So collected the clients files in the iMC/uam/etc directory for IMC EIA R&D.



Solution

R&D feedback needs to replace relevant EIA documents attached to solve the problem of Invalid Msg-Authenticator

1. Stop the uam process in the monitoring agent

 2. Back up uam.exe, libeay32.dll, and ssleay32.dll in the iMC/uam/bin directory, and then copy the files in the compressed package to this directory 

3. Restart the uam process in the monitoring agent

After the file is replaced, the on-site problem is solved and the authentication is successful.


Please rate this case:   
0 comments

No comments

Add Comments:

举报

×

侵犯我的权益 >
对根叔知了社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔知了社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明

提出建议

    +

Login before you can operate!

login

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作