Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Steelneck
Steelneck
Just browsing
Member since Oct 25, 2024
11 hours ago
Community Record
4
Posts
0
Kudos
0
Solutions
yesterday
We are running into issues with the 1.5 version, both when upgrading from an earlier version and with a install from scratch. I wrote a post about the issue: https://community.meraki.com/t5/Developers-APIs/Missing-entity-mappings-in-Meraki-Service-Graph-Connector-1-5/m-p/261619#M11916
... View more
yesterday
Hi, We have run into errors with the latest version of Meraki Service Graph Connector (1.5) Both me, and a colleague of mine are running into issues with the 1.5 version which was released with support for Xanadu. I have tried upgrading from an earlier version, and he has tried a clean install and we both get the same issues. What we're encountering is that there appears to be missing references between fields in the robust transform map. This leads to the import of data failing immediately without any actual write happening. This is one of the error messages from a failed import set: java.lang.IllegalArgumentException: Invalid Entity class for field (name: location, sysid: 8d4ee2901b479610f5cf97d7b04bcb85) at com.glide.robust_transform_engine.definition_provider.RteEntityBasedCoordinator.validateEntities(RteEntityBasedCoordinator.java:39) at com.glide.robust_transform_engine.definition_provider.RteEntityBasedCoordinator.<init>(RteEntityBasedCoordinator.java:28) at com.glide.robust_transform_engine.definition_provider.CmdbRobustTransformEngineDefinitionProvider.getRobustTransformEngineDefinition(CmdbRobustTransformEngineDefinitionProvider.java:99) at com.glide.robust_transform_engine.RobustTransformEngineDefinitionLoader.getRobustTransformDefinition(RobustTransformEngineDefinitionLoader.java:42) at com.glide.robust_transform_engine.RobustTransformEngine.getRTEDefinition(RobustTransformEngine.java:435) at com.glide.robust_transform_engine.RobustTransformEngine.<init>(RobustTransformEngine.java:93) at com.glide.robust_transform_engine.RobustTransformEngine$Builder.build(RobustTransformEngine.java:156) at com.glide.db.impex.transformer.service.RobustImportSetProcessor.init(RobustImportSetProcessor.java:63) at com.glide.db.impex.transformer.service.RobustImportSetProcessor.<init>(RobustImportSetProcessor.java:54) at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:164) at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:114) at com.glide.system_import_set.ImportSetTransformer.transformAllMaps(ImportSetTransformer.java:91) at com.snc.automation.ImportSetTransformerJob.runTransform(ImportSetTransformerJob.java:291) at com.snc.automation.ImportSetTransformerJob.execute(ImportSetTransformerJob.java:103) at com.glide.schedule.JobExecutor.lambda$executeJob$1(JobExecutor.java:195) at com.snc.db.data_replicate.replicator.DataReplicationAdvisors.runInOriginatorContext(DataReplicationAdvisors.java:74) at com.glide.schedule.JobExecutor.lambda$inDataReplicationContext$3(JobExecutor.java:225) at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:198) at com.glide.schedule.JobExecutor.execute(JobExecutor.java:178) at com.glide.schedule.JobExecutor.execute(JobExecutor.java:168) at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:609) at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$2(SchedulerWorkerThread.java:402) at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35) at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:402) at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:178) Anyone else run into this issue? Anyone got a solution?
... View more
Oct 27 2024
2:05 AM
Thanks for the answer! This makes sense. It is a bummer though that the auditing gets "spammed" with daily Install status changes and I cannot find a way to exclude this audit. An idea I had is that If the import was using a kind of staging table (that was emptied after every run) it could use a GlideRecord query to compare the CMDB with the staging table. If the CMDB has CIs with Discovery Source = SG-Meraki that is not in the staging table, it could change the install status of those CIs to Retired and keep the rest as Installed. That way only the missing CIs would have their CI status changed to Retired.
... View more
Oct 25 2024
6:38 AM
I have a question regarding how the Meraki Service Graph Connector is setting install status on the imported CIs. Currently, on every import all the CIs toggles between Retired and Installed install status and I wonder why that is? I found that during the Data source import a script include SGConnectorMerakiImportUtils() runs a startImport() method In this script include the startImport() method runs another method deactivateRecords() where all Meraki Organization and Meraki Network CIs is set to Active=False for "preprocessing" purposes. As there is a business rule Update Related CI Install Status that set the network device CIs to Retired if the Network status is false, this results in all related CIs going to Retired status during the import Later in the import process the correct status is set during the transform and all the CIs get their install status to Installed. I cannot find any sensible reason for why this is done, as the robust transform map will set the Network and Organization status afterwards. What am I missing with this preprocessing and why is it needed? I would prefer to not do any customizations to the connector as we don't want to risk the script getting outdated in the future but at the same time we can't have CIs flipping between installed and retired on a daily basis as this not only adds a lot of unnecessary audit entries but also could have effect on CMDB lifecycle processes. So I guess my question is: is this by design and how come the deactivation is needed during import? My guess is that the API can only find active networks and therefor cannot update inactive networks.
... View more
© 2025 Cisco Systems, Inc.
