Fibre channel network employing registered state change notifications with enhanced payload

• US 8,320,241 B2
• Filed: 07/30/2002
• Issued: 11/27/2012
• Est. Priority Date: 07/30/2002
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Chen, Xiaoheng, Tsai, Raymond C., Hammons, Richard L., Pathak, Lalit D.
• Primary Examiner(s): HSU, ALPUS
• Application Number:
  US10/208,375
• Publication Number:
  US 20040024852A1
• Time in Patent Office: 3,773 Days
• Field of Search: 370/230, 370/236, 370/254, 370/400, 709/217, 709/220, 709/223, 709/238, 711/118
• US Class Current: 370/230
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A network of switches that employ Registered State Change Notifications (RSCNs) with enhanced payloads is disclosed. In one embodiment, the network comprises multiple switches coupled together, and multiple node devices each directly-coupled to at least one other switch. Each of the switches preferably provides RSCNs to other switches when a node device state change is detected. One or more of the RSCNs preferably includes a device entry having more than four properties associated with the node device undergoing the state change. The switches receiving the enhanced RSCNs preferably maintain caches of remote node device entries copied from the RSCN device entries. The device entries preferably include one or more of the following: Owner Identifier, Port Type, Port Identifier, Port Name, Node Name, Initial Process Associator, Node IP Address, Class of Service, FC-4 Types, Port IP Address, Fabric Port Name, and Hard Address. Traffic overhead may advantageously be reduced.

Claims

1. A method, comprising:

using state change messages to establish and maintain a cache of remote node device entries on a device, the state change messages comprising updates for node devices;

receiving a node device information request; and

generating a response based on the cache of remote node device entries if the node device information request regards a remote node device, a node device being remote if not directly coupled to the device.

2. The method of claim 1, wherein at least one device entry includes properties associated with a particular node device;

wherein the properties are not identifiers of the node device.

3. The method of claim 1, wherein at least one device entry includes a field for indicating a format of the device entry.

4. The method of claim 1, wherein at least one device entry includes a field for identifying a switch to which the remote node device is directly coupled.

5. The method of claim 1, wherein at least one device entry includes a field for a Port Type associated with the remote node device.

6. The method of claim 1, wherein at least one device entry includes a field for a Port Identifier associated with the remote node device.

7. The method of claim 1, wherein at least one device entry includes a field for a Port Name associated with the remote node device.

8. The method of claim 1, wherein at least one device entry includes a field for a Node Name associated with the remote node device.

9. The method of claim 1, wherein at least one device entry includes a field for an Initial Process Associator associated with the remote node device.

10. The method of claim 1, wherein at least one device entry includes a field for a Node IP Address associated with the remote node device.

11. The method of claim 1, wherein at least one device entry includes a field for a Class of Service associated with the remote node device.

12. The method of claim 1, wherein at least one device entry includes a field for a Port IP Address associated with the remote node device.

13. The method of claim 1, wherein at least one device entry includes a field for a Hard Address associated with the remote node device.

14. A method, comprising:

using node device add/delete messages to establish and maintain a database of local node device entries;

using state change messages to establish and maintain a cache of remote node device entries;

receiving a node device information request regarding a particular node device;

generating a response based on the database of local node device entries if the node device information request regards a local node device; and

generating a response based on the cache of remote node device entries if the node device information request regards a remote node device.

15. The method of claim 14, wherein at least one device entry includes properties associated with the particular node device;

wherein the properties are not identifiers of the particular node device.

16. The method of claim 14, wherein at least one device entry includes more than four properties associated with the particular node device.

17. The method of claim 14, wherein at least one device entry includes a field for indicating a format of the device entry.

18. The method of claim 14, wherein at least one device entry includes a field for identifying a switch to which the particular node device is directly coupled.

19. The method of claim 14, wherein at least one device entry includes a field for a Port Type associated with the particular node device.

20. The method of claim 14, wherein at least one device entry includes a field for a Port Identifier associated with the particular node device.

21. The method of claim 14, wherein at least one device entry includes a field for a Port Name associated with the particular node device.

22. The method of claim 14, wherein at least one device entry includes a field for a Node Name associated with the particular node device.

23. The method of claim 14, wherein at least one device entry includes a field for an Initial Process Associator associated with the particular node device.

24. The method of claim 14, wherein at least one device entry includes a field for a Node IP Address associated with the particular node device.

25. The method of claim 14, wherein at least one device entry includes a field for a Class of Service associated with the particular node device.

26. The method of claim 14, wherein a device entry in the cache of remote node device consists of a subset of properties contained in a device entry of local node device entries.

27. The method of claim 14, wherein at least one device entry includes a field for a Port IP Address associated with the particular node device.

28. The method of claim 14, wherein at least one device entry includes a field for a Hard Address associated with the particular node device.

29. A device, comprising:

a cache of remote node device entries established and maintained using state change messages, the state change messages comprising updates for node devices;

wherein the device

receives a node device information request; and

generates a response based on the cache of remote node device entries if the node device information request regards a remote node device, a node device being remote if not directly coupled to the device.

30. A device, comprising:

a database of local node device entries established and maintained using node device add/delete messages; and

a cache of remote node device entries established and maintained using state change messages;

wherein the device

receives a node device information request regarding a particular node device;

generates a response based on the database of local node device entries if the node device information request regards a local node device; and

generates a response based on the cache of remote node device entries if the node device information request regards a remote node device.

31. The device of claim 30, further comprising a cache manager

32. The device of claim 30, further comprising a resident name server.

33. The device of claim 30, wherein at least one device entry includes a field for a Port Type associated with the particular node device.

34. The device of claim 30, wherein at least one device entry includes a field for an Initial Process Associator associated with the particular node device.

35. The device of claim 30, wherein at least one device entry includes a field for a Node IP Address associated with the particular node device.

36. The device of claim 30, wherein at least one device entry includes a field for a Class of Service associated with the particular node device.