Lte Enodeb Integration Via Moshell

  • Uploaded by: Est Dleo
  • 0
  • 0
  • March 2021
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Lte Enodeb Integration Via Moshell as PDF for free.

More details

  • Words: 633
  • Pages: 8
Loading documents preview...
fnfnfnfnfnfnffn

Introduction ›



ENODEB Integration Types › Auto Integration with DHCP (BSIM) › Auto Integration without DHCP (BSIM) › Manual Integration (BSIM & Manual Activation of PCA) › Integration via Moshell/AMOS Moshell Advantage › Not Dependent on OSS. › Excellent for LTE trials as it will involve configuration changes regularly. › Excellent for troubleshooting during failures. › Requires only a client and connection cables to the ENODEB. › Scripts can be run even when transmission is not ready (Auto Integration fails if Transmission isn’t available and thus you have to result to manual integration using the PCA when transmission becomes available ) › However, BSIM is Ericsson Recommended for advantages not highlighted here.

Document prerequisites › › › ›

This document focus is on Integration with moshell OSS is available with moshell already installed. A basic software package is already loaded in eNodeB. All commands displayed or identified are on moshell unless specified.

eNodeB Logical Components ›



Hardware Components › DUL › Digital Unit LTE › RU or RRU › Radio Unit or Remote Radio Unit › Cabinet › RBS 6000 Series › Other system support modules such as PDU, BFU, SAU, SCU etc. › Antenna and Feeder System. Software Components › Basic Package

› ›

Upgrade Package MOMs and MIB

Hardware Info

Hardware MOM Info

Software MOM Info

Integration Flow

Site Basic Configuration ›

Site Basic Configuration comprises › OAM Access & Unique Logical Name Configuration (Fingerprint) › DNS Server Configuration. › Network Synchronization Configuration. › Traffic Configuration › Traffic Synchronization Configuration

OAM Access & Logical Name Configuration

Configuration verification Site Basic Configuration Verification alt (verify no alarms related to site basic configuration) get . fingerprint (verifies unique logical name configured) get 0 (verifies site name, logical name and user label configured) get 1 (verifies node local time and network sync server IP configured) ping (verifies NTP can be reached) get ipinterface=1 defaultrouter0$ (verifies configured OAM router interface IP). get hostlink ipaddress (verifies configured OAM ENODEB IP Address). ping (verifies OAM router interface can be reached) get routing (verifies static route configuration) get . dnsserveraddress (verifies configured DNS IP address)

ping st hostet (verifies status of traffic link) get hostet address (verifies configured ENODEB traffic IP) get interface=2 defaultrouter0$ (verifies configured router traffic interface IP). facc hostet ping (verifies traffic interface can be reached) st syncref (verifies status of synchronization) get syncref address (verifies configured traffic synchronization IP configured) get synchronization nodesystemclock (verify if sync is ok. (locked mode)) Site Equipment Configuration Verification alt (verify no alarms related to site equipment configuration) get . hubposition (verifies port configuration external modules within the cabinet) st hwunit (verifies status of all external modules within the cabinet) st ru (verifies status of configured radio units) st riport (verifies status of ports connecting the DUL and RUL.) st rfport (verifies status of ports connecting the RUL to the antenna system) st sector (verifies status of sector configuration) Transport Network Configuration Verification st sctp (verifies status of sctp) get . enbid (verifies configured ENODEB Identity) get enodebfunction sctp (verifies that the control plane to be used by the ENODEB has being assigned) get enodebfunction accesshost (verifies that the traffic plane to be used by the ENODEB has being assigned) st mme (verifies status of MME) get mme ipaddress (verifies configured MME termination point IP)

facc hostet ping <MME termination point IP address> (verifies termination point IP address can be reached). Radio Network Configuration Verification get . earfcn (verifies configured downlink and uplink frequencies) get . lchannelbandwidth (verifies configured downlink and uplink bandwidth) deb cell (unblocks the cell) lh ru fui get vswr (Carries out VSWR test on all the feeders if connected. Result should not be less than 14dB)

Related Documents


More Documents from "S Bhattacharya"