OSN3500 device network element user name and password are entered incorrectly 5 times in a row, prompting NSERR_SM_ACCOUNTS_DISABLED,error code 0x9119

Phenomenon Description

A customer is performing on-site maintenance on OSN3500 equipment, logging in to the equipment from the command line, and logging in to the network element using the " szhw " user, the login to the network element does not work, and the error message for the command line login is as follows : " failed! cmd:0x2022 error:0x9119NSERR_SM_ACCOUNTS_DISABLED ", the customer has done a hard reset operation on the main control board, and the fault phenomenon still exists; the central computer room uses the U2000 network management to log on to the network element, and the network management logs on normally; the operation of the network element operates normally.

Cause analysis

NGSDH equipment, network element login, if the user name and password are entered incorrectly five times in a row, it will cause the network element user to be locked, and when logging in, it will prompt " NSERR_SM_ACCOUNTS_DISABLED ", and the network element can not be logged in.

After 5 consecutive errors, the network element is locked, and the default lockout time is 900 seconds ( 15 minutes).

After a network element user is locked, if you hard reset the single board, then the network element user will be unlocked.

Operation Procedure

According to the phenomenon described by the customer, the root cause of not being able to log in to the network element from the command line has been found. The user " szhw " has been locked out due to five consecutive wrong password inputs. The user " szhw " has been locked out of the network element due to five consecutive incorrect password entries, resulting in the command line login prompting " NSERR_SM_ACCOUNTS_DISABLED "; however, the customer indicated that he has reset the hard master board, why the command line still can not login to the network element;

When a network element user logs on to a network element, NGSDH products will have a log of the time and operation IP of the network element logged on, so query the log of the network element logged on to confirm;

A large number of szhw user login failure logs are found, indicating that other network administrators or terminals are continuously logging into the network element and using wrong szhw user passwords to log in; use to check the logging status.

Querying the logon details, we found that a network administrator with IP address 10.34.8.110 is repeatedly logging on the network element. After confirming the logon details, we found the reason: the network administrator has started the DC tool in the background, and the DC tool uses the szhw user to log on to the network element, and the user has changed the password of the shzw user on the command line, and the DC tool on the network administrator has changed the password of the shzw user on the command line. The user had previously changed the password of the " shzw " user using the command line, and the DC tool on the network administrator used the default " nesoft " password to log in to the network element, causing the " szhw " user to be locked out.

After changing the password of the szhw user in the DC tool on the T2000V2R7C03 network administrator, the login of the " szhw " user returns to normal.

Recommendation Summary

Common commands for troubleshooting network element user login:

:sm-get-secucfg // Query the default settings of network element users;

:sm-get-seculog // Query the network element user login log;

:sm-get-secrlog-new //query the detailed log of network element user login;

:sm-edit-lockduration:// Set network element user lock duration;

:log-query:bid, "oplog" //query network element operation log.