# US 2013/0111048 A1 · Full mesh optimization for spanning tree protocol

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0111048 A1
- Document ID: US20130111048A1
- Status: Published application
- Kind: A1
- Application number: 13/007,977
- Filed: 2011-01-17
- Published: 2013-05-02
- Earliest claimed: 2004-07-12
- Assignees: Oracle International Corporation
- Inventors: Xiaoming Tong; Nakul Pratap Saraiya
- Web page: https://patentgrep.com/patent/US20130111048A1

## CPC

- H04L 12/462: {LAN interconnection over a bridge based backbone}
- H04L 45/48: Routing tree calculation
- H04L 45/76: Routing in software-defined topologies, e.g. routing between virtual machines
- H04L 49/602: {Multilayer or multiprotocol switching, e.g. IP switching}
- H04L 49/354: for supporting virtual local area networks [VLAN]
- H04L 49/357: {Fibre channel switches}
- H04Q 2213/13056: Routines, finite state machines
- H04Q 2213/13106: Microprocessor, CPU
- H04Q 2213/13204: Protocols
- H04Q 2213/13389: LAN, internet
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)

## Abstract

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.

## Claims

### Claim 1

(canceled)

### Claim 2

(canceled)

### Claim 3

(canceled)

### Claim 4

(canceled)

### Claim 5

(canceled)

### Claim 6

(canceled)

### Claim 7

(canceled)

### Claim 8

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;
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.

### Claim 9 (depends on 8)

The method of claim 8, wherein each internal port is a fabric-backplane enterprise server port that is directly connected to another fabric-backplane enterprise server.

### Claim 10 (depends on 8)

The method of claim 8, 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.

### Claim 11 (depends on 10)

The method of claim 10, wherein the device is a switch.

### Claim 12 (depends on 8)

The method of claim 8, 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.

### Claim 13 (depends on 12)

The method of claim 12, wherein the device is a server.

### Claim 14

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 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.

### Claim 15 (depends on 14)

The system of claim 14, wherein each internal port is a fabric-backplane enterprise server port that is directly connected to another fabric-backplane enterprise server.

### Claim 16 (depends on 14)

The system of claim 14, 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.

### Claim 17 (depends on 16)

The system of claim 16, wherein the device is a switch.

### Claim 18 (depends on 14)

The system of claim 14, 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.

### Claim 19 (depends on 18)

The system of claim 18, wherein the device is a server.

### Claim 20

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;
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.

### Claim 21 (depends on 20)

The computer-readable memory device of claim 20, wherein each internal port is a fabric-backplane enterprise server port that is directly connected to another fabric-backplane enterprise server.

### Claim 22 (depends on 20)

The computer-readable memory device of claim 20, 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.

### Claim 23 (depends on 22)

The computer-readable memory device of claim 22, wherein the device is a switch.

### Claim 24 (depends on 20)

The computer-readable memory device of claim 20, 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.

### Claim 25 (depends on 24)

The computer-readable memory device of claim 24, wherein the device is a server.
