• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 全部
  • 全部
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
高级搜索

Cannot enter system mode after logging in S75E via Telnet

2020-08-21 Published
  • 0关注
  • 0收藏,64浏览
孟普 五段
粉丝:1人 关注:0人

Network Topology

Null

Problem Description

A customer reported that after logging in S75E via Telnet, the user obtained the highest permission, but could not enter the system mode after logging in the device.


Process analysis

1. Log in S75E via Telnet, and find that the reboot command can be input normally, which means that the logged role has indeed obtained the highest privilege, and the debug information of 7506E can also be seen that the role has obtained the highest privilege, as follows:

*Aug 17 15:08:57:425 2017 XYKZC-KS-CORE-7506E-01 RADIUS/7/PACKET: -MDC=1;

    Service-Type=Callback-Administrative

    Session-Timeout=86400

    Login-Service=Telnet

H3c-Exec-Privilege=15


The authentication server is IMC, and role levels can also be seen on IMC:

CODE = 1.

ID = 71.

ATTRIBUTES:

         User-Name(1) = "test@hxks".

         Password(2) = "$$$".

         Service-Type(6) = 1.

         NAS-Identifier(32) = "XYKZC-KS-CORE-7506E-01".

         Framed-IP-Address(8) = 1781483207.

         NAS-IP-Address(4) = 1781530371.

 

%% 2017-08-17 13:01:53.499 ; [LDBG] ; [3932] ; radDispatcher ; prsRawPkt: chk-sum 3465568905.

%% 2017-08-17 13:01:53.499 ; [LDBG] ; [3932] ; LAN ; prsMixedUsr: in [test@hxks], out [test@hxks].

%% 2017-08-17 13:01:53.499 ; [LDBG] ; [3932] ; radEnt ; setPxyType: Needn&39;t proxy. domainname=hxks, Code=1.

%% 2017-08-17 13:01:53.499 ; [LDBG] ; [3932] ; LAN ; getIpMacFromItem: no attribute of Calling-Station-Id.

%% 2017-08-17 13:01:53.530 ; [LDBG] ; [2264] ; MNG ; Send message attribut list:

Code = 2

ID = 71

ATTRIBUTES:

Service_Type(6) = 1

Session-Timeout(27) = 86400

Login_Service(15) = 0

hw_Exec_Privilege(29) = 15


No command entered into the system view was found when entering the question mark, which is suspected to be a command line authorization problem.


2. Check the authentication, authorization, accounting, etc. of different applications in the Domain:

<XYKZC-KS-CORE-7506E-01>display domain

Total 2 domain(s)

 

Domain:system

 State: Active

 default Authentication Scheme:  local

 default Authorization  Scheme:  local

 default Accounting     Scheme:  local

 Authorization attributes :

  Idle-cut : Disable

 

Domain:hxks

 State: Active

 login   Authentication Scheme:  radius: hxks, local

 login   Authorization  Scheme:  radius: hxks, local

 login   Accounting     Scheme:  radius: hxks, none

 default Authentication Scheme:  local

 default Authorization  Scheme:  local

 default Accounting     Scheme:  local

 Authorization attributes :

Under Domain HXKS, everything is local except for login authentication, authorization, billing, and radius HXKS.


3. Once again display the information of the local server. Through debug, it can be found that there will be printing authorization failure and log that the user does not exist:

<XYKZC-KS-CORE-7506E-01>debugging local-server all

<XYKZC-KS-CORE-7506E-01>t m

The current terminal is enabled to display logs.

<XYKZC-KS-CORE-7506E-01>t  d

The current terminal is enabled to display debugging logs.

<XYKZC-KS-CORE-7506E-01>*Aug 18 14:29:14:043 2017 XYKZC-KS-CORE-7506E-01 LOCALSER/7/EVENT: -MDC=1;

 Received authorization request message.

*Aug 18 14:29:14:043 2017 XYKZC-KS-CORE-7506E-01 LOCALSER/7/EVENT: -MDC=1;

 Authorization failed, user "hxks" doesn&39;t exist.


Telnet logins are all authenticated with remote 3A. Generally, there is no need to configure the user name locally, because the command line authorization is also implemented through HwTACacs, and there is no need for local authorization.


4. Check the configuration under VTY and find that command authorization does exist:

line vty 0 4

 authentication-mode scheme

 user-role network-operator

 command authorization

 command accounting


Combined with point 2, command line authorization is the default mode, namely local authorization, because the local user name does not exist, so the command line authorization cannot be completed, resulting in the failure of command line authorization.


Solution

Since the RADIUS server is used as the 3A authentication server, it is not recommended to configure command line authorization; simply delete command line authorization.Of course, the on-site problem could be to add a user name to the device and reconfigure the user name with a role that would make command line authorization safe, but that would be unnecessary.


0 comments

No comments

Add Comments:

举报

×

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

侵犯我的权益

×

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

泄露了我的隐私

×

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

侵犯了我企业的权益

×

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

抄袭了我的内容

×

原文链接或出处

诽谤我

×

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

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

×

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

不规范转载

×

举报说明

提出建议

    +
<

亲~登录后才可以操作哦!

确定

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