Method for testing data path of peripheral server devices

• US 6,618,360 B1
• Filed: 06/15/1999
• Issued: 09/09/2003
• Est. Priority Date: 06/15/1999
• Status: Expired due to Term

• Current Assignee: QNAP Systems Incorporated
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Bueb, Patrick A., Scoville, Dean L.
• Primary Examiner(s): Chin, Wellington
• Assistant Examiner(s): SCHULTZ, WILLIAM C
• Application Number:
  US09/333,362
• Time in Patent Office: 1,547 Days
• Field of Search: 370/229, 370/235, 370/241, 370/242, 370/243, 370/244, 370/245, 370/246, 370/247, 370/248, 370/249, 370/250, 370/251, 370/253, 709/224
• US Class Current: 370/248
• CPC Class Codes: H04L 43/50 Testing arrangements

Abstract

A method for testing a data path of a server operably connected between at least one peripheral device and at least one client device via a network includes independently testing one of a peripheral interface portion of the data path and a network interface portion of the data path, and generating a status report indicating the result of the test.

Claims

1. A method for testing a data path of a server operably connected between at least one peripheral device and at least one client device via a network, the data path being adapted to transmit data between the peripheral device and the network as requested by the client device, said method comprising the steps of:

independently testing the operating performance characteristics of one of a peripheral interface portion of the data path and a network interface portion of the data path, including testing to determine if the rate at which the server received data were faster than the rate at which it could transmit the data and thereby determine the existence of any bottleneck in a portion of the data path; and

generating a status report indicating a result of said testing.

2. The method as defined in claim 1 wherein prior to said testing step said method further comprises the steps of:

opening at least one test connection between the network and the server; and

establishing at least one data connection between the network and the server.

3. The method as defined in claim 2 wherein said step of opening at least one test connection includes the steps of:

sending a signal to one of a plurality of connections of a test port provided on the server, requesting that said at least one test connection be opened; and

opening said at least one test connection through at least one of said plurality of connections of said test port when said one of said plurality of connections of said test port is available, and issuing a response to the network indicating that said test connection could not be opened and disconnecting communication with the network after issuing said response when said at least one of said plurality of connections of said test port is not available.

4. The method as defined in claim 3 wherein the server disconnects communication with the network without issuing said response when an error prevents the server from issuing said response.

5. The method as defined in claim 3 wherein said step of opening at least one test connection further includes the steps of;

separately determining whether each of at least one command issued by the at least one client device through said opened test connection is valid; and

processing each said valid command, and generating a response indicating receipt of an invalid command for each invalid command received by the server.

6. The method as defined in claim 2 wherein said step of establishing a data connection includes the steps of:

sending a signal to a selected one of a plurality of data ports provided on the server, requesting that said data connection be established through said selected data port;

establishing said data connection when the server determines that said selected data port is available, and issuing a response to the network indicating that said data connection could not be opened and closing communication with the network when the server determines that said selected data port is not available; and

setting a maximum segment size of data to be sent through said established data connection after establishing said data connection.

7. The method as defined in claim 6 wherein the server closes communication with the network without issuing said response when an error prevents the server from issuing said response.

8. The method as defined in claim 2 wherein said step of testing said peripheral interface portion of the data path includes the steps of:

issuing at least one setup command to the server to prepare the server for testing said peripheral interface portion;

sending a test command to the server;

determining whether said test command is valid; and

testing said peripheral interface portion of the data path as specified by said test command when said test command is determined to be valid by the server.

9. The method as defined in claim 8 wherein said testing said peripheral interface portion includes transmitting test data generated by the at least one peripheral device to the server and measuring the amount of time required for the server to receive a specified number of bytes of said test data from the peripheral device.

10. The method as defined in claim 9 wherein said test data transmitted from the peripheral device to the server is discarded by the server once said test data are received by the server.

11. The method as defined in claim 8 wherein said at least one setup command is sent from the network to the server via said at least one opened data connection, said test command is sent from the network to the server via said at least one opened test connection, and said status report is sent by the server to network also via said opened test connection.

12. The method as defined in claim 11 wherein said test connection is opened through at least one connection of a plurality of connections in a test port provided on said network interface portion of the server, and said data connection is established through at least one data port provided on said network interface portion of the server.

13. The method as defined in claim 8 wherein the server cancels said step of testing said peripheral interface portion when the network issues a command to the server to cancel said testing of said peripheral interface portion.

14. The method as defined in claim 13 wherein said cancel command is issued to the server via said at least one test connection.

17. The method as defined in claim 8 wherein the server generates said status report at any time after said step of opening said at least one data connection, when the network issues a command to the server to generate said status report.

18. The method as defined in claim 17 wherein said command to generate said status report is issued to the server via said at least one test connection.

19. The method as defined in claim 8 wherein said testing said peripheral interface portion includes measuring a speed at which the server opens and closes connections a specified number of times between the server and the at least one peripheral device.

20. The method as defined in claim 19 wherein said connections are multiple logical channel connections.

21. The method as defined in claim 2 wherein said step of testing said network interface portion of the data path comprises the steps of:

issuing at least one setup command to the server to prepare the server for testing said network interface portion;

sending a test command to the server;

determining whether said test command is valid; and

testing said network interface portion of the data path as specified by said test command when said test command is determined to be valid by the server.

22. The method as defined in claim 21 wherein said testing said network interface portion includes transmitting test data generated by the server to the network and measuring the amount of time required for the network to receive a specified number of bytes of said test data from the server device.

23. The method as defined in claim 21 wherein said at least one setup command is sent from the network to the server via said at least one opened data connection, said test command is sent from the network to the server via said at least one opened test connection, and said status report is sent by the server to the network also via said opened test connection.

24. The method as defined in claim 23 wherein said test connection is opened through at least one connection of a plurality of connections in a test port provided on said network interface portion of the server, and said data connection is established through at least one data port provided on said network interface portion of the server.

25. The method as defined in claim 21 wherein the server cancels said step of testing said network interface portion when the network issues a command to the server to cancel said testing of said network interface portion.

26. The method as defined in claim 25 wherein said cancel command is issued to the server via said at least one test connection.

29. The method as defined in claim 21 wherein the server generates said status report at any time after said step of opening said at least one data connection, when the network issues a command to the server to generate said status report.

30. The method as defined in claim 29 wherein said command to generate said status report is issued to the server via said at least one test connection.

15. A method for testing a data path of a server operably connected between at least one peripheral device and at least one client device via a network, the data path being adapted to transmit data between the peripheral device and the network as requested by the client device, said method comprising the steps of:

independently testing one of a peripheral interface portion of the data path and a network interface portion of the data path by opening at least one test connection between the network and the server; and

establishing at least one data connection between the network and the server; and

generating a status report indicating a result of said test;

wherein said step of testing said peripheral interface portion of the data path includes the steps of;

issuing at least one setup command to the server to prepare the server for testing said peripheral interface portion;

sending a test command to the server;

determining whether said test command is valid; and

testing said peripheral interface portion of the data path as specified by said test command when said test command is determined to be valid by the server;

and wherein the server resets said step of testing said peripheral interface portion when the network issues a command to the server to reset said testing of said peripheral interface portion.

16. The method as defined in claim 15 wherein said command to reset is issued to the server via said at least one test connection.

27. A method for testing a data path of a server operably connected between at least one peripheral device and at least one client device via a network, the data path being adapted to transmit data between the peripheral device and the network as requested by the client device, said method comprising the steps of:

independently testing one of a peripheral interface portion of the data path and a network interface portion of the data path by opening at least one test connection between the network and the server; and

establishing at least one data connection between the network and the server; and

generating a status report indicating a result of said test;

wherein said step of testing said network interface portion of the data path comprises the steps of;

issuing at least one setup command to the server to prepare the server for testing said network interface portion;

sending a test command to the server;

determining whether said test command is valid; and

testing said network interface portion of the data path as specified by said test command when said test command is determined to be valid by the server;

and wherein the server resets said step of testing said network interface portion when the network issues a command to the server to reset said testing of said network interface portion.

28. The method as defined in claim 27 wherein said command to reset is issued to the server via said at least one test connection.

31. A peripheral server operably connected between at least one peripheral and at least client via a network for transmitting data between the peripheral and the client, said server comprising:

a network interface adapted to connect the server to the network for transmitting data between the server and the network;

a peripheral interface adapted to connect the server to the at least one peripheral for transmitting data between the server and the peripheral;

at least one data path connected between said network interface and said peripheral interface for transmitting data between the at least one peripheral and the at least one client; and

a firmware provided in said at least one data path and programmed to independently test a peripheral interface portion and a network interface portion of said data path, and to determine if the rate at which the server received data were faster than the rate at which it could transmit the data and thereby determine the existence of any bottleneck in a portion of the data path and to generate a status report indicating the result of said tests, in response to corresponding test commands received from the at least one client.

34. The server as defined in claim 31 further including at least one test connection for receiving said test commands and sending said status report to the client, and at least one data port for transmitting data between the server and the network.

35. The server as defined in claim 34 wherein said firmware generates said status report automatically at a conclusion of said test, and when a status report command is received from the at least one client via said test connection with respect to a specified data port.

37. The server as defined in claim 34 wherein said firmware is further programmed to change a maximum segment size of data to be transferred through the network interface and the peripheral interface in accordance with a maximum segment size command received from the at least one client with respect to a specified data port.

38. The server as defined in claim 34 wherein said firmware is further programmed to cancel a currently running said test and generate said status report with respect to a specified data port when a cancel command is received from the at least one client to cancel said test in connection with said specified data port.

40. The server as defined in claim 34 wherein said firmware measures the amount of time required for said server to receive a specified number of bytes of data from the at least one peripheral via said peripheral interface when said peripheral interface portion is being tested.

41. The server as defined in claim 34 wherein said firmware generates a specified number of bytes of test data and sends said test data on said network interface to the network when said network interface portion is being tested.

42. The server as defined in claim 34 wherein said firmware measures a speed at which said peripheral network portion repeatedly opens and closes logical connections with the at least one peripheral, when said peripheral interface portion is being tested.

43. The server as defined in claim 34 wherein said server includes a plurality of said test connections, and said firmware is programmed to receive a plurality of instructions via said test connections and execute said instructions while said peripheral interface portion and said network interface portion are independently being tested.

32. A peripheral server operably connected between at least one peripheral and at least one client via a network for transmitting data between the peripheral and the client, said server comprising:

a network interface adapted to connect the server to the network for transmitting data between the server and the network;

a peripheral interface adapted to connect the server to the at least one peripheral for transmitting data between the server and the peripheral;

at least one data path connected between said network interface and said peripheral interface for transmitting data between the at least one peripheral and the at least one client; and

a firmware provided in said at least one data path and programmed to independently test a peripheral interface portion and a network interface portion of said data path and to generate a status report indicating the result of said test, in response to corresponding test commands received from the at least one client;

wherein said network interface is a TCP interface and/or SPX interface, and said peripheral interface is a bitronics interface.

33. A peripheral server operably connected between at least one peripheral and at least one client via a network for transmitting data between the peripheral and the client, said server comprising:

a network interface adapted to connect the server to the network for transmitting data between the server and the network;

a peripheral interface adapted to connect the server to the at least one peripheral for transmitting data between the server and the peripheral;

at least one data path connected between said network interface and said peripheral interface for transmitting data between the at least one peripheral and the at least one client; and

a firmware provided in said at least one data path and programmed to independently test a peripheral interface portion and a network interface portion of said data path and to generate a status report indicating the result of said test, in response to corresponding test commands received from the at least one client;

wherein said data path is a scan gateway for transmitting scan data from a scanning peripheral.

36. A peripheral server operably connected between at least one peripheral and at least one client via a network for transmitting data between the peripheral and the client, said server comprising:

a network interface adapted to connect the server to the network for transmitting data between the server and the network;

a peripheral interface adapted to connect the server to the at least one peripheral for transmitting data between the server and the peripheral;

at least one data path connected between said network interface and said peripheral interface for transmitting data between the at least one peripheral and the at least one client; and

a firmware provided in said at least one data path and programmed to independently test a peripheral interface portion and a network interface portion of said data path and to generate a status report indicating the result of said test, in response to corresponding test commands received from the at least one client;

said server further including at least one test connection for receiving said test commands and sending said status report to the client, and at least one data port for transmitting data between the server and the network;

wherein said firmware generates said status report automatically at a conclusion of said test, and when a status report command is received from the at least one client via said test connection with respect to a specified data port; and

wherein said firmware generates said status report of a currently running said test when said status report command is received during said currently running test, of a most recently completed test when no test is being run at the time said status report command is received and an empty status report when no said test have been run.

39. A peripheral server operably connected between at least one peripheral and at least one client via a network for transmitting data between the peripheral and the client, said server comprising:

a network interface adapted to connect the server to the network for transmitting data between the server and the network;

a peripheral interface adapted to connect the server to the at least one peripheral for transmitting data between the server and the peripheral;

at least one data path connected between said network interface and said peripheral interface for transmitting data between the at least one peripheral and the at least one client; and

a firmware provided in said at least one data path and programmed to independently test a peripheral interface portion and a network interface portion of said data path and to generate a status report indicating the result of said test, in response to corresponding test commands received from the at least one client;

wherein said server further including at least one test connection for receiving said test commands and sending said status report to the client, and at least one data port for transmitting data between the server and the network;

wherein said firmware is further programmed to reset a currently running said test on said at least one data port when a reset command is received from the at least one client, wherein said resetting said test includes closing said at least one test connection other than said at least one test connection through which said reset command is received, canceling said currently running said test, and setting a maximum segment size of data to be transmitted through said interface and peripheral networks to a default value.

said peripheral interface portion and said network interface portions are independently being tested.