OSS-RC Applications for NOC Engineers

Tags
OSS-RC Applications for NOC Engineers

LNA 108 9006 R13B

Depiction

Do you have to know what data components are inside each of the LTE hubs? Do you discover arrange administration a high-weight and testing action? Every day must you react to requests for data on the status of the system, organize patterns and enhancement? This course furnishes understudies with a comprehension of the Operation Support System (OSS) apparatuses accessible on the OSS-RC for RF Engineers dealing with the LTE/SAE arrange. Understudies will figure out how to use the OSS to perform the regular operation and upkeep errands for alert administration and survey organize component arrangement.

Learning destinations

On consummation of this course, the members will have the capacity to: 
1. Module 1 - OSS Introduction: After this module, the members will have the capacity to:
2. Understand the reason and capacity of the OSS
3. Describe the capacity of the OSS equipment hubs
4. List OSS applications identified with LTE/SAE

Module 2 – ALEX: After this module, the members will have the capacity to:
1. List the errands that OSS clients can perform utilizing ALEX documentation apparatuses
2. Launch and explore the ALEX apparatus
3. Describe the structure of the OSS record library.

Module 3 - OSS Explorer: After this module, the members will have the capacity to:
1. List the assignments that can be performed with the OEX instrument
2. Locate and utilize the OEX client documentation in the OSS CPI
3. Launch and explore the OEX device
4. Launch OSS applications from the OEX device

Module 4 - ERBS Element Manager: After this module, the members will have the capacity to:
1. List the undertakings that can be performed with the RBS Element Manager device
2. Locate and utilize the Element Manager client documentation in the LTE RAN CPI
3. Describe the eRBS data sees
4. Perform setup changes
5. Launch and explore the RBS Element Manager
 
Module 5 - Fault Management: After this module, the members will have the capacity to:
1. List the highlights and elements of the OSS Fault Management environment›
2. List the undertakings that OSS clients can perform utilizing OSS Fault Management›
3. List the client apparatuses for overseeing cautions in the OSS›
4. Locate and utilize Fault Management apparatuses client documentation›
5. Describe the highlights and elements of the Alarm List Viewer (ALV), Alarm Status Grid (ASM), and Alarm Log Browser (ALB) tools›
6. Use ASM to show an outline of caution states for different hubs
7. Learn to explore and arrange the ALV to see alarms›
8. Use ALB to see caution history›
9. Export caution data from ALV and ALB to a file›
10.Develop a work stream for alert dealing with utilizing the FM devices on the OSS and CPI

Module 6 - Software Management Organizer: After this module, the members will have the capacity to:
 1. List the undertakings that can be performed by Software Management Organizer (SMO)
2. Locate and utilize the SMO client documentation
3. Launch and explore the SMO UI
4. View LTE arrange component programming and equipment data
5. Export Hardware, Software and License data from SMO
6. Synchronize SMO database data for Hardware, Software, and Licensing
7. Create CVs on eRBS and transfer to the FTP Server utilizing SMO
8. Perform eRBS wellbeing checks from the SMO   

Module 7 - Common Explorer: Configuration: After this module, the members will have the capacity to:
1. List the highlights in CEX for LTE
2. Locate and utilize the CEX client documentation in the OSS CPI
3. Launch and explore the CEX device
4. Understand the Configuration Perspective Features for LTE
 
Module 8 - Common Explorer: Status: After this module, the members will have the capacity to:
1. List the highlights in CEX for LTE
2. Locate and utilize the CEX client documentation in the OSS CPI
3. Launch and explore the CEX instrument
4. Understand Status Perspective Features for LTE
 
Module 9 - Cabinet Viewer: After this module, the members will have the capacity to:
1. List the errands that can be performed with the Cabinet Viewer device
2. Launch and explore the Cabinet Viewer to see eNodeB alerts and equipment status
3. View and translate visual pointers (LEDs) utilizing the Cabinet Viewer
4. Use the Cabinet Viewer to bolt, open and restart eNodeB module units
5. Use the Cabinet Viewer get to eNodeB data


Target group of onlookers
The intended interest group for this course is: Service Engineer, NOC Engineer

Essentials
Fruitful fulfillment of the accompanying courses: LTE/SAE System Overview, LZU1087020

Length and class measure
The length of the course is 3 days and the most extreme number of members is 8.

Learning circumstance
This course depends on hypothetical educator drove lessons given in a classroom domain

How to Configure Baseband 5212/5216 Ericsson

How to Configure Baseband 5212/5216 Ericsson

Devices:

1. Web Browser (prescribed utilize Firefox or Chrome)
2. Most recent Moshell or least Moshell 17.0c
3. RJ-45 LAN link straight
4. SFTP application
5. Programming 17A SW R5E74

Baseband Configuration Files

1. RBS Summary Script
2. Site Basic Script
3. Site Equipment Script
4. Transport Network Script
5. Radio Network Script

1. Catalyst Baseband 521x

Interface Laptop to port LMT Baseband utilizing RJ45 link straight
IP Laptop Setting 169.254.2.1
After Auto Integration finish, in AutoIntegration Web
Firewall and antivirus should be disabled on the local PC
Setting SFTP Server
- IpAddress Baseband : 169.254.2.1
- User : ftp
- Password : ftp
- Root path : Directory to Software 17A SW R5E74 and script folder

2. Open IE/Chrome/Firefox
Log in to AutoIntegration Web GUI :
https://169.254.2.2
- Host : 169.254.2.1 (IP Laptop)
- Username : ftp
- Password: ftp
- Site Installation File: /<RBS_Summary>.xml

 3. Press button ‘Download Files’ until download complete.
Proses download will appear in AutoIntegration log
After download files complete, press button “Integrate” for starting integration. Baseband will restart before integration, the process started (estimation 15 minutes).
Make sure transmission cable already connect to TRM Equipment (mandatory)

After Auto Integration complete, in AutoIntegration Web
 GUI will seem "Welcome to RBS".
 Open Moshell, sign in to RBS utilizing default IP 169.254.2.2.
If Integration process fizzled/blunder, Baseband will naturally reestablish to production line setting. Points of interest blunder check-in Emergency Access https://169.254.2.2/ea.html


4. Running Transport Network and Radio Network content by means of Netconf with summoning beneath.
!ssh - o PubKeyAuthentication=no - o UserKnownHostsFile=/dev/invalid - o ForwardX11=no - p <port_netconfssh> rbs@169.254.2.2 - s netconf < filename.xml
Case :
!ssh - o PubKeyAuthentication=no - o UserKnownHostsFile=/dev/invalid - o ForwardX11=no - p 830 rbs@169.254.2.2 - s netconf </home/enurnug/BB5212/Test/Transport_Local.xml
 Another charge perhaps useful

› Chek macintosh address switch: MCC Router=vr_Traffic3G indicate arp-store
› Ping test: MCC Router=Traffic ping 10.211.38.86 - check 2 - packet size 1000
› Make CV: acc BrmBackupManager createBackup or cvmk <backup name>
› Delete CV: acc BrmBackupManager deleteBackup or cvrm <backup name>
› Cvset and hub restart on startable CV: acc BrmBackup=XX reestablish or cvre <backup name>
› Restart Node: acc FieldReplaceableUnit=1 restartUnit

A brief guide on using moshell

A brief guide on using moshell


Introduction to Moshell commands

Moshell is a Command LIne (COLI) Man to Machine Interface (MMI) program that runs on UNIX-based operating systems. For Moshell operation in windows based terminal, another software is needed as a UNIX catalyst on the MS operating system. Windows. The software is named Cygwin.
Moshell is Ericsson's proprietary software and may only be used by Ericsson personnel. Giving copies of Moshell programs to people other than Ericsson personnel is an illegal act.

1. Moshell connection via RBS
The connection to RBS is done by inputting the following syntax command at the prompt:
moshell
2. lt command
lt (Load mo Types) is a command that is used to load Manage Object (MO) into the moshell terminal. Each MO represents a component of the RBS configuration. To load all MO from Node B is used "lt all" command.
3. pr / lpr command
The "pr" command is used to display MO from Node B. The output of the "pr" command is the Proxy number & address of the corresponding MO (LDN - Local Distinguished Name)
the "lpr" command is used to display MO and its derivatives.
Here is a variation of the use of the command "pr" & "lpr".
* pr show all MO from Node B
* pr slot = 9 display MO with LDN containing the word "slot = 9"
* lpr slot = 9 shows MO with LDN containing the word "slot = 9" and its derivative
* pr 10 displays MO with proxy id = 10
* pr 10 - 12 displaying MO with proxy id 10 to 12
* pr localcell display Mo which has localcell element in its LDN
4. st / lst command
The "st" command is used to display MO from Node B and its Operational State & Administrative State.
* st tx displays Mo which has a tx element inside its LDN and Op. & Adm state.
* lst tx displays Mo which has a tx element inside its LDN and Op. & Adm state and its derivatives.
5. get / lget command
Command get is used to view property of an MO. Similar to the pr / lpr & st / lst commands, the command get followed by the proxy id or LDN.
6. set / lset command
ATTENTION! This command in certain usage may cause Node B to be down or down its performance.
The command set / lset is used to change the value in the property of a MO.
The syntax command set is "set
7. bl / lbl command
ATTENTION! This command in certain usage may cause Node B to be down or down its performance.
the bl / lbl command is used to block a MO.
The syntax of the command bl is: bl <proxy id OR LDN>
8. deb / ldeb command
ATTENTION! This command in certain usage may cause Node B to be down or down its performance.
The deb / ldeb command is used to deblock an MO. This command is the opposite of the bl / lbl command.
The syntax of the deb command is: deb <proxy id OR LDN>
9. acl / lacl command
The acl command (action list) is used to view the list of actions that can be performed by an MO.
The acl command syntax is: acl
10. acc / lacc command
ATTENTION! This command in certain usage may cause Node B to be down or down its performance.
The acc (action call) command is used to execute possible actions in a MO.
Syntax command acc is: acc <proxy id OR LDN>
11. del / ldel command
ATTENTION! This command in certain usage may cause Node B to be down or down its performance.
The del command is used to remove MO.
The syntax of the del / ldel command is: del & ldel
12. run command
the run command is used to load the script extension mos (* .mos) which is inside the moshell folder on the terminal (laptop).
The syntax of the run command is: run <file name>
13. trun command
the run command is used to load the script extension mo (* .mo) which is inside the moshell folder on the terminal (laptop).
The syntax of the trun command is: trun
14. ctrl-z command
the command ctrl-z (control & z buttons are pressed together) is used to force out from moshell connection to node b.
15. cab / cabx command
command cab / cabx is used to display information about board name, address, status LED, temperature & production data from node b. the cab command only displays the boards located on the digital sub-rack while the cabx command also displays the auxiliary modules of node b like FU, RU, RRU & ASC. TMA not shown.
16. cv command
cv command has several options:
cvcu to see the current cv on node b
cvls to see the current cv on node b and also show another cv that exist on node b
cvmk to create a new cv.
Syntax: cvmk
cvset to set a cv that exists in a node to be startable
Syntax: cvset
cvms to create a new cv and simultaneously set it as a startable cv
Syntax: cvms
cvrm to remove a cv from the configuration. Note: deleted cv is not the last cv created or cv that is in the rollback list.
Syntax: cvrm
17. al command
The al command is used to view the current alarm on node b.
18. lg command
command command is used to extract logs from rbs. The extractable logs are:
log lga alarm
log event lge
log system lgs
log availability lgv
log upgrade lgu
log command lgo
each of the above options can be combined in a single command, for example lgae will extract the event logs & event logs simultaneously.
Specific extracts at any given time can be done by adding the time attribute behind the lg command, for example:
lga 2007-11-10 extract log alarm that occurred on November 10, 2007-12-04
lge 30 extract event logs over the last 30 days
lgs 5h extract log system for last 5 hours
lgv 30m extract log availability for the last 30 minutes
19. pget command
The pget command is used to display the performance of an MO.
Syntax: pget


Tutorial Restore CV RBS

Tags
Troubleshooting DUW or DUS Via CMD Jika Data DUW Corrupt

 Berikut tool yang perlu di siapkan :

1.  Siapkan DUW baru
2.  Siapkan Cable RJ45 untuk connect DUW Ke Laptop (via CMD/Command Promt)
3.  Siapkan Cable Bafo untuk connect ke DUW (via Hiperterminal)
4.  Siapkan UP atau Upgrade Package 3G (versi lengkap all UP bisa hubungi saya)
5.  Siapkan CV Backup 3G site tersebut (versi ter update bisa minta di NOC)
6.  Setelah mendapatkan CV dari NOC, pilihlah UP yang sesuai dengan CV tersebut.
7.  Buat folder di C:\ di laptop misalkan “restore”
8.  Extract CV dan UP tersebut, kemudian copy masukan ke folder “restore”
9.  Ganti DUW yang lama dengan DUW baru 
10. Format DUW baru
-   Connect Laptop ke DUW menggunakan Cable Bafo
-   Masuk software Hiperterminal
-  Ketik command “vols” untuk melihat kapasitas data C dan D di DUW (biasanya total usednya 0% untuk DUW baru)
-   Ketik “reload --"untuk memunculkan c2
-    Setelah muncul c2 dan d
-    Format data c2 dengan command “formathd /c2”
-    Format data d dengan command “formathd /d”
-    Cek IP default DUW dengan command “ifconfig”
-    Kemudian setting IP default DUW dengan command “ifconfig le0 169.254.1.1 netmask    255.255.0.0”
-    Kemudian cek lagi IP default DUW dengan command “ifconfig” jika muncul keterangan broadcast berarti IP sudah sukses di setting
-    Jika IP setting Failed, ketik “reload --" ulangi langkah diatas
-    Kemudian reload DUW dengan command “reload” dan DUW sudah sukses anda format
11. Langkah selanjutnya masuk command promt
12.Kemudian setting cmd dengan CV dengan command “ cd c:\restore\(nama CV)\misc “kemudian enter
13. Kemudian Transfer CV Ke DUW dengan command
“ ftp –v –s:cvftpput.sh 169.254.1.1” kemudian enter
14. Close cmd kemudian masuk lagi
15. Setting cmd dengan UP dengan command “ cd c:\restore\(nama UP) “ kemudian enter
16. Kemudian transfer UP ke DUW dengan command
“ftp –v –s:/restore/(nama CV)/misc/upftpput_CXP9023291%2_R4JA14.sh 169.254.1.1”
kemudian enter

17. Tunggu beberapa saat hingga UP tercopy ke DUW
18. Restart DUW dari Hiperterminal dengan command “reload”
19. Langkah terakhir, coba anda monitoring, jika sudah teremote hubungi NOC untuk clear alarm Licence Key
20. Selamat mencoba, semoga sukses good luck....





Step by step BRING UP OAM

COMMAND BRING UP OAM ( jika script gagal running)
Ver.1.0

1. Pertama sobat pastikan mempunyai file Planingnya, misalkan contoh di bawah ini "HCP_RAN_JKT_Summary IP Planning Inner Jabodetabek_V876_02_Apr_2017". File ini penting untuk mengetahui data konfigurasi. Jika belum mengetahui hubungi RTS sesuai region anda.
2. Sobat buka file tersebut dan klik di sheet RNC anda, di contoh RNC MM2
3. Di contoh ini kita coba ambil sample site 91469, tandai dengan warna lain site tersebut untuk mempermudah pencarian anda. Seperti contoh dibawah ini site 91469_PLASASENAYAN_3G kita warnai dengan warna kuning
4. Setelah step 1,2 dan 3 sobat lakukan maka sekarang silahkan login local LMT melalui laptop anda.
5. Setelah login berhasil, sobat coba masukan command LST DEVIP pada colom command input seperti contoh dibawah ini.
6. Ketik command LST IPRT, kemudian execute.
7. Selanjutnya kita remove Destination IP yang sesuai segmen IP login local anda, dengan command RMVW IPRT.
8. Setelah remove berhasil kita tambahkan IP Route baru sesuai planning. Pastikan file IP plan tadi sudah anda buka. Masukan command ADD IPRT. Sobat akan menumakan banyak IP pada kolom NODEB Service dan NODEB OM, sesuai judul title abaikan NODEB SERVICE, focus cari pada kolom NODEB OM dan VRRP Gateway, Setelah sobat yakin benar kemudian EXECUTE
9. LIST IPRT kembali dan cek apakah NEXT HOP IP pada segmen IP yang anda tambahkan sudah berubah dengan NEXT OP IP baru, jika sudah lanjutkan step berikut nya.
10. Masukan command RMV VLANCLASS dan isi sesuai konfigurasi exixting. Tujuan command ini untuk menghapus VLAN ID existing. isi masing masing sesuai site, seperti gambar berikut:
Lakukan command ini sebanyak jumlah VLAN Group pada hasil yang muncul. Pada contoh diatas ada 3 VLAN Group dengan 3 Traffic Type. scrip contoh diatas akan seperti ini
RMV VLANCLASS:VLANGROUPNO=1,TRAFFIC=OTHER; RMV VLANCLASS:VLANGROUPNO         =1,TRAFFIC=OM_HIGH; RMV VLANCLASS:VLANGROUPNO         =1,TRAFFIC=OM_LOW;

Pada script diatas Traffic Typenya bebeda sesuai konfigurasi pada VLAN Group 1. 
Jika sudah dipastikan semua fill terisi dengan benar, lanjutkan dengan Execute 
11. Setelah sukses kita remove selanjutnta kita akan akukan penbahan dengan VLAN ID baru. Masukan command ADD VLANCLASS. Isi data sesuai konfigurasi existing tadi.
12. LST VLANCLASS isi VLAN Goup No dengan angka 1. Pastikan VLAN ID baru anda sudah berubah dengan VLAN ID baru sesuai data pada  IP PLan
13. Kita lakukan konfigurasi pada VLANMAP, masukan command LST VLANMAP
14. Setelah  sukses,  lanjutkan  dengan  penambahan  VLANMAP  baru.  Masukan  command  ADD VLANMAP
15. LST VLANMAP dan pastikan NEXT HOP IP sudah berubah sesuai dengan yang tertera pada IP Plan file.
16. Selanjutkan masukan command ADD DEVIP 
yang kosong isi sesuai title yang tertera pada hasil LST DEVIP anda sebelumnya pada Step 5-6, kecuali kolom IP ADDRESS masukan IP dari file IP Plan di kolom VRRP Gateway dalam kolom NodeB OM 
Jika sudah yakin dengan file konfigurasi yang anda input selanjutnya klik tombol Execute 
17. Masukan command LST OMCH, execute 
Pastikan sobat menyimpan konfigursi existingnya
18. Masukan command MOD OMCH dan isi fill yang kosong KECUALI Local IP 
Untuk fill LOCAL IP pastikan data yang sudah dimasukan benar pada setiap kolom, lanjutkan dengan menekan tombol execute
19. SELESAI. Jika masih belum up coba lakukan LST pada semua konfigurasi diatas, pastikan data anda benar benar sudah sesuai dengan data yang tertera pada IP PLan. Seperti contoh berikut scriptnya :
-  LST DEVIP:;
-  LST IPRT:;
-  LST VLANCLASS:;
-  LST VLANMAP:;
-  LST OMCH:;

Opsi A : Sampai sini seharusnya site anda sudah bisa dimonitoring. Infokan ke BO Wireless untuk proses bring up Service.

Opsi B : Jika semua data anda sudah sesuai dengan IP Plan tapi site belum up/OM belum naik, coba cek dengan BO Transmisi apakah Linknya sudah tembus, apakah VLAN dan sitenya sudah di create dari sisi transmisi?.

.:: END, SEMOGA BERMANFAAT ::.

procedure for replacing duw bts ericsson

1. Description

This instruction describes procedures for replacing DUW without opening flash card and make warranty seal broken.
There are 3 method can be use for replacing DUW :
1.    Replace DUW – NodeB with Dual DUW (StandbyReady DUW faulty)
2.    Replace DUW – NodeB with Dual DUW using copy /c and /d  (Active DUW faulty )
3.    Replace DUW – NodeB with Single DUW using copy /c and /d
4.    Replace DUW – NodeB with Single DUW using restore a configuration version (CV)

All above procedures are executed from a PC/laptop that has serial and Ethernet connections to the node. The node does not have to be operational, but at least the DUW must be free from hardware faults.

This procedure base on OPI 119/1543-CRX 901 49/1 Uen N with additional of some screenshots of each step to make this document easy to be understand and to minimize human error.

2. Prerequisites

2.1. Document
Emergency Restoring a Configuration Version Backup (119/1543-CRX 901 49/1 Uen N)

2.2. Tool
•    Serial cable (IND 2040457 / M3) => direct connection
•    Ethernet cable (RPM 901 110 / M3) => direct connection
•    LAN cable => Ethernet via APP
•    RJ45 to serial cable => serial via APP
•    Serial to USB converter
•    Screwdriver Torx 8

2.3. Conditions
Before starting this procedure, ensure that the following conditions are available
1    Upgrade Package (match to CV)   
2     Latest CV backup from OSS   
3    Amos / Element Manager   
4    SecureCrt/Putty/Hyperterminal for serial connection  

3. Procedure

3.1. Replace DUW – NodeB with Dual DUW (StandbyReady DUW faulty)

When replacing a faulty DU, the replacement DU must have the same capacity as the faulty DU.
Note: It is not recommended to have any basic CV installed in the new DU, to avoid using the wrong CV for configuration.
If one of the DUs is replaced in a dual DU configuration, the node identity does not change
Note: It is recommended to change only one DU at a time, to avoid reconfiguring the RBS and to minimize RBS downtime

1.    Lock the DU to be replaced.
2.    Switch OFF the power to the DUW to be replaced using on / off button on the Power Distribution Unit (PDU) corresponding to the DUW.
3.    Disconnect all cables from the DU to be replaced.
4.    Replace the DUW with a new DUW.
5.    Put back all cables except “IDL” cable
6.    Switch ON the power to the DUW newly replaced using on / off button on the Power Distribution Unit (PDU) corresponding to the DUW
7.    Connect using serial cable
- DB9 connector on serial cable to COM1 of the client / laptop.
- RJ-45 connector on serial cable to LMT A port (DUW 20 01or DUW 30 01) or to LMT port (DUW 41 01)
8.    Use any software for terminal emulation in the PC, for example Windows HyperTerminal/ SecureCrt/Putty, and configure it for communication over COM1 with the following parameters:
a.    baud rate = 9600 bits per second
b.    parity = none
c.    stop bits = 1 bit
d.    data bits = 8 bits
e.    flow control = none / XON/XOFF
9.    In the communication window of the terminal emulation software, click OK or press Enter
10.    The $ prompt is shown indicating that a serial connection to the DU is established
11.    Enter backup mode by using command “reload  --” 
12.    Verify that the /c2 volume is mounted, using the command vols /c2.
 If the /c2 volume is not mounted, mount the volume, using the command: mount_c2.
13.    Use command “vols”
14.    Please pay attention that in backup mode /c will become /c2 but /d will remain /d
15.    Format the /c2 disk using the command formathd /c2
16.    Format the /d disk using the command formathd /d
17.    Use command reload
18.    Plug-in the Inter-DU Link-cable (IDL) to new DUW.
19.    Turn Off and then Turn On both DUW.
20.    New DUW will restore automatically / synchronizing
21.    Check the result from existing DUW by Connect using Eth connection (RJ-45 cable) LMT B     port (DUW 20 01 and DUW 30 01) or to LMT port (DUW 41 01)
22.    Use the Element Manager or AMOS to check the state of faultTolerantCoreStates on MO ManagedElement.
The already configured DUW has state Active.
The new DU has state PassiveNotReady during the restore procedure. This can take several minutes.
The new DU has state PassiveReady when the restore procedure is finished.
23.    Unlock the new DU
24.    Check the optical indicators; check the indicator status and ensure that all configured hardware is functional
25.    Check the alarm list using the RBS EM and verify that there are no alarms indicating DU problems