Notes and Considerations
Refer to the following notes and considerations:
|
■
|
The multi-path leaf and spine architecture is only supported in an out-of-band cluster. |
|
■
|
The spine link GigaStream must be of type stack. Stack GigaStream carry bi-directional traffic. |
|
■
|
All spine link GigaStream must have the same parameters, such as the same hash value and failover mode. |
|
■
|
Once a spine link is configured, editing of GigaStream parameters is not supported, except for editing the comment. |
|
■
|
Adding a new node to an existing leaf-spine topology is not supported. If you need to add a new node, ensure that you remove the existing configurations and reconfigure them for the new topology. |
|
■
|
GigaStream must be configured before spine links are configured. |
|
■
|
Once a GigaStream is configured in a spine link, it cannot be deleted. To delete a spine link, the stack links must first be deleted. |
|
■
|
A spine link cannot be deleted if a map is using the spine link. |
|
■
|
A spine link cannot be created if a map is using the GigaStream. |
The number of spine and leaf nodes is not limited. The ratio of spine and leaf nodes are determined by the cluster traffic needed between the leaf nodes. Larger topologies have the same restrictions as the GigaVUE‑OS as follows:
|
■
|
the total number of nodes in a cluster, for example, 32 |
|
■
|
the number of links in a GigaStream (which depends on the GigaVUE node and line card or module, for example, the PRT-HC0-X24 module on GigaVUE‑HC2 can have 24 stack GigaStream) |