Method for upgrading embedded configuration databases

• US 7,130,870 B1
• Filed: 08/04/2000
• Issued: 10/31/2006
• Est. Priority Date: 05/20/2000
• Status: Expired due to Term

• Current Assignee: Ciena Corporation
• Original Assignee: Ciena Corporation
• Inventors: Pecina, Christine, Perry, James R, Perry, Thomas R, Black, Darryl, Sullivan, Jr., Daniel J
• Primary Examiner(s): Wiley, David
• Assistant Examiner(s): NEURAUTER, GEORGE C
• Application Number:
  US09/633,155
• Time in Patent Office: 2,279 Days
• Field of Search: 709/224, 709/225, 709217-219, 709/220, 707202-204, 707/104.1, 714 5- 13
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

The present invention provides a method for upgrading embedded configuration databases while a network device is operating and with minimal disruption to network device operation. While a network device is operating and using an embedded primary configuration database, an embedded backup configuration database stops performing as a backup database and is upgraded. The upgraded configuration database is then switched over to become the primary configuration database. The original primary configuration database may immediately become the backup configuration database, or the original primary configuration database may remain unchanged until the upgrade is committed. If the upgrade is not committed, for example, due to errors, then the original primary configuration database may be quickly switched over to again become the primary configuration database. As a result, embedded configuration databases may be upgraded while a network device is operating and with minimal disruption to network device operation.

Claims

1. A method of operating a network device, wherein the network device comprises a first printed circuit board including a first processor component and a second printed circuit board including a second processor component, and wherein said first and said second printed circuit boards are coupled to an internal communications bus configured to enable communication between said first and said second printed circuit boards, said method comprising:

providing a first configuration database containing data for configuring and operating the network device;

operating the network device with the first configuration database as a primary configuration database;

providing a second configuration database containing backup data corresponding to the data contained in the first configuration database;

operating the network device with the second configuration database as a backup configuration database;

replicating modifications made to the first configuration database to the second configuration database;

detecting a configuration database upgrade operation;

stopping replication of data from the first configuration database to the second configuration database;

upgrading the second configuration database while said first configuration database continues to provide configuration data to said network device;

maintaining the first configuration database through the first processor component; and

operating the network device with the first printed circuit board as a primary printed circuit board and the first processor component as a primary processor component;

maintaining the second configuration database through the second processor component;

operating the network device with the second printed circuit board as a backup printed circuit board and the second processor component as a backup processor component;

switching over to use the second configuration database as the primary configuration database; and

switching over to use the second printed circuit board and second processor component as the primary printed circuit board and the primary processor component.

2. The method of claim 1, further comprising:

detecting a commitment of the configuration database upgrade operation;

operating the network device with the first configuration database as a backup configuration database; and

replicating modifications made to the second configuration database to the first configuration database.

3. The method of claim 1, further comprising:

detecting errors with the configuration database upgrade operation.

4. The method of claim 1, wherein upgrading the second configuration database comprises:

receiving a configuration control file from a network management server; and

executing the configuration control file.

5. The method of claim 4, wherein upgrading the second configuration database further comprises:

receiving a data definition language (DDL) file including structured query language (SQL) commands; and

wherein executing the configuration control file comprises executing the SQL commands to construct an upgraded database schema in the second configuration database.

6. The method of claim 1, wherein detecting a configuration database upgrade operation comprises:

receiving an upgrade definition from a network management system server.

7. The method of claim 6, wherein receiving an upgrade notification from a network management system server comprises:

receiving SQL commands from the network management server; and

executing the SQL commands.

8. The method of claim 7, wherein executing the SQL commands comprises:

writing a software load record indicating a configuration database upgrade in a table within the first configuration database.

9. The method of claim 8, wherein the table comprises a software management system table.

10. The method of claim 7, wherein the SQL commands are received within a DDL file.

11. The method of claim 8, wherein detecting a configuration database upgrade operation further comprises:

detecting the software load record indicating the configuration database upgrade through a master system resiliency manager (SRM); and

notifying a first slave SRM associated with the record configuration database to perform a configuration database upgrade.

12. The method of claim 11, wherein stopping replication of data from the first configuration database to the second configuration database comprises:

causing the second configuration database to cause replicating data changes made to the first configuration database.

13. The method of claim 1, wherein before detecting a configuration database upgrade operation the method further comprises:

receiving upgraded applications from a network management server.

14. The method of claim 1, wherein before detecting a configuration database upgrade operation the method further comprises:

receiving new applications from a network management server.

15. The method of claim 2, wherein detecting commitment of configuration database upgrade comprises:

saving the upgraded second configuration database to persistent memory.

16. A method of managing a telecommunications network, comprising:

operating a network device with a first printed circuit board having a first processor component, and a first configuration database as a primary configuration database, said first configuration database containing data for configuring and operating the network device;

maintaining the first configuration database through the first processor component;

operating the network device with a second printed circuit board having a second processor component, and a second configuration database as a backup configuration database,

said second configuration database containing backup data corresponding to the data contained in the first configuration database and wherein said first and said second processor components communicate via an internal communications bus;

maintaining the second configuration database through the second processor component;

replicating modifications made to the first configuration database to the second configuration database;

sending SQL commands from a network management server to the network device;

executing the SQL commands to write a software load record indicating a configuration database upgrade in a table within the first configuration database;

stopping replication of data from the first configuration database to the second configuration database;

upgrading the second configuration database while the first configuration database continues to provide configuration data to applications executing on the network device;

switching over to use the second configuration database as the primary configuration database; and

switching over to use the second printed circuit board and second processor component as the primary printed circuit board and the primary processor component.