Buy or Renew
Buy or Renew
Cisco DNA Center is now Catalyst Center. New name, same great product. Learn more about Catalyst Center here.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
980
Views
3
Helpful
2
Replies

DNA Center integration with DNA Spaces

Go to solution
Lebowski1991
Level 1
Level 1

‎03-22-2023 07:23 AM - last edited on ‎09-29-2023 01:58 AM by Community Manager

Hi all,

I'm integrating DNA Center with DNA Spaces and the DNA Spaces was successful, however, when attempting to sync Map Hierarchy with DNA spaces , specifically Area ( Design > Network Hierarchy > (Select Area ) > Sync : DNA Spaces/CMX ) an error pops up stating the following :

Unable to export hierarchy to the CMX for domain(s). CMX instance is not configured.

And If I attempt to sync the building lower in hierarchy I'm getting:

 

Success
Sync with DNA Spaces/CMX is success

The main point is, no matter what, DNA Spaces hierarchy is not updated.

From Map-service I can only see DNA attempting to sync with CMX and nothing about connecting to DNA Spaces:

| 42 | |2023-03-22 13:58:30,705 | WARN | ew-dna-maps-service-1 | | c.c.a.m.d.m.s.a.CmxSyncHierarchyMessageHandler | AMQP=CMX#52 - Unable to export hierarchy to the CMX for domain(s). CMX instance is not configured.
| 43 | com.cisco.apicem.mapsapp.core.interfaces.exception.InternalFailureException: Unable to export hierarchy to the CMX for domain(s). CMX instance is not configured.
| 44 | at com.cisco.csg.ngmaps.impl.apicem.CMXCommonServiceImpl.syncMapHierarchy(CMXCommonServiceImpl.java:191) ~[classes/:na]
| 45 | at com.cisco.apicem.mapsapp.dna.maps.service.amqp.CmxSyncHierarchyMessageHandler.handleRequest(CmxSyncHierarchyMessageHandler.java:89) ~[classes/:na]
| 46 | at jdk.internal.reflect.GeneratedMethodAccessor295.invoke(Unknown Source) ~[na:na]
| 47 | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
| 48 | at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
| 49 | at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 50 | at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 51 | at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 52 | at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:84) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 53 | at com.cisco.apicem.fish.tagging.LoggingTagAspect.aroundImpl(LoggingTagAspect.java:120) ~[map-services-7.14.514.62231.jar:7.14.514.62231]
| 54 | at com.cisco.apicem.fish.tagging.LoggingTagAspect.aroundAmqpClass(LoggingTagAspect.java:102) ~[map-services-7.14.514.62231.jar:7.14.514.62231]
| 55 | at jdk.internal.reflect.GeneratedMethodAccessor51.invoke(Unknown Source) ~[na:na]
| 56 | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
| 57 | at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
| 58 | at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 59 | at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 60 | at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 61 | at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 62 | at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 63 | at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 64 | at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.19.RELEASE.jar:4.3.19.RELEASE]
| 65 | at com.sun.proxy.$Proxy154.handleRequest(Unknown Source) ~[na:na]
| 66 | at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.invokeHandler_aroundBody0(GrapevineMessageListener.java:425) ~[message-queue-sdk-7.0.514.62231.jar:7.0.514.62231]
| 67 | at com.cisco.grapevine.amqp.impl.GrapevineMessageListener$AjcClosure1.run(GrapevineMessageListener.java:1) ~[na:7.0.514.62231]
| 68 | at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) ~[aspectjrt-1.9.2.jar:na]
| 69 | at com.cisco.enc.i18n.localization.aop.EnableI18nOnRequestHandler.getEmptyResponse(EnableI18nOnRequestHandler.java:26) ~[i18n-7.1.514.62231.jar:7.1.514.62231]
| 70 | at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.invokeHandler(GrapevineMessageListener.java:398) ~[message-queue-sdk-7.0.514.62231.jar:7.0.514.62231]
| 71 | at com.cisco.grapevine.amqp.impl.GrapevineMessageListener.onMessage(GrapevineMessageListener.java:236) ~[message-queue-sdk-7.0.514.62231.jar:7.0.514.62231]
| 72 | at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:546) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 73 | at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:472) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 74 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$001(SimpleMessageListenerContainer.java:61) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 75 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$1.invokeListener(SimpleMessageListenerContainer.java:110) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 76 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.invokeListener(SimpleMessageListenerContainer.java:611) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 77 | at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.executeListener(AbstractMessageListenerContainer.java:454) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 78 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.doReceiveAndExecute(SimpleMessageListenerContainer.java:474) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 79 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.receiveAndExecute(SimpleMessageListenerContainer.java:458) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 80 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.access$300(SimpleMessageListenerContainer.java:61) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 81 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.run(SimpleMessageListenerContainer.java:551) ~[spring-rabbit-1.2.0.RELEASE.jar:na]
| 82 | at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
| 83 | |2023-03-22 13:58:45,675 | INFO | ew-dna-maps-service-1 | | c.c.a.m.d.m.s.a.CmxSyncHierarchyMessageHandler | AMQP=CMX#54 - Handling sync request for domain: 8f749d21-303d-4baf-ad3d-95dbbe26cf42, type: 2, triggering operation: FULL_SYNC
| 84 | |2023-03-22 13:58:45,685 | WARN | ew-dna-maps-service-1 | | c.c.c.n.i.a.CMXCommonServiceImpl | AMQP=CMX#54 - Group with UUID 8f749d21-303d-4baf-ad3d-95dbbe26cf42 doesn't contain domains. Synchronization between CMX and DNAC won't happen until domains are added.

Version running is : 2.3.3.5 
Both Spaces and DNA center are completely empty apart from this configuration in network hierarchy.
When configuring from DNA Spaces side I do see options to import maps which are exported from DNAC but am I stilly to assume that we should be able to synchronize this automatically (no matter if just maps with wireless placements or hierarchy)?

The way I understood this was that if DNA Spaces account is integrated with DNAC hierarchy and wireless maps would be synchronized as well as Wireless/Wired data. 

Am I misunderstanding how DNA Center can be used with DNA Spaces and by some miracle I would need both CMX and DNA Spaces to integrate ? ( Which makes no sense to me )
Or perhaps DNA Spaces connector needs to be somehow specified? 
Or this would not work at all the way I envisioned it. 

Thanks for all the help in advance.

 

1 person had this problem
Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Lebowski1991
Level 1
Level 1

‎03-24-2023 02:58 AM

In the meantime, I managed to get my answer from other sources so posting it here for visibility.

DNA Center will only Sync information once Wireless and wired is fully integrated as information needs to be tethered from WLC to Spaces cloud.

So, the Idea would be: 
We first integrate WLC with Spaces using Spaces connector and DNAC needs to be integrated with Spaces.
Once this is done:
1. Maps can be uploaded from DNA Center to Spaces and visible in Spaces Map Service.
2. Location hierarchy will be automatically created in DNA Spaces
3. Later changes to floor plan automatically pushed from DNA Center to Map Service.
4. Spaces processed wireless data (endpoints, rogues, ... anything done in Spaces) streamed continuously from spaces to DNA Center.

The documentation on these topics is lacking and honestly operations are counter intuitive so the only way to get the right information is to raise a ticket. 

View solution in original post

2 Replies 2

Go to solution
Lebowski1991
Level 1
Level 1

‎03-24-2023 02:58 AM

In the meantime, I managed to get my answer from other sources so posting it here for visibility.

DNA Center will only Sync information once Wireless and wired is fully integrated as information needs to be tethered from WLC to Spaces cloud.

So, the Idea would be: 
We first integrate WLC with Spaces using Spaces connector and DNAC needs to be integrated with Spaces.
Once this is done:
1. Maps can be uploaded from DNA Center to Spaces and visible in Spaces Map Service.
2. Location hierarchy will be automatically created in DNA Spaces
3. Later changes to floor plan automatically pushed from DNA Center to Map Service.
4. Spaces processed wireless data (endpoints, rogues, ... anything done in Spaces) streamed continuously from spaces to DNA Center.

The documentation on these topics is lacking and honestly operations are counter intuitive so the only way to get the right information is to raise a ticket. 

Go to solution
nsanchez2
Level 1
Level 1
In response to Lebowski1991

‎03-28-2024 07:52 PM

You must enable location services from DNA Center  Design -> Network Settings -> Wireless
Select the site you want enable location services.
Under Cisco Spaces/CMX Servers click your DNA Spaces  account and then hit save.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents