On This Page
The gateway can be used in various deployment topologies, each with their particular strength.
The Skyway appliances are connected to the Spine switches of the Fat Tree. This topology requires fewer hops to reach the Skyway, though, on the other hand, the Spine ports are occupied instead of keeping them available for future expansion of the cluster.
The Skyway appliances are connected to the Leaf switches. This topology makes Spine ports available for future expansion, though, on the other hand, the hop count from cluster nodes to the Skyway are not even—there may be nodes with a fewer hop count than others.
The Skyway appliances are connected to a dedicated cell for services (e.g., storage and login services). This topology provides fairness and symmetry among all nodes on all other cells, though, on the other hand, it requires having an additional cell (or "services island").
The Skyway appliances are connected directly to leaf switches on the compute islands. An additional cell (or "service island") is not required.
The clearest advantage of LAG/MLAG is that it is a simple and standard topology. While the topology provides a good load distribution and good resiliency, it is limited in scale. For more information on configuring MLAG, see the following community post.
Please consider the following while implementing LAG/MLAG using Skyway appliances:
There is no Inter Peer Link (IPL) across Skyway appliances.
Skyway-based MLAG cannot be VLAN enabled. Ports are always access.
All Skyway appliances in an MLAG domain will share the same Virtual IP.
Any encapsulation/tunneling must start and terminate at the Ethernet switch
Multiple IP subnets can be configured over the InfiniBand network. In such cases, every IPoIB subnet will be served by dedicated Skyway appliances that are configured in High Availability (HA) Domain.
The specific IP configuration (e.g., Default Gateway, Next Hop Router, and so forth) will have to be configured separately per HA domain of the Skyway appliances.