Peer to peer interconnect diagnostics

• US 6,490,253 B1
• Filed: 11/22/2000
• Issued: 12/03/2002
• Est. Priority Date: 11/22/2000
• Status: Expired due to Fees

• Current Assignee: Seagate Technology LLC (Seagate Technology Holdings Plc)
• Original Assignee: Seagate Technology LLC (Seagate Technology Holdings Plc)
• Inventors: Coomes, James Allen, Miller, Michael Howard
• Primary Examiner(s): Yao, Kwang Bin
• Application Number:
  US09/718,995
• Time in Patent Office: 741 Days
• Field of Search: 370/244, 370/242, 370/245, 370/248, 370/249, 370/250, 370/251, 370/221, 370/222, 709/224, 714/4, 714/5, 714/712, 714/716, 714/717
• US Class Current: 370/241
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0847 Transmission error

Abstract

An information handling system, such as a disc drive, includes a controller that communicates with other devices in a loop, and performs distributed or peer-to-peer loop error diagnostics. One example of a loop is a fiber channel arbitrated loop. Distributed or peer-to-peer loop error diagnostics identifies and diagnoses errors in the immediately upstream device and the immediately upstream link by monitoring the error count to determine of the error count is increasing or not. An increasing error count or a changed loop configuration indicates that the source of the error is not the upstream device, while an unchanging error count and an unchanged loop configuration indicates that the source of the error is the upstream link.

Claims

1. A method of loop error diagnostics in a distributed daisy-chained peer-to-peer loop, the method performed by a device in the distributed daisy-chained peer-to-peer loop, the method comprising steps of:

(a) identifying an error condition locally on the device, the identifying step comprising;

(a)(1) receiving a current error status count from a local source for an upstream device in the distributed daisy-chained peer-to-peer loop;

(a)(2) receiving a prior error status count from a local source for an upstream device in the distributed daisy-chained peer-to-peer loop; and

(a)(3) comparing the current error status count to the prior error status count; and

(b) diagnosing the error.

2. The method of claim 1, wherein the distributed daisy-chained peer-to-peer loop includes a Fibre-Channel arbitrated loop.

3. The method of claim 1, wherein the method is performed by the device detecting the error.

4. The method of claim 1, wherein the receiving step (a)(1) is performed after the receiving step (a)(2).

5. The method of claim 4, wherein the receiving step (a)(2) is performed during an initialization of the device.

6. The method of claim 1, wherein the method further includes:

(a)(4) determining that the comparison indicates an error.

7. The method of claim 6, wherein the determining step (a)(4) includes:

(a)(4)(i) determining that the current error status count is equal to the prior error status count.

8. The method of claim 6, wherein the diagnosing step (b) includes:

(b)(1) generating an error report indicating that the error is suspected to be in a link between the device and the upstream device in the distributed daisy-chained peer-to-peer loop.

9. The method of claim 6, wherein the determining step (a)(4) includes:

(a)(4)(i) determining that the current error status count is not equal to the prior error status count.

10. The method of claim 9, wherein the diagnosing step (b) includes:

(b)(1) determining that the error source is not suspected to be in a link between the device and the upstream device in the distributed daisy-chained peer-to-peer loop.

11. The method of claim 9, wherein the diagnosing step (b) includes:

(b)(1) testing a link between the device and the upstream device in the distributed daisy-chained peer-to-peer loop.

12. The method of claim 11, wherein the testing step (b)(1) includes:

(b)(1)(i) transmitting data from the upstream device to the device through the distributed daisy-chained peer-to-peer loop; and

(b)(1)(ii) determining that the data was not received by the device as it was transmitted.

13. The method of claim 1, wherein the device further comprises a disc drive.

14. A peer apparatus in a loop comprising:

a communication input; and

a loop error isolation management application operably coupled to the communication input, the loop error isolation management application comprising;

a determiner of the identity of an upstream device in the loop;

a local store of the identity, operably coupled to the determiner;

a requester of link error counts from the upstream device in the loop, operably coupled to the store;

a local store of the link error counts, operably coupled to the requester;

a requester of a current link error count from the upstream device in the loop;

a determiner of configuration loop changes;

a comparator of current link error count to the saved error count, operably coupled to the determiner, the store of link error counts, and the store of current link error counts;

a resolver of link errors, operably coupled to the comparator; and

a transmitter of a device error diagnostics request operably coupled to the comparator and the store of the identity.

15. The peer apparatus of claim 14, wherein the peer apparatus includes a disc drive having a base and a disc rotatably attached to the base.

16. The peer apparatus of claim 14, wherein

the resolver includes a link tester;

the determiner of the identity of an upstream device in the loop includes a retriever of the identity of an upstream device from a loop map; and

the apparatus includes an initializer, operably coupled to the determiner of the identity of an upstream device in the loop, and operably coupled to the local store of the identity.

17. The peer apparatus of claim 14, wherein the peer apparatus further comprises a disc drive.