Transcript Dorado 400

Dorado 400
Series Server
Club 2200
Page 1
Dorado 400 Series Server
• First member of the Dorado family
based on the Next Generation
architecture
• Employs Intel 64 Xeon Dual Core
processors
• Executes all existing OS 2200
basic mode programs and
extended mode programs without
re-compilation or re-linking
• Highly evolved development test
suites used to validate:
– Security
– Availability
– Reliability
Page 2
Dorado 400 Series Server
• Flexible buying options
– Dorado 420 non-metered model
– Dorado 430 metered model
• Pre-Paid
• Base Plus usage
• Workload pricing
–
–
–
–
General Purpose Production
Development and Test
BIS and EAE
Disaster Recovery
• Provides long term support of your
OS 2200 applications
Page 3
Dorado 400 Series Server
• System performance up to 400 MIPS
• Single thread performance 90 MIPS
• Single partition system
• Supports same peripherals as Dorado 300
• Running today in a Unisys production
environment
– Demand, Batch, HVTIP, TIP, BIS, DMS,
RDMS, SFS, EAE
• Supported by OS 2200 ClearPath Rel 11.2
• Available now
Page 4
The Cell
• The central building block of this system is the cell
containing
– Four dual core processors
– Two gigawords of memory
– Redundant power and cooling
Page 5
Hardware Components
• The Dorado 400 system
consists of a number of rack
mounted major components
Remote I/O Module
– Internal I/O Cell
– Procnode Cell
– Remote I/O Module
Procnode Cell
Internal I/O Cell
Page 6
Hardware Components
• The Dorado 400 systems
contain two cells
comprising a cell-pair
Procnode Cell
– Internal I/O Cell
– Procnode Cell
Internal I/O Cell
Page 7
Hardware Components
• The Internal I/O Cell contains the major
processing components of the system
–
–
–
–
Intel processors
Memory
Network Interface Cards (NIC)
Infrastructure components such as power
and cooling
– System (SAS) disks
Note: the network interfaces for the Dorado 400 system
are found in the Internal I/O Cell
SAS – Serial attached SCSI
Page 8
Hardware Components
Internal I/O Cell
• Internal I/O cells contain four dual-core Tulsa processors
and 2GW of memory
– One Internal I/O Cell, configured with one DVD for installation
of SAIL software,
– One on-board, dual-port Network Interface, and five PCI slots
support Host Bus Adapters and Network interface Cards
– The on-board Network Interfaces provide network connectivity
for both the SAIL and OS 2200
– The HBAs provide connectivity for the storage used by SAIL
Page 9
Hardware Components
Procnode Cell
• The Procnode cell provides pathway to the Remote I/O
Module (I/O Cell)
– Is paired with the Remote I/O Module
– Is not allowed to have processors or memory
Procnode Cell
Page 10
Hardware Components
Main Storage
• The Main Storage Unit is contained within the Internal I/O
Cell
– The base cell contains 2GW of memory (using 4 GByte
DIMMs)
– One 36-bit OS 2200 word is contained in each 8 bytes of
platform memory
– Memory is used by infrastructure and 2200 software
Page 11
Hardware Components
Remote I/O Module
• OS 2200 storage peripherals are attached through the
OS 2200 Remote I/O Module
Page 12
Hardware Components
Remote I/O Module
• Each of four Storages IOPs supports two native peripheral
component interconnect (PCI) slots (8 total)
– One PCI slot contains a controller card for the DVD
– Remaining SIOP slots contain HBAs or a bridge card to an
external PCI Expansion Rack with up to 7 PCI cards
Page 13
Architecture
• The Dorado 400 Series systems have a new software
infrastructure layer not present in predecessor systems
OS 2200 Applications
OS 2200
Remote I/O Module
Procnode Cell
System Architecture
Interface Layer
Internal I/O Cell
Page 14
Architecture
Virtualization
• On Dorado 400 systems, virtualization is provided in the
form of the System Architecture Interface Layer (SAIL)
– Includes infrastructure software consisting of Linux programs
and applications
– Includes Unisys extensions/modifications to Linux packages
– Includes the OS 2200 emulation environment
– Includes Linux Kernel* software
IP Engine
I/O
Native EXEC Support Functions
Environment Control
Hardened Linux Subset
Comm
Console
Note: Linux Kernel
is also referred to as
the SAIL Kernel
Page 15
Architecture
Virtualization
• The underlying virtualization logic contains many
components
Page 16
Implementation
• The Dorado 400 system software is implemented in the
form of several different layers
– OS 2200
– System Architecture Interface Layer (SAIL)
• Infrastructure
• Kernel
– External components
SAIL
External
Components
OS 2200
Page 17
Software Components
SAIL
• The underlying software in which the OS 2200
environment executes is referred to as the System
Architecture Interface Layer (SAIL)
– SAIL kernel
– System Control
– SAIL Control Center
SAIL
External
Components
OS 2200
Page 18
Software Components
OS 2200
• OS 2200 refers to the combination of operating system
products that constitute the 2200 Series OS
– Integrated Operating Environment products
– Including the OS 2200 products and features
– Including the 2200 Series EXEC with Dorado 400 specific
adaptations
SAIL
External
Components
OS 2200
Page 19
Software Components
External Components
• External components include software external to the
system cabinet
– Operations Sentinel
– OS 2200 Server Management Control
– Client Interfaces
SAIL
External
Components
OS 2200
Page 20
Software Components
SAIL - SAIL Kernel
• The SAIL kernel provides the operational environment
supporting core functions of the infrastructure
– Interfaces with hardware and allows other layers to be
hardware independent
– Provides lock down security and other enhancements
– Provides APIs
• For networking (sockets)
• For peripherals for Server Sentinel hardware APIs
Page 21
Software Components
SAIL – SAIL Kernel
• The SAIL kernel includes
–
–
–
–
–
–
–
true multitasking
virtual memory
shared libraries
demand loading
shared copy-on-write executables
proper memory management
TCP/IP networking
Page 22
Administration & Operations
• The Dorado 400 provides a
number of administrator
and operator interfaces
– Accessible through the
Operations Server or
Workstation
– Associated with different
functions and phases of
operation
– Accessible at a high level
through Operations
Sentinel (SPO)
Page 23
Administration & Operations
•
Each interface is used for a different purpose and
operator or administrator role
1. Host operating environment setup and activation
2. Host operating system console
3. Virtualization software installation
4. Virtualization software configuration and diagnosis
5. OS 2200 system setup and activation
6. OS 2200 operations
Page 24
Administration & Operations
• In practice the operator interface remains largely unchanged from the past
– Host OS setup is done during installation and after stops
– Virtualization software setup is done during installation and
after stops
– OS 2200 activation and operations are the norm…
Page 25
Administration & Operations
• The interfaces on the Dorado
400 can be compared to
those on previous systems
– Each is dedicated to a
purpose or role
– Each is initiated only when
needed
– Most are rarely used
– Each is accessible from a
common point – the
Operations Sentinel Console
Page 26
Considerations
• Customers that use Exec local code or software that
depends on hardware monitor instrumentation may need to
change their software to run on Dorado 400
Page 27
Considerations
Multi-Host
• The format of the Dorado 400 boot tape is different than on
predecessor systems
– Dorado boot tapes cannot be used on non-Dorado 400
systems
– A Dorado 400 boot tape may be deployed across multiple
Dorado 400 systems
Page 28
Considerations
Operational Interfaces
• Dorado 400 system has a number of new or different
Operational interfaces
Page 29
Considerations
Communications
• A new communications control program, Communications
Platform for Open Systems (CPCommOS) is introduced
to manage OS 2200 networking
Page 30
Considerations
System Time
• System time is managed (configured) through the SAIL
Control Center (SAIL CC)
Page 31
Considerations
Memory Management
• Memory management and allocation in the system has
changed
Page 32
Considerations
Log Data
• In addition to the OS 2200 log files, SAIL maintains log
data in separate files
• The Dorado 400 system utilizes SLAR for log reduction
System Log Analysis and Reports for ClearPath
OS 2200 (SLAR) produces reports from ClearPath
OS 2200 system log files AND SAIL system log files.
System administrators can use these reports to analyze
the use of the system.
Page 33
Considerations
Console Messages
• Minor changes have been made to utilities and messages
to reflect differences between the Dorado 400 and
predecessor systems
Page 34
Unisys
Thank you
Page 35