Cisco Cisco Prime Network Registrar 8.1 Technical References
Cisco Prime Network Registrar IPAM 8.1.1 CLI and API Guide
3
Command Line Interfaces (CLI)
Assumptions Regarding CLI Usage
Each CLI performs a specific task, or in some cases, several tasks at once. However, there
are assumed dependencies among the different CLIs such that some CLIs will not function
properly unless either other CLIs are run or some manual data setup is performed.
The following manual data setup is recommended to populate the initial Cisco Prime
The following manual data setup is recommended to populate the initial Cisco Prime
Network Registrar IPAM database before running any CLIs:
• Manual step – create block types
• Manual step – create device types
• Manual step – create user defined fields
• Manual step – create IP allocation reasons
• Manual step - create IP address allocation templates
• Manual step - create DNS and/or DHCP servers
• Manual step – create device types
• Manual step – create user defined fields
• Manual step – create IP allocation reasons
• Manual step - create IP address allocation templates
• Manual step - create DNS and/or DHCP servers
Table 1 illustrates the recommended order in which the Cisco Prime Network Registrar
IPAM CLIs should be run.
Table 1 CLI Sequence
Sequence
CLI Name
Brief Description
Data Dependencies
1
ImportContainer
(logical)
Imports logical
containers
N/A
2
ImportNetElement
Imports network
elements such as
routers and switches
N/A
3
ImportContainer
(device)
Imports device
containers
Network elements created using
ImportNetElement
ImportNetElement
CLI or created
manually
4
ImportRootBlock
Imports root IP
address blocks
Containers created using
ImportContainer
ImportContainer
CLI or created
manually
5
ImportChildBlock
Imports child IP
address blocks
Root blocks created using
ImportRootBlock
ImportRootBlock
CLI or created
manually
6
ImportDevice
Imports devices
Blocks created using
ImportChildBlock
ImportChildBlock
,
ImportRootBlock
, or created manually