Page tree
Skip to end of metadata
Go to start of metadata

SNMP tests all discovered hosts for system SNMP responsiveness. The system uses a master SNMP credentials list that indicates whether SNMPv2c Common Credentials or SNMPv3 credentials should be used during discovery, what authentication (SHA, MD5, none) and privacy type (AES, AES256,DES, none) to use for each. The order that you input the SNMP aliases becomes their priority order.

This procedure assumes that you have already created an Organization, Zone, and one or more Collectors. It also assumes that you've populated your Zone Network and Discovery Space lists. If you haven't completed these preliminaries or need more information on them, refer to . . .

  1. Creating & Managing Organizations - Creating a container for all of your organization's zones
  2. Adding & Managing Zones - Defining an area of the network to discover and index.
    1. Set Zone Networks & About Lists  - Using the Known, Eligible, and Internal list buttons to identify the IPs and CIDRs composing your defined zone.
  3. Adding & Managing Collectors - Adding the collectors.
    1. Scope: Discovery Spaces - Telling your collector where in the network to do its job
    2. Adding & Managing Lists (Zone Networks & Discovery Spaces)

Configuring SNMP

To configure SNMP Discovery:

  1. In the Lumeta Command Center GUI, browse to Settings > Zones.
  2. Select the zone and collector in which you want to configure Host Discovery.  
  3. Select the SNMP tab, click Edit, and update the form.
  4. Click Update.
  5. Set SNMP Credentials by clicking Credentials > Add, updating the form, and then clicking Create.

    The SNMP configuration is complete. Discovery cycles initiate with these settings.

A Sample Configuration

This is a typical SNMP configuration, reasonable for most organizations.

  1. Select the options below and click Update:
    1. Enable SNMP Discovery
    2. Common SNMPv2 credentials
    3. Collect interface data
    4. Collect layer 2 data
    5. Collect routes
    6. In Maximum route table size, input 5,000.
    7. Skip BGP routes

  2. Select the Credentials tab on the right-hand side of the page and add credentials as necessary.

    1. For an SNMP v2c-type credential, supply . . .

      1. A community string such as “public”

      2. Use community string for alias

      3. An alias such as “aliasforpublic”

    2. For an SNMP v3-type credential, supply an. . .

      1. Alias such as “encrypteduser”

      2. Username such as “person123”

      3. Context, which is the name a management application should use to access network devices. Completing this field is optional.

      4. Authentication type, such as SHA, MD5, or none

      5. If you selected an authentication type of SHA or MD5,also select AES, AES256, or DES as the privacy type.

      6. Skip BGP routes.

Next Steps

  1. Assess and validate what's returned by reviewing reports.
  2. Analyze any newly discovered networks as well as known networks that could not be reached.
  3. Adjust the configuration based on your findings, reaching out to your technical consultant if you need assistance adjusting the discovery settings to achieve the visibility you seek.
  • No labels