Method and apparatus providing interoperation of execution images of different versions

• US 7,383,541 B1
• Filed: 08/07/2003
• Issued: 06/03/2008
• Est. Priority Date: 08/07/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Uban, Thomas W., Leclerc, Denis H., Donahue, Timothy P., Banks, Donald E.
• Primary Examiner(s): Kendall; Chuck
• Application Number:
  US10/638,149
• Time in Patent Office: 1,762 Days
• Field of Search: 717168-178
• US Class Current: 717/131
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A method is disclosed for providing interoperation of a first execution image of a first version and a second execution image of a second version. A compatibility matrix specifies whether the versions are compatible, base-level compatible, or incompatible. In one embodiment, the compatibility matrix may comprise a sparse table that stores a compatibility indicator for all permutations of a plurality of versions of a network operating system. As part of initialization of a system that includes the first execution image and second execution image, version information for the execution images is determined. An entry in the compatibility matrix corresponding to the versions is identified. The execution images are operated in a fully synchronized state when the identified entry of the compatibility matrix specifies that the versions are either compatible or base-level compatible. Individual components of the execution images interoperate according to the results of individual session negotiations. If the versions are incompatible, an alternative redundancy operation mode may be used. Embodiments provide for negotiation of compatible message versions and capabilities among peer components or clients of the execution images as source information to generate the compatibility matrix.

Claims

1. A method of providing interoperation of a first execution image of a first version and a second execution image of a second version, the method comprising the computer-implemented steps of:

receiving a compatibility matrix specifying whether the versions are compatible, base-level compatible, or incompatible;

determining the versions of the first execution image and second execution image;

identifying an entry in the compatibility matrix corresponding to the versions; and

operating the execution images in a stateful switchover mode when the identified entry of the compatibility matrix specifies that the versions are either compatible or base-level compatible;

wherein operating the execution images in a stateful switchover mode comprises operating the first execution image with a first processor of a dual-processor system and concurrently operating the second execution image with a second processor of the system.

2. A method as recited in claim 1, further comprising the steps of:

receiving a list of base-level components for which compatibility is required if the first version and second version are compatible;

negotiating compatibility among each of the base-level components of the first version and a corresponding base-level component of the second version;

determining, based on the list of base-level components and based on the negotiating step, whether the first version and second version are compatible, base-level compatible, or incompatible; and

storing, in the compatibility matrix, an entry associated with the first version and second version of the execution images, wherein the entry indicates the first version and second version are compatible, base-level compatible, or incompatible.

3. A method as recited in claim 2, further comprising the steps of:

repeating the steps of negotiating, determining, and storing for all peer versions of the execution images to result in creating and storing a fully-populated compatibility matrix.

4. A method as recited in claim 2, further comprising the steps of creating and storing the compatibility matrix based on a message version negotiation, wherein the message version negotiation comprises the steps of:

from the first execution image, sending a first message that specifies a message type and a range of acceptable message versions;

receiving a second message that specifies the same message type and a message version within the range;

determining whether support for the message version is available; and

sending a third message that specifies compatibility when support for the message version is available.

5. A method as recited in claim 4, further comprising the step of sending a fourth message specifying incompatibility, when support for the message version is unavailable.

6. A method as recited in claim 4, wherein the message version of the second message comprises a highest version value within the range that is supported by a peer execution image.

7. A method as recited in claim 4, further comprising the steps of:

determining, based on the first message, whether interoperation with the first execution image is possible;

sending a compatibility message as the second message when interoperation with the first execution image is possible; and

sending an incompatibility message as the second message when interoperation with the second execution image is not possible.

8. A method as recited in claim 2, further comprising the steps of creating and storing the compatibility matrix based on a capability negotiation that further determines whether the components are compatible on a session-by-session basis.

9. A method as recited in claim 8, wherein the capability negotiation comprises the steps of:

determining that the components are incompatible for a then-current session if the capability negotiation fails;

performing the message version negotiation recited in claim 4 only when the capability negotiation succeeds; and

determining that the components are compatible only when the message version negotiation succeeds.

10. A method as recited in claim 9, further comprising the step of creating and storing results of the capability negotiation and message version negotiation for pairs of components for a particular session for use by a compatibility matrix utility that creates the compatibility matrix based on the results.

11. A method as recited in claim 9, further comprising the steps of storing results of the capability negotiation and message version negotiation for pairs of components of the execution image of first version for a particular session as part of that execution image.

12. A method as recited in claim 11, further comprising the steps of:

retrieving, from the execution images of the first version and the second version, all pairs of results for corresponding clients associated with the first version and the second version; and

determining whether the first version and the second version are compatible, base-level compatible or incompatible based on all pairs of results.

13. A method as recited in claim 2, further comprising performing the steps of negotiating, determining and storing with respect to a plurality of stateful clients associated with the execution images.

14. A method as recited in claim 2, further comprising the steps of configuring the first execution image and second execution image in a mode to generate compatibility information used to build the compatibility matrix entry for any two image versions.

15. A method as recited in claim 1, wherein the first execution image and the second execution image run on route processors of a distributed router, and further comprising the step of operating the first execution image and the second execution image in a mode which does not support stateful switchover of the route processors when the identified entry of the compatibility matrix specifies that the first version and the second version are incompatible.

16. A method as recited in claim 1, wherein the first execution image and the second execution image run on redundant route processors of a distributed router, and wherein the steps of claim 1 are performed as part of initialization of the redundant route processors.

17. A method as recited in claim 1, wherein one execution image among the first and second execution images performs message transformations for all messages sent or received at an agreed version value.

18. A computer-readable storage medium carrying one or more sequences of instructions for providing interoperation of a first execution image of a first version and a second execution image of a second version, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving a compatibility matrix specifying whether the versions are compatible, base-level compatible, or incompatible;

determining the versions of the first execution image and second execution image;

identifying an entry in the compatibility matrix corresponding to the versions; and

operating the execution images in a stateful switchover mode when the identified entry of the compatibility matrix specifies that the versions are either compatible or base-level compatible;

wherein operating the execution images in a stateful switchover mode comprises operating the first execution image with a first processor of a dual-processor system and concurrently operating the second execution image with a second processor of the system.

19. An apparatus for providing interoperation of a first execution image of a first version and a second execution image of a second version, comprising:

means for receiving a compatibility matrix specifying whether the versions are compatible, base-level compatible, or incompatible;

means for determining the versions of the first execution image and second execution image;

means for identifying an entry in the compatibility matrix corresponding to the versions; and

means for operating the execution images in a stateful switchover mode when the identified entry of the compatibility matrix specifies that the versions are either compatible or base-level compatible;

wherein the operating means comprises means for operating the first execution image with a first processor of a dual-processor system and for concurrently operating the second execution image with a second processor of the system.

20. The apparatus as recited in claim 19, further comprising:

means for receiving a list of base-level components for which compatibility is required if the first version and second version are compatible;

means for negotiating compatibility among each of the base-level components of the first version and a corresponding base-level component of the second version;

means for determining, based on the list of base-level components and based on the negotiating step, whether the first version and second version are compatible, base-level compatible, or incompatible; and

means for storing, in the compatibility matrix, an entry associated with the first version and second version of the execution images, wherein the entry indicates the first version and second version are compatible, base-level compatible, or incompatible.

21. The apparatus as recited in claim 20, further comprising means for configuring the first execution image and second execution image in a mode to generate compatibility information used to build the compatibility matrix entry for any two image versions.

22. The apparatus as recited in claim 19, wherein the first execution image and the second execution image run on redundant route processors of a distributed router, and wherein the means of claim 20 comprise part of means for initialization of the redundant route processors.

23. The apparatus as recited in claim 20, further comprising means for creating and storing the compatibility matrix based on a means for message version negotiation, wherein the means for message version negotiation comprises:

means for sending, from the first execution image, a first message that specifies a message type and a range of acceptable message versions;

means for receiving a second message that specifies the same message type and a message version within the range;

means for determining whether support for the message version is available; and

means for sending a third message that specifies compatibility when support for the message version is available.

24. The apparatus as recited in claim 23, further comprising:

means for determining, based on the first message, whether interoperation with the first execution image is possible;

means for sending a compatibility message as the second message when interoperation with the first execution image is possible; and

means for sending an incompatibility message as the second message when interoperation with the second execution image is not possible.

25. The apparatus as recited in claim 20, further comprising means for creating and storing the compatibility matrix based on means for determining whether the components are compatible on a session-by-session basis.

26. The apparatus as recited in claim 25, wherein the means for capability negotiation comprises:

means for determining that the components are incompatible for a then-current session if the capability negotiation fails;

means for performing the message version negotiation recited in claim 7 only when the capability negotiation succeeds; and

means for determining that the components are compatible only when the message version negotiation succeeds.

27. The apparatus as recited in claim 20, further comprising means for negotiating, determining and storing with respect to a plurality of stateful clients associated with the execution images.

28. The apparatus as recited in claim 19, wherein the first execution image and the second execution image run on route processors of a distributed router, and further comprising means for operating the first execution image and the second execution image in a mode which does not support stateful switchover of the route processors when the identified entry of the compatibility matrix specifies that the first version and the second version are incompatible.

29. An apparatus for providing interoperation of a first execution image of a first version and a second execution image of a second version, comprising:

a network interface that is coupled to the data network for receiving one or more packet flows therefrom;

one or more processors;

a computer-readable storage medium comprising one or more stored sequences of instructions which,

when executed by the one or more processors, cause the one or more processors to carry out the steps of;

receiving a compatibility matrix specifying whether the versions are compatible, base-level compatible, or incompatible;

determining the versions of the first execution image and second execution image;

identifying an entry in the compatibility matrix corresponding to the versions; and

operating the execution images in a stateful switchover mode when the identified entry of the compatibility matrix specifies that the versions are either compatible or base-level compatible;

wherein operating the execution images in a stateful switchover mode comprises operating the first execution image with a first processor of a dual-processor system and concurrently operating the second execution image with a second processor of the system.

30. The apparatus of claim 29, further comprising instructions which when executed cause:

receiving a list of base-level components for which compatibility is required if the first version and second version are compatible;

negotiating compatibility among each of the base-level components of the first version and a corresponding base-level component of the second version;

determining, based on the list of base-level components and based on the negotiating step, whether the first version and second version are compatible, base-level compatible, or incompatible; and

storing, in the compatibility matrix, an entry associated with the first version and second version of the execution images, wherein the entry indicates the first version and second version are compatible, base-level compatible, or incompatible.

31. The apparatus of claim 30, further comprising instructions which when executed cause configuring the first execution image and second execution image in a mode to generate compatibility information used to build the compatibility matrix entry for any two image versions.

32. The apparatus of claim 31, wherein the first execution image and the second execution image run on route processors of a distributed router, and further comprising instructions which when executed cause operating the first execution image and the second execution image in a mode which does not support stateful switchover of the route processors when the identified entry of the compatibility matrix specifies that the first version and the second version are incompatible.

33. The apparatus of claim 30, further comprising instructions which when executed cause creating and storing the compatibility matrix based on a message version negotiation, wherein the message version negotiation comprises instructions which when executed cause:

from the first execution image, sending a first message that specifies a message type and a range of acceptable message versions;

receiving a second message that specifies the same message type and a message version within the range;

determining whether support for the message version is available; and

sending a third message that specifies compatibility when support for the message version is available.

34. The apparatus of claim 33, further comprising instructions which when executed cause:

determining, based on the first message, whether interoperation with the first execution image is possible;

sending a compatibility message as the second message when interoperation with the first execution image is possible; and

sending an incompatibility message as the second message when interoperation with the second execution image is not possible.

35. The apparatus of claim 30, further comprising instructions which when executed cause creating and storing the compatibility matrix based on a capability negotiation that further determines whether the components are compatible on a session-by-session basis.

36. The apparatus of claim 35, wherein the capability negotiation is executed using instructions which when executed cause:

determining that the components are incompatible for a then-current session if the capability negotiation fails;

performing the message version negotiation recited in claim 7 only when the capability negotiation succeeds; and

determining that the components are compatible only when the message version negotiation succeeds.

37. The apparatus of claim 30, further comprising executing the instructions for negotiating, determining and storing with respect to a plurality of stateful clients associated with the execution images.

38. The apparatus of claim 29, wherein the first execution image and the second execution image run on redundant route processors of a distributed router, and wherein the instructions of claim 29 are executed as part of initialization of the redundant route processors.