Importing Inventory using CSV File
You can manually create a CSV file with device details, in a prescribed format, and import the CSV file into Cisco VTS.
The CSV file is used to define device mappings. If the format is incorrect, Cisco VTS displays an error and provides the details of the error. After a successful import, the topology gets displayed based on the mapping specified in the file.
Note |
You should be an admin user to download or upload the CSV file. Also, if you are uploading a CSV file for the first time and there are issues uploading the file, then only the partial information is uploaded. You may encounter problems due to the partial upload. |
To download a sample inventory file, click Download latest CSV Template . You can use the Export Inventory option to export the current inventory details in CSV format, for reuse.
-
device-name—The device host-name (leaf, spine, DCI)
-
device-ip—IP address for the device (leaf, spine, DCI)
-
device-platform—Can be Cisco Nexus 9000, Cisco Nexus 7000 etc based on the device that is part of the network.
-
device-role—The role that a particular device plays in the data center. -
leaf—If the device plays the role of a Leaf in the data center.
-
border leaf—If the device plays the role of a Border Leaf in the data center.
-
spine—If the device plays the role of a Spine in the data center.
-
spine-rr—If the Spine plays the role of a Route Reflector in the data center.
-
dci—If the device plays the role of a DCI in the data center.
-
-
group-tag—Identifier for the group.
-
port-name—Physical port connectivity (local interface)
-
connection-type—server (if connected to compute host); fabric (if connected to another leaf, spine, DCI devices).
-
server-id—Host-name or IP address of the connected device based upon what is configured on the actual host. If you enter hostname, ensure that it contains hostname in FQDN format, i.e <hostname>.<domain>.
-
server-type—virtual-server for computes; baremetal for connections to spine, DCI.
-
interface-name—Physical port connectivity (interface of the connected device)
Note
-
Do not use a/b for interface names instead, use a letter followed by a number. For example, Excel converts 5/28 to May-28.
-
Use a text editor like notepad++, instead of Excel to append new items to the CSV file.
Prior to CSV import, you can update the existing interface names in a/b format by adding a letter next to a/b. All dependencies related to an interface name or model data that has an interface name should be changed. This is because Excel does not convert this interface name to a date.
-
-
server-ip— IP address of the connected device.
-
auth-group—Authorization group name, created as part of initialization, with correct credentials.
-
sriov-enabled— If the interface (interface-name) is SR-IOV enabled, this has to be TRUE.
-
physnet-name— Physnet name associated with the interface (interface-name) in OpenStack. If sriov enabled is TRUE, it is the Physnet to be used for SR-IOV. If it is FALSE, the other possibilities are that the port is associated to L2 switch or OVS. In case of OVS, you need to give Physnet intended to be used for OVS.
-
bgp-asn— BGP ASN number.
-
underlay-loopback-num— Underlay loopback number.
-
overlay-loopback-num— Overlay loopback number.
Note |
In a VMware environment, each time you add a leaf, you must create a corresponding VMware vSphere Distributed Switch (vDS). See the Notes Regarding VMware vSphere Distributed Switch section for details. |
Note |
While importing inventory with IPv6 addresses for compute hosts in vCenter, the host labels in vCenter (if they have IPv4 addresses) need to be changed. In order to change them, you need to disconnect the host in vCenter, add the host back to the Datastore with IPv6 address. |
Note |
These three fields are optional in inventory CSV file. Only when you decide to place them in inventory CSV, the order specific above has to be followed. |
Procedure
Step 1 |
Go to . The Inventory > Import and Discovery window appears. |
||
Step 2 |
Select the CSV radio button. |
||
Step 3 |
Click Import CSV to choose the CSV file. Browse for the CSV file, and click Open.
The following details are displayed for Devices:
Click the drop-down to view the Host Interface details pertaining to each bucket. Only for new devices, you can use the Bulk Edit option to update BGP-ASN and Loopback Interface Number. You can also use the Bulk Edit option to disable secure communication. By default, this is enabled in Cisco VTS. |
||
Step 4 |
Click Update Inventory, and confirm that you need to update the inventory. Based on what is uploaded from CSV, the entire Inventory get replaced. |
||
Step 5 |
After the inventory is replaced successfully, you can choose the following options to add/update device.
For reuse, you can use the Export Inventory option to export the current inventory details in the CSV format. You can also export the CSV file :
|