Portal User asked a question.
SNOW to ServiceNow connector data import - fresh start
We migrated our Production ServiceNow to Orlando and upgraded the Catalog and CMDB connectors to the latest versions in SIM 5.23. We cleared out the CMDB completely before starting the first aggregation.
Aggregations are working and I can see the imports processing. Question is, are those first passes supposed to completely populate all the CI's? Or does it take a couple runs in order to complete the process?
Also, there are errors showing up. Is there a guide to resolve those errors or do I need to engage ServiceNow support?
What I am looking for is those with experience that can tell me this is normal or it is not normal.
thank you
Hi Mark,
We are also on Orlando and SIM 5.23
We decided to upload our computers step by step, so I set some organisation restrictions for the API user that is configured in SIM Connector.
But when you didn't set such organisation restrictions then it should upload all CI 's from Snow to ServiceNow in one step.
We also had some errors, but that was due to configurations in ServiceNow,
For example our ServiceNow team added an own (custom field) configured as mandatory. But this field does not exist in SLM. So they needed to add a transform map, that handles a default value for this field.
I do not know if you already checked the Guided Setup in ServiceNow. Here Snow created a very good step by step instruction to setup the Snow for ServiceNow Connector. And you would find if you missed some.
So in our environment normally all computers (defined in Orgrestrictions) are updated in ServiceNow.
But we have some problems with VM relationships. The relationships cannot be created correctly once because of mismatch of FQDN and shortnames, other reason is, that Snow is using some other relationships for upload, than our team want to use.
Hope this may help a bit.
I have started going through the Guided Setup yes. But some of the items are confusing since I am not real familiar ServiceNow, but am learning.
In our TEST environment it took over a week to fully populate all items in the CMDB and it is still missing Software installed on each device. Very confusing.
Another question. In the Import Status window on ServiceNow. There are column headers, Total, Updates, etc. I understand what those ones mean, but what would "Skipped" and "Ignored" mean? Under what circumstances would items fall into those categories?
Also, any idea what this means in the SIM log when the ServiceNow aggregation is run?
Vcenter does not exist in the lookup. No last aggregation date to set.
Vmware does not exist in the lookup. No last aggregation date to set.
Relationships does not exist in the lookup. No last aggregation date to set.
SoftwarePackage does not exist in the lookup. No last aggregation date to set.
It looks like it is uploading soemthing:
Upload of SoftwarePackage to ServiceNow complete. Size of exported batch: 18192.
I'm also no specialist for ServiceNow and still learning :-) Also our ServiceNow team is still learning
But I think I can at least anwer some of your questions.
I do not know how many computers do you upload? As mentioned, we do not upload all our computers until now, at the moment we are at around 8000. Perhaps you have more and therefore this problem?
We plan to upload the computers of our biggest company part in the next weeks. That will be additional 15.000. I will check if I then would notice similar problems.
The column Ignored is when ServiceNow decides there is no change and so nothing needs to be updated. Becasue SIM always uploads the whole computer after a new scan, although there are perhaps no/less changes, a lot of information can be ignored, for example most of the software installations.
We have less Skipped messages, but when there are some and you click on this Tranform history, then you can see the tab Import set Row Errors and a message what happened. This is then something my ServiceNow colleagues need to check. At the moment I have this for 2 Network adapters and the message is "Unable to resolve target record, .." It seems there was an upload, but the corresponing computer is not available in ServiceNow.
Regarding the messages in SIM log ... does not exist in the lookup. No last aggregation date to set
We also have these messages. I'm not 100% sure. But because we don't want a full upload of all computers every day, SIM is doing a Delta upload. In registry it sets a date, when the last upload was done, and then only uploads computers that have a last scandate after this LastAggregationDate. I assume for VCenters, Relationships, ... it does not set this aggregation date.
What perhaps also can be helpful for you is to check if SIM created the correct/complete data for upload. I already needed to check this.
When you create the subdirectory directory ServiceNowCSV in C:\ProgramData\SnowSoftware\IntegrationManager\ , then SIM will also write the csv files to this directory and you can check the content of the files to see for example, if the missing applications were created for upload.
You need to remove these csv's then by yourself, so you disk don't get full.
When you don't need this anymore, then remove the created subdirectory.
I will create that folder. That's a great idea, I have been wondering what is passed in those CSV files. Thank you.