System and method for supporting configuration daemon (CD) in a network environment

• US 9,563,682 B2
• Filed: 05/10/2013
• Issued: 02/07/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: Johnsen, Bjrn Dag, Narasimhamurthy, Prabhunandan, Holen, Line
• Primary Examiner(s): Fan, Shiow-Jy
• Application Number:
  US13/892,129
• Publication Number:
  US 20130304699A1
• Time in Patent Office: 1,369 Days
• US Class Current: 1/1
• 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 a master CD is an active CD on a switch with a master subnet manager (SM). The master CD operates to perform consistency check on one or more states associated with one or more peer CDs in the network environment, and replicate a configuration file to the one or more peer CDs, wherein the configuration file includes at least one management key (M_Key) value.

Claims

1. A method for supporting network management in a network environment, comprising:

providing, at a plurality of switches in a network environment that includes a subnet, a plurality of subnet managers and configuration daemons, including, for each switch, a subnet manager and a configuration daemon that are associated with that switch,

wherein a master configuration daemon is an active configuration daemon on a switch with an associated master subnet manager also on that switch,

wherein the master configuration daemon communicates with peer configuration daemons within the subnet, and

wherein each switch provides a transactional interface that allows management of the subnet using one or more transactions;

prior to allowing an operation to be performed on the subnet as part of a transaction, performing, via the master configuration daemon, a consistency check on state information associated with one or more peer configuration daemons in the network environment;

replicating, via the master configuration daemon, a configuration file to the one or more peer configuration daemons, wherein the configuration file includes at least one management key (M_Key) value;

receiving, by the master configuration daemon, confirmation from the one or more peer configuration daemons that the replicating has successfully completed when the peer configuration daemons have received and stored the configuration file;

performing a consistency check on the configuration file received and stored at the one or more peer configuration daemons to determine that the configuration file received and stored at the one or more peer configuration daemons is consistent with the configuration file replicated via the master configuration daemon;

instructing, via the master configuration daemon, and after the master configuration daemon has received confirmation that the replicating has successfully completed and the consistency check has been performed, each of the one or more peer configuration daemons to make the stored configuration file available to its associated subnet manager (SM) on the switch; and

performing a commit operation by the master configuration daemon instructing each of the one or more peer configuration daemons to update its associated subnet manager with a list of M_Key values provided by the configuration file.

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

determining an order for replicating the configuration file to the one or more peer configuration daemons based on a type of a transaction.

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

using the configuration file to first update one or more known lists of M_Key values on the master subnet manager, when the transaction is an add-only transaction.

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

using the configuration file to first update one or more known lists of M_Key values on one or more subnet managers other than the master subnet manager, when the transaction is not an add-only transaction.

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

allowing the one or more states to include

availability of the one or more peer configuration daemons,

compatible implementation/protocol version,

correct current daemon run-time state, and

correct current configuration state/version on the one or more peer configuration daemons.

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

verifying a consistent encryption password for each configuration daemon prior to initiating a transaction.

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

prohibiting changing a new current M_Key value and deleting an old current M_Key value in a same transaction.

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

ensuring that the master subnet manager has a known M_Key list not shorter than any M_Key list maintained by the other subnet manager instance.

9. A system for supporting network management in a network environment, comprising:

a plurality of switches, having one or more microprocessors, in a network environment that includes a subnet, a plurality of subnet managers and configuration daemons, including, for each switch, a subnet manager and a configuration daemon that are associated with that switch;

a master configuration daemon, wherein the master configuration daemon is an active configuration daemon on a switch with an associated master subnet manager also on that switch,

wherein the master configuration daemon communicates with peer configuration daemons within the subnet, and

wherein each switch provides a transactional interface that allows management of the subnet using one or more transactions;

wherein the master configuration daemon operates to

prior to allowing an operation to be performed on the subnet as part of a transaction, perform a consistency check on state information associated with one or more peer configuration daemons in the network environment;

replicate a configuration file to one or more peer configuration daemons, wherein the configuration file includes at least one management key (M_Key) value;

receive confirmation from the one or more peer configuration daemons that the replicating has successfully completed when the peer configuration daemons have received and stored the configuration file;

perform a consistency check on the configuration file received and stored at the one or more peer configuration daemons to determine that the configuration file received and stored at the one or more peer configuration daemons is consistent with the configuration file replicated via the master configuration daemon;

instruct, after the confirmation has been received and the consistency check has been performed, each of the one or more peer configuration daemons to make the stored configuration file available to its associated subnet manager (SM) on the switch; and

perform a commit operation by the master configuration daemon instructing each of the one or more peer configuration daemons to update its associated subnet manager with a list of M_Key values provided by the configuration file.

10. The system according to claim 9, wherein:

an order for replicating the configuration file to the one or more peer configuration daemons can be determined based on a type of a transaction.

11. The system according to claim 10, wherein:

the master configuration daemon operates to use the configuration file to first update one or more known lists of M_Key values on the master subnet manager, when the transaction is an add-only transaction.

12. The system according to claim 10, wherein:

the master configuration daemon operates to use the configuration file to first update one or more known lists of M_Key values on one or more subnet managers other than the master subnet manager, when the transaction is not an add-only transaction.

13. The system according to claim 9, wherein:

the one or more states include

availability of the one or more peer configuration daemons,

compatible implementation/protocol version,

correct current daemon run-time state, and

correct current configuration state/version on the one or more peer configuration daemons.

14. The system according to claim 9, wherein:

a consistent encryption password is verified for each configuration daemon prior to initiating a transaction.

15. The system according to claim 9, wherein:

an operation to change a new current M_Key value and an operation to delete an old current M_Key value is prohibited in a same transaction.

16. The system according to claim 9, wherein:

the master configuration daemon operates to ensure that the master subnet manager has a known M_Key list not shorter than any M_Key list maintained by the other subnet manager instance.

17. A non-transitory machine readable storage medium having instructions stored thereon that when executed cause a system to perform the steps comprising:

providing, at a plurality of switches in a network environment that includes a subnet, a plurality of subnet managers and configuration daemons, including, for each switch, a subnet manager and a configuration daemon that are associated with that switch,

wherein a master configuration daemon is an active configuration daemon on a switch with an associated master subnet manager also on that switch,

wherein the master configuration daemon communicates with peer configuration daemons within the subnet, and

wherein each switch provides a transactional interface that allows management of the subnet using one or more transactions;

prior to allowing an operation to be performed on the subnet as part of a transaction, performing, via the master configuration daemon, a consistency check on state information associated with one or more peer configuration daemons in the network environment;

replicating, via the master configuration daemon, a configuration file to the one or more peer configuration daemons, wherein the configuration file includes at least one management key (M_Key) value;

receiving, by the master configuration daemon, confirmation from the one or more peer configuration daemons that the replicating has successfully completed when the peer configuration daemons have received and stored the configuration file;

performing a consistency check on the configuration file received and stored at the one or more peer configuration daemons to determine that the configuration file received and stored at the one or more peer configuration daemons is consistent with the configuration file replicated via the master configuration daemon;

instructing, via the master configuration daemon, and after the master configuration daemon has received confirmation that the replicating has successfully completed and the consistency check has been performed, each of the one or more peer configuration daemons to make the stored configuration file available to its associated subnet manager (SM) on the switch; and

performing a commit operation by the master configuration daemon instructing each of the one or more peer configuration daemons to update its associated subnet manager with a list of M_Key values provided by the configuration file.