This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
storage:svc_esc_config [2024/11/08 00:05] manu [Storage connectivity] |
storage:svc_esc_config [2025/03/17 17:17] (current) manu |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Example of cabling | Example of cabling | ||
| - | In the best recommandations, alternate one port on Fabric SAN A, then a port on B... | + | In the best recommandations, alternate one port on Fabric SAN A (blue), then a port on B (red)... |
| + | |||
| + | {{:storage:svc_fc_connexions_08.png?4000}} | ||
| + | |||
| + | {{:storage:svc_fc_connexions_09.png?2000}} | ||
| - | {{:storage:SVC SA2-SV3 connection.png?650}} | ||
| Set the port mask to 11, so only ports 1 and 2 are able to communicate in node | Set the port mask to 11, so only ports 1 and 2 are able to communicate in node | ||
| <cli prompt='>'> | <cli prompt='>'> | ||
| - | SVC:superuser>chsystem -localfcportmask 00000011 | + | SVC:superuser>chsystem -localfcportmask 00001100 |
| SVC:superuser>lssystem |grep mask | SVC:superuser>lssystem |grep mask | ||
| - | local_fc_port_mask 0000000000000000000000000000000000000000000000000000000000000011 | + | local_fc_port_mask 00000000000000000000000000000000000000000000000000000000001100 |
| </cli> | </cli> | ||
| - | FIXME Why using 2 set of ports for host with different speed ?\\ | + | FIXME Why using 2 set of ports for host with different speed flagged 16Gb and 32Gb?\\ |
| - | It's a best practice preventing SVC ports to negotiate between different speeds on hosts | + | It's a best practice preventing SVC ports to negotiate between different speeds on hosts. Dedicated ports for high speed traffic. But on SAN switches leave the auto-negotiation so both can do 32Gb. |
| {{:storage:SAN zoning for SVC enhanced stretch cluster.png?650}} | {{:storage:SAN zoning for SVC enhanced stretch cluster.png?650}} | ||