System and method for supporting state synchronization in a network environment

• US 9,690,836 B2
• Filed: 05/10/2013
• Issued: 06/27/2017
• Est. Priority Date: 05/10/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Hodoba, Predrag, Johnsen, Bjrn Dag, Narasimhamurthy, Prabhunandan
• Primary Examiner(s): Taylor, Nicholas
• Assistant Examiner(s): PENA-SANTANA, TANIA M
• Application Number:
  US13/892,133
• Publication Number:
  US 20130304883A1
• Time in Patent Office: 1,509 Days
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• 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 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/24 using dedicated network management hardware
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 49/358 Infiniband Switches
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/1051 Group master selection mechanisms

Abstract

A system and method can support network management in a network environment. The network environment can include a plurality of configuration daemons (CDs), wherein each CD resides on a switch in the network environment. The CD operates to receive a configuration file that includes a list of known management key (M_Key) values. Furthermore, the CD operates to store the configuration file, and make the configuration file available to a local subnet manager (SM) on the switch, wherein the local SM is associated with a currently used M_Key value. Then, the CD operates to update the local SM with a new M_Key, after receiving an instruction from a master CD that is associated with a master SM in the network environment.

Claims

1. A method implemented on a first switch comprising a processor coupled with a non-transient memory device for supporting state synchronization in an associated node of an associated network environment comprising a plurality of switches including the first switch, a master subnet manager (SM), and a master configuration daemon (CD) associated with the master SM, the method comprising:

providing a local SM executing on the first switch;

providing a local CD executing on the first switch;

associating the local CD with the local SM;

associating one or more subnet management agents (SMAs) of the associated node with the local SM;

receiving, from the master SM via the local CD, a distributed transaction implemented by the master CD across the plurality of switches in the network environment, the distributed transaction comprising a commit command and a configuration file, wherein the configuration file includes a list of known management key (M_Key) values comprising an intended new M_Key value;

storing, by the local CD, the configuration file in the non-transient memory device of the first switch;

while deferring updating by the local CD the current M_Key value to the intended new M_Key value;

making the known M_Key values of the configuration file available, by the local CD, for immediate probing operation and/or discovery operation use by the local SM on the first switch; and

selectively using, by the local SM, the current M_Key value for updating and/or setting M-Key values of the one or more SMAs associated with the local SM;

selectively updating, by the local CD in a first transaction, the current M_Key value of the local SM with the intended new M_Key value exclusively in response to receiving an update instruction from the master CD; and

discontinuing selectively using the current M_Key value by the local SM for the updating and/or setting the M_Key values of the one or more SMAs in the associated network environment responsive to the current M_Key value being updated in accordance with the commit command by the local CD from the current M_Key value to the intended new M_Key value.

2. The method according to claim 1, further comprising:

including in the configuration file a trusted M_Key and one or more key values that are transparently generated based on the trusted M_Key.

3. The method according to claim 1, further comprising:

using, via the CD, a dedicated SM command line interface (CLI) command to update the local SM.

4. The method according to claim 1, further comprising:

updating, via the CD, the local SM with a current local secret key configuration when at least one of the SM and CD is restarted.

5. The method according to claim 1, further comprising:

containing in the configuration file information about the current M_Key value and information about the intended new M_Key value.

6. The method according to claim 5, further comprising:

recording the current M_Key value in the list of known M_Key values.

7. The method according to claim 1, further comprising:

using the new M_Key value to fence off a SM on an unavailable node.

8. The method according to claim 1, further comprising:

ensuring that the master SM has a known M_Key list not shorter than any M_Key list maintained by a standby SM instance.

9. The method according to claim 8, further comprising:

initiating a commit operation of the commit command on the master SM.

10. A switch system for supporting state synchronization in an associated node of an associated network environment comprising a plurality of switches including the first switch, a master subnet manager (SM), and a master configuration daemon (CD) associated with the master SM, the system comprising:

one or more microprocessors;

a non-transient memory device;

a local SM executing on the one or more microprocessors; and

a local CD associated with the local SM and executing on the one or more microprocessors, wherein the CD operates to;

receive, from the master SM via the local CD, a distributed transaction implemented by the master CD across the plurality of switches in the network environment, the distributed transaction comprising a commit command and a configuration file, wherein the configuration file includes a list of known management key (M_Key) values comprising an intended new M_Key value;

store, by the local CD, the configuration file in the non-transient memory device of the first switch;

while deferring updating by the local CD the current M_Key value to the intended new M_Key value;

make the known M_Key values of the configuration file available, by the local CD, for immediate probing operation and/or discovery operation use by the local SM on the first switch; and

selectively use, by the local SM, the current M_Key value for updating and/or setting M-Key values of one or more SMAs associated with the local SM;

selectively update, by the local CD in a first transaction, the current M_Key value of the local SM with the intended new M_Key value exclusively in response to receiving an update instruction from the master CD; and

discontinue selectively using the current M_Key value by the local SM for the updating and/or setting the M_Key values of the one or more SMAs in the associated network environment responsive to the current M_Key value being updated in accordance with the commit command by the local CD from the current M_Key value to the intended new M_Key value.

11. The system according to claim 10, wherein:

the configuration file includes a trusted M_Key and one or more key values that are transparently generated based on the trusted M_Key.

12. The system according to claim 10, wherein:

the CD operates to use a dedicated SM command line interface (CLI) command to update the local SM.

13. The system according to claim 10, wherein:

the CD operates to update the local SM with a current local secret key configuration when at least one of the SM and CD is restarted.

14. The system according to claim 10, wherein:

the configuration file contains information about the current M_Key value and information about the intended new M_Key value.

15. The system according to claim 14, wherein:

the CD operates to record the current M_Key value in the list of known M_Key values.

16. The system according to claim 10, wherein:

the new M_Key value is used to fence off a SM on an unavailable node.

17. The system according to claim 10, wherein:

the master CD operates to ensure that the master SM has a known M_Key list not shorter than any M_Key list maintained by a standby SM instance.

18. A non-transitory machine readable storage medium having instructions stored thereon that when executed cause a first switch system including a processor and a non-transient memory device to perform steps of supporting state synchronization in an associated network environment comprising a plurality of switches including the first switch system, a master subnet manager (SM), and a master configuration daemon (CD) associated with the master SM, the steps comprising:

providing a local SM executing on the first switch system;

providing a local CD executing on the first switch system;

associating the local CD with the local SM;

associating one or more subnet management agents (SMAs) of the associated node with the local SM;

receiving, from the master SM via the local CD, a distributed transaction implemented by the master CD across the plurality of switches in the network environment, the distributed transaction comprising a commit command and a configuration file, wherein the configuration file includes a list of known management key (M_Key) values comprising an intended new M_Key value;

storing, by the local CD, the configuration file in the non-transient memory device of the first switch system;

while deferring updating by the local CD the current M_Key value to the intended new M_Key value;

making the known M_Key values of the configuration file available, by the local CD, for immediate probing operation and/or discovery operation use by the local SM on the first switch system; and

selectively using, by the local SM, the current M_Key value for updating and/or setting M-Key values of the one or more SMAs associated with the local SM;

selectively updating, by the local CD in a first transaction, the current M_Key value of the local SM with the intended new M_Key value exclusively in response to receiving an update instruction from the master CD; and

discontinuing selectively using the current M_Key value by the local SM for the updating and/or setting the M_Key values of the one or more SMAs in the associated network environment responsive to the current M_Key value being updated in accordance with the commit command by the local CD from the current M_Key value to the intended new M_Key value.