HardwareRequirementsGuide 13.8

Intelerad
Hardware and Network

Requirements
Guide
Version 13.8
Published June 30 2015
Intelerad Medical Systems - Confidential
Hardware Requirements Guide
Table of Contents
How to Use this Document ____________________________ 3
Hardware Approval Process ___________________________ 5
Operating System Requirements _______________________ 6
InteleRIS Servers ___________________________________ 8
Virtual Infrastructure Requirements _____________________ 9
Networked Storage Performance Requirements __________ 11
Networking Requirements ____________________________ 12
Server Monitoring __________________________________ 15
Configuration A: Large Server ________________________ 16
Configuration AA: High Performance Server _____________ 20
Configuration AB: Blade Server _______________________ 24
Configuration AV: Medium and Large Virtual Servers ______ 26
Configuration D: Utility Server _________________________ 28
Configuration E, ExD: Small Server ____________________ 31
Configuration EV: Small Virtual Server _________________ 39
Configuration F: Medium Server _______________________ 41
Configuration R: Rendering Server _____________________ 46
Configuration S: External Storage _____________________ 48
Configuration T: Tape Library _________________________ 52
Configuration U: Uninterruptible Power Supply ___________ 54
Configuration X: Fax Modem _________________________ 55
Appendix 1: Networking Details _______________________ 56
Appendix 2: Frequently Asked Questions ________________ 60
How to Use this Document

Introduction
This guide describes the hardware, virtual hardware and network requirements of Intelerad
software. It is the core of Intelerads hardware approval process. Regulatory bodies in
several countries have certified Intelerad software. For example, IntelePACS is an FDA
Class II Medical device and must comply with some quality, reliability, and performance
standards. The goal of this process is to ensure that Intelerad software can perform reliably
and with adequate performance. Following the recommendations in combination with the
requirements presented in this document helps ensure that your server infrastructure is
adequate for the volume of data and the architecture of your system. Further, these
standard server configurations ensure that your system is easily supported by Intelerad.
Hardware Covered in this Document

The following types of hardware or virtualized hardware require formal approval by
Intelerad:
PACS servers
RIS Servers
Disk enclosures connected to servers
Networked storage
Tape libraries
Fax modems
Uninterruptible power supplies (UPS)
NOTE: Workstation configurations for diagnostic and clinical review are subject to review
without formal approval process.
We do not currently require approval of networking infrastructure or PCs for use by referring
physicians or for casual use. However, we recommend that all infrastructures complement
the server hardware and that our minimum requirements are observed.
Disclaimer
Intelerad is a software company. As such, Intelerad's approval of the hardware does not
constitute a guarantee that the hardware configuration provided by the hardware vendor is
functional. Intelerad relies on the hardware vendor to ensure compatibility of all its internal
and external components, as well as the operating system.
Hardware requirements mostly concern the components significant for performance and
reliability. Minor components like cables, connectors, power cords and rack mounting rails
may be required even though they are not explicitly listed in the minimum requirements.
The purchase of these components should follow the hardware vendors recommendations.
A medical device such as IntelePACS must be supported and maintained to be used under
applicable authority regulations. If your IntelePACS is not accessible to Intelerad's Support
Team, Intelerad will not provide maintenance (including remote monitoring, remote
diagnostics, and maintenance). IntelePACS is a medical device, and as such, must meet
medical device safety and effectiveness requirements imposed by national regulations.
The Client is advised that using IntelePACS without access from Intelerads Support Team
may put the health and safety of patients at risk, as the Client may not be advised of the
availability of software patch, bug fix, update or upgrade, nor will be informed of Field
Safety Notices, Medical Device Recalls, or Advisory Notices related to IntelePACS.
Furthermore, Intelerad will not be in a position to have access to the Clients systems to
implement corrections to prevent occurrences of patient safety issues. Any use of the
Licensed Software beyond Intelerads standard support practice is clients own
responsibility.
Approval Process
Hardware Approval Process

Our Hardware approval process consists of four simple steps:
1.
Issuance of Hardware Specifications

At the beginning of a project requiring new hardware (new installation, server
evergreening, or server addition), Intelerads Architecture and Systems Group will
recommend the hardware required to run the proposed solution. You will receive a
Hardware Requirements form that lists all servers required for your project with a
reference to the corresponding configuration from this document (for example,
Configuration A, D, F, etc).
2.
Review Of Vendors Quote (skip this step for virtual hardware configurations)
Upon reception of the Hardware Requirements form, you are required to provide
Intelerad with a copy of a quote from your hardware vendor detailing the
specifications of the hardware you plan to purchase.
3.
Approval of Vendors Quote (skip this step for virtual hardware configurations)
After verifying the quote, Intelerad will send you a Hardware Approval document,
which is an official authorization for you to go ahead and purchase the specified
hardware.
4.
Verification of Hardware and Configuration

At installation time, an Intelerad Deployment Specialist will validate the hardware
you purchased against the initial requirements and verify you installed the right
Operating System in the required configuration, including use of the prescribed
hostname. If there is a discrepancy between the approved and delivered system,
you will be required to correct the situation. Such a discrepancy may lead to delays
in the installation of Intelerad software.
OS
Operating System Requirements

Supported Red Hat Versions
The following operating system is supported for new IntelePACS and InteleOne servers:
For installations older than IntelePACS 4.10.1R2:

o
Red Hat Enterprise Linux 6, latest Update, for 64-bit x86.
For installations of IntelePACS 4.10.1R2 or higher:

o
Red Hat Enterprise Linux 7, latest Update, for 64-bit x86.
IntelePACS servers running a PACS version older than 4-3-1 may require an older version
of Red Hat.
Notes on Red Hat Installation
Operating System installation is the responsibility of the client.
Recommended Red Hat subscription is Standard Subscription. Self-Support

Subscription is acceptable for those customers comfortable with the RedHat
terms.
The prescribed hostname must be used.
Hyper-threading must be disabled on the server.
All servers must be registered with the Red Hat Network and subscribed to the
following channel, according to the version of Red Hat:
o
RHEL6: rhel-6-server-optional-rpms
RHEL7: rhel-7-server-optional-rpms
Internal, external, or virtual CD/DVD drive will be required to install the OS
All servers must be configured to use the ext4 file system.
All partitions for PACS must be mounted by referencing their filesystem UUID.
Logical Volume Manager (LVM) is not supported.
Swap space must be 12 GB and must be located on the OS RAID.
Maximum supported LUN size is 3TB.
Please use a standard install. Intelerad will install any missing packages.
Please use media (CD or DVD) with the latest updates of the Red Hat versions
listed above. Older versions may lack drivers.
If you are installing on Dell hardware, do not use the OpenManage installation
disks. Install from the latest Red Hat media only. Do not reuse any pre-existing
partitions.
6
OS
Please skip the X Windows configuration and run the system in run-level 3. This
will ensure X Windows is not started automatically.
Please ensure to enable write-back caching on RAID controllers equipped with a

battery-backed cache.
All firmware pertaining to RAID controllers and arrays, remote access consoles
and tape libraries should be verified and, if necessary, upgraded to the current
revision from the hardware manufacturer.
Supported Windows Versions

The following operating system is supported for new InteleRIS servers:
Microsoft Windows Server 2008 R2 Standard Edition 64-bit
Notes on Windows Installation
Operating System installation is the responsibility of the client.
The prescribed hostname must be used.
Hyper-threading must be disabled at the BIOS level.
Installation of Microsoft .NET Framework 4.0 and Microsoft .NET Framework 3.5
SP1 by the client is required on all Windows servers. They are distributed free of
charge by Microsoft at
http://www.microsoft.com/download/en/details.aspx?id=17851 and
http://www.microsoft.com/en-us/download/details.aspx?id=22.
Purchase and installation of Microsoft Office (or Word) 2007 or 2010 by the client
is required only for InteleRIS v7 Fax Servers. Microsoft Office/Word is not required
for InteleRIS v8 servers. Office 2013, 365 are not supported.
The required version of Microsoft SQL Server is SQL Server 2008 R2 with at least
Service Pack 3.
Microsoft SQL Server 2008 R2 licenses are purchased from Intelerad for the
InteleRIS servers that require it. Intelerad installs and configures Microsoft SQL
Server 2008 R2 as part of the installation of InteleRIS.
Internal, external, or virtual CD/DVD drive will be required to install the OS.
All servers must be configured to use the NTFS file system.
All partitions must be created with a partition offset of 1024K.
Disable Windows System Restore.
InteleRIS Servers
InteleRIS Servers
Server hardware and partitioning
InteleRIS makes use of a software architecture different from IntelePACS and so the
different configurations for InteleRIS servers are specified as variations from the base
PACS server configurations and partitioning schemes.
The naming scheme for the InteleRIS servers is comprised of three parts:
The letter representing the base hardware configuration (eg: A, E, F, etc)
A number representative of the annual order volume capacity of the system (RIS1
to RIS6)
A letter, A or B, specifying the server type
Typically the InteleRIS architectures will be specified as dual pairs of server types of the
same capacity.
For example to get the specifications for a medium-sized InteleRIS server combination
such as E(RIS3A) and E(RIS3B), go to the hardware requirements for Configuration E
further in the guide and note the changes in hardware from the base Configuration E server
configuration (found in the InteleRIS Server section for each server type). The RAID and
disk partitioning scheme to be used for these servers will also be found in the Configuration
E section.
InteleRIS database server location

The database replication and licensing in use in InteleRIS Database servers requires
specific networking requirements between the servers for proper operation. Unless
otherwise explicitly authorized in Intelerads recommendations, the database servers must
be operated at the same location.
InteleRIS Server Redundancy and Mirroring

Requirements
InteleRIS data replication between servers require that the InteleRIS servers be part of a
Windows domain. In particular, SQL Server Mirroring requires that the database servers be
part of the domain to make use of SQL Sync, and File Share Mirroring requires the
Windows Domain DFS (Distributed File Share) feature.
Installation and on-going support and management of a Windows domain is the customers
responsibility.
Note that SQL Server servers cannot be Domain Controllers.
Virtualization
Virtual Infrastructure Requirements

Supported Infrastructures
The following infrastructures are supported for IntelePACS and InteleOne servers:
VMware vSphere 4.x Essentials Plus or higher
VMware vSphere 5.x Essentials Plus or higher
Notes on vSphere
In order to facilitate troubleshooting performance-related issues of a virtual

machine, it may be necessary to temporarily isolate the problematic guest using
vMotion. This requires that your virtual infrastructure provides sufficient compute
resources to isolate the largest of your virtual Intelerad servers to a host not
running any other virtual machines for the duration of the troubleshooting. Since a
typical virtual infrastructure will have enough hosts to accommodate failure of one
or more physical machines, no special consideration to extra hardware is normally
required.
The resources allocated to a virtual machine may need to be changed over time to
ensure appropriate performance and compliance with newer versions of this
document. This allows Intelerad to recommend virtual hardware with less spare
capacity than would be necessary in physical configurations that are expected to
last until they are evergreened.
Intelerad servers that provide redundant services should not be running on the
same host, and preferably not on the same shared storage.
All hardware must be on VMwares hardware compatibility list.
Configuration X Fax Modems are not supported by VMware. Servers that use them
cannot be virtualized.
All servers hosting virtual Intelerad servers must use Intel Xeon processors.
NTP will be used on the guest OS, and as such, time synchronization with the host
should be disabled.
CPU resources must be fully reserved (i.e. vCPUs x min. clock speed).
Total number of vCPUs assigned to all VMs on a host should be less than (or
equal to) the total number of physical cores on that host.
Memory resources must be fully reserved.
VMware tools must be installed on the guest OS.
Console access to Intelerad servers must be provided to Intelerad. A new user

account may be required for this purpose.
VMwares Fault Tolerance feature is not supported (not compatible with vSMP).
If supported by your vSphere license, enable Hot Add (memory and CPU).
Use Paravirtualized SCSI adapters (PVSCSI): one for OS; one for database; and
one for image storage (where applicable).
9
Virtualization
For Linux virtual machines: Allow ESXi to handle I/O scheduling by changing the
VM's I/O scheduler from CFQ to NOOP (VMware KB2011861).
Storage disk type:

o
VSphere version less than 5.5: Only physical-compatibility mode raw

device mappings on shared storage may be used for Configuration SM2,
SM3, SC2, or SC3 storage (iSCSI SAN or FC SAN only).
VSphere version 5.5 or newer: Virtual disks, in addition to physicalcompatibility mode raw device mappings on shared storage, may be used
for Configuration SM2, SM3, SC2, or SC3 storage.
Virtual disks must be on shared storage (iSCSI SAN, FibreChannel (FC) SAN or
NFS).
Virtual disks must be thick-provisioned.
Virtual disks must be implemented with the same class of hardware

(enterprise/midline/desktop) as the corresponding physical configurations.
10
Networked Storage
Networked Storage Performance

Requirements
I/O performance is critical to overall performance of Intelerad servers and can be difficult to
isolate for troubleshooting once in production. The performance of shared networked
storage can vary widely depending on usage patterns and vendor specific configuration
parameters. Instead of certifying all products and configurations, Intelerad requires minimal
scores on simple standardized benchmarks.
The fio file system performance test tool is used to measure the number of random write
operations per second that a server can do.
To measure burst writes on the DB partition, run:
fio --name=burst --rw=randwrite --size=4m --bs=4k --ioengine=sync \
--invalidate=1 --iodepth=1 --direct=1 --directory=/opt/imsdb
To measure sustained writes on the DB partition, run:

fio --name=sustained --rw=randwrite --size=4g --bs=4k --ioengine=sync \
--invalidate=1 --iodepth=1 --direct=1 --directory=/opt/imsdb
To measure the performance on the image partition, use the directory option to specify a
path to the image partition (e.g. -directory=/usr/local/PACS/images). In the
resulting output, the score to consider is the one listed after iops=.
The following table shows burst and sustained writes requirements for the various
configurations that use networked storage:
AV3
Recommended
burst write
score
15,000
Minimal
burst write
score
10,000
Recommended
sustained write
score
5,000
Minimal
sustained write
score
3,000
AV2
7,000
5,000
3,000
2,000
EV, AV1
SM2, SM3
SC2, SC3
4,000
3,000
2,000
3,000
2,000
1,500
1,500
1,500
1,500
1,000
1,000
1,000
Configuration
11
Network
Networking Requirements
Each Intelerad server must comply with the following networking requirements in order to
function properly and guarantee service and support from Intelerad Support Center.
Internally, all Intelerad servers need to have unrestricted access to all other Intelerad
servers. All TCP and UDP ports as well as all ICMP packets require unrestricted access
between servers. Each server must be identified by a single hostname and IP address pair
across the system. Network address translation between servers is not supported.
The High Availability Cluster and Load Balanced Cluster features for IntelePACS rely on IP
address migration between servers; it is required that the servers be on the same local area
network and that multicasting be enabled on that network.
InteleRIS client connections to InteleRIS servers should take place only over an encrypted
VPN connection to help ensure the safety of the data.
PACS Outgoing
Normally, opening up outgoing ports is not a problem for our clients because humans do
not operate IntelePACS servers. Consequently, restricting outgoing web access (to ports
80 and 443, for example) is not an issue. IntelePACS servers must therefore be able to
initiate outbound network traffic to the following addresses and ports:
Port and
Protocol
443/TCP
From
PACS
Server
All
To
Remote
Address
All
Service
Comments
Notifier,
IPMON, IV
site license
retrieval,
RPM
downloads,
Red Hat
Network ,
M*Modal VR
This port is absolutely essential for

remote monitoring via our Notifier
and IPMON software. It is also used
to connect to the Red Hat Network.
If necessary, the remote address
range can be restricted to Intelerad's
subnetworks (67.69.227.96/27 and
67.69.227.160/27) and to your
upstream Ret Hat Network servers
(rhn.redhat.com,
xmlrpc.rhn.redhat.com and
satellite.rhn.redhat.com).
When integrating with M*Modal VR,
this port is also used to connect to
the M*Modal data centers.
80/TCP
All
All
RPM
downloads,
Red Hat
Network
We require this port both to

download RPMs from Intelerad and
to connect to the Red Hat Network.
The address range requirements are
the same as for port 443 above.
25/TCP
All
All
email
notifications
PACS servers need to be able to

deliver email notifications to local
administrators. The target server
range can be restricted accordingly.
12
Network
Port and
Protocol
22/TCP
53/UDP,TCP
123/UDP,TCP
From
PACS
Server
All
To
Remote
Address
All
Service
Comments
ssh
If necessary, the remote address

range can be restricted to the
Intelerad IP range. We need to use
ssh during maintenance and
troubleshooting to connect back to
Intelerad.
Distribution
server
Distribution
server
All
DNS
This is required for DNS, otherwise

name lookups do not work.
All
ntp
You can close this port if you have

another NTP server on the inside
network against which we can
synchronize the time.
PACS Incoming
IntelePACS servers must be able to accept direct inbound network traffic from the following
addresses and ports:
Port and
Protocol
22/TCP
443/TCP,UDP
From Remote
Address
Intelerad's
subnetworks
(67.69.227.96/27
and
67.69.227.160/27)
All
To PACS
Server
Distribution
server
Service
Comments
ssh
Required to connect
to the servers for
maintenance.
Web server
All IntelePACS
user applications
InteleViewer
If you do not have

any users (such as
referring physicians)
outside your network,
you can restrict the
remote address
range to the
Intelerad IP range.
Allow HTTP
tunneling on port
443
5022/TCP
HTTP tunneling
is required for
access to Instant
Messaging
Feature and
InteleViewer
Image Streaming
All
Only required if
HTTP tunneling
over port 443 is
not possible
Web server
InteleViewer
Image Streaming
The same comment

as for port 443
applies.
RIS Incoming
InteleRIS servers must be able to accept direct inbound network traffic from the following
addresses and ports:
13
Network
Port and
Protocol
1433/TCP
From Remote Address
3389/TCP
Intelerad's subnetworks
(67.69.227.96/27 and
67.69.227.160/27)
All InteleRIS clients
To RIS
server
All
Service
Comments
Microsoft
SQL Server
Required to access
the InteleRIS
database.
All
Remote
Desktop
Protocol
Required to connect
to the servers for
maintenance.
VPN Connection (or port-forwarding)

Intelerad can support VPN connections to your firewall. In the case a VPN is problematic,
access via port-forwarding will be setup instead. No matter the connection method,
Intelerad requires at least two (2) reachable SSH-enabled hosts in the customer local
network: one primary and one backup.
If you wish to setup access, please contact your or implementation Project Manager or
Account Manager.
14
Monitoring
Server Monitoring
Intelerad remotely monitors servers 24/7 and is automatically notified of a wide range of
conditions. Most of this monitoring is application specific and must be interpreted by
Intelerad Support Center personnel.
Intelerad does not directly monitor servers at the hardware level. For those Intelerad
customers who wish to monitor their server hardware, Intelerad supports server
management solutions from both Dell and HP. These monitoring systems are based on
SNMP and require Intelerads Deployment Team to install and configure software on the
monitored servers. They also require that clients deploy a management console on which
to install the appropriate management and monitoring software. The management console
should be deployed separately from the Intelerad servers it is monitoring.
For information regarding the solution to use, refer to the following:
Dell: OpenManage Essentials
http://en.community.dell.com/techcenter/systems-management/w/wiki/openmanageessentials.aspx
HP: HP Systems Insight Manager (SIM)
http://h18013.www1.hp.com/products/servers/management/hpsim/index.html
OR
HP OneView
http://www8.hp.com/ca/en/products/server-software/product-detail.html?oid=5410258
Once the hardware vendors monitoring hardware and software is in place, simply
download and complete the request form available from the Intelerad Education and
Support Center (https://support.intelerad.com/modules/wfsection/article.php?articleid=452)
and Intelerads Deployment Team will configure the servers to provide monitored
information, such as RAID status, CPU status, fan speed, memory, server temperature,
power supply status etc., to the management console.
15
Configuration A: Large Server

Common uses
Modality Server
A Large Modality Server requires external image storage. See Configuration SM.
Image Depot Server
An Image Depot Server is used to warehouse large amounts of images for reference as
priors. The server requires external image storage - see Configuration SC.
PACS Database Server
Separate database servers are recommended for very large IntelePACS systems.
Typically, such systems process volumes less than 500K studies per year.
Analytics Server
This configuration is typically used when a PACS Analytics server is required.
RIS Database Server
Separate database servers are recommended for large InteleRIS systems. Typically, such
systems process volumes less than 150K orders per year.
RIS Fax Butler and File Server
Separate file servers are recommended for large InteleRIS systems. Typically, such
systems process volumes up to 300K orders per year.
Minimum Requirements
The approved minimum hardware configurations and vendors are:
Component
Model
Form Factor
CPU
Memory
Network
Remote Console
RAID controller
Hewlett-Packard
Rack: ProLiant DL360 Gen9
OR
Tower: ProLiant ML150 Gen9
Rack 1U or Tower
2 x Intel Xeon E5-2640v3
(2.60GHz/8-core/90W)
4 x HP 8GB 2Rx8 PC3-12800E11 Kit Memory (32GB total)
HP Ethernet 1GbE 4-port
331FLR Adapter
HP iLO Advanced 1 Server
License with 1yr 24x7 Technical
Support and Updates
HP Smart Array P440ar/2G
Controller + Battery
Dell
Rack: PowerEdge R430
OR
Tower: PowerEdge T430
Rack 1U or Tower
4 x 8GB RDIMM, 2133MHz, Dual
Rank x8 (32 GB total)
On-board Broadcom 5720 QP
1Gb LOM
iDRAC8 Enterprise
PERC H730P RAID Controller,

2GB NV Cache
16
Component
Hard Disks
Hewlett-Packard
8 x HP 300GB 6G SAS 10K
RPM SFF (2.5-inch) SC
Enterprise Hard Drive
2 x HP 500W Flex Slot Platinum
Hot Plug Power Supply
See Configuration "U"
Other
Components
UPS
Image Storage
Space Available
HP Smart Buy
Suggestion
Dell
8 x 300GB 10K RPM SAS 6Gbps
2.5in Hot-plug Hard Drive
Dual, Hot-plug, Redundant Power
Supply (1+1), 550W
This server configuration does not provide image storage.

Applies to HP server only
Rack - SKU: 780019-S01
Note: The Smart Buy option for the HP server build is included as a suggestion only and
may not be available at all times and geographies. It is a pre-configured server, without an
OEM Operating System. Additional components may be required to achieve the minimum
server requirements.
Permissible Upgrades
Different server chassis from same generation hardware with the same
components
Upgrade CPUs to Xeon E5-2600v3 processors with more cores, faster core speed,
more cache
More memory configured to run at optimal speed (DIMMs per channel, ranks per
DIMM, etc)
15K RPM drives instead of 10K RPM drives
Larger capacity hard disks
Change to configuration AB or AA
InteleRIS Server (Changes from Configuration A)

RIS5B: RIS Fax Butler/File Share Server
Component
Hewlett-Packard
Dell
RAM
4 x 4GB RDIMM, 2133MHz (16GB total)
Hard Disks
2 x HP 300GB 6G SAS 10K RPM SFF

(2.5-inch) SC Enterprise Hard Drive
4 x 4GB RDIMM, 2133MHz, Low Volt

(16GB total)
17
Expandability
When used as a Large Modality Server or Image Depot Server, the maximum amount of
image storage space that the server can sustain will depend on the particular load
experienced by the server. If the observed load permits it, the image storage on this server
can be expanded through the addition of additional storage configuration of type SM or SC.
Please note that mixing of storage configurations SM and SC on the same server is not
permitted. Lastly, the ultimate size of image storage will be limited by the available space
on the database RAID. For predominantly small image sizes (e.g. CT), this limit can be as
low as 100 times the size of the database RAID.
Disk Configuration for PACS Server (except

Analytics)
OS: 4 x 300GB in RAID 1+0
Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
first partition
Database: 4 x 300GB in RAID 1+0

Mount Point
/opt/imsdb
Size
All available space
Comments
Image Data: Nil, Please refer to Configuration SM or SC.
Disk Configuration for PACS Analytics Server

OS: 2 x 300GB in RAID 1
Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
first partition
About 260 GB

Mount Point
/opt/imsdb
Size
All available space
Comments
About 810 GB
Image Data: Nil.

18
RIS4A: Disk Configuration for RIS Database

Server
Array 1: 2 x 300GB in RAID 1
Drive Letter
C:
G:
H:
L:
Size
80GB
50GB
100GB
50GB
Purpose
OS System Files
OS Temp Files
SQL Files
SQL Master DB
NTFS Cluster Size

4k
4k
4k
64k
64k
64k
64k
64k
Stripe Size
NTFS Cluster Size

64k
64k
NTFS Cluster Size

64k
64k
64k
64k
NTFS Cluster Size

64k
64k
64k
64k

Drive Letter
D:
Size
280GB
Purpose
SQL Data
Stripe Size

Drive Letter
E:
M:
Size
90GB
190GB
Purpose
SQL Transaction Logs
SQL Index
Stripe Size

Drive Letter
F:
N:
Size
90GB
190GB
Purpose
SQL Temp DB
SQL Tran Log Backups
Stripe Size
RIS5B: Disk Configuration for RIS Fax Butler/File

Server:
Drive Letter
Size
C:
L:
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster
Size
4k
4k
Stripe Size
64k
64k
Array 2: 5 x 900GB in RAID 5 and 1 x 900GB hot spare

Drive Letter
Size
D:
3.35TB
Purpose
File share
NTFS Cluster
Size
64k
Stripe Size
128k
19
AA
Configuration AA:
High Performance Server
Common uses
High Performance PACS Database Server
High performance database servers are recommended for the largest IntelePACS systems.
Typically, such PACS systems process volumes of more than 500K studies per year.
High Performance PACS Modality Server
A High Performance Large Modality Server would be used where a very high volume of studies
is to be received into the PACS. The server requires external image storage - see
Configuration SM.
High Capacity PACS Image Depot Server
A High Capacity Image Depot Server is used to warehouse large amounts of image data. The
server requires external image storage - see Configuration SC.
High Performance PACS Gateway Server
A High Performance Gateway Server provides high speed routing of images with minimal
image data retention.
PACS Monitoring Server
A PACS Monitoring Server is used to help alleviate stress on user-facing critical servers by
hosting non-imaging and non-workflow-related services. Used on PACS systems processing
volumes of more than 500K studies per year.
High Performance RIS Database Server
High performance database servers are recommended for large InteleRIS systems. Typically,
such RIS systems process volumes of up to 300K orders per year.
For these types of server, the approved minimum hardware configurations and vendors are:
Component
Model
Hewlett-Packard
OR
Form Factor
CPU
Rack 2U or Tower
(3.20GHz/8-core/135W)
8 x 4GB RDIMM, 2133 MHz
(32GB total)
Memory
Dell
PowerEdge R730xd Chassis with
up to 12 + 12, 2.5" Hard Drives
and 2 Controllers
OR
Tower: PowerEdge T630 Chassis
with up to 16 + 16, 2.5" Hard
Drives and 2 Controllers
Rack 2U or Tower
(3.20GHz/8-core/135W)
8 x 4GB RDIMM, 2133 MHz (32GB
total)
20
AA
Component
Network
Hewlett-Packard
HP Ethernet 1GbE 4-port 331i
Adapter
Remote Console

Support and Updates
RAID controllers
HP Smart Array P440ar/2GB

FBWC 12Gb 2-ports Int FIO SAS
Controller
HP Smart Array P440/4GB
FBWC 12Gb 1-port Int SAS
Controller
Dual PERC H730P Integrated

RAID Controllers, 2GB NV Cache
Hard Disks
HP DL380 Gen9 Additional 8SFF

Bay2 Cage/Backplane Kit

Other
Components
UPS

Hot Plug Power Supplies

Supply (1+1), 750W
Image Storage
Space Available
HP Smart Buy
Suggestion
Dell
Broadcom 5720 QP 1Gb Network
Daughter Card
iDRAC8 Enterprise
PACS Gateway Server: Approximately 1.1TB

Other server type: No image storage
Rack - SKU: 800076-S01
Different server chassis from same generation hardware with the same components
Upgrade CPUs to other fast model in the E5-2600v3 family
DIMM, etc)
Larger capacity hard disks, spinning at 15K RPM
InteleRIS Server (Changes from Configuration AA)

RIS5A: RIS Database Server
Component
Hewlett-Packard
Dell
Hard Disks


21
AA
Expandability
When used as a Large Modality Server or Image Depot Server, the maximum amount of image
storage space that the server can sustain will depend on the particular load experienced by the
server. If the observed load permits it, the image storage on this server can be expanded
through the addition of additional storage configuration of type SM or SC. Please note that
mixing of storage configurations SM and SC on the same server are not permitted. Lastly, the
ultimate size of image storage will be limited by the available space on the database RAID. For
predominantly small image sizes (e.g. CT), this limit can be as low as 100 times the size of the
database RAID.
Disk Configuration for PACS AA server

(For all PACS AA configurations except Gateway)
Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
first partition

Mount Point
/opt/imsdb
Size
All available space
Comments
Image Data: Nil, Please refer to Configuration SM or SC.
Disk Configuration for PACS gateway server

Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
first partition

Mount Point
/opt/imsdb
Size
All available space
Comments
22
AA
Image Data: 8 x 300GB in RAID 1+0

Mount Point
/usr/local/PACS
Size
All available space
Comments
Approximately 1.1TB

Server
Drive Letter
C:
L:
Size
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster Size

4k
4k
64k
64k
Stripe Size
NTFS Cluster Size

64k
64k
64k
64k
NTFS Cluster Size

64k
64k
NTFS Cluster Size

64k
64k
NTFS Cluster Size

64k
64k
NTFS Cluster Size

64k
64k
64k
64k

Drive Letter
D:
M:
Size
190GB
90GB
Purpose
SQL Files
SQL Master DB
Stripe Size
Array 3: 4 x 300GB in RAID 1+0

Drive Letter
E:
Size
560GB
Purpose
SQL Data
Stripe Size

Drive Letter
F:
Size
280GB
Purpose
Stripe Size

Drive Letter
G:
Size
280GB
Purpose
SQL Index
Stripe Size

Drive Letter
H:
N:
Size
90GB
190GB
Purpose
SQL Temp DB
Stripe Size
Global Hot Spare(s):

2 x 300GB Hard Drives
23
AB
Configuration AB: Blade Server

Caveat
These blade systems rely on SAN storage for the databases residing on each server.
Database, and consequently server performance are dependent on the available
input/output from the SAN. As SAN resources may be shared among other servers,
performance variances outside of the control of Intelerad may arise.
Common uses
Database Server
Large Modality Server
A Large Modality Server requires external image storage. See Configuration "SM2" or
"SM3".
Image Depot Server
priors. An Image Depot Server is certified to warehouse at least 25TB of image data. The
server requires external image storage. See Configuration "SC2" or "SC3".
For these types of servers, the approved minimum hardware configurations and vendors
are:
Component
Model
Hewlett-Packard
ProLiant BL460c Gen9 Server
Blade
Form Factor
CPU
Half-height blade
(32GB total)
HP FlexFabric 10Gb 2P 554FLB
Adapter
Memory
Network
Remote Console
RAID controller
HP iLO Advanced for

BladeSystem
1 x HP Smart Array P244br
Controller with 1GB FBWC
Dell
PowerEdge M630 2.5"
Backplane with up to 2 Hard
Drives and PERC RAID
Controllers
Half-height blade
(32GB total)
Broadcom 57810-k Dual port
10Gb KR Blade Network
Daughter Card
iDRAC8 Enterprise
1 x PERC H730 Controller
24
AB
Component
Hard Disks
UPS
Image Storage
Space Available
Hewlett-Packard
Dell
Guaranteed power to be provided
more cache
DIMM, etc)
15K RPM drives instead of 10K RPM
Equivalent full height blade
Upgrade to configuration A or AA
Disk Configuration
OS: 2 x 600GB in RAID 1
Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
first partition
Database: 600GB on SAN

Mount Point
/opt/imsdb
Size
All available space
Comments
Image Data: Nil, Please refer to Configuration SM2, SM3,

SC2, or SC3.
25
AV
Configuration AV:
Medium and Large Virtual Servers
Common uses
Database Server
Large Modality Server
A Large Modality Server requires external image storage. See Configuration "SM2" or
"SM3".
Image Depot Server
priors. An Image Depot Server is certified to warehouse at least 25TB of image data. The
server requires external image storage. See Configuration "SC2" or "SC3".
Analytics Server
Configuration AV1, AV2, AV3

All Configuration AV servers need to comply with the section Virtual Infrastructure
Requirements and the section Networked Storage Performance Requirements. In the latter,
I/O performance requirements for Configuration AV are separated into AV1, AV2, AV3.
These performance requirements are the only difference between the three configurations.
Intelerad may explicitly require Configuration AV2 or AV3 for servers requiring the extra
performance. A server specified only as Configuration AV can be assumed to be AV1.
In addition to the resource requirements specified below, this virtual server and its vSphere
environment must comply with section Virtual Infrastructure Requirements.
Component
Model
CPU
Memory
Network
Remote Console
VMware vSphere Enterprise

Virtual Machine Version 7
4 x virtual CPUs (2.66 GHz each)
24 GB
1 x 1GB network uplinks (VMXNET3 adapter)
Console access via vSphere client or URL
26
AV
Component
Storage

1 x 300GB thick-provisioned virtual disk
Image Storage
Space Available
Faster CPU clock
More memory
Upgrade to configuration A, AA, or AB
Different-sized thick-provisioned virtual disks specified by Intelerad
Disk Configuration
OS: 300GB on SAN
Mount Point
/boot
Swap
/
Size
500 MB
12 GB
All remaining space
Comments
first partition

Mount Point
/opt/imsdb
Size
All available space
Comments
Image Data: Nil, Please refer to Configuration SM2, SM3,

SC2 or SC3.
27
Configuration D: Utility Server

Common uses
DICOM router
A DICOM router can be used in small clinics, typically with volumes less than 30K studies per
year, no significant large multi-image (such as CT, PET, tomosynthesis, etc) data volume.
Fax Server
A Configuration D server can act as a PACS fax server with the addition of a Configuration X
fax modem board.
RIS Fax Butler
Separate fax servers may be recommended for smaller InteleRIS systems. Typically, such
systems process volumes less than 35K orders per year.
For these types of servers, the approved minimum hardware configurations and vendors are:
Component
Model
Form Factor
CPU
Hewlett-Packard
OR
Tower or Tower
(2.4GHz/6-core/15MB/85W)
Memory
2 x 4GB RDIMM (8GB Total)
Network
On-Board Dual Gigabit Network

Adapter
Remote Console
HP iLO Advanced including 1yr

24x7 Technical Support and
Updates Single Server License
HP Smart Array P440/4GB FBWC
12Gb 1-port Int Controller
2 x HP 300GB 6G Hot Plug 2.5
SAS Dual Port 10K RPM
RAID controller
Hard Disks
Other
Components
UPS
1 x HP 550W Power Supply Kit

Dell
OR
Rack 1U or Tower
2.40GHz, 20M Cache, 8.0GT/s
QPI, 8C, 85W, Max Mem
1866MHz
2 x 4GB 1R or 2R RDIMM (8GB
Total)
On-Board Dual Gigabit Network
Adapter
iDRAC8 Enterprise
PERC H730 RAID Controller,

1GB NV Cache
1 x Cabled Power Supply,

550W
28
Component
Hewlett-Packard
Image Storage
Space Available
HP Smart Buy
Suggestion
Dell
Approximately 200GB

Tower - SKU: 793008-S01 (using 15K LFF hard disks)
Xeon CPU with the following characteristics: faster core frequency, more cache,
more cores
More memory
450GB hard drives instead of 300GB
Replace the system with Configuration E (Small Modality Server)
Replace power supplies with higher-wattage model(s)
InteleRIS Server (Changes from Configuration D)

No special InteleRIS hardware configurations apply to Configuration D servers.
Disk Configuration for PACS server

All Data: 2 x 300GB in RAID 1
Mount Point
/boot
swap
/
/opt/imsdb
/usr/local/PACS
Size
500 MB
8 GB
50 GB
70 GB
All remaining space
Comments
First partition
Approximately 160GB
29
RIS1B and RIS2B: Disk Configuration for RIS Fax

Butler
Drive Letter
Size
C:
L:
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster
Size
4k
4k
Stripe Size
64k
64k
30
Configuration E, ExD: Small Server

Common uses
Small PACS Modality Server
A small modality server can typically handle volumes of less than 80K studies per year and less
than 6K large multi-image studies (such as CT, PET, tomosynthesis, etc) per year.
RIS Database Server
A dedicated database server for an InteleRIS system typically handling volumes less than 75K
orders per year.
RIS Fax Butler/File Server
A dedicated file and fax server for an InteleRIS system typically handling volumes less than 150K
orders per year.
Alternate configuration
Configuration ExD Server - Small PACS Modality Server with expanded storage
Provides similar image ingest capacity to the Small Modality Server, with expanded image storage
capacity.
Component
Model
Hewlett-Packard
Rack : ProLiant DL360 Gen9
OR
Rack 1U or Tower
2 x 8GB RDIMM, 2133MHz (16GB
total)
Dell
OR
Rack 1U or Tower
2 x 8GB RDIMM, 2133MHz
(16GB total)
Network
HP Ethernet 1Gb 4-port 331FLR

Adapter
Remote Console
HP iLO Advanced 1 Server License

with 1yr 24x7 Technical Support
and Updates
Smart Array P440ar/2G Controller
On-Board Broadcom 5720 Quad

Port 1Gb LOM or Broadcom
5720 DP 1Gb Network Interface
Card
iDRAC8 Enterprise
Form Factor
CPU
Memory
RAID controller
PERC H730 RAID Controller,

1GB NV Cache
31
Component
Hard Disks
Other
Components
UPS
Hewlett-Packard
6 x HP 300GB 6G SAS 10K RPM
SFF (2.5-inch) SC Enterprise
2 x HP 500W Common Slot Gold
Image Storage
Space Available
HP Smart Buy
Suggestion
Dell
Supply (1+1), 550W
Using 300GB hard drives: 700GB

Using 600GB hard drives: 1.3TB
Rack - SKU: 780019-S01
Note: The Smart Buy option for the HP server build is included as a suggestion only and may not
be available at all times and geographies. It is a pre-configured server, without an OEM
Operating System. Additional components may be required to achieve the minimum server
requirements.
Upgrade CPU to another in Intel Xeon E5-2600v3 family meeting or exceeding specs
above with respect to number of cores, cache, or core frequencies
More memory configured to run at optimal speed (optimal DIMMs per channel, ranks per
DIMM, etc); faster RAM
RAID controller model with larger capacity for the FBWC
Replace hard drives with 600GB or 900GB 10K RPM SAS hard drives
Replace the system with Configuration EV or upgrade to a Configuration F (Medium

Modality Server)
Replace power supplies with higher-wattage models.
Replace with Configuration ExD (see complete details below). Provides similar image
ingest volume capacity to the Configuration E server, with expanded image storage
capacity:
32
Configuration ExD Server

Component
Model
Hewlett-Packard
Rack: ProLiant DL380 Gen9 24 SFF + 2 SFF Front/Rear
Kit
OR
Form Factor
CPU
Rack 2U or Tower
Memory
4 x HP 8GB RDIMM,
2133MHz (32GB total)
331FLR Adapter
Network
Remote Console
RAID controller

License with 1yr 24x7
Technical Support and
Updates
Hard Disks
HP DL380 Gen9 2SFF

Front/Rear SAS/SATA Kit
Other Components
2 x HP 800W Flex Slot

Platinum Hot Plug Power
Supply
See Configuration U
UPS
Image Storage
Space Available
HP Smart Buy
Suggestion
Dell
Rack: PowerEdge R730xd
Chassis with up to 24 x 2.5"
Drives + 2 x 2.5" Flex Bay
Drives
OR
Chassis with up to 32, 2.5"
Hard Drives
Rack 2U or Tower
4 x 8GB RDIMM, 2133MHz,
Dual Rank x8 (32 GB total)
Broadcom 5720 QP 1Gb
Network Daughter Card
iDRAC8 Enterprise
PERC H730P RAID

Controller, 2GB NV Cache
8 x 300GB 10K RPM SAS
6Gbps 2.5in Hot-plug Hard
Drive
18 x 600GB 10K RPM SAS
6Gbps 2.5in Hot-plug Hard
Drive
2 x Hot-plug, Redundant
Power Supply (1+1), 750W
See Configuration U

Rack - SKU: 777339-S01
Note: The Smart Buy option for the HP server build is included as a suggestion only
and may not be available at all times and geographies. It is a pre-configured server,
without an OEM Operating System. Additional components may be required to
achieve the minimum server requirements.
Permissible Upgrades for Configuration ExD

(In addition to the Configuration E Permissible Upgrades above)
33
900GB 10K RPM SAS hard drives for the image data partitions. With these, the image
data partitions will have approximately 12.6TB image storage space
InteleRIS Server (Changes from Configuration E)

RIS1A: RIS Database/File Share Server
No changes apply from configuration E server.
RIS2A: RIS Database/File Share Server

Component
Hewlett-Packard
Dell
Hard Disks



Component
Hewlett-Packard
Dell
Memory
4 x HP 8GB 2Rx8 PC3-12800E-11 Kit

Memory (32GB total)


Component
Hewlett-Packard
Dell
Hard Disks



Component
Hewlett-Packard
Dell
Hard Disks


34
Disk Configuration for Configuration E PACS Server

Using 300GB Hard Drives:
All Data: 6 x 300GB in RAID 1+0
Mount Point
/boot
Swap
/
/opt/imsdb
/usr/local/PACS
Size
500 MB
12 GB
50 GB
60 GB
All remaining space
Comments
First partition
Approximately 700GB
Configuration E PACS server disk configuration when using

Hard Drives larger than 300GB:
All Data: 6 x Hard Drive in RAID 1+0
Mount Point
/boot
Swap
/
/opt/imsdb
/usr/local/PACS
Size
500 MB
12 GB
150 GB
200 GB
All remaining space
Comments
First partition
Disk Configuration for Configuration ExD PACS

Server
Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
First partition
Approximately 550GB

Mount Point
/opt/imsdb
Size
All available space
Comments
Approximately 560GB
35
Image Data: 8 x 600GB in RAID 5

Mount Point
/usr/local/PACS
/usr/local/PACS/images/devX
Size
2TB-3TB
2TB-3TB each
Comments
First image data partition
Additional image data
partitions (1..M)

Mount Point
Size
All Available space
Comments
partitions (M+1..N)
Global Hot Spare(s):

2 x 600GB
RIS1A: Disk Configuration for RIS Database Server

Drive Letter
C:
E:
F:
G:
Size
80GB
50GB
100GB
50GB
Purpose
OS System Files
OS Temp Files
SQL Files
SQL Master DB
NTFS Cluster Size

4k
4k
4k
64k
64k
64k
64k
64k
Stripe Size
NTFS Cluster Size

64k
64k
NTFS Cluster Size

4k
64k

Drive Letter
D:
Size
280GB
Purpose
SQL Data
SQL Index
SQL Temp DB
Stripe Size

Drive Letter
R:
Size
280GB
Purpose
File Share
Stripe Size

Drive Letter
C:
E:
F:
Size
80GB
50GB
100GB
Purpose
OS System Files
OS Temp Files
SQL Files
NTFS Cluster Size

4k
4k
4k
Stripe Size
64k
64k
64k
36
G:
50GB
SQL Master DB
64k
64k
NTFS Cluster Size

64k
64k
NTFS Cluster Size

4k
Stripe Size
64k

Drive Letter
D:
Size
280GB
Purpose
SQL Data
SQL Index
SQL Temp DB
Stripe Size

Drive Letter
R:
Size
560GB
Purpose
File Share

Drive Letter
C:
F:
G:
H:
Size
80GB
50GB
100GB
50GB
Purpose
OS System Files
OS Temp Files
SQL Files
SQL Master DB
NTFS Cluster Size

4k
4k
4k
64k
64k
64k
64k
64k
Stripe Size
NTFS Cluster Size

64k
64k
64k
64k
64k
64k
NTFS Cluster Size

64k
64k
Stripe Size
64k
64k

Drive Letter
D:
L:
M:
Size
145GB
90GB
45GB
Purpose
SQL Data
SQL Index
Stripe Size

Drive Letter
E:
N:
Size
140GB
140GB
Purpose
SQL Temp DB

Share Server
Drive Letter
Size
C:
L:
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster
Size
4k
4k
Stripe Size
64k
64k
37

Drive Letter
R:
Size
1.1TB
Purpose
File Share
NTFS Cluster Size

64k
Stripe Size
64k

Share Server
Drive Letter
Size
C:
L:
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster
Size
4k
4k
Stripe Size
64k
64k

Drive Letter
R:
Size
1.6TB
Purpose
File Share
NTFS Cluster Size

64k
Stripe Size
64k
38
EV
Configuration EV:
Small Virtual Server
Common uses
Small Modality Server
This configuration is for a small modality server, typically with volumes less than 50,000
studies per year and less than 4,000 large multi-image studies (such as CT, PET,
tomosynthesis, etc) per year.
In addition to the resource requirements specified below, this virtual server and its vSphere
environment must comply with section Virtual Infrastructure Requirements and section
Networked Storage Performance Requirements.
Component
Model
CPU
Memory
Network
Remote Console
Storage
Image Storage Space

Available

Virtual Machine Version 7
4 virtual CPUs (2.66 GHz each)
16 GB
1 x 1GB network uplinks (VMXNET3 adapter)
Console access via vSphere client or URL
Approximately 700GB
Faster CPU clock
More memory
Upgrade to configuration E or F
Different-sized thick-provisioned virtual disks specified by Intelerad
39
EV
Disk Configuration
OS: 65GB on SAN
Mount Point
/boot
Swap
/
Size
500 MB
12 GB
All remaining space
Comments
First partition

Mount Point
/opt/imsdb
Size
All available space
Comments
Images: 700GB on SAN

Mount Point
/usr/local/PACS
Size
All available space
Comments
40
Configuration F: Medium Server

Common uses
Medium Modality Server
This configuration is typically used for volumes less than 200,000 studies per year,
including large multi-image studies (such as CT, PET, tomosynthesis, etc).
Analytics Server
RIS Database Server
A dedicated database server for an InteleRIS system typically handling volumes less than
650K orders per year.
RIS Fax Butler / File Server
A dedicated file and fax server for an InteleRIS system typically handling volumes less than
650K orders per year.
Component
Model
Hewlett-Packard
8SFF
OR
Form Factor
CPU
Memory
Network
Rack 2U or Tower
4 x HP 8GB RDIMM, 2133MHz
(32GB total)
331FLR Adapter
Remote Console

Support and Updates
RAID controllers

Controller
FBWC 12Gb 1-port Int SAS
Controller
Dell
Rack: PowerEdge R730xd
2.5 Chassis with up to 12 + 12
Hard Drives and 2 Controllers
OR

Chassis with up to 16 + 16, 2.5"
Hard Drives and 2 Controllers
Rack 2U or Tower
Daughter Card
iDRAC8 Enterprise
Dual PERC H730P RAID

Controllers, 2GB NV Cache
41
Component
Hard Disks
Hewlett-Packard
HP DL380 Gen9 Additional
8SFF Bay2 Cage/Backplane Kit
Other
Components
UPS
Image storage
space available
HP Smart Buy
Suggestion
Dell

Supply (1+1), 750W

Using 1.2TB hard drives: 6.4TB
Rack - SKU: 777338-S01
more cache
DIMM, etc)15K RPM drives instead of 10K RPM drives
900GB (or 1.2TB) drives instead of 600GB drives for image storage. In this case, the
image data partition should be split in two with the first half mounted under
/usr/local/PACS and the second half mounted under /usr/local/PACS/images/dev1.
With this upgrade, the total image storage space is approximately 4.8TB (or 6.4TB
when using 1.2TB drives)
For IntelePACS, replace the system with Configuration A plus one Configuration SM
InteleRIS Server (Changes from Configuration F)

Component
Hewlett-Packard
Dell
Memory
8 x HP 8GB (1x8GB) Single Rank PC312800 (DDR3-1600) Registered CAS-11

Memory (64GB total)

42
Hard Disks


RIS6B: RIS Fax Butler / File Share Server

Component
Hewlett-Packard
Dell
Model
ProLiant DL380 Gen9 - 24 SFF
Memory
Hard Disks
2 x 8GB RDIMM, 2133MHz, 1R or 2R x8

(16GB total)
PowerEdge R730xd Chassis with up

to 24 x 2.5" Drives + 2 x 2.5" Flex
Bay Drives
2 x 8GB RDIMM, 2133MHz, 1R or 2R
x8 (16GB total)
RAID
controller
HP Smart Array P440ar/2G Controller +

Battery
PERC H730P Integrated RAID

Expandability
The maximum amount of image storage space that the server can sustain will depend on
the particular load experienced by the server. If the observed load permits it, the image
storage on this server can be expanded through the addition of external storage of
configuration SM connected to a dedicated host bus adapter. The ultimate size of image
storage will be limited by the available space on the database RAID. For predominantly
small image sizes (e.g. CT), this limit can be as low as 100 times the size of the database
RAID.
Disk Configuration for PACS Modality Server

Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
First partition
43

Mount Point
/opt/imsdb
Size
All available space
Comments
Image Data: 7 x 600GB in RAID 5 and 1 x 600GB hot spare

Mount Point
/usr/local/PACS
Size
All available space
Comments
Approximately 3.2TB
Note: Two image partitions will be required when using larger hard drives. See note
under permissible upgrades.
Disk Configuration for PACS Analytics Server

RAID Controller 1:
Mount Point
/boot
swap
/
Size
500 MB
12 GB
All remaining space
Comments
First partition
About 1.1 TB
RAID Controller 2:
Mount Point
/opt/imsdb
Size
All available space
Comments
About 2.1 TB

Server
Drive Letter
C:
L:
Size
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster Size

4k
4k
64k
64k
Stripe Size
NTFS Cluster Size

64k
64k
64k
64k

Drive Letter
D:
M:
Size
190GB
90GB
Purpose
SQL Files
SQL Master DB
Stripe Size
44

Drive Letter
E:
Size
1.1TB
Purpose
SQL Data
NTFS Cluster Size

64k
64k
Stripe Size
NTFS Cluster Size

64k
Stripe Size
64k
NTFS Cluster Size

64k
64k
NTFS Cluster Size

64k
64k
64k
64k

Drive Letter
F:
Size
560GB
Purpose

Drive Letter
G:
Size
560GB
Purpose
SQL Index
Stripe Size

Drive Letter
H:
N:
Size
180GB
380GB
Purpose
SQL Temp DB
Stripe Size

Share Server
Drive Letter
Size
C:
L:
190GB
90GB
Purpose
OS System Files
OS Temp Files
NTFS Cluster
Size
4k
4k
Stripe Size
64k
64k
Array 2: 12 x 600GB in RAID 5 and 2 x 600GB hot spare

Drive Letter
R:
Size
6TB
Purpose
File Share
NTFS Cluster Size

64k
Stripe Size
128k
45
Configuration R: Rendering Server

Configuration R1: Dedicated Rendering Server
This configuration is typically used as a dedicated 3D Rendering server for IntelePACS 3D.
Component
Model
Form Factor
CPU
Memory
Network
Remote Console
RAID controller
Hard Disks
Other
Components
UPS
Image Storage
Space Available
HP Smart Buy
Suggestion
Hewlett-Packard
ProLiant DL360 Gen9
Rack 1U
(2.60GHz/10C/25M/105W)
8 x 8GB RDIMM, 2133MHz,
Dual Rank x8 (64 GB total)
331FLR Adapter
Dell
PowerEdge R430
Rack 1U
(2.60GHz/10C/25M/105W)
Daughter Card
iDRAC8 Enterprise

Support and Updates
PERC H730 Integrated RAID
Supply (1+1), 750W
Rack - SKU: 780020-S01
Faster Intel E5v3 CPUs with at least 10 cores and 2133MHz memory bus speed
46
More memory configured to run at least at 2133Hz (optimal DIMMs per channel, ranks
per DIMM, etc)
Larger Flash Backed Write Cache on RAID Controller
Equivalent blade server: HP BL460c Gen9 or Dell M630
Disk Configuration
All Data: 2 x 300GB in RAID 1
Mount Point
/boot
swap
/opt/imsdb
/
Size
500 MB
12 GB
30 GB
All remaining space
Comments
First partition
Image Data: Nil
Configuration R2:
Rendering Upgrade for Other Server Types
Often, Depot or Modality servers can be upgraded to accommodate 3D Rendering. Use the
following guidelines:
CPU must be at least Intel Xeon with memory bus running at least at 1600MHz. Intel
E5v3 processor family with memory bus at 2133MHz is preferred
Configuration A/AA/AB/AV/F servers shall have a minimum of 48GB of memory
Configuration E servers shall have a minimum of 32GB of memory
47
Configuration S: External Storage

External storage arrays can be attached to some server types to increase their storage
capacity. A separate RAID controller with external SAS ports is needed to attach external
storage. See Configuration SM1 and SC1. When multiple arrays are attached to the same
server, they may share the same RAID controller card but should be connected to different
SAS ports on the card whenever possible. It is the clients responsibility to fully configure
and present the storage (including any multipath setup), and to format the storage before
any scheduled Deployment-related activities occur.
Storage Area Network (SAN) technology can be used as an alternative to external disk
storage subject to the requirements described in the section Networked Storage
Performance Requirements. See Configuration SM2, SM3, SC2 and SC3.
SM: Storage for Large Modality Server

Component
Hewlett-Packard
Dell
SM1
Model
Form Factor
RAID
Controller
Hard Disks
HP Storage D3700
Rack 2U
HP Smart Array P421/1GB FBWC
6Gb 2-ports Ext SAS Controller
24 x HP 600GB 6G Hot Plug 2.5
SAS Dual Port 10K RPM
Image Storage
Space
Available
PowerVault MD1420
Rack 2U
PERC H830 RAID Adapter for External
JBOD, 2GB NV Cache
24 x 600GB 10K RPM Serial-Attach SCSI
6Gbps 2.5in Hot Plug Hard Drive

Using 1.2TB hard drives: 21.8TB
SM2
Fiber Channel
SAN Storage
Qlogic FibreChannel host bus adapter

3-5TB on enterprise class SAN meeting the performance criteria from the
Networked Storage Performance Requirements section
SM3
iSCSI SAN
Storage
Qlogic iSCSI adapter with complete iSCSI and TCP/IP offload

Gigabit or faster ethernet connection to SAN on dedicated iSCSI network
3-5TB on enterprise class meeting the performance criteria from the Networked
Storage Performance Requirements section
SM1:
Use 900GB or 1.2TB disks instead of 600GB disks (all disks of the same
size)
48
15K RPM instead of 10K RPM drives
Larger Flash Backed Write Cache on RAID Controller
HP: Replace P421 controller with P822 or P431. Recommended if more

than two arrays may be connected to the server
HP: add a second hot spare drive
Disk Configuration for PACS Server

Note for storage addition on a PACS server which is already in
production:
The following applies to prevent IntelePACS from writing studies to the new storage before
it has been fully configured, which can cause operational problems.
When preparing additional storage for a PACS server which is already in production,
please do not mount the partitions under the final mount points prior to the Deployment
Team performing its storage commissioning. Rather, once the new array has been
prepared, connected to the server, and the new partitions created, either
Do not mount the partitions, or
Mount them under temporary mount points:
/mnt/test_usr_local_PACS_images_devX where X is a number
Deployment will perform the final mounting operation.

Mount Point
/usr/local/PACS
Size
2TB-3TB
2TB-3TB each
Comments
partitions (1..M)

Mount Point
Size
2TB-3TB each
Comments
partitions (M+1..N)

Mount Point
Size
2TB-3TB each
Comments
partitions (N+1..O)
Global Hot Spare: 1 x 600GB
49
SC: Storage for Image Depot Server

Component
Hewlett-Packard
Dell
SC1
Model
Form Factor
RAID Controller
Hard Disks
HP Storage D3600
Rack 2U
FBWC 6Gb 2-ports Ext SAS
Controller
HP Smart Array Advanced
Pack 2.0
12 x HP 2TB 6G Hot Plug 3.5
SAS 7.200K RPM MDL Dual
Port Hard Drive
Image Storage Space

Available
PowerVault MD1400
Rack 2U
PERC H830 RAID Adapter
for External JBOD, 2GB NV
Cache
12 x 2TB 7.2K RPM NearLine SAS 6Gbps 3.5in Hot

Plug Hard Drive
Using 2TB hard drives: 18.2TB

SC2
Fiber Channel SAN
Storage for Image
Depot Server
Qlogic FibreChannel host bus adapter

Up to 60TB on enterprise class SAN meeting the performance
criteria from the Networked Storage Performance
Requirements section
SC3
iSCSI SAN Storage for
Image Depot Server
Qlogic iSCSI adapter with complete iSCSI and TCP/IP offload

Dedicated Gigabit or faster ethernet connection to SAN
Up to 60TB on enterprise class SAN meeting the performance
criteria from the Networked Storage Performance
Requirements section
SC1:
Use 3TB or 4TB disks instead of 2TB disks (all disks of the same size)
12Gbps disks instead of 6Gbps
HP: Replace P421 controller with P822 or P431. Recommended if more than two
arrays may be connected to the server.
Disk Configuration
Note for storage addition on a PACS server which is already in
production:
The following applies to prevent IntelePACS from writing studies to the new storage before
it has been fully configured, which can cause operational problems.
50
When preparing additional storage for a PACS server which is already in production,
please do not mount the partitions under the final mount points prior to the Deployment
Team performing its storage commissioning. Rather, once the new array has been
prepared, connected to the server, and the new partitions created, either
Do not mount the partitions, or
Mount them under temporary mount points:
/mnt/test_usr_local_PACS_images_devX where X is a number
Deployment will perform the final mounting operation.
Image Data: 12 x 2TB in RAID 6

Mount Point
/usr/local/PACS
Size
2TB-3TB
2TB-3TB each
Comments
partitions (1..N)
51
Configuration T: Tape Library

A tape library is connected to one or more Archive Servers with a SCSI, SAS or
FibreChannel controller. The tape library must support either LTO1-5, SDLT320/600, or
VS160 and must be in RedHats Certified Hardware list. Note that use of LTO-6 tapes is not
supported.
Supported Tape Libraries

Here is a list of currently certified tape libraries. Intelerad is willing to certify other
brands/models, provided the SCSI Reference Manual of the library is supplied to Intelerad.
Brand
Model
Slots
Drives
ADIC
FastStor
ADIC
FastTor2
ADIC
Scalar 24
SDLT: 21, LTO: 24
ADIC
Scalar 100
15-95
ADIC
Scalar 1000
118-1182
48
ADIC
Scalar 10K
700-3945
84
Dell
PV122T
Dell
PV124T
8/16
Dell
PV136T
15-72
Dell
PowerVault 136T
15-72
Dell
PowerVault ML6000*
36-404
18
Dell
TL2000/4000
24/48
2/4
HP
EML E-Series
71-505
16
HP
ESL E-Series
286-712
24
HP
MSL 2024/4048
24/48
2/4
HP
MSL6030
30
IBM
TS3200
44
IBM
TS3310
30-396
18
Quantum
ATL-P7000
679
16
Quantum
PX_Series
32-726
1-20
Quantum
M1500
25
Quantum
Super-Loader-3
8/16
Overland
Neo 2000
SDLT: 26 LTO: 30
QualStar
TLS-4000
14-600
12
Sony
CSM-200 Petasite
216 per cabinet
12
StorageTek
L700
216-1344
24
StorageTek
SL500
30-575
18
* The design of some tape libraries (such as the Dell ML6000) force the library robotics to be connected to
the host through one of the tape drives. In multi-server archive systems, this means that one drive must be
sacrificed since Intelerad uses a dedicated robotics server.
52
T1: Small Tape Library
Component
Hewlett-Packard
Dell
Model
HP StoreEver 1/8 G2 LTO-4

Ultrium 1760 SAS Tape
Autoloader
LTO-4, 1 drive, 8 slots
PowerVault 124T, LTO4-120

HH SAS, 800/1600GB
10 x HP LTO-4 Ultrium 1.6TB

RW Data Cartridge
HP H221 Host Bus Adapter
Tape Media for LTO4-120 tape

drive, 800GB/1.6TB, 10 Pack
6Gb SAS HBA, Dual Port
Tape
Technology
Components
Host Bus
Adapter
UPS
T2: Medium Tape Library

Component
Hewlett-Packard
Dell
Model
HP Storage MSL2024 1 LTO-4

Ultrium 1760 SAS Tape Library
Tape
Technology
Components
PowerVault TL2000, LTO4120HH, 800GB/1.6TB, 1 HH SAS

Drive
HP LTO-4 Ultrium 1.6TB Data

Cartridge (20pk)

Host Bus
Adapter
UPS
T3: Large Tape Library

Component
Hewlett-Packard
Dell
Model
HP Storage MSL4048 2 LTO-4

Ultrium 1760 SAS Tape Library
Tape
Technology
Components
LTO-4, 2 drives, 48 slots
PowerVault TL4000, 4U, LTO4120HH, 800GB/1.6TB, 2 HalfHeight SAS Drives

LTO-4, 2 drives, 48 slots
Host Bus
Adapter
UPS
Redundant Power
50 x HP LTO-4 Ultrium 1.6TB

RW Data Cartridge
TC: Custom-Size Tape Library

Please refer to the notes on your Hardware Requirements form.
53
Configuration U:
Uninterruptible Power Supply
In order to prevent potentially damaging unexpected power losses, all Intelerad servers
must be either provided with guaranteed power, such as at most co-location facilities, or on
an uninterruptible power supply (UPS).
Intelerad software supports the entire APC SmartUPS product line, not to be confused with
the APC SmartUPS On-Line products which are not supported. Each UPS must be
connected to one Intelerad server by a USB cable. All servers should have at least one
power supply connected to a UPS.
The Dell SmartUPS product line is also compatible.
In order to provide enough power for a clean shutdown, the following table should be used
to calculate the power requirement of your UPS:
Configuration Type
Power Requirement
1000VA
AA
1500VA
1000VA
1000VA
ExD
1500VA
1500VA
R1
1000VA
SM1, SC1
1000VA
T1, T2
T3
500VA
1000VA
54
Configuration X: Fax Modem

Intelerad requires the use of Mainpine brand fax modem boards to support report
distribution by fax. The boards require a free PCI-Express expansion slot in the server. See
http://www.mainpine.com/fax-board.php for more information. Fax modems can usually
send up to 30K to 50K reports per line per year. Actual sending performance may depend
on the transfer speed accepted by the receiving devices. Use of these Fax Modems from a
Virtual Machine is not supported.
X1: Smaller-Volume Fax Modem Board

Mainpine RF5120 / IQ Express 2-Line
X2: Medium-Volume Fax Modem Board

X3: High-Volume Fax Modem Board

55
Networking Details
Appendix 1: Networking Details

This section describes the network traffic of Intelerad software. Generally, we expect interserver traffic to be unrestricted. Therefore, the information provided in this section is subject
to change. However, this can be useful in the case where a firewall partitions the network.
Generally, it is a good practice to enforce Quality Of Service (QoS) on the network. In the
following tables, we provide our recommended QoS priorities that can be used to configure
QoS on the network. A lower priority number indicates that this traffic should take
precedence over other traffic with a higher priority number. Generally, database traffic
needs to be delivered most urgently while DICOM traffic can use the leftover bandwidth
with the lowest priority.
Between IntelePACS servers

In the case where one must filter the network internally between IntelePACS servers,
please verify that the following ports are open.
QoS
Priority
2
Protocol
Port
Service
Explanation
TCP
22
ssh
6
2
2
2
2
2
2
TCP
TCP
TCP
TCP/UDP
TCP
TCP
TCP
25
80
443
123
513
514
1991
smtp
http
https
ntp
login
login
https
2
5
2
2
2
2
TCP
TCP
TCP
TCP
TCP
TCP
4559
5000
5005
5006
5008
5009
hylafax
DICOM
RIS
RIS
RIG
https
3
2
4
2
2
3
1
2
1
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
5010-5011
5012-5019
5020-5022
5080
5100-5300
5269
5483
6130-6880
7100
DMWL
IntelePACS
InteleViewer
http/https
IntelePACS
Tigase
PostgreSQL
IntelePACS
sybase
Interactive Support Access and NonDICOM Data Transfer

Error Mails
Web Applications
Web Applications
Time Synchronization
Non-DICOM Data Transfer
Non-DICOM Data Transfer
Database Intermediaries Accounting
Central
HylaFAX client-server protocol
DICOM image transfer
Hl7 Communications
HL7GS console
RIG Proxy
Database Intermediaries Proxy
(external)
DICOM Modality Worklist
Inter-Process Communication
Wavelet Data for InteleViewer
webProxyController
Instant messaging
Database Access
Inter-Server Communication
Database Access
56
Networking Details
QoS
Priority
1
3
3
Protocol
Port
Service
Explanation
TCP
TCP
TCP
7110
9000-9012
9013
sybase
signaling
signaling
ICMP
Database Access
ReportServices (PACS 4-5-1 and lower
only)
Monitoring
ping
Between IntelePACS web server in DMZ and

IntelePACS servers
From IntelePACS servers to the IntelePACS web server in the DMZ, all ports need to be
open as per the table above (c.f. section Between IntelePACS servers). The following ports
are required to establish connections from the IntelePACS web server in the DMZ to the
IntelePACS servers on the internal network.
QoS
Priority
2
Protocol
Port
Service
Explanation
TCP
22
ssh
2
2
2
2
TCP
TCP
TCP/UDP
TCP
80
443
123
1991
http
https
ntp
https
5
2
2
2
TCP
TCP
TCP
TCP
5000
5005
5006
5009
DICOM
RIS
RIS
https
2
4
2
2
3
1
2
1
1
3
3
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
5012-5019
5020-5022
5080
5100-5300
5269
5483
6130-6880
7100
7110
9000-9012
9013
IntelePACS
InteleViewer
http/https
IntelePACS
Tigase
PostgreSQL
IntelePACS
sybase
sybase
signaling
signaling
ICMP
interactive support access and nonDICOM data transfer

web applications
web applications
time synchronization
Database Intermediaries Accounting
Central
Hl7 Communications
HL7GS console
Database Intermediaries Proxy
(external)
Wavelet data for InteleViewer
webProxyController
Instant messaging
database access
IntelePACS inter-server communication
database access
database access
inter-process communication
ReportServices (PACS 4-5-1 and lower
only)
monitoring
ping
57
Networking Details
Between IntelePACS servers and RIS

QoS
Priority
2
Protocol
Port
Service
TCP
5005
HL7
Explanation
This is the port on which the RIS is listening.
For a unidirectional RIS, this is port 5005 on
the RIS gateway server (or whichever port the
RIS listens on).
From scanner to IntelePACS servers

QoS
Priority
5
Protocol
Port
Service
Explanation
TCP
5000
DICOM
TCP
5010-5011
DMWL
DICOM Modality Worklist
From InteleViewer workstations to IntelePACS

servers
QoS
Priority
3
Protocol
Port
Service
Explanation
TCP
80
http
InteleBrowser
TCP
443
https
secure InteleBrowser sessions
TCP
5020
InteleViewer
unencrypted Wavelet data for InteleViewer
TCP
5021
InteleViewer
encrypted Wavelet data for InteleViewer
TCP
5022
InteleViewer
Wavelet proxy for InteleViewer
Note 1: this is not applicable to other vendor's workstations.

Note 2: for workstations outside the IntelePACS network, the Wavelet proxy will always be
used. As well, it is recommended that external access always be encrypted, so only ports
443 (SSL) and 5022 (Wavelet proxy for InteleViewer) will be required outbound from
external InteleViewer workstations. Note that if HTTP tunneling over port 443 is available,
wavelet proxy will also be handled over port 443, and port 5022 will not be required.
From IntelePACS servers to M*Modal Data

Centers
QoS
Priority
3
Protocol
Port
Service
Explanation
TCP
443
https
Audio streaming for voice recognition
Note 1: this is applicable only when using Multi-Method reporting with M*Modal VR
58
Networking Details
From IntelePACS servers to InteleViewer

workstations
QoS
Priority
5
Protocol
Port
Service
Explanation
TCP
5035
InteleViewer
DICOM data for InteleViewer
59
FAQ
Appendix 2:
Frequently Asked Questions
Why does Intelerad require exactly this
configuration?
IntelePACS servers are a Class II medical device certified by regulatory bodies in several
countries and therefore are supported by Intelerad only in the provided configuration. With
our standard certified configurations, we believe to have captured the optimal reliability and
performance to meet the IntelePACS requirements. While certification for different
configurations is possible, the delays and costs involved make this an economically
undesirable option.
How does Intelerad determine the recommended

hardware configurations?
In order to provide the responsiveness that is required in a busy clinical environment, we
expect our servers to respond to 98% of all queries in less than 2s. Monitoring the behavior
of our existing servers in the field allows us to maintain good software design practices as
well as adjust our recommended hardware configurations to stay in-line with this
expectation.
In addition to the performance of our servers, best information technology practices dictate
a standard in component redundancy and hardware supportability.
Why does Intelerad specify expensive SAS

drives?
SAS (Serial Attached SCSI) drives are made for the load experienced by a busy server.
SAS drives have more sophisticated controllers that can better interact with a RAID
(Redundant Array of Inexpensive Disks) controller, and thus offer greater reliability. For
instance, Hewlett Packard states meantime between failures for SAS drives at 100% duty
cycle but only at 40% duty cycle for SATA (Serial ATA).
Why do the Database and Image Depot servers

have so many disks?
Image Depot and Database servers contain large databases to index the entire IntelePACS
(Database Server) or to index a large store of priors (Image Depot Server). These
databases experience a significant load. Consequently, they require reliable SAS-based
RAIDs. A Database or Image Depot server has typically two RAID sets, one for the OS and
software, the other for databases.
60
FAQ
I already have hardware from my previous PACS

or RIS. Can I use the server hardware?
You can reuse the old server hardware only if you can adjust the old server hardware to
match our specifications.
Can Intelerad certify my existing server

hardware?
Yes we can, provided it meets our standards. However, the cost and time delays involved
in certifying different hardware configurations are significantly larger than individual server
hardware. This approach is only economical for very large installations with consistent
existing hardware.
Can Intelerad migrate my old image data and

then reuse the old hardware?
No. For purposes of data migration, Intelerad software has to be installed on its final
hardware and the legacy system usually has to continue operating for the duration of the
data migration.
I already have a SAN. Can I reuse it?

Yes. Provided the SAN (Storage Area Network) can interface with our IntelePACS servers
via FibreChannel or iSCSI, IntelePACS servers can use the SAN for image storage. SAN
storage needs to be based on FibreChannel or SAS drives for Modality Servers. SATA
drive based storage is only permitted for Image Depot Servers.
NFS may be used for virtual disks and is subject to the performance requirements of
section Virtual Infrastructure Requirements.
If you already have data on your SAN, and you want to reuse the same storage space after
a data migration, you need to ensure that IntelePACS initially has enough SAN storage to
store all migrated data.
I want to use VMware. Do you support

virtualized servers?
Intelerad supports the operation of virtualized IntelePACS and InteleOne. If you are
confident that you can meet the requirements for a virtual server infrastructure as described
in sections Virtual Infrastructure Requirements, Configuration AV:
Medium and Large Virtual Server, and Configuration EV:
Small Virtual Server, then please request that we architect your solution in terms of these
server types. Pay close attention to the I/O performance requirements which have a
significant impact on overall performance.
61
FAQ
Do virtual machines ever need to be

evergreened or assigned additional hardware
resources?
Yes.
The resources allocated to a virtual machine may need to be changed over time to ensure
appropriate performance and compliance with newer versions of this document. This allows
Intelerad to recommend virtual hardware with less spare capacity than would be necessary
in physical configurations that are expected to last until they are evergreened.
Even if appropriate resources are added to a virtual machine over time, Intelerad may
eventually require a new virtual machine with a fresh installation of a newer version of the
Operating System as a prerequisite to an upgrade of its products.
Do you support iSCSI storage?

Yes.
In order to avoid excessive CPU load and to allow for a dedicated storage network, iSCSI
storage requires an iSCSI host bus adapter in the server.
Do I need to follow Intelerad's hardware

specifications?
Intelerad will review the server hardware prior to installation of software. Intelerad will not
install its software on server hardware that does not meet its specifications. Any
discrepancy between the approved and delivered hardware will lead to delays in software
installation.
Do I need to follow a particular host naming

conventions when installing servers?
Yes.
Intelerad has a specific naming convention for servers running Intelerad software. This
policy allows our employees to best provide effective and efficient service. For details on
this policy, please see: https://support.intelerad.com/modules/technotes/faq.php?faqid=199
(login required).
What will happen if my hardware doesnt meet

Intelerads hardware specifications?
Intelerad is ISO 13485:2003 certified and follows strict quality standards. Before deploying
our software, our Deployment Specialists validate every server against this document and
will report any discrepancy to your designated Intelerad Project Manager or Account
62
FAQ
Manager for approval. This may result in delays in installing and configuring the server,
which invariably cause delays in putting the server in production. Intelerad reserves the
right to refuse to install its software on hardware that doesnt meet its requirements.
63

HardwareRequirementsGuide 13.8

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

HardwareRequirementsGuide 13.8

Загружено:

Авторское право:

Доступные форматы

Intelerad

Hardware and Network

Intelerad Medical Systems - Confidential

Hardware Requirements Guide

Hardware Requirements Guide

How to Use this Document

Hardware Covered in this Document

Disk enclosures connected to servers

Uninterruptible power supplies (UPS)

Hardware Requirements Guide

Hardware Requirements Guide

Hardware Approval Process

Issuance of Hardware Specifications

Verification of Hardware and Configuration

Hardware Requirements Guide

Operating System Requirements

For installations older than IntelePACS 4.10.1R2:

Red Hat Enterprise Linux 6, latest Update, for 64-bit x86.

For installations of IntelePACS 4.10.1R2 or higher:

Red Hat Enterprise Linux 7, latest Update, for 64-bit x86.

Notes on Red Hat Installation

Operating System installation is the responsibility of the client.

Recommended Red Hat subscription is Standard Subscription. Self-Support

The prescribed hostname must be used.

Hyper-threading must be disabled on the server.

Internal, external, or virtual CD/DVD drive will be required to install the OS

All servers must be configured to use the ext4 file system.

Logical Volume Manager (LVM) is not supported.

Swap space must be 12 GB and must be located on the OS RAID.

Maximum supported LUN size is 3TB.

Hardware Requirements Guide

Please ensure to enable write-back caching on RAID controllers equipped with a

Supported Windows Versions

Microsoft Windows Server 2008 R2 Standard Edition 64-bit

Notes on Windows Installation

Operating System installation is the responsibility of the client.

The prescribed hostname must be used.

Hyper-threading must be disabled at the BIOS level.

All servers must be configured to use the NTFS file system.

All partitions must be created with a partition offset of 1024K.

Disable Windows System Restore.

Hardware Requirements Guide

The letter representing the base hardware configuration (eg: A, E, F, etc)

A letter, A or B, specifying the server type

InteleRIS database server location

InteleRIS Server Redundancy and Mirroring

Hardware Requirements Guide

Virtual Infrastructure Requirements

VMware vSphere 4.x Essentials Plus or higher

VMware vSphere 5.x Essentials Plus or higher

In order to facilitate troubleshooting performance-related issues of a virtual

All hardware must be on VMwares hardware compatibility list.

Memory resources must be fully reserved.

VMware tools must be installed on the guest OS.

Console access to Intelerad servers must be provided to Intelerad. A new user

Hardware Requirements Guide

Storage disk type:

VSphere version less than 5.5: Only physical-compatibility mode raw

Virtual disks must be thick-provisioned.

Virtual disks must be implemented with the same class of hardware

Hardware Requirements Guide

Networked Storage Performance

To measure sustained writes on the DB partition, run: