Page 3
Warning: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules.
Page 5
You may (i) use the software on a single machine; (ii) make only one copy of the software into any machine-readable or printed form for backup purposes; (iii) merge the software into other software for your use on the single machine (provided that any portion of the software merged into other software will continue to be subject to the terms and conditions of this license);...
Page 6
Check the DPT web site for availability of an updated version of this manual (SmartRAID V User’s Manual) in Adobe Acrobat PDF format. The current SmartRAID V Quick Install Guide is also available for download from the DPT web site in PDF format. The Quick Install Guide contains text in English, French, German, Italian, Polish and Spanish.
Page 15
A list of parts and accessories you received with your new controller. What type of host system you need to successfully install and use a DPT SmartRAID V controller. Notices regarding electrical safety and electrostatic discharge protection.
Page 16
• The User’s Manual (this book), which contains information that helps you to configure and install your SmartRAID V product and using the Storage Manager software. This document also contains information about using the DPT storage subsystem utility – Storage Manager on ROM;...
Page 17
SmartRAID V controller and manage your storage subsystem. Chapter 7, Theory of Operations – This chapter provides an overview of the technology used in the SmartRAID V series of controllers: caching, RAID, DPT controller architecture, I PCI, SCSI, Fibre Channel and other related topics.
Page 18
Using RAIDstation? Configure Cabinet Refer to: Storage Cabinets and Devices manual Set SCSI ID Fibre Channel? Configure Termination See Chapter 3, Configuration and Installation Add-on Modules? Plug in RA4050 / SX405x Plug in cache memory Plug in BB4050 See Chapter 3, Configuration and Installation Install the controller Attach cables See Chapter 3, Configuration and Installation...
Page 19
2MB of disk space. See Chapter 5, “Software Installation” for information about supported operating systems. All SmartRAID V controllers are PCI 2.2 compliant and are designed to operate in host systems that comply with revision 2.2 of the PCI specification.
Page 20
Throughout this manual are various notices that indicate procedures or practices that can result in loss of data, damage to equipment or personal injury. Be sure to read the following sections for additional information regarding electrical shock hazards and preventing damage from electrostatic discharge.
Page 21
Any device that uses electricity must be treated with caution. Follow these guidelines to ensure general safety. • Keep the chassis area clear and dust-free during and after installation. • Do not perform any action that creates a potential hazard to people or makes the equipment unsafe.
Page 22
Electrostatic discharge (ESD) can damage electronic components and equipment. ESD occurs when electronic components are improperly handled and can result in complete or intermittent failures. Always follow ESD- prevention procedures when removing and replacing components. Use the following guidelines to prevent ESD damage: •...
Page 23
This chapter presents the features of DPT SmartRAID V SCSI and Fibre Channel A look at the features common to controllers, along with the Bus Expansion, SmartRAID V hardware. RAID Accelerator and Battery Backup modules. Specific features of our high performance RAID controller.
Page 24
64MB of onboard cache. • SX405x Bus Expansion Modules add extra SCSI channels or a Fibre Channel port to SmartRAID V controllers. You can use a Fibre Channel expansion module to provide both SCSI and Fibre Channel connections on a SmartRAID V SCSI controller.
Page 25
The following SmartRAID V products and accessories are documented in this manual:...
Page 26
All SmartRAID V controllers include: • Support for I O OSMs provided by major operating system vendors; DPT provides drivers for some operating systems. See Chapter 5, “Software Installation” for a list of drivers supplied by DPT. • Certifications for major operating systems, including Novell NetWare and Windows NT.
Page 27
SmartRAID V Millennium products are high-performance RAID controllers for host computers with a PCI expansion bus. Key features of the Millennium include: • High-performance RISC processor (80 MIPs) • Hardware RAID 0, 1, and 5 • Support for striping multiple arrays as a single logical drive (RAID 0+1 and RAID 0+5) •...
Page 28
SX4055F Bus Expansion Module, Fibre Channel and SCSI buses can coexist on the same SCSI controller (PM375xU2 models only). SX405x Bus Expansion Modules are daughter cards that attach to the SmartRAID V controller and do not require an additional card slot in the host system.
Page 29
SmartRAID V Decade and Century controllers are designed to provide high performance solutions for workstations and servers in environments where cost is a factor. The following Decade and Century controllers are available: The Decade (PM1554U2 ) controller features include: • Onboard I/O processor (31 MIPs) •...
Page 30
SX405x Bus Expansion Modules provide additional channels for SmartRAID V controllers. The SX4055F Bus Expansion Module, can be used to add a FC-AL port to a SmartRAID V Ultra2 SCSI controller or a second Fibre Channel bus to a SmartRAID V Fibre Channel controller.
Page 31
SX405x modules attach to the SmartRAID V controller and do not require an additional slot in the host system: • A single channel SX405xU2-1 Ultra2 SCSI Bus Expansion Module adds one SCSI channel and provides one external Very High Density Cable Interconnect (VHDCI) 0.8 mm connection and one internal high-...
Page 32
The BB4050 Battery Module adds battery backup for the data cache on a SmartRAID V PM3755U2B controller using DPT DM4050 or DM4060 memory modules. The following features of the BB4050 provide additional data security for high-reliability servers: • Nickel Metal Hydride battery pack provides a backup time of 72 hours (using a single 16MB memory module).
Page 33
SmartRAID V controllers provide nine LEDs that let you visually monitor controller activity. Several different controller states are indicated by the LED as outlined in the following sections. Two additional LEDs indicate the status of the cache memory on the controller. See Appendix A, “Assembly Drawings”...
Page 34
Refer to Appendix B, “Troubleshooting” for more information on interpreting LED patterns. Heartbeat Two LEDs on the SmartRAID V controller indicate the status of the onboard cache RAM. Refer to Appendix A, “Assembly Drawings” for the location of the LEDs on your controller.
Page 35
The BB4050 module has two LED indicators labeled CHARGE and TRICKLE. These LEDs indicate the following conditions: Use the Battery Configuration dialog in Storage Manager to view the current status of the BB4050 module. DPT controllers with caching capability (Millennium models or Decade/ Century models using an RA4050 module) have an audible alarm.
Page 37
Configure Devices Your new DPT SmartRAID V controller is the center of a complete system consisting Prepare your SCSI peripherals for of the controller, disk drives and other use by setting their SCSI IDs and termination. Fibre Channel disks peripherals, and the connecting cables.
Page 38
Adapter Configuration and Installation The process of installing a SmartRAID V controller consists of the following steps: If you are using a RAIDstation storage cabinet, configure it as described in the RAIDstation User’s Manual. Configure device IDs, cables and termination for SCSI devices in the host system.
Page 39
Wide devices. This ensures that the 16-bit signals are correctly terminated. SmartRAID V SCSI controllers contain a single Wide SCSI bus with one internal and one external SCSI connector. Each SmartRAID V SCSI controller kit contains a Wide, 68-conductor SCSI cable. This cable is for connections internal to the computer cabinet only.
Page 40
If you are using multiple SCSI busses on a single controller, each separate bus must be terminated. SCSI termination for SmartRAID V controllers is configured through the SMOR utility or from the Configure Host Bus Adapter window in Storage Manager. The controller has four possible termination settings: By using a 68-pin to 50-pin SCSI cable adapter, an 8-bit SCSI device can be attached to a Wide SCSI cable along with Wide SCSI devices.
Page 41
Adapter Configuration and Installation The following illustrations show various SCSI cabling examples. Terminate your SCSI devices as shown in the examples, ensuring that only the devices at the ends of the cables are terminated.
Page 42
Set the SCSI ID of each SCSI device attached to the controller to a unique ID number between 0 and 6. The SmartRAID V controller is set to ID 7 by default (most SCSI controllers use ID 7.) Wide SCSI devices can also use SCSI IDs 8 through 15.
Page 43
Adapter Configuration and Installation NOTE SmartRAID V Millennium controllers and Century or Decade controllers with an RA4050 module should have at least 16MB of cache installed. Several optional modules are available to upgrade the performance of your SmartRAID V controller: •...
Page 44
Adapter Configuration and Installation SmartRAID V Century controllers can be upgraded to support RAID 5, 0+5 and data caching by installing the RA4050 RAID Accelerator module. A Decade (PM1554U2) controller has built-in RAID 5 and 0+5 support without an RA4050 module. Adding an RA4050 module to a Decade controller provides up to 64MB of cache and hardware XOR performance for RAID 5 operation.
Page 45
Adapter Configuration and Installation SmartRAID V controllers accept the following Bus Expansion Modules: SX4054 Bus Expansion Modules are intended for use with Decade or Century controllers. For a 64-bit Millennium controller, use an SX4055x Bus Expansion Module. Up to 15 devices may be attached to each SCSI bus. Up to 125 devices can be attached to the SX4055F Fibre Channel Bus Expansion Module.
Page 46
Adapter Configuration and Installation To install an SX4054/SX4055 module: Remove the module mounting bracket from the end of the module. Keep the bracket screws. Attach the module to the controller, connecting P5 on the SX405x to J7 on the controller. Refer to Appendix A, “Assembly Drawings” for connector locations.
Page 47
256MB of cache using four onboard SIMM sockets. One to four memory modules of the same type and capacity can be installed. SmartRAID V Decade and Century controllers can use up to 64MB of cache provided by the SIMM sockets on an RA4050 module. One to four SIMMs of the same type and capacity can be installed.
Page 48
60ns EDO SIMMs can be used, DPT recommends that you use DPT SM4050-16 or -64 ECC SIMMs for maximum data integrity. To confirm that the SIMMs have been properly installed, use SMOR to view the amount of cache memory reported when the SmartRAID V controller is selected.
Page 49
Install the DIMMs in the sockets as shown starting with socket 1. Refer to Appendix A, “Assembly Drawings” for socket locations. To confirm that the DIMMs are properly installed, start SMOR and select the SmartRAID V controller to display the amount of cache memory reported.
Page 50
Adapter Configuration and Installation The BB4050 Battery Backup Module is used only on a PM3755U2B Millennium controller. To install the BB4050 Module: Before installing the BB4050 module, be sure the battery pack electrical connector is plugged in the socket on the BB4050 board. Align the Battery Backup Module and the Millennium controller as shown in the illustration.
Page 51
Adapter Configuration and Installation Connect the computer’s disk activity LED cable to connector P6 on the controller. See Appendix A, “Assembly Drawings” for the location of this connector. Pins 1 and 3 of P6 are connected to +5V and pins 2 and 4 are connected to GND.
Page 52
O BIOS occupies the lowest address if you want the DPT controller to be the booting controller. • In systems with multiple DPT SmartRAID V controllers, the DPT controller in the lowest PCI slot number will be assigned the lowest BIOS address, and will be the booting controller.
Page 53
Adapter Configuration and Installation SmartRAID V controllers retain their setup parameters even when powered off. These parameters are stored on the controller in an area of nonvolatile memory (NVRAM). There is a possibility that, through improper configuration, the controller can be put into a state where it hangs the system during boot.
Page 54
Adapter Configuration and Installation The information presented in this section is intended to help you configure SmartRAID V controllers and a storage subsystem for host systems that use Microsoft Cluster Server (MSCS) to provide fault-tolerant network server resources. For specific information about installing and configuring MSCS support on your Windows NT server, refer to the Microsoft Cluster Server Administrator’s Guide.
Page 55
Refer to the Microsoft Cluster Server Administrator’s Guide for additional information. • Create a server cluster with two host systems that have SmartRAID V controllers that are connected to a common storage subsystem. The shared storage must use the NTFS file system.
Page 56
The cluster servers must be restarted to ensure that the deleted array does not continue to be reported as available. NOTE Both SmartRAID V controllers must be connected to the shared storage subsystem using special cables that include pass- through termination. These cables can be purchased from DPT.
Page 57
Storage Manager on ROM (SMOR) is a BIOS-based setup utility that lets you Run SMOR by pressing Ctrl+D configure your DPT SmartRAID V controller during system boot. without starting an operating system and using Storage Manager. You can also use SMOR to perform basic array configuration.
Page 58
To configure your hardware and create disk arrays when Storage Manager is not available, run Storage Manager on ROM (SMOR) during the system boot. This is especially useful for a new system where you need to create disk arrays before you install the operating system. After your storage subsystem is configured, install your operating system according to the appropriate procedure in Chapter 5, “Software Installation”.
Page 59
The navigation keys work in a similar fashion to those of Windows Explorer. Use these keys to move around in SMOR:...
Page 60
The SMOR Main Menu changes dynamically depending on what is selected in the tree view. The following is a complete list of possible selections: SMOR uses the following icons in Tree View: Array Controller Disk CD-ROM Tape Other Device...
Page 61
The SMOR interface works like the Windows Explorer tree-structured interface. The screen is divided into three major components: a menu bar across the top of the screen and two display panes below the menu bar. Information & Configuration Tab Pages Menu Bar Tree View To open a specific menu, press...
Page 62
The Tree View, displayed in the left pane, is the central control for SMOR. This view displays a tree structure that represents the organization of the DPT storage subsystem. This includes DPT controllers, storage devices and arrays detected by SMOR. By moving the highlight with the up and down arrows, you can select items you want to view or configure.
Page 63
Within the Information View, you select an item to configure by using the keys to move the highlight to the item. Items that cannot be selected are shown in black. The way in which you change an item depends on the type of control associated with it. Check-boxes are toggled by using the .
Page 64
Start SMOR by pressing when the DPT I O BIOS message appears on the screen during the boot sequence. The letters that appear during the initial device scan process are: CD-ROM Disk drive Scanner, SAF-TE or intelligent RAID enclosure, or a second controller (MSCS).
Page 65
When you highlight an item within the Tree View, the corresponding Information View is displayed. The example above is the default Information View when SMOR starts. The settings in this view affect the DPT I O BIOS and all the DPT controllers in your system.
Page 66
Tree View after power on, set the delay to a longer interval. This setting determines the way that SmartRAID V controllers handle Extended BIOS Data Area (EBDA) relocation. You can enable this feature to help avoid conflicts with other adapter cards if the controller is installed in a host system with other adapters that follow standard EBDA relocation rules.
Page 67
To view or change the configuration of a DPT RAID Controller, highlight the controller in the Tree View. Two tabs are available: Information and Configuration. The Information Tab for a Controller displays general information reported by that controller. Some of the fields have special conditions:...
Page 68
can be reported as: SCSI Expansion Module* Fibre Expansion Module* RAID Accelerator Battery Backup Module *Bus Expansion Modules are always reported as either . SMOR is not able to determine which specific model is attached. Memory modules are reported as: Starting with Bank 0.
Page 69
To modify the hardware parameters for the highlighted SmartRAID controller, press to display the Configuration tab. Select to reset the parameters on this tab to their default values. NOTE Depending on the specific hardware, some items displayed in the Configuration tab may be read-only. The settings are subdivided according to which parameters relate to the individual peripheral bus and which parameters relate to the entire controller.
Page 70
SmartRAID V controllers are configured by default at SCSI ID 7. This value should not be changed unless required for special configurations. NOTE Fibre Channel IDs can be 0 – 126. However, these IDs are configured dynamically and cannot be changed using SMOR or Storage Manager.
Page 71
Individual devices are listed in the Tree View under the controller to which they are connected. Highlight a device to view its configuration information. The Device Information view displays general device information and hardware configuration. This view is divided into three parts: Identification, Capabilities and Status.
Page 72
The capabilities section is a list of the capabilities defined in the SCSI specifications. A checkmark indicates that the device supports that SCSI function. The following status conditions can be indicated for attached devices:...
Page 73
SmartRAID V controllers implement RAID 0, 1 or 5 disk arrays in hardware. RAID 0 arrays are composed of any combination of individual drives. RAID 1 arrays are always composed of two drives. RAID 5 arrays contain three or more drives.
Page 74
The identification section displays a general description of the highlighted array: This section displays the SCSI capabilities of the array, as reported to the operating system. The capabilities reported depend on the devices that were used to create the array. This field displays the current status of the array.
Page 75
There are two configuration options on the File menu: Causes SMOR to rescan to detect any changes in hardware configuration or status. Any changes that have been made and not saved are lost. This operation is run automatically when SMOR is started.
Page 76
You can use SMOR to create or manage disk arrays. The following sections describe how to use SMOR to create arrays and parity groups, delete arrays, assign hot spare drives, and rebuild an array. Refer to the Chapter 7, “Theory of Operation” for a complete discussion of RAID levels and disk arrays.
Page 77
b. To remove a previously selected device from the array, highlight the device and press the When you are finished selecting drives for the new array, select If you are creating a RAID 1 array, the RAID-1 Build Option dialog appears.
Page 78
Creating a parity group (RAID 0+1 or 0+5) is similar to creating a normal RAID 1 or RAID 5 array group. Do the following to create a RAID 0+1 or RAID 0+5 parity group: Create and build your array groups as described in the preceding section (Creating an Array).
Page 79
To delete an array, follow the steps below: In the left pane, highlight the array that you want to remove, then select You will be warned that all data will be lost. Choose The array configuration for the devices is not deleted until you select or exit SMOR and choose to save your changes.
Page 80
512 bytes you must change the format to 512-byte sectors before you can use the drive with a SmartRAID V controller. You can use SMOR to start a low-level format operation and create a 512 byte/sector format.
Page 81
SMOR includes several features that let you upgrade, save and restore the firmware on your SmartRAID V controller. These options are listed on the menu when a controller is selected in the Tree View. feature lets you install the latest DPT controller firmware, O BIOS and SMOR utility software.
Page 82
Do the following to upgrade controller NVRAM, firmware, I O BIOS, or SMOR utility: Place the diskette containing the image files in the diskette drive of the system where the controller is installed. In the Tree View, select the controller that you want to update. Select .
Page 83
This feature provides you with a way to save the current ROM software and NVRAM settings for your controller to a bootable diskette. The resulting diskette is a bootable disk and contains a copy of the three controller software components: firmware, I2O BIOS and SMOR. The utility also saves the current and default NVRAM settings.
Page 84
To create the firmware backup diskette: Press when the DPT I2O BIOS banner appears during system startup to start SMOR. Move the highlight to the controller that you want to backup. Insert a blank, formatted diskette into the host diskette drive. NOTE This operation overwrites the entire diskette.
Page 85
Your new SmartRAID V controller uses I drivers that may be supplied by DPT or your A DPT I O driver is supplied with operating system vendor. This chapter your controller. discusses driver and operating system installation when using SmartRAID V controllers.
Page 86
The DPT SmartRAID V driver for Windows NT 4.0 provides support for both disk drives and other SCSI devices, such as CD-ROMs and scanners. NOTES • Windows NT must be updated with Service Pack 4 or later. • If you choose the Microsoft I O OSM in place of the DPT class or miniport driver, you will not be able to use Storage Manager.
Page 87
Windows NT. During the Windows NT installation, you will need one blank high-density diskette to create an Emergency Repair Diskette. To install a SmartRAID V controller and Windows NT 4.0 into a new computer system, follow the steps below: Install the SmartRAID V controllers and storage devices according to the instructions in Chapter 3, “Configuration and Installation”.
Page 88
Windows NT mass storage detection, follow the steps below: Install the SmartRAID V controllers and storage devices according to the instructions in Chapter 3, “Configuration and Installation”. Boot your system and run SMOR to verify your configuration.
Page 89
If you are removing the old DPT controller, you should also remove the old driver. To add a DPT SmartRAID V controller to an existing Windows NT 4.0 system, do the following: From Control Panel, select the SCSI Adapters icon. Then select the Drivers tab and click Add.
Page 90
O OSM in place of the DPT miniport driver, you will not be able to run Storage Manager. To add a DPT SmartRAID V controller to an existing Windows NT 4.0 system using the Microsoft Windows NT OSM, do the following:...
Page 91
Each of these cases requires a slightly different procedure. This section describes the steps to install Windows 98 (Full Installation Version) on one disk drive or array group using a SmartRAID V host controller. Ensure that your hard drives, arrays, CD-ROM drive, and any other SCSI device attached to the host controller are recognized by SMOR before proceeding.
Page 92
If you are installing the operating system, go back to step 12 and continue the procedure. If you are adding a SmartRAID V to an existing configuration, go to step 3 on page 5-12 and continue with the procedure.
Page 93
This section describes the steps to install Windows 95 (OEM SR2 Version) on one disk drive or array group using a SmartRAID V controller. Ensure that your disk drives, arrays, CD-ROM drive, and any other SCSI devices attached to the controller are recognized by SMOR before proceeding.
Page 94
If you are installing the operating system, go back to step 12 and continue the procedure. If you are adding a SmartRAID V to an existing configuration, go to step 3 on page 5-12 and continue the procedure.
Page 95
, the process continues as a normal installation on a new system. This section describes the steps to install a SmartRAID V controller to an existing Windows 95/98 configuration. Ensure that your hard drives, arrays, CD-ROM drive, and any other SCSI device attached to the controller are recognized by SMOR before proceeding.
Page 96
If you are installing the operating system, go to step 12 on page 9 and continue the procedure. If you are adding a SmartRAID V to an existing configuration, go to step 3 and continue the procedure.
Page 97
When the SmartRAID V controllers are properly recognized by Windows, from the DPT Windows 95/98 diskette and follow the on-screen prompts to install the Storage Manager software. The installation program detects which version of Windows you are using and installs the appropriate Storage Manager files for your operating system.
Page 98
A diskette for SCO UNIX 3.2V4.2 and SCO UNIX OpenServer 5 (3.2V5.x) is included with your SmartRAID V controller. The DPT diskette for SCO contains the drivers for both versions of SCO. A second diskette contains a Motif version of DPT Storage Manager for each version of SCO UNIX.
Page 99
Rebuild the kernel after the package is installed. Shutdown and reboot the system to install the new kernel and add devices on the controller. Install the SmartRAID V controller as in Chapter 3, “Controller Configuration and Installation”. Obtain the latest I...
Page 100
“diskadd” is run and can be ignored. Use the utility to add drives or arrays that are attached to a SmartRAID V controller. Run the sdiconfig –l utility in a terminal window or non-GUI screen. This will list all controllers recognized by the operating system and any attached devices.
Page 101
You must follow the procedures in the following sections to installing a SmartRAID VI controller for Novell NetWare, especially as a booting controller. There are specific steps that must be completed to ensure that NetWare will recognize the DPT controller and any attached devices. The DPT diskette for NetWare contains the device drivers you need to install a DPT controller for NetWare 4.2 and 5.0.
Page 102
This section describes how to install a SmartRAID VI controller as a boot device for NetWare 4.11 servers. NOTE Part of this procedure requires that you have enough free space on your C: drive to hold the contents of the NetWare CD-ROM.
Page 103
This section describes how to integrate a DPT SmartRAID VI controller into a new or existing Novell NetWare 4.11 system as a secondary controller. Ensure that your NetWare version is at the minimum patch level specified by Novell. NOTE The server must have patch kit IWSP4 or later installed to use the drivers supplied by DPT.
Page 104
This procedure is for installing a SmartRAID VI controller as the boot device in a NetWare 4.2 server. Install the SmartRAID VI controller as the primary controller and attach the disk drives or storage subsystem. Ensure that you are using a CD-ROM that is not attached to the DPT controller.
Page 105
This section describes how to integrate a DPT SmartRAID VI controller into a new or existing Novell NetWare 4.2 system as a secondary controller. Ensure that your NetWare version is at the minimum patch level specified by Novell. NOTE NetWare 4 Support Pack 8 contains the latest Novell I drivers.
Page 106
Use the following procedure to install support for a SmartRAID VI controller during installation of NetWare 5. The controller should be installed at the beginning of the procedure so that it can be detected by the install routine. Install the DPT controller as the primary controller and attach the disk drives.
Page 107
This section describes how to integrate a DPT SmartRAID VI controller into a new or existing Novell NetWare 5.0 system as a secondary controller. Ensure that your NetWare version is at the minimum patch level specified by Novell. NOTE NetWare 5 Support Pack 4 contains the latest Novell I drivers.
Page 108
Linux support for DPT SmartRAID V controllers. file is a HOWTO document that describes the installation of a SmartRAID V controller in a system using Linux. DPT controller and RAID management is available through the DPT SMOR utility or Storage Manager for Linux. Storage Manager for Linux requires Linux 6.x (kernel version 2.2.5 or higher).
Page 109
These instructions are for installation of the DPT device driver for Linux on a system using Red Hat Linux 5.2 or 6.0. Install and configure your DPT controller according to the instructions in Chapter 3, “Configuration and Installation”. If you want to install Linux on a disk array, use SMOR to configure any disk arrays before beginning the operating system installation.
Page 110
When prompted, insert the DPT driver diskette and press You will be prompted for the language and keyboard type. You will be asked to specify the location of the media packages to be installed. If you are installing from CD-ROM, select .
Page 111
When the download is complete, run the following command from the prompt: tar -xvf linsm218.tar After the file extraction is finished, run the following command from the prompt: ./install You will be asked if you want the DPT Communication Server to load on boot.
Page 113
– to providing online event logging and performance statistics. Each physical or logical storage SmartRAID V controllers also include device is shown as an icon. To Storage Manager on ROM, which lets you display information or configure the build disk arrays prior to installing your device, click on its icon.
Page 114
DPT Storage Manager is included with your SmartRAID V controller. This utility performs several functions: • Checks hardware configuration. • Allows you to create, expand or delete disk arrays. • Provides online functions for the DPT storage subsystem such as event logging and notification, array status and I/O statistics.
Page 115
You can run Storage Manager: • On the same computer that contains the DPT hardware and peripheral devices (local operation). • Remotely, across a TCP/IP network. This lets you view and configure servers from remote locations. • In demo mode, where Storage Manager simulates a storage subsystem that contains various types of DPT controllers and peripheral devices.
Page 116
Storage Manager on ROM (SMOR) is a ROM-based version of Storage Manager which is provided on your SmartRAID V controller. If you are installing a new system, use SMOR to configure your RAID subsystem prior to installing your operating system.
Page 117
button toggles between the Physical Configuration View and the Logical Configuration View window. starts the process of creating a RAID logical disk. will print a text report of the subsystem configuration.
Page 118
On the right side of the Logical Configuration View window are all physical devices that are attached to DPT controllers. On the left side of the window are the associated logical devices as seen by the host computer. Non-disk devices use the same icon for both logical and physical views. Disks drives can be seen either as individual drives or as members of arrays.
Page 119
The controller to which the device is attached. PCI bus slots are scanned from lowest to highest looking for DPT controllers. As DPT controllers are found they are assigned numbers incrementally, starting with 0. The controller bus to which the device is attached. SmartRAID V controllers can have up to three buses.
Page 120
Manager will prompt you to select an unused logical device address for that drive. Status is reported by SmartRAID V controllers for arrays and drives. Some status conditions are indicated by Storage Manager through status flags on the drive or array icons. View the information window for the drive or array to see specific status information.
Page 122
Double click on a controller or device icon to display an Information window for that controller or device. The Host Bus Adapter Info window displays configuration information reported by that controller. The Controller section displays the revision and amount of installed .
Page 123
NOTE During the initial calibration cycle for a BB4050 module, the controller disables automatic, low-battery write-through mode. After the calibration, use the Battery Backup Configuration dialog to set a threshold for entering write-through mode when the battery charge drops below a predetermined level. This option lets you view the status of the BB4050 Battery Backup Module and set operating parameters when the battery capacity reaches a predetermined level.
Page 124
Click the button to set the Battery Capacity Warnings to their default values. Actual default values are calculated by the controller based on the size of the cache memory. Battery Module status is reported as one of the following: The Initial Calibration operation is started when a BB4050 Battery Backup Module is first installed on a controller.
Page 125
When this option is selected, the date of the most recent Maintenance cycle is displayed. To modify hardware parameters for the SmartRAID V controller, click the button in the Host Bus Adapter Info window. The Configure Host Bus Adapter window appears.
Page 127
Buttons available are: – lets you test the audible alarm on the controller. – displays the Flash Configuration dialog to update the controller firmware and BIOS. – allows you to select the controller cache parameters. – resets the controller configuration to factory default settings. –...
Page 128
Configure Host Bus Adapter window. The SmartRAID V controller manages its data cache according to built-in algorithms (see Caching Configuration in this chapter and Chapter 7, “Theory of Operation” for additional information). If you are using Windows NT 4.0, do the following to ensure optimum performance:...
Page 129
This window displays the following information: The manufacturer and model. The drive firmware version. The logical address of the device. Storage capacity of the device in megabytes. For removable media disk devices, is reported for the currently inserted media. Disk devices also display the number of on the media along with the sector size.
Page 130
The data can also be cached for subsequent read commands. The Predictive Cache checkbox enables and disables the predictive caching feature on SmartRAID V controllers. By default the box is not checked and the feature is disabled.
Page 131
Predictive caching is a feature of SmartRAID V controllers that attempts to reduce average disk access time by determining when the host is requesting data that it read previously and reading in additional sequential data before it is actually requested.
Page 132
From the Logical Configuration View, you can double-click on an Array Group icon to display the Array Group Information window. Information windows for arrays that are part of a Parity Group can be viewed by clicking on the icons for those arrays.
Page 133
The Array Group Information window displays the following information: NOTE The availability of the various buttons depends on the current configuration and state of the array. Buttons include button will appear for redundant arrays that have a failed drive. For arrays that are building or rebuilding, a button is displayed.
Page 134
To create an Array Group, do the following: Click the button. The Select Array Type dialog appears. Specify whether or not you want (RAID 1 or 5) (RAID 0) Select whether the array is to be (RAID 5) or (RAID 1). As you make your selections, the change to indicate which RAID level and stripe size best suit your selection.
Page 135
During the drive selection process some drives might be displayed in a blue color. This indicates that these drives cannot be included in the array unless you change the configuration. You must either select more drives for the array or remove one or more drives from the array.
Page 136
NOTE Dynamic Array Expansion is available only for arrays created with SmartRAID V controllers running in a Windows NT host system. Dynamic Array Expansion allows you to increase your storage capacity by adding one or more drives to your RAID 0 and RAID 5 arrays while your system remains online.
Page 137
NOTE There is a significant impact on system performance during array expansion. The relative priorities given to system performance and the array expansion process can be adjusted by use of the Background Task Priority setting in Storage Manager. Dynamic Array Expansion maintains the performance gains of RAID 0 and RAID 5, spreading accesses randomly across the drives in the array.
Page 138
NOTE If a drive fails during expansion, the expansion will complete successfully. However, the new, larger array will be in a degraded state until the problem is fixed. If there is a Hot Spare associated with the array, the degraded array is rebuilt using the Hot Spare.
Page 139
When you are finished choosing drives, click . The icon for the Array Group appears with a black flag until the expansion process is started. Select to start the array expansion. The status flag on the Array Group turns blue and the flags on the components turn white during the expansion process.
Page 140
To delete an Array Group, do the following: From the Logical Configuration View window, select the LSU or Array Group icon of the array you want to delete. Then click Click when the confirmation message appears to complete the delete operation. Click to exit without deleting the Array Group.
Page 141
Events are generated for detected fault conditions as well as subsystem status changes. The events are grouped into four categories as follows: 1 – Soft Error An operation on a disk drive that caused an error but was successful after a retry. 2 –...
Page 142
When events occur, they are automatically logged in the cache on the SmartRAID V controller where they occurred. In addition, you can specify that Storage Manager maintain an event log on disk (see Event Notification). The contents of the event log can be displayed by clicking in any controller, drive or array information window.
Page 143
If your operating system supports a Broadcaster, Storage Manager lets you specify that event messages be sent to users, groups, devices, through e-mail, to the system error log and the DPT Log File. Select to display the Event Broadcasting dialog. The options in the Event Broadcasting dialog may vary depending upon your operating system.
Page 144
You can select or modify the following parameters:...
Page 145
DPT Storage Manager for Windows NT can also send event messages to alphanumeric paging devices. The messages are sent as e-mail to pagers that support e-mail text message delivery. NOTE: This feature should work with any alphanumeric paging system that supports message delivery via e-mail. Contact your service provider for specific information.
Page 146
Broadcasters are provided on the DPT diskettes for Windows NT, SCO UNIX and SCO UnixWare. The Broadcaster collects events logged by DPT controllers in the host computer on which that broadcaster is running. The Broadcaster records these events to disk files for each controller for use by Storage Manager.
Page 147
DPT provides a Broadcaster for SCO UNIX 3.2V4.2, SCO OpenServer 5 and SCO UnixWare 7. The Broadcaster collects events from DPT controllers and saves them to files in the directory for use by Storage Manager. Events can also be sent to an ASCII file, specified devices, the User/Group list or e-mailed to users as specified in the Event Broadcasting dialog.
Page 148
The Windows NT Broadcaster collects events from DPT controllers and records them to files in the \ directory for use by Storage Manager. Additionally, events are sent to the Windows NT Event Viewer. When the DPT installation program runs, the Broadcaster is copied to the subdirectory by default.
Page 149
This window displays a list of the events submitted to the Application Log by the DPT Broadcaster, as well as other applications. Events are single- line entries that contain the following information: An icon that indicates the Windows NT severity level for the event.
Page 150
SmartRAID V controllers can perform a low-level format on attached fixed disk drives. This function is available from the SCSI Device Information window in Storage Manager. SmartRAID V controllers format drives in standard 512-byte format. A low-level format is not normally required before using a disk drive.
Page 151
Drive failures are indicated by flags on the icons associated with the Array Group, array and individual drives. Failure conditions are indicated as follows: A drive belonging to an Array Group fails The drive icon displays a red flag in both the Physical and Logical Configuration Views.
Page 152
NOTE If you are using a DPT RAIDstation storage cabinet with a SmartRAID V controller, failed drives can be replaced and rebuilt without using Storage Manager. RAIDstation storage cabinets and drives have hot swap (SCA-2) connectors so that failed drives can be removed or replaced without first quieting the bus.
Page 153
To assign a drive as a Hot Spare, click in the drive’s SCSI Device Information window. Click to reassign an existing Hot Spare drive as a normal drive. Any drive that is not assigned to an array can be assigned as a Hot Spare. Hot Spares are reserved to automatically replace failed drives in RAID 1 or 0+1 and RAID 5 or 0+5 arrays and cannot be accessed by the operating system for data storage.
Page 154
Running a Verify operation for RAID 1 and RAID 5 arrays ensures that the redundant information contained in the array is consistent. This operation is performed by the SmartRAID V controller concurrent with normal system operation and requires no user or host computer intervention.
Page 155
You can run rebuild and verification operations without taking an array offline. These functions are performed as background tasks on the SmartRAID V controller and are transparent to the host operating system. However, the controller interleaves I/O from the operating system with I/O from the background task and this can affect system performance.
Page 156
SmartRAID V controllers keep a cumulative record of I/O operations in cache RAM for use in analyzing the efficiency of the storage subsystem. You can view this data by selecting in the Information window for any, controller, drive or array. By analyzing these statistics, the array configuration, cache and stripe size can be optimized for your particular system configuration.
Page 157
Command Statistics = the total number of sectors written to disk by the controller.
Page 158
In RAID 1 arrays, can be up to twice the value of because each sector written from the host results in a write to each mirrored disk. In RAID 5 arrays, each write from the host can generate up to two disk reads and two disk writes. If the controller has cache memory, this can result in the actual number of sectors read from or written to disk being reported as less than this value.
Page 159
If cache hits are low, adding more cache RAM can also increase the hit count. Systems with a large number of disk writes also derive significant performance benefits from the controller cache. For RAID 0 and RAID 5 arrays, the default stripe size is set for optimal performance in most environments.
Page 160
The Storage Manager Remote Communication feature lets you use Storage Manager running on your local workstation to manage remote server systems that contain DPT controllers. The Available Connections window shows the types of connections you can use and any predefined connections you have created.
Page 161
Storage Manager can run as a client/server application across a network using a TCP/IP connection. The Storage Manager client runs on a supported workstation operating system and connects to one of the supported networked servers running the DPT communication engine. The following illustration shows the supported workstation and server connections for a TCP/IP network.
Page 162
You must configure Remote Communication before it can be used. For both workstations and servers, this is done by editing the DPT configuration file ( ). There may be additional server configuration steps, depending on your operating system. You must have physical connections between the servers and client workstations.
Page 163
If you are using an operating system that supports the DPT communication server and selected the Communication Server option during Storage Manager setup, the server was automatically installed at that time. Additional steps may be required to complete the installation, depending on your operating system.
Page 164
Under SCO UNIX, a communication server entry is placed into the files, which causes it to be started when the system is booted into multi- user mode. During installation, the file is created in the directory into which Storage Manager is installed. The ownership of this file is set to , and permissions are (660 -rw-rw---...
Page 165
Select to use Storage Manager to manage DPT hardware in a remote server system using the remote communication feature. This menu item displays the Available Connections window. NOTE: You can also use the IP= address command line parameter when you start Storage Manager. This parameter causes Storage Manager to connect to the remote system at the specified IP address instead of the default Local connection.
Page 166
Under the section of the Available Connections window, there is an icon the TCP/IP protocol that you configured in the file, and an icon for the system you are using ( To make a connection to a remote system, click the icon that represents the protocol for that system.
Page 167
You can save the server name, address, user name and protocol of systems you frequently access in the Phonebook. After you have entered data for a system, you can place an icon under make future connections to that system without having to reenter the connection information each time.
Page 168
Under the Custom Connections section of the Available Connections window, there is one icon for each system that you marked for display in the Phonebook. To make a connection to a remote system, double-click the icon. The Connection Information dialog appears. Enter the password of the server selected.
This chapter provides background and Chapter Topics: reference information about: • Intelligent RAID Controllers • Pipelined Parallel Processing • Operation of SmartRAID V controllers • Caching Algorithms • Disk array configuration • RAID Levels • SCSI device interfaces and cabling •...
Page 170
Theory of Operation File servers achieve maximum throughput when the performance of their component subsystems is optimized for the CPU bandwidth. If any component is not capable of supplying data at an optimum rate, that component will restrict the data path performance and slow down the entire system.
Page 171
CPU. Intelligent I/O frees the CPU to process user application software and requests, which significantly increases data throughput and overall system response. DPT SmartRAID V controllers implement intelligent I/O using an onboard RISC microprocessor. Controllers that depend on the host CPU for processing low-level I/O functions can require a significant portion of the total processing power of the system: from 25% to nearly 100%, depending on the task.
Page 172
I O compliant products. This design allows for much faster device driver development for specific operating system platforms. For additional information, see the SmartRAID V Architecture section in this chapter. I O Split Driver Architecture HOST OS Specific...
Page 173
• Real-Time Control System – P technology can process a virtually unlimited number of host commands in parallel. The SmartRAID V Real-Time Control System (RTCS) breaks each command down into sub-tasks that are then routed to one of the following hardware processors on the controller: –...
Page 174
The total amount of cache space supported by a SmartRAID V controller is fixed. Some of this total cache space is used when physical memory modules are installed on the controller to be used for standard cache.
Page 175
When cache RAM is added to a SmartRAID V controller, the operating system cache buffers must still be flushed. However, the controller receives and caches the flushed data in a fraction of the time required to actually write to a disk.
Page 176
1 second instead of 11 seconds. The SmartRAID V controller can then flush its cache to disk in elevator-sorted order using its separate I/O bus, concurrently with other system activity.
Page 177
I/O for the host system. This section describes the methods and rules used by SmartRAID V controllers to cache data for host I/O operations. Write-back is a method of postponing data to be written to a peripheral device, such as a disk drive, by temporarily saving the data in a cache.
Page 178
SmartRAID V controllers use virtual cache to track the patterns of data access for the most recently accessed disk data without actually caching that data.
Page 179
7-11 Theory of Operation The SmartRAID V pre-fetch algorithm analyses disk access patterns to detect whether the host is reading data that it previously read. By using records stored in virtual cache, the caching algorithm determines the boundaries of the contiguous block of previously read data surrounding the current host read request, then reads that data block into cache.
Page 180
Most operating systems that have caching capability can automatically manage the size of their disk cache. The SmartRAID V cache is used for predictive reads, elevator sorted write-backs and as temporary storage during RAID 5 parity calculations. Increasing the size of the cache makes these features more efficient. More cache RAM allows the controller to hold and elevator-sort more records, resulting in closer spacing between consecutive write-back segments.
Page 181
7-13 Theory of Operation The basic idea of RAID (Redundant Array of Independent Disks) is to combine multiple inexpensive disk drives into an array of disk drives to obtain performance, capacity and reliability that exceeds that of a single large drive. The array of drives appears to the host computer as a single logical drive.
Page 182
7-14 Theory of Operation STRIPING DISK DRIVES Disk 1 Disk 2 Disk 3 Disk 4 Data stripes from each drive are interleaved to create one logical drive. By striping the drives in the array with stripes large enough so that each record falls entirely within one stripe, most records can be evenly distributed across all drives.
Page 183
ECC information. Because all disk drives today embed ECC information within each sector, RAID 2 offers no significant advantages over other RAID architectures and is not supported by SmartRAID V. RAID 2 Parallel Array with ECC Each write operation spans all drives.
Page 184
Synchronized-spindle drives are required for RAID 3 arrays in order to avoid performance degradation with short records. Because RAID 5 arrays with small stripes can yield similar performance to RAID 3 arrays, RAID 3 is not supported by SmartRAID V. RAID 3 Parallel Array with Parity Read and write operations span all drives.
Page 185
7-17 Theory of Operation RAID 5, sometimes called a Rotating Parity Array, avoids the write bottleneck caused by the single dedicated parity drive of RAID 4. Under RAID 5 parity information is distributed across all the drives. Since there is no dedicated parity drive, all drives contain data and read operations can be overlapped on every drive in the array.
Page 186
At least three drives are required for RAID 5 arrays. In addition to the standard RAID levels, SmartRAID V controllers can combine multiple hardware RAID arrays into a single array group or parity group. In a dual-level RAID configuration, the controller firmware stripes two or more hardware arrays into a single array.
Page 187
7-19 Theory of Operation RAID 5 offers improved storage efficiency over RAID 1 because only the parity information is stored, rather than a complete redundant copy of all data. The result is that three or more drives can be combined into a RAID 5 array, with the storage capacity of only one drive dedicated to store the parity information.
Page 188
SmartRAID V controllers maintain two lists for each RAID 5 array: a Bad Parity List, and a Bad Data List. These lists contain the physical block number of any parity or data block that could not be successfully written during normal write, rebuild or dynamic array expansion operations.
Page 189
A failed drive can be replaced in a RAID 1 or RAID 5 array by physically removing the drive and replacing it or by a designated Hot Spare. SmartRAID V controllers will rebuild the data for the failed drive onto the new drive or Hot Spare. This rebuild operation occurs online while normal host reads and writes are being processed by the array.
Page 190
O Messaging, which uses the full performance capability and function of the PCI bus. SmartRAID V controllers can communicate with any ASPI protocol device under Windows NT and Windows 95/98. ASPI support under MS-DOS is limited to CD-ROM drives only. MS-DOS support is provided by the I2ODDL.SYS and DPTCDROM.SYS driver files.
Page 191
Command overlapping is a technique that lets a controller receive and respond to multiple host requests before any particular request is completed. SmartRAID V controllers can receive additional commands before the previous command has finished executing. By allowing multiple outstanding commands, SmartRAID V controllers can optimize performance by overlapping commands for multiple devices, thereby keeping all devices busy as much as possible.
Page 192
Data returned by this command is stored in the controller’s Event Log. You can use Storage Manager to view the Event Log. Data to be read or written by the SmartRAID V controllers need not be aligned to word or long-word boundaries in system memory. If the data...
Page 193
264MB/sec (64-bit PCI). If a Plug-and-Play BIOS is available, automatic expansion card configuration is also available. All SmartRAID V controllers use a PCI bus for internal communication as well as their interface to the host computer. SmartRAID V Century controllers are configured by the host BIOS as multifunction PCI devices.
Page 194
These SCSI IDs can be any number from 0 – 7 or, for Wide SCSI devices, 0 – 15. The SmartRAID V controller ID is set by default to ID 7. In 8-bit SCSI systems, the device with ID 7 has the highest priority and ID 0 has the lowest priority when arbitrating for use of the SCSI bus.
Page 195
Theory of Operation A SCSI device may contain up to eight sub-devices or Logical Units, assigned Logical Unit Numbers (LUN) 0 – 7. SmartRAID V controllers support multiple LUNs. However, most devices other than bridge controllers consist of only one LUN and are accessed as LUN 0 by SmartRAID V controllers.
Page 196
It is also possible for a SCSI peripheral device to read or write less data than was requested by the host. If this occurs, SmartRAID V controllers will report the actual number of bytes transferred as less than the requested number of bytes.
Page 197
Do not attach High Voltage Differential devices to an Ultra2 bus. The SCSI-2 specification defines 8-bit, 16-bit and 32-bit bus widths. All SmartRAID V controllers use a 16-bit bus and support both 8-bit and 16-bit SCSI devices. SmartRAID V controllers are capable of handling a combination of SCSI devices with different transfer speeds, and both synchronous and asynchronous protocols on the same SCSI bus.
Page 198
7-30 Theory of Operation The original SCSI specification synchronous transfer rates of up to 5MHz. The SCSI-2 specification increased the maximum synchronous rate to 10MHz. Devices that support the faster 10MHz rate are called Fast SCSI devices. The SCSI-3 specification defines transfer rates up to 20MHz (Fast- 20/Ultra SCSI).
Page 199
7-31 Theory of Operation Beware of capacitance changes. As devices are added to a SCSI bus, capacitance is introduced to each signal from the connectors, receivers, and circuit board traces. The SCSI-3 working specification limits this capacitance to 25pF because added capacitance lowers the impedance of the cable near the device and adds delay.
Page 200
7-32 Theory of Operation When the total length of a SCSI cable must exceed the maximum length for single-ended buses, DPT recommends the use of an Ultra2 Low Voltage Differential SCSI interface. The following guidelines will help ensure reliability when configuring Ultra2 SCSI systems: •...
Page 201
7-33 Theory of Operation SCSI termination for SmartRAID V controllers is controlled through Storage Manager or SMOR. Refer to Chapter 3, “Configuration and Installation” for information about setting SCSI termination for SmartRAID V controllers. SmartRAID V controllers contain onboard active SCSI terminators for maximum reliability with Fast and Ultra SCSI devices.
Page 202
If all devices supplying termination for the SCSI cable are also capable of supplying their own termination power, then TERMPWR supplied to the SCSI cable from SmartRAID V controllers can be disabled using SMOR or Storage Manager. SmartRAID V controllers supply termination power onto the SCSI cable through a circuit breaker which protects the controller from a short-to- ground on the TERMPWR line.
Page 203
200MB/sec. DPT SmartRAID V Fibre Channel controllers can have a one or two HSSDC (copper) connectors. If you want to use a cable length greater than 30 meters, a Media Interface Adapter (MIA) can be used to convert electrical signals to optical signals for use with fiber optic cable.
Page 204
7-36 Theory of Operation SmartRAID V controllers are shipped with the DPT I O BIOS loaded on an EEPROM. This BIOS intercepts and processes Int13 requests with an embedded DOS driver. The host system Plug-and-Play BIOS can automatically disable or change the address of the I O BIOS ROM.
P P E N D I X Assembly Drawings This chapter contains outline drawings of Millennium Controllers DPT’s SmartRAID V products with jumpers PM3755F and connectors labeled for easy reference. PM3755U2B PM3754U2 See the SmartRAID V Controller LEDs section in Chapter 2 for specific information...
Page 216
A-12 Assembly Drawings BB4050 Battery Module CAUTION Danger of explosion if battery is incorrectly replaced. Replace only with the same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufacturer’s instructions.
Page 217
This chapter provides answers to many commonly asked questions. If a situation Phone: 407-830-5522 occurs that is not covered in this chapter, or (Press 6 and follow the prompts.) if the recommendations here do not correct the problem, contact DPT Technical Sup- Fax: 407-830-4793 port.
Page 218
The device might not be powered on. The device is not connected to the SCSI cable or the connection is loose. Problem: In addition to the SmartRAID V controller, the system contains another manufacturer’s SCSI controller and hangs during boot. Solution: The other controller does not correctly implement EBDA usage rules.
Page 219
BIOS. SmartRAID V Century controllers require a motherboard BIOS that supports multifunction devices, where one of the devices is a PCI-PCI bridge. All SmartRAID V controllers require a BIOS that supports large memory-mapped address ranges. Refer to the SmartRAID V READ.ME file on the DPT diskette for information about motherboard compatibility and a list of motherboards that DPT has tested with SmartRAID V products.
Page 220
Problem: The controller does not respond and various LEDs in the 1–4 range flash once per second. Solution: This pattern indicates an internal microprocessor trap occurred in the controller. Remove all attached devices, cables and option modules and retry. If the trap error disappears, reconnect the cables and devices, one device at a time, until the faulty device, cable or module is isolated.
Page 221
Solution: This typically happens when a drive that is attached to a SmartRAID V controller has been formatted with a sector size other than 512 bytes . Use Storage Manager or SMOR to reformat the drive with 512 byte sectors.
Page 222
Problem: After updating the SmartRAID V controller firmware or BIOS and rebooting, LEDs 1 and 5 or 2 and 5 flash once per second. Solution: These patterns indicate that the adapter startup code detected a firmware checksum error or a flash error. Attempt the firmware update procedure again by using the procedure in the following Problem description to recover from this condition.
Page 223
Problem: After a flash ROM upgrade of the I O BIOS only, pressing at the system prompt displays the message Card not configurable. Solution: Perform a flash ROM upgrade for SMOR to correct this condition. Problem: The floppy disk drive cannot be accessed after installing a DPT controller. Solution: Use SMOR to enable the EBDA Relocation option.
P P E N D I X Specifications Specifications: This chapter lists the electrical and environ- mental specifications for the SmartRAID V • DC Power Requirements product line. • Environmental Specifications • Memory Requirements • Battery...
Specifications Environmental Specifications NOTE Maximum ambient temperature is 40°C when using a BB4050 module. Memory SmartRAID V controllers accept up to four memory modules. The total memory installed must not exceed the maximum cache capacity of the controller. Capacities SIMMs...
Page 228
Specifications DIMMs DIMMs to be installed in SmartRAID V controllers must be DPT DM4050 or DM4060 memory modules only. Use of non-DPT DIMMs can result in data corruption. Battery The following applies to the BB4050 module only: Exceeding the temperature limits can shorten the battery life and reduce the battery capacity.
Page 229
P P E N D I X SNMP Introduction Simple Network Management Protocol (SNMP) is an industry-wide standard What’s Included protocol designed to allow you to re- motely manage your computer network. System Requirements By using the DPT SNMP subagent and an SNMP-based management console, Hardware Support you can get the DPT hardware configu-...
Simple Network Management Protocol Introduction Simple Network Management Protocol (SNMP) lets you obtain basic DPT hardware configuration and status information from an SNMP-based management console. You can also receive SNMP Traps, which are messages about changes in the hardware status. These messages alert you to important events that affect the DPT hardware and attached devices.
Simple Network Management Protocol Every system resource to be managed is represented as an object and the MIB is a collection of these objects. In a network environment each system (workstation or server) maintains a copy of the MIB containing the current status of the objects which it defines.
Page 232
Simple Network Management Protocol Refer to the MIB itself for the exact contents of each of these groups. The following lists are the groups’ contents: DPT SCSI System Modules group identifies the versions, creation date and various capabilities of the software modules. The following specific modules are included: DPT SNMP Subagent DPT SNMP Engine...
Page 233
Simple Network Management Protocol DPT SCSI Device group is a list of SCSI Devices managed by the DPT SCSI subsystem and represents the physical configuration. For each device in the system there is: Device SCSI Address information: Controller Device SCSI Inquiry data Device Capacity and Block Size Device RAID level and status (Optimal, Failed, etc.) DPT SCSI Array group contains all the RAID-specific...
• The SNMP Service for your operating system must be installed. Hardware Support The DPT SNMP agent is designed to work with all DPT SmartRAID V controllers. The specific controller information available will vary depending on whether or not that device has RAID or cache capability. Management Consoles The DPT SNMP agent conforms to the SNMP Version 1 specification.
Simple Network Management Protocol Operating System Support The following table lists the environments in which DPT hardware is manageable from an SNMP management console: Installation of DPT SNMP Software The following topics describe how to install DPT SNMP sub- agent software components and how to install SNMP support for Microsoft Windows 95/98 and Windows NT 4.0.
Page 236
Simple Network Management Protocol Installing SNMP for Microsoft Windows 95 If your operating system is Windows 95, the SNMP Service must be installed by following these steps: Insert the Windows 95 Installation CD-ROM into your CD-ROM drive. If the Autostart window appears, close the window.
Simple Network Management Protocol Operation Before you can view information about your DPT hardware, you must install the DPT Management Information Base (MIB) into the Management Console database. During the installation of the SNMP feature, the DPT MIB is installed by default as .
Page 238
Simple Network Management Protocol D-10 TC P/IP SNM P M anagem ent SNM P M aster Agent Console DPT SCS I Sub-Agent DPT Engine SN MP Trap Broadcast M odule DPT Event Logger DPT Driver D P T C ontroller DPT SNMP Sub-Agent The DPT SNMP sub-agent attaches to the operating system- specific Master Agent to handle SNMP requests for objects...
Page 239
Simple Network Management Protocol D-11 DPT SNMP Trap Broadcaster Module The SNMP Trap implementation uses the Broadcaster feature of the DPT Event Logger. The Event Logger has individual broadcast modules that have complete control over how events are received from the Event Logger. The modules define what events are to be sent and how they want to receive the event information.
Page 241
Glossary This glossary provides brief definitions of selected terms and acronyms used through- out this manual.
Page 242
Glossary Adapter Bridge Controller SCSI Host Bus Adapter or HBA A device which appears as a single device on the bus, but which bridges to multiple devices. ANSI Bridge controllers are typically used to American National Standards Institute. overcome limitations on the number of devices that can be on a single bus or to control remote Arbitrated Loop subsystems.
Page 243
See also SIMM. keyboards, and printers all require controllers. Dirty The DPT SmartRAID V is a controller for disk Refers to a cache page in which data has been drives and disk arrays. See also, HBA.
Page 244
Glossary EDO DRAM Flash ROM Extended Data Output DRAM. A type of RAM A nonvolatile memory device on the controller that improves memory read performance on that can be reprogrammed using special systems that are designed to use EDO memory. software without removing it from the board.
Page 245
The logical units are assigned from 0 to 7. Typically, SCSI devices such as a disk or tape Initiator drive contain only one subunit (LUN 0). A SCSI device, such as a SmartRAID V controller, that sends commands to SCSI Target LVD SCSI devices such as disk drives.
Page 246
Glossary MTBF Mean Time Between Failure. The average time Peripheral Component Interconnect. An between expected failures of a device in a large intelligent computer bus specification that sample group of devices. provides automatic configuration of peripheral cards. The bus supports 32-bit data paths at a Multilevel RAID 132 MB/sec data transfer rate or 64-bit data A method of combining multiple RAID 1 or...
Page 247
A SCSI device, such as a disk drive, that packaging for RAM on a small circuit board with receives and executes commands from a SCSI a defined edge connector. See also DIMM. Initiator device such as a DPT SmartRAID V controller. Single-ended An electrical signal protocol which transmits TCP/IP information through changes in voltage.
Page 248
Fast-40 SCSI. VHDCI Very High Density Cable Interconnect. The small industry standard 68-pin external connector used on DPT SmartRAID V SCSI controllers. Wide SCSI A SCSI protocol and signal definition that provides a data path more than 8-bits wide.
Page 249
6-11 audible 2-13, 6-39 features 2-10 disable 2-13, 6-39 installing 3-14 testing 6-15 status 6-12 architecture, SmartRAID V 7-22 bootable devices 4-10 array group booting controller 3-16 building with SMOR 4-21 bridge controller 7-27 building with Storage Manager 6-23...
Page 250
4-14 BSD/OS 4.1 5-1 overview 3-18 FreeBSD 5-1 requirements 3-19 Linux 5-24, 5-25 SmartRAID V 3-20 Novell NetWare 5-17 command SCO Unix 5-14 overlapping 7-23 Windows NT 5-2, 5-7 queuing 7-24 Dynamic Array Expansion. See See DAE...
Page 251
Index event notification broadcasters 6-34 configuring 6-31 hardware device module (HDM) 7-22, 7-23 NetWare 6-34 Hot Spare 2-4, 6-41 pager messages 6-33 assigning 4-23 SCO Unix 6-35 icon 6-4 SCO UnixWare 6-35 removing 4-23 SNMP D-11 Windows NT 6-36 expanding arrays 6-26 I/O statistics 6-44 extended BIOS data area definition of G-3...
Page 252
Microsoft Cluster Server NetWare 4.2 - secondary 5-21 cables 3-20 NetWare 5 - booting 5-22 enable/disable, support for 4-14 NetWare 5 - secondary 5-23 overview 3-18 SmartRAID V 3-20 OpenServer 5 5-14 system requirements 3-19 UNIX 3.2v4.2 5-14 UnixWare 7 5-15...
Page 253
Index Windows 95/98 5-7 RAID 0 7-14 Windows NT 5-2 RAID 1 7-15 RAID 2 7-15 operating system services module (OSM) RAID 3 7-16 description of 7-22 RAID 4 7-16 dynamic array expansion 6-25 RAID 5 7-17 Microsoft Windows 5-2, 5-6 RAID Accelerator features 2-9 installation 3-8...
Page 254
D-7 installing 3-11 operation D-9 restrictions 3-11 software overview D-9 single-ended SCSI 7-28 sub-agent D-10 SM4050, installing 3-11 system requirements D-6 SmartRAID V trap broadcaster D-11 architecture 7-22 status configuration 6-13 array 6-8 controller ID 3-6 device 4-16 features 2-4...
Need help?
Do you have a question about the SmartRAID V and is the answer not in the manual?
Questions and answers