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.
IntroductionDeploying
Introduction
Currently when changing the Authentication Template under the Onboarding section, there is no choice but to remove SGTs, VNs and IP Pools which clearly disrupt existing services.
Hitless Authentication was introduc...
IntroductionRequirementsCisco DNA Center Deployment StepsISE Deployment Steps
Introduction
Host Onboarding is the term used when connecting an endpoint (hosts , IOT , Other devices) to the fabric , and can be accomplished in a couple of ways.One opti...
IntroductionRequirementsAnycast GatewayDHCP Design ConsiderationsDHCP Flow in The Fabric
Introduction
In a typical network a DHCP flow would look something like this.
If your DHCP server resides on a different subnet (which will most probably...
IntroductionRequirementsPrerequisitesSSHERS APIpxGridDeployment Steps
Introduction
Whether you’re beginning your SD-Access journey or are in the process, it's critical to understand the various components that make up the SD-Access solution: Design...
ACS
ACS to ISE Migration
ACS 5.x: TACACS+ Authentication and Command Authorization based on AD group membership Configuration Example - Cisco
ACS Shell Command Authorization Sets on IOS and ASA/PIX/FWSM Configuration Example - Cisco
ASA 8.3: TACACS ...
If your endpoint is statically configured you shouldnt have any issue with DHCP right?
What about other endpoints in that same scope that would like to have DHCP services , if we remove the option we could cause outages for others as well.
You are referring to what we call L2 Flooding in SD-Access.
This is used to support numerous use cases as such the one you point out.
See here for more information regarding this topic.https://community.cisco.com/t5/networking-documents/cisco-sd-acce...
A hybrid solution is not supported.
Having said that you could use Layer2 Hand off on Layer 2 border , this is mainly a solution used for migrating an existing network to SDA. Its not recommended as a long term solution.
I dont see a problem with this , as long as this is a dedicated interface which will be needed to be setup as a trunk for L2 handoff
Im not aware of any HW limitiations at this point.
