Start Up APZ 212 60 - 2

Ericsson Internal
TEST INSTRUCTIONS 1 (177)

Prepared (also subject responsible if other) No.
UABINGE 104/1532-B/AXE 106 99 Uen

Approved Checked Date Rev Reference
EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F
© Copyright Ericsson AB 2010. All rights reserved.
Factory Start Up and Initial NE Test of a CP

Cluster
Abstract
This document provides the necessary information to perform Factory Node

Test of a CP Cluster (= Blade Cluster).
Factory Node Test is performed at the production line.
Note 1: This document is not intended to be used at customer sites.
Note 2: This document will not cover any project after APZ 16.0.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing. Always check
GASK for latest revision. Ericsson has 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.
Ericsson Internal


Contents
1 Introduction 4
1.1 Concerned Hardware 4
2 Range of Test 5
2.1 Work Flow 6
3 Conditions before Starting 7
4 Tools 7
5 General 8
5.1 CP Blade Differences with Earlier APZ systems 10
5.2 Blade Positions and Information 10
6 Method 11
6.1 Preparation 11
6.1.1 General 11
6.1.2 Power Up 11
6.2 Unlock the CPHW Blade System 11
6.3 Blade Definition in eGEM 13
6.4 Setting CP Identification Values 17
6.5 Installing PES and CPHW Dump Versions 22
6.6 Checking Proxy Boot Configuration 27
6.7 Transferring of CP Dump to APG43 30
6.8 Ping Tests 43
6.8.1 Ping the Two APG43 from the CP Blades 43
6.8.2 Ping the CP Blades from the Two APG43 44
6.9 Boot Starting of the CP Blades 46
6.10 Initial Testing of the CP Blades 52
6.11 Initial Loading of the CP Blades 55
6.12 Definition of AP2 59
6.13 Definition of Routing Tables for IPonCP for VLAN INT-SIG 61
6.13.1 General 61
6.13.2 SPX1 61
6.13.3 SPX2 62
6.13.4 CP Blades 63
6.14 Definition of Routing Tables for IPonCP for SIG-1 and SIG-2 65
6.14.1 Configuration Layout 65
6.14.2 SPX1 and SPX2 65
6.14.3 TSC Blades 85
6.15 Definition of Routing Tables for IPonCP for BC-SIG 90
6.15.2 SPX1 and SPX2 91
6.16 Definition of Routing Tables for IPonCP for BC-SIG-EXT1 107
6.16.1 SPX1 and SPX2 107
6.17 Definition of Routing Tables for IPonCP for BC-SIG-EXT2 123
6.17.1 SPX1 and SPX2 123
6.18 Definition of Routing Tables for IPonCP for BC-SIP 139
6.18.2 MSC Blades 140
6.19 Definition of Routing Tables for IPonCP for BC-DNS 142
Ericsson Internal


6.20 Definition of Routing Tables for IPonCP for BC-BLD-EXT1 146
6.21 Perform System Backup Copies 148
7 HELPFUL HINTS 150
7.1 Information Displayed by a CDU 150
7.1.1 Left-Most Digit, Encoding 150
7.1.2 Numerical Value, Intervals 151
7.1.3 Numerical Values, during Loading of CP 151
7.1.4 Numerical Values, during remote Upgrade of Firmware 152
7.1.5 Numerical Values, when a Fault is detected during CP Loading 153
7.2 CP Cluster States 155
7.3 IP Addresses of the APG43 155
7.4 CP Blades Configuration for APZ 212 55 157
7.5 CP Blades Configuration for APZ 212 60 158
7.6 CSBIN 159
7.7 Manual Rotation of RELFSW Files 160
7.8 LEDs 161
7.9 STRABs 162
7.10 Blade Information for APZ 212 55 and APZ 212 60 163
7.11 Login to the ISM Web Pages 165
7.12 Login to the SIS Blade 165
7.13 Lock/Unlock Blades 166
7.14 References 167
8 Revision Information 170
9 Glossary 171
9.1 Terminology 171
9.2 Abbreviations 174
Ericsson Internal

1 Introduction
This test instruction is used for Factory Node Test of a CP Cluster
(= Blade Cluster (BC)).
Factory Node Test is performed at the production line.
1.1 Concerned Hardware
The MSC-S BC is seen from the network as one MSC Server, and is a
network of nodes.
It is built up with MSC-S blades, TSC blades, Signalling Proxy (SPX), and
network interfaces for IP. (ATM and TDM interfaces are optional).
SIS and I/O are part of the system for connection to OSS.
An MSC-S BC comprises the following main components:
• Two SPX. They convert and route signalling traffic (TDM, ATM and IP
based signalling).
• Common I/O system, based on two APG43.
• Cluster System, implementing two different logical nodes; MSC-S and

TSC.
Figure 1 MSC-S BC
MSC-S Blade Cluster
MSC-S MSC-S MSC-S MSC-S MSC-S

blade blade blade blade blade
SCTP/IP
Signalling
SGW I/O
SIS IO
I/O
proxy
TDM ATM IP
RAN CN OSS
The Cluster System is housed in an IS infrastructure. It provides an eGEM,

MXB, EXB, ISLB, IPLB (ISER in older versions), and SIS (marked PMD-IDE
on the blade).
Ericsson Internal


The SPX and I/O reside outside the IS infrastructure as attached systems,
connected to the IS via special switch blades (EXB).
2 Range of Test
The scope of this test instruction is to test the Cluster System and bring it into
service.
This test instruction is divided into a number of procedures to test the most
vital parts of the Cluster System. During test the internal power distribution,
connections and alarm presentation are checked. Initial loading of all CP
blades are performed.
Note 1: This document is not intended to be used at customer sites.
Note 2: This document will not cover any project after 09A.
Ericsson Internal


2.1 Work Flow
This test instruction should be executed in the following order:
Section Page Action
6.1 11 Preparation
6.2 11 Unlock the CPHW Blade System
6.3 13 Blade Definition in eGEM
6.4 17 Setting CP Identification Values
6.5 22 Installing PES and CPHW Dump Versions
6.6 27 Checking Proxy Boot Configuration
6.7 30 Transferring of CP Dump to APG43
6.8 43 Ping Tests
6.9 46 Boot Starting of the CP Blades
6.10 52 Initial Testing of the CP Blades
6.11 55 Initial Loading of the CP Blades
6.12 59 Definition of AP2
6.13 61 Definition of Routing Tables for IPonCP for VLAN INT-SIG
6.14 65 Definition of Routing Tables for IPonCP for VLAN SIG-1 and SIG-2
6.15 90 Definition of Routing Tables for IPonCP for BC-SIG
6.16 107 Definition of Routing Tables for IPonCP for BC-SIG-EXT1
6.17 123 Definition of Routing Tables for IPonCP for BC-SIG-EXT2
6.18 139 Definition of Routing Tables for IPonCP for BC-SIP
6.19 142 Definition of Routing Tables for IPonCP for BC-DNS
6.20 146 Definition of Routing Tables for IPonCP for BC-BLD-EXT1
6.21 148 Perform System Backup Copies

Ericsson Internal

3 Conditions before Starting

• The IS part must have been configured. It must have been tested
according to reference [30] on page 168.
• A Kickstart Server must be configured with base SW.
• The IS cabinets must be correct mounted and grounded.
4 Tools
• WinFIOL version 7 or later.
Note: WinFIOL 7 is required due to SSH (Secure Shell), when an APG43

is connected.
• The command file document 104/190 90-B/AXE 106 99 is used for

executing the CLI commands in WinFIOL.
• CPI-store, see
http://internal.ericsson.com/page/hub_inside/support/rd/tools/cpi/index.jsp
• IE-Select is used to get node building documents.

Ericsson Internal

5 General
The MSC-S blades use n+1 redundancy.
The CP Cluster System contains a number of blades in eGEM equipment

practise subracks, where each blade is a Field Replacement Unit (FRU).
The complete solution for the MSC-S BC system includes two APZ systems,
APZ 212 55/APZ 212 60 and APZ 214 01. The APZ 212 55/APZ 212 60
system contains two SPX systems and the APZ 214 01 system contains the
CP BC part.
The two APZ source systems are connected to two APG43 systems.
Statistics and charging are handled through the GEP based APG43 IO
system. One APG43 acts as single point of entry for all MML commands
towards the BC. This APG43 is used for regular IO activities and statistics.
The other APG43 is used for charging data.
The RPB-E implementation allows two APZ 212 55/APZ 212 60 systems to
exist in the same Ethernet environment.
The APZ 214 01 CP blades physically resides in an IS environment, while the

remaining parts are outside IS, that is, they are “attached systems” in IS
terminology.
The CP blades (GEP boards) are housed in IS eGEM subracks with MXB
blades. The MXB blades are backplane switches. The first subrack (IS1)
includes EXB switches that connect the attached non-IS systems with SIS
and IPLB (ISER in older versions). The EXB switches are then connected to
the SCB-RPs in the other non-IS eGEM.
MXB provides switching to the blades in each IS based subrack. The MXB
(MXB5) is used for connection between the IS subracks. SCP-RP4 provides
switching to the blades in each AXE based subrack.
SIS is used for Operation and Maintenance Support. It holds the configuration
and current status information of the IS infrastructure.
The IPLB is designed to operate in pairs for redundancy reasons. One IPLB
will be active and the other standby. The IPLBs can not be installed in the
same side of the magazine. That is, one IPLB must be installed in the left side
of the magazine (slot 1-12) and the other in the right side of the magazine
(slot 13-24). Slot 2 and 14 should not be used.
The external communication with a CP Blade System (BS) is performed via

IPLB/ISER and not via the APG43 systems.
Ericsson Internal


The APZ 214 01 CP BS consists hardware (HW) wise of a cluster of CP
blades. The number of TSC blades is either two or zero. If zero, the TSC
functionality is moved to the MSC blades. For APZ 212 55 with GEP1 boards,
the number of MSC-blades is between four and fifteen, mostly eight. For
APZ 212 60 with GEP2 boards, the number of MSC-blades is between three
and fourteen. The addressing is prepared for 64 CP blades. When the
application uses two TSC blades, the ISP will be determined very much on
those two blades.
Each CP blade is the same blade as for APZ 212 55/APZ 212 60, that is, one
of the blades in the GEP family equipped with at least 12 GB memory.
The Cluster Handler (CH) is a completely new feature in APZ, designed to

support the application with a defined set of CP blades, which can be used by
an application.
The CH has the responsibility for making a group of individual CPs operate as
a cluster. It is the only cluster aware function in APZ (that is the one that deals
with all blades as a unified object). CH hides the complexity of the distributed
system from the rest of APZ. This allows the rest of APZ to function in a One
CP environment.
A BSOM function on the CP blades enables the BS to communicate with IS in

order to perform management functions. The BSOM is the interface unit
between the CP BS and SIS. There is only one (active) BSOM in the system
represented by a unique IP address provided by IS. The BSOM is used by the
APZ to perform operations over the IPMI bus, such as turn on MIA LED, reset
a CP blade, or fetch information from IPMI registers.
When VM starts and there are several CP blades to choose between, the CP
blade with the lowest CPID will act as active BSOM. CPID is defined in the
HWC table stored in the APG43. When PLEX and MAS start, MAS decides
which CP blade that must act as active BSOM, and it will be the one that is
the Leader. The CP blade that has been up the longest time is the Leader.
The reason to that VM decides which CP blade that must act as active BSOM
is that CPT uses BSOM, and CPT has to work even when PLEX is not up and
running.
SW updates, upgrades and fallback per MSC-S and TSC blades in an MSC-S
BC, are possible to execute within 0.5 hours or less. This excludes the time
needed for traffic isolation, back-up, and CP preparation.
SW updates, upgrades and fallback for the SPX (per SPX instance) are
possible to execute within 2 hours or less, including possible VM middleware
updates.
The ATM Link Interface (ALI) blade provides signalling over ATM to the
MSC-S. The ATM option is for up to 8+8 ALI. No Group Switch (GS)
connection is required for ALI.
Ericsson Internal


C7/S7 over TDM signalling is optional and is supported for Narrow Band (NB)
and/or High Speed (HSL). The TDM option is for up to 4+4 ET155-1 and 8
STEB (512 C7/S7 and 32 HSL). GS connection is required for TDM signalling.
5.1 CP Blade Differences with Earlier APZ systems
The APZ 214 01 will introduce an architecture and concept that differ
substantially from earlier APZ systems. Main differences are:
• The CP is a Single sided CP, that is, no redundancy per CP blade.
• There is no MAU unit attached to the CP blades.
• Although the APZ system consists of a cluster of CP blades, there is no

APZ function that operates cluster wide except for the new CH function.
That is, each CP blade is in all respects handled as a separate system
with its own data set, file sizes, SW generation etc. It is an application
issue to create data replication and data consistency between different
blades when needed with the support from the CH.
• The CP BC resides in an IS infrastructure and must hence apply to

mandatory requirements on BS in IS.
• Regional processors are not supported.
5.2 Blade Positions and Information
The document “Blade Cluster Cabinet 1, BFM 107 1029,” in reference [31] on
page 168 describes the blade positions in cabinet 1 in a BC with APZ 212 55
and GEP1 boards.
The document "Blade Cluster Cabinet 2, BFM 107 1031," in reference [32] on
page 168 describes the blade positions in cabinet 2 in a BC with APZ 212 55
and GEP1 boards.
The document “Dynamic AGO, Blade Cluster 2.0 Cabinet 1” in reference [33]
on page 168 describes the blade positions in cabinet 1 in a BC with
APZ 212 60 and GEP2 boards.
The document "Dynamic AGO, Blade Cluster 2.0 Cabinet 2" in reference [34]
on page on page 168 describes the blade positions in cabinet 2 in a BC with
APZ 212 60 and GEP2 boards.
The Plant Engineering Description (PED) “AXE Blade Cluster" in reference

[29] on page 168, shows how the BC HW is connected.
The Allocation Drawing “MSC Server Blade Cluster” in reference [53] on page
170 shows the cable drawing for cabinets with APZ 212 55 and GEP1 boards.
The Allocation Drawing “MSC Server Blade Cluster 2.0” in reference [54] on
page 170 shows the cable drawing for subracks with APZ 212 60 and GEP2
boards.
Ericsson Internal


IS/MXB supervises the fans for the IS subracks. AXE/SCP-RP supervises the
fans for the AXE subracks. In that way related alarms will be stored in the
same alarm system. This means that fans for the IS subracks are connected
to the MXB, and the fans for the AXE subracks are connected to the SCB-RP.
6 Method
6.1 Preparation
6.1.1 General
Check the blade positions as indicated in chapter 5.2 "Blade Positions and
Information" on page 10.
6.1.2 Power Up
The eGEMs contains redundant power (-48V), either on the SCB-RP blades
or on the MXB blades.
Power up (if not already done) the eGEMs with their blades by inserting the
six power cables to the two SCB-RP blades for each eGEM, and the six
power cables to the MXB blades for each BC eGEM.
Check the LEDs. See chapter 7.8 “LEDs” on page 161.
6.2 Unlock the CPHW Blade System
1. Login to the ISM web pages is done according to chapter 7.11 on page 165.
The document “Factory Start Up and Initial NE Test of a CP Cluster in IS

Environment” in reference [30] on page 168, contains detailed information on
how to login to ISM web pages and SIS Blades.
Ericsson Internal


2. Unlock the CPHW blade system.
Integrated Site Services -> Hardware -> Open Blade systems
Press the table row icon for the CPHW blade system.
Press Unlock.
For more information, see chapter 7.13 "Lock/Unlock Blades" on page 166.
Check the status:

Integrated Site Services -> Hardware -> Open Blade systems
Observe the HW status in the "Open blade systems". The status for
"bs_CPHW_n" will first be Disabled and "Starting up". After a while it will
change to Enabled and Available.
Ericsson Internal


6.3 Blade Definition in eGEM
The MAC-addresses for the CP blades are stored in the DHCP table in the
APG43. This DHCP configuration is performed by the CSBIN service
ACS_CS_SERVICE_0 on the A-side and ACS_CS_SERVICE_1 on the
B-side (, which replaces ACS_MODD_SERVICE (MODDBIN)). CSBIN
regularly checks that the MAC-addresses are correctly stored in APG43, and
updates them if needed. CSBIN is responsible for the configuration of the
DHCP server and maintains the HWC table. Whenever the HWC table is
changed, CSBIN updates the DHCP table.
The CP blades use the DHCP server to fetch their IP addresses, boot
address and boot file name. They then use their MAC address in the DHCP
request.
The CP blades have to be defined in the eGEM. That is performed in the

following way from the APG43 with APIO.
1. Login via remote desktop over the public network towards both sides of the
APG43 with APIO (it has a DVD board).
Login to side A of this APG43.
2. Check that the CSBIN resources are up and running:
C:\>cluster res ACS_CS_SERVICE_0 (for side A)

C:\>cluster res ACS_CS_SERVICE_1 (for side B)
See chapter 7.6 “CSBIN” on page 159 for more information.
3. If they are not up and running, bring them up:
C:\>cluster res ACS_CS_SERVICE_0 /on /wait

C:\>cluster res ACS_CS_SERVICE_1 /on /wait
Note: The name of the service is ACS_CS_SERVICE_1 on the B-side.

Ericsson Internal


4. Print the Hardware Configuration Table.
See “hwcls” in reference [6] on page 167.
C:\>hwcls -m a.b.0.d
The value for a is received from the strap connector 00/55.

The value for b is received from the strap connector 00/40.
The value for c is received from the strap connector 00/25. Must always be 0.
The value for d is received from the strap connector 00/10.
For more information, see chapter 0 ”STRAP Connectors” on page 161.
Note 1: The subrack address (option -m) must be 0.0.0.0 for the IS1
subrack, and 1.0.0.0 for the IS2 subrack.
Note 2: See chapter 7.10 “Blade Information” on page 163 for more
information.
5. Remove faulty entries from the HW configuration table if needed.

See “hwcrm” in reference [7] on page 167.
C:\>hwcrm -m a.b.0.d -s <slot number>
If hwcrm has been entered, execute the following commands so that the
allocated IP addresses in the next step will start from the beginning.
C:\>cluster res ACS_CS_Service _x /off /wait (x=0 or x=1)

C:\>cluster res ACS_CS_Service_x /on /wait (x=0 or x=1)
6. Check the common data for the BS.

See “nels” in reference [55] on page 170.
C:\>nels
DERIVED DATA
System Type: Multi-CP System
Number of Dual-Sided CPs: 2
Number of Single-Sided CPs: 10
Number of APs: 2
Front AP: AP1
Alarm Master CP: SPX-01
Clock Master CP: SPX-02
OPERATOR CHANGEABLE DATA

Network Element Identity:
Note: The data must as above, with the exception of “Number of Single-
Sided CPs”, which can differ depending on HW configuration.
Ericsson Internal


7. Insert the correct values for the CP blades into the HW configuration table.
See “hwcadd” in reference [5] on page 167.
Note 1: Check the blade positions as indicated in chapter 5.2

"Blade Positions and Information" on page 10.
Note 2: The slot numbers can differ depending on the blade positions.
Available slots for GEP1 boards are:
IS1: 5, 7, 9, 18, 20, 22.
IS2: 3, 7 13, 17.
IS1: 5, 9, 11, 17, 21. 23 is optional.
IS2: 1, 3, 5, 9, 11, 13, 15, 17, 21, 23 are all optional.
Note 3: The sequential number (option -u) is 0 for the first CP blade, 1 for
the next, and so on. –u has its value described in chapter 7.4
“CP Blades Configuration for APZ 212 55” on page 157 and in
chapter 7.5. “CP Blades Configuration for APZ 212 60” on page
158.
Note 4: Option -y is not used, but must be given a value. It can have the
value 1, since 0 is not allowed.
Note 5: The subrack address (option -m) must be 0.0.0.0 for the IS1
subrack, and 1.0.0.0 for the IS2 subrack.
C:\>hwcadd -m a.b.0.d -s <slot number> -n CPUB -t BC -y 1 -d client -u <sequential number>
Repeat this step for all slot positions that have CP blades.
For IS1 with GEP1 boards (APZ 212 55):

C:\>hwcadd -m 0.0.0.0 -s 5 -n CPUB -t BC -y 1 -d client -u 0
For IS2 with four GEP1 boards (APZ 212 55):

Ericsson Internal


For IS1 with six GEP2 boards (APZ 212 60):
For IS2 with ten GEP2 boards (APZ 212 60):

C:\>hwcadd -m 1.0.0.0 –s 15 -n CPUB -t BC -y 1 -d client -u 12
C:\>hwcadd -m 1.0.0.0 –s 21 -n CPUB -t BC -y 1 -d client -u 14
8. Print the Hardware Configuration Table.

C:\>hwcls
The following printout is an example:
HARDWARE CONFIGURATION TABLE
MAG SLOT SYSTYPE SYSNUM FBN IPA IPB

...
0.0.0.0 s BC 0 CPUB 192.168.169.61 192.168.170.61
...
Note 1: The IP address for IPA is 192.168.169.x, x=56 or higher.

The IP address for IPB is 192.168.170.x, x=56 or higher.
Note 2: The first CP blade will have the IP address 192.168.169.61 for IPA,
and 192.168.170.61 for IPB.
Ericsson Internal


9. Synchronize the HW configuration table with the subrack.
See “hwcsync” in reference [8] on page 167.
C:\>hwcsync
Note: hwcsync is only needed when a CP blade is replaced. The only

thing that it performs is to re-read the MAC-addresses for the CP
blades. HWC needs to be synchronized with the SCB-RP MIBs.
The APG43 server CSBIN performs the synchronization.
6.4 Setting CP Identification Values
1. Print the CP Identification Table.

See “cpls” in reference [12] on page 167.
C:\>cpls -l
Printout: CP IDENTIFICATION TABLE
The value of CPNAME is set automatically. The value is given from

systemType (option -t in hwcadd) and systemNum (option -y) for dual sided
CP (SPX), and from systemType and seqNum (option -u) for Single sided CP
(CP blade). If systemType is CP, the value of CPNAME will be CPn, where n
is given systemNum. If systemType is BC, the value of CPNAME will be BCn,
where n is given seqNum.
The value of CPID is equal to systemNum (option -y) + 1000 for SPX, and
equal to seqNum (option -u) for the CP blades.
Ericsson Internal


2. Set the CP identification list for the CP blades:
See “cpch” in reference [11] on page 167.
For APZ 212 55:

C:\>cpch -a <TSC-B0x or MSC-S-B0x> -s APZ21401 -t 21255 <cpid>
For APZ 212 60:

C:\>cpch -a <TSC-B0x or MSC-S-B0x> -s APZ21401 -t 21260 <cpid>
Note 1: The alias (-a) string length can not exceed 7 characters.
x is cpid + 1.
Note 2: cpid is the sequential number (-u), specified as in chapter 7.4

158.

IS1: 5, 7, 9, 18, 20, 22.
IS2: 1, 3, 5, 7, 9, 13, 15, 17, 19, 21 and 23. They are all optional.

IS1: 5, 9, 11, 17, 21. 23 is optional.
IS2: 1, 3, 5, 9, 11, 13, 15, 17, 21, 23. They are all optional.
For APZ 212 55 with ten CP blades:

C:\>cpch -a TSC-B03 -s APZ21401 -t 21255 2
C:\>cpch -a MSC-B01 -s APZ21401 -t 21255 0
Ericsson Internal


For APZ 212 60 with sixteen CP blades:
3. Set the CP identification list for the first SPX system (if not already done):
For APZ 212 55:

C:\>cpch -a SPX-01 -s APZ21255 -t 21255 1001
For APZ 212 60:

C:\>cpch -a SPX-01 -s APZ21260 -t 21260 1001
Note: cpid is the system number (-y) + 1000, specified with the command
hwcadd for CPUB. This means that cpid will be 1001. It should
have been specified in “Factory Start Up and Initial NE Test of
APZ 212 55 and APZ 212 60” in reference [2] on page 167.
4. Set the CP identification list for the second SPX system (if not already done):
For APZ 212 55:

C:\>cpch -a SPX-02 -s APZ21255 -t 21255 1002
For APZ 212 60:

C:\>cpch -a SPX-02 -s APZ21260 -t 21260 1002
Note 1: cpid is the system number (-y) + 1000, specified with the command
hwcadd for CPUB. This means that cpid will be 1002. It should
have been specified in “Factory Start Up and Initial NE Test of
APZ 212 55 and APZ 212 60” in reference [2] on page 167.
Note 2: cpid must have different values for the different SPX systems.
Ericsson Internal


C:\>cpls -l
6. Define the CP group that contains TSC blades.

See “cpgdef” in reference [50] on page 169.
C:\>cpgdef -cp cpname . . . ALLTSC
For APZ 212 55:

C:\>cpgdef -cp BC2,BC3 ALLTSC
See chapter 7.4 “CP Blades Configuration for APZ 212 60” on page 157.
For APZ 212 60 (if using TSC blades):

C:\>cpgdef -cp BC0,BC3 ALLTSC
See chapter 7.5. “CP Blades Configuration for APZ 212 60” on page 158.
Note 1: The CP group name (ALLTSC) can not exceed 7 characters.
Note 2: There is on the OSS side applications’ relying on that the CP group
name is exactly ALLTSC.
7. Define the CP group that contains MSC blades.

C:\>cpgdef -cp cpname . . . ALLMSC
For APZ 212 55 with ten CP blades:

C:\>cpgdef -cp BC0,BC1,BC4,BC5,BC7,BC9,BC11,BC13 ALLMSC
See chapter 7.4 “CP Blades Configuration for APZ 212 60” on page 157.
For APZ 212 60 with sixteen CP blades:

C:\>cpgdef - BC1,BC2,BC4,BC5,BC6,BC7,BC8,BC9,BC10,BC11,BC12,BC13,BC14,BC15 ALLMSC
See chapter 7.5. “CP Blades Configuration for APZ 212 60” on page 158.
Note 1: The CP group name (ALLMSC) can not exceed 7 characters.
Note 2: There is on the OSS side applications relying on that the CP group
name is exactly ALLMSC.
Ericsson Internal


8. Define the CP group that contains SPX1 and SPX2.
C:\>cpgdef -cp CP1,CP2 ALLSPX
See chapter 7.10 “Blade Information” on page 163.
Note 1: The CP group name (ALLSPX) can not exceed 7 characters.
Note 2: There is on the OSS side applications’ relying on that the CP group
name is exactly ALLSPX.
9. List all defined CP groups.

See “cpgls” in reference [51] on page 169.
C:\>cpgls
10. Print the contents of the APZ VLAN tables.

See “apzvlanls” in reference [52] on page 169.
C:\>apzvlanls
11. Restart the cluster resources.
C:\>prcboot
The reboot will create all necessary CPHW and APZ VM directories in
APG43.
Note: The connection to the APG43 will be lost since the active APG43
side is now rebooted. The passive APG43 side will now become
active and new directory structure will be created for the CP
boards. The passive APG43 side will become active in
approximately two minutes.
Login to the APG43 once again and continue with the next chapter.
Ericsson Internal


6.5 Installing PES and CPHW Dump Versions
This chapter is applicable only if IS 2.0 or later is installed. The binary files
and configuration files for PES and CPHW for CP Blades are stored on the
APG43 and not on SIS.
Note: This chapter requires that chapter 6.4 “Setting CP Identification

Values” on page 17 has been executed.
1. To be able to unlock CP blades also the CPHW registration files

xxxxBL-SI.CXP and xxxxBS-SI.CXP must be installed on SIS.
No other SW for PES or CPHW has to be installed on SIS.
The CPHW IS dump LZY 201 290 R13A can be installed on SIS if GEP1
boards are used as CP blades.
The CPHW IS dump LZY 201 290 R14A can be installed on SIS if GEP2
boards are used as CP blades. It can also be used for GEP1 boards.
There will be an R15 version with some formal changes. It will not contain any
new functionality.
Make sure that the correct version is stored on SIS, before continuing with the
following steps.
2. The PES and CPHW dumps with the MW can be transferred to partition K: on
the APG43 in the following way.
The following are used as examples for CPHW and PED:

CPHW: CPHW_Dump.zip
PES: PlexEngine_Dump.zip
Assume that the above mentioned files are stored on a remote ftp server.
3. You can use either Remote Desktop, SSH, SFTP2 or DVD to load PES and
CPHW dumps onto the APG43. In this example we will use SFTP2 to load
PES and CPHW dumps onto the APG43 on the folder K:\ftpvol.
K:\ftpvol>sftp2 <remote FTP server ip_address>

user:<user_id>
password:<password>
sftp2>cd <source_directory on remote FTP server>
sftp2>bin
sftp2>mget * (confirm with Y for the PES and CPHW dumps)
sftp2>quit
Ericsson Internal

4. Install the CPHW dump package.

See “cfeted” in reference [47] on page 169.
K:\ftpvol>cfeted -d hw <CPHW_Dump>.zip
5. Install the PES dump package.

See “cfeted” in reference [47] on page 169.
K:\ftpvol>cfeted -d pe <PlexEngine_Dump>.zip

C:\>cpls -l
Note: CPHW and PES must then be installed in the BCx blade.
(See CPNAME in the printout).
Ericsson Internal


7. Install the CPHW dump package and PES dump package in a CP blade (BCx
blade). See “cfeted” in reference [47] on page 169.
C:\>cfeted -n hw -cp BCx (x=0, 1. . .)

C:\>cfeted -n pe -cp BCx (x=0, 1. . .)
C:\>cfeted -v cur -cp BCx (x=0, 1. . .)
For IS1 for APZ 212 55:
For slot 5:
C:\>cfeted -n hw -cp BC0
C:\>cfeted -n pe -cp BC0
C:\>cfeted -v cur -cp BC0
For slot 7:
For slot 9:
For slot 18:

For slot 20:

For slot 22:

Ericsson Internal


For IS2 with four GEP1 boards for APZ 212 55:
For slot 3:
For slot 7:
For slot 13:

For slot 17:

For IS1 with six GEP2 boards for APZ 212 60:
For slot 5:
For slot 9:
For slot 11:

For slot 17:

For slot 21:

Ericsson Internal


For slot 23:
For IS2 with ten GEP2 boards for APZ 212 60:
For slot 1:
For slot 3:
For slot 5:
For slot 9:
For slot 11:

For slot 13:

For slot 15:

For slot 17:

For slot 21:

Ericsson Internal


For slot 23:
8. Perform the previous step for all CP blades (BCx blades).
6.6 Checking Proxy Boot Configuration
This chapter is only applicable for AP1.
Proxy Boot is a new functionality that makes it possible for the CP blades to
boot from the APG instead of from the IS.
Ericsson Internal


1. Check that the resource SPOE_IP_BACKUP exists in the cluster group (see
the picture below). This resource should be of Resource Type “IP Address”.
The IP address must be 192.168.170.33.
Start -> Administrative Tools -> Cluster Administrator
Click on “Cluster Group”.

Right-click on “SPOE_IP_BACKUP”.
Click on Properties and then on Parameters.
Note: Remote desktop has to be used.

Ericsson Internal


2. Check that the tftp root path is set to K:\APZ\data (see the picture below).
Start -> My Computer -> C:
Go to C:\PROGRAM FILES\Winagents\TFTP Service
Double-click on SRVCONF.exe
Note: Remote desktop has to be used.

Ericsson Internal


6.7 Transferring of CP Dump to APG43
This is an example on how to transfer the CP dump to the APG43 CPF file
system. The assumption is that the CP blades are located as described in
chapter 7.4 “CP Blades Configuration for APZ 212 55” on page 157 or in
chapter 7.5. “CP Blades Configuration for APZ 212 60” on page 158.

IS1: 5, 7, 9, 18, 20, 22.
IS2: 3, 7 13, 17. They are all optional.

IS1: 5, 9, 11, 17, 21. 23 is optional.
IS2: 1, 3, 5, 9, 11, 13, 15, 17, 21, 23. They are all optional.
1. Assume that the CP dump is stored on a remote ftp server.
2. You can use SFTP2 or DVD to load the CP dump to the APG43 in the temp
folder K:\ftpvol. In this example we will use SFTP2.
K:\ftpvol>sftp <remote FTP server ip_address>

user: <user_id>
password: <password>
sftp2>cd <source_directory on remote FTP server>
sftp2>bin
sftp2>mget * (confirm with Y for the CP dump)
sftp2>quit
Note: In this example we have the same CP dump installed on all CP

blades.
3. Unzip the CP dump file in case it is zipped.
K:\ftpvol>zipc -e –o <zipped CP dump file> “K:\ftpvol\tmp\RELFSWDIR”

C:\>cpls -l

Ericsson Internal


5. Define volume RELVOLUMSW for all CP blades.
C:\>mkdir K:\FMS\data\<cpname>\CPF\RELVOLUMSW
IS1 for APZ 212 55:
C:\>mkdir K:\FMS\data\BC0\CPF\RELVOLUMSW (slot 5)

IS2 for APZ 212 55 with four GEP1 boards:

IS1 for APZ 212 60 with six GEP2 boards:

IS2 for APZ 212 60 with ten GEP2 boards:

Ericsson Internal


6. Define volume EXCHVOLUME for all CP blades.
C:\>mkdir K:\FMS\data\<cpname>\CPF\EXCHVOLUME
IS1 for APZ 212 55:
C:\>mkdir K:\FMS\data\BC0\CPF\EXCHVOLUME (slot 5)




Ericsson Internal


7. Define LO.
C:\>cpfmkfile –cp <cpname> -l 512 -c -f reg LO EXCHVOLUME
Note: LO is used when loading central software units in the central

processor with the command LASUL.
IS1 for APZ 212 55:
C:\>cpfmkfile -cp BC0 -l 512 -c -f reg LO EXCHVOLUME (slot 5)




Ericsson Internal


8. Define FC.
C:\>cpfmkfile -cp <cpname> -l 512 -c -f reg FC EXCHVOLUME
Note: FC is used when changing central software units in the central

processor with the command FCSUL.
IS1 for APZ 212 55:
C:\>cpfmkfile -cp BC0 -l 512 -c -f reg FC EXCHVOLUME (slot 5)




Ericsson Internal


9. Define LMAFILE.
C:\>cpfmkfile -cp <cpname> -l 125 -f inf -s 120 LMAFILE EXCHVOLUME
Note: LMAFILE must exist to prevent alarm that the file does not exist.
IS1 for APZ 212 55:
C:\>cpfmkfile -cp BC0 -l 125 -f inf -s 120 LMAFILE EXCHVOLUME (slot 5)




Ericsson Internal


10. Define system backup files in CPF file system.
C:\>cpfmkfile -cp <cpname> -k -c -l 2048 -f reg RELFSW0 RELVOLUMSW

Note: -k means that the dump will be compressed.
IS1 for APZ 212 55:
For slot 5:
C:\>cpfmkfile -cp BC0 -k -c -l 2048 -f reg RELFSW0 RELVOLUMSW
For slot 7:
For slot 9:
For slot 18:

For slot 20:

For slot 22:

Ericsson Internal


For slot 3:
For slot 7:
For slot 13:

For slot 17:

Ericsson Internal


For slot 5:
For slot 9:
For slot 11:

For slot 17:

For slot 21:

For slot 23:

Ericsson Internal


For slot 1:
For slot 3:
For slot 5:
For slot 9:
For slot 11:

For slot 13:

For slot 15:

For slot 17:

Ericsson Internal


For slot 21:
For slot 23:

11. Transfer CP dump file to CPF file RELFSW99.
K:\ftpvol>cpfport -cp <cpname> -i K:\ftpvol\tmp\RELFSWDIR RELFSW99
IS1 for APZ 212 55:
K:\ftpvol>cpfport -cp BC0 -i K:\ftpvol\tmp\RELFSWDIR RELFSW99 (slot 5)


Ericsson Internal




12. Check CPF file table for RELFSW99.
K:\ftpvol>cpfls –cp <cpname> -lsk RELFSW99
IS1 for APZ 212 55:
K:\ftpvol>cpfls -cp BC0 -lsk RELFSW99 (slot 5)


Ericsson Internal




Ericsson Internal


6.8 Ping Tests
6.8.1 Ping the Two APG43 from the CP Blades
Command ping is executed from the CP blades towards both APG43 sides, to
test whether the communication between APG43 and the CP blades works.
1. Login to the ISM web pages is done according to chapter 7.11 on page 165.
The document “Factory Start Up and Initial NE Test of a CP Cluster in IS

Environment” in reference [30] on page 168, contains detailed information on
how to login to ISM web pages and SIS Blades.
Note: You need to be on the active SIS blade to perform this test.
2. List the ISOB IP addresses for the CP Blades with GUI.
Integrated Site Services -> Network Configuration -> Blade Systems
Press the table row icon for bs_CPHW_n.
Press Blades.
The Internal O&M Basic subnet (ISOB) IP addresses are then listed.
3. Check that it is possible to ping to the two APG43.
Note: This step is not performed in a system taken into service, since
commands performed on the CP blades can disturb VM (PES),
making the system to crash.
Login to the SIS blade according to chapter 7.12 "Login to the SIS Blade" on
page 165.
Login to a "bs_CPHW_n" CP blade for IS1 as in the following example:
You will then get a new cp-prompt, which can differ from case to case.
SIS1:~# ssh 169.254.0.81

cpblade- login: root
Note: If problem with ssh, use telnet instead.
Check that both "bond0.169" and "bond0.170" have IP addresses attached.
cp-prompt:~# ifconfig
Ericsson Internal


The following printout is an example for "bond0.169":
bond0.169 Link encap:Ethernet HWaddr 00:01:EC:F0:68:5C

inet addr:192.168.169.70 Bcast:192.168.169.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:91502016 errors:0 dropped:0 overruns:0 frame:0
TX packets:91517132 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4590017519 (4.2 GiB) TX bytes:6771739554 (6.3 GiB)
Verify then that "inet addr", Bcast and Mask exist with assigned values both
for section "bond0.169" and section "bond0.170".
Ping the first APG43 (AP1 cooperating with SPX1):
"cp-prompt":~# ping -c 2 192.168.169.1

"cp-prompt":~# ping -c 2 192.168.169.2
"cp-prompt":~# ping -c 2 192.168.170.1
"cp-prompt":~# ping -c 2 192.168.170.2
This APG43 (AP1), has the fixed IP addresses 192.168.169.1/2 and

192.168.170.1/2.
Ping the second APG43 (AP2 cooperating with SPX2), if it exists:
"cp-prompt":~# ping -c 2 192.168.169.3

"cp-prompt":~# ping -c 2 192.168.169.4
"cp-prompt":~# ping -c 2 192.168.170.3
"cp-prompt":~# ping -c 2 192.168.170.4
This APG43 (AP2), has the fixed IP addresses 192.168.169.3/4 and

192.168.170.3/4.
Repeat this step for all "bs_CPHW_n" CP blades for IS1 and IS2 if available,
shown in the previous step.
See also chapter 7.3 "IP Addresses of the APG43" on page 155 for more
information.
6.8.2 Ping the CP Blades from the Two APG43
Command ping is executed from both APG43 sides towards both Ethernet
interfaces (defined by separate IP addresses), to test whether the
communication between APG43 and CP blades works
The IP addresses can be different for each site and is determined by reading
the contents in the HWC table on the APG43 by using the command hwcls.
1. Login to side A in APG43 with APIO.

Ericsson Internal

2. Print the Hardware Configuration Table for CP BC.

C:\>hwcls -t BC
The IP addresses of both planes of the Ethernet connection to CP blades are

returned with the answer printout HARDWARE CONFIGURATION TABLE.
3. Test the communication from APG43 side A to the CP blades.
Execute command ping with the IP address of Ethernet A connection for a CP

blade.
C:\>ping -n 2 <IP address for “IPA” for a CP blade>
Execute command ping with the IP address of Ethernet B connection for a CP

blade.
C:\>ping -n 2 <IP address for “IPB” for a CP blade>
Repeat this step for all CP blades.
4. Login to side B in APG43 with APIO.
5. Print the Hardware Configuration Table for CP BC.

C:\>hwcls -t BC
The IP addresses of both planes of the Ethernet connection to CP blades are

returned with the answer printout HARDWARE CONFIGURATION TABLE.
Ericsson Internal


6. Test the communication from APG43 side B to the CP blades.
Execute command ping with the IP address of Ethernet A connection for a CP

blade.
C:\>ping -n 2 <IP address for “IPA” for a CP blade>
Execute command ping with the IP address of Ethernet B connection for a CP

blade.
C:\>ping -n 2 <IP address for “IPB” for a CP blade>
Repeat this step for all CP blades.
7. Repeat step 1 to step 6 for the other APG43.
6.9 Boot Starting of the CP Blades
In this chapter is the installation described of CPHW SW and PES SW into

the CP blades.

C:\>cpls -l
2. Enter an MML command session from a WinFIOL terminal towards a CP

blade that is affected.
C:\>mml -cp <cpname> –a
If the following printout is received, continue with step 9.

Otherwise proceed with the next step.
CP NOT OBTAINABLE
YOU MAY NOW ENTER: APLOC, PTCOI, OR EXIT COMMAND
Note: If rufing is ongoing, for example loading of new BIOS, it will not
be possible to use CPT. Then you have to wait until the rufing is
completed, before you can continue with using CPT commands.
Ericsson Internal


3. Enter an MML command session from a WinFIOL terminal towards another
CP blade that is working OK.
CP NOT OBTAINABLE
4. Connect to CPT mode.
<PTCOI;
Confirm the following question with y.
CPT COMMANDS ARE DANGEROUS TO CLUSTER CP, CONTINUE (Y/N)?:y;
EXECUTED
Note 1: The question is always received when connecting to a CP blade,

since a CP blade is always in EX-mode and not in SB-mode.
Note 2: This should result in the CPT mode prompt:
cpt<
5. Check that no rufing is ongoing.
<PTCRP:REG=RUFSTATUS,PRO=GPR,CP=<cpid>;
Note: cpid is the sequential number (-u), specified as in chapter 7.4

158.

CPT MESSAGE PROCESSOR REGISTER
PRO CP
GPR <cpid>
REGISTER DATA
RUF-STATUS H'0000000
RUF-STATUS must be zero. If not, rufing is ongoing. If rufing is ongoing, you

have to wait a while and then perform this step again until RUF-STATUS is
zero.
Ericsson Internal


6. Boot start (reset) the CPU. The PES dump binaries and the CPHW dump
binaries will then be upgraded.
cpt<PTCPR:CP=<cpid>;
See “PTCPR” in reference [19] on page 168.
Warning!
Wait for the CP blade to reload completely. The CP-FW upgrade will be
started immediately. This upgrading process can take up to 20 minutes
and the contact to the CP blade may not be possible. During this period
it is not allowed to abort the upgrading process by power off the CP blade,
rebooting the AP or by stopping the DHCP server in the AP.
EXECUTED just shows that the CPT has performed the reboot. If upgrade is
needed due to new FW, this will take up to 20 minutes to perform.
By entering PTCRP:PRO=GPR,REG=CDU,CP=<cpid>; it is possible to get

information about the upgrade phases. See chapter 0 “Numerical values,
during remote upgrade of firmware” on page 152. When the value 800 is
received, the upgrade process is finished. It is also possible to see that the
upgrade is finished according to step 16 on page 51.
7. Disconnect CPT.
cpt<PTCOE;
8. Close the MML session.
<EXIT;
Continue with step 19.

Ericsson Internal


<PTCOI;
EXECUTED

cpt<
10. Check the CP state.
cpt<PTWSP;
Printout: CPT MESSAGE CLUSTER CP INFORMATION

See reference [10] on page 167.
Check that the CP state is OK.
11. Check that no rufing is ongoing.
<PTCRP:REG=RUFSTATUS,PRO=GPR,CP=<cpid>;
Note: cpid is the sequential number (-u), specified as in chapter 7.4

158.

CPT MESSAGE PROCESSOR REGISTER
PRO CP
GPR <cpid>
REGISTER DATA
RUF-STATUS H'0000000
RUF-STATUS must be zero. If not, rufing is ongoing. If rufing is ongoing, you

have to wait a while and then perform this step again until RUF-STATUS is
zero.
Ericsson Internal


12. Passivate the PHC function.
See “PTPHR” in reference [15] on page 167.
cpt>PTPHR;
Check that the PHC function is passive.
cpt>PTWSP;

13. Boot start (reset) the CPU. The PES dump binaries and the CPHW dump
binaries will then be upgraded.
cpt<PTCPR;
See “PTCPR” in reference [19] on page 168.
Warning!
Wait for the CP blade to reload completely. The CP-FW upgrade will be
started immediately. This upgrading process can take up to 20 minutes
and the contact to the CP blade may not be possible. During this period
it is not allowed to abort the upgrading process by power off the CP blade,
rebooting the AP or by stopping the DHCP server in the AP.
EXECUTED just shows that the CPT has performed the reboot. If upgrade is
needed due to new FW, this will take up to 20 minutes to perform.
By entering the CPT command PTCRP:PRO=GPR,REG=CDU; in step 16, it

is possible to get information about the upgrade phases. See chapter 0
“Numerical values, during remote upgrade of firmware” on page 152. When
the value 800 is received, the upgrade process is finished. It is also possible
to see that the upgrade is finished according to step 16 on page 51.
The following printout is received instead of EXECUTED if the connection is

lost:
NOT ACCEPTED
FAULT CODE 2
DATA LINK ERROR
Ericsson Internal


14. Enter an MML command session from a WinFIOL terminal towards the CP
blade that has been reset.
CP NOT OBTAINABLE
<PTCOI;
EXECUTED

cpt<
16. Check if reload is finished. The reload is complete when the contents of DATA
register are zero. See “PTCRP” in reference [16] on page 167.
cpt<PTCRP:PRO=GPR,REG=CDU;
Compare the received values with chapter 7.1 “Information Displayed by a

CDU” on page 150.
Note: Since there is no PLEX dump, 999 shall be received as end digits.
It means that no PLEX dump is loaded. If a PLEX dump had been
used, 000 had been received instead.
17. Disconnect CPT:
cpt<PTCOE;
<EXIT;
Ericsson Internal

19. Repeat step 2 to step 18 for all the CP blades.
6.10 Initial Testing of the CP Blades
This chapter requires that CPHW SW and PES SW are installed into the CP
blades. This means that chapter 6.9 on page 46 must have been executed.

C:\>cpls -l

blade that is affected.
CP NOT OBTAINABLE
<PTCOI;
EXECUTED

cpt<
Ericsson Internal


4. Check that the PHC function is passive.
cpt<PTWSP;

5. Stop program execution.
cpt<PTPEE;
6. Disconnect CPT:
cpt<PTCOE;
<EXIT;
8. Enter an MML command session from a WinFIOL terminal towards another

CP blade from which the test will be initiated.
CP NOT OBTAINABLE
Ericsson Internal


<PTCOI;
EXECUTED

cpt<
10. Order initial test of the CP blade. The test can take up to 20 minutes.
See “PTITI” in reference [9] on page 167.
cpt<PTITI:CP=<cpid>;
Printout: CPT MESSAGE INITIAL TEST RESULT
If the fault code is not 0, then compare with the printout description.
Repair faults by replacing suspected HW with spares.
Note 1: The test can not be performed towards the CP blade from which
the command is entered.
Note 2: The test can be interrupted by entering the command PTITE;
Note 3: The test 138 is omitted.
Note 4: While waiting for the result it is OK to continue with the next
CP blade in step 14 in this chapter and performing the tests of
the CP blades in parallel to gain time.
Ericsson Internal


11. Order Extended Memory Test (EMT) of the CP blade. The test can take 20-45
minutes. See “PTITI” in reference [9] on page 167.
Note 1: If extended memory test already has been executed for the
CP blade during the board tests, this step can be omitted.
cpt<PTITI:CP=<cpid>,TEST=138;
Printout: CPT MESSAGE INITIAL TEST RESULT
If the fault code is not 0, then compare with the printout description.
Repair faults by replacing suspected HW with spares.
Note 2: The test can not be performed towards the CP blade from which
the command is entered.
Note 3: The test can be interrupted by entering the command PTITE;
12. Disconnect CPT:
cpt<PTCOE;
<EXIT;
6.11 Initial Loading of the CP Blades
Initial loading is performed on all CP blades.

C:\>cpls -l

Ericsson Internal


2. Open an MML session towards a CP blade that is affected.
3. Connect to CPT.
<PTCOI;
EXECUTED

4. Check that the PHC function is passive.
cpt<PTWSP;

5. Stop program execution.
cpt<PTPEE;
6. Order an initial load.

See “PTCPL” in reference [13] on page 167.
cpt<PTCPL:FILE=RELFSW99;
7. Release the IO terminal and wait for the initial load to finish.
Enter <CTRL-D> on the IO terminal used for CPT.

Ericsson Internal


8. Check the printouts from CPT (this repeats for a few minutes).
The following printouts may be received.
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STARTED
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN PROGRESS
9. If loading is successful, this printout may appear:
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) FINISHED
10. If loading is not successful, check the meaning of the fault code in POD.
Printout: CPT MESSAGE INITIAL LOADING (ABSOLUTE) STOPPED
Solve the fault, and start again from step 6.
11. Disconnect CPT:
cpt<PTCOE;
<EXIT;
13. Open an MML session towards the CP blade.
14. Wait either for result printout (RANK SYSTEM START) or the exchange
header, after loading into the CP blade.
Printout: SYSTEM STARTED (if received)

Ericsson Internal


15. Start the application blocks in the CP blade.
See “SYATI” in reference [17] on page 167.
<SYATI:RESTART;
Release the terminal by entering <CTRL-D>.
Wait for the result printout.
Printout: APPLICATION ACTIVATION RESULT
Blocks in state PASSIVE are started and their states are set to ACTIVE.
A large system restart is then initiated.
16. Set Error Printout Format to large format in the CP blade.
<DIEFC:FORM=2;
17. Set the program clock in the CP blade.
<CACLS:DATE=yymmdd,TIME=hhmm;
<PTCOI;
EXECUTED


Ericsson Internal


19. Activate the PHC function.
See “PTPHS” in reference [14] on page 167.
cpt>PTPHS;
Check that the PHC function is active.
cpt>PTWSP;

20. Disconnect CPT:
cpt<PTCOE;
<EXIT;
Repeat step 2 to step 21 for all the CP blades.
6.12 Definition of AP2
Define the second APG43 (AP2) used for charging on all CP blades.

C:\>cpls -l
2. Open an MML session to a CP blade.

Ericsson Internal


3. Define AP2.
<APAMI:AP=2,TYPE=0;
If the command is rejected with the following result, proceed with the next
step.
NOT ACCEPTED
COMMAND RESTRICTED
If not rejected due to this, continue with step 6 in this chapter.
4. Insert command APAMI into Command Category (COCA) Group 0.
<IOCTI:COMMAND=APAMI,COCA=0;
5. Perform a new attempt to define AP2.
<APAMI:AP2,TYPE=0;
<EXIT;
7. Repeat step 2 to step 6 in this chapter for all CP blades.

Ericsson Internal


6.13 Definition of Routing Tables for IPonCP for VLAN INT-SIG
6.13.1 General
This chapter defines the functionality IPonCP for VLAN INT-SIG.
See the document “Factory Start Up and Initial NE Test of a CP Cluster in IS

Environment” in reference [30] on page 168 for detailed information about the
VLANs.
See the document “MSC Server Blade Cluster (MSC-S BC) Network
Introduction” in reference [35] on page 169 for detailed information about the
used IP addresses and the VLANs.
6.13.2 SPX1
Note: This chapter can be omitted if already done.
This chapter defines the routing for the VLAN INT-SIG from SPX1.
1. Enter an MML command session from a WinFIOL terminal towards SPX1.
C:\>mml -cp CP1 –a
2. Create the virtual interface “ETHA-1001” on the physical interface ETHA.

See “IHIFI” in reference [44] on page 169.
<IHIFI:VIF=ETHA-1001;
3. Create the virtual interface “ETHB-1001” on the physical interface ETHB.

<IHIFI:VIF=ETHB-1001;
4. Add the IP address and netmask for SPX1 on VLAN INT-SIG to the virtual
interface ETHA-1001. See “IHIFC” in reference [45] on page 169.
<IHIFC:VIF=ETHA-1001,ADD,IP=192.168.1.n,NETMASK=255.255.255.0,ARP=YES;
Note: The value of n must be the same as used in the HW-DT.

Ericsson Internal


interface ETHB-1001. See “IHIFC” in reference [45] on page 169.
<IHIFC:VIF=ETHB-1001,ADD,IP=192.168.1.n,NETMASK=255.255.255.0,ARP=YES;
6. Print the virtual interfaces.

See “IHIFP” in reference [46] on page 169.
<IHIFP;
Printout: VIRTUAL ETHERNET INTERFACE DATA
<EXIT;
6.13.3 SPX2
Note: This chapter can be omitted if already done.
This chapter defines the routing for the VLAN INT-SIG from SPX2.


Ericsson Internal


<IHIFC:VIF=ETHA-1001,ADD,IP=192.168.1.n,NETMASK=255.255.255.0,ARP=YES;
interface ETHB-1001. See “IHIFC” in reference [45] on page 169.
<IHIFC:VIF=ETHB-1001,ADD,IP=192.168.1.n,NETMASK=255.255.255.0,ARP=YES;

<IHIFP;
<EXIT;
6.13.4 CP Blades
This chapter defines the routing for the VLAN INT-SIG from the CP blades.

C:\>cpls -l

Ericsson Internal


blade.
Note: Choose a BCx blade from chapter 6.13.1 on page 61.
3. Create the following named virtual interface.

<IHIFI:NVIF=INT-SIG;
4. Add the IP address and netmask for the CP blade to the named virtual
interface. See “IHIFC” in reference [45] on page 169.
Note 1: The values for n and m must be the same as used in the HW-DT.
For GEP1 boards and GEP2 boards that are TSC blades:
<IHIFC:NVIF=INT-SIG,ADD,IP=192.168.1.n,NETMASK=255.255.255.0,ARP=YES;
Note 2: Examples of values for n for GEP2 TSC blades are 101 and 102.
For GEP2 boards that are MSC blades:

<IHIFC:NVIF=INT-SIG,ADD,BASEIP=192.168.1.m,NETMASK=255.255.255.0,ARP=YES;
Note 3: The same BASEIP address must be configured for all GEP2 MSC
blades. If m is 102, then for each MSC blade the fourth field in the
automatically allocated IP address from the system will be 102 + u
(see chapter 7.5 on page 158).

<IHIFP;
<EXIT;
7. Repeat step 2 to step 6 in this chapter for all CP blades.

Ericsson Internal

6.14 Definition of Routing Tables for IPonCP for SIG-1 and SIG-2
Note: This chapter is only applicable for APZ 212 55 and GEP1 boards.
This chapter defines the functionality IPonCP for VLAN SIG-1 and SIG-2.

VLANs.
See the document “MSC Server Blade Cluster Network Introduction” in

reference [35] on page 169 for detailed information about the used IP
addresses and the VLANs.
6.14.1 Configuration Layout
Figure 2 Example of Blade Configuration
The customer dependant values are described in reference [48] on page 169.
It can be fetched on the following link:
http://cdmweb.ericsson.se/WEBLINK/ViewDocs?DocumentName=EAB%2FF
T-08%3A0106&Latest=true
6.14.2 SPX1 and SPX2
This chapter defines the routing for the VLANs SIG-1 and SIG-2 from SPX1
and SPX2.
Ericsson Internal


C:\>cpls -l
6.14.2.1 SPX1




Ericsson Internal


6. Add the IP address and netmask for SPX1 on VLAN SIG-1 to the virtual
Note 1: The IP address is a public one and needs to be unique for the
customer. If unknown, omit this step.
<IHIFC:VIF=ETHA-2001,ADD,IP=<IP address>,NETMASK=<netmask>,ARP=YES;
For example:
<IHIFC:VIF=ETHA-2001,ADD,IP=193.180.18.58,NETMASK=255.255.255.192,ARP=YES;
Note 2: The IP address has to be on another subnet than the IP addresses

for ETHA-2002 in the next step. The netmask in the example is
26 bits.
Note 3: This IP address will automatically also be used by ETHB-2001.
For example:

for ETHA-2001 in the previous step. The netmask in the example is
26 bits.

<IHIFP;

Ericsson Internal


9. Initiate router supervision from ETH-2001 towards IPLB1/ISER1 and
IPLB2/ISER2 over VLAN SIG-1. See “IHRSI” in reference [41] on page 169.
Note 1: The IP addresses are public ones and need to be unique for the
<IHRSI:VIFP=ETH-2001,GW=<GW IP addresses for for IPLB1&IPLB2 or SER1&ISER2>,

PINGA=<IP address A>,PINGB=<IP address B>,IPMIGR=YES,TTL=1,HOFF=5;
For example:
<IHRSI:VIFP=ETH-2001,GW=193.180.18.61&193.180.18.62,
PINGA=193.180.18.54,PINGB=193.180.18.55,IPMIGR=YES,TTL=1,HOFF=5;
Note 2: The PINGx IP addresses have to be on another subnet than the

PINGx IP addresses for ETH-2002 in the next step.

<IHRSI:VIFP=ETH-2002,GW=<GW IP addresses for IPLB1&IPLB2 or ISER1&ISER2>,

For example:
<IHRSI:VIFP=ETH-2002,GW=193.180.18.125&193.180.18.126,

PINGx IP addresses for ETH-2001 in the previous step.
11. Print the router supervision.

See “IHRSP” in reference [42] on page 169.
<IHRSP;
Printout: ROUTER SUPERVISION DATA
Note: STATE must be WO, which means full contact with IPLB/ISER
over ETHA and ETHB. NOW=HOME means that the current
location of the IP address is at the primary interface (ETHA-2001
and ETHA-2002).
Ericsson Internal


12. Define a Route from ETHA-2001 over VLAN SIG-1 via IPLB1/ISER1.
See “IHRHC” in reference [39] on page 169.
<IHRHC:VIF=ETHA-2001,ADD,DEST=<dest IP address>,
NETMASK=<netmask>,GW=<GW IP address>,PREF=120;
For example:
<IHRHC:VIF=ETHA-2001,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.61,PREF=120;
Note 2: GW is the IP address for IPLB1/ISER1. DEST is the IP address

for the external network. NETMASK is for DEST.
Note 3: A higher value on PREF gives a higher priority.
13. Define a Route from ETHB-2001 over VLAN SIG-1 via IPLB1/ISER1.
<IHRHC:VIF=ETHB-2001,ADD,DEST=<dest IP address>,
For example:
<IHRHC:VIF=ETHB-2001,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.61,PREF=80;

Note 3: A lower value on PREF gives a lower priority.
Note 4: This step requires that step 9 in this chapter has been
performed, since there must be at least one IP address defined
also for ETHB-2001 (PINGB).
Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.62,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.62,PREF=120;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.125,PREF=120;

customer. If unknown, omit this step. NETMASK is for DEST.
For example:
NETMASK=255.255.0.0,GW=193.180.18.125,PREF=80;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.126,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.126,PREF=120;

20. Print the routing table definitions.

See “IHRHP” in reference [40] on page 169.
<IHRHP;
Printout: ROUTE HANDLING

Ericsson Internal


21. Ping from ETHA-2001 towards IPLB1/ISER1 over VLAN SIG-1.
See “IHNPI” in reference [43] on page 169.
Note: The IP address is a public one and needs to be unique for the
<IHNPI:DEST=<dest IP address>,VIF=ETHA-2001,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.61,VIF=ETHA-2001,CNT=3,WAIT=20;
Printout: PING DATA
22. Ping from ETHB-2001 towards IPLB1/ISER1 over VLAN SIG-1.

<IHNPI:DEST=<dest IP address>,VIF=ETHB-2001,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.61,VIF=ETHB-2001,CNT=3,WAIT=20;
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA
<EXIT;
6.14.2.2 SPX2

Ericsson Internal




For example:

for ETHA-2002 in the next step. The netmask in the example is
26 bits.

Ericsson Internal


For example:

for ETHA-2001 in the previous step. The netmask in the example is
26 bits.

<IHIFP;

<IHRSI:VIFP=ETH-2001,GW=<GW IP addresses for ISER1&ISER2>,

PINGA=<IP address A>,PINGB=<IP address B>,IPMIGR=YES,TTL=1,
HOFF=5;
For example:
<IHRSI:VIFP=ETH-2001,GW=193.180.18.61&193.180.18.62,
PINGA=193.180.18.56,PINGB=193.180.18.57,IPMIGR=YES,TTL=1,
HOFF=5;

PINGx IP addresses for ETH-2002 in the next step.
Ericsson Internal



For example:
<IHRSI:VIFP=ETH-2002,GW=193.180.18.125&193.180.18.126,

PINGx IP addresses for ETH-2001 in the previous step.

<IHRSP;
location of the IP address is at the primary interface (ETHA-2001
and ETHA-2002).
For example:
NETMASK=255.255.0.0,GW=193.180.18.61,PREF=120;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.61,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.62,PREF=80;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.62,PREF=120;

For example:
NETMASK=255.255.0.0,GW=193.180.18.125,PREF=120;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.125,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.126,PREF=80;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.126,PREF=120;


<IHRHP;

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.14.3 TSC Blades
This chapter defines the routing for the VLANs SIG-1 and SIG-2 from the TSC
blades.
See Figure 2 on page 65 in chapter 6.14.1 “Configuration Layout”.
Note: Only routing for TSC blades are defined.

C:\>cpls -l
2. Enter an MML command session from a WinFIOL terminal towards a TSC

blade.
C:\>mml -cp <cpname> -a

Ericsson Internal


3. Create the following named virtual interfaces.
<IHIFI:NVIF=SIG-1;
<IHIFI:NVIF=SIG-2;
4. Add the IP address and netmask for the TSC blade to the named virtual
interfaces. See “IHIFC” in reference [45] on page 169.
Note 2: The IP addresses and the netmask must be the same as are used
in the HW-DT.
<IHIFC:NVIF=SIG-1,ADD,IP=<IP address>,NETMASK=<netmask>,ARP=YES;
<IHIFC:NVIF=SIG-2,ADD,IP=<IP address>,NETMASK=<netmask>,ARP=YES;
Example of IP addresses for SIG-1: 193.180.18.1, 193.180.18.2.

Example of IP addresses for SIG-2: 193.180.18.65, 193.180.18.66.
Example of netmask: 255.255.255.192.
Note 3: The IP address for SIG-1 has to be on another subnet than the IP
address for SIG-2. The netmask in the example is 26 bits.

<IHIFP;

Ericsson Internal


6. Define a Route from the TSC blade over VLAN SIG-1 via IPLB1/ISER1.
<IHRHC:NVIF=SIG-1,ADD,DEST=<dest IP address>,
For example:
<IHRHC:NVIF=SIG-1,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.61,PREF=120;

For example:
NETMASK=255.255.0.0,GW=193.180.18.62,PREF=80;


Ericsson Internal


Note 1: This step is only applicable for GEP1 boards.
For example:
NETMASK=255.255.0.0,GW=193.180.18.125,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.126,PREF=120;


<IHRHP;

Ericsson Internal


11. Ping from the TSC blade towards IPLB1/ISER1 over VLAN SIG-1.
<IHNPI:DEST=<dest IP address>,NVIF=SIG-1,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.61,NVIF=SIG-1,CNT=3,WAIT=20;
Printout: PING DATA
For example:
Printout: PING DATA
For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
16. Repeat step 2 to step15 in this chapter for all TSC blades.
6.15 Definition of Routing Tables for IPonCP for BC-SIG
This chapter defines the functionality IPonCP for VLAN BC-SIG.

VLANs.

addresses and the VLANs when ISER is used.

reference [37] on page [37] for detailed information about the used IP
addresses and the VLANs when IPLB is used.
See the document “Factory Start Up and Initial NE Test of a CP Cluster” in

reference [38] on page 169 for detailed information about used IP addresses.
Ericsson Internal


This chapter defines the routing for VLAN BC-SIG from SPX1 and SPX2.

C:\>cpls -l
6.15.2.1 SPX1
C:\>mml -cp CP1 -a

Ericsson Internal



4. Add the IP address and netmask for SPX1 on VLAN BC-SIG to the virtual
Note 2: The command must be entered twice:

Once for externally advertised subnet BC-SIG-1,
and once for externally advertised subnet BC-SIG-2.
They are both part of subnet BC-SIG.
For example:
Note 3: The netmask in the example is 27 bits.

<IHIFP;

Ericsson Internal


IPLB2/ISER2 over VLAN BC-SIG. See “IHRSI” in reference [41] on page 169.
Note 2: If there are two IPLB pairs, it is the IP addresses for the IPLB
pair in IS1 that must be used.

For example:
<IHRSI:VIFP=ETH-2001,GW=193.180.18.29&193.180.18.30,

<IHRSP;
location of the IP address is at the primary interface (ETHA-2001).
8. Define a Route from ETHA-2001 over VLAN BC-SIG via IPLB1/ISER1.

For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=120;


Ericsson Internal


9. Define a Route from ETHB-2001 over VLAN BC-SIG via IPLB1/ISER1.
For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=80;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=120;


<IHRHP;
13. Ping from ETHA-2001 towards IPLB1/ISER1 over VLAN BC-SIG.

For example:
Printout: PING DATA

Ericsson Internal

14. Ping from ETHB-2001 towards IPLB1/ISER1 over VLAN BC-SIG.

For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.15.2.2 SPX2


Ericsson Internal


4. Add the IP address and netmask for SPX2 on VLAN BC-SIG to the virtual

Once for externally advertised subnet BC-SIG-1,
and once for externally advertised subnet BC-SIG-2.
They are both part of subnet BC-SIG.
For example:

<IHIFP;

IPLB2/ISER2 over VLAN BC-SIG. See “IHRSI” in reference [41] on page 169.

For example:
<IHRSI:VIFP=ETH-2001,GW=193.180.18.29&193.180.18.30,
Ericsson Internal


<IHRSP;
location of the IP address is at the primary interface (ETHA-2001).

For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=120;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=80;

For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=80;


Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=120;


<IHRHP;

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.15.3 TSC Blades
This chapter defines the routing for VLANs BC-SIG from the TSC blades.

C:\>cpls -l

blade.

Ericsson Internal


<IHIFI:NVIF=BC-SIG;
in the HW-DT.

Once for BC-SIG-1 and once for BC-SIG-2.
<IHIFC:NVIF=BC-SIG,ADD,IP=<IP address>,NETMASK=<netmask>,ARP=YES;
Example of IP addresses for BC-SIG (BC-SIG-1): 193.180.18.1, 193.180.18.2.

Example of IP addresses for BC-SIG (BC-SIG-2): 193.180.18.17, 193.180.18.18.

<IHIFP;

Ericsson Internal


6. Define a Route from the TSC blade over VLAN BC-SIG via IPLB’s/ISER’s
VRRP. See “IHRHC” in reference [39] on page 169.

Once for IPLB’s/ISER’s VRRP for BC-SIG-1,
and once for ISER’s VRRP for BC-SIG-2.
Note 3: If there are two IPLB pairs, it is the IP addresses for the IPLB pair
in IS1 that must be used.
<IHRHC:NVIF=BC-SIG,ADD,DEST=<dest IP address>,
NETMASK=<netmask>,GW=<GW IP address>,PREF=<pref>;
For example:
<IHRHC:NVIF=BC-SIG,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.12,PREF=120;
<IHRHC:NVIF=BC-SIG,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.28,PREF=80;
Note 4: GW is the IP address for IPLB’s/ISER’s VRRP (BC-SIG-1 or

BC-SIG-2). DEST is the IP address for the external network.
NETMASK is for DEST.

<IHRHP;

Ericsson Internal


8. Ping from the TSC blade towards VRRP for IPLB1/ISER1 over VLAN BC-SIG.
<IHNPI:DEST=<dest IP address>,NVIF=BC-SIG,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.12,NVIF=BC-SIG,CNT=3,WAIT=20;
Printout: PING DATA
9. Ping from the TSC blade towards VRRP for IPLB2/ISER2 over VLAN BC-SIG.
<IHNPI:DEST=<dest IP address>,NVIF=BC-SIG,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.28,NVIF=BC-SIG,CNT=3,WAIT=20;
Printout: PING DATA
<EXIT;
11. Repeat step 2 to step 10 in this chapter for both TSC blades.
Ericsson Internal


6.16 Definition of Routing Tables for IPonCP for BC-SIG-EXT1
Note: This chapter is only applicable for APZ 212 60 and GEP2 boards
and if IPLB is used instead of ISER.
This chapter defines the functionality IPonCP for VLAN BC-SIG-EXT1.

VLANs.


This chapter defines the routing for VLAN BC-SIG-EXT1 from SPX1 and
SPX2.

C:\>cpls -l
6.16.1.1 SPX1
C:\>mml -cp CP1 -a


Ericsson Internal

4. Add the IP address and netmask for SPX1 on VLAN BC-SIG-EXT1 to the
virtual interface ETHA-2002. See “IHIFC” in reference [45] on page 169.

Once for externally advertised subnet BC-SIG-1-EXT1,
and once for externally advertised subnet BC-SIG-2-EXT1.
They are both part of subnet BC-SIG-EXT1.
For example:

<IHIFP;
6. Initiate router supervision from ETH-2002 towards IPLB1 and IPLB2 over
VLAN BC-SIG-EXT1. See “IHRSI” in reference [41] on page 169.
<IHRSI:VIFP=ETH-2002,GW=<GW IP addresses for IPLB1&IPLB2>,

For example:
<IHRSI:VIFP=ETH-2002,GW=193.180.18.29&193.180.18.30,
Ericsson Internal


<IHRSP;
Note: STATE must be WO, which means full contact with IPLB over
ETHA and ETHB. NOW=HOME means that the current location of
the IP address is at the primary interface (ETHA-2002).
8. Define a Route from ETHA-2002 over VLAN BC-SIG-EXT1 via IPLB1.

For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=120;
Note 3: GW is the IP address for IPLB1. DEST is the IP address for the
external network. NETMASK is for DEST.

Ericsson Internal


9. Define a Route from ETHB-2002 over VLAN BC-SIG-EXT1 via IPLB1.
For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=80;
For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=80;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=120;

<IHRHP;
13. Ping from ETHA-2002 towards IPLB1 over VLAN BC-SIG-EXT1.

For example:
Printout: PING DATA

Ericsson Internal

14. Ping from ETHB-2002 towards IPLB1 over VLAN BC-SIG-EXT1.

For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.16.1.2 SPX2


Ericsson Internal



For example:

<IHIFP;

For example:
<IHRSI:VIFP=ETH-2002,GW=193.180.18.29&193.180.18.30,
Ericsson Internal


<IHRSP;

For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=120;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=80;
For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=80;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=120;

<IHRHP;

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.16.2 TSC Blades
This chapter defines the routing for VLANs BC-SIG-EXT1 from the TSC
blades.

C:\>cpls -l

blade.

Ericsson Internal


<IHIFI:NVIF=BC-SIG-EXT1;
in the HW-DT.
Note 3: The command must be entered twice.

Once for BC-SIG-1-EXT1 and once for BC-SIG-2-EXT1.
<IHIFC:NVIF=BC-SIG-EXT1,ADD,IP=<IP address>,NETMASK=<netmask>,ARP=YES;
Example of IP addresses for BC-SIG-EXT1 (BC-SIG-1-EXT1): 193.180.18.1, 193.180.18.2.


<IHIFP;

Ericsson Internal


6. Define a Route from the TSC blade over VLAN BC-SIG-EXT1 via IPLB’s
Note 2: The command must be entered twice, once for IPLB’s VRRP for
SIG-1 and once for IPLB’s VRRP for SIG-2.
<IHRHC:NVIF=BC-SIG-EXT1,ADD,DEST=<dest IP address>,
For example:
<IHRHC:NVIF=BC-SIG-EXT1,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.12,PREF=120;
NETMASK=255.255.0.0,GW=193.180.18.28,PREF=80;
Note 4: GW is the IP address for IPLB’s VRRP (BC-SIG-1-EXT1 or

BC-SIG-2-EXT1). DEST is the IP address for the external network.

<IHRHP;

Ericsson Internal


8. Ping from the TSC blade towards VRRP for IPLB1 over VLAN BC-SIG-EXT1.
<IHNPI:DEST=<dest IP address>,NVIF=BC-SIG-EXT1,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.12,NVIF=BC-SIG-EXT1,CNT=3,WAIT=20;
Printout: PING DATA
For example:
Printout: PING DATA
<EXIT;
Ericsson Internal

6.17 Definition of Routing Tables for IPonCP for BC-SIG-EXT2
This chapter defines the functionality IPonCP for VLAN BC-SIG-EXT2.

VLANs.


This chapter defines the routing for VLAN BC-SIG-EXT2 from SPX1 and
SPX2.

C:\>cpls -l
6.17.1.1 SPX1
C:\>mml -cp CP1 -a

Ericsson Internal



For example:

<IHIFP;

Ericsson Internal



For example:
<IHRSI:VIFP=ETH-2006,GW=193.180.18.29&193.180.18.30,

<IHRSP;

For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=120;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=80;
For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=80;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=120;

<IHRHP;

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.17.1.2 SPX2


Ericsson Internal



For example:

<IHIFP;

For example:
<IHRSI:VIFP=ETH-2006,GW=193.180.18.29&193.180.18.30,
Ericsson Internal


<IHRSP;

For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=120;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.29,PREF=80;
For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=80;

Ericsson Internal


For example:
NETMASK=255.255.0.0,GW=193.180.18.30,PREF=120;

<IHRHP;

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA

For example:
Printout: PING DATA

Ericsson Internal


For example:
Printout: PING DATA
<EXIT;
6.17.2 TSC Blades
This chapter defines the routing for VLANs BC-SIG-EXT2 from the TSC
blades.

C:\>cpls -l

blade.

Ericsson Internal


<IHIFI:NVIF=BC-SIG-EXT2;
in the HW-DT.

Once for BC-SIG-1-EXT2 and once for BC-SIG-2-EXT2.
<IHIFC:NVIF=BC-SIG-EXT2,ADD,IP=<IP address>,NETMASK=<netmask>,ARP=YES;


<IHIFP;

Ericsson Internal


6. Define a Route from the TSC blade over VLAN BC-SIG-EXT2 via IPLB’s

Once for IPLB’s VRRP for BC-SIG-1-EXT2,
and once for IPLB’s VRRP for BC-SIG-2-EXT2.
<IHRHC:NVIF=BC-SIG-EXT2,ADD,DEST=<dest IP address>,
For example:
NETMASK=255.255.0.0,GW=193.180.18.12,PREF=120;
NETMASK=255.255.0.0,GW=193.180.18.28,PREF=80;
Note 4: GW is the IP address for IPLB’s VRRP (BC-SIG-1 or BC-SIG-2).

DEST is the IP address for the external network.

<IHRHP;

Ericsson Internal


For example:
Printout: PING DATA
For example:
Printout: PING DATA
<EXIT;
Ericsson Internal


6.18 Definition of Routing Tables for IPonCP for BC-SIP
This chapter defines the functionality IPonCP for VLAN BC-SIP.

VLANs.




Ethernet
Link
Aggregation
Group (LAG)
Static Route 193.180.18.34..42

BFD Session MSC-S BC Site
MSC-S
MSC-S
AS (SPX1) IS
R-P1
ISER1 #0
SCB EXB MXB SE1
VRIP: 193.180.18.92 L2 Switch 1
CPUB
CPUB
0A
#0
Backbone
SCB EXB MXB ISER2 #1

L
R-P2
SE2
L2 Switch 2
1A
APUB
1B
APUB
Presentation of Static Routes
Note that static routes are depicted as “bi-directional” routes for
simplicity. In fact one double arrow stands for two independent static
routes defined in the end-points towards the according opposite.
Ericsson Internal


6.18.2 MSC Blades
This chapter defines the routing for VLANs BC-SIP from the MSC blades.
Note: Only routing for MSC blades are defined.

C:\>cpls -l
2. Enter an MML command session from a WinFIOL terminal towards an MSC

blade.

<IHIFI:NVIF=BC-SIP;
4. Add the BASEIP address and netmask for the MSC blade to the named virtual
in the HW-DT.
<IHIFC:NVIF=BC-SIP,ADD,BASEIP=193.180.18.n,NETMASK=255.255.255.192,ARP=YES;
Note 3: The value for n must be the same as used in the HW-DT.
blades. If n is 33, then for each MSC blade the fourth field in the
Ericsson Internal


<IHIFP;
6. Define a Route from the MSC blade over VLAN BC-SIP via IPLB’s/ISER’s
<IHRHC:NVIF=BC-SIP,ADD,DEST=<dest IP address>,
For example:
<IHRHC:NVIF=BC-SIP,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.92,PREF=100;
Note 2: GW is the IP address for IPLB’s/ISER’s VRRP. DEST is the IP

address for the external network. NETMASK is for DEST.

<IHRHP;
8. Ping from the MSC blade towards VRRP for IPLB1/ISER1 over VLAN BC-SIP.
<IHNPI:DEST=<dest IP address>,NVIF=BC-SIP,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.92,NVIF=BC-SIP,CNT=3,WAIT=20;
Printout: PING DATA

Ericsson Internal

<EXIT;
10. Repeat step 2 to step 9 in this chapter for all MSC blades.
6.19 Definition of Routing Tables for IPonCP for BC-DNS
This chapter defines the functionality IPonCP for VLAN BC-DNS.

VLANs.



Ericsson Internal



Ethernet
Link
Aggregation
Group (LAG)
Static Route 193.180.18.98..106

BFD Session MSC-S BC Site
MSC-S
MSC-S
AS (SPX1) IS
R-P1
ISER1 #0
SCB EXB MXB SE1
VRIP: 193.180.18.156 L2 Switch 1
CPUB
CPUB
0A
#0
Backbone
SCB EXB MXB ISER2 #1

L
R-P2
SE2
L2 Switch 2
1A
APUB
1B
APUB
Presentation of Static Routes
Note that static routes are depicted as “bi-directional” routes for
simplicity. In fact one double arrow stands for two independent static
routes defined in the end-points towards the according opposite.
6.19.2 MSC Blades
This chapter defines the routing for VLAN BC-DNS from the MSC blades.

C:\>cpls -l

blade.

Ericsson Internal


<IHIFI:NVIF=BC-DNS;
in the HW-DT.
<IHIFC:NVIF=BC-DNS,ADD,BASEIP=193.180.18.n,NETMASK=255.255.255.192,ARP=YES;

<IHIFP;

Ericsson Internal


6. Define a Route from the MSC blade over VLAN BC-DNS via IPLB’s/ISER’s
<IHRHC:NVIF=BC-DNS,ADD,DEST=<dest IP address>,
For example:
<IHRHC:NVIF=BC-DNS,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.156,PREF=100;


<IHRHP;
8. Ping from the MSC blade towards VRRP for IPLB1/ISER1 over VLAN
BC-DNS. See “IHNPI” in reference [43] on page 169.
<IHNPI:DEST=<dest IP address>,NVIF=BC-DNS,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.156,NVIF=BC-DNS,CNT=3,WAIT=20;
Printout: PING DATA
<EXIT;
Ericsson Internal


6.20 Definition of Routing Tables for IPonCP for BC-BLD-EXT1
This chapter defines the functionality IPonCP for VLAN BC-BLD-EXT1.

VLANs.


6.20.1 MSC Blades
This chapter defines the routing for VLAN BC-BLD-EXT1 from the MSC
blades.

C:\>cpls -l

blade.

<IHIFI:NVIF=BC-BLD-EXT1;
Ericsson Internal


in the HW-DT.
<IHIFC:NVIF=BC-BLD-EXT1,ADD,BASEIP=193.180.18.n,NETMASK=255.255.255.192,ARP=YES;

<IHIFP;
6. Define a Route from the MSC blade over VLAN BC-BLD-EXT1 via
IPLB’s/ISER’s VRRP. See “IHRHC” in reference [39] on page 169.
<IHRHC:NVIF=BC-BLD-EXT1,ADD,DEST=<dest IP address>,
For example:
<IHRHC:NVIF=BC-BLD-EXT1,ADD,DEST=10.180.0.0,
NETMASK=255.255.0.0,GW=193.180.18.156,PREF=100;


Ericsson Internal


<IHRHP;
8. Ping from the MSC blade towards VRRP for IPLB1/ISER1 over VLAN
BC-BLD-EXT1. See “IHNPI” in reference [43] on page 169.
<IHNPI:DEST=<dest IP address>,NVIF=BC-BLD-EXT1,CNT=3,WAIT=20;
For example:
<IHNPI:DEST=193.180.18.156,NVIF=BC-BLD-EXT1,CNT=3,WAIT=20;
Printout: PING DATA
<EXIT;
6.21 Perform System Backup Copies

C:\>cpls -l
2. Open an MML session to a CP blade.

Ericsson Internal


3. Prepare output of a system backup copy to RELFSW2 ( that is to the highest
defined reload file in an unbroken sequence of files):
<SYBUP:FILE;
Release the terminal by entering <CTRL-D>
Printout: OUTPUT TO FILE RELFSW2
Accept the proposed file and give order for execution with semicolon (;).
ORDERED
Printout: BACKUP INFORMATION OUTPUT PROGRESS

Printout: BACKUP INFORMATION OUTPUT
Wait until finished.
<EXIT;

Ericsson Internal

7 HELPFUL HINTS
7.1 Information Displayed by a CDU
Information Displayed by a CP Display Unit (CDU). The CDU is only for the
SPX. To get these values for the CP blades, the CPT command PTCRP has
to be used. See “PTCRP” in reference [16] on page 167.
cpt<PTCRP:PRO=GPR,REG=CDU; or
cpt<PTCRP:CP=<cpid>,PRO=GPR,REG=CDU;
Compare the received values with the following subchapters. For more
information, see “CDU Register, Handling” in reference [49] on page 169.
7.1.1 Left-Most Digit, Encoding
Table 1
Value Behaviour Activity in progress
0 On System restart, or system start
3 Flashing Loading of Central Processor (CP)
3 On Loading of CP, CP is waiting for a reply from

the equipment used for Loading
8 On Remote upgrade of firmware is invoked
9 On Loading of CP, fault has been detected
Note: A display value is only shown, if the function to show it is

implemented in the CP.
Ericsson Internal


7.1.2 Numerical Value, Intervals
Table 2
Lower Higher Description

Limit Limit
000 254 Absolute start/restart phase
7.1.3 Numerical Values, during Loading of CP
Table 3
Value Activity in progress
300 Initiate loading
320 Loading of dump from Main Store (MS)
340 Loading of file Backup Info
341 Loading of file Small Data Dump (SDD).
343 Loading of file Large Data Dump (LDD).
345 Loading of file Program Store (PS).
346 Loading of file Reference Store (RS).
371 Consistency check of Backup area.
372 Loading of APZ stores
380 Finished, halted after initial loading
390 Finished
Ericsson Internal


7.1.4 Numerical Values, during remote Upgrade of Firmware
Last digit is 0: It has finished successfully.

Last digit is 1: It is in progress.
Last digit is 9: Error occurred.
Table 4
Value Activity
800 Firmware remote handler finished successful
801 Firmware upgrade is in progress
809 Error during firmware upgrade
810 Firmware upgrade of Central Processor Unit Board (CPUB)

Intelligent Platform Management Interface (IPMI) is finished
successful
811 Firmware upgrade of CPUB IPMI is in progress
819 Error during firmware upgrade of CPUB IPMI
820 Firmware upgrade of CPUB Basic Input Output System

(BIOS) is finished successful
821 Firmware upgrade of CPUB BIOS is in progress
829 Error during firmware upgrade of CPUB BIOS

Ericsson Internal


7.1.5 Numerical Values, when a Fault is detected during CP Loading
Table 5
Value Fault description
970 Data Store (DS) exceeded while loading segment
971 PS exceeded while loading segment
972 RS exceeded while loading segment
973 Fatal program error at loading to APZ stores
974 Fatal program error at unpacking to DS
975 Fatal program error in Backup services
976 Fatal program error in File Transfer services
977 Fatal program error while loading
978 Insufficient memory size for PS
979 Insufficient memory size for RS
97A Insufficient memory size for LDD
990 Connection with File Transfer Protocol (FTP) server lost
991 Connection with Backup server lost
992 Connect to FTP server failed
993 Connect to Backup server failed
994 Response time-out from Backup server
995 Response time-out from FTP server
996 System Backup Copy was not found
997 System Backup Copy reservation failed
998 System Backup Copy identity out of range
999 Subfile error
99A Backup server is being shutdown
99B Unsupported Backup protocol version

Ericsson Internal

99C File does not exist FTP error
99D Directory does not exist FTP error
99E Invalid user name or password FTP error
99F Unknown FTP error
9A0 Fatal program error in Backup server
9A1 Fatal program error in FTP server
9A2 No progress at reading subfile
9B0 No large data dump segment found in backup area
9B1 No program store segment found in backup area
9B2 No reference store segment found in backup area
9B3 Checksum error in segment headers
9B4 Checksum error in segment data
9B5 Checksum error in special segment
9B6 Illegal block number at unpacking to DS
9B7 Illegal base address number at unpacking to DS
9B8 Fatal error in header
9B9 Incompatible Virtual Machine (VM) and loaded dump
9BA Running firmware not corresponding to identity stored on

dump
9BB Max dump or load in progress

Ericsson Internal


7.2 CP Cluster States
Table 6
State Description
Active CP is a cluster member from both APZ and APT point of

view. It is part of the Quorum.
Intermediate CP is temporarily not sending heartbeats (for example at

FC, fault or APZ maintenance).
Non-op The CP is out of operation and not sending heartbeats.
Passive CP is a cluster member from APZ point of view, but

unknown to APT. It is part of the Quorum.
Small restart CP is doing a small restart.
Undefined The Quorum has no information about the CP.
7.3 IP Addresses of the APG43
When using the eGEM backplane network, it is important that it is knows on

which APG43 they are running since we have a two-APG43 configuration for
BC. Table 7 shows which IP addresses are allocated for each APG43. It is
suggested that SPOE addresses are allocated as described in the table.
Table 7
APG43 Side A Side B SPOE Address

(1) (3)
AP 1 192.168.169.1 192.168.169.2 192.168.169.33
(2) (4)
192.168.170.1 192.168.170.2 192.168.170.33
(5) (7)
AP 2 192.168.169.3 192.168.169.4 192.168.169.34
(6) (8)
192.168.170.3 192.168.170.4 192.168.170.34
. . . .
AP 16 192.168.169.31 192.168.169.32 192.168.169.50

192.168.170.31 192.168.170.32 192.168.170.50
(1) - (8)
are described on the figure on the next page.
Ericsson Internal


Ericsson Internal


7.4 CP Blades Configuration for APZ 212 55
Table 8 Fully CP blades equipped IS magazine.
IS1 IS2
S: 5 7 9 18 20 22 1 3 5 7 9 13 15 17 19 21 23
-u 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
BC 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
IP1 A B C D E F G H I J K L M N O P Q
IP2 A B C D E F G H I J K L M N O P Q
Table 9 Delivered CP blades equipped IS magazine.
IS1 IS2
S: 5 7 9 18 20 22 - 3 - 7 - 13 - 17 - - -
-u 0 1 2 3 4 5 7 9 11 13
BC 0 1 2 3 4 5 7 9 11 13
IP1 A B C D E F H J L N
IP2 A B C D E F H J L N
S: The slot position that can contain a CP blade.
-u: The sequential number used in the command hwcadd. (See

reference [5] on page 167.) The value for –u is chosen as in the
tables above so that all systems get the same values for the
same slot positions, independent of used configuration. -u is
also CPID in command cpch. (See reference [11] on page 167.)
BC: cpname (BC<digit>) received in command cpls. For example,

BC2 and BC3 are TSC-blades, and the rest are MSC-blades.
(See reference [12] on page 167.)
IP1: Public IP address for VLAN SIG-1. Must be unique.
IP2: Public IP address for VLAN SIG-2. Must be unique.
For detailed information for IS1, see “Blade Cluster Cabinet 1, BFM 107 1029”
in reference [31] on page 168.
For detailed information for IS2, see “Blade Cluster Cabinet 2, BFM 107 1031”
in reference [32] on page 168.
Ericsson Internal


7.5 CP Blades Configuration for APZ 212 60
Note: This chapter is not valid after APZ 16.0.
Table 10 Maximum CP blades equipped IS magazine.
IS1 IS2
S: 5 9 11 17 21 23 1 3 5 9 11 13 15 17 21 23
-u 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
BC 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
IP1 A B C D E F G H I J K L M N O P
Table 11 Minimum CP blades equipped IS magazine (no IS2).
IS1
S: 5 9 11 17 21 -
-u 0 1 2 3 4
BC 0 1 2 3 4
IP1 A B C D E
S: The slot position that can contain a CP blade.
-u: The sequential number used in the command hwcadd. (See

reference [5] on page 167.) The value for -u is chosen as in the
tables above so that all systems get the same values for the
same slot positions, independent of used configuration. -u is
also CPID in command cpch. (See reference [11] on page 167.)
BC: cpname (BC<digit>) received in command cpls. For example,

BC0 and BC3 are TSC-blades if TSC-blades are used, and the
rest are MSC-blades. (See reference [12] on page 167.)
IP1: Public IP address for VLAN BC-SIG. Must be unique.
For detailed information for IS1, see “Dynamic AGO, Blade Cluster 2.0
Cabinet 1” in reference [33] on page 168.
For detailed information for IS2, see “Dynamic AGO, Blade Cluster 2.0
Cabinet 2” in reference [34] on page 168.
Ericsson Internal


7.6 CSBIN
The service ACS_MODD_SERVICE (MODDBIN) is used in clone images in

APG43, that do not support BC (multiple CP system).
ACS_CS_SERVICE_0 (CSBIN) on the A-side and ACS_CS_SERVICE_1

(CSBIN) on the B-side replace ACS_MODD_SERVICE (MODDBIN) in clone
images in APG43 that support BC.
It is possible to check whether CSBIN or MODDBIN is used in the APG43 in

the following way.
C:\>swrprint csbin
C:\>swrprint moddbin
If information about csbin is received, the service ACS_CS_SERVICE_X must

be used instead of the service ACS_MODD_SERVICE. If so,
ACS_CS_SERVICE_X must be used in all the steps where
ACS_MODD_SERVICE is used.
If not, but information about moddbin is received, the service

ACS_MODD_SERVICE must be used instead of the service
ACS_CS_SERVICE_X.
Ericsson Internal


7.7 Manual Rotation of RELFSW Files
When rotating backup files in the APG43 using SYTUC some tests are done
with aspects to dump file date and contents.
At start-up it might not be allowed to rotate the files, for instance if some of the
files are defined but empty. In this case a manual rotation can be done.
Note: This procedure must never be used in a live switch!
1. Rename the file to be switched to DUMMY.
<APLOC;
C:\>cpfrename -cp <cpname> relfsw2 dummy
2. Rename the file RELFSW0 to RELFSW2.
C:\>cpfrename -cp <cpname> relfsw0 relfsw2
3. Rename the file DUMMY to RELFSW0.
C:\>cpfrename -cp <cpname> dummy relfsw0
C:\>exit
The files RELFSW2 and RELFSW0 are now switched.

Ericsson Internal


7.8 LEDs
In the IS system, visual indicators are used to display the status of each
blade. There are two types of blades depending on which type of
maintenance bus they use. One blade type uses the legacy M-bus which only
has one LED marked MIA (Manual Intervention Allowed), which lights up
when you lock the blade. See Table 12.
Table 12 One LED blade.
Yellow LED Meaning
OFF The blade is unlocked and in service. It must not be removed. (The blade
could also be malfunctioning so that the LED does not light up, but that is
very unlikely.
ON The blade is locked and can be removed.
The other blade uses the IPMI bus and has three LEDs mounted on the front
of each blade. See Table 13.
Table 13 Three LED blades.
Green LED Red LED Yellow LED Meaning
OFF - - The blade internal voltage levels are not

correct.
ON OFF OFF The blade is unlocked and in service. It must

not be removed.
ON OFF ON The blade is locked and can be removed.
ON ON OFF The slot has not been configured, the blade

has been installed in the wrong slot, or there is
an alarm on the blade.
The following is valid for the CP blades:
The upper green LED indicates main power.
The middle red LED, System Not Connected (SNC), is not used by the APZ
but might be temporarily lit after, for example, power-up or board
replacement.
The bottom yellow LED is the MIA indicator.

Ericsson Internal


7.9 STRABs
There are three STRABs used for the subrack address.
They are located on position 0 on the left side of each eGEM. There are four
slots which will accept the strap boards in the positions 00/10, 00/25, 00/40
and 00/55. The RP addressing is performed by a strap board in the position
00/55. The eGEM identity information is performed by strap boards in the
positions 00/10 and 00/40. They get their values according to the group
switch matrix if the eGEM contains XDB/XNB. If not, they get the value zero.
The position 00/25 is not used in normal operation.
In the parameter -m a.b.0.d in command hwcadd, a has the value from

position 00/55 and d the value from position 00/10. Two different IS subracks
must have different values for position 00/55.
Note 1: If an address plug value for an IS subrack is changed, the whole IS

configuration must be performed from the beginning once more.
Each STRAB has a value in the range 0 - 15. They are programmable by
means of a six dip switch, where switches 1 to 5 are used, and switch 6 is not
connected. The subrack address (option -m) is normally 0.0.0.0 for the IS1
subrack and 1.0.0.0 for the IS2 subrack.
Note 2: It is the STRAB information specified in OIT and IE-Select that

must be used. If this information is different from the ones specified
above, it is the information specified in OIT that must be used.
IE-Select generates the document “Strapping Information” 6/19317
which contains the STRAB information which must be used.
Ericsson Internal


7.10 Blade Information for APZ 212 55 and APZ 212 60
Table 14 Blade information.
Name MagAddr FBN SysType SysNo SeqNo

BC0 0.0.0.0 CPUB BC 1 0
BC1 0.0.0.0 CPUB BC 1 1
BC2 0.0.0.0 CPUB BC 1 2
BC3 0.0.0.0 CPUB BC 1 3
BC4 0.0.0.0 CPUB BC 1 4
BC5 0.0.0.0 CPUB BC 1 5
BC6 1.0.0.0 CPUB BC 1 6
BC7 1.0.0.0 CPUB BC 1 7
BC8 1.0.0.0 CPUB BC 1 8
BC9 1.0.0.0 CPUB BC 1 9
BC10 1.0.0.0 CPUB BC 1 10
BC11 1.0.0.0 CPUB BC 1 11
BC12 1.0.0.0 CPUB BC 1 12
BC13 1.0.0.0 CPUB BC 1 13
BC14 1.0.0.0 CPUB BC 1 14
BC15 1.0.0.0 CPUB BC 1 15
BC16 1.0.0.0 CPUB BC 1 16
1.2.0.4 SCB-RP - - 1
CP1(A) 1.2.0.4 CPUB CP 1 -
1.2.0.4 MAUB CP 1 -
CP1(B) 1.2.0.4 CPUB CP 1 -
AP1A 1.2.0.4 APUB AP 1 -
1.2.0.4 Disk AP 1 -
Ericsson Internal

1.2.0.4 DVD AP 1 -
1.2.0.4 Disk AP 1 -
AP1B 1.2.0.4 APUB AP 1 -
1.2.0.4 GEA AP 1 -
1.2.0.4 SCB-RP - - 2
15.2.0.4 SCB-RP - - 3
CP2(A) 15.2.0.4 CPUB CP 2 -
15.2.0.4 MAUB CP 2 -
CP2(B) 15.2.0.4 CPUB CP 2 -
AP2A 15.2.0.4 APUB AP 2 -
15.2.0.4 Disk AP 2 -
15.2.0.4 Disk AP 2 -
AP2B 15.2.0.4 APUB AP 2 -
15.2.0.4 SCB-RP - - 4
Ericsson Internal


7.11 Login to the ISM Web Pages
This chapter is only for production unit and labs, and not for sites.
Open a browser (Mozilla Firefox or Internet Explorer) and enter the IP

address for the SIS blade in the URL field. This can be done when connected
to the Kick start Server.
The following IP addresses are examples, configured in the Kickstart Server.
IP address for SIS1: 192.168.0.25

IP address for SIS2: 192.168.0.26
This will start the ISM for the SIS blade.
Note 1: The IP addresses are the ones for the MAC addresses defined for
the SIS blades in the Dynamic Host Configuration Protocol (DHCP)
file on the Kickstart Server.
Note 2: It is only possible to start ISM by typing the IP address for the
active SIS blade.
Login as expert:
User ID: expert
Password: expert
7.12 Login to the SIS Blade
This chapter is only for production unit and labs, and not for sites.
It is possible to login to the SIS blade, when connected to the Kickstart

Server, by using one of the following two ways:
N -> System -> Terminal -> Konsole (N if Novell Linux is used).
Or
right click -> Run Command… -> enter Konsole (use the <TAB>).
Enter: ssh sid@<IP address for SIS1>

Enter the password: sidsid
If having the prompt "sid@sis1>", enter <CTRL-D> twice to get the "SISx:~#"
prompt.
Ericsson Internal


7.13 Lock/Unlock Blades
To unlock a blade system, go to "Open blade system":
Integrated Site Services -> Hardware.
Under "Configuration" click on "Open Blade systems".
From the "Open blade systems" list click on the table row icon for the blade
system and then click on the Unlock button.
To lock a blade system, go to "Open blade system":
Integrated Site Services -> Hardware.
Under "Configuration" click on "Open Blade systems".
From the "Open blade systems" list click on the table row icon for the blade
system and then click the Lock button.
Ericsson Internal


7.14 References
[1] Factory Start Up and Initial NE Test of APG43,

100/1532-B/AXE 106 99
[2] Factory Start Up and Initial NE Test of APZ 212 55 and

APZ 212 60, 101/1532-B/AXE 106 99
[3] Upgrade of PES and CPHW Dumps,

1543–LZY 201 154
[4] Cable information: GEP,

1070-ROJ 208 800
[5] hwcadd,
1/190 80-CNZ 222 119
[6] hwcls,
2/190 80-CNZ 222 119
[7] hwcrm,
3/190 80-CNZ 222 119
[8] hwcsync,
4/190 80-CNZ 222 119
[9] PTITI,
3/190 82-CNZ 214 300
[10] CPT MESSAGE CLUSTER CP INFORMATION,

4/190 83-CNZ 214 300
[11] cpch,
1/190 80-CNZ 222 132
[12] cpls,
2/190 80-CNZ 222 132
[13] PTCPL,
2/190 82-CNZ 214 300
[14] PTPHS,
4/190 82-CNZ 214 300
[15] PTPHR,
5/190 82-CNZ 214 300
[16] PTCRP,
7/190 82-CNZ 214 300
[17] SYATI,
7/190 82-CNZ 214 241
Ericsson Internal


[18] PTCOI,
1/190 82-CNZ 214 300
[19] PTCPR,
21/190 82-CNZ 214 300
[20] PTCOE,
32/190 82-CNZ 214 300
[21] PTWSP,
30/190 82-CNZ 214 300
[22] PTPEE,
10/190 82-CNZ 214 300
[23] CPT MESSAGE INITIAL TEST RESULT,

1/190 83-CNZ 214 300
[24] CPT MESSAGE INITIAL LOADING (ABSOLUTE) FINISHED,

6/190 83-CNZ 214 300
[25] CPT MESSAGE INITIAL LOADING (ABSOLUTE) HALTED,

7/190 83-CNZ 214 300
[26] CPT MESSAGE INITIAL LOADING (ABSOLUTE) IN

PROGRESS,
8/190 83-CNZ 214 300
[27] CPT MESSAGE INITIAL LOADING (ABSOLUTE) STARTED,

10/190 83-CNZ 214 300
[28] CPT MESSAGE INITIAL LOADING (ABSOLUTE) STOPPED,

11/190 83-CNZ 214 300
[29] Plant Engineering Description

AXE Blade Cluster,
1/194 01-APZ 214 01
[30] Factory Start Up and Initial NE Test of a CP Cluster in IS

Environment, 106/1532-B/AXE 106 99
[31] Blade Cluster Cabinet 1, BFM 107 1029,

1551-BFM 107 1029
[32] Blade Cluster Cabinet 2, BFM 107 1031,

1551-BFM 107 1031
[33] Dynamic AGO, Blade Cluster 2.0 Cabinet 1,

1551-BFM 107 1036
[34] Dynamic AGO, Blade Cluster 2.0 Cabinet 2,

1551-BFM 107 1037
Ericsson Internal


[35] MSC Server Blade Cluster Network Introduction,
16/1553-HSC 113 01/52

16/1553-HSC 113 01/6

16/1553-HSC 113 01/6-L
[38] User guide for MSC Server Blade Cluster Configuration and
Handling, 36/1553-CSA 121 01/2
[39] IHRHC,
5/190 82-CNZ 225 15
[40] IHRHP,
6/190 82-CNZ 225 15
[41] IHRSI,
7/190 82-CNZ 225 15
[42] IHRSP,
10/190 82-CNZ 225 15
[43] IHNPI,
1/190 82-CNZ 225 26
[44] IHIFI,
1/190 82-CNZ 225 15
[45] IHIFC,
2/190 82-CNZ 225 15
[46] IHIFP;
4/190 82-CNZ 225 15
[47] cfeted,
1/190 80-CNZ 225 271
[48] Customer Dependant Values in CP Cluster Environment,

EAB/FT-08:01061
[49] CDU Register, Handling,

8/154 31-CNZ 214 307
[50] cpgdef,
9/190 80-CNZ 222 132
[51] cpgls,
8/190 80-CNZ 222 132
[52] apzvlanls,
11/190 80-CNZ 222 132
Ericsson Internal


[53] MSC Server Blade Cluster,
1951-FAP 199 0079
[54] MSC Server Blade Cluster 2.0,

1074-BFM 107 1036
[55] nels,
3/190 80-CNZ 222 132 S
[56] Concepts and Terminology for MSC Server Blade Cluster,

3/1550-CSA 121 01/2.
[57] Concepts and Terminology for Blade Cluster in APZ,

0033-APZ 214 03/127
8 Revision Information
Table 15
Rev Date Author Reason
A 2008-09-22 UABINGE This is the first revision
B 2009-03-26 UABINGE APZ 212 60 is introduced.

It is specified that the CP group
names must have specific values.
The chapters 5, 5.2, 6.2, 6.3, 6.4,
6.6, 7.10 and 9 are updated.
Chapters 6.11 and 7.5 are new.
C 2009-04-01 UABINGE Chapter 6.6 is only for AP1.

Step 11 in chapter 6.7 is updated.
Chapter 6.8 is updated.
Chapter 6.8.3 is removed.
Step 3 in chapter 6.12 is updated.
Step 4 in the chapters 6.13.4 is
updated.
Chapter 6.14.1 is updated.
Chapter 6.14.3 is updated.
The chapters 6.15-6.17 are added.
Chapter 7.14 is updated.
D 2009-12-09 UABINGE IPLB replaces ISER.

The VLANs receive new names.
Reference 56 is added.
Reference 55 is updated.
E 2010-01-19 UABINGE Chapter 6.15 is updated.

The chapters 6.16, 6.17 and 6.20
are added.
F 2010-06-18 UABINGE The use of BASEIP is clarified.

Ericsson Internal

9 Glossary
See “APZ Terms for Blade Cluster” in reference [57] on page 170 and
“Concepts and Terminology for MSC Server Blade Cluster” in reference [56]
on page 170.
9.1 Terminology
Administrative State The state of a blade or a blade system. The states are:
locked The blade or blade system is not available to
network traffic of CLI commands and may be removed.
shuttingdown The blade or blade system is in the progress of
shutting down gracefully. The blade is then not allowed to be
removed.
unlocked The blade or blade system is available to network
traffic of CLI commands. The blade is then not allowed to be
removed.
CMF The CMF service provides an XML based machine-machine

interface (NetConf) for site management.
CP cluster state The individual state of a cluster CP as seen by other members of

the cluster. The states are:
Active
Intermediate
NonOp
Passive
Recovery (valid from APZ 17.0)
Small Restart (valid up to APZ 16.0)
Undefined
The CP blades that have status Active or Passive are part of the
Quorum.
The following values for the CP cluster state are given in the
exchange header in the printouts:
ACT (Active)
INT (Intermediate)
NA (NonOP or Undefined)
PAS (Passive)
CP Group A number of CPs defined to form a group with a name that a user of
the I/O system can connect to. After connection to a CP group all
commands issued by that user will be dispatched to all CPs within
the group.
The following values for the CP cluster state are given in the
exchange header in the printouts:
If the CP states of the CPs are the same, the common CP state is
displayed.
NA (Not Applicable) is displayed, if the CP states of the CPs differ
Ericsson Internal


CP id The logical address of a CP, 0-63
Destination Can be a CP Name, a CP Group or an empty string meaning any

CP blade. The term Destination differs from Origin in that
Destination is used referring to an access originating from the
outside going inside towards a CP whilst Origin is used referring to
an access originating from a CP going outside
DISK Hard disk or data disk
Egress direction In this document the Egress direction is related to the switch (out
from the switch).
ET155 The ET155 is a 155 Mb/s STM-1 interface between the Group
Switch and the SDH transport networks. The interface towards the
network is available in an optical or electrical solution
Front-End-AP One APG43 in an MCS-S BC that will serve as the primary gateway
to the AXE domain of the MSC-S BC system
IE-Select A Data Base. It is used to get documents for a specific subrack
Ingress direction In this document the Ingress direction is related to the switch (from
outside towards the switch)
IS management bus A generic term for the M-bus and the IPMI bus, the two
management buses in the IS
ISM The IS Management system resides on the SIS blade system and
provides a number of IS internal services to the BS: boot-loading,
management support, configuration, fault management, network file
system (NFS), etc
IS1 Subrack 0 in an IS system
IS2 Subrack 1 in an IS system
ISNB The IS NorthBound subnet (ISNB) is hosted on a tagged VLAN

dedicated for remote management of an IS. Use of ISNB is optional
and application dependent. A BS may obtain IP address, subnet,
mask, default gateway and domain name server with DHCP. The
domain name server is local and inaccessible to OSS. A BS will
publish its IP address as an attribute in an (application owned)
Managed Object where OSS can read it through CMF.
Joiner A CP that is in the progress of becoming a member of the Quorum
Legacy Mode The APG43 and the CP blades are in old mode, meaning every CP
blade works independently.
Loopback Interface The loopback interface is a virtual interface, and traffic to the
loopback interface is directed to the VR that owns it.
Ericsson Internal


Multi(ple) CP system A system including several CPs, regardless if the CPs are Single
sided CPs or Dual sided CPs. (This term is only used for IO/APG
related documents to denote that the APG supports several CPs)
NEID Network Element Identity. A defined name for an MSC-S BC system

supported by one and the same group of APGs
One CP system A system with only one CP
Origin See the explanation for “Destination”
PHCI The PHCI (PHC Inhibit) function inhibits the watchdog, and is then
active. Normally the PHCI function must not inhibit the watchdog,
and is then passive. When the PHCI function is passive the PHC
function is active, and vice versa. See chapter 9.2 “Abbreviations”.
PMD-IDE NSP5 with disk, that is, the HW that SIS is executing on
Port Based VLAN The Port based VLAN should be used for handling the untagged
traffic that flows in an Ingress port. There is one entry for each port
in the switch. They are used for telling the switch the following
information - per port:
a) The interconnection among different ports across the switch.
b) The ports where to insert the VLAN tag (in the Egress direction)
SCB-RP Support and Communication Board – Regional Processor. It

provides switching capabilities between subracks as well as within
the subrack
Single CP system A system with one Dual sided CP. Not recommended for use
Sponsor A CP selected by the Leader to run Join protocol in order to take a

new CP into the Quorum
STM Synchronous Transfer Mode
STM-1 SDH level 1 with 155 Mbps
Tagged VLAN The VLAN should be used for handling the tagged traffic that flows
in an ingress port. There is one entry for each defined VLAN. They
are used for telling the switch the following information per VLAN:
a) The interconnection among different ports across the switch for
the broadcast domain.
b) The ports where to remove the VLAN tag in the Egress direction.
Traffic execution state

The traffic execution state of a CP. The states are:
Isolated: Executing isolated traffic for testing purposes if CP
Cluster State is Active. Not executing any traffic if CP Cluster State
is Intermediate.
None: Not executing any traffic. CP Cluster State can be
anything except Active.
Normal: Executing normal traffic. CP Cluster State is Active
Ericsson Internal


VLAN Virtual LAN, commonly known as vLAN or VLAN. It is a method of
creating independent logical networks within a physical network.
Several VLANs can co-exist within such a network. This helps in
reducing the broadcast domain and aids in network administration
by separating logical segments of a LAN (like company
departments) that should not exchange data, by using a LAN (they
still can exchange data by routing)
9.2 Abbreviations
AGO Assembly Grouping Object
ALI ATM Link Interface
APIO Adjunct Processor Input/Output
APM Adjunct Processor Module
ATM Asynchronous Transfer Mode
BFD Bidirectional Forwarding Detection
BIOS Basic Input Output System
BSOM Blade System O&M Master
CC ClearCase
C7 CCITT No.7
CDU Central Processor Display Unit
CH Cluster Handler
CLI Command Line Interface
CMF Common Management Framework
CN Core Network
CPT Central Processor Test
CPUB Central Processor Unit Board
DHCP Dynamic Host Configuration Protocol
DISK Hard disk or data disk
eGEM enhanced Generic Ericsson Magazine
E1 External 1
E4 External 4
Ericsson Internal


EMT Extended Memory Test
ET155-1 Exchange Terminal 155 Mbps. See chapter 9.1 “Terminology”
FIOL File Transfer and Online PC Program
FRU Field Replacement Unit
GARP Generic Attribute Registration Protocol
GB Giga Bytes
GE Gigabit Ethernet
GEP Generic Ericsson Processor Board
GS Group Switch
GUI Graphical User Interface
HC HW Configuration
HD Hard Disk
HSL High Speed Bc-signaling Link
HW Hardware
HWC HW Configuration Table
IP Internet Protocol
IPLB IP Line Board
IPMI Intelligent Platform Management Interface
ISL Inter Subrack Link
ISLB Inter Subrack Link Board
ISM IS Management
ISNB IS NorthBound subnet
ISOB Internal O&M Basic subnet
ISP In Service Performance
ISS Integrated Site Services
LAG Link Layer Aggregation
LED Light Emitting Diode

Ericsson Internal


MAC Media Access Control
MIA Manual Intervention Allowed
MML Man Machine Language
MSS Mobile Switching Solution
MUM Middleware Upgrade Master
MWUG Middleware Upgrade
NB Narrow Band
NE Network Element
NETCONF Network Configuration Protocol
NTP Network Time Protocol
PED Plant Engineering Description
PES Plex Engine Subsystem
PHC Program Handling Circuit
PHCI Program Handling Circuit Inhibit
RAN Radio Access Network
RP Regional Processor
RPB-E Regional Processor Bus – Ethernet
RUF Remote Upgrade of Firmware
S1 Site variant 1
SAP Service Access Point
SDH Synchronous Digital Hierarchy
SS7 Bc-signaling System #7
SID Site Installation Documentation
SSH Secure Shell
STEB Bc-signalling Terminal Enhanced Board
STRAB Strap Board
SW Software
Ericsson Internal


TC Traffic Case
TDM Time Division Multiplexing
ToD Time of Day
TSC Transit Switching Center
VLAN Virtual Local Area Network
VR Virtual Router
VRRP Virtual Router Redundancy Protocol
XML Extensible Markup Language

Start Up APZ 212 60 - 2

Uploaded by

Copyright:

Available Formats

You might also like

Start Up APZ 212 60 - 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Start Up APZ 212 60 - 2

Uploaded by

Copyright:

Available Formats

Ericsson Internal

TEST INSTRUCTIONS 1 (177)

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

© Copyright Ericsson AB 2010. All rights reserved.

Factory Start Up and Initial NE Test of a CP

This document provides the necessary information to perform Factory Node

Factory Node Test is performed at the production line.

Note 1: This document is not intended to be used at customer sites.

This document is intended to be used when starting up new equipment and

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

Factory Node Test is performed at the production line.

1.1 Concerned Hardware

An MSC-S BC comprises the following main components:

• Common I/O system, based on two APG43.

• Cluster System, implementing two different logical nodes; MSC-S and

MSC-S Blade Cluster

MSC-S MSC-S MSC-S MSC-S MSC-S

The Cluster System is housed in an IS infrastructure. It provides an eGEM,

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

Note 1: This document is not intended to be used at customer sites.

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

This test instruction should be executed in the following order:

Section Page Action

6.2 11 Unlock the CPHW Blade System

6.3 13 Blade Definition in eGEM

6.4 17 Setting CP Identification Values

6.5 22 Installing PES and CPHW Dump Versions

6.6 27 Checking Proxy Boot Configuration

6.7 30 Transferring of CP Dump to APG43

6.8 43 Ping Tests

6.9 46 Boot Starting of the CP Blades

6.10 52 Initial Testing of the CP Blades

6.11 55 Initial Loading of the CP Blades

6.12 59 Definition of AP2

6.13 61 Definition of Routing Tables for IPonCP for VLAN INT-SIG

6.15 90 Definition of Routing Tables for IPonCP for BC-SIG

6.16 107 Definition of Routing Tables for IPonCP for BC-SIG-EXT1

6.17 123 Definition of Routing Tables for IPonCP for BC-SIG-EXT2

6.18 139 Definition of Routing Tables for IPonCP for BC-SIP

6.19 142 Definition of Routing Tables for IPonCP for BC-DNS

6.20 146 Definition of Routing Tables for IPonCP for BC-BLD-EXT1

6.21 148 Perform System Backup Copies

UABINGE 104/1532-B/AXE 106 99 Uen

EAB/FLE/UE [Ingemar Andersson] 2010-06-18 F

3 Conditions before Starting

• A Kickstart Server must be configured with base SW.

• The IS cabinets must be correct mounted and grounded.

Note: WinFIOL 7 is required due to SSH (Secure Shell), when an APG43

• The command file document 104/190 90-B/AXE 106 99 is used for

• IE-Select is used to get node building documents.