This topic shows an example of a data file for a topology batch import.
The following section lists syntax rules and notes about batch import files.
The area between the dotted lines is for information only.
#-------------------------------------------------------------------------
# Sample Data File for Topology Batch Import
# ------------------------------------------
#
# Syntax:
# # - commented line
# $entity=<entityName> - a entity name descriptor
# $attributes=|attr1|attr2|... - attribute descriptor
# |data1|data2|... - field data in the attributes order.
#
# Notes:
# * Attribute names are case sensitive
# * Any line starting with a char other than $ or | is ignored.
# * Any blank space between || in a data field are not ignored.
#
# * For Network elements, the mandatory attributes are:
# scopeName, role, ipAddr, & mgmtIPAddr
#
# * For scope, the mandatory attributes are:
# name, type, and parent
#
# * Unspecified attributes take default values, if the attribute is
# not mandatory. The default values are:
# regPassword = ""
# privPassword = ""
# vtyPassword = ""
# secPassword = ""
# userId = ""
# telnetPort = 23
# vendor = "Cisco"
# distProtocol = "CLI/Telnet"
# discProtocol = "CLI"
# osVersion = set by discovery
# platform = set by discovery
# ieIPAddr = null (IP address of the Cisco IE2100)
#
#------------------------------------------------------------------------
The following is an example of a batch import file. See note above for a list of mandatory fields.
$entity=Scope
$attributes=|name|type|parent
|Region-A|Region|AD0
|Region-B|Region|AD0
# Note: "scopeName" used in the NetworkElement must be the "name" of an
# existing Scope or a newly added Scope.
$entity=NetworkElement
$attributes=|name|regPassword|privPassword|vtyPassword|userId|ipAddr|mgmtIPAddr|role|scopeName
|Host-Name-1|pw|pw|pw||10.4.8.40 |10.4.8.40 |GW|Region-A
|Host-Name-2|pw|pw|pw||10.4.6.110|10.4.6.110|GK|Region-A
## ----- END -----