cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1443
Views
2
Helpful
4
Replies

DNAC takes too long to mark device as unreachable

gerdo1961
Level 1
Level 1

Hello all, my DNAC takes far too long to mark a device as unreachable. If I reboot a switch, DNAC doesn't see it as unreachable and therefore I dont receive an email alert to say it's unreachable. It seems to take a device to be unreachable for about 15mins or so before DNAC marks it as unreachable. Is there a setting somewhere to adjust this? I cant find it 

4 Replies 4

Leo Laohoo
Hall of Fame
Hall of Fame

@gerdo1961 wrote:
Is there a setting somewhere to adjust this?

15 minute polling time is the only settings.  

So if one of my switches reboots for any reason, DNAC will not tell me ? That's not much use.

 


@gerdo1961 wrote:
So if one of my switches reboots for any reason, DNAC will not tell me ? That's not much use.

Routers, switches, WLC, APs take about 5 to 7 minutes to crash and reboot.  If this falls inside the 15 minute polling period, DNAC will not see the crash and will not see the reboot. 

Where I work, we use AKiPS that pings-n-polls, any device with an IP address, every 60 seconds.  We only use DNAC to build switches and even that can be a struggle because the behaviour &/or result is not consistent.  Sometimes it works.  

Shibble1991
Level 1
Level 1

You might want to look into Cisco DNA event settings for a possible solution. You can define a destination (email server for example under System settings -> External Services -> Destinations) and bind that to an notification under Platform -> Developer Toolkit -> Notifications. You could use the event "Device Reboot Crash" for example. Snmp might not be fast enough with polling, but atleast DNA will tell you a device unexpectedly rebooted based on assurance data.