Full mesh optimization for spanning tree protocol
An optimized spanning tree protocol (OSTP) minimizes latency and provides high throughput in a full-mesh portion of a network, and is compatible with external networks where a standard spanning tree protocol is used. The OSTP enables traffic traversing the full-mesh portion to take a shortest path from source to destination through use of full-mesh connectivity. In some embodiments, a cluster includes a plurality of servers connected in a full mesh, and the OSTP is used on internal ports of the servers. In some embodiments, the OSTP is configured on a per-VLAN basis. In some embodiments, the servers exchange special messages enabling determination of full-mesh connectivity. In further embodiments, sending of the special messages is suppressed on certain port types, such as external ports. In some embodiments, determination of the full-mesh connectivity disables use of a standard spanning tree protocol and/or enables use of OSTP on the full-mesh portion.
1. A method comprising:
clustering a plurality of multi-chassis fabric-backplane enterprise servers into a full-mesh topology, the clustered plurality comprising a full-mesh enterprise server cluster providing one or more Virtual Local Area Networks (VLANs) therein;
for each port of the full-mesh enterprise server cluster, identifying a type of the port as being a particular one of a set of port types including internal port, external port, and edge port, the external port and edge port types being non-internal ports of the full-mesh enterprise server cluster and wherein each edge port is a fabric-backplane enterprise server port that is connected to a device that is not a fabric-backplane enterprise server;
within the full-mesh enterprise server cluster, for each VLAN, forwarding packets received from non-internal ports to all ports of the VLAN; and
within the full-mesh enterprise server cluster, for each VLAN, forwarding packets received from internal ports to all non-internal ports of the VLAN as per a spanning tree protocol.
2. The method of claim 1 , wherein each internal port is a fabric-backplane enterprise server port that is directly connected to another fabric-backplane enterprise server.
3. The method of claim 1 , wherein each external port is a fabric-backplane enterprise server port that is connected to a device external to the full-mesh enterprise server cluster.
4. The method of claim 3 , wherein the device is a switch.
5. The method of claim 1 , wherein the device is a server.
6. A system comprising:
a plurality of multi-chassis fabric-backplane enterprise servers clustered into a full-mesh topology, the clustered plurality comprising a full-mesh enterprise server cluster providing one or more Virtual Local Area Networks (VLANs) therein, each port of the full-mesh enterprise server cluster identified by a type of the port as being a particular one of a set of port types including internal port, external port, and edge port, the external port and edge port types being non-internal ports of the full-mesh enterprise server cluster wherein each edge port is a fabric-backplane enterprise server port that is connected to a device that is not a fabric-backplane enterprise server and wherein within the full-mesh enterprise server cluster, for each VLAN, forwarding packets received from non-internal ports to all ports of the VLAN and within the full-mesh enterprise server cluster, for each VLAN, forwarding packets received from internal ports to all non-internal ports of the VLAN as per a spanning tree protocol.
7. The system of claim 6 , wherein each internal port is a fabric-backplane enterprise server port that is directly connected to another fabric-backplane enterprise server.
8. The system of claim 6 , wherein each external port is a fabric-backplane enterprise server port that is connected to a device external to the full-mesh enterprise server cluster.
9. The system of claim 8 , wherein the device is a switch.
10. The system of claim 6 , wherein the device is a server.
11. A computer-readable memory device having stored therein a set of instructions which, when executed by a processor cause the processor to manage a full-mesh enterprise server cluster by:
clustering a plurality of multi-chassis fabric-backplane enterprise servers into a full-mesh topology, the clustered plurality comprising the full-mesh enterprise server cluster providing one or more Virtual Local Area Networks (VLANs) therein;
for each port of the full-mesh enterprise server cluster, identifying a type of the port as being a particular one of a set of port types including internal port, external port, and edge port, the external port and edge port types being non-internal ports of the full-mesh enterprise server cluster and wherein each edge port is a fabric-backplane enterprise server port that is connected to a device that is not a fabric-backplane enterprise server;
within the full-mesh enterprise server cluster, for each VLAN, forwarding packets received from non-internal ports to all ports of the VLAN; and
within the full-mesh enterprise server cluster, for each VLAN, forwarding packets received from internal ports to all non-internal ports of the VLAN as per a spanning tree protocol.
12. The computer-readable memory device of claim 11 , wherein each internal port is a fabric-backplane enterprise server port that is directly connected to another fabric-backplane enterprise server.
13. The computer-readable memory device of claim 11 , wherein each external port is a fabric-backplane enterprise server port that is connected to a device external to the full-mesh enterprise server cluster.
14. The computer-readable memory device of claim 13 , wherein the device is a switch.
15. The computer-readable memory device of claim 11 , wherein the device is a server.