Global Services Step-by-Step Guide For Node B Commissioning

Global Services Step-by-Step Guide for Node B Commissioning
Step by step guide to Node B Commissioning

CHECKLIST BEFORE GOING ONSITE: ............................................... 3
THIN CLIENT CONFIGURATION: ......................................................... 4
STEPS TO BE FOLLOWED FOR THE ACTUAL
COMMISSIONING: .............................................................................. 10

HECKLIST BEFORE GOING ONSITE:
Equipment:
Laptop PC with the following:
Ethernet 10/100 capability
Internet Explorer 5.0
A suitable FTP client (i.e. Filezilla)
HyperTerminal or similar Serial connection interface
command line interface window.
Java Version 1.3.1 latest version possible i.e. 1.3.1_14,
works on most Node B packages.
Ethernet crossed cable.
Serial cable with RS232 end to RJ45 end.
Software:
Basic software package for Node B
XML files for the O&M Wizard and the Site Equipment Wizard.
Site Specific .mo script for setting up the Iub link.
Set_3202.mo script for informing the GPB of an older backplane
in some of the older versions of the Nodes. Only applicable if using
an old Node B version, this can be identified by either or all of
these features. The revision of the Baseband Subrack is
ROJ605107/1, the TXB is in slot 26 of the Baseband Subrack and
the RAXB revision is of RAX 2 nature. There will be a minimum
of 4 RAXBs installed in the Subrack, these boards are of older
revision and of low channel element capacity. They are being
replaced now with a RAX 3, which is a RAX board with 128
Channel Element capacity.
On Site:
List of all settings if XML files not used
Node B RNC link available (Mub set up at RNC)
O&M router configured
Comment [ e1] : Now 15
Comment [ e2] : these
Comment [ e3] : XML
Step-by-Step Guide for Node B Commissioning
- 4 - Copyright 2005 by Ericsson AB
THIN CLIENT CONFIGURATION:
A detailed description can be viewed as above in the RBS
3202/3101 library.
Copyright 2005 by Ericsson AB - 5 -
Step by step checklist includes:
Step 1.
Set up your HyperTerminal/Serial (com port (com1)) connection
with the following settings:
Step 2.
Change the laptop IP address to 1 address more than the node, such
that if the Nodes IP = 10.31.1.1, then laptop is always allocated
10.31.1.2.
Both the Node and the Laptop (Thin Client) must share the same
Sub-Netmask sequence i.e. 255.255.255.240.
This can be changed by the following steps:
Comment [ e4] : subnet mask
Double click on Internet Protocol (TCP/IP) and change the
address as stated.
To check that the Thin Client has obtained the correct address open
a command window and type ipconfig.
Step 3.
Editing the Java policy file:
Select The Java Policy file as shown, open it with a text editor, e.g.
Notepad, and add in the following line of code at the start of the
programme
grant {
permission java.security.AllPermission;
};
Save the file and exit the application.
Step 4.
Configuring the Java properties:
Note: Steps 3 & 4 only have to be done after initial installation of
the Java version.
From the Start menu select the following applications:
Start > Settings > Control Panel > Java Plug-In 1.3.1_14
Copy the settings as shown in the following screenshots:
Click on Apply and exit the application.
Step 5.
Set up your FTP client with the following features.
The Transfer method must be set to Binary from the Transfer drop
down menu.
You must know the username and password of the Node in order to
open an FTP connection. Normally this is set to User: rbs and
Password: rbs.
Filezilla automatically picks up the port number.
Comment [ e5] : Password:
STEPS TO BE FOLLOWED FOR THE ACTUAL
COMMISSIONING:
Step 1.
Formatting the disk and setting the IP address and Password
1 In the HyperTerminal window force the RBS into backup mode
by using the command:
reload --
2 Enter the command listenv which will tell you if the node is
in Basic or backup mode.
3 With the Node in backup mode format both d and c2 drives
using the command:
formathd /d
formathd /c2.
4 Again do a reload -- and a listenv to ensure the Node is
in Backup Mode i.e. the line ending gpb_backup mp750 should
appear in the HyperTerminal window.
5 Set the IP address of the Node and Subnet mask using the
following command:
Ifconfig le0 <IPAddress_of_Node> netmask <Subnetmask_Number>
i.e. ifconfig le0 10.31.1.1 netmask 255.255.255.240
6 Check that the address was successfully stored by entering the
command ifconfig
7 Set password and username for the Node using the following
command passwd and pressing enter on your keyboard. This
will prompt you to enter the password to be set for the Node.
This is essential that the password is correct (normally rbs) so
as it matches with the NMCs password they will use to access
the Node over the Mub link.
8 Perform a reload to save this configuration on the Node.
Step 2.
FTP-ing the basic package software to the Node
1 Open the FTP client window and connect to the Node. On the
left hand pane navigate to the /d folder found in the basic
package folder for the Node.
2 On the right hand pane where it reads remote site navigate
through the GPB flash disk on the Node to the equivalent /d
drive window.
3 Highlight the contents of the /d drive on the Left pane and right
click to upload the files to the GPB flash disk on the Node.
4 This should only take 2 to 3 mins for the /d folder contents and
the same procedure has then to be repeated for the /c2 folder.
The /c2 folder will take roughly 15 mins to transfer across to
the Node.
Note: It is important to ensure that you are FTP-ing the contents of
the drives from the thin client into the open folder on the Node. If
this is not implemented properly then it causes conflict because
what you are actually trying to do is FTP for instance the /d folder
from the thin client, into the /d folder on the GPB which will not be
seen from the Node B side. For example when the node wants to
read the file cv.ptr it would have to point to /d/d/cv.ptr, instead of
/d/cv.ptr as it is configured to do.
5 When the files are successfully transferred across to the node a
further reload has to be done to store the files on the GPB flash
Disk.
We do this by typing the command reload into the
HyperTerminal window.
Note: The Node restarts in Basic Mode now and can be viewed
from the line gpb_cs_basic mp750. The Node remains in Basic
mode for the rest of the procedure from here on.
6 If the files have been FTPd successfully to the Node you
should expect to find 37 loadmodules on the GPB. To check
this type the command pglist and wait a few mins for all
the load modules to register after the last reload.
Step 3.
Element Manager (EM) can now be used to begin commissioning
1 Open an Internet Explorer window and type the following
address with the actual IP address of the Node into the
hyperlink window http://10.31.1.1/em/index_stubbed.html
2 When the Element Manager (EMAS) window has opened the
next step is to open the Cabinet Equipment Wizard,
<Configuration>Cabinet Equipment>. This Wizard normally
does not have an XML file associated with it. It is a small
procedure with only a single page of configurations.
The Type of ET-M1 field may need to be changed here
depending on the transmission being used i.e.E1/J1/T1.
Comment [ e6] : Internet Explorer
Comment [ e7] : procedure
By clicking Next the Wizard moves through the next page
until it has reached the end of the section. A print out of the
operators choice of configurations can then be viewed before
finally accepting the Configuration settings.
3 After reaching this page there is the option to read the
configuration before saving it to the Node and creating a CV.
By clicking the Previous button, the commissioner may track
back and make corrections to the Wizard before saving it to the
Node. By clicking the Finish button, all settings are saved and
a CV is created called INITIAL_CV and set as the next
startable CV. You may now be prompted to reload the Node,
which reloads the Node with the INITIAL_CV.
It is good practice to restart the Node after each Configuration
Wizard and this can be done by either typing reload or
restartObj me into the CLI window and pressing return. The
connection to EM will be lost during the reload, so the GUI
will have to be restarted.
4 The next Wizard is the O&M Access Wizard as seen below:
For this Wizard the normal thing is to have an XML file that
contains all of the settings for this configuration. To load the
XML file just click on the O&M Access Wizard and click
Browse in the following window to select the XML file
associated with the Wizard. When you have located the XML
file and selected it, click Next at the bottom of the page.
Notice that the Wizard loads the settings needed for this
section and enters them into the control fields associated with
such settings. Again the results of the Wizard can be viewed
on the last page of the Wizard before actually clicking Finish.
The commissioner still has the option to go back into the
Wizard and make changes to the settings before saving the
configuration. Such changes may include the IP Address of the
Node for instance, may have to be changed from a generic IP
Address, generated from the XML file, to the actual IP
Address of the Node.
5 It is not essential to reload the Node here as the OAM_CV is
automatically created by EM. However it is essential to wait for
the Node to synchronise properly before the Site Equipment
Configuration Wizard can be started to avoid any instability in
the Node. The system clock must reach Locked Mode and can
take up to 25 mins to be achieved. There are two methods of
checking the Synchronization status. (See Method two before
Reloading)
Method 1
Is to go to the ATM view in EM, right click on the Network
Synchronization link and select properties. The following
should appear when the Node has reached Locked Mode:
Comment [ e8] : generic
Method 2
Is to set up a trace on the node, however this requires a reload
of the node to clear any previous logs on the node. The
following trace can be used set up on the TUB to monitor
synchronization in the Node.
$ lhsh 000400
Welcome to OSE Shell OSE4.4.1
000400> te e trace1 Nss*
000400> te save Nss*
000400> te s Nss*
000400> te log clear
000400> exit
$ restartObj me
The Node goes through a warm reload and when it returns
accessible type in the command.
$ lhsh 000400
Welcome to OSE Shell OSE4.4.1
000400> te log read
When the system has reached Locked mode then the Site
Equipment Configuration Wizard can be started.
6 The Same procedure is followed here for the Site Equipment
Configuration, as for the O&M Access Wizard. We normally
use an XML file to input the data, then sift through the Wizard
pages and click on the Finish button on the last page. Again it
is good practice to reload the node but not essential as the CV
called the SITE_CV has been created from this Wizard, and is
set as startable on the Node. If a further reload is done here it
would be wise again to wait the 25 mins for the Node to reach
Locked Mode again. Most commissioners would just move to
the next step before restarting the Node this time, and run in the
Iub script.
7 This is the final step to the Commissioning process. Using
Config File Executer from the Configuration drop down
menu, repeat section Step 3.2 for running in the Script. This
time browsing and selecting the .mo script, which the
commissioner should have in your possession for setting up the
Iub link. This script is often called
02_rbs_specific_Iub.mo
Or something similar to
Site_complete_configuration_E1_3202_FABA.mo,
-depending on the operators choice. Again the script should
come back as successful when it has been run on the Node.
8 Save the Site Specific Configuration:
A CV must now be created to save the final configuration of
the Node. From the left hand drop down menu select software.
Right click on Configuration Versions and select Create
The following window will appear:
Call the CV a suitable name and perhaps include your ID in
the comment box. Click Apply and the following window will
appear:
Click on Load Now > OK and the RBS will reload with the
new configuration.
The final step is to wait until the Node comes back up and
reaches Locked Mode. Check the LED status and ensure that
the following table is satisfied
Green LEDs All Boards On
Yellow LEDs TUB, AIUB, RFIFB, MCPA Fast Flash 16Hz
Red LEDs All Boards Off
This should only take 2-3 mins to come back into service.
9 From either a telnet session or from the HyperTerminal, use
the Ping command to try and communicate with the associated
RNC
i.e. ping <IPAddress of RNC> or for example:
ping 10.0.30.4. If the Node has been configured properly
then you should receive a reply from the RNC telling you that
it is alive. The Node should also be checked from the RNC side
to ensure proper communication both ways before the
Commissioner leaves the site.
The site should be left in a tidy manner rolling up cables and
locking doors etc, left in a way that you would like to find it.
The Commissioning is now fully completed.
Posted by Electronics and Communication at 1:10 AM

Global Services Step-by-Step Guide For Node B Commissioning

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Global Services Step-by-Step Guide For Node B Commissioning

Diunggah oleh

Hak Cipta:

Format Tersedia

Global Services Step-by-Step Guide for Node B Commissioning

Step by step guide to Node B Commissioning

Anda mungkin juga menyukai