Vous êtes sur la page 1sur 37

SRAN17A Network Architecture

NetAct
NE3S/
HTTP
OSS
OMS
BTS
Mediator
NWI3/ MSC/VLR HLR
CORBA
GSM NSS
A
SOAM
MSS PSTN
BSC 3G Voice Core
Abis IMS

GSM UE IuCS
Um RNC MGW
IuB
IuPS SGSN PCS GPRS
WCDMA UE Uu
SBTS
S1-U
LTE-Uu
GGSN
LTE UE Internet
SGW+PGW EPC
S1-MME

MME

1 RA23101EN170GLA0 © Nokia Solutions and Networks 2017

Nokia RAN evolution to Single BTS O&M Architecture

Allows unified integration of radio
technologies on available
Develop common O&M Unified object model hardware, incl. FDD-LTE, TD-LTE,
WCDMA, GSM, Cloud and 5G.
application layer for BTS and operations Brings common operability
SW which will unify between different RATs.
New binary protocol between BTS
operations across Nokia and Mediator allows for more
portfolio and allow to M-plane binary condensed transmission which
grow into 5G and Cloud protocol translates to higher capacity and
speed of synchronisation.

Migration towards browser based
Introduce re-designed tool gives HW/OS independency
to end-user with no need of
Site manager installation. Common tool for
SingleRAN, LTE, Cloud and 5G

Confidential

2 RA23101EN170GLA0 © Nokia Solutions and Networks 2017

Single BTS O&M Components – logical view

OSS DataCenter /
vSphere
Common… everything NE3S
New Element
NetAct BTS Management
• Object model Mediator Tool

• O&M implementation in BTS SOAM IF SOAM IF

• Transport BTS

• Common element Management tool LTE

• New BTS Mediator (replaces LTE OMS.) WCDMA

GSM

Single BTS O&M code
w/
• Plan : SRAN17A, LTE, cBTS18A , 5G unified object model
Common Transport

Confidential
3 RA23101EN170GLA0 © Nokia Solutions and Networks 2017

a.BTS Mediator • Overview BTS Mediator (a.k. BTSMED) is: singleOAM Architecture • Part of BTS OAM SW Integration • loosely coupled and co-located with NetAct NBI point • Own software delivery NetAct OSS • Virtualized and bare-metal deliveries • Gets OAM metadata from BTS (minimizes SW NE3S IF changes due to BTS radio features ) BTSMED MD • Maps between BTS internal object model and management object model (visible to user) SOAM IF • Validates parameters LTE File Interface (CM/PM) / Message Interface (FM) … RAT Binary Interface BTS BTS BTS BTS 1…10 000 4 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

BTSMED Operability and Maintenance Possibility to monitor and troubleshoot mediator as independent network element • Feature covers both standalone BTSMED node instance and BTSMED cluster nodes deployments NBI • Possibility to manage BTSMED configuration – Manual parameters commission via CLI (standalone NetAct configuration) NE3S IF – Manual parameter commission via NE3S (EMS: NetAct configuration) BTSMED • Possibility to monitor BTSMED – Alarm generation based of fault notification and clearance SOAM IF based on fault clearance (resource. inbound/outbound traffic volume) … • Possibility to collect BTSMED logs BTS BTS BTS BTS 1…10 000 • Possibility of remote BTSMED backup 5 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . start/stop operations in the following four categories: • CPU utilization • RAM utilization • HDD utilization • Network utilization (number connected BTSs. severity. time. NE type) – Measurement counters with configurable retention.

ova Currently the SW package is delivered as one Open Virtualization Appliance (.Deployment Prerequisites (1/3) SW Package: nokia-btsmed-17a.x86_64.china.ova) file available from intranet access: http://hztdci01.xxxxxxxx-x.net/userContent/BTSMED/ Confidential 6 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .nsn-net.

Deployment Prerequisites (2/3) Parameters to be planned before deployment: • northboundIPAddress – BTSMED <–> NetAct connection • southboundIPAddress – BTSMED <–> SBTS connection • btsmedID – identifier to be assigned to the BTSMED Other required parameters: DNS IP address – NetAct DNS NTP server IP address Confidential 7 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

not including syslog server Confidential 8 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . and BTSMED is distributed as a separate VM vCP RAM BTSs Cells U S 4 16 5k 11k M 6 20 11k 24k • Virtual HDD 80GB. in which VMWare solution is used to deploy VMMachines. Deployment Prerequisites (3/3) HW requirements: BTSMED is designed to be deployed in NetAct data center environment.

You can ue the web browser based Web Client or the vSphere Client downloadable application to access the deloyment panel Confidential 9 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . Deployment procedure vCenter login Log in to the administrator panel.

Deployment procedure vCenter Go to the Hosts and Clusters Confidential 10 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

Confidential 11 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . Deployment procedure Procedure start Right click the vCenter Server and select Deploy OVF Template.

Deployment procedure .ova selection In the new window select the downloaded . Confidential 12 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .ova file.

Deployment procedure Rpm version In Review details the rpm version of BTSMED can be seen. Confidential 13 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

Select the datacenter used for the VM. Confidential 14 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . Deployment procedure Naming the VM Enter the name of the new VM as BTSMED.

Confidential 15 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . select where to run the deployed OVA template image. Deployment procedure Resource selection On the Select a resource window. and click Next. select the NetAct cluster.

select destination storage Select Thick Provision Eager Zeroed in virtual disk format pull down menu and keep VM Storage policy as Datastore Default. Make sure that the free disk space is more than 80GB Confidential 16 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . Deployment procedure Storage On the Select storage window.

Deployment procedure Networking On the Setup networks window. and VM Network NB destination for VM Network NB source. select VM Network SB destination for VM Network SB source. and click Next Confidential 17 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

Select Power on after deployment and click Finish. Confidential 18 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . check if all the selected parameters are correct. Deployment procedure Verification On the Ready to complete window. On the bottom of the window.

Deployment procedure Deployment progress On the bottom of the vCenter window. you can see the progress bar shows the status is In Progress. Confidential 19 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . This step will take some time to complete the Deploy OVF template task. in Recent Tasks tab.

Right click the BTSMED VM and choose Open Console. Deployment procedure Open console To do network configuration. you need to first login to the console of BTSMED VM. You can now log in as Nemuadmin/nemuuser Confidential 20 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

/opt/imp/17a.sh start BTSMED rpm version Path to the cript Confidential 21 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . [Nemuadmin@btsmed /]$ .sh script has to be run.20170915. Configuration Opening the BTSMED CLI After logging into the VM as Nemuadmin linux command line is opened. In order to start the BTSMED CLI imp-cli-control.1.a6c197/cli/bin/imp-cli-control.

/imp-cli-control. Configuration BTSMED CLI [Nemuadmin@btsmed bin]$ .sh start Tue Sep 19 10:51:04 +01 2017 ====== CLI starting ====== 8888888888888888888888888888888888888888888888888888888888888888888888888888 oooooooooo ooooooooooo ooooooooo oooo oooo ooooooooooo ooooooooo 888 888 88 888 88 888 8888o 888 888 888 88o 888oooo88 888 888oooooo 88 888o8 88 888ooo8 888 888 888 888 888 888 88 888 88 888 888 888 o888ooo888 o888o o88oooo888 o88o 8 o88o o888ooo8888 o888ooo88 8888888888888888888888888888888888888888888888888888888888888888888888888888 Version:1.0.0 Welcome to BTSMED CLI btsmed> Confidential 22 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

will take effect after btsmed restart Confidential 23 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . Configuration BTSMED CLI Before configuration the BTSMED has to be initialized using the btsmed init command btsmed init --btsmedId <btsmedId> (eg: btsmed init --btsmedId 1) btsmed>btsmed init --btsmedId 1 Btsmed init success.

Confidential 24 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .Configuration BTSMED CLI Configuration of BTSMED is done by executing the config command config set --dn /BTSMED-1 Distinguished name of the BTSMED instance in the NetAct cluster After the command is executed a script will start that will ask for user input for the specific paramers metioned in the Deployment section of this slideset.

0.Configuration ntpIPAddress2: 0.0.91.1 Please input the value or directly use the original value by northboundIpAddress: 0.0.91.0.0.0.0.0 enter tlsModeSouthbound: TLS_OR_PLAINTEXT Please input the value Please input the value or directly use the original or directly use the original value by enter: value by enter: enter enter End of parameter configuration! Confidential 25 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .67.0 Please input the value enter: or directly use the original value by enter: enter tlsModeNorthbound: Forced Please input the value or 10.0 Please input the value or northboundGateway: 0.0.218 timeZone: (GMT-11) Etc/GMT+11 10.0.0 Please input the value or directly use the original value by BTSMED CLI enter: enter /BTSMED-1 ntpIPAddress3: 0.1 20 southboundIpAddress: 0.0 Please input the value or or directly use the original value by enter: directly use the original value by enter: 10.91 directly use the original value by enter: ntpIPAddress1: 0.0.64.0.0.44.0.32.0.0.0 enter: Please input the value or directly use the original enter value by enter: southboundIpPrefixLength: 0 Please input the value or directly use the original value by enter: enter 20 northboundIpPrefixLength: 0 Please input the value southboundGateway: 0.0.0 Please input the value or directly use the original value by dnsIPAddress: 0.0 Please input the value or directly use the original value by enter: directly use the original value by enter: 10.92.92.

Configuration BTSMED CLI The configuration to take effect has to be commited to the SBTS btsmed>config commit ATTENTION : The following parameters change will cause NE Restart!!!The process of restart may last 1~4 mins BTSMED.northboundIpAddress BTSMED.southboundIpAddress Do you want to commit? (y/n) y Confidential 26 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

btsmed>config list --dn /BTSMED-1 List single configuration parameters of the BTSMED.Configuration BTSMED CLI List all the cm parameters under the MOC of the BTSMED-1. btsmed>config list --dn /BTSMED-1 --path dnsIPAddress Confidential 27 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

2. first the integration should be done and then NetAct SWM should be used to upload the SBTS SW to NetAct repository. a proper version of SBTS adaptation file has to be uploaded to the BTSMED. If the BTSMED is not integrated to NetAct.Adaptation to SBTS SW version In order for BTSMED to support connectivity from the SBTS. manual adaptation alignment has to be performer. This can be done in two ways: 1. WFT) Confidential 28 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 . In both cases the first step is to check which SW version is running on the SBTS and download the SW package from the official repository (NOLS. If the BTSMED can be integrated to NetAct.

e.20170627.xml In btsmed /opt/imp/17a.txz to get ConverterEngine.de6539/plugins create a directory named with the SW release mkdir SBTS17A_FSM4__9999_170905_002140 Put FCT and BtsMedBD.Adaptation alignment to SBTS SW version Manual To perform manual alignment: Transfer the downloaded SBTS SW to BTSMED (i.zip to get FCT and BtsMedBD.jar SBTS17A_FSM4__9999_170905_002140/FCT mkdir ConverterEngine_S1767955 put ConverterEngine.zip to get 2 files: btsmed_SBTS17A_FSM4__9999_170905_002140. by using WinSCP) unzip SBTS00_FSM4_9999_170905_002140_release_BTSSM_downloadable_A53.1.jar into ConverterEngine_S1767955 Confidential 29 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .xml into SBTS17A_FSM4__9999_170905_002140 In SBTS17A_FSM4__9999_170905_002140/FCT tar -xvf ConverterEngine_S1767955.zip and bts_sw unzip btsmed_SBTS17A_FSM4__9999_170905_002140.

sh -nt BTSMED -v BTSMED17A Check activation status: ads_client.BTSMED integration to NetAct Official guide is available under NetAct CuDo: Integration -> Integration BTS Mediator to NetAct Quick guide: 1) Activating basic network element release support metadata in NetAct: cd /opt/oss/NOKIA-integrationmanager/bin/ sh ads_client.sh -nt BTSMED -v BTSMED17A -q 2) Add maintenance region Confidential 30 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

118.91.BTSMED integration to NetAct 3) Add following services in “Network Element Access Control”: SOAM Web Service Access user/password: wsuser/wspassword 4) Configure DNS on NetAct Add one line to /etc/hosts file: 10.112 btsmed-1 Confidential 31 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

BTSMED integration to NetAct In NetAct Monitor create a BTSMED object with NE3SWS and SSH children objects: |-PLMN-<instance ID> |-BTSMED-1 |-NE3SWS-1 |-SSH-1 Confidential 32 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

1. Upgrade of BTSMED Version check After logging into the VM as Nemuadmin we can check the rpm version [Nemuadmin@btsmed ~]$ rpm -qa | grep nokia-imp rpm -e nokia-imp-17a.20170829.2fdf5b-1.china.net/view/IMP_GIT_TRUNK/job/IMP_GIT_TRUNK_RPM_PACKAGE/ New rpm has to be transfered to the BTSMED (WinSCP) Confidential 33 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .nsn-net.noarch [Nemuadmin@btsmed ~]$ New rpm can be downloaded from: http://hztdci01.

commandline.Main [ OK ] stop.Main to stop.nokia.imp.standalone.Main arg:60 Fri Sep 15 08:02:06 +01 2017 Stop redis-server [ OK ] Fri Sep 15 08:02:01 +01 2017 waiting for process:com.groupdaemon.standalone.Main to com.nokia. Fri Sep 15 08:02:05 +01 2017 Stop com.imp.noarch Fri Sep 15 08:02:00 +01 2017 ====== CLI stoping ====== Fri Sep 15 08:02:03 +01 2017 ====== GroupDaemon stoping ====== Fri Sep 15 08:02:00 +01 2017 killProcess Fri Sep 15 08:02:03 +01 2017 killProcess arg1:javaprocess arg2:com.Main arg:normal_kill arg1:javaprocess arg2:com.main.imp.noarch [toor4nsn@btsmed ~]# rpm -e nokia-imp-17a.nokia..1.Main [ OK ] iptables: Saving firewall rules to /etc/sysconfig/iptables: [ OK ] 34 /etc/sudoers.Upgrade of BTSMED RPM deletion As a toor4nsn user delete the current running rpm by executing rpm -e nokia-imp-17a.imp.bak: parsed OK RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .imp.nokia. remaining time: 60 Fri Sep 15 08:02:06 +01 2017 killProcess arg1:notjavaprocess arg2:redis- server arg:normal_kill Fri Sep 15 08:02:03 +01 2017 Stop com.imp.Main arg:normal_kill Fri Sep 15 08:02:00 +01 2017 waitForProcessToStop Fri Sep 15 08:02:03 +01 2017 waitForProcessToStop arg1:javaprocess arg2:com.imp.main.standalone.2fdf5b-1.imp.commandline.Main arg:60 arg1:javaprocess arg2:com.Main arg:60 Fri Sep 15 08:02:00 +01 2017 Stop Fri Sep 15 08:02:03 +01 2017 waiting for process:com.imp.main.Main arg:normal_kill Fri Sep 15 08:02:05 +01 2017 waiting for process:redis-server to stop.nokia.commandline.20170829.standalone.nokia. remaining time: 60 IMP and redis stopping.imp.20170829.imp.nokia.Main [ OK ] Fri Sep 15 08:02:01 +01 2017 ====== IMP stopping ====== Fri Sep 15 08:02:05 +01 2017 ====== Redis stoping ====== Fri Sep 15 08:02:01 +01 2017 ====== controlImpCore stoping ====== Fri Sep 15 08:02:05 +01 2017 waitForProcessToStop arg1:notjavaprocess arg2:redis- Fri Sep 15 08:02:01 +01 2017 killProcess server arg:60 arg1:javaprocess arg2:com.nokia.main.groupdaemon.nokia.1.2fdf5b-1. remaining time: Fri Sep 15 08:02:01 +01 2017 waitForProcessToStop 60 arg1:javaprocess arg2:com.groupdaemon..nokia.groupdaemon.nokia.

bak: parsed OK Generated a random string as password for keystore iptables: Saving firewall rules to /etc/sysconfig/iptables: [ OK ] Success to set BTSMED startup with boot Fri Sep 15 08:02:39 +01 2017 ====== IMP starting ====== Btsmed not inited.rpm n@btsmed ~]# rpm -i nokia-imp-17a.a6c197-1.20170915.noarch.1.a6c197-1.1.0.Upgrade of BTSMED RPM installation Install the new rpm rpm –i(hv) nokia-imp-17a.1 btsmed Stopping auditd: [ OK ] Starting auditd: [ OK ] chmod: cannot access `/opt/imp/data/hcache/btses/*': No such file or directory /etc/sudoers.noarch. Please init btsmedId first via CLI tool.1. 35 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .a6c197-1.rpm [toor4nsrpm -i nokia-imp-17a.20170915.noarch.rpm btsmed already exists : 127.20170915. and restart.0.

Confidential 36 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .

Upgrade of BTSMED CLI login Open the BTSMED CLI and check the configuration. if it is empty the config command has to be used to configure it again following the configuration procedure 37 RA23101EN170GLA0 © Nokia Solutions and Networks 2017 .