Path detection in trill networks

• US 8,634,308 B2
• Filed: 11/19/2010
• Issued: 01/21/2014
• Est. Priority Date: 06/02/2010
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Vobbilisetty, Suresh, Koganti, Phanidhar, Mahajan, Arun
• Primary Examiner(s): HAILE, AWET A
• Application Number:
  US12/950,968
• Publication Number:
  US 20110299406A1
• Time in Patent Office: 1,159 Days
• Field of Search: 370/224, 370/241, 370/242, 370/244, 370/248, 370/249, 370/250, 370/252, 370/401, 709/224
• US Class Current: 370/248
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

One embodiment of the present invention provides a system for detecting a path between two nodes. During operation, the system transmits a network-testing request frame, which includes a time-to-live (TTL) field within a Transparent Interconnection of Lots of Links (TRILL) header, from a source node to a destination node. In response to receiving a network-testing response frame sent from an intermediate node, the system increments the TTL value by 1 and re-transmits the network-testing frame to the destination node. In response to receiving a network-testing response frame sent from the destination node, the system determines a path between the source node and the destination node. The network-testing request or response frames is not processed on an Internet Protocol (IP) layer.

Claims

1. A method, comprising:

transmitting a network-testing request frame, which includes a time-to-live (TTL) field within a Transparent Interconnection of Lots of Links (TRILL) header, from a source node to a destination node;

in response to receiving a network-testing response frame sent from an intermediate node, incrementing a value of the TTL field within the TRILL header by 1 and re-transmitting the network-testing request frame to the destination node; and

in response to receiving another network-testing response frame sent from the destination node, determining a path between the source node and the destination node;

wherein the network-testing request frame or the network-testing response frame is not processed on an Internet Protocol (IP) layer.

2. The method of claim 1, wherein the network-testing request frame or the network-testing response frame includes an Ethernet frame.

3. The method of claim 2, wherein the Ethernet frame includes a field which indicates that the Ethernet frame is an Operation, Administration, and Management (OAM) frame.

4. The method of claim 1, further comprising executing a network-testing command which includes an address of the destination node.

5. The method of claim 1, wherein the network-testing request frame or the network-testing response frame is a TRILL frame.

6. The method of claim 5, wherein the network-testing request frame or the network-testing response frame includes the TRILL header comprising an address of the destination node in an outer media access control (MAC) destination address (DA) field.

7. The method of claim 5, wherein the network-testing request frame or the network-testing response frame includes the TRILL header and an encapsulated Ethernet frame, and wherein an Ethertype field of the encapsulated Ethernet frame specifies that the network-testing request frame or the network-testing response frame is a TRILL OAM frame.

8. The method of claim 7, wherein the encapsulated Ethernet frame includes a TRILL OAM header field.

9. The method of claim 8, wherein the TRILL OAM header field includes an operation code (opcode) field, and wherein the opcode field specifies whether the TRILL OAM frame is the network-testing request frame or the network-testing response frame.

10. The method of claim 8, wherein the TRILL OAM header field includes a transaction identifier, and wherein the network-testing request frame and the corresponding network-testing response frame have the same transaction identifier.

11. The method of claim 8, wherein the TRILL OAM header field includes a flag field, and wherein the flag field of the network-testing response frame can be encoded to indicate whether the network-testing response frame is sent from the intermediate node or the destination node.

12. The method of claim 1, wherein the network-testing response frame sent from the intermediate node includes route information to a next hop, and wherein the route information includes an address and a port number of the next hop.

13. The method of claim 1, wherein the network-testing response frame or the network-testing request frame is transmitted as a payload of an Internet Protocol (IP) packet or a Fibre Channel over Ethernet (FCoE) packet, wherein the network-testing response frame or the network-testing request frame includes an inner Ethernet MAC frame, and wherein an Ethertype field within the inner Ethernet MAC frame is set as IP or FCoE.

14. The method of claim 13, wherein the Ethertype field is set as IP, and wherein the network-testing response frame or the network-testing request frame is included in a payload of a transmission control protocol (TCP) frame or a user datagram protocol (UDP) frame.

15. The method of claim 13, wherein the Ethertype field is set as FCoE, and wherein the network-testing response frame or the network-testing request frame is included in a payload of the FCoE frame.

16. A switch, comprising:

a request-transmission mechanism configured to transmit a network-testing request frame, which includes a time-to-live (TTL) field within a Transparent Interconnection of Lots of Links (TRILL) header, from a source node to a destination node;

a mechanism configured to, in response to receiving a network-testing response frame sent from an intermediate node, increment a value of the TTL field within the TRILL header by 1 and re-transmitting the network-testing request frame to the destination node; and

a determination mechanism configured to, in response to receiving another network-testing response frame sent from the destination node, determine a path between the source node and the destination node;

wherein the network-testing request frame or the network-testing response frame is not processed on an Internet Protocol (IP) layer.

17. The switch of claim 16, wherein the network-testing request frame or the network-testing response frame includes an Ethernet frame.

18. The switch of claim 17, wherein the Ethernet frame includes a field which indicates that the Ethernet frame is an Operation, Administration, and Management (OAM) frame.

19. The switch of claim 16, further comprising a command-execution mechanism configured to execute a network-testing command which includes an address of the destination node.

20. The switch of claim 16, wherein the network-testing request frame or the network-testing response frame is a TRILL frame.

21. The switch of claim 20, wherein the network-testing request frame or the network-testing response frame includes the TRILL header comprising an address of the destination node in an outer media access control (MAC) destination address (DA) field.

22. The switch of claim 20, wherein the network-testing request frame or the network-testing response frame includes the TRILL header and an encapsulated Ethernet frame, and wherein an Ethertype field of the encapsulated Ethernet frame specifies that the network-testing request frame or the network-testing response frame is a TRILL OAM frame.

23. The switch of claim 22, wherein the encapsulated Ethernet frame includes a TRILL OAM header field.

24. The switch of claim 23, wherein the TRILL OAM header field includes an operation code (opcode) field, and wherein the opcode field specifies whether the TRILL OAM frame is a network-testing request frame or a network-testing response frame.

25. The switch of claim 23, wherein the TRILL OAM header field includes a transaction identifier, and wherein the network-testing request frame and the corresponding network-testing response frame have the same transaction identifier.

26. The switch of claim 23, wherein the TRILL OAM header field includes a flag field, and wherein the flag field of the network-testing response frame can be encoded to indicate whether the network-testing response frame is sent from an intermediate node or the destination node.

27. The switch of claim 16, wherein the network-testing response frame sent from the intermediate node includes route information to a next hop, and wherein the route information includes an address and a port number of the next hop.

28. The switch of claim 16, wherein the network-testing response frame or the network-testing request frame is transmitted as a payload of an Internet Protocol (IP) packet or a Fibre Channel over Ethernet (FCoE) packet, wherein the network-testing response frame or the network-testing request frame includes an inner Ethernet MAC frame, and wherein an Ethertype field within the inner Ethernet MAC frame is set as IP or FCoE.

29. The switch of claim 28, wherein the Ethertype field is set as IP, and wherein the network-testing response frame or the network-testing request frame is included in a payload of a TCP frame or a UDP frame.

30. The switch of claim 28, wherein the Ethertype field is set as FCoE, and wherein the network-testing response frame or the network-testing request frame is included in a payload of the TCP or UDP frame.

31. An apparatus, comprising:

means for transmitting a network-testing request frame, which includes a time-to-live (TTL) field within a Transparent Interconnection of Lots of Links (TRILL) header, from a source node to a destination node;

means for, in response to receiving a network-testing response frame sent from an intermediate node, incrementing a value of the TTL field within the TRILL header by 1 and re-transmitting the network-testing frame to the destination node; and

means for, in response to receiving another network-testing response frame sent from the destination node, determining a path between the source node and the destination node;

wherein the network-testing request frame or the network-testing response frame is not processed on an Internet Protocol (IP) layer.