Abstract: One embodiment disclosed relates to a method of cost determination for paths between switches in a mesh. A set of paths between each pair of the mesh switches is defined, and start-up costs for the paths are calculated. The costs for the previously defined paths are subsequently recalculated using a directed cost protocol. The directed cost protocol may include generating at a first switch a cost packet with path information associated with a specific path, and unlasting the cost packet via the specific path to a second switch.

Abstract: One embodiment disclosed relates to a switching system. The switching system includes first, second, and third sets of switches. The first set of switches is configured with a first instance of meshing software such that the switches in the first set are members of a first mesh domain. The second set of switches is configured with a second instance of the meshing software such that the switches in the second set are members of a second mesh domain. The third set of switches is configured with both the first and second instances of the meshing software such that the switches in the third set are members of both the first and second mesh domains. Another embodiment disclosed relates to a packet switch apparatus executing multiple instances of meshing software. Another embodiment disclosed relates to a method of configuring a switching system having multiple mesh domains.

Abstract: One embodiment disclosed relates to a method of handling oversubscribed ports between switches. An oversubscribed port is detected at a detecting switch. A set of paths exiting at the oversubscribed port is selected for retagging, and tags for the set of paths are invalidated. When packets with the invalidated tags are received, the received packets are retagged with a tag associated with a detour path. Another embodiment disclosed relates to a packet switch apparatus with oversubscribed port handling capability for use in a switching mesh. Another embodiment disclosed relates to a switching mesh including a capability to handle oversubscribed ports between switches.

Abstract: One embodiment disclosed relates to a method of handling link failures between switches. A failed link is detected at a detecting switch. The detecting switch determines a set of path tags whose paths are affected by the failed link. Subsequently, when packets are received with one of the path tags affected by the failed link, those packets are retagged with a detour path tag associated with a detour path circumventing the failed link. Another embodiment disclosed relates to a packet switch apparatus with link failure handling capability for use in a switching mesh. Another embodiment disclosed relates to a switching mesh including a capability to handle link failures.

Abstract: One embodiment relates to a method by a switch of tracing a broadcast path from the switch through a group of switches. A broadcast traceroute packet is issued with a first hop entry from each port within the broadcast path. Trace hop packets are received from hop switches within the broadcast path, and trace complete packets are received from end switches within the broadcast path. Other embodiments are also disclosed.

Abstract: An apparatus in one example comprises a first mesh network switch, of a plurality of mesh network switches, that employs mesh connection information of one or more mesh network switches of the plurality of mesh network switches to determine a plurality of paths between the first mesh network switch and a second mesh network switch, of the plurality of mesh network switches, before a selection of one path of the plurality of paths for transmission of one or more packets from the first mesh network switch to the second mesh network switch.

Abstract: One embodiment disclosed relates to a method of automated path tracing from an original mesh switch through a switching mesh to a specified destination. A mesh traceroute packet to the specified destination is built. The mesh traceroute packet is transmitted via an exit port associated with the specified destination and the returned packet is received. Another embodiment disclosed relates to a method of responding to receipt of a mesh traceroute packet during an automated path tracing. The mesh traceroute packet is received at a switch. A hop entry is appended to the mesh traceroute packet by the switch.

Abstract: One embodiment disclosed relates to a method of broadcasting packets through a network of switches. A packet is received to be broadcast through the network of switches. A broadcast path is selected from a plurality of generated broadcast paths. A broadcast path tag associated with the selected broadcast path is created and inserted into the packet. A determination is made of the port(s) by which to forward the packet, and the packet is transmitted via the port(s) to next switch(es) in accordance with the selected broadcast path.

Abstract: One embodiment disclosed relates to a switching system. The switching system includes first, second, and third sets of switches. The first set of switches is configured with a first instance of meshing software such that the switches in the first set are members of a first mesh domain. The second set of switches is configured with a second instance of the meshing software such that the switches in the second set are members of a second mesh domain. The third set of switches is configured with both the first and second instances of the meshing software such that the switches in the third set are members of both the first and second mesh domains. Another embodiment disclosed relates to a packet switch apparatus executing multiple instances of meshing software. Another embodiment disclosed relates to a method of configuring a switching system having multiple mesh domains.

Abstract: An apparatus in one example comprises a first mesh network switch that directs a path verification request along a specific path to a second mesh network switch to test operability of the specific path.

Abstract: One embodiment disclosed relates to a switching system. The switching system includes first, second, and third sets of switches. The first set of switches is configured with a first instance of meshing software such that the switches in the first set are members of a first mesh domain. The second set of switches is configured with a second instance of the meshing software such that the switches in the second set are members of a second mesh domain. The third set of switches is configured with both the first and second instances of the meshing software such that the switches in the third set are members of both the first and second mesh domains. Another embodiment disclosed relates to a packet switch apparatus executing multiple instances of meshing software. Another embodiment disclosed relates to a method of configuring a switching system having multiple mesh domains.

Abstract: One embodiment disclosed relates to a method of load balancing traffic in a switching mesh. A packet is received at a switch of the mesh. A MAC destination address is gathered from the packet. An entry in a MAC address table is found with the MAC destination address, and a switch identifier associated with the MAC destination address is obtained. An entry in a switch table is found with the switch identifier, and data associated with the switch identifier is obtained. A hash function is used on field data from the packet to generate a hash value, and the hash value and the associated data are used to generate an index value. An entry in the tag table is found with the index value, and a path tag associated with the index value is obtained. The path tag is inserted into the packet. The path tags may be weighted.

Abstract: One embodiment relates to a method by a switch of tracing a broadcast path from the switch through a group of switches. A broadcast traceroute packet is issued with a first hop entry from each port within the broadcast path. Trace hop packets are received from hop switches within the broadcast path, and trace complete packets are received from end switches within the broadcast path. Other embodiments are also disclosed.

Abstract: One embodiment disclosed relates to a method of handling link failures between switches. A failed link is detected at a detecting switch. The detecting switch determines a set of path tags whose paths are affected by the failed link. Subsequently, when packets are received with one of the path tags affected by the failed link, those packets are retagged with a detour path tag associated with a detour path circumventing the failed link. Another embodiment disclosed relates to a packet switch apparatus with link failure handling capability for use in a switching mesh. Another embodiment disclosed relates to a switching mesh including a capability to handle link failures.

Abstract: An apparatus in one example comprises a first mesh network switch, of a plurality of mesh network switches, that employs mesh connection information of one or more mesh network switches of the plurality of mesh network switches to determine a plurality of paths between the first mesh network switch and a second mesh network switch, of the plurality of mesh network switches, before a selection of one path of the plurality of paths for transmission of one or more packets from the first mesh network switch to the second mesh network switch.

Abstract: An apparatus in one example comprises a first mesh network switch that directs a path verification request along a specific path to a second mesh network switch to test operability of the specific path.

Abstract: One embodiment disclosed relates to a switching system. The switching system includes first, second, and third sets of switches. The first set of switches is configured with a first instance of meshing software such that the switches in the first set are members of a first mesh domain. The second set of switches is configured with a second instance of the meshing software such that the switches in the second set are members of a second mesh domain. The third set of switches is configured with both the first and second instances of the meshing software such that the switches in the third set are members of both the first and second mesh domains. Another embodiment disclosed relates to a packet switch apparatus executing multiple instances of meshing software. Another embodiment disclosed relates to a method of configuring a switching system having multiple mesh domains.

Abstract: One embodiment disclosed relates to a method of handling oversubscribed ports between switches. An oversubscribed port is detected at a detecting switch. A set of paths exiting at the oversubscribed port is selected for retagging, and tags for the set of paths are invalidated. When packets with the invalidated tags are received, the received packets are retagged with a tag associated with a detour path. Another embodiment disclosed relates to a packet switch apparatus with oversubscribed port handling capability for use in a switching mesh. Another embodiment disclosed relates to a switching mesh including a capability to handle oversubscribed ports between switches.

Abstract: One embodiment disclosed relates to a method of load balancing traffic in a switching mesh. A packet is received at a switch of the mesh. A MAC destination address is gathered from the packet. An entry in a MAC address table is found with the MAC destination address, and a switch identifier associated with the MAC destination address is obtained. An entry in a switch table is found with the switch identifier, and data associated with the switch identifier is obtained. A hash function is used on field data from the packet to generate a hash value, and the hash value and the associated data are used to generate an index value. An entry in the tag table is found with the index value, and a path tag associated with the index value is obtained. The path tag is inserted into the packet. The path tags may be weighted.

Abstract: One embodiment disclosed relates to a method of cost determination for paths between switches in a mesh. A set of paths between each pair of the mesh switches is defined, and start-up costs for the paths are calculated. The costs for the previously defined paths are subsequently recalculated using a directed cost protocol. The directed cost protocol may include generating at a first switch a cost packet with path information associated with a specific path, and unlasting the cost packet via the specific path to a second switch.