topic Re: Adding stack member using dnac in Cisco Catalyst Center

Adding stack member using dnac

p.whitton — Tue, 02 Nov 2021 21:36:13 GMT

I can either add a new physical switch to an existing stack in dnac and then do a resync or provision on the cli of the switch in advance of adding the new member and then resync in dnac. At which point dnac becomes aware that stack has a new member.

My question is how do you then get dnac to actually put some (fabric) config on the new interfaces on the new stack member so they can be used by clients?

Thanks

Re: Adding stack member using dnac

fh — Mon, 20 Dec 2021 14:27:53 GMT

We have the same problem! the only solution is to copy and paste the interface config from the existing stackmembers to the new stackmembers over CLI and reload the whole stack...

Re: Adding stack member using dnac

Flavio Miranda — Wed, 22 Dec 2021 13:12:44 GMT

DNAC has a feature called "Device Replacement" under Inventory > Actions.

You may want to take a look on this video:

https://www.youtube.com/watch?v=1ILTxmRtLVY

Re: Adding stack member using dnac

fh — Wed, 22 Dec 2021 14:13:21 GMT

Hi Miranda

thanks for your suggestion. But this replacement workflow is no help if you want to add stackmembers to an existing Stack.

Maybe there will be a Workflow for Adding Stackmembers in the future?

Re: Adding stack member using dnac

Flavio Miranda — Wed, 22 Dec 2021 15:00:31 GMT

I will test on my lab environment and get back to you.

Re: Adding stack member using dnac

Rajesh Kongath — Sun, 26 Dec 2021 11:41:45 GMT

We also have the same issue, we are manually doing host onboarding port configuration for the newly added member ports. Manually copy past on CLI can cause a compliance error. I am using a small python code with a for loop invoking SDA API to configure in bulk.

I have opened a case on this issue, TAC yet to come back, i will post the outcome here.

Re: Adding stack member using dnac

Rajesh Kongath — Wed, 29 Dec 2021 05:50:59 GMT

Update!

TAC is suspecting a potential bug for our case ( new stack members doesn't have any port configuration). We have seen the same behavior for all versions from 1.3.X.X. The workaround suggested in the bug details will still miss the IPDT command or sometime bpduguard command

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa44791

Re: Adding stack member using dnac

bora1337 — Wed, 29 Dec 2021 07:25:31 GMT

Re: Adding stack member using dnac

Rajesh Kongath — Mon, 20 Mar 2023 07:11:50 GMT

I found a better workaround for this issue.

DNAC > Design > Network Settings > Go to the affected site/floor > Disable wired end point data collection
DNAC > Provision > Inventory > Go to affected site > select affected device > Action > Telemetry > Update telemetry settings > Force.

Now re-enable wired data end point collection and re-apply telemetry settings with forced ticked. This will add the missing “device-tracking attach-policy IPDT_POLICY”

Hope it helps, Thanks