System and method for supporting dry-run mode in a network environment

• US 9,594,818 B2
• Filed: 05/10/2013
• Issued: 03/14/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, Moxnes, Dag Georg, Holen, Line, Tjemsland, Kurt
• Primary Examiner(s): Taylor, Nicholas
• Assistant Examiner(s): PENA-SANTANA, TANIA M
• Application Number:
  US13/892,174
• Publication Number:
  US 20130304891A1
• Time in Patent Office: 1,404 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 subnet management in a network environment. One or more inactivated switches can be included in a subnet, wherein each of the inactivated switches is associated with an empty set of known secret keys. A subnet manager (SM) in a dry-run mode can perform one or more dry-run operations on the one or more inactivated switches, before activating the one or more inactivated switches.

Claims

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

providing a first switch and a second switch in a subnet, wherein the second switch includes a subnet manager in a dry-run mode, and wherein the first switch is associated with a set of disabled secret keys, wherein the set of disabled secret keys causes the first switch to be inactivated from the perspective of the second switch;

performing, via the subnet manager of the second switch, one or more dry-run operations, wherein the one or more dry-run operations include

at least one operation configured to initialize the first switch by providing configuration and policy information for each port in the first switch, and

at least one operation configured to determine that the subnet has required properties and connectivity; and

activating the first switch by enabling the set of disabled secret keys, in response to the subnet manager that has determined that the subnet has the required properties and connectivity.

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

ignoring the first switch by one or more subnet managers in the subnet.

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

ensuring a dry-run mode subnet manager associated with the first switch does not become a master subnet manager in the activated subnet.

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

providing a dry-run subnet manager on either the first switch or an already activated switch in a new set of subnet manager nodes, which is used to support controlled merge of different subnets.

5. The method according to claim 4, further comprising adding a complete set of secret M_Key values from the different subnets to the new set of subnet manager nodes, and transferring mastership to the new set of subnet manager nodes.

6. The method according to claim 4, further comprising performing a dry-run update transaction on the new set of subnet manager nodes, without a current master subnet manager.

7. The method according to claim 1, further comprising performing a dry-run activation of subnet managers from a new firmware version during a rolling upgrade process for a fabric.

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

providing multiple subnets and/or multiple sub-subnets in the network environment.

9. The method according to claim 8, further comprising using a proxy mechanism that is implemented by one or more router ports to allow discovery across subnet boundaries.

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

one or more microprocessors;

a subnet manager, running on the one or more microprocessors, wherein the subnet manager operates to

provide a first switch and a second switch in an activated subnet, wherein the second switch includes a subnet manager in a dry-run mode, and wherein the first switch is associated with a set of disabled secret keys, wherein the set of disabled secret keys causes the first switch to be inactivated from the perspective of the second switch,

perform, via the subnet manager of the second switch, one or more dry-run operations, wherein the one or more dry-run operations include

at least one operation configured to initialize the first switch by providing configuration and policy information for each port in the first switch, and

at least one operation configured to determine that the subnet has required properties and connectivity, and

activate the first switch by enabling the set of disabled secret keys, in response to the subnet manager that has determined that the subnet has the required properties and connectivity.

11. The system according to claim 10, wherein the subnet manager operates to ignore the first switch.

12. The system according to claim 10, wherein a dry-run mode subnet manager associated with the first switch operates to not become a master subnet manager in the subnet.

13. The system according to claim 10, wherein:

one or more dry-run subnet managers on either the first switch or an already activated are included in a new set of subnet manager nodes, which is used to support controlled merge of different subnets.

14. The system according to claim 13, wherein a complete set of secret M_Key values are added from the different subnets to the new set of subnet manager nodes, and mastership can be transferred to the new set of subnet manager nodes.

15. The system according to claim 13, wherein a dry-run update transaction is performed on the new set of subnet managers nodes without a current master subnet manager.

16. The system according to claim 10, wherein a dry-run activation of subnet managers can be performed from a new firmware version during a rolling upgrade process for a fabric.

17. The system according to claim 10, wherein the network environment includes multiple subnets and/or multiple sub-subnets, and a proxy mechanism implemented by one or more router ports to allow discovery across subnet boundaries.

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

providing a first switch and a second switch in a subnet, wherein the second switch includes a subnet manager in a dry-run mode, and wherein the first switch is associated with a set of disabled secret keys, wherein the set of disabled secret keys causes the first switch to be inactivated from the perspective of the second switch;

performing, via the subnet manager of the second switch, one or more dry-run operations, wherein the one or more dry-run operations include

at least one operation configured to initialize the first switch by providing configuration and policy information for each port in the first switch, and

at least one operation configured to determine that the subnet has required properties and connectivity; and

activating the first switch by enabling the set of disabled secret keys, in response to the subnet manager that has determined that the subnet has the required properties and connectivity.