E
INTERNAL INFORMATION
TEST INSTRUCTION
Uppgjord — Prepared
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
SG/ERA/LZ/STM Ulrika Thorildsson 404 8 007
Godkänd — Approved
Kontr — Checked
1 (85)
Tillhör/referens — File/reference
ERA/LZ/STMC (Jan Brännström)
START UP OF IOG11
Contents
SEIF v1.2,
Page
1
1.1
1.2
INTRODUCTION
Warnings
Concerned Hardware
2
3
3
2
2.1
RANGE OF TEST
Work Flow
4
4
3
CONDITIONS BEFORE STARTING
6
4
TEST TOOLS
7
5
5.1
5.2
5.3
PREPARATIONS
Connections
Strapping
Check of Data
8
8
32
48
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.12
6.13
6.14
METHOD
Power up/down Sequence
Start up of APN (SPS/FMS)
Formatting Hard Disks
Creation of Volumes on Hard Disk
Application Software Preparation
SP System Function Change and Installation
SP System Start, Node A
Preparation of Hardware table
SP System Start, Node B
SP Deblocking and Parallel Update
Check of DCS and MCS data for AT-0
Check of RPA and BEMBES prior to APZ Start
Preparation of files in IOG 11
Backup File Conversion from FD
49
49
50
53
54
56
58
61
64
66
69
71
74
75
76
7
7.1
7.2
7.3
7.4
7.5
HELPFUL HINTS
Exchange Data
Procedures
System Related Information
Common Problems
References
78
78
79
79
83
84
8
REVISION INFORMATION
85
INTERNAL INFORMATION
TEST INSTRUCTION
E
1
2 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
INTRODUCTION
This instruction describes the installation and startup of the IOG11 for
GSM (900, 1800, 1900) applications.
There are several configurations and types of IOG11. The most common in GSM (900, 1800, 1900) applications is IOG11B5 with two
nodes, A and B.
The different types are:
•
•
•
•
IOG11B, CP-3 processor
IOG11B5, CP-5 processor
IOG11C, CP-3 processor with node A and B in the same
cabinet
IOG11C5, CP-5 processor with node A and B in the
same cabinet
IOG11 consists of the hardware for:
•
•
•
•
Support Processor Subsystem (SPS), APN 167, MC
68000/68030
File Management Subsystem (FMS), MSM
Data Channel Subsystem (DCS), IOEXT
Man machine Communication Subsystem (MCS), IOEXT
Volume sizes and names are application dependent and should be
checked before proceeding.
The SP System to be installed is application dependent.
Test of additional IOG equipment:
NE Test of External Alarms for IOG11
Start Up and NE Test of ODD
INTERNAL INFORMATION
TEST INSTRUCTION
E
1.1
3 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Warnings
WARNING
The contents of this document are subject to revision without notice
due to continued progress in methodology, design, and manufacturing. Ericsson shall have no liability for any error or damages of any
kind resulting from the use of this document.
This document is intended to be used when starting up new equipment and should not be used for operating equipment already taken
in to service.
1.2
Concerned Hardware
This test instruction can be used when testing the following HW:
Product No.
Described in
document at:
IOG11B-S/L2
BFE 301 035/1, 2
5.1.2.1
IOG11B5-S
BFE 301 076/1, 2
5.1.2.1
IOG11C-S
BFE 301 039/1
5.1.2.2
IOG11C5-S
BFE 301 077/1
5.1.2.2
MSM
BFD 324 575/2, 4
5.1.7
MSM
BFD 324 575/5
5.1.8
MSM-2
BFD 748 502/4
5.1.9
SPSM-2
BFD 324 592/2
5.1.3
SPSM-5
BFD 748 504/2
5.1.4
SPSM-6
BFD 748 504/3
5.1.5
SPSM-6
BFD 748 504/6
5.1.6
RPAM-2
BFD 322 020/3
5.1.13
BNAM
BFD 321 515/2
5.1.14
IOEX-2
BFD 324 562/5
5.1.10
IOEX-3
BFD 324 562/6
5.1.11
IOEX-4
BFD 748 505/3
5.1.12
INTERNAL INFORMATION
TEST INSTRUCTION
E
2
4 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
RANGE OF TEST
The scope of this test instruction is to test the IOG11 equipment in
the GSM (900, 1800, 1900) application and put it into service to be
able to bring up the other APZ equipment at a later stage.
During the test the internal power distribution, hardware strapping,
connections and alarm presentation is checked.
Test is done by setting up the hardware physically by following the
chapter 5 Preparation in this document and then powering up the IOG
and bringing the system into operation.
Tests are done by means of internal board diagnostics at power on
(supervised by LEDs) and command initiated tests of all IOG11 units.
The IOG11 is started by formatting the hard disks, creating necessary
volumes and files, and introducing the IOGs operation system with
the function change method.
After this test the IOG is operational and ready to be loaded with
more IOG applications if necessary.
These applications are defined in test instructions performed at a later
stage.
2.1
Work Flow
This test instruction should be executed in the following order:
Section
Action
3
Conditions before starting
4
Test Tools
5.1
Connections
5.2
Strapping
6.1
Power up/down Sequence
6.2
Start up of APN (SPS/FMS)
6.3
Formatting Hard Disks
6.4
Creation of Volumes on Hard Disk
6.5
Application Software Preparation
6.6
SP System Function Change and Installation
6.7
SP System Start, Node A
6.8
Preparation of Hardware Table
6.9
SP System Start, Node B
INTERNAL INFORMATION
TEST INSTRUCTION
E
5 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
6.10
SP Deblocking and Parallel Update
6.11
Check of DCS and MCS Data for AT-0
6.12
Check of RPA and BEMBES prior to APZ Start
6.13
Preparation of Files in IOG11
6.14
Backup File Conversion from FD
INTERNAL INFORMATION
TEST INSTRUCTION
E
3
6 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
CONDITIONS BEFORE STARTING
a
Magazines should be mounted and grounded correctly
b
Power in the magazines should be turned OFF
c
RP-bus should be connected to the RPA magazines,
nodes A and B
d
Head protection sheet from the FD-drives should be
removed
e
Power level and polarity should be checked, and
connected to magazines.
Do NOT power on the magazines
INTERNAL INFORMATION
TEST INSTRUCTION
E
4
7 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
TEST TOOLS
•
Diskettes containing:
−
−
−
−
−
Start-up diskettes (small system) STARTSx
IOG11 systems for nodes A and B use
about 9-11 TRANSP disks.
Exchange data diskette, SP_INITD01
(destination volume OMFZLIBORD)
Data diskette with RPLOADFILE,
SP_INITD02 (destination volume PROG_A/
PROG_B)
SP modules for the program volume
PROG_A/PROG_B.
•
Two terminals connected to IOG11 CPU node A and
node B, e.g. PC with FIOL or compatible. Use a NULL
MODEM IO cable from PC to APN local port.
•
Relevant command and printout descriptions, OPI’s
(B-MODULE).
•
Document Guidelines for volume and file definitions in
IOG 11 (TV-93:0025). Can be found in Ericsson DELTA
library EPK-APZ/IO : GENERAL : HANDLING
INTERNAL INFORMATION
TEST INSTRUCTION
E
5
PREPARATIONS
5.1
Connections
5.1.1
Schematic Connection
8 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
The IOG11 consists of a many different magazines and units. The
figure below shows the hardware units and interconnections.
5.1.2
Cabinet Layout
5.1.2.1
IOG11B/IOG11B5
The IOG11B consists of two cabinets. Each cabinet is equipped with
a number of magazines with a fan unit on top for cooling.
The MSM magazine consists of a floppy disk unit, one or two hard
disk units and control boards.
INTERNAL INFORMATION
TEST INSTRUCTION
E
9 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
The SPSM magazine consists of the CPU, memory boards (if CP-3
processor board is used) and interface boards.
A high-capacity CPU board (CP-5) is also available, if this is used,
the three 4MW storage boards are not used, since CPU-5 carries
both the processor and 32MW RAM.
The RPAM magazine contains interface boards towards the RP bus.
The BNAM magazine is equipped with an interface board towards the
ICB. The IOEXT magazine contains boards for data links and terminal
connections. The ALRANG magazine is a connection field for external alarms. The ALI, which is within IOEXT, contains hardware for
external alarm receivers and alarm displays.
EBA-SC is used to extend the SCSI bus control to other magazines.
Usually only one unit is connected to each EBA-SC card. The most
common units are MSM and MTM.
It is also possible to connect an Optical Disk as an alternative to the
Magnetic Tape. These equipment alternatives are in most cases
located in a separate cabinet.
IOG11B5
RPAM, BNAM, SPSM are integrated in SPSM (SPSM-6)
Maximum 2 EBA-SC per node, available only with CPU-5 processor
board.
EXRANG is located as a panel beside IOEXT-A to the left in the
cabinet.
An Optical Disk can be placed in the spare shelf.
INTERNAL INFORMATION
TEST INSTRUCTION
E
10 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Figure 1
Cabinet view of IOG11B-5-S, BFE 301 076/1, 2
Figure 2
Cabinet view of IOG11B5-5-S/L2, BFE 301 092/1, 2
IOG11B
Maximum 3 EBA-SC per node, available only with CPU-3 processor
board.
ALRANG is located as a magazine between RPAM-A and BNAM-A.
INTERNAL INFORMATION
TEST INSTRUCTION
E
Figure 3
5.1.2.2
11 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Cabinet view of IOG11B-S/L2, BFE 301 035/1, 2
IOG11C/IOG11C5
IOG11C is a more compact version of the IO system, with exactly the
same functionality. Both nodes are placed in the same cabinet.
RPAM, BNAM, SPSM are all integrated in SPSM (SPSM-5).
Maximum 2 EBA-SC per node, available with CPU-5 processor board.
ALRANG is located as a panel beside IOEXT to the left in the cabinet.
Fewer Alphanumeric Terminals can be connected (single IOEXT-4
magazine).
INTERNAL INFORMATION
TEST INSTRUCTION
E
Figure 4
5.1.3
12 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Cabinet view of IOG11C (left) and IOG11C5 (right)
Magazine SPSM-2, BFD 324 592/2
Figure 5
Address-plug view of BFD 324 592/2
Figure 6
Cable view of BFD 324 592/2
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 1
13 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Connection information for SPSM-2
Pos
ROF
Name
ROF Number
Strapping
Connections
02
POU 5V
BFB 101 001/
1
-
B*2F, Power Cable
04
POU 12V
137 7017/3
-
B*3F, Power Cable
05
07
09
LMU
137 7761/1
-
A*1F, Front Connector Plate (ROA
119 572/1)
B’1F, In position 05,
Address-plug (RNV 991 03/1)
B’1F, In position 07,
Address-plug (RNV 991 03/33)
B’1F, In position 09,
Address-plug (RNV 991 03/65)
11
CPU
137 5291/1
5.2.6
A*1F, Front Connector Plate (ROA
119 572/1)
B*2F, Strapping plug (RNV 991
712/012) for reset/reload/halt of
CPU
12
B*1F, In node A, Address-plug
(RNV 991 03/2) for setting of node
address
B*1F, In node B, Address-plug
(RNV 991 03/3) for setting of node
address
B*1F, Local terminal connection
13
BNA-I
137 1602/1
5.2.1
A*1F, Cable to BNAM (BUF,
09B*1F)
B*1F, Cable to BNAM (PRO,
11B*1F)
14
EBA-SC
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F, Address-plug (RNV 991 03/
1)
B*1F, Ribbon-bus Cable to MSM
15
BEM-S
137 1564/1
5.2.3
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Cable to BES (IOEXT), See
figure 26
16
BEM-P
137 1563/1
5.2.2
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Cable to BES (IOEXT), See
figure 26
INTERNAL INFORMATION
TEST INSTRUCTION
E
17
BNA-I
137 1602/1
14 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
5.2.1
A*1F, Cable to other node
B*1F, Cable to other node
19
EBA-SC
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F. Address-plug (RNV 991 03/
2)
B*1F, Ribbon-bus Cable to ODM/
MTM
20
EBA-SC
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F, Address-plug (RNV 991 03/
3)
B*1F, Ribbon-bus Cable to ODM/
MTM
5.1.4
Magazine SPSM-5, BFD 748 504/2
Figure 7
Terminator and Address-plug view of BFD 748 504/2
Figure 8
Cable view of BFD 748 504/2
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 2
15 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Connection information for SPSM-5
Pos
ROF
Name
ROF Number
Strapping
Connections
000
008
RPBU
132 017/1
-
A*1F, RP-bus cable
A*1F, In node B, Terminator (RNV
991 245/003)
B*1F, RP-bus cable
B*1F, In node B, Terminator (RNV
991 245/003)
016
RIB
131 912/1
-
A*1F, RP Address-plug (RNV 991
04/x)
A*2F, RP Address-plug (RNV 991
04/x)
024
ROB-2
131 913/2
-
030
TRU-2
131 918/2
-
036
DBH-2
131 917/2
-
042
BUF
137 1718/1
-
B*1F, Cable to 056A*1F
048
PRO
137 1719/4
5.2.13
A*3F, Strapping plug (RNV 991
712/016) for reset of RPA
B*1F, Front Connector Plate (ROA
219 099/1)
056
BNA-I
137 1602/1
5.2.1
A*1F, Cable to 042B*1F
B*1F, Front Connector Plate (ROA
219 099/1)
062
068
074
LMU
137 7761/1
-
A*1F, Front Connector Plate (ROA
119 0304/1)
B*1F, In position 062,
Address-plug (RNV 991 03/65)
B*1F, In position 068,
Address-plug (RNV 991 03/33)
B*1F, In position 074,
Address-plug (RNV 991 03/1)
INTERNAL INFORMATION
TEST INSTRUCTION
E
080
CPU
137 5291/1
16 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
5.2.6
088
B*2F, Strapping plug (RNV 991
712/012) for reset/reload/halt of
CPU
B*1F, Address-plug (RNV 991 03/
73)
B*2F, In node AAddress-plug
(RNV 991 03/2)
B*2F, In node BAddress-plug
(RNV 991 03/3)
B*4F, Cable to connect local
terminal
096
BEM-P
137 1563/1
5.2.2
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Cable to BES (IOEXT). See
figure 26
104
BEM-S
137 1564/1
5.2.3
A*1F, Front Connector Plate (ROA
219 099/1)
B’1F, Cable to BES (IOEXT). See
figure 26
112
EBA-SC
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F, Address-plug (RNV 991 03/
1)
B*1F, Ribbon-bus Cable to MSM
120
BNA-I
137 1602/1
5.2.1
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Front Connector Plate (ROA
219 099/1)
128
BNA-L
137 1604/1
-
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Front Connector Plate (ROA
219 099/1)
136
STRAP
197 1096/1
-
A*1F, Terminator (RNV 991 245/
011)
B*1F, Terminator (RNV 991 245/
011)
B*1F, In node A, Terminator (RNV
991 148/007)
INTERNAL INFORMATION
TEST INSTRUCTION
E
144
EBA-SC
17 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F. Address-plug (RNV 991 03/
2)
B*1F, Ribbon-bus Cable to ODM/
MTM
5.1.5
162
POU 5V
BFB 101 001/
1
-
B*2F, Power Cable
178
POU
137 7017/3
-
B*3F, Power Cable
Magazine SPSM-6, BFD 748 504/3
Figure 9
Terminator and Address-plug view of BFD 748 504/3
Figure 10
Table 3
Cable view of BFD 748 504/3
Connection information for BFD 748 504/3
Pos
ROF
Name
ROF Number
Strapping
Connections
000
RPBU
132 017/1
-
A*1F, RP-bus (A-bus)
A*1F, Terminator (RNV 991 245/
003), Only Node B
B*1F, RP-bus (A-bus)
B*1F, Terminator (RNV 991 245/
003), Only Node B
INTERNAL INFORMATION
TEST INSTRUCTION
E
008
RPBU
132 017/1
18 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
-
A*1F, RP-bus (B-bus)
A*1F, Terminator (RNV 991 245/
003), Only Node B
B*1F, RP-bus (B-bus)
B*1F, Terminator (RNV 991 245/
003), Only Node B
016
RIB
131 912/1
-
A*1F, RP Address-plug (RNV 991
04/x)
A*2F, RP Address-plug (RNV 991
04/x)
024
ROB-2
131 913/2
-
030
TRU-2
131 918/2
-
036
DBH-2
131 917/2
-
042
BUF
137 1718/1
-
B*1F, Cable to 056A*1F
048
PRO
137 1719/4
5.2.13
A*3F, Strapping plug (RNV 991
712/016) for reset of RPA
B*1F, Front Connector Plate (ROA
219 099/1)
056
BNA-I
137 1602/1
5.2.1
A*1F, Cable to 042B*1F
B*1F, Front Connector Plate (ROA
219 099/1)
080
CP5
137 7936/1
5.2.4
A*3F, Strapping plug (RNV 991
712/012) for reset/reload/halt of
CPU
A*4F, Local terminal connection
096
BEM-P
137 1563/1
5.2.2
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Cable to BES (IOEXT). See
figure 26
104
BEM-S
137 1564/1
5.2.3
A*1F, Front Connector Plate (ROA
219 099/1)
B’1F, Cable to BES (IOEXT). See
figure 26
112
EBA-SC
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F, Address-plug (RNV 991 03/
1)
B*1F, Ribbon-bus Cable to MSM
120
BNA-I
137 1602/1
5.2.1
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Front Connector Plate (ROA
219 099/1)
INTERNAL INFORMATION
TEST INSTRUCTION
E
128
BNA-L
19 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
137 1604/1
-
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Front Connector Plate (ROA
219 099/1)
136
STRAP
197 1096/1
-
A*1F, In node B, Terminator (RNV
991 245/011)
B*1F, In node A, Terminator (RNV
991 245/011)
B*1F, In node A, Terminator (RNV
991 148/007)
144
EBA-SC
137 7741/1
5.2.7
A*1F, Address-plug (RNV 991 03/
238)
A*2F. Address-plug (RNV 991 03/
2)
B*1F, Ribbon-bus Cable to ODM/
MTM
5.1.6
162
POU 5V
BFB 101 001/
1
-
B*2F, Power Cable
178
POU
137 7017/3
-
B*3F, Power Cable
Magazine SPSM-6, BFD 748 504/6
Figure 11
Terminator and Address-plug view of BFD 748 504/6
Figure 12
Cable view of BFD 748 504/6
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 4
20 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Connection information for BFD 748 504/6
Pos
ROF
Name
ROF Number
Strapping
Connections
000
RPBU
132 017/1
-
A*1F, RP-bus (A-bus)
A*1F, Terminator (RNV 991 245/
003), Only Node B
B*1F, RP-bus (A-bus)
B*1F, Terminator (RNV 991 245/
003), Only Node B
008
RPBU
132 017/1
-
A*1F, RP-bus (B-bus)
A*1F, Terminator (RNV 991 245/
003), Only Node B
B*1F, RP-bus (B-bus)
B*1F, Terminator (RNV 991 245/
003), Only Node B
016
RIB
131 912/1
-
A*1F, RP Address-plug (RNV 991
04/x)
A*2F, RP Address-plug (RNV 991
04/x)
024
ROB-2
131 913/2
-
030
TRU-2
131 918/2
-
036
DBH-2
131 917/2
-
042
BUF
137 1718/1
-
B*1F, Cable to 056A*1F
048
PRO
137 1719/4
5.2.13
A*3F, Strapping plug (RNV 991
712/016) for reset of RPA
B*1F, Front Connector Plate (ROA
219 099/1)
056
BNA-I
137 1602/1
5.2.1
A*1F, Cable to 042B*1F
B*1F, Front Connector Plate (ROA
219 099/1)
080
CP5 or
CP5-R
137 7936/1 or
137 8427/1
5.2.45.2.5 A*3F, Strapping plug (RNV 991
712/012) for reset/reload/halt of
CPU
A*4F, Local terminal connection
B*3F, Local terminal connection,
Only CP5-R (ROF 137 8427/1).
096
BEM-P
137 1563/1
5.2.2
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Cable to BES (IOEXT). See
figure 26
INTERNAL INFORMATION
TEST INSTRUCTION
E
104
BEM-S
21 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
137 1564/1
5.2.3
A*1F, Front Connector Plate (ROA
219 099/1)
B’1F, Cable to BES (IOEXT). See
figure 26
112
EBA-SC
137 8407/1
5.2.8
A*1F, Address-plug (RNV 991 03/
238)
A*2F, Address-plug (RNV 991 03/
1)
A*3F, Cable to FIF (MSM)
B*1F, Ribbon-bus Cable to MSM
120
BNA-I
137 1602/1
5.2.1
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Front Connector Plate (ROA
219 099/1)
128
BNA-L
137 1604/1
-
A*1F, Front Connector Plate (ROA
219 099/1)
B*1F, Front Connector Plate (ROA
219 099/1)
136
STRAP
197 1096/1
-
A*1F, In node B, Terminator (RNV
991 245/011)
B*1F, In node A, Terminator (RNV
991 245/011)
B*1F, In node A, Terminator (RNV
991 148/007)
144
EBA-SC
137 8407/1
5.2.8
A*1F, Address-plug (RNV 991 03/
238)
A*2F. Address-plug (RNV 991 03/
2)
B*1F, Ribbon-bus Cable to ODM/
MTM
162
POU 5V
BFB 101 001/
1
-
B*2F, Power Cable
178
POU
137 7017/3
-
B*3F, Power Cable
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.1.7
22 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Magazine MSM, BFD 324 575/2, 4
Figure 13
Terminator view of BFD 324 575/2
Figure 14
Cable view of BFD 324 575/2
This magazine exists in different versions and the index gives you the
following meaning:
Index
Information
/2
Fully equipped magazine
/4
Magazine not equipped with HD and FD
Also different revision state is equipped with different combinations of
HDs and FDs, see 5.2.12 for Harddisk versions. Two variants of FD
exist, 5,25” (ROD 907 04) and 3,5” (ROF 131 8206/1).
Table 5
Connection information for BFD 324 575/2, 4
Pos
ROF
Name
ROF Number
Strapping
Connections
1
BIC
137 7901/1
5.2.10
A*1F, SCSI-bus Cable from
SPSM
B*1F, SCSI-bus to MSA-SC
2
MSA-SC
137 1802/1
5.2.9
A*1F, Terminator (RNV 991 301/
001)
B*1F, SCSI-bus from BIC
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.1.8
23 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
4
FDD
ROD 907 04
or ROF 131
8206/1
-
10
17
SCSI-HD
137 7942/2, 4,
6
5.2.12
25
POU
+12V
BFB 101 001/3
-
B*3F, Power Cable
29
POU +5V
BFB 101 001/1
-
B*3F, Power Cable
Magazine MSM, BFD 324 575/5
Figure 15
Terminator view of BFD 324 575/5
Figure 16
Cable view of BFD 324 575/5
Different revision state is equipped with different combinations of HDs
and FDs, see 5.2.12 for Harddisk versions. Two variants of FD exist,
5,25” (ROD 907 04) and 3,5” (ROF 131 8206/1).
Table 6
Connection information for BFD 324 575/5
Pos
ROF Name
ROF Number
Strapping
Connections
1
BIC
137 7901/1
5.2.10
A*1F, SCSI-bus Cable from
SPSM
B*1F, Terminator (RNV 991 950/
1)
2
FIF
137 8414/1
5.2.11
B*1F, Cable from EBA-SC
(SPSM)
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.1.9
24 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
4
FDD
ROD 907 04
or ROF 131
8206/1
-
8
POULOAD
ROF 137
8423/1
-
17
SCSI-HD
137 7942/2,
4, 6, 8
5.2.12
25
POU +12V
BFB 101 001/
3
-
B*3F, Power Cable
29
POU +5V
BFB 101 001/
1
-
B*3F, Power Cable
Magazine MSM-2, BFD 748 502/4
Figure 17
Terminator view of BFD 748 502/4
Figure 18
Cable view of BFD 748 502/4
Also different revision state is equipped with different combinations of
HDs and FDs, see 5.2.12 for Harddisk versions. Two variants of FD
exist, 5,25” (ROD 907 04) and 3,5” (ROF 131 8206/1).
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 7
25 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Connection information for MSM-2
Pos
ROF
Name
ROF Number
Strapping
Connections
000
179
MSA-SC
137 1802/1
5.2.9
A*1F, Terminator (RNV 991 301/
001)
B*1F, SCSI-bus to HD
008
141
SCSI-HD
5.2.12
137 7942/1,3,
5, 7
A*1F, SCSI-bus cable from
SPSM
B*1F, SCSI-bus cable to MSA-SC
5.1.10
046
118
FDD
ROD 907 04
or ROF 131
8206/1
-
069
109
DC/DC
137 0614/1
-
B*4F, Power Cable
077
093
POU
131 991/2
-
B*2F, Power Cable
Magazine IOEXT-2, BFD 324 562/5
Figure 19
Table 8
Cable view of BFD 324 562/5
Connection information for IOEXT-2
Pos
ROF
Name
ROF Number
Strapping Connections
2
POU
BFB 101 001/
1
-
B*2F, Power Cable
4
POU
137 7017/3
-
B*3F, Power Cable
5
BES
137 1565/1
-
A*1F, Cable to SPSM (BES)
B*1F, Cable to SPSM (BEM)
06
09
12
15
RPU
137 5251/1
-
INTERNAL INFORMATION
TEST INSTRUCTION
E
07
08
10
11
13
14
16
17
LIU1
18
ALAMP
137 5252/1
26 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
-
A*1F, Cable to AT
A*2F, Cable to AT
A*3F, Cable to AT
A*4F, Cable to AT
137 7546/3
5.2.14
A*2F, Cable to EXRANG (0-7) pos
04 or ALRANG 01B*1
A*3F, Cable to main alarm panel
B*1F, Attind. cable
B*2F, Cable to AT-1, pos 07A*2
B*3F, Internal bus Cable
19
ALADIN
137 7547/1
-
A*1F, Cable to small alarm panel
A*3F, Cable to second alarm panel
B*1F, Cable to second small alarm
panel
B*3F, Internal bus Cable
20
ALEX
137 7548/1
-
A*1F, Cable to EXRANG pos 08 or
ALRANG pos 01A*1
B*3F, Internal bus Cable
21
SCAN
137 7549/1
-
A*1F, Cable to SCAN alarms
B*3F, Internal bus Cable
23
5.1.11
APT
SPGA
131 049/1
-
A*3F, Power Cable
A*4F, Power Cable
Magazine IOEXT-3, BFD 324 562/6
Figure 20
Cable view of BFD 324 562/6
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 9
27 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Connection information for IOEXT-3
Pos
ROF
Name
ROF
Number
Strapping
Connections
02
POU
BFB 101
001/1
-
B*2F, Power Cable
04
POU
137 7017/3
-
B*3F, Power Cable
05
BES
137 1565/1
-
A*1F, Cable to SPSM (BES), See
figure 26
B*1F, Cable to SPSM (BEM), See
figure 26
5.1.12
06
09
12
15
RPU
137 5251/1
-
07
10
13
LIU4
137 5252/2
-
15
18
21
LIATTL
137 5259/1
-
16
19
22
ADAP
131 4290/1
-
A*1F, Data link cable
A*3F, Data link cable
B*4F, Cable to PCD-D (G.703)
Magazine IOEXT-4, BFD 324 562/3
Figure 21
Table 10
Cable view of BFD 324 562/3
Connection information for IOEXT-4
Pos
ROF
Name
ROF Number
Strapping Connections
000
170
LLO
131 991/1
-
B*2F, Power Cable
016
162
DC/DC
137 7017/3
-
B*3F, Power Cable
INTERNAL INFORMATION
TEST INSTRUCTION
E
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
024
106
BES
030
050
064
112
132
146
RPU
137 5251/1
-
038
044
058
072
080
120
126
140
LIU1
137 5252/1
-
088
ALAMP
137 1565/1
28 (85)
Datum — Date
-
A*1F, Cable to SPSM (BES)
B*1F, Cable to SPSM (BEM)
A*1F, Cable to AT
A*2F, Cable to AT
A*3F, Cable to AT
A*4F, Cable to AT
137 7546/4
5.2.14
A*2F, Cable to EXRANG (0-7) pos
04 or ALRANG 01B*1
A*3F, Cable to main alarm panel
B*1F, Attind. cable
B*2F, Cable to AT-1, pos 07A*2
B*3F, Internal bus Cable
094
ALEX
137 7548/1
-
A*1F, Cable to EXRANG pos 08 or
ALRANG pos 01A*1
B*3F, Internal bus Cable
5.1.13
Magazine RPAM-2, BFD 322 020/3
Figure 22
Terminator and Address-plug view of BFD 322 020/3
INTERNAL INFORMATION
TEST INSTRUCTION
E
Figure 23
Table 11
29 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Cable view of BFD 322 020/3
Connection information for RPAM-2
Pos
ROF
Name
ROF Number
Strapping
Connections
01
POU
137 0964/1
-
B*2F, Power Cable
03
04
RPBU-A
132 017/1
-
A*1F, RP-bus cable
A*1F, In node B, Terminator (RNV
991 245/003)
B*1F, RP-bus cable
B*1F, In node B, Terminator (RNV
991 245/003)
05
RIB
131 912/1
-
A*1F, RPA Address-plug (RNV
991 04/x)
A*2F, RPA Address-plug (RNV
991 04/x)
06
ROB-2
131 913/2
-
07
TRU-2
131 918/2
-
08
DBH-2
131 917/2
-
09
BUF
137 1718/1
-
B*1F, Cable to SPSM (BNA-I,
13A*1F)
11
PRO
137 1719/4
5.2.13
A*3F, Strapping plug (RNV 991
712/016) for reset of RPA
B*1F, Cable to SPSM (BNA-I,
13B*1F)
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.1.14
30 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Magazine BNAM, BFD 321 515/2
Figure 24
Terminator view of BFD 321 515/2
Figure 25
Cable view of BFD 321 515/2
Table 12
Connection information for BNAM
Pos
ROF
Name
ROF Number
Strapping
Connections
01
POU
137 0963/1
-
B*2F, Power Cable
03
BNA-L
137 1604/1
-
A*1F, Cable to 17A*1F (SPSM)
B*1F, Cable to 17B*1F (SPSM)
04
A*1F, In node A, Cable to node B
pos 04B*1F (BNAM)
A*1F, In node B, Terminator (RNV
991 245/011)
B*1F, In node B, Cable to node A
pos 04A*1F (BNAM)
B*1F, In node A, Terminator (RNV
991 245/011)
B*1F, In node A, Terminator (RNV
991 148/007)
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.1.15
31 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
BEM-BES Cross connection
The BEM-BES is a cross-connection device which allows either node
in a pair to control equipment connected to either of the IOEXT
magazines.
It should be noted that this is only part of the IOG that will not raise an
automatic alarm if it goes faulty, so it should be checked thoroughly.
Figure 26
SPSM and IOEXT cross-connection
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2
Strapping
5.2.1
BNAI, ROF 137 1602/1
Figure 27
32 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Strapping view of ROF 137 1602/1
There are two BNAI-boards, they should be strapped as follows:
A strapped
B strapped
BNAI-1
no
yes
BNAI-2
yes
yes
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.2
5.2.3
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
BEM-P, ROF 137 1563/1
Figure 28
Strapping view of ROF 137 1563/1
BEM-S, ROF 137 1564/1
Figure 29
33 (85)
Datum — Date
Strapping view of ROF 137 1564/1
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.4
34 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
CP5, ROF 137 7936/1
Figure 30
Strapping view of ROF 137 7936/1
Setting of Node address
The Node address is set by two rotary switches (SW1 and SW2):
Table 13
Setting of SW1 and SW2
Node
SPG
Node
Addr.
SW1
SW2
A
0
1
0
1
1
17
1
1
0
2
0
2
1
18
1
2
B
Battery Strap
Strapping B6 and B7 should be set in their UPPER position, the
factory setting is done to prevent discharging the battery.
Restart/Reload
The reset button is used to manually initiate restart or reload.
Note
See section “Use of the Reset Button” before using the
manual restart/reload buttons.
INTERNAL INFORMATION
TEST INSTRUCTION
E
35 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
WARNING The UPPER button on the reset-plug and the ABORT
switch are PROCESSOR HALT buttons. Never use these unless
specifically told so by an instruction.
To initiate a restart
•
•
Flick Reset switch ONCE, or
Press the LOWER button on Reset Plug ONCE
To initiate a reload
•
•
5.2.5
Flick Reset switch TWICE, or
Press the LOWER button on Reset Plug TWICE
CP5-R, ROF 137 8427/1
Figure 31
Strapping view of ROF 137 8427/1
Setting of Node address
The Node address is set by two rotary switches (SW1 and SW2):
Table 14
Setting of SW1 and SW2
Node
SPG
Node
Addr.
SW1
SW2
A
0
1
0
1
1
17
1
1
INTERNAL INFORMATION
TEST INSTRUCTION
E
B
36 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
0
2
0
2
1
18
1
2
Restart/Reload
The reset button is used to manually initiate restart or reload.
Note
See section “Use of the Reset Button” before using the
manual restart/reload buttons.
WARNING The UPPER button on the reset-plug and the ABORT
switch are PROCESSOR HALT buttons. Never use these unless
specifically told so by an instruction.
To>To initiate a restart
•
•
Flick Reset switch ONCE, or
Press the LOWER button on Reset Plug ONCE
To>To initiate a reload
•
•
5.2.6
Flick Reset switch TWICE, or
Press the LOWER button on Reset Plug TWICE
CPU-P, ROF 137 5291/1
Figure 32
Strapping view of ROF 137 5291/1
Restart/Reload
INTERNAL INFORMATION
TEST INSTRUCTION
E
37 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
A Reset-plug (RNV 991 712/012) is placed on position B*2F. The
reset button is used to manually initiate restart or reload.
NOTE: See section “Use of the Reset Button” before using the
manual restart/reload buttons.
Warning: The UPPER button on the reset-plug is PROCESSOR
HALT button. Never use this unless specifically told so by an
instruction.
To>To initiate a restart
•
Press the LOWER button on Reset Plug ONCE
To>To initiate a reload
•
5.2.7
Press the LOWER button on Reset Plug TWICE
EBA-SC, ROF 137 7741/1
Figure 33
Strapping view of ROF 137 7741/1
Straps C, B, A are for setting the SCSI-bus address.
The address-plugs on positions A*1F and A*2F are set differently depending on which equipment this board controls. The setting should
be as follows:
INTERNAL INFORMATION
TEST INSTRUCTION
E
Board
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Address-plug (RNV 991 03/xx)
Cable to:
A*1F
A*2F
EBA-SC-0
238
01
MSM
EBA-SC-1
238
02
MTM/ODM
EBA-SC-2
238
03
MTM/ODM
Table 15
5.2.8
38 (85)
Datum — Date
SCSI address setting
SCSI Switch settings
ID
ID2
ID1
ID0
Used for device type
0
out
out
out
FD, set on MSA-SC
1
out
out
in
HD1
2
out
in
out
HD2
3
out
in
in
4
in
out
out
5
in
out
in
6
in
in
out
7
in
in
in
EBA-SC, ROF 137 8407/1
Figure 34
Strapping view of ROF 137 8407/1
INTERNAL INFORMATION
TEST INSTRUCTION
E
39 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
The switches S1, S2, S3 changes the working mode of the EBA-SC
see table 16
The address-plugs on positions A*1F and A*2F are set differently depending on which equipment this board controls. The setting should
be as follows:
Board
Address-plug (RNV 991 03/xx)
Cable to:
A*1F
A*2F
EBA-SC-0
238
01
MSM
EBA-SC-1
238
02
MTM/ODM
EBA-SC-2
238
03
MTM/ODM
Table 16
Setting of switches on EBA-SC
Switch no:
Pos:
Comment:
On/Off:
S1
1
EBA old mode or
new mode
On = new mode, Off = old
mode
2
Mode
On = 5.1/4", Off = 3.1/2"
3
NC
—
4
NC
—
1
SCSI ID 0
Off
2
SCSI ID 1
Off
3
SCSI ID 2
Off
4
NC
—
1
Disk type 3.1/2" or On = 5.1/4", Off=3.1/2"
5.1/4"
2
NC
—
3
NC
—
4
NC
—
S2
S3
Notes:
NC
=
not connected
new mode
=
EBA-SC in combination with FIF, ROF 137 8414/1
old mode
=
EBA-SC in combination with MSA-SC, ROF 137 1802/2
The LED’s on the front have the following meaning:
INTERNAL INFORMATION
TEST INSTRUCTION
E
LED-1
LED-2
LED-3
LED-4
5.2.9
Yellow
Yellow
Green
Green
40 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
User defined sw controlled
Old/New mode, light=new
FPGA configuration and SW indication OK
Internal +5V OK and no VSCSI shortcut
MSA-SC, ROF 137 1802/1
Figure 35
Strapping view of ROF 137 1802/1
The DIP-switches has the following meaning and default setting (on =
closed = 0).
Switch
no.
Meaning
Setting
1
PROM size (1=32k, 0=64k)
set
2
FDD ready (1=DOOR function,
0=READY function)
set
3
SCSI bus address, LSB
set
4
SCSI bus address
set
5
SCSI bus address, MSB
set
6-8
Not used
Example of SCSI-bus address:
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.10
5
4
3
SCSI id
0
0
0
0
0
0
1
1
0
1
0
2
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
BIC, ROF 137 7901/1
Figure 36
41 (85)
Datum — Date
Strapping view of ROF 137 7901/1
Bus terminator sockets, NO terminators should be fitted in the
positions on the upper half of the circuit board
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.11
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
FIF, ROF 137 8414/1
Figure 37
Strapping view of ROF 137 8414/1
The six LEDs indicates the following signals:
+5V
Termicon
DS1
DS2
DS3
DS4
Green
Green
Green
Green
Green
Green
42 (85)
Datum — Date
Light
Light
Light
Light
Light
Light
indicates
indicates
indicates
indicates
indicates
indicates
+5V power
termination provided
floppy drive 1 active
floppy drive 2 active
floppy drive 3 active
floppy drive 4 active
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.12
43 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
SCSI-HD-B, ROF 137 7942/1-8
Figure 38
Strapping view of ROF 137 7942/2
Figure 39
Strapping view of ROF 137 7942/4, 6
INTERNAL INFORMATION
TEST INSTRUCTION
E
44 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Figure 40
Strapping view of 137 7942/7, 8
Figure 41
Front view of ROF 137 7942/7, 8
This board exists in eight variations shown in table 17 and the SCSI
address must be set according to table 18.
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 17
45 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Variations on ROF 137 7942
ROF no.
IOG
type
HD type
Terminator type
ROF 137 7942/1
IOG11C
1 GB
At top position on board
ROF 137 7942/2
IOG11B
1 GB
Backplane in magazine
ROF 137 7942/3
IOG11C
1 GB
At top position on board
ROF 137 7942/4
IOG11B
1 GB
Backplane in magazine
ROF 137 7942/5
IOG11C
2 GB
At top position on board
ROF 137 7942/6
IOG11B
2 GB
Backplane in magazine
ROF 137 7942/7
IOG11C
2 GB
At top position on board
ROF 137 7942/8
IOG11B
2 GB
Backplane in magazine
Table 18
SCSI address setting
SCSI Switch settings
ID
ID2
ID1
ID0
Used for device type
0
out
out
out
FD, set on MSA-SC
1
out
out
in
HD1
2
out
in
out
HD2
3
out
in
in
4
in
out
out
5
in
out
in
6
in
in
out
7
in
in
in
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.13
46 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
PRO, ROF 137 1719/1
Figure 42
Strapping view of ROF 137 1719/1
A note to the Yellow LED, when there is CP-SP traffic going on the
yellow LED is flashing.
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.2.14
47 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
ALAMP, ROF 137 7546/4
Figure 43
Table 19
Strapping view of ROF 137 7546/4
Setting of Switch 1-8
Switch
Function (1/0)
Std. Setting
1
EXAL 8-32 (included/excluded)
set (1)
2
Distinctive Ringing
not set (0)
3
ALDI 4-15 (included/excluded)
set (1)
4
SCAN 0-15 (included/excluded)
not set (0)
5
Number of data bits (8/7)
not set (0)
6
Number of stop bits (1/2)
set (1)
7
Parity (Odd/Even)
not set (0)
8
Connection type (RP-EM/SP)
not set (0)
9
Baud rate, See table 20
not set (0)
10
Baud rate, See table 20
not set (0)
Table 20
Setting of Switch 1-8
Function
Switch
9
10
Baud rate
0
0
2400
INTERNAL INFORMATION
TEST INSTRUCTION
E
5.3
-
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
0
1
1200
1
0
600
1
1
300
Check of Data
48 (85)
Datum — Date
INTERNAL INFORMATION
TEST INSTRUCTION
E
49 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
6
METHOD
6.1
Power up/down Sequence
All actions listed in 3 CONDITIONS BEFORE STARTING and all of
the previous actions in 5 PREPARATIONS should have been done
before powering up the IOG.
•
•
Connect the cables to the magazines.
Check the fans. All 3 fans in each node should be
working.
The power switches are operated in the following order:
•
Table 21
Power on sequence
POWER ON:
1
A
MSM +5V
2
A
MSM +12V
3
B
MSM +5V
4
B
MSM +12V
5
A
BNAM (master)
6
B
BNAM
7
A
RPAM
8
B
RPAM
9
A
IOEXT +5V
10
A
IOEXT +12V
11
B
IOEXT +5V
12
B
IOEXT +12V
If IOG is equipped with MT or
OD:
Connect: SCSI ribbon cable from
EBA/SC to MTM/ODM.
Power on: MTM +5V (if applicable),
ODM +5V (if applicable), ODM
+12V(if applicable)
NOTE: Do not execute step 13-16 until the instruction says so if
CPU is of type CPU-5
13
A
SPSM +5V
14
A
SPSM +12V
15
B
SPSM +5V
16
B
SPSM +12V
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 22
50 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Power off sequence
POWER OFF:
6.2
NODE:
MAG:
1
SB
SPSM +12V
2
SB
SPSM +5V
3
EX
SPSM +12V
4
EX
SPSM +5V
5
A
MSM +12V
6
A
MSM +5V
7
B
MSM +12V
8
B
MSM +5V
9
A
BNAM +5V
10
B
BNAM +5V
11
A
RPAM +5V
12
B
RPAM +5V
13
A
IOEXT +12V
14
A
IOEXT +5V
15
B
IOEXT +12V
16
B
IOEXT +5V
Start up of APN (SPS/FMS)
The IOG11 is started using the STARTS system, sometimes referred
to as the ’small system’, found on floppy disks.
Differences in volume sizes for different SP applications are described in the document ’GUIDELINES FOR VOLUME AND FILE
DEFINITIONS FOR IOG 11’.
———————————————————————————————
1.
Only if CPU board is of type CP-3, otherwise
continue to step 2 page 51.
When all actions in chapter ’PREPARATIONS’ is finished, mount the diskette ’STARTSxx’ in FD-1 in Node
A.
Connect terminal to CPU local port, pos 12B*4.
INTERNAL INFORMATION
TEST INSTRUCTION
E
51 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
If the message received is garbled then check the baud
rate, parity etc. of the terminal, which should be 4800,
Even parity, 7 data bits, 1 stopbit, then make sure the
correct baud rate is set in the IOG11B (strap RNV 991
03/73 on CPU-P).
If this is all correct, and the same problem occurs in the
other node, then check the null modem cable.
Continue with step 3 page 52.
———————————————————————————————
2.
Only if CPU board is of type CP-5, otherwise
continue to step 3 page 52.
Connect terminal to CPU local port, pos 11A*4.
Check the baud rate, parity etc. of the local terminal,
which should be 4800, Even, 7 data bits, 1 stopbit.
Power on the SPSM magazine, point 13 to 16 in 6.1
’Power up/down Sequence’.
Wait 15-20 seconds for the memory test to finish, then
flip the ’ABORT’ switch on the CPU-board once.
A prompt ’CPUMon>’ will appear.
Command: setup
Parity=Y (Y/N)?
Even/Odd=E (E/O)?
Bits/Char=7 (7/8)?
Stop Bits=1 (2/1)?
Baud Rate=4800?
Test strap On=N (Y/N)?
RPA equipped=N (Y/N)?
NMI allowed=N (Y/N)?
Hardware configuration of port
Hardware configuration of port
Hardware configuration of port
Hardware configuration of port
Do Boot table Change=N (Y/N)?
Program FLASH EPROM=N (Y/N)?
Programming is done!
Y
E
7
1
4800
N
Y
Y
1=232?
2=232?
3=232?
4=232?
N
Y
<enter>
.
.
.
.
.
.
.
.
.
.
.
.
<enter>
Mount the diskette ’STARTSxx’ in FD-1 in Node A.
Enter from the terminal:
CPUMon>RE1
INTERNAL INFORMATION
TEST INSTRUCTION
E
52 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
This will reload from index 1
The text EBBA BOOTSTRAP - EBBA BOOT P3A
BOOTBLOCK READ FROM INDEX 1 will appear.
———————————————————————————————
3.
Only if CPU board is of type CP-3, otherwise
continue to step 4 page 52.
Push the RESET button on the CPU-P board twice and
the loading starts.
If the reset plugs have 2 buttons, use the LOWER one.
Upper button causes a Non Maskable Interrupt, node
stops dead. If UPPER BUTTON is pressed, lower button
must be pressed twice.
Printout: BOOTSTRAP rev
Printout: BOOTBLOCK READ FROM INDEX 01
Printout: SYSTEM <NAME> LOADED
———————————————————————————————
4.
After loading of the first diskette is finished the system
prompts for next STARTS-diskette.
Specify drive for volume STARTSxx
Insert the disk marked ’Startdisk 2, FileLoaded’ and
enter:
Command (if disk in SPG=0 node A): 1::FD-1
Command (if disk in SPG=0 node B): 2::FD-1
Command (if disk in SPG=1 node A): 17::FD-1
Command (if disk in SPG=1 node B): 18::FD-1
The system responds (If Node A, SPG 0):
Mount volume STARTSx on 1::FD-1 and hit return
Hit enter, <CR>, system files are loaded from the
second diskette.
Wait until reload message appears, “System
STARTSxxxx...LIF;1 loaded”
INTERNAL INFORMATION
TEST INSTRUCTION
E
53 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Printout: SP INITIAL SYSTEM RESTARTED
———————————————————————————————
5.
Open the terminal communication by holding the Ctrl
key and pressing E, CTRL <E>
Printout: WELCOME TO ERIOS
———————————————————————————————
6.
Unmount FD.
Command: ISMCT;
Command: ISVOE:IO=FD-1;
Command: END;
———————————————————————————————
7.
Repeat step 1 page 50 to step 6 page 53 for other node.
———————————————————————————————
6.3
Formatting Hard Disks
IOG11B uses hard disk of type KDR 363 02 (1.1 GB storage capacity). The bad sector list is written on the disk, and will be read by
FMS during formatting, so DO NOT specify it in ISMEI.
The allocation of drives in the MSM magazine is opposite to what one
might expect, see the labeling of the MSM magazine.
———————————————————————————————
1.
Check system time and date and change them if necessary. Date is entered in form 19YY-MM-DD and time is
entered in form HHMMSS.
Command: SHOW DATE
Command: SHOW TIME
Command: SET DATE
Command: SET TIME
———————————————————————————————
2.
Start SP initialization mode.
Command: ISMCT;
INTERNAL INFORMATION
TEST INSTRUCTION
E
54 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
3.
Format the HD, e.g. HD-1. Change to TTY mode in
FIOL, DON’T specify bad sectors. They are specified on
the disk.
Wait for the formatting to finish. Progress is reported as
a string of stars (*****.....*********).
This takes about 40 minutes.
Command: ISMEI:IO=HD-1;
Printout: Specify list of unavailable areas Y/N
Command: N
———————————————————————————————
4.
Repeat step 3 page 54 for the other Hard Disks in this
node.
———————————————————————————————
5.
Repeat steps step 1 page 53 to step 4 page 54 for all
other nodes. Connect to the node where the disk is
located.
———————————————————————————————
6.4
Creation of Volumes on Hard Disk
Volume names and sizes depend on the function of the SPG. Note
that the commands listed below are only examples, use appropriate
DT-files for the definitions.
The document GUIDELINES FOR VOLUME AND FILE DEFINITIONS
IN IOG 11 can be used as a guide. If in doubt, contact FSC/ESO for
correct values.
USE UPPER CASE LETTERS WHEN DEFINING VOLUMES
(CAPSLOCK ON).
———————————————————————————————
1.
Create the necessary volumes. Change to BUF mode
(ESC F5) in FIOL.
The file definitions to be loaded should be taken from
the real Data Transcript, for BSC subfile 12100, for SS
subfile 00001. No other DT than the IS-commands can
be loaded.
INTERNAL INFORMATION
TEST INSTRUCTION
E
55 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
In these examples, use:
X=A, dummyname=PROG_A for NODE A
X=B, dummyname=PROG_B for NODE B
Load commands for both nodes from local port, node A.
Command: ISVOI:VOL=dummyname,IO=HD1,NODE=X,REV=1,SIZE=60000,EXPDATE=2020-12-31;
Command:
ISVOC:VOL=dummyname,IO=HD-1,NODE=X,LIMIT=90;
Command: ISVOI:VOL=OMFZLIBORD,IO=HD1,NODE=X,REV=1,SIZE=15000,EXPDATE=2020-12-31;
Command: ISVOC:VOL=OMFZLIBORD,IO=HD1,NODE=X,LIMIT=90;
Command: ISVOI:VOL=RELVOLUMSW,IO=HD1,NODE=X,REV=1,SIZE=500000,EXPDATE=2020-1231;
Command: ISVOC:VOL=RELVOLUMSW,IO=HD1,NODE=X,LIMIT=90;
Command: ISVOI:VOL=EXCHVOLUME,IO=HD1,NODE=X,REV=1,SIZE=456098,EXPDATE=2020-1231;
Command: ISVOC:VOL=EXCHVOLUME,IO=HD1,NODE=X,LIMIT=80;
Command: ISVOI:VOL=CALLVOLUME,IO=HD1,NODE=X,REV=1,SIZE=1000000,EXPDATE=2020-1231;
Command: ISVOC:VOL=CALLVOLUME,IO=HD1,NODE=X,LIMIT=80;
Command: END;
———————————————————————————————
2.
Restart the Node. Wait for response. Answer YES (TTY
mode). Or Push RESET BUTTON once
SPS checks the volumes and changes the volume
index, e.g. OMFZLIBORD01.
Command: RESET
INTERNAL INFORMATION
TEST INSTRUCTION
E
56 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Printout: DO YOU REALLY WANT TO RESTART ??
Command: YES
Printout: SP INITIAL SYSTEM RESTARTED
———————————————————————————————
3.
Repeat step 2 page 55 for node B.
———————————————————————————————
6.5
Application Software Preparation
In FIOL use ESC <F5> to toggle between TTY and BUF modes. If
you are bringing up the nodes together, copy files to BOTH nodes.
If you are bringing up the nodes separately, copy only to the node
you are bringing up.
———————————————————————————————
1.
Start SP initialization mode, CTRL <E>
Command: ISMCT;
———————————————————————————————
2.
Are the OMFZLIBORD and RPLOAD files ( SP_INIT )
available on FD or OD?
FD: Continue with step 3 page 56.
OD: Continue with step 11 page 57.
———————————————————————————————
3.
Insert the diskette ’SP_INITD01’ into FD-1, node A. The
exact name may vary e.g. ’SP_INITD1’.
This disk contains the basic DCS data definitions, plus
AT-0 data.
———————————————————————————————
4.
Copy the application data files to volume OMFZLIBORD
to HD in node A.
Command: SYSBT:IO=FD-1,IONODE=A,EXDATA,
VNODE=A,VOLUME=OMFZLIBORD;
Printout: SP SOFTWARE BACKUP TRANSFER
INTERNAL INFORMATION
TEST INSTRUCTION
E
57 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
5.
Copy the application data files to volume OMFZLIBORD
to HD in node B.
Command: SYSBT:IO=FD-1,IONODE=A,EXDATA,
VNODE=B,VOLUME=OMFZLIBORD;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
6.
Remove the diskette from the FD.
———————————————————————————————
7.
Insert the diskette ’SP_INITD_02’ into FD-1, node A.
The exact name may vary, e.g. ’SP_INITD_2’.
This disk contains the RPU programs that are downloaded to the Line Units at deblocking. e.g. RPLOAD02
will be used by LU’s with CHAR=2.
———————————————————————————————
8.
Copy the RPLOAD file(s) to the volume PROG_A in
node A.
Command: SYSBT:IO=FD-1,
IONODE=A,RPLOAD,VNODE=A;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
9.
Copy the RPLOAD file(s) to the volume PROG_B in
node B.
Command: SYSBT:IO=FD-1,
IONODE=A,RPLOAD,VNODE=B;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
10.
Remove the diskette from the FD.
Continue with step 16 page 58.
———————————————————————————————
11.
Insert the OD in the OD-drive in node A.
INTERNAL INFORMATION
TEST INSTRUCTION
E
58 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
12.
Transfer the RPLOAD files from the OD to the HD in
node A.
Command: SYSBT:IO=OD-1,IONODE=A,
RPLOAD,VNODE=A;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
13.
Transfer the RPLOAD files from the OD to the HD in
node B.
Command: SYSBT:IO=OD-1,IONODE=A,
RPLOAD,VNODE=B;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
14.
Transfer the OMFZLIBORD files from the OD to the HD
in node A.
Command: SYSBT:IO=OD-1,IONODE=A,
EXDATA,VNODE=A,VOLUME=OMFZLIBORD;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
15.
Transfer the OMFZLIBORD files from the OD to the HD
in node B.
Command: SYSBT:IO=OD-1,IONODE=A,
EXDATA,VNODE=B,VOLUME=OMFZLIBORD;
Printout: SP SOFTWARE BACKUP TRANSFER
———————————————————————————————
16.
Terminate SP initialization mode.
Command: END;
———————————————————————————————
6.6
SP System Function Change and Installation
Note
If you are bringing up the nodes individually, then connect to the node in which the function change will be
performed. Confirm commands with a semi-colon.
INTERNAL INFORMATION
TEST INSTRUCTION
E
59 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
1.
Initiate SPG function change.
Command: FCSPI;
———————————————————————————————
2.
Specify the type of function change.
The format for bringing up both nodes together is:
Command:
FCSLS:LNODE=A&B,RNODE=A&B,RSNODE=A&B;
Alternatively, the function change may be performed in
each node independently. For node A, the format is:
Command: FCSLS:LNODE=A,RNODE=B,RSNODE=A;
For node B, the format is:
Command: FCSLS:LNODE=B,RNODE=A,RSNODE=B;
———————————————————————————————
3.
Are the TRANSP files available on FD or OD?
FD: Continue with step 4 page 59.
OD: Continue with step 7 page 60.
———————————————————————————————
4.
Place the TRANSP disk with the highest number into
FD-1, NODE A. For convenience reasons, change to
BUF-mode and copy the SP software to harddisk.
Command: FCSSL:IO=FD-1,IONODE=A;
Printout: SP SOFTWARE LOAD
———————————————————————————————
5.
Repeat item 3 for all other TRANSP disks in descending
order, down to (including) TRANSP_01. This takes 2-3
minutes per diskette.
Leave TRANSP_01 in the drive after all diskettes have
been loaded. TRANSP_01 contains the SYSTEM
DESCRIPTION file.
Note: Sometimes TRANSP_01 only contains the
SYSTEM DESCRIPTION file.
INTERNAL INFORMATION
TEST INSTRUCTION
E
60 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
6.
Copy the system description file onto the hard disk.
Change to TTY-mode again.
Command: FCSDL:IO=FD-1,IONODE=A;
Printout: SP SYSTEM DESCRIPTION LOAD
Continue with step 9 page 60.
———————————————————————————————
7.
Insert the OD in the OD-drive in NODE A and copy the
SP system to the HD.
Command: FCSSL:IO=OD-1,IONODE=A;
Printout: SP SOFTWARE LOAD
———————————————————————————————
8.
Copy the system description file onto the hard disk.
Command: FCSDL:IO=OD-1,IONODE=A;
Printout: SP SYSTEM DESCRIPTION LOAD
———————————————————————————————
9.
Create the system file. Create takes about 5-15 minutes.
Command: FCSSI;
Printout: SP FUNCTION CHANGE
———————————————————————————————
10.
SKIP THIS POINT IF NODES ARE BROUGHT UP
SEPARATELY
Transfer the system to the other nodes by command.
Transfer takes about one hour to complete. Check that
hard disks on both nodes are accessed continually.
Command: FCSST;
Printout: SP SYSTEM TRANSFER
———————————————————————————————
11.
Create the remote installation file. Takes 1-3 minutes.
INTERNAL INFORMATION
TEST INSTRUCTION
E
61 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Command: FCSRI;
Printout: SP REMOTE SYSTEM INSTALLATION
———————————————————————————————
12.
Install the system. Takes 1-3 minutes.
Command: FCSII;
Printout: SP LOCAL SYSTEM INSTALLATION
———————————————————————————————
13.
Leave SP function change mode by command.
Command: FCSPE;
Printout: SP FUNCTION CHANGE DATA
———————————————————————————————
14.
If you are bringing up the nodes separately, repeat step
1 page 59 to step 13 page 61 for the other node.
———————————————————————————————
6.7
SP System Start, Node A
READ THIS
The following assumes that NODE B was not yet started, and should
be dead or running the small system. The aim of this section is to
have NODE A reload the big system from it’s own hard drives, to
check that the BNA is node A is deblocked, and to force NODE A to
become executive, given that NODE B is still running the small
system.
In the event that you wish to do Node B first, then follow this section
using "NODE=B" everywhere it says "NODE=A" and follow the next
section using "NODE=A" whenever it says "NODE B".
———————————————————————————————
1.
Connect the PC or terminal to the CPU port in NODE A
(If SPSM-2 and CP-3: 12*B4, If SPSM-6 and CP-5:
80*A4).
———————————————————————————————
2.
Remove any diskette from FD-1. Press the reset button
twice in NODE A.
INTERNAL INFORMATION
TEST INSTRUCTION
E
62 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
The node will load the "BIG System" from HD. See
’Helpful Hints’ for meaning of INDEX XX
BOOTSTRAP rev
BOOTBLOCK READ FROM INDEX xx
System <NAME> loaded.
Wait a few minutes until disk activity has ceased.
———————————————————————————————
3.
Open communications with NODE A. Use <CR> on
dumb terminals or <F5> in FIOL.
At first, the system may ask for a user and password.
Change to TTY mode (ESC F5).
USERNAME: SYSTEM
PASSWORD: INIT
Printout: WELCOME TO ... 1LZY217........
———————————————————————————————
4.
Check the date and time
Command: DATEP;
Command: TIMEP;
Change if necessary. Change is done so that if it is necessary to print the SP alarm log later, a valid time period
may be specified.
Command: DATEI:DATE=YYMMDD;
Command: TIMEI:TIME=HHMMSS;
———————————————————————————————
5.
Connect to SP Maintenance mode. Print the current
node status, if node B is powered off, or there is no contact the status will be unknown for that node (status
printed as ’-’ only).
Command: IMMCT;
Command: IMCSP;
Printout: NODE CONFIGURATION STATUS
INTERNAL INFORMATION
TEST INSTRUCTION
E
63 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
6.
Print the state of the BNA. If the OPMODE is READY or
MODE10 then everything is normal, in case of OPMODE -BLOCKED there is a possible HW fault. See
next action point.
Command: INATP:NODE=A,IO=NA-1;
Printout: IO UNIT ATTRIBUTE
Leave the SP Maintenance mode
Command: END;
———————————————————————————————
7.
If the BNA was not blocked in step 6 page 63 then
continue to 6.8 Preparation of Hardware Table
Otherwise if the BNA was blocked in step 6 page 63
then continue to step 8 page 63.
———————————————————————————————
8.
Manually block the BNA in NODE A.
Command: BLSUI:SPG=0,NODE=A,UNIT=NA-1;
———————————————————————————————
9.
Order a test of the BNA in NODE A. If faulty hardware is
indicated, replace it.
Command:
DISUI:SPG=0,NODE=A,UNIT=NA-1,TEST=3;
Printout: SP UNIT DIAGNOSTIC TEST RESULT
———————————————————————————————
10.
Deblock the BNA.
Command: BLSUE:SPG=0,NODE=A,UNIT=NA-1;
———————————————————————————————
11.
Repeat step 8 page 63 to step 10 page 63 until the BNA
is not blocked.
———————————————————————————————
INTERNAL INFORMATION
TEST INSTRUCTION
E
6.8
64 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Preparation of Hardware table
In this SP generation, all optional hardware connected to the SPG
(HD,OD,FD,MT,RPU,BNA,WSU etc.) is defined in a changeable table.
The SP system is shipped with default hardware defined, and at this
point it is necessary to remove or add any hardware that does not
match the site configuration. Failure to do so will cause SP alarms
and may prevent updating of the SB node.
This table also defines which equipment routine and command
ordered (RESUI) diagnostics will actually test.
See also page 83, for help about configuration of hardware table for
FD.
———————————————————————————————
1.
Print the SP hardware table in NODE A.
This command takes time the first time it is entered,
since the IOG has to build a configuration file on
harddisk.
Command: IMHWP:NODE=A;
Printout: SP HARDWARE DATA
———————————————————————————————
2.
Print the SP hardware table in NODE B.
Command: IMHWP:NODE=B;
Printout: SP HARDWARE DATA
———————————————————————————————
3.
You will most probably find that the hardware printed
doesn’t match your configuration, e.g. the number of
harddisks or harddisk type may differ, optical disk may
be defined instead of magnetic tape and so on.
Make a list of all differences between the list and your
actual hardware configuration for the IOG.
———————————————————————————————
4.
Change the hardware configuration list for both nodes
in the node you are connected to via the local port.
Use the commands IMHWI (initiate missing equipment)
and IMHWR (remove non-existing equipment) until the
INTERNAL INFORMATION
TEST INSTRUCTION
E
65 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
printout given by command IMHWP corresponds to your
actual set of equipment for both nodes.
If IMHWI returns the fault ’UNIT NOT DEFINED’, the
command IMHWL has to be entered first. All commands
are responded with ORDERED. Log off with command
EXIT;
The format for IMHWI, IMHWR and IMHWL is:
Command: IMHWI:NODE=A,UNIT=HD-1 GB;
Command: IMHWR:NODE=A,UNIT=HD-1;
Command: IMHWL:NODE=A,UNIT=HD-1
GB,NAME="DISK_SC",INDEX=1,UFIELD="H11";
Items listed as ’HD-1 GB’ and ’HD-2 GB’ are 1.1 GB
harddisks, other ’HD’ items are for the old 380 MB
Harddisk type.
The system is normally defined as a CP-3 system at delivery, this is loadable the first time, but if CP-5 is used
the following sequence must be loaded, for both nodes:
Command: IMHWC:NODE=node,UNIT=LWSU0,NAME="MEMORY",DESCR="LWSU",
INDEX=1,SPARE="****",UFIELD="32";
Command: IMHWR:NODE=node,UNIT=LWSU-1;
Command: IMHWR:NODE=node,UNIT=LWSU-2;
Command: IMHWC:NODE=node,UNIT=CONFIG1,NAME="CONFIGURATIO",INDEX=1,
SPARE="****",UFIELD="IOGB5";
———————————————————————————————
5.
If the hardware configuration has been changed the new
definition has to be brought into the memory of the
working node by means of a reload:
Command:
SYRSI:SPG=0,NODE=node,RANK=RELOAD;
Wait for the text ’System PROG_X:LZY 216 XXX.SYS
Loaded’ to appear, and then wait another 5 minutes for
the system to recover.
———————————————————————————————
INTERNAL INFORMATION
TEST INSTRUCTION
E
6.9
66 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
SP System Start, Node B
The following assumes that NODE A was already started, and should
be executive. The aim of this section is to have NODE B reload the
big system from its own hard drives, to check that the BNA in node B
is deblocked, and to force NODE B to accept that NODE A (which
was started first) is executive.
———————————————————————————————
1.
Connect the PC or terminal to the CPU port in NODE B
(If SPSM-2 and CP-3: 12*B4, if SPSM-6 and CP-5:
80*A4)
———————————————————————————————
2.
Remove any diskette from FD-1. Press the reset button
twice in NODE B.
The node will load the "BIG System" from HD. See
’Helpful Hints’ for meaning of INDEX xx .
BOOTSTRAP rev
BOOTBLOCK READ FROM INDEX xx
SYSTEM <NAME> LOADED
———————————————————————————————
3.
Wait at least 5 minutes for the system to recover, then
open communications with NODE B. Use <CR> on
dumb terminals or <F5> in FIOL.
At first, the system may ask for a user and password.
Change to TTY mode (ESC F5).
USERNAME: SYSTEM
PASSWORD: INIT
WELCOME TO <1LZY...........>
———————————————————————————————
4.
Connect to SP Maintenance mode.
Command: IMMCT;
Print the current node status.
Command: IMCSP;
INTERNAL INFORMATION
TEST INSTRUCTION
E
67 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Printout: NODE CONFIGURATION STATUS
The status should be: Node A (Normal) and Node B
(Isolated blocked).
If this is the status, then NODE B has communicated
with NODE A via the ICB (BNAM’s) and accepted a
blocked state.
The status could be: Node B (Normal) and Node A
(Isolated blocked).
If this is the status, then NODE B has not communicated
with NODE A via the ICB (BNAM’s) and so assumed an
executive state. This is probably caused by the BNAM
in node B being blocked (In the previous section, SP
Start of NODE A, we deblocked the BNAM in NODE A
and established it as EXECUTIVE).
———————————————————————————————
5.
Print the state of the BNA.
If the OPMODE is READY or MODE10 then everything
is normal, in case of OPMODE -BLOCKED there is a
possible HW fault. See next action point.
Command: INATP:NODE=B,IO=NA-1;
Printout: IO UNIT ATTRIBUTE
Leave the SP Maintenance mode
Command: END;
———————————————————————————————
6.
If the BNA was not blocked in step 5 page 67 then
continue to 6.10 SP Deblocking and Parallel Update
Otherwise if the BNA was blocked in step 5 page 67
then continue to step 7 page 67.
———————————————————————————————
7.
The following step is only executed in the rare situation
that node B’s BNAM is blocked and node B thinks it is
executive, even though node A was brought up first. If
you did not meet the requirements of step 6 you should
not be executing this step. If you get the message
"NODE NOT EXECUTIVE" for BLSUI below, you should
not be executing this step.
INTERNAL INFORMATION
TEST INSTRUCTION
E
68 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Be sure to be connected to NODE B CPU when
executing these steps.
Manually block the BNA in NODE B.
Command: BLSUI:SPG=0,NODE=B,UNIT=NA-1;
Order a test of the BNA in NODE B.
Command:
DISUI:SPG=0,NODE=B,UNIT=NA-1,TEST=3;
Printout: SP UNIT DIAGNOSTIC TEST RESULT
If faulty hardware is indicated, replace it.
Deblock the BNA.
Command: BLSUE:SPG=0,NODE=B,UNIT=NA-1;
———————————————————————————————
8.
Connect to SP Maintenance mode.
Command: IMMCT;
Print the state of the BNA. The OPMODE should not be
BLOCKED.
Command: INATP:NODE=B,IO=NA-1;
Printout: IO UNIT ATTRIBUTE
Leave the SP Maintenance mode.
Command: END;
———————————————————————————————
9.
Now that the BNA is deblocked, NODE B must be
restarted so that it accepts being blocked.
Command: SYRSI:NODE=B,SPG=0,RANK=SMALL;
———————————————————————————————
10.
Connect to SP Maintenance mode. Connect is done
from node B’s CPU.
Command: IMMCT;
Print the current node status.
INTERNAL INFORMATION
TEST INSTRUCTION
E
69 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Command: IMCSP;
The status should be: Node A (Working Normal) and
Node B (Isolated Blocked).
Printout: NODE CONFIGURATION STATUS
———————————————————————————————
6.10
SP Deblocking and Parallel Update
The following assumes that NODE A was started first and is EXECUTIVE, and that NODE B is BLOCKED. Also, it must have been
verified that both BNAM’s are deblocked.
———————————————————————————————
1.
Connect the PC or terminal to the CPU port in NODE A
(If SPSM-2 and CP-3: 12*B4, if SPSM-6 and CP-5:
80*A4).
———————————————————————————————
2.
Open terminal communication <CR>.
e.g. WELCOME TO <1LZY...........>
———————————————————————————————
3.
Print the current node status.
Command: IMMCT;
Command: IMCSP;
Print the state of the BNAM in NODE A.
Command: INATP:NODE=A,IO=NA-1;
Printout: IO UNIT ATTRIBUTE
Print the state of the BNAM in NODE B.
Command: INATP:NODE=B,IO=NA-1;
Printout: IO UNIT ATTRIBUTE
The OPMODE should not be BLOCKED in either case.
End the IMMCT dialogue.
Command: END;
INTERNAL INFORMATION
TEST INSTRUCTION
E
70 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
4.
Deblock NODE B.
Note
BLSNE can only be given from the EX node. If the CP
is already working, it can only be given from an AT
terminal.
NODE B should reload from HD-1, which takes about 5
minutes.
Command: BLSNE:SPG=0,NODE=B;
A terminal in NODE B should see this message. See
helpful hints for meaning of INDEX xx.
BOOTBLOCK READ FROM INDEX xx
System <name> loaded
———————————————————————————————
5.
From a terminal in NODE A, print the node status. Node
B will first make a reload, then go diagnosing and after
about 5 minutes it should go Updating Large.
Command: IMMCT;
Command: IMCSP;
Printout: NODE CONFIGURATION STATUS
———————————————————————————————
6.
Print node status. Check that the value is changing.
Print takes approx. 1 hour 30 minutes. Check it regularly. If the SP package is for APZ Phase 2, the update
will take significantly shorter time.
If the node goes blocked, follow the suggestions in the
section "ACTIONS AT FAILED UPDATE OR NODE
RESTART" in the helpful hints.
Command: IMSIP:NODE=B;
———————————————————————————————
7.
Print the table containing the current node status. Wait
until Node B is updated and “Working Normal”.
Command: IMCSP;
Printout: NODE CONFIGURATION STATUS
INTERNAL INFORMATION
TEST INSTRUCTION
E
71 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
End the IMMCT dialogue.
Command: END;
———————————————————————————————
6.11
Check of DCS and MCS data for AT-0
This section is used to verify that data for AT-0 has been provided on
the Applications Disk Software that was loaded into OMFZLIBORD. It
is a good idea to compare the data with what is specified in the
I-module data transcript.
———————————————————————————————
1.
Try connecting to the AT-0 port.
If you get the message CP NOT OBTAINABLE and can
connect to SP maintenance mode then this section can
be skipped.
Command: MCLOC:USR=SYSTEM,PSW=INIT;
———————————————————————————————
2.
Check that LU=1-1-1 is defined with CHAR=2.
Command: IMLCT:SPG=0;
Command: ILLUP;
Printout: DCS LINE UNIT DATA
If necessary, define and deblock.
Command: ILLUI:LU=1-1-1,CHAR=2;
Command: ILBLE:LU=1-1-1;
If a line unit goes hardware blocked (HB) the are 4
probable causes:
1.
The RPLOAD file corresponding to the CHAR
value used was not copied into the program
volume, e.g. CHAR=2 uses RPLOAD02.
See 6.5 Application Software Preparation.
2.
The wrong type of LIU card is being used.
LIU 1 (ROF 137 5252/1), Normal X28,X25 V24
ports
INTERNAL INFORMATION
TEST INSTRUCTION
E
72 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
LIU 2 (ROF 137 5253/1), HDLC data links (CPT),
G.703 links with LIA-TTL, V.35 links with LIA-V35
LIU 4 (ROF 137 5253/2), V.35 data links/CPT
3.
There is a gap in the RPU hardware, e.g. LU=11-4 cannot function unless the RPU cards for
1-1-1, 1-1-2 and 1-1-3 are present. This is because the backplane connection to the next LU
position is made by the RPU card.
4.
A port that is defined and deblocked on a LIU
card that is not physically present will cause the
line unit to go hardware blocked.
Note: If you get frequent SP restarts with cause = 593x
(where x= 0..9) then there is a high probability that there
is a hardware fault in the BEMP/BEMS/BES/RPU/LIU
hardware. This will cause the executive node to restart.
To determine which BEM-BES-IOEXT has the fault,
block all the line units in each node, one node at a time,
until the fault has been traced.
———————————————————————————————
3.
Check DCS data for NP=1-1-1-1. Check that
NP=1-1-1-1 is defined.
Command: ILNPP:NP=1-1-1-1,ALL;
Printout: DCS PORT DATA
If necessary, define it
Command:
ILSLI:NP=1-1-1-1,RATE=4800,PROT=X28/V24;
Check that NTN=1011101 has been defined with a
priority.
Command: ILACP;
Printout: DCS ACCESS CONTROL
Check that NTN=1015100 has been connected to the
X29 session.
Command: ILSPP;
Printout: DCS SESSION PORT DATA
If necessary, define it.
Command: ILSPI:SP=X29,NTN=1015100;
INTERNAL INFORMATION
TEST INSTRUCTION
E
73 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Check that 1011101 is connected to the B side NTN
1050100.
Command: ILPCP:NTNA=1011101;
Printout: DCS PVC STATUS
If necessary, define it.
Command: ILPCI:NTNA=1011101,NTNB=1015100;
If necessary, deblock NP=1-1-1-1.
Command: ILBLE:NP=1-1-1-1;
———————————————————————————————
4.
Check MCS data for NP=1-1-1-1. Check that AT-0 is
defined to NTN=1011101, NP=1-1-1-1.
Command: MCDVP:NP=1-1-1-1;
Printout: MCS IO DEVICE DATA
———————————————————————————————
5.
Check that NP=1-1-1-1 is connected to NTN=1011101.
Command: ILTEP:NTN=1011101;
Printout: DCS TERMINAL DATA
If necessary, define it.
Command: ILTEI:NTN=1011101,NP=1-1-1-1;
———————————————————————————————
6.
Check that NTN=1011101 is in the USER directory.
Command: MCDCP:DIR=USER;
Printout: MCS USER DIRECTORY
If necessary, define it.
Command:
MCDCI:NAME=T1011101,DIR=USER,AUTH=ABCDEFGH;
———————————————————————————————
7.
Check that NTN=1011101 is in the COMM directory.
INTERNAL INFORMATION
TEST INSTRUCTION
E
74 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Command: MCDCP:DIR=COM;
Printout: MCS COMMUNICATION DIRECTORY
If necessary, define it.
Command:
MCDCI:NAME=T1011101,DIR=COMM,AUTO=YES,
NTN=1011101,QUEUE=YES,SUPRV=NO;
———————————————————————————————
8.
If necessary, deblock them.
Command: MCDBE:DIR=USER,NAME=T1011101;
Command: MCDBE:DIR=COM ,NAME=T1011101;
———————————————————————————————
6.12
Check of RPA and BEMBES prior to APZ Start
The reason for testing the BEMBES connection is that this is the only
unit in the IOG not supervised by alarms. If the unit is faulty no
alarms will be given and no problems noticed until when CP sides are
switched, for instance at Application system change, when there will
be no contact with the CP.
Test of RPA is done because software is transferred to the APZ by
this unit over the RP-bus.
———————————————————————————————
1.
Connect to the CPU port of the Executive Node.
———————————————————————————————
2.
Block the standby node
Command: BLSNI:SPG=spg,NODE=node;
———————————————————————————————
3.
Order a Test of CM-1 i.e. in the blocked node.
Command: DISUI:SPG=0,NODE=A,UNIT=BEMBES1,TEST=1,FORM=LARGE;
Printout: SP UNIT DIAGNOSTIC TEST RESULT
Node A EXECUTIVE ==> SEL1,SEL2 = ACTIVE
Node A STANDBY ==> SEL1,SEL2 = PASSIVE
INTERNAL INFORMATION
TEST INSTRUCTION
E
75 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
———————————————————————————————
4.
Order a test of the RPA in the blocked node. If faulty
hardware is indicated, replace it.
Command:
DISUI:SPG=0,NODE=A,UNIT=RPA-1,TEST=2;
Printout: SP UNIT DIAGNOSTIC TEST RESULT
———————————————————————————————
5.
Deblock the previously blocked node from EX side.
Command: BLSNE:SPG=0,NODE=node;
———————————————————————————————
6.
Check the working status, wait until the IOG has
reached parallel state.
Command: IMMCT:SPG=0;
Command: IMCSP;
Command: END;
———————————————————————————————
7.
When the system is in parallel block the executive node
(loss of IO contact might occur) and connect to the CPU
port of the former standby node.
Repeat step 3 page 74 and step 4 page 75 for the
former executive node.
Deblock the node after test and let the system reach
parallel state.
———————————————————————————————
6.13
Preparation of files in IOG 11
In this chapter it is made sure that all files necessary for the basic
functions in the APZ are loaded. The file definitions to be loaded
should be taken from the real Data Transcript.
Note that the following commands are just an example, what is
loaded is dependent on functions and hardware delivered.
———————————————————————————————
INTERNAL INFORMATION
TEST INSTRUCTION
E
1.
76 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Connect to normal AT-port and change to FIOL in
BUF-mode.
———————————————————————————————
2.
Load necessary files from the Data Transcript.
———————————————————————————————
3.
For example DT refer to 7.1 Helpful Hints - Exchange
Data.
Normally more files exists, for example STS files, Charging files, BTS SW files and files for statistic recording or
logging. This is dependent on functions sold. Rest of
files will be loaded at a later stage.
Command: INMCT:SPG=spg;
Command: INFIP:VOL=RELVOLUMSW;
Command: INFIP:FCLASS=DEV;
Command: END;
———————————————————————————————
6.14
Backup File Conversion from FD
This chapter is to be seen as a preparation for start-up of APZ, if CP
dump is available on other data media than diskettes or start-up
of APZ is not to be performed, this section should be skipped. If
CP-dump is available on Magnetic Tape it will be loaded during
execution of Start Up and NE Test of MTG10.
———————————————————————————————
1.
Insert the first CP dump diskette in disk drive, Node A or
B.
———————————————————————————————
2.
Logon to SP local mode.
Command: MCLOC:USR=SYSTEM,PSW=INIT;
———————————————————————————————
3.
Initiate the file conversion session.
Command: SYACI:SPG=0;
———————————————————————————————
INTERNAL INFORMATION
TEST INSTRUCTION
E
4.
77 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Initiate the file conversion. Wait for answer printout.
Command:
SYCFI:FILE=RELFSW2,DIR=IN,IO=FD-no,NODE=node;
Printout: BACKUP INFORMATION FILE CONVERSION
———————————————————————————————
5.
Insert the Floppy Disk requested in printout and start the
file conversion.
Wait for result printout.
Command: SYCFP;
Command: END;
Printout: BACKUP INFORMATION FILE CONVERSION
———————————————————————————————
6.
Connect to dialogue mode.
Command: SYACI:CON;
Remove the loaded floppy from the drive.
———————————————————————————————
7.
If the sequence is not finished repeat fromstep 5 page
77. The sequence should be repeated until "FINISHED"
is indicated in result printout.
———————————————————————————————
8.
End the function for file conversation. Wait for answer
printout. Disconnect the dialogue mode.
Command: SYCFE;
Printout: BACKUP INFORMATION FILE CONVERSION
Command: END;
The file conversion from FD to HD is now ready.
———————————————————————————————
INTERNAL INFORMATION
TEST INSTRUCTION
E
7
HELPFUL HINTS
7.1
Exchange Data
7.1.1
File Definitions
78 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
CP DUMP FILES
INFII:FILE=RELFSW0,VOL=RELVOLUMSW,RLENGTH=2048,SIZE=16,
EXP=64,TYPE=SEQ,FCLASS=CMP;
INFII:FILE=RELFSW1,VOL=RELVOLUMSW,RLENGTH=2048,SIZE=16,
EXP=64,TYPE=SEQ,FCLASS=CMP;
INFII:FILE=RELFSW2,VOL=RELVOLUMSW,RLENGTH=2048,SIZE=16,
EXP=64,TYPE=SEQ,FCLASS=CMP;
COMMAND LOG FILES
INFII:FILE=RELADMPAR,VOL=RELVOLUMSW,RLENGTH=32,SIZE=192,
EXP=32,TYPE=SEQ,FCLASS=CMP;
INFII:FILE=RELCMDHDF,VOL=RELVOLUMSW,RLENGTH=160,SIZE=1000,
EXP=100,TYPE=SEQ,FCLASS=CMP;
DEVICE FILES
INFII:FILE=FD0A1,NODE=A,IO=FD1,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;
INFII:FILE=FD0B1,NODE=B,IO=FD1,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;
INFII:FILE=MT0A1,NODE=A,IO=MT1,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;
INFII:FILE=OD0B1,NODE=B,IO=OD1,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;
INFII:FILE=DL0A1,NODE=A,IO=DL1,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;
INFII:FILE=DL0B1,NODE=B,IO=DL1,RLENGTH=512,SIZE=16,EXP=64,TYPE=SEQ,FCLASS=DEV;
TRANSACTION LOG FILES
INFII:FILE=TRLOGFILE,VOL=EXCHVOLUME,RLENGTH=256,SIZE=100,
EXP=100,TYPE=SEQ,FCLASS=CMP;
INTERNAL INFORMATION
TEST INSTRUCTION
E
79 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
7.2
Procedures
7.2.1
Changes in the Boot Table for CP-5
Sometimes the predefined settings in the boot table of the CP-5
boards are not correct. In this case it is necessary to change the boot
table, i.e. define which units the system should boot from and in
which priority order. This is done by using following procedure:
1.
Perform step 2 page 51 in 6.2 Start-up of
APN(SPS/FMS), except the part about powering up the
SPSM magazine (if it is already powered on).
2.
Give the same answers as stated, except on the question "Do Boot Table Change", where the answer Y
should be given. Next question that appears is "Number
of Boot Indexes", which can be answered with 5, since
only the first couple of positions are of interest.
3.
Make the necessary changes. Normally Position 1 (first
alternative) should be 1 (FD-1), and Position 2 (second
alternative) should be 31 (1,1 GB HD in own node).
4.
When all necessary changes have been made, the
question “Program FLASH EPROM” should be
answered with Y.
7.3
System Related Information
7.3.1
Getting help from the system
To get helpful hints about parameters in SP media initialization mode,
write:
Command: HELP;
To get a list of commands available from the "BIG SYSTEM" write
(while in the Big System):
Command: HELP;
7.3.2
Bootblock read information
When reloading an SP the following message is received "BOOTBLOCK READ FROM INDEX ..." where the index corresponds to the
following source:
INTERNAL INFORMATION
TEST INSTRUCTION
E
Table 23
7.3.3
80 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Bootblock Index
Index
Reloading from source
CP-3
board
CP-5
board
1
FD-1
x
x
22
HD-1 (380 MB)
x
24
HD-1 (1.1 GB)
x
31
HD-1 (1.1GB)
x
Using FILUTIL
Command: FILUTIL;
UTILITYMENUE
FILUTIL.N
0 Backup(physical copying of volume)
Q Quick physical copying
1 Copy (logical copying of volume )
V Backup vol to file
P Copy Volume(result printout per file)
W Restore vol from file
2 Pack Volume
3 Copy File
4 Pack File
5 Volume Catalogue
5S Volume Cat/Short List
6 Call Process (e.g. FILDISUT)
7 Format Medium and Create Volume
8 Delete a File
9 Force Volume Close
S Close a volume
A Create File
I List Volume Contents
B Compare Files
J Selective Delete
C Compare Volumes
K Rename File
D Rename Volume
L To Command mode
E List Medium
M Selective Copy
F Mount Medium
N Purge Files
G Format Medium
O Set def file owner
H Create Volume
R Change vol map
INTERNAL INFORMATION
TEST INSTRUCTION
E
81 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
Z EXIT
enter selection
Filutil is a very powerful utility that enables one to examine the contents of any FMS device e.g. FD, MT, HD. However, it should only be
used when troubleshooting, and should never be used to format hard
disks or create volumes. It should never be used in live sites, and
may generally only be used under the supervision of ESO.
Filutil is menu driven, and the most useful selection is option 5, Volume Catalog, which gives information on volumes and the files
contained within them. The format for specifying volumes is slightly
different to other FMS commands.
i.e. CM::HD(x):file.type
where CM is the CM number of the node in which the disk is found,
HD(x) is the volume, identified by its volume index, x file.type is the
filename.filetype, like a DOS format.
The volume indices for a switch depends on the definition order for
the volumes. On the 1.1 GB HD there can be 16 volumes defined.
PROG_A
OMFZLIBORD01
1::HD(1)
1::HD(2)
PROG_B
OMFZLIBORD02
2::HD(1)
2::HD(2)
EXCHVOLUME01
1::HD(3)
EXCHVOLUME02
2::HD(3)
RELVOLUMSW01
1::HD(4)
RELVOLUMSW02
2::HD(4)
Floppy Drive A
1::FD(1)
Floppy Drive B
2::FD(1)
To look at all the binary files in PROG_A, SPG-0, the format is
1::HD(1):*.BIN or 1::PROG_A:*.BIN
For node B the format would be 2::HD(1):*.BIN or 2::PROG_B:*.BIN
Always close the volumes associated with floppy drives after any
operation on them with OPTION 9 (Force Volume Closed).
In these examples 1::HD(1) is the logical volume corresponding to the
volume name PROG_A, i.e. it is the first volume in the first hard disk.
It does not refer to the physical media, which are specified with a different format. To look at a media, and list the volumes on it, select
option E and specify the media as:
1::HD-1
1::HD-2
2::HD-1
2::HD-2
(HD-1,node
(HD-2,node
(HD-1,node
(HD-2,node
A)
A)
B)
B)
INTERNAL INFORMATION
TEST INSTRUCTION
E
82 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
This gives the same information as the SP initialization commands
ISMEP:IO=HD(1);
Another useful feature is the ability to copy and delete files. Again,
this should only be done under supervision of ESO. To copy files
selectively use OPTION M, e.g.
INPUT VOLUME
OUTPUT VOLUME
Fileowner
1::FD(1):*.DAT
2::HD(2)
0
would copy all the data files on the floppy disk in node A to volume
OMFZLIBORD in node B, but you must know the fileowner.
To delete files selectively use OPTION J, e.g.
INPUT VOLUME
Fileowner or 0.
1::FD(1):*.DAT
0
would delete all the data files on the floppy disk in node A. In this
case, it may be necessary to know the specific file owner.
Finally, it is sometimes useful to redefine a volume or rename a volume. This can be done using option R and then selecting sub-option
R, RENAME. This will destroy the contents of the volume, and should
not be used without direct supervision from Ericsson Support Office.
7.3.4
Use of the Reset Button
The reset button shall never be used except when it is indicated by
an operational instruction. The operational instruction will indicate if it
shall be pressed once or twice.
Manual node restarts and reloads shall be made by the command
SYRSI.
Consequences of the Use
When the reset button is pressed the memory will be cleared and all
active processes will be instantly killed. This implies that there is a
great risk for corrupt files, since most updating in the file tables involve more than one step. Also, write orders to files that were on the
way but had not yet been written on the hard disk will be lost.
When a node restart is ordered by a program or by command SYRSI
the restart will be performed in a softer and more ordered way, via a
function in the File Access System (FAS Shutdown). Then there
should be no risk for lost file data or corrupt files.
Placement and Function of the Reset Button
INTERNAL INFORMATION
TEST INSTRUCTION
E
83 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
The reset button (switch in case of CPU-5) is placed on the CPU
board, magazine SPSM. It is pressed once to initiate a restart and
twice to initiate a restart with reload.
Note that the other button (switch in case of CPU-5) is a HALT button
that will stop the IOG11 completely and is intended only for debugging at test sites. If it has been operated by mistake, the reset button
must be pressed to initiate a restart.
7.3.5
7.3.6
Reinstalling or Reformatting
1
It is important to be aware that IO port data, charging,
STS files and reload files will be destroyed if you reformat the hard drives. Thus you should take a dump to
tape, and copy all the data files in OMFZLIBORD to
floppy disk before starting.
2
Also, sometimes things can go badly wrong when installing a new system, e.g. a bad floppy disc, so do not
format all the hard drives on both nodes at the same
time. Do one node at a time, get it working again, and
then do the other node. This will avoid the situation
which has happened regularly, that people kill both
nodes, run into problems, and cause all other testing to
be delayed until they sort out the mess.
3
If you have a problem with the contents of just one volume, then rather than formatting the entire disk again,
you can just wipe that volume using option R, sub option
R in FILUTIL, as described above. Be aware though,
that the contents are destroyed, and you may have to
re-define port or file data e.g. if AMATVOLUME was
wiped, you would have to redefine the STAR files, if EXCHVOLUME is wiped you would have to reload all other
files and STS data, if OMFZLIBORD is wiped, you must
copy the APPL software again, and then redefine new
all DCS/MCS data. And if the PROG volume is wiped,
the system must be reinstalled. This procedure is only
recommended for start-up phases.
Hardware table for FD
There are two types of floppy drives available, 5,25” and 3,5”.
In the hardware table the parameter UFIELD should be 412M5 for
5,25” and 412M7 for 3,5”.
7.4
Common Problems
7.4.1
Actions at Failed Update or Node Restart
The most common causes of a failed update in an SPG are:
INTERNAL INFORMATION
TEST INSTRUCTION
E
1
84 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
The executive node restarted.
Action: Check the NODE restart data.
2
The standby node restarted.
Action: Check the NODE restart data.
Note: BLSNE always causes a cause 3010 restart in SB
node.
3
Blocking Order received during update.
Action : Print the NODE Alarm Log.
Whenever a node restarts, the restart data and alarm log should be
saved, and copies sent to ESO. To gain such information, use the
following procedure, e.g. for node A.
Command: IMMCT:SPG=0;
Command: IMCSP;
Command: IMRDP:NODE=A,FORM=LARGE;
Printout: NODE RESTART DATA
Note the time of the restart in the restart data, and see if the restart
occurred during the deblocking or update.
Command: IMALP:NODE=A,FRTIME=frtime,FRDATE=frdate;
where frtime = time about 15 minutes before the restart or BLSNE
e.g. 1620 and frdate = the date on which the restart or BLSNE
occurred. e.g. 1992-08-11
When checking the alarm log, look for event types
DUPC ERROR - DUPC indicates a problem with the HD media.
These are suggestions, but not guaranteed:
•
•
•
VOLUME COPY ==> Re-format the EX node.
VOLUME SEARCH==> Re-format the EX node.
SHADOW WRITE ==> Re-format the SB node,perhaps
replace hard disk.
NODE FAULT - NODE indicates a problem with a hardware unit.
7.5
References
-
INTERNAL INFORMATION
TEST INSTRUCTION
E
8
85 (85)
Datum — Date
Rev
Dokumentnr — Document no
1998-10-08
D
23/1532-APZ 212 11 Uen
REVISION INFORMATION
Table 24
Revision information for this test instruction
Rev
Date
Author
Reason
A
97-05-23
ERARBER
Based on 6/1532-APZ 212 11
B
97-12-01
ERAFRSU
Information about new HW
added
C
98-09-03
ERAULTH
Title changed, table 21and 22
updated. Picture for BIC
changed.
D
98-10-08
ERAULTH
Faults corrected