Alcatel-Lucent GSM

Merge G2 TC to 9125 TC
BSC & TC Document
Reconfiguration Method
Release B10
3BK 17430 0691 RJZZA Ed.06
Status RELEASED
Short title MPI69 / MDR1
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel-Lucent.
BLANK PAGE BREAK
2 / 32 3BK 17430 0691 RJZZA Ed.06
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.1 Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.2 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.4 Grouped Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.2 Site Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.3 External Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4 Telecom/Supervision Outage and Operating Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.1 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.2 Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.3 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1 Before Going Onsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.1 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.2 Required Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3 Scenario Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.1 Initial Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.2 Change TRAU LOUDNESS Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.3 Switch First Ater Mux Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.4 Test Call Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.5 Switch Other Ater Mux Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.6 Test Call and GPRS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.7 Final Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4 Reverse Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4.1 Stop Traffic on Ater Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4.2 Cable Moved Ater Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4.3 Set Traffic on Ater Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.4 Test Call and GPRS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.5 Final Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3BK 17430 0691 RJZZA Ed.06 3 / 32
Contents
4 / 32 3BK 17430 0691 RJZZA Ed.06
Preface
Preface
Purpose This document describes how to merge G2 TC into 9125 TC.
It is applicable to BSS at technical release level B10.
Whats New In Edition 06
New section Declare the BSC at the 9125 TC Equipped with TC STM1-IP
Subrack (Section 2.3.3.1) is created.
In Edition 05
Update with the new equipment naming.
In Edition 04
The following sections were updated:
Prerequisites (Section 1.2.1)
Site Specific Information (Section 1.2.2)
In Edition 03
Improvements were made in Restrictions (Section 1.1.3)
In Edition 02
Overall document quality was improved following an editorial review.
Improvements were made in the following sections due to a system evolution:
Prerequisites (Section 1.2.1)
Site Specific Information (Section 1.2.2)
Overall document quality was improved following an editorial review.
First official release of the document for B10MR2.
In Edition 01
Overall document quality was improved following an editorial review.
First official release of the document for B10.
3BK 17430 0691 RJZZA Ed.06 5 / 32
Preface
Audience This document is intended for:
Field service technicians
Specialists
Project managers
Foremen.
6 / 32 3BK 17430 0691 RJZZA Ed.06
Preface
Assumed Knowledge You must have a basic understanding of the following:
Planning:
Network architecture and reshuffling principles
Basic knowledge for scheduling.
Implementation:
Alcatel-Lucent operations and maintenance concepts for the BSS
9153 OMC-R operation
Equipment (BSC, BTS, MFS, TC) hardware configurations
Windows environment.
3BK 17430 0691 RJZZA Ed.06 7 / 32
Preface
8 / 32 3BK 17430 0691 RJZZA Ed.06
1 Overview
1 Overview
This Overview gives information needed by project managers and foremen, for
presentation to the customer and for site planning.
3BK 17430 0691 RJZZA Ed.06 9 / 32
1 Overview
1.1 Presentation
This scenario describes how to merge a G2 TC with an 9125 TC/ 9125 TC
equipped with TC STM1IP subrack.
After this procedure, the G2 TC must be dismantled at an appropriate time.
In case it is necessary to replace E1 links with STM1 or vice versa, see E1 to
STM1 Configuration or STM1 to E1 Configuration, as needed.
This scenario does not cover the upgrade of an 9125 TC with TC STM1 board.
If it is the case, first perform Upgrade 9125 TC with TC STM1 board.
1.1.1 Cases
The following cases apply:
C1: LCS activated on the BSS
C2: The BSS is multi GPU.
The scenario uses the configuration management rules specific to the 9153
OMC-R.
1.1.2 Options
None.
1.1.3 Restrictions
This procedure does not handle BSC or TC extension.
10 / 32 3BK 17430 0691 RJZZA Ed.06
1 Overview
1.1.4 Grouped Task Sequence
The following figure shows the grouped task sequence for this scenario.
Initial Checks
OMCR TC MSC
Switch First Ater Mux Connection
Test Call Service
Test Call and GPRS Services
Change HR PRESENCE and
TRAU LOUDNESS Parameters
Switch Other Ater Mux Connections
Final Checks
Figure 1: Merge G2 TC into 9125 TC
3BK 17430 0691 RJZZA Ed.06 11 / 32
1 Overview
1.2 Preparation
1.2.1 Prerequisites
The following prerequisites apply:
The site is clean, tidy and easily reachable
The BSS is operational in release B10
If a new 9125 TC rack is needed, it must be installed and commissioned
before the operation. Note the TC rack number; it must be greater than
or equal to 5.
The generic transmission data settings for the 9125 TC are downloaded.
The newly inserted boards in an 9125 TC rack already in use are already
configured.
In the case of an X.25 connection routed through the Ater/A interface,
redundancy is mandatory.
12 / 32 3BK 17430 0691 RJZZA Ed.06
1 Overview
1.2.2 Site Specific Information
You must have the following specific information to complete the scenario:
Site Preparation Specifications (SPS) with specific values for the Trau
Loudness parameter.
Site Preparation Specifications (SPS) with specific information on the
extraction point of X.25 connections, necessary for loading the right generic
transmission settings in the TC.
1.2.3 External Tasks
None.
3BK 17430 0691 RJZZA Ed.06 13 / 32
1 Overview
1.3 Scheduling
Time based on technical constraints
The number of resources shown in the following table does not take into
account individual customer or safety requirements.
Grouped Task MSC BSC Impacted TC OMC-R Time/Task
Initial Checks - - - 1 ope.
(15 min.)
15 min.
Change TRAU
LOUDNESS Parameter
- - - 1 ope.
(1-7 min.)
1-7 min.
Switch First Ater Mux
Connection
1 ope.
(5 min.)
- 1 com.
(16 min.)
1 ope.
(54 min.)
64 min.
Test Call Service - - - 1 ope.
(10 min.)
10 min.
Switch Other Ater Mux
Connections
1 ope.
(5 min./Ater
Mux)
- 1 com.
(15 min.)
1 ope.
45 min. + 2
min./NSVC (for
GboFR) or 2
min./SGSN
_IP_
ENDPOINT
(for GboIP) +
4 min./Ater Mux
+ 3 min. 30
sec./board
(60 min. + 2
min./NSVC (for
GboFR) or 2
min./SGSN_IP_
ENDPOINT (for
GboIP) + 4
min./Ater Mux
+ 3 min. 30
sec./board)
Test Call and GPRS
Services
- - - 1 ope.
(10 min.)
10 min.
Final Checks - - - 1 ope.
(20 min.)
20 min.
TOTAL TIME 1 h 58 min. + 19 min./ Ater Mux + 2 min./GSL + 4 min./board + 2 min. /NS-VC
(for GboFR) or 2 min./SGSN_IP_ENDPOINT (for GboIP)
ope. : OMC-R, TC or MSC operator
com. : Commissioning Team
14 / 32 3BK 17430 0691 RJZZA Ed.06
1 Overview
1.4 Telecom/Supervision Outage and Operating Impact
The following table describes the traffic outage and loss of supervision caused
by each grouped task.
Out.
Ref. Grouped Task
Tel. /
GPRS
/ LCS
Out
Tel. / GPRS
Red Sup.Out
Oper.
Impact Impacts...
- Initial Checks - - - - None.
- Change TRAU
LOUDNESS Parameter
- - - - None.
1, 2 Switch First Ater Mux
Connection
- (1) 30 min. /
(2) 33 min.
- - (1) CS Reduction
(2) GPRS Reduction
- Test Call Service - - - - None.
1, 2 or
4, 3
Switch Other Ater Mux
Connections
- /
(4) 40
min./
(3) 41
min.
(1) 30
min./Ater
Mux / (2) 33
min./Ater Mux
- - (1) CS Reduction
(2) GPRS Reduction
(3) LCS Outage, if last
GSL on BSS
(4) GPRS Outage, if
last GSL on BSS
- Test Call and GPRS
Services
- - - - None.
- Final Checks - - - - None.
TOTAL TIME (4) 40 min.
(3) 41 min.
(1) 30
min./Ater
Mux
(2)33
min./Ater
Mux
-
3BK 17430 0691 RJZZA Ed.06 15 / 32
1 Overview
1.5 Resources
1.5.1 Tools
The following tables describe the necessary hardware tools, software tools,
and forms.
1.5.1.1 Hardware Tools
Item Part Number Use at ...
PC with CD-ROM reader and associated cables. - TC
Installation tools. - TC
Anti-static wrist strap. - TC
1.5.1.2 Software Tools
Item Part Number Use at ...
9125 TC Terminal. - TC
Customer documentation CD with the version associated with the current
document edition. Remember that the document you are reading cannot be
used as a paper version. It is online documentation using hypertext links
which take you to other parts of a document on the same CD-ROM. All words
in italics are hypertext links.
- TC,
OMC-R
1.5.1.3 Forms
None.
1.5.2 Supplies
The following table describes the necessary supplies for moving a BSS from a
TC to another.
Item Part Number Contents Use at ...
Site Documentation. - - TC, OMC-R
16 / 32 3BK 17430 0691 RJZZA Ed.06
1 Overview
1.5.3 Applicable Documents
You must have the following documents or have electronic access to the
following documents:
B10 BSS Methods Handbook
BSS Configuration Handbook
BSS Surveillance Handbook
Network Reconfiguration Recommendations
9125 TC User Guide
Site Preparation Specifications (SPS)
3BK 17430 0691 RJZZA Ed.06 17 / 32
1 Overview
18 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
2 Scenario
This Scenario presents all checks needed before beginning the scenario, and
all detailed tasks to be performed on each site.
3BK 17430 0691 RJZZA Ed.06 19 / 32
2 Scenario
2.1 Before Going Onsite
Before going onsite, you must check that the following information and supplies
are available:
All Prerequisites (Section 1.2.1) are met
The customer is informed of the:
Date and time
Site name and address
Purpose of operation.
Personnel are available (refer to Scheduling (Section 1.3))
Site Specific Information (Section 1.2.2) is available
Tools (Section 1.5.1) are available and ready for operation
Supplies (Section 1.5.2) are available and ready for operation
Applicable Documents (Section 1.5.3) are available.
Ensure that the technical release level of the delivered board is in accordance
with the BSS hardware technical release document.
Ensure that the method used at the BSS site is at the same level as at the
OMC-R.
20 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
2.2 Before You Start
2.2.1 Checks
Perform the following operations:
Check that all Prerequisites (Section 1.2.1) are met
Check the availability of all necessary Tools (Section 1.5.1) and Supplies
(Section 1.5.2)
Inform the operator.
Among the cases described in Cases (Section 1.1.1) and the options described
in Options (Section 1.1.2), identify which cases and options apply to you.
2.2.2 Required Knowledge
You must be familiar with the following:
Safety Rules and Precautions
Telecom/Supervision Outage and Operating Impact (Section 1.4)
Reverse Procedure
Grouped Task Sequence (Section 1.1.4)
Operating Hints
How to document Faults and Anomalies.
3BK 17430 0691 RJZZA Ed.06 21 / 32
2 Scenario
2.3 Scenario Description
This section describes how to merge a G2 TC into an 9125 TC.
2.3.1 Initial Checks
Note Task Description Site To do Outage
CHECK Perform an Audit Alarm State on the BSS. OMC-R 5 min. None.
CHECK View Status of Managed Objects and
Alarms (TC) and print them.
OMC-R 10 min. None.
2.3.2 Change TRAU LOUDNESS Parameter
The following operations must be repeated for each BSC or TC G2 rack.
You must adjust the TRAU Loudness (up and down) parameter according to
the site requirements.
Note Task Description Site To do Outage
OMC-R 1 min. None INPUT Modify Ater TRAU Loudness to set the
right value.
Note:Modifying the TRAU LOUDNESS parameter
automatically launches a programming
transmission, but you can immediately start the
next task.
22 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
2.3.3 Switch First Ater Mux Connection
You must take into account the following information before starting the tasks
in this section:
Disconnect the first Ater Mux and the related A interfaces from the terminal
blocks of the G2 TC and then reconnect to the terminal blocks of the 9125
TC on the BSC side and on the MSC side at the same time. The old SM
Adapt from the TC site (ASMC board) related to this Ater Mux is unplugged.
During this time, the MSC operator is advised to lock the CICs in order to
avoid alarms.
It is advisable to ensure GSL resource redundancy. If GSL/GPU redundancy
is not ensured, the Ater Mux carrying the GSL must belong to the second
part of the moved Ater Mux.
There is CS traffic outage when there are no more available N7s; otherwise
there is CS traffic reduction.
There is GPRS outage when there are no more available GSL or
NS-VC/SGSN_IP_ENDPOINT; otherwise there is GPRS reduction.
The following actions must be synchronized with the MSC in order to update
the addresses of the reconnected Ater Mux and A Interfaces.
2.3.3.1 Declare the BSC at the 9125 TC Equipped with TC STM1-IP Subrack
This task refers to the 9125 TC equipped with TC STM1-IP subrack and
before the merging procedure starts, it is necessary to declare the associated
BSCs in the TC-NEM.
Note Task Description Site To do Outage
- Declare the BSC associated to the 9125
TC equipped with TC STM1-IP subrack
in the TC NEM.
TC 6 min. None
2.3.3.2 Declare the 9125 TC at the OMC-R (if needed)
Note: This task refers to the 9125 TC equipped with TC STM1-IP subrack, and it has
to be performed if the 9125 TC was not previously declared at the OMC-R.
Note Task Description Site To do Outage
- If the 9125 TC was not previously declared
at the OMC-R, perform the task Declare
an 9125 TC with TC-STM1 Boards to
OMC-R..
OMC-R 6 min. None
3BK 17430 0691 RJZZA Ed.06 23 / 32
2 Scenario
2.3.3.3 Stop Traffic on First Ater Mux
Note Task Description Site To do Outage
- If this Ater Mux carries a GSL, Lock GSL. OMC-R 1 min. START2
OMC-R 5 min. + 2
min. /Ater
Mux
START1
Reduction2
- Shut Down Traffic on Ater Mux (WTC=4
min.) on first Ater Mux.
Note: If the ATR carries a GSL, a warning
message appears. Confirm the message to
continue with the operation.
EXCH Inform the TC site that cabling can begin. OMC-R 1 min. Reduction1
Reduction2
2.3.3.4 Cable First Ater Mux
Note: In case it is necessary to replace E1 links with STM1 see E1 to STM1
Configuration. In order to avoid outage, modify in the configuration file only
the links that are moved at this step.
Note Task Description Site To do Outage
TC 15 min. Reduction1
Reduction2
- For the first Ater Mux link: disconnect
the following from the G2 TC and
reconnect them to the 9125 TC:
Four A interface PCMs between the
TC and the MSC
One Ater Mux PCM between the TC
and the BSC (MFS).
Note: Disconnection and reconnection are
performed simultaneously on the Ater Mux and
A interface sides by both commissioners to
minimize traffic reduction.
- Unplug the concerned ASMC board from
the G2 TC.
TC 30 sec. Reduction1
Reduction2
EXCH Inform the OMC-R site when cabling is
finished.
TC 1 min. Reduction1
Reduction2
2.3.3.5 Set Traffic on First Ater Mux
Note Task Description Site To do Outage
- Unlock Traffic on Ater Mux (first Ater
Mux).
OMC-R 1 min. + 2
min./ Ater Mux
END1
Reduction2
- Lock Board (the concerned ASMC board),
using Display Related TC Boards.
OMC-R 30 sec. /
board
Reduction2
24 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
Note Task Description Site To do Outage
OMC-R 3 min. / board START1
END1
Reduction2
- Unlock Board (the concerned ASMC
board), using Display Related TC Boards.
Note:This operation is necessary to force the
download of the new transmission settings.
- If the GSL was locked, Unlock GSL on the
Ater Mux.
OMC-R 1 min. END2
Automatic
actions
30 min. None. - Wait for the TC auto-identification, a
hardware audit triggered after 15 minutes
and transmission programming.
Note:At the end of this step, in the BSSUSM
window of the OMC-R, the new MT120 board
(related to the first Ater Mux) is visible.
When the Abis/Ater view is not up to date!
It will be reloaded message appears, click on
[ OK ].
2.3.4 Test Call Service
If tests are unsuccessful, apply the Reverse Procedure (Section 2.4).
Note Task Description Site Time/Task Outage
OMC-R 10 min. None. CHECK Display USD Detailed DTC Information to check
in the DTC report if CS calls are made on moved
Ater Mux and print the report.
The Reverse Procedure (Section 2.4) can
be performed from this point onwards.
2.3.5 Switch Other Ater Mux Connections
Repeat the following operations for each Ater Mux.
Disconnect the Ater Muxes from the terminal blocks of the G2 TC and then
reconnect them to the terminal blocks of the 9125 TC on the BSC side and
on the MSC side at the same time.
During this time, the MSC operator is advised to lock the CICs in order to
avoid alarms.
The following actions must be synchronized with the MSC in order to update
the addresses of the reconnected Ater Mux and A Interfaces.
3BK 17430 0691 RJZZA Ed.06 25 / 32
2 Scenario
2.3.5.1 Stop Traffic on Other Ater Mux
Note Task Description Site To do Outage
- If the Ater Mux supports the last
operational GSL on the BSS, Lock GPRS
Traffic on BSS.
OMC-R 1 min. START4
C2 If the Ater Mux supports the last GSL on
the GPU in the case of multi-GPU, Lock
GPRS on cells from NSEI for all cells
mapped on this GPU.
OMC-R 1 min. START2
- If the operation to lock the GPRS on the
BSS or on cells was already performed
for GboFR, Lock NS-VC for related
NS-VC
for GboIP, Lock SGSN_IP_ENDPOINT
for related SGSN_IP_ENDPOINT.
OMC-R 1 min./NS-VC
(for GboFR) or
1 min./SGSN_
IP_
ENDPOINT
(for GboIP)
Outage4 or
Reduction2
C1 If the Ater Mux supports the last
operational GSL on BSS, Disable LCS
on BSS.
OMC-R 1 min. Outage4 or
Reduction2
START3
- If this Ater Mux carries a GSL Lock GSL. OMC-R 1 min. START2
OMC-R 5 min. + 2
min./Ater Mux
START1
Reduction2
- Shut Down Traffic on Ater Mux
(WTC=4min.) on each Ater Mux to be
moved.
Note:If the Ater Mux supports the last active
X.25 connection or the last active N7, the Ater
Mux cannot be locked. Traffic is cut when the
cabling is disconnected.
If the ATR carries a GSL, a warning message
appears. Confirm the message to continue with
the operation.
EXCH Inform the TC site that cabling can begin. OMC-R 1 min. Reduction1
Reduction2
26 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
2.3.5.2 Cable Other Ater Mux
Note: In case it is necessary to replace E1 links with STM1 see E1 to STM1
Configuration. Modify in the configuration file the rest of the links that remained
to be moved at this step.
Note Task Description Site To do Outage
TC 15 min. Reduction1
Reduction2
- For each Ater Mux link to be recabled:
disconnect the following from the G2 TC
and reconnect them to the 9125 TC:
Four A Interface PCMs between the
TC and the MSC
One Ater Mux PCM between the TC
and the BSC (MFS).
Note:Disconnection and reconnection are
performed simultaneously on the Ater Mux and
A interface sides by both commissioners to
minimize traffic reduction.
EXCH Inform the OMC-R site when cabling is
finished.
TC 1 min. Reduction1
Reduction2
2.3.5.3 Set Traffic on Other Ater Mux
Note Task Description Site To do Outage
- Unlock Traffic on Ater Mux. OMC-R 1 min. + 2
min./Ater Mux
END1
Reduction2
- Lock Board (the concerned ASMC board),
using Display Related TC Boards.
OMC-R 30 sec./board Reduction2
OMC-R 3 min./board START1
END1
Reduction2
- Unlock Board (the concerned ASMC
board) using Display Related TC Boards .
Note:This operation is necessary to force the
download of the new transmission settings.
- If GPRS was already locked on the BSS,
Unlock GPRS Traffic on BSS.
OMC-R 1 min. END2
C2 If GPRS was already locked on cells,
Unlock GPRS on Cells from NSEI.
OMC-R 1 min. END2
- In the case of
GboFR, Unlock NS-VC for the related
Ater Mux
GboIP, Unlock SGSN_IP_ENDPOINT
for the related Ater Mux
OMC-R 1 min./NSVC
(for GboFR) or
1 min./SGSN
_IP_
ENDPOINT
(for GboIP)
Reduction2
- If the GSL was already locked, Unlock
GSL on the Ater Mux.
OMC-R 1 min. END2
3BK 17430 0691 RJZZA Ed.06 27 / 32
2 Scenario
Note Task Description Site To do Outage
C1 If the Ater Mux supports the last
operational GSL on the BSS, Enable LCS
on BSS.
OMC-R 1 min. END3
Automatic
actions
30 min. None. - Wait for TC auto-identification, a hardware
audit triggered after 15 minutes and
transmission programming.
Note: At the end of this step, in the BSSUSM
window of the OMC-R, the new MT120 board
(related to all Ater Mux) is visible.
When the Abis/Ater view is not up to
date! It will be reloaded message
appears, click on [ OK ].
2.3.6 Test Call and GPRS Services
If tests are unsuccessful, apply the Reverse Procedure (Section 2.4).
Note Task Description Site Time/Task Outage
OMC-R 10 min. None. CHECK Perform CS and GPRS calls to test the
Ater Mux.
Display USD Detailed DTC Information to
check in the DTC report if CS and GPRS
calls are made on each moved Ater Mux
and print the report.
The Reverse Procedure (Section 2.4) can be
performed from this point onwards.
2.3.7 Final Checks
Note Task Description Site To do Outage
CHECK Perform an Audit Alarm State on the BSS
and compare alarms and states with
those generated during the Initial Checks
(Section 2.3.1).
OMC-R 10 min. None.
CHECK View Status of Managed Objects and
Alarms (TC) and compare with printed
values from Initial Checks (Section 2.3.1).
OMC-R 10 min. None.
28 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
2.4 Reverse Procedure
Repeat the following operations for every BSC rack.
2.4.1 Stop Traffic on Ater Mux
Note Task Description Site To do Outage
OMC-R 1 min. + 2
min./Ater Mux
- - Lock Traffic on Ater Mux (on all Ater Mux
links to be recabled).
Note:If the Ater Mux supports the last active
X.25 connection or the last active N7, the Ater
Mux cannot be locked. Traffic is cut when the
cabling is disconnected.
If the ATR carries a GSL, a warning message
appears. Confirm the message to continue with
the operation.
2.4.2 Cable Moved Ater Mux
Disconnect all the Ater Mux links and related A interfaces to be recabled
from the terminal blocks of the 9125 TC and then reconnect them to the
terminal blocks of the G2 TC. Reconnect the BSC side and the MSC side at
the same time.
Note: In case it is necessary to replace STM1 links with E1 see STM1 to E1
Configuration.
Note Task Description Site To do Outage
- Plug the ASMC board that was unplugged
during the scenario into the G2 TC rack.
TC 30 sec. -
- For all Ater Mux links to be recabled:
Disconnect the following from the 9125 TC
and reconnect them to the G2 TC:
Four A Interface PCMs between the TC
and the MSC
One Ater Mux PCM between the TC
and the BSC (MFS).
TC 15 min. -
3BK 17430 0691 RJZZA Ed.06 29 / 32
2 Scenario
2.4.3 Set Traffic on Ater Mux
Note Task Description Site To do Outage
- Unlock Traffic on Ater Mux (on each
recabled Ater Mux).
OMC-R 1 min. + 2
min./Ater Mux
-
- Lock Board (all MT120 boards related to
the recabled Ater Muxs) using Display
Related Boards TC.
OMC-R 30 sec./board -
- Unlock Board (all MT120 boards related to
the recabled Ater Mux links) using Display
Related TC Boards.
OMC-R 3 min./board -
Automatic
actions
30 min. - - Wait for TC auto-identification, a the
hardware audit triggered after 15 minutes
of tempo and transmission programming.
Note:At the end of this step, in the BSSUSM
window of the OMC-R, the ASMC and ATBX
boards (related to all Ater Mux) are visible.
When the Abis/Ater view is not up to
date! It will be reloaded message
appears, click on [ OK ].
- Lock TC-Adapt (four related ATBX boards
for each recabled Ater Mux), using Lock
Board.
OMC-R 30 sec./board -
- Unlock TC-Adapt (four related ATBX
boards for each recabled Ater Mux), using
Unlock Board.
OMC-R 2 min./board -
2.4.4 Test Call and GPRS Services
Note Task Description Site To do Outage
OMC-R 10 min. - CHECK Perform CS and GPRS calls to test the
modified Ater Mux.
Display USD Detailed DTC Information to
check in the DTC report if CS and GPRS calls
are made on each recabled Ater Mux and
print the report.
Note:Several packets must be transferred.
Resource allocation is not performed at mobile
connection but at data transfer.
30 / 32 3BK 17430 0691 RJZZA Ed.06
2 Scenario
2.4.5 Final Checks
Note Task Description Site To do Outage
CHECK Perform an Audit Alarm State on the BSS
and compare alarms and states with
those generated during the Initial Checks
(Section 2.3.1).
OMC-R 10 min. -
CHECK View Status of Managed Objects and
Alarms (TC) and compare with printed
values from the Initial Checks (Section
2.3.1).
OMC-R 10 min. -
3BK 17430 0691 RJZZA Ed.06 31 / 32
2 Scenario
BLANK PAGE BREAK
32 / 32 3BK 17430 0691 RJZZA Ed.06