Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi community,I am labbing Cisco SD-WAN in my eve-ng environment. I have been following instructions from these two guides:https://codingpackets.com/blog/cisco-sdwan-self-hosted-lab-part-2/https://www.theansweris101010.network/sd-wan-deploying-the-con...
Hi community,We have set up a 9200L as a policy extended node in our network, hoping to leverage the micro-segmentation policy defined in ISE and applied to the rest of the network. When verifying that the automated onboarding and provisioning of thi...
Hello community, We are migrating a campus from an existing MPLS campus with PE routers at each distribution block in the network. The original migration strategy was to acquire new hardware as intermediate nodes to be installed in the same location ...
Hello,We have recently deployed an SD-Access network with two defined VNs: users_vn and devices_vn.After provisioning the fabric roles in DNA Center we are testing end device connectivity on the users_vn. Users can authenticate and are allocated an I...
Hi there, We have recently labbed an SD-Access implementation using 9200L edge switches, only to be hit with this error when deploying multiple VNs to the fabric:Provisioning failed due to invalid parameter. Cisco Catalyst 9200L Switch Stack supports...
I've got the controllers up and running now. I'll go ahead and provide the solution for future reference. I used a site-id of 0... As soon as I changed the site-id on the controllers to another number, the connections were formed as expected!Further ...
Yes that is correct. When you select external RP, you need to specify the RP-address (the IP on the fusion in this case) for DNA Center to configure it on the fabric nodes. Hope that helps.Josh
The automatic deployment workflow from DNA Center will handle RP-address configuration all fabric nodes including the border, as well pim sparse-mode on the fusion facing SVI. The border will then form an upstream PIM neighbourship once you configure...
Native multicast uses SSM in the underlay. You then have the option to use SSM or ASM in the overlay. Which multicast method you use in the overlay is up to you, however it is typically ASM. With ASM you must have an RP per VN, in which case you migh...
Providing you can enable multicast on your firewall (PIM sparse mode, RP address etc.), it will be okay to place the multicast source behind the firewall. Attaching the source to your border or fusion devices would make things easier, but that's a de...
