Ericsson AXE 3 Service Manual
Competence Development Centre
AXE Operation & Maintenance Platform
IO-System
Help Exit
PREFACE
Target Audience
This book is preliminary intended to be used as a course manual in the
Ericsson Operation and Maintenance training program. The book is a
training document and is not to be considered as a specification of any
Ericsson language or system.
Identification
EN/LZT 101 105/3 R1A
Responsibility
Training Supply
ETX/TK/XM
Ericsson Telecom AB 1996, Stockholm, Sweden
All rights reserved. No part of this document may be reproduced in any
form without the written permission of the copyright holder.
Table of Contents
1. Introduction 1
1.1 Module Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2. Configuration of IOG 11
and Hardware Structure 3
2.1 Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Configuration of IOG11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1 SP-based IO Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.2 Input/Output Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.3 IO Device Functions and Characteristics. . . . . . . . . . . . . . . . . . . . 9
2.3 Subsystems in IOG11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3.1 Support Processor Subsystem (SPS) . . . . . . . . . . . . . . . . . . . . . 12
2.3.2 Man-machine Communication Subsystem (MCS). . . . . . . . . . . . 14
2.3.3 File Management Subsystem (FMS). . . . . . . . . . . . . . . . . . . . . . 16
2.3.4 Data Communication Subsystem (DCS) . . . . . . . . . . . . . . . . . . . 18
2.4 Hardware Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.2 Different SP-Based IO Systems. . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.3 Magnetic Tape Group (MTG 10) . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4.4 IOG 11B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.5 IOG 11B5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.6 EXternal RANGing (EXRANG) . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.4.7 IOG 11C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.8 IOG 11C5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.4.9 LEDs and Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.4.10 1.05 GBytes Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
03802-EN/LZM 112 19 R1A i
I/O System
3. Command and File Handling 53
3.1 Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.2 IOG 11 Command Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.2.1 Entry Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.2.2 Subcommands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.2.3 Local Mode and CPT Commands . . . . . . . . . . . . . . . . . . . . . . . . 60
3.3 Status of IOG 11 Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.3.1 RPA State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.3.2 Node Configuration Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.3.3 Line Unit Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.3.4 Port Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.3.5 MCS Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.3.6 Blocking and Deblocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.4 File Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.4.1 FMS Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.4.2 Functions of FMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.4.3 The Software of FMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.4.4 Mass-Storage Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.4.5 Volumes on Floppy Disk, Optical Disk and Tape . . . . . . . . . . . . . 80
3.4.6 Volumes on Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.4.7 File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
3.4.8 Creation of a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.4.9 Printing File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.4.10 Removal of a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.4.11 Copying of Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.4.12 Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.5 File Process Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.5.2 Manual Transfer over Data Link. . . . . . . . . . . . . . . . . . . . . . . . . . 91
3.5.3 Automatic Transfer over Data Link. . . . . . . . . . . . . . . . . . . . . . . . 91
3.5.4 Output on Magnetic Tape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.5.5 Direct File Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.6 Charging Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.7 The MCS Transaction Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.8 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ii 03802-EN/LZM 112 19 R1A
Table of Contents
4. System Backup Handling 105
4.1 Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.2 Backup Functions of the CP . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.2.1 Manual Dumps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.2.2 Automatic Dumps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.2.3 The CP Backup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.2.4 Backup Handling (APZ P1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.2.5 Command Log (APZ P1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.2.6 Backup Handling (APZ P2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4.2.7 Command Log (APZ P2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.3 Conversion of System Backup Files . . . . . . . . . . . . . . . . . . . . . 119
4.4 Backup of the SP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
4.5 Loading of APZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.5.1 The APZ Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.5.2 States of the two CP sides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4.5.3 CPT System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.5.4 Separation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.5.5 Loading of APZ 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.5.6 Loading of APZ 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4.6 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
03802-EN/LZM 112 19 R1A iii
1. Introduction
1.1 Module Objectives
Module Objectives
After completing this module the participant will be able to:
• Describe the configuration of IOG11
• Name the basic concepts of the four subsystems in IOG11, i.e. SPS,
FMS, MCS and DCS.
• Explain the purpose of entry commands in IOG11.
• Describe briefly the different statuses and states of the nodes in a
node pair.
• Use IOG11 commands for creating, copying, deleting, writing to,
reading the contents of and executing files.
• Explain the purpose of the File Process Utility function (FPU)
giving the types of data that are normally transferred by this
function.
• Use the FPU function to transfe r files from hard disk to a magnetic
tape or via an already existing data link.
• Set up logging conditions for the MCS Transaction Log and
execute searching in the log file.
• Perform command-initiated conversion, loading, dumping and
logging of CP backups.
Figure 1.1
Module objectives
1.2 General
This module is valid for the control systems and IO systems available in
the following APZ Source Systems:
APZ P1:
•
APZ 212 10 R2
•
APZ 212 02 R3
•
APZ 211 10 R2
•
APZ 211 02 R7
03802-EN/LZM 112 19 R1A 1
IO System Basic
APZ P2:
•
APZ 211 11 R1
•
APZ 212 11 R1
•
APZ 212 03 R1
The processors to be used for AXE Local 12.3 will all have to run with the
APZ P2 operating system.
The APZ P1 versions can be updated to APZ P2 by changing the PROM
stored firmware.
For APZ P2, the IO system IO-P2 has been introduced. Both processor and
storage capacity have been improved in comparison with IO-P1. Ho we v er,
the IO system can easily be updated from IO-P1 to IO-P2 for both APZ P1
and APZ P2.
The most relevant differences between APZ P1 and APZ P2 concerning
the IO system are the use of the Command Log and reloading of CP
backups.
In this module, all the Operational Instructions that are mentioned are
valid for AXE Local 12.3.
2 03802-EN/LZM 112 19 R1A
2. Configuration of IOG 11 and Hardware Structure
2.1 Chapter Objectives
Chapter Objectives
After completing this chapter the participant will be able to:
• Describe the main tasks of the IO System.
• Describe the configuration of an IOG11.
• Explain the concepts Node, Link and SPG.
• Relate the main use of Hard Disks, Floppy Disks, Magnetic Tapes
and Optical Disks.
• Relate the main use of Data Links.
• Name the four subsystems incorporated in IOG11 and give the
names of the hardware units that are included in each subsystem.
• Briefly account for the main differences between the IO variants
IOG 11B/B5 and IOG 11C/C5.
• Name the different magazines that are included in IOG 11 and
know where the IO devices are connected.
• Describe the units that constitute an MTG 10.
• Interpret leds and buttons.
Figure 2.1
Chapter objectives
2.2 Configuration of IOG11
2.2.1 SP-based IO Systems
This book provides a description of the Input/Output system IOG 11 as
suited to the work of the operation and maintenance technician.
IOG 11 belongs to what is normally called SP-based IO Systems. SP is an
abbreviation for Support Processor, the separate processor that controls the
IO system.
Several variants of SP-based IO Systems exist today:
IOG 11A, IOG 11B, IOG 11C, IOG 11B5, IOG 11C5 and IOMC.
Each of these will be covered, except IOG 11A and IOMC.
03802-EN/LZM 112 19 R1A 3
IO System Basic
This document will include such topics as:
the IO functions and devices
•
the hardware configuration
•
the subsystems that are included in the IO group
•
the connection to the Central Processor, CP
•
command handling
•
the treatment of files on magnetic storage media
•
general operation procedures for IOG 11.
•
Examples will be given of
file handling
•
charging outputs
•
dumping and system backup handling (conversion)
•
logging functions
•
loading of APZ during normal operation.
•
Initial loading and maintenance of the CP will be covered in the course
LZU 108 1453, AXE 10 Hardware Maintenance.
2.2.2 Input/Output Functions
The IO functions of IOG 11 reflect the tasks to be performed by the equipment. These tasks can be generally described as follows:
handling of data
•
secondary storage
•
The above mentioned data handling can consist of the transportation of
either
from a terminal or over a data link - or of data stored in
netic media. Note that the information stored in a file can be either binary
information e.g. backup data, or alphanumeric data e.g. commands in a
command file.
alphanumeric
information - e.g. commands and printouts sent to or
(binary or alphanumeric) to and from the
CP. IOG 11 is the IO interface to the
world outside an AXE exchange.
(mass storage) of information on magnetic
media, e.g. hard disk, flexible disk, magnetic tape and optical disk.
files
on the mag-
From the above considerations we see that the hardware of IOG 11 must
contain the following components:
an interface to the Regional Processor Bus (RP Bus) for connection of
•
the IOG to the CP
4 03802-EN/LZM 112 19 R1A
Configuration of IOG 11 and Hardware Structure
a processor with the necessary software to control the different units,
•
diagnose IO faults and to communicate with the CP
external mass storage devices (hard disks, floppy disks, magnetic tapes
•
and optical disks)
data links for both high speed and low speed traffic using both asyn-
•
chronous and synchronous transfer
alphanumeric terminals for man-machine communication.
•
As well as the above units, the IO Group is also required to provide alarm
information on the alarm panel and alarm printer.
The alarm information concerns both internal alarms from APT, APZ and
the IOG itself, as well as external alarms (temperature, humidity, door
control, etc).
The IOG must also contain:
an alarm printer - i.e. an alphanumeric terminal to which alarm print-
•
outs are automatically routed. A separate alarm printer is normally
defined (but any alphanumeric terminal and slave printer can be used.)
an alarm interface to which alarm panels and external alarm sensors are
•
connected.
The above mentioned components are incorporated in IOG 11 as shown in
figure 2.2.
03802-EN/LZM 112 19 R1A 5
IO System Basic
CP
DL DL
Figure 2.2
Example of an IOG11
AT
AT
ALI
RPA
SP
RPA
ICB
HD
AT
FD FD
AT
OD
AT
MT MT
Note:ODforIOG11B5/C5
SP
HD
OD
Figure 2.2 shows the standard IOG 11 configuration for the products
IOG 11B/B5 and IOG 11C/C5. The differences between the variants will
be covered later.
The interface to the Regional Processor Bus is called the
RP Bus Adapter
(RPA).
The RPA is basically a regional processor, with its own unique address,
that is adapted to the task of helping the main processor in IOG 11 in its
communication with the CP.
The control unit in IOG 11 is a processor called the
SP
for short.
Support Processor
, or
The IOG11B/C is based upon the Motorola 68010 (CP-3) processor, introduced with APZ 212/211 10 R1, APZ 212 02 R2 and APZ 211 02 R6. The
IOG 11B5/C5 is based upon the Motorola 68030 (CP-5) processor, introduced with APZ P2.
The SP contains a considerable amount of software and has an internal
memory of max 12 megabytes (Mb) for IOG 11B/C and 32 Mb for
IOG 11B5/C5. Furthermore, a large amount of data required by the SP is
stored on the hard disks and used by the SP when required.
6 03802-EN/LZM 11 2 19 R1A
Configuration of IOG 11 and Hardware Structure
The CP also contains a fairly large amount of software used by IOG 11.
We will look at this later on when the different subsystems of IOG 11 are
examined.
As can be seen, the RPA and SP are duplicated in the standard IOG 11
configuration. This is done as a precaution against faults (hardware or software) arising in one of the SPs.
The two SPs are connected by a bus called the
The ICB allows data to be transferred between the two SPs. It is an 8 bit
parallel bus and carries data at a maximum nominal rate of 115 kilobytes/s
(kb/s).
The SP is often called
switched data network).
The nodes in the duplicated configuration shown above are designated
Node A
The RPA is also called
The IO devices shown in figure 2.2 are as follows:
AT
•
ALI
•
DL
•
HD
•
FD
•
OD
•
Node B
and
Optical Disk drive
Node
(as it can be used as a node in a packet
.
Link
, as it is a link between the SP and the CP.
Alphanumeric Terminal
Alarm Interface
Data Link
Hard Disk drive
Floppy Disk drive
Inter Computer Bus (ICB)
.
MT
•
The IO devices will be covered in detail in the next section.
An IOG 11 as described above - with two nodes each controlling a number
of IO devices - is called a
An SPG can consist of one unduplicated node, but this is very unusual
with IOG 11A, IOG 11B,and IOG 11C. The product IOMC has a very
compact design and consists of one single node. It is used for very small
exchanges.
A Support Processor Group is shown in figure 2.3
Magnetic Tape drive
Support Processor Group, SPG
.
03802-EN/LZM 112 19 R1A 7
IO System Basic
.
CP-A
CP-B
RPA
SP
RPA
RPB-A
RPB-B
SP
ICB
SPG
Figure 2.3
A Support Processor Group (SPG)
It is possible to connect up to four SPGs to the CP, as is shown in
figure 2.4.
CP
RPB-A
RPB-B
SP SP SP SP
ICB
SPG-0
ICB
SPG-1
ICB
SPG-2
ICB
SPSPSPSP
SPG-3
Figure 2.4
Four SPGs connected to the RP bus
As can be seen from the figure, each SPG is numbered, with the first SPG
being designated SPG-0.
Most AXE exchanges with IOG 11 will require just one SPG, i.e. SPG-0,
whereas exchanges requiring very large amounts of output data storage
and transfer would require two or three SPGs.
SPG-1, SPG-2, and SPG-3 provide basically separate processors for handling such data. They relieve the workload of the SPs in SPG-0 which can
be used to handle the alphanumeric IO devices and alarms.
8 03802-EN/LZM 112 19 R1A
IO System Basic
The data stored in these SPGs is norma lly toll ticke ting data a nd statisti ca l
data which is subsequently transferred to remote destinations on high
speed data links or transferred to tape.
We will look more at this later when we examine the different possible
IOG configurations.
In SPG-0, the link at Node A is designated
Link 1
nated
Link 0 has RP address
In the other SPGs the corresponding designations are:
Link 2 (RP-5) and Link 3 (RP-6)
•
Link 4 (RP-7) and Link 5 (RP-8)
•
Link 6 (RP-9) and Link 7 (RP-10)
•
.
RP-1
and Link 1 has RP address
Link 0
and at Node B is desig-
2.2.3 IO Device Functions and Characteristics
The IO devices that we use in IOG 11 have already been mentioned. They
will now be examined in more detail.
Alphanumeric Terminal (AT)
nication. The ATs are used for sending commands and receiving printouts.
An AT can be any type of
computer (PC), a display handler or typewriter . It can also be a line p rinter ,
e.g. the alarm printer is also an AT, as shown in figure 2.5.
PCs and display handlers can, of course, have hardcopy printers
connected.
is the device used for man machine commu-
asynchronous
terminal, normally a personal
RP-4
.
9 03802-EN/LZM 11 2 19 R1A
IO System Basic
CP
RPA
ICB
SP
HD
AT
FD
AT
OD
ALI
MT
DL
Figure 2.5
IO devices
Alarm Interface (ALI)
is the interface to which the alarm panels and external alarm sensors are connected. External alarm information is sent to the
SP, and internal and external alarm information sent to the alarm panels,
via this interface.
As we shall see when we look at the hardware configuration, the ALI is
connected to the SP in exactly the same manner as an AT device. It is
regarded as being an AT device and is defined in the data as such.
It should be noticed from figure 2.2 that in the standard configuration the
ALI is usually only found in one IOG 11 side - Node A.
In the SP and CP reference packages, four AT devices are predefined in the
initial data:
AT-0 normal AT for use when SPG has been started
•
AT-1 the alarm interface ALI
•
AT-4 normal AT for use once the IOG has been started
•
(maintenance)
AT-5 as AT-4 (or ALI in node if this exists)
•
If more AT devices are needed they have to be defined by commands and
new hardware has to be installed if necessary. Connecting new AT devices
is covered in the course LZU 108 1452, AXE 10 Operation Handling.
10 03802-EN/LZM 11 2 19 R1A
IO System Basic
Hard Disk (HD)
is a mass storage unit type Winchester disk drive consis-
ting of a number of rapidly rotating disks with magnetic surfaces.
The number of disks per drive varies between the different IOG 11
variants leading to different storage capacities, as given below.
Per Hard Disk (HD):
Unformatted Formatted
IOG 11B/B5, IOG 11C/C5 382 Mb 300 Mb
1.27 Gb 1.05 Gb
The HD units are used to store a backup of the SP programs and data, a
backup of the CP software, Command Log and Transaction Log functions,
charging output data and statistical data.
With regard to the hard disks, it should be noted that the CP is always
loaded or reloaded from a HD unit.
Floppy Disk (FD)
is a mass storage unit for replacable diskettes. The dis-
kette size is 5 1/4” and storage capacity is 1.2 Mb when formatted.
Diskettes are used as moveable media. Examples of their use are the loa-
ding of SP software at initial start of IOG 11 and the loading of command
files.
The CP reference dump can also be copied to hard disk from diskettes
prior to initial loading of the CP. However, magnet ic tape is normally more
convenient for this due to the large number of diskettes otherwise required.
Magnetic Tape (MT)
can be used for certain applications where a move-
able medium that can store large amounts of data is required.
It is normally used at initial loading of the CP reference when the
exchange is started for the first time. The reference is c opied from the ta pe
to hard disk before loading. Backups of the CP software can also be stored
on magnetic tape (max 55 Mb). The required backup file on hard disk must
be copied to the tape for this purpose.
MT (max 35 Mb) is also used as a storage for charging data such as toll
ticketing output. The data is first output to hard disk and then transferred
to tape.
MT can also be used as a manual backup function for a data link during
transfer of charging data, or for storing charging data from Operator
Subsystem (OPS) which is first output to HD and then transferred to tape
or data link.
Optical Disk (OD)
(the complete name is Optomagnetic Disk) is a massstorage unit for replaceable disks. The storage capacity of the 5 1/4” disk is
2x297 Mb, when formatted and 2x325 Mb when unformatted.
The OD is readable, writable and rewritable. Writing and rewriting is
realized by using the magnetic material on the disk.
The OD is an optional medium used for backups of reloading data and is
an alternative to MT for large data store sizes.
11 03802-EN/LZM 11 2 19 R1A
IO System Basic
The handling of the OD is im portant, therefore the Operational Instruction
should always be followed.
Data Links (DL)
can be used for the connection of remote terminals at an
OMC, and for the transmission of data - e.g charging output or statistics to a processing centre.
2.3 Subsystems in IOG11
The following subsystems belong to IOG 11:
SPS
•
MCS
•
FMS
•
DCS
•
The hardware of each subsystem is shown in figure 2.6.
Support Processor Subsystem
Man-machine Communication Subsystem
File Management Subsystem
Data Communication Subsystem
CP
RPA
SPS
AT
SP
HD
FD
MCS
AT
OD
ALI
MT
DCS
DL
Figure 2.6.
The subsystems of IOG 11
2.3.1 Support Processor Subsystem (SPS)
General
ICB
FMS
SPS implements the program control of the Support Processor, the SP-CP
communication function and maintenance functions for the SP and RPA.
12 03802-EN/LZM 11 2 19 R1A
IO System Basic
SPS consists of the following components:
the Support Processors (SPs) with their operating system
•
the Regional Processor bus Adapters (RPAs)
•
software for communication between CP and SP
•
software for operation and maintenance functions for the SPG.
•
SPS interworks with the following subsystems:
Central Processor Subsystem (CPS)
•
Regional Processor Subsystem (RPS)
•
MCS, FMS, DCS
•
Several APT subsystems, for example Statistics and Traffic Measure-
•
ment Subsystem (STS) and Remote Measurement Subsystem (RMS).
(These two subsystems have their software loaded into the SP.)
The SP is an Ericsson designed real time computer called
based on the Motorola M68000 family.
At loading or reloading of an SP, a PROM-stored bootstrap is used to
initiate loading of the SP operating system and software into the primary
memory of the SP from the hard disk. During start up of IOG 11 the software is first transferred to the hard disk from a number of diskettes.
The RPA is the interface unit between the RP bus and the SP, see figure
2.7. It transfers and receives messages to and from the CP.
CP
APN 167
RPB-A
RPB-B
. It is
RPA
SP
ICB
BNA
Figure 2.7
The hardware of SPS
RPA works as a Slave to the SP which has the Master functions.
It consists basically of a microprocessor with its own operating system and
software stored in a PROM memory.
The hardware of SPS is the SP and RPA magazines.
13 03802-EN/LZM 11 2 19 R1A
IO System Basic
Bus Network Adapter (BNA)
The
The Software of SPS
The SPS software is situated in the CP, SP and RPA.
In the SP the function blocks of all the subsystems are divided into units
called
called EriPascal.
As mentioned above, the SPS contains the operating system of the SP and
software for handling both CP-SP communication and maintenance of the
nodes and links and a number of SPS operation functions.
CP-SP communication is looked at very briefly below, whereas maintenance functions will be looked at briefly in chapter 3.3 Status of IOG 11
Units.
CP-SP Communication
Communication between the RPA and the CP is in accordance with the
OSI Model for data communication. The OSI Model principles lie outside
the scope of this module and will not be covered here.
modules
. The modules are written in a real time, high level language
is the interface to the ICB in each node.
Communication between the RPA and the SP uses Direct Memory Access
(DMA) which allows the SP to read and write directly from and to the
memory of the RPA.
The CP sees each of the RPAs as an RP and chooses either one when
sending signals to a function block in the SP. This depends on the work
being performed by the CP at that moment.
Normally the CP takes the direct path via the RPA in the executive node
side, but can also access this node via the other RPA over the ICB if necessary. A blocked or separated RPA in the executive node are examples of
such a case. The SP would take the same path for communication in the
opposite direction.
2.3.2 Man-machine Communication Subsystem (MCS)
General
MCS supplies the man-machine interface for operation and maintenance.
MCS handles two types of information:
alphanumeric information (commands, printouts)
•
alarm information (internal, external).
•
The subsystem consists mainly of software - mostly in the CP, but also in
the SP - but some hardware does exist:
the alarm interface (ALI)
•
the alarm panel(s).
•
14 03802-EN/LZM 11 2 19 R1A
IO System Basic
MCS interworks with FMS (File Management Subsystem) which provides
storage media for the Transaction Log and for some printouts.
MCS also interworks with SPS and DCS.
This interwork serves three main purposes:
communication between SP and CP for transfer of commands/printouts
•
(SPS)
communication with the terminals (DCS)
•
operation and maintenance of the terminals (DCS).
•
In the above communication the command path is:
SP CP
MCS...............SPS...............SPS...............MCS
The terminal interfaces belong to DCS as will be seen in the section on this
subsystem.
MCS interworks with all command receiving and printout generating
blocks. It also interworks with all program blocks that generate alarms.
The Hardware of MCS
The hardware of MCS consists of the ALI and alarm panels.
The ALI and AT have already been described in chapter 2.2.3 IO Device
Functions and Characteristics. Both the ALI and alarm panel hardware
will be described in chapter 2.4 Hardware Structure.
The ATs - although handled by MCS - do not themselves belong to MCS
(nor any subsystem).
They are physically connected to hardware interfaces belonging to DCS.
15 03802-EN/LZM 11 2 19 R1A
IO System Basic
CP
RPB-A
RPB-B
SP
HD
AT
FD
MCS
AT
OD
ALI
MT
DL
Figure 2.8
ALI and the IO devices handled by MCS
2.3.3 File Management Subsystem (FMS)
General
ICB
FMS incorporates hardware and software for handling the external mass
storage of AXE.
The software of FMS is loaded both in the CP and the SP.
The hardware consists of mass storage Winchester hard disks comple-
mented with the file devices for diskette drives, magnetic tape drives and
optical disk drives, see figure 2.9.
16 03802-EN/LZM 11 2 19 R1A
IO System Basic
CP
RPB-A
RPB-B
Figure 2.9
The hardware of FMS
DL
AT
AT
ALI
SP
ICB
HD-1
HD-2
FD-1
FMS
OD-1
MT-1
FMS interworks with SPS, MCS, DCS and a number of file users in other
different subsystems.
The Hardware of FMS
The hardware of FMS consists of one Mass Storage Magazine (MSM) per
node in IOG 11B. In IOG 11C the single MSM serves both Node A and
Node B.
In IOG 11B5/C5 the FMS hardware includes also the Optical Disk Magazine (ODM), which contains the Optical Disk drive OD-1.
The MSM contains two Hard Disk drives, HD-1 and HD-2, and one
Floppy Disk drive FD-1 in IOG 11B/B5. In IOG 11C/C5 there is one HD
and one FD per node.
In IOG 11B/B5 two extra Hard Disk drives, HD-3 and HD-4, can be added
to each node (only if 300 Mb hard disks).
The hardware also consists of at least one Magnetic Tape Group (MTG 10)
in IOG 11.
The buses connecting the FMS hardware to the SP (SCSI buses) can also
be included.
17 03802-EN/LZM 11 2 19 R1A
IO System Basic
The hardware variants will be covered in chapter 2.4 Hardware Structure.
2.3.4 Data Communication Subsystem (DCS)
General
DCS supplies data communication support for operation and maintenance
applications in AXE 10. DCS is transparent to all data entering or leaving
the IOG via the terminals and data links.
The structure of DCS is based on the OSI model, i.e. a layered structure
for data communication that is in general use today.
It is not necessary to know the principles of the OSI model for normal
operation of IOG 11 and they will not be discussed further here.
DCS resides entirely in the SP, unlike the other three subsystems which
exist in both the CP and SP.
Data from ATs or data links enters the system via DCS functions and is
then transferred to either MCS or FMS within the SP. At start up of
IOG 11, DCS accesses SPS directly.
DCS interworks with SPS, FMS and MCS.
This interwork serves three main purposes:
basic software maintenance of DCS (SPS)
•
storage of DCS dependent data (FMS)
•
operation and maintenance procedures (MCS)
•
DCS offers communication services and provides interfaces to data network users.
It provides network services comparable to a stand-alone
switching
and X.25 networks.
An SP in IOG 11 operates from the DCS point of view as a switch or
Communication Module (CM)
A CM is a logical concept. It defines logically the presence of DCS in the
node (i.e SP). Within an IOG 11 each CM is numbered internally: in
SPG-0, Node A is associated with CM-1, Node B with CM-2. It should be
noted that in SPG-1, Node A is associated with CM-17, Node B with
CM-18 etc.
system, which allows connection to external X.25 equipment
in a packet switched data network.
X.25 packet
To the operation and maintenance engineer the CM concept is only of
importance when designating the hardware interfaces used by DCS. DCS
also provides an alphanumeric terminal interface based on X.28/X.3/X.29
recommendations for the connection of asynchronous terminals to synchronous X.25 equipment.
18 03802-EN/LZM 11 2 19 R1A
IO System Basic
The Hardware of DCS
The hardware is realized in the boards of a Line Unit (LU), the only hardware function block in DCS. The LUs contain the interfaces to the alphanumeric terminals and data links.
2.4 Hardware Structure
2.4.1 Introduction
This chapter will explain the differences between the products that exist
today in the IOG 11 family, i.e.:
IOG 11B-S
•
IOG 11B-L2
•
IOG 11B5-S
•
IOG 11B5-L2
•
IOG 11C
•
IOG 11C5
•
IOG 11A and IOMC will not be explained in detail since they are no
longer supplied.
2.4.2 Different SP-Based IO Systems
IOG 11A
IOG 11A was the first release of the new generation of IO, based on APN
167. It was originally named IOG 11 (without “A”).
IOG 11B/B5
IOG 11B/B5 is a more powerful version of IOG 11A with respect to
processor and disk capacity. These two products can be used with most
types of APZ.
IOG 11B/B5 exists in two configurations. The standard configuration,
IOG 11B/B5-S, is used for system back up, command handling, printouts,
file handling, data link output, CP T commands etc. This is used for SPG-0.
IOG 11B/B5-L2 is a subset of the standard version with the functionality
limited to support charging output or corresponding applications. There
are no terminals or alarm functions connected to this configuration. It is
used together with IOG 11B/B5-S. It has the same hardware as the standard configuration except for the alarm interface boards. It is used for
SPG-1, SPG-2 and SPG-3.
IOG 11C/C5
IOG 11C/C5 is a cost-reduced version of IOG 11B/B5. It is intended to be
used for small and medium sized applications, normally when APZ 211 is
used. It has, compared with IOG 11B/B5, less storage capability and fewer
IO-ports for connection of terminals and data links. It fits in one cabinet.
19 03802-EN/LZM 11 2 19 R1A
IO System Basic
IOMC
IOMC was a single node compact version with products from IOG 11B
and IOG 11C. It was intended to be used with APZ 211 10 for small sized
applications. IOMC consists of one magazine.
All IO equipment is mounted in BYB 202 cabinets.
Figure 2.10 shows the cabinet configuration for IOG 11B.
20 03802-EN/LZM 11 2 19 R1A
IO System Basic
NodeA NodeB
FAN-A FAN-B
MSM-0-A MSM-0-B
SPSM-A SPSM-B
AL
-A
B-
NAM
-A
RPAM
-B
RPAM
RANG
-A
IOEXT-A IOEXT-B
AL
RANG
-B
B-
NAM
-B
*
MSM-1-A MSM-1-B
Note: NoALRANGinIOG11B-L2
Optional,canbeplacedinMTG10
*)
if5shelfcabinetisused.
Figure 2.10
IOG 11B cabinet configuration
*
The IOG 11B cabinet contains the following magazines except for the air
cooling (FAN) on top of the magazine:
MSM Mass Storage Magazine (FD and HD)
•
SPSM Support Processor Subsystem Magazine (APN 167)
•
RPAM RP bus Adapter Magazine
•
ALRANG ALarm RANGing (external alarms)
•
BNAM Bus Network Adapter Magazine (ICB)
•
IOEXT Input Output EXTension (connection of AT, DL and
•
containing the ALI).
Figure 2.11 shows the cabinet configuration for IOG 11B5.
21 03802-EN/LZM 11 2 19 R1A
IO System Basic
NodeA NodeB
FAN-A FAN-B
**
ODM ODM
MSM-A MSM-B
SPSM-A SPSM-B
*
IOEXT-A IOEXT-B
** **
MSM-1-A MSM-1-B
EXRANG
*)
**)
Optional
Note: NoALRANGinIOG11B5-L2
**
Figure 2.11
IOG 11B5 cabinet configuration
The IOG 11B5 cabinet contains the following magazines:
ODM Optical Disk Magazine (OD)
•
MSM Mass Storage Magazine (HD and FD)
•
SPSM Support Processor Subsystem Magazine (APN 167)
•
IOEXT Input Output EXTension (connection of AT, DL and
•
containing the ALI)
EXRANG EXternal RANGing (external alarms).
•
2.4.3 Magnetic Tape Group (MTG 10)
Magnetic Tape units are placed in separate cabinets.
Each SP is capable of handling one MTG 10. Each MTG 10 can consist of
four Magnetic Tape Drives (MTD) but only one is necessary. For security
reasons Ericsson recommend connection of two MTG 10s to an IOG 11,
one to each node.
22 03802-EN/LZM 11 2 19 R1A
IO System Basic
Optional
CDR DRR DRR
(Master) (Slave)
FAN
MTD-0
(MT-1) (MT-2)
MTM
Figure 2.12
MTG 10
FAN FAN FAN
MTD-1 MTD-2 MTD-3
The MTG 10 cabinet contains (see figure 2.12):
DRR
A fan unit
•
The Magnetic Tape Drive (MTD)
•
The Magnetic Tape Magazine (MTM) with a power unit and one inter-
•
face board per MTD, TDA-SC, for connection to the IOG 11 (see figure
2.13).
P
TDA-
O
SC
U
MTM
Figure 2.13
The Magnetic Tape Magazine in MTG 10
23 03802-EN/LZM 11 2 19 R1A
IO System Basic
2.4.4 IOG 11B
IOG 11B consists of two nodes, one in each cabinet. It contains the following magazines:
Mass Storage Magazine (MSM)
MSM (see figure 2.14) consists of two hard disk units, one flexible disk
unit, a single interface for all units in the magazine and two power boards.
The capacity of one hard disk is 300 Mb formatted.
MSA-SC Mass Storage Adapter SCSI (SCSI = Small Computer
System Interface)
FDD Flexible Disk Drive
HDD Hard Disk Drive
POU Power Unit
A Mass Storage Magazine with two extra hard disks (no flexible disk
drive) can be added to the system. This magazine is placed at the bottom
of the cabinet. So, the possible configuration of hard disks in each node is
one, two or four.
If 1.05 Gb hard disks are used, see figure 2.32 for the MSM layout.
Note:
24 03802-EN/LZM 11 2 19 R1A
IO System Basic
01
02
03
04
07
08
09
10
15
16
17
22
MSA-SC
FDD1
HDD2
HDD1
23
24
POU1 +12V
27
28
POU2 +5V
31
Figure 2.14
The Mass Storage Magazine in IOG11B
25 03802-EN/LZM 11 2 19 R1A
Loading...