Notes on Circuit Ports and Circuit GigaStream in Fabric Maps

As mentioned in the pre-requisites section, Circuit ports and Circuit GigaStreams are required for creating Fabric Maps. Refer to the following notes:

■

You cannot specify the Circuit Ports and Circuit GigaStreams that are to be used in a fabric map. You can only define the Circuit Ports and Circuit GigaStreams.

■

Circuit Ports and the Circuit GigaStream for the fabric path are selected as follows:

o

Circuit GigaStreams at the first clusters are selected randomly for efficient load balancing.

o

For hop beyond second hops, previously used Circuit Gigastreams may be selected if ‘Resource Sharing’ is set to enabled mode. This allows to reuse the circuit tunnels previously created. Refer to Share Circuit ID Resource.

■

For Circuit GigaStreams on the Circuit links that connect two clusters, it is recommended to not have more than one ingress GigaStream in any of the devices of the cluster.

■

Do not configure redundant Circuit GigaStream between non leaf-spine clusters as this may lead to various issues such as traffic duplication, source port configuration and other such issues.

Consider the following leaf-spine topology. Fabric map is created between the two leaf nodes and the spine node. The second Circuit GigaStream in the leaf node may be used when the circuit ports are of different speeds.

1

Circuit GigaStreams in Fabric Maps

Notes for Circuit ID

Keep in mind the following points while configuring the Circuit ID:

■

Circuit ID is used internally to pass traffic from one cluster to another. You can configure Circuit ID ranges from 2 to 4000, or set your own custom range, with each topology able to reuse ID ranges (e.g., 2-513) across multiple topologies.

■

Circuit ID allocation is managed globally, beginning from the lower limit of the defined range. This ensures that IDs are allocated efficiently across different topologies. It is allocated automatically.

■

To enable the Circuit ID optimal allocation feature in your currently deployed maps, it is necessary to delete the existing maps. After deletion, create a new map that includes the optimal allocation feature, as it cannot be applied to the existing maps directly.

■

Each cluster can use up to 512 Circuit IDs from the global pool (default range is 2–4000), allowing for 512 unique destination sets per cluster or standalone node. Multiple fabric maps can also be created, each with 512 unique destination sets.

■

Circuit IDs are allocated on a per-hop and per-direction basis.

■

The Circuit ID optimal allocation is not applicable for second-level maps with Fabric Port Group destination.

■

The circuit tunnel is not shared for first-level maps even in Shared mode.