3-BaseBand 6630 Integration Guide [PDF]

Zitiervorschau

BASEBAND 6630 integration guide

Hadi Balharith

Pre-requisite Category Netconf (XML) Script

MOS Script

Item

Format

Comment

RbsSummary File

Netconf (xml)

Mandatory for LMT Integration

SiteBasic Template

Netconf (xml)

Mandatory for LMT Integration

SiteEquipment Template

Netconf (xml)

Mandatory for LMT Integration

TN Template

Netconf (xml)

RN Template

Netconf (xml)

Feature Activation Script

Moshell (.mos)

Post Integration Script

Moshell (.mos)

Cell Relation Script

Moshell (.mos)

UP

Upgrade Package (UP)

ZIP

LKF

License Key File (LKF)

XML

PC

Client PC

Cable

Ethernet Cable

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 2

Baseband LMT - PC

Configuration Node Provisioning

› Configuration files are used to build up the node Managed Information Base (MIB). › Initially, the Site Equipment File and Site Basic File must be installed and configured. › Additional configurations are handled from OSS.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 3

RBS Summary File Node Provisioning

› The purpose of the RBS Summary File is to define the paths to other configuration files used for integration of a node.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 4

RBS Summary File › Check following from “xxx_RbsSummaryFile.xml” XML script



Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 5

Same with XML script In SFTP server

Site Equipment File Node Provisioning

› The purpose of the Site Equipment File is mainly to handle configuration of equipment. › The most important part is to set up the first DU and the TnPort on the DU, to enable Site Basic File to run, and set up the connection to OSS. › Additional equipment configuration can be modified from OSS. › Attribute default values can be modified in the Site Equipment File.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 6

Site Equipment File › As an example, a list of the breakdown of the components is outlined below: 1. FieldReplaceableUnit – the Baseband 6630 unit and associated RiPort for RU/RRU connection and TNPort, and RiLinks. 2. Radio Unit/Remote Radio Unit 3. AntennaUnitGroup 1. RfBranch 2. AntennaUnit and its associated sub-components (TMA/RET), AntennaUnit, AuPort 4. EcPort (Environment Control function) 5. EcBus 6. NodeSupport 7. SectorEquipmentFunction 8. PDU (Power Distribution Unit), SHU (Support Hub Unit), SCU (Support Control Unit), other APC unit Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 7

Site Equipment File Node Provisioning

› The following MOs below MO ManagedElement in the Site Equipment Configuration File are configured:

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 8

Configuration Flow Node Provisioning

› Part I: Create Baseband Unit/DU and set up connection to OSS › Part II: Create and Configure Equipment › Part III: Connect Equipment

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 9

Site Basic File Node Provisioning

› The site basic contains the basic Transport connectivity information of the node such as, Ethernet Port and VLAN Port, Router configuration data, and System Functions including both System Management and Security Management configuration (TLS)

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 10

Site Basic File Node Provisioning

› The purpose of the Site Basic File is to set the attributes that define security management, system management, and transport network configuration › At least one maintenance user must be added at integration. The maintenance user enables emergency access to the node. If no Maintenance User is configured at integration, no maintenance user can be configured after integration. › The maintenance user configuration is part of the Site Basic File. A maintenance user can be configured for a TLS client or an SSH client log on, or both. – For TLS client log on a trusted certificate and node credentials are needed. – For SSH client log on username and password are needed.

› Use a TLS client if possible for the maintenance user log on. If not, the SSH client is also acceptable. Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 11

Site Basic File

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 12

User Management Node Provisioning

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 13

Enrollment & Node Credential Node Provisioning

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 14

Transport Network script (Netconf) Node Provisioning

› The TN netconf file contains Transport related configuration data, such as Sctp, SctpEndPoint, and Synchronization. › Here is a breakdown of the components under Transport MO (Managed Object): 1. 2. 3. 4. 5. 6.

SctpProfile SctpEndPoint Synchronization (RadioEquipmentClock) QoSProfiles and its associated DscpPcpMap MO TimeSyncIO - to synchronize all clocks in the network to a common time FrequencySyncIO – to provide the limited quality level management support for synchronous Ethernet, 1 PPS, NTP frequency synchronization, and PTP frequency synchronization 7. Router instances referencing to QoSProfiles – LTE Router - User Traffic – vr_OAM – OAM Traffic

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 15

Transport Network script (Netconf)

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 16

Radio Network script (netconf) › The RN netconf file contains the Radio network configuration data, such as EUTranCellFdd, SectorCarrier, and necessary PLMN/MME information for the core network registration. › As an example, here is a breakdown of the primary MO components in the RN netconf file; 1. 2. 3. 4. 5.

PLMN information – MCC (Mobile Country Code) and MNC (Mobile Network Code) SectorCarrier EUTranCellFdd EnodeBFunction TermPointToMme

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 17

Radio Network script (netconf)

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 18

Integration Pre-requisite › Baseband6630 should be installed and be power on.

› Scripts prepared and stored in Client PC Save integration files (XML, Upgrade Package, MOS) to SFTP home directory (C:\BB6630)

› SFTP Server ( Core FTP) installed in Client PC › Moshell for latest version Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 19

Pre-requisite › Create Folder under C: directory like (C:\BB6630) and put all integration files (XML, Upgrade Package, MOS) inside this folder

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 20

1. Client PC Setup (1) › Client PC connects to Baseband6630 LMT port › Set Client PC IP address - IP Address : 169.254.2.1 - Subnet mask : 255.255.0.0 - Default gateway : 169.254.2.2 › Stop Antivirus software

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 21

Core sftp server settings 1. 2.

Click Setup Click New

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 22

Core sftp server settings Set the following : 1. Domain name : BB6630 2. Domain IP Address : 169.254.2.1 3. Port : 22 4. Base Directory : C:\BB6630 (create this folder if not already created) 5. Tick the check box for ▪ ▪

Disable FTP SSH/SFTP

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 23

Core sftp server settings Highlight on BB6630 account and click New under Users

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 24

Core sftp server settings Under General, Set the following : User name: rbs Password: rbs Home Directory: C:\BB6630

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 25

Core sftp server settings Under Permission: 1. Click Add , Choose the folder C:\BB6630 2. Check all the permission boxes 3. Click OK

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 26

Core sftp server settings › Click OK

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 27

Core sftp server settings At the Main page , click Start to start the SFTP Server

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 28

Core sftp server settings Make sure the SFTP is active ( BB630 active ) in the dialog box

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 29

Lmt integration pre-check › Check following from “xxx_RbsSummaryFile.xml” XML script



Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 30

Same with XML script In SFTP server

Lmt integration pre-check › Connect PC to BB6630 using LMT port. › Open a web browser and go: https://169.254.2.2/ea.html › If the node status is “Node has not been UP” proceed to the next step.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 31

Lmt integration pre-check

› If Node status shows "Node is working" then click on "Board restore" to clear all existing data from the Baseband.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 32

Lmt integration on-site › › › ›

Launch an internet browser In the address bar, enter in https://169.254.2.2 If security certificate is prompted, click on Once connected, you will see example screen below

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 33

Lmt integration on-site • • • •

In the HOST field type the IP address of the local terminal: 169.254.2.1 In the Username field type: rbs In the password Field type: rbs In the Site Installation File field type the full name of the RBS Summary File

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 34

Lmt integration on-site •

Click on Download files to start integration

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 35

Lmt integration on-site › Once the initial loading is loaded to about 65% Software Download and Install Complete appears at the bottom of the screen, the option to Integrate the BB6630 will become available › Click on “Integrate”

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 36

Lmt integration on-site › Continue to check the Auto Integration Log Box for progress of integration.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 37

Lmt integration on-site › Once the configuration file is completed, Proceed to load the TN/RN scripts if needed otherwise contact your NIC Engineer to finalize the integration. › At this time, your network loader should be at 70%

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 38

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 39

Apply RN/TN & Post Integration scripts using Cygwin/moshell › Netconf scripts are applied to the Baseband node using a Cygwin terminal window and the Moshell application. › Store the RN/TN and any other post integration Netconf xml scripts in Cygwin c:\cygwin\home\>user name< folder.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 40

Apply RN/TN & Post Integration scripts using Cygwin/moshell › Open Cygwin and go to the folder where the scripts are stored. cd /home/>user nameuser name< folder.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 49

Apply moshell scripts using Cygwin › Open Cygwin and go to the folder where the scripts are stored. cd /home/>user name< › Type ls to show the stored files

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 50

Apply RN/TN & Post Integration scripts using Cygwin/moshell › In the Cygwin window, moshell to the Baseband using the LMT port IP address. › moshell 169.254.2.2

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 51

Apply RN/TN & Post Integration scripts using Cygwin/moshell › Once connected to the Baseband, type: lt all › When prompted, type rbs for username and rbs for the password.

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 52

Apply moshell scripts using Cygwin › Execute the Feature Activation Script from Cygwin terminal. run FE_featureActivation.mos › Execute the Post Integration Script from Cygwin terminal. run post_integration.mos

› Take CV & restart the BB6630 as mentioned earlier

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 53

How to collect ESI log › Collect ESI log in case integration fails – Emergency Access Tool page (https://169.254.2.2/ea.html) – Put in required information according to SFTP server setting – Click “Export” button to export ESI log

• Host : 169.254.1.1 • Username : ftp • Password : ftp • Directory :

Baseband6630 Integration Procedure | Ericsson Internal | 2015-11-08 | Page 54