Users Guide

Specifying IPs, Ranges, or Host names Using XML or CSV

Files

You must specify ranges during discovery, inventory, and status tasks. A range in this instance is defined

either as an individual IP address, a host name, or an actual range of IPs such as 192.168.7.1-50 or

10.35.0.*. Add ranges, IPs, or host names either to an xml or csv-based input file and then read the file by

specifying it on the command line using the

–RangeList or –RangeListCSV argument. A sample XML

file (RangeList.xml) and CSV file (RangeList.csv) are included in the samples folder at C:\Program Files\Dell

\SysMgt\Essentials\Tools\CLI\Samples. To create multiple input files, edit and rename either the xml or

csv file.

NOTE: If you are creating discovery range groups, then each group can only have one

corresponding subnet. The subnet for a group is read from the DiscoveryProfile.xml file and not

from the RangeList.xml or RangeList.csv file. If required, you can create multiple groups for each

subnet.

An example of theRangeList.xml file is outlined as follows:

<?xml version="1.0" encoding="utf-8" ?>

</DiscoveryConfigurationRanges>

An example of the RangeList.csv is outlined as follows:

Name SubnetMask

192.168.10.* 255.255.255.0

192.168.10.1-255 255.255.255.0

192.168.1-2.* 255.255.255.0

10.35.*.1-2 255.255.255.0

192.168.2.1 255.255.224.0

192.168.2.2 255.255.254.0

192.168.3.3 255.255.128.0

192.168.3.4 255.255.128.0

Specifying Input Files in PowerShell

To use input files in PowerShell, specify the location of the file in the command line. By default,

OpenManage Essentials CLI starts at the following directory:

PS C:\Program Files\Dell\SysMgt\Essentials\Tools\CLI>

If you are running commands from the default CLI directory, with commands located in the directory one

level from it (\samples), you can use either of the following methods of specifying the path to the input

files:

• Type the entire path name in quotes. For example, Add-DiscoveryRange –Profile “C:

\Program Files\Dell\SysMgt\Essentials\Tools\CLI\Samples\DiscoveryProfile.xml”.

397