Configuration rules and requirements Configuration rules

This topic describes the rules and requirements for configuring a SAN Volume Controller. It also provides a list of defined terms that are referenced in the configuration rules. Before you read the rules, read these definitions, which can help you to understand the rules.

Properties
ISL hop
A hop on an Inter-Switch Link (ISL).

With reference to all pairs of N-ports or end-nodes that are in a fabric, an ISL hop is the number of links that are crossed on the shortest route between the node pair whose nodes are farthest apart from each other. The distance is measured only in terms of the ISL links that are in the fabric.

oversubscription
The ratio of the sum of the traffic that is on the initiator N-node connections to the traffic that is on the most heavily-loaded ISLs, where more than one ISL is in parallel between these switches.

This definition assumes a symmetrical network and a specific workload that is applied equally from all initiators and sent equally to all targets. A symmetrical network means that all initiators are connected at the same level and all the controllers are connected at the same level.

The SAN Volume Controller makes this calculation difficult, because it puts its back-end traffic onto the same network, and this back-end traffic varies by workload. Therefore, the oversubscription that a 100% read hit gives is different from the oversubscription that 100% write-miss gives.

If you have an oversubscription of 1 or less, the network is nonblocking.

redundant SAN
A SAN configuration in which if any one component fails, connectivity between the devices that are in the SAN is maintained, possibly with degraded performance. The way to make a redundant SAN is to split the SAN into two independent counterpart SANs.
counterpart SAN
A non-redundant portion of a redundant SAN. A counterpart SAN provides all the connectivity of the redundant SAN, but without the redundancy. The SAN Volume Controller is typically connected to a redundant SAN that is made out of two counterpart SANs.
local fabric
The fabric that consists of those SAN components (switches and cables) that connect the components (nodes, hosts, and switches) of the local cluster.

Because the SAN Volume Controller supports Remote Copy, significant distances might exist between the components of the local cluster and those of the remote cluster.

remote fabric
The fabric that consists of those SAN components (switches and cables) that connect the components (nodes, hosts, and switches) of the remote cluster.

Because the SAN Volume Controller supports remote copy, significant distances might exist between the components of the local cluster and those of the remote cluster.

Local/Remote fabric interconnect
The SAN components that connect the local fabrics to the remote fabrics. These components might be single-mode optical fibres that are driven by Gigabit Interface Converters (GBICs), or they might be other, more advanced components, such as channel extenders.
SAN Volume Controller Fibre Channel port fan in
The number of hosts that can see any one SAN Volume Controller.

Some controllers recommend that the number of hosts that use each port be limited to prevent excessive queuing at that port. If the port fails, or the path to that port fails, the host might failover to another port, and the fan-in requirements might be exceeded in this degraded mode.

Invalid configuration
A configuration that refuses to operate and generates an error code to indicate what caused it to become invalid.
Unsupported configuration
A configuration that might operate successfully, but for which IBM does not guarantee to be able to solve problems that might occur.

Usually this type of configuration does not create an error log.

Valid configuration
A configuration that is neither invalid nor unsupported.
Degraded
A valid configuration that has had a failure, but continues to be neither invalid nor unsupported.

Typically, a repair action is required to restore the degraded configuration to a valid configuration.

(C) Copyright International Business Machines Corporation 2003, 2004