Fabric-Site vs Fabric in a Box
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2020 12:56 PM
Hi Guys,
Operationally, and feature set wise, are there any differenes between a Fabric-Site and Fabric in a Box. My main area of thought is Wireless. Can I still have a centralised WLC that supports a distribted campus? I.E, lots of Fabric-Sites and Fabric in Boxes.
Cheers
- Labels:
-
Other Cisco DNA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2020 08:42 AM
Fabric in a Box or 'FiaB' is a type of device which can be provisioned to a Fabric-site. Fabric in a box is essentially one device which is provisioned as an Edge node, Border node, and Control Plane node. Some devices which support being provisioned as a FiaB can even take it one step further by adding embedded wireless capabilities to the FiaB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2022 06:10 AM
We are large consumers of the FIAB configuration. We use it so we don't expose the vlans from our main campus site to our partner / WAN locations. we have recently found out and are currently testing the embedded wireless controller on my 9300s because this feature is required to utilize wireless at the FIAB sites.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2022 06:37 PM
We are also using FIAB extensively, even beyond the published/advertised limits with a number of subtended edge and even policy extended nodes. We also enable the eWLC functionality and provision the APs in fabric mode to the FIAB. We have not hit any performance limitations, even upwards of 1000+ endpoints.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2022 02:41 AM
thats very intresting, yes its all depends on use case and client usage, if simple usage yes that should work. Cat 9K has good chipset so it can handle
but good to know your input.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 04:45 PM
Hi everyone
quick question: I know that for FAIB, the recommended topology is to use one logical switch (switch stacking), but can we use two logical switches in the FIAB role (have two separate switch stacks), and connect a couple of edge nodes to both of them (dual-homing)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 06:36 PM - edited 03-23-2025 06:41 PM
John,
at some of our FIAB sites, we have additional edge switches hanging off the main head switch which is performing all 3 roles. But I don’t believe you can have more than one switch or stack performing all three roles at once.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 08:17 PM
thanks for reply
my consideration here is that my customer wants to have two separate switches instead of using the switch stack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 08:28 PM
I would just connect your second switch on the underlay for that FIAB site and give it the role of edge. You should be all set.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2025 12:21 AM
We can have two FIABs in a fabric site. The FIABs can be standalone switches or stack or SVL. I would avoid dual FIAB with LISP/BGP fabric, the routing becomes too complicated. LISP Pub/Sub fabric makes it easier to accomplish dual FIAB. Even easier again is FIAB + separate Edge Node since the BN routing becomes relatively simple.
