Cascade system for network units

1. A network stack comprising:

a plurality of network units, wherein each of the plurality of network units comprises a multiplicity of ports for receiving and forwarding addressed data packets, at least two cascade ports, and a switching engine for forwarding received data packets to at least one of the multiplicity of ports in accordance with address data in the data packets;

a first cascade connection comprising a first unidirectional path for data packets composed of links between a first cascade port of a first network unit and a cascade port of a second network unit, wherein the data packets are to flow through the first unidirectional path from the first cascade port of the first network unit to the cascade port of the second network unit; and

a second cascade connection comprising a second unidirectional path for the data packets composed of links between a second cascade port of the first network unit and a cascade port of a third network unit, wherein the second unidirectional path is directed into a direction that is opposite the first unidirectional path, wherein the data packets are to flow through the second unidirectional path from the second cascade port of the first network unit to the cascade port of the third network unit,

wherein each of the data packets which is received at any given port of a given network unit from an external network and is forwarded onto one of the first and the second cascade ports is provided a header source field which, uniquely across the plurality of network units, identifies the given port and the given network unit through which the data packet was received.

2. The network stack according to claim 1 , wherein in a normal mode of operation of each network unit, the respective switching engine directs data packets received at a cascade port and intended for further transmission on the cascade out of the same cascade port, and in a loop-back mode of operation of a network unit, the switching engine directs data packets received at a cascade port and intended for further transmission on the cascade out of a different port and in a changed direction of progress around the stack.

3. The network stack according to claim 2 , wherein each of the network units includes means for detecting an operational failure between that network unit and an adjacent network unit to cause the network unit to enter the loop-back mode.

4. The network stack according to claim 2 , wherein each of the network units is operable in a bypass mode wherein data packets proceeding on the cascade connection and received at one or more of the at least two cascade ports are forwarded from the same port without being redirected by the switching engine.

5. The network stack according to claim 2 , wherein each switching engine is responsive to control data conveyed between the network units on control paths separate from the unidirectional paths.

6. The network stack according to claim 5 , wherein said control paths are constituted by a chain of half-duplex links, each from one network unit to a next network unit and wherein each network unit includes cascade control logic, which responds to control frames on respective links to control the switching engine of the respective network unit.

7. The network stack according to claim 1 , wherein the header source field is a multiple bit binary field of which a first plurality of bits identifying the given port and a second plurality of bits identify the given network unit.

8. The network stack according to claim 1 wherein each data packet which is forwarded onto the cascade connection includes a header destination field for identifying a destination network unit and a port thereon and another field which indicates the validity of the header destination field.

9. The network stack according to claim 8 wherein the header source field and the header destination field having the same format.

10. The network stack according to claim 1 wherein each data packet which is forwarded onto the cascade includes a header portion which indicates which of the network units in the stack have been traversed by the data packet.

11. The network stack according to claim 10 wherein the header portion is a bit mask.

12. A network unit for use in a cascade stack of network units, said network unit comprising:

a multiplicity of ports for receiving and forwarding addressed data packets;

a switching engine for forwarding received data packets to at least one of the multiplicity of ports in accordance with address data in the data packets; and

at least two cascade ports for connection to other network units in the stack, wherein a first cascade port is to form a first cascade connection comprising a first unidirectional path to a cascade port of a second network unit, wherein the data packets are to flow through the first unidirectional path from the first cascade port of the first network unit to the cascade port of the second network unit, and a second cascade port is to form a second cascade connection comprising a second unidirectional path to a cascade port of a third network unit, wherein the second unidirectional path is directed into a direction that is opposite the first unidirectional path, and wherein data packets are to flow through the second unidirectional path from the second cascade port of the first network unit to the cascade port of the third network unit,

wherein said switching engine provides a normal mode wherein the data packets_ received at any of the cascade ports are forwarded from the same port in the same direction of progress and a loop-back mode wherein a data packet received at a cascade port is forwarded from a different cascade port in a different direction of progress, and

wherein for each data packet which is received at any given port of the network unit from an external network and is to be forwarded onto one of the first cascade port and the second cascade port, the network unit is to provide a header source field which, uniquely across the cascade stack of network units, identifies the given port of the network unit.

13. The network unit according to claim 12 wherein the network unit is responsive to control data indicating the operational status of other network units in the stack to determine the mode.

14. The network unit according to claim 12 , wherein the network unit is operable in a bypass mode in which data packets received at one of the first and second cascade ports and intended for further transmission on said cascade are forwarded from the same port without being redirected by the switching engine.

15. The network unit according to claim 12 , wherein the header source field is a multiple bit binary field of which a first plurality of bits identifying the given port and a second plurality of bits identify the network unit.

16. The network unit according to claim 12 , wherein for each data packet which is forwarded onto the cascade connection, the network unit is to provide a header destination field for identifying a destination network unit and a port thereon and another field which indicates the validity of the header destination field.

17. The network unit according to claim 12 , wherein for each data packet which is forwarded onto the cascade, the network unit is to include a header portion which indicates which of the network units in the stack have been traversed by the data packet.

18. The network unit according to claim 17 , wherein the header portion is a bit mask.