Supported hardware

The Fabric Services System currently supports hardware in the leaf, spine, backbone, and border leaf roles as shown in Supported hardware and roles.

Table 1. Supported hardware and roles
Hardware type EVPN capable? Eligible for these roles
T1 (Leaf) T2 (Spine) T3 (Back-bone) T3 (Border Leaf)
7250 IXR-6 - - Yes Yes -
7250 IXR-10 - - Yes Yes -
7220 IXR-D2 Yes Yes - - -
7220 IXR-D2L Yes Yes - - -
7220 IXR-D3 Yes Yes Yes Yes Yes
7220 IXR-D3L Yes Yes Yes Yes Yes
7220 IXR-H2 - - Yes Yes -
7220 IXR-H31 - - Yes Yes -
7220 IXR-D52 - - Yes Yes -
210 WBX-32Q3 Yes Yes Yew Yes Yes
  1. The system does not configure port speed or support breakout capability on 7220 IXR-H3 nodes.
  2. The IXR-D5 is supported only for manual fabric topologies.
  3. The 210 WBX 32Q is supported only for manual fabric topologies.

Hardware-driven exceptions and special cases

The type of hardware used in a fabric intent can impact the Fabric Services System features available to you.

For WBX nodes:

  • manual topology only: you must import the fabric topology, it cannot be automatically generated by the system.
  • updates to the fabric topology require importing a new topology file with the new configuration, which can then be associated with a new candidate version of the fabric intent.
  • although network resources pools are active and can be selected in the Fabric Services GUI during fabric creation, these pools are not used for WBX nodes and should not selected in the UI for WBX fabrics.
  • LAG configurations must be specified within the manual topology; you cannot configure LAGs for WBX nodes using the Fabric Services System GUI.
  • the JSON configuration for WBX nodes cannot be displayed on the Fabric Intents page.