Whether you're standing up an Orion beta for the first time or it's a process with which you're all too familiar, sometimes it's just faster/easier to start with a known good set of devices to work with, rather than kicking off a broad sweeping subnet discovery and weeding through the results. Such a list may come from an existing spreadsheet you maintain independently, an export from your production Orion instance, or even a dump from a CMDB, DNS, DHCP, or alternative monitoring solution.
Now in the SAM 6.4 beta we have made this process a whole lot faster and easier. Under [Settings -> All Settings] you will find a new option entitled 'Import Nodes from a File' located under the 'Getting Started with Orion' section of the 'Settings' page.
From the 'Import Nodes From File' screen you can download an example comma separated value (CSV), Excel (XLS), or text (TXT) file to use as a template for importing your nodes into Orion.
The only mandatory column in any of these file types is 'IP_Address' field. All other columns are optional. Additional field columns not defined within the examples provided are fully supported, and can be used during the field mapping process outlined below. It's important to note however, that field values which are based on polled data, such as 'Contact', 'MachineType', and 'Location' may be overwritten after the first polling of the device once it has been successfully imported into Orion.
When you have defined the contents of the file to your liking, click the 'Browse' button to upload the file and click 'Next'.
On the following screen you will be asked to map the columns in the uploaded file to fields in Orion. A best-effort attempt to automatically map the columns in the file uploaded, to fields in Orion will be performed. You can however manually override any automatic field mapping by clicking the drop down next to the spreadsheet column name and selecting the appropriate Orion database column from the drop down list. Here is also where you can leverage any additional fields contained within your uploaded file to automatically create Custom Properties in Orion. The value used in that column for the node will be automatically populated upon import, making the creation of Custom Properties and the populating of their values a simple and straightforward affair.
Once you've completed mapping all your fields, click 'Next'. If you plan to uploaded additional files in the same format you can click the 'Remember the current column mapping' checkbox. This will store your field mapping selections as the default for any future files you may import in the future.
On the final step of the Node Import from File Wizard you are given an opportunity to review the results of the import process and verify the field mappings before they are committed to the database. If you made an error in your field mappings, just click the 'Back' button at the bottom of the page to be taken back to the "Map Columns' step where you can make any necessary corrections. Once you're satisfied with the results, click the 'Import to Database' button to import the nodes and their associated properties into Orion.
At the conclusion of the import from a file process you will receive a success confirmation. If any errors occurred during the import process they will be displayed here in place of the 'success' message. Now at this point the nodes that were imported are simple ICMP only nodes. Also the nodes imported did not need to be reachable to be imported. This is great for anyone who builds pre-configured Orion servers for remote deployments prior to shipping them to their intended destination. To convert these nodes to SNMP or WMI, check the 'Create Discovery Profile' checkbox and before clicking the 'Finish' button. This will create a targeted discovery profile containing only those nodes which were imported from the file.
Edit the newly created discovery profile to define the SNMP community strings or WMI credentials to test against the list of imported nodes. Any credentials which match during the discovery process will be associated to the node upon completion of the Sonar Discovery Wizard.
Once you've defined your discovery profile settings, click 'Discover Now' to start the discovery process
Depending how many nodes were included in the imported file and how many credentials were provided within the discovery profile the discovery process may take anywhere from a couple minutes to upwards of an hour to complete successfully. During this time a progress bar indicates how far along the discovery process is. If you don't feel like waiting, you can simply click the 'Run in Background' button. This will allow you to continue using Orion while the discovery process runs in the background.
When the discovery completes walk through the discovery import process to a import any volumes, interfaces, or applications which were found during the discovery process.
The ability to bring in devices reguardless of status as ICMP devices with all custom properties allowing for current status to be viewable within the environment. If running multiple pollers which poller do they get added to, useful if could assign to a particular poller. Would be very useful if available to call using the API so that can script this from a discovery environment.
This document was generated from the following discussion: Import Nodes from a File