Name |
Unique and descriptive name for this credential. For example, you might call
it SNMP Community Atlanta. |
Active |
Enable or disable these credentials for use. |
Applies to |
Select whether to apply these credentials to All MID
servers in your network, or to one or more Specific MID
servers. Specify the MID Servers that should use these credentials
in the MID servers field. |
MID servers |
Select one or more MID Servers from the list of available MID Servers. The
credentials configured in this record are available to the MID Servers in this
list. This field is available only when you select Specific MID
servers from the Applies to field. |
Order |
Order (sequence) in which Discovery tries this
credential as it attempts to log on to devices. The smaller the number, the higher in the
list this credential appears. Establish credential order when using large numbers of
credentials or when security locks out users after three failed login attempts. If all the
credentials have the same order number (or none), the instance tries the credentials in a
random order.
|
User name |
Enter the SNMP user name. Avoid leading or trailing spaces in user names. A
warning appears if the platform detects leading or trailing spaces in the user
name. |
Authentication protocol |
Select the authentication type to use for this credential. The choices are
MD5 and SHA. |
Authentication Key |
Enter the authentication key to use for this credential. |
Privacy protocol |
Select the encryption protocol for this credential. The choices are: |
Privacy key |
Enter the key associated with the selected privacy protocol. |
Credential ID |
Enter the unique key configured for external credentials in the JAR file
uploaded to the MID Server for an external credential provider. The
Credential ID field has a limit of 40 characters. This
field is only visible when the External credential store
check box is selected. |
Privacy Credential ID |
Enter the privacy account key configured for SNMPv3 credentials in CyberArk.
If you are using a privacy protocol in CyberArk, this field must have the same
value as the Name field for the CyberArk SNMPv3 Privacy
Account. This field is only visible for SNMPv3 when you select
CyberArk from the Credential Store
Type field. If you are not using a privacy key for CyberArk, leave
this field empty. |
Credential alias |
Allow workflow creators to assign individual credentials to any activity in
an Orchestration workflow or assign different credentials to each occurrence of
the same activity type in an Orchestration workflow. |
External credential store |
Select this check box to use an external credential storage system. When
external storage is enabled, the Credential ID field
appears. External credential storage is only available when the External Credential Storage plugin is activated and the
External Storage view is selected. |
Credential Store Type |
Select the external storage provider. Select CyberArk
only if you are using a CyberArk SNMPv3 privacy key. The Privacy
Credential ID field appears to allow entry of the key. |
Use Context |
Select this check box to add a context value for this credential. This field
is visible in the Discovery view. Contexts are not
currently supported for external credential storage.Note: A context is a
collection of management information accessed by an SNMPv3 credential that
references a specific OID. Contexts are sometimes referenced to collect
information about the device that cannot be accessed by the normal credential. A
context can be provided by the manufacturer or configured separately. For
additional information, see Context Name and Context ID.
Note: If you have multiple SNMPv3 credentials with the same user name and
keys, but some of your devices need a context and some do not, then you will
need to create separate records for each device. |
Context Name |
Enter the context name value for this credential. This should only be used if
you have devices that require this value for full access. This field is visible
when the Use Context check box is selected. |