HSG80 ACS Solution Software V8.6 for Windows NT and Windows 2000 Installation and Configuration Guide

Figures
Figure 1 General configuration flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Figure 2 Configuring storage with the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Figure 3 Configuring storage with SWCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Figure 1–1 Location of controllers and cache modules in a Model 2200 enclosure . . . . . . . . . . . 1–2
Figure 1–2 Location of controllers and cache modules in a BA370 enclosure . . . . . . . . . . . . . . . 1–3
Figure 1–3 “This controller” and “other controller” for the Model 2200 enclosure . . . . . . . . . . . 1–4
Figure 1–4 “This controller” and “other controller” for the BA370 enclosure . . . . . . . . . . . . . . . 1–4
Figure 1–5 Transparent failover
normal operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Figure 1–6 Transparent failover
after failover from controller B to controller A . . . . . . . . . . . 1–7
Figure 1–7 Typical multiple-bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
Figure 1–8 Mirrored caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
Figure 1–9 Connections in separate-link, transparent failover mode configurations . . . . . . . . . 1–14
Figure 1–10 Connections in single-link, transparent failover mode configurations . . . . . . . . . . 1–15
Figure 1–11 Connections in multiple-bus failover mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16
Figure 1–12 LUN presentation to hosts, as determined by offset . . . . . . . . . . . . . . . . . . . . . . . . 1–18
Figure 1–13 Limiting host access in transparent failover mode . . . . . . . . . . . . . . . . . . . . . . . . . 1–22
Figure 1–14 Limiting host access in multiple-bus failover mode . . . . . . . . . . . . . . . . . . . . . . . . 1–25
Figure 1–15 Placement of the worldwide name label on the Model 2200 enclosure . . . . . . . . . 1–28
Figure 1–16 Placement of the worldwide name label on the BA370 enclosure . . . . . . . . . . . . . 1–29
Figure 2–1 PTL naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Figure 2–2 PTL addressing in a configuration in a BA370 enclosure. . . . . . . . . . . . . . . . . . . . . . 2–4
Figure 2–3 PTL addressing in a single-bus configuration, six Model 4310R disk enclosures . . . 2–6
Figure 2–4 PTL addressing in a dual-bus configuration, three Model 4350R disk enclosures. . . 2–7
Figure 2–5 PTL addressing in a single-bus configuration, six Model 4314R disk enclosures . . . 2–8
Figure 2–6 PTL addressing in a dual-bus configuration, three Model 4354R disk enclosures. . . 2–9
Figure 2–7 Mapping a unit to physical disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Figure 2–8 Container types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Figure 2–9 An example storageset profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Figure 2–10 A 3-member RAID 0 stripeset (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14