Uploading Network connectivity

[NF-London]

Hello,

When we first installed DCO 5 years ago there was no facility to update cabling information using csv or xls files after the initial established system installation.  In other words to add another datacentres connectivity information to the established system would mean manually inputting all the connectivity.  We have continued in this vein since, but I thought I would ask again if this situation has changed (perhaps with the migration to ITA?)  We have more locations coming online and would like to know if there will be an opportunity to upload a csv or similar before doing it all manually.

Thanks

[gsterling]

Hello Nigel.

Can you describe the type of connections you'd like to make via an import like function? If you are adding data centers I assume then you are referring to making network connection between racked assets and then from the rack to other devices in the room(s)?

It is possible to make/create network connections between items using an ETL Import database but this can be complex to manage.

Given your post mentioned bringing more locations online it would seem you would be planning to build new rooms? DCO and ITA both have the ability to enable a equipment import tool which allows the user to download a xls template from which you can add devices, their custom properties, tags, power connections, and network connections ... then import them.

This tool has a few caveats in that its meant as an engineering tool which is why its not enabled by default, and its solely meant for importing/creating items ... not updating. Used incorrectly is can lead to unexpected results.

I will send you a direct email with more details as I cannot post the template in this forum.

Also, in the future it is likely ITA will have a set of REST api's customer will be able to use to perform network operations like connection maintenance and so on. These are not available yet.

Regards

Greg Sterling

[NF-London]

Greg,

The type of connections for this required event will be inputting patching, mostly in rack patching, between servers and switches already installed in the system.  We do have new locations being added but these will mostly be already installed in the system (location/room/rack/equipment) before the patching stages, in other words a large install of all the nested equipment and its patching cannot be run in one upload.

I was aware of the upload sheet method that is not configured by default but also recognise that this system has limitations of requiring the deletion and re-adding of all the connectivity (e.g. upstream UPS etc.).  I understand the caveats of this system and frankly it does not fit our needs as I need the remote teams in other regions to update their systems, simply,  at their leisure.  Using a csv or similar upload function for patching would help accelerate the data upload.

As the locations involved have small numbers of racks to update I think it is easier for the local engineers to update the patching using the manual tools.  If the numbers of racks were say, in to 3 figures, we might need to re-assess though.

I think we can close this ticket but I remain interested in developments in this area, if as you suggested, there might be future functionality in ITA using REST API.

[gsterling]

Hello Nigel. I will share your feedback.

The xls import sheet can be used on subsets of the room, in fact that is typically how the tool is used by services and some cases customers. 

So if you are building out a new 10 rack section of an existing room, there is no reason you cannot use the template to import the 10 racks, their assets and connections for just those items. None of the other room items would be impacted.

If the assets (racks and servers for example) are already built out in DCO or ITA then its probably less useful.

Regards

Greg Sterling

[NF-London]

Greg,

I have another need to use this excel upload function.  A new stores location requires a register of 1400 devices uploaded to it.  As this is far too many to do manually we need to use this tool to do it quicker.

Please send me details of its use.

Thanks

Nigel

[gsterling]

Hello Nigel. I will forward a direct email to you regarding the importer tool.

Regards

Greg Sterling

[Anonymous user]

I was aware of the upload sheet method that is not configured by default but also recognise that this system has limitations of requiring the deletion and re-adding of all the connectivity (e.g. upstream UPS etc.).  I understand the caveats of this system and frankly it does not fit our needs as I need the remote teams in other regions to update their systems, simply,  at their leisure.  Using a csv or similar upload function for patching would help accelerate the data upload. As the locations involved have small numbers of racks to update I think it is easier for the local engineers to update the patching using the manual tools.  If the numbers of racks were say, in to 3 figures, we might need to re-assess though. WalgreensListens

[Anonymous user]

I am still searching for some proper solution.

[gsterling]

Without using the xls import template, there are a couple other options for completing a task of this nature. The first two being something you can do today, the last item being more of a future discussion.

#1 Create your own ETL integration which allows you to import network connections for objects which already exist in DCO/ITA. Thi would require you create your own integration which uses an ETL import database to create the connections between devices. It is possible to create, edit and delete network connections via ETL. Some pre-configuration work is necessary to complete this task and for most customers, some education would probably be required to understand how to complete this type of project.

#2 Engage Schneider's ACS team to create an integration for you or contract with them to help you complete the task yourself. 

#3 In the future the network connectivity features will be implemented in the the ITA web client UI. At that point there should be REST api calls which would be able to make, edit, and delete network connections. This solution would likely be less complex than an ETL integration.

Regards

Greg Sterling