Why does authentication fail when you log in to the web NMS for S series switches

4

The possible causes of authentication failures when you log in to the web NMS on an S series switch (except the S1700) are as follows:
1. The user name or password is incorrect.
Run the display local-user command to check whether the user exists.
Run the display local-user username user-name command to check whether the user password is correct.
2. There is no HTTP user access type.
Run the display local-user username user-name command to check whether the AuthMask field of the user contains H (HTTP login).
3. The user connected to the switch is full. The switch supports a maximum of five users.

Other related questions:
When authorization is not required, why the HWTACACS authentication of S series switches fails
When configuring the HWTACACS server template on an S series switch (except the S1700 switch), specify an authorization server even if authorization is not required. If not, the HWTACACS authentication will fail.

Why does the authentication fail during the web platform login
Authentication failed during the web platform login. The possible causes are: 1. The user name or password is incorrect. - Run the display local-user command to verify that the user exists. - Verify that the password is correct. 2. There is no HTTP user access type. Run the display local-user username user-name command to check whether the Service-type-mask field of the user contains H (indicating HTTP login). 3. The number of login users reaches the upper limit.

Why does the NMS display an error message when it uses SNMPv2c to connect to an S series switch
When an NMS uses SNMPv2c to connect to an S series switch (except the S1700), error message "another nms was polling the switch with wrong community" is displayed. The reason is that the community name configured on the NMS is different from that configured on the switch. Run the display snmp-agent community command on the switch to check the configured community name.

Prevent users failing RADIUS authentication from logging in to S series switches
Administrative users can log in to S series switches (except S1700 switches) after they pass the RADIUS authentication. Their user accounts are configured on the remote RADIUS server but not in the AAA view of a local switch. The methods of configuring switches to allow administrative users to log in after they pass the RADIUS authentication are similar.

Why is the time in a log on CE series switches inconsistent with that on the NMS
Logs sent to the NMS use the standard UTC time. Therefore, the log time displayed on the NMS has no time zone. If the time zone is configured on the device, the log time displayed on the device will differ from that displayed on the NMS.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top