Beginning with NMC2 firmware v6.0.6, user configuration/modification is no longer supported or available via the config.ini. This functionality can now be accomplished via a .csf file which can be uploaded to the NMC2 via FTP or SCP. INIUtil-v3, available in knowledge base FA156117 for uploading/download config.ini files in bulk, will now support uploading .csf files (since they cannot be downloaded). Alternatively, a user can write a script to create users via the CLI (which is accessible via the local serial console, Telnet, or SSH).

Resolution

The user can use a .csf configuration file to be uploaded to the NMC2 via FTP or SCP. Alternatively, these instructions can be used by the user to create a script which can be used with the NMC2 via local serial console, telnet, or SSH.

To begin, the NMC2 offers a "default settings" configuration (which is availablein the config.ini as well as all of the other NMC2 interfaces - review knowledge base FA175982 for a known issue) which can serve as a template for adding users. If many of your users will have the same preferences (which are now configurable on a per user basis), you can modify these settings first so that your .csf file requires less data. You can also still configure preferences individually via the .csf file.

So, to begin, if you want to configure the Default User Settings that will apply to most, if not all, of your local users, begin with that. You can do this in the web interface in the Configuration Menu->Security->Local Users->Default settings. See below.

If the web interface is not an option, you can also configure this via the CLI using the userdflt command.

Once these settings have been modified or you've chosen to skip it, you'll need to create your .csf file if you're not scripting this. This must be a plain text file which has been modified to a .csf file extension. (Make sure that your system is set to show file extensions to avoid a filename such as userupload.csf.txt.)

You'll use the syntax of the usercommand to create your .csf user configuration file. The syntax is shown below. This would be the syntax you follow if you're creating your own script.

Note: There is a bug in AOS 6.0.6 in which the Read-Only or Device user type will not work via the user command. This type of user must be added via the web interface for v6.0.6. This is corrected in v6.1.3 AOS or higher. (Each Network Management Card has an AOS and application file and they cannot be updated independently. Please check http://www.apc.com/tools/download/index.cfm to verify the latest versions available for your device.)

Once your file is complete, save it as <anyname>.csf and you'll be able to upload it to your NMC2 via one of the specified methods. To confirm your changes were accepted, you can display the current user list by issuing the command user -l via CLI or checking the web interface under Configuration->Security->Local Users->Management to view your system's local users. Please note, there is no way to export this list to a file unless you do it manually or script it.

Still not working or do you have questions?

If you need further assistance or your .csf file is not working, please contact APC technical support and be prepared to provide the following information:

Your .csf file with any personal information removed, if required

Firmware version

Event.txt (and config.ini if pertaining to default user settings) - instructions to retrieve these are in knowledge base FA156131.