Showing results for 
Search instead for 
Did you mean: 

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!

  • Register for the monthly Cisco DNA Center Ask the Expert Sessions to learn about Cisco DNA Center configuration and deployment.
  • 395

    Cisco DNA Communication Issue

    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?




    Everyone's tags (1)
    2 REPLIES 2
    VIP Collaborator

    Re: Cisco DNA Communication Issue

    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.
    Cisco Employee

    Re: Cisco DNA Communication Issue

    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 
    [On DNAC CLI console]
    [Sat Jun 23 05:55:18 UTC] maglev@ (maglev-master-1) ~
    $ ping
    PING ( 56(84) bytes of data.
    64 bytes from icmp_seq=1 ttl=252 time=0.579 ms
    64 bytes from icmp_seq=2 ttl=252 time=0.684 ms
    64 bytes from 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.

    Content for Community-Ad