Software installation in a multi-chassis network device

• US 7,747,999 B1
• Filed: 09/26/2005
• Issued: 06/29/2010
• Est. Priority Date: 09/26/2005
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Mahajan, Pallavi, Eng, Wing, Shafer, Philip A.
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): CHOW, CHIH CHING
• Application Number:
  US11/235,715
• Time in Patent Office: 1,737 Days
• Field of Search: 717/174, 717/168, 709/227, 370/400
• US Class Current: 717/174
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0846 based on copy from other elements
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements

Abstract

A multi-chassis router allows an administrator to install software from a single user interface. The multi-chassis router automatically forwards the software to each chassis within the multi-chassis router when given a single command to install the software from an administrator. The multi-chassis router also automatically validates the software on each chassis. This allows each chassis within the multi-chassis router to have the same software during all stages of a software installation and ensures software on each chassis is compatible with software on every other chassis. In effect, an administrator does not need to account for the multiple chassis configuration, and an administrator familiar with software installation on a standalone router can use that knowledge to install software on the multi-chassis router.

Claims

1. A method for installing software in a multi-chassis router comprising:

receiving with a control node associated with the multi-chassis router a command to install software on the multi-chassis router, wherein the multi-chassis router includes a plurality of chassis;

automatically downloading the software from the control node to the plurality of chassis in response to the command;

receiving a software validation result from each of the plurality of chassis after downloading the software from the control node to the plurality of chassis in response to the command, wherein the software validation results represent comparisons of current configurations of each of the plurality of chassis with compatibility of the software; and

after receiving the validation result from each of the plurality of chassis, sending a commit command to the plurality of chassis from the control node to commit the software on each of the plurality of chassis.

2. The method of claim 1, further comprising validating the software on the plurality of chassis prior to installation of the software.

3. The method of claim 2, wherein validating the software comprises validating that the software is compatible with the configuration of the of the plurality of chassis.

4. The method of claim 1, further comprising outputting a compiled result representing the validation results from each of the plurality of chassis in accordance with a format of a standalone router.

5. The method of claim 1, wherein automatically downloading the software from the control node to the plurality of chassis in response to the command includes copying the software to each of the plurality of chassis sequentially.

6. The method of claim 1, wherein the method is performed by a management daemon included in a routing engine in a first chassis of the plurality of chassis.

7. The method of claim 1, wherein the method is performed by an administrative device, wherein the administrative device is connected to the multi-chassis router via a network.

9. The method of claim 1, wherein committing the plurality of chassis to the software comprises:

moving the software into a directory of the plurality of chassis; and

installing the software on each of the plurality of chassis.

10. The method of claim 1, further comprising:

receiving a group of commit confirmations, wherein the group of commit confirmations includes a commit confirmation from each of the plurality of chassis; and

producing a compiled response representing the group of commit confirmations.

11. The method of claim 10, further comprising presenting the compiled response to an administrator via an interface.

8. A method for installing software in a multi-chassis router comprising:

receiving with a control node associated with the multi-chassis router a command to install software on the multi-chassis router, wherein the multi-chassis router includes a plurality of chassis;

automatically downloading the software from the control node to the plurality of chassis in response to the command;

receiving a failed software validation result from at least one of the plurality of chassis alter downloading the software from the control node to the plurality of chassis in response to the command, wherein the failed software validation result represents a comparison of a current configuration of at least one of the plurality of chassis with compatibility of the software; and

sending a rollback command to the plurality of chassis to cancel the software installation in response to the failed software validation result received from at least one of the plurality of chassis.

12. The method of claim 8, further comprising receiving either the commit command or the rollback command from an administrator.

13. A multi-chassis router comprising:

a plurality of chassis; and

a control node coupled to the plurality of chassis by communication links;

wherein the control node receives a command to install software on the multi-chassis router, and automatically downloads the software to the plurality of chassis in response to the command, wherein the control node is configured to send a commit command to the plurality of chassis to commit the software when a successful validation result is received from each of the chassis, wherein the successful validation results represent comparisons of current configurations of each of the plurality of chassis with compatibility of the software, and send a rollback command to the plurality of chassis to cancel the software installation when a failed software validation result is received from at least one of the plurality of chassis, wherein the failed software validation result represents a comparison of a current configuration of at least one of the plurality of chassis with compatibility of the software.

14. The multi-chassis router of claim 13, wherein control node validates the software on the plurality of chassis.

15. The multi-chassis router of claim 14, wherein the control node receives a software validation result from the plurality of chassis.

16. The multi-chassis router of claim 14, wherein the control node that validates the software is compatible with the configuration of the of the plurality of chassis.

17. The multi-chassis router of claim 13, wherein the control node outputs a compiled result representing the validation results from each of the plurality of chassis in accordance with a format of a standalone router.

18. The multi-chassis router of claim 13, wherein, in response to the commit command from the control node, the plurality of chassis are each configured to:

move the software into an active directory, and

perform an in service software upgrade to install the software.

19. The multi-chassis router of claim 13, wherein the control node

receives a group of commit confirmations, wherein the group of commit confirmations includes a commit confirmation from each of the plurality of chassis, and

produces a compiled response representing the group of commit confirmations.

20. The multi-chassis router of claim 19, wherein the control node presents the compiled response to an administrator via a user interface.

21. The multi-chassis router of claim 13, wherein the control node receives either the commit command or the rollback command from an administrator.

22. The multi-chassis router of claim 13, wherein the control node downloads the software to each of the plurality of chassis sequentially.

23. The multi-chassis router of claim 13, wherein the control node is within a routing engine in a first chassis of the plurality of chassis.

24. The multi-chassis router of claim 23, wherein the first chassis is a switch card chassis.

25. A computer-readable medium comprising instructions that cause a programmable processor in a network device to:

receive a command to install software on a multi-chassis router, wherein the multi-chassis router includes a plurality of chassis;

automatically download the software to the plurality of chassis without manual intervention in response to the command;

receive a software validation result from each of the plurality of chassis alter downloading the software to the plurality of chassis in response to the command, wherein the software validation result represents a comparison of a current configuration of at least one of the plurality of chassis with compatibility of the software; and

alter receiving the validation result from each of the plurality of chassis, send a commit command to the plurality of chassis from the control node to commit the software on each of the plurality of chassis.

26. The computer-readable medium of claim 25, comprising further instructions that cause the programmable processor to validate the software on the plurality of chassis.

27. The computer-readable medium of claim 26, comprising instructions that cause the programmable processor to validate that the software is compatible with the configuration of the of the plurality of chassis.

28. The computer-readable medium of claim 25, comprising further instructions that cause the programmable processor to output a compiled result representing the validation results from each of the plurality of chassis in accordance with a format of a standalone router.

29. The computer-readable medium of claim 25, comprising further instructions that cause the programmable processor to:

send a commit command to the plurality of chassis to commit the software when a successful validation result is received from each of the plurality of chassis; and

send a rollback command to the plurality of chassis to cancel the software installation when a failed software validation result is received from at least one of the plurality of chassis.

30. The computer-readable medium of claim 29, comprising further instructions that cause the programmable processor to receive either the commit command or the rollback command from an administrator.

31. The computer-readable medium of claim 25, wherein the commit command comprises instructions that cause the programmable processor to:

move the software into a directory in each of the plurality of chassis; and

install the software on each of the plurality of chassis.

32. The computer-readable medium of claim 25, comprising further instructions that cause the programmable processor to:

receive a group of commit confirmations, wherein the group of commit confirmations includes a commit confirmation from each of the plurality of chassis; and

produce a compiled response representing the group of commit confirmations.

33. The computer-readable medium of claim 32, comprising further instructions that cause the programmable processor to present the compiled response to an administrator.

34. The computer-readable medium of claim 25, comprising further instructions that cause the programmable processor to copy the software to each of the plurality of chassis sequentially.