|
The first new data that needs to be upgraded is the usmUserTable. This is done on the USM sub-tab page of the Security page. Entering a new row is done by pressing the "New" button on that page. That will allow you to enter the name of the new user in the usmUserName field.

At this point it is good to know what your system administrator’s policy is for network configuration of EngineID’s. It is possible to use a unique engineID for each user. If this is your network’s policy then you need to get your unique engineID from your system administrator, which can be entered after making sure the "Enter my own EngineID" radio button is selected. In the event that it is your network policy for each agent to have one EngineID then selecting the "Use Local EngineID" radio button will bring up the EngineID which was established for this agent. If no EngineID has been established you will have to go back to the "Agent Page" to setup the ID to be used locally.
The security passwords now need to be set. For the purposes of this example we will use passwords which are not very secure. Please consult your network manager for more secure passwords. What levels of authorization and privacy are used in your network are, again network policies to be acquired from your system administrator.
For authorization you have the options of using no authorization or of using one of the MD5 or SHA authorization protocols. The two active protocols will be decided on by your system administrator and you must follow his lead or you will have no communications.
Privacy encoding has only one option other than not doing it at all. It is refered to as DES encryption.
In addition to setting up the user in the usmUserTable it is necessary to also include a mapping of what branches of the MIB that the agent impliments are available for specific access, namely "Read", "Write" and "notify". This procedure is outlined in the help topic Configuring Views.