Information gathering worksheet for FC-to-SAS bridges
-
PDF of this doc site
- Install a fabric-attached MetroCluster
- Install a MetroCluster IP configuration
- Install a stretch MetroCluster configuration
- Transition from MetroCluster FC to MetroCluster IP
Collection of separate PDF docs
Creating your file...
Before beginning to configure the MetroCluster sites, you should gather required configuration information.
Site A, FC-to-SAS bridge 1 (FC_bridge_A_1a)
Each SAS stack requires at least two FC-to-SAS bridges.
Each bridge connects to Controller_A_1_port-number
and Controller_B_1_port-number
.
Site A |
Your value |
---|---|
Bridge_A_1a IP address |
|
Bridge_A_1a Username |
|
Bridge_A_1a Password |
Site A, FC-to-SAS bridge 2 (FC_bridge_A_1b)
Each SAS stack requires at least two FC-to-SAS bridges.
Each bridge connects to Controller_A_1_port-number
and Controller_B_1_port-number
.
Site A |
Your value |
---|---|
Bridge_A_1b IP address |
|
Bridge_A_1b Username |
|
Bridge_A_1b Password |
Site B, FC-to-SAS bridge 1 (FC_bridge_B_1a)
Each SAS stack requires at least two FC-to-SAS bridges.
Each bridge connects to Controller_A_1_`port-number` and Controller_B_1_`port-number`.
Site B |
Your value |
---|---|
Bridge_B_1a IP address |
|
Bridge_B_1a Username |
|
Bridge_B_1a Password |
Site B, FC-to-SAS bridge 2 (FC_bridge_B_1b)
Each SAS stack requires at least two FC-to-SAS bridges.
Each bridge connects to Controller_A_1_`port-number` and Controller_B_1_`port-number`.
Site B |
Your value |
---|---|
Bridge_B_1b IP address |
|
Bridge_B_1b Username |
|
Bridge_B_1b Password |