
2 – General Description Supported Network Configurations
Q
2.3.3.1
How the Solution Protects Against Failures
The following tables provides a list of common failure points in a network and the corresponding protection that this 
Table 
| Failed Component: | Protection: | 
| HBA or path to | Host software uses a remaining HBA or path to the same SANbox | 
| SANbox SSP | SSP | 
| 
 | 
 | 
| All HBAs or paths to | Virtual volume becomes active on alternate SANbox SSP, host | 
| one SANbox SSP | software uses alternate HBA | 
| 
 | 
 | 
| One SANbox SSP | Virtual volume becomes active on alternate SANbox SSP, host | 
| 
 | software uses alternate HBA | 
| 
 | 
 | 
| One path between | ■  | 
| one SANbox SSP | ■ LUN uses alternate storage controller, if necessary | 
| and storage | 
 | 
| 
 | 
 | 
| All paths between | ■ Virtual volume becomes active on alternate SANbox SSP | 
| one SANbox SSP | ■ Host software uses alternate HBA | 
| and storage | 
 | 
| 
 | 
 | 
| Storage controller | ■  | 
| 
 | 
 | 
| SVM appliance | Alternate SVM appliance takes over system management | 
| 
 | 
 | 
| One or more paths | Alternate SVM appliance takes over system management | 
| between one SVM | 
 | 
| and one SANbox | 
 | 
| SSP | 
 | 
| 
 | 
 | 
2.3.3.2
Setup Requirements
To configure a 
■Each HBA sees only one SANbox SSP.
■Each host sees both SANbox SSP in the 
■Each StoreAge SVM appliance sees both SANbox SSPs.
■Each StoreAge SVM appliance sees all storage ports.
■If the storage includes 
