Import from
Device List Window


Use the Import from Device List window to import your network devices into the Policy Manager application. Initially, you must import your network devices into Policy Manager before you can configure and enforce policies. Later, you can use this window to import new devices or update device data. You can access the Import from Device List window by selecting File > Import > From Device List.

  TIP: You can also open the Import from Device List window directly from the Getting Started Wizard (Help > Getting Started). From the left panel of the wizard, expand the Basic Tasks folder and select Import Devices.

A Device List is a text file that lists your network devices and (optionally) their SNMP access information. You can create a Device List using a text editor. See How to Create and Import Device Lists for more information.
NOTES: There are special utility programs available that will create a device list for you based on your HP OpenView®, NetSight Switch and Topology Manager, or NetSight Element Manager device database. Contact Support for more information.

If you import a device list from an older version of Policy Manager where the "Contain to VLAN" and "Deny Traffic" choices were not available, the VLANs Selection View appears, where you can select the VLANs you want to act as Discard VLANs.

When you import a device, Policy Manager determines whether or not authentication is enabled on the device. If yes, the appropriate Authentication Type is displayed in the device's Authentication tab, with the Authentication Status set to Enabled.  If authentication is not enabled on the device, Policy Manager displays the previous Authentication Type/ Authentication Status setting for the device if there was one, or Authentication Type: Web-Based and Authentication Status: Disabled, if not.

The Policy Manager Small Business Edition allows a maximum of 10 devices. If your device list exceeds the maximum number of devices allowed, one or more of the devices will not be imported.

Click the graphic for more information.

Import From Device List

Source of Device Data

File name
Enter the name and path to the file (Device List) you want to import. Or use the Browse button to navigate to the file. See How to Create and Import Device Lists for more information.
Browse
Click Browse to navigate to the file (Device List) you want to import.
Destination Device Group
To import the device(s) into an existing device group, select the device group from the drop-down list. The imported device(s) will appear in the selected device group, and also in the Devices folder. Devices in the device list that already exist in the Devices folder will still be imported into the device group.

Format of Device Data
The device list can be in the following formats. Select the format that applies to the device list you are importing.
TIP: If you create a device list without community names, devices will be imported into Policy Manager using the list of community names in the Community Names window. If you populate the Community Names window with valid community names before doing the import, you won't have to specify community names for each entry in the device list.

NetSight Generated Format
SNMPv1 devices and SNMPv3 devices use different NetSight Generated device list formats. The formats include the device name or IP address, and the device's SNMP access information. This information is used by Policy Manager to access and manage the device. You can mix SNMPv1 and SNMPv3 formats in a single device list. If you list both an SNMPv1 and SNMPv3 entry for a device, Policy Manager stores the v1 values, but uses the v3 values to contact the device.
 
SNMPv1 Devices:
SNMPv1 access information consists of the read only, read write, and super user community names for the device. The device name or IP address is the only required information. The string of information for each device must be on a separate line with no line breaks in the string. If you create a device list without community names, devices will be imported into Policy Manager using the list of community names in the Community Names window. If no community name exists for a device in the Community Name list, you will be given the opportunity to add a community name for the device before importing.
 
dev=[device name or IP address] ro=[Read Only Community Name] rw=[Read Write Community Name]
su=[Super User Community Name]


Example:
dev=Switch1 ro=public rw=public su=public
dev=10.20.30.40 ro=public rw=public
su=public

NOTE: For RoamAbout R2 devices. If you are importing the device with SNMPv1 (SNMPv3 is recommended), the default community names on the device must be updated. There are four SNMPv1 community names on the R2:
  • Community #1 -- allows limited read-only access (MIB II system group)
  • Community #2 -- allows creation of new views
  • Community #3 -- allows read-only access to all MIBs
  • Community #4 -- allows read/write access to all MIBs
Policy Manager will import the device based on community names #3 and #4. For read-only access, set community name #3 on the device and then use that community name for the "ro" value in the device list. For read/write and super user access, set community name #4 on the device, and then use that community name for the "rw" and "su" values in the device list.
SNMPv3 Devices:
SNMPv3 access information consists of certain SNMPv3 USM (User-based Security Model) settings. The device name or IP address and the user name is the only required information. Each device must be on a separate line. For more information on SNMPv3, read RFC2574.
 
dev=[device name or IP address] user=[User Name] authtype=[Authorization Type] authpwd=[Authorization Password] privtype=[Privacy Type] privpwd=[Privacy Password] seclevel=[Security Level]

Example:
dev=Switch1 user=name
dev=Switch2 user=name authtype=MD5 authpwd=password seclevel=AuthNoPriv
dev=10.20.30.40 user=name authtype=MD5 authpwd=password privtype=DES privpwd=password seclevel=AuthPriv

SNMPv3 USM Settings:
IP Only Format
A list of device IP addresses using the following format:
[IP address]
Each device must be on a separate line. For example:
10.20.30.40
10.20.30.50
10.20.30.60


If you create a device list without community names, devices will be imported into Policy Manager using the list of community names in the Community Names window. If no community name exists for a device in the Community Name list, you will be given the opportunity to add a community name for the device before importing.
Application of Imported Device Data
Use these options to determine how the imported data will be added to your existing .pmd file. You can see "tool tips" for these options by positioning your mouse pointer over the text labels.
Append devices from file to existing device data
Select this option to add devices that don't currently exist in your Policy Manager database. Existing devices will not be modified.
Update existing data with data from file 
Select this option to update the SNMP access information for your existing Policy Manager devices and import any devices that are not already in the current .pmd file.
NOTE: If you import a Read Only community name that is different from the Read Only name currently being used for the device, and the new community name does not match any of the community names that are configured on the device, Policy Manager will revert to using the original Read Only community name. If the Read Write or Super User community names are different, they are not checked against the device and the new values from the file will always be used.
Overwrite existing device data
Select this option to replace your existing Policy Manager devices with devices from the device list.

Top


Related Information

For information on related tasks: For information on related windows: Top