Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Operations Management
Table of Contents
Choose your release version
    Home Orlando IT Operations Management IT Operations Management ITOM Visibility Discovery Discovery configuration SNMP support for Discovery

    SNMP support for Discovery

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    SNMP support for Discovery

    Discovery supports SNMP versions 1, 2c, and 3. Discovery uses version 1 and 2c by default. You must enable support for version 3.

    MID Servers support all SNMP protocol versions by default. You can set a MID Server to support only specific versions of SNMP.

    Add an SNMPv3 user credential in Discovery

    Set up your credentials so Discovery can access SNMPv3 targets.

    Before you begin

    Role required: admin

    About this task

    A MID Server parameter is also available to control SNMP versions. See MID Server parameters.

    Procedure

    1. Navigate to Discovery > Credentials.
    2. Click New.
    3. Click SNMPv3 Credentials.
    4. Fill in the form, using the fields in the table.
      Figure 1. SNMPv3 credentials form
      SNMPv3 credentials form
      Table 1. SNMPv3 credential fields
      Field Input value
      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:
      • 3DES
      • AES128
      • AES192
      • AES256
      • DES
      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.
      Table 2. SNMPv3 security options
      Option Fields to configure
      noAuthNoPriv security
      • Authentication protocol: None
      • Privacy protocol: None
      • Authentication Key: Leave blank
      • Privacy Key: Leave blank
      authNoPriv security
      • Authentication protocol: Set
      • Privacy protocol: Leave blank
      • Authentication Key: Set
      • Privacy Key: Leave blank
      authPriv
      • Authentication protocol: Set
      • Privacy protocol: Set
      • Authentication Key: Set
      • Privacy Key: Set

    Set SNMP version on the Discovery schedule

    You must also add an SNMPv3 credential if you set the SNMP version to v3 or All.

    Before you begin

    Role required: admin

    About this task

    A MID Server parameter is also available to control SNMP versions. See MID Server parameters.

    Procedure

    1. Navigate to Discovery > Discovery schedules> your Discovery schedule.
    2. In the Use SNMP Version field, select the appropriate version.
      Valid options are v1/v2c, v3, or All.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      SNMP support for Discovery

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      SNMP support for Discovery

      Discovery supports SNMP versions 1, 2c, and 3. Discovery uses version 1 and 2c by default. You must enable support for version 3.

      MID Servers support all SNMP protocol versions by default. You can set a MID Server to support only specific versions of SNMP.

      Add an SNMPv3 user credential in Discovery

      Set up your credentials so Discovery can access SNMPv3 targets.

      Before you begin

      Role required: admin

      About this task

      A MID Server parameter is also available to control SNMP versions. See MID Server parameters.

      Procedure

      1. Navigate to Discovery > Credentials.
      2. Click New.
      3. Click SNMPv3 Credentials.
      4. Fill in the form, using the fields in the table.
        Figure 1. SNMPv3 credentials form
        SNMPv3 credentials form
        Table 1. SNMPv3 credential fields
        Field Input value
        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:
        • 3DES
        • AES128
        • AES192
        • AES256
        • DES
        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.
        Table 2. SNMPv3 security options
        Option Fields to configure
        noAuthNoPriv security
        • Authentication protocol: None
        • Privacy protocol: None
        • Authentication Key: Leave blank
        • Privacy Key: Leave blank
        authNoPriv security
        • Authentication protocol: Set
        • Privacy protocol: Leave blank
        • Authentication Key: Set
        • Privacy Key: Leave blank
        authPriv
        • Authentication protocol: Set
        • Privacy protocol: Set
        • Authentication Key: Set
        • Privacy Key: Set

      Set SNMP version on the Discovery schedule

      You must also add an SNMPv3 credential if you set the SNMP version to v3 or All.

      Before you begin

      Role required: admin

      About this task

      A MID Server parameter is also available to control SNMP versions. See MID Server parameters.

      Procedure

      1. Navigate to Discovery > Discovery schedules> your Discovery schedule.
      2. In the Use SNMP Version field, select the appropriate version.
        Valid options are v1/v2c, v3, or All.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login