- Print
- PDF
Adding Devices from a Configuration File
You can also add one or more devices by importing them from an XML file. This is especially useful when you need to add a large number of devices.
Note: The XML interface is deprecated and has been phased out as of Legacy orchestrator 23.12. Northbound systems must migrate to the CSV file format for PM data reception.
Importing Device Configurations
To import an existing device configuration or a list of device configurations
Access the page Devices ▶ Managed Elements or Devices ▶ Unmanaged Elements.
Click the Import device profiles from XML button. The Import Elements dialog is displayed.
Browse to the XML file and click the Import button. The status of the import is indicated in the Import elements dialog.
Close the Import devices dialog.
Refresh the Managed Elements or Unmanaged Elements page.
The following example of an XML file defines two network configurations, each definition providing data for the network configuration.
Example of XML File for Importing Network Configurations
<managed-elements>
<network-elements>
<network-element>
<discovery-enabled>true</discovery-enabled>
<element-details>
<ne-label>PLM-JF1</ne-label>
<ne-mgdstate>MANAGED</ne-mgdstate>
<ne-invtpolling>false</ne-invtpolling>
</element-details>
<interface-details>
<end-point>
<ip-address>192.168.106.160</ip-address>
<port>22</port>
</end-point>
<auth-method>USERID_BASED</auth-method>
<auth-details>
<credentials>admin</credentials>
</auth-details>
</interface-details>
</network-element>
<network-element>
<discovery-enabled>true</discovery-enabled>
<element-details>
<ne-label>PLM-JF2</ne-label>
<ne-mgdstate>MANAGED</ne-mgdstate>
<ne-invtpolling>false</ne-invtpolling>
</element-details>
<interface-details>
<end-point>
<ip-address>192.168.106.234</ip-address>
<port>22</port>
</end-point>
<auth-method>USERID_BASED</auth-method>
<auth-details>
<credentials>admin</credentials>
</auth-details>
</interface-details>
</network-element>
<network-element>
<discovery-enabled>true</discovery-enabled>
<element-details>
<ne-label>BOSTON-SUB1</ne-label>
<ne-mgdstate>MANAGED</ne-mgdstate>
<ne-invtpolling>false</ne-invtpolling>
</element-details>
<interface-details>
<end-point>
<ip-address>192.168.106.164</ip-address>
<port>22</port>
</end-point>
<auth-method>USERID_BASED</auth-method>
<auth-details>
<credentials>admin</credentials>
</auth-details>
</interface-details>
</network-element>
<network-element>
<discovery-enabled>true</discovery-enabled>
<element-details>
<ne-label>BOSTON CO12</ne-label>
<ne-mgdstate>MANAGED</ne-mgdstate>
<ne-invtpolling>false</ne-invtpolling>
</element-details>
<interface-details>
<end-point>
<ip-address>192.168.106.163</ip-address>
<port>22</port>
</end-point>
<auth-method>USERID_BASED</auth-method>
<auth-details>
<credentials>admin</credentials>
</auth-details>
</interface-details>
</network-element>
<network-element>
<discovery-enabled>true</discovery-enabled>
<element-details>
<ne-label>VM-2-1</ne-label>
<ne-mgdstate>MANAGED</ne-mgdstate>
<ne-invtpolling>false</ne-invtpolling>
</element-details>
<interface-details>
<end-point>
<ip-address>192.168.106.162</ip-address>
<port>22</port>
</end-point>
<auth-method>USERID_BASED</auth-method>
<auth-details>
<credentials>admin</credentials>
</auth-details>
</interface-details>
</network-element>
</network-elements>
</managed-elements>
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks