I P - D S U U s e r ’ s M a n u a l
02/02/08
21
<IP ADDRESS> [<TCP PORT>] [-P<Password>] # Comment
An example “device.master” file follows:
# This is a Sample master device list file “device.master”.
# Note that there is one device ( Connect IP Address ) per line.
# TCP Port Override is allowed. Registration may use the serial console.
# Password Override is allowed.
# It is OK to have devices that do not need registration listed for inventory.
# Comments in this file are preceded with a pound symbol.
# Blank Lines are treated as comments.
# Basic Line Format is as follows:
10.0.1.80 # Device at Location ‘A’
192.168.7.82 # Device at Location ‘B’
192.168.7.155 50001 # Example of TCP port Override.
192.168.7.156 50001 –pcustom1 # Example of Password Override.
Once the “dt_device.master” file is prepared, it is used as an input to the
getinfo
utility.
getinfo dt_device.master
This
getinfo
utility will collect information on each device in the master file. The
getinfo
utility will also make a determination if a registration is actually required. Consequently,
the
getinfo
utility is also useful in performing inventory functions outside of the device
registration. The output of the
getinfo
utility is a file named “dt_device.info” that is
always created in the current directory.
The file “dt_device.info” is attached to an email and sent to the address
.
The registration procedure is performed and a file named
“dt_device.register” is attached to return email to the original sender. A messages file
named “dt_device.msgs” is also attached and may be printed as a report of the key
generation function.
After receiving the “dt_device.register” file, the
setreg
utility is invoked with the relative
path of the “dt_device.register” file as it’s sole argument. The
setreg
utility will only
