Choose one of the topics below for Cisco DNA Center Resources to help you on your journey with Cisco DNA Center
This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!
We will not comment or assist with your TAC case in these forums.
All our documentation recommends using a separate interface for mgmt/Cloud updates & Enterprise (to access the network devices), however we have a customer for which it would be difficult to separate these 2 interfaces.
Is it ok to use the Enterprise link only or will we get in trouble with future updates?
Also interested to get the answer.
We have been told by Cisco that only enterprise and intra-cluster (as we cannot change anymore cluster link when configured) interfaces are mandatory. And mgmt were needed/interesting when we have an OOB network.
So if we need to connect other interfaces i am interested to know ...
I can see only two reasons why you should use both interfaces:
1) As Philippe already said, this is the only way to map access via an OOB network.
2) To avoid that the Enterprise Interface is congested when downloading updates etc. This could disrupt the communication between DNAC, ISE, routers and switches.
Short answer is if the customer is not using a cold standby DNAC at a different location, then it should be OK.
When you do cold standby then the enterprise port needs to be shut down on the cold standby interface until the primary fails and during that time cloud interface can be used by cold standby DNAC to access internet and download updates etc.