cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1897
Views
15
Helpful
4
Replies

DNA C Plug and Play with C1117-4PWE

DeanMoore
Level 1
Level 1

Afternoon everyone,

 

I have a DNA Center appliance on loan to test if it can replace our heavily automated APIC-EM Plug and play system.  One of the devices that was reported to be support is the C1117-4P and C1117-4PWE models we use a lot of, from the spreadsheet the 1K devices should be supported for PnP

 

My aim is for devices to call in to PnP and then our automation can push out a basic configuration, after this our existing automation can take over with Prime.  I'm hitting a problem though with using the PnP tool manually not via the API.

 

I've followed the docs as best as fits our situation but when I claim a device I get the error below.  I'm unsure where to go for help.

Progress
Domain Service did not reply - Configuration preview timed out
Failure Reason
NCOB02082: Async task timed out
 
I believe I have the firewall configured OK, let me know if you need any more information

Thanks for reading
4 Replies 4

balaji.bandi
Hall of Fame
Hall of Fame

what is the version of the device IOS XE running :

 

Look at the matrix and supported version of DNAC for PnP to work :

 

https://www.cisco.com/c/en/us/support/cloud-systems-management/dna-center/products-device-support-tables-list.html

 

Domain Service did not reply - Configuration preview timed out

Looks for me like some DNS Look up the issue - may be connected to console look complete logs?

 

https://www.cisco.com/c/en/us/td/docs/routers/access/1100/software/configuration/xe-16-7/cisco_1100_series_swcfg_xe_16_7_x/cisco_1100_series_swcfg_chapter_01010.html#concept_xjc_gbc_bbb

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Ah of course the supported version is 17.1.1, I'll try it on that version as we are currently running 16.10.2 as that is what we have tested so guestshell works.

 

When you spend all day looking at it, you can't see the wood for the trees!

 

Thank you

That is the reason the community helps you giving pair of eyes extra or more - point you in the right direction.

 

keep us posted outcome.

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

DeanMoore
Level 1
Level 1

I've tried it on 17.03.03 and I get the same error.  If I ssh to DNA C I can use NC to connect to the CPE on port 22 and 443, running TCPDump shows the comms attempting to connect.

 

10:22:26.761229 IP [CPE IP].33374 > [DNAC IP].443: Flags [S], seq 1728570680, win 4128, options [mss 536], length 0
10:22:26.761327 IP [CPE IP].33374 > 169.254.45.181.443: Flags [S], seq 1728570680, win 4128, options [mss 536], length 0
10:22:26.761350 IP 169.254.45.181.443 > [CPE IP].33374: Flags [S.], seq 1633961316, ack 1728570681, win 65280, options [mss 1360], length 0
10:22:26.761360 IP [DNAC IP].443 > [CPE IP].33374: Flags [S.], seq 1633961316, ack 1728570681, win 65280, options [mss 1360], length 0
10:22:26.783139 IP [CPE IP].33374 > [DNAC IP].443: Flags [.], ack 1, win 4128, length 0
10:22:26.783171 IP [CPE IP].33374 > 169.254.45.181.443: Flags [.], ack 1, win 4128, length 0

I've got to be missing a bit of config somewhere

Review Cisco Networking for a $25 gift card