Generate an authentication key and a privacy key.
-
Log in to an NFM-P single-user client, client delegate server, or main server station.
Note:
If you log in to a RHEL main or client delegate server station, you must log in as the nsp user.
If you log in to a single-user client station, you must log in as the user who installed the client, or as a local administrator.
-
Open a console window.
-
On a RHEL station, navigate to the install_directory/nms/bin directory, where install_directory is one of the following:
-
the NFM-P main server installation location, /opt/nsp/nfmp/server
-
the NFM-P single-user client or client delegate server installation location, typically /opt/nsp/client
-
On a Windows station, navigate to the install_directory\nms\bin directory, where install_directory is the NFM-P single-user client or client delegate server installation location, typically C:\nsp\client.
-
Enter one of the following to create an authentication key:
./nmsclient.bash password2key method password engine_ID ↵
nmsclient.bat password2key method password engine_ID ↵
where
method is the authentication method, either MD5, SHA, SHA224, SHA256, SHA384 or SHA512
password is the authentication key password
engine_ID is the SNMP engine ID obtained in
Step 2
Note: You must enclose a password that contains a special character in single quotation marks; for example:
password2key method 'Mypa$$word'
Only use the authentication key from the output.
-
Enter the following to create a privacy key.
./nmsclient.bash password2key method password engine_ID ↵
nmsclient.bat password2key method password engine_ID ↵
where
method is the authentication method, either MD5, SHA, SHA224, SHA256, SHA384 or SHA512
password is the privacy key password
engine_ID is the SNMP Engine ID of the SR, in hexadecimal form with 10-64 hex digits (5-32 bytes)
Note: You must enclose a password that contains a special character in single quotation marks; for example:
password2key method 'Mypa$$word'
The list of privacy keys for each privacy method is displayed.
-
Store the generated keys for your applicable authentication and privacy methods.