Cisco DNA Communication Issue

[mediaos718]

We have been dealing with a Cisco DNA issue for the past 24 hours. We added a access switch within the DNA fabric - End result:

1) By adding the new switch, it breaks 2 other access switch that use to work - User are unable to get DHCP or ping outside the VLAN

2) The new access switch continue to work.

3) All the switches are on the same fabric.

Anyone else experienced the same issue?

[Mike.Cifelli]

Are the other two access switches daisy chained off of the one that you put in the fabric? If so, you can only run certain platforms as an extended node. For example, I am pretty sure a 3560-cx can act as an extended node.

[Farhan Mohamed]

Yes, as you described in your issues with DNA center is commonly faced issue as a part of DNAC Assurance, DHCP server is generally found unreachable and ping test fails, some reasons might be due to RF issues. Some ping failures is due to route not setup correctly on DNAC. You have to create an SVI and test connectivity between DNAC using follow script:-

[On seed device]

Switch(config)#interface vlan1
Switch(config-if)#ip address 192.168.99.1 255.255.255.0 
Switch(config-if)#end

[On DNAC CLI console]

[Sat Jun 23 05:55:18 UTC] maglev@10.195.192.157 (maglev-master-1) ~
$ ping 192.168.99.1
PING 192.168.99.1 (192.168.99.1) 56(84) bytes of data.
64 bytes from 192.168.99.1: icmp_seq=1 ttl=252 time=0.579 ms
64 bytes from 192.168.99.1: icmp_seq=2 ttl=252 time=0.684 ms
64 bytes from 192.168.99.1: icmp_seq=3 ttl=252 time=0.541 ms

[On seed device]

Switch(config)#default int vlan 1
Interface Vlan1 set to default configuration

If the ping test fails, the route is not set up correctly on Cisco DNA Center.