You are on page 1of 16

Alcatel BSS

IO 112 - Changing the


Synchronization Mode for
A9130 MFS Evolution

MFS Document
Customization Procedure
Release B8

3DF 00300 0112 UAZZA Ed.01

BLANK PAGE BREAK

Status

RELEASED

Short title

Short Title
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel/Evolium.

2 / 16

3DF 00300 0112 UAZZA Ed.01

1 Overview

1 Overview

3DF 00300 0112 UAZZA Ed.01

3 / 16

1 Overview

1.1 Introduction
This document describes how to change the synchronization mode for the
A9130 MFS Evolution.
The two possible synchronization modes are:
autonomous, where each GP is synchronized from the TC or the SGSN
through a PCM.
centralized, where all GP boards are synchronized from only two fixed
sources (TC or SGSN). These fixed sources are defined when the first GP
is configured, for the whole MFS.
When changing the synchronization, the MFS must be running in configuration
mode. The synchronization mode is global on the MFS, either autonomous
or centralized.

1.2 Prerequisites
IMT Terminal, configured according to A9130 MFS Evolution IMT User Guide
(3BK 20873 AAAA PCZZA).
The MFS must be operational and running, with both stations in site mode.

1.3 Scheduling
1.3.1 Human resources
1 operator on terminal.

1.3.2 Duration
1h -1h 30 minutes - depending on MFS - IMT connection.

1.4 Telecom / Supervision Outage


1.4.1 Telecom (GSM Traffic)
None.

1.4.2 GPRS
The GPRS is lost when stations are relaunched in site mode after executing
mfssetup, until the all the links (BSC-MFS, MFS-TC, MFS-SGSN) are
recreated and aligned. The GPRS outage is less than 30 minutes.

1.4.3 Supervision
The supervision is lost when the active station is restarted in configuration
mode. The supervision outage is finished when the active station is relaunched
again in site mode.

4 / 16

3DF 00300 0112 UAZZA Ed.01

2 Procedure

2 Procedure

3DF 00300 0112 UAZZA Ed.01

5 / 16

2 Procedure

2.1 Print Gb and MFS TP Configuration


This step is used to keep a record of the GPRS configuration defined on
each Ater Mux going through MFS to set exactly the same configuration
after synchronization mode change.
To keep records of Gb resources defined on MFS-SGSN links and MFS-TC
links, perform at OMC-R:
1. Follow the menu path in the MFS Ater/Gb Supervision window:
Configure->Gb
2. Select the NSC Configuration toggle.
3. Click on [ + ] next to the NSE object to obtain the list of NS-VC.
4. Select each NS-VC and follow the menu path Edit->Modify to obtain the
NS-VC Modification window, save the window using snapshot or print
the screen and click on [ Cancel ].
5. Click on [ Close ] to quit the window.
6. In case of multi-GPU BSS, perform steps 3 and 4 for each NSE associated
to BSS.
To keep records of MFS TP configuration:
1. In the MFSUSM main window, select Configure->Links and Connections.
2. Select BSC-MFS links. Select->BSC to select the BSC.
Save the window using snapshot or print the screen.
3. Select MFS-TC links and save the window using snapshot or print the
screen.
4. Select MFS-SGSN links and save the window using snapshot or print
the screen.
5. Select cross-connection and save the window using snapshot or print
the screen.
6. Click on [ Close ] to quit the window.

6 / 16

3DF 00300 0112 UAZZA Ed.01

2 Procedure

2.2 Change the Synchronization Mode


Perform the following steps in order to change the synchronization mode:
1. Open connections (telnet, putty) on the two stations, from the DOS
command mode:
telnet 172.17.3.3, for Station A
telnet 172.17.3.4, for Station B
Enter root username and password.
2. Determine which is the active station on the MFS, with the command:
#ps -edf | grep mfs

The active station has the BckpRstr and PatchSrv processes running,
the stand-by station not.
3. Perform on the stand-by station:
<STANDBY> # /usr/mfs/bin/mfs_stop_tomas

Confirm the reboot with y.


4. Start the active station in configuration mode:
<ACTIVE> # /usr/mfs/bin/mfs_start_tomas -conf

Confirm the reboot with y.


5. After rebooting, both stations become unavailable for a while. Try to connect
both of them after some minutes, with telnet.
6. Enter root username and password, when stations are available again. The
<ACTIVE> station starts in configuration mode.
7. Check on the active station when rebooting in configuration mode is
complete:
<ACTIVE> # ps -edf |grep nectar

The reboot is complete when UP_GP_TCP process appears as launched.

3DF 00300 0112 UAZZA Ed.01

7 / 16

2 Procedure

8. Configure the active station:


<ACTIVE> # mfssetup

During the execution of the script, you will be asked for the synchronization
mode (Enter the mic type synchro).
Set the mode as appropriate (1= AUTONOMOUS 2=CENTRALIZED). Do not change
values that are between brackets (IPs, hostnames)!
#################################
MX MFS B8 Installation procedure
Alcatel 2005
#################################
Current date and time is Thu May 5 11:48:22 2005
-0.295809 seconds
Do you want to change it Y/[N]?
If necessary to change date type y, and enter the new time.
n
Enter the rack number [1]
1
Rack number is always 1.
Choose the shelf configuration
1: Stand-alone with 1 shelf extensible (12 E1/GP,9+1
GP max)
2: Stand-alone with 2 shelves (12 E1/GP,21+1 GP max)
3: Stand-alone with 1 shelf not extensible (16
E1/GP,9+1 GP max)
Enter the value according with the case.
1
Do you want to setup Vlan configuration for F300 LAN
and GPU/MUX ne1oe VLAN: y/[n]?
Answer y for Vlan configuration.
y
Enter the mic type synchro (1= AUTONOMOUS
2=CENTRALIZED)
Enter the value according with the operator request (1 or 2)
2
subrack_profile.bul has been regenerated
0
You are in conf mode. To take into account the new
bul, reboot in configuration mode:
/usr/mfs/bin/mfs_start_tomas -conf and reload the bul
Update_bul_files script launched
MX MFS Internet configuration
...................
== eth0.5 interface configuration ==
Enter external IP address for "STATION_A" on "EXT0"
[must not be 172.17.3.3 - currently: ]
Enter the first external IP address of the station x.
Enter "netmask_eth0.5"
Enter the netmask for first external IP address of the station x.
== eth1.5 interface configuration ==
Enter external IP address for "STATION_A" on "EXT1"
[must not be 172.18.3.3 - currently: ]
Enter the second external IP address of the station x
Enter "netmask_eth1.5"

8 / 16

3DF 00300 0112 UAZZA Ed.01

2 Procedure

Enter the netmask for second external IP address of the station x


Enter "station_mfs" IP address
Enter the MFS floating IP adress, the same address on both stations
Enter "netmask_floating_address"
Enter the netmask for MFS floating IP adress, the same value on both
stations
Enter address of the router on "EXT0"
Enter the IP adress for the router on EXT0
Enter address of the router on "EXT1"
Enter the IP adress for the router on EXT1
/etc/apache/httpd.conf VirtualHost modified with
address 172.17.3.3
/etc/apache/httpd.conf VirtualHost modified with
address 172.18.3.3
/etc/apache/httpd.conf VirtualHost modified with
address 192.168.14.72
Apache server stopped, will be restarted later
/usr/sbin/apachectl stop: apache (no pid file) not
running
Enter OMC hostname:
Enter OMC hostname according to operator request
Enter OMC IP address:
Enter OMC IP address according to operator request
omcr19 added to /etc/hosts.
Do you want to add another omc [y]?
n
NTP configuration ----------------Current NTP:[omcrxx]
Current OMC: for
Enter NTP server hostname:
Enter NTP hostname according to operator request. The NTP could be
the OMC.
Testing omcrxx...
Original /etc/ntp.conf.server saved to
/etc/ntp.conf.server.pre_mfs_ntp.2.
omcrxx is an NTP server for STATION_A.
Allow to use local clock in last resort when all other
NTP sources have gone away.
Stopping NTP server: ntpd.
Restarting NTP server
Enter the MFS Ident (Manager Element Id) ? [508]
Enter the MFS ID, the same value for both stations
Enter the MFS Name (32 maximum characters) [mfs08]
Enter the MFS name, the same name for both stations
/usr/mfs/etc/GPMGP has been modified successfully
/usr/mfs/etc/nServerFile has been modified successfully
/usr/mfs/etc/param.cfg has been modified successfully
End of installation script
9. Run the same command on stand-by station:
<STANDBY> # mfssetup

3DF 00300 0112 UAZZA Ed.01

9 / 16

2 Procedure

During the execution of the script, you will be asked for the synchronization
mode (Enter the mic type synchro).
Set the mode as appropriate (1= AUTONOMOUS 2=CENTRALIZED). Do not change
values (IPs, hostnames) that are between brackets!
10. Launch the bul files on the active station (which is in configuration mode):
<ACTIVE> #cd /usr/mfs/bul
<ACTIVE> #buif 01_mfs.bul
Before going to the next step check that the GPM process is started:
<ACTIVE> #ps -ef | grep mfs
<ACTIVE> #buif 02_mfsconfig.bul
Wait until the prompt is available again.
<ACTIVE> #buif 03_mfsliu.bul
Wait until the prompt is available again.
<ACTIVE> #buif dataPatch.bul
11. Copy the customer bul file from the CD to the STATION_A in /usr/mfs/bul
directory and launch it
<ACTIVE> #buif template_set_parameters_in_site_mode.bul
Wait until the prompt is available again.
12. Start the active station in site mode:
<ACTIVE> # /usr/mfs/bin/mfs_start_tomas -site
Confirm the reboot with y, then wait 2 minutes and reconnect to the
active station.
13. Start the other station in site mode:
<STANDBY> # /usr/mfs/bin/mfs_start_tomas -site
Confirm the reboot with y, then wait 2 minutes and reconnect to the
active station.
14. Check that the MFS starts correctly, when both stations have restarted,
check that all the MFS UNIX processes are launched:
<ACTIVE> #ps -edf |grep mfs
<STANDBY> #ps -edf |grep mfs
root 1298 1 0 Apr26 00:00:00 /usr/mfs/bin/DUMP_SRV
root 1460 1 0 Apr26 00:00:00 /usr/mfs/bin/TRACE_SRV
root 1624 1456 0 Apr26 00:00:00 /usr/mfs/bin/GAM
root 1633 1456 0 Apr26 00:00:02 /usr/mfs/bin/GEM
root 1658 1456 0 Apr26 00:00:00 /usr/mfs/bin/SCA
root 1660 1456 0 Apr26 00:00:00 /usr/mfs/bin/GOM
You have to be patient: After GOM process is started on STATION_A, the
other processes starts after 15 minutes.
root 2101 1456 0 Apr26 00:00:00 /usr/mfs/bin/GPM
root 2111 1456 0 Apr26 00:00:00 /usr/mfs/bin/GLM
root 2116 1456 0 Apr26 00:00:00 /usr/mfs/bin/mfsQ3Agt
root 2125 1456 0 Apr26 00:00:00 /usr/mfs/bin/CRAFT_SUP
root 2133 1 0 Apr26 00:00:00 /usr/mfs/bin/BckpRstr
root 2135 1 0 Apr26 00:00:00 /usr/mfs/bin/PatchSrv

Note:

The BckpRstr and PatchSrv processes runs only on the active control station.
15. Display the Craft_SUP process by typing:
<ACTIVE> # ps -ef | grep CRAFT_SUP
root 2125 1456 0 Apr26 00:00:00 /usr/mfs/bin/CRAFT_SUP
When the CRAFT_SUP Linux process starts, the IMT connection is possible.

10 / 16

3DF 00300 0112 UAZZA Ed.01

2 Procedure

2.3 Restore GP and MFS TP Configuration


Perform the following steps at the OMC-R in order to restore Gb and TP
configuration:

Resynchronize GPRS
1. In the RNUSM, SC main window, select the MFS and right-click on it.
2. Select Re-Synchronize GPRS from the pop-up menu.

Configure Transport

Configure transport for each GP, by aligning BSC-MFS and MFS-TC links for all
BSCs one by one, then cross-connect GP board if necessary:
1. In the MFSUSM main window, select Configure -> Links And Connections.
The Links configuration window opens.
2. If the window is opened empty without any TP, select Select -> BSC
3. Select the required BSC in "Links configuration/BSC Selection" window
and click on [ Select ]. The BSS panel displays the available TPs of the
selected BSC.

Redo MFS - SGSN Links

If MFS - SGSN links were present on the original configuration (check the prints
done before), redo all the links between the MFS and SGSN:
1. Click on the MFS - SGSN links tab.
2. Select either Select -> BSC to select the GPU TPs linked with the BSC or
Select -> MFS GPU board to select the GPU directly.
The BSC Selection window or GPU Selection window opens.
3. Select the required BSC or GPU and click on [ Select ]. You see the TPs of
the linked GPU in the Shelf/GPU panel.
4. Select the required GPU TP.
5. Click on [ Link ].
The new link is displayed in the Links panel.
6. Redo in this way all the links between MFS and SGSN that were existing in
the original configuration.

Align Links

Align all the links:


1. Select Links -> Align Links and redo the original configuration (that was
printed before).

Note:

In case of multi-GPU, the appropriate GPU has to be selected from the Align
Links - Links configuration/GPU Selection window.
2. Click on the [ Cross-Connections ] tab.
3. Select Connection -> Connect GPU Board and redo the original
configuration (that was printed before).

Note:
Align GPRS
Configuration

In case of multi-GPU, the appropriate GPU has to be selected from the window
that appears after the Cross-Connect operation.
For all Ater Mux on the MFS, align GPRS Configuration on all TPs. The MFS
part of the MFSUSM window is then updated.
1. In the MFSUSM main window, click on the [ Ater supervision ] tab.
2. Select Align -> GPRS Configuration -> Align All TPs.

3DF 00300 0112 UAZZA Ed.01

11 / 16

2 Procedure

2.4 Configure Gb Interface


This task configures the MFS-TC link if the TC supports Gb, or the MFS-SGSN
link.

Note:

The NSE and NS-VC, PVC, FR-BC must have the same identifier as in
the previous configuration of the MFS. Otherwise no GPRS packet can
be transferred between the MFS and SGSN.The operator must refer to the
screen printouts made before.

Note:

In order to reduce GPRS outage, first one NSE and related NSVC for each
BSS is created. The GPRS traffic starts on one GPU for each BSS. Then the
remaining NSE are created.

Create NSE

For one GP associated with the BSS and for each BSS, create NSE:
1. In the MFSUSM main window, click on the [ Gb supervision ] tab.
2. Select Configure -> Gb. The "Gb Configuration" window opens.
3. Create NSE by selecting Edit -> Add -> NSE, enter an NSEI in the "NSE
Creation" window, select an associated BSS, and click on [ OK ].

Create NS-VC

Create NS-VC for the GP, a first NS-VC on the links supporting Gb
resources, using the values printed before (you have already opened the
"Gb Configuration" window:
1. In the MFSUSM main window, click on the "Gb supervision" tab.
2. Select Edit -> Add -> NS-VC. The "NS-VC Creation" window opens.
3. Select GPU Board.
4. Select TP port.
5. Select the time slots to be changed by first clicking on the highest numbered
time slot, then the lowest numbered time slot.
All time slots between the first and last time slots are selected, and are
set green in color.
6. Select the NS-VC parameters.
7. Select the Bearer channel parameters time slots by first clicking on the
highest numbered time slot, then the lowest numbered time slot.
All time slots between the first and last time slots are automatically selected.
8. Enter the PVC parameters, and click on [ OK ].

Unlock GPRS

Unlock GPRS Traffic on BSS (for the BSS where GPRS traffic is locked):
1. In the RNUSM, PRC or SC main window, select the required BSC.
2. Right-click, and select Unlock GPRS from the pop-up menu.
3. Click on [ OK ].

Unlock NS-VC

Unlock NS-VC, because an NS-VC is created in the locked state:


1. In the MFSUSM main window, click on the [ Gb supervision ] tab.
2. Select Configure -> Gb. The "Gb Configuration" window opens.
3. Click on the "NSC Configuration" tab, and select the required NS-VC.
4. Select Supervise -> Unlock as required.

12 / 16

3DF 00300 0112 UAZZA Ed.01

2 Procedure

Unlock GSL

Unlock GSL, because a GSL is created in the locked state:


1. In the MFSUSM main window, click on the [ Ater supervision ] tab.
2. Select the required TP.
3. Right click and select Unlock GSL as required.
Proceed the same for each GP associated with a BSS and for each BSS, using
the information printed before to recreate the original configuration.
Perform a global MFS check, by selecting Checks -> Global Check in the
MFSUSM main window.

2.5 Option (Only in Autonomous Mode): Set the PCM TTP


Attributes on Each GP
1. Connect the IMT with the root username and password.
2. Select View -> Phisical View from the main menu. The Phisical View
window opens.
3. For each equipped GP, click on the respective GP.
4. Right click on a PCM TTP and select Set Attributes.
5. For the attribute Synchronizing, select [ yes ] when synchronization mode is
autonomous, and [ No ] when it is centralized.
Check if a clock icon appears on the PCM TTP rectangle when synchronized.
6. Set Synchronizing attribute in the same way for the second PCM TTP
of the GP.
7. Proceed the same for all equipped GPs.

3DF 00300 0112 UAZZA Ed.01

13 / 16

2 Procedure

14 / 16

3DF 00300 0112 UAZZA Ed.01

3 Completion Check List (CCL) for IO112

3 Completion Check List (CCL) for IO112

3DF 00300 0112 UAZZA Ed.01

15 / 16

3 Completion Check List (CCL) for IO112

Operation

Duration

Site

Print Gb and MFS TP Configuration


Change the Synchronization Mode for A9130 MFS
Evolution
Restore GP and MFS TP Configuration
Configure Gb Interface
OPTION: Set the PCM_TTP attributes on each GP

Date, time & duration of work:

Responsible:

Start

Visa:

End

Duration

Date:

Traffic outage
Start

End

Comments

Comments

16 / 16

3DF 00300 0112 UAZZA Ed.01

You might also like