Smartjack for fault-testing network segments on Ethernet and other internet protocol network architectures

• US 7,085,238 B2
• Filed: 12/11/2003
• Issued: 08/01/2006
• Est. Priority Date: 12/11/2003
• Status: Active Grant

• Current Assignee: Spirent Communications of Rockville, Inc. (Spirent Communications Incorporated)
• Original Assignee: Spirent Communications of Rockville, Inc. (Spirent Communications Incorporated)
• Inventors: McBeath, Tom
• Primary Examiner(s): Duong, Frank
• Application Number:
  US10/735,129
• Publication Number:
  US 20050144328A1
• Time in Patent Office: 964 Days
• Field of Search: None
• US Class Current: 370/249
• CPC Class Codes: H04L 12/46 Interconnection of networks

Abstract

A fault-testing node for a connectionless data link has at least two opposing communication ports; a soft switch for controlling port-to-port data flow through the device; and an instance of software for modifying packet header information. The node enables loop-back testing by one or more port-to-port data flow paths being switched through activation of the soft switch to loop incoming packets back to the sender of the packets through the device and wherein the instance of software reverses the order of source and destination addresses of data units to insure acceptance of looped data units at the sender station.

Claims

1. A fault-testing node for a connectionless data link comprising:

at least two opposing communication ports;

a soft switch for controlling port-to-port data flow through the device; and

an instance of software modifying header information associated with data units by copying the data from the first field to memory, copying the data from the second field and pasting the data into the first field, and then pasting the data from the memory into the second field;

wherein one or more port-to-port data flow paths are switched by activating the soft switch to loop incoming data units back to the sender of the data units through the device, and wherein the instance of software reverses the order of source and destination addresses of data units to insure acceptance of looped data units at the sender station.

2. The node of claim 1 wherein the connectionless data link is an Ethernet data link, the data units are Ethernet frames, and the source and destination addresses are MAC addresses.

3. The node of claim 1 wherein the connectionless data link is an IP data link, the data units are IP data packets, and the source and destination addresses are IP addresses.

4. The node of claim 1 having two operating modes, a loop-back mode and a pass-through mode.

5. The node of claim 1 further comprising an array of resident fault testing applications and a logging component to create activity and error logs during testing and during normal operation.

6. The node of claim 1 wherein loop-back tests performed include one or a combination of tests returning data for number of bytes sent or received over the link for a specified period, number of packets sent or received over the link for a specified period;

number of CRC errors occurring over a specified period, average packet length of packets sent or received over the link during a specified period, average transmission rate over the link, address identification of the link, and protocol types in operation over the link.

7. The node of claim 1 wherein intrusive tests are performed including Bit-Error-Rate-Testing, testing for throughput between the node and another on-line device, testing for packet delay between any two points on the link, testing for jitter between any two point on the link, and testing for packet loss between any two points on the link.

8. In a fault-testing node for a connectionless data link, the node having at least two opposing communication ports and an instance of software for modifying data unit header information, a method for switching data sets resident in address fields of a data unit enabling loop-back of data units received at the node to the sender of the data units comprising steps of:

(a) copying the data set from a first field to a memory;

(b) copying the data set from a second field;

(c) pasting the data set from the second field into the first field; and

(d) pasting the data set copied to memory in step (a) into the second field.

9. The method of claim 8 wherein in step (a) the first field is a source address field the data set a source IP address of an IP data packet.

10. The method of claim 9 wherein in steps (b) and (c) the second field is a destination address field the data set a destination IP address, which becomes a source IP address when pasted into the source field of the IP data packet.

11. The method of claim 10 wherein in step (d) the data set is a source address, which becomes a destination IP address when pasted into the destination field of the IP data packet.

12. The method of claim 8 wherein in step (a) the first field is a destination address field the data set a destination IP address of an IP data packet.

13. The method of claim 12 wherein in steps (b) and (c) the second field is a source address field the data set a source IP address, which becomes a destination IP address when pasted into the destination field of the IP data packet.

14. The method of claim 13 wherein in step (d) the data set is a destination IP address, which becomes a source IP address when pasted into the source field of the IP data packet.

15. The method of claim 8 wherein in step (a) the first field is a source address field the data set a source machine access code address of an Ethernet data frame.

16. The method of claim 15 wherein in steps (b) and (c) the second field is a destination address field the data set a destination machine access code address, which becomes a source machine access code address when pasted into the source field of the Ethernet data frame.

17. The method of claim 16 wherein in step (d) the data set is a source address, which becomes a destination machine access code address when pasted into the destination field of the Ethernet data frame.

18. The method of claim 8 wherein in step (a) the first field is a destination address field the data set a destination machine access code address of an Ethernet data frame.

19. The method of claim 18 wherein in steps (b) and (c) the second field is a source address field the data set a source machine access code address, which becomes a destination machine access code address when pasted into the destination field of the Ethernet data frame.

20. The method of claim 19 wherein in step (d) the data set is a destination machine access code address, which becomes a source machine access code address when pasted into the source field of the Ethernet data frame.