Huawei Router Telnet Login Failure Causes

H12-811 By islever Editorial Last updated

Network Troubleshooting AAA Principles and Configuration

Short answer

BCD The cause is the administrator account being deleted, having user level 0, or being disabled, as these affect only the specific user while Telnet remains active for others.

Question

An administrator cannot log in to a Huawei router through Telnet, but other administrators can log in to the router. Which of the following are possible causes? (Choose all that apply.)
  1. The Telnet service has been disabled on the AR2200 router.
  2. The administrator account has been deleted. Correct Answer
  3. The user level of the administrator account has been changed to 0. Correct Answer
  4. The administrator account has been disabled. Correct Answer

Key Takeaways

The trap is confusing global service failures (Telnet disabled) with user-specific authentication failures (account status/level).

Identify why a single Huawei administrator cannot log in via Telnet while others succeed. The correct causes involve account deletion, Level 0 restrictions, or account disabling.

Common mistake: Selecting A because it seems like a security setting, but it would block all users, contradicting the 'others can log in' premise.

Expert Analysis

The scenario specifies that only one administrator cannot log in via Telnet, while others can. This isolates the issue to the specific user account or its configuration, rather than a global service failure.

A. The Telnet service has been disabled on the AR2200 router. This is incorrect. If the global Telnet service were disabled, no administrators would be able to log in. Since others are successful, the service is active.

B. The administrator account has been deleted. This is correct. If the specific user account is removed from the local AAA database, authentication will fail for that user exclusively.

C. The user level of the administrator account has been changed to 0. This is correct. In Huawei VRP, User Level 0 is designated for network monitoring and diagnostic commands (like ping) but does not permit interactive login or command execution at higher levels. A user with Level 0 privileges effectively cannot log in to manage the device.

D. The administrator account has been disabled. This is correct. An explicitly disabled account prevents authentication regardless of other settings.

Exam Strategy

When troubleshooting access issues, always check if the problem is global or local. If multiple users are affected, look at global services (like Telnet/SSH status). If only one user is affected, investigate their specific account attributes (existence, password, enabled state, and privilege level).

Frequently Asked Questions

Why does User Level 0 prevent Telnet login?

In Huawei VRP, User Level 0 is restricted to diagnostic commands and does not allow interactive login or configuration access.

Can I still use Ping if my account is Level 0?

Yes, Level 0 users typically have permission to run simple diagnostic tools like ping and tracert, but cannot log in to manage the device.

More H12-811 FAQ →

Community Votes

D
42%
B
33%
C
17%
A
8%

42% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 7 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 7

  1. 4c4da48 👍 1
    A. The Telnet service has been disabled on the AR2200 router. This is not a possible cause in this specific scenario, as if the Telnet service is disabled, no administrator would be able to log in. B. The administrator account has been deleted. This is a possible cause. If the specific administrator's account has been deleted, that user will not be able to log in. C. The user level of the administrator account has been changed to 0. This is also a possible cause, as a user level of 0 typically means no permissions, preventing access. D. The administrator account has been disabled. This is a possible cause as well. If the account is disabled, the administrator would not be able to log in. In summary, the correct possible causes for the specific administrator not being able to log in via Telnet while others can would be B, C, and D. Thank you for your understanding, and I appreciate your feedback!
  2. andrpercud 👍 1
    Possible Causes The administrator account has been deleted. If the specific account is deleted, that administrator cannot log in. The administrator account has been disabled. If the account is disabled, the administrator will not be able to log in. Not a Possible Cause The user level of the administrator account has been changed to 0. The account can still log in, but the user would have very limited permissions. The Telnet service has been disabled. This would affect all users, not just the specific administrator.
  3. Fmoura17 👍 1
    Answer: B, C, and D B. Account deleted ✅ — If the account no longer exists, that specific admin cannot log in. C. User level changed to 0 ✅ — Level 0 has no login privileges, so the admin cannot access the router via Telnet. D. Account disabled ✅ — A disabled account cannot authenticate, blocking that specific admin. A. ❌ — If Telnet was completely disabled on the router, no one could log in via Telnet. Since other admins can log in, the Telnet service is clearly still running.
  4. IBB90704 👍 1
    La respuesta es la B y D
  5. TIConstecoin 👍 1
    BD correct
Show 2 more comments
  1. hafizhou 👍 1
    AD correct
  2. Chleong 👍 1
    Bbb Ddd

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

← Back to H12-811 Study Guide