Switch ports required for a MetroCluster configuration with array LUNs

Contributors ntap-bmegan Download PDF of this page

When you are connecting ONTAP systems to FC switches for setting up a MetroCluster configuration with array LUNs, you must connect FC-VI and HBA ports from each controller to specific switch ports.

If you are using both array LUNs and disks in the MetroCluster configuration, you must ensure that the controller ports are connected to the switch ports recommended for configuration with disks, and then use the remaining ports for configuration with array LUNs.

The following table lists the specific FC switch ports to which you must connect the different controller ports in an eight-node MetroCluster configuration with array LUNs.

Overall cabling guidelines with array LUNs

You should be aware of the following guidelines when using the cabling tables:

  • The Brocade and Cisco switches use different port numbering:

    • On Brocade switches, the first port is numbered 0.

    • On Cisco switches, the first port is numbered 1.

  • The cabling is the same for each FC switch in the switch fabric.

  • FAS8200 storage systems can be ordered with one of two options for FC-VI connectivity:

    • Onboard ports 0e and 0f configured in FC-VI mode.

    • Ports 1a and 1b on an FC-VI card in slot 1.

  • FAS9000 storage systems require four FC-VI ports. The following tables show cabling for the FC switches with four FC-VI ports on each controller.

    For other storage systems, use the cabling shown in the tables but ignore the cabling for FC-VI ports c and d.

    You can leave those ports empty.

Brocade port usage for controllers in a MetroCluster configuration

The following tables show port usage on Brocade switches. The tables show the maximum supported configuration, with eight controller modules in two DR groups. For smaller configurations, ignore the rows for the additional controller modules. Note that eight ISLs are supported on the Brocade 6510 and G620 switches.

Port usage for the Brocade 6505 switch in an eight-node MetroCluster configuration is not shown. Due to the limited number of ports, port assignments must be made on a site-by-site basis depending on the controller module model and the number of ISLs and bridge pairs in use.

The following table shows the cabling for the first DR group:

Brocade 6520, 6510, 6505, G620, G610, or 7840 switch

Component

Port

Switch 1

Switch 2

controller_x_1

FC-VI port a

0

FC-VI port b

-

0

FC-VI port c

1

-

FC-VI port d

-

1

HBA port a

2

-

HBA port b

-

2

HBA port c

3

-

HBA port d

-

3

controller_x_2

FC-VI port a

4

-

FC-VI port b

-

4

FC-VI port c

5

-

FC-VI port d

-

5

HBA port a

6

-

HBA port b

-

6

HBA port c

7

-

HBA port d

-

7

The following table shows the cabling for the second DR group:

Brocade 6510 Brocade 6520 Brocade G620

Component

Port

Switch 1

Switch 2

Switch 1

Switch 2

Switch 1

Switch 2

controller_x_3

FC-VI port a

24

-

48

-

18

-

FC-VI port b

-

24

-

48

-

18

FC-VI port c

25

-

49

-

19

-

FC-VI port d

-

25

-

49

-

19

HBA port a

26

-

50

-

24

-

HBA port b

-

26

-

50

-

24

HBA port c

27

-

51

-

25

-

HBA port d

-

27

-

51

-

25

controller_x_4

FC-VI port a

28

-

52

-

22

-

FC-VI port b

-

28

-

52

-

22

FC-VI port c

29

-

53

-

23

-

FC-VI port d

-

29

-

53

-

23

HBA port a

30

-

54

-

28

-

HBA port b

-

30

-

54

-

28

HBA port c

31

-

55

-

29

-

HBA port d

-

31

-

55

-

29

ISLs

ISL 1

40

40

23

23

40

40

ISL 2

41

41

47

47

41

41

ISL 3

42

42

71

71

42

42

ISL 4

43

43

95

95

43

43

ISL 5

44

44

Not supported

44

44

ISL 6

45

45

45

45

ISL 7

46

46

46

46

ISL 8

47

Cisco port usage for controllers in a MetroCluster configuration running ONTAP 9.4 or later

The tables show the maximum supported configuration, with eight controller modules in two DR groups. For smaller configurations, ignore the rows for the additional controller modules.

Cisco 9396S

Component

Port

Switch 1

Switch 2

controller_x_1

FC-VI port a

1

-

FC-VI port b

-

1

FC-VI port c

2

-

FC-VI port d

-

2

HBA port a

3

-

HBA port b

-

3

HBA port c

4

-

HBA port d

-

4

controller_x_2

FC-VI port a

5

-

FC-VI port b

-

5

FC-VI port c

6

-

FC-VI port d

-

6

HBA port a

7

-

HBA port b

-

7

HBA port c

8

-

HBA port d

-

8

controller_x_3

FC-VI port a

49

FC-VI port b

-

49

FC-VI port c

50

FC-VI port d

-

50

HBA port a

51

HBA port b

-

51

HBA port c

52

HBA port d

-

52

controller_x_4

FC-VI port a

53

-

FC-VI port b

-

53

FC-VI port c

54

-

FC-VI port d

-

54

HBA port a

55

-

HBA port b

-

55

HBA port c

56

-

HBA port d

-

56

Cisco 9148S

Component

Port

Switch 1

Switch 2

controller_x_1

FC-VI port a

1

-

FC-VI port b

-

1

FC-VI port c

2

-

FC-VI port d

-

2

HBA port a

3

-

HBA port b

-

3

HBA port c

4

-

HBA port d

-

4

controller_x_2

FC-VI port a

5

-

FC-VI port b

-

5

FC-VI port c

6

-

FC-VI port d

-

6

HBA port a

7

-

HBA port b

-

7

HBA port c

8

-

HBA port d

-

8

controller_x_3

FC-VI port a

25

FC-VI port b

-

25

FC-VI port c

26

-

FC-VI port d

-

26

HBA port a

27

-

HBA port b

-

27

HBA port c

28

-

HBA port d

-

28

controller_x_4

FC-VI port a

29

-

FC-VI port b

-

29

FC-VI port c

30

-

FC-VI port d

-

30

HBA port a

31

-

HBA port b

-

31

HBA port c

32

-

HBA port d

-

32

Cisco 9132T

MDS module 1

Component

Port

Switch 1

Switch 2

controller_x_1

FC-VI port a

1

-

FC-VI port b

-

1

FC-VI port c

2

-

FC-VI port d

-

2

HBA port a

3

-

HBA port b

-

3

HBA port c

4

-

HBA port d

-

4

controller_x_2

FC-VI port a

5

-

FC-VI port b

-

5

FC-VI port c

6

-

FC-VI port d

-

6

HBA port a

7

-

HBA port b

-

7

HBA port c

8

-

HBA port d

-

8 +4

MDS module 2

Component

Port

Switch 1

Switch 2

controller_x_3

FC-VI port a

1

-

FC-VI port b

-

1

FC-VI port c

2

-

FC-VI port d

-

2

HBA port a

3

-

HBA port b

-

3

HBA port c

4

-

HBA port d

-

4

controller_x_4

FC-VI port a

5

-

FC-VI port b

-

5

FC-VI port c

6

-

FC-VI port d

-

6

HBA port a

7

-

HBA port b

-

7

HBA port c

8

-

HBA port d

-

Note: The following table shows systems with two FC-VI ports. AFF A700 and FAS9000 systems have four FC-VI ports (a, b, c, and d). If using an AFF A700 or FAS9000 system, the port assignments move along by one position. For example, FC-VI ports c and d go to switch port 2 and HBA ports a and b go to switch port 3.

Cisco 9250i*

Component

Port

Switch 1

Switch 2

controller_x_1

FC-VI port a

1

-

FC-VI port b

-

1

HBA port a

2

-

HBA port b

-

2

HBA port c

3

-

HBA port d

-

3

controller_x_2

FC-VI port a

4

-

FC-VI port b

-

4

HBA port a

5

-

HBA port b

-

5

HBA port c

6

-

HBA port d

-

6

controller_x_3

FC-VI port a

7

-

FC-VI port b

-

7

HBA port a

8

-

HBA port b

-

8

HBA port c

9

-

HBA port d

-

9

controller_x_4

FC-VI port a

10

-

FC-VI port b

-

10

HBA port a

11

-

HBA port b

-

11

HBA port c

13

-

HBA port d

-

13

Note: The Cisco 9250i switch is not supported for eight-node MetroCluster configurations.

Shared initiator and shared target support for MetroCluster configuration with array LUNs

Being able to share a given FC initiator port or target ports is useful for organizations that want to minimize the number of initiator or target ports used. For example, an organization that expects low I/O usage over an FC initiator port or target ports might prefer to share FC initiator port or target ports instead of dedicating each FC initiator port to a single target port.

However sharing of initiator or target ports can adversely affect performance.