IP Pool design

[KevinR99]

Hi

Can anyone share their experiences of a large SD Access deployment and how they allocated IP pools?  I've read that since there are no broadcasts to propagate, except where a certain functionality needs L2 flooding, then it can be common to use large subnets/pools and just put everyone in the same address range.  Or at least put each type of device Laptops/phones/IoT etc in their own pool.  This saves us then allocating and managing many address pools across a large campus.

So, I'm wondering how others have approached this issue and any issues your choice may have had further down the line.

Thanks, Kev.

[balaji.bandi]

Not you come across this CVD have a look CVD :

https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Campus/sda-fabric-deploy-2019oct.pdf

[KevinR99]

I have read the CVD thank you.  However, as I said, I am more interested in people's practical experiences of deployment.  In the CVD it does show allocating lots of /24's.  However, why do we create small subnets?  To create smaller broadcast domains.  This isn't an issue in SD Access unless you enable L2 flooding so why bother about /24's ?  Why not just use large subnets and less pools?  Assuming we secure the client access with .1x we secure the network with SGT's, not IP address based ACL's so where is the benefit of carving up your subnets?

Kev.