ClearPath Dorado 300/400/700/800/4000/4100/4200 Server I/O ...

ClearPath
Dorado
300/400/700/800/4000/4100/4200
Server
I/O Planning Guide
October 2012 3839 6586–010
unisys

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information
described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to
purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the
products described in this document are set forth in such agreement. Unisys cannot accept any financial or other
responsibility that may be the result of your use of the information in this document or software material, including
direct, special, or consequential damages.
You should be very careful to ensure that the use of this information and/or software material complies with the
laws, rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice. Revisions may be issued to advise of such
changes and/or additions.
Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed
at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard
commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract
data rights clauses.
Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries.
All other brands and products referenced in this document are acknowledged to be the trademarks or registered
trademarks of their respective holders.

Contents
Section 1. PCI-Based I/O Hardware
1.1. Architecture Overview ...................................................................... 1–1
1.1.1. Dorado 300 Series .................................................................... 1–1
1.1.2. Dorado 700 Series.................................................................... 1–2
1.1.3. Dorado 800 Series ................................................................... 1–4
1.1.4. Dorado 400 Server ................................................................... 1–6
1.1.5. Dorado 4000 Server ................................................................ 1–7
1.1.6. Dorado 4100 Server ................................................................. 1–9
1.1.7. Dorado 4200 Series ................................................................ 1–11
1.2. I/O Module Overview ...................................................................... 1–13
1.2.1. PCI Standard ............................................................................ 1–14
1.2.2. I/O Bus Layout......................................................................... 1–15
1.2.3. Dorado 300 and Dorado 400 IOPs ..................................... 1–16
1.2.4. Dorado 700, Dorado 800, Dorado 4000, Dorado
4100 and Dorado 4200 IOPs (PCIOP-M and
PCIOP-E) ............................................................................... 1–18
1.2.5. Host Bus Adapters ................................................................ 1–18
1.2.6. Network Interface Card ........................................................ 1–18
1.3. I/O Modules and Components ...................................................... 1–19
1.3.1. I/O Module for the Dorado 300 and 400 .......................... 1–19
1.3.2. I/O Module (Internal or External) for the Dorado
700 ......................................................................................... 1–21
1.3.3. I/O Expansion Module (Internal or External) for
the Dorado 800 .................................................................. 1–23
1.3.4. I/O Expansion Module for the Dorado 4000 ................... 1–25
1.3.5. I/O Expansion Module for the Dorado 4100 .................... 1–27
1.3.6. PCI Host Bridge Card ............................................................. 1–28
1.3.7. PCI Expansion Rack ............................................................... 1–28
1.3.8. Dorado 700/4000/4100 Expansion Rack or PCI
Channel Module (DOR385-EXT) ..................................... 1–29
1.3.9. Configuration Restriction ..................................................... 1–30
1.3.10. Dorado 300 I/O Addressing ................................................. 1–33
1.3.11. SCMS II and I/O Addressing ................................................ 1–35
1.4. Host Bus Adapters .......................................................................... 1–37
1.4.1. Fibre Channel ........................................................................... 1–37
1.4.2. SCSI ............................................................................................ 1–39
1.4.3. SBCON ...................................................................................... 1–43
1.4.4. FICON ....................................................................................... 1–44
1.5. Ethernet NIC ...................................................................................... 1–46
1.5.1. Original Ethernet ..................................................................... 1–46
1.5.2. Fast Ethernet - 802.3u ........................................................... 1–46
1.5.3. Gigabit Ethernet ...................................................................... 1–46
1.5.4. Connecting NICs ..................................................................... 1–47
3839 6586–010 iii

Contents
1.5.5. NIC Styles .................................................................................1–48
1.5.6. Single-Port Fiber Ethernet Handle and
Connector ............................................................................ 1–49
1.5.7. Single-Port Copper Ethernet Handle and
Connector ............................................................................ 1–50
1.5.8. Dual-Port Fiber NIC ................................................................ 1–51
1.5.9. Dual-Port Copper NIC ............................................................ 1–52
1.5.10. SAIL Peripherals ...................................................................... 1–53
1.6. Other PCI Cards ................................................................................ 1–54
1.6.1. DVD Interface Card ................................................................ 1–54
1.6.2. XIOP Myrinet Card ................................................................. 1–55
1.6.3. Clock Synchronization Board ............................................... 1–57
1.6.4. Cipher API Hardware Accelerator Appliance .................. 1–61
Section 2. Channel Configurations
2.1. Fibre Channel ....................................................................................... 2–1
2.1.1. Fibre Channel on SIOP ............................................................. 2–2
2.1.2. Direct-Connect Disks (JBOD) ................................................ 2–2
2.1.3. Symmetrix Disk Systems ....................................................... 2–5
2.1.4. CLARiiON Disk Systems ....................................................... 2–10
2.1.5. T9x40 Family of Tape Drives .............................................. 2–16
2.1.6. 9x40 Tape Drives on Multiple Channels Across
a SAN .................................................................................... 2–19
2.1.7. Connecting SCSI Tapes to a SAN .......................................2–27
2.2. SCSI ..................................................................................................... 2–28
2.2.1. Direct-Connect Disks (JBOD) ............................................. 2–30
2.2.2. Control-Unit-Based Disks .................................................... 2–32
2.3. SBCON ............................................................................................... 2–35
2.3.1. SCMS II Configuration Guidelines ..................................... 2–36
2.3.2. Directors .................................................................................. 2–38
2.4. FICON ................................................................................................. 2–42
2.4.1. FICON on SIOP ....................................................................... 2–42
2.4.2. SCMS II Configuration Guidelines ..................................... 2–43
2.4.3. Switch Configuration Guidelines ....................................... 2–46
Section 3. Mass Storage
3.1. EMC Systems ...................................................................................... 3–1
3.1.1. Disk .............................................................................................. 3–1
3.1.2. Control Unit ................................................................................ 3–1
3.1.3. Channel ....................................................................................... 3–2
3.1.4. Path .............................................................................................. 3–2
3.1.5. Subsystem ................................................................................. 3–2
3.1.6. Daisy-Chained Control Units ................................................. 3–3
3.2. OS 2200 I/O Algorithms ................................................................... 3–4
3.2.1. Not Always First In, First Out ............................................... 3–4
3.2.2. Disk Queuing (Not Using I/O Command
Queuing) ................................................................................3–5
3.2.3. I/O Command Queuing .......................................................... 3–6
3.2.4. Multiple Active I/Os on a Channel ...................................... 3–8
iv 3839 6586–010

Section 4. Tapes
Contents
3.2.5. Standard I/O Timeout Processing ....................................... 3–9
3.2.6. Multiple Control Units per Subsystem .............................. 3–9
3.2.7. Multiple Channels per Control Unit ................................... 3–10
3.2.8. Configuring Symmetrix Systems in SCMS II ................... 3–11
3.3. OS 2200 Miscellaneous Characteristics ..................................... 3–12
3.3.1. Formatting ................................................................................ 3–12
3.3.2. 504 Bytes per Sector ............................................................ 3–13
3.3.3. Multi-Host File Sharing .......................................................... 3–13
3.4. EMC Hardware .................................................................................. 3–14
3.4.1. Components ............................................................................ 3–15
3.4.2. Disks .......................................................................................... 3–15
3.5. Disk Performance ............................................................................. 3–17
3.5.1. Definitions ................................................................................ 3–18
3.5.2. Queue Time ............................................................................. 3–19
3.5.3. Hardware Service Time ....................................................... 3–20
3.5.4. Little’s Law .............................................................................. 3–25
3.5.5. Request Existence Time ..................................................... 3–27
3.5.6. Disk Performance Analysis Tips ........................................ 3–27
3.6. Symmetrix Remote Data Facility (SRDF)
Considerations ............................................................................ 3–29
3.6.1. Synchronous Mode ............................................................... 3–30
3.6.2. Asynchronous Mode ............................................................. 3–31
3.6.3. Adaptive Copy Mode ........................................................... 3–32
3.6.4. SRDF Performance ............................................................... 3–32
3.6.5. SRDF Synchronous Mode Time Delay
Calculation .......................................................................... 3–33
4.1. 36-Track Tapes ................................................................................... 4–1
4.2. T9840 and 9940 Tape Families ...................................................... 4–2
4.2.1. T9840 Family ............................................................................ 4–2
4.2.2. T9940B ....................................................................................... 4–3
4.2.3. T10000A ..................................................................................... 4–3
4.2.4. T9840/9940 Performance Advantages ............................. 4–4
4.2.5. Operating Considerations ..................................................... 4–5
4.3. T9x40 Hardware Capabilities ......................................................... 4–6
4.3.1. Serpentine Recording ............................................................ 4–6
4.3.2. Compression ............................................................................ 4–7
4.3.3. Super Blocks............................................................................. 4–8
4.3.4. Data Buffer ................................................................................ 4–8
4.3.5. Streaming Tapes...................................................................... 4–9
4.3.6. Tape Repositioning ................................................................. 4–9
4.3.7. OS 2200 Logical Tape Blocks .............................................. 4–10
4.3.8. Synchronization ....................................................................... 4–12
4.3.9. Tape Block-ID .......................................................................... 4–13
4.3.10. Tape Block Size ....................................................................... 4–13
4.4. Optimizing T9x40 Tape Performance ......................................... 4–15
4.4.1. Tape Mark Buffering.............................................................. 4–15
4.4.2. How to Use Tape Mark Buffering...................................... 4–17
4.4.3. Fast Tape Access ...................................................................4–18
3839 6586–010 v

Contents
4.4.4. Block Size ................................................................................ 4–20
4.4.5. Compression .......................................................................... 4–23
4.4.6. FURPUR COPY Options G, D, and E.................................. 4–24
4.5. Tape Drive Encryption .................................................................... 4–25
4.5.1. Tape Drives capable of supporting encryption ............. 4–26
4.5.2. Restrictions ............................................................................. 4–26
4.6. Sharing Tapes Across Multiple Partitions ................................. 4–26
4.6.1. Electronic Partitioning on Fibre Channel .......................... 4–27
4.6.2. Automation ............................................................................. 4–27
Section 5. Performance
5.1. Overview .............................................................................................. 5–1
5.1.1. Basic Concepts ......................................................................... 5–1
5.1.2. Performance Numbers and Your Site ............................... 5–10
5.2. SIOP ..................................................................................................... 5–11
5.2.1. SIOP Performance .................................................................. 5–13
5.2.2. Fibre HBA Performance ........................................................ 5–17
5.2.3. Sequential File Transfers ...................................................... 5–21
5.3. SCSI HBA ........................................................................................... 5–23
5.4. SBCON HBA ...................................................................................... 5–23
5.5. FICON HBA ........................................................................................ 5–24
5.6. Tape Drives per Channel Guidelines .......................................... 5–26
5.7. CIOP Performance—Communications ...................................... 5–26
5.8. Redundancy ...................................................................................... 5–27
5.8.1. Expansion Racks .................................................................... 5–27
5.8.2. Dual Channel HBAs and NICs ............................................. 5–27
5.8.3. Single I/O Modules ................................................................ 5–28
5.8.4. Configuration Recommendations ..................................... 5–28
Section 6. Storage Area Networks
6.1. Arbitrated Loop ................................................................................... 6–2
6.2. Switched Fabric ................................................................................. 6–4
6.3. Switches ............................................................................................... 6–7
6.4. Storage Devices ................................................................................. 6–7
6.4.1. Arbitrated Loop Devices Running in a SAN ....................... 6–7
6.4.2. T9840 Family of Tape Drives ............................................... 6–8
6.4.3. JBODs ........................................................................................ 6–8
6.4.4. SCSI/Fibre Channel Converters ............................................ 6–9
6.5. SAN Addressing ............................................................................... 6–10
6.5.1. OS 2200 Addressing .............................................................. 6–11
6.5.2. SCMS II ...................................................................................... 6–12
6.5.3. OS 2200 Console .................................................................... 6–13
6.5.4. SAN Addressing Examples .................................................. 6–14
6.6. Zoning .................................................................................................. 6–17
6.6.1. Zoning and 12-Bit OS 2200 Addressing ............................ 6–17
6.6.2. Guidelines ................................................................................. 6–17
6.6.3. Zoning Disks ............................................................................ 6–18
6.6.4. Zoning with Multiple Switches ........................................... 6–19
vi 3839 6586–010

Contents
6.6.5. Multihost or Multipartition Zoning .................................... 6–20
6.6.6. Remote Backup Zoning ........................................................ 6–21
Section 7. Peripheral Systems
Section 8. Cabling
7.1. Tape Drives .......................................................................................... 7–1
7.1.1. LTO ............................................................................................... 7–1
7.1.2. T9840D Tape Subsystem ....................................................... 7–5
7.1.3. T10000A Tape System ............................................................ 7–6
7.1.4. T9840D and T10000A Applicable .........................................7–8
7.1.5. T9940B Tape Subsystem ....................................................... 7–9
7.1.6. T9840A Tape Subsystem ..................................................... 7–12
7.1.7. T9840C Tape Subsystem ..................................................... 7–15
7.1.8. T7840A Cartridge ................................................................... 7–18
7.1.9. T9840B Cartridge ................................................................... 7–18
7.1.10. T9840A Cartridge ................................................................... 7–19
7.1.11. DLT 7000 and DLT 8000 Tape Subsystems .................... 7–19
7.1.12. OST5136 Cartridge .................................................................7–22
7.1.13. OST4890 Cartridge ............................................................... 7–23
7.1.14. 4125 Open Reel ...................................................................... 7–24
7.2. Cartridge Library Units ................................................................... 7–24
7.2.1. SL3000 ..................................................................................... 7–24
7.2.2. SL8500 ..................................................................................... 7–24
7.2.3. CLU5500 .................................................................................. 7–25
7.2.4. CLU700 ..................................................................................... 7–25
7.2.5. CLU180 ..................................................................................... 7–25
7.2.6. CLU9740 .................................................................................. 7–25
7.2.7. CLU9710 ................................................................................... 7–25
7.2.8. CLU6000 .................................................................................. 7–25
7.3. EMC Symmetrix Disk Family ........................................................ 7–26
7.3.1. EMC Virtual Matrix (V-Max) Series ................................... 7–26
7.3.2. Symmetrix DMX Series ........................................................7–27
7.3.3. Symmetrix 8000 Series ........................................................7–27
7.3.4. Symmetrix 5 and Earlier Series ..........................................7–27
7.4. CLARiiON Disk Family .................................................................... 7–29
7.4.1. CLARiiON Multipath .............................................................. 7–29
7.4.2. Without CLARiiON Multipath .............................................. 7–31
7.4.3. LUNs ......................................................................................... 7–33
7.4.4. CX Series ................................................................................. 7–35
7.4.5. ESM/CSM Series ................................................................... 7–36
7.5. Just a Bunch of Disks (JBOD) ...................................................... 7–37
7.5.1. JBD2000 .................................................................................. 7–37
7.5.2. CSM700.................................................................................... 7–37
7.6. Other Systems ................................................................................. 7–37
8.1. SCSI ........................................................................................................ 8–1
8.2. Fibre Channel .......................................................................................8–2
8.3. SBCON ..................................................................................................8–2
8.4. FICON ................................................................................................... 8–8
3839 6586–010 vii

Contents
8.5. PCI-Based IOPs .................................................................................. 8–8
8.5.1. Ethernet NICs ........................................................................... 8–8
8.5.2. Communications IOP (CIOP) ................................................. 8–9
8.5.3. XPC-L IOP (XIOP) ...................................................................... 8–9
Section 9. Peripheral Migration
9.1. Central Equipment Complex (CEC) ................................................ 9–1
9.2. I/O Processors (IOP) .......................................................................... 9–2
9.3. Tape Migration Issues....................................................................... 9–2
9.3.1. BMC-Connected Tapes ........................................................... 9–2
9.3.2. 18-Track Proprietary (5073) Compression ......................... 9–2
9.3.3. Read-Backward Functions .................................................... 9–3
9.3.4. CSC Tape Library Software................................................... 9–3
9.4. Tape Devices ...................................................................................... 9–3
9.4.1. Supported Cartridge Library Units ...................................... 9–6
9.4.2. End-of-Life Tape Devices ...................................................... 9–6
9.4.3. End-of-Life Tape Libraries ...................................................... 9–7
9.5. Disk Devices ........................................................................................ 9–7
9.5.1. Supported Disks ....................................................................... 9–7
9.5.2. SAIL Disks ................................................................................ 9–10
9.5.3. Supported DVDs ..................................................................... 9–11
9.5.4. Non-RoHS Host Bus Adapters (HBAs) ............................. 9–12
9.5.5. RoHS Host Bus Adapters (HBAs) ...................................... 9–12
9.5.6. SAIL Host Bus Adapters (HBAs) ........................................ 9–13
9.5.7. End-of-Life Disks .................................................................... 9–13
9.6. Device Mnemonics .......................................................................... 9–13
9.7. Communications Migration Issues .............................................. 9–18
9.7.1. DCP ............................................................................................ 9–18
9.7.2. FEP Handler .............................................................................. 9–18
9.7.3. HLC ............................................................................................. 9–19
9.7.4. CMS 1100 .................................................................................. 9–19
9.7.5. FDDI ........................................................................................... 9–19
9.8. Network Interface Cards ................................................................ 9–19
9.8.1. Dorado 300, 400, and 700 Series Systems ..................... 9–19
9.8.2. Dorado 4000 Series Systems ............................................ 9–20
9.8.3. Dorado 4100 Series Systems ............................................. 9–20
9.8.4. Dorado 4200 Series Systems ............................................ 9–20
9.9. Other Migration Issues ................................................................... 9–21
9.9.1. Network Multihost File Sharing .......................................... 9–21
9.9.2. NETEX and HYPERchannel ................................................... 9–21
9.9.3. Traditional ADH ....................................................................... 9–21
9.9.4. DPREP ........................................................................................ 9–21
Appendix A. Fibre Channel Addresses
Appendix B. Fabric Addresses
Appendix C. Key Hardware Enhancements by Software Release
viii 3839 6586–010

Appendix D. Requesting Configuration Assistance
Contents
Index ..................................................................................................... 1
3839 6586–010 ix

Contents
x 3839 6586–010

Figures
1–1. Dorado 300 Series Cabinet Layout .............................................................................. 1–2
1–2. I/O Module for the Dorado 800 (Front View) ............................................................ 1–4
1–3. I/O Module for the Dorado 800 (Rear View) ............................................................. 1–5
1–4. Dorado 400 Series Cabinet Layout .............................................................................. 1–7
1–5. Dorado 4000 Series Cabinet Layout with One to Two I/O Expansion
Modules ......................................................................................................................... 1–8
1–6. Dorado 4050 Server Cabinet Layout ........................................................................... 1–9
1–7. Dorado 4100 Series Cabinet Layout with One to Two I/O Expansion
Modules ....................................................................................................................... 1–10
1–8. Dorado 4150 Server Cabinet Layout .......................................................................... 1–11
1–9. I/O manager for the Dorado 4200 Series ................................................................. 1–12
1–11. Primary and Secondary PCI Bus Location ................................................................ 1–16
1–12. IOP Card ............................................................................................................................ 1–17
1–13. Top View of the I/O Module ........................................................................................ 1–20
1–14. I/O Module Connection to Expansion Racks .......................................................... 1–21
1–15. Internal I/O Module Layout for the Dorado 700 ..................................................... 1–21
1–16. Remote (External) I/O Module Layout for the Dorado 700 ................................. 1–22
1–17. IOPs in an I/O Module ................................................................................................... 1–22
1–18. Minimum Connection Configuration for Dorado 4000 I/O .................................. 1–26
1–19. Maximum Configuration for Dorado 4000 I/O ........................................................ 1–26
1–20. Minimum Connection Configuration for Dorado 4100 I/O ................................... 1–27
1–21. Maximum Configuration for Dorado 4100 I/O ........................................................ 1–27
1–22. PCI Host Bridge Card Handle and Connector ......................................................... 1–28
1–23. PCI Expansion Rack Layout ......................................................................................... 1–30
1–24. Dorado 300 Cabinet with IP Cells and I/O Cells ..................................................... 1–33
1–25. OS 2200 I/O Addressing ............................................................................................... 1–35
1–26. Fibre Card Handle With Dual Ports ............................................................................ 1–38
1–27. SCSI Channel Card Handle ........................................................................................... 1–41
1–28. SCSI LVD – HVD Converter .......................................................................................... 1–42
1–29. SBCON Channel Card Handle ...................................................................................... 1–43
1–30. Bus-Tech FICON HBA .................................................................................................... 1–45
1–31. Single-Port Fiber Ethernet Handle and Connector ................................................. 1–49
1–32. Single-Port Copper Ethernet Handle and Connector ............................................ 1–50
1–33. Dual-Port Fiber NIC ........................................................................................................ 1–52
1–34. Dual-Port Copper NIC .................................................................................................... 1–53
1–35. IDE Cable Connection on DVD Interface Card ........................................................ 1–55
1–36. Myrinet Card 2G and Connector ................................................................................. 1–56
1–37. Myrinet Card 10G ............................................................................................................ 1–56
1–38. Clock Synchronization Board ....................................................................................... 1–58
1–39. CSB Handle and BNC Connector ................................................................................ 1–58
2–1. Example JBOD Configuration (First 4 of 18 Disks) ................................................. 2–4
2–2. Arbitrated Loop ................................................................................................................. 2–7
3839 6586–010 xi

Figures
2–3. OS 2200 View of Arbitrated Loop Example ..............................................................2–8
2–4. Switched Fabric Example ............................................................................................... 2–9
2–5. OS 2200 View of Switched Fabric Example ............................................................ 2–10
2–6. Direct-Attach CLARiiON System ................................................................................ 2–12
2–7. OS 2200 View of Channel for Nonredundant Disks .............................................. 2–13
2–8. Unit-Duplexed Configuration ....................................................................................... 2–14
2–9. Multihost Configuration ................................................................................................ 2–18
2–10. OS 2200 View of Tape Drives ..................................................................................... 2–18
2–11. Load-Balanced SAN ...................................................................................................... 2–20
2–12. Daisy Chaining with Eight Control Units ................................................................... 2–21
2–13. Redundant SAN ............................................................................................................. 2–23
2–14. Redundant Daisy Chaining .......................................................................................... 2–24
2–15. Redundant SAN with Remote Tapes ........................................................................2–27
2–16. FC / SCSI Converter ...................................................................................................... 2–28
2–17. Single-Port Configuration ............................................................................................ 2–30
2–18. JBOD Disk Configuration............................................................................................. 2–32
2–19. SCSI Disk Configuration Example (Only 16 of the 80 Disks Shown) ................ 2–34
2–20. Tapes Using SBCON Directors .................................................................................. 2–37
2–21. Configuring Two Hosts Through One Director ..................................................... 2–39
2–22. Configuring Two Hosts Through Two Directors ................................................... 2–40
2–23. Chained SBCON Directors .......................................................................................... 2–42
3–1. OS 2200 Architecture Subsystem .............................................................................. 3–3
3–2. Daisy-Chained JBOD Disks ........................................................................................... 3–4
3–3. I/O Request Servicing Without IOCQ .........................................................................3–5
3–4. The Effect of IOCQ.......................................................................................................... 3–6
3–5. Time for One I/O .............................................................................................................. 3–8
3–6. Time for Multiple I/Os .................................................................................................... 3–9
3–7. Single-Channel Control Units (CU).............................................................................. 3–10
3–8. Multiple Channel Control Units ................................................................................... 3–11
3–9. EMC Symmetrix Data Flow.......................................................................................... 3–14
3–10. Disk Device Terminology ............................................................................................. 3–16
3–11. I/O Request Time Breakdown .................................................................................... 3–17
3–12. Disk Queue Impact ....................................................................................................... 3–20
3–13. Transfer Time ................................................................................................................. 3–23
3–14. Hardware Service Time Affected by Cache-Hit Rate .......................................... 3–24
3–15. Requests Join a Queue ............................................................................................... 3–25
3–16. Response Time .............................................................................................................. 3–26
3–17. Queue Sizes .................................................................................................................... 3–27
3–18. SRDF Modes ................................................................................................................... 3–30
3–19. Synchronous Mode ........................................................................................................ 3–31
4–1. 36-Track Tape .................................................................................................................... 4–1
4–2. Helical Scan ....................................................................................................................... 4–7
4–3. 288-Track Tape ................................................................................................................ 4–7
4–4. File on a Labeled Tape .................................................................................................. 4–11
4–5. T9840A/B Write Performance ................................................................................... 4–14
5–1. Dorado 300 and Dorado 400 PCI Bus Structure ......................................................5–3
5–2. Dorado 700, Dorado 4000, and Dorado 4100 PCI Bus Structure ........................ 5–4
5–3. Dorado 800 and Dorado 4200 PCI Bus Structure ....................................................5–5
5–4. SIOP: Dorado 300 I/Os per Second ........................................................................... 5–13
xii 3839 6586–010

Figures
5–5. SIOP: Dorado 700 I/Os per Second ........................................................................... 5–13
5–6. SIOP: Dorado 800 I/Os per Second ........................................................................... 5–14
5–7. SIOP: Dorado 4200 I/Os per Second ......................................................................... 5–14
5–8. SIOP: Dorado 300 MB per Second ............................................................................ 5–15
5–9. SIOP: Dorado 700 MB per Second ............................................................................ 5–15
5–10. SIOP: Dorado 800 MB per Second ............................................................................ 5–15
5–11. SIOP: Dorado 4200 MB per Second .......................................................................... 5–16
5–12. Dorado 800 I/O Manager Throughput Ratios ......................................................... 5–16
5–13. Dorado 4200 I/O Manager Throughput Ratios ....................................................... 5–17
5–14. SIOP Fibre HBA: I/Os per Second .............................................................................. 5–18
5–15. Dorado 800 Single Port Fibre HBA: I/Os per Second............................................ 5–18
5–16. Dorado 4200 Single Port Fibre HBA: I/Os per Second ......................................... 5–19
5–17. SIOP Fibre HBA: MB per Second ............................................................................... 5–19
5–18. Dorado 800 Single Port Fibre HBA: MB per Second ............................................ 5–20
5–19. Dorado 4200 Single Port Fibre HBA: MB per Second ......................................... 5–20
5–20. Dorado 800 Single Port Fibre HBA Throughput Ratio .......................................... 5–21
5–21. Dorado 4200 Single Port Fibre HBA Throughput Ratio ........................................ 5–21
5–22. SIOP Fibre Disk: Sequential I/O .................................................................................. 5–22
5–23. SIOP Fibre Tape: Sequential I/O................................................................................. 5–22
5–24. SIOP SCSI Compared to CSIOP SCSI ........................................................................ 5–23
5–25. SIOP SBCON Tape Performance ............................................................................... 5–24
5–26. SIOP/CSIOP Performance Ratio (SBCON Tape) .................................................... 5–24
5–27. Multiple Drive SIOP FICON Performance ................................................................ 5–25
5–28. Single Drive/Device SIOP FICON Performance Ratio Relative to
SBCON Baseline ....................................................................................................... 5–25
6–1. Arbitrated Loop ................................................................................................................. 6–2
6–2. Switched Fabric Topology............................................................................................. 6–5
6–3. Switched Fabric ............................................................................................................... 6–6
6–4. FC / SCSI Converter ........................................................................................................ 6–9
6–5. Brocade Switch ............................................................................................................... 6–16
6–6. Zoning ................................................................................................................................ 6–18
6–7. Zoning with Multiple Switches ................................................................................... 6–19
6–8. Multihost Zoning ............................................................................................................ 6–20
6–9. Remote Backup .............................................................................................................. 6–21
7–1. Unit Duplexing and RAID 1 .......................................................................................... 7–33
7–2. CLARiiON Disk System ................................................................................................ 7–34
7–3. CLARiiON System with Unit Duplexing ................................................................... 7–34
8–1. SBCON Channel to Peripheral Distances .................................................................. 8–3
8–2. SBCON Cable Connections ........................................................................................... 8–4
8–3. SBCON Cable or Connector Types ............................................................................. 8–5
8–4. Trunk Cables ..................................................................................................................... 8–6
8–5. Usage of Trunk and Jumper Cables ............................................................................8–7
3839 6586–010 xiii

Figures
xiv 3839 6586–010

Tables
1–1. Dorado 800 I/O Styles ..................................................................................................... 1–5
1–2. Dorado 300 and 400 IOP Card Styles ....................................................................... 1–17
1–3. Dorado 700, 800, 4000, 4100, and 4200 IOP Styles .............................................. 1–18
1–4. PCI Host Bridge Card Style .......................................................................................... 1–28
1–5. Expansion Rack ............................................................................................................... 1–29
1–6. Dorado 4200 Series PCI Card Placement ...................................................................... 1–32
DORADO 4200 SERIES Slot ........................................................................................................ 1–32
1–7. Fibre Channel Style ........................................................................................................ 1–39
1–8. SCSI HBA Style ............................................................................................................... 1–41
1–9. SCSI Converter Styles ................................................................................................... 1–43
1–10. SBCON HBA Style ......................................................................................................... 1–44
1–11. PCIOP-E PDID assignments for Bus-Tech FICON HBA ........................................ 1–45
1–12. Ethernet Styles................................................................................................................1–48
1–13. Myrinet Card Style ......................................................................................................... 1–57
1–14. Partition Time Values Compared to Source Time Values .................................... 1–59
1–15. Myrinet Card Style ......................................................................................................... 1–60
1–16. Cipher Appliance Style .................................................................................................. 1–61
2–1. ANSI and ISO Standards for SCSI Fibre Channel ...................................................... 2–1
2–2. SCMS II View of JBOD Configuration ........................................................................ 2–4
2–3. SCMS II View of Arbitrated Loop Example................................................................2–8
2–4. SCMS II View of Switched Fabric ............................................................................... 2–10
2–5. SCMS II View of Channel for Nonredundant Disks ............................................... 2–13
2–6. SCMS II View of Unit-Duplexed Example ................................................................ 2–15
2–7. T9x40 Family of Tape Drive Styles ............................................................................ 2–16
2–8. SCMS II View of Switched Fabric ............................................................................... 2–19
2–9. SCMS II Values in Daisy-Chain of Eight Control Units ...........................................2–22
2–10. SCMS II View of Redundant Daisy Chains .............................................................. 2–25
2–11. JBOD Disk Subsystems and Target Addresses..................................................... 2–31
2–12. Control-Unit-Based Disk Channels and Addresses .............................................. 2–34
2–13. SCMS II Configuration for SBCON ............................................................................ 2–37
2–14. FICON 32-bit Target Address Fields ......................................................................... 2–45
2–15. FICON target address for direct-connected real tapes – point to
point. ............................................................................................................................ 2–45
2–16. FICON target address for direct-connected virtual tapes – point to
point. ............................................................................................................................ 2–46
2–17. FICON target address for switch-connected real tapes – switched
point to point or Cascade FICON switches. ...................................................... 2–46
2–18. FICON target address for switch-connected virtual tapes – switched
point to point or Cascade FICON switches. ...................................................... 2–46
3–1. Word-to-Kilobyte Translation ..................................................................................... 3–24
3839 6586–010 xv

Tables
4–1. 36-Track Model Performance Metrics ...................................................................... 4–2
4–2. Performance Values for the T9840 Family of Tapes ............................................. 4–3
4–3. Transfer Rates for Labeled Tapes ............................................................................. 4–12
4–4. Translation of Tracks to Words ................................................................................. 4–14
4–5. Transfer Rate Based on File Size ............................................................................... 4–16
4–6. Block Size Options for COPY,G ................................................................................. 4–25
5–1. Busy Percentage per Path ............................................................................................ 5–9
5–2. Translation of Tracks to Words and Bytes .............................................................. 5–12
5–3. Tape Drives Guidelines ................................................................................................ 5–26
6–1. Arbitrated Loop Addressing ......................................................................................... 6–3
6–2. Arbitrated Loop With Eight JBOD Disks ................................................................... 6–4
6–3. 24-Bit Port Address Fields ........................................................................................... 6–10
6–4. 12-bit SAN Addressing Example ................................................................................. 6–14
6–5. 24-bit SAN Addressing Example ................................................................................ 6–16
7–1. Supported Features for the T10000A and T9840D Tape Devices ......................7–8
7–2. SCSI and SBCON Compatibility Matrix ..................................................................... 7–14
7–3. Capabilities Supported by the Exec ......................................................................... 7–20
7–4. DMX Series Characteristics .........................................................................................7–27
7–5. Symmetrix 8000 Series ................................................................................................7–27
7–6. EMC Symmetrix 5.5 ...................................................................................................... 7–28
7–7. EMC Symmetrix 5.0 ...................................................................................................... 7–28
7–8. EMC Symmetrix 4.8 ICDA ........................................................................................... 7–28
7–9. EMC Symmetrix 4.0 ...................................................................................................... 7–29
7–10. Unit-Duplexed Pairs ...................................................................................................... 7–35
8–1. LVD-HVD Converter Styles ............................................................................................ 8–1
8–2. Supported Expansion Rack CIOP NICs ...................................................................... 8–9
8–3. Supported XIOP and XPC-L NIC .................................................................................. 8–10
9–1. CEC Equipment That Can Be Migrated ....................................................................... 9–1
9–2. Supported Tape Devices ............................................................................................... 9–4
9–3. Supported Cartridge Library Units .............................................................................. 9–6
9–4. End-of-Life Tapes ............................................................................................................ 9–6
9–5. End-of-Life (EOL) Table Libraries .................................................................................. 9–7
9–6. Supported Disk Devices ................................................................................................ 9–8
9–7. Supported SAIL Disks ................................................................................................... 9–10
9–8. Supported DVDs ............................................................................................................. 9–11
9–9. Supported Non-RoHS Host Bus Adapters (HBAs) ................................................ 9–12
9–10. Supported RoHS Host Bus Adapters (HBAs) ......................................................... 9–12
9–11. SIOP Device Mnemonics (By Mnemonic) ................................................................ 9–14
9–12. SIOP Device Mnemonic (By Device) ......................................................................... 9–16
9–13. Ethernet NICs .................................................................................................................. 9–19
9–14. Ethernet NICs ................................................................................................................. 9–20
9–15. Ethernet NICs ................................................................................................................. 9–20
9–16. Ethernet NICs ................................................................................................................. 9–20
A–1. Allowed Positions on an Arbitrated Loop ................................................................. A–1
xvi 3839 6586–010

Tables
B–1. Brocade Switch Addresses .......................................................................................... B–2
B–2. Older Model McData Switch Addresses .................................................................. B–9
B–3. Newer Model McData Switch Addresses (ED10000, 4400, 4700) .................. B–16
C–1. Key Hardware Attributes by Release ......................................................................... C–1
3839 6586–010 xvii

Tables
xviii 3839 6586–010

Section 1
PCI-Based I/O Hardware
This section covers the configuration of the Peripheral Component Interconnect
(PCI)-based hardware, I/O processors, host bus adapters (HBAs), and network
interface cards (NICs). It is intended to help the service representative set up and
maintain the I/O hardware complex.
Note: The Dorado 400, 4000, 4100 and 4200 Series only support the SIOP PCI-based
I/O hardware.
Documentation Updates
This document contains all the information that was available at the time of
publication. Changes identified after release of this document are included in problem
list entry (PLE) 18899124. To obtain a copy of the PLE, contact your Unisys
representative or access the current PLE from the Unisys Product Support Web site:
http://www.support.unisys.com/all/ple/18899124
Note: If you are not logged into the Product Support site, you will be asked to do
so.
1.1. Architecture Overview
With the introduction of the Dorado 300 Series, the architecture of the Dorado
systems was revolutionized. The Dorado 400, 4000, 4100, and 4200 Series systems
move that revolution forward.
1.1.1. Dorado 300 Series
The Dorado 300 Series systems contain cell pairs. One cell contains the instruction
processors (IPs) and is attached to another cell for input/output (I/O).
The minimum configuration contains the following:
• One IP cell with 4 OS 2200 IPs and 4 GB of memory
• One I/O cell
For systems with more than one IP cell, the cells are arranged so that the IP cells are
adjacent. For example, IP cell 0 is adjacent to IP cell 1. I/O cell 0 is below the two IP
cells and I/O cell 1 is above the two IP cells.
3839 6586–010 1–1

PCI-Based I/O Hardware
The following illustration shows the layout of a Dorado 300 cabinet. The minimum
configuration is shown with solid lines and white background, and dashed lines with
gray background are used for customer-optional equipment.
1.1.2. Dorado 700 Series
Figure 1–1. Dorado 300 Series Cabinet Layout
The Dorado 700 is similar to the Dorado 300 in the cabinets. The differences are
Dorado 740 and Dorado 750
• IP cell with four OS 2200 IPs and 4 GB of memory
• PCI-X based PCIOP-E I/O processor and Channel cards
• Support for Internal I/O only with a maximum of four IOPs (SIOP, CIOP, and XIOP)
• No support for connection to XPC-L
1–2 3839 6586–010

Dorado 780 and Dorado 790
PCI-Based I/O Hardware
• Faster 2200 processor (about 15 percent faster than Dorado 740 and Dorado 750)
• PCI-X based PCIOP-E I/O processor and Channel cards
• Support for External I/O with a maximum of six IOPs in a Remote I/O Module
(SIOP, CIOP, and XIOP)
• Support for XPC-L connectivity through the PCIOP-E version of the XIOP
Dorado 700 series I/O Configuration
The I/O for the Dorado 700 Series can either be Internal with a maximum of four IOP
cards for each cell (740 and 750) or External with a maximum of six IOP cards for each
Remote I/O Module (780 and 790).
The Internal I/O contains one to four I/O Processor units (PCIOP-E) with each PCIOP-E
connecting to a PCI Expansion Rack. The PCI Expansion Rack can contain either
standard channel cards or NIC cards. Each PCIOP-E requires a separate expansion rack
and can have only NIC cards or storage HBA cards, but cannot have both in the same
rack.
The External I/O is located in the Remote I/O Module. The Remote I/O Module
contains one to six I/O Processor units (PCIOP-E). The same PCI Expansion Racks
connect to the external I/O processors.
The Internal I/O or the Remote I/O Module does not contain PCI Channel cards. They
are located in the PCI Expansion Racks.
Notes:
• Internal I/O DVD – The PCIOP-E card used for connection to the DVD drive can
only be inserted in IOPx1 slot when viewed from the rear of the IP Cell, due to
cable routing within the cell. The DVD appears as PDID=61392 (xEFD0 or
167720), CU address=0, Device address =0.
• External I/O DVD – The PCIOP-E card used for connection to the DVD drive can
only be inserted in IOPx5 slot when viewed from the rear of the Remote I/O
Module, due to cable routing within the cell. The DVD appears as PDID=61392
(xEFD0 or 167720), CU address=0, Device address =0.
Each PCIOP-E (SIOP, CIOP, and XIOP) requires two cables, a communications cable,
and an I/O cable. The Remote I/O Module contains the platform logic for primary PCI
buses. These PCI buses are where the PCIOP-E boards are attached.
The PCIOP-E contains the I/O processor (IOP) and the 36-bit data formatter needed to
perform the I/O operations. The primary PCI bus is connected to the memory side of
the formatter and IOP bridges. A secondary PCI bus is attached to the channel side of
the bridges. PCI cards that support the IDE DVD drive and the three inbuilt SAS drives
must be installed in one of the available PCI slots to drive these interfaces.
The PCIOP-E and PCI cards can be hot replaced, but only if their status is DOWN.
3839 6586–010 1–3

PCI-Based I/O Hardware
The PCI cards can consume a maximum of 25 watts each, drawing power from either
the 3.3 volt or the 5 volt rails, or both, as long as the sum of both does not exceed
25 watts for each card.
1.1.3. Dorado 800 Series
The Dorado 800 series has the following configuration:
• Cells ranging from a single cell with 4 IPs to 8 cells with 32 IPs
• Maximum memory of 256 GB
• Support for internal I/O and external I/O using PCIOP-M cards (SIOP, CIOP, XIOP)
Dorado 800 Series I/O Configuration
Dorado 800 utilizes the I/O Manager Module PCIOP-Ms for the storage (SIOP-M) and
communication IOPs (CIOP-M), and the PCIOP-E for the initial delivery of the XIIP (also
called XIOP). The PCIOP-E cannot be used for storage or communication IOPs.
The I/O Manager is a 4U module that consists of two PCIOP-Ms. Each of the PCIOP-
Ms can be a storage IOP (SIOP-M) or communications IOP (CIOP-M) or future XIOP-M.
The PCIOP-M consists of the I/O processing engine and slots for up to six PCIe add-in
cards (NICs or HBAs). The PCIOP-M connects to the rest of the Dorado 800 system
through the Host Card installed in the Internal or Remote I/O Module. The Host Bridge
card is simply a PCI-X to PCIe bridge, with no processing logic.
Figure 1–2. I/O Module for the Dorado 800 (Front View)
1–4 3839 6586–010

PCI-Based I/O Hardware
Figure 1–3. I/O Module for the Dorado 800 (Rear View)
The following are the styles for the Dorado 800 I/O.
Table 1–1. Dorado 800 I/O Styles
Style Description
DOR204-IOM I/O Manager Rack with two PCIOP-Ms
DOR1-HST Dorado I/O Manager PCI-X to PCIe card and 5m
cable (2 required per DOR204-IOM)
DOR800-CIO I/O: Dorado 800 Series - Communications IOP
DOR800-SIO I/O: Dorado 800 Series - Storage IOP
ETH10201-PCE PCIe 2 Port 1 Gb Ethernet (Fiber)
ETH20201-PCE PCIe 2 Port 1 Gb Ethernet (Copper)
ETH10210-PCE PCIe 2 Port 10 Gb Ethernet (Fiber)
FCH9430232-PCE Fibre Channel 4Gb – 2 port
FCH9540231-PCE Fibre Channel 8Gb – 2 port
FIC1001-PCE FICON Channel 4Gb – 1 port
CIP2001-PCE Nitrox Cypher
CSB1-PCE Time card
Configuration rules are required for the location of the Host Channel Cards for the
PCIOP-Ms in the Internal and Remote I/O Modules and the connection of the IOPs
(PCIOP-Ms) in the I/O Manager module to these cards.
With the PCIOP-E, the PCIOP-E is installed in the Internal or Remote I/O Module and
connects to the Expansion rack, which contains the XIIP interface card.
3839 6586–010 1–5

PCI-Based I/O Hardware
All of the I/O slots in the Internal I/O Module in the Dorado 800 are PCI-X 133MHz. In
the Remote I/O Module, only three of the I/O slots are PCI-X 133MHz, the remaining
three slots are PCI-X 100MHz. The SIOP-M requires the highest bandwidth. The
configuration rules for the Dorado 800 must assign the SIOP-M first to the 133MHz
PCI-X buses and then use the 100MHz PCI-X buses.
For more information on the PCI-card slot assignments, see Section 1.3.3 I/O
Expansion Module (Internal or External) for the Dorado 800.
The IOP logical number to PCI-card slot assignments are the same in the Internal I/O
Module and the Remote I/O Module due to the software configuration based on the
PCI assignments. To keep the configurations the same for Internal I/O Modules or
Remote I/O Modules, the same rules are utilized for the Host card assignments.
1.1.4. Dorado 400 Server
For the Dorado 400 Server systems, the configuration contains the following:
• One internal I/O cell containing
− High-level high-speed Xeon® Processor MP processors
− 16 GB memory
− Dual-port network interface
− Read-only DVD for SAIL only
• One Procnode cell without processors or memory
• One remote I/O cell
− Read/Write DVD for OS 2200
− Up to 3 other SIOPs
• One Managed LAN Switch
• One Operations Server
The following illustration shows the layout of the Dorado 400, 4000, and 4100 cabinet.
The minimum configuration is shown with solid lines and white background, and
dashed lines with gray background are used for customer-optional equipment.
1–6 3839 6586–010

1.1.5. Dorado 4000 Server
Figure 1–4. Dorado 400 Series Cabinet Layout
PCI-Based I/O Hardware
The Dorado 4000 Server contains the following changes from the Dorado 400 Series:
• Utilizes the ClearPath 4000 cell for processing.
• Utilizes the PCIOP-E in the I/O Expansion Module for SIOP.
• The ClearPath 4000 cell connects to the I/O Expansion Module.
• The I/O Expansion Module connects to the PCI Channel Module.
3839 6586–010 1–7

PCI-Based I/O Hardware
The following Dorado 4000 cabinet layout is with one or two I/O Expansion Modules.
The minimum configuration is shown with a white background and a gray background
is used for customer-optional equipment.
Figure 1–5. Dorado 4000 Series Cabinet Layout with One to Two I/O Expansion
Modules
Dorado 4050 Server
The Dorado 4050 Server is an entry level model with a fixed configuration. The Dorado
4050 is similar to the Dorado 4000 in the cabinets, but the following options are not
available
• Flexibililty of configuring IOPs and HBAs
• A redundant switch
• External SAIL disk
• SBCON/ESCON HBA
• Cavium Nitrox (Encryption) card
• High Availability
1–8 3839 6586–010

The following illustration shows the layout of the Dorado 4050 cabinet.
1.1.6. Dorado 4100 Server
Figure 1–6. Dorado 4050 Server Cabinet Layout
PCI-Based I/O Hardware
The only difference for the Dorado 4100 Server from the Dorado 4000 Series is that it
uses the ClearPath 4100 cell for processing.
The following Dorado 4100 cabinet layout is with one or two I/O Expansion Modules.
The minimum configuration is shown with a white background and a gray background
is used for customer-optional equipment.
3839 6586–010 1–9

PCI-Based I/O Hardware
Figure 1–7. Dorado 4100 Series Cabinet Layout with One to Two I/O Expansion
Modules
Dorado 4150 Server
The Dorado 4150 Server is an entry level model with a fixed configuration. The Dorado
4150 is similar to the Dorado 4100 in the cabinets, but the following options are not
available
• Flexibililty of configuring IOPs and HBAs
• A redundant switch
• SBCON/ESCON HBA
1–10 3839 6586–010

• Cavium Nitrox (Encryption) card
• High Availability
The following illustration shows the layout of the Dorado 4150 cabinet.
1.1.7. Dorado 4200 Series
Figure 1–8. Dorado 4150 Server Cabinet Layout
PCI-Based I/O Hardware
Dorado 4200 Series utilizes the I/O Manager that was introduced with the Dorado 800
Series. The I/O Manager is a Unisys designed, custom built, 4U module that contains 2
IOPs, with up to 6 PCIe cards per IOP. Connection to the Dorado 4200 Series host is
via an industry standard PCIe External Cabling Interconnect. The I/O Manager has a
number of significant advantages over the prior Dorado 4100 Series PCIOP-E based
I/O. Among them are:
• Modern and higher bandwidth connection to the host (Gen 2 PCIe)
• Compact packaging (2 IOPs and up to 12 HBAs in 4U rack space)
• Usage of the latest generation HBAs
• Faster processors with lower latency memory accesses
• Mechanical and electrical design that allows for easy replacement of one of the
IOPs within an I/O Manager while the other continues to operate unaffected.
3839 6586–010 1–11

PCI-Based I/O Hardware
Figure 1–9. I/O manager for the Dorado 4200 Series
I/O Manager PCIe Connector Ports
This section details cabling restrictions both from the host card to the switch card in
an I/O Manager and from the switch card to an IOP in an I/O Manager. The figure
below shows the rear view of an I/O Manager. The switch card is located on the far
left of the figure, but is not directly visible due to enclosed metal sheet. The switch
card contains four Gen 2 PCIe connector ports mounted vertically- that are visible in
the figure. The switch ports are labeled (from bottom to top) UP-0, DWN-0, DWN-1,
and DWN-2. Additionally, each IOP contains a Gen 2 PCIe connector port. This is
located between the Ethernet port and Slot 0 and mounted horizontally.
1–12 3839 6586–010

PCI-Based I/O Hardware
The following figure represents the switch ports and the cabling between ports.
Figure 1–10: Switch Ports and Cabling
Following are the I/O Manager PCIe connector port cabling rules:
• The PCIe cable connected to the host card must always be connected to switch
card port UP-0 of the first I/O Manager for that slot.
• Switch card port DWN-0 must always be connected to the IOP 0 port.
• Switch card port DWN-1 must always be connected to the IOP 1 port.
• If an additional I/O Manager is connected off the same host card, it must be
connected from switch card port DWN-2 on the first I/O Manager for that slot to
switch card port UP-0 on the second I/O Manager for that slot.
• A maximum of two I/O Managers (four IOPs) may be connected to a single host
card.
Usage of multiple I/O Managers per host slot is not allowed until after each host slot
has first been connected to an I/O Manager (that is, the number of I/O Managers
exceeds the number of host cards).
1.2. I/O Module Overview
The following introduces the terminology and the architecture of the Dorado 300, 400,
700, 4000, 4100, and 4200 Servers.
Note: For this discussion, consider the Dorado 300 and 700 Series I/O Module and
the Dorado 400, 4000, 4100, and 4200 Series PCI Channel Module as equivalents.
3839 6586–010 1–13

PCI-Based I/O Hardware
1.2.1. PCI Standard
Caution
The SIOP and earlier SCIOP components are microcoded components. They
are the same devices that may perform roles as an IOP, XIIP, or a PCIOP for
communications. Their base personality is burned into them at the Factory
when they are built. Once a microcode set has been established in them, a
field location attempt to change the set that is installed on the device is not
advised. Doing so makes the device unusable and it will have to be
returned to the factory to be reinitialized. In cases where the hardware is
different, the microcode load attempt will be rejected by the IOP with an
appropriate status code. However, in case of the differences between
Dorado 300, Dorado 700 and the Dorado 400, Dorado 4000, Dorado 4100 or
Dorado 4200 the microcode load attempt will not be rejected. Loading the
Dorado 400 or 4000, 4100 or 4200 version of microcode on an SIOP for a
Dorado 300 or Dorado 700 will make the device unusable and it will have to
be returned to the factory to be reinitialized. A change will be developed in
IOPUTIL and provided in the near future that will verify that the IOP
Microcode matches the host system that is connected to the SIOP device.
Peripheral Component Interconnect (PCI) provides a processor-independent data path
(a bridge) between the I/O processors and the peripheral controllers (HBAs and NICs).
More than one controller can be attached to the same PCI bus.
PCI is an industry standard, first released by Intel in 1992. The following definitions are
based on the standard:
• Bus Speeds
The original standard, 1.0, supported 33-MHz and 32-bit bus width. Revision 2.1
introduced the possibility of faster cards with a bridge by supporting the following:
− 66-MHz maximum bus speeds
Cards running at 33 MHz are also supported.
− 64-bit bus
64 bits are sent in parallel (at the same time). Potentially, the bus is twice as
fast as a 32-bit bus.
− If any component of a PCI bus runs at 33 MHz, all the components of the bus
run at 33 MHz.
• PCI-PCI Bridges
The original specification allowed four PCI cards, but the number of cards could be
increased by using a PCI bridge. The bridge allows for additional slots, using one
original slot and bridging to another bus that has its own set of slots. PCI-to-PCI
bridges are Application Specific Integrated Circuits (ASICs) that electrically isolate
two PCI buses while enabling bus transfers to be forwarded from one bus to
another. Each bridge device has a primary and a secondary PCI bus. Multiple bridge
devices can be cascaded to create a system with many PCI buses.
1–14 3839 6586–010

PCI-Based I/O Hardware
• ASIC
An ASIC is a custom-designed chip for a specific application. ASICs improve
performance over general-purpose CPUs because ASICs are hardwired to do a
specific job and do not incur the overhead of fetching and interpreting stored
instructions.
• Signaling
The original standard, supported by the technologies of that time, was based on
5.0-volt signaling for the cards and the backplane. As the technology evolved,
3.3-volt signaling became a better choice. However, vendors offered backplanes
that had all the slots supporting either 3.3-volt or 5.0-volt PCI cards. This meant the
PCI cards could not be mixed within the same backplane. Then, PCI add-in card
vendors developed Universal cards that can plug into a 3.3-volt slot or a 5.0-volt
slot.
• PCI Revisions
− Revision 2.1
Supported 3.3-volt cards, 5.0-volt cards, and Universal cards.
− Revision 2.2
Minor changes.
− Revision 2.3
Supported 3.3-volt cards and Universal add-in cards; no support for 5.0-volt
cards.
1.2.2. I/O Bus Layout
The following figure shows the key components of the I/O complex and the primary
and secondary PCI buses that connect them.
The SIOH and P64 are Intel chips used for I/O processing. There is no further
description in this document.
The DVD Interface Card and the PCI Host Bridge Card are specific HBAs. They are
described later in this section.
The expansion rack contains up to seven additional HBAs or NICs. It is described later
in this section.
3839 6586–010 1–15

PCI-Based I/O Hardware
Figure 1–11. Primary and Secondary PCI Bus Location
1.2.3. Dorado 300 and Dorado 400 IOPs
Each type of IOP has its own microcode. The Dorado 300 and 400 Servers support the
following type of I/O processor:
• SIOP, Storage IOP
The SIOP supports PCI cards that connect to tapes and disks. The cards are
classified as Host Bus Adapters (HBA). The PCI cards can be Fibre, SCSI, or
SBCON.
The Dorado 300 Server supports the following types of I/O processors:
• CIOP, Communications IOP
The CIOP supports an Ethernet PCI card. This is also known as a network interface
card (NIC). CIOP is not supported on Dorado 400.
• XIOP, Extended IOP
The XIOP supports one connection to the XPC-L. The Myrinet is the only
supported card. The Myrinet card only goes into slot 0. Slot 1 must remain unused.
XIOP is not supported on Dorado 400.
1–16 3839 6586–010

Styles
The following are the IOP card styles:
Figure 1–12. IOP Card
Table 1–2. Dorado 300 and 400 IOP Card Styles
Style Connection
DOR400-SIO SIOP for Dorado 400 HBAs (PCIOP-D)
DOR380-SIO SIOP for Dorado 300 HBAs (PCIOP-D)
DOR380-CIO CIOP for Ethernet NICs for Dorado
300
DOR380-XIO XIOP for XPC-L for Dorado 300
Dual Paths Needed for Online Loading of SIOP Microcode
PCI-Based I/O Hardware
When online loading microcode into the SIOP, the peripherals (disk or tape) that can be
accessed through that SIOP are not available for normal access by the system. There
must be a redundant SIOP that is UP and can access the same peripherals as the SIOP
being loaded. If this restriction is not met for disks, the online load process could
result in a system stop, system hang, or have unpredictable results.
If you have peripherals that are single path or you are loading several SIOPs, you
should use SUMMIT offline EPTS.
3839 6586–010 1–17

PCI-Based I/O Hardware
1.2.4. Dorado 700, Dorado 800, Dorado 4000, Dorado 4100
and Dorado 4200 IOPs (PCIOP-M and PCIOP-E)
The PCIOP-M platform is the next generation PCIOP design. The PCIOP-M is attached
to the Dorado 800 through a PCI-X to PCI express bridge card.
The PCIOP-M module is a standard rack mount 4U unit. It contains two sub modules,
which to the host are two separate IOPs. Each sub module has 6 on-board PCI express
slots, which support the PCI express standard hot plug controller interface. An
external I/O Expansion rack is not required for the PCIOP-M. Each PCIOP-M has one
DVD, which is only used by the SIOP. The DVD is attached to the sub module on the
left (looking from the rear of the PCIOP-M).
The PCIOP-E is the I/O processor (IOP) to be used on the Dorado 700, Dorado 4000,
and Dorado 4100 Servers. The IOP fits into a standard full-sized PCI slot. The PCI
channel cards (HBAs) require an external I/O Expansion Module attached to each IOP.
Note: For the Dorado 700, the PCIOP-E card used for connection to the DVD drive
can only be inserted in the left-most slot (internal I/O = PCIBUS_x_3, Remote
I/O=PCIBUS_x_2) due to cable routing within the cell.
Table 1–3. Dorado 700, 800, 4000, 4100, and 4200 IOP
Styles
Style Connection
DOR700-SIO SIOP for Dorado 700 HBAs (PCIOP-E)
DOR800-SIO SIOP-M for Dorado 800 HBAs (PCIOP-M)
DOR4000-SIO SIOP for Dorado 4000 and 4100 HBAs (PCIOP-E)
DOR700-CIO CIOP for Ethernet NICs for Dorado 700
DOR800-CIO PCIOP-M for Ethernet NICs for Dorado 800
DOR700-XIO XIOP for XPC-L for Dorado 700
DOR4000-XIO XIOP for XPC-L for Dorado 4000, 4100 and 4200
1.2.5. Host Bus Adapters
A host bus adapter (HBA) is a printed circuit board that connects one or more
peripheral units to a computer. The HBA manages the transfer of data and information
between the host and the peripheral.
An HBA contains an onboard processor, a protocol controller, and buffer memory. The
HBA receives an I/O request from the operating system and completely handles
activities such as segmentation and reassembly, flow control, error detection and
correction, as well as command processing of the protocol being supported. HBAs
offload the Dorado server CPU.
1.2.6. Network Interface Card
1–18 3839 6586–010

PCI-Based I/O Hardware
A network interface card (NIC) connects a computer to a communications network.
For the Dorado Series, it is an Ethernet network.
Note: For the Dorado 400, 4000, 4100, and 4200 a PCIOP is not required for NICs.
For the Dorado 400, the NICs are installed in the Internal I/O Cell. For the Dorado
4000, 4100, and 4200 the NICs are installed in the ClearPath 4000, 4100, and 4200
respectively.
A NIC relies on the server for protocol processing, including such functions as the
following:
• Maintaining packet sequence order
• Segmentation and reassembly
• Error detection and correction
• Flow control
The NIC contains the protocol control firmware and Ethernet Controller needed to
support the Media Access Control (MAC) data link protocol used by Ethernet.
Each network interface card is assigned an Ethernet source address by the
manufacturer of the network interface card. The source address is stored in
programmable read-only memory (PROM) on the network interface card. The
addresses are globally unique.
1.3. I/O Modules and Components
The following describes the I/O modules and components.
1.3.1. I/O Module for the Dorado 300 and 400
The I/O Module consists of 12 slots. There is room for 4 IOPs; each IOP can control up
to 2 PCI slots in the I/O Module.
The I/O Module
• Supports PCI revision 2.2
• Supports 3.3-volt or Universal add-in PCI cards
The following figure shows the slots in the I/O Module:
3839 6586–010 1–19

PCI-Based I/O Hardware
Example
Figure 1–13. Top View of the I/O Module
The area in the ellipse shows the locations for IOP1 and the PCI card slots the IOP
controls (more about the types of IOPs and PCI cards later).
The area in the ellipse is set up at the factory with an SIOP in PCI slot 0 and a DVD
Interface Card in PCI slot 1. Due to cable length limitations, this location must be used
for the DVD interface since it is closest to the DVD reader. (For more information on
DVD, see 1.6.2.) The other PCI slot, slot 0, can be used for an SIOP, an HBA, or a PCI
Host Bridge Card to an expansion rack.
The following figure shows IOPs in an I/O Module.
• The CIOP controls two NICs.
• One SIOP has two HBAs.
• One SIOP has an interface to a DVD and a PCI Host Bridge Card to two fibre HBAs
in an expansion rack.
Notes:
• CIOP is not supported on Dorado 400.
• This example does not apply to the Dorado 4000, 4100 or 4200. See Figures 1–
14, 1–15, 1–16, and 1–17 for the Dorado 4000 and 4100 connections.
1–20 3839 6586–010

Figure 1–14. I/O Module Connection to Expansion Racks
PCI-Based I/O Hardware
1.3.2. I/O Module (Internal or External) for the Dorado 700
The Internal I/O Module consists of five slots. There is room for four IOPs; each IOP
can control a maximum of seven PCI slots in the PCI Expansion Rack.
Figure 1–15. Internal I/O Module Layout for the Dorado 700
3839 6586–010 1–21

PCI-Based I/O Hardware
Example
The Remote I/O Module (External) consists of 12 slots. There is room for six IOPs;
each IOP can control a maximum of seven PCI slots in the PCI Expansion Rack.
Figure 1–16. Remote (External) I/O Module Layout for the Dorado 700
In Figure 1–16, the area in the ellipse shows the locations for IOP0 – IOP5 and possible
locations of the available six IOPs. This is set up at the factory with an SIOP in the IOP5
location which includes the DVD Interface. IOP5 is the default and only location for the
DVD. Only SIOP, CIOP, and XIOP cards can be placed in the Remote I/O Module.
The following figure shows the IOPs in an I/O Module.
Figure 1–17. IOPs in an I/O Module
1–22 3839 6586–010

In this example,
• The CIOP controls seven NICs
• One SIOP has two HBAs
Note: CIOP is not supported on Dorado 400, 4000, 4100 or 4200.
PCI-Based I/O Hardware
This example does not apply to the Dorado 4000, 4100 and 4200. See Figures 1–14, 1–
15, 1-16, and 1–17 for the Dorado 4000 and 4100 connections.
1.3.3. I/O Expansion Module (Internal or External) for the
Dorado 800
The Dorado 800 utilizes both Internal and Remote I/O Modules.
The Internal I/O Module has five PCI-X card slots, the PCIOP-E or PCIOP-M Host Cards
are installed in these card slots. The location of the card dictates the 2200 logical IOP
number (the cell number is appended to the IOP number to form the complete logical
IOP number). The assignments are as follows.
Internal I/O Module
PCI-X Card Slot
2200 Logical IOP
Number IOP Type Allowed PCI-X Bus Frequency
PCI-X Bus 3/Slot 1 IOP4 Third CIOP-M
SIOP-M if IOP1 and
IOP3 are already
SIOP-Ms
Cannot be XIOP-E
PCI-X Bus 4/Slot 1 IOP1 First SIOP-M
only assign XIOP-E
or CIOP-M if IOP0,
IOP2 and IOP4 are
already used
PCI-X Bus 5/Slot 1 IOP0 First CIOP-M or
XIOP-E
SIOP-M if IOP1 and
IOP3 are already
SIOP-Ms
PCI-X Bus 6/Slot 1 IOP3 Second SIOP-M
only assign XIOP-E
or CIOP-M if IOP0,
IOP2 and IOP4 are
already used
PCI-X Bus 7/Slot 1 IOP2 Second CIOP-M or
XIOP-E
SIOP-M if IOP1 and
IOP3 are already
SIOP-Ms
133MHz
133MHz
133MHz
133MHz
133MHz
3839 6586–010 1–23

PCI-Based I/O Hardware
The Remote I/O Module has eleven PCI-X card slots, but only six of these are used for
the PCIOP-E or PCIOP-M Host Cards. The location of the card dictates the 2200 logical
IOP number (the cell number is appended to the IOP number to form the complete
logical IOP number). The assignments are as follows.
Remote I/O Module
PCI-X Card Slot
2200 Logical IOP
Number IOP Type Allowed PCI-X Bus Frequency
PCI-X Bus 2/Slot 1 IOP5 Third SIOP-M
only assign XIOP-E
or CIOP-M if IOP0,
IOP2, and IOP4 are
already used
PCI-X Bus 3/Slot 1 IOP4 Third CIOP-M
SIOP-M if IOP1,
IOP3 and IOP5 are
already SIOP-Ms
PCI-X Bus 4/Slot 1 IOP1 First SIOP-M
only assign XIOP-E
or CIOP-M if IOP0,
IOP2, and IOP4 are
already used
PCI-X Bus 5/Slot 1== IOP0 First CIOP-M or
XIOP-E
SIOP-M if IOP1,
IOP3 and IOP5 are
already SIOP-Ms
PCI-X Bus 6/Slot 1 IOP3 Second SIOP-M
only assign XIOP-E
or CIOP-M if IOP0,
IOP2, and IOP4 are
already used
PCI-X Bus 7/Slot 1 IOP2 Second CIOP-M or
XIOP-E
I/O Module to PCIOP-M Cabling
SIOP-M if IOP1,
IOP3 and IOP5 are
already SIOP-Ms
133MHz
100MHz
133MHz
100MHz
133MHz
100MHz
The I/O Manager 4U rack contains two PCIOP-Ms. The PCIOP-M is cabled to the Host
Card in the Internal I/O or Remote I/O Module. At the rear of the I/O Manager rack,
logical PCIOP-M IOP0 is on the left and IOP1 is on the right. This numbering has no
association to the 2200 logical IOP number. It is simply used to identify the location in
the I/O Manager rack.
1–24 3839 6586–010

PCI-Based I/O Hardware
The personality of the PCIOP-M is dictated by the firmware that is loaded on the IOP.
Choosing the firmware to load in each PCIOP-M needs to be determined by the I/O
assignments that are being made for each cell and the cabling to the PCIOP-M.
In the I/O Manager module, only the PCIOP-M in the IOP0 location is connected to the
DVD. The Host Card for the SIOP-M should be cabled to the IOP0 location in the I/O
Manager, as only an SIOP-M can control the DVD.
It is recommended that the odd numbered 2200 Logical IOPs (IOP1, IOP3, and IOP5
which are recommended as SIOP-Ms) are connected to the PCIOP-M IOP0. If there are
more SIOP-Ms than there are PCIOP-M IOP0s available, then these can be cabled to a
PCIOP-M IOP1.
It is recommended that the even numbered 2200 Logical IOPs (IOP0, IOP2, IOP4 which
are recommended as CIOP-Ms) are connected to the PCIOP-M IOP1. If there are more
CIOP-Ms than there are PCIOP-M IOP1s available, then these can be cabled to a PCIOP-
M IOP0.
The PCIOP-Ms in the I/O Manager rack can be split between different cells and
different partitions. However, it is recommended that the I/O Manager rack is assigned
to a single cell.
PCIOP-M HBA/NIC PCIe Add-in Card Configuration
All six of the PCIe slots in the PCIOP-M are identical, which are PCIe Gen2 x4
interfaces with x8 mechanical connectors. HBAs or NICs can be installed in any slot. If
the IOP is not fully loaded with cards, it is recommended that you use the following
order to allow the best physical access to the PCIe cards: slot 0, slot 2, slot 4, slot 1,
slot 3, slot 5.
For the SIOP-M, the valid cards are the Fibre Channel HBAs (4Gb and 8Gb), FICON HBA,
and Encryption card.
For the CIOP-M, the valid cards are the dual port copper GbE NIC, dual port fibre GbE
NIC, dual port fibre 10GbE NIC, and time card. The time card in the CIOP is
recommended to be installed in cards slots 1 or 2 to allow for ease of installing the
cables.
1.3.4. I/O Expansion Module for the Dorado 4000
For the Dorado 4000, the I/O Expansion Module contains the components necessary
to connect the ClearPath 4000 cell to the PCIOP-E. Only PCIOP-Es are to be used in the
rack. The I/O Expansion Module is 3U high and has five 133 MHz PCI-X slots. Due to
peak band pass limitations, only four of the five slots are used.
3839 6586–010 1–25

PCI-Based I/O Hardware
The following figure shows the basic connection configuration:
Figure 1–18. Minimum Connection Configuration for Dorado 4000 I/O
The IOPs in the I/O Expansion Module each connect to a separate PCI Channel Module.
The following figure shows the maximum configuration:
Figure 1–19. Maximum Configuration for Dorado 4000 I/O
1–26 3839 6586–010

1.3.5. I/O Expansion Module for the Dorado 4100
PCI-Based I/O Hardware
For the Dorado 4100, the I/O Expansion Module contains the components necessary
to connect the ClearPath 4100 cell to the PCIOP-E. Only PCIOP-Es are to be used in the
rack. The I/O Expansion Module is 3U high and has five 133 MHz PCI-X slots. Due to
peak band pass limitations, only four of the five slots are used.
The following figure shows the basic connection configuration:
Figure 1–20. Minimum Connection Configuration for Dorado 4100 I/O
The IOPs in the I/O Expansion Module each connect to a separate PCI Channel Module.
The following figure shows the maximum configuration:
Figure 1–21. Maximum Configuration for Dorado 4100 I/O
3839 6586–010 1–27

PCI-Based I/O Hardware
1.3.6. PCI Host Bridge Card
Style
The PCI Host Bridge Card connects by cable to the expansion rack. The cable comes
with the expansion rack.
Note: This PCI Host Bridge Card is not supported on the Dorado 4000, 4100 and
4200.
The following are the important characteristics:
• 64-bit, 33-MHz card
• PCI revision 2.2
• Universal add-in card
Can connect to 3.3-volt or 5.0-volt slots
• 2-meter cable supplied
Figure 1–22. PCI Host Bridge Card Handle and Connector
The following table contains the PCI Host Bridge Card style:
Table 1–4. PCI Host Bridge Card Style
Style Description
PCI645-PHC 64 bit, 33 MGHz
1.3.7. PCI Expansion Rack
Note: For the Dorado 4000 and 4100 this is the “PCI Channel Module.”
Both the SIOP and the CIOP also support a PCI card known as the PCI Host Bridge
Card. This card connects by cable to an expansion rack. The expansion rack has slots
for a maximum of seven additional PCI cards.
1–28 3839 6586–010

PCI-Based I/O Hardware
The Dorado 4000, 4100, and 4200 use a PCI-e Host I/O card to interface with the I/O
Expansion Module. The SIOP is located in the I/O Expansion Module and has an inbuilt
Host Bridge interface to communicate with the PCI Channel Module.
The expansion rack
• Supports PCI revision 2.2
• Supports 64 bits, 33 MHz
• Supports 5.0-volt PCI cards or Universal add-in cards
See section 1.6 for more information on the PCI Host card.
The following are the styles for the expansion rack.
Table 1–5. Expansion Rack
Style Description
PCI645-EXT Expansion rack for the Dorado 300 and 400
DOR385-EXT PCI Channel Module for the Dorado 700, 4000, 4100
and 4200
The PCI cards in the expansion rack are controlled by the IOP that controls the PCI
Host Bridge Card. If the IOP card is an SIOP, all the cards in that expansion rack must
be HBAs. If the controlling IOP is a CIOP, the cards in that expansion rack can be either
Ethernet NICs or clock cards.
Note: CIOP is not supported on Dorado 400, 4000, 4100 or 4200.
1.3.8. Dorado 700/4000/4100 Expansion Rack or PCI Channel
Module (DOR385-EXT)
The following can be considered for the Dorado 700 Expansion Rack or the Dorado
4000 and 4100 PCI Channel Module:
• The PCI Expansion Rack or PCI Channel Module attached to the Dorado
700/4000/4100 IOP has seven slots.
• Slots 1 to 4 run at 66 MHz, while slots 5 to 7 run at 100 MHz.
• If there is exactly one active peripheral controller, it will realize greater bandwidth
if it resides in slots 5 to 7 as opposed to slots 1 to 4.
• The SBCON card (SIOP) and the Time Card run at a maximum frequency of 66
MHz. If installed in the IOP’s PCI expansion rack, the card will force the entire PCI
bus associated with that slot to run at a maximum frequency of 66 MHz.
Therefore, installing an SBCON card or Time Card in slot 5 will reduce the available
bandwidth on slot 6 and vice versa.
3839 6586–010 1–29

PCI-Based I/O Hardware
• Slot 7 is on its own bus. Therefore, its bandwidth is not affected by a card placed
in another slot.
The following illustration shows the layout of the PCI Expansion Rack or the PCI
Channel Module
Figure 1–23. PCI Expansion Rack Layout
1.3.9. Configuration Restriction
Dorado 300 and Dorado 400
For the Dorado 300 and 400, the IOP controls two onboard slots. If each onboard slot
contains a link to an expansion rack, then up to 14 HBAs or NICs could be controlled by
a single IOP (7 x 2). If all the HBAs/NICs are dual-ported cards, then the IOP could
theoretically have 28 ports (channels).
The maximum number of ports per IOP is actually less than the theoretical hardware
limit of 28. The limits are the following:
• 16 ports (channels) for HBAs
• 14 ports (channels) for NICs
The firmware for the SIOP (HBAs) and the firmware for the CIOP (NICs) are different.
However, they both initialize in the same way. As they detect a card, they count the
number of possible connections. For a dual port card, the possible number is two.
1–30 3839 6586–010

PCI-Based I/O Hardware
Once the maximum number of ports is encountered, error conditions occur upon
detection of the next card.
If you have all dual-port cards, you are limited to
• 8 HBAs per SIOP
• 7 NICs per CIOP
Note: CIOP is not supported on Dorado 400, 4000, or 4100.
If you have a combination of single-port and dual-port cards, you can have more than
the number of cards shown here, but you are still limited by the number of ports as
defined above.
The port (channel) limitation is true whether or not you have anything connected to the
port. Since the limitation determination occurs at microcode initialization, you cannot
down the unused channel and you must configure it in SCMS II.
Dorado 700, Dorado 4000, and Dorado 4100
For the Dorado 700, 4000, and 4100 servers, the PCIOP-E only connects to one PCI
Channel Module with 7 slots and a maximum of 14 ports.
To prevent one of the SCSI Ports from failing to initialize in certain configurations, the
SCSI HBA should be placed in slot 1, with any subsequent SCSI HBAs placed in the PCI
Channel Module according to the guidelines in the following table. An HBA of a
different type (Fibre or SBCON) should be placed in the rack ahead (in the scan order)
of the SCSI HBA. The IOP scans the PCI Channel Module PCI bus from slot 6, slot 5,
slot 7, slot 4, slot 3, slot 2, and then slot 1. For example, if the SCSI HBA is placed in
slot 1, a FIBRE should be placed in slot 6 or an SBCON card should be placed in slot 2.
If there is only one SCSI card installed in the rack, the IxyCz1 port on that SCSI card will
be unusable. For example, if there are SCSI HBAs in slots 1 to 4
(IxyC10/11 to IxyC40/41), the IxyC41 will be unusable.
For the XIOP, only one Myrinet PCI card (MYR1001-P64) can be installed in the
expansion rack and no other PCI cards can be installed in this rack. The Myrinet card
must be installed in slots 1 to 4, or slot 7. Slot 7 is the preferred location as there is
one less PCI Bridge to go through to reach the Myrinet card. If your previously
shipped Dorado Platform has the Myrinet card in slots 1 to 4, there is no need to move
the card to slot 7. If the card is moved, a new ODB (PTN) file will need to be
generated and loaded.
The guidelines for populating the expansion rack are listed in the following table.
HBA Slot Order
SCSI 1, 2, 3, 4, 7, 5, 6
SBCON 1, 2, 3, 4, 7
CAVIUM 6, 5, 7, 4, 3, 2, 1
3839 6586–010 1–31

PCI-Based I/O Hardware
FIBRE 6, 5, 7, 4, 3, 2, 1
FICON 6, 5, 7, 4, 3, 2, 1
The slots numbers can be determined by looking at the expansion rack from the back.
Slot 1 is the rightmost slot and slot 7 is the leftmost slot. It is not recommended to
put an SBCON HBA in slot 5 or 6, as this will restrict the PCI bus to 66 MHz PCI mode
for both slots 5 and 6.
Notes:
• Slot 1 - IxyC10/IxyC11 (66 MHz)
• Slot 2 - IxyC20/IxyC21 (66 MHz)
• Slot 3 - IxyC30/IxyC31 (66 MHz)
• Slot 4 - IxyC40/IxyC41 (66 MHz)
• Slot 5 - IxyC50/IxyC51 (100 MHz)
• Slot 6 - IxyC60/IxyC61 (100 MHz)
• Slot 7 - IxyC70/IxyC71 (100 MHz)
Dorado 4200
PCI Cards
There are some restrictions for PCI card placement. Some of them are based upon
limiting the amount of engineering effort associated with testing the numerous
combinations that would otherwise be possible. The following tables and the rules
that follow them should be adhered while configuring Dorado 4200 Series systems.
DORADO
4200
SERIES
Slot
Card
Type(s)
1–6. Dorado 4200 Series PCI Card Placement
7 6 5 4 3 2 1
I/O
Manager
host
card
1 Gb
quad
port
copper
Intel NIC
1 Gb Intel
NIC, 10
Gb Intel
NIC
DORADO 4200 SERIES PCIe add-in card rules:
1 Gb Intel
NIC, 10
Gb Intel
NIC
I/O
Manager
host
card
1 Gb
quad
port
copper
Intel NIC
1 Gb
Intel
NIC, 10
Gb Intel
NIC
• All PCI slot numbers are indicated on the back of the DORADO 4200 SERIES cell.
All PCIe cards in slots 1 to 3 must have half-height face plates. All slots are PCIe
Gen 3 slots.
• Only the card types and locations indicated in the table are supported.
1–32 3839 6586–010

PCI-Based I/O Hardware
• The order for installing I/O Manager Host cards is: Slot 7, 3. Note that the host card
in slot 7 must use a full-height face plate and the host card in slot 3 must use a
half-height face plate.
• The order for installing NICs is: Slot 6, 2, 5, and 4, 1. Note that the NICs in slots 4 tp
6 must use a full-height face plate and the NICs in slots 1 to 2 must use a halfheight
face plate.
1.3.10. Dorado 300 I/O Addressing
The following figure shows a Dorado 300 Series with eight IP cells, each IP cell
connected to its corresponding I/O Module.
Figure 1–24. Dorado 300 Cabinet with IP Cells and I/O Cells
The location within the cabinet is not flexible. For example, IP Cell 0 must be in the
location shown. If there is an IP Cell 1, it must be in the location shown.
The I/O Modules must also be in the location shown.
Notice how the I/O Module 0 is below IP Cell 0 and how the pattern reverses as each
IP cell is added.
The figure shows eight IP cells (for a 32x system) with an I/O Module corresponding to
each IP cell. Each cell and I/O Module pair has a unique number (0 through 7). This
number is used in the I/O addressing done by OS 2200.
OS 2200 requires a unique address for every path and device. As part of that
addressing scheme, the path through the I/O complex must be identifiable by a unique
value.
3839 6586–010 1–33

PCI-Based I/O Hardware
The addressing format for Dorado 300 Series servers is IwxCyz:
w = the I/O Module (0 through 7). (Note the location of each number in
Figure 1–13.)
x = the IOP (0 through 3) within the I/O Module. Each I/O Module can have four
IOPs.
y = the slot within the IOP.
0 Slot 0, within the I/O Module, closest to the controlling IOP.
1 to 7 Slot in the expansion rack, if Slot 0 has a PCI Host Bridge Card.
8 Slot 1, within the I/O Module, farthest from the controlling IOP.
9 to F Slot in the expansion rack, if Slot 1 has a PCI Host Bridge Card.
z = the port on the HBA or NIC.
0 if single port or upper port.
1 if lower port.
The following figure is an example of I/O addresses. Notice how the second-to-last
digit of the expansion rack address depends on which slot connects to the expansion
rack.
1–34 3839 6586–010

Figure 1–25. OS 2200 I/O Addressing
1.3.11. SCMS II and I/O Addressing
PCI-Based I/O Hardware
SCMS II is the software that configures the I/O complex for the Dorado 300, 400, 700,
800, 4000, 4100 and 4200 Series systems. The configuration process is structured
well, but you need information on how to relate the physical layout in the racks with
the logical descriptions in SCMS II. The following explains the relationship of the
physical card layout and the SCMS II information. It also explains some differences in
the terminology of SCMS II and this document.
SCMS II Terminology
PROC-NODE-n
Refers to the IP Cell (as it is called in this document). The n value is the same as the w
value in the IO Node definitions that follow.
IO-NODE-w
Called a Remote I/O Module in this document. Each IO-NODE pairs with a PROC-NODE.
The w identifies which I/O Module (0 through 7). Figure 1–12 shows the positioning of
the PROC-NODE (IP Cell) and IO-NODE (I/O Module).
3839 6586–010 1–35

PCI-Based I/O Hardware
IO-NODE-SLOT-w-x
The place in the I/O Module that the IOP is inserted. The w is the value of the IO-NODE
associated with this slot. The x (0 through 3) identifies the location within the I/O
Module. In SCMS II, as you look at the screen, the slots go from top to bottom in
ascending values (0 through 3). See Figure 1–19 for the mapping of the physical
location to the address. Notice that the addressing is not sequential. Look at the IOPw
boxes. If you stand behind the I/O Module (as shown in the picture), the addressing for
x from left to right is 1, 0, 3, 2. Determine where the IOP is placed in the I/O Module
and use that x value to choose the proper IO-NODE-SLOT in SCMS II.
You can click the IO-NODE-SLOT and then, from Insert Device, you can choose XIOP,
SIOP, or CIOP. After choosing, you generate an IOP as described below.
IOPwx
Contains a status that can be set (UP or DOWN).
IOPwx-SLOT-y
For the CIOP or SIOP, two IOPwx-SLOT-y statements are generated. This is because
these IOPs can control both of the PCI slots; the XIOP only generates one statement
because only one PCI card can be controlled by the XIOP; the other slot is unused. The
y value for the IOPwx-SLOT-y statement is 0 or 1. This refers to the slot location (see
Figure 1–19).
1. Click the IOPwx-SLOT-y display in the SCMS II window and click Insert Device.
This enables you to select the PCI card that goes in the slot.
You can choose SCSI, SBCON, Fibre, or an expansion rack.
For example, if you choose Fibre card, SCMS II displays FIBRE-CARD-wx-y-0 and
the following daughter statements:
FIBRE-wx-y-0-PORT-0
FIBRE-wx-y-0-PORT-1
These statements refer to the two ports on the Fibre card. The wx refers to the
IOP number, the y refers to the IOP slot and the 0 indicates it is in an onboard slot.
The 0 or 1 after the PORT refers to the port address.
Note: If you had selected the expansion rack, the number following wx-y would
have been a 1.
2. If you click one of these daughter statements and perform an Insert Device, you
are asked to identify the card type again. There are some situations where
different information is possible, but for most situations you repeat what you
specified earlier; in this example, Fibre.
Now you have actually configured the channel that is attached: Fibre, SCSI,
SBCON, Ethernet. The selection generates another statement, for example
UP I00C80
The UP refers to the UP or DOWN status. The rest of the statement is the I/O
address of the channel. This is the value that is displayed in console statements
and peripheral utilities. See I/O Addressing and Figure 1–13 for how slot values and
I/O addresses correlate.
1–36 3839 6586–010

PCI-Based I/O Hardware
3. If you click the statement (for example: I00C80), you can insert the devices that
are attached to the channel.
4. One device needs a little more configuration information. See 1.6.1 for more
information on configuring the DVD interface card.
1.4. Host Bus Adapters
A host bus adapter (HBA) is a printed circuit board that connects one or more
peripheral units to a computer. The HBA manages the transfer of data and information
between the host and the peripheral.
Notes:
• For the Dorado 300 Servers, the HBAs are installed in the Remote I/O Module or
in the Expansion Racks.
• For the Dorado 400, the HBAs are in the Remote I/O Module or the Expansion
Rack.
• For the Dorado 700, 4000, 4100, and 4200 the HBAs are in the PCI Channel
Module.
• For the Dorado 800, the HBAs are in the Internal I/O Module or Remote I/O
Module.
• SCSI and SBCON channels are not supported on Dorado 800 systems.
1.4.1. Fibre Channel
The Fibre Channel HBAs are industry-standard fiber-optic cards capable of attaching to
your SAN or directly connecting to your fibre-capable peripherals, tape or disk. There
are two styles of fibre cards (FCH1002-PCX, 2-Gb and FCH1042-PCX, 4-Gb).
ClearPath OS 2200 Fibre Channel HBA
The Fibre Channel is a PCI-compliant HBA that is controlled by the SIOP. It attaches to
a Fibre switch or directly to Fiber capable peripherals.
Note: Unisys purchases industry standard HBAs from mission-critical suppliers.
Newer cards and potentially different vendors are introduced on a frequent basis.
The following information is based on the most recent card as of this printing. You
might have different cards. However, they should have similar capabilities to those
shown in the following information.
The fibre channel is dual ported and has two Lucent Connectors.
The FCH1002-PCX HBA supports the following key standards:
• Full duplex
• 2 Gb per second or 1 Gb per second FC Link Speeds
• Fabric support using F_Port and FL_Port connections
3839 6586–010 1–37

PCI-Based I/O Hardware
• Conforms to the PCI-X 1.0a and PCI 2.3 specification
• Universal add-in card (3.3-volt or 5.0-volt)
• 66/100MHz PCI-X bus speeds
The FCH1042-PCX HBA supports the following key standards:
• Full duplex
• 4Gb/s, 2Gb/s or 1Gb/s FC Link speeds
• Fabric support using F_Port and FL_Port connections
• Conforms to PCI–X 2.0 and PCI 3.0 specification
• Universal add-in card (3.3-volt or 5.0-volt)
• 66/100MHz PCI-X bus speeds
The HBAs have the following media support:
• 50/125 mm (multimode)
Up to 300 meters at 2 Gb per second
Up to 150 meters at 4 Gb per second
The following figure shows the Fibre card handle with dual ports.
Figure 1–26. Fibre Card Handle With Dual Ports
1–38 3839 6586–010

LED Status
Style
1.4.2. SCSI
The following assumes the system has been booted and is in operation.
PCI-Based I/O Hardware
• Link Down
Flashing green with no flashing yellow/amber. The adapter has passed Power On-
Self-Test (POST). There is no valid link on Fibre Channel or a problem with the
driver in the OS 2200 system.
• Link Up
Solid green with flashing yellow/amber. The card has passed POST, the link is up
to the Fibre Channel, and the driver is likely to be loaded correctly. The flash speed
indicates the following:
− 1 fast blink = 1-Gb link
− 2 fast blinks = 2-Gb link
• Any other combination usually means the card is defective.
The following table contains the Fibre Channel style:
Table 1–7. Fibre Channel Style
Style Description
FCH1002-PCX Fibre, 2 Gb, PCIX, 2 Channel
FCH1042-PCX Fibre, 4 Gb, PCIX, 2 Channel (Dorado 700, 4000, and
4100 only)
Small computer system interface (SCSI) is a bus architecture where devices are
connected along a line that has a beginning and an end. This cabling scheme is
commonly called a daisy chain.
The SCSI card enables connection to tape or disks.
SCSI was introduced in 1979; SCSI-1 became an ANSI standard in 1986 (X3.131-1986).
SCSI is a parallel interface. The original specification sent out one byte (8 bits) at a
time. 8-bit, or Narrow, SCSI devices require 50-pin (or fewer) connections. Up to
seven different devices can be controlled in a Narrow bus.
A later specification defined a two-byte (16-bit) interface. 16-bit, or Wide, SCSI devices
require 68-pin connections. Up to 15 different devices can be controlled in a Wide bus.
The two extreme ends of a SCSI bus segment must be properly terminated. A
terminator is a small device that dampens electrical signals reflected from the ends of
a cable. Termination is disabled for any SCSI device that is positioned between the
two ends.
3839 6586–010 1–39

PCI-Based I/O Hardware
SCSI is a downward-compatible technology. Older SCSI devices can be installed in a
newer (and faster) SCSI bus segment, but overall system performance might be
reduced.
The SCSI standards have evolved over the years: the speed has gone up, the electrical
requirements have evolved, and the technology for the bus and associated disks has
improved.
Below are some simpler definitions and their relationship to our ClearPath OS 2200
SCSI support.
• Single-Ended SCSI (SE SCSI)
Provides signaling for most SCSI devices. SE SCSI is very susceptible to noise and
has a rather short distance limitation, a maximum of 6 meters, even less with
some later standards. Unless a device says otherwise, it is probably an SE SCSI
device.
Note: SE SCSI disks or tapes are not supported on Dorado servers.
• High Voltage Differential (HVD)
(Also known as "Differential SCSI") provides reliable signaling in high noise
environments over a long bus length (up to 25 meters). HVD hardware cannot be
mixed with other SCSI signal types.
Note: HVD SCSI disks and tapes are supported on Dorado servers. The long
bus length support is ideal for large systems.
• Low Voltage Differential (LVD)
The replacement for HVD. A typical multimode LVD/SE SCSI system provides a
moderately long bus length (up to 12 meters). LVD was introduced as part of the
Ultra-2 SCSI standard in 1997.
Note: LVD support is only for the converter. LVD SCSI disks or tapes are not
supported on Dorado servers.
The SCSI HBA on the Dorado servers has the following characteristics:
• Wide Ultra320 SCSI and LVD support
• Two independent channels
• 68-pin VHDCI connector on each channel
Each channel connection is a Very High Density Centronics Interface with 68 pins
(VHDCI 68). The name comes from the connector first used on the Centronics
printer beginning in the 1960s.
• PCI revision 2.2
• 64 bits
• 33 MHz
• Universal add-in cards (3.3-volt and 5.0-volt signaling)
1–40 3839 6586–010

LED Status
Style
There are no LED indicators.
Figure 1–27. SCSI Channel Card Handle
The following table contains the SCSI HBA style:
Table 1–8. SCSI HBA Style
Style Description
SCI1002-PCX LVD / VHDCI 68 Centronics
Connecting an LVD HBA to HVD SCSI Disks
PCI-Based I/O Hardware
The channel connection on the SCSI HBA is an LVD interface, but the SCSI disks and
tapes supported on Dorado have HVD interfaces. In order to connect the HVD SCSI
disks or tapes to an LVD SCSI HBA, the bus must run through a converter that is an
LVD device.
All peripherals must be on the outboard side of the converter. HVD devices cannot
directly connect to the LVD HBA.
The cable from the HBA to the converter (an LVD device) can be up to 12 meters in
length.
3839 6586–010 1–41

PCI-Based I/O Hardware
The bus for HVD peripherals has a maximum length of 25 meters. This distance is
measured from the converter. The cable that connects the HBA to the converter is not
counted as part of the bus length for the HVD peripherals.
Key Characteristics of the Converter
The converter has the following characteristics:
• Data transfers up to 40 MB per second
• Does not occupy a SCSI ID
• LVD/SE to HVD or HVD to LVD/SE conversion
• Meets ANSI SCSI specifications up to X3.T10/1142D SPI-2 (Ultra2 SCSI) Document
• Supports up to 16 SCSI devices
• Transparent operation (no software required)
• Wide (16-bit SCSI Bus)
• Supports Ultra320/160/80 LVD
• SCSI Connector
Two 68-pin high density (HD) connectors
The following figure shows the back of the converter and where to plug in the LVD
bus from the HBA and the HVD bus from the peripherals.
HBA Converter
Peripherals
Figure 1–28. SCSI LVD – HVD Converter
001751
1–42 3839 6586–010
HVD
LVD/SE

Style
The following table lists the SCSI Converter styles:
Table 1–9. SCSI Converter Styles
PCI-Based I/O Hardware
Style Description Comments
DOR104-SCV LVD-HVD Converter
x indicates the number of ports: 1, 2, 3, or 4
CBL22xx-OSM xx ft Cable where xx is 05 to 35 in
5-foot increments
Has 68-pin HD connectors
Connects HBA to converter
The SCSI HBA has a 68-pin VHDCI connector. The converter has a 68-pin HD
connector. A connector on the cable pairs with the proper connector on the HBA or
converter.
See 8.1 for converter cabling information.
1.4.3. SBCON
The SBCON HBA supports the connection of tapes.
The SBCON HBA is a 32-bit connector.
The following figure shows the SBCON channel card handle.
Figure 1–29. SBCON Channel Card Handle
3839 6586–010 1–43

PCI-Based I/O Hardware
LED Status
Style
1.4.4. FICON
• IRQ (amber)
Upper left LED. When the card generates an interrupt to the host, the LED is lit.
When the host acknowledges, the LED is off.
• ACTV (green)
Lower left LED. The ACTIVE LED is lit when the channel interface is actively
communicating on the channel.
• ONLN (green)
Lower right LED. The ONLINE LED is lit when the channel interface is logically
connected to the channel/control unit. The channel interface must be online to
respond to selections by the host. The channel interface cannot go online if the
channel is disconnected or down.
• FAIL/ERR (amber)
Upper right LED. The FAIL LED is lit at power up, but goes off within a few
seconds if the Power-On Self-Test (POST) passes. During normal operation, this
LED is lit if the receive SBCON signal is not present or is invalid.
The following table contains the SBCON HBA style:
Table 1–10. SBCON HBA Style
Style Description
SBN1001-P64 ESCON/SBCON connection
Bus-Tech FICON HBA
FICON channels support the Bus-Tech PXFA-MM (Multi-Mode) FICON HBA. This PCI-X
Bus FICON Adapter supports either standard FICON (1 Gbs) or FICON Express (2 Gbs).
1–44 3839 6586–010

The following is a picture of the Bus-Tech FICON HBA.
The PXFA-MM FICON HBA
Figure 1–30. Bus-Tech FICON HBA
• Supports full-duplex data transfers.
PCI-Based I/O Hardware
• Supports multiplexing to allow small data transfers concurrently with large data
transfers.
• Supports data transfer to a maximum of 80 km without bandwidth degradation.
• Operates at 133 MHz and supports either 32-bit or 64-bit wide addressing.
Since the Bus-Tech FICON HBA is a bridged board, the PDID numbers defined for
PCIOP-E will not work for the Bus-Tech FICON HBA. The following table shows the
new PDID numbers assigned for the Bus-Tech FICON HBA.
Table 1–11. PCIOP-E PDID assignments for Bus-Tech FICON HBA
Slot 7 Slot 6 Slot 5 Slot 4 Slot 3 Slot 2 Slot 1
Bus=0x88
Dev=0x08
Fun=b’xxx’
Bus=0x0C
Dev=0x08
Fun=b’xxx’
Bus=0x14
Dev=0x08
Fun=b’xxx’
Bus=0xC8
Dev=0x08
Fun=b’xxx’
Bus=0xD0
Dev=0x08
Fun=b’xxx’
Bus=0xD8
Dev=0x08
Fun=b’xxx’
Bus=0xE0
Dev=0x08
Fun=b’xxx’
3839 6586–010 1–45

PCI-Based I/O Hardware
1.5. Ethernet NIC
Ethernet was named in the 1970s for the passive substance called "luminiferous (lighttransmitting)
ether" that was once thought to pervade the universe, carrying light
throughout. Ethernet was also named to describe the way that cabling, also a passive
medium, could carry data everywhere throughout the network.
In the OSI model, Ethernet technology operates at the physical and data link layers,
Layers One and Two. Ethernet supports all popular network and higher-level
protocols, principally Internet Protocol (IP).
Ethernet is an IEEE standard 802.3. (The Institute of Electrical and Electronics Engineers
(IEEE) is a technical professional society that fosters the development of standards
that often become national and international standards.)
Notes:
• The CIOP hardware is not supported on the Dorado 400, 4000, 4100 or 4200.
Instead, the Ethernet NICs are supported through SAIL.
• For the Dorado 300 and 700 Servers, the NICs are installed in the I/O Module or
in the Expansion Racks.
• For the Dorado 400, the NICs are in the Remote I/O Module or the Expansion
Rack.
• For the Dorado 4000 and 4100, the NICs are in the ClearPath 4000, 4100, and
4200 cells respectively.
1.5.1. Original Ethernet
The original Ethernet standard, supporting a data rate of 10 megabits per second, was
widely deployed in the 1980s. The most commonly implemented version was 10Base-
T, Ethernet over Twisted Pair Media. The "10" in the media type designation refers to
the transmission speed of 10 Mbps. The "T" represents the twisted-pair.
1.5.2. Fast Ethernet - 802.3u
Fast Ethernet provides transmission speeds up to 100 megabits per second and is
typically used for LAN backbone systems, supporting workstations with 10BASE-T
cards. Fast Ethernet technology came about in the mid-1990s. It increased
performance and avoided the need to completely recable existing Ethernet networks.
1.5.3. Gigabit Ethernet
Gigabit Ethernet provides a data rate of 1 billion bits per second (one gigabit). It is
being used or is being deployed as the backbone in many enterprise networks.
Existing Ethernet LANs with 10 and 100 Mbps cards can feed into a gigabit Ethernet
backbone.
1–46 3839 6586–010

PCI-Based I/O Hardware
Gigabit Ethernet is the merger of protocols from Fast Ethernet and ANSI Fibre. Gigabit
Ethernet can take advantage of the existing high-speed physical interface technology
of Fibre Channel while maintaining the IEEE 802.3 Ethernet frame format and be
backward compatible for installed media.
It is supported over both optical fiber and twisted pair cable (primarily on optical fiber
but with very short distances possible on copper media).
The following are the IEEE formats for the cable types:
• 802.3z Gigabit Ethernet over Fibre
• 802.3ab Gigabit Ethernet over UTP CAT5 (copper)
1.5.4. Connecting NICs
Fiber
Ethernet NICs are connected using optical fiber cabling or copper wiring.
An optical fiber in American English, or “fibre” in British English, is a transparent thin
fiber for transmitting light. It is flexible and can be bundled as cables. A transmitter
takes digital bits and forms them into light pulses. The transmitter sends light down
the glass or plastic fiber. At the other end, a receiver converts the light pulses back to
a digital signal. Fibers are generally used in pairs, with the fibers of the pair carrying
signals in opposite directions.
The following are some terms to describe the medium:
• Core
The center of the fiber where the light is transmitted.
• Cladding
The outside optical layer of the fiber that traps the light in the core and guides it
along, even through curves.
• Buffer coating
A hard plastic coating on the outside of the fiber that protects the glass from
moisture or physical damage.
The diameter of the core varies. It can be 50 or 62.5 microns for multimode. The
diameter of the cladding (including the core) is 125 microns.
In most cases, there are additional layers and materials to aid in, for example, pulling
the cables into position.
Multimode fiber enables many "modes," or paths, of light to propagate down the fiber
optic path. The relatively large core of a multimode fiber enables good coupling from
inexpensive lasers and the use of inexpensive couplers and connectors.
3839 6586–010 1–47

PCI-Based I/O Hardware
Copper
The cabling distances can be
• 275 m at 62.5 mm
• 550 m at 50 mm
Copper wiring is the primary way to connect PCs or workstations to an Ethernet LAN.
It is sometimes a way to connect the servers to the in-house wiring. For Ethernet,
Unshielded Twisted Pair (UTP) is the transmission medium. It consists of balanced
pairs of copper wire usually with a plastic insulation surrounding each wire. The wires
are twisted around each other to reduce unwanted signal coupling from adjacent pairs
of wires.
UTP is standardized in performance categories based on electrical and transmission
characteristics. All of the following standards are based on four pairs of UTP and
terminate with an RJ-45 jack or can directly connect to a hub.
Cabling distances are up to 100 m.
The cabling today is primarily composed of standards that have evolved from different
categories (CAT):
• CAT5 is suitable for 100 Mbps (Fast Ethernet) and distances up to 100 meters. Fast
Ethernet communications only use two of the four pairs of wires.
• CAT5E (Enhanced) is faster than CAT5. It enables connection speeds of 400 MHz
with a maximum distance of 100 meters. CAT 5E cable supports short-run Gigabit
Ethernet by using all four wire pairs and is backward-compatible with ordinary
CAT5. The connection speed varies depending upon the environment.
• CAT6 was designed with Gigabit Ethernet in mind, and typically enables
transmission speeds of 400 to 550 MHz with a maximum distance of 100 meters.
It utilizes all four pairs of wires and supports communications at up to more than
twice the speed of CAT5E.
1.5.5. NIC Styles
Ethernet NICs can connect to multimode fiber optic or copper cables.
Table 1–12. Ethernet Styles
Style Description
ETH33311-PCX Fiber, single port
ETH33312-PCX Copper, single port
ETH23311-P64 Fiber, single port
ETH23312-P64 Copper, single port
ETH10021-PCX Fiber, dual port
ETH10022-PCX Copper, dual port
1–48 3839 6586–010

Table 1–12. Ethernet Styles
Style Description
ETH10041-PCE Copper, quad port
ETH9330211-PCE Fiber, dual port
PCI-Based I/O Hardware
The following figures illustrate the handles and the cables for the different styles.
1.5.6. Single-Port Fiber Ethernet Handle and Connector
The following information applies to the newer single-port card. The other single-port
card is older and has similar but potentially different characteristics. For example, it
has an SC connector. Important characteristics of the ETH23311-P64 style are
• PCI revision 2.2 support
• 64-bit support
• 66-MHz bus support
• Universal add-in card (3.3-volt or 5.0-volt)
Figure 1–31. Single-Port Fiber Ethernet Handle and Connector
3839 6586–010 1–49

PCI-Based I/O Hardware
LED Status
The LED is an ACT/LNK indicator:
• On
Adapter is connected to a valid link partner.
• Blinking
Adapter is actively passing traffic.
• Off
No link.
1.5.7. Single-Port Copper Ethernet Handle and Connector
LED Status
Important characteristics of the newer single-port card, style ETH23312-P64, are
• PCI revision 2.2 support
• 64-bit support
• 66-MHz bus support
• Universal add-in card (3.3-volt or 5.0-volt)
Figure 1–32. Single-Port Copper Ethernet Handle and Connector
The top LED is the ACT/LNK indicator:
• Green on
Adapter is connected to a valid link partner.
• Green flashing
Data activity.
1–50 3839 6586–010

• Off
No link.
• Yellow flashing
Identify. See Intel PROSet Help for more information.
The bottom LED identifies Ethernet connection speed:
• Off
10 Mbps
• Green
100 Mbps
• Yellow
1000 Mbps
1.5.8. Dual-Port Fiber NIC
The important characteristics are
• PCI revision 2.2 support
• 64-bit support
• 66-MHz bus support
• Universal add-in card (3.3-volt or 5.0-volt)
The ports are identified as the following:
• Upper port = Port A
• Lower port = Port B
The connectors are Lucent Connectors.
PCI-Based I/O Hardware
3839 6586–010 1–51

PCI-Based I/O Hardware
LED Status for Each Port
The LED is the ACT/LNK indicator:
Figure 1–33. Dual-Port Fiber NIC
• On
Adapter is connected to a valid link partner.
• Blinking
Adapter is actively passing traffic.
• Off
No link.
1.5.9. Dual-Port Copper NIC
The important characteristics are
• PCI revision 2.2 support
• 64-bit support
• 66-MHz bus support
• Universal add-in card (3.3-volt or 5.0-volt)
The ports are identified as the following:
• Upper port = Port A
• Lower port = Port B
The connectors are RJ-45.
1–52 3839 6586–010

LED Status for Each Port
Figure 1–34. Dual-Port Copper NIC
The top LED is the ACT/LNK indicator:
• Green on
Adapter is connected to a valid link partner.
• Green flashing
Data activity.
• Off
No link.
• Yellow flashing
Identify. See Intel PROSet Help for more information.
The bottom LED identifies Ethernet connection speed:
• Off
10 Mbps
• Green
100 Mbps
• Yellow
1000 Mbps
1.5.10. SAIL Peripherals
PCI-Based I/O Hardware
The only option for SAIL disk storage is the disks that are internal to the SPM cell.
The SPM cell contains a DVD drive that is used by SAIL only. It is a read/write drive.
The DVD selected for Mariner 3.0 is SATA +/- DVD RW Optical Drive.
3839 6586–010 1–53

PCI-Based I/O Hardware
The Dorado 4280/4290 package styles includes three Quad port copper NICs
(ETH9330422-PCE). Two NICs (eight ports) are used for connections to the BSM
Specialty Engines. The third NIC is for the Customer connections. For the fixed
configurations a dual port fibre NIC is also included (ETH9330212-PCE). Additional NICs
can be ordered.
1.6. Other PCI Cards
Other PCI-based cards can be inserted into the I/O Module.
1.6.1. DVD Interface Card
The I/O Module contains a DVD reader. Unisys is installing a DVD in every I/O Module
on the Dorado 300, 700, and 400 Servers because the OS 2200 release media is on
DVD. The release media is no longer available on tape. Software deliveries for earlier
platforms continue to be on tape. This is consistent with our embrace of industrystandard
technology.
The DVD is read-only on the Dorado 300, 700, and 400 Servers.
Note: The Dorado 700 Series server interfaces with a DVD through the PCIOP-E.
For the Dorado 4000, 4100, and 4200 Series servers, the ClearPath 4000, 4100, and
4200 cells share a DVD with other components.
The DVD interface card is a 32-bit 66-MHz PCI card that connects to an IDE cable. The
other end of the cable connects to an adapter that connects to the DVD reader.
The card has dual ports. The port farthest from the handle is used for the connection
to the DVD reader. The closest port is not used. Other key attributes are
• PCI revision 2.2 support
• 32-bit, 66-MHZ bus support
The DVD interface card is configured in SCMS II. It is located, using SCMS II
terminology, in IOPx1-SLOT-1 where x is the cell number. Select a SCSI card and put
the DVD connection on Port 1. Choose the DVDTP-SUBSYS subsystem.
1–54 3839 6586–010

Figure 1–35. IDE Cable Connection on DVD Interface Card
PCI-Based I/O Hardware
There is no style for the DVD interface card. All Remote I/O Modules have one
installed by the factory and there is no need to order any more.
1.6.2. XIOP Myrinet Card
The XIOP is the I/O processor that connects the XPC-L to an OS 2200 host. The XIOP
has one onboard Virtual Interface (VI) card connected by a fiber optic cable to a VI PCI
card in the XPC-L server.
Note: XIOP is not supported on Dorado 400.
Most sites have two XIOPs connected to the primary XPC-L server and another two
XIOPs connected to the secondary XPC-L server. For more information see the
Extended Processing Complex-Locking (XPC-L) Systems Installation, Configuration,
and Migration Guide (6885 3522).
One PCI card (Myrinet) supports one connection to the XIOP. For Dorado 300, the
Myrinet card only goes into slot 0. Slot 1 must remain unused. For Dorado 700, 4000,
and 4100 the Myrinet card should be installed in slot 7 of the PCI channel module.
A new Myrinet card is used for Dorado 800 and connects only to the XPC-L-3 type
Servers (CP4100 Platform). The myrinet card should be installed in slot 0 of the IO
Manager XIOP. One PCI card (myrinet) supports one connection to the XIOP. For more
information, see the Extended Processing Complex-Locking (XPC-L) Systems
Installation, Configuration, and Migration Guide (3850 7430).
3839 6586–010 1–55

PCI-Based I/O Hardware
The following figure illustrates the Myrinet card 2G and the cable.
LED
LC Connector
Figure 1–36. Myrinet Card 2G and Connector
The following figure illustrate Myrinet Card 10G.
Figure 1–37. Myrinet Card 10G
1–56 3839 6586–010
001560

Style
LED Status
The following table contains the Myrinet Card style:
Table 1–13. Myrinet Card Style
Style Description
MYR1001-P64 2 GB, 1 port, fibre
MYR10110-PCE PCIe, 10gb, 1 port, fibre
MYR10110-SFP SFP Transceiver 10G
The green LED indicates the link state:
• Off
• On
Not connected to an operating port.
Connected to an operating port.
• Blinking
Traffic.
1.6.3. Clock Synchronization Board
PCI-Based I/O Hardware
This transceiver is required for MYR10110-PCE.
The Clock Synchronization Board (CSB) is an optional card that can be installed in
Dorado 300 and Dorado 700 partitions. It is a 3.3/5.0 volt (universal) card.
Note: The CSB is not supported on Dorado 400, 4000, 4100 or 4200.
The CSB retrieves time from an external source and uses it to ensure the accuracy of
the values made available to the Exec. The Exec can use the CSB as the partition Clock
Calendar in place of the time supplied by the Windows-based Service Processor. This
new capability improves accuracy and granularity within a Dorado partition as well as
aiding with synchronization between multiple Dorado partitions.
The CSB supplies time to one partition only. For example, in the following figure, the
top Dorado partition would have a T connector while the bottom would have the
standard BNC connector; the cable would terminate into the card.
3839 6586–010 1–57

PCI-Based I/O Hardware
Figure 1–38. Clock Synchronization Board
The following figure illustrates the CSB handle. Also shown is the BNC (Bayonet Neill
Concelman) T connector. The T connector enables the time signal to be received by
the card and enables the signal to be passed to another card.
Figure 1–39. CSB Handle and BNC Connector
1–58 3839 6586–010

Time Distribution
PCI-Based I/O Hardware
To ensure the overall accuracy of the time values within a system (or between
systems in a clustered, multi-host environment), some manner of time reference must
be used. The following are some examples of a time reference:
• Global Position Satellites (GPS time)
• Radio stations broadcasting a standard government time signal (for example,
WWV, CHU, DCF77)
• Common company time base
The common methods to distribute the time signal internally across the enterprise IT
center are a LAN or a dedicated IRIG-B time signal interface.
System software or the CSB can receive time from a common source destined for an
OS 2200 partition.
System Software Time
CSB Time
Prior to the CSB, system software retrieved Exec time from the Service Processor.
The Service Processor is Windows-based, and unless synchronized with an outside
time reference, Windows time can drift significantly. When time is adjusted on the
Service Processor system, the Exec can experience large jumps in the timeline.
The CSB on a Dorado partition receives time from a time server through a hard-wired
IRIG-B time interface. The CSB does not use a shared LAN or Network Time Protocol
(NTP). In the IRIG-B interface, nothing is allowed to connect to the wire except the
time server and other time card connections, and nothing is transmitted across the
cable except a signal containing the time and date. The cable is located in the
enterprise IT center, presumably behind some physical security mechanism.
Theoretically, it is possible to connect to the cable or potentially override the GPS or
radio connection, but all that could be done would be to impose an erroneous time
value on the systems that use it.
Table 1–14. Partition Time Values Compared to Source Time Values
Attribute
Source:
Service Processor Time CSB Time
Partition compared to source Within 1 second Within 10 milliseconds
Accuracy Within 1 second Within 10 milliseconds
Resolution Within 10 milliseconds Within 1 microsecond
3839 6586–010 1–59

PCI-Based I/O Hardware
Style
CSB Hardware
The following is the CSB style:
Table 1–15. Myrinet Card Style
Style Description
PCI1001-CSB Clock Synchronization Board (CSB)
The following are requirements and attributes for the CSB hardware:
• It can run on any Dorado server except the Dorado 400, 4000, 4100, or 4200.
• It can be installed in the remote I/O Module or in an expansion rack. The CSB can
share an expansion rack with other cards.
− If it is installed in an expansion rack, the expansion rack must be controlled by
a CIOP.
− It can be installed in a CIOP remote I/O Module.
• It supplies time only to the partition in which it is included. A partition can contain
multiple CSBs. However, the Exec selects one CSB for its time input. If that CSB
fails, Exec selects another CSB. In the event that no CSB is available, the Exec gets
the time from the Service Processor.
• It is ready to go out of the box. The firmware is loaded by the IOP. The CSB is
automatically detected at system initialization. No configuration is needed in SCMS
II or the Exec.
• It requires ClearPath OS 2200 Release 9.1 or later.
• The CSB is controlled by the Exec, not CPComm. (It is not used by CPComm even
though it is on an IOP controlled by CPComm.) It is an Exec peripheral in that an
I/O request is issued to the CSB to get the time value. The response time is
around 40 microseconds, much faster than the response time for the Service
Processor. This increases the accuracy of the OS 2200 partition time.
• The Exec actually delivers time values from the hardware dayclock (onemicrosecond
granularity). The Exec initializes the dayclock from the clock calendar
(an external time source: either the CSB or the Service Processor). The Exec
periodically compares the dayclock with the clock calendar. If there is a difference,
the Exec gradually slows down or speeds up the dayclock until it has the same
time as the clock calendar.
For more information about Exec time, see the Exec System Software Administration
Reference Manual (7831 0323) Section 11.
1–60 3839 6586–010

1.6.4. Cipher API Hardware Accelerator Appliance
PCI-Based I/O Hardware
Cipher API provides access for the OS 2200 environment to certain FIPS-certified
industry-standard cryptography algorithms. Calls to Cipher API originate in the user
program according to the needs of the application. The calls provide all necessary data
for Cipher API to perform the cryptography service efficiently. An optional hardware
accelerator appliance can be installed to provide increased performance for bulk
cryptography services.
Note: SCMS II 2.4.0 is required to configure the Cipher API Hardware Accelerator
appliance.
Table 1–16. Cipher Appliance Style
Style Description
CIP1001-PCX PCI 64, 133 MHz, Crypto Accelerator
Unique control unit and device mnemonics have been added to the Exec to support
the hardware accelerator. The following mnemonics are available:
• CRYPCU
For hardware accelerator control units
• CRYPDV
To define the virtual cryptography devices within the accelerator appliance
The appliance is a full-height industry-standard-PCI RoHS-compliant 3.3 volt card. The
hardware accelerator appliance is connected to an HBA SIOP device.
Logical Device Pairs
The physical hardware accelerator appliance is configured into logical devices to
provide cryptography services. When viewed by the EXEC, the devices are
independent devices. When viewed by the Cipher API, the two devices are used as a
device pair connected to a control unit. Both devices in a device pair must be available
to the Exec to be managed by Cipher API.
Each cryptographic request for which the hardware accelerator is desired requires
exclusive use of one logical device pair. The card has 16 cores and each core can
satisfy up to 16 simultaneous cryptographic requests. The maximum number of
devices that can be configured for each hardware accelerator appliance is 256 device
pairs (16 device pairs for each of the 16 cores). Contact your Unisys representative for
sizing services.
Configuring the Hardware Accelerator
Use SCMS II to configure a hardware accelerator appliance. Use the following
guidelines for defining the hardware accelerator appliance.
• The hardware accelerator appliance is
− A unique device type in the Exec (with the mnemonic CRYPCU)
3839 6586–010 1–61

PCI-Based I/O Hardware
− Connected to a PCI bus
On an SIOP, it must attach to one of the two 3.3 volt on-board slots. The SIOP
can physically accommodate two cards, but throughput needs to be
considered.
• The state of control units (of mnemonic CRYPCU) should be UP.
• The state of devices (of mnemonic CRYPDV) should be RV.
• The number of logical devices that are configured is user-determined but limited
to 256 by SCMS II.
Concurrent Cryptography Requests
The number of logical device pairs determines the maximum number of concurrent
cryptography requests. For example, if 32 devices (16 device pairs) are configured and
all are being used, the next request that specifies the use of the hardware accelerator
for cryptography services returns the following error:
No Devices Are Available.
Use of the dynamic mode in a request avoids the potential error and enables the
Cipher subsystem to select the hardware accelerator appliance if available. Otherwise,
the software solution is used to satisfy the request.
Initializing the Hardware Accelerator Card
Cipher API establishes the necessary internal control structures to manage
cryptography services through the background run SYS$LIB$*RUN$.CIPHER. This run
initializes the Cipher subsystem before the first application call, including detecting the
presence of a hardware accelerator card. If the Cipher subsystem is terminated, run
SYS$LIB$*RUN$.CIPHER before using Cipher API again.
Removing a Hardware Accelerator
To remove a hardware accelerator appliance
1. Terminate Cipher API as documented in the Cipher Application Programming
Interface Programming Reference Manual (3826 6110).
2. Bring down the control unit in the Exec.
3. Remove the hardware accelerator card hot from the Remote I/O Module, or stop
the partition and remove power from the cell containing the card.
See the Fault Isolation and Servicing Guide (6875 5552) for more information.
1–62 3839 6586–010

Section 2
Channel Configurations
This section contains information about configuring Dorado 300, 400, 700, 800, 4000,
4100, and 4200 Series server channels. Where there is a difference in configuring
something, the text attempts to identify the proper platform. The channels covered
are the following:
• Host channels
Fibre, SCSI, SBCON, FICON
Note: Dorado 800 does not support SBCON or SCSI Peripherals.
• Communications channel
Ethernet
This section also contains information about hardware characteristics, the OS 2200
view, and SCMS II guidelines.
2.1. Fibre Channel
Fibre Channel works within a Storage Area Network (see Section 6, “Storage Area
Networks”). The Fibre Channel standards provide a multilayered architecture for
moving data across the network. Fibre Channel is supported on SIOP.
Some definitions used in Fibre Channel are as follows:
• Initiator
A host that initiates an I/O request to a storage device. The Fibre Channel Channel
Adapter (FC-CA) is an initiator.
• Target
A control unit of a storage device. The initiator sends I/O requests to targets.
• Logical Unit Number (LUN)
The addressing system for the disks controlled by the control unit.
The Fibre Channel implementation was based on the following standards:
Table 2–1. ANSI and ISO Standards for SCSI Fibre Channel
ANSI/ISO Standard FCP Standard
X3.230-1994 (X3T9) Fibre Channel Physical and Signaling Interface (FC-PH)
X3.269-1996D (X3T10) Fibre Channel Protocol for SCSI (FCP)
3839 6586–010 2–1

Channel Configurations
Table 2–1. ANSI and ISO Standards for SCSI Fibre Channel
ANSI/ISO Standard FCP Standard
X3.272 (X3T11) Fibre Channel Arbitrated Loop (FC-AL)
2.1.1. Fibre Channel on SIOP
Dorado 300, 400, 700, 4000, 4100, and 4200 Series servers offer Fibre Channel support
on SIOP, supporting a PCI-compliant Fibre Channel host bus adapter (HBA).
SCMS II Configurations
The HBA supports up to 16 connections per channel (port). This is different from the
number supported on the legacy connection. The original implementation was done
when just a bunch of disks (JBODs) were the primary connection and more than 16
connections were needed. Today, most connections are done to Symmetrix or
CLARiiON systems, which require far fewer connections.
The following information applies to all HBAs. Since the situation is most likely to
occur with Fibre, it is reproduced here.
The SIOP controls two onboard slots. If each onboard slot contains a link to an
expansion rack, then up to 14 HBAs could be controlled by a single HBA (7 x 2). If all
the HBAs were dual-ported cards, then the SIOP could theoretically have 28 ports
(channels).
The maximum number of ports per IOP is actually less than the theoretical hardware
limit of 28. The limit is 16 ports (channels) for HBAs, 8 dual-port HBAs per SIOP.
When the firmware for the SIOP (HBAs) detects a card, it counts the number of
possible connections. For a dual-port card, the number is two.
Once the maximum number of ports is encountered, the following error message
appears upon detection of the next card in SCMS II:
This IOP can only have 16 channels included in the partition. It has XX.
where XX is 17 to 28.
The port (channel) limitation is true whether or not you have anything connected to the
port. Since the limitation determination occurs at microcode initialization, you cannot
down the unused channel. You must reconfigure it in SCMS II.
2.1.2. Direct-Connect Disks (JBOD)
JBODs are direct-connect disks that are supported on Fibre Channel.
Unisys uses hard target addresses. They must be set before loop initialization time
and cannot change. The disks are put in a priority order and assigned addresses
2–2 3839 6586–010

Channel Configurations
depending on the switch settings on the JBOD enclosure and the positioning of the
drive within the enclosure.
See Appendix A for a complete list of the arbitrated loop addresses.
JBODs support dual-porting and dual access. Each JBOD can be on two separate
arbitrated loops. Both loops can be active, but access to an individual disk from both
loops at the same time is not allowed.
Since addressing is based on the relative position of the disk on the loop, the disk has
the same target address in both loops.
OS 2200 Considerations
• JBODs are not supported in an MHFS environment.
• JBODs can be redundant through the use of unit duplexing.
• JBODs cannot be split into logical disks.
SCMS II Configuration Guidelines
Each JBOD is a target with LUN address 0. The maximum number of JBODs
supported by an OS 2200 host varies according to the I/O processor type; Fibre
Channel on SIOP and a PCI-compliant HBA support up to 16 JBODs.
The two control units on each disk must have different names but the same target
address. The logical control unit address is the decimal equivalent of the AL_PA of the
paired target. The address is determined by switch settings. Each logical subsystem
has one disk with up to two control units.
In SCMS II, the subsystem for JBOD disks is JBOD_SINGLE_SUBSYS or JBOD-
DOUBLE-SUBSYS.
JBOD Configuration Example
The example has 18 subsystems, each with two control units and one disk
(see the table following the figure). The following figure shows how it appears to the
OS 2200 architecture. Only the first four disks are shown.
3839 6586–010 2–3

Channel Configurations
Figure 2–1. Example JBOD Configuration (First 4 of 18 Disks)
The following table shows the SCMS II view of the JBOD configuration:
Table 2–2. SCMS II View of JBOD Configuration
Channel Control Unit CU Address Disks Subsystem
I00C00 CUD00A 239 DSK00 SS00
CUD01A 232 DSK01 SS01
CUD02A 228 DSK02 SS02
CUD03A 226 DSK03 SS03
CUD04A 225 DSK04 SS04
CUD05A 224 DSK05 SS05
CUD06A 220 DSK06 SS06
CUD07A 218 DSK07 SS07
CUD08A 217 DSK08 SS08
CUD09A 214 DSK09 SS09
CUD10A 213 DSK10 SS10
CUD11A 212 DSK11 SS11
CUD12A 211 DSK12 SS12
CUD13A 210 DSK13 SS13
CUD14A 209 DSK14 SS14
CUD15A 206 DSK15 SS15
I00C04 CUD16A 205 DSK16 SS16
CUD17A 204 DSK17 SS17
I20C00 CUD00B 239 DSK00 SS00
CUD01B 232 DSK01 SS01
CUD02B 228 DSK02 SS02
2–4 3839 6586–010

Table 2–2. SCMS II View of JBOD Configuration
Channel Control Unit CU Address Disks Subsystem
CUD03B 226 DSK03 SS03
CUD04B 225 DSK04 SS04
CUD05B 224 DSK05 SS05
CUD06B 220 DSK06 SS06
CUD07B 218 DSK07 SS07
CUD08B 217 DSK08 SS08
CUD09B 214 DSK09 SS09
CUD10B 213 DSK10 SS10
CUD11B 212 DSK11 SS11
CUD12B 211 DSK12 SS12
CUD13B 210 DSK13 SS13
CUD14B 209 DSK14 SS14
CUD15B 206 DSK15 SS15
I20C04 CUD16B 205 DSK16 SS16
2.1.3. Symmetrix Disk Systems
CUD17B 204 DSK17 SS17
Channel Configurations
The EMC Symmetrix family supports control-unit-based Fibre-connected disks. The
Symmetrix systems can be attached to different OS 2200 hosts.
The people who configure Symmetrix systems usually give numbers in hexadecimal. It
is common for OS 2200 references to be in decimal. When discussing configuration
information with other people, make sure you are clear on the numbering system.
Symmetrix Characteristics
A Symmetrix system can support multiple OS 2200 subsystems of disks; each
subsystem can contain up to 512 (decimal) disks.
Access to each disk subsystem is through an EMC Channel Director port. Most sites,
for performance and redundancy reasons, have multiple interface ports accessing the
same group of disks.
Symmetrix control-unit-based systems support MHFS. In an MHFS environment, there
are two channels per host and both channels can be active.
See Section 3 for more information on the hardware characteristics.
3839 6586–010 2–5

Channel Configurations
SAN Characteristics
The Symmetrix family is fabric-capable. It can run in arbitrated loop mode or as a fabric
device. See 7.3 for more information.
In arbitrated loop mode, each Symmetrix interface port connects directly to an OS
2200 host Fibre Channel. This is an arbitrated loop with one initiator and one target. No
other devices are on the loop. Since most sites have multiple interface ports that
access the same group of disks, there are multiple arbitrated loops that access that
group of disks.
SCMS II Configuration Guidelines
Before configuring Fibre devices, read 6.5 to learn more about addressing and how
OS 2200 and SANs interact.
The following are the SIOP configuration limitations:
• The HBA supports up to 16 connections per channel (port).
• Up to 16 ports (channels) per SIOP (software limitation).
Configure Symmetrix systems so that each channel has its own control unit.
See Section 5 to learn more about redundancy and performance.
The following are guidelines for fibre connections:
• Control Units on Arbitrated Loops
− There is one OS 2200 logical control unit for every Symmetrix interface port.
The control unit address is based on the LoopID, as configured in the
Symmetrix system. This LoopID is translated to an AL_PA value. The control
unit address is the decimal version of the AL_PA value of the target.
− The target addresses on each interface port pointing to the same group of
disks are usually the same but they can be different. Since each target is on a
different loop, the values do not have to be equal.
• Control Units on Switched Fabric
− The port that connects to the storage system is configured as the OS 2200
logical control unit address. The address is a decimal version of the last 12 bits
of the port address and is of the form xx-yyy.
− Only the port that connects to the storage device is configured. Neither the
port that connects to the OS 2200 host nor any interswitch link (ISL) ports are
configured in SCMS II.
• Fanouts
− Fanout on a switch is when multiple OS 2200 host channels point to the same
Symmetrix disk channel. Fanout is usually done when the Symmetrix disk
channel has a higher bandwidth than the OS 2200 host channel. (Example: 1 Gb
on the Dorado system and 2 Gb on the Symmetrix side).
2–6 3839 6586–010

Channel Configurations
− You should not fanout when the OS 2200 channel and the Symmetrix IOP are
rated at the same speed.
− When configuring SCMS II, each OS 2200 host channel has its own control
unit. For each OS 2200 channel that accesses the same Symmetrix interface
port, each control unit has a different name but the same address.
In OS 2200 terminology, a logical disk is the same as a LUN.
There should be one OS 2200 subsystem for every group of disks (up to 512). There
can be up to sixteen physical channels active per subsystem. More can be configured
but they are only used for redundancy. See 3.2.3 for Command Queueing information.
In SCMS II, the subsystem for all Symmetrix disks is UNIVERSAL-DISK-SUBSYSTEM.
Arbitrated Loop Configuration Example
The following are used in the example:
• 256 logical disks
• Six interface ports, each connecting to one OS 2200 host channel
The following figure shows this connection:
Figure 2–2. Arbitrated Loop
Since there are six Symmetrix interface ports, there are six arbitrated loops. Each loop
connects to an FC-CA on the OS 2200 host.
3839 6586–010 2–7

Channel Configurations
The OS 2200 architecture has six logical control units (one for each channel), with all
logical disks accessible from each control unit. The disks and the control units are
common to each other and are all contained within one OS 2200 logical subsystem.
See the following figure.
Figure 2–3. OS 2200 View of Arbitrated Loop Example
SCMS II would contain configuration information as shown in the following table. This
would all be on one OS 2200 subsystem.
Table 2–3. SCMS II View of Arbitrated Loop Example
Channel Control Unit Disks CU Address LUN Address
I00C00 CUDAA DSK000–DSK255 00-239 0 – 255
I20C10 CUDAB DSK000–DSK255 00-239 0 – 255
I10C00 CUDAC DSK000–DSK255 00-239 0 – 255
I30C10 CUDAD DSK000–DSK255 00-239 0 – 255
I40C00 CUDAE DSK000–DSK255 00-239 0 – 255
I60C10 CUDAF DSK000–DSK255 00-239 0 – 255
Switched Fabric Example
Symmetrix disks can be hooked up in a switched fabric. Figure 2–4 is similar to
Figure 2–2 illustrating an arbitrated loop.
• 256 logical disks
• Six OS 2200 host channels connected to a switch
• Three Symmetrix interface ports connect to a switch.
2–8 3839 6586–010

Channel Configurations
This example assumes the Symmetrix disk system has the faster interface ports than
the OS 2200 channels, using a 2:1 fanout. For this example, the switch ports used for
the Symmetrix system are 01, 02, and 03.
Figure 2–4. Switched Fabric Example
The way that the OS 2200 architecture sees the configuration is shown in the
following figure. The architecture appears the same as it does in the arbitrated loop
configuration. Since all the disks and the control units are connected to each other,
there is only one subsystem.
3839 6586–010 2–9

Channel Configurations
Figure 2–5. OS 2200 View of Switched Fabric Example
The information in the following table is placed in SCMS II. This is all on one OS 2200
subsystem.
Note: Every group of two control units has the same CU address. The two host
channels point to one port on the switch that connects to the Symmetrix system.
Table 2–4. SCMS II View of Switched Fabric
Channel Control Unit Disks CU Address
LUN
Address
I00C00 CUDAA DSK000–DSK255 01-000 0 – 255
I20C10 CUDAB DSK000–DSK255 01-000 0 – 255
I10C00 CUDAC DSK000–DSK255 02-000 0 – 255
I30C10 CUDAD DSK000–DSK255 02-000 0 – 255
I40C00 CUDAE DSK000–DSK255 03-000 0 – 255
I60C10 CUDAF DSK000–DSK255 03-000 0 – 255
2.1.4. CLARiiON Disk Systems
The CLARiiON family is a control-unit-based system. The CLARiiON family is a
midrange departmental system. It does not have all the mission-critical attributes that
the high-end Symmetrix system does. Some sites configure the CLARiiON systems
with less redundancy than the Symmetrix systems. An example below shows some
possibilities.
Multiple hosts can access CLARiiON systems. Each host can have a set of disks on the
CLARiiON system.
2–10 3839 6586–010

Channel Configurations
For sites wanting redundancy, OS 2200 Unit Duplexing should be used because the
Storage Processor is a single point of failure.
See 7.4 for more information on the hardware characteristics.
The CLARiiON family can be run in arbitrated loop mode or as a fabric device. See
Section 6, “Storage Area Networks,” for more information.
SCMS II Configuration Guidelines
Before configuring Fibre devices, read Section 6, “Storage Area Networks,” to learn
more about addressing and how OS 2200 and SANs interact.
The following are the SIOP configuration limitations:
• The HBA supports up to 16 connections per channel (port).
• Up to 16 ports (channels) per SIOP (software limitation).
The following are the SCMS II configuration guidelines:
• Control Units on an Arbitrated Loop
− Each interface port connects to one channel. Each connection is an arbitrated
loop.
− There is one OS 2200 logical control unit for every arbitrated loop. The control
unit address is the decimal version of the AL_PA value of the target.
− The AL_PA value for the target (control unit) is assigned in the CLARiiON
configuration. The configuration asks for the SCSI ID. This is the same as the
Device Address Setting shown in Appendix A. Usually, the value is set to 0.
This equates to an AL_PA value of EF and an SCMS II value of 239.
• Control Units on Switched Fabric
− There is one logical control unit for every interface port. The OS 2200 logical
control unit address points to the port that connects to the storage subsystem
and that is accessible by that host channel. The address is a decimal version of
the last 12 bits of the port address and is of the form xx-yyy.
− Many sites have set up a fanout with multiple OS 2200 host channels sharing
access to a CLARiiON port. Newer CLARiiON systems have a 2-Gb connection
and the OS 2200 host channel has a 1-Gb connection. Even sites with high I/O
loads and the newer Fibre Channels can consider a 2:1 fanout. Sites with lower
throughput might consider a higher fanout. When configuring SCMS II, each
OS 2200 host channel has its own control unit. For the host channels
accessing the same CLARiiON port, each control unit has a different name but
the same address.
In OS 2200 terminology, a logical disk is the same as a LUN. Behind each target are the
disk partitions (LUNs) associated with that Storage Processor. These disks should be
connected to the logical control unit associated with that Storage Processor.
3839 6586–010 2–11

Channel Configurations
For each host that can access the CLARiiON system, there is a limit of 233 LUNs for
the ESM7900 and 512 LUNs for the CX models. The LUN values for each server must
be unique.
There should be one OS 2200 subsystem for every group of disks.
In SCMS II, the subsystem for all CLARiiON disks is UNIVERSAL-DISK-SUBSYSTEM.
Development and Test Example: No Redundancy
Some customers use their CLARiiON system for non-mission-critical applications.
They do not need redundant connections. Here is an example:
• Eight disks connecting through a single channel and a single Storage Processor
• Arbitrated loop to OS 2200 host
Figure 2–6. Direct-Attach CLARiiON System
OS 2200 sees this as a simple connection. See the following figure:
2–12 3839 6586–010

Channel Configurations
Figure 2–7. OS 2200 View of Channel for Nonredundant Disks
The following table illustrates the SCMS II view of the example. This is all on one
OS 2200 logical subsystem.
Channel
Table 2–5. SCMS II View of Channel for Nonredundant Disks
Control
Unit
SCSI
ID
Port Adr
(hex)
SCMS II
(dec)
Disk
Name
I00C00 CUDAA 0 EF 239 DSK000 0
Redundant Configuration Example
DSK001 1
DSK002 2
DSK003 3
3839 6586–010 2–13
LUN
DSK004 4
DSK005 5
DSK006 6
DSK007 7
Many sites configure their CLARiiON systems as redundant, using OS 2200 Unit
Duplexing. This example is a redundant version of the earlier example:
• There are eight unit-duplexed disks. In this example, the duplexed disks are on the
other Storage Processor, but on the same CLARiiON system. Most sites have the
unit-duplexed disks on a separate CLARiiON system for even more redundancy.

Channel Configurations
• There are two channels per Storage Processor. This gives redundancy in case a
channel is lost. It also gives increased performance.
The following figure shows the CLARiiON system that appears to OS 2200 and SCMS
II:
• There are 16 independent disks. SCMS II and the OS 2200 I/O architecture do not
recognize unit duplexing.
• For each string of disks, there are two independent control units giving dual
access to the disks. The Storage Processors (SP) are not visible to SCMS II or OS
2200.
• In SCMS II, put each control unit in a separate cabinet.
Figure 2–8. Unit-Duplexed Configuration
The following table provides the configuration information required for SCMS II.
Configure two subsystems: one for the disks on SP-A and one for the disks on SP-B.
2–14 3839 6586–010

Channel
Channel Configurations
Table 2–6. SCMS II View of Unit-Duplexed Example
Control
Unit SCSI ID
AL_PA
SCMS II
Disk
Name
I00C00 CUDAA 0 EF 239 DSK000 0
3839 6586–010 2–15
LUN
DSK001 1
DSK002 2
DSK003 3
DSK004 4
DSK005 5
DSK006 6
DSK007 7
I20C10 CUDAB 0 EF 239 DSK000 0
DSK001 1
DSK002 2
DSK003 3
DSK004 4
DSK005 5
DSK006 6
DSK007 7
I30C10 CUDBA 0 EF 239 DSK100 100
DSK101 101
DSK102 102
DSK103 103
DSK104 104
DSK105 105
DSK106 106
DSK107 107
I40C10 CUDBB 0 EF 239 DSK100 100
DSK101 101
DSK102 102
DSK103 103
DSK104 104
DSK105 105
DSK106 106
DSK107 107

Channel Configurations
2.1.5. T9x40 Family of Tape Drives
The T9x40 family of tape drives supports fibre connections. The following are the
members of the family:
Table 2–7. T9x40 Family of Tape Drive Styles
Model Style Comments
T9840A CTS9840 Oldest member, arbitrated loop. 20 GB native capacity.
T7840A CTS7840 Same as 9840A but with fabric support.
T9840B CTB9840 Same capacity as 9840A but two times faster. Fabric support.
T9840C CTC9840 Twice the capacity of 9840A or B. Fabric support.
T9940B CTB9940 10 times the capacity of 9840A or B. Fabric support.
All tape drives have a single drive and a single control unit.
Each control unit has two ports (A and B). The tape system can access one or more
hosts. It can also access one or more partitions within a host. Only one tape port can
access the drive at the same time. The two ports increase redundancy, but do not
increase performance.
For more information on how the different family members connect to an arbitrated
loop or a SAN, see 6.4 or 6.5.
SCMS II Configuration Guidelines
SCMS II only allows a host channel to access the tape drive through one path. This
means that a host channel can either access a tape drive through tape drive Port A or
Port B, not both. In an arbitrated loop environment, it is not physically possible for one
host channel to access both ports. In a switched environment, it is physically possible
for one host channel to access both ports of a tape drive, but this is restricted by
SCMS II.
SCMS II allows up to eight channels connected to a tape drive. However, any one
partition can only have up to four connections configured.
Each member of the T9840 family is configured with a single control unit. If multiple
channels from the same partition can access the tape drive, the control unit name on
both channels is the same. However, the control unit address must be different.
2–16 3839 6586–010

The following are some of the guidelines:
• Up to 16 devices can be configured on a channel.
Channel Configurations
• Different members of the 7840/9840/9940 family can be configured on the same
channel.
• Arbitrated loop mode
The address is the decimal representation of the AL_PA value assigned to the tape
port.
• Switched fabric
The address is based on the location on the switch to which the tape port
connects, the port that connects to the tape drive configured as the OS 2200
logical control unit address. The address is a decimal version of the last 12 bits of
the port address and is of the form xx-yyy.
• Only the port that connects to the storage device is configured. Neither the port
that connects to the OS 2200 host nor any ISL ports are configured in SCMS II.
For the T9840A, T9840B, and T7840A, the subsystem is CTS9840-SUBSYS. For
the T9840C, the subsystem is CTS9840C-SUBSYS.
For the T9940B, the subsystem is CTS9940B-SUBSYS.
• There must be one subsystem for each tape drive and its control unit.
Before configuring Fibre devices, read Section 6, “Storage Area Networks,” to learn
more about addressing and how OS 2200 and SANs interact.
Switched Fabric Configuration Example
The switched fabric example contains the following:
• Two T9840Bs
Each drive has Ports A and B connected to the SAN. For redundancy, Port A
connects to one switch and Port B connects to another switch.
• Two hosts or two partitions
Each has two Fibre Channels connecting to the SAN. The host Fibre Channels
connect to different switches for redundancy.
• The SAN in zones
The zones are shown within the dotted circle. Each zone has one host channel and
two port connections, one to each tape drive.
3839 6586–010 2–17

Channel Configurations
OS 2200 View
The following figure illustrates this configuration example:
Figure 2–9. Multihost Configuration
OS 2200 sees each tape drive having two connections to the host. Only one path to a
drive can be used at a time. The following figure shows how it looks to the OS 2200
architecture of one host.
Figure 2–10. OS 2200 View of Tape Drives
2–18 3839 6586–010

SCMS II View
Channel Configurations
The following table shows how the device is configured in SCMS II in one host or
partition. Each tape drive and control unit is a separate subsystem.
Channel
Table 2–8. SCMS II View of Switched Fabric
Control
Unit
Tape
Device
Port Address
(Hex)
SCMS II Value
(dec)
I00C00 T98A T98A0 010200 02-000
T98B T98B0 010300 03-000
I20C00 T98A T98A0 010600 06-000
T98B T98B0 010700 07-000
2.1.6. 9x40 Tape Drives on Multiple Channels Across a SAN
Many sites are connecting multiple tape drives from the 9x40 family to a SAN switch
and setting up access to the OS 2200 host through multiple channels that also connect
to their Storage Area Network (SAN).
Configuring for Optimum Channel Performance
For any one partition, you can configure the following:
• Up to 16 control units per channel
• Up to four channels per control unit
• One path per control unit per channel
The T9840 family member is a single device with an embedded control unit. The
control unit has two ports, A and B. The ports cannot be sending I/O at the same time.
You can have a tape pool of up to 16 tape drives and up to four channels; all the drives
can access all the channels. This means that 16 drives can access the same channel
and four channels can access each drive.
You can have access to a tape drive through both Port A and B. However, a channel
cannot connect to the drive through both ports. If both ports are configured, they
must go to different channels.
You probably do not want to have 16 drives active on four channels. Our performance
guideline is that you have a maximum of three drives per channel. However, this does
not apply in all cases. Each site must evaluate its needs. You might set up a pool of
tapes with more drives per channel. You might also set up a pool of tapes with one
drive per channel because you need to put data onto a tape as fast as possible and
that is best accomplished when the drive is not sharing the channel or the SIOP.
3839 6586–010 2–19

Channel Configurations
Larger Pools Are Better
A big pool of channels (up to four) and tapes (up to 16) is better than two small pools,
assuming that both pools have similar performance characteristics. This can be shown
in the following examples using eight tape drives and four channels.
The examples compare one pool of eight drives and four channels with two pools,
each with four drives and two channels. The larger pool has better balance and the
potential for higher throughput under most conditions.
• Example: All Four Channels in Use
The tape selection algorithm is rotational. It selects the first available drive starting
at drive 0. The next selection takes the first available drive starting at drive 1, and
so on. When the drive is selected, the least busy channel is used. If all four
channels are in the same pool, then the least busy of the four is chosen (optimal).
If there are two pools, the rotational tape selection is the same. It starts at drive 0
and so on. This causes situations where four drives are busy on two channels and
fewer (or no) drives are busy on the other two channels. The load is usually not
balanced.
• Example: If One Channel Fails
If you have four channels sharing the load for eight drives and one channel fails,
you can still run reasonably well because three channels are sharing eight drives.
If you have two pools where each pool contains two channels and one channel
fails, you probably have a problem because four drives are sharing one channel.
T9840 Configuration Example: No Redundancy
For this discussion, assume four channels with two drives per channel for a total of
eight tape drives. They are all in the same pool.
Physical SAN Layout
The following figure shows this configuration in a SAN environment
Figure 2–11. Load-Balanced SAN
2–20 3839 6586–010

Channel Configurations
The port addresses chosen for the tape drives are 0 through 7. However, the tape
drives can be connected to any port on the switch. OS 2200 can handle any port
address as long as the proper zoning rules are followed.
The port addresses selected for the OS 2200 host channels are arbitrary; any port can
be used. Neither SCMS II nor the Exec has any knowledge of what port is used for the
OS 2200 channel.
The figure only uses Port A on each controller; the second port is only valuable for
redundancy. The figure could have used Port A on some drives and Port B on others,
but this makes the picture more complicated and it does not add any value.
OS 2200 Architecture
The OS 2200 architecture has no awareness of SANs. The architecture is based on
channels, control units, and devices. When the example is configured according to our
recommendation, the architecture shows eight devices daisy chained to four channels;
each channel can access eight devices. The following figure shows all four channels
connected to one port on the control unit.
Figure 2–12. Daisy Chaining with Eight Control Units
SCMS II View
This SAN layout must be properly configured in SCMS II.
• Each tape drive or control unit is a separate subsystem. This example has eight
tape drives so there are eight subsystems.
• The following table shows the recommended naming conventions for
configurations.
3839 6586–010 2–21

Channel Configurations
Table 2–9. SCMS II Values in Daisy-Chain of Eight Control Units
Channel
Control
Unit
Tape Device
Port Address
(Hex)
SCMS II
Value (dec)
I00C00 T98A T98A0 010000 00-000
T98B T98B0 010100 01-000
T98C T98C0 010200 02-000
T98D T98D0 010300 03-000
T98E T98E0 010400 04-000
T98F T98F0 010500 05-000
T98G T98G0 010600 06-000
T98H T98H0 010700 07-000
I10C00 T98A T98A0 010000 00-000
T98B T98B0 010100 01-000
T98C T98C0 010200 02-000
T98D T98D0 010300 03-000
T98E T98E0 010400 04-000
T98F T98F0 010500 05-000
T98G T98G0 010600 06-000
T98H T98H0 010700 07-000
I20C00 T98A T98A0 010000 00-000
T98B T98B0 010100 01-000
T98C T98C0 010200 02-000
T98D T98D0 010300 03-000
T98E T98E0 010400 04-000
T98F T98F0 010500 05-000
T98G T98G0 010600 06-000
T98H T98H0 010700 07-000
I30C00 T98A T98A0 010000 00-000
T98B T98B0 010100 01-000
T98C T98C0 010200 02-000
T98D T98D0 010300 03-000
T98E T98E0 010400 04-000
T98F T98F0 010500 05-000
T98G T98G0 010600 06-000
T98H T98H0 010700 07-000
2–22 3839 6586–010

Zones
Channel Configurations
You should do single-channel zoning (each OS 2200 host channel is in a separate zone)
in the switch. There should be four zones for this example.
• For I00C00
Switch 1, Port 20 can talk to Switch 1, Port 00 to 07
• For I10C00
Switch 1, Port 21 can talk to Switch 1, Port 00 to 07
• For I20C00
Switch 1, Port 22 can talk to Switch 1, Port 00 to 07
• For I30C00
Switch 1, Port 23 can talk to Switch 1, Port 00 to 07
Redundancy and the Real World
When configuring your tapes, you probably want to build in some redundancy. The
pictures above explained load balancing across a simple configuration, but for most
sites such a simple configuration has insufficient redundancy. Now add redundancy to
the example.
The example is still the same: four channels and eight drives. One problem with the
earlier example is that there are the following single points of failure:
• If the switch fails, all access to the drives is lost.
• If the port on a drive fails, access to that drive is lost.
You can remove these points of failure by adding a second switch and using both
ports of the drive. The following figure shows what a redundant environment looks
like.
Figure 2–13. Redundant SAN
3839 6586–010 2–23

Channel Configurations
The performance potential for the redundant configuration is the same as the
nonredundant one because all four channels can access all eight drives and the load is
shared across the channels. The difference is that two channels access all the drives
through Switch 1, and two channels access all the drives through Switch 2. You have
not increased performance, but have added redundancy.
• If you lose a switch, you can still access all the drives.
• If you lose a tape port, you can still access the drive.
You have put all the A ports of the drives through one switch and all B ports through
the other. This setup creates the desired redundancy and is easy to visualize. (Both
ports of any one drive should not go through the same switch. If you lose the switch,
you lose the drive.)
Note: The port addresses for Tape Drive Port A and Port B are the same on
Switches 1 and 2. This is not a requirement. OS 2200 can handle any port address as
long as the proper zoning rules are followed.
OS 2200 Architecture
The following figure illustrates how the redundant SAN configuration looks to the
Exec. It is still four daisy chains (four channels) but now they use both ports on the
tape controllers.
Figure 2–14. Redundant Daisy Chaining
2–24 3839 6586–010

SCMS II Configuration
Channel Configurations
Each tape drive or control unit is a separate subsystem. This example has eight
subsystems.
There are still four channels. Instead of all four connected to Switch 1, there are two
channels connected to Switch 1 and two channels connected to Switch 2.
The number of paths in this configuration is the same as for the non-redundant one.
Each tape drive still connects to all four channels. In the non-redundant case, 32 paths
run through Switch 1. In the redundant case, 16 paths run through Switch 1 and 16
paths run through Switch 2.
This configuration does use more ports on the switches. In the non-redundant
configuration, 12 ports are used (four for channels and eight for drives). In the
redundant configuration, 20 ports are used: four for channels, eight for the Port A tape
drives, and eight for the Port B tape drives.
The SCMS II statements generate the paths between the channels and the control
units. Even though more switch ports are used, both the non-redundant and the
redundant configuration have the same number of paths: 32.
In the non-redundant configuration, four paths run through Port A of each tape drive. In
the redundant configuration, two paths run through Port A and two paths run through
Port B on each tape drive. Since Port B is used for each tape drive, an extra eight
switch ports are required.
The following table shows a different switch specified for the last two channels. See
the column labeled Port Address and look at the first two digits in the cells.
Channel
Table 2–10. SCMS II View of Redundant Daisy Chains
Control Unit
Tape Device
Port Address
(Hex)
SCMS II
Value (dec)
I00C00 T98A T98A0 010000 00-000
T98B T98B0 010100 01-000
T98C T98C0 010200 02-000
T98D T98D0 010300 03-000
T98E T98E0 010400 04-000
T98F T98F0 010500 05-000
T98G T98G0 010600 06-000
T98H T98H0 010700 07-000
I10C00 T98A T98A0 010000 00-000
T98B T98B0 010100 01-000
T98C T98C0 010200 02-000
T98D T98D0 010300 03-000
T98E T98E0 010400 04-000
3839 6586–010 2–25

Channel Configurations
Channel
Table 2–10. SCMS II View of Redundant Daisy Chains
Control Unit
Tape Device
Port Address
(Hex)
SCMS II
Value (dec)
T98F T98F0 010500 05-000
T98G T98G0 010600 06-000
T98H T98H0 010700 07-000
I20C00 T98A T98A0 020000 00-000
T98B T98B0 020100 01-000
T98C T98C0 020200 02-000
T98D T98D0 020300 03-000
T98E T98E0 020400 04-000
T98F T98F0 020500 05-000
T98G T98G0 020600 06-000
T98H T98H0 020700 07-000
I30C00 T98A T98A0 020000 00-000
Zones
T98B T98B0 020100 01-000
T98C T98C0 020200 02-000
T98D T98D0 020300 03-000
T98E T98E0 020400 04-000
T98F T98F0 020500 05-000
T98G T98G0 020600 06-000
T98H T98H0 020700 07-000
Single-channel zoning should be used. This example of two switches should have four
zones.
• For I00C00
Switch 1, Port 20 can talk to Switch 1, Port 00 to 07
• For I10C00
Switch 1, Port 21 can talk to Switch 1, Port 00 to 07
• For I20C00
Switch 2, Port 20 can talk to Switch 2, Port 00 to 07
• For I30C00
Switch 2, Port 21 can talk to Switch 2, Port 00 to 07
Remote Tape Drives
Many sites are moving some tape drives to a remote site as part of their disaster
protection plans. This is very often done as part of a SAN where two switches, many
miles or kilometers apart, are connected by remote links.
2–26 3839 6586–010

Channel Configurations
The following figure shows such a possibility. It takes the previous redundant SAN
example and uses four switches to move the tapes offsite.
Figure 2–15. Redundant SAN with Remote Tapes
The SCMS II configuration for this example is the same as for the previous redundant
one. The switch numbers have been adjusted so that Switches 1 and 2 are now
remote. This minor change allows the configuration for redundant SANS, Figure 2–13,
to be used for the figure above.
SCMS II has no knowledge of the switch ports that connect to the host channels or
any knowledge of interswitch links. SCMS II only cares about the port addresses that
connect to the tapes.
The daisy-chaining figure shown for redundant SANs, Figure 2–14, is also the same for
Figure 2–15.
2.1.7. Connecting SCSI Tapes to a SAN
Some sites have SCSI peripherals and want to use them (especially tapes) to access
hosts across a SAN. The Crossroads 4150 has been qualified for that purpose.
The Crossroads converter has a SCSI bus for devices as well as a fibre connection that
can connect to a fabric switch. The OS 2200 host, running across a SAN, can address
the SCSI devices because the converter builds a table where the device address (SCSI-
ID) has a unique LUN address.
3839 6586–010 2–27

Channel Configurations
2.2. SCSI
Figure 2–16. FC / SCSI Converter
For more information on connecting SCSI tape drives to a converter, see Section 6.4.
SCMS II Configuration
• When configuring the features associated with the device type, enter the number
of devices connected to that converter (the default for tapes is one).
• When configuring the control unit address, follow the SCMS II rules for a SAN
address (xx-yyy).
• When configuring each device on the control unit, set the device address
(ADDR [decimal]) to the LUN value assigned by the converter.
The SCSI-2W Ultra channel adapter supports SCSI-3, officially termed SCSI-3-Fast 20.
The host supports SCSI Ultra by using the SCSI-2 command set (a subset of the SCSI-3
command set).
Communication occurs when the initiator, the OS 2200 host channel adapter,
originates a request, and the target (tape or disk controller) performs the request.
On disk devices, the target normally disconnects during the seek and latency time.
During the time the target is disconnected from the bus, the host (initiator) can use the
bus to transfer commands and data for any other device. The result is that the bus
utilization can be very high, with many operations overlapped to maximize throughput.
2–28 3839 6586–010

Channel Configurations
Characteristics of the Unisys SCSI-2W Ultra channel adapter are as follows:
• Only one OS 2200 series channel adapter can be configured per SCSI bus. SCSI
multi-initiator mode is not supported on the OS 2200 series.
• A maximum of 15 targets can be configured per channel. Target addresses range
from 0 through 6 and 8 through 15. SCSI bus address 7 is reserved for the SCSI-2W
channel and cannot be assigned as a target address. Address 7 has the highest
priority on the SCSI bus, followed in order by 6 through 0 and then by 15 through 8
(lowest).
• Disks and tapes are the only target types supported for attachment to the SCSI
bus.
SCSI-2N Devices
The SCSI-2W channel adapter can be connected to either SCSI-2N or SCSI-2W devices.
The 4125 (9-track open reel tape drive) is a SCSI-2N device. SCSI-2N devices require an
adapter cable (ADP131-IT3) because of the following:
• When only SCSI-2N targets are connected to the channel, SCSI addressing
protocol limits the maximum number of attached targets to 7 (SCSI bus addresses
0 through 6).
• When SCSI-2W and SCSI-2N targets are intermixed, the SCSI-2N targets use
addresses 0 through 6 and the SCSI-2W targets use any unused addresses in the 0
through 6 range and addresses 8 through 15.
• When physically connecting a mixed string of SCSI-2N and SCSI-2W targets, cable
the SCSI-2W targets to the channel before the SCSI-2N targets.
SCSI on a PCI-Based IOP—SIOP
The PCI-based HBA
• Supports LVD
It requires a converter to connect to HVD SCSI peripherals. The converter is not
configured in SCMS II.
• Supports two channels (ports) per card
There is an updated I/O addressing scheme to identify the second channel. Proper
configuration requires knowledge of the channel address on the card. See “I/O
Addressing” in section 1 for more information.
The following are configuration examples for SCSI peripherals on the SIOP.
3839 6586–010 2–29

Channel Configurations
SCSI Device Layout (for all IOPs)
The following figure illustrates a configuration for a SCSI channel adapter:
Figure 2–17. Single-Port Configuration
Targets (disks) on the server platform can be divided into two classes:
• Direct-connect systems (JBODs)
• Control-unit-based systems (EMC)
2.2.1. Direct-Connect Disks (JBOD)
Just a bunch of disks (JBOD) are direct-connect disks that are typically used in test
environments or in non-mission-critical situations. They are the least expensive option
for disks but have less redundancy and performance capacity as compared to a
control-unit-based system.
JBODs do not use external control units and are referred to as direct-connect devices.
The control unit is on the SCSI drive. These devices have single-port attachment
capability to the host. The disk can be connected to only one SCSI channel.
JBOD Configuration Characteristics
The following are the characteristics of a JBOD configuration:
• JBODs do not support multiple logical disks per physical drive.
• JBODs service only one I/O at a time.
• Only one SCSI-2W disk can be configured per target.
2–30 3839 6586–010

Channel Configurations
• There can be up to 15 targets (disks) per SCSI channel. The logical unit number
(LUN) is 0.
• The SCSI target addresses are determined by the position in the rack (addresses 0
to 6). A jumper can be used to daisy chain a second rack to the bus (addresses 8
to 14). Address 7 is reserved for the SCSI channel adapter (initiator).
• It is recommended that the first JBOD start at address 0 and then fill up the
addresses consecutively.
• JBODs cannot be mirrored other than through host software (unit duplexing).
• Direct-connect SCSI-2W disks cannot run in an MHFS configuration. The OS 2200
operating system does not support multi-initiator. JBODs typically do not provide
multiple parallel interfaces.
• Since there are usually multiple JBOD disks on one channel and therefore multiple
subsystems per channel, SCSI channels are usually daisy chained.
SCMS II Configuration Guidelines
The following are the SCMS II guidelines for configuring a JBOD:
• Each target (JBOD) has a single control unit and the control unit connects to only
one disk and one channel. The control unit address is the same as the target
address and is determined by the position in the rack.
• Each disk, and its associated control unit, is configured as a single logical
subsystem.
• In SCMS II, the subsystem is JBOD-SINGLE-SUBSYS.
JBOD Configuration Example
There are seven JBOD disks on a SCSI-2W channel adapter bus. This system has
seven subsystems, each with one control unit and one disk.
Table 2–11. JBOD Disk Subsystems and Target Addresses
Subsystem Control Unit Disks CU/Target Address
SS00 CUD00 DSK00 0
SS01 CUD01 DSK01 1
SS02 CUD02 DSK02 2
SS03 CUD03 DSK03 3
SS04 CUD04 DSK04 4
SS05 CUD05 DSK05 5
SS06 CUD06 DSK06 6
3839 6586–010 2–31

Channel Configurations
The following figure shows how the example appears to SCMS II. It has one channel
with seven control units connected and each controller has one disk.
Figure 2–18. JBOD Disk Configuration
2.2.2. Control-Unit-Based Disks
EMC Symmetrix systems support SCSI connections.
The OS 2200 SCSI implementation allows 15 target addresses per SCSI channel. The
OS 2200 architecture supports 32 LUNs per target, but only 16 LUNs per target can be
configured due to the EMC implementation.
In the OS 2200 architecture, a logical disk equates to a LUN on the EMC system. A
single SCSI channel can accommodate 240 logical disks (15 targets x 16 LUNs).
EMC Configuration Guidelines
One EMC interface port connects to one OS 2200 host channel adapter using a SCSI
channel. Only in a SCSI environment can an interface port support multiple targets.
The configuration recommendation below is based on multiple targets per interface
port.
Most sites have multiple SCSI channel connections between the server and the EMC
system. It is recommended that the logical disks be configured with access to the
OS 2200 host through all the SCSI channels.
Typically, for each SCSI channel, the EMC disks (LUNs) are placed on the first target
until it is filled (16 LUNs). Then the second target is filled, and so on, until all the disks
have been assigned to that channel.
Each target has a unique address on that channel. The first target has address 0 and
the next target has address 1, and so on. The allowed addresses are 0 to 6 and 8 to 15.
Address 7 is reserved for the OS 2200 host channel adapter.
2–32 3839 6586–010

Channel Configurations
The assignment of disks and targets is repeated for each SCSI channel on the EMC
system. The disk names and target values are the same on every channel. The number
of targets for the entire EMC system is equal to the number of targets on a channel
multiplied by the number of channels.
SCMS II Configuration Guidelines
The OS 2200 logical control units equate to, and are paired with, a target on the EMC
physical system. Each control unit has only one channel connection.
The logical control unit names are unique across the entire EMC system.
Configure one OS 2200 subsystem for every target on the channel. Assign the control
units with the same control unit address from all the channels, along with their
associated logical disks, to the same subsystem. Each subsystem should have up to
16 disks, along with a control unit from every SCSI channel. Each control unit on the
subsystem points to the same set of disks.
Usually, more than 16 disks are on a channel, which means there is more than one
subsystem. In this case the channel is daisy chained.
The subsystem for all disks is UNIVERSAL-DISK-SUBSYSTEM.
Example Application
For this example, there are
• 80 logical disks (3-GB logical disks)
• Six EMC interface ports
Five targets are required for each SCSI channel (80 ÷ 16).
All 80 disks should be configured in the Symmetrix BIN file and SCMS II so they are
accessible from all six OS 2200 channels. This example requires 30 logical control
units (6 channels x 5 targets per channel).
Configure one logical subsystem for every target value. The example has five targets
per channel, so there are five logical subsystems. Assign all the control units with the
same address and the same disks to the subsystem.
The following figure is a representation of one subsystem of the example. It contains
16 disks and all 16 logical disks shown can be accessed from the six channels.
If the configuration were complete, a separate set of 16 disks would access a
separate set of six control units. Each control unit would access one of the channels
shown. This would be repeated until all 80 disks are included.
3839 6586–010 2–33

Channel Configurations
The actual configuration is described in the table following the figure.
Figure 2–19. SCSI Disk Configuration Example (Only 16 of the 80 Disks Shown)
The following table shows how the 80 disks of this example are assigned. The table
shows five subsystems. Each subsystem has six control units. All the control units
access the same 16 disks. These subsystems are daisy-chained on each channel.
Table 2–12. Control-Unit-Based Disk Channels and Addresses
Channel Control Unit
Target
Address Disks
LUN
Address Subsystem
I00C00 CUD00A 0 DSK00–DSK0F 0–15 SS0
CUD01A 1 DSK10–DSK1F 0–15 SS1
CUD02A 2 DSK20–DSK2F 0–15 SS2
CUD03A 3 DSK30–DSK3F 0–15 SS3
CUD04A 4 DSK40–DSK4F 0–15 SS4
I20C10 CUD00B 0 DSK00–DSK0F 0–15 SS0
CUD01B 1 DSK10–DSK1F 0–15 SS1
CUD02B 2 DSK20–DSK2F 0–15 SS2
CUD03B 3 DSK30–DSK3F 0–15 SS3
CUD04B 4 DSK40–DSK4F 0–15 SS4
I10C00 CUD00C 0 DSK00–DSK0F 0–15 SS0
CUD01C 1 DSK10–DSK1F 0–15 SS1
CUD02C 2 DSK20–DSK2F 0–15 SS2
CUD03C 3 DSK30–DSK3F 0–15 SS3
CUD04C 4 DSK40–DSK4F 0–15 SS4
I30C10 CUD00D 0 DSK00–DSK0F 0–15 SS0
CUD01D 1 DSK10–DSK1F 0–15 SS1
CUD02D 2 DSK20–DSK2F 0–15 SS2
2–34 3839 6586–010

Channel Configurations
Table 2–12. Control-Unit-Based Disk Channels and Addresses
Channel Control Unit
Target
Address Disks
LUN
Address Subsystem
CUD03D 3 DSK30–DSK3F 0–15 SS3
CUD04D 4 DSK40–DSK4F 0–15 SS4
I40C00 CUD00E 0 DSK00–DSK0F 0–15 SS0
CUD01E 1 DSK10–DSK1F 0–15 SS1
CUD02E 2 DSK20–DSK2F 0–15 SS2
CUD03E 3 DSK30–DSK3F 0–15 SS3
CUD04E 4 DSK40–DSK4F 0–15 SS4
I60C00 CUD00F 0 DSK00–DSK0F 0–15 SS0
2.3. SBCON
CUD01F 1 DSK10–DSK1F 0–15 SS1
CUD02F 2 DSK20–DSK2F 0–15 SS2
CUD03F 3 DSK30–DSK3F 0–15 SS3
CUD04F 4 DSK40–DSK4F 0–15 SS4
The following configuration information applies to the single-byte command code set
connection (SBCON) and the SBCON channel that connects to the SIOP, the PCI-based
IOP. There are no differences in how they are handled or configured.
The SBCON channel, when used with channel director switches in multi-host
environments, can connect any host to any SBCON subsystem.
One SBCON channel is located on the board. The single port can connect to a single
control unit or to a single director port. The channel protocol is compatible with the
ANSI SBCON channel protocol.
The T9840A and T9840B have one port. Each port can connect to a host channel. The
models have a dedicated control unit for the tape drive. The models can be used, with
directors, to access multiple hosts. The tape drive can only be controlled or accessed
though one channel or one host at the same time. The control unit can be up at more
than one host, but only one host can access the drive at the same time.
See 8.3 for SBCON cabling information.
3839 6586–010 2–35

Channel Configurations
Directors and Direct Connect
The transmission medium for the SBCON interface is called a link. A link is a point-topoint
pair of fiber-optic conductors that physically interconnect the following pairs:
• A channel and a control unit
• A channel and a dynamic switch
• A control unit and a dynamic switch
• In some cases, two dynamic switches
The paths between channels and control units can be either static or dynamic.
• Static connection (direct connect)
Two units can only communicate with each other. For OS 2200, this is a single
tape drive connected on a single SBCON channel.
• Dynamic connection (through directors)
Two units communicate for brief intervals and then release the connection path.
The dynamic switch for links between channels and control units is called a director.
An SBCON director is a collection of ports and a switching array that can interconnect
pairs of ports within the director. Only one control unit is allowed to communicate
with a channel, but multiple different control unit and channel pairs can simultaneously
communicate.
A director can be configured such that one host can talk to multiple devices across a
single channel. It can also be configured such that multiple hosts can access the same
tape drive (but not at the same time).
The SBCON fiber connections from the host as well as the tape devices plug into
ports on the director. Each port has an address (hex), shown on the port into which it
plugs.
The director has a configuration matrix tool that enables you to identify which host
channels can communicate with which devices.
The SBCON protocol allows port addresses to range from 2 to FF. Different director
models offer different numbers of allowable connections. The most common model
allows for port addresses C0 to CF. The Unisys SBCON director is an IBM-ESCONcompliant
director.
2.3.1. SCMS II Configuration Guidelines
There is one control unit per tape device.
For direct connect, the control unit address is always 1. For director-connected
devices, the control unit address is the decimal value of the port address (hex) of the
tape drive.
The port address of the SBCON connection between the OS 2200 host and the
director is not configured in SCMS II. An SBCON director is invisible to SCMS II.
2–36 3839 6586–010

Each tape controller must be in a unique OS 2200 series subsystem.
Channel Configurations
SCMS II allows up to eight channels connected to a tape drive. However, any one
partition can only have up to four connections configured.
Different tape drive types, assuming they support SBCON, can run on the same
channel.
Example Configuration
• Three CTS5236 tape drives, each with two ports (A and B).
• Two SBCON directors, each connecting to all three tape drives.
• Two hosts, each host having two channels for redundancy.
Figure 2–20. Tapes Using SBCON Directors
The following are the SCMS II configurations for both hosts.
Table 2–13. SCMS II Configuration for SBCON
Host Channel Control Unit Tape Device
CU Address
(Decimal)
Port Address
(Hex)
H1 I00C00 TS52A TS52A0 200 C8
TS52B TS52B0 204 CC
TS52C TS52C0 205 CD
H1 I20C00 TS52A TS52A0 200 C8
TS52B TS52B0 204 CC
TS52C TS52C0 205 CD
H2 I10C00 TS52A TS52A0 200 C8
TS52B TS52B0 204 CC
TS52C TS52C0 205 CD
3839 6586–010 2–37

Channel Configurations
Table 2–13. SCMS II Configuration for SBCON
Host Channel Control Unit Tape Device
CU Address
(Decimal)
Port Address
(Hex)
H2 I30C00 TS52A TS52A0 200 C8
2.3.2. Directors
Host 1
TS52B TS52B0 204 CC
TS52C TS52C0 205 CD
Subsystems Control Units Tapes
S1 TS52A TS52A0
S2 TS52B TS52B0
S3 TS52C TS52C0
Host 2
Subsystems Control Units Tapes
S1 TS52A TS52A0
S2 TS52B TS52B0
S3 TS52C TS52C0
SBCON channels used in conjunction with dynamic switching on SBCON directors
offer the opportunity to load balance a pool of SBCON channels against up to 16
SBCON channel adapters.
SBCON channel pools should be directed at groups of similar devices. You should
configure a set of channels to support tape and another pool to support disk.
Operational Considerations
Many sites have a farm of SBCON tape drives that are interconnected by SBCON
directors. Typically, some are dedicated to different hosts depending on the workload.
(Tape systems cannot be shared at the same time by different hosts.) As the workload
mix changes, for example, end-of-the-month processing, tape drives can be
reassigned from one host to another.
These tape drives can be easily reassigned because they are configured with the
same names on different hosts. You can down or up the tape drives, depending on
what host controls the tape drive.
2–38 3839 6586–010

Resiliency and Connectivity
When planning the SBCON connectivity, remember the following general
recommendations:
Channel Configurations
• Configure at least two SBCON directors to maintain a high availability of control
units.
• Configure every host to every director to assure full connectivity and sharing of
control units across all the hosts. This connectivity might not always be desirable
for reasons of data security if your environment restricts such configurations.
• Configure each control unit to connect to multiple directors to assure high
availability. If one of the directors fails, the host can still access the control unit.
• Reserve some port attachment capability on each director for growth and
conversion. The number of ports required is equal to the total number of control
unit connections plus the total number of host channels plus an allowance for
growth.
Sharing Control Units Across Host Systems
Setting up connectivity through an SBCON director to allow multiple hosts to share
control units can be straightforward. The following figure shows a simple
configuration with one host and one director. Host B and two control units are added
to illustrate a multiple-host environment and are given access to Host A control units
through the director.
Figure 2–21. Configuring Two Hosts Through One Director
To improve the availability of the control units of both hosts, add another director (see
the following figure). Assume that the applications on Host A use control units 1 and 2
(through either director). If necessary, Host A can also access control units 3 and 4 for
backup or for sharing. Similarly, assume that Host B uses control units 3 and 4. If
necessary, Host B can also access control units 1 and 2.
3839 6586–010 2–39

Channel Configurations
Control of Connectivity
Figure 2–22. Configuring Two Hosts Through Two Directors
Directors initially enable any port on that director to dynamically connect with any
other port on the same director. At some point, the connectivity attributes of the
director might need to change. The following are the levels of control that you can put
in place. These levels result in a hierarchy, referred to as the connectivity attribute
hierarchy.
• Blocking all communication through a port (assign the block attribute)
• Establishing dedicated connections between two ports (assign the connect
attribute)
• Prohibiting dynamic connections with other specified ports (assign the prohibit
attribute)
Blocking All Communication
Dynamic connection cannot be established to a blocked port. A dedicated connection
with a blocked port remains in effect, but information transfer through the dedicated
connection is not possible.
You can block a port for several reasons. For example, you can block a port to
suppress link error reporting until a client engineer completes repairs on whatever is
causing the errors. Then, you can unblock the port.
As many ports as necessary can be blocked. However, at least one unblocked port
must remain connected to a channel to enable communication to occur with a host.
2–40 3839 6586–010

Establishing Dedicated Connections
Channel Configurations
A dedicated connection is a direct path between two ports that restricts those ports
from exchanging information with any other ports. Dedicated connections are required
to support chained directors. As many dedicated connections as necessary can be
created.
Prohibiting Dynamic Connections
You can prohibit two ports from dynamically connecting to each other without
affecting their ability to connect with other ports on the same director. For example,
you might want to prevent dynamic connections from occurring between a port
supporting a test system and a port supporting a production system.
Each port can be prohibited from connecting to another single port or multiple ports of
a director. You can prohibit communication between as many pairs of ports as
necessary.
A dedicated connection is not the same as prohibiting all but one connection to a port.
Dynamic connections and dedicated connections transfer data differently. Dedicated
connections exist primarily to support chained directors.
Increased Distances
The distance from a host to control units can be extended by chaining two SBCON
directors with a dedicated connection through at least one of the switches. Chained
switches require a physical connection (through a fiber-optic cable) from a port on one
director to a port on another director. Chained switching must meet the following
criteria:
• One or both directors must provide a dedicated connection.
• A path cannot pass through more than two directors.
Chained directors are illustrated in the following figure. The dedicated connection on
Director A is between ports C1 and C4.
3839 6586–010 2–41

Channel Configurations
2.4. FICON
Figure 2–23. Chained SBCON Directors
The configuration information in this section applies to the Fibre single-byte
connection (FICON) and the FICON channel.
2.4.1. FICON on SIOP
The PCIOP-E based Dorado 700, Dorado 4000, Dorado 4100 and Dorado 4200 Series
servers offer FICON channel support on SIOP.
The first release of FICON for the SIOP is supported on the following:
• SIOP firmware level
− 9.x.3 for Dorado 700
− 9.x.4 for Dorado 4000
When migrating from SIOPs with firmware levels earlier than 8.16.y (y=3 for
Dorado 700, y=4 for Dorado 4000), you must install an 8.16.y level first. This
installation upgrades the Board Service Package, which in turn allows
upgrading of the firmware to a larger firmware size (9.x.y level).
• Plateau level
− 1.0 for Dorado 4100
− 2.2 for Dorado 4000
− 2.1 for Dorado 700
• Exec levels
− ClearPath 12.0 plus PLE 18740982
− ClearPath 12.1
2–42 3839 6586–010

• EMC Centera and Celera firmware levels
Channel Configurations
− Information is not available at the time of publication but will be provided
when available.
FICON devices can be directly connected to an SIOP-resident FICON HBA. The
following device is supported on FICON channels (PCI-X Bus Bus-Tech FICON HBA):
• Bus-Tech Mainframe Data Library (MDL)
FICON on OS 2200 only supports tapes for the Mainframe Appliance for Storage
(MAS), Mainframe Data Library (MDL), or Virtual Tape Subsystem (VTS). No other tapes
are supported. FICON channel connections to disks are not supported.
MAS or MDL units should run at least on the following firmware level for setting up
FICON:
• Virtuent 6.0.43 for FICON channel interfaces.
• MAS S/W 5.01.46 for SBCON channel interfaces that are in a subsystem that also
has MAS or MDL units with FICON interfaces.
The following TeamQuest products are needed to support tapes configured to FICON
channels:
• TQ-BASELINE-7R4B.I1
• OSAM-7R3A.2
• PAR-9R1.I2
2.4.2. SCMS II Configuration Guidelines
The configuration guidelines and limitations for FICON channels are similar to the
configuration guidelines for Fibre SCSI channels.
Note: The virtual control unit number must be specified through SCMS when
configuring a virtual control unit.
Configuration Restrictions
The following configuration restrictions that existed previously are not applicable for
IOP microcode level 9.16.x (x=3 or 4):
• Only 32 total devices (LUNs) for each HBA are supported.
Device addresses might be sparsely allocated up to an address of 256, but no
more than 32 are allowed to be allocated for installed devices.
SCMS allows more than 32 device address configuration for each HBA. Device
addresses might be sparsely configured up to an address of 256. However, ensure
that no more than 32 unique devices are allowed to be or have been in the UP
status by the 2200 system. Any attempts to up more than 32 unique devices
results in a “Device Offline” error that is displayed on the 2200 console.
3839 6586–010 2–43

Channel Configurations
Therefore, it is highly recommended, at this time, to only configure 32 devices
(LUNs) for each channel. For example, you can configure 32 CUs with one LUN for
each CU or two CUs with 16 LUNs for each CU.
• The FICON HBAs may not reside in the same PCI bus with the SBCON HBAs.
This enables the FICON HBA to operate at the speed of the SBCON HBA. This is a
permanent guideline.
Note: This rule is generally applicable for all other HBA types
• FICON slot configurations for a 2200 system must be as follows:
Only one FICON HBA can be installed in each of the following physical slot groups
in the expansion rack to avoid unpredictable IOP problems:
− Group 1 – slot 1, 2, 3, and 4
− Group 2 – slot 5 and 6
− Group 3 – slot 7
Note: If you stand behind the I/O module, the slot numbers are assigned from
right to left.
Configuration Restriction for IOP Microcode Level 9.16.x or Higher
Only 64 total devices (LUNs) for each HBA are supported.
Device addresses might be sparsely allocated up to an address of 256, but no more
than 64 are allowed to be allocated for installed devices.
SCMS allows more than 64 device address configuration for each HBA. Device
addresses might be sparsely configured up to an address of 256. However, ensure
that no more than 64 unique devices are allowed to be or have been in the UP status
by the 2200 system. Any attempts to up more than 64 unique devices results in a
“Device Offline” error that is displayed on the 2200 console. Therefore, it is highly
recommended, at this time, to only configure 64 devices (LUNs) for each channel. For
example, you can configure 64 CUs with one LUN for each CU or two CUs with 32
LUNs for each CU.
FICON-Capable IOP Microcode and FICON HBA Installation Procedure
The following are the recommended installation steps that must be followed for
Dorado 700, 4000, 4100, and 4200:
1. If at IOP microcode level 8.15.x or lower, install IOP microcode 8.16.x.
2. Load a Plateau that supports FICON on the system.
3. If not done already, boot Exec level with FICON supported PCRs.
4. Load FICON supported IOP microcode, 9.x.x.
5. Take the system down and install PTN with FICON channel configured.
6. Install FICON HBA (see note 2 below).
7. Boot system.
2–44 3839 6586–010

Notes:
Channel Configurations
1. If this procedure is not followed, it will not be possible to up the IOP and it may
be disabled in a manner that it must be returned to Manufacturing.
2. Firmware level shown on the HBA LED should always be 1.xxx. If the level is
4.xxx, the IOP should be downed and upped to reinitialize the firmware in the
HBA. Any other level means the firmware was not correctly loaded at the
factory or the HBA has failed during the operation so it should be returned to
Unisys for replacement.
FICON Target Address
FICON uses a 24-bit fibre link address, which is the same as Fibre Channel SCSI
(FCSCSI). The Exec and SCMS, however, support a 32-bit target address (Interface
Number) for FICON channels. FICON channels assume the full functionality of the
support in Exec for 24-bit port SAN address on a fabric switch connected to an SIOP.
The Exec view of the FICON address is a 32 bit value described in Table 2–15, broken
down into two major fields. The first field is an 8-bit Virtual Control Unit Image Number
(CUIN) which is only meaningful in this form to the SCMS, Exec, and the IOP. The IOP
transforms the CUIN appended to a standards-based 24-bit fabric address consisting
of Domain, Area, and AL_PA by creating the correct packet that allows it to address
the Control Unit within the subsystem correctly. The fabric address is the only part
that is seen by intervening switches, as the CUIN is embedded in a subordinate
structure for transmission over the fabric. This is described in Table 2–16.
Table 2–14. FICON 32-bit Target Address Fields
Bits 31-24 Bits 23-16 Bits 15-08 Bits 07-00
Virtual CUIN Domain Area AL_PA
Tables 2–16 and 2–17 show the FICON target addressing format for real and virtual
tapes.
Table 2–15. FICON target address for direct-connected real tapes –
point to point.
Domain
(Bits 23-16)
Area
(Bits 15-08)
AL_PA
(Bits 07-00)
00 00 Same as FCSCSI
3839 6586–010 2–45

Channel Configurations
Table 2–16. FICON target address for direct-connected virtual tapes –
point to point.
CUIN
(Bits 31-24)
00-255
(00-15 for MAS)
Domain
(Bits 23-16)
Area
(Bits 15-08)
AL_PA
(Bits 07-00)
00 00 Same as FCSCSI
Table 2–17. FICON target address for switch-connected real tapes –
switched point to point or Cascade FICON switches.
Domain
(Bits 23-16)
Area
(Bits 15-08)
AL_PA
(Bits 07-00)
00-255 00-255 Same as FCSCSI
Table 2–18. FICON target address for switch-connected virtual tapes –
switched point to point or Cascade FICON switches.
CUIN
(Bits 31-24)
00-255
(00-15 for MAS)
Domain
(Bits 23-16)
2.4.3. Switch Configuration Guidelines
Area
(Bits 15-08)
AL_PA
(Bits 07-00)
00-255 00-255 Same as FCSCSI
The configuration guidelines for FICON switches are similar to the configuration
guidelines for Fibre switches.
Notes:
• The switch that should be configured must support FICON channels.
• Only FICON-capable Brocade switches qualified by Unisys that are available at
the time of publication are supported.
• Brocade switches used in a FICON SAN must be at least at code level 5.2.1B.
2–46 3839 6586–010

Section 3
Mass Storage
The OS 2200 I/O architecture was created some 40 years ago, based on the hardware
technology of that time. The architecture is still in use today but the technology has
changed.
Today, disk technology for OS 2200 consists of
• Control-unit-based disk systems
EMC Symmetrix and CLARiiON represent the storage devices most OS 2200
enterprise-class applications, with EMC Symmetrix being by far the most
common.
• JBOD (Just a Bunch of Disks)
These are individual disks that do not have the enterprise attributes of Symmetrix
or CLARiiON systems but can work well in a development environment.
3.1. EMC Systems
3.1.1. Disk
Below is a description of common OS 2200 architecture terms compared to current
popular hardware, EMC systems.
EMC systems manage large physical disks. These disks typically range in capacity
from 36 GB to well over 200 GB. The Symmetrix systems can partition the physical
disks into logical disks called hypervolumes, which appear to OS 2200 as physical
disks. Typically, a logical OS 2200 disk is between 3 GB and 9 GB, but can be larger.
3.1.2. Control Unit
A control unit is connected to the host by a channel. It interprets host commands,
controls the disk, and returns status to the host. OS 2200 architecture assumes there
is a control unit that interfaces between the host and one or more storage devices.
Control units can have multiple channel connections to the host and multiple control
units can access a particular disk.
Each control unit has a unique address for each channel connecting to the OS 2200
host. When the architecture was first developed, the control unit was a physical
device separate from the storage unit.
3839 6586–010 3–1

Mass Storage
EMC Symmetrix systems do not have a separate control unit to manage the disks. The
control unit functionality is done in the Channel Director and Disk Director. Similarly,
JBOD disks have a control unit built into the disk cabinet. There is no separate device,
but the functionality of the control unit is separate from the functionality of the disk.
3.1.3. Channel
3.1.4. Path
A channel is a high-speed link connecting a host and one or more control units. OS
2200 assumes that there is no direct connection to a storage device; the channel
connects to a control unit and the control unit attaches to the disk or disks. OS 2200
enables more than one channel to attach to a single control unit. If more than one
control unit is attached to a single channel, it is known as daisy chaining.
A path is a logical connection between the OS 2200 host and the control unit. It is used
to determine the route for an I/O to run through the I/O complex. The OS 2200
architecture assumes a path can go through components such as IOPs, channel
modules, channel adapters, subchannels, and control units.
OS 2200 is not aware of all the components that can be in the path, such as Fibre
Channel switches, SBCON directors, channel extenders or protocol converters.
Each path is unique. For example, a control unit with two host channels has two paths.
3.1.5. Subsystem
An OS 2200 logical disk subsystem is a set of logical disks and control units. It is all the
devices that can be addressed by a single control unit plus all the other control units
that can access those devices. All control units see the same set of disks.
All the channels connected to all the control units in the logical subsystem must be the
same channel type (SCSI or Fibre). Channels are not considered part of a subsystem.
The term “subsystem” has historically also been used to describe hardware
peripherals. EMC uses the term “system” to describe their disk family. Subsystem,
when used in this document, refers only to the OS 2200 definition.
3–2 3839 6586–010

Figure 3–1. OS 2200 Architecture Subsystem
OS 2200 has the following subsystem capacity limits:
• Up to 16 control units per logical subsystem
• Up to 512 devices per logical subsystem (depending on the channel type)
Other OS 2200 I/O configuration information includes
• Up to four channels per control unit
Mass Storage
• Logical volumes of up to 67 GB each; however, the EMC Symmetrix firmware
limitation is 15.2 GB for Symmetrix systems other than the DMX series (the DMX
limitation is 30 GB).
• OS 2200 system limitation of 4094 devices
3.1.6. Daisy-Chained Control Units
When control units share a channel, they are daisy-chaining on the channel. Most tape
devices have their own control unit. A SCSI disk subsystem is usually daisy-chained
across multiple channels. JBODs are usually daisy-chained on a single channel.
The following figure shows two SCSI JBOD disk drives daisy-chained on a single
channel. There are two subsystems; each disk and its control unit is a separate
subsystem.
3839 6586–010 3–3

Mass Storage
Figure 3–2. Daisy-Chained JBOD Disks
3.2. OS 2200 I/O Algorithms
The following information describes how OS 2200 algorithms handle disk I/O.
3.2.1. Not Always First In, First Out
The operating system is free to choose any of the queued requests for a disk device
as the next to be issued; it does not have to use the algorithm of first-in, first-out. OS
2200 can rearrange the order of I/O requests based on priority. For example, a realtime
program I/O request is selected before a batch program I/O request.
Modifying the order of I/O requests does not cause problems for application data
integrity. Order is preserved within an application program (and the database
managers) by issuing synchronous I/O requests where the application does not issue
its next I/O until it is notified that the previous I/O is complete. No two synchronous
I/O requests from the same activity can be in process at the same time. Therefore, all
I/O requests that are in process must be from different activities (or are issued as
asynchronous requests by the same activity, in which case the program does not care
about order). Since all requests that are active at a particular moment are
asynchronous with regard to each other, the operating system is free to process them
in any order it chooses.
3–4 3839 6586–010

3.2.2. Disk Queuing (Not Using I/O Command Queuing)
Mass Storage
The following queuing information applies to those disk systems that do not work
with I/O Command Queuing (IOCQ).
OS 2200 algorithms treat each logical disk unit as a separate addressable entity. The
operating system maintains a software device queue for every disk device configured
in the system. The operating system considers a logical disk unit as either busy or idle.
Upon issuing a request to a device, the device is marked busy and remains so until I/O
completion status is received. Additional requests arriving for a busy device are
queued in the OS 2200 host. When the I/O completion status is received for the
outstanding I/O, a queued I/O for that device is selected (if a queue for that device
already exists).
The following figure shows a typical case:
Figure 3–3. I/O Request Servicing Without IOCQ
In this example, three I/O requests arrive at about the same time with R1 being the
first. All three requests are accessing the same logical disk. Without IOCQ, R2 and R3
must wait until R1 is complete.
R1 is a read request. The data is not in cache (cache miss) so the data must be read
from disk. Reading from disk is significantly longer than a cache hit. A disk read
typically takes 2 to 6 ms while a cache hit is less than 1 ms. (The units of time in the
example above are just relative values, not necessarily milliseconds.)
R2 and R3 are both cache hits (can be reads or writes). Even though the data is already
in cache (read hit) or can be written to cache, they must wait until the earlier arriving
requests are complete.
For more information on disk queuing, see 3.5.
3839 6586–010 3–5

Mass Storage
3.2.3. I/O Command Queuing
Functionality
Most sites do I/O-intensive transaction processing. Therefore, the performance of disk
I/O is of great importance.
I/O Command Queuing (IOCQ) can greatly improve disk performance. IOCQ enables
multiple I/Os to be performed on the same logical disk at the same time. This can
reduce the amount of queuing and the length of time needed to complete I/Os, which
reduces the I/O existence time and, potentially, overall transaction existence time.
Most sites have configurations that have multiple channels accessing a subsystem of
disks. The physical disks are split into logical disk volumes, typically from 3 GB to 9 GB
per logical disk.
With IOCQ, OS 2200 does not queue I/Os that are for the same disk. Those I/Os are
issued and the EMC microcode determines if any queuing is needed. If the request
can be satisfied in cache (cache hit), then the I/O is performed. If an earlier I/O is
accessing the physical disk (cache miss) and a subsequent I/O also must access that
physical disk, then the subsequent one is queued until the earlier I/O completes.
IOCQ enables multiple I/O requests to be processed simultaneously to a single logical
disk volume. Without IOCQ, I/O requests can be queued in OS 2200 (see 3.2.2). With
IOCQ, there is no queuing in OS 2200. The I/Os are sent to the disk system and any
queuing is done by the disk system.
The effect of IOCQ is shown in the following figure.
Figure 3–4. The Effect of IOCQ
In Figure 3–4, three I/O requests arrive exactly as they did in the previous example. R1,
the cache miss, is processed first and takes a relatively long time to complete. R2 and
R3 are initiated as soon as they arrive. Since they are both cache hits, they complete
rapidly.
3–6 3839 6586–010

Performance
Enabling IOCQ
Mass Storage
With IOCQ, cache hits can complete faster. The amount of improvement depends
upon the cache-hit rate; a higher hit rate gives greater benefits.
Sites that have disks that generate many cache misses see little benefit. Only one disk
access can be active at any one time, any subsequent miss must remain queued until
the active one completes. For example, a FAS SAVE tends to read data from the disk
in a sequential manner. There is less chance of the I/O request being satisfied in
cache.
However, with disk systems using speculative read algorithms and large amounts of
cache, the I/O request can still be satisfied in cache.
IOCQ is enabled differently depending on the hardware platform. In addition, there are
certain criteria for the disk systems and the configuration.
• For the Dorado 400, 4000, 4100, and 4200 Series, all qualifying disk systems
automatically use IOCQ (see conditions that follow).
• For earlier Dorado platforms, IOCQ works for any system partition that contains
one or more PCI-based I/O processors (SCIOP). IOCQ also works on any
compatible channel I/O processors (CSIOP) in that same system partition.
• IOCQ is available separately for CSIOP-only Dorado system partitions as a CER
request, and can be obtained through Unisys Technical Consulting Services.
IOCQ is enabled under the following conditions. All conditions must be met:
• ClearPath OS 2200 Release 9.2, 10.1, or higher.
• The subsystem must be an EMC Symmetrix or DMX model.
• The EMC functional microcode level must be 5668.xx.yy or higher and include
Symmetrix 6 (DMX-1 and DMX-2) models, but exclude Symmetrix 4.8 and earlier
models.
• All logical controllers in the subsystem must be configured as single-port
(single-path) in the partition in which they exist.
• Fibre Channel connections supported only.
Additional IOCQ Information
IOCQ allows one I/O active to the same logical disk for every channel that can access
that disk.
Up to 8 channels can be configured; therefore, up to 8 I/O can be active.
In a multihost environment, up to 32 (4 x 8) can be active, but only 8 from any one
host.
3839 6586–010 3–7

Mass Storage
IOCQ can cause some I/Os to complete earlier than they did before, in some cases a
later arriving I/O completes before an earlier I/O. Changes in I/O order completion do
not affect application data integrity.
Some applications that do Read-Before-Write I/O might not be able to take advantage
of IOCQ. If a second Read-Before-Write is received that wants to access the same
record that is being accessed by the first, then the second one must wait. However,
I/Os that are not Read-Before-Writes that come in at the same time can still take
advantage of IOCQ.
IOCQ works independently of other I/O features. You do not need to change anything
if you are using the following features:
• Multi-Host File Sharing
• XPC and XPC-L
• Unit Duplexing
• Tapes
Because only one tape I/O can be active at any one time, IOCQ does not affect
tape usage.
3.2.4. Multiple Active I/Os on a Channel
A channel can have multiple I/Os active.
An I/O is made up of the following components:
• Command
• Data transfer
• Status
There can be periods of idle time between the completion of one component of the
I/O and the start of another. It is during these idle times that the channel can accept
another command, move data for a prior transfer, or return any pending status.
The duration of an idle period within an I/O can be quite lengthy: for example, on a
read miss after the controller receives the command, it must pause while it fetches
the data from the physical disk. The controller disconnects from the host channel and
becomes idle for the duration.
The following figure is an example of the time required to complete one I/O. The idle
time is when the channel is waiting for something to do.
Figure 3–5. Time for One I/O
3–8 3839 6586–010

Mass Storage
The following figure is an example of a channel doing multiple I/Os. The figure only
represents two I/Os (however, a channel can work on more I/Os simultaneously).
Figure 3–6. Time for Multiple I/Os
3.2.5. Standard I/O Timeout Processing
A timeout condition occurs when there is no status received in response to an I/O
command within a specified time period. A timeout is the absence of any status.
The standard timing duration for any given hardware low-level I/O is stated as from 6
to 12 seconds (modifiable by keyins). What actually happens is a sweep occurring
every 6 seconds. On each sweep each active I/O has its timeout counter decremented
by one. If the counter for any active I/O goes to zero, a timeout condition is declared
for that I/O. For most devices the initial timeout counter is set to 2. Therefore, I/Os
started just before a sweep timeout in just over 6 seconds; I/Os started just after a
sweep timeout in just less than 12 seconds.
An application I/O can be retried on multiple paths (channels) to the target device, and
depending on what the exact problem is, each of these can also time out. Therefore,
the total time out duration of a high-level user I/O might be N * (6 to 12) seconds,
where N is the number of data paths. This means that, for a two-path device, it can be
12 to 24 seconds, and a four-path device it can be 24 to 48 seconds.
3.2.6. Multiple Control Units per Subsystem
Multiple channels accessing a disk subsystem can give a higher throughput than a
single channel to the disk subsystem. You should configure one control unit for each
channel. Multiple control units can be working on the same subsystem of disks at the
same time. While any one disk can have only one I/O active at any one time, as long as
there are enough disks with I/O to do, more work can be done with multiple control
units (channels).
When choosing a path for an I/O, the operating system selects the least busy path.
The order in which the paths are searched is determined by the path information
generated when the Partition Profile (SCMS II) is built. The search order cannot be
changed dynamically. If all the paths are busy, it selects the path that has the fewest
incomplete requests outstanding. If multiple paths are at the same level, it is the first
path in a list it has created.
In the following figure, I/O can be active on all four paths at the same time. If one path
fails, three paths are still doing I/O. If another path fails, two paths are doing I/O.
3839 6586–010 3–9

Mass Storage
Figure 3–7. Single-Channel Control Units (CU)
3.2.7. Multiple Channels per Control Unit
OS 2200 prevents multiple channels on one control unit from being active at the same
time by selecting one of the controller’s paths as the preferred path for an extended
period (11 minutes) and not letting the other paths become active. The term
“preferred” is misleading; the designated path is mandatory. When the time period
expires, a new preferred path is selected. This algorithm for selecting new paths
ensures that all paths get used and any latent problems in a hardware component in
the paths are detected early and the component can be removed and repaired.
Since a control unit has only one channel active at a time, multiple channels to a
control unit do not increase performance. Multiple channels enable increased
redundancy; if one channel fails, a second one is available to take over data transfers.
In the following figure, two channels can be active (one per control unit). If one
channel fails, the other channel can take over. However, only two channels for the
entire disk subsystem can be active at the same time.
3–10 3839 6586–010

Figure 3–8. Multiple Channel Control Units
3.2.8. Configuring Symmetrix Systems in SCMS II
Mass Storage
Most OS 2200 platforms access a Symmetrix system by using multiple channels.
The recommended configuration is to have a control unit for every channel, as
discussed in 3.2.6.
Having four channels each with one control unit has twice the throughput capacity of
four channels and two control units; there is also an increase in reliability:
• In the case of four channels, each with its own control unit
− If one channel fails, three paths are active.
− If another channel fails, two paths are active.
• In the case of four channels, with two channels per control unit
− If one channel fails, two paths are active.
− If another channel fails, one or two paths could be active. If both failing
channels are on the same control unit, then the only access is through the
other control unit and that can have only one path active.
Configuring Symmetrix systems with a control unit for each channel offers increased
performance as well as increased reliability compared to configuring fewer control
units with multiple channels on each control unit.
3839 6586–010 3–11

Mass Storage
3.3. OS 2200 Miscellaneous Characteristics
The following are OS 2200 characteristics for mass storage.
3.3.1. Formatting
Word
Mass storage addressing evolved from drums and FASTRANDs. Early magnetic drums
were word addressable, whereas the FASTRAND subsystems were addressed by
sector.
The word is a basic unit of addressing in OS 2200 Series systems. A word is a
contiguous set of 36 bits that begins on a 36-bit boundary. The 36 bits are derived
from the hardware convention of four bytes, each composed of eight data bits and
one parity bit.
Word-Addressable Format
Mass storage can be accessed in units of single words. The old storage drums (no
longer supported) could actually read single words, but OS 2200 simulates it for all
current devices. Word-addressable files are files that are capable of being accessed in
units of single words.
Modern mass storage reads and writes data in blocks or records. When data is read in
something smaller than a record, the computer must read the record and extract the
desired data. When data is written on an off-record boundary (a partial write), the
associated records must first be read, then modified, and then written out to storage.
This is referred to as “read-before-write.”
FASTRAND Format
Mass storage space is allocated in granules of tracks or positions as denoted on an
@ASG run control statement. This came to be known as FASTRAND-formatted mass
storage, or mass storage that is accessible in units of 28 words (one sector).
1 sector = 28 words
1 track = 64 sectors (1792 words)
1 position = 64 tracks
This form of addressing could be on actual FASTRAND hardware or any storage device
that simulates this format. Over time the term “FASTRAND” became known as the
format of storage, rather than the physical device.
3–12 3839 6586–010

3.3.2. 504 Bytes per Sector
Mass Storage
All user and OS 2200 data is written out to disk as 504 bytes per sector independent
of channel type. The 504-byte value comes from the old sector value used for
FASTRAND (28 words). The OS 2200 architecture is mapped to the SCSI standard by
putting four 28-word sectors into a SCSI sector. Two 36-bit words equal nine 8-bit
bytes; therefore, 112 words equal 504 bytes.
Disks today are SCSI-based with a sector of 512 bytes. The 504 bytes of user data
come from memory in the same way for all channels. SCSI and Fibre Channels are
based on the same protocol: SCSI. The IOP adds 8 bytes of zeros, known as pad/strip,
to get a 512-byte sector.
The difference in sector sizes affects some configurations:
• OS 2200 Unit Duplexed disks must be of the same channel protocol. Channels can
access a subsystem of UD disks or SCSI and Fibre Channels can access them.
• OS 2200 Multi-Host File Sharing (MHFS) configurations require that all hosts use
the same channel type to access a shared device. See below for more
information.
3.3.3. Multi-Host File Sharing
Multi-Host File Sharing (MHFS) is the ability of multiple host systems to simultaneously
access data residing on the same mass storage subsystems. This access enables
multiple hosts to simultaneously operate on a single common set of data.
Hardware connections from each host to the shared mass storage subsystem provide
the physical access to the shared mass storage. All hosts use the same channel type
to access a shared device.
The MHFS feature supports the XPC-L as the only MHFS interhost communication
method. The XPC-L manages the locks for all hosts and passes MHFS coordination and
control information amongst the hosts. All hosts connect to the XPC-L.
EMC DMX and Symmetrix disk systems support MHFS. No other disk systems
support it. All hosts accessing a shared system must be of the same channel type.
For more information on MHFS see the ClearPath Enterprise Servers Multi-Host File
Sharing (MHFS) Planning, Installation, and Operations Guide (7830 7469).
3839 6586–010 3–13

Mass Storage
3.4. EMC Hardware
Connectivity
Data Flow
Below is a simple overview of EMC Symmetrix hardware. The information is geared
towards what it means to OS 2200. It does not describe differences between different
Symmetrix families or describe CLARiiON hardware. Since most OS 2200 customers
have Symmetrix systems, and at this level of description the differences between
Symmetrix and CLARiiON are not important, the information below assumes
Symmetrix systems. For more detailed hardware information, go to www.emc.com/.
EMC Symmetrix systems can contain multiple OS 2200 subsystems. They can connect
to multiple OS 2200 hosts as well as to other systems.
Some Symmetrix families support multiple channel types: Fibre, SCSI, or SBCON. For
those that support multiple channel types, the Symmetrix system can access the host
or hosts with more than one channel type connection; however, any one OS 2200
subsystem must be of the same channel type.
On a write
Figure 3–9. EMC Symmetrix Data Flow
• The Channel Director writes the data to cache and sends an acknowledgement
back to the OS 2200 host.
• The Disk Director writes the data to the disk.
3–14 3839 6586–010

On a read
Mass Storage
• If the data is in cache, the Channel Director transfers it to the OS 2200 host.
• If the data is not in cache, the Disk Director reads the data from disk and transfers
it to cache. When the data appears in cache, the Channel Director starts
transferring it to the OS 2200 host.
3.4.1. Components
The EMC Symmetrix systems contain several components.
Channel Directors
Cache
Channel Directors provide the connectivity to OS 2200 hosts and handle the I/O
requests. They contain intelligent microprocessors that support the proper channel
protocol and interface with the rest of the Symmetrix system. There are at least two
Channel Directors on every Symmetrix system.
Each Channel Director has multiple host connections, called Interface Ports. The
number of Interface Ports per Channel Director varies depending on channel type and
Symmetrix family member. There is no physically separate control unit; however, the
OS 2200 architecture requires one, so it is best to think of each Interface Port as a
control unit.
Cache memory provides transparent buffering of data between the host and the
physical disks. The amount of cache is variable. The more cache there is, the higher
the chance of a cache hit (finding the data already in cache).
Disk Directors
3.4.2. Disks
Disk Directors manage the interface to the physical disks and are responsible for data
movement between the disks and cache. Each Disk Director has multiple
microprocessors and paths to a single disk. There are multiple Disk Directors per
Symmetrix system.
Within Symmetrix systems, the physical disks are subdivided into multiple, smaller
logical hypervolumes. Each hypervolume appears as a disk to OS 2200.
For most sites with EMC Symmetrix disk systems, around 90 percent of I/O read
requests are from cache (100 percent of write requests are written to cache).
However, when I/O must be read from disk, the performance impact is significant
because the data from disk takes much longer than accessing it from cache.
The following information on disks is generic. It applies to all disks, not just EMC
products. The performance numbers are based on enterprise class disks. The values
are current as of this writing, but disk performance improves rapidly; the values might
be out of date by the time you read it.
3839 6586–010 3–15

Mass Storage
Data is stored on disk drives on platters and there are multiple platters per disk drive.
The platters are mounted on an axle, known as the spindle. The spindle is in the
center of the platters and the platters spin around the spindle, similar to phonograph
records.
Data is stored on the platter in tracks and sectors. Tracks are circles on each platter
and each track is divided into sectors. A sector is 512 bytes and is the smallest
addressable unit of a disk. The data is read from or written to the platters by
read/write heads. Since data is stored on both sides of the platter, there are two
heads for each platter: top and bottom. The heads, attached to an actuator arm, move
across the platter.
All the heads move across their platters in tandem. Each head is at the same relative
location of the platter at the same time. For example, if one head is at the outermost
track, all the heads are at the outermost track. Only one head can access data at any
point in time. A cylinder is made up of all the tracks that are positioned at the same
location across all the platters.
The following figure illustrates some key components of disks.
Figure 3–10. Disk Device Terminology
3–16 3839 6586–010

3.5. Disk Performance
Mass Storage
I/O system performance is a critical factor in determining the overall performance of
your system. This section gives an overview of I/O performance so that you might
have a better understanding when analyzing performance at your site.
I/O performance typically looks at Request Existence Time (RET), the time it takes
from when an I/O action is requested until it completes.
RET = QT + HST
The two major components of the RET are
• Queue Time (QT)
Length of time an I/O request must wait for the disk to be available to process the
request.
• Hardware Service Time (HST)
Length of time a disk takes to service the request.
HST is further broken down into two components:
− Access Time
Length of time it takes to locate the data in cache or to position the disk head
over the correct location on the disk.
− Transfer Time
Length of time to move the data from cache or disk to the OS 2200 host.
As the following figure shows, access time can also be broken down into smaller
components: channel setup time, seek time, latency time, and control unit delay time.
Figure 3–11. I/O Request Time Breakdown
3839 6586–010 3–17

Mass Storage
3.5.1. Definitions
• Server
A disk is a server that performs I/O operations. Only one I/O can be active to any
given disk. A disk is a single server.
• Service Time
The Service Time is the amount of time for the disk to service (process) an I/O
request. The time to service a request can vary, (for example, for a cache hit or for
a cache miss). Hardware Service Times (HST) are usually given in milliseconds, for
example, 2 ms.
• Queue
If an I/O request is made while the disk is servicing another I/O request, that
second request is queued until the first one completes. Any additional requests
are also queued. If the requests continue to come in faster than they can be
serviced then the queue is infinite or some other throttling mechanism
(bottleneck) occurs.
• Throughput
Throughput is the number of requests that a disk (server) performs in a given
amount of time. For example, a disk might do 300 I/Os per second.
Maximum throughput that a disk can perform can be calculated by dividing a unit
of time by the average service time. For example, if a disk has an average
hardware service time of 2 ms, then
Max Throughput = 1 sec / 0.002 sec = 500 I/Os per second
Most of the time, the maximum cannot be achieved. Even if it can be achieved,
you might not want to get too close. As you approach the maximum, your
response time very often becomes unacceptable.
• Utilization
Utilization is throughput divided by Max Throughput. For example, a disk
performing 300 I/Os per second with a capacity of 500 I/Os per second has a
utilization of 60 percent.
• Bandwidth
Bandwidth is a measure of the speed that a device/channel can transfer data and
is given in total bits per second. Maximum throughput is typically defined in terms
of requests per second, and based on average hardware service times. I/O packet
sizes are also factors in performance and the number of bits transmitted must be
considered.
• Response Time
Response Time is the total time to complete an I/O request. The time is
composed of the amount of time spent on the queue plus the time for the disk to
process the I/O.
In order to minimize response time
− The queue should be empty.
− The server should be idle.
3–18 3839 6586–010

Response time is related to throughput. In order to maximize throughput
− The queue should never be empty.
− The server should never be idle.
Mass Storage
Usually the goal is to minimize response time and maximize throughput.
Therefore, a balance must be struck between the queue depth and the server
utilization.
• TeamQuest PAR (Performance Analysis Routine)
The Unisys I/O performance tools display some of the above values. For more
information, see the latest documentation on PAR, Performance Analysis
Routines (PAR) End Use Reference Manual (7831 3137). The names that PAR uses
are shown on the left.
Request Execution Time (RET) = Response Time
Channel/Device Queue Time (Q) = Queue Time
Hardware Service Time (HST) = Service Time
Request Execution Time is composed of two components: Channel/Device Queue
Time and Hardware Service Time.
3.5.2. Queue Time
Queue Time occurs when OS 2200 has issued an I/O request but the request must
wait until the server is finished with an earlier request. The newly arriving request is
queued. The amount of queuing can greatly impact your overall system performance.
Hamburger Stand Analogy
Queue Time and the effects of queuing can be illustrated with a simple analogy: the
hamburger stand. If the hamburger stand server (the person behind the counter) can
prepare an order and deliver it to the customer before the next customer arrives, the
flow through the stand is smooth. The time to service a request is known as the
service time.
The wait time increases when a new customer arrives before the server is finished
with the current customer. The new customer must wait until the current customer’s
request is completed before the new customer can be served. This is the queue time.
If additional new customers enter, they must join the queue at the end and their queue
time is even longer. If the queue gets long, the stand begins to get crowded;
movement within the stand becomes more difficult, further slowing the flow. Those
stuck inside are not able to go on their way and complete their other tasks.
This hamburger stand is located in a small shopping mall and shares a resource (the
parking lot) with other businesses (services) in the mall. When the hamburger stand
gets overrun with customers, the parking lot becomes grid locked with the cars left by
those customers. Customers of the other businesses cannot get a parking place. The
other businesses start to suffer; they have plenty of capacity, but because of the
gridlock caused by the hamburger stand, they are blocked from serving their
customers.
3839 6586–010 3–19

Mass Storage
What has the hamburger stand analogy got to do with disk performance and ultimately
system performance? Inefficient processing of I/O requests can lead to a
bottlenecked system.
The following figure shows OS 2200 transactions accessing an application and doing
disk I/Os. If a bottleneck occurs at the disk (server), it can cause other locks and
queues to overflow and slow or hang the system.
3.5.3. Hardware Service Time
Access Time
Figure 3–12. Disk Queue Impact
The next major component of Request Existence Time is Hardware Service Time
(HST). HST is a value that you can see when looking at I/O trace data.
HST is broken down into two components: Access Time and Transfer Time. These
components are not visible when looking at I/O trace data, but need to be understood
when considering HST. Before HST is discussed in greater detail, Access and Transfer
Time are explained.
Access time is the time, once an I/O command is selected for processing, to initiate
the I/O command to the IOP and up to the point that data transfer is to begin. Access
time can vary. If the request can be satisfied by cache, the time is much less.
Access time is made up of the following components:
Access Time = Channel Setup + if disk access required:
Controller Overhead + Seek + Latency
Channel Setup Time
Channel setup is the time spent preparing the channel for a particular I/O command.
For example, the time it takes for the dialog between the OS 2200 host bus adaptor
and the EMC Channel Director.
The channel setup time for newer channel adaptors is small, under 0.5 ms.
If the I/O request is satisfied in cache, then no additional time is needed for the access
time.
3–20 3839 6586–010

Controller Overhead Time
Mass Storage
Controller overhead time is the time from when the command is given to the disk until
something starts happening. For example, this is the time for the dialog between the
Disk Director and the disk. The time is usually short, around 0.5 ms. Many times disk
manufacturers include this number in the seek times.
Seek Time
Seek time is the time needed for the actuator arm to move the read/write head from
its current location to a new location (track) on the platter. Seek times vary. For
example, movement from one track to the next sequential track is much faster than
movement from the innermost to the outermost track. Seek time is usually given as
an average: the value is commonly based on the time to move the heads across onethird
of the disk cylinders. An average seek time for a newer disk model can be 5 ms.
Average seek time given by disk manufacturers cannot be relevant when looking at
your particular disk layouts. Many sites have optimized file placements. If you are
reading consecutive tracks, your seek time is very low.
Latency Time
Transfer Time
Latency time is the time from when the proper track is located to when the head is
positioned over the proper sector. The time is variable. In the best case, the proper
sector is at the right spot when the seek is completed. In the worst case, the platter
has to complete almost a full revolution to get to the right sector.
Latency times are usually given as an average: the time to move halfway around the
cylinder. Latency times are determined by the speed of the rotation of the disk, given
in revolutions per minute (rpm): the higher the rpms, the lower the average latency.
The average latency time for a 15,000-rpm disk is 2 ms.
Average latency time given by disk manufacturers cannot be relevant for your site.
You might have good file placement; for example, your average I/O request might
have many sequential accesses. In this case, there is little head movement and
average latency for your site is less.
Access Time Varies
If data must be read from disk, the access time is quite variable. Using our example
above, access time can be as follows:
• Best case: around 1 ms
• Average case: 5 ms + 2 ms = 7 ms
• Worst case: 10 ms + 6 ms = 16 ms
Transfer time is the other component of Hardware Service Time. Transfer time varies
depending upon the amount of data being transferred. A 16-KB packet takes eight
times longer to transfer than a 2-KB packet.
3839 6586–010 3–21

Mass Storage
Transfer Rate
Transfer time is determined by the packet size and the transfer rate. The transfer of
data is over multiple interfaces and the slowest one determines the effective transfer
rate. For this level of discussion, there are three different interfaces involved: cache,
disk, and channel. Below is a description of the transfer rate for each interface on the
EMC Symmetrix system.
• Cache
The cache interface for EMC Symmetrix systems has multiple interfaces, each
with a bandwidth of hundreds of megabytes per second. The cache interface is
many times faster than the other two interfaces: the disk and the channel.
• Disk
The transfer rate for a disk varies depending on the transfer conditions. For
example, the rate for transferring data to or from an inner track is slower than
from an outer track. An outer track is longer than an inner track and has more
sectors (known as zone bit recording). More sectors per track means there is
more data per track. Since it takes the same amount of time to do one rotation
whether you are reading an inner or outer track, more data is transferred over the
same period of time to or from an outer track.
A common metric used by disk vendors is the sustained transfer rate. This is
based on a larger file, which includes time to move data off the platters as well as
the head and cylinder positioning time. Typical transfer speeds are given in ranges;
for example, 40 to 60 MB per second.
• Channel
The transfer rate varies with the channel type connected from the OS 2200 host to
the Symmetrix system. The fastest channel, Fibre – FCA66x, has a peak transfer
rate of 32 MB per second. (This is the peak for transfer ignoring any pauses or I/O
setup time. It is not a number that you see in your real world measurements.)
Transfer Time
The transfer time is determined by two factors:
• Transfer rate of the slowest interface
In most cases, it is the OS 2200 channel. In the previous example, the fastest and
newest Fibre Channel was used, which has a transfer rate of 32 MB per second.
• Packet size
It is a linear function. It takes two times as long to transfer a packet twice as big.
The following graph shows transfer times. It assumes a transfer rate of 32 MB per
second and variable packet sizes (measured in KB). You can see that the transfer time
is directly related to the packet size: as the packet size doubles, so does the transfer
time.
3–22 3839 6586–010

Hardware Service Time
Figure 3–13. Transfer Time
Mass Storage
Hardware Service Time (HST) is the time that the server (disk) takes to process an I/O
request, the time from the initial channel command until the OS 2200 application is
notified of the I/O being complete. It is the sum of the following components:
• Access time
The time required to initiate the hardware request and, if accessing the disk, to
position the heads for a data transfer.
• Transfer time
The time required to transfer the data between the cache or disk platter and the
OS 2200 host.
The Largest Component
For most I/Os at most sites, the access time is the largest component of Hardware
Service Time. The access time is zero for cache. In the figures below, channel set up
time and access time are combined and shown as access time.
An additional time component, not previously discussed, should also be considered
when looking at this example. A small value is needed for the instruction processing
time of the IOP; the IOP must execute some instructions in preparing to issue the I/O
request. A reasonable value is 100 microseconds. This value is added to the access
time in the figures below.
The access time for any message size is the same. For messages under 16 KB, the
access time is the majority of the total Hardware Service Time.
Some parameters in OS 2200 products are in words, some in tracks, and some in
bytes. The following table offers a translation.
3839 6586–010 3–23

Mass Storage
Table 3–1. Word-to-Kilobyte Translation
Tracks Words Kilobytes
1 1,792 8,064
2 3,584 16,128
4 7,168 32,256
8 14,336 64,512
16 28,672 129,024
Note: Kilobyte values represent user data. SCSI sector size is 512 bytes, but user
data is 504 bytes. 8,064 bytes of user data requires 16 sectors (8192 bytes).
Cache Misses Greatly Affect Average HST
For sites with EMC Symmetrix disk systems, most disk I/Os are satisfied in cache and
cache hits have a low HST. However, for those I/Os that are cache misses and require
a disk access, the HST can be much higher. A small percentage of cache misses can
greatly affect the average HST. The following figure shows the average HST based on
some percentage of cache misses. This figure assumes values used earlier in this
discussion (7000 microseconds is disk access time).
• Cache-hit HST = 710 microseconds (100 + 360 + 250)
• Cache-miss HST = 7710 microseconds (100 + 360 + 7000 + 250)
Figure 3–14. Hardware Service Time Affected by Cache-Hit Rate
3–24 3839 6586–010

3.5.4. Little’s Law
Mass Storage
In 1961, John Little developed Little’s Law that helps to understand queuing impacts.
Little’s Law states:
Mean number of tasks in a stable system = arrival rate X mean response time.
This discussion of queuing is based on assumptions of simplicity.
• There is a single server, one that accommodates one customer at a time. There is
a waiting line called a queue that is created when random requests arrive and wait
for the server to be available.
• Arrival rates vary, but over the long term, arrivals equal departures.
• The server can spend a variable amount of time servicing a request. However,
assume this is an exponential distribution. Most requests are serviced at close to
average, and the overall values are somewhat shorter than average. This
assumption greatly simplifies the formula (commonly done when doing
performance analysis). (For those exploring the actual formula [not shown here], C
= 1).
• Queuing occurs when, for a short duration, the arrival rate exceeds the service
time. (If the arrival rate is always greater than the service time, you have an
infinite queue, not something that computer systems like to handle.)
• Items placed on the queue are processed in FIFO fashion: first in, first out.
Figure 3–15. Requests Join a Queue
Little’s law allows some related formulas to be derived for queuing analysis:
R Average number of arriving requests per second
Ts Average time to service a request
U Server utilization (0..1): R = R x Ts
Tw Average time per request in waiting line: Tw = Ts x U / (1-U)
Tq Average time per request: Tq = Ts + Tw
Lw Average length of waiting line: Lw = R x Tw
Lq Average length of queue: Lq = R x Tq
3839 6586–010 3–25

Mass Storage
Notes:
• “Waiting line” is composed of the requests waiting for the server.
• “Queue” is the waiting line plus the request being processed by the server.
The following figure is a graph of response time increasing as the throughput
increases. The following assumptions are made:
• Average hardware service time (HST) is 2 milliseconds.
• Maximum throughput is 500 I/Os per second.
• Response Time = Queue-Time + HST.
Figure 3–16. Response Time
This graph is a common model for throughput and response. As the curve approaches
80 percent of maximum throughput, the response time increases rapidly. Since the
average HST is the same, the increase in response time is due to increased queuing.
Below is a different graph based on the same scenario shown above. This one shows
how the number of requests queued start to build as the percentage of maximum
throughput increases. As the throughput increases to 80 percent, the number of
queued requests grows rapidly. You can look at both graphs and see the relationship
between number of items on queue and response time.
3–26 3839 6586–010

3.5.5. Request Existence Time
Figure 3–17. Queue Sizes
Request Existence Time (RET) is the total time an I/O takes from the time it is
requested by the application until the completion status is returned.
RET = Queue Time + Hardware Service Time (HST)
RET is sometimes called Response Time.
Mass Storage
When looking at I/O traces, you see somewhat different names than described here.
The names on the right are the ones listed in the PAR runstreams.
RET = RET
Queue Time = Chan/Dev Q
HST = Hdw Svc
The values for access and transfer time are not displayed.
3.5.6. Disk Performance Analysis Tips
The TeamQuest product PAR reduces SIP IO Trace data and displays average I/O
times for devices. Roseville Engineers have looked at many traces over the years and
have developed some guidelines that might help you when looking at PAR output.
These are only generalizations and might not apply to your site.
Note: The terms used below are defined earlier in this section. If you are unsure of
the meaning, please review the definition and return to this section.
3839 6586–010 3–27

Mass Storage
Channel/Device Queue
The Channel/Device Queue Time should be no more than one-half of the Hardware
Service Time (HST). (Many times this value is zero, no queuing occurred.) As the total
number of I/Os to a device (throughput) increases, the Queue Time starts to rise. An
increase in Queue Time increases the individual response time. You want to keep the
throughput as high as is reasonable while keeping the response time as low as is
reasonable. Trying to get the Queue Time to be one-half of HST is a good balance
between response time and throughput. Here is an example: a Queue Time of
1 milliseconds is a reasonable number when the HST is 2 milliseconds.
When the Queue Time is about one-half the HST, it usually means that the I/O
utilization rate of the physical disks is around 35 percent of maximum throughput.
Sometimes a high Queue Time is normal. For example, a Database Save is a single
activity that reads files from disk and writes them to tape. The Database Save activity
has four asynchronous I/Os sequentially reading the file on disk. Potentially, there are
four outstanding disk reads and each one must wait for the preceding one to
complete. This results in the blocks having a normal, but seemingly long, queue time
of perhaps 8 to 20 milliseconds.
Hardware Service Time
Hardware Service Times for sites with EMC Symmetrix systems are typically around 2
to 3 milliseconds. However, times can vary from less than a millisecond to 8
milliseconds (newer platforms generally have lower HST values). These sites typically
have a cache-hit rate around 90 percent. The HST for some devices can be higher.
Sometimes it is normal and sometimes it is not.
• A high HST can be normal for files that have a poor cache hit rate. Files with
random access patterns cause a lot of disk access. Since a disk access takes
longer than a cache access, the average HST can be a higher value.
• A high HST is normal when very long I/O transfer sizes are being done. It takes
longer to move big blocks of data than small ones.
• A high HST can also be due to excessive queuing due to channel resources. If the
number of disk I/Os simultaneously being done is high enough to have a high
channel utilization rate, then the I/Os waiting for the channel are queued at the
EMC hardware level. OS 2200 is not aware of this queuing. It issued an I/O and
when the completion comes back it has a high HST. In this situation, adding more
channels can lower the HST.
Waterfall Effect
Usually, for a disk subsystem with multiple control units, the I/Os are not equally
balanced. Some paths do more I/O than the others. This is normal. It is the result of
the OS 2200 I/O algorithms. When looking at an I/O analysis, this can appear as a
“waterfall.” (A waterfall is when one path has done the most I/Os, the next path has
less, and so on.) If all paths show the same amount of I/Os, it might be that all paths
are saturated: 100 percent busy. (This is not a good sign but does not happen very
often at customer sites.)
3–28 3839 6586–010

Comparable I/O Transfers Have Comparable HSTs
Mass Storage
When looking at a trace, comparable I/O transfers (similar transfer size, channel
adaptor, disk system) usually have comparable HSTs. Typically, there is some variation
in the I/O pattern, but an HST that is multiple times higher than similar I/O transfers
can merit further investigation.
For example, file placement on the physical disk. You might be seeing “spindle
contention” within the Symmetrix system (more than one logical OS 2200 disk can be
on the same physical disk and two or more logical disks might have a lot of disk I/O
traffic). In this case, the disk heads of the physical disk would be moving back and
forth between different locations on the physical pack. The movement of the heads
(access time) greatly increases the HST. In this case, consider moving one or more of
the files to a less busy physical disk. Note that in today’s environment, multiple host
platforms can share an EMC system. The file that is in contention with the OS 2200 file
does not have to be an OS 2200 file; it can be one from another hardware platform.
(When it is a file on another platform, it makes the analysis of the OS 2200
performance more difficult.)
Analysis Runstream
You should use the following runstream to reduce I/OTRACE. Analysis of this trace can
be done on a device level with the summary section having the filenames for those
files accessed on that device. File activity summaries show which files have the
highest access rates.
Unisys Service
@par,e iotracefilename.
Iotsort ’device’
Iotrace ’summary ’, ’device ’, ’file ’
Exit
@eof
I/O analysis is difficult to do but can be done by experienced individuals. Unisys offers
a sold service for I/O analysis. Contact your TCS representative or email
Timothy.Nelson@Unisys.com.
3.6. Symmetrix Remote Data Facility (SRDF)
Considerations
Symmetrix Remote Data Facility (SRDF) is an EMC hardware and software feature that
provides for remote data mirroring. SRDF is a convenient and easy way to implement
automatic data transfer to a remote location. The primary motivation to create a
remote copy of data is to have a disaster backup solution. However, a backup solution
can affect performance at the primary sites.
The typical SRDF configuration has a Symmetrix system at the local (primary) site. The
system, also known as the source, is connected by remote links to another Symmetrix
system, known as the target at a remote site.
3839 6586–010 3–29

Mass Storage
As the primary host writes to the source, the updates are sent to the target through
the remote links. Read requests by the primary host are performed locally (source
Symmetrix). They are not sent to the remote site.
Figure 3–18. SRDF Modes
The remote links can be extended through a variety of technologies, including
dedicated optical fiber and various communication devices on leased lines.
Sites can specify the mode on a logical disk basis. SRDF supports the following modes
of operation:
• Synchronous
Has the greatest data reliability and simplest recovery at the remote site.
• Asynchronous
Eliminates the delay in I/O service times at the primary site and has a very simple
recovery process at the remote site, but it does have a small window of data loss.
• Adaptive copy
Used to set up a disaster recovery site (populating the remote database) but
should not be used for the disaster recovery site.
3.6.1. Synchronous Mode
Each write request is given an end-to-end acknowledgement prior to generating a
completion status at the host. This guarantees that the original application order of I/O
is maintained, in both the source and target Symmetrix.
The following is the sequence:
1. The source receives the write from the host and updates its local cache.
2. The source sends the write to the remote target.
3. The target updates its cache and returns an acknowledgement to the source.
4. The source returns completion status to the host.
3–30 3839 6586–010

Figure 3–19. Synchronous Mode
Mass Storage
The I/O packet sizes to the target are the same size as written to the source unless
the I/O size is greater than 32 KB, the size of a Symmetrix track. For I/Os greater than
32 KB, the I/Os are done in packets of 32 KB (the size of the last packet is the
remainder).
In the event of a disaster at the primary site and a restart at the backup site using the
target data, the recovered data is consistent from an application point of view. This is
critical to OS 2200 Integrated Recovery environments. A recovery at the remote site is
simple and straightforward, a simple recovery boot.
A potential problem with synchronous mode is performance. The average time to
process I/O increases because the primary host must wait until the I/O has been
acknowledged at the remote site and that status is returned to the primary site.
3.6.2. Asynchronous Mode
Asynchronous mode transfers discreet data sets on a cyclic timed basis, as
infrequently as once every 5 seconds. Data sets are collected in the source Symmetrix
cache for the duration of each cycle. If multiple updates occur to the same location,
only the latest update is retained in the data set. Each data set represents the state of
the updates in cache at a consistent point in time. At the point of a cycle switch, new
updates are captured in the new cache cycle while the prior closed cycle is
transferred to the target.
The target always has a valid complete cycle. When a new cycle is completely
received, it is transferred to the disks at the target. If a disaster (loss of the source)
should occur while a cycle is in transit, that cycle is invalid for recovery and the prior
complete cycle is used at the target. The maximum data loss upon restart is two
cycles.
Asynchronous Mode Compared to Synchronous Mode
An advantage of the asynchronous mode is that it has no impact on local performance
and requires less network traffic than synchronous mode. It also enables you to move
your remote site much farther away from your primary site than you can with
synchronous mode.
3839 6586–010 3–31

Mass Storage
A disadvantage is that some data is lost in asynchronous mode upon recovery (the
amount lost is determined by how you set up your configuration).
3.6.3. Adaptive Copy Mode
Adaptive copy mode is used primarily to initialize or load the target Symmetrix at the
remote site at the time it is installed. After the target Symmetrix is fully loaded, the
site can start up its SRDF mode of choice (Synchronous or Asynchronous). Adaptive
copy is also useful when combined with another EMC feature known as TimeFinder
(or BCV) to move large amounts of data in the shortest possible time and as a tool for
migrating data from one subsystem to another when a new Symmetrix unit is
installed.
Adaptive copy mode should not be used to provide real-time data backup at a remote
site. Adaptive copy mode moves large amounts of data rapidly to a remote site but
the order of transfer to the target is completely unpredictable. There is nothing that
can be counted on to be available or to be in order at the remote site in the event of a
disaster recovery.
Adaptive copy does I/O to the target Symmetrix in 32-KB packets, known as a
Symmetrix track. One Symmetrix track is equal to four OS 2200 tracks. Adaptive copy
maintains a list of changed tracks. It transfers tracks to the target at its convenience; it
does not always do it at the first instance of a track being updated.
3.6.4. SRDF Performance
There are additional factors that affect the potential performance of SRDF.
The internal “track” size used by Symmetrix is 32,768 bytes (64 x 512 blocks). This
translates to four OS 2200 tracks (7168 words). Within Symmetrix, cache is allocated in
32-KB segments. Also, the size of an individual SRDF link transmission is limited to
32 KB. This means that if the write size is greater than four OS 2200 tracks (32 KB) the
source breaks the transmission to the target into multiple discrete blocks. There are
one or more blocks of 32 KB. The last block is the remainder of the data.
Symmetrix supports multiple SRDF link connections between the source and target.
Symmetrix uses each link in parallel to achieve maximum data rates between the
source and the target. For those I/Os that are greater than four OS 2200 tracks and
must be broken up into multiple packets, the packets can be sent across multiple
links, in parallel, and reassembled at the target.
3–32 3839 6586–010

3.6.5. SRDF Synchronous Mode Time Delay Calculation
Mass Storage
Synchronous mode enables data to be stored at a remote site and to be easily
recovered at the remote site in the event of a disaster. However, this does not come
free in terms of performance. The primary host is forced to wait for a complete endto-end
acknowledgement before receiving completion status. This extends the
hardware service time for each write to a device.
The increase in time to complete the I/O is made up of the following components:
• Processing
There is a certain amount of time required for each I/O to initiate the transfer to
the target and then to acquire cache, do the update, and generate an
acknowledgement. The times are getting better because each new generation of
Symmetrix is faster than its predecessor. For estimation purposes, a value of 1 ms
per write (including the acknowledgment) is reasonable. This amount covers the
time spent in both the source and target.
• Networking
The time to move the data across the network is variable. This is the propagation
delay, also known as the flight time. Flight time has two very important
components: speed and capacity.
− Speed is fixed. It is the time required to propagate the first bit of a message
over the distance from the source to the target. The upper bound is limited by
the speed of light (186,000 miles per second) but factors such as switching
delay, amplifiers, repeaters and media resistance reduce the speed. An
accepted value is 120 miles (200 KM) per millisecond.
The 120 miles per millisecond is the upper bound and is usually the most
significant factor. Additional delays occur in the different boxes that handle
protocol. The times vary with each configuration and each site should consider
these additional delays when thinking about SRDF. However, for this
explanation, the additional delays are being ignored.
− The capacity, or bandwidth, of the line is how many bits can be sent through a
line in a period of time. A 100-Mb line can transmit 100 megabits a second. A 1-
GB line can transmit 1 gigabyte a second.
When given the distance, knowing the speed enables you to calculate how long it
takes for the first bit to arrive at the destination. When given the block size, knowing
the bandwidth enables you to calculate how much additional time is needed for the
last bit to be received at the destination.
3839 6586–010 3–33

Mass Storage
Example
A primary site has a disaster backup site 60 miles away. SRDF is doing remote I/Os of
8 KB. (Most OLTP applications have average I/Os of 2 KB.) A 100-MB line links the
sites.
Delays due to distance: The first bit arrives at the remote host in 0.5 ms. After the
packet is received, an acknowledgement must be sent back, which adds another 0.5
ms.
Time delay = 1 ms.
Delays due to packet size: The time needed to transmit 64,000 bits on a 100,000,000bit
line is calculated as
64,000 / 100,000,000 = 0.0064 seconds = 0.64 ms.
Increase in Hardware Service Time: 1 ms + 0.64 ms = 1.64 ms.
Each site has a different situation. There are different distances, different packet sizes,
and different bandwidths for the remote links. In addition, each site has to evaluate the
impact of the propagation delay on the hardware service time for I/O.
3–34 3839 6586–010

Section 4
Tapes
This section is an overview of tapes for ClearPath platforms, including
• Characteristics
• Performance
• Ways to enhance application usage
4.1. 36-Track Tapes
Performance
36-track tape technology started in the early 1990s, popularized by the IBM model
3490E. This format not only had twice the number of tracks on the 1/2-inch tape, but
the tape could be written and read in both directions. The odd tracks are read or
written in one direction; the even tracks go in the other direction.
Figure 4–1. 36-Track Tape
The 3490E model was compatible with previous models. However, the 3490E
supported compression while the previous models did not.
The 3490E tape model was released on different drives and with different tape
lengths over time. There were three models from IBM. The table below gives
performance characteristics. The Enhanced model shows multiple values for Speed at
the Head. Multiple tape drives supported the 3490E model and the newer ones were
faster.
3839 6586–010 4–1

Tapes
Table 4–1. 36-Track Model Performance Metrics
36-Track
(3490E) Standard Enhanced Quad
Density 76,000 BPI 76,000 BPI 76,000 BPI
Tape Length 550 feet 1100 feet 2200 feet
Capacity (native) 0.4 GB 0.8 GB 1.6 GB
Speed at the Head 3 MB per second 3 to 6 MB per second 6 MB per second
The rewind time of a 36-track tape was potentially much better than an 18-track tape.
A full 18-track tape had to be rewound entirely. A full 36-track tape did not need to be
rewound. It already was back at its starting point. This was a great improvement when
writing large amounts of data to tape.
Note: See 8.1 for a 36-track SCSI tape operating consideration.
4.2. T9840 and 9940 Tape Families
In 1999, the T9840 tape technology was released for OS 2200 systems. From
StorageTek, this represented a significant advancement in tape technology from the
earlier 18-track and 36-track tapes.
4.2.1. T9840 Family
The 9840 tape media is not compatible with the 18-track and 36-track tapes. The 9840
cannot read or write 18-track or 36-track tapes and 18-track or 36-track tape drives
cannot read or write 9840 tapes.
Over the years, updated versions of the 9840 were released. They have differences
but are all considered part of the 9840 family. All the family members have 288 tracks
and most have a density of 125,000 bpi (the 9840C has a density of 162,000 bpi).
The 9840 was renamed the 9840A to show that all the tapes were part of the family.
The members are
• 9840A
Original member of family
• 7840A
Repackaged 9840A
• 9840B
Faster transfer rate than 9840A or 7840A
• 9840C
Higher transfer rate than 9840B and larger capacity
Writes at a higher density
4–2 3839 6586–010

• 9840D
Almost twice the capacity of the 9840C
Writes 576 tracks on a tape
Tapes
Some performance values are in Table 4–2. (These are values achievable by the drives
themselves. Other system factors can reduce the actual number.)
Model
4.2.2. T9940B
Table 4–2. Performance Values for the T9840 Family of Tapes
Style
Uncompressed
Capacity (GB)
Maximum Transfer Rate
(MB per second) - Uncompressed
7840A CTS7840 20 10
9840A CTS9840 20 10
9840B CTB9840 20 19
9840C CTC9840 40 30
9840D CTD9840 75 30
In 2003, another tape drive from StorageTek was released for OS 2200 systems, the
T9940B.
The 9940B is not compatible with any member of the 9840 family. The tape cartridges
are different. The 9940 drive can only read or write 9940 tapes.
StorageTek released multiple members of the 9940 family, as they did with the 9840
family. However, OS 2200 only supports the 9940B.
The 9940B has 576 tracks and an uncompressed capacity of 200 GB. It has a
maximum transfer rate of 30 MB per second (uncompressed).
4.2.3. T10000A
The T10000A was released in 2008.
The T10000A is not compatible with any member of the 9840 family. The tape
cartridges are different. The T10000A drive can only read or write T10000A tapes.
The T10000A has 768 tracks and an uncompressed capacity of 500 GB. It has an
uncompressed transfer capacity of 120 MB per second.
3839 6586–010 4–3

Tapes
4.2.4. T9840/9940 Performance Advantages
The T9840 and 9940 are technologies that have advantages over previous tapes
(18-track and 36-track). The following are the advantages from which you can benefit:
• Increased capacity
Fewer tapes to manage
• Data protection
Backup times are reduced
• Data restoration
Recovery times are improved
The T9840s and 9940s are the best choice for these operations.
Note: Below are some performance comparisons. The values are intentionally
vague. The purpose of the numbers is to show that the newer technology is better,
but that each site sees a different level of performance gain. Adding a new
peripheral that is ten times faster than the old peripheral does not mean that you
see a ten times performance improvement. Other factors affect system
performance and they can impact the performance gains seen at the system level.
Increased Capacity
The T9840 tape family can store more data than 18-track or 36-track tapes. More data
on a single tape media can result in significant operations savings.
It can take 25 36-track tapes or 100 18-track tapes to store as much data as a single
9840 tape.
• Tapes must be stored or archived onsite. This costs money in both storage and
handling. How much can be saved by having 90 to 99 percent fewer tapes?
• A cartridge tape library (CTL) is a significant investment. How much easier is it to
justify a CTL if you can store 25 to 100 times more data in each CTL?
Data Protection
Your site probably has time set aside for backing up files, and there is always
increasing pressure to reduce this backup window. The T9840 family can help in the
following ways:
• The T9840 family can write out data to tape two to six times faster than 18-track
or 36-track tapes.
• The T9840 family, because of its much higher capacity, reduces the number of
tape swaps needed when backing up data. How long does it take your site to do a
single tape swap? One minute? Figure out the reduction in the number of tape
swaps and estimate the improvement this gives to backup times.
4–4 3839 6586–010

Data Restoration
Tapes
Possibly the most important factor at your site is the time it takes to restore data after
a major failure: restoring files and reloading data.
A feature available with the T9840s is Fast Tape Access (FTA), sometimes called
Locate Block. It can greatly speed up data restoration.
Earlier tape technology required that the tape be read until the proper file or record
was found.
Fast Tape Access enables the T9840 tapes to capture the tape address where files
are stored. This address can be saved and used during recovery to issue a tape
command to rapidly position the tape at the start of the file or record.
Recovery times (the portion attributable to tape access and locate) are 3 to100 times
faster when using the T8940 tapes and FTA feature.
4.2.5. Operating Considerations
The following are operating considerations for the T9840 tape systems:
Booting, Dumping, and Auditing
T9840 tape subsystems are supported as boot devices, system dump devices, tape
audit trails, and for checkpoint/restart. However, if you do tape audits to the larger
capacity drive, 9840C, there are some recovery situations that can take longer than
you can accept. See Section 7, “Peripheral Systems,” and read the information on the
appropriate tape drive to learn more.
Handling Tapes
Do not degauss T9840 tapes. Servo tracks are written on the tape at the factory.
When these tracks are erased, the tape cartridge becomes unusable.
If you drop a cartridge from a height of less than one meter, the cartridge is warranted
to continue to read and write new data, but the media life might be shortened. You
should copy the data from a dropped tape to a new tape and throw away the dropped
cartridge.
Read Backwards
Read backward I/O functions are not supported. If you attempt to read backward, it is
terminated with an I/O error status of 024 (octal).
3839 6586–010 4–5

Tapes
SORT/MERGE
ROLOUT
Prior to the introduction of 9840 tapes, SORT/MERGE defaulted to assign scratch files
based on the capacity of the tape. Now, the SORT processor assumes that the last
tape volume associated with each input file assigned to a tape device contains 2 GB.
See the OS 2200 SORT/MERGE Programming Guide (7831 0687) documentation to
learn how to override the defaults.
The larger capacity tapes can make ROLOUT more effective. You should do periodic
saves to increase the number of files that can be unloaded without dynamically
creating a ROLOUT tape. This has the following advantages:
• Fills the tapes during the periodic saves
• Reduces output tapes for ROLOUT
There can be relatively little data being rolled out, which can result in a
considerable amount of unused tape.
• Greatly speeds up ROLOUT
A current backup already exists and the needed mass storage space is
immediately freed without waiting for tape assigns, mounts, and writes.
• Moves these tape operations to a noncritical time of the day
FAS writes a copy of the master file directory (MFD) to a separate volume for
performance and protection reasons. Based on the client application environment, it is
possible that production can immediately resume after the MFD is restored while FAS
does file reloads in the background.
4.3. T9x40 Hardware Capabilities
The T9840 tape family and the T9940B (together designated as T9x40) have a much
faster performance and higher capacity than the earlier 18-track or 36-track tape
families. The T9x40 tapes can improve the tape operations at your site, but you might
not be getting the full benefits without configuration and operations changes to your
system utilities and user applications. The purpose of this section is to identify those
potential changes.
This section describes the features of the T9x40 family and how to use them for best
performance, but does not cover the system aspect of number of devices per
channel, number of channels, number of IOPs, and so on.
4.3.1. Serpentine Recording
The T9x40 can record 288 tracks on the 1/2-inch tape. Each tape drive has a read/write
head that has 16 elements: each element can read or write one bit. The tape head
writes 16 bits at a time in one direction, reaches the end of the tape, and then starts
reading/writing in the other direction. The tape head can make 18 passes over the 1/2inch
tape. This gives a total of 288 tracks (16 x 18). Not all the tracks are for user data.
Some are used for error checking.
4–6 3839 6586–010

Tapes
This type of head movement is called serpentine recording. The following figure
illustrates a good way to visualize the head movement over the tape (even though the
actual placement of bits and the head movement is more complex than shown). The
tape starts at Pass 1, moves the entire length of the tape, starts Pass 2 in the other
direction, and so on.
Figure 4–2. Helical Scan
The T9x40 automatically loads at the midpoint of the tape, essentially halving the
search time during restore operations. Before unloading, the T9x40 repositions the
tape to its midpoint location for future use.
Figure 4–3. 288-Track Tape
The serpentine design means that the average access time for a file on a T9840B is 12
seconds. This is much faster than 18-track or 36-track tapes where the tape must be
read from the beginning until the proper file is found (the time to read a 36-track tape
can be a minute or more).
4.3.2. Compression
Compression is a procedure that inputs 8-bit data bytes and outputs a bit stream
representing data in compressed form. Incoming data is compared to earlier data;
compression results from finding sequential matches. The T9x40 uses an
implementation based on the Lempel-Ziv 1 (LZ1) class of data compression algorithms.
Compression and decompression are done at the control unit. The uncompressed data
is sent from the OS 2200 host across the channel and presented to the control unit.
The control unit compresses the data and it is then written to the tape. The process is
reversed for reading data from tape.
3839 6586–010 4–7

Tapes
Most customers run with compression turned on. In most cases, this gives
approximately a 2 to 1 reduction in the amount of media used for compressed versus
uncompressed data. A 2:1 compression means that twice as much data can be stored
on a tape. Compression varies from file to file and each site sees different
compression ratios. You might see up to a 3 to 1 benefit or even no benefit (1 to 1
ratio).
Since the work of doing the compression and decompression is done at the tape
control unit, compression does not use any processing power of the OS 2200 host.
However, it does enable more data to be transferred across the channel. For example,
the T9840B can support a transfer rate to the tape of 19 MB per second. With no
compression, the host could support that transfer rate by sending data at 19 MB per
second. With compression on and assuming 2:1 compression, the host would have to
send data at 38 MB per second to support the speed of the tape.
When looking at tape drive specifications, you usually see two values: one for
uncompressed and one for compressed (the compressed value is higher). The number
is the transfer rate at which the control unit can receive data from the host.
4.3.3. Super Blocks
Data is written to (or read from) tape in blocks. Each block is typically written in a
single operation with the tape running continuously during the write.
Between each physical block on the tape is a blank space, also called an inter-block
gap (IBG). For the T9x40, the IBG is less than 1/4 of an inch (2 mm). The gap enables
the drive to prepare for the read or write of the next block.
User programs or applications do I/O to the tape in blocks, but these blocks are almost
always not the actual blocks written to tape. The T9x40 can combine multiple user
blocks into a super block and write out the super block to the tape. Writing out super
blocks has the following advantages:
• Usually results in a higher overall transfer rate
• Decreases the number of IBGs
This makes more space available for data.
The largest block that can be written to the T9x40 is 256 KB (approximately 57,000
words or 32 tracks).
4.3.4. Data Buffer
Before the data is written to the tape, user blocks are written to a buffer in the tape
controller. All members of the T9x40 have a buffer. The buffer size varies.
The following are the buffer sizes for the T9x40:
• T9840A = 16 MB
• T9840C = 64 MB
• T9940B = 64 MB
4–8 3839 6586–010

Tapes
For most I/O requests, acknowledgement is immediate: the I/O returns control to the
application when the data is in the buffer. The user is unaware that the data has not
been written to tape.
The buffer stores user blocks until some condition or command forces a write of the
data to the tape. For example
• The device determines there is enough data to write to tape.
• The user I/O command forces the data to be written to tape immediately (“Do not
return control until the data is on tape.”).
4.3.5. Streaming Tapes
All T9x40 are streaming tapes.
• The tape runs continuously as long as data is available to be written to the tape.
• The tape does not slow down.
The drives can accept data and write it to tape up to the speed the medium moves
and the density at which bits are packed.
The tape gets data from the buffer that potentially has many blocks ready to transfer.
Having a large number of blocks available means that the tape can stream until there
are no more blocks. To keep the tape streaming, input to the tape buffer should be
about the same speed (or higher) as needed by the tape. There are always some slight
speed-ups or slow-downs between the host and the tape drive so having a buffer of
multiple blocks minimizes the chance that slight speed bumps affect the streaming of
the tape.
The tape cannot always be fed at its optimum speed. The following are some possible
reasons:
• The application might not send data fast enough.
• The channel or disks might limit the throughput.
• The host might issue I/O commands that force the buffered data to the tape and,
once written to tape, might result in the tape stopping because there is no data
ready to be written.
4.3.6. Tape Repositioning
If the tape cannot be fed data fast enough, it must stop and wait for additional data.
Modern tape technologies with high tape speeds do not operate well in stop/start
mode. Each stop and start operation (also called repositioning) requires the
mechanism to stop the tape and wait for additional data. When the data is available,
the tape drive must increase the speed again and resume writing. This start-stop
increases the wear and tear on the drive. This also causes the overall throughput rate
to drop.
3839 6586–010 4–9

Tapes
Repositioning of the tape drive takes a long time. During the repositioning, no data is
being written to the tape. If there are many repositions in a short amount of time, the
transfer rate dramatically slows, but this might not be noticeable to the user. The
following are measured tape repositioning times:
• T9840A = 0.4 seconds
• T9840B = 0.4 seconds
• T9840C = 1.2 seconds
• T9940B = 1.2 seconds
If the application is slow or the other hardware connections are causing the
bottleneck, the repositioning is not noticed. Even though the tape is repositioning and
cannot accept data, the data can be stored in the buffer. The buffer is most likely big
enough to store the incoming data until the repositioning is complete. Once the
repositioning is complete, the tape can stream for multiple blocks before emptying
out the buffer and doing another repositioning.
Any repositioning that does occur does not show up in any I/O analysis. The I/O
completion time is the time when the data is put into the buffer, not the time that the
data is put on tape.
However, tape repositioning can become a significant factor on tape performance if
very frequent tape marks occur forcing the tape buffers to empty to tape.
4.3.7. OS 2200 Logical Tape Blocks
Most sites write tapes using tape labeling that is based on the ANSI standard (X3.27).
Information (user and control) is written to the tape in blocks. (OS 2200 software
treats these as individual blocks on the tape, but the blocks might be packaged into
super blocks.) The main categories are
• Label blocks
These are 80 characters in length. Labels are used to keep security and file
structure information. There are several kinds of labels: volume label, file header
labels, file trailer labels, and so on.
• Data blocks
The user or application data. These can vary in size.
• Tape mark
A unique tape mark that separates files or volumes of data.
The example below shows a tape with two files on a labeled tape. There can be
variations in this structure, depending on your site parameters. It is not a complete
description of labeled tape formatting, just sufficient information to make it easier to
understand T9x40 tape technology. For more information on labeled tapes, see
Section 7, “Tape Labeling and Tape Management,” in the Exec System Software
Administration Reference Manual (7831 0323).
4–10 3839 6586–010

Example
Two EOFs in a row signify the end of the tape. See Figure 4–4.
Tapes
• For earlier tape drives, OS 2200 wrote two EOFs and then backed up the tape to
position it at the start of the second EOF. If the application did more writes to the
tape, the second EOF was overwritten.
• For the current release, OS 2200 only writes one EOF. When the file is closed, a
second EOF is written.
The frequency of tape marks can impact capacity and performance.
• Capacity
Tape marks take up space on a tape, space that could be used for storing data.
Writing smaller files to tape means that there are more tape marks on the tape,
which means that there is less space for storing data.
• Performance
See 4.3.8 for how tape marks impact performance.
Figure 4–4. File on a Labeled Tape
3839 6586–010 4–11

Tapes
4.3.8. Synchronization
Synchronization means that the data written by the user is actually on the tape. There
are I/O commands that force the flushing of the data buffer. Control is not returned to
the user until the data is successfully written to tape.
Writing Tape Marks forces synchronization. The data is actually written to the tape
upon successful completion of the Write-Tape-Mark I/O. Other I/O requests also
cause resynchronization, for example, Rewind or Locate-Block.
Each time synchronization is completed, it causes a tape repositioning. There is no
data left to write so the tape must slow down and stop.
The format for labeled tapes, as shown above, is three tape marks per file. (The format
for unlabeled tapes is one tape mark per file.) Each tape mark causes the tape to
synchronize and reposition.
The impact on overall throughput can be very significant for small files, (not so much
for very large files). Table 4–3 shows transfer rates for different size files to a labeled
tape. The table assumes a large number of files at the specified size.
Copying Files to Labeled Tapes (T9840B)
• Optimal Transfer Rate = 19 MB per second
• Repositioning Time per file (3 tape marks) = 2.4 seconds
Table 4–3. Transfer Rates for Labeled Tapes
File Size
Tracks MBs
Transfer Rate (MB per second)
10 0.08 0.03
100 0.8 0.3
1,000 8 3
10,000 80 12
100,000 800 17
If your site has many small files that are written to labeled tapes, this can be a
significant bottleneck.
OS 2200 has been enhanced to eliminate the impact of tape marks with Tape Mark
Buffering (two phases). The tapes still meet all ANSI standards and the enhancements
ensure that the data is written to tape correctly.
4–12 3839 6586–010

Tapes
Prior to the introduction of the Tape Mark Buffering feature, the hardware performed
the synchronization transparently to the software. Now, the software issues a
synchronization command. See 4.4.1 for more information.
4.3.9. Tape Block-ID
The T9x40 has the capability to know exactly where the head is on the tape. There are
“tachometer” marks all along the tape that create a unique address. Knowing the
address of a file or record enables OS 2200 applications to move very fast to that file
or record instead of having to search through the entire tape.
For example, assume that the tape is currently at block-ID 1234 and this is the start of
a file that is being written to tape. This address can be captured by an OS 2200
application (for example, IRU and FAS) by an Exec Request (ER) and saved. Later, if the
application wants to load that file from tape, the application can use the address and
do a Locate Block command to position the tape at the start of the file.
4.3.10. Tape Block Size
Tape performance can be looked at from two perspectives:
• Physical transfer of the super blocks to a tape
The tape technology generally hides this from the user.
• Block size written out by the application
In general, doing I/O of larger blocks results in a higher transfer rate (how fast data
can be transferred from the user program to the tape buffer). It is this
characteristic that gets noticed and the one that applications can control.
Other performance factors (channel speed, IOP speed, number of drives per channel)
are important but are not discussed here.
Block Size Written to Tape Buffer
The tape performance was measured based on block size. The measurements that
follow eliminate other bottlenecks and just look at the impact of block size.
• Data is transferred from memory, eliminating disks as a bottleneck.
• There is only one drive per channel.
• There were no tape marks, eliminating tape repositioning from software
commands.
The time to write data to the tape buffer is made up of two components:
• I/O set up time is the time it takes for the channel and controller to prepare to do
the I/O. The set up time is the same value no matter how much data is transferred.
• Transfer time is the time it takes to move the data to the tape buffer. It is directly
proportional to the size of the transfer. A transfer size that is twice as large takes
twice as long to transfer.
3839 6586–010 4–13

Tapes
The I/O set up time has a large effect on the overall time it takes to complete an I/O.
The I/O set up time has a greater impact on the effective rate, as the message sizes
get smaller. You can see this in the values for the T9840B shown below. As the size
of the blocks increased, the transfer rate increased because a smaller proportion of
the time was spent doing I/O set up.
Another thing to notice is that there is a limit to how fast data can be transferred. As
the maximum transfer rate for each device is approached, increasing the block size
has no effect on the transfer rate. The streaming tape cannot handle incoming data
any faster.
Figure 4–5. T9840A/B Write Performance
The values in Figure 4–5 are given as 8-KB blocks; one 8-KB block is equal to one
track. Parameters in OS 2200 products are sometimes given in words or tracks. The
following table offers a translation:
Table 4–4. Translation of Tracks to Words
Tracks Words Bytes
1 1,792 8,064
2 3,584 16,128
4 7,168 32,256
8 14,336 64,512
16 28,672 129,024
4–14 3839 6586–010

Table 4–4. Translation of Tracks to Words
Tracks Words Bytes
32 57,344 258,048
4.4. Optimizing T9x40 Tape Performance
Tapes
This section explains what has been implemented in the Exec and OS 2200 products
so that you can make use of the T9x40 performance features. It also discusses how
to turn on compression and how to increase block size.
The features that are the most valuable for most customers are Tape Mark Buffering
and Fast Tape Access.
4.4.1. Tape Mark Buffering
Phase 1
A Tape Mark forces a resynchronization: emptying of the tape buffer to tape. Once all
the data is on the tape, the tape must stop and reposition. The repositioning time is
quite long when comparing it to the speed of the tape (the T9840B can write out 15
MB in the time it takes to do a reposition). This repositioning time is most noticeable
when writing out small files.
The Exec and OS 2200 system software has been enhanced to buffer some or all of
the tape marks. Buffering means that the tape marks are written out to the tape
buffer but they do not force the tape buffer to be emptied (which forces a reposition).
This can greatly reduce the time it takes to back up your program files (FAS
runstreams) or to dump your database (IRU).
The Tape Mark Buffering enhancements have been delivered in two phases.
Phase 1 of Tape Mark Buffering (sometimes referred to as File Mark Buffering) was
released in ClearPath OS 2200 Release 6.1. Phase 1 helps the performance of labeled
tapes (three tape marks per file) but does not help the performance of unlabeled tapes
(one tape mark per file).
In Phase 1, the first two tape marks of a file are buffered (written to the tape buffer
without causing a synchronization).
Upon writing the third tape mark (after the EOF group), an FSAFE$ (File Safe) I/O
command is issued to the device. This forces the write of the data in the tape buffer
to tape. Return of status is delayed until all data has written from the buffer to the
tape. This command ensures that all the buffered data is written on the tape and the
tape is positioned correctly to receive the next data block.
3839 6586–010 4–15

Tapes
Phase 2
The following table shows the transfer rate based on file size for T9840B tapes. Two
columns for Transfer rate are shown: one for the transfer rate when processing three
tape marks per file (no enhancement) and one for the transfer rate when processing
one tape mark per file (Phase 1).
Copying Files to Labeled Tapes (T9840B)
• Potential Transfer Rate = 19 MB per second
• Repositioning Time per file:
− No enhancement = 2.4 seconds
− Phase 1 = 0.8 seconds
Table 4–5. Transfer Rate Based on File Size
File Size Transfer Rate (MB per second)
Tracks MB No Enhancement Phase 1
10 0.08 0.03 0.1
100 0.8 0.3 1
1,000 8 3 7
10,000 80 12 16
100,000 800 17 19
With the Phase 1 enhancement, labeled tapes have the same transfer time potential as
unlabeled tape (they both have one tape mark per file that causes repositioning).
Enhancements were made in the Exec, FURPUR, FAS, and IRU.
Phase 1 also increases the amount of data that can be stored on a tape compared to
no File Mark Buffering (FMB). However, writing lots of small files to a tape with FMB
Phase 1 reduces the amount of data that can be stored on a tape when compared to
its stated capacity.
The Phase 2 enhancement buffers all file marks on a tape and only issues an FSAFE$
I/O command when the reel is closed or swapped. Many files can be written to a tape
before the synchronization is done.
Phase 2 is not offered as a default system value, but might be invoked by using the
BUFTAP parameter on tape assign statements (see 4.4.2).
The potential performance bottleneck due to tape marks can now be eliminated.
Phase 2 offers significant performance gains beyond Phase 1 but more responsibility is
placed on applications such as FAS or user-written programs to recover from tape
errors.
4–16 3839 6586–010

Tapes
The added risk of Phase 2 is that an unrecoverable error on the tape results in a loss of
position and the tape has to be rewritten or the program that is writing it has to read
the tape to recover the position.
User programs that write small files to tape can improve performance significantly.
However, the user is responsible for saving the original data for possible error
recovery. The Exec does not provide any means for the user to recover this data. With
this capability, it is possible for a user program to be returned good status on writes
of hundreds of files, when actually none of the files have been written to tape. (The
files are still in the buffer.)
If an error occurs while they are being written to tape, the remaining blocks in the tape
subsystem might never be written. The new BLOCK-ID SAFE (BSAFE$) I/O function
enables a program to determine if a data/file mark from an earlier I/O write request
has been recorded on the tape without stopping the tape. It also enables a program to
determine if a data/file mark is on a physical tape after a tape error.
4.4.2. How to Use Tape Mark Buffering
The following are descriptions of how to use Tape Mark Buffering:
• Exec
You can specify the buffered option you want on ECL commands, such as @ASG.
There is also an Exec configuration value, TAPBUF, which defaults a choice if you
have not specified one in your ECL command.
− TAPBUF value of 0: do not buffer the first two file marks of each file (system
default)
− TAPBUF value of 1: buffer the first two file marks of each file
Set the value to 1 if you do not want to change your user runstreams to use the
enhancement. This defaults the buffered field on the ASG (or similar statements)
to BUFFIL.
Only set TAPBUF to 1 if all your tape drives support the capability. Units that
support buffered write are the T9x40 and the DLT family.
For more information about TAPBUF, see Section 6, Configuring Basic Attributes,
in the OS 2200 Exec System Software Installation and Configuration Guide (7830
7915).
• FAS @ASG Statements
The @ASG statement enables you to specify buffering, assuming the tape drive
supports it.
FAS Assign Example
@ASG, TNF OBACKUP1.,HIS98/////////CMPLON/BUFFIL,,,RING
In the example above, the field is specified as BUFFIL. The options are
− BUFOFF. No buffering of any data blocks. (Not an option for T9x40 tapes.)
3839 6586–010 4–17

Tapes
− BUFON. This is the default unless you have set the TAPBUF to 1. It forces a
tape resynchronization on each of the three file marks at the end of a file on a
labeled tape and one file mark on an unlabeled tape.
− BUFFIL. A tape resynchronization is only done once per file for labeled tapes.
− BUFTAP. No synchronization is done when the files are written out; it is only
done when the tape reel is closed or swapped. Do not use this unless you are
using FAS 9R2 (ClearPath OS 2200 Release 10.0) or later. The @ASG and @CAT
statements are rejected if there are no tape units up and available that support
BUFTAP. There is no configuration parameter for BUFTAP.
Buffered-write modes can also be specified on @CAT and @MODE ECL
statements.
For more information about @ASG, see Section 7 of the Executive Control
Language (ECL) and FURPUR Reference Manual (7830 7949) and Section 9 of the
OS 2200 File Administration System (FAS) Operations Guide (7830 7972).
• IRU
The parameter and recommended value, which buffers the first two tape marks, is
shown below.
TAPE-BUFFERING BUFFIL
This is only valid for tape drives that support tape buffering. Units that support
buffered write mode are the T9x40 and the DLT family.
IRU has no plans to implement support for buffering of the third tape mark. Many
files copied out by the IRU are large, so there is little gain for most sites.
• FURPUR and the W Option
The W option, on the @COPOUT, @COPY[,option], and @MARK statements that
write to tapes, reduces the impact of having to recover from tape errors for users
that want to copy to tapes that have been assigned with the BUFTAP option.
If the W option is included, FURPUR ensures that all buffered data has been
successfully written to the physical tape at the conclusion of output tape
operations and performs an FSAFE$ I/O function (synchronize) if necessary.
The synchronize function increases the time required to write the file. If the W
option were used on every file copied, it would have the same performance as if
the tape had been assigned with the BUFFIL option. To increase performance, the
W option can be used periodically to establish error recovery checkpoints. The W
option is ignored if the buffered-write mode is BUFOFF, BUFON, or BUFFIL.
For more information, see the OS 2200 Executive Control Language (ECL) and
FURPUR Reference Manual (7830 7949).
4.4.3. Fast Tape Access
If your site does database reloads and tape recoveries, you want to restore the data
and get back running as fast as possible. A big portion the time to restore data and
recover is finding the right location on the dump tapes or audit trail tapes.
4–18 3839 6586–010

Exec
IRU
Tapes
The Exec and IRU have been enhanced to capture the block-ID of where key
information is stored on tape. During the recovery process, instead of searching the
entire tape for that key location, the Exec or IRU can tell the T9x40 control unit to
position the tape to that spot. Because moving the tape to a specific location is much
faster than searching the tape, the recovery process is much faster.
FAS has also been enhanced to more quickly find files to reload.
The Exec feature, Improve Short/Medium Recovery Audit Performance, results in
shorter recovery times for cartridge tape and mass storage audit trails.
Information about the location of the Periodic Save audit records (PSRs) is used to
move quickly through an audit trail. Information about the last PSR is recovered from
the previous session and is available for use by the Exec and IRU Short and Medium
Recovery. Information about each prior PSR is contained in the Periodic Save audit
record.
The Fast Tape Access feature is always used for audit trails. This enhancement
enables the T9x40 family to be supported as an audit peripheral for IRU applications.
Privileges Required for Fast Tape Access
Special security privileges are required to use block-IDs for fast tape access. The
required privileges depend on the type of security that your site has configured.
For sites configured for Fundamental Security (Exec configuration parameter
SENTRY_CONTROL = FALSE), one of the following is required:
• The run uses the overhead account number.
• The run uses the security officer account number.
For sites configured for Security Option 1, 2 or 3 (Exec configuration parameter
SENTRY_CONTROL = TRUE), both of the following privileges are required:
• SSBHDR1RDCHK (bypass_tape_hdr1_read_checks)
• SSBYOBJREUSE (bypass_object_reuse)
The IRU has enhancements for both reloads and recoveries. The IRU refers to this
feature as Fast Tape Access or Use Locate Block. The recovery speed up is also called
Audit Trail Performance Improvement – Phase 2.
• All supported levels of IRU offer improved performance of RELOADs by saving the
location (block-ID) of the start of each file on a dump tape in the dump history file.
IRU uses this information during reload processing to position directly to a file
location on the dump tape. This is especially useful for long tapes where files
reside near the end of the tape.
3839 6586–010 4–19

Tapes
FAS
• IRU speeds up short, medium, and long QITEM recovery. IRU uses the Locate
Block feature to position the tape at the last periodic save record and database
recovery start point. The previous method of reading every audit block backwards
from the end to find the recovery start point has been eliminated.
The IRU defaults to automatically use the Locate Block feature. The IRU configuration
value is
USE-LOCATE-BLOCK TRUE
The configuration parameter USE-LOCATE-BLOCK is an ASSUME parameter.
See Section 7 in the Integrated Recovery Utility Administration Guide (7833 1576) for
more information.
FAS enables the block-IDs of files to be saved as they are written to output volumes.
When this file is to be retrieved from the tape, FAS does a Locate Block to position
the tape to the starting block of the file.
To enable this capability in your FAS runstream, insert the following (the default is NO):
SET FAST_TAPE_ACCESS:= YES
This command should be added in all FAS runstreams after the @FAS call and prior to
the ACT or END.
There are other considerations, such as security and access privileges, when enabling
this capability. For more information see Section 9 of the File Administration System
(FAS) Operations Guide (7830 7972).
4.4.4. Block Size
Exec
The size of the blocks written to tape affects performance. In general, writing larger
blocks results in a higher transfer rate.
For both tape and mass storage audits, the amount of audit trail information written to
tape has two dependencies:
• The block is full (size is configurable).
• A timer expires.
The size of the audit control tape buffer is configurable and is set on the audit trail
configuration statement:
TRANSFER MAXIMUM is X FOR TRAIL trail-ID,
where X is the size of the buffer in words.
4–20 3839 6586–010

Tapes
The recommended audit trail for T9x40s is the largest value with an audit buffer of 16
tracks.
Transfer Maximum is 28,672
The space used for the buffers does not cause any memory or addressing problems.
Make the buffer as big as possible for optimum I/O as well as making it better to
support the recommended TIMER value.
TIMER is an optional I/O delay mechanism used to balance audit throughput against
the size of the audit blocks written. Writing small blocks for either tape media or mass
storage is inefficient because setting the timer to nonzero creates larger audit blocks
by accumulating multiple audit requests in an audit buffer before initiating an I/O write.
In general, the greater the TIMER value, the larger the block sizes written. However,
throughput of audit writes depends on multiple variables, such as
• TIMER value
• Amount of buffer space
• Mix, size, and frequency of mandatory versus nonmandatory audit requests
• Media type I/O device speeds
The problem is determining the correct TIMER value. There are many
interdependencies and understanding all the variables is difficult.
The TIMER values are configured on the ATTRIBUTE TRAIL statement:
ATTRIBUTE TRAIL trail-ID PARAMETERS ARE: TIMER,value/value.
The recommended TIMER values are zero/zero.
TIMER,0/0
Exec audit control has two buffers. Audit data is written to one audit buffer. That audit
buffer is written to tape or mass storage when the buffer is full or a mandatory audit
command is received.
If the TIMER values are set to 0/0 and a mandatory audit is received, the current buffer
is written to tape. If no mandatory audits are received, the audits continue to be
stored in the buffer until the buffer is filled and then it is written to tape or mass
storage. All subsequent audits received while the first buffer is written, even
mandatory ones, are stored in the other buffer. When the I/O from the first buffer
completes, audit control checks for a mandatory audit (there can be more than one) in
the second buffer. If yes, then I/O is initiated on the second buffer and subsequent
audits are stored in the empty first buffer.
If the TIMER values are nonzero and a mandatory audit is received, the TIMER is
activated. The data buffer is written to tape or mass storage when the TIMER expires.
3839 6586–010 4–21

Tapes
IRU
The advantage of TIMER values of 0/0 is that the audit processing is not suspended
while buffers get written out. Audits continue to be stored in the audit buffer until the
I/O on the other buffer is complete. Configuring larger buffers ensures that the I/O on
one buffer completes before the second buffer is filled.
With TIMER values greater than 0/0, there is a possibility that I/Os are outstanding for
both buffers. If that happens, then all transactions using that audit trail are suspended.
This is a bad situation that is much less likely to happen when the TIMER values are
0/0.
Most of the time, and for most sites, the actual size of the audit buffers written to
tape or mass storage is small (frequent mandatory audits). However, there are times,
such as overnight batch processing, that mandatory audits are infrequent. The space
used by the audit buffers is not a problem. Make the buffer as big as possible to
reduce the chance that this can become a bottleneck.
TIMER values of 0/0 do not apply in all cases. You must make your decision based on
your site characteristics.
For more information about audit trail block sizes and TIMER values, see 12.4, “Audit
Trail Configuration Statements,” in the Exec System Software Installation and
Configuration Guide (7830 7915).
IRU assigns four buffers for database dumps. The IRU fills a buffer and then starts
filling another. A separate activity writes out the buffers to tape. If the mass storage
read is faster than the tape writes, then eventually all four buffers are filled and the
next read of mass storage waits until the write to tape is complete.
The IRU can do multiple database dumps simultaneously. Each copy of IRU has its own
set of four buffers.
The configuration parameter is
TAPE-BUFFER-SIZE number
where number is in words. The minimum value is 14,336 words (8 tracks or
approximately 64,500 bytes). The maximum value is 64,512 words (36 tracks or
approximately 290,000 bytes). For best performance, this value should be a multiple of
a track (1792 words). The actual buffer size is increased by the IRU to include the page
headers.
• When dumping UDS files, IRU uses a dump buffer size equal to the configuration
parameter TAPE-BUFFER-SIZE (except for the last buffer of each file, which can be
smaller). You should use a value of 28,672 (16 tracks), the default value, for the
T9x40 tapes.
• When dumping TIP files, IRU uses a maximum buffer size of 9 tracks or TAPE-
BUFFER-SIZE whichever is smaller. This smaller buffer size restriction is because
of an FCSS maintenance read limitation.
4–22 3839 6586–010

FAS
Tapes
• The IRU MOVE command also uses the parameter TAPE-BUFFER-SIZE. For most
sites, the optimum value for the DUMP command is a satisfactory value for the
MOVE command. The MOVE command has a maximum value of 32 KB words,
however.
For more information, see Section 2 in the Integrated Recovery Utility Operations
Guide (7830 8914). Also see Section 5, “Integrated Recovery Utility,” in the Universal
Data System Configuration Guide (7844 8362).
You can modify the tape block size used by FAS operations. The parameter is
SET TAPE_BLOCK_SIZE:= n;
where n refers to the number of tracks and can be 1, 2, 4, 8, or 16. The default is 4
tracks.
You should use the value of 16 for the T9x40 family. 16 tracks equals 129,024 bytes or
approximately 29,000 words.
The block size must be set every time you create tapes by using BACKUP operations
(BACKUP, COPY_VOLUME, ARCHIVE, and so on). Otherwise, the default is used. For
example, if you are creating copies of tapes by using the COPY_VOLUME command,
the output tapes default to four tracks even if you had created the original tapes with
16-track blocks.
If the block size is set to 16, FAS uses 16 buffers, of 1800 words each (one track per
buffer). Mass storage and tape I/O are separate activities so multiple mass storage
buffers can be waiting to be written to tape.
4.4.5. Compression
Exec
IRU
CMPLON is the option that enables compression for T9x40 drives. CMPOFF, the
default, disables compression. The following information tells how to turn it on.
Compression is specified on the ATTRIBUTE TRAIL statement, keyword UNIT. To turn
compression on, configure the keyword as follows:
ATTRIBUTE TRAIL trail-ID PARAMETERS ARE: UNIT,CMPLON
For more information see 12.4, “Audit Trail Configuration Statements,” in the Exec
System Software Installation and Configuration Guide (7830 7915).
IRU assigns tapes and has a configuration parameter for turning compression on or
off. For the T9x40, the following value turns compression on:
TAPE-COMPRESSION CMPLON
3839 6586–010 4–23

Tapes
FAS
For more information on IRU values see the Integrated Recovery Utility Operations
Guide (7830 8194).
Compression is turned on or off by the tenth positional parameter when you use the
@ASG statement for tapes.
@ASG Tape.,HIS98/////////CMPLON,111C
For more information, see the Executive Control Language (ECL) and FURPUR
Reference Manual (7830 7949 ).
4.4.6. FURPUR COPY Options G, D, and E
The following describes using the COPY command and the available options.
Uncompressed Tapes: COPY,GD
Many sites have runstreams to copy files from mass storage to tape. Some
runstreams have been around for decades. The information below explains some
enhancements that have occurred over the years, but some sites might not yet have
taken advantage of them. Proper use of these capabilities optimizes I/O operations
when copying files to your high-speed tapes.
Most sites copy mass storage files to tape using the COPY,G command. Its definition
is
copy n allocated tracks of the file, beginning with relative track 0, which are written
to tape in blocks of n*1,794 words.
Each 1,792-word track is prefixed with two words containing the relative track
address, block sequence number, and checksum. FURPUR writes two EOF marks on
the tape after copying the file, unless the statement contains an E option.
The original implementation of the COPY, G command wrote out one track at a time;
eight tracks of data would write eight 1-track blocks to the tape. Later on, for
performance reasons, the COPY,G command was enhanced to write out 8-track tape
blocks. To ensure compatibility, the D option was created to enable the option of
selecting the old format for COPY,G (writing out 1-track blocks) on uncompressed
tapes. These options apply to both labeled and unlabeled tapes.
4–24 3839 6586–010

The following table shows the block size options:
Table 4–6. Block Size Options for COPY,G
FURPUR COPY
Options
Compression
Tracks Per Block
ON OFF
COPY,G 8 1
COPY,GD 8 8
Tapes
You should use the D option on all uncompressed tapes to create tapes with larger
block sizes. This enhances performance when the tapes are written, read, or copied.
While the default value for the block size is set to 8-track blocks, it can be configured
by site to be between 1-track and 16-track blocks.
Unlabeled Tapes: COPY,GE
The COPY,G command, upon completing the data transfer to tape, writes two EOFs to
tape and then backspaces over the last one. Two EOFs in a row means there are no
more files on this tape. If you put more data on the tape, then the second EOF is
overwritten when the next write is done.
High-speed tapes, such as the T9x40, take a long time to reposition and, for unlabeled
tapes, the backspace over the second EOF causes a reposition.
The E option (@COPY,GE) causes only one EOF to be written for unlabeled tapes; the
write of the second EOF and the backspace are not done. This avoids repositioning.
However, you must take explicit action to put the second EOF on the tape when
@CLOSE or @MARK are done writing to it.
The E option is ignored for labeled tapes.
For more information, see Section 7 of the Executive Control Language (ECL) and
FURPUR Reference Manual (7830 9796).
4.5. Tape Drive Encryption
Encryption is one of the most effective ways to achieve data security today. Beginning
with OS 2200 11.3, OS 2200 supports tape drive encryption and the Sun/StorageTek
Crypto Key Management Solution (KMS) Version 2.0 (KMS v2.0). Encryption
functionality is built directly into the tape drive so the operating system is not involved
in the encryption processing. The Sun encryption solution utilizes a standard AES-256
cipher algorithm.
3839 6586–010 4–25

Tapes
A successful data encryption strategy must address proper key management and
make sure that the keys to unlock data are never lost. The Sun Crypto Key
Management System provides safe, robust key management. It includes of a number
of components:
• Clustered Key Management Appliances (KMA) are dedicated appliances for
creating, managing and storing encryption keys.
• KMA Manager Software provides for the setup and administration of the
encryption system, the interface uses a GUI management program.
• The encryption agents are hardware and software embedded in the tape drives
themselves.
With this initial release of encryption on OS 2200, the encryption process is totally
transparent to OS 2200. Once a tape device has been enrolled into the Key
Management System, all cartridges created on that device are encrypted. An
encrypting tape device can also read unencrypted cartridges, but cannot write to an
unencrypted cartridge unless it is at the beginning of the tape (load point) and the
cartridge becomes encrypted. A tape cartridge currently cannot contain a mixture of
encrypted data and unencrypted data, either the entire cartridge is encrypted or the
entire cartridge is not encrypted.
4.5.1. Tape Drives capable of supporting encryption
• Sun/StorageTek T10000A
Encryption with the T10000A is fully supported beginning with OS 2200 11.3.
• Sun/StorageTek T9840D
Encryption with the T9840D is fully supported beginning with OS 2200 11.3.
• Sun/StorageTek LTO4-HP
Encryption with the LTO4-HP is fully supported beginning with OS 2200 11.3.
• DSI LTO4-HP
4.5.2. Restrictions
Encryption is not supported on this drive at this time.
Since the tape drive encryption process is totally transparent to the operating system,
it is recommended that all drives be configured for encryption or all drives configued
for no encryption. This release of encryption does not include any encryption
subfield(s) on ECL or using program interfaces (ERs and CALLs). Future OS 2200
releases are to include enhancements to standard ECL statements for encryption
specifications.
4.6. Sharing Tapes Across Multiple Partitions
The following describes the affects and considerations when sharing tapes across
multiple partitions.
4–26 3839 6586–010

4.6.1. Electronic Partitioning on Fibre Channel
Benefits
Tapes
Electronic Partitioning (EP) optimizes Fibre Channel tape usage. Prior to the availability
of EP, sharing fibre tapes on a SAN was an operator-intensive effort with the risk of
having one host interrupt tape operations on another host that shared the SAN and its
tape devices.
Electronic Partitioning, part of SCSITIS, the SCSI Tape Driver for OS 2200 systems,
assigns the drive to the first host requesting it, preventing inadvertent access from a
second host. The exclusive use remains until the controlling system releases the drive
with a down (DN) keyin; or the other system does a Release Tape Unit (TU keyin) to
the drive. Exclusive use ensures that another host does not accidentally write to the
tape.
A drive remains exclusively assigned (reserved) across recovery or I-Boots to the
system that last assigned it. When the system that last assigned the drive is rebooted
or recovered, the drive is still UP and reserved to that system.
Drives can be shared by systems either through manual facility keyins (UP/DN) across
the systems involved or through the use of Operations Sentinel Shared Tape Drive
Manager (SPO STDM). (Operations Sentinel was formerly Single Point Operations
(SPO).)
Migrating to Tape Drive Electronic Partitioning
There is a compatibility consideration when migrating multiple OS 2200 hosts to
Electronic Partitioning. If a Fibre Channel tape drive is shared among multiple OS 2200
hosts and some systems support EP and some have not yet migrated, the operational
characteristics are similar to those that arise when sharing Fibre Channel devices
without EP protection. For example, if a drive on a system without EP protection is
currently in use, and the same drive is brought UP on the EP-supported system, the EP
system gains exclusive use of that drive. This interrupts any work in progress on the
drive on the system without EP support.
There is also a difference in operational behavior in the Initial Control Load Program
(ICLP) area. When EP is supported on one or more systems that share a Fibre Channel
tape drive, and a host that supports EP is halted (did not release the drive), the drive
cannot be used to boot another host that shares it until it is released. In this example,
the host that has it was halted. The solution is to recover that host and DN the drive,
or power down and power up the drive to clear its reservation, or TU the device from
any connected host. The device must be in a DN state prior to issuing the TU keyin.
4.6.2. Automation
Operations Sentinel Shared Tape Drive Manager (STDM) is a separately priced service
using Operations Sentinel to facilitate the management of tape drives assigned to a
shared pool. STDM is recommended for automation of tape drive management.
3839 6586–010 4–27

Tapes
STDM provides for automatic error-free movement of shared tape drives between
systems. Additionally, STDM acquires drives from systems with a surplus, hence
leveraging equipment that is not used by a system continuously.
The Shared Tape Drive Manager is a consulting deliverable, meaning that the
Operations Sentinel Technology Consulting Group can configure Operations Sentinel
and Operations Sentinel Status to perform the automated movement of tape drives
between systems. STDM is built on a standard Operations Sentinel product, with
advanced configuration and extensions. For more information on Operations Sentinel
Services and STDM, contact your local Unisys representative or send an e-mail directly
to Jim.Malnati@Unisys.com.
4–28 3839 6586–010

Section 5
Performance
This section discusses the performance of the PCI-based IOPs for the Dorado 300,
400, 700, 800, 4000, 4100 and 4200 Series servers:
• SIOP
I/O processor for disks and tapes
• CIOP
I/O processor for communications (Ethernet).
Note: CIOP is not supported on Dorado 400, 4000, 4100 and 4200 Series.
5.1. Overview
This overview explains what the performance numbers, given in the rest of this
section, might mean to your site.
5.1.1. Basic Concepts
Bandwidth
The I/O complex can be viewed as a hierarchy of shared components. The following
are important considerations in building an I/O complex configuration:
• Build in performance resiliency
Group devices so that, despite the loss of a resource, the I/O hierarchy still
supports adequate I/O performance levels to and from key peripheral devices.
• Group devices for connection to higher-level resources
The total bandwidth of all the devices cannot exceed the performance threshold
of the higher level resource.
Bandwidth is the capacity of a component to transfer data. The term “peak
bandwidth” refers to situations that reflect the best-case performance numbers. The
numbers can be achieved under ideal conditions, such as sequential access with no
competition for the device or path. Peak bandwidth is the value when the unit is 100
percent busy. However, peak bandwidth is not a common situation and is not
sustainable for very long. The peak bandwidth numbers are based on measurements
done with channels, channel adapters, and drivers. Also, available bandwidth has a
greater effect on the performance of relatively low-overhead, large block I/O transfers.
Performance of small block I/O transfers is affected more by IOP processing speed
and latency than by bandwidth because of the greater overhead associated with small
block I/O transfers.
3839 6586–010 5–1

Performance
The term “sustained bandwidth” refers to conditions that are closer to the real world
of On Line Transaction Processing (OLTP). The disk accesses are more random and
there is more contention for devices and paths.
Note: Sustained bandwidth values are estimates. They are 80 percent of the peak
bandwidth. In addition, these numbers assume no other bottleneck in the system.
The numbers represent the best case for that particular component.
The sustainable values vary from site to site. The numbers at your site are probably
lower than the guideline numbers in this section.
SIOP and CIOP have a hierarchical PCI bus structure. Each level of the hierarchy is
separated by a PCI bridge. Each bridge uses a round-robin arbitration scheme, giving
equal priority to all active components at each level; therefore, each active PCI slot
gets an equal part of the bandwidth available to that level of components. Likewise,
the bandwidth available to any PCI-to-PCI bridge is equally distributed to the active
peripheral controllers (HBAs or NICs) or bridges connected to that bridge’s
subordinate bus, and each peripheral controller port receives an equal share of the
bandwidth available to the peripheral controller.
The following equation can be used to estimate the percentage of IOP bandwidth
available to a particular peripheral controller:
• For peripheral controllers on a level 1 bus:
B=100/N1/P
• For peripheral controllers on a level 2 bus:
B=100/N1/N2/P
• For peripheral controllers on a level L bus:
where:
B=100/N1/N2/…/NL/P
B is the percentage of IOP bandwidth available to a particular port.
N1 is the number of active slots or bridges on the first level of the IOP bus structure.
N2 is the number of active slots or bridges on the second level of the IOP bus
structure.
NL is the number of active slots or bridges on the level associated with the peripheral
controller.
P is the number of ports in use on the peripheral controller associated with the port.
Level 1 is the bus closest to the IOP that is not separated from the IOP by PCI-to-PCI
bridges. Level 2 is separated from the IOP by 1 PCI-to-PCI bridge.
5–2 3839 6586–010

Performance
When calculating the number of active slots or bridges on each level, work toward the
IOP from the peripheral controller, and only count the number of active slots on that
level that are on the same bus. For example, there may be 2 busses on Level 2 of the
bus hierarchy because they are associated with different bridges. Do not count all the
active components on both busses.
A PCI bridge is considered active if there are one or more active peripheral controllers
subordinate to that bridge. A peripheral controller is considered active if it is
transferring data at its fullest potential.
The following figure shows the structure of the PCI bus hierarchy for Dorado 300 and
Dorado 400 PCI Expansion Rack.
Figure 5–1. Dorado 300 and Dorado 400 PCI Bus Structure
The following figure shows the structure of the PCI bus hierarchy for Dorado 700 PCI
Expansion Rack and Dorado 4000 and 4100 PCI Channel Module.
3839 6586–010 5–3

Performance
Figure 5–2. Dorado 700, Dorado 4000, and Dorado 4100 PCI Bus Structure
5–4 3839 6586–010

Figure 5–3. Dorado 800 and Dorado 4200 PCI Bus Structure
Best Case Bandwidth Allocation
Performance
Optimal performance is realized when a single-port peripheral controller is inserted at
the lowest available level and all other slots are not active. The following example
reveals that the port gets the maximum bandwidth:
• Dorado 300 and Dorado 400
N1 = 1 and P = 1
100%=100/1/1
• Dorado 700, Dorado 4000, and Dorado 4100
N1 = 1, N2 = 1, and P = 1
100%=100/1/1/1
• Dorado 800 and Dorado 4200
N1 = 1, N2 = 1, and P = 1
100%=100/1/1/1
3839 6586–010 5–5

Performance
Worst Case Bandwidth Allocation
The worst-case scenario for the Dorado 300 or Dorado 400 involves each slot
connected to a PCI Expansion Rack with each rack fully populated with dual-port
peripheral controllers. The following calculation reveals that each port gets minimal
bandwidth:
N1 = 2, N2 = 7, and P = 2
3.6%=100/2/7/2
The worst-case scenario for the Dorado 700, Dorado 4000, and Dorado 4100 involves
a dual-port HBA in one of the slots from slots 1through 4 (level 3 bus) in the PCI
Expansion Rack, and the PCI Expansion Rack is fully populated with active HBAs. The
following calculation reveals that each port gets minimal bandwidth (two bridges on
level 1, one bridge and slot on level 2, four slots on level 3, and two ports on the HBA):
N1=2, N2=2, N3=4, P=2
3.125%=100/2/2/4/2
The worst-case scenario for the Dorado 800 and Dorado 4200 involves each slot fully
populated with dual-port peripheral controllers. The following calculation reveals that
each port gets minimum bandwidth:
N1 = 1, N2 = 6, and P = 2
8.33%=100/1/6/2
Typical Bandwidth Allocation
A more common IOP configuration on the Dorado 300 or Dorado 400 might have a
dual-port peripheral controller and a PCI Expansion Rack on level 1. The PCI Expansion
Rack might contain three single-port and one dual-port peripheral controllers on level
2. The following calculation reveals the bandwidth for each port in slot 0:
N1 = 2 and P = 2
25%=100/2/2
The following calculation reveals the bandwidth for each single-port peripheral
controller on level 2 in the expansion rack:
N1 = 2, N2 = 4, and P = 1
12.5%=100/2/4/1
The following calculation reveals the bandwidth for each port on the dual-port
peripheral controller in the expansion rack:
N1 = 2, N2 = 4, and P = 2
6.3%=100/2/4/2
A similar IOP configuration on Dorado 700, 4000, or 4100 may have a dual-port
peripheral controller in slot 7 of the PCI Expansion Rack plus three single port and 1
dual port peripheral controllers in slots 1 to 4. The following calculation reveals the
bandwidth allocated to each port in slot 7 of the expansion rack:
5–6 3839 6586–010

N1=1, N2=2, P=2
25% = 100/1/2/2
The following calculation reveals the bandwidth for each single-port peripheral
controller in slots 2 to 4 of the expansion rack:
N1=1, N2=2, N3=4, P=1
12.5%=100/1/2/4/1
The following calculation reveals the bandwidth for each port on the dual-port
peripheral controller in slot 1 of the expansion rack:
N1=1, N2=2, N3=4, P=2
6.3%=100/1/2/4/2
Performance
A similar IOP configuration on Dorado 800 or 4200 may have three dual-port peripheral
controllers plus three single port peripheral controllers. The following calculation
reveals the bandwidth allocated to each port:
N1 = 1, N2 = (3 + 3), P = (2 + 1)/2
11.1% = 100/1/6/1.5
Special Considerations for Dorado 700
The Dorado 700 Remote I/O motherboard (RIO) has slots available for up to six IOPs.
However, bandwidth is not equally distributed to all six slots. Even IOPs (IOP00,
IOP02, and so forth) run at 100 MHz, while odd IOPs (IOP01, IOP03, etc.) run at 133
MHz. Therefore, in the RIO, there is 33% more bandwidth available to odd IOPs than
even IOPs.
The PCI Expansion Rack attached to the Dorado 700 IOP has seven slots. Slots 1
through 4 run at 66 MHz, while slots 5 through 7 run at 100 MHz. If at any given time,
there is exactly one active peripheral controller, that controller realizes greater
bandwidth if it resides in one of slots 5 through 7 as opposed to slots 1 through 4.
The SBCON card (SIOP) and the Time Card (CIOP) run at a maximum frequency of 66
MHz. If installed in the IOP’s PCI Expansion Rack, the card forces the entire PCI bus
associated with that slot to run at a maximum frequency of 66 MHz. Therefore,
installing an SBCON card or Time Card in slot 5 reduces the available bandwidth on slot
6 and vice versa. Slot 7 is on its own bus, so its bandwidth is not affected by a card
placed in another slot.
Special Considerations for Dorado 4000 and 4100
On Dorado 4000 and 4100, the IOP resides in an I/O Expansion Module. This I/O
Expansion Module supplies enough potential bandwidth to support two IOPs running
at full speed. If more than two IOPs are active in a single I/O Expansion Module, the
available bandwidth is evenly distributed among all IOPs in the I/O Expansion Module.
An IOP in an I/O Expansion Module with multiple other IOPs might realize less
bandwidth than an IOP in an I/O Expansion Module with only one other IOP. For
example, assume one I/O Expansion Module has one active IOP, a second I/O
Expansion Module has two active IOPs, and a third I/O Expansion Module has four
3839 6586–010 5–7

Performance
active IOPs. The IOP in the first I/O Expansion Module receives 50% of the I/O
Expansion Module’s available bandwidth because the I/O Expansion Module can
support two IOPs at full speed. An IOP in the second I/O Expansion Module also
receives 50% of the I/O Expansion Module’s available bandwidth. An IOP in the third
I/O Expansion Module, however, only receives 25% of the I/O Expansion Module’s
available bandwidth.
The PCI Channel Module attached to the Dorado 4000 or 4100 IOP has seven slots.
Slots 1through 4 run at 66 MHz, while slots 5 through 7 run at 100 MHz. If at any given
time, there is exactly one active peripheral controller, that controller realizes greater
bandwidth if it resides in one of slots 5 through 7 as opposed to slots 1 through 4.
The SBCON card runs at a maximum frequency of 66 MHz. If installed in the IOP’s PCI
Channel Module, the card forces the entire PCI bus associated with that slot to run at a
maximum frequency of 66 MHz. Therefore, installing an SBCON in slot 5 reduces the
available bandwidth on slot 6 and vice versa. Slot 7 is on its own bus, so its bandwidth
is not affected by a card placed in another slot.
Special Considerations for Dorado 4200
On Dorado 4200 there are some performance considerations to be made while
deciding on how to connect the IOPs in an I/O Manager to the host system. If four
IOPs (in 2 I/O Managers) are connected to a single host slot (by using the switch card
to daisy chaining them together), the IOPs attached to the second switch in the daisy
chain may receive as little as half the bandwidth of the IOPs attached to the first
switch card. Note that such a configuration should only occur if more than 2 I/O
Managers are utilized in a single system.
For the case of four IOPs connected to the same host slot, the best and worst-case
bandwidth allocations for the IOPs are calculated as follows:
Best case scenario (single-port peripheral controller in an IOP in the I/O Manager
connected to the first switch card):
N1 = 3, N2 = 1, and P = 1
33.3%=100/3/1/1
Worst-case (six dual-port peripheral controllers in an IOP in the I/O Manager
connected to the second switch card):
N1 = 3, N2 = (2 * 6), and P = 2:
1.3%=100/3/12/2
80 Percent Guideline
Performance resiliency requires having multiple paths to a device or subsystem so
that in the event of a loss of a path, the remaining paths can still provide acceptable
performance. The remaining paths should be no more than 80 percent busy
(sustainable).
5–8 3839 6586–010

Performance
There is an easy way to calculate what the busy percentage should be for your
production paths. Assume that you have already lost a path. The remaining paths
should be no more than 80 percent busy.
1. Multiply the number of remaining paths by 80.
2. Add your failed path (1) back to the number of remaining paths.
3. Divide this number into the value you got in step 1 (when you multiplied by 80).
The result is the target number for the maximum percentage busy on your production
paths.
Example
What percentage busy should four paths be so that, if one path is lost, the remaining
three are no more than 80 percent busy?
3 x 80 = 240 (Remaining paths multiplied by 80)
3 + 1 = 4 (Remaining paths plus the lost path)
240 / 4 = 60 (Result from step 1 divided by total paths)
Answer: The four production paths should be sized so that they are not more than 60
percent busy.
The following shows the busy percentage that should be planned for each production
path such that if one production path is lost, the remaining paths are no more than 80
percent busy.
Table 5–1. Busy Percentage per Path
Number of production paths 2 3 4 6 8 10
Percent busy for each production path 40% 55% 60% 67% 70% 72%
The 80 Percent Performance Guideline and Your Site
The 80 percent guideline is too simplistic to be the only guideline used at your site for
all your paths. The guideline works well when considering the number of channels to
connect to your production disk family. However, it gets more complicated when you
consider what happens when you lose other resources, such as a power domain. The
key is to understand your I/O complex needs over the course of the production day,
month, and year. Therefore, do your planning by looking at your I/O complex and
determining how to continue production with reasonable performance after losing
different I/O components.
If you try to strictly apply the 80 percent guideline, it might point you to more disks,
channels, or IOPs than you actually need. (It can also point you to less than you need.)
Disks especially tend to be affected by other performance factors, such as
concurrency or contention that are not easily defined here. Consult your Unisys
storage specialist for an accurate assessment of your I/O configuration needs.
3839 6586–010 5–9

Performance
Measuring System Performance
One of the first steps in determining the connectivity versus performance tradeoff for
a given workload is to characterize that workload. For existing systems, the software
instrumentation package (SIP) provides the information needed to characterize I/O
workloads and I/O trace data that can be used in conjunction with third-party data
reduction software to produce time series analysis of I/O loads. Time series data
identifies workload characteristics for the peak activity periods that stress the I/O
complex configuration the most. For systems currently under design, it is best to
identify the set of files accessed by the system and then build file reference patterns
for each transaction. Finally, scaling up to peak I/O load requires establishing
multipliers of I/O loads that relate to peak transaction rates.
This calculation can be done using modeling techniques with a spreadsheet approach
that makes use of component utilization limits ensuring adequate performance.
A tool for performance evaluation is TeamQuest Baseline. For more information see
the TeamQuest Baseline Framework and TeamQuest Online User Guide (7830 7717).
5.1.2. Performance Numbers and Your Site
The information in this section is intended to help you better understand the
performance numbers stated and how they relate to performance to your site.
These performance numbers are given for various channels and peripherals. However,
these measurements were intended to find the upper limit for the particular
component measured. Other bottlenecks that could impact the component being
measured were as best eliminated as possible.
Some of the things that were done for optimization of the performance numbers are
not things that most sites are able to do.
Differences Between Our Measurement Environment and Production
Site Performance
• There was no other traffic in the system. Traffic can dilute system performance of
the component being measured.
• Our drivers transfer the input from memory. For example, tape transfer rate is
measured by transferring data from memory to tape. Sites move data from disk to
channel to memory and then from memory to channel to tape. Sites have many
more potential bottlenecks.
• When measured, the device is the only active device on the channel or IOP. Most
sites want multiple devices per channel. However, as more devices are activated
on the channel, the performance level of each device drops.
5–10 3839 6586–010

Performance
• When measuring channels or IOPs, devices are added until the maximum channel
transfer rate is reached. As devices are added, the speed of any one device drops.
With a large number of devices, the speed of the individual devices might be too
low for sites to accept.
• Disk measurements are done with 100 percent cache hits. Sites usually do not
achieve this value. Each cache miss takes longer to perform and affects the overall
performance level.
Tape Performance
5.2. SIOP
Note: The Dorado 400 does not support tape in this release.
Almost all sites have data backup times or windows. These windows are under
pressure to be reduced because most sites want to back up their data as fast as
possible.
Tape vendors give numbers about how fast data can be written to the tape. However,
the numbers might not be the ones you experience. Other factors limit the tape from
hitting its maximum performance. Some performance limitation factors include the
following:
• The channel might not be able to handle the tape drive performance. If so, the
channel limits the tape transfer rates.
• You might assume that you can achieve the stated channel speed. However,
channel speed is usually measured with multiple devices active. This reduces any
idle time in the channel. A channel with a single device usually has a lower
performance number than a channel with multiple devices.
• A tape is usually the receiver of data. It can only go as fast as the disks and the
disk channel can send the data. Disks and their channels can be slower than the
tape drives and their channels.
• The IOP can also be a limitation. If too many devices or channels are present, the
bandwidth of the IOP limits how much data can be sent to the tape drive. In some
cases, sites doing back up have had the disks and tapes on the same IOP.
• User applications can impact tape performance. Block size and file size can
actually have more of an impact on performance than hardware. See Section 4,
“Tapes,” for a description of how to optimize your software parameters.
Component and system performance are very complex to optimize. You might engage
Unisys in a service contract to evaluate your application and configuration plans and to
make recommendations.
The SIOP is the PCI-based I/O processor that runs on Dorado 300, 400, 700, 800, 4000,
4100 and 4200 Series servers.
Note: The results shown in the following graphs are from Dorado 300, 700, Dorado
800 and Dorado 4200 tests. Similar differences between the Dorado 400, Dorado
4000 and Dorado 4100 are expected but the tests have not been completed at the
3839 6586–010 5–11

Performance
time of publication for this document. See the support Web site for more
information.
This section gives data about performance, expressed in charts. This enables you to
make better estimates of your site projected performance.
The measurements were taken using our latest peripherals, cards, and microcode.
Over time, newer devices and microcode levels are released. With newer equipment,
there is usually an increase in performance. If you migrate your older peripherals to
the newer IOP and HBAs, you might not achieve the performance levels described
here.
These charts are not updated for every improvement in performance. The following
measurements are done in our laboratory and are only guidelines. A slight change in
values, based on newer hardware or firmware, is not significant enough for these
charts to be out of date.
When looking at this data, remember that your numbers are likely to be less than
shown here.
The charts are measured in tracks. The following table can help you translate the
values into other units.
Table 5–2. Translation of Tracks to Words and Bytes
Tracks Words Bytes
1 1,792 8,064
2 3,584 16,128
4 7,168 32,256
8 14,336 64,512
16 28,672 129,024
32 57,344 258,048
5–12 3839 6586–010

5.2.1. SIOP Performance
Performance
The performance numbers (for all but the sequential tests) were based on our
RANDIO tests, a benchmark test designed to analyze channel performance for
different disk I/O packet sizes. It is not modeled after any particular application. The
purpose is to measure the performance of SIOP; all other potentially limiting factors
were eliminated.
RANDIO tests have the following characteristics:
• 100 percent cache-hit rate using EMC DMX systems
• Multiple activities, each accessing a separate disk, active on a channel
• Multiple Fibre HBAs used
One of the graph lines is “80% Reads 20% Writes.” This is a typical transaction
profile.
In the following figures, the Writes are a little slower than the Reads.
Note that the scales on the figures are not the same. The Dorado 700 starts with
almost twice as many requests per second and the block sizes are much larger.
Figure 5–4. SIOP: Dorado 300 I/Os per Second
Figure 5–5. SIOP: Dorado 700 I/Os per Second
3839 6586–010 5–13

Performance
Figure 5–6. SIOP: Dorado 800 I/Os per Second
Figure 5–7. SIOP: Dorado 4200 I/Os per Second
5–14 3839 6586–010

Figure 5–8. SIOP: Dorado 300 MB per Second
Figure 5–9. SIOP: Dorado 700 MB per Second
Figure 5–10. SIOP: Dorado 800 MB per Second
Performance
3839 6586–010 5–15

Performance
Figure 5–11. SIOP: Dorado 4200 MB per Second
Figure 5–12. Dorado 800 I/O Manager Throughput Ratios
5–16 3839 6586–010

Figure 5–13. Dorado 4200 I/O Manager Throughput Ratios
5.2.2. Fibre HBA Performance
Performance
One of the graph lines is “80% Reads 20% Writes.” This is a typical transaction profile.
In the figures below, the Writes are a little slower than the Reads.
Compare the performance numbers of the SIOP with those of the Fibre HBA; they are
about the same. One Fibre HBA can fully utilize an SIOP.
• If you have multiple Fibre HBAs on the same SIOP, you cannot achieve full
performance on the Fibre HBAs; they share the bandwidth of the SIOP.
• The Fibre HBA has two ports; we recommend that you use both ports. However,
if both ports are active and pushed to their limits, then they are limited by the
performance capacity of the SIOP.
A Fibre Channel HBA in an expansion rack has a slightly lower bandwidth than a similar
HBA in the I/O module.
3839 6586–010 5–17

Performance
Figure 5–14. SIOP Fibre HBA: I/Os per Second
Figure 5–15. Dorado 800 Single Port Fibre HBA: I/Os per Second
5–18 3839 6586–010

Figure 5–16. Dorado 4200 Single Port Fibre HBA: I/Os per Second
Figure 5–17. SIOP Fibre HBA: MB per Second
Performance
3839 6586–010 5–19

Performance
Figure 5–18. Dorado 800 Single Port Fibre HBA: MB per Second
Figure 5–19. Dorado 4200 Single Port Fibre HBA: MB per Second
5–20 3839 6586–010

Performance
Figure 5–20. Dorado 800 Single Port Fibre HBA Throughput Ratio
Figure 5–21. Dorado 4200 Single Port Fibre HBA Throughput Ratio
5.2.3. Sequential File Transfers
In a database dump or file save environment, the data patterns are different from
those in the more random transaction environment. At any point in time, a single file is
being sequentially read from a disk and written to tape, which is usually accomplished
in large blocks.
The transfer rates for sequential transfers are slower than when doing multiple I/Os at
the same time. The following figures are representative of a file save activity.
3839 6586–010 5–21

Performance
Disks
Tapes
The measurements were taken to compare a DMX800 and a DMX2. The DMX 800
Write is the bottom line; the DMX 800 Read is the second from the top. A Fibre
Channel was used.
The figure below shows that Writes are slower than Reads.
Figure 5–22. SIOP Fibre Disk: Sequential I/O
The following measurements are taken on the T9840C tape drive. The tape drive has a
rated maximum transfer rate from the tape control unit to the tape of 30 MB per
second.
When compression is turned off, the host can only send data at 30 MB per second.
When compression is turned on, compression is done at the tape control unit. That
means that the host can send data faster than 30 MB per second; it is the compressed
data that is written at 30 MB per second to the tape.
Figure 5–23. SIOP Fibre Tape: Sequential I/O
The two top lines are with compression turned on. Writes are just a little slower than
Reads. With compression turned off, the transfer rate maximizes at 30 MB per second
(tape drive limit). A Fibre Channel was used.
5–22 3839 6586–010

Performance
A rate of 60 MB per second is believed to be about the top speed of the channel for
sequential writes; adding additional tape drives does not significantly increase the
amount of data sent across the channel.
Database Saves or File Saves
The performance numbers above only measure one thing because other bottlenecks
are removed. The numbers can help you make some estimates of Database Saves or
File Saves in your environment, but remember to take into account the more complex
nature of Database or File Saves.
Database or File Saves are the copying of files from a disk to a tape. At its basic level,
this process is one file being copied from one disk across one disk channel to a tape
channel and to a tape drive. Performance bottlenecks can arise that are not visible in
the numbers above. Examples:
• The disk channel is slower than the tape channel. In this case, the speed of the
tape writes is limited by the disk channel.
• The tape channel is on the same SIOP as the disk channel. Fibre HBA performance
is about the same as the SIOP. If you have both channels on the same SIOP, then
the SIOP must handle the data twice: from the disk and to the tape. That cuts the
overall transfer rate in half.
5.3. SCSI HBA
The following graph is based on sequential tape I/O (Reads and Writes) and compares
the newer SCSI HBA on the SIOP to the older SCSI CA on the CSIOP. It has one
T9840A tape drive on the SCSI channel.
In this environment, the new SCSI HBA is about 1.5 times faster than the older SCSI
CA.
5.4. SBCON HBA
Figure 5–24. SIOP SCSI Compared to CSIOP SCSI
The graph below has one T9840C tape drive on an SBCON channel. The SBCON HBA
achieved about 15 MB per second when writing out 16-track blocks (typical size for
3839 6586–010 5–23

Performance
database dumps or file saves). This is close to the rated speed of SBCON (17 MB per
second), so adding tape drives to the HBA does not greatly increase the overall
throughput of the HBA.
Figure 5–25. SIOP SBCON Tape Performance
The following graph is based on sequential tape I/O (Reads and Writes) and compares
the newer SBCON HBA on the SIOP to the older SBCON CA on the CSIOP. One tape
drive was used.
In this environment, the new SBCON HBA on the SIOP has about the same
performance level as the older SBCON CA on the CSIOP.
Figure 5–26. SIOP/CSIOP Performance Ratio (SBCON Tape)
5.5. FICON HBA
The following graph shows the FICON HBA performance information. Multiple MAS
drives were connected to one FICON channel that was configured to an SIOP.
5–24 3839 6586–010

Figure 5–27. Multiple Drive SIOP FICON Performance
Performance
The following graph shows the FICON HBA performance ratio relative to SBCON
baseline. One T9840C tape drive was used on SBCON HBA with compression on and
one MAS drive was used on FICON HBA.
Figure 5–28. Single Drive/Device SIOP FICON Performance Ratio Relative to
SBCON Baseline
3839 6586–010 5–25

Performance
5.6. Tape Drives per Channel Guidelines
The guidelines in the following table assume I/O writes are being done in large block
sizes.
Most sites have more tape drives configured than the channel can support if all the
drives were to be run at their rated speed. The larger number below reflects that
approach.
If your most important consideration is to have the tape drive run at its rated speed
(and with compression turned on), use the smaller number as a guideline. The smaller
number is based on a file save routine or database dump where you read from disk
and write to tape (using the same channel type for the disk and tape, but the tape and
disk are not on the same channel or SIOP).
Table 5–3. Tape Drives Guidelines
Tape Drive Fibre SCSI SBCON
LTO GEN 3 1 - 3 NA NA
T7840A 4 - 8 NA NA
T9840A 4 - 8 2 - 4 1 - 3
T9840B 2 – 4 NA 1 - 2
T9840C 1 – 3 NA 1 - 2
T9940B 1 – 3 NA NA
5.7. CIOP Performance—Communications
Note: CIOP is not supported on Dorado 400, 4000, 4100 and 4200.
Multiple communications connections can be connected through one CIOP. The
number connected is not important; what is important is the total bandwidth from all
the connections. The maximum sustained bandwidth is limited by the CIOP.
The biggest limiting factor is the number of packets per second. The size of the
packets is a factor, but not the most important one.
The following numbers are maximum values, assuming you run all packets at
maximum packet size. Applications that do file transfers can approach these numbers,
but TIP applications that typically have a smaller packet size have a lower number for
megabytes per second.
5–26 3839 6586–010

A single Ethernet NIC can support the following:
Performance
• Up to 12,000 small packets a second
This should be sufficient to support the performance load of a typical system TIP
transaction rate and profile, but you should have multiple connections for
redundancy.
• Up to 13 MB per second for a single ASCII file transfer
The PUT (sending files to another platform) is about 10 percent faster than the GET
(receiving files).
• Up to 21 MB per second for concurrent ASCII file transfers
The PUT is about 10 percent faster than the GET.
The NIC is actually faster than these numbers. These numbers are limited by the
bandwidth of the CIOP. Multiple NICs on the same CIOP have a combined bandwidth
of approximately these values.
These measurements only measured the NIC; the measurement was not intended to
look at the whole system. You might not meet these numbers because your
transactions are much more complicated, IP-intensive, and I/O-intensive.
5.8. Redundancy
Most sites build redundancy into their I/O complex. The goal is to have an alternate
path to peripherals so that, if one path fails, access to the peripheral is still maintained.
The following are general guidelines:
• All peripherals need to connect to at least two independent channels.
• The independent channels need to connect to at least two independent HBAs.
• The independent HBAs need to connect to independent IOPs.
5.8.1. Expansion Racks
When setting up redundancy, many people like to mirror the connections. When
mirroring, a connection to a device through one IOP has the same connection through
another IOP.
With the Dorado 300, 400, and 700 Series, HBAs in an expansion rack can mirror other
HBAs that are on a different IOP but are not in an expansion rack. This might not at
first appear to be a mirror, but it gives equivalent performance in most cases. The
performance bottleneck is usually the IOP. HBAs running through an expansion rack
have the same performance limitation as HBAs in the I/O module.
5.8.2. Dual Channel HBAs and NICs
Use both ports on the NICs and HBAs. The reliability of using both ports on a single
HBA is higher than using a single port on two HBAs.
3839 6586–010 5–27

Performance
5.8.3. Single I/O Modules
For Dorado 350-class systems or smaller, only one I/O module and one IP cell is
offered. Even in the single IP cell, there are components with redundancy.
Redundant Power and Cooling
IP performance is purchased based on MIPS used in the IP cell (four processors). If
one IP goes down, the remaining IPs can supply the required performance for most
sites.
While there are components in the IP cell that are single points of failure, these
components have good projected reliability.
Many customers can have their IP needs met by a Dorado 350 Series system or
smaller. Almost all of these customers can meet their I/O needs with the single I/O
module, achieving equivalent performance to what they had on their older platforms
and still offering redundancy.
Redundant Paths
Set up your paths so that, if you lose one path, you can continue your production with
equivalent or slightly degraded performance. Evaluation of historical customer I/O
profiles and expectations for Dorado 300 and 700 Series I/O performance indicate that
sites are able to set up this performance level.
Contact your Unisys representative to have a thorough performance analysis done.
5.8.4. Configuration Recommendations
For IOPs
• Set up two IOPs (SIOP) for disk and tapes.
• For the Dorado 300, 700, and 800 also set up two IOPs for communications (CIOP).
• IOP1 (the left-hand IOP slot as you look from the back of the I/O module) is
shipped from the factory with an SIOP. The DVD reader is controlled by the SIOP
at IOP1. The DVD reader has a cable length restriction, so it must be installed in
Slot 1 (furthest left-hand slot as you look from the back of the I/O module). See
Figure 1–19 for a picture and the address names.
• Unisys suggests that you use IOP0 (the IOP slot second from the left) as your
second SIOP. This creates consistency for installation and configuration personnel
that work with multiple sites and platforms.
• Use IOPs 2 and 3 as communications IOPs (the two right-hand IOPs).
5–28 3839 6586–010

For tape and disk
Performance
• Use both ports on the fibre HBA for maximum connectivity. If you need maximum
performance on a particular channel, only use one port on the HBA.
• A PCI Host Bridge Card in Slot 0 of IOP1 is used at many sites. Most sites split the
channels between IOP0 and IOP1. Since there is only one PCI slot open on IOP1
(the DVD interface card is in the other), the open PCI slot usually contains a PCI
Host Bridge Card, so seven extra PCI slots are available.
• IOP0 might not need a PCI Host Bridge Card, even if there is one in IOP1. IOP0
controls two PCI slots in the I/O module. With dual-port cards, this provides four
channels on that IOP. If more than four channels are needed, one of the dual-port
cards can be replaced by a PCI Host Bridge Card for a connection to a PCI
expansion rack.
For Ethernet
• The number of Ethernet connections at sites varies. Usually the number is
between 2 and 8. The number of connections is usually determined by security
and convenience, not performance requirements.
• Spread your communications across both IOP0 and IOP1 to achieve redundancy.
3839 6586–010 5–29

Performance
5–30 3839 6586–010

Section 6
Storage Area Networks
Storage Area Networks, or SANs, are key enablers of shared and scalable storage
application solutions for the enterprise. Fibre Channel provides major advances in
connectivity, bandwidth, and transmission distances. These advantages, when
deployed in Storage Area Networks, enable clients to achieve new levels of
performance and data management
Fibre Channel is an ANSI standard protocol for high-speed data transfer technology.
The standard covers the physical interface and the encoding of data packets. It also
covers the routing and flow control across a Storage Area Network (SAN), which
enables multiple servers and storage devices to be part of the same environment.
Note: “Fibre” is used when discussing Fibre Channel protocol. “Fiber” refers to
the optical fiber transmission medium in Fibre Channel protocol as well as Ethernet.
SANs are dedicated networks of storage and connectivity components that alleviate
data traffic from the LAN/WAN client network. Fibre Channel devices run SCSI
protocol and are viewed by servers as directly attached SCSI devices, even though the
devices might be located kilometers away.
Fibre Channel “pipes” are bigger. A single Fibre Channel path can accommodate up to
200 MB per second. The addition of SAN Fabric increases the number of available
paths and dramatically increases the aggregate bandpass for storage available to the
Enterprise network.
The following terms are sometimes used to describe the Fibre Channel technology:
• SCSI Fibre
Used because the SCSI command set is an upper-layer protocol being transported
by the Fibre Channel.
• ANSI Fibre
Used because Fibre is an ANSI standard.
• Fibre Channel
Widely used today.
3839 6586–010 6–1

Storage Area Networks
Topologies
Fibre Channel technology can be divided into the following topologies:
• Point-to-point links a single host and a single storage device. Dorado servers use
this protocol when talking to a single device. This is seamless to the outside
world; it appears as an arbitrated loop.
• An arbitrated loop provides direct connection between the server (HBA) and the
Fibre Channel devices in one large loop. This was the first popular use. A common
setup would be to have 10 to 15 disks on a Fibre Channel connected to a server.
The devices on the loop shared a bandwidth of 1 GB. This technology is still very
common but now most customers are investing in switched fabric.
• Switched fabric configurations provide multiple connections to all devices,
subsystems, and servers allowing the creation of flexible zones of ownership. This
topology enables a managed Storage Area Network with the potential for millions
of storage devices and hosts. It is the growth area of SANs.
6.1. Arbitrated Loop
Loop topology (see Figure 6–1) interconnects up to 127 nodes; up to 125 can be
storage devices. Each server arbitrates for loop access and, once granted, has a
dedicated connection between sender and receiver. The available bandwidth of the
loop is shared among all devices.
Figure 6–1. Arbitrated Loop
One variation on a straight loop configuration is the addition of hubs to the loop. A hub
is a hardware component that enables the interconnection of several devices in the
loop without breaking the loop.
Hubs in loop topology enable nondisruptive expansion to the network and enable the
replacement of failed units while loop activity continues; this is known as hot-plugging.
Because hubs enable the mixing of copper and fiber cables, implementing hubs in the
loop enables greater distance between nodes so that the devices do not have to be as
physically close to each other. The enhanced distance support and the simple
configuration of hubs can help increase the flexibility of loop topology.
6–2 3839 6586–010

Storage Area Networks
Loop topology has a potential performance disadvantage when large numbers of
devices are on the loop. Only two nodes communicate at a time.
Loops are efficient when
• A network’s high bandwidth requirements are intermittent
• Each node in the loop is less than 100 meters apart
An arbitrated loop topology is the right choice for many small networks. For
performance reasons, arbitrated loops usually have around 10 to 15 devices. More
devices can be added if access to the devices is intermittent.
Addressing
Devices on an arbitrated loop only use the last 8 bits of the 24-bit port address. These
last 8 bits are known as the Arbitrated Loop Physical Address (AL_PA).
Table 6–1. Arbitrated Loop Addressing
Bits 23-08 Bits 07-00
Fabric Loop Identifier AL_PA
Arbitrated loop devices do not recognize the Fabric Loop Identifier; they only care
about the AL_PA field. If the arbitrated loop is a private loop (no connections with an
FL_Port to a fabric), the upper two bytes are zeros, x’0000’. If it is a public arbitrated
loop, the values are the fabric loop values for the domain and area. These values are
handled by the NL_Port on the arbitrated loop and enable the arbitrated loop devices
to communicate with nodes outside the loop.
There are 127 addresses allowed for arbitrated loops, but they are not all sequential.
Many of the 256 possibilities are eliminated due to the Fibre Channel standard
encoding scheme and other reasons.
AL_PA values have a priority scheme. Address priority for the devices on the loop is
the highest for the address with the lowest AL_PA value. The highest priority address
(AL_PA = 00) is reserved for a connection (FL_Port) to a Fibre Channel switch. The next
highest priority is for the ClearPath Plus channel adapter, which has an AL_PA value of
01. Only one ClearPath Plus channel adapter is allowed per arbitrated loop. Multiinitiator
support is not qualified on the ClearPath Plus server.
There is usually no single point of failure because most sites hook up the storage
devices and hosts so that the devices and the host each have two connections with
each connection on a separate arbitrated loop.
Usually, the first storage device put on the loop starts at the lowest priority value,
AL_PA = EF. The priority of a disk usually does not affect performance.
Do not put tapes on the same arbitrated loop as disks. This restriction is not due to
the protocol but to the different performance characteristics of tape and disk devices.
3839 6586–010 6–3

Storage Area Networks
Table 6–2 is an example of an arbitrated loop with eight JBOD disks, one ClearPath
Plus server, and a connection to an FL_Port (SAN connection). It has the following
address settings.
Table 6–2. Arbitrated Loop With Eight JBOD Disks
Device Address
Setting
(hex) (dec)
AL_PA
(hex)
SCMS II /
Exec (dec)
Comments
0 0 EF 239 1 st JBOD
1 1 E8 232 2 nd JBOD
2 2 E4 228 3 rd JBOD
3 3 E2 226 4 th JBOD
4 4 E1 225 5 th JBOD
5 5 E0 224 6 th JBOD
6 6 DC 220 7 th JBOD
7 7 DA 218 8 th JBOD
7D 125 01 01 Host Channel
7E 126 00 00 Switch Port
See Appendix A for a complete listing of all possible AL_PA values.
For more information about arbitrated loop devices, see 6.4.
6.2. Switched Fabric
Switched fabric provides huge interconnection capability and aggregate throughput.
Each server or storage subsystem is connected point-to-point to a switch and
receives a nonblocking data path to any other port or device on the switch. This setup
is equivalent to a dedicated connection to every device. As the number of servers and
storage subsystems increases to occupy multiple switches, the switches are, in turn,
connected together.
The term “switched fabric” indicates there are one or more switches in the
environment. Each switch can support multiple ports. Ports can support 100 MB per
second or 200 MB per second (based on newer standards). The total bandwidth of the
SAN is based on the number of ports. The bandwidth of each port adds to the overall
bandwidth of the SAN.
The implementation of a SAN through switches enables for up to approximately 16
million addresses.
A switched fabric topology (see Figure 6–2) is generally the best choice for large
enterprises that routinely handle high volumes of complex data between local and
remote servers.
6–4 3839 6586–010

Nodes and Ports
Figure 6–2. Switched Fabric Topology
Storage Area Networks
Nodes are the entry and exit points between the Fibre Channel network and the
servers and devices (disks and tapes). Usually, the node has a unique fixed 64-bit node
name that has been registered with the IEEE. The node name is not configured in
SCMS II or used by OS 2200.
Each ClearPath Plus Fibre Channel is a node.
Ports are the entities that transmit or receive data across a SAN. Ports reside on fabric
switches as well as entry and exit locations to the SAN. Ports on switches connect to
other ports on switches to transmit data between switches. Ports on switches can
also connect to ports associated with hosts or storage devices. Usually one port is
associated with the node of that device. Each ClearPath Plus Fibre Channel contains a
port within the node.
Port addresses, the basis for routing data packets across the Fibre Channel
connections, are dynamically assigned 24-bit values called N_Port ID. The ports on the
switches have the address. The ports that are part of nodes do not have addresses
but are connected to ports on switches so that the data can be sent to or from the
proper node.
Ports usually have a unique 64-bit Port_Name. The port name is not configured by
SCMS II or used by OS 2200.
3839 6586–010 6–5

Storage Area Networks
There are several kinds of ports, depending on the functionality. The microcode
determines the proper port type at initialization.
• N_Port
The Node Port is used in a fabric environment. It is the port on the node (server,
disk, or tape) that supports access to the SAN. It has a fibre connection to a fabric
port, F_Port, that is on the fabric switch.
• NL_Port
The Node Loop Port is the port on the arbitrated loop that connects to a SAN. It
has a fibre connection to a fabric loop port, FL_Port, that is on the fabric switch.
• E_Port
The Expansion Port is a port on a fabric switch that connects to another E_Port;
this enables switches to communicate with each other. An E_Port is frequently
referred to as an interswitch link (ISL).
• G_Port
The Generic Port is a port on a switch that can act as one of the ports above. Each
manufacturer has determined its usage.
The dynamic addresses, N_Port IDs, are associated with the ports on the switches.
The F_Port and FL_Port can connect to either the OS 2200 host or to storage devices.
The port that connects to storage devices is configured in SCMS II and used by OS
2200 to send and receive data from the proper storage devices. A form of the N_Port
ID is used as the address for the control unit of the storage device.
Figure 6–3. Switched Fabric
Nodes A, B, and C are all fabric-capable nodes directly attaching to the switched fabric.
Nodes A, B, and C can be servers or storage devices. Node D is a connection from an
arbitrated loop device.
6–6 3839 6586–010

6.3. Switches
Storage Area Networks
Switches route the data across the network. Switches are available with different
numbers of ports.
Switches are not configured in SCMS II nor recognized by OS 2200. However, the port
on the switch that connects to the OS 2200 storage device is configured in SCMS II.
Most storage devices connect directly to the SAN by using ports on a switch. The
devices are fabric-capable and have their own 100-MB or 200-MB connections to the
fabric.
• Brocade Switches
− These switches support the connection of the arbitrated loop devices.
− OS 2200 Fibre Channels can connect to F_Ports or FL_Ports on the switch.
They cannot connect to E_Ports or G_Ports.
See 6.5 and Appendix B for information on port addresses.
• McData Switches
− These switches do not support the connection of the arbitrated loop devices.
− OS 2200 Fibre Channels can connect to F_Ports on the switch. They cannot
connect to FL_Ports, E_Ports, or G_Ports.
− Port addressing is biased by 4 on some McData switches.
See 6.5 and Appendix B for more information.
6.4. Storage Devices
Storage devices must have static addresses. SCMS II must know the address at
configuration time. The address cannot change unless SCMS II is reconfigured. See 6.5
for more information.
The methods for setting addresses are different depending on device type. See the
installation documentation for your storage devices to determine how to set the
addresses.
6.4.1. Arbitrated Loop Devices Running in a SAN
Some early Fibre Channel devices were developed before switched fabric became
popular. The device microcode only supports arbitrated loop, not switched fabric.
These devices are sometimes referred to as non-fabric-capable devices.
Some Brocade switches enable arbitrated loop devices to participate in a SAN,
referred to as QuickLoop mode. An FL_Port on the switch can connect to the
arbitrated loop (NL_Port). The devices on the arbitrated loop only know about devices
on that loop. They are fooled or “spoofed” and can be accessed by initiators outside
the loop. This loop is known as a public arbitrated loop.
3839 6586–010 6–7

Storage Area Networks
The port on the switch that connects the tape drive must be set to run in QuickLoop.
Multiple tape drives can be on the same arbitrated loop. The host channel accessing
the drive must also be set to QuickLoop.
6.4.2. T9840 Family of Tape Drives
T9840A
Each tape unit has a single drive and a single control unit. Each unit has two ports (A
and B). The tape system can access one or more hosts; it can also access one or more
partitions within a host. Only one tape port can access the drive at the same time. The
two ports increase redundancy, but do not increase performance.
When connecting to a switch, each port on the drive connects to a separate switch
port, assuming access is desired from both tape drive ports.
The T9840A runs only in arbitrated loop mode, but can run in a SAN environment
when connected to the proper Brocade switch.
Other T9840 Family Members
T7840A, T9840B, T9840C, and T9940B run as a fabric device but they can also be set
to run as an arbitrated loop device to a Brocade switch. It is preferred to run them as a
fabric device, but you might have situations where you want to run them in arbitrated
loop mode. For example, replacing a T9840A and not wanting to assign a new host
channel to the new device.
Configuring the Front Panel
Each T tape drive is configurable from its front panel.
• The emulation mode for the T family is standard, “EMUL STD.”
• If the drive is to run in fabric mode, select soft addressing (HARD PA=N).
• If the drive is to run in arbitrated loop mode, select hard addressing (HARD PA=Y).
• Select an AL_PA value. The AL_PA value must be unique within that arbitrated
loop. If both tape drive ports are used, they must be in separate arbitrated loops.
Tape Drives in the CLU8500
The tape drives of the CLU8500 must be connected to a fabric switch (as well as the
ClearPath OS 2200 Fibre Channels). Direct connect is not allowed for the CLU8500
tape drives.
6.4.3. JBODs
The CSM700 runs in arbitrated loop mode. It can connect to a Brocade switch that
supports QuickLoop.
All the JBOD devices in a rack must be on the same arbitrated loop. Racks on the
same loop can be in different auxiliary cabinets. The location of the rack within a
cabinet has no effect on the address of the devices.
6–8 3839 6586–010

Storage Area Networks
JBOD devices set switches to give their starting position for the disks in the
enclosure. The next disk in the enclosure has the next highest position on the loop,
and so on until the enclosure is full. The number of disks in an enclosure varies
depending on disk type.
6.4.4. SCSI/Fibre Channel Converters
Some sites have SCSI peripherals and want to use them (especially tapes) to access
hosts across a SAN. The Crossroads 4150 has been qualified for that purpose.
The Crossroads converter has a SCSI bus for devices as well as a fibre connection that
can connect to a fabric switch. The OS 2200 host, running across a SAN, can address
the SCSI devices because the converter builds a table where each device address
(SCSI-ID) has a unique LUN address.
Figure 6–4. FC / SCSI Converter
Each SCSI device on the converter bus must have a unique target address (0 to 6,
8 to 15). If the address has to be changed, set the target SCSI-ID for each device as
described by the configuration information for that device. The converter generates a
default unique LUN value. It is recommended that you use the default.
3839 6586–010 6–9

Storage Area Networks
Crossroads Configuration
The converter can run in arbitrated loop or fabric mode. It is recommended that fabric
mode be used when connecting to a switch.
• If running in Fabric mode, configure the converter with Auto Sense-Soft ALPA.
• If running in arbitrated loop mode, configure the converter with Auto Sense-Hard
ALPA.
• If running in initiator mode, connecting Fibre Channel hosts to SCSI devices,
configure the converter with Use Indexed Addressing. Static addressing must be
used so that the OS 2200 host knows the device address.
The user should turn off FC Discovery so that the router uses only the mapping tables
configured. However, some sites have set this to different values and their systems
work.
For information on the SCMS II configuration of SCSI tapes connected by a converter,
see 2.1.7.
6.5. SAN Addressing
Each port on a fabric switch has a dynamically assigned 24-bit port address, N_Port ID,
which is the basis for routing data packets across the Fibre Channel connections.
The 24-bit port address is broken into three fields, each one byte long.
Table 6–3. 24-Bit Port Address Fields
Bits 23-16 Bits 15-08 Bits 07-00
Domain Area (Port) Port (AL_PA)
• Domain
Each switch in a fabric has a unique domain value. There are 239 allowable switch
values (some values are reserved). In a single switch SAN environment, the value
is always constant. In a multiswitch environment, a unique domain value is
assigned when the switch connects to the SAN. All devices connected to the
switch have the same domain value.
• Area (most documents call it the Port field)
The values are determined by which port on the switch is connected to the node
of the storage device.
• Port (most documents call it the AL_PA field)
For non-fabric-capable devices on an arbitrated loop, the values used are the
AL_PA values.
6–10 3839 6586–010

Storage Area Networks
Note: The Domain, Area, and Port terms are “official” names for these parts of the
field. However, most people and documents use the terms in parentheses. See
below for a description. In this document, the terms are the ones that are most
commonly used, not the official names.
For fabric-capable devices, the switch assigns a value that varies depending on the
switch vendor.
Addressing Conventions
ClearPath Plus servers and their storage can connect to SANs controlled by Brocade
or McData switches. The switch vendors have some different addressing conventions.
The switches cannot interoperate within the same SAN.
• Brocade
Port 0 has a port value of x’00’. Port 1 has a value of x’01’. Port 12 has a port value
of x’0C’, and so on.
The AL_PA value for all fabric-ready devices is x’00’.
• McData
Older McData switches have a port offset of 4. Port 0 has a port value of x’04’.
Port 1 has a value of x’05’. Port 12 has a value of x’00’, and so on.
The newer McData switches (for example, ED10000, 4400, 4700) do not have the
port offset. Port 0 has a port value of x’00’. Port 1 has a value of x’01’. Port 12 has a
value of x’0C’, and so on.
The AL_PA value for both older and newer McData switches for all fabric-ready
devices is x’13’.
• T7840A, T9840B, T9840C, and T9940B
Select soft addressing on the device: “HARD PA=N.” The tape device port has a
different AL_PA value depending on the switch vendor.
6.5.1. OS 2200 Addressing
OS 2200 with Exec levels earlier than 48R4 only support 12-bit San addressing. With
Exec level 48R4 or greater 24-bit addressing is supported on the SCIOP and SIOP. It is
not support in any level for the CSIOP. The 12-bit addressing has two addressing
restrictions in a SAN environment, but neither is significant. SCMS II and OS 2200 can
access devices within a SAN, either on the same switch or on different switches. With
proper zoning, there is no practical limit to the number of storage devices that can be
accessed by a ClearPath Plus server.
Static Addressing
SAN environments operate in dynamic mode. When a storage device is added to the
network or changes location, the hosts can recognize the new address without
rebooting. OS 2200 requires a static address. Any storage device that changes
locations or the addition of a new storage device requires a reconfiguration of SCMS II
and a reboot of OS 2200.
3839 6586–010 6–11

Storage Area Networks
12-Bit Addressing (CSIOP) or (SIOP/SCIOP with Exec early than 48R4)
SAN addressing is based on a 24-bit field but OS 2200 only uses the last 12 bits on
CSIOP or SIOP/SCIOP with Exec levels early than 48R4: the last 4 bits of the port field
and the 8 bits of the AL_PA field. The upper 12 bits must be configured to 0 using
SCMS II if 24-bit addressing is not supported by the OS2200.
SCMS II is configured with the last 12 bits of the storage device address. When the
ClearPath Plus server initiates an I/O, OS 2200 sends the host channel adapter the 12bit
address. The channel adapter then sends the 12 bits to the SAN Name Server,
which contains information about other devices in the SAN. The channel adapter asks
the Name Server to send back the 24-bit address of the storage device that has the
last 12 bits of its address equal to the 12 bits supplied by the channel adapter. The
Name Server responds with the first match it finds. The channel adapter then builds
the proper 24-bit address and the I/O operation is requested of that storage device.
It is possible that one or more devices have equal values for the last 12 bits, which
could cause OS 2200 to address the wrong device. However, this potential problem
can easily be avoided by proper zoning. See 6.6 for more information.
24-Bit Addressing (SIOP/SCIOP with Exec 48R4 or greater)
OS2200 with Exec level of 48R4 or greater supports a 24-bit SAN address for a SCIOP
or SIOP. A 24-bit SAN address is not supported for CSIOP.
6.5.2. SCMS II
In SCMS II, when a control unit (CU) is highlighted, the Property and Property Value is
displayed in the middle of the page. For each CU, the properties are Domain, Area, and
Address.
If 24-bit addressing is not supported by the OS2200 the Domain should be set to 0 and
the upper 4 bits of the Area should be set to 0.
For arbitrated loops, the control unit address is the decimal equivalent of the AL_PA
value. For example, the AL_PA value x’EF’ is decimal 239 and, for this, CU the following
are set:
Domain: 0
Area: 0
Address: 239
For fabric configurations, the CU address is the decimal equivalent of the Domain plus
Area plus Address. For example, a device connected to port 4 of a Brocade switch
would have the following properties set:
Domain: 0
Area: 4
Address: 0
6–12 3839 6586–010

Some examples of devices converted to SCMS II values are as follows:
• Device on an arbitrated loop: AL_PA x’E8’. SCMS II values are
Domain: 0
Area: 0
Address: 232
Storage Area Networks
• Arbitrated loop device in a SAN: Port x’0C’ AL_PA x’EF’. SCMS II values are
Domain: 0
Area: 12
Address: 239
• Fabric-ready device on a Brocade switch: Port x’1F”, AL_PA x’00’. SCMS II values
are
Domain: 0
Area: 15
Address: 232
• Fabric-ready device on a McData switch: Port x’04’, AL_PA x’13’. SCMS II values
are
Domain: 0
Area: 4
Address: 19
6.5.3. OS 2200 Console
OS 2200 messages display the control unit address in decimal, based on the value in
SCMS II. For arbitrated loops, it is the three-digit value configured in SCMS II.
For fabric environments, the address displayed is calculated (in decimal) from the value
in SCMS II. The formula used is as follows:
(last 4 bits of the port x 256) + AL_PA value
For example, a non-fabric-capable device in a SAN configured in SCMS II as Area = 12,
Address = 239 would be displayed in a console message as 3311 ((12 x 256) + 239).
(The last 12 bits of the address displayed in the switch would be x’CEF’.)
An example used earlier was a fabric-capable device on a McData switch: Port x’04’,
AL_PA x’13’. The SCMS II values are Area = 04 and Address = 019. The value displayed
on a console would be 1043 ((4 x 256) + 19).
3839 6586–010 6–13

Storage Area Networks
FS keyins can return the Exec value. For example, if you want to find the port
associated with a channel
• Key in FS IOOC12//T99C
• Response is IOOC12/1043/T99C UP
Appendix B, “Fabric Addresses,” contains tables for both Brocade and McData
switches, showing the relationship between port addresses, SCMS II values, and Exec
path values.
6.5.4. SAN Addressing Examples
This section contains both 12-bit and 24-bit SAN addressing examples.
12-bit SAN Addressing Example
Here is an example of devices connected to a Brocade switch and their resulting
addresses. Table 6–4 and Figure 6–5 only show one switch. Most sites build in
redundancy and have a second switch that can access the devices. In this example,
assume that the storage device drives connect to two switches but the connections
to only one switch are shown.
Devices 0 through 3 are non-fabric-capable JBOD disks connected to an arbitrated
loop. Since they are on the same loop, each AL_PA must be unique.
Devices 4, 5, and 6 are T9840As. They are arbitrated loop devices, connected to the
Brocade switch in QuickLoop mode. Since they are on the same loop, they have
different AL_PA values. These drives, along with a host channel, are in the same zone.
Devices 7 and 8 are T9840Bs. They are running in switched fabric mode. They are
zoned together, along with a host channel.
Device 9 is a Symmetrix disk system with three connections to the switch.
Device 10 is a CLARiiON disk system. It has one connection to the switch.
Device
in the
Example
Table 6–4. 12-bit SAN Addressing Example
Full Fabric Address
Domain Port AL_PA
SCMS II
Address
0 01 0F EF Area = 15
Address = 239
1 01 0F E8 Area = 15
Address = 232
2 01 0F E4 Area = 15
Address = 228
OS 2200
Display
6–14 3839 6586–010
4079
4072
4068

Device
in the
Example
Table 6–4. 12-bit SAN Addressing Example
Full Fabric Address
Domain Port AL_PA
Storage Area Networks
SCMS II
Address
3 01 0F E2 Area = 15
Address = 226
4 01 0D EF Area = 13
Address = 239
5 01 0C E8 Area = 12
Address = 232
6 01 0B E4 Area = 11
Address = 228
7 01 09 00 Area = 09
Address = 000
8 01 08 00 Area = 08
Address = 000
9 01 06 00 Area = 06
Address = 000
01 05 00 Area = 05
Address = 000
01 04 00 Area = 04
Address = 000
10 01 00 00 Area = 00
Address = 000
See the following figure for a diagram of a Brocade switch.
OS 2200
Display
3839 6586–010 6–15
4066
3567
3304
3044
2304
2048
1536
1280
1024
0

Storage Area Networks
24-bit SAN Addressing Example
Figure 6–5. Brocade Switch
The following table is an example of 24-bit SAN addressing feature. This feature is
supported by OS 2200 with Exec level of 48R4 and later when connected to SIOPs or
SCIOPs.
Table 6–5. 24-bit SAN Addressing Example
Domain Area AL-PA SCMS II Address OS 2200 Display
FF FF FF 255-255-255 16777215
01 0F E8 001-015-232 69608
BC AE AC 188-174-172 12365484
05 07 08 005-007-008 329480
6–16 3839 6586–010

6.6. Zoning
Storage Area Networks
An enterprise Storage Area Network (SAN) can be very complex, containing multiple
switches, heterogeneous host systems, and storage systems. Zoning is a way to
partition the environment and create a virtual private network within the SAN.
The primary advantage of zones is security. It protects the devices in the zone from
being accessed by other platforms in the SAN that are not part of that zone.
Zones are not configured in SCMS II or recognized by OS 2200.
6.6.1. Zoning and 12-Bit OS 2200 Addressing
OS 2200 12.0 with Exec level of 48R4 supports 24-bit SAN addressing when
connected to SIOPs or SCIOPs. The 24-bit SAN addressing feature is not supported
when connected to CSIOPs. If 24-bit addressing is not supported, unique 24-bit port
addresses can appear the same to OS 2200. OS 2200 is only aware of the last 12 bits
of the 24-bit port address for ClearPath Plus storage devices. You must ensure that all
devices that are accessible from a ClearPath Plus server channel have addresses such
that the last 12 bits of the address are unique.
Zoning makes this easy. Zoning creates subsets within the SAN. The requirement for
uniqueness only needs to be satisfied for all devices within that zone. A device in one
zone can have the same 12-bits in its address as a device in a different zone and not
cause a problem for OS 2200.
Here are situations that increase the chance of having port addresses with the same
last 12 bits. Be aware so that you do not configure devices in the same zone with the
same OS 2200 address:
• Switches with more than 16 ports
The Port field is two hexadecimal characters. However, SCMS II only knows the
last one: Port 02 appears the same as Port 12.
• Multiple switches
Each switch in a SAN has a unique Domain value; however, OS 2200 does not see
the Domain field. In SCMS II, the address for Port 02 on Switch 01 is the same as
Port 02 on Switch 04.
• Multiple switches with more than 16 ports
Port 1A on Switch 02 has the same SCMS II address as Port 0A on Switch 01.
6.6.2. Guidelines
The simplest (and recommended) method of zoning is port-based zoning. You can say
“Only allow devices on switch 01, port 01 to talk to the storage device on switch 13,
port 04.”
Hard zoning is preferred over soft zoning.
World Wide Name (WWN) zoning is not recognized by OS 2200. If you move OS 2200
storage devices within the switch or the SAN, you have to rebuild SCMS II.
3839 6586–010 6–17

Storage Area Networks
Put each ClearPath Plus server channel into its own zone. Include all the connections
to the storage devices that can access that host channel. This ensures that only one
initiator logs in to the zone and there is no contention for the targets. This is
sometimes called single-HBA zoning.
Zones for ClearPath Plus servers and their storage devices should not contain any
foreign hosts or devices. Do not include UNIX or Windows hosts or storage devices.
Arbitrated loop devices, such as the T9840A, must be zoned with similar devices. They
must be in separate zones from devices running in fabric mode.
6.6.3. Zoning Disks
Figure 6–6 is an example of two ClearPath Plus servers and their disks separated by
zones. Zone A is dedicated to one host and Zone B is dedicated to the other. The
middle set of disks is an example of a multihost file sharing (MHFS). The disks are
accessible from each host.
Figure 6–6. Zoning
6–18 3839 6586–010

6.6.4. Zoning with Multiple Switches
Storage Area Networks
Figure 6–7 is an example of a single host or partition accessing an EMC subsystem
through two switches. Each host channel is in its own zone. Note that each EMC
interface port is in two zones.
Figure 6–7 shows a 2:1 fanout, two host OS 2200 channels connected to one EMC
interface port. This is commonly done when the OS 2200 host channel is rated at a
slower speed than the EMC interface port (1 Gb to 2 Gb). The newer OS 2200 Fibre
Channels are rated up to 2 Gb and 4 Gb, so you might not need to consider a fanout.
Figure 6–7. Zoning with Multiple Switches
3839 6586–010 6–19

Storage Area Networks
6.6.5. Multihost or Multipartition Zoning
Many sites can share tape drives between two or more ClearPath Plus servers or
between partitions on the same host. The zoning recommendation is the same as it is
for a single host: each host channel and all the tape drives it can access are in one
zone. Figure 6–8 is for separate hosts but it also applies to separate partitions.
Figure 6–8 has Host 1 with two zones: W can access the A port of both tape drives
and Y can access the B ports of both tape drives. Host 2 has zones X and Z with
similar access to the ports of the tape drives.
Figure 6–8. Multihost Zoning
6–20 3839 6586–010

6.6.6. Remote Backup Zoning
Storage Area Networks
Many customers have a primary production site and a backup facility. They utilize
switches in the primary site to connect through an ISL to switches in the backup
location. Figure 6–9 is a simplified representation of this configuration.
Figure 6–9. Remote Backup
At a real site, there would be at least one more switch at the primary and the backup
location. This is simplified to make the picture easier to understand. Some comments
on the configuration include
• There are two zones. Each zone is a single-HBA zone.
• SCMS II for the production system is configured with the address of one control
unit as 04-xxx and the address of the second control unit address as 05-xxx. The
port address of any host connection is not configured in SCMS II and neither is the
ISL. The rightmost digit of the port address for the host or the ISL could be the
same value as the rightmost digit of the port address of the mass storage device.
This would not cause any confusion in SCMS II.
3839 6586–010 6–21

Storage Area Networks
6–22 3839 6586–010

Section 7
Peripheral Systems
This section provides information about the peripherals supported on these servers.
See Section 9 for a list of supported and unsupported peripherals.
Technology enhancements can rapidly make the information in this document out of
date. For current information on Unisys storage, see the following URL:
http://www.unisys.com/products/storage/
7.1. Tape Drives
7.1.1. LTO
The following are the supported tape drives.
Linear Tape Open (LTO) is an open format technology.
The drives connect to a 2-Gb Fibre Channel using Lucent Connectors. The drives
provide two ports for Fibre Channel connections. As with all tape devices, they can be
used to provide redundant paths within a single system or for sharing devices
between systems or partitions, but only one system or one path at a time can be
using the device.
The drive supports tape buffering. It has 128 MB of cache.
LTO Generation 4 (Ultrium 4)
Generation 4 has the following characteristics:
• Native capacity of 800 GB per cartridge
• Compressed capacity of 1600 GB per cartridge
• Sustained data transfer rate of 120+ MB per second with LTO Gen 4 media
• Read/write Ultrium 3 (Gen3) cartridges
• Read Ultrium 2 (Gen2) cartridges
ClearPath OS 2200 Release 11.3 introduced support for the StorageTek Linear Tape
Open (LTO4-HP tape subsystem). With the ClearPath OS 2200 Release 11.3, the LTO4-
HP is configured as a LTO4-SUBSYS tape subsystem.
3839 6586–010 7–1

Peripheral Systems
Caution
Unisys supports LTO tape drives for audit devices. However, before
configuring a Step Control type audit trail to use either the LTO3-HP or
LTO4-HP drives, you should consider the potential impact on the
application’s recovery time. Application recovery times can be significantly
impacted depending upon the location (on the tape) of the recovery start
point and the number of LBLK$ operations required to position the tape
during recovery. Application programs, thread duration, audit volume, AOR
action, and TCDBF checkpoints will affect tape positioning and could push
the combined Exec and IRU short recovery times beyond fifteen minutes.
The LTO4-HP tape subsystem can be used either in a library or in a freestanding
environment. The subsystem supports both SCSI (Ultra 320) and fibre channel
connections to the host; however, OS 2200 systems only support the fibre channel.
As required by the LTO4-HP subsystem can write to Ultrium 3 and Ultrium 4 cartridge
media. A Generation 4 subsystem can read Ultrium 2 cartridges, but cannot write to
them.
The Ultrium 3 media has an uncompressed capacity of 400 GB and a compressed
capacity of 800 GB. The Ultrium 4 media has an uncompressed capacity of 800 GB and
a compressed capacity of 1600 GB.
The Generation 4 subsystem uses the LTO-DC data compression format, which is
based on ALDC. The subsystem does not compress data that is already compressed.
The Ultrium 4 device transfers uncompressed data at 120 MB per second and
compressed data at 320 MB per second. The actual transfer rate is limited by the
channel connection and IOP type.
There are no density options. The Generation 4 subsystem writes at the density that is
appropriate for the media type being used.
Electronic partitioning (EP) is supported for the HP Ultrium 4 device.
The Generation 4 subsystem supports buffering, and Ultrium 4 devices include a
128-MB cache buffer. Both Tape Mark Buffering Phase I (BUFFIL) and Tape Mark
Buffering Phase II (BUFTAP) are supported.
The LTO specification requires that a device can read and write the current generation
format (Ultrium 4) and one previous format (Ultrium 3). For the Generation 4
subsystem, if an Ultrium 4 cartridge or Ultrium 3 cartridge is mounted, it can be read
and written. The Generation 4 subsystem cannot write to an Ultrium 2 cartridge, but it
can read from it.
7–2 3839 6586–010

Restrictions
Peripheral Systems
• Sort/Merge consideration
A tape volume for LTO4-HP tape subsystems can store up to 1600 GB or more of
compressed data. In the past, unless a NUMREC parameter was specified or
scratch files were explicitly assigned, the SORT processor assumed that tape files
would fill the tape volumes associated with the file. Based on that assumption,
the SORT processor would assign appropriately sized scratch files.
Because of the size of tape volumes for LTO4-HP tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or pass
a NUMREC or RECORD parameter to the SORT processor runstream.
LTO Generation 3 (Ultrium 3)
Generation 3 has the following characteristics:
• Native capacity of 400 GB per cartridge
• Compressed capacity of 800 GB per cartridge
• Sustained data transfer rate of 80+ MB per second with LTO Gen 3 media
• Read/write Ultrium 2 (Gen2) cartridges
• Read Ultrium 1 (Gen1) cartridges
ClearPath OS 2200 Release 11.0 introduced preliminary support for the StorageTek
Linear Tape Open (LTO3-HP tape subsystem). With the ClearPath OS 2200 Release
11.3, the LTO3-HP is configured as a LTO3-SUBSYS tape subsystem. With 11.3 you can
no longer configure the LTO3-HP as a LTO-SUBSYS tape subsystem.
Caution
Unisys supports LTO tape drives for audit devices. However, before
configuring a Step Control type audit trail to use either the LTO3-HP or
LTO4-HP drives, you should consider the potential impact on the
application’s recovery time. Application recovery times can be significantly
impacted depending upon the location (on the tape) of the recovery start
point and the number of LBLK$ operations required to position the tape
during recovery. Application programs, thread duration, audit volume, AOR
action, and TCDBF checkpoints will affect tape positioning and could push
the combined Exec and IRU short recovery times beyond fifteen minutes.
The LTO3-HP tape subsystem can be used either in a library or in a freestanding
environment. The subsystem supports both SCSI (Ultra 320) and fibre channel
connections to the host; however, OS 2200 systems only support the fibre channel.
As required by the LTO3-HP subsystem can write to Ultrium 2 and Ultrium 3 cartridge
media. A Generation 3 subsystem can read Ultrium 1 cartridges, but cannot write to
them.
3839 6586–010 7–3

Peripheral Systems
The Ultrium 2 media has an uncompressed capacity of 200 GB and a compressed
capacity of 400 GB. The Ultrium 3 media has an uncompressed capacity of 400 GB and
a compressed capacity of 800 GB.
The Generation 3 subsystem uses the LTO-DC data compression format, which is
based on ALDC. The subsystem does not compress data that is already compressed.
The Ultrium 3 device transfers uncompressed data at 80 MB per second and
compressed data at 160 MB per second. The actual transfer rate is limited by the
channel connection and IOP type.
There are no density options. The Generation 3 subsystem writes at the density that is
appropriate for the media type being used.
Electronic partitioning (EP) is supported for the HP Ultrium 3 device.
The Generation 3 subsystem supports buffering, and Ultrium 3 devices include a
128-MB cache buffer. Both Tape Mark Buffering Phase I (BUFFIL) and Tape Mark
Buffering Phase II (BUFTAP) are supported.
The LTO specification requires that a device can read and write the current generation
format (Ultrium 3) and one previous format (Ultrium 2). For the Generation 3
subsystem, if an Ultrium 3 cartridge or Ultrium 2 cartridge is mounted, it can be read
and written. The Generation 3 subsystem cannot write to an Ultrium1 cartridge, but it
can read from it.
Restrictions
• Encryption is not supported.
• You must configure the devices as LTO3-SUBSYS tape subsystems, you can no
longer configure the devices with the LTO-SUBSYS subsystem.
• Sort/Merge consideration
A tape volume for LTO3-HP tape subsystems can store up to 800 GB or more of
compressed data. In the past, unless a NUMREC parameter was specified or
scratch files were explicitly assigned, the SORT processor assumed that tape files
would fill the tape volumes associated with the file. Based on that assumption,
the SORT processor would assign appropriately sized scratch files.
Because of the size of tape volumes for LTO3-HP tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or pass
a NUMREC or RECORD parameter to the SORT processor runstream.
7–4 3839 6586–010

OS 2200 Implementation
The following are the OS 2200 supported features:
• Fibre Channel support only
• Assign mnemonic of LTO, LTO3, LTO4
Peripheral Systems
• Data Compression mnemonic of CMPON (LTO-DC compression based on ALDC)
• Electronic Partitioning is supported
• Buffering: supports BUFON, BUFFIL, and BUFTAP
• Boot device and dump device are supported
The following is an OS 2200 configuration consideration:
In SCMS II, configure as LTO3-SUBSYS or LTO4-SUBSYS tape subsystem.
The following are the OS 2200 restrictions;
• Devices do not have LED displays; the load display commands are not supported.
• Limited distribution of OS 2200 System Releases on LTO Media. OS 2200 system
releases for Dorado 400, 4000, 4100, and 4200systems are shipped on CD/DVD.
Approved Vendors
The following vendors have had their drives qualified on the Dorado Series. No other
vendors have been qualified.
DSI Alpine ALP63
Single-drive or dual-drive configurations are available in rack mount Fibre Channel
configurations and with a 30-cartridge Fibre Channel auto-cartridge loader (ACL).
Models other than ALP63-FAS/FAD require SAN switch connectivity.
StorageTek LTO4-HP and LTO3-HP Library Tape Drives
The LTO tape drive can be configured in the SL8500, L1400, L700, L180, and SL3000
libraries.
7.1.2. T9840D Tape Subsystem
The T9840D tape technology provides for higher density compared to 18 and 36-track
tapes and almost twice the capacity of the T9840C. The maximum data capacity per
cartridge supported by the T9840D is 75GB uncompressed compared to 40GB for the
T9840C. The high density T9840D writes 576 tracks on a tape. The T9840D is three
times faster that the T9840A, 1.6 times faster than the T9840B, and as fast as the
T9840C. The new drive accepts the same medium as the T9840A, T9840B and
T9840C.
3839 6586–010 7–5

Peripheral Systems
The T9840D tape subsystem attaches to the ClearPath OS2200 series systems using a
SCSI Fibre (SCSI) channel interface. The T9840D tape subsystem can either be
included in the STK tape libraries or in a standalone environment. Although the
T9840D drive uses a half-inch cartridge tape, the T9840D tape is not interchangeable
with the cartridge tape used by 18-track, 36-track, U9940, T10000A, DLT, or LT03-
HP/LTO4-HP tape drives or vice versa. The Exec provides unique equipment
mnemonics for configuring the subsystem T9840D and a unique specific assignment
mnemonic ‘HIS98D’ for assigning tape files. Due to media incompatibility, any of the
existing file assignment mnemonics that are available today for the half-inch cartridge
tape assignment, except ‘T’ mnemonic, should not be used to assign a T9840D tape
drive. For more information on mnemonics, see Section 9.6.
The T9840D uses the existing CSC (Client System Component) library feature when
included in the tape libraries. The tape device driver is supported within the Exec
using the same handlers as its predecessors. Other features provided by the T9840D
that are supported by the Exec include LED display, operator tape cleaning message,
LZ1 data compression, fast tape access, and extended buffer mode. The T9840D is
supported by the Exec as a boot device and system dump device. The T9840D may
also be used for checkpoint and restart and may be used as an Audit Trail device.
Checkpoint can assign the T9840D tape device via the new file assignment mnemonic
‘HIS98D’ or via the generic file assignment mnemonic, ‘T’. Restart can assign the
T9840D tape devices via the new file assignment mnemonic ‘HIS98D’
Restrictions
• Sort/Merge consideration—A tape volume for T9840D tape subsystems can store
up to 150 GB or more of compressed data. In the past, unless a NUMREC
parameter was specified or scratch files were explicitly assigned, the SORT
processor assumed that tape files would fill the tape volumes associated with the
file. Based on that assumption, the SORT processor would assign appropriately
sized scratch files.
Because of the size of tape volumes for T9840D tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or pass
a NUMREC or RECORD parameter to the SORT processor runstream.
7.1.3. T10000A Tape System
The T10000A (T10K) new capacity tape technology is an extension to Sun’s current
StorageTek T9940B tape drives (single spool, serpentine cartridge) and 2.5 times the
capacity of the T9940B. The maximum data capacity per cartridge supported by the
T10000A is 500GB uncompressed compared to 200GB for the T9940B. (There is also a
Sport cartridge available with 120GB, but currently there is no way to internally
determine which is mounted on the drive.)
7–6 3839 6586–010

Peripheral Systems
The low density T10000A writes 768 tracks on a tape. The T10000A is four times
faster than the T9940B. The new drive is designed to accept only a unique 2,805-foot
half-inch cartridge tape (for standard T10000A) that contains T10000A specific servo
information. Therefore, the tape should never be degaussed; it cannot be used once it
has been degaussed unless the servo information is restored at the factory.
The T10000A tape subsystem attaches to the ClearPath OS2200 series systems using
a SCSI Fibre (SCSI) channel interface. The T10000A tape subsystem can either be
included in the STK tape libraries or in a standalone environment. Although the
T10000A drive uses a half-inch cartridge tape, the T10000A tape is not interchangeable
with the cartridge tape used by 18-track, 36-track, U9840, U9940, DLT, or LT03-
HP/LTO4-HP tape drives or vice versa. The Exec provides unique equipment
mnemonics for configuring the subsystem T10000A and a unique specific assignment
mnemonic ‘T10KA’ for assigning tape files. Due to media incompatibility, any of the
existing file assignment mnemonics that are available today for the half-inch cartridge
tape assignment, except ‘T’ mnemonic, should not be used to assign a T10000A tape
drive. For more information on mnemonics, see Section 9.6.
The T10000A uses the existing CSC (Client System Component) library feature when
included in the tape libraries. The tape device driver is supported within the Exec via
the same handlers as its predecessors. Other features provided by the T10000A that
are supported by the Exec include operator tape cleaning message, LZ1 data
compression, fast tape access, and extended buffer mode. The T10000A is supported
by the Exec as a boot device and system dump device. The T10000A can also be used
for checkpoint and restart and may be used as an Audit Trail device.
Checkpoint can assign the T10000A tape device using the new file assignment
mnemonic ‘T10KA’ or using the generic file assignment mnemonic, ‘T’. Restart can
assign the T10000A tape devices using the new file assignment mnemonic ‘T10KA’.
LED display for the T10000A is not supported by the Exec due to the hardware
limitation. The T10000A drive itself does not have an LED. However if you order a
rack-mount device, the rack itself does include a display. There is no display for library
drives, you must use Virtual Operator Panel (VOP) software to control the drive.
Restrictions
• Sort/Merge consideration—A tape volume for T10000A tape subsystems can
store up to 1000 GB or more of compressed data. In the past, unless a NUMREC
parameter was specified or scratch files were explicitly assigned, the SORT
processor assumed that tape files would fill the tape volumes associated with the
file. Based on that assumption, the SORT processor would assign appropriately
sized scratch files.
Because of the size of tape volumes for T10000A tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or pass
a NUMREC or RECORD parameter to the SORT processor runstream.
3839 6586–010 7–7

Peripheral Systems
7.1.4. T9840D and T10000A Applicable
The T9840D and T10000A support AES256 encryption supported by the SUN Crypto
Key Management Station (KMS). Currently all devices of a particular type must be
encryption capable or have encryption disabled.
The T9840D and T10000A tape devices are supported by all Dorado systems.
BUFFIL (buffering of tape file marks) is supported by T9840D and T10000A.
BUFTAP (Tape Mark Buffering Phase II) is supported by T9840D and T10000A.
The Media Manager ILES (MMGR) and the Exec Media Manager code are modified to
support the T9840D and T10000A tape devices. New bits are added in the TIF record
and MMI work buffer to represent the T9840D and T10000A devices and the new
density values. The addition of the T9840D and T10000A add other devices as the
eighth and ninth type of media (for example, open-reel, 18/36-track, DLT, LTO3-
HP/LTO4-HP, T9840A, T9940, U9840C, T9840D and T10000A cartridge). The existing
media is represented by open-reel, half-inch cartridge, T9840A, T9940B, U9840C,
T9840D, DLT, LTO3-HP/LTO4-HP, and T10000A cartridge. This design addresses nine
media types by having MMGR return different statuses for each media type when a
media incompatibility is found.
The following table provides a summary of the features that are supported within the
Exec for T9840D and T10000A tape devices (Y=yes, the feature/capability is
supported; N=no, the feature/capability is not supported; NA=not applicable, the
feature/capability does not apply because it is not supported by the vendor)
Table 7–1. Supported Features for the T10000A and T9840D Tape Devices
Features/Capabilities Supported by the Exec Fibre- T9840D Fibre T10000A
LZ1 data compression Y Y
Fast Tape Access Y Y
Enhanced Statistical Information (ESI) logging 1 Y (1216 log entry) Y (1216 log entry)
Expanded Buffer (256K bytes maximum) Y Y
Enabling/Disabling buffered mode Y Y
Audit Trail capable Y Y
Auto-loader in AUTO mode NA NA
Auto-loader in MANUAL mode NA NA
Auto-loader in SYSTEM mode NA NA
ACS library support Y Y
Electrical Partitioning Y Y
LED display Y N
Tape Mark Buffering (BUFFIL) Y Y
7–8 3839 6586–010

Peripheral Systems
Table 7–1. Supported Features for the T10000A and T9840D Tape Devices
Features/Capabilities Supported by the Exec Fibre- T9840D Fibre T10000A
Tape Mark Buffering Phase II (BUFTAP) Y Y
Operator clean message Y Y
Media manager support Y Y
CKRS support Y Y
1 Tape Alert Log Sense page is saved in the ESI log entry.
7.1.5. T9940B Tape Subsystem
T9940B tape subsystems connect to ClearPath systems server channels through Fibre
Channel (FC) SCSI channels. T9940B tape subsystems are used in STK tape libraries.
The T9940B uses the existing Client System Component (CSC) library feature when it
is included in tape libraries (this version of CSC still uses the STK$ Executive request).
The tape device driver is supported within the Exec through the SCSITIS separately
packaged Exec feature when the T9940B attaches to the host through FCSCSI
channels.
T9940B tape subsystems provide a maximum capacity per cartridge of 200 GB of
uncompressed data. The tape subsystems use the LZ1 data compression algorithm
that can improve capacity by factors of 2 and greater. However, individual results
might vary depending on characteristics of the data and other variables.
The tape cartridges use half-inch tape. These cartridges are not interchangeable with
cartridges used with 18-track, 36-track, DLT, T9840A, T9840B, or T9840C tape drives.
The Exec provides unique equipment mnemonics for configuring the subsystem and a
unique specific assign mnemonic for assigning tape files. Other than generic assign
mnemonic T, existing assign mnemonics used to assign 1/2-inch cartridge tapes
cannot be used to assign T9940B tape drives. For more information on mnemonics,
see 9.6 Device Mnemonics.
The Exec supports T9940B tape subsystems as boot devices, system dump devices,
audit trail devices, and for checkpoint/restart. Checkpoint can assign T9940B tape
devices with the new assign mnemonic HIS99B, or the more generic assign
mnemonic T. Restart can assign T9940B tape devices with the new assign mnemonic,
HIS99B.
3839 6586–010 7–9

Peripheral Systems
Considerations for using the T9940B tape subsystem are as follows:
• Tape used by the T9940B has a native capacity of 200 GB. This is 120.5 times the
capacity of an E-cart 1100-foot cartridge written in 36-track format.
Cautions
• Do not degauss 9940B tapes. Servo tracks are written on the tape at
the factory. When these tracks are mistakenly erased, the tape
cartridge must be discarded.
• If you drop a 9940B tape cartridge from a height of less than 1 meter,
the cartridge is warranted to continue to read and write new data, but
the media life might be shortened. Therefore, Unisys recommends that
you copy data from a dropped cartridge to another cartridge and retire
the dropped cartridge. Because the compressed capacity could be 400
GB per cartridge or greater, the importance of protecting cartridges
from being dropped cannot be overstated.
• In order to crossboot to previous Exec levels that do not support a new device
type, you must use a partitioned data bank (PDB) that does not contain the new
device type. Products that are sensitive to new device equipment mnemonics and
file assignment mnemonics can be affected.
• Read backward I/O functions are not supported. If a read backward is attempted,
it is terminated with an I/O error status of 024 (octal).
• T9940B tapes are not compatible with any other ClearPath system tape device.
• T9940B tape subsystems cannot read traditional 9-track, 18-track, 36-track, DLT, or
T9840A formatted tapes. To read these tapes and transfer the data to a T9940B
tape subsystem, you must have a tape device on the host system that can read
9-track, 18-track, 36-track, DLT, or T9840A/B formatted tapes. You can then
transfer the data to the T9940B tape subsystem.
• The function of general assign mnemonic T is expanded so that it can be used
with T9940B tape subsystems.
• Using ACS names as assign mnemonics is not supported for T9940B tape
subsystems. You should use assign mnemonic HIS99B (or absolute device assign)
when assigning T9940B tape drives. If an ACS name is specified in a tape
assignment statement, the Exec attempts to assign only 1/2-inch cartridge tape
drives (for example, HIC, HICL) available in ACS.
• An LED indicator on a tape device lights when the drive needs cleaning or the tape
is bad. The operator clean message on the system console is also supported for
the T9940B. When T9940B tape subsystems are part of a tape library, the
Automated Cartridge System Library Software (ACSLS) should be set to
autocleaning-enabled mode. This enables ACSLS and the library to perform the
cleaning.
7–10 3839 6586–010

Peripheral Systems
• The following products or features are required to support T9940B tape
subsystems:
− Client System Component (CSC) library product supports the library
configuration for T9940B tape subsystems.
− SCSITIS separately packaged Exec feature must be installed in order to
configure T9940B tape drives.
− TeamQuest MSAR level 7R1A (or higher) and TeamQuest LA level 7R1 (or
higher) are required to support the T9940B tape subsystem.
• Sort/Merge consideration
A tape volume for T9940B tape subsystems can store up to 400 GB or more of
compressed data. In the past, unless a NUMREC parameter was specified or
scratch files were explicitly assigned, the SORT processor assumed that tape files
would fill tape volumes associated with the file. Based on that assumption, the
SORT processor would assign appropriately sized scratch files.
Because of the size of tape volumes for T9940B tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or
passing a NUMREC or RECORD parameter to the SORT processor runstream.
• Audit device consideration
There are no technical restrictions on using the T9940B tape subsystem as audit
devices. However, there are some practical considerations. These devices have a
much larger capacity than any current audit device. They take a lot longer to fill
than previous tapes. If filled, they take a lot longer to read. Some recovery
mechanisms are able to use block-IDs of the fast tape access feature to reach the
recovery start point in a reasonable timeframe. Other recovery mechanisms
cannot use block-IDs, and must read all the data on the tape to perform the
recovery. If the tape is full, this might take more than a reasonable amount of time.
Use the following considerations to minimize recovery time when using T9940B
tape subsystems as audit devices:
− Always set the IRU configuration parameter USE-LOCATE-BLOCK to TRUE.
− Make sure the run-ID executing recovery has Fast Tape Access privileges.
− Remember that a long recovery from a TBSN or point in time reads each block
from the beginning of the tape looking for the start point. A history file
directed recovery following a reload is a recovery from a point in time.
− Consider swapping tapes before they are full. You have to balance the desire
for most efficient use of tape (generally filling each tape) with the desire for
speedy recoveries (which are faster if you can skip reading data that is not
required for recovery, but happens to reside on the same tape as the start
point) to find the best solution for your application.
3839 6586–010 7–11

Peripheral Systems
7.1.6. T9840A Tape Subsystem
T9840A tape subsystems connect to the ClearPath systems server channels through
single-byte command code set connection (SBCON), small computer system interface
(SCSI-2W or SCSI-ULTRA), or Fibre Channel (FC) SCSI channels. The T9840A can be
included in STK tape libraries or in a stand-alone environment.
The T9840A uses the existing Client System Component (CSC) library feature when it
is included in tape libraries (this version of CSC still uses the STK$ Executive request).
The tape device driver is supported within the Exec through the SCSITIS separately
packaged Exec feature when the T9840A attaches to the host through SCSI-2W,
SCSI-ULTRA, or FCSCSI channels, and the CARTLIB separately packaged Exec feature
when the T9840A attaches to the host through SBCON channels.
Note: Throughout this subsection, wherever SCSI T9840A is mentioned, FCSCSI
T9840A also applies.
T9840A tape subsystems provide a maximum capacity per cartridge of 20 GB of
uncompressed data. The tape subsystems use the LZ1 data compression algorithm
that can improve capacity by factors of 2 and greater. However, individual results
might vary depending on the characteristics of the data and other variables.
The tape cartridges use half-inch tape. These cartridges are not interchangeable with
cartridges used with 18-track, 36-track, or DLT tape drives.
The Exec provides unique equipment mnemonics for configuring the subsystem and a
unique specific assign mnemonic for assigning tape files. Other than the generic
assign mnemonic T, existing assign mnemonics used to assign 1/2-inch cartridge tapes
cannot be used to assign T9840A tape drives. For more information on mnemonics,
see 9.6 Device Mnemonics.
The Exec supports T9840A tape subsystems as boot devices, system dump devices,
for audit trails, and for checkpoint/restart. Checkpoint can assign T9840A tape devices
with the new assign mnemonic HIS98, or the more generic assign mnemonic T.
Restart can assign T9840A tape devices with the new assign mnemonic, HIS98.
Considerations for using the T9840A tape subsystem are as follows:
• The T9840A tape used by the T9840A has a native capacity of 20 GB. This is 12.5
times the capacity of an E-cart 1100-foot cartridge written in 36-track format.
7–12 3839 6586–010

Cautions
Peripheral Systems
• Do not degauss T9840A tapes. Servo tracks are written on the tape at
the factory. When these tracks are mistakenly erased, the tape
cartridge must be discarded.
• If you drop a T9840A tape cartridge from a height of less than 1 meter,
the cartridge is warranted to continue to read and write new data, but
the media life might be shortened. Therefore, Unisys recommends that
you copy data from a dropped cartridge to another cartridge and retire
the dropped cartridge. Because the compressed capacity could be 40
GB per cartridge or greater, the importance of protecting cartridges
from being dropped cannot be overstated.
• In order to crossboot to previous Exec levels that do not support T9840A tape
subsystems, you must use a partitioned data bank (PDB) that does not contain the
T9840A equipment mnemonic. Products that are sensitive to the new device
equipment mnemonics and file assignment mnemonics can be affected.
• Read backward I/O functions are not supported. If a read backward is attempted,
it is terminated with an I/O error status of 024 (octal).
• T9840A tapes are not compatible with any other ClearPath IX system tape device.
• Beginning with Exec level 46R6 (ClearPath OS 2200 Release 7.0), the 32-Bit Block
ID feature is introduced. This feature enables 32-bit block ID mode for all T9840A
tape subsystems that are connected through SBCON channels. The following
considerations apply to this feature:
− If the 32 Bit Block ID feature is not installed in the system, there is a difference
in the block number field size between T9840A SBCON and SCSI devices. The
difference is that T9840A SBCON devices use a 22 Bit block number and
T9840A SCSI devices use a 32 Bit block number. Because of this difference,
tapes that are generated on SCSI and SBCON drives have different
characteristics that result in operational difficulties.
− If the 32 Bit Block ID feature is installed in the system, the different
characteristics between the two different types of subsystems are eliminated.
Note that the microcode level in the T9840A subsystem must be equal to or
greater than RA.28.119e.
3839 6586–010 7–13

Peripheral Systems
Tape
Format
IBM 9840
(32-bit
Block ID)
Unisys
9840
(22-bit
Block ID)
Unisys
9840
(32-bit
Block ID)
The following table shows the incompatibilities that can exist between the three
different types of tapes that can be created on T9840/3590 subsystems.
Table 7–2. SCSI and SBCON Compatibility Matrix
IBM
9840/SBCON
“3590 Mode”
(32-bit capable)
Read
Append
Unisys
9840/SBCON
(with feature)
(32-bit capable)
Read
Device Types
Append
Unisys
9840/SBCON
(without feature)
(22-bit capable)
Unisys
9840/SCSI or
FCSCSI
(32-bit capable)
7–14 3839 6586–010
Read
Append
Read
OK OK OK OK Error 1 Error 2 OK OK
OK up
to 22
bit
OK up
to 22
bit
Error OK OK OK OK OK OK
Error OK OK OK up
to 22
bit 3
OK up
to 22
bit 3
OK OK
Append
1 LBLK operation results in I/O error 03. For read, an existing operator error message “DEVERR” and
an I/O error status 012 is returned to the user with fault symptom code (FSC) in sense data = 33E7.
2 LBLK operation results in I/O error 03. For read, an existing operator error message “DEVERR” and
an I/O error status 012 is returned to the user with fault symptom code (FSC) in sense data = 33E8.
3 LBLK operation beyond 22-bit addressing results in I/O error 03. For read, an existing operator error
message “DEVERR” and an I/O error status 012 is returned to the user. Fault symptom code (FSC) in
sense data = 338A.
• T9840A tape subsystems cannot read traditional 9-track, 18-track, 36-track, or DLT
formatted tapes. To read these tapes and transfer data to a T9840A tape
subsystem, you must have a tape device on the host system that can read 9-track,
18-track, 36-track, or DLT formatted tapes. You can then transfer the data to the
T9840A tape subsystem.
• The function of the general assign mnemonic T is expanded so that it can be used
with T9840A tape subsystems.
• Using ACS names as assign mnemonics is not supported for T9840A tape
subsystems. You should use assign mnemonic HIS98 (or absolute device assign)
when assigning T9840A tape drives. If an ACS name is specified in a tape
assignment statement, the Exec attempts to assign only 1/2-inch cartridge tape
drives (for example, HIC, HICL) available in ACS.

Peripheral Systems
• An LED indicator on a tape device lights when the drive needs cleaning or the tape
is bad. The operator clean message to the system console is also supported for
the T9840A. When T9840A tape subsystems are part of a tape library, the
Automated Cartridge System Library Software (ACSLS) should be set to the
autocleaning-enabled mode. This enables the ACSLS and the library to perform the
cleaning.
• The following products or features are required to support T9840A tape
subsystems:
− The Client System Component (CSC) library product supports the library
configuration for T9840A tape subsystems.
− The SCSITIS and /or the CARTLIB separately packaged Exec features must be
installed in order to configure T9840A tape drives.
− TeamQuest MSAR level 6R1D (or higher) and TeamQuest LA level 6R4 (or
higher) are required to support T9840A tape subsystems.
• Sort/Merge consideration
A tape volume for T9840A tape subsystems can store up to 40 GB or more of
compressed data. In the past, unless a NUMREC parameter was specified or
scratch files were explicitly assigned, the SORT processor assumed that tape files
would fill the tape volumes associated with the file. Based on that assumption, the
SORT processor would assign appropriately sized scratch files.
Because of the size of tape volumes for T9840A tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or
passing a NUMREC or RECORD parameter to the SORT processor runstream.
7.1.7. T9840C Tape Subsystem
T9840C tape subsystems connect to ClearPath systems server channels through Fibre
Channel (FC) SCSI, SBCON, and FICON channels. T9840C tape subsystems can be used
in STK tape libraries.
T9840C tape subsystems use the existing Client System Component (CSC) library
feature when it is included in tape libraries (this version of CSC still uses the STK$
Executive request). The tape device driver is supported within the Exec through the
SCSITIS separately packaged Exec feature when the T9840C attaches to the host
through FCSCSI channels.
T9840C tape subsystems provide a maximum capacity per cartridge of 40 GB of
uncompressed data. Tape subsystems use the LZ1 data compression algorithm, which
can improve capacity by a factor of 2 and greater. However, individual results might
vary depending on characteristics of the data and other variables.
The tape cartridges use half-inch tape. These cartridges are not interchangeable with
the cartridges used with 18-track, 36-track, DLT, or T9940B tape drives.
3839 6586–010 7–15

Peripheral Systems
The Exec provides the unique equipment mnemonic U9840C for the device and the
existing control unit mnemonic CU98SC (SCSI) or CU98SB (SBCON) for configuring the
subsystem and the unique specific assign mnemonic HIS98C for assigning tape files.
Other than generic assign mnemonic T, existing assign mnemonics used to assign
1/2-inch cartridge tapes cannot be used to assign T9840C tape drives. For more
information on mnemonics, see 9.6 Device Mnemonics.
The Exec supports T9840C tape subsystems as boot devices, system dump devices,
and for checkpoint/restart. Checkpoint can assign tape devices with new assign
mnemonic HIS98C, or the more generic assign mnemonic T. Restart can assign
T9840C tape devices with new assign mnemonic, HIS98C.
Considerations for using T9840C tape subsystems are as follows:
• Tape used by the T9840C has a native capacity of 40 GB.
Caution
If you drop a 9840C tape cartridge from a height of less than 1 meter, the
cartridge is warranted to continue to read and write new data, but the
media life might be shortened. Therefore, Unisys recommends that you
copy data from a dropped cartridge to another cartridge and retire the
dropped cartridge. Because the compressed capacity could be 80 GB per
cartridge or greater, the importance of protecting cartridges from being
dropped cannot be overstated.
• In order to crossboot to previous Exec levels that do not support a new device
type, you must use a partitioned data bank (PDB) that does not contain the new
device type. Products that are sensitive to the new device equipment mnemonics
and file assignment mnemonics can be affected.
• Read backward I/O functions are not supported. If a read backward is attempted,
it is terminated with an I/O error status of 024 (octal).
• T9840C tape subsystems cannot read traditional 9-track, 18-track, 36-track, DLT, or
T9940B formatted tapes. To read these tapes and to transfer data to a T9840C
tape subsystem, you must have a tape device on the host system that can read
the 9-track, 18-track, 36-track, DLT, or T9940B formatted tapes. You can then
transfer the data to the T9840C tape subsystem.
• The function of general assign mnemonic T is expanded so that it can be used
with T9840C tape subsystems.
• Using ACS names as assign mnemonics is not supported for T9840C tape
subsystems. You should use assign mnemonic HIS98C (or absolute device assign)
when assigning T9840C tape drives If an ACS name is specified in a tape
assignment statement, the Exec attempts to assign only 1/2-inch cartridge tape
drives (for example, HIC, HICL) available in ACS.
• T9840C tape subsystems can read 9840A/9840B tape media, but cannot write to
the media.
7–16 3839 6586–010

Peripheral Systems
• An LED indicator on a tape device lights when the drive needs cleaning or the tape
is bad. The operator clean message to the system console is also supported for
T9840C tape subsystems. When T9840C tape subsystems are part of a tape
library, the Automated Cartridge System Library Software (ACSLS) should be set to
the autocleaning-enabled mode. This enables the ACSLS and library to perform the
cleaning.
• The following products or features are required to support T9840C tape
subsystems:
− Client System Component (CSC) library product supports the library
configuration for T9840C tape subsystems.
− SCSITIS separately packaged Exec feature must be installed in order to
configure T9840C tape drives.
− TeamQuest MSAR level 7R2A (or higher) and TeamQuest LA level 7R2 (or
higher) are required to support the T9840C tape subsystem.
• Sort/Merge consideration
A tape volume for T9840C tape subsystems can store up to 80 GB or more of
compressed data. In the past, unless a NUMREC parameter was specified or
scratch files were explicitly assigned, the SORT processor assumed that tape files
would fill the tape volumes associated with the file. Based on that assumption,
the SORT processor would assign appropriately sized scratch files.
Because of the size of tape volumes for T9840C tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a tape device
contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must
assign appropriately sized scratch files before calling the SORT processor or pass
a NUMREC or RECORD parameter to the SORT processor runstream.
T9840 Family Compatibility
The tape cartridges for the T9840 family are identical; however, there are some
incompatibilities between the T9840C-written tapes and the tapes written on the
earlier devices. The T9840C writes to cartridges at a high density, higher than the
other family members: T7840, T9840A, and T9840B. These members write at a low
density.
Reading Tape
• T9840C drives can read low-density tapes (created on T7840A, T9840A/B).
• Low-density drives cannot read high-density tapes (created on T9840C).
Writing Tapes—Appending Data
• T9840C drives cannot write to a low-density tape.
• Low-density drives cannot write to a high-density tape
3839 6586–010 7–17

Peripheral Systems
Writing Tapes—Beginning of Tape (BOT)
• T9840C drives can write over a low-density tape. Label checking is done. No error
message is generated.
• Low-density drives can write over a T9840C tape. The first write generates a
console message and data is destroyed. There can be multiple console messages.
7.1.8. T7840A Cartridge
The T7840A tape drive is the same as the T9840A tape drive with the same
performance characteristics. It is different from the T9840A in two areas. The T7840A
• Is fabric-capable and supports a 1-Gb fabric interface
• Only supports fabric connections; there is no support for SCSI or SBCON.
• Has a Standard Connector (SC).
Each T7840A drive has its own control unit. The control unit supports LZ1 hardware
data compression.
A single cartridge holds 20 GB (native) of data, averaging approximately 40 GB of
compressed data.
The T7840A has a midpoint load, an uncompressed data transfer rate of approximately
10 MB per second, and an average access time of less than 12 seconds.
The T7840A has no unique configuration parameters. It uses the same media as the
T9840A and T9840B. Tapes are fully interchangeable.
The assign mnemonic for the T7840A tape drive is HIS98.
See Section 4 for information on how to optimize performance of T7840A tape drives.
7.1.9. T9840B Cartridge
The T9840B supports SBCON and Fibre Channel connections.
• The Fibre Channel connection has a native 2-Gb Fibre Channel interface using a
Lucent Connector. It can support both public and private arbitrated loops as well
as fabric connectivity. The T9840B supports two ports. Both ports can access the
same host or different ones, but only one connection can be active at one time.
• There is only one SBCON connection. The T9840B should be run in 3490 mode
when setting the configuration of the tape drive on the front panel.
Each T9840B drive has its own control unit. The control unit supports LZ1 hardware
data compression.
A single T9840B cartridge holds 20 GB (native) of data, averaging approximately 40 GB
of compressed data.
The T9840B has a midpoint load, 19-MB (native)-per-second transfer rate and an
average of just 8 seconds search time.
The T9840B uses the same media as the T9840A and T7840A drives. Tapes created
on these drives are fully interchangeable.
7–18 3839 6586–010

The assign mnemonic for the T98840B tape drive is HIS98.
Peripheral Systems
See Section 4 for information on how to optimize performance of T9840B tape drives.
7.1.10. T9840A Cartridge
The T9840A tape is available with SCSI, SBCON, and Fibre Channel connectivity.
Note: The T9840A was the first member of the 9840 family. It was originally
known as the T9840. When the T9840B was released, the T9840 was renamed the
T9840A.
Each T9840A drive has its own control unit. The control unit supports LZ1 hardware
data compression.
The Fibre Channel connection supports two ports. Both ports can access the same or
different hosts, but only one connection can be active at one time. The T9840A has a
Standard Connector (SC).
There is only one SCSI connection.
There is only one SBCON connection from the T9840A. The T9840A should be run in
3490 mode when setting the configuration of the tape drive on the front panel.
The T9840A has a midpoint load, has an uncompressed data transfer rate of
approximately 10 MB per second, and has an average access time to data of less than
12 seconds.
The T9840A tape cartridge has an uncompressed capacity of 20 GB, averaging
approximately 40 GB of compressed data.
The T9840A uses the same media as the T9840B and T7840A drives. Tapes created
on these drives are fully interchangeable: they can be read or written on any of the
other drives.
The assign mnemonic for the T98840A tape drive is HIS98.
See Section 4 for information on how to optimize performance of T9840A tape drives.
7.1.11. DLT 7000 and DLT 8000 Tape Subsystems
Note: DLT 8000 tape subsystems are supported only in the 35-GB mode
configured as the DLT 7000. All information in this subsection applies to both
DLT 7000 and DLT 8000 tape subsystems.
The DLT 7000 tape subsystem connects through SCSI-2W channels. The DLT 7000
tape subsystem does not work on SCSI narrow channels.
DLT 7000 tape subsystems provide a maximum capacity per cartridge of 35 GB of
uncompressed data (up to 70 GB of compressed data) and a sustained data transfer
rate of 5 MB per second. Tape subsystems use the LZ1 data compression technique.
3839 6586–010 7–19

Peripheral Systems
Tape cartridges use half-inch tape. These cartridges are not interchangeable with
cartridges used with 9-, 18-, and 36-track tape drives.
The Exec provides unique equipment mnemonics for configuring the subsystem and a
unique specific assign mnemonic for assigning tape files. Other than the generic
assign mnemonic T, existing assign mnemonics used to assign half-inch cartridge
tapes cannot be used to assign DLT 7000 tape drives. For more information on
mnemonics, see 9.6 Device Mnemonics.
The Exec supports DLT 7000 tape subsystems as boot devices and system dump
devices. They can also be used for checkpoint/restart. Checkpoint can assign DLT
7000 tape devices with the new assign mnemonic DLT70, or the more generic assign
mnemonic T. Restart can assign DLT 7000 tape devices with the new assign
mnemonic, DLT70.
Considerations for the DLT 7000 tape subsystem are as follows:
• Read backward I/O functions are not supported. If a read backward is attempted,
it is terminated with an I/O error status of 024 (octal).
• DLT 7000 tape drives are not compatible with any other OS 2200 tape device.
• The LED display is not supported by the Exec due to a DLT 7000 hardware
limitation; therefore, the Exec does not display either system-ID or reel-ID on the
drive.
• The Exec does not support all densities or write capabilities that the DLT 7000
hardware supports. The following table lists the capabilities that are supported
and those that are not supported by the Exec.
Table 7–3. Capabilities Supported by the Exec
Tape Type Densities Tape Read Tape Write
DLT III 2.6 GB No No
6.0 GB No No
10 GB (uncompressed) Yes No
20 GB (compressed) Yes No
DLT IIIxt 15 GB (uncompressed) Yes No
30 GB (compressed) Yes No
DLT-IV 35 GB (uncompressed) Yes Yes
70 GB (compressed—actual
capacity depends on data)
Yes Yes
DLT III and DLT IIIxt type tapes can only be read by DLT 7000 tape subsystems.
They cannot be used as blank or scratch tapes.
7–20 3839 6586–010

Caution
Peripheral Systems
All DLT 7000 cartridge tapes contain header blocks that are written at the
factory. Therefore, the tapes must never be degaussed because any
attempt to read or write a degaussed DLT 7000 tape can produce
unpredictable I/O errors (for example, timeout or data check).
• DLT 7000 tape subsystems cannot read traditional 9-, 18-, or 36-track formatted
tapes. To read these tapes and transfer the data to a DLT 7000 tape subsystem,
you must have a tape device on the host system that can read the 9-, 18-, or 36track
formatted tapes. You can then transfer the data to the DLT 7000 tape
subsystem.
• The function of the general assign mnemonic T is expanded so that it can be used
with DLT 7000 tape subsystem. You must be aware of tape drive allocation while
using this mnemonic in case the general assign mnemonic T is configured using
SERVO TYPE SGS or as a standard system tape device. In this case, the assigned
DLT 7000 tape drive is freed (@FREE) by the system and, if there is other tape
drives available, you are given an option to choose another type. If the only tape
drives available are DLT 7000 tape drives, you might have to reconfigure the
system for mass storage audit trail devices.
• Using ACS names as assign mnemonics is not supported for DLT 7000 tape
subsystems. You should use other means (for example, absolute device
assignments when assigning DLT 7000 tape drives). If an ACS name is specified in
a tape assignment statement, the Exec attempts to assign only half-inch cartridge
tape drives (for example, HIC, HICL) available in ACS.
• Audit trails cannot be configured to use DLT 7000 tape subsystems. You must be
aware of tape drive allocation while using the general assign mnemonic T in case it
is configured through SERVO TYPE SGS or as a standard system tape device. In
this case, the assigned DLT 7000 tape drive is freed (@FREE) by the system and, if
there are other tape drives available, you are given an option to choose another
type. If the only tape drives available are DLT 7000 tape drives, you might have to
reconfigure the system for mass storage audit trail devices.
• The operator clean message to the system console is not supported for the DLT
7000 because the drive does not report ANSI standard requests for cleaning.
However, the DLT 7000 has an LED indicator that is lit when the drive needs
cleaning or the tape is bad. When DLT 7000 tape subsystems are part of a tape
library, the Automated Cartridge System Library Software (ACSLS) should be set to
the autocleaning-enabled mode. This enables the ACSLS and the library to perform
the cleaning.
• The SCSITIS separately packaged Exec feature must be installed in order to
configure DLT 7000 tape drives.
• Business Information Server (previously MAPPER) level 41R1 (or higher) and
TeamQuest LA level 6R3 (or higher) are required to support the DLT 7000 tape
subsystem.
• MMGR level 46R2 (HMP IX 5.0) or higher is required to support DLT 7000 tape
subsystems.
3839 6586–010 7–21

Peripheral Systems
• Sort/Merge consideration
A tape volume for DLT 7000 tape subsystems can store up to 70 GB of
compressed data. In the past, unless a NUMREC parameter was specified or
scratch file was explicitly assigned, the SORT processor assumed that tape files
would fill tape volumes associated with the file. Based on that assumption, the
SORT processor would assign appropriately sized scratch files.
Because of the size of tape volumes for DLT7CT tape subsystems, the SORT
processor no longer makes that assumption. Now, the SORT processor assumes
that the last tape volume associated with each input file assigned to a DLT7CT
tape device contains 2 GB. If the last tape volume of a file contains more than 2
GB, you must assign appropriately sized scratch files before calling the SORT
processor or passing a NUMREC or RECORD parameter to the SORT processor
runstream.
• FAS consideration
DLT 7000 tape subsystems are not included in the Locate Block Performance and
FAS Usage Scenarios discussions under Performance Considerations in the FAS
Operations Guide (7830 7972) because DLT 7000 tape subsystems do not
experience the same performance problems. However, tests indicate that
performance of this tape subsystem does not improve significantly until you
access files larger than 500,000 tracks.
7.1.12. OST5136 Cartridge
The OST5136 is a rack-mounted 36-track cartridge tape; it is SCSI-2W capable. It is
available as a free-standing unit or with an automatic cartridge loader (ACL). The ACL
includes a 5-cartridge magazine.
The capacity of the cartridge is approximately 400 MB uncompressed. The maximum
transfer rate is 6 MB per second.
Note: You need to install SCSITIS if your site is configured with an OST5136
subsystem.
Considerations for the OST5136 tape subsystem are as follows:
• Due to device equipment mnemonics and file assignment mnemonics introduced
by this feature, products that are sensitive to these mnemonics are affected.
• Currently, all existing OST5136 customers use freestanding drives. The OST4890
tape subsystem has been specifically designed by StorageTek to configure in a
single-size 9710 ACS library managed by ACSLS software. If your site has both
OST5136 freestanding drives and OST4890 ACS drives, the following potential
compatibility issues might exist when using the HIC51 mnemonic:
− Drive allocation is based on the location of the volume. If the library has the
volume-ID, an OST4890 drive is selected. If the library does not have the
volume-ID, a freestanding OST5136 drive is selected.
− In case you want to force the assignment to an OST5136, you can use the pool
of NONCTL to force a drive allocation outside of the library.
You can always use absolute device assignments.
7–22 3839 6586–010

7.1.13. OST4890 Cartridge
Peripheral Systems
OST4890 is a 36-track tape subsystem that is attached to ClearPath systems through
SCSI-2W channels.
The OST4890 is a functionally compatible tape subsystem as compared to the existing
OST5136 tape subsystem; as such, the Exec provides a unique control unit mnemonic
for configuring this subsystem but no new assignment mnemonic and thus no new
device equipment mnemonic is created. The existing OST5136 device assignment
mnemonic, HIC51, is used for assigning tape files for the OST4890. The existing
OST5136 device equipment mnemonic, U5136, is also used for configuring the
OST4890 devices.
Note: You need to install SCSITIS if your site is configured with an OST4890
subsystem.
Considerations for the OST4890 tape subsystem are as follows:
• Due to the new control unit equipment mnemonic introduced by this feature,
products that are sensitive to this mnemonic are affected.
• Currently, all existing OST5136 customers use freestanding drives. The OST4890
tape subsystem has been specifically designed by StorageTek to configure in a
single-size 9710 ACS library managed by ACSLS software. If your site has both
OST5136 freestanding drives and OST4890 ACS drives, the following potential
compatibility issues might exist when using the HIC51 mnemonic:
− Drive allocation is based on the location of the volume. If the library has the
volume-ID, an OST4890 drive is selected. If the library does not have the
volume-ID, a freestanding OST5136 drive is selected.
− In case you want to force the assignment to an OST5136, you can use the pool
of NONCTL to force a drive allocation outside of the library.
You can always use absolute device assignments.
If your site uses the 9710 library, and eventually migrates to a larger library (for
example, CLU6000), you need to change all HIC51 assign mnemonics. If you are
planning to migrate to a larger library, use HICM for the OST4890 usage to avoid
potential mnemonic changes. However, if you use HICM for the OST4890 drives, and
then add a larger library (for example, CLU6000), you could have two competing
libraries. In this case, the query/polls would assign a drive in the correct library based
on the location of the volume-ID. If you add the freestanding U47M instead, the drive
allocation is purely based on whether the library software (that is, ACSLS) returns a
positive-poll for a specified volume-ID. If the library has the volume-ID, an OST4890
drive is selected. If the library does not have the volume-ID, a freestanding U47M
drive is selected. For more information on mnemonics, see Section 9.6.
3839 6586–010 7–23

Peripheral Systems
7.1.14. 4125 Open Reel
The 4125 is an open reel tape device. This 1/2-inch, 9-track, tabletop tape drive
provides a transfer rate of up to 780 KB per second (125 inches per second at 6,250
bytes per inch). It has an SCSI interface to the host.
The 4125 is designed as a streaming tape device and has limited capabilities. It is not
intended for general tape usage as a start/stop device and is not recommended for
everyday use. Use in start/stop mode impacts performance negatively.
7.2. Cartridge Library Units
A cartridge library unit (CLU) is a library of cartridge tapes that are automatically loaded
and unloaded by a robotic arm. StorageTek supplies Unisys with various models of
CLUs.
The CLU is controlled by a UNIX-based workstation. Automated Cartridge System
Library Software (ACSLS) is a UNIX application that communicates with a CLU. ACSLS
forwards tape mount and dismount requests to the library, provides status
information, and maintains a database that describes the volumes within the library.
ACSLS supports a mix of drive and media types in the same library.
Client System Component (CSC) is a software application running on the server. CSC
communicates requests from the OS 2200 operating system to mount and dismount
tapes to the tape library through the server and provides status information to the
operator through the OS 2200 operating system.
The CSC can only communicate with one ACSLS application. ACSLS can control
multiple CLUs.
Different platforms (open and OS 2200) can share the same CLU but the drives in the
library must be dedicated to a platform.
ACSLS and CSC are released and ordered separately. They are independent of
OS 2200 software releases.
7.2.1. SL3000
The SL3000 library system is scalable from 200 to 3,000 slots. The system also
supports encryption using the Crypto Key Management System. The SL3000 is
connected to a fibre channel.
7.2.2. SL8500
The SL8500 is scalable. It starts at 1,456 slots and can grow to more than 300,000
slots.
The tape drives of the SL8500 must be connected to a fabric switch (as well as the
ClearPath OS 2200 Fibre Channels). Direct connect is not allowed for the SL8500 tape
drives.
7–24 3839 6586–010

7.2.3. CLU5500
Peripheral Systems
The CLU5500 is also called the L5500. It is scalable; there are 1500 to 5500 slots in a
single module. There can be up to 24 library storage modules with a total capacity of
132,000 slots.
7.2.4. CLU700
The CLU700 library is scalable. It can accommodate up to 20 DLT7000/8000s or 12
T9840A, T9840B, T7840A or T9940B tape drives, or any combination. The CLU700 is
field upgradeable.
The CLU700 is available in three basic sizes: 216, 384, or 678 cartridge tapes.
The CLU700 can perform 450 exchanges per hour.
7.2.5. CLU180
The CLU180 library is scalable. It can accommodate up to ten DLT7000/8000s or six
T9840A, T9840B, T7840A or T9940B tape drives, or any combination. The CLU180 is
field-upgradable.
The CLU180 is available in three basic sizes: 84, 140, and 174 cartridge tapes.
The CLU180 can perform 450 exchanges per hour.
7.2.6. CLU9740
The CLU9740 Automated Cartridge System (ACS) handles the data storage
complexities of large multi-platform environments. The CLU9740 is a robotic tape
handler capable of accepting T9840A, T9849B, or T7840A cartridge tape drives, or
from 1 to 10 Digital Linear Tape (DLT) cartridge tape drives. The CLU9740 can handle up
to 494 cells.
7.2.7. CLU9710
The CLU9710 Automated Cartridge System (ACS) is a robotic tape handler capable of
accepting T9840 cartridge tape drives or DLT7000 tape drives.
Configuration flexibility for a single unit enables from 1 drive and 252 cartridges up to
10 drives and 588 cartridges.
7.2.8. CLU6000
The CLU6000 is a high-capacity (up to 6,000 cells) automated cartridge tape library. A
CLU6000 can accommodate T9840A, T9840B and T7840A tape drives.
The CLU6000 can support up to 450 exchanges per hour.
3839 6586–010 7–25

Peripheral Systems
7.3. EMC Symmetrix Disk Family
The difference between high-end, enterprise class storage and mid-tier storage is the
architecture on which they are built. The high-end products are designed for extensive
connectivity, high capacity, high performance, total redundancy, concurrent
maintenance and continuous availability to the data that resides in the storage
platform. Midrange products are designed with as much of this enterprise-class
capability as can be included within the constraints of meeting a price point which is
compatible with the server market to which they are targeted.
High-end products tend to use discrete components for channel attachment, cache,
disk attachment, and maintenance/support interfaces, while midrange products tend
to include these functional areas on a single “Storage Processor” to gain the
economies of the single-board cost structure. High-end products have much greater
throughput capacity than midrange products.
The high-end Symmetrix uses multiple dedicated controllers, channel directors, cache
modules, disk directors and other components. This provides tremendous throughput
and performance and also results in a minimal performance impact in the event of the
loss of one of these components. Continual availability of data while that component is
in a failed state and as it is replaced and the unit returned to a fully operational state
has long been a hallmark of Symmetrix products.
Note: OS 2200-assigned logical disks should not share the Symmetrix physical disk
with other platforms because it is difficult to predict or detect contention and
performance problems when the disk is independently accessed.
Within the Symmetrix line, the DMX series is the newest and the fastest.
The DMX series supports up to 32 splits per Hyper-Volume. Controlling the number of
Hyper-Volume splits is required to avoid degradation of performance. If one 181-GB
device had no splits, spindle contention would be nonexistent, but performance would
not be good because of device queuing. On the other hand, if the same drive has a
32-way split, performance might be good for cache hits, but spindle contention could
be very high with a substantial number of cache misses.
Guidelines for Hyper-Volume splits are developed for each new drive that is released
and are available through your EMC or Unisys storage specialist.
7.3.1. EMC Virtual Matrix (V-Max) Series
The V-Max subsystems provide enhanced access to your storage configuration for
your ClearPath Dorado systems supported through Fibre-Channel connections. The
capacities and connections of this device family may vary within models as technology
advances. To insure the availability of the most current information, Unisys suggests
that the customer reference the current version of the EMC Publication P/N 300-008-
603 (Rev A01 is the revision initially available). The connection method that would
apply is the Fibre Channel connection. The “Mainframe Connection” section of that
document covers FICON attachment which is NOT supported with ClearPath Dorado
host systems.
7–26 3839 6586–010

7.3.2. Symmetrix DMX Series
Peripheral Systems
The Symmetrix DMX (Direct MatriX) Series is a matrix-interconnect architecture. There
are multiple models within the Symmetrix DMX Series.
The DMX Series connects to the OS 2200 host using Fibre Channel. They all have
Lucent Connectors.
Maximum DMX 800
Table 7–4. DMX Series Characteristics
DMX
950 DMX 1000 DMX 2000 DMX 3000 DMX-3 DMX-4
Fibre Channels 16 16 48 64 64 64 64
Cache 64 GB 64 GB 128 GB 256 GB 256 GB 256 256
Disk Drives 120 360 144 288 576 1920 2400
Raw Storage 35 TB 180 TB 43 TB 86 TB 172 TB 950 TB > 1 PB
7.3.3. Symmetrix 8000 Series
The Symmetrix 8000 series is the rebranded version of the Symmetrix 5.5 family. It
connects to the ClearPath Plus server using Fibre Channel and SCSI.
Table 7–5. Symmetrix 8000 Series
Maximum 8230 8530 8830
Channel Directors 2 6 8
Disk Drives 48 96 384
Storage 3.5 TB 17.3 TB 69.5 TB
7.3.4. Symmetrix 5 and Earlier Series
All Symmetrix 5 and earlier series have Standard Connectors for their Fibre Channel
connections.
Symmetrix 5.5
The EMC Symmetrix 5.5 Integrated Cache Disk Array (ICDA) family consists of the
8000 Series.
Symmetrix 5.5 systems support host connections through Fibre and SCSI channels.
The EMC Symmetrix 5.5 ICDA family uses large cache memory configurations (up to
64 GB).
3839 6586–010 7–27

Peripheral Systems
Table 7–6. EMC Symmetrix 5.5
Maximum 8230 8530 8830
Channel Directors 2 6 8
Disk Drives 48 96 384
Storage 3.5 TB 17.3 TB 69.5 TB
Symmetrix 5.0
The EMC Symmetrix 5.0 Integrated Cache Disk Array (ICDA) family consists of the
8000 Series.
Symmetrix 5.0 systems support host connections through Fibre and SCSI channels.
Table 7–7. EMC Symmetrix 5.0
Maximum 8430 8730
Channel Directors 6 8
Disk Drives 8 to 96 16 to 384
Raw Capacity 17.3 TB 34 TB
Symmetrix 4.8
The EMC Symmetrix 4.8 ICDA family consists of two series: the 3000 Series and the
5000 Series. Both series support Fibre and SCSI host connections.
Table 7–8. EMC Symmetrix 4.8 ICDA
Maximum 3630/5630 3830/5830 3930/5930
Channel Directors 4 6 8
Disk Drives 4 to 32 8 to 96 32 to 384
Raw Capacity 1.1 TB 3.4 TB 12 TB
7–28 3839 6586–010

Symmetrix 4.0
Peripheral Systems
The EMC Symmetrix 4.0 ICDA family consists of two series: the 3000 Series and the
5000 Series. Both series support Fibre and SCSI host connections.
Table 7–9. EMC Symmetrix 4.0
Maximum 3330/5330 3430/5430 3730/5730
Channel Directors 4 6 8
Disk Drives 4 to 32 8 to 96 32 to 384
Raw Capacity 576 GB 1.7 TB 6 TB
7.4. CLARiiON Disk Family
The CLARiiON family is a good solution for applications that are not mission critical.
The CLARiiON family does not have all the redundancy features available in the
Symmetrix family.
The CLARiiON family comes with two Storage Processors: SP-A and SP-B. Each
Storage Processor enables multiple Fibre Channel interfaces to the OS 2200 host.
Multiple hosts can access the CLARiiON family. A ClearPath Plus server can use one
Fibre Channel on an SP and an open server can use the other Fibre Channel on that
Storage Processor.
The disks on the CLARiiON family support multiple varieties of RAID, including
mirroring.
Multiple Fibre Channels per Storage Processor offer redundancy at the channel level. If
one goes down, the disks attached to that Storage Processor can still be accessed.
Some CLARiiON models support Multipath, which enables a surviving Storage
Processor to take over the LUNs controlled by a failed Storage Processor.
Note: OS 2200-assigned logical disks should not share the CLARiiON physical disk
with other platforms because it is difficult to predict or detect contention and
performance problems when the disk is independently accessed.
7.4.1. CLARiiON Multipath
This feature takes advantage of a CLARiiON capability referred to as “auto trespass.”
Trespassing of a LUN is when a nonowning Storage Processor attempts to access the
LUN.
This capability is only supported for CX200/300/400/500/600/700 systems.
3839 6586–010 7–29

Peripheral Systems
Functionality
This capability is available on the Dorado 300, 400, 700, 4000, 4100, and 4200 Series
(SIOP).
Note: Support for CLARiiON Multipath is available on OS 2200 CP 9.2 and 10.1 after
applying PLE 18302586.
Prior to Multipath, the Storage Processors on CLARiiON systems were single points of
failure. If a Storage Processor failed, access to the disks it controlled was lost until the
Storage Processor was repaired. See 7.4.2 for more information on the single point of
failure as well as information on a solution: unit duplexing.
For OS 2200 releases 9.2 and 10.1, implementation of PLE18302586 enables failover to
the remaining Storage Processor with no disruption in service to the LUNs attached to
that failed Storage Processor. The loss of the Storage Processor means that half of
the I/O paths are not available, but the bandwidth of the remaining paths is usually
more than sufficient to handle the load.
Configuration Using SCMS II
OS 2200 configuration for the CLARiiON system is the same as the recommendation
for the EMC Symmetrix/DMX system: each channel attached to a Storage Processor is
configured with one logical control unit and each control unit should have only one
channel.
• CX200/300/400/500 models have up to 4 channels.
• CX600/700 models have up to 8 channels.
Configure SCMS II so that all the channels can access all the disks in an OS 2200
subsystem.
Configuration Using EMC Navisphere
Set the CLARiiON failover mode to 2 (using the Failover Wizard). Use of the Failover
Wizard requires that the target devices be part of a Storage Group.
Alternatively, the failover mode can be modified using the Storage tab in the
Navisphere Enterprise Storage page. Arraycommonpath should be enabled.
If these changes are not made correctly, attempts to access the disks from the OS
2200 host might result in sense status indicating LOGICAL UNIT NOT READY -
MANUAL INTERVENTION REQUIRED.
When configuring LUNs, you designate the owning Storage Processor. Try to balance
the load of all the LUNs across the Storage Processors; typically, each Storage
Processor owns half the LUNs.
7–30 3839 6586–010

Peripheral Systems
Note: When changing any one of the Arraycommpath, Failovermode, and Initiator
Type settings, all settings are set to the array default settings, so it is necessary to
set not only the setting that is being changed but also all initiator settings. This
applies to both methods of changing these parameters: Group Edit in Connectivity
Status and the Failover Wizard.
More detailed instructions for modifying the parameters are available in the EMC
Knowledgebase accessed using EMC Powerlink, Support, Self-Help Tools.
Operation
A LUN can only be accessed (owned) by one Storage Processor at any time. At
initialization time, the Exec interrogates each CLARiiON logical disk to determine which
Storage Processor owns the disk. The Exec then selects only those I/O paths to the
disk that use the owning Storage Processor. The other paths are the failover paths.
If a Storage Processor fails or there is no remaining IOP to the Storage Processor,
Exec error recovery retries the error through the nonowning Storage Processor, and
the retry is successful. This results in a host “Do You Want To Down path?” message
(you might see a message for each path). Do not respond to the message until the
Storage Processor is repaired. Then answer N(o). The I/O path is suspended until the
message is answered, but any I/O gets sent down an alternate path.
When a Storage Processor fails, there is a delay of approximately 100 ms to the next
I/O when a disk is switched to the other Storage Processor.
7.4.2. Without CLARiiON Multipath
The following describes the usage of CLARiiON without Multipath.
Single Point of Failure
One component of all CLARiiON systems, the Storage Processor, can be a single point
of failure. Each Storage Processor is an independent controller. The controller
manages the channels, a set of disks, and the cache for those disks.
The CLARiiON products are not dual-access products, which have typically been used
on OS 2200 systems for many years. Dual-access refers to the ability to access a
given drive from two or more independent control units. When cache is present in a
subsystem, the only way to provide cache coherency and data consistency is through
a shared-cache architecture and that increases the complexity and cost of the storage
subsystem. The CLARiiON CX products have a dedicated cache on each Storage
Processor and there is no logic between the two cache modules in the separate
Storage Processors to provide this cache coherency interface so each Storage
Processor and its associated channels, cache, and drives are independent logical
systems.
The loss of the Storage Processor results in the inability to access all disks behind that
Storage Processor until the Storage Processor is replaced. Each Storage Processor
has access to only those devices configured to it when the subsystem is installed. In
the event of a failure, the devices configured to the channels connected to a Storage
Processor are unavailable until the Storage Processor is restored to operation.
3839 6586–010 7–31

Peripheral Systems
The CLARiiON CX family requires RAID1 or RAID5. This protects against a disk failure
but does not solve the single point of failure (the Storage Processor) because the
same Storage Processor must control all associated RAID disks.
For CLARiiON disks connected to OS 2200 hosts, Unisys strongly recommends RAID1
(mirroring) along with Unit Duplexing (described below).
Unit Duplexing Eliminates Single Point of Failure
Host mirroring (OS 2200 Unit Duplexing) is one way to have multiple copies of disks
and eliminate a single point of failure of the disk or subsystem.
Unit Duplexing is a separately packaged Exec feature that supports a hardware
configuration where each mass storage device can have an associated mirrored
device. The mirrored device is transparent to all end-user software and to most
system software.
If a user program issues a request to read or write to a file on a unit-duplexed device,
the write request is automatically performed on both devices, and the read request is
performed from either device. From a user’s point of view, the unit-duplexed devices
are bit-for-bit identical.
By maintaining two bit-for-bit identical copies of a device, Unit Duplexing enables
system operations to continue if one device in the duplex pair fails. In addition, by
configuring each device in the pair to a different control unit, and connecting each
control unit to a different I/O processor (IOP), you can also ensure that system
operations continue if a control unit, channel, or IOP fails.
The relationships between the duplexed disks are established using keyins. See the
Unit Duplexing Planning, Installation, and Operations Overview (7830 7592) for
information on the functionality and maintenance of unit duplexing.
Unit Duplexing and RAID
For the CX family, it is a requirement to have either RAID1 or RAID5 (RAID1 is
recommended). This protects the data on the disks. To protect against the failure of a
Storage Processor, the optional OS 2200 offering, Unit Duplexing, is available.
Choosing both Unit Duplexing and RAID results in four copies of the data but does
ensure optimal protection. In Figure 7–1, there is 36 GB of user data. Each copy is one
of four disks.
7–32 3839 6586–010

7.4.3. LUNs
Figure 7–1. Unit Duplexing and RAID 1
Peripheral Systems
The physical disks are split into partitions called LUNs. A LUN equates to an OS 2200
logical disk. A physical disk can have some LUNs on SP-A and some on SP-B.
A physical disk should not be split between a ClearPath server and an open system. All
the LUNs of that disk should be assigned to the same server (minimizes contention
and makes it easier to detect).
The LUN values must be unique within the system. Each Fibre Channel connection
from the CLARiiON system to a ClearPath Plus server is a separate arbitrated loop, and
even though the normal convention is that LUN values only have to be unique within
an arbitrated loop, it is a requirement of the CLARiiON configuration that LUNs be
unique within the disks that can access that host. The names default to LUNxx, where
xx is the LUN value.
When configuring LUNs on a CLARiiON system, you must choose the partition size, an
available LUN value, and whether the partition is controlled by SP-A or SP-B.
Figure 7–2 shows two physical disks, each with four LUNs. This is a small
configuration, but illustrates how the CLARiiON subsystem controls the disks and the
LUNs. Note that even though each Storage Processor can access each physical disk,
the LUNs can only be managed by one or the other Storage Processor, not both.
The LUN names, along with the Storage Processor that they are assigned to, are
arbitrary. All the LUNs on a physical disk are assigned to the same Storage Processor,
but just as easily some could have been assigned to SP-A and some to SP-B. Each disk
could also have been split into more LUNs or fewer LUNs.
3839 6586–010 7–33

Peripheral Systems
Figure 7–2. CLARiiON Disk System
Figure 7–3 is based on the earlier example with OS 2200 Unit Duplexing added. The
disks are unit-duplexed within the same CLARiiON system. (They could have been
duplexed in a different peripheral subsystem for increased protection, but the
example above is closest to disk mirroring done as a RAID solution.)
The names of the disk partitions are arbitrary. The names or LUN values do not need
to be sequential on a physical disk.
Figure 7–3. CLARiiON System with Unit Duplexing
7–34 3839 6586–010

Peripheral Systems
Table 7–10 shows the OS 2200 unit-duplexed pairing established as part of the OS
2200 keyins. Again, the assignment is arbitrary as to which disk partition is duplexed to
which disk partition.
Table 7–10. Unit-Duplexed Pairs
Storage Processor Pairs
SP-A LUN000 LUN001 LUN002 LUN003 LUN104 LUN105 LUN106 LUN107
SP-B LUN100 LUN101 LUN102 LUN103 LUN004 LUN005 LUN006 LUN007
Establish redundancy by having the unit-duplexed pairs
• Controlled by different Storage Processors
• On different physical disks
7.4.4. CX Series
CX700
CX500
CX300
All the CX series, with a Fibre Channel connection, have a Lucent Connector.
The CLARiiON CX700 is the fastest and largest system of the CLARiiON family.
• Up to two Storage Processors
• Up to four 2-Gb Fibre Channels
• Up to 2048 LUNs
The CLARiiON CX500 is a smaller system of the CLARiiON family.
• Up to two Storage Processors
• Up to four 2-Gb Fibre Channels
• Up to 1034 LUNs
The CLARiiON CX300 is a better performing system of the CLARiiON CX family.
• Up to two Storage Processors
• Up to four 2-Gb Fibre Channels
• Up to 512 LUNs (The active volume count should be limited to 60 LUNs.)
3839 6586–010 7–35

Peripheral Systems
CX200
CX600
CX400
The CLARiiON CX200 is the entry point system of the CLARiiON CX family. It has the
same attributes as the CX300, but with lower performance.
• Up to two Storage Processors
• Up to four 2-Gb Fibre Channels
• Up to 512 LUNs (The active volume count should be limited to 60 LUNs.)
The CLARiiON CX600 is the largest system of the older version of the CLARiiON
family.
• Up to two Storage Processors
• Up to eight 2-Gb Fibre Channels
The CLARiiON CX400 is a smaller system of the older version of the CLARiiON family.
• Up to two Storage Processors
• Up to four 2-Gb Fibre Channels
7.4.5. ESM/CSM Series
ESM7900
CSM6800
CSM6700
The following devices belong to the ESM/CSM family of devices:
The ESM7900 system is a medium-range cache disk subsystem. It uses Fibre Channel
interfaces. The ESM7900 is the same as the CLARiiON 4700
The ESM7900 capacity is up to 120 drives for a total of up to 21.7 TB.
The CSM6700 and CSM6800 provided access from two control units in a CLARiiON
system to common drives, but this was not brought forward to the ESM7900.
Unit duplexing is the recommended way to have redundancy in the ESM7900.
The CSM6800 is an entry-level RAID array for ClearPath Plus servers.
The CSM6700 is an entry-level RAID array for ClearPath Plus servers.
7–36 3839 6586–010

7.5. Just a Bunch of Disks (JBOD)
Peripheral Systems
Just a bunch of disks (JBODs) are supported on ClearPath Plus servers. They are
gradually losing market share to control-unit-based disks.
7.5.1. JBD2000
The JBD2000 is a 2-GB Fibre Channel JBOD. It is a channel rack-mount enclosure with
up to 14 disk drives. It has single and dual host interface connections and supports
direct and SAN-attach configurations. Multiple disk drives are supported, starting at
18 GB and 36 GB in size.
7.5.2. CSM700
CSM700 systems offer low-cost JBOD storage. CSM700 provides protection from a
single point of failure: power supplies, cooling fans, and data paths. Data protection
must be provided at the host level (unit duplexing).
Features include
• Dual Fibre Channel loops and dual-ported Fibre Channel disk drives that ensure
alternative data paths from the host to the disk drives.
• Dual paths between the host system and the disk system on two Fibre Channel
loops that provide up to 200 MB per second of end-to-end data I/O bandwidth.
7.6. Other Systems
Printer
Other devices connect as I/O peripherals to the ClearPath Plus server. For information,
see Section 23 Interfacing with the Arbitrary Device Interface in the System Services
Programming Reference Manual (7833 4455).
Printers are supported through Enterprise Output Manager (formerly DEPCON). See
the following for more information:
• Enterprise Output Manager Configuration and Operations Guide (7833 3960)
• ClearPath Enterprise Servers Enterprise Output Manager for ClearPath OS 2200
and ClearPath MCP Configuration and Operations Guide (7850 4362)
3839 6586–010 7–37

Peripheral Systems
7–38 3839 6586–010

Section 8
Cabling
8.1. SCSI
This section provides information about cabling for the supported I/O channels. The
PCI-based IOPs handle standard I/O based on PCI standards. The IOPs are CIOP, SIOP,
and XIOP.
Note: Dorado 400 Series servers support SIOP only. Dorado 4000, Dorado 4100 and
4200 Series servers now support SIOP and XIOP.
Note: There have been isolated reports of timeouts during tape backup and
recovery applications (for example, FAS backup/restore, IRU) when 36-track SCSI
tape drives are in a daisy-chained configuration. To avoid this situation, do not daisy
chain the tape drives.
Dorado 300 and 700 Server systems are shipped with dual-port SCSI cards. To avoid
daisy chaining, configure both ports of the SCSI card to a single tape connection on
each. You must also add the LVD/HVD converter and cable for connectivity to each
tape drive on each SCSI port being converted.
In order to attach older High Voltage Differential (HVD) SCSI2W devices to newer
platforms, you must use a converter to adapt to the Low Voltage Differential (LVD)
Host Bus Adapters.
SCSI LVD-HVD converters are available to replace SCSI-CNV, which is being phased
out. The following are the styles:
Table 8–1. LVD-HVD Converter Styles
Style
DSI1002-L1H 1
DSI1002-L2H 2
DSI1002-L3H 3
DSI1002-L4H 4
Number of Channels
Converted
DSI1002-RMK Rack mount kit
3839 6586–010 8–1

Cabling
The part number for the cable to be used from the LVD HBA to the converter is
CBL22XX-OSM (where XX is the length of the cable and is 05 to 35 in 5-foot
increments). Cables from existing SCSI devices to the previous HVD SCSI HBAs
(CBL133-XXX) are used to attach to the SCSI-2W/SCSI-3 HVD device to the converter.
As with previous installations, if you are attaching SCSI-2N devices, they require
adapter cable ADP131-T3 in addition to the cable CBL133-XXX (where XXX is the
length of the cable and is 1, 2, 3, 5 or 10 to 100 in 10-foot increments).
8.2. Fibre Channel
Maximum cable lengths for Unisys Fibre Channel adapters are the following:
• 10 km for the 9-micron single-mode glass fiber using a long wavelength laser
• 300 meters at 2 Gb per second for the 50-micron multimode using a short
wavelength laser (OM2 fiber cable)
• 150 meters at 4 Gb per second for the 50-micron multimode using a short
wavelength laser (OM2 fiber cable)
• 380 meters at 4 Gb per second for the 50-micron multimode using a short
wavelength laser (OM3 fiber cable)
• 150 meters at 8 Gb per second for the 50-micron multimode using a short
wavelength laser (OM3 fiber cable)
The 50-micron connection is the most common connection for Fibre Channel. The only
difference in Fibre Channel operation is the distance.
Optical cable can have splices or connectors in the path from one end to the other as
long as the optical path meets an overall quality requirement.
Longer distances can be achieved with the use of switches.
To use OM3 cables, you require cable style CBL17103-XX (available from Unisys) or
equivalent OM3 cables that are compliant to the ISO/IEC 11801 standards.
8.3. SBCON
There is a variety of cable types for interconnecting single-byte command code set
connection (SBCON) components. Jumper cables and trunk cables are made of
different diameter fibers, depending on the intended usage.
The multimode light emitting diode SBCON interface used on the system utilizes either
the 62.5/125-micrometer (µm) cable or the 50/125-µm cable, individually or in
interconnecting combinations. Cable styles CBL143-xx, available from Unisys, are
stocked in various lengths. Cable lengths (the xx in the part number) of 1, 2, 5, or 10
feet can be used.
The single-mode (laser) interface (also called the extended distance facility or XDF)
uses only the 9/125-µm cable. The 62.5-µm cable cannot be combined or intermixed
with the 9/125-µm cable on any interface. The single-mode interface is not supported
8–2 3839 6586–010

y the system, except to achieve extended distances when used as the interface
between two serial SBCON Directors.
Cabling
In Figure 8–1, path A shows a directly connected peripheral with a distance of 3 km
(1.86 miles). Path B shows an SBCON Director in the path with a maximum distance of
6 km (3.72 miles). Path C shows two Directors in the path with a maximum distance of
9 km (5.58 miles). Path D shows two Directors in the path with the XDF cable between
the Directors giving a maximum distance of 26 km (16.12 miles).
Figure 8–1. SBCON Channel to Peripheral Distances
Over an SBCON link, the transmitter from the device propagates light to the receiver
of the next device. Each jumper cable or trunk cable pair has an A and B connection at
each end of the cable. A transmitter connects to the B connection and a receiver
connects to the A connection.
Light pulses flow through the link from a transmitter, entering the cable at the B
connector. At the other end of the jumper or trunk, light pulses exit the cable from the
A connector and enter either a receiver or the B connector of the next cable in the
link. The B to A crossover must be maintained for the correct light propagation
through a multi-element link.
3839 6586–010 8–3

Cabling
Cables with straight-tip (ST) or biconic connections are commercially available and
have black and white color coding. The white end is the signal entry (B) and the black
end is the signal exit (A). Figure 8–2 shows the two types of cable classes: jumper and
trunk cables. Several jumper cable lengths of up to 400 feet are provided.
Figure 8–2. SBCON Cable Connections
Jumper cables can be obtained with several different connector types
• Single-mode duplex connector
• Multimode duplex connector
• ST physical contact connector
• Biconic nonphysical contact connector
Figure 8–3 illustrates these connectors.
8–4 3839 6586–010

Figure 8–3. SBCON Cable or Connector Types
The following is important jumper cable information:
• Commercially produced cables are available in lengths up to 500 meters.
• Selected lengths of cables up to 100 meters (328 feet) are supplied.
• Excess cable can be coiled without problems.
• Standard duplex connectors attach to SBCON CAs, SBCON Directors, SBCON
converters, SBCON extenders, and SBCON control units.
• Cable ends are notched to avoid an intermix of LED and XDF cables.
• ST and biconic connectors are commercially available.
Cabling
3839 6586–010 8–5

Cabling
The following are the two supported types of trunk cables:
• IBM factory-assembled trunk cables
− Three- or six-layer, 12-fiber ribbon packaging (see Figure 8–4)
− One-inch-diameter cable (very stiff)
− Premounted connector panels at both ends
− 72 optical element trunk cables (36 duplex cable pairs with jumper connection,
referred to as a 12 pack) with connector panel (18 inches wide x 6 inches high
x 7 inches deep)
− 36 optical element trunk cables (18 duplex cable pairs with jumper connection,
referred to as a 6 pack) with connector panel (9 inches wide x 6 inches high x
7 inches deep)
• Commercially available trunk cables
− Detachable distribution panels
− Cables assembled onsite with ST or biconic connectors
− Number of duplex pairs varies with manufacturer
Figure 8–4. Trunk Cables
8–6 3839 6586–010

Cabling
A few examples of the use of jumper and trunk cables are shown in Figure 8–5. The
following are questions to consider before selecting a cable configuration:
• Is the SBCON peripheral to be located on the same floor and at a distance of less
than 400 feet?
• Is the SBCON peripheral to be located on a different floor in the building?
• Is the SBCON peripheral to be located in another building in a campus
environment?
• Is the SBCON peripheral to be located across town at a distance of greater than 5
miles?
Figure 8–5. Usage of Trunk and Jumper Cables
3839 6586–010 8–7

Cabling
8.4. FICON
Standard Fibre Channel switches are used for FICON channels. The same cable used in
SAN networks (the orange Fibre cable) with LC connectors as Fibre Channel is used for
FICON channels.
Maximum cable lengths for Unisys FICON channel adapters are as follows:
• 120 meters (approximately 394 feet) for the 62.5-micron multimode
• 300 meters at 2 Gb per second for the 50-micron multimode using a short
wavelength laser (OM2 fiber cable)
• 150 meters at 4 Gb per second for the 50-micron multimode using a short
wavelength laser (OM2 fiber cable)
• 380 meters at 4 Gb per second for the 50-micron multimode using a short
wavelength laser (OM3 fiber cable)
The 50-micron connection is the most common connection for FICON Channel. The
only difference in FICON Channel operation is the distance.
Longer distances can be achieved with the use of switches.
To use OM3 cables, you require cable style CBL17103-XX (available from Unisys) or
equivalent OM3 cables that are compliant to the ISO/IEC 11801 standards.
8.5. PCI-Based IOPs
8.5.1. Ethernet NICs
The customer needs to get NIC cables of appropriate quantity and length.
10M/100M Copper Cables
An industry-standard Unshielded Twisted Pair CAT5 cable with RJ-45 connectors is
required.
10M/100M/1000M Copper Cables
An industry-standard UTP CAT5E or CAT6 cable with RJ-45 connectors is required.
Gigabit Ethernet Optical Cables
Any industry-standard multimode fiber cable is required for use with the optical
version of Gigabit Ethernet.
8–8 3839 6586–010

8.5.2. Communications IOP (CIOP)
Note: CIOP is not supported on the Dorado 400, 4000, 4100, and 4200.
CIOP supports PCI cards that connect to COM devices or networks. The cards are
classified as network interface cards (NICs).
Cabling
The CIOP also supports a PCI card known as the PCI Host Bridge card. This card
connects by cable to an expansion rack. The expansion rack has slots for up to seven
additional PCI cards.
Table 8–2. Supported Expansion Rack CIOP NICs
FRU Part Number Style Description
38460671-003 DOR380-CIO CIOP (RoHS)
82190885-000 DOR700-CIO CIOP (RoHS)
NIC Cards
68790864-001 ETH23311-P64 Single port Fiber
68687664-001 ETH23312-P64 Single port CU
38284071-000
38284089-000
38284121-000
38284139-000
38284170-000
38284188-000
38284220-000
38284238-000
ETH33311-PCX Single port Fiber
ETH33312-PCX Single port CU
ETH10021-PCX Dual port Fiber
ETH10022-PCX Dual port CU
38282273-000 PCI1001-CSB Clock Sync Card set
8.5.3. XPC-L IOP (XIOP)
Note: XIOP is not supported on the Dorado 400.
XIOP supports one PCI card for connectivity to the XPC-L server.
The XIOP does not support the PCI Host Bridge card.
If there is a XIOP installed, there are no expansion racks attached.
3839 6586–010 8–9

Cabling
Table 8–3. Supported XIOP and XPC-L NIC
FRU Part Number Style Description
38460679-003 DOR380-XIO XIOP (RoHS)
82190893-000 DOR700-XIO XIOP (RoHS)
NIC Card
68945435-000 MYR1001-P64 VI LAN interface card
8–10 3839 6586–010

Section 9
Peripheral Migration
The following are migration issues for system peripherals. Most SIOP peripherals
supported on a Dorado 300 and 400 Series server are supported on Dorado 700, 4000,
4100, and 4200 Series server and can be migrated.
Notes:
• BMC channels are not supported on Dorado 300, 400, 700, 4000, 4100 or 4200
Series systems. Devices that require a BMC interface cannot migrate to Dorado
300, 400, 700, 800, 4000, 4100, and 4200 Series systems.
• This section lists many peripherals that are supported for migration to Dorado
300, 400, 700, 800, 4000, 4100, and 4200 Series systems. This information is
current as of the release date of this document.
Technology enhancements can rapidly make the information in this document out of
date. For current information on Unisys storage, see the following URL:
www.unisys.com/products/storage/
9.1. Central Equipment Complex (CEC)
Only the following CEC equipment can be migrated to a Dorado 300 or 400 Series
system:
Table 9–1. CEC Equipment That Can Be Migrated
Style Description
PCI645-EXT 64-bit expansion rack
PCI645-PHC PCI Host Bridge Card and cable
3839 6586–010 9–1

Peripheral Migration
9.2. I/O Processors (IOP)
SIOPs support the following channel adapters:
• Fibre Channel
• SBCON
• SCSI
• FICON
9.3. Tape Migration Issues
The following are migration issues for tape peripherals. It lists the devices no longer
supported, as well as some alternatives to replace and migrate from unsupported
devices.
Note: If you need help converting tape media no longer supported, contact your
Unisys sales representative or Technology Consulting Services personnel.
9.3.1. BMC-Connected Tapes
BMC is not supported on Dorado 300, 400, 700, 800, 4000, 4100 or 4200 Series
systems, but some sites continue to run unsupported devices that use BMC
interfaces. The following tape devices, using the BMC interface, do not work on
Dorado 300, 400, 700, 800, 4000, 4100 or 4200 Series systems:
• CTS5118
• 5073 / 0899
• 5042-II / 0874-II
• 5042-xx / 0872, 0873, 0874
9.3.2. 18-Track Proprietary (5073) Compression
Users with 18-track proprietary compressed (CMPON, CMP8ON, and CMP9ON) tape
cartridges cannot read those tapes on Dorado 300, 400, 700, 800, 4000, 4100 or 4200
Series systems. Although 36-track tape drives can read 18-track uncompressed tapes,
they cannot read the proprietary compressed data.
An associated issue is an Exec SYSGEN parameter HICDCOMP
(hic_data_compression). This parameter controls the default compression type for a
half-inch cartridge (HIC) device. A value of 1, 2, or 3 specifies proprietary compression
and cannot be used. Use either 0 (off, default) or 4 (CMPEON) as the value. For more
information about this parameter, see the Exec System Software Installation and
Configuration Guide (7830 7915).
9–2 3839 6586–010

9.3.3. Read-Backward Functions
Peripheral Migration
SIOP hardware does not support the RB$ (Read Backward) and SCRB$ (Scatter Read
Backward) functions on tape. This applies to all tape devices, regardless of the ability
of the device to perform these functions. User programs now receive an I/O error 024
if they attempt to issue read-backward functions on devices that did support readbackward
functions on older systems. These devices include the 4125 and CTS5136.
9.3.4. CSC Tape Library Software
With the discontinuance of BMC connectivity, the StorageTek Control Path Adapters
(CPA) are no longer supported (CPAs are Ethernet channel adapters). All of the
hardware to support the Client Direct Interconnect (CDI) component of Client System
Component (CSC) is no longer supported, so the CDI software component is no longer
supported. In addition, the CDI component relied on the traditional ADH interface,
which is not supported on Dorado 300, 400, 700, 800, 4000, 4100 or 4200 Series
systems.
Finally, because CMS 1100 is no longer supported, CSC can only be configured to use
Communications Platform (CPComm). This requires CSC level 4R1 or higher; CSC level
5R1 is preferred and uses a CIOP-based Ethernet connection.
9.4. Tape Devices
The following table lists the tape devices supported for Dorado 300, 400, 700, 4000,
4100 or 4200 Series systems. Some of these devices might be suitable replacements
for devices no longer supported. Dorado 800 and 4200 Series systems do not
support SCSI and SBCON peripherals.
Note: The following table is accurate as of the date of publication for this
document. The latest list of supported tape devices can be found on the Product
Support Web site at www.support.unisys.com. Sign in, select the server model, and
then click Storage Information.
Peripherals listed as unsupported might still work satisfactorily. They were fully
qualified on the prior platform, but have not undergone formal engineering testing on
the Dorado 700, 800, 4000, 4100, and 4200. It is also important to note that in many
cases the vendor no longer supports these peripherals; an alternate storage solution
should be considered. Dorado 800 and 4200 Series systems do not support SCSI and
SBCON channels.
3839 6586–010 9–3

Peripheral Migration
Model Description
LTO GEN 3 Note 400 GB
cartridge
LTO GEN 4 Note 800 GB
cartridge
Table 9–2. Supported Tape Devices
Channel
Type
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Dorado
4100
Dorado
4200
Fibre
Fibre
LTO GEN 5 Fibre — — —
DLT8000 36 GB
cartridge
DLT7000 35 GB
cartridge
T9940B
(CTS9940B)
T9840C
(CTS9840C)
200 GB
cartridge
40 GB
cartridge
T7840A/B Note 20 GB
cartridge
T9840B
(CTS9840B)
T9840A
(CTS9840A)
T9840D Note
(CTS9840D)
20 GB
cartridge
20 GB
cartridge
75 GB
cartridge
OST5136 36-track
cartridge
SCSI —
SCSI — — — —
Fibre
Fibre
SBCON
9–4 3839 6586–010
Fibre —
Fibre
SBCON
Fibre
SCSI
SBCON
Fibre
FICON
—
—
SCSI —
Bus-Tech MAS Virtual tape SBCON —
T10000A Note Fibre
T10000B Fibre
DSI-9900 (VTL) Note Fibre
SUN VSM4 SBCON —
4125 9 track
open reel
SCSI —
SUN VTL PLUS Fibre
DSI9XX3 VTL 2.2
(9983003-XXX)
Fibre (8Gb
only)
—
—
—
—
—
—
—
—
—
—

Model Description
DSI-9XX3 VTL 2.1
(DSI998300-XXX,
DSI9992012-XXX,
DSI9303002-XXX,
DSI9253002-XXX)
DSI-9XX2 VTL 2.1
(9992-002 /
9982-002 /
9942-002 /
9602-002 /
9552-002 /
9252-002)
DSI300XXX VTL 3.0
(300XXX-XXX)
Table 9–2. Supported Tape Devices
Channel
Type
Fibre (4Gb
only)
Fibre (4 GB
only)
Fibre (8Gb
only)
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Peripheral Migration
Dorado
4100
Dorado
4200
EMC DLm120 FICON — —
EMC DLm960 FICON — —
EMC DLm1010/1020 FICON — —
EMC DLm2000 FICON — —
EMC DLm6000 FICON — —
EMC DLm8000 FICON — — — — — —
MDL2000/4000/6000 FICON
Notes:
SBCON
‘ ‘ indicates ‘Supported’ and ‘—‘ indicates ‘Unsupported’ in above table.
—
LTO GEN 3:
For all releases prior to OS 220011.3 LTO GEN 3 must be configured as DLT tape.
For all releases starting with OS 2200 11.3, LTO GEN 3 must be configured as LTO GEN 3. In
other words, effective with OS 2200 11.3, configuring LTO GEN 3 as DLT tape is not
supported.
T 7840A/B:
T7840A/B are low cost entry Fibre drives.
T9840D:
Encryption is supported.
T10000A:
Encryption is supported with the use of a Sun Key Management Station.
LTO GEN 4:
Encryption is not supported.
DSI-9900:
Only 9840B model types are supported.
3839 6586–010 9–5
—
—

Peripheral Migration
9.4.1. Supported Cartridge Library Units
The following cartridge library units do not depend on host channel type for support;
however, the drives themselves do depend on host channel type. You might need to
upgrade your CSC version to one that can use CIOP-style communications devices.
Table 9–3. Supported Cartridge Library Units
Model Supported Tape Drives
SL3000 LTO3/4, 9840C/D, T10000A/B
CLU8500 T7840A, T9840x, T9940B, LTO
CLU5500 T7840A, T9840x, T9940B
CLU1000 T9840
9.4.2. End-of-Life Tape Devices
The following tape devices have reached, or soon will reach, their end of service life
on Dorado systems. Contact your Unisys representative for more information.
Table 9–4. End-of-Life Tapes
Model Description Date
DLT7000 35 GB cartridge 11/30/07
CTS5136 36-track HIC
USR5073 18-track HIC
ALP8436 36-track cartridge Vendor support ends
OST4125 Open reel Vendor support ends
CTS5236E 36-track cartridge Vendor support ends 12/31/08
CTS5236 36-track cartridge Vendor support ends 12/31/08
CTS9840A
CTS9840B
T10000A
CTS7840A
CTS7840B
Note: End-of-life peripherals might work on the SIOP. These peripherals have not
undergone formal Engineering test on the SIOP. However, informal testing was
done to verify basic functionality.
9–6 3839 6586–010

9.4.3. End-of-Life Tape Libraries
Peripheral Migration
The following tape libraries have reached, or soon will reach, their end of service life
on Dorado systems. Contact your Unisys representative for more information.
Table 9–5. End-of-Life (EOL) Table Libraries
Model Supported Tape Drives Date
CLU9740 DLT8000, DLT7000, T7840A, T9840x, T9940B 12/31/08
CLU9710 DLT7000 12/31/08
CLU6000 T7840A, T9840x, T9940B 12/31/08
CLU700, 1400 DLT8000, DLT7000, T7840A, T9840x, T9940B, LTO
CLU180 DLT8000, DLT7000, T7840A, T9840x, T9940B, LTO
9.5. Disk Devices
The following are the disks that are supported on Dorado 300, 400, 700, 4000, 4100 or
4200 Series systems and the disks that are no longer supported. Dorado 800 and 4200
Series systems do not support SCSI and SBCON peripherals.
9.5.1. Supported Disks
The following table lists disk devices that are supported on Dorado 300, 400, 700,
4000, 4100 or 4200 Series systems.
Notes:
• The following table is accurate as of the date of publication for this document.
The latest list of supported tape devices can be found on the Product Support
Web site at www.support.unisys.com. Sign in, select the server model, and then
click Storage Information.
• Dorado 700, 4000, 4100 and 4200 does not support SCSI to disks.
• Dorado 800 and 4200 Series systems do not support SCSI and SBCON channels.
The following disk types are no longer supported and their BMC interfaces are not
functional:
• Symm 4.8
• Symm 4.0
Peripherals listed as unsupported might still work satisfactorily. They were fully
qualified on the prior platform, but have not undergone formal engineering testing on
the Dorado 700, 800, 4000, 4100, and 4200. It is also important to note that in many
cases the vendor no longer supports these peripherals; an alternate storage solution
should be considered.
3839 6586–010 9–7

Peripheral Migration
Disks Description
Table 9–6. Supported Disk Devices
Channel
Type
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Dorado
4100
DMX Series Fibre
DMX2 Note Fibre
DMX3 Note Fibre
DMX4 Note Fibre
Z8830 Fibre
SCSI Note
Z8530 Fibre
SCSI Note
8230 Symm 5.5
Series
8570 Symm 5.0
Series
8430 Symm 5.0
Series 2
3630/5630 Symm 4.8
Series
3830/5830 Symm 4.8
Series
3930/5930 Symm 4.8
Series
3330/5330 Symm 4.0
Series
3430/5430 Symm 4.0
Series
3730/5730 Symm 4.0
Series
Fibre Note
SCSI Note
Fibre Note
SCSI Note
Fibre Note
SCSI Note
Fibre Note
SCSI
Fibre Note
SCSI
Fibre Note
SCSI
Fibre Note
SCSI
Fibre Note
SCSI
Fibre Note
SCSI
—
—
—
—
—
—
—
—
—
—
—
—
Dorado
4200
9–8 3839 6586–010
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
CX700 Note CLARiiON Fibre —
CX600 Note CLARiiON Fibre —
CX500 Note CLARiiON Fibre —
CX400 Note CLARiiON Fibre —
CX300 Note CLARiiON Fibre —
CX200 Note CLARiiON Fibre —
CX3 10c CLARiiON Fibre
CX3 20/F CLARiiON Fibre
CX3 40/F CLARiiON Fibre
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—

Disks Description
Table 9–6. Supported Disk Devices
Channel
Type
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Peripheral Migration
Dorado
4100
CX3 80 CLARiiON Fibre
CX4-120 CLARiiON Fibre
CX4-240 CLARiiON Fibre
CX4-480 CLARiiON Fibre
CX4-960 CLARiiON Fibre
Dorado
4200
ESM7900 CLARiiON Fibre — — — —
CSM6800 CLARiiON Fibre — — — —
CSM6700 CLARiiON Fibre — — — —
JBD2000 JBOD Fibre —
CSM700 JBOD Fibre — — —
OSM3000 JBOD Fibre — — — —
HDA 9500V Hitachi Fibre —
TagmaStore
USP
Hitachi Fibre —
USP-V Hitachi Fibre —
V-Max E V-Max
Series Note
V-Max V-Max
Series Note
V-Max10k V-Max
Series Note
V-Max20k V-Max
Series Note
V-Max40k V-Max
Series Note
Fibre
Fibre
Fibre
Fibre
Fibre
VNX5100 Fibre
VNX5300 Fibre
VNX5500 Fibre
VNX5700 Fibre
VNX7500 Fibre
3839 6586–010 9–9

Peripheral Migration
Notes:
‘ ‘ indicates ‘Supported’ and ‘—‘ indicates ‘Unsupported’ in above table.
DMX Series
DMX2
DMX3
DMX4:
Device supports I/O Command Queuing using standard released software.
Z8830 SCSI
Z8530 SCSI:
Device is not supported by the device manufacturer. Although the device can be
connected and should function properly, Unisys does not support the device.
8230
8570
8430:
Device supports I/O Command Queuing using a Custom Engineering Request (CER).
3630/5630 Fibre
3830/5830 Fibre
3930/5930 Fibre
3330/5330 Fibre
3430/5430 Fibre
3730/5730 Fibre:
Device is not supported by the device manufacturer. Although the device can be
connected and should function properly, Unisys does not support the device.
CX700
CX600
CX500
CX400
CX300
CX200:
For Dorado 300 and 400 Series, device supports 2200 Active/Passive Failover
capability.
V-Max Series
Only available on SIOP and SCIOP connected systems.
9.5.2. SAIL Disks
The following are the supported SAIL disk devices:
Table 9–7. Supported SAIL Disks
Disk Channel Type Dorado 400 Dorado 4000 Dorado 4100 Dorado 4200
Fujitsu (Model
MAY2073RC)
SAS — — —
iQstor RTS2880 Fibre — —
9–10 3839 6586–010

RAID Disk
Table 9–7. Supported SAIL Disks
Peripheral Migration
Disk Channel Type Dorado 400 Dorado 4000 Dorado 4100 Dorado 4200
Seagate (Model
ST9146802SS)
Seagate (Model
ST9146852SS)
Seagate (Model
ST9146852SS0)
SAS — — —
SAS — — —
6 Gb SAS — — —
Note: ‘ ‘ indicates ‘Supported’ and ‘—‘ indicates ‘Unsupported’ in above table.
9.5.3. Supported DVDs
In each remote I/O module, each Dorado 300, 400, 700 and 800 has a DVD device that
emulates a tape device. The DVD device is primarily for loading software releases to
your system. Software releases are provided on DVD instead of tape. SCSI and
SBCON channels are not supported on Dorado 800 and 4200 Systems.
The following are the supported DVDs:
DVD
Table 9–8. Supported DVDs
Channel
Type
Toshiba-DVD (read only) SCSI/
ATAPI
Toshiba-DVD (read and write) SCSI/
ATAPI
Sony/NEC-DVD (read only) SCSI/
ATAPI
DVD (read-only) PCIOP-E
SATA
DVD from SAIL
(read and write from SAIL,
read only from 2200)
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Dorado
4100
Dorado
4200
— — — —
— — — — — —
— — — — —
— — — — —
SATA — — — —
Samsung SH-222AB DVD +/- RW SATA — — — — —
Note: ‘ ‘ indicates ‘Supported’ and ‘—‘ indicates ‘Unsupported’ in above table.
3839 6586–010 9–11

Peripheral Migration
9.5.4. Non-RoHS Host Bus Adapters (HBAs)
HBAs
The following non-RoHS compliant HBAs are supported:
Table 9–9. Supported Non-RoHS Host Bus Adapters (HBAs)
Channel
Type
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Dorado
4100
Dorado
4200
Emulex LP9002 Fibre — — — —
Emulex
LP10000DC
Fibre — — — —
Luminex L6999 SBCON — — — —
LSI 22320-R SCSI — — — —
Promise ATA
Ultra133 TX2
PATA (for
DVD)
— — — — —
Cavium Nitrox Cipher — — — — —
Note: ‘ ‘ indicates ‘Supported’ and ‘—‘ indicates ‘Unsupported’ in above table.
9.5.5. RoHS Host Bus Adapters (HBAs)
The following RoHS compliant HBAs are supported:
HBAs
Table 9–10. Supported RoHS Host Bus Adapters (HBAs)
Channel
Type
Dorado
300
Dorado
400
Dorado
700
Dorado
4000
Dorado
4100
Dorado
4200
Emulex LP10000DC Fibre —
Emulex LP11002 Fibre — —
Emulex LPe11002 Fibre — — — — —
Emulex LPe12002 Fibre — — — — —
Luminex L6999 SBCON —
LSI 22320-R SCSI —
Promise ATA Ultra133
TX2
PATA (for
DVD)
— — — — —
Cavium Nitrox Cipher —
EMC (Bus-Tech) PEFA-
LP
Cavium Nitrox CN1620-
400-NHB4-E-G
FICON — — — — —
Cipher — — — — —
9–12 3839 6586–010

9.5.6. SAIL Host Bus Adapters (HBAs)
The following SAIL HBAs are supported:
HBAs
Channel
Type
Dorado
400
Dorado
4000
Peripheral Migration
Dorado
4100
Dorado
4200
Emulex LP1050 Fibre — — —
LSI SAS3442x-R SAS — — —
Emulex LPe1150 Fibre — — —
Dell PERC 6/i SAS — — —
Dell PERC H700 SAS — — —
Dell PERC H710 mini 6 Gb SAS — — —
Note: ‘ ‘ indicates ‘Supported’ and ‘—‘ indicates ‘Unsupported’ in above table.
9.5.7. End-of-Life Disks
Some sites continue to run devices with BMC interfaces that have reached their end
of service life. These disks, using the BMC interface, do not work on Dorado 300, 400,
700, 800, 4000, 4100 or 4200 Series systems, including the following:
• USP5100
• USP5500
• M9760
• M9720
For the following disks, SCSI channels might function on Dorado 300, 400, 700, 4000
or 4100 Series systems. However, Unisys does not test these disks because they
have passed their end-of-life:
• USP5100 cache disk
• USP5500 cache disk
• USR3000 JBOD
• USR4000 JBOD
9.6. Device Mnemonics
SIOP hardware keys off the device mnemonic to select the correct driver.
Note: This does not affect your ability to use Exec system generation CONV
statements to include or exclude existing devices within group mnemonics, or to
create new groups with existing device mnemonics.
3839 6586–010 9–13

Peripheral Migration
The following device mnemonics are known and supported for devices attached to
the SIOP channels:
Table 9–11. SIOP Device Mnemonics (By Mnemonic)
Device
Mnemonic Device
Tapes
T All tapes
HIC Any available 18-track or 36-track drive (for example 5073, CTS5236)
HICL Any available 18-track drive (for example, 5073)
HICM Any available 36-track drive (for example, CTS5136, CTS5236, OST4890)
DLT70 Any available DLT 7000 tape drive
HIS98 Any available HIS98 tape drive
LTO
LTO3
LTO4
Any LTO tape drive
VTH Appropriate tape drives
CULT04
ULT04
CU70SC
U7000
CU52SC
CU52SB
U5236
CU98SC
U9840
CU98SC
CU98SB
U9840
CU98SC
CU98SB
U9840C
HIS98C
LTO Gen4, LTO Gen5
DLT 7000, DLT8000
CTS5236, CTS5236E
T7840A
T9840A, T9840B
T9840C
HIS98D T9840D
CU99SC
U9940B
HIS99B
CU5136
U5136
CUT10K
UT10KA
T10KA
T9940B
OST5136
T10000A
9–14 3839 6586–010

Table 9–11. SIOP Device Mnemonics (By Mnemonic)
Device
Mnemonic Device
Tapes
U47M Bus-Tech MAS
U47LM SUN/ Storage Tek VSM4
FORM8
U45N
CULASC,
ULTO3
CULASC,
ULTO4
CU98SC,
CU98SB,
U9840
CU98SC,
CU98SB,
U9840
CU98SC,
CU98SB,
U9840C
CU98SC,
U9840D
CU98SB
CU99SC,
U9940B
CUTASC,
UT10KA
CU98SC,
U9840
CU4780,
U47LM
CU4780
U47LM
Disks
CUCSCS
SCDISK
OST4125
LTO Gen 3
LTO Gen 4, LTO Gen 5
CTS9840A – EOL Tape
CTS9840B – EOL Tape
CTS9840C
CTS9840D
CTS9940B
T10000A – EOL Tape, T10000B
DSI-9900 (VTL), Oracle VTL Plus (VTL), DSI-9XX3, DSI-9XX2
EMC DLm120, EMC DLm960
EMC DLm1010/1020, EMC DLm2000, EMC DLm6000, EMC DLm8000,
MDL2000/4000/6000
Peripheral Migration
DMX Series, DMX2 Series, DMX3 Series, DMX4 Series, Z8830, Z8530, 8230
(Symm 5.5), 8570 (Symm 5.0), 8430 (Symm 5.0), CX700, CX600, CX500, CX400,
CX300, CX200, CX3 10c, CX3 20/F, CX3 40/F, CX3 80, CX4-120, CX4-240, CX4-
480, CX4-960, EXM7900, CSM6700, CSM6800, JBD2000, CSM700, OSM3000,
HDA9500V, TagmaStore USP, USP-V, V-Max E, V-Max, V-Max10k, V-Max20k, V-
Max40k, VNX5100, VNX5300, VNX5500, VNX5700, VNX7500
CU98SC DSI 9900 VTL
3839 6586–010 9–15

Peripheral Migration
Table 9–11. SIOP Device Mnemonics (By Mnemonic)
Device
Mnemonic Device
Tapes
U9840
DVD
CUDVDT
DVDTP
HBAs
Toshiba DVD, Sony/NEC DVD, DVD, Samsung DVD
FCSCSI Emulex LP9002, Emulex LP10000DC, Cavium Nitrox, LP11002
SBCON Luminex L6999
SCSI2W LSI 22320-R
Tapes
Notes:
• Be aware that when you use general assign mnemonics (T and HIC), you
should determine the exact device type that was allocated so that later
reassignments use the required assign mnemonic to read the tape. For
example, if you begin with “HIC” and are allocated a 36-track device, you
must use HICM, HIC51, HIC52, or U47M to reassign a 36-track device in
order to read the tape.
• Using the pool name “NONCTL” with the mnemonic U47 will force the
assignment to a freestanding U47 drive.
Table 9–12. SIOP Device Mnemonic (By Device)
Device Device Mnemonic
All tapes T
Any available 18-track or 36-track drive (for example 5073, CTS5236) HIC
Any available 18-track drive (for example, 5073) HICL
Any available 36-track drive (for example, CTS5136, CTS5236, OST4890) HICM
Any available DLT 7000 tape drive DLT70
Any available HIS98 tape drive HIS98
Any LTO tape drive LTO
LTO3
LTO4
Appropriate tape drives VTH
9–16 3839 6586–010

DLT 7000, DLT8000
CTS5236, CTS5236E
Table 9–12. SIOP Device Mnemonic (By Device)
Peripheral Migration
Device Device Mnemonic
CU70SC
U7000
CU52SC
CU52SB
U5236
T7840A CU98SC U9840
T9840A, T9840B CU98SC
CU98SB
U9840
T9840C CU98SC
CU98SB U9840C
HIS98C
T9840D HIS98D
T9940B CU99SC U9940B
HIS99B
CU5136
U5136
OST5136 CUT10K
UT10KA
T10KA
T10000A U47M
Bus-Tech MAS U47LM
SUN/ Storage Tek VSM4 FORM8
U45N
LTO Gen 3 CULASC, ULTO3
LTO Gen 4, LTO Gen 5 CULASC, ULTO4
CTS9840A – EOL Tape CU98SC, CU98SB,
U9840
CTS9840C
CU98SC, CU98SB,
U9840C
CTS9840D CU98SC, U9840D,
CU98SB
CTS9940B
CU99SC, U9940B
T10000A – EOL Tape, T10000B CUTASC, UT10KA
DSI-9900 (VTL), Oracle VTL Plus (VTL), DSI-9XX3, DSI-9XX2
CU98SC, U9840
EMC DLm120, EMC DLm960 CU4780, U47LM
3839 6586–010 9–17

Peripheral Migration
Table 9–12. SIOP Device Mnemonic (By Device)
Device Device Mnemonic
EMC DLm1010/1020, EMC DLm2000, EMC DLm6000, EMC DLm8000,
MDL2000/4000/6000
Disks
DMX Series, DMX2 Series, DMX3 Series, DMX4 Series, Z8830,
Z8530, 8230 (Symm 5.5), 8570 (Symm 5.0), 8430 (Symm 5.0), CX700,
CX600, CX500, CX400, CX300, CX200, CX3 10c, CX3 20/F, CX3 40/F,
CX3 80, CX4-120, CX4-240, CX4-480, CX4-960, EXM7900, CSM6700,
CSM6800, JBD2000, CSM700, OSM3000, HDA9500V, TagmaStore
USP, USP-V, V-Max E, V-Max, V-Max10k, V-Max20k, V-Max40k,
VNX5100, VNX5300, VNX5500, VNX5700, VNX7500
CU4780 U47LM
CUCSCS
SCDISK
DSI 9900 VTL CU98SC, U9840
DVD
Toshiba DVD, Sony/NEC DVD, DVD, Samsung DVD CUDVDT, DVDTP
HBAs
Emulex LP9002, Emulex LP10000DC, Cavium Nitrox, LP11002 FCSCSI
Luminex L6999 SBCON
LSI 22320-R SCSI2W
9.7. Communications Migration Issues
9.7.1. DCP
The following are migration issues for communications devices.
DCPs are beyond their support lifetime and require a CER.
DCPs connected to BMC host channels are no longer supported.
DCP continues to be available, with a CER, through an Ethernet line module and
Communications Platform (CPComm). If you want to retain channel-connected DCPs,
you must migrate to an Ethernet connection.
9.7.2. FEP Handler
The FEP handler is obsolete; this was a BMC interface only. Any local software that
uses the FEP handler does not function.
9–18 3839 6586–010

9.7.3. HLC
Peripheral Migration
The HLC is unsupported and does not work on Dorado 300 or 400 Series systems; it
uses a BMC interface.
9.7.4. CMS 1100
9.7.5. FDDI
There is no longer any hardware that can be driven by CMS 1100. Therefore, CMS 1100
itself is nonfunctional on Dorado 300, 400, 700, 800, 4000, 4100 or 4200 Series
systems.
There are no FDDI network interface cards supported on Dorado 300, 400, 700, 800,
4000, 4100 or 4200 Series systems. If you have an FDDI network, consider either one
of these options:
• Convert this network to an Ethernet network.
• Connect an Ethernet LAN to the Dorado 300 or 400 Series system and attach a
router that can attach to your FDDI network.
9.8. Network Interface Cards
The following are the network interface cards (NICs) that are supported on Dorado
300, 400, 700, 4000, 4100 or 4200 Series.
9.8.1. Dorado 300, 400, and 700 Series Systems
The following table lists NICs that are supported on Dorado 300, 400, and 700
systems.
Note: These are not supported on the Dorado 4000, 4100 or 4200 Series.
Table 9–13. Ethernet NICs
Model Description
ETH33311-PCX Fibre: single port
ETH33312-PCX Copper: single port
ETH10021-PCX Fibre: dual port
ETH10022-PCX Copper : dual port
While these single-port NICs are supported, dual-port NICs are recommended for
enhanced connectivity.
3839 6586–010 9–19

Peripheral Migration
9.8.2. Dorado 4000 Series Systems
The following table lists NICs that are supported on Dorado 4000 systems.
Table 9–14. Ethernet NICs
Model Description
ETH10041-PCE Copper: quad port
ETH9330211-PCE Fibre: dual port
9.8.3. Dorado 4100 Series Systems
The Dorado 4180/4190 package styles do not include a NIC. A minimum of one NIC
must be ordered with the system. Additional NICs may be ordered. The following
package styles are used to order NICs:
Table 9–15. Ethernet NICs
Model Description
ETH21401-PCE INTEL PRO/1000 PT QUAD PORT NIC PCI-E (copper)
ETH10201-PCE Intel Pro/1000PF NIC (dual port) x4 PCIe, 1 Gbit Ethernet (optical)
ETH10210-PCE Note Intel 10 Gb PCIe X8, dual port Optical
Note: A maximum of two ETH10210-PCE cards are supported for each system.
9.8.4. Dorado 4200 Series Systems
The following table lists NICs that are supported on Dorado 4200 systems.
Table 9–16. Ethernet NICs
Model Device Type Host Slot Type LAN Type
Intel i350-T4 NIC (quad port) with
RJ-45 connectors
x8 PCIe Gen 2
1 Gb Ethernet
(Copper)
Intel i350-F2 NIC (dual port) x8 PCIe Gen 2 1 Gb Ethernet
(Optical)
Intel X540-T2 (E10G42KT) NIC (dual port) with
RJ-45 connectors
X8 PCIe Gen 2
Intel X520-SR2 (E10G42BFSR) NIC (dual port) X8 PCIe Gen 2
10 Gb Ethernet
(Copper)
10 Gb Ethernet
(Optical)
9–20 3839 6586–010

9.9. Other Migration Issues
The following are some other issues related to peripherals migration.
9.9.1. Network Multihost File Sharing
Peripheral Migration
The CA3000 device and older, similar versions of BMC Host LAN Controller (HLC)
devices are not supported on Dorado 300, 400, 700, 800, 4000, 4100 or 4200 Series
systems.
The CA3000 device was used to support the network version of Multi-Host File
Sharing (MHFS), which is also an underlying technology used by the Partitioned
Applications (PA) feature. Sites that want to use PA or just MHFS must migrate to an
XPC–L.
The Data Mover is not supported on the Dorado 300, 400, 700, 800, 4000, 4100 or
4200 Series systems.
9.9.2. NETEX and HYPERchannel
The SIOP on Dorado 300 and 700 Series systems required a change to the Arbitrary
Device Handler (ADH) interface used by the NetEX software. NESi has adapted to this
new interface for their current NESiGate product. Customers using this product should
contact their NESi representative to obtain new versions of NetEx for use on Dorado
300 and 700 Series systems.
Previous NESi products, including the HYPERchannel DXE Model N220 (BMC) and N225
(SBCON), are no longer supported by SUN/StorageTek and, due to the requirement for
this new ADH interface, cannot be supported on the Dorado 300 and 700 Series.
NETEX and HYPERchannel also had an FEP option in addition to the ADH option;
support for FEP is also unavailable. Contact your Unisys representative to discuss
alternatives.
9.9.3. Traditional ADH
IOPs require the use of a different maintenance interface. All existing ADH programs
do not function, even on similar channel types. The replacement maintenance
interface (Arbitrary Device Handler) is documented in the System Services
Programming Reference Manual (7833 4455).
9.9.4. DPREP
DPREP level 10R3 or later is necessary to prep disks on SIOP channels using the
Dorado 300, 400, 700, 800, 4000, 4100 or 4200 Series maintenance interface.
3839 6586–010 9–21

Peripheral Migration
9–22 3839 6586–010

Appendix A
Fibre Channel Addresses
The following table shows the allowable positions on an arbitrated loop. The table also
shows the associated AL_PA value along with the resulting SCMS II and Exec value.
The first entry in the table is the lowest priority in the loop. The highest priority in the
loop, the address reserved for the connection to the fabric switch (AL_PA = 00), is at
the end of the table. The ClearPath Plus channel adapter, the next highest priority
(AL_PA = 01), is the entry just above the entry for the fabric switch.
Table A–1. Allowed Positions on an
Arbitrated Loop
Device Address Setting
(hex) (dec)
AL_PA
(hex)
SCMS II/Exec
(dec)
0 0 EF 239
1 1 E8 232
2 2 E4 228
3 3 E2 226
4 4 E1 225
5 5 E0 224
6 6 DC 220
7 7 DA 218
8 8 D9 217
9 9 D6 214
A 10 D5 213
B 11 D4 212
C 12 D3 211
D 13 D2 210
E 14 D1 209
F 15 CE 206
10 16 CD 205
11 17 CC 204
3839 6586–010 A–1

Fibre Channel Addresses
Table A–1. Allowed Positions on an
Arbitrated Loop
Device Address Setting
(hex) (dec)
AL_PA
(hex)
SCMS II/Exec
(dec)
12 18 CB 203
13 19 CA 202
14 20 C9 201
15 21 C7 199
16 22 C6 198
17 23 C5 197
18 24 C3 195
19 25 BC 188
1A 26 BA 186
1B 27 B9 185
1C 28 B6 182
1D 29 B5 181
1E 30 B4 180
1F 31 B3 179
20 32 B2 178
21 33 B1 177
22 34 AE 174
23 35 AD 173
24 36 AC 172
25 37 AB 171
26 38 AA 170
27 39 A9 169
28 40 A7 167
29 41 A6 166
2A 42 A5 165
2B 43 A3 163
2C 44 9F 159
2D 45 9E 158
2E 46 9D 157
2F 47 9B 155
30 48 98 152
A–2 3839 6586–010

Table A–1. Allowed Positions on an
Arbitrated Loop
Device Address Setting
(hex) (dec)
AL_PA
(hex)
Fibre Channel Addresses
SCMS II/Exec
(dec)
31 49 97 151
32 50 90 144
33 51 8F 143
34 52 88 136
35 53 84 132
36 54 82 130
37 55 81 129
38 56 80 128
39 57 7C 124
3A 58 7A 122
3B 59 79 121
3C 60 76 118
3D 61 75 117
3E 62 74 116
3F 63 73 115
40 64 72 114
41 65 71 113
42 66 6E 110
43 67 6D 109
44 68 6C 108
45 69 6B 107
46 70 6A 106
47 71 69 105
48 72 67 103
49 73 66 102
4A 74 65 101
4B 75 63 99
4C 76 5C 92
4D 77 5A 90
4E 78 59 89
4F 79 56 86
3839 6586–010 A–3

Fibre Channel Addresses
Table A–1. Allowed Positions on an
Arbitrated Loop
Device Address Setting
(hex) (dec)
AL_PA
(hex)
SCMS II/Exec
(dec)
50 80 55 85
51 81 54 84
52 82 53 83
53 83 52 82
54 84 51 81
55 85 4E 78
56 86 4D 77
57 87 4C 76
58 88 4B 75
59 89 4A 74
5A 90 49 73
5B 91 47 71
5C 92 46 70
5D 93 45 69
5E 94 43 67
5F 95 3C 60
60 96 3A 58
61 97 39 57
62 98 36 54
63 99 35 53
64 100 34 52
65 101 33 51
66 102 32 50
67 103 31 49
68 104 2E 46
69 105 2D 45
6A 106 2C 44
6B 107 2B 43
6C 108 2A 42
6D 109 29 41
6E 110 27 39
A–4 3839 6586–010

Table A–1. Allowed Positions on an
Arbitrated Loop
Device Address Setting
(hex) (dec)
AL_PA
(hex)
Fibre Channel Addresses
SCMS II/Exec
(dec)
6F 111 26 38
70 112 25 37
71 113 23 35
72 114 1F 31
73 115 1E 30
74 116 1D 29
75 117 1B 27
76 118 18 24
77 119 17 23
78 120 10 16
79 121 0F 15
7A 122 08 08
7B 123 04 04
7C 124 02 02
7D 125 01 01
7E 126 00 00
3839 6586–010 A–5

Fibre Channel Addresses
A–6 3839 6586–010

Appendix B
Fabric Addresses
The following tables show the port locations and the corresponding port addresses,
SCMS II values, and Exec values for peripherals attached to Brocade and McData
switches. There are two tables because the Brocade and McData switches generate
different values.
The physical location refers to the actual connector location on the switch. The
Brocade port addresses are the same values as the connector locations. The McData
port addresses are offset by 4 on some McData switches; for example, the decimal
port address at port location x00 is 04 and the decimal port address at port location
x0D is 13. On newer McData switches (for example, ED10000, 4400, 4700), the port
address matches the port location as they do on Brocade.
The following table assumes that all the devices are fabric-capable. The default AL_PA
value for Brocade is 0. The default AL_PA value for McData is x’013’. In SCMS II, this is
a decimal 19. If a device attached to the port is an arbitrated loop device, then the
AL_PA value is most likely 239 (EF).
SCMS II can access any port on a switch. SCMS II only uses the last digit of the 2-digit
hexadecimal port field; it can see 16 unique devices. It is possible for two unique ports
(for example, port fields 05 and 15) to appear the same to SCMS II. However, proper
zoning can ensure that this never happens.
Note: The 12-bit addressing restriction does not apply to OS 2200 12.0 with Exec
level of 48R4 when connected to SIOPs or SCIOPs.
The Exec values are used in console messages as well as dumps of SCMS II tables.
The values are calculated as follows:
(Port address x 256) + AL_PA value
3839 6586–010 B–1

Fabric Addresses
The following table lists Brocade switch addresses.
Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
0 00 00
1 01 00
2 02 00
3 03 00
4 04 00
5 05 00
6 06 00
7 07 00
8 08 00
9 09 00
10 0A 00
11 0B 00
12 0C 00
13 0D 00
14 0E 00
15 0F 00
16 10 00
17 11 00
SCMS II
(dec)
Exec
(dec)
Area = 0
Address = 000 0
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address = 000 0
Area = 1
Address = 000 256
B–2 3839 6586–010

Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
18 12 00
19 13 00
20 14 00
21 15 00
22 16 00
23 17 00
24 18 00
25 19 00
26 1A 00
27 1B 00
28 1C 00
29 1D 00
30 1E 00
31 1F 00
32 20 00
33 21 00
34 22 00
35 23 00
36 24 00
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address =000 0
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
3839 6586–010 B–3

Fabric Addresses
Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
37 25 00
38 26 00
39 27 00
40 28 00
41 29 00
42 2A 00
43 2B 00
44 2C 00
45 2D 00
46 2E 00
47 2F 00
48 30 00
49 31 00
50 32 00
51 33 00
52 34 00
53 35 00
54 36 00
55 37 00
SCMS II
(dec)
Exec
(dec)
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address = 000 0
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
B–4 3839 6586–010

Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
56 38 00
57 39 00
58 3A 00
59 3B 00
60 3C 00
61 3D 00
62 3E 00
63 3F 00
64 40 00
65 41 00
66 42 00
67 43 00
68 44 00
69 45 00
70 46 00
71 47 00
72 48 00
73 49 00
74 4A 00
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address = 000 0
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
3839 6586–010 B–5

Fabric Addresses
Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
75 4B 00
76 4C 00
77 4D 00
78 4E 00
79 4F 00
80 50 00
81 51 00
82 52 00
83 53 00
84 54 00
85 55 00
86 56 00
87 57 00
88 58 00
89 59 00
90 5A 00
91 5B 00
92 5C 00
93 5D 00
SCMS II
(dec)
Exec
(dec)
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address = 000 0
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
B–6 3839 6586–010

Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
94 5E 00
95 5F 00
96 60 00
97 61 00
98 62 00
99 63 00
100 64 00
101 65 00
102 66 00
103 67 00
104 68 00
105 69 00
106 6A 00
107 6B 00
108 6C 00
109 6D 00
110 6E 00
111 6F 00
112 70 00
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address = 000 0
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
Area = 0
Address = 000 0
3839 6586–010 B–7

Fabric Addresses
Port Location
(dec)
Table B–1. Brocade Switch Addresses
Brocade Switch
(hex)
Port AL_PA
113 71 00
114 72 00
115 73 00
116 74 00
117 75 00
118 76 00
119 77 00
120 78 00
121 79 00
122 7A 00
123 7B 00
124 7C 00
125 7D 00
126 7E 00
127 7F 00
SCMS II
(dec)
Exec
(dec)
Area = 1
Address = 000 256
Area = 2
Address = 000 512
Area = 3
Address = 000 768
Area = 4
Address = 000 1024
Area = 5
Address = 000 1280
Area = 6
Address = 000 1536
Area = 7
Address = 000 1792
Area = 8
Address = 000 2048
Area = 9
Address = 000 2304
Area = 10
Address = 000 2560
Area = 11
Address = 000 2816
Area = 12
Address = 000 3072
Area = 13
Address = 000 3328
Area = 14
Address = 000 3584
Area = 15
Address = 000 3840
B–8 3839 6586–010

The following table lists older model McData switch addresses.
Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
0 04 13
1 05 13
2 06 13
3 07 13
4 08 13
5 09 13
6 0A 13
7 0B 13
8 0C 13
9 0D 13
10 0E 13
11 0F 13
12 10 13
13 11 13
14 12 13
15 13 13
16 14 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
3839 6586–010 B–9

Fabric Addresses
Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
17 15 13
18 16 13
19 17 13
20 18 13
21 19 13
22 1A 13
23 1B 13
24 1C 13
25 1D 13
26 1E 13
27 1F 13
28 20 13
29 21 13
30 22 13
31 23 13
32 24 13
33 25 13
34 26 13
SCMS II
(dec)
Exec
(dec)
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
B–10 3839 6586–010

Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
35 27 13
36 28 13
37 29 13
38 2A 13
39 2B 13
40 2C 13
41 2D 13
42 2E 13
43 2F 13
44 30 13
45 31 13
46 32 13
47 33 13
48 34 13
49 35 13
50 36 13
51 37 13
52 38 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
3839 6586–010 B–11

Fabric Addresses
Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
53 39 13
54 3A 13
55 3B 13
56 3C 13
57 3D 13
58 3E 13
59 3F 13
60 40 13
61 41 13
62 42 13
63 43 13
64 44 13
65 45 13
66 46 13
67 47 13
68 48 13
69 49 13
70 4A 13
SCMS II
(dec)
Exec
(dec)
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
B–12 3839 6586–010

Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
71 4B 13
72 4C 13
73 4D 13
74 4E 13
75 4F 13
76 50 13
77 51 13
78 52 13
79 53 13
80 54 13
81 55 13
82 56 13
83 57 13
84 58 13
85 59 13
86 5A 13
87 5B 13
88 5C 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
3839 6586–010 B–13

Fabric Addresses
Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
89 5D 13
90 5E 13
91 5F 13
92 60 13
93 61 13
94 62 13
95 63 13
96 64 13
97 65 13
98 66 13
99 67 13
100 68 13
101 69 13
102 6A 13
103 6B 13
104 6C 13
105 6D 13
106 6E 13
SCMS II
(dec)
Exec
(dec)
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
B–14 3839 6586–010

Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
107 6F 13
108 70 13
109 71 13
110 72 13
111 73 13
112 74 13
113 75 13
114 76 13
115 77 13
116 78 13
117 79 13
118 7A 13
119 7B 13
120 7C 13
121 7D 13
122 7E 13
123 7F 13
124 80 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
3839 6586–010 B–15

Fabric Addresses
Table B–2. Older Model McData Switch Addresses
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
125 81 13
126 82 13
127 83 13
SCMS II
(dec)
The following table lists newer model McData switch addresses.
Exec
(dec)
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
0 00 13
1 01 13
2 02 13
3 03 13
4 04 13
5 05 13
6 06 13
7 07 13
8 08 13
9 09 13
SCMS II
(dec)
Exec
(dec)
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
B–16 3839 6586–010

Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
10 0A 13
11 0B 13
12 0C 13
13 0D 13
14 0E 13
15 0F 13
16 10 13
17 11 13
18 12 13
19 13 13
20 14 13
21 15 13
22 16 13
23 17 13
24 18 13
25 19 13
26 1A 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
3839 6586–010 B–17

Fabric Addresses
Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
27 1B 13
28 1C 13
29 1D 13
30 1E 13
31 1F 13
32 20 13
33 21 13
34 22 13
35 23 13
36 24 13
37 25 13
38 26 13
39 27 13
40 28 13
41 29 13
42 2A 13
43 2B 13
SCMS II
(dec)
Exec
(dec)
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
B–18 3839 6586–010

Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
44 2C 13
45 2D 13
46 2E 13
47 2F 13
48 30 13
49 31 13
50 32 13
51 33 13
52 34 13
53 35 13
54 36 13
55 37 13
56 38 13
57 39 13
58 3A 13
59 3B 13
60 3C 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
3839 6586–010 B–19

Fabric Addresses
Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
61 3D 13
62 3E 13
63 3F 13
64 40 13
65 41 13
66 42 13
67 43 13
68 44 13
69 45 13
70 46 13
71 47 13
72 48 13
73 49 13
74 4A 13
75 4B 13
76 4C 13
77 4D 13
SCMS II
(dec)
Exec
(dec)
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
B–20 3839 6586–010

Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
78 4E 13
79 4F 13
80 50 13
81 51 13
82 52 13
83 53 13
84 54 13
85 55 13
86 56 13
87 57 13
88 58 13
89 59 13
90 5A 13
91 5B 13
92 5C 13
93 5D 13
94 5E 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
3839 6586–010 B–21

Fabric Addresses
Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
95 5F 13
96 60 13
97 61 13
98 62 13
99 63 13
100 64 13
101 65 13
102 66 13
103 67 13
104 68 13
105 69 13
106 6A 13
107 6B 13
108 6C 13
109 6D 13
110 6E 13
111 6F 13
SCMS II
(dec)
Exec
(dec)
Area = 15
Address = 019 3859
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
B–22 3839 6586–010

Table B–3. Newer Model McData Switch Addresses
(ED10000, 4400, 4700)
Port Location
(dec)
McData Switch
(hex)
Port AL_PA
112 70 13
113 71 13
114 72 13
115 73 13
116 74 13
117 75 13
118 76 13
119 77 13
120 78 13
121 79 13
122 7A 13
123 7B 13
124 7C 13
125 7D 13
126 7E 13
127 7F 13
SCMS II
(dec)
Fabric Addresses
Exec
(dec)
Area = 0
Address = 019 19
Area = 1
Address = 019 275
Area = 2
Address = 019 531
Area = 3
Address = 019 787
Area = 4
Address = 019 1043
Area = 5
Address = 019 1299
Area = 6
Address = 019 1555
Area = 7
Address = 019 1811
Area = 8
Address = 019 2067
Area = 9
Address = 019 2323
Area = 10
Address = 019 2579
Area = 11
Address = 019 2835
Area = 12
Address = 019 3091
Area = 13
Address = 019 3347
Area = 14
Address = 019 3603
Area = 15
Address = 019 3859
3839 6586–010 B–23

Fabric Addresses
B–24 3839 6586–010

Appendix C
Key Hardware Enhancements by
Software Release
The following table identifies when key hardware enhancements were implemented.
In some cases, the hardware was released at a later date.
Release Level
Table C–1. Key Hardware Attributes by Release
Exec
Level
Release
Date Significant Changes
OS 2200 9.1 47R4 10/01/04 Dorado 280/290
T9840C
XPC-L
Voyager SCIOP
MIPs Metering
OS 2200 10.0 47R5 4/07/05 Tape Mark Buffering Phase 2 – FAS Portion
I/O Command Queuing
Dorado 240/250 (post-GCA)
OS 2200 9.2 47R4B Sept 2005 Dorado 340/350/380/390
DVD on Dorado 300
I/O Command Queuing
LTO Gen 3 (PLE)
CLARiion MultiPath (PLE)
OS 2200 10.1 47R5B Sept 2005 Dorado 340/350/380/390
OS 2200 11.1 48R1 Nov 2006
DVD on Dorado 300
I/O Command Queuing
LTO Gen 3 (PLE)
OS 2200 11.2 48R2 Oct 2007 Dorado 400
CLARiion MultiPath (PLE)
3839 6586–010 C–1

Key Hardware Enhancements by Software Release
Release Level
Table C–1. Key Hardware Attributes by Release
Exec
Level
Release
Date Significant Changes
OS 2200 11.3 48R3 Sept 2008 Dorado 700
Dorado 4000
LTO Gen 4
512 disks per control unit
T10000A
LTO GEN3
T9840D
OS 2200 12.0 48R4 Jun 2009 24-Bit SAN addressing
4094 Devices per System
I/O Affinity Path Length and AIET
improvements
OS 2200 12.0 + 48R5 Nov 2009 XPC-L Support on Dorado 4000
FICON
OS 2200 12.1 48R6 Jun 2010 Dorado 4100
C–2 3839 6586–010

Appendix D
Requesting Configuration Assistance
For the US and Canada, help for configuring your system can be obtained by
generating an electronic service request at http://www.service.unisys.com/. If you
prefer, contact can be made via phone at 1-800-328-0440 Prompt 2, then 4.
The material needed will vary dependant on present and target system configuration.
It is best to contact CSC and discuss the desired action. In some cases, only minimum
information is needed and can be documented via phone.
Contact points:
• USCT – United States – Canada Theater
− Telephone: 1-800-328-0440 (Prompt 2,4)
• APT – Asia Pacific Theatre
− Telephone: +61-2-9647-7114
− Unisys Limited
− c/o Client Support Centre
1G Homebush Bay Drive
Rhodes NSW 2138
Australia
• Europe – Both UK & CE
− Customer Service Centre
Telephone: Net 741-2521, off-Net +44-1908-212521
c/o CSC Duty Manager
Fox Milne
Milton Keynes
United Kingdom
MK15 OYS
3839 6586–010 D–1

Requesting Configuration Assistance
• LACT – Latin America – Caribbean Theater
− Unisys Brasil LTDA
Customer Service Centre
Telephone: Net 692-8058, off Net +55-11-3305-8058
c/o CSC Duty Manager
Av. Rio Bonito, 41
Veleiros
Sao Paulo SP
04779–900
Brazil
D–2 3839 6586–010

Index
A
access time, 3-20, 3-21
ACS, 7-25
ACSLS, 7-24
address
arbitrated loop, 6-3
I/O, 1-33
LUN, 2-1
SAN, 6-10
SCMS II, 1-35
zones, 6-17
algorithms
disk queue, 3-5
FIFO, 3-4
multiple channels, 3-10
multiple control units, 3-9
multiple I/Os, 3-8
standard timeout, 3-9
Symmetrix, 3-11
arbitrated loop
address, 6-3
control-unit-based disks, 2-7
overview, 6-2
storage area network, 6-7
B
bandwidth
calculations, 5-1
definition, 3-18
block size, 4-20
Brocade switch addresses, B-2
Bus-Tech
FICON, 1-44
C
cable
Ethernet, 8-8
Fibre Channel, 8-2
FICON, 8-8
Gigabit Ethernet, 8-8
SBCON, 8-2
SCSI, 8-1
cartridge library units
description
CLU180, 7-25
CLU5500, 7-25
CLU6000, 7-25
CLU700, 7-25
CLU8500, 7-24
CLU9710, 7-25
CLU9740, 7-25
supported, 9-6
Channel Directors, 3-15
CIOP
bandwidth, 5-2
IOP style, 1-16
300, 1-17
700, 1-18
NIC cards, 8-9
performance, 5-26
style, 8-9
Cipher API Hardware Accelerator Appliance
concurrent requests, 1-62
configuration, 1-61
initialization, 1-62
logical device pairs, 1-61
overview, 1-61
removal, 1-62
CLARiiON disk family
CSM6700, 7-36
CSM6800, 7-36
CX200, 7-36
CX300, 7-35
CX400, 7-36
CX500, 7-35
CX600, 7-36
CX700, 7-35
ESM7900, 7-36
LUNs, 7-33
Multipath, 7-30
overview, 7-29
single point of failure, 7-31
3839 6586–010 Index–1

Index
Unit Duplexing, 7-32
Clock Synchronization Board
connection, 1-58
hardware, 1-60
overview, 1-57, 1-60
time distribution, 1-59
CLU, See cartridge library units
CLU180, 7-25
CLU5500, 7-25
CLU6000, 7-25
CLU700, 7-25
CLU8500, 7-24
CLU9710, 7-25
CLU9740, 7-25
CMPLOFF, 4-23
CMPLON, 4-23
CMS700 JBOD, 7-37
command queuing, 3-6
communications
channel, 2-1
CIOP, 1-16
migration issues, 9-18
performance, 5-26
compression, 4-23
control-unit-based disks
configuration guidelines, 2-32
example application, 2-33
Crossroads converter
configuration, 6-10
overview, 6-9
CSB, See Clock Synchronization Board.
CSC, 7-24
CSM6700, 7-36
CSM6800, 7-36
CSM700, 6-8
CX200, 7-36
CX300, 7-35
CX400, 7-36
CX500, 7-35
CX600, 7-36
CX700, 7-35
D
daisy chain
control units, 3-3
nonredundant, 2-21
redundant, 2-24
DEPCON, See Enterprise Output Manager
device mnemonic, 9-13
direct-connect disks
JBOD characteristics, 2-30
JBOD example, 2-31
directors
communication blocks, 2-40
configuration considerations, 2-38
control of connectivity, 2-40
dedicated connections, 2-41
increased distance, 2-41
operational considerations, 2-38
prohibit dynamic connections, 2-41
resiliency and connectivity, 2-39
share control units, 2-39
disk
data format, 3-13
drives
CSM6700, 7-36
CSM6800, 7-36
CSM700, 7-37
CX200, 7-36
CX300, 7-35
CX400, 7-36
CX500, 7-35
CX600, 7-36
CX700, 7-35
EMC 3330, 7-29
EMC 3630, 7-28
EMC 3730, 7-29
EMC 3830, 7-28
EMC 3930, 7-28
EMC 5330, 7-29
EMC 5430, 7-29
EMC 5630, 7-28
EMC 5730, 7-29
EMC 5830, 7-28
EMC 5930, 7-28
EMC 8430, 7-27, 7-28
EMC 8730, 7-27, 7-28
ESM7900, 7-36
end-of-life devices, 9-13
performance
access time, 3-20
definitions
bandwidth, 3-18
Performance Analysis Routine, 3-19
queue, 3-18
response time, 3-18
server, 3-18
service time, 3-18
throughput, 3-18
utilization, 3-18
Hardware Service Time, 3-23
Little’s Law, 3-25
overview, 3-17
Index–2 3839 6586–010

queue, 3-19
Request Existence Time, 3-27
transfer time, 3-21
subsystem performance
capacity, 3-3
logical subsystem, 3-2
supported devices, 9-7
Symmetrix
8000 Series, 7-27
DMX family, 7-27
disk devices, 9-7
DLT 7000 and DLT 8000 tape
considerations, 7-19
DOR380-CIO, 1-18
DOR380-XIO, 1-18
DOR4000-SIO, 1-18
DOR4000-XIO, 1-18
DOR700-SIO, 1-18
DOR800-CIO, 1-18
DOR800-SIO, 1-18
Dorado 800 IOP style, 1-18
DPREP level 10R3, 9-21
E
EMC hardware
components
cache, 3-15
Channel Directors, 3-15
Disk Directors, 3-15
connectivity, 3-14
data flow, 3-14
disks, 3-15
overview, 3-14
Symmetrix 4.0 ICDA, 7-29
Symmetrix 4.8 ICDA, 7-28
Symmetrix 5.0 ICDA, 7-27, 7-28
Enterprise Output Manager, 7-37
ESM7900, 7-36
Ethernet
cable, 8-8
connections, 1-47
Fast, 1-46
expansion rack, 1-28
F
fast tape access, 4-18
Fibre Channel
9x40 on multiple channels, 2-19
Index
addresses, A-1
arbitrated loop address, 6-3
cable, 8-2
characteristics, 6-1
CLARiiON, 2-10
configuring control-unit-based disks, 2-5
configuring JBOD, 2-2
host bus adapter, 1-37
JBOD, 2-2
OS 2200 characteristics, 6-3
overview, 2-1
SCMS II configurations, 2-2, 2-6, 2-11
SIOP, 1-37
Symmetrix, 2-5
T9x40, 2-16
Fibre HBA, performance, 5-17
FICON, 2-43
Bus-Tech HBA, 1-44
cable, 8-8
channel, 2-42
configuration restrictions, 2-43
installing HBA, 2-44
PXFA-MM FICON HBA, 1-44
SCMS II Configuration, 2-43
switch, 2-46
target address, 2-45
FURPUR COPY options, 4-24
3839 6586–010 Index–3
G
gigabit Ethernet cable, 8-8
H
Hardware Service Time, 3-23
HBA, See host bus adapter.
host bus adapter
Fibre Channel, 1-37
FICON, 1-44
SIOP, 1-37
HST, See Hardware Service Time.
I
I/O address, 1-33
I/O architecture
channel, 3-2
control unit, 3-1
disk, 3-1

Index
overview, 3-1
path, 3-2
subsystem, 3-2
I/O command queuing, 3-6
I/O configuration, disk data format, 3-13
I/O Module, 1-19
IOCQ, 3-6
J
JBOD
CSM700, 7-37
description, 6-8
JBD2000, 7-37
OS 2200 configuration guidelines, 2-3
OS 2200 considerations, 2-3
K
key hardware enhancements, by release, C-1
L
latency time, 3-21
Little’s Law, 3-25
LSI1002-LxH, 1-43
LUNs, 7-33
M
McData Switch addresses, B-9, B-16
media, software
tape, 7-9, 7-12, 7-15
migration
communication issues, 9-18
other issues, 9-21
peripherals, 9-1
tape issues, 9-2
mnemonic, 9-13
N
network interface cards, 1-19, 8-9, 9-19
NICs, 1-19, 8-9, 9-19
nodes, switched fabric, 6-5
Index–4 3839 6586–010
O
open reel (4125), 7-24
Operations Sentinel Shared Tape Drive
Manager, 4-27
OS 2200 characteristics
bytes per sector, 3-13
formatting, 3-12
Multi-Host File Sharing, 3-13
OST4890 tape subsystem
considerations, 7-23
OST5136 cartridge, 7-22
overhead time, 3-21
P
PAR, See Performance Analysis Routine.
PCI Host Bridge Card, 1-20, 5-29, 9-1
PCI standard, 1-14
performance
background, 5-1
bandwidth, 5-1
CIOP, 5-26
Fibre HBA, 5-17
measure, 5-10
resiliency, 5-8
SBCON, 5-23
SCSI, 5-23
SIOP, 5-13
Symmetrix Remote Data Facility, 3-32
Performance Analysis Routine,
definition, 3-19
peripheral
disk subsystems, 7-26
migration, 9-1
printer subsystems, 7-37
ports, switched fabric, 6-5
printer subsystems, 7-37
Q
queue
definition, 3-18
time, 3-19
QuickLoop, 6-8

R
read backward, 4-5
Request Existence Time, 3-27
resiliency, performance, 5-8
response time, definition, 3-18
RET, See Request Existence Time.
ROLOUT, 4-6
S
SAN, See storage area network
SBCON
cable, 8-2
channel characteristics, 2-35
connection, 1-44
description, 1-43
directors, 2-38
overview, 2-35
performance, 5-23
SCMS II configuration, 2-36
SCMS II
arbitrated loop, 6-12
Brocade switch, B-2
CLARiiON, 2-11, 7-30
DVD location, 1-54
EMC system, 2-33
Fabric addresses, B-1
Fibre channel, 2-2
FICON, 2-43
I/O address, 1-35
JBOD, 2-3
LTOGEN, 7-5
McData switch, B-9
OS 2200 console, 6-12
SAN address example, 6-14
SBCON, 2-36
SCSI converter, 2-28
static address, 6-11
storage devices, 6-7
switch addresses, B-1
switched fabric port, 6-6
Symmetrix, 2-6, 3-11
T9x40, 2-16
terminology, 1-35
view of
arbitrated loop, 2-8
daisy chain, 2-21
JBOD, 2-4
nonredundant disks, 2-13
redundant daisy chain, 2-25
Index
switched fabric, 2-10, 2-19
unit-duplexed disks, 2-14
XIOP, 1-36
zones, 6-17
SCSI
cable, 8-1
connect tape to SAN, 2-27
connection, 1-41
control-unit-based disks, 2-32
description, 1-39
direct-connect disks, 2-30
overview, 2-28
performance, 5-23
SCSI-2N devices, 2-29
seek time, 3-21
server, definition, 3-18
Service Time, definition, 3-18
setup time, 3-20
SIOP
bandwidth, 5-2
cable
Fibre Channel, 8-2
FICON, 8-8
SBCON, 8-2
SCSI, 8-1
channels
Fibre, 6-1
SBCON, 2-35
configuration guidelines, 2-3
Fibre Channel, 1-37
IOP style, 1-16
300, 1-17
400, 1-17
4000, 1-18
700, 1-18
location, 1-20
migration, 9-2
performance, 5-13
software
media
tape, 7-9, 7-12, 7-15, 7-19
SORT/MERGE, 4-6
SRDF, See Symmetrix Remote Data Facility.
storage area network
address
12-bit address, 6-12
conventions, 6-11
OS 2200, 6-11
overview, 6-10
arbitrated loop, 6-2, 6-7
nodes, 6-5
overview, 6-1
plan, 6-4
3839 6586–010 Index–5

Index
port addresses, 6-5
storage devices, 6-7
topologies, 6-2
zones
12-bit address, 6-17
24-bit address, 6-17
disks, 6-19
guidelines, 6-17
multipartition, 6-20
overview, 6-17
remote backup, 6-21
tape in multiple zones, 6-18
switch
addresses
Brocade, B-2
for SCMS II, B-1
McData, B-9, B-16
Brocade, 6-7
FICON, 2-46
McData, 6-7
overview, 6-7
switched fabric
overview, 6-4
ports and nodes, 6-5
topology, 6-4
Symmetrix
disk family
8000 series, 7-27
DMX series, 7-27
overview, 7-26
Symmetrix 4.0, 7-29
Symmetrix 4.8, 7-28
Symmetrix 5.0, 7-28
Symmetrix 5.5, 7-27
Remote Data Facility
adaptive copy mode, 3-32
overview, 3-29
performance, 3-32
synchronous mode, 3-30
time delay calculation, 3-33
system performance, 5-10
T
T connector, 1-58
T7840A, 6-8, 7-18
T9840 family
advantages, 4-4
cartridge, 7-19
compression, 4-7
considerations, 4-5
data buffer, 4-8
hardware capabilities, 4-6
operation, 4-5
optimize performance, 4-15
OS 2200 logical tape blocks, 4-10
overview, 4-2
serpentine recording, 4-6
streaming tapes, 4-9
super blocks, 4-8
synchronization, 4-12
tape block ID, 4-13
tape block size, 4-13
tape repositioning, 4-9
T9840A, 6-8, 7-19
T9840A tape subsystem
considerations, 7-12
T9840B, 6-8, 7-18
T9840C tape subsystem
considerations, 7-15
T9940
advantages, 4-4
operation, 4-5
T9940B, 4-3, 6-8
T9940B tape subsystem
considerations, 7-9
tape
compression, 4-8
drives
4125 open reel, 7-24
CLU6000, 7-25
CLU700, 7-25
CLU9710, 7-25
CLU9740, 7-25
OST5136 cartridge, 7-22
sharing, 4-27
T7840A, 7-18
T9840A, 7-19
T9840B, 7-18
migration issues, 9-2
performance, 5-26
supported devices, 9-3
tape considerations
36-track tape subsystems
OST4890, 7-23
DLT 7000 and DLT 8000, 7-19
T9840A, 7-12
T9840C, 7-15
T9940B, 7-9
Tape Mark Buffering
@ASG statements, 4-17
Phase 1, 4-15
Phase 2, 4-16
target address
Index–6 3839 6586–010

FICON, 2-45
throughput, definition, 3-18
time distribution, 1-59
transfer time, 3-21
U
Unit Duplexing, 7-32
utilization, definition, 3-18
X
XIOP
IOP style, 1-16
300, 1-17
4000, 1-18
700, 1-18
Myrinet card, 1-55
NIC card, 8-9
SCMS II, 1-36
style, 8-9
Index
3839 6586–010 Index–7

Index
Index–8 3839 6586–010

*38396586-010*
3839 6586–010