CP6100 Configuration and Management Manual

CP6100 Configuration and Management Manual—426741-003
2-1
2
Overview of the CP6100 Subsystem
This section provides an introduction to and describes the subsystem components of
the CP6100 subsystem and the protocols supported by CP6100.
This section contains the following topics:
•
Introduction to CP6100 on page 2-1
•
CP6100 Supported Protocols on page 2-3
•
CP6100 Subsystem Management Tools on page 2-6
•
Online Expansion and Reconfiguration on page 2-7
Introduction to CP6100
The CP6100 subsystem consists of the CP6100 input-output process (IOP) and a
protocol module. The CP6100 IOP, also known as the CP6100 Communications
Access Process (CAP), is a NonStop process pair running in a NonStop server. The
process acts as a file-transfer mechanism to move data between an application and a
protocol module that resides and runs in the Communications Line Interface Process
(CLIP) as a task.
The protocol module is a microcode file or down load module (DLM) that contains OSI
Layer-1 and Layer-2 processing tasks. The CP6100 CAP thus provides the application
with a data-link level interface to asynchronous, byte-synchronous, or bit-synchronous
protocol modules in a 6100 Communications Subsystem (CSS), which uses the SWAN
concentrator. Application data is passed to one of several protocol modules by
CP6100. The protocol module gives the application extensive control over the line, and
each protocol module can control either a single line or multiple lines. Figure 2-1
illustrates a CP6100 environment with two CPUs.