Method and system for component compatibility verification

• US 6,898,768 B1
• Filed: 05/17/2002
• Issued: 05/24/2005
• Est. Priority Date: 05/17/2002
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Yellai, Prabhakara, Stebbins, Robert, Medved, Jan, Truong, Alex, Theodossy, Samer
• Primary Examiner(s): THOMPSON, ANNETTE M
• Application Number:
  US10/150,599
• Time in Patent Office: 1,103 Days
• Field of Search: 716/5, 716/1, 703/27, 710/104, 709/230
• US Class Current: 716/111
• CPC Class Codes: G06F 2117/08 HW-SW co-design, e.g. HW-SW partitioning
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

Components to be verified for compatibility are identified. Each of the components maintains a relationship with the other components such that all of the components are compatible with one another. A change to one component triggers an automatic evaluation of the relationships between the changed component and the other components to determine if compatibility is maintained. The automatic evaluation of the relationships is based on predetermined compatibility information provided in a compatibility matrix. When the automatic evaluation identifies incompatibility between the changed component and the other components, the change is rejected.

Claims

1. A method for performing compatibility verification, comprising:

creating a compatibility matrix for a plurality of components in a system the plurality of components including a control module, the compatibility matrix including compatibility information for each of the components in the system, the compatibility information including hardware revision information, software revision information, and migration information from a hardware revision to another hardware revision;

automatically performing a self-verification of the control module to determine if an associated hardware revision and one or more associated software revisions are compatible with one another based on the compatibility information of the control module;

when one of the components is modified, using the compatibility matrix to automatically determine if the modified component is a compatible component; and

accepting the modified component as one of the components in the system when the modified component is determined to be a compatible component.

2. The method of claim 1, further comprising rejecting the modified component as one of the components in the system when the modified component is determined to be not a compatible component.

3. The method of claim 1, wherein a component is modified by migrating its associated hardware from one hardware revision to another hardware revision.

4. The method of claim 1, wherein a component is modified by migrating its associated software from one software revision to another software revision.

5. The method of claim 1, wherein the compatibility information includes migration information from a software revision to another software revision.

6. The method of claim 1, wherein the compatibility information includes graceful migration paths.

7. The method of claim 1, wherein the compatibility information further includes non-graceful migration paths, wherein a less than desirable performance by the system is experienced when a non-graceful migration path exists.

8. The method of claim 1, wherein the compatibility information further includes supported migration paths.

9. The method of claim 1, wherein the modified component is determined to be a compatible component when its hardware revision information is compatible with its software revision information.

10. The method of claim 1, wherein the modified component is determined to be a compatible component when a migration from one hardware revision to another hardware revision is graceful or non-graceful.

11. The method of claim 1, wherein the modified component is determined to be a compatible component when a migration from one software revision to another software revision is graceful or non-graceful.

12. The method of claim 1, wherein the modified component is determined to be a compatible component when it is compatible with the other components in the system.

13. The method of claim 1, wherein using the compatibility matrix to automatically determine if the modified component is a compatible component comprises:

determining a first state of the modified component before the component is modified;

determining a second state of the modified component after the component is modified;

locating compatibility information of the modified component in the compatibility matrix; and

determining if the compatibility information of the modified component supports a migration path from a pre-modification state to a post-modification state.

14. The method of claim 13, further comprising accessing an instance of the compatibility matrix in a non-persistent memory in order to locate the compatibility information of the modified component.

15. A communication system, comprising:

a control module configured to automatically perform self-verification to determine if its associated hardware revision and one or more associated software revisions are compatible with one another based on compatibility information for the control module provided in a predetermined compatibility matrix,

wherein after the control module successfully performs the self-verification, the control module automatically verifies each of one or more related service modules, based on compatibility information for the service modules provided in the predetermined compatibility matrix, to determine if the control module is compatible with the one or more related service modules based on the compatibility information for the control module, wherein the compatibility information for the control module and the compatibility information for the service module include allowed migration paths and non-allowed migration paths.

16. The communication system of claim 15, wherein the control module verifies hardware revisions and software revisions of each of the one or more related service modules.

17. A computer readable medium having stored thereon sequences of instructions which are executable by a system, and which, when executed by the system, cause the system to:

form a compatibility matrix that includes compatibility information for a plurality of components being installed in a system the plurality of components including a control module, the compatibility information including information about supported hardware revisions, supported software revisions for each of the plurality of components, and graceful migration paths and non-graceful migration paths from a supported hardware revision to another supported hardware revision and from a supported software revision to another supported software revision;

automatically performing a self-verification of the control module to determine if an associated hardware revision and one or more associated software revisions are compatible with one another based on the compatibility information of the control module; and

responsive to a change to the system affecting at least one of the components, automatically determining whether to accept or reject the change based on the compatibility matrix.

18. The computer readable medium of claim 17, wherein a new version of the compatibility matrix is formed when a new supported component is introduced.