Cisco Cisco Prime Network Registrar 8.1 Technical References
ImportAggregateBlock
Cisco Prime Network Registrar IPAM 8.1.1 CLI and API Guide
9
File Format
Col
Field
Accepted Values
Required
A
Container
The name of the container into which to insert the new
aggregate block. Names can be in either short or long
format. Short format example: Dallas. Long format
example: Cisco Prime Network Registrar
IPAM/Texas/Dallas.
Long format eliminates ambiguity in cases where there
are duplicate container names.
Yes
B
Start Address
The start address of the new aggregate block.
Yes
C
Block Size
The size of the block in short-notation (e.g., 24 for a
255.255.255.0 network).
Yes
D
Block Type
The Block Type for the block If not specified, a block
type of Any is assumed.
No
E
Block Name
A name for the block. Defaults to system
supplied name of Address space/Block size.
No
F
Description
A description of the block.
No
G
SWIP Name
SWIP name for the block.
Yes, if
required by
container
rules
H
Allocation Reason
The name of a pre-existing Allocation Reason.
No
I
Allocation Reason
Description
A description of the reason for the allocation. Wrap
the statement in “quotes” if it contains any commas.
No
J
Interface Name
If this block is being added to a device container, the
name of the interface to attach the block to.
Yes, if block is
being added
to device
container.
Otherwise,
no.
K
Interface Offset or
Address
The specific address, or offset from the beginning, for
the interface IP address. If an IP address is specified, it
should be in the form xxx.xxx.xxx.xxx. If an integer is
specified, it will be interpreted as an offset from the
beginning of the block (i.e., an offset of 2 in a /24
block will create an interface xxx.xxx.xxx.2).
An offset of 1 is assumed if none is specified.
An offset of 1 is assumed if none is specified.
No
L
Create Reverse
Domains
Whether or not to automatically create reverse DNS
domain(s) for this block. Accepted values are true or
false. If not specified, defaults to false.
No
M
Domain Type
Specify the domain type for the reverse DNS
domain(s) to be created when Create Reverse Domains
is “true”. If not specified, defaults to “Default”.
No
N
User Defined Fields
A series of name=value pairs, where the name is the
UDF name and the value is desired value. Multiple
pairs can be specified by separating each pair with the
“|” character. For example, UDFone=value one
|UDFtwo=value two. If the UDF type is Checkbox,
the valid values are “on” or “off”. If the UDF type is
Textarea, use “\n” to separate lines.
Yes, for
UDFs defined
as required
fields.