Fabric Scaling

This section lists the fabric scaling information.

Table 1. Fabric Maximums
Attribute	Product	Maximum number supported (with and without vIST)
Number of SPB IS-IS areas	5320 Series	1
	5420 Series	1
	5520 Series as boundary node	2
	5720 Series as boundary node	2
	7520 Series	2
	7720 Series	2
Number of B-VIDs	5320 Series	2
	5420 Series	2
	5520 Series	2
	5720 Series	2
	7520 Series	2
	7720 Series	2
Maximum number of Physical and Logical (Fabric Extend) NNI interfaces/adjacencies (Home and Remote area total when operating as Boundary Node)	5320 Series	64
	5420 Series	50
	5520 Series	128
	5720 Series	128
	7520 Series	255
	7720 Series	255
I-SIDs supported (local UNI present on device)	5320 Series	See Number of I-SIDs supported
	5420 Series	See Number of I-SIDs supported
	5520 Series	See Number of I-SIDs supported
	5720 Series	See Number of I-SIDs supported
	7520 Series	See Number of I-SIDs supported
	7720 Series	See Number of I-SIDs supported
Maximum number of Layer 2 VSNs per switch (local UNI present on device)	5320 Series	48-port models: 500 16- and 24-port models: 250
	5420 Series	500
	5520 Series	3,580
	5720 Series	4,000
	7520 Series	4,000
	7720 Series	4,000
Maximum number of Transparent Port UNIs per switch	5320 Series	48-port models: 53 24-port models: 29 16- models: 20
	5420 Series	56
	5520 Series	48-port models: 48 24-port models: 24
	5720 Series	60
	7520 Series	56 (up to 125 with channelization)
	7720 Series	32 (up to 125 with channelization)
Maximum number of Layer 2 E-Tree/PVLAN UNIs per switch	5320 Series	48-port models: 50 16-port and 24-port models: 20
	5420 Series	100
	5520 Series	200
	5720 Series	100
	7520 Series	100
	7720 Series	100
Maximum number of routed PVLANs/E-Trees	5320 Series	10
	5420 Series	10
	5520 Series	10
	5720 Series	100
	7520 Series	50
	7720 Series	50
Maximum number of Layer 3 VSNs per switch See VRF Scaling.	5320 Series	48-port models: 64 16- and 24-port models: 1 local VRF and 23 remote accepted I-SIDs
	5420 Series	64
	5520 Series	256 including mgmt VRF and GRT
	5720 Series	256
	7520 Series	256
	7720 Series	256
Maximum number of FA ISID/VLAN assignments per port	5320 Series	94
	5420 Series	94
	5520 Series	94
	5720 Series	94
	7520 Series	94
	7720 Series	94
Maximum number of IP multicast S,Gs when operating as a BCB (intra-area)	5320 Series	16,000
	5420 Series	16,000
	5520 Series	16,000
	5720 Series	50,000
	7520 Series	50,000
	7720 Series	50,000

Table 2. SPBM Multi-area Maximums
Scaling	5520 Series	5720 Series	7520 Series	7720 Series
SPBM enabled nodes per area	500	500	500	500
SPBM total nodes home + remote	650	650	1,000	1,000
I-SIDs supported on boundary nodes (no local UNI present on device)	2,000	2,000	9,600	9,600
Maximum number of inter-area redistributed Layer 2 VSNs (no local UNI present on Boundary Node)	2,000	2,000	9,600	9,600
Maximum number of IP multicast S,Gs when operating as a boundary node (inter-area)	1,600	1,600	4,800	4,800
DvR host routes redistributed across area boundary	n/a	6,000	13,900	13,900
SPBM multicast-fib entries	10,000	10,000	35,000	35,000

Table 3. Multidimensional Fabric node scale
Device	Node scaling¹	SPBM nodes²	Total unicast BMACs³	Switched UNI endpoints ⁴	Multicast Data I-SIDs⁵
Device	Node scaling¹	SPBM nodes²	Total unicast BMACs³	Switched UNI endpoints ⁴	Ingress BEB	Egress BEB
5320 Series	Enabled	500	500	400	16- and 24-port models: 250 48-port models: 500	1,200
5320 Series	Disabled	350	350	700/800	16- and 24-port models: 250 48-port models: 500	800
5420 Series	Enabled	500 without vIST 340 with vIST	500 without vIST 340 with vIST	400	500	1,200
5420 Series	Disabled	350 without vIST 340 with vIST	350 without vIST 340 with vIST	700/800	500	800
5520 Series		500/800	800	2,700	2,700	4,000
5720 Series		500/1,000	2,000	4,850	4,000	6,000
7520 Series		500/1,000	2,000	12,000	4,000	6,000
7720 Series		500/1,000	2,000	12,000	4,000	6,000
Node scaling—refers to the enabled state of the boot configuration flags spbm-node-scaling command, if applicable. For 5320 Series and 5420 Series using Fabric Extend or vIST, it is a best practice to enable this command. SPBM nodes—refers to the number of supported SPBM enabled nodes, both BEB and BCB. When different, the number is formatted as per area/total per device. For 5420 Series, this number is impacted by vIST. Total unicast BMACs—refers to the total number, both virtual and physical, this node can share services with. This number includes Layer 2 VSNs, Layer 3 VSNs, E-TREE, Multicast, and Transparent Port UNI. For 5420 Series, this number is impacted by vIST. Switched UNI endpoints—refers to the maximum local tagged and untagged endpoints, either manual, RADIUS, or FA-assigned. When different, the number is formatted based on the configuration of the boot config flags macsec command: enabled/disabled. Multicast Data I-SIDs—refers to the maximum Layer 2 or Layer 3, dynamic and static originated data I-SIDs. The overall limits are across all locally configured Layer 2 VSNs

The following table provides numbers for 5320 Series and 5420 Series only, to reflect the impact of the boot configuration flags spbm-node-scaling command.

Table 4. Maximum remote multicast sender nodes and local I-SIDs
Device	Node scaling¹	Total remote multicast sender nodes²	Total local I-SIDs³
5320 Series	Enabled	200	16- and 24-port models: 274 48-port models: 500
5320 Series	Disabled	150	16- and 24-port models: 274 48-port models: 564
5420 Series	Enabled	200	500
5420 Series	Disabled	150	564
Node scaling—refers to the enabled state of the boot configuration flags spbm-node-scaling command. For 5320 Series and 5420 Series using Fabric Extend or vIST, it is a best practice to enable this command. Total remote multicast sender nodes—refers to the total number of nodes that send IP multicast streams that the local BEB receives. This space is shared with unicast BMACs in the preceding table. Documented limits are individual in isolation; introducing vIST clusters or nodes that advertise IP multicast streams decreases the total number of physical nodes in an area. Total local I-SIDs— refers to the total for Layer 2, Layer 3, and Multicast.

Number of I-SIDs Supported for the Number of Configured IS-IS Interfaces and Adjacencies (NNIs)

The number of I-SIDs supported depends on the number of IS-IS interfaces and adjacencies (NNIs) configured.

The following table shows the number of UNI I-SIDs supported per BEB. UNI I-SIDs are used for Layer 2 VSN, Layer 3 VSN, Transparent-UNI, E-Tree, Switched-UNI and S, G for Multicast.


Number of IS-IS interfaces (NNIs)	Product	I-SIDs with vIST configured on the platform	I-SIDs without vIST configured on the platform
4	5320 Series	n/a	500
	5420 Series	564	564
	5520 Series	4,000	4,000
	5720 Series	4,000	4,000
	7520 Series	4,000	4,000
	7720 Series	4,000	4,000
6	5320 Series	n/a	500
	5420 Series	564	564
	5520 Series	3,500	4,000
	5720 Series	3,500	4,000
	7520 Series	4,000	4,000
	7720 Series	4,000	4,000
10	5320 Series	n/a	500
	5420 Series	564	564
	5520 Series	2,900	4,000
	5720 Series	2,900	4,000
	7520 Series	2,900	4,000
	7720 Series	2,900	4,000
20	5320 Series	n/a	500
	5420 Series	564	564
	5520 Series	2,000	4,000
	5720 Series	2,000	4,000
	7520 Series	2,000	4,000
	7720 Series	2,000	4,000
48	5320 Series	n/a	500
	5420 Series	564	564
	5520 Series	1,000	2,000
	5720 Series	1,000	2,000
	7520 Series	1,000	2,000
	7720 Series	1,000	2,000
72	5320 Series	n/a	n/a
	5420 Series	n/a	n/a
	5520 Series	750	1,500
	5720 Series	750	1,500
	7520 Series	750	1,500
	7720 Series	750	1,500
100	5320 Series	n/a	n/a
	5420 Series	n/a	n/a
	5520 Series	550	1,100
	5720 Series	550	1,100
	7520 Series	550	1,100
	7720 Series	550	1,100
128	5320 Series	n/a	n/a
	5420 Series	n/a	n/a
	5520 Series	450	900
	5720 Series	450	900
	7520 Series	450	900
	7720 Series	450	900
250	5320 Series	n/a	n/a
	5420 Series	n/a	n/a
	5520 Series	n/a	n/a
	5720 Series	n/a	n/a
	7520 Series	n/a	n/a
	7720 Series	n/a	n/a

Interoperability Considerations for IS-IS External Metric

BEBs running VOSS 5.0 can advertise routes into IS-IS with the metric type as external. They can also correctly interpret route advertisements with metric type external received by means of IS-IS. In an SPB network with a mix of products running different versions of software releases, you must take care to ensure that turning on the ability to use metric-type external does not cause unintended loss of connectivity.

Note the following before turning on IS-IS external metric if the SPB network has switches running a release prior to VOSS 5.0:

There are no special release or product type implications if the switch does not have IP Shortcuts or Layer 3 VSN enabled. For example, this applies to Layer 2 only BEBs and BCBs.
There are no special release or product type implications if the Layer 3 VSN in which routes are being advertised with a metric-type of external is not configured on the switch.
If a switch running a VOSS release that is prior to VOSS 5.0 but VOSS 4.2.1 or later, it will treat all IS-IS routes as having metric-type internal, regardless of the metric-type (internal or external) used by the advertising BEB in its route advertisement.
Switches running VSP 9000 Series release 4.1.0.0 or later will treat all IS-IS routes as having metric-type internal, regardless of the metric-type (internal or external) used by the advertising BEB in its route advertisement.
Switches running VOSS releases prior to 4.2.1.0 might not correctly install IS-IS routes in a Layer 3 VSN if any routes advertised with metric-type external are advertised in that Layer 3 VSN by other BEBs in the network. Layer 3 VSNs in which there are no routes with an external metric-type will not be impacted. Similar note applies to the GRT.
Switches running VSP 9000 Series releases prior to 4.1.0.0 might not correctly install IS-IS routes in a Layer 3 VSN if any routes advertised with metric-type external are advertised in that Layer 3 VSN by other BEBs in the network. Layer 3 VSNs in which there are no routes with an external metric-type will not be impacted. Similar note applies to GRT.
Switches running any ERS 8800 release might not correctly install IS-IS routes in a Layer 3 VSN if any routes advertised with metric-type external are advertised in that Layer 3 VSN by other BEBs in the network. Layer 3 VSNs in which there are no routes with an external metric-type will not be impacted. Similar note applies to GRT.