Adding a new switch to an existing stack

[Jordi Martinez]

Hello, 

We have installed two new switches (5&6) on an existing Fabric Stack Edge (4 switches), we can see all the S/N on the DNAC Inventory, but device-tracking configuration is not applied on all new ports/switches. 

SW-WTCP3-NT-S-1#show switch detail
Switch/Stack Mac Address : ecc0.1812.8d80 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
-------------------------------------------------------------------------------------
*1 Active ecc0.1812.8d80 15 V05 Ready
2 Member c02c.17e8.3080 12 V05 Ready
3 Member c02c.17e8.2000 10 V05 Ready
4 Standby 748f.c27e.8600 13 V05 Ready
5 Member 38fd.f821.e280 1 V01 Ready
6 Member 38fd.f833.1e80 1 V01 Ready

We try to do a Provision and deploying fabric again, but the configuration is not applied. 

Somebody have any solution for this question? 

Maybe we need to configure it manually on all this ports? 

Thank you in advance. 

[balaji.bandi]

If you using template to push the config, that new switch should able to get it.

if not you can also configure manually and re-sync from DNAC

check below guide :

https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/tech_notes/b_dnac_sda_lan_automation_deployment.html#id_89815

[Jordi Martinez]

Thanks for your answer Balaji.

But, this part of configuration is automatically configured by DNAC the first time I assign a switch to an edge role, so I need to apply it mannually when add a new stack member?

The configuration that is not applied:

SW-WTCP3-NT-S-1#sh run int gi4/0/35 --->> CONFIG OK
Building configuration...

Current configuration : 438 bytes
!
interface GigabitEthernet4/0/35
switchport mode access
device-tracking attach-policy IPDT_POLICY
ip flow monitor dnacmonitor input
ip flow monitor dnacmonitor output
ipv6 flow monitor dnacmonitor_v6 input
ipv6 flow monitor dnacmonitor_v6 output
dot1x timeout tx-period 7
dot1x max-reauth-req 3
source template DefaultWiredDot1xClosedAuth
spanning-tree portfast
spanning-tree bpduguard enable
ip nbar protocol-discovery
end

SW-WTCP3-NT-S-1#show run int gi5/0/1 --->> CONFIG NO OK.
Building configuration...

Current configuration : 214 bytes
!
interface GigabitEthernet5/0/1
switchport mode access
dot1x timeout tx-period 7
dot1x max-reauth-req 3
source template DefaultWiredDot1xClosedAuth
spanning-tree portfast
spanning-tree bpduguard enable
end

SW-WTCP3-NT-S-1#

This "bold" lines are not configured on new stack member added to an a production 4members stack edge.

Thank you.

Regards,

[andy!doesnt!like!uucp]

i wonder what will happen if u conduct host on-boarding for new ports.

[jalejand]

the IPDT policy is part of the "Wired Telemetry" section of device controllability, try changing the device type/tag from access to distribution and back to access in inventory, that can enable the configuration of the remaining ports (though that policy is kind of useless as DHCP snooping and LISP already enabled like 3 of these VLAN wide in  FE ).

The netflow monitors and NBAR are part of "Application Telemetry", which you can disable and re-enable from inventory/actions. That should reconfigure all ports in the switch with the appropriate netflow/nbar config.