Archived - How do I define a device file (seed file)? – Entuity

This article has been superseded by Entuity v19.0. Note, importing devices via a device file (seed file) has been replaced by the Discovery Scope functionality in Entuity v19.0. Please see this article to view the latest information on this topic.

To import SNMPv1/v2 device files

To import SNMPv2c device files only

To import SNMPv3 device files

You must define a device file (also known as a seed file) before using it to import devices for management.

Before using the device file, you must check that:

each device responds to ICMP Echo requests.
devices you want to manage at Full or Basic management levels allow SNMP requests from the server with the provided SNMP credentials.
there is no IP address or port management access list in operation for the devices that would prevent SNMP or ICMP replies from the devices to the Entuity server.

To import SNMPv1/v2 device files:

For SNMPv1/v2 devices, the format is:

<deviceIdentifier> <community string> <#optional comment>

You can also specify a SNMPv1/2 device using the alternative format:

-d <deviceIdentifier> -c <community string> <#optional comment>

where:

deviceIdentifier	the IP address or hostname that resolves to the management address. You can resolve each device name into an IP address on the Entuity server using one of the following methods: Static hosts file (e.g. \etc\hosts). NIS (Network Information System) or NIS+. DNS (Domain Name System). This resolution is not required if the device identifier is itself the IP address of the device. The choice of identifier is important, because it is the primary method of identifying devices in ENA.
Community String	the read-only SNMP (Simple Network Management Protocol) community string required to read the MIB-II (Management Information Base-II) system group for the device, e.g. public.
Optional Comment	a non-mandatory text string to help describe the device.

To import SNMPv2c device files only:

By default, if the SNMP version is omitted, the devices will be managed using a combination of SNMPv1 and SNMPv2c. If you would prefer to use SNMPv2c exclusively, you can add the -v 2c- option into each line of the seed file like so:

-d <deviceIdentifier> -v 2c -c READ_ONLY COMMUNITY

To import SNMPv3 device files:

For SNMPv3 devices, the format is:

-d <deviceIdentifier> -u <UserName> -a MD5 -A <Auth passwd> -x DES -X <Privacy passwd>

where:

-d	indicates the following value is the device name.
deviceIdentifier	the IP address or hostname that resolves to the IP address of the management interface on switches, and a single interface on a router. You can resolve each device name into an IP address on the Entuity server using one of the following methods: Static hosts file (e.g. \etc\hosts). NIS (Network Information System) or NIS+. DNS (Domain Name System). This resolution is not required if the device identifier is itself the IP address of the device.
-u <UserName>	requires a valid username to access the device.
-a <Auth protocol>	sets the authentication protocol. Valid values are: MD5 (Message-Digest algorithm 5), SHA (Secure Hash Algorithm).
-A <Auth password>	sets the authentication password. Valid values must be between 8 and 32 characters long. If the password contains spaces, double quotes must be placed around the password.
-x DES <Priv Protocol>	sets the privacy protocol. Valid values are DES (Data Encryption Standard), AES, 3DES, AES192, AES256.
-X <Privacy password>	sets the privacy password. Valid values must be between 8 and 32 characters long. If the password contains spaces, double quotes must be placed around the password.

Although 3DES, AES192 and AES256 are widely implemented encryption algorithms, they are not included to the SNMP standard. Therefore, a particular manufacturer's implementation of one or more of these technologies may not be supported by ENA.

To import SNMPv1/v2 device files:

To import SNMPv2c device files only:

To import SNMPv3 device files:

Related articles