02-19-2020 12:08 AM
Hi,
We are designing an SD Access solution for a customer site that involves less than 100 endpoints, as a starting point. Customer would like to go for very small design using Fabric-in-the-Box. In the future, customer wants to add redundancy to the provided solution, as more network segments will be migrated to SD Access. I assume that Fabric-in-the-Box, does not provide any kind of redundancy.
Is there a way to migrate from Fabric-in-the-Box to normal Fabric (2 Border / CP Nodes, etc) and have redundancy in the future?
Solved! Go to Solution.
02-19-2020 01:46 PM
With FIAB, you can test redundancy by having a stack of switches, logically a single entity for FIAB function.
At time of scale out with separate Border/CP devices in pair, you need to add these devices one by one and remove FIAB. Since every customer network is different, you need to look in the services, wired/wireless access etc.
There will be downtime. To get better guidance when you are up for migrate in a production you can reach out to sda-designcouncil@cisco.com with details of your setup.
02-19-2020 01:46 PM
With FIAB, you can test redundancy by having a stack of switches, logically a single entity for FIAB function.
At time of scale out with separate Border/CP devices in pair, you need to add these devices one by one and remove FIAB. Since every customer network is different, you need to look in the services, wired/wireless access etc.
There will be downtime. To get better guidance when you are up for migrate in a production you can reach out to sda-designcouncil@cisco.com with details of your setup.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide