Sie sind auf Seite 1von 24

CHAPTER 1

1.0PROCEDURES FOR FORMATTING


NODE B
1. Launch HyperTerminal on the computer
2. Connect USB-Serial-RJ 45 to LMT A of Node B
3. Create a Connection
-set a connection name
-select a com port that USB to serial is connected
-set com properties(by restoring defaults)
4.After hyper-terminal window Appear connected
-Press enter
- user name: rbs
-Press enter
-password:rbs
-Press enter
5.Enter the following commands to format the node B and put the IP Address
Before you format first check the Basic CV if is available on the node B by performing the following command
$ Cv ls
then if the basic CV is not set you need to format Node B,Check the startable CV by perfoming the command as
shown below

formathd /c
formathd /d
vols
reload --
ifconfig le0 169.254.1.1 netmask 255.255.0.0
reload
Note:There two things to consider when commissioning DUW ,In setting ip addres for the node and mounting C2
drive you must set the node in the backup mode which is achieved through the commands below:-

$ reload -- <!- opening backup mode -!>


$mount_c2
$vols
$ifconfig le0 169.254.1.1 netmask 255.255.0.0
$reload <!Closing the backup mode!>

6.Launch Total commander


go to net
ftp connect
new connection
-set session name(as in hyper terminal)
-hostname is the ip address put using the hyperterminal=169.254.1.1
-username:rbs
-password=rbs
-OK
-CONNECT
Browse c2 and D folders from your computer and paste them on the NODE
Wait until finished
7.Launch EM and follow the following procedures

The following steps must be considered before launching Element manager


-Go to control panel
-Click network and sharing center
-Then click change adapter settings
-Set ip address as shown below and click OK

-Open element manager and click connect for the ip setted that match with the above printscreen
-Go to tools and select cabinet equipment configuration,this step is only done if the node doesnt contain an initial
CV
-To check an initial CV you can use an element manager in the drop down select Software, in some other
nodes select backup and upgrade.Otherwise run the cabinet equipment configuration as shown below:-

On the input windowdont check use configuration file


-Click next and wait a moment for the script to load

Cabinet Equipment Configuration load successfully on base station


After loading the script default IP change to 169.254.1.1

-Click next and wait for a minutes


loading

169.254.0.1 IS NOT REACHABLE ANYMORE CHANGE YOU LAN SETTING


GO TO tools then site Equipment Configuration

Select file form laptop then next, file script will be loaded on base
station hint next
Site Equipment Configuration done successfully hint OK

GO TO tools then O&M access Configuration


Select to use configuration file and wizard then next

On server configuration pls use this ip 0.0.0.0 as below


See on the moshell window I just set the clock to current time then hit
Next

O&M script loaded successful, try to ping DARNC01 IP-10.20.128.5


Ping rns
10.64.0.2
10.64.7.2 (currently)
10.64.7.4
10.50.34.
51(LTE
RNC)

DUW COMFIGURATION FOR EXPANSION OF 3G

The only thing to consider when expanding 3G on DUW 30 01 Or 31 01

-Connect optical cable from primary DUW on port F to secondary DUW on port F

-Connect other optical cable on one end labelled primary to the primary DUW on the IDL port then the other end
labelled secondary should be connected to the secondary DUW on the IDL port

-Connect EC cable from primary DUW on the AUX port to the EC port on the secondary DUW

When commissioning 3G System containing primary and secondary DUW,the secondary DUW must be formatted
first then the next step is to run the cabinet equipment configuration on the primary DUW,On running cabinet
equipment configuration c2 & d files from primary DUW will be transferred automatically to the secondary DUW
till it reaches 100%
How to install cygwin and moshell for Windows
When running on Windows, Moshell uses a unix emulator known as Cygwin.
Go directly to step 13 if you have already installed and configured cygwin previously.

1- Go to the website www.cygwin.com

2- Click on "Install Now"

3- Save the 'setup-x86.exe' file, then execute it.

4- Choose "Install from internet", then click Next.

5- Root Directory "C:/cygwin" (It is not recommended to choose a different directory, especially if it
contains spaces).
IMPORTANT: "Default Text File Type" should be set to UNIX (NOT DOS !!! otherwise ftp transfers get
corrupted). Then click Next.

6- Select Internet Connection: put the proxy settings or select "use IE settings". Then click Next.

7- Choose a Download Site. The site http://sourceware.mirrors.tds.net is recommended.

8- Select Packages: Add the following packages:


- under "Archive", select "zip" and "unzip"
- under "Interpreters", select "perl"
- under net, select "inetutils", "openssh", "openssl"
- under shells, select "rxvt"
- under "Editors" select "vim" (optional)

9- Click Next. Install will start. Wait for installation to complete.

10- Download the file 'http://utran01.au.ao.ericsson.se/moshell/cygwin_install.txt' to C:/Cygwin .

11- Click on Start --> Run. In the "Run" window, type:


c:/cygwin/bin/perl c:/cygwin/cygwin_install.txt , then press "enter" .
This will create the following files:
c:/cygwin/etc/profile,
c:/cygwin/cygwin.bat,
c:/cygwin/home/ezawhte/.bashrc,
c:/cygwin/home/ezawhte/.Xdefaults,
c:/cygwin/home/ezawhte/.inputrc.
If those files already exist, they are automatically moved to the folder c:/cygwin/tmp/installbackup.

12- Open a cygwin terminal window by double-clicking on the cygwin icon in the start menu or on the
file c:/cygwin/cygwin.bat.
The window should be black with white text and the prompt should like this: [~]$
If not, then go through all the steps again and make sure you haven't missed out anything.

13.Copy moshell file to the temp file and moshell_install to the cygwin

14. Double click moshell icon on the desk top

15.Once it pops up write the command : cd/tmp then press enter,then follow the steps as shown below
in thhe command window

MOSHELL COMMANDS ON NODE B

In order to login in the node B use : moshell <node ip address> ,eg . moshell 169.254.1.1

Command to check cabinet: cabx

Print MO LDNs and proxy ids for all or part of the MO tree currently loaded in moshell

169.254.1.1> pr Carrier
Print state of MOs (operationalState and administrativeState when applicable).

169.254.1.1> lst Utrancell=AITU01A

Restart commands from MO interface

RNCSM01> mom restartrank

RNCSM01> mom restartcause

RNCSM01> acc 0 manualrestart

Logs Handling

RNCSM02> h lg

Checking Restart Information

RNCSM01> lgvsm

RNCSM01> lgd !Node restart times!

RNCSM01> lhsh 001400 llog l !board restarts logs!

RNCSM01> cabr !all board!

Check fault on NODE B

ter | grep -i Fault

Check the hardware part fault

invh

Check T1/E1 errors


pget t1

######## CHECK Error/Fault/Failure on NODEB


ORNEK> ter | grep -i error
ORNEK> ter | grep -i Fault
ORNEK> ter | grep -i Failure

######## CHECK for BOARD FAULTY on NODEB


ORNEK> bo
######## USEFUL COMMANDS on RBS
ORNEK> get . power -> to check all power related parameters
ORNEK> get . feature -> to check all feature related parameters
ORNEK> get . license -> to check all license related parameters
ORNEK> get 0 -> to check NodeB type and other
ORNEK> get 10 -> to check nodeSystemClock
ORNEK> get . at -> to check atenation
ORNEK> al -> to check alarms
ORNEK> lga -> to check alarm history
-> to check operational
ORNEK> lgo history
ORNEK> st cell -> to check cell status
ORNEK> st aux -> to check AuxPlugInUnit staus
-> to check Retu Device
ORNEK> st ret Group
ORNEK> get . noofradio -> to monitor RadioLink on NodeB
ORNEK> get retdevice -> to check RETU status
ORNEK> get asc -> to check RETU staus
ORNEK> get . electricalantenna -> to check e-tilt
ORNEK> get . sectorantenna antennatype -> to check specific NodeB parameter
ORNEK> get . cqiAdjustmentOn -> to check specific NodeB parameter
ORNEK> get . hsScchMaxCodePower -> to check specific NodeB parameter
ORNEK> get . queueSelectAlgorithm -> to check specific NodeB parameter
ORNEK> get . eulMaxShoRate -> to check specific NodeB parameter
ORNEK> get . featureState16Qam -> to check specific NodeB parameter
ORNEK> get . featureStateHsdpaFlexibleScheduler -> to check specific NodeB parameter
ORNEK> get . flexibleSchedulerOn -> to check specific NodeB parameter
ORNEK> get . supportOf16qam -> to check specific N
ORNEK> get .
featureStateHsdpaDynamicCodeAllocation -> to check specific NodeB parameter
ORNEK> get . dynamicHsPdschCodeAdditionOn -> to check specific NodeB parameter
ORNEK> get . eulMaxOwnUuLoad -> to check specific NodeB parameter
ORNEK> get . eulNoERgchGroups -> to check specific NodeB parameter
ORNEK> get . eulSlidingWindowTime -> to check specific NodeB parameter
ORNEK> get . maxEAgchPowerDl -> to check specific N
ORNEK> get . maxEAgchPowerDlTti2 -> to check specific NodeB parameter
ORNEK> get . maxNumEulUsers -> to check specific NodeB parameter
ORNEK> get . maxNumHsdpaUsers -> to check specific N
ORNEK> get . maxNumHsPdschCodes -> to check specific NodeB parameter
ORNEK> get . maxUserEHichERgchPowerDl -> to check specific NodeB parameter
ORNEK> get . maxUserEHichPowerDlTti2 -> to check specific NodeB parameter
ORNEK> get . steeredHsAllocation -> to check specific NodeB parameter
ORNEK> get .
featureStateHsdpaIncrementalRedundancy -> to check specific NodeB parameter
ORNEK> get . featureStateEul2msTti -> to check specific NodeB parameter
ORNEK> get . hsIncrementalRedundancyOn -> to check specific NodeB parameter
ORNEK> get . dlLicFractBbPool2 -> to check specific NodeB parameter
ORNEK> get . ulLicFractBbPool2 -> to check specific N
ORNEK> get . maxhsrate -> to che
ORNEK> get . featureStateGrake -> to check specific N
ORNEK> get . eulMaxAllowedSchRate -> to check specific NodeB para
ORNEK> Cabx -----to check RBS status--
st pp *checks the number of E1s on the site

get . 16qam *shows the feature and license state on the node

If the featurestate16Qam is ACTIVATED and the license state is DISABLED it


will result in the alarm. To clear the alarm set the featurestate16Qam to
DEACTIVATED.set NodeBFunction featureState16Qam 0 *Sets the feature to
DISABLED since no license is installed on the site

Password File Fault:


RBS Library in ALEX: Operation and Maintenance -> Fault Management ->
Alarms -> Password File Fault The alarm indicates that the password required
at Security Level 1 and 2, for user access via Telnet,SSH, FTP, SFTP or a serial
port, was never set or that the locally stored passwd file has been found to
be corrupt.
RBS:
moshell Uxxxx *log onto the node
lt all *load all Managed Objects
alt *show current alarms
passwd; rbs ; rbs *resets the password on the Node B
alt *confirm the alarm has cleared

To check for any errors on the E1 links use the following command:
pmx e1 pm m 1
CHAPTER 2
CREATING 777 2K IDB

2.0 FEEDER DELAYS

From the above chat

Feeder is 7/8 inch Cable=3.7

Jumper is inch Cable=4.1

Add Total lower jumpers delay,Feeder delay band upper jumper delay to get total
FEEDER DELAY.
2.1 ESB DELAY
If CAT 5 cable is used. Delay per meter is 5ns

Multiply This value by Total length of the Ethernet ESB cable used to get total
ESB DELAY.

2.3 MASTER TRANSMITTER CHAIN DELAY


Read Master 1800 IDB

From the IDB,

Go to Configuration>Display>Information>RBS>Run

Then Read the Transmitter Chain delay from there.

This is the MASTER TRANSMITTER CHAIN DELAY on the SLAVE(777) IDB


CHAPTER 3
MINI LINK CN 510
IP address>192.168.0.2

Subnet Mask> 255.255.0.0

Default gateway>192.168.0.1(Put this in the Minilink craft Login Window)

3.1 RJ 45 TO E1 PIN CONFIGURATION


If you are doing a back-to-back configuration connecting MIN_LINK CN 510/210 or channel
bank, then you need a cross-T1/E1 cable with the following pin-outs.

RJ 45 ON CN RJ 45 ON DUG

1 RX+ 4 TX+
2 RX- 5 TX-
4 TX+ 1 RX+
5 TX- 2 RX-
TCU CABLE CONFIGURATION
END A END B
1 4
2 5
3 7
4 1
5 2
6 8
7 3
8 6
4.0 TROUBLESHOOTING TCP/IP
Procedure that you use to troubleshoot TCP/IP issues depends on the type of network
connection The that you are Manual troubleshooting

To manually troubleshoot your TCP/IP connectivity, use the following methods in the order that
they
appear:

Method 1: Use the IP Config tool to verify the configuration


To use the IP Config tool to verify the TCP/IP configuration on the computer that is experiencing
the problem, click Start, click Run, and then type cmd. You can now use the ipconfig command
to determine the host computer configuration information, including the IP address, the subnet
mask, and the default gateway using and the connectivity problem that you are experiencing.

You can also start the Network Diagnostics interface directly by using the following command:
netsh diag gui

Method 2:Use the Ping tool to test your connectivity

The Ping tool helps you verify IP-level connectivity. If you ran the ipconfig /all command, and the IP
configuration appeared, you do not have to ping the loopback address and your own IP address.
IPConfig has already performed these tasks to display the configuration. When you troubleshoot,
verify that a route exists between the local computer and a network host. To do this, use the
following command:

ping IP address; Is the ip addres you want to connect to.

In order to verify the TCP/IP has been installed successful on the computer ping the loopback
address 127.0.0.1 if the loopback address fails the possible shortcoming may be

The TCP drivers are corrupted.

The network adapter is not working.

Another service is interfering with IP.


Method 3: Use the Arp tool to clear the ARP cache

If you can ping both the loopback address (127.0.0.1) and your IP address but you cannot ping any other
IP addresses, use the Arp tool to clear out the Address Resolution Protocol (ARP) cache. To view the
cache entries, type any one of the following commands:

arp -a

arp -g

To delete the entries, type the following command:

arp -d IP address

To flush the ARP cache, type the following command:

netsh interface ip delete arpcache

c:>wmic bios get serialnumber <To check serial number of laptop>

COLOR CODE FOR E1 COMFIGURED ON ERICSSON DDF

PORT COLOUR CODE

RED BLUE

RED
2A
White_blue

Blue

2B RED_orange

Orange

WHITE orange

Orange

2C RED_green
Green

WHITE_green

Green

2D RED_brown

Brown

WHITE brown
Brown

SHU PORT COMFIGURATION

UNIT PORT

DUW B1(MASTER NODE)

DUG A5,A6,A7

PDU A2,B2

PSU A3,B3,A4,B4

BFU B5

CHRONING E1 FROM CHRONE BLOCK


STRAIGH RJ CHRONE CHRONE BLOCK PAIR #
T TRANSLATION BLOCK
TRANSLATION NUMBER

White blue RX+ TX + White Blue 01

Blue RX- TX Blue 01

White TX+ RX+ White green 02


orange

Orange TX- RX Orange 02

White green NOT USED

Green NOT USED

White NOT USED


Brown

Brown NOT USED