Unable to import anymore devices from Orion into Cirrus

Question

I currently have 5411 nodes in my Orion Database.  When I am in Cirrus and try to do an Import from Orion's Database, the last several hundred devices are not in the list that I can select to import.  I have the unlimited Cirrus version so that isn't the issue.  It appears that the import function is limited in the number of devices it can see and it starts at the top of the NODE ID list in the Orion's database and then runs out of room.

Has anyone else ran into the issue that they are not able to import any more new devices from Orion in Cirrus due to a "count" level in the import function?

I have a support ticket open and it has been open for over 6 weeks without any real feedback other than "Development is working on it".  I am getting tired of hand entering nodes one at a time in both Orion and then again in Cirrus.  Plus, after I add it into Cirrus, I need to then edit each node and give it the DNS name as it labels the names as $System and then when I run my custom SQL command to make the comparison of the two inventories, I get mismatches from Orion to Cirrus to because the Node Name in Orion doens't equal $System that Cirrus shows.  Very time consuming.  The import function automatically gives it the Node Name assigned in Orion.

chris.lapoint · Answer

Thanks for that.  I'll look into this to see where this stands in dev.   Wrt/ auto-synch from Orion to Cirrus, we're definitely planning on providing some control over the import and merge process (e.g. triggering off of a custom property).  I'll keep you in the loop once we get close to final design so we can vet our approach with you.

CNeale · Answer

My support ticket number is 31896.  I have read a few forums about the Auto- Synch and it sounds like you have some good ideas if we do have the option to narrow the list down or to make a Custom Property in Orion to mark those that should be in Cirrus.

I think I may have mis-typed earlier.  We don't actually use SQL to import/merge devices.  One of my Co-Workers wrote two SQL queries that tells us the devices that are in Orion but not in Cirrus (and he has narrowed it down to the devices we want in both) and the other is the reverse, the devices in Cirrus that aren't in Orion.  Then I take both the lists and manually remove/add devices as needed to make the lists the same.  We run this periodically to just keep everything on an even keel.

chris.lapoint · Answer

Can you give me your support ticket # for this issue?   I'd like to see where this is at in development.

Good news about the future.  We are planning on building in an automatic synch job in Cirrus that will pull/merge Orion node data on a scheduled basis in the next major release (2H08).   Hopefully, this will eliminate the need for any custom SQL merging.

Would you mind describing how your custom merging process works?  We'd like to ensure that we're accounting for your specific use-case requirements.

Thanks,