Book 1 PW Ipt Ic Level 1

Parallel Wireless

LTE RAN Solution

Training – Course – 4
PW Solution I&C – Level‐1
System Installation & Commissioning

Day 5
Copyright © 2019 Parallel Wireless Inc. All Rights Reserved
This document is produced and copyrighted by Parallel Wireless, Inc. Under federal copyright laws,
this document may not be copied, in whole or in part, without the written consent of Parallel
Wireless, Inc.
9/21/2019
CWS Hardware and
HetNet Gateway S/W
Rel. 4.3.x
Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1
Objectives
• HNG software architecture
• Logical components of CWS
• Logical components in HNG
• HNG Hardware
• CWS Hardware
• Public Safety specific hardware
• Installation examples
1
9/21/2019
HNG – Software Architecture
HNG
Virtualization Manager
Virtualization Manager ‐ allows operators to
share CWSs capacity and traffic separation to
control end‐to‐end QoS. Virtualization also
allows operators to fully utilize available
bandwidth based on service level agreements.
The Virtualization Manager within the HetNet
Gateway provides two‐way virtualization, making
it possible to interface with a Mobile Virtual
Network Operator (MVNO):
HNG • Access Network Virtualization Layer
• EPC Virtualization Layer
2
9/21/2019
Call Manager
Call Manager ‐ maintains the mapping between
CWS and UE. This relationship data helps HetNet
Gateway to perform call admission control and
Traffic Policy Manager for marking the user plane
data
HNG
Backhaul Manager
Backhaul Manager ‐ is responsible for managing
backhaul technologies Whitespace/Wi‐Fi/4G and
Ad‐hoc/meshed wireless (licensed and un‐
licensed) for CWS nodes. When CWS wants to
enable backhaul meshing it will request Backhaul
Manager to assign a frequency for the available
backhaul technologies. Backhaul Manager will
analyze the CWSs neighbor Radio conditions and
allocate a suitable available backhaul frequency to
HNG the CWS
3
9/21/2019
Call Admission Control
Call admission control ‐ decides, if a call request is
admitted or rejected based on number of
virtualized resource available per operator to
guarantee QoS requested. It also assures that if a
call is accepted, QoS of already accepted calls will
be maintained. Call admission control uses the
virtualization algorithms for this function as
explained in Virtualization Manager Section to
admit or reject new calls
HNG
Data Path Manager
Datapath Manager or S1‐GW Manager ‐ hides the
CWS deployment topology from EPC and act as S1
GW for S1‐MME and S1‐U interfaces between CWS
and EPC Core. S1‐GW Manager can virtualize single
or multiple CWSs and present virtualized CWSs as
a single CWS node or multiple CWSs to multiple
operator EPC cores with unique Global eNodeB Id
HNG
4
9/21/2019
Traffic Policy Manager
Traffic Policy Manager or Backhaul Traffic and
Policy Manager ‐ appends the user plane data
with the operator assigned priority for the user,
if user plane data is destined for meshed CWS.
This priority will later be assigned to the user
based on subscribed services or user service
level agreements. When the host CWS receives
the user data it looks at the priority marking and
sends the user plane data to next hop meshed
HNG CWS node on the backhaul frequency assigned
to the priority.
If the resources are not available for assigned
backhaul frequency then CWS will use the best
available backhaul frequency, if resources are
available.
SON
SON ‐ The HetNet Gateway virtualized SON Server

employs a hybrid approach that combines
distributed and centralized algorithm deployments
to ensure a wider area of coverage on a slower
time scale.
HNG
NOTE : SON features such as Self Config, Optimisation and Healing will be discussed in detail in sperate section
10
5
9/21/2019
HNG NFV Architecture
Based on Open ETSI NFV NFV Management &
Orchestration
OSS/BSS Orchestrator
VNF Working Domain
EMS EMS EMS VNF
Management
Gateway C‐RAN, SON Security
Virtualisation Layer
Virtual Compute Virtual Storage Virtual Network
Virtualised
Infrastructure
Manager
Computing Storage Networking

Hardware Hardware Hardware
Hardware Resources
11
Gateway VNF NFV Management &
Orchestration
Gateway VNFs:
3G Gateway Functions
• HNB Gateway/Virtual RNC (vRNC)
OSS/BSS Orchestrator • Small cell/femto gateway
• Security GW
• SON
4G Gateway Functions
VNF Working Domain • S1 Gateway
EMS EMS EMS VNF • X2 Gateway
Management • Super Cell/Virtual‐eNB
Gateway C‐RAN, SON Security • Small Cell gateway/HeNBGW
• Security GW
• SON
Wi‐Fi Gateway Functions
Virtualisation Layer • Wi‐Fi Controller/Trusted and Untrusted
Wi‐Fi Gateway (TWAG/SaMOG, ePDG)
Virtual Compute Virtual Storage Virtual Network • SON
Additional Capabilities
Virtualised • MEC
Infrastructure • MOCN
• IoT
Manager
• Unlicensed Assist Backhaul (SDN)
EPC Functionality
Storage Networking
• MME
Computing
Hardware Hardware Hardware • SGW
Hardware Resources • PGW
12
6
9/21/2019
C‐RAN and SON VNF NFV Management &
Orchestration C‐RAN and SON VNF :
• Multi‐technology: 3G, 4G, Wi‐Fi
OSS/BSS Orchestrator • C‐RAN follows Moore’s Law
• Works with gateway VNFs to provide
true cloud‐based C‐RAN
VNF Working Domain • Not proprietary
EMS EMS EMS VNF • Standards‐based
Management • Virtual RNC
Gateway C‐RAN, SON Security • Real‐time
• Parallel scheduler leveraging X2
Brokering
• Real‐time SON (load balancing)
Virtualisation Layer • Dynamic resource allocation
• MEC (video traffic optimization)
Virtual Compute Virtual Storage Virtual Network • SDN (unlicensed assisted backhaul,
QoE)
Virtualised
• Wi‐Fi orchestration via ANDSF+ and HS
Infrastructure
2.0
Manager

Hardware Resources
13
Security VNF NFV Management &
Orchestration
Security VNF:
• Unifies security across all RAN, VNFs +
OSS/BSS
mesh
Orchestrator • 3GPP‐based standard IPsec
• Security gateway for licensed and
unlicensed (Small Cell gateway,
VNF Working Domain TWAG/SaMOG, ePDG)
EMS EMS EMS VNF
• Secure authentication
Management
• Virtualized DPDK fast path
Gateway C‐RAN, SON Security
Virtualisation Layer
Virtual Compute Virtual Storage Virtual Network
Virtualised
Infrastructure
Manager

Hardware Resources
14
7
9/21/2019
Functional Division in CWS and HNG (VeNB) ‐ LTE
CWS • Intercell RRM • Intercell RRM Control
VeNB
• RB Control • RB Control
• Connection Mobility Control • Mobility Control SON
• Radio Admission Control • Admission Control
• eNB Measurement • CWS Measurement
Configuration and Provision Configuration and
• Dynamic Resource Provisioning
Allocation (Scheduler) • Dynamic Resource
Allocation (Scheduler)
• RRC • S1AP • S1AP • S1AP
• PDCP • SCTP • SCTP • SCTP
• RLC • IP • IP • IP
• MAC • MAC • MAC • MAC
• PHY • PHY • PHY • PHY
15
Functional Division in CWS and HNG (vRNC) – 3G
• RAB Management • HNB Management
CWS
• Radio Resource Mgmt
vRNC
• Iu Signalling Link Mgmt • UE Management for HNB

• GTP‐U Tunnels Mgmt • Iuh User‐plane Mgmt
• Buffer Mgmt • Iuh User plane Transport
• Mobility Management Bearer Handling
• Security Functions
• Service and Network Access • Iu Link Mgmt Functions
• Paging Co‐ordination • Security GW Function
• UE Registration for HNB • HNB‐GW Function
• Iuh user‐plane Management
• HMS Function
RRC RANAP RANAP RANAP
RLC SCCP SUA SCCP SUA
M3UA M3UA Signaling

MAC Transport
SCTP SCTP
PHY IP (IPSec) IP (IPSec)
16
8
9/21/2019
Logical component in CWS
17
CWS – nk Functional Components
TRX1
GPS
TRX2
RF
BBP‐Master BBP‐Slave
SFP (CWS/HNG) PoE ( To BHM/CWS/HNG)

18
9
9/21/2019
CWS – nk Logical Components
GPS
• Performance Manager (perfmgr)
• Config Manager (cfgmgr) 4G / 3G
• Fault Manager (faultmgr) Access
• Platform Manager (platmgr)
Radio
• System Manager (sysmgr)
• OAM Manager (oammgr)
• SON Client
BBP + RU
To CWS/HNG
PoE‐PSE (Ethernet to BHM
19
BHM Functional Components
LTE BH
Radio
• LTE Modem
• Mesh Modem
• Wi‐Fi Access
• Routing
Wireless
Mesh
Radio
GPP
Ethernet RJ‐45 (PoE‐PD) Ethernet RJ‐45 (PoE‐PS)
(Can go to HNG or CWS) (Can go to other BHM or CWS)
20
10
9/21/2019
MWS Functional and Logical Components
GPS
• Performance Manager (perfmgr)
• Config Manager (cfgmgr)
• Fault Manager (faultmgr) 4G
• Platform Manager (platmgr) Access
Radio
• SON Client
BBP + RU
RJ45 ‐ Ethernet to CCH
21
CCH Functional and Logical Components
Wi‐Fi Access
LTE BH
Radio
• LTE Modem
• Mesh Modem
• Wi‐Fi Access
• Routing
Wireless
Mesh
Radio
GPP
Port#1 MWS Port #2 and #3 ‐To Vehicle devices
(RJ45) (RJ45)
22
11
9/21/2019
Logical Components in HNG
23
HNG in LTE
24
12
9/21/2019
HNG in UMTS
25
HNG in GSM
S
E
G
W
26
13
9/21/2019
HNG in Untrusted Non‐3GPP
27
IP Sec Gateway in HNG PKI – Public Key Infrastructure

SCEP – Simple Certificate Enforcement Protocol
CMP – Certificate Management Protocol
IP Sec Tunnel Workflow CA ‐ Certificate Authority
OCSP ‐ Online Certificate Status Protocol
PKI UniManage
CA
MME
SCEP
CMPv2 OAM
S‐GW
Factory Certificate (Primary) Tunnel
Initial config specs for the
1
eNodeB operational certificate fetch
SGSN
LTE
NodeB HNG UMTS

Operational Certificate Tunnel
WiFi
WiFi OAM
LTE MGW/MSS
UMTS 2
WiFi
OCSP / CMP
CWS
ePDG
OCSP – Protocol used by HNG to get the certificate status from CWS
CMPv2 – Protocol used to fetch the certificate from CA to CWS
28
14
9/21/2019
HNG and CWS Hardware
29
HetNet Gateway
Minimum Hardware Configuration for PoC
• HP DL360 Gen9 or equivalent 2 socket x86 server

• Intel Xeon E5-2697v4 (18 core), 2.3 GHz
• Total processors: 2
• Minimum 128GB of RAM
• One or two 2x10GbE NICs. Intel X710 or 82599 based NICs recommended
• 4x1GbE NIC
• Minimum 256 GB disk space
• Hardware RAID controller
• Dual redundant power supplies
• System capacity:
• 5 Gbps – 20 Gbps with IPsec (Depends on ordered configuration)
• Up to 25000 APs (Combination of HNBs and HeNBs)
30
15
9/21/2019
HetNet Gateway
Minimum Hardware Configuration for Public Safety
• HP C7000 enclosure with BL460c Gen9 blades.
• Each blade has following configuration
– Intel Xeon 2 x E5‐2699v3 (18 core), 2.3 GHz
– Total processors: 2
– 64 GB RAM
– 2x10Gb NIC1 (HP 536FLB: QLogic 57840S)
– 2x10Gb NIC2 (HP 560M: Intel 82599)
– 2 x 1TB disks
– Hardware RAID controller
31
CWS Hardware
32
16
9/21/2019
CWS Family: Ideal for Rural, Urban and Public Safety
CWS‐1000 CWS‐2000 CWS‐3000
 Multi‐mode, multi‐band
 Most compact and light
weight high performance
high power macro: radio,
filter, baseband, edge router,
integrated backhaul ‐‐ just
add antenna (power supply is
integrated in SCO design)
 Various outdoor installations All major 3G/4G bands
 Low power consumption Integrated flexible backhaul
 LOW OPEX AND CAPEX Pluggable backhaul mesh and Wi‐Fi
 Self‐configuring and self‐ • TX/RX: • TX/RX: • TX/RX:
optimizing via HNG 2T2R for 4G 2T2R for 4G 2T2R for 4G
1T2R for 3G 1T2R for 3G 1T2R for 3G
 Much lower cost • RF Output: 2 x 5 Watt • RF Output: 2 x 20 Watt • RF Output: 2 x 40 Watt
 Self‐configuring and self‐ 2T2R‐ 2 x 5W 4G 2T2R‐ 2 x 20W 4G 2T2R‐ 2 x 40W 4G
optimizing via HNG 1T2R – 1 x 5W 3G 1T2R – 1 x 20W 3G 1T2R – 1 x 40W 3G
• 126 Watts power consumption • 205 Watts power consumption • 325 Watts power consumption
• Weight: 6.5 Kg/13 lbs • Weight: 10.3 kg/22.7 (w/brackets • Weight: 11.1 kg/24.5 lbs
and sun guard)
33
(To BHM / Wi‐Fi Access) 30 W PoE
(To HNG / CWS)
GPS Port
(3G/4G Access) (3G/4G Access)
BOTTOM TOP
34
17
9/21/2019
CWS‐nk Connectors
35
CWS – 210 – In‐Vehicle CWS
• One LTE (or 3G) 2x2 MIMO radio slot
• 0.5W+0.5W (nominal – before RF filter/duplexer/switching loss) radio, bands: 3 (1800 MHz), 4 (1700
MHz), 8 (900 MHz), 13 (700 MHz), 14 (700 MHz), 17 (700 MHz), 20 (800 MHz).
• 3 PCIe minicard slots (2 Wifi radio/ 1 LTE UE)
• USB Port
• Integrated GPS Receiver
• DC power (12/24V automotive)
36
18
9/21/2019
CWS Family: CWS‐210 Specifications
Architecture High‐capacity platform for instant resilient coverage Throughput  Downlink/Uplink @ 20MHz
anywhere o 2x2 MIMO : 150Mbps/75 Mbps
Flexibility  Auto‐config Security  Network connection security: IPsec
 Self‐healing  Device security and authentication: Certificate
Air Interface 3GPP Release 9 compliant and software upgradeable  Air interface integrity and ciphering: 128‐
to any future releases EIA1(SNOW 3G) , 128‐EIA2 (AES), EIA0 (Null), 128‐
EEA1 (SNOW 3G), and 128‐EEA2 (AES), EEA0 (Null)
Software Features  QoS based mesh routing
 SON resource control Resilience Full hardware and software redundancy through HetNet
 Low latency links (< 2ms round trip) Gateway
Timing Support Built‐in GPS Dimensions  Height 6.99 cm (2.75 ins), Width 24.13 cm (9.5 ins),

and Weight Depth 24.13 cm (9.5 ins)
Antenna type Connectors for long haul link support with high  Weight 2.72 kg (6 lbs)
gain/narrow beam antenna & omni/sectored antenna
Temperature Vehicle enclosure (‐30 °C to +50 °C)
Frequency Bands All major LTE frequency bands supported
Input Power 12 ‐ 24 VDC
RF and backhaul  5, 10, 20 MHz 2X2 MIMO LTE radios, 1W
 Wi‐Fi Access: 2X2 MIMO, WPA 2 Enterprise Power 60W
encryption, dual band 802.11a,b,g,n, Consumption
 Built in SDN mesh backhaul: multi‐radio mesh, up Peak Power 2x0.5W (2x27dBm). Adjustable. Maximal power varies
to 2X2 MIMO, 40 MHz wide, WPA 2 Enterprise Output depending on data rate, frequency band and country
grade encryption setting
User Capacity 64 active/128 connected users (software limited)
37
CWS‐210 – Ports and Connectors
38
19
9/21/2019
CWS Family: CAP
Single Mode ‐ CAP Dual Mode ‐ CAP
39
CWS Family: CAP
Flexibility Virtualized design: functions based on software are not coupled Antenna LTE 2x2 MIMO External Antenna
to hardware. SON support Wi‐Fi 2x2 MIMO External Antenna
Air Interface  3G/UMTS: Release 6 compliant Transmit Power LTE 21 dBm Output Power (single path)/23dBm (aggregate)
 4G/LTE: 3GPP Release 8, 9 compliant (Rel. 10 support in Output Wi‐Fi 17dBm Output Power (single path)/20 dBm(aggregate)
later phase, future upgradable to other releases) UMTS: 23 dBm 1T,2R
Timing Support Wireless Sync, NTP or IEEE1588 Adjustable. Maximal power varies depending on data rate, frequency
Supported Operating Bands Major frequency bands can be supported by customer request band and country setting
Wi‐Fi Access WPA 2 Enterprise encryption, 2x2 dual band concurrent Network Sniffing 3G: Band1 ‐2100MHz
802.11a,b,g,n, ac Support options 4G: Band3‐1.8GHz
Bandwidth 5,10, 15, 20 MHz Interference Fully automatic via HetNet Gateway
management
Throughput 150/50 DL/UL
Indicators * Power * Internet * LTE signal *UMTS signal
Wi‐Fi Frequency 2.4 GHz and 5GHz
* 5 GHz * 2.4 GHz * LAN
User Count LTE 32 users & UMTS 32 users
Interfaces  Power jack
Dimensions Single mode CAP: 221.78mm x 221.77mm x 35.02mm
 Power switch on/off button
Multi‐mode CAP: 271.2x235x42.8mm
 Push button for factory reset
Operating Temperature Indoor enclosure (0 °C to +40 °C)  IEEE802.3 10/100/1000 Ethernet Port ( RJ45)
Operating Humidity 10% to 95% RH non‐condensing Emergency Call Support for E911, 112, 999, and other national and international
Power Consumption 30 W typical Support standards for emergency voice call services
Auto‐configuration Zero‐touch mechanism via HetNet Gateway
40
20
9/21/2019
Backhaul Module
BHM‐101 BHM‐201
41
BHM Specifications
Capability BHM‐201 Security All communication with the BHM is over IPsec with
hardware itself supporting a secure boot.
# of radios 1/2 Wi‐Fi Radio  3.5W max diss.
 Dual Band (2.4/5.8)
Radio configurations  Single Mesh  2x2 MIMO
 Sngle LTE Backhaul  802.11 a/b/g/n/ac
 Dual LTE Backhaul  17‐23dBm (total, for two chains) transmit power
 Dual Mesh LTE Radio  US and EMEA bands: LTE‐A: B1‐B5, B7, B8, B12, B13,
B20, B25, B26, B29, B30, B41
RF Connectors & (4) N‐type antennas:  Support Carrier Aggregation
Antenna Ports  The LTE antenna ports are N‐type connectors  23dBm transmit power
 Two Wi‐Fi antenna ports, N‐type connectors LTE Backhaul Supports commonly used bands for LTE backhaul.
Connectors  Four N‐type (female) connectors (two out the
top, two out the bottom)
 Two Cat6 Ethernet with glands
Antenna Any preferred external antenna
Input Power POE+ (less than 30W) via RJ‐45 (PE+ PD).
Power 13 W typical, 15 W max
42
21
9/21/2019
BHM Specifications
BH Radio
Model Modem(s) Mesh (dBm) LTE Backhaul (dBm)
BHM‐201‐01 Single LTE Wireless Backhaul ‐ 23dBm
BHM‐201‐02 Single Mesh 25dBm ‐
BHM‐201‐04 Mesh and LTE Backhaul 25dBm 23dBm1
BHM‐201‐05 Dual Mesh 2 x 25dBm ‐
BHM‐201‐06 Mesh and LTE Backhaul 18dBm 23dBm1
BHM‐201‐07 Dual Mesh 2 x 18dBm ‐
BHM‐201‐08 Single Mesh 18dBm ‐
43
BHM – 201 Connectors
Bottom Top
44
22
9/21/2019
CWS – Without BHM Integration

Case – 1 – 3-sector LTE 2x2 MIMO deployment with Wired BH – Daisy Chain
SFP Ethernet SFP Ethernet SFP Ethernet

RJ‐45 RJ‐45 RJ‐45
BH To HNG
(Ethernet/ADSL/Optic/MW/VSAT)

45
45

Case – 1 – 3-sector LTE 2x2 MIMO deployment with Wired BH – Star Topology

RJ‐45 RJ‐45 RJ‐45
BH To HNG

46
46
23
9/21/2019
CWS – BHM - Integration

Case – 1 – 3-sector LTE 2x2 MIMO deployment with Wired BH and Wireless Mesh
BHM
PoE‐PSE
(Input)
SFP
SFP SFP
PoE‐PSE
(Output)
PDN
Wireless
Mesh
Serving EPC
BHM
PoE‐PSE
(Input)
SFP
SFP SFP PoE‐PSE
(Output)
47

Case – 1 – 3-sector LTE 2x2 MIMO deployment with LTE BH
BHM LTE BH To HNG
PoE‐PSE
(Input)
SFP Ethernet SFP Ethernet SFP PoE‐PSE

RJ‐45 RJ‐45 (Output)
BH EPC
Serving EPC
PDN

48
48
24
9/21/2019

BHM
PoE‐PSE
(Input)
Wireless Mesh
SFP Ethernet SFP Ethernet SFP
PoE‐PSE
BHM
PoE‐PSE
(Input)

PoE‐PSE
BH EPC
49

BHM
PoE‐PSE
Wireless Mesh
(Input)
SFP
SFP SFP
PoE‐PSE
(Output)
BHM
PoE‐PSE
(Input)
SFP
SFP SFP PoE‐PSE
(Output)
BH EPC
50
25
9/21/2019
CWS‐3000 Connectivity Options
SFP for BH and RJ‐45 for Daisy‐Chain
Backhaul: 1000 Base‐X via SFP Backhaul: 1000 Base‐T via SFP
Daisy chain: 1000 Base‐T via RJ‐45 Daisy chain: 1000 Base‐T via RJ‐45
51
RJ‐45 for BH and SFP for Daisy‐Chain
Backhaul: 1000 Base‐T via RJ‐45 Backhaul: 1000 Base‐T via RJ‐45
Daisy chain: 1000 Base‐X via SFP Daisy chain: 1000 Base‐T via SFP
52
26
9/21/2019
Wireless Mesh
53
CWS‐3000 Mounting Hardware & Connectors
54
27
9/21/2019
External BBU Architecture
55
External BBU Architecture
• External BBU in ground cabinet HetNet Gateway + EPC

adds capacity without adding
Internet
additional base station(s)
• Increased number of 4G users to
200+ per carrier/400+ per • CWS
• Any antenna
CWS/1200 hundred per 3‐sector
ANY backhaul
site (3 2 carrier CWS)
• HNG functionality does not change
Ethernet interface (1 Gbps)
(Fronthaul)
BBU in outdoor cabinet
***Depending on latency, could also be
placed farther away (i.e. baseband
processing farm)
Power
56
28
9/21/2019
Why External BBU?
• Adds scalability and flexibility to existing CWS portfolio

• Applicable cases:
• Urban/dense urban
• Sites that require higher capacity/higher user count 4G
• Carrier Aggregation (compatible with rel.12)
• 3-sector or 6-sector sites / multiple layers of LTE
• Urban – quickly increase capacity at much lower cost
(no need for new base stations)
• 3-sector/6-sector macro: enable shared capacity
increase with 1 BBU
• Ideal for 4G
• Instantaneous capacity increase
• Protects investment for 5G
Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1 57 | © Parallel Wireless Inc. Proprietary

& Confidential
57
Comparison
+
CWS‐3050, Standard CWS‐3050 with external COTS BBU
User Count 64 per 4G carrier (128 per sector) 200+ per carrier/400 per CWS w/2 carriers of LTE
CWS: BBU (in ground cabinet):
Weight & Dimensions • 1.7” (43mm) x 17.2” (437mm) x 9.8” (249mm) (HxWxD)
31 lbs (14 kgs) • Net weight 8 lbs (3.62 kg); gross weight 12 lbs (5.44 kg)
8.66” x 14.69” x 6.46” (220 x 373 x 164.2 mm) • 1U rackmount
150/75Mbps per 20 MHz carrier Multi‐carrier enabled at high carrier bandwidth
Throughput
300/150 Mbps per 2 carriers
# of carriers supported 1 (no aggregation) 2 with carrier aggregation (Rel.12)

*Possibility to support more
Deployment Scenario Rural Urban, suburban, macro

58 | Parallel Wireless, Inc. Proprietary
58
29
9/21/2019
Dynamic Function Splitting

• Easy migration path toward 5G
• reducing the impact of less than
perfect FH in system
performance.
• From core network perspective:
HNG = single (e)NodeB
(E)UTRAN) + aggregator.
backhaul
• CWSs are compact (e)NodeBs
including RRH and processing
unit
• BBU is a COTS server
• In all deployed scenarios, a less
than perfect FH between HNG
and CWS provides connectivity
while maintaining required QoS.

& Confidential
59
Use Cases for External BBU
• Single urban cell to add extra capacity

• Higher user count at macro site
• 2+ layers of LTE (3-sectors of Band X and 3-sectors of Band Y)
• Rel. 12 Carrier Aggregation (dual-connectivity)
• Not ideal for scenarios with limited backhaul (practical limitation, not a technical limitation)
HetNet Gateway + EPC
Ethernet
Internet

& Confidential
60
30
9/21/2019
3-sector-macro tower
Shared COTS BBU Capacity
Internet
Ethernet

& Confidential
61
6-sector-macro tower
Shared COTS BBU Capacity
Internet
Ethernet

& Confidential
62
31
9/21/2019
QUESTIONS?
Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1 63
63
Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1 64
64
32
9/21/2019
HetNet Gateway Server
OS and HNG S/W
Installation
Rel. 4.3.x
Parallel Wireless, Inc. Proprietary PW‐SYS‐S04‐PW System Admin‐HNG System Installation and Basic System Troubleshooting‐4.3‐v1.0 1
In This Presentation
• Understanding HNG Server Specification
• HNG Installation Prepare
• Installing HNG Application
• HNG Application Software Upgrade
Parallel Wireless, Inc.
OFFICIAL
9/21/2019
Document to Refer
Software Installation and Upgrade Guide
for detailed information.
HetNet Gateway
Minimum Hardware Configuration for PoC
• HP DL360 Gen9 or equivalent 2 socket x86 server
• Intel Xeon E5‐2697v4 (18 core), 2.3 GHz
• Total processors: 2
• Minimum 128GB of RAM
• One or two 2x10GbE NICs. Intel X710 or 82599 based NICs recommended
• 4x1GbE NIC
• Minimum 256 GB disk space
• Hardware RAID controller
• Dual redundant power supplies
• System capacity:
– 5 Gbps – 20 Gbps with IPsec (Depends on ordered configuration)
– Up to 25000 APs (Combination of HNBs and HeNBs)
OFFICIAL
9/21/2019
HNG – Software Installation
Before installing the operating system or product software, obtain the following:
• Laptop
• Operating system and product software DVD
• All necessary network IP addresses
• Make sure that your laptop connections are established.
This connection must be made before you begin downloading software on the HetNet
Gateway (HNG)/Uni‐Manage servers.
Refer
Software Installation Guide
for detailed information.
Points to Note
• HNG is a CentOS based closed system.
• HNG Application SW comes with CentOS OS and HNG Software in ISO or
binary format.
OFFICIAL
9/21/2019
Best Practices for HNG Software Installation
• Networking requirements
– The inter‐HNG redundancy link needs to be exclusive/isolated to each pair of HNGs.
– More than 2 HNGs should not use the same L2 network. For e.g. if using VLANs, use one VLAN per pair.
– This is because in 1:1 redundancy, the HNGs use multicast to discover it's peer.
• BIOS settings
– Set the BIOS to boot to legacy mode
– Disable CPU hyperthreading
• Console
– PW CLI console (username: admin) is on 1‐3 ptys
– Linux console (username: root) is on 4‐6. Use Alt‐Fn to go to relevant pty
• Factory‐mode, post install
– Factory default OAM port must be configured after software installation. Refer “Post Installation”
section.
Before Installation
• Obtain software CD from PW.
• Verify required server specification with PW field personnel.
• Obtain OAM IP address from IT/Network administrator.
• Plan Redundancy Setup and Obtain required IP addresses.
OFFICIAL
9/21/2019
Prerequisites for HNG ISO Installation
• HNG Installation is recommended in an VM environment:

• KVM-based VM Installation
• VMWare-Based VM Installation
• In this session we will talk about KVM-VM based installation.
Preparing KVM Setup

Pre-requisites
• KVM hypervisor should be installed on server where VM needs to be

created.
• At least 8 CPUs and 16 GB Memory allocate for VM
• At least 600 GB storage available for data
10
OFFICIAL
9/21/2019
Preparing KVM Setup
1. Get identified AR Build ISO on your KVM server where new VM for AR is to be created.
2. SSH to KVM Hypervisor machine and launch virt-manager
3. Following window will appear:
11
Preparing KVM Setup
4. Go to File -> New Virtual Machine
12
OFFICIAL
9/21/2019
Preparing KVM Setup
5. New window Create a new virtual machine will appear.

6. Select Local install media (ISO image or CDROM) and click Forward.
13
Preparing KVM Setup
7. Browse to the selected ISO.

8. Select Automatically detect operating system based on install media.
9. Click Forward.
14
OFFICIAL
9/21/2019
Preparing KVM Setup
10. Allocate memory and CPUs and click Forward.
15
Preparing KVM Setup
11. Allocate Disk Space and click Forward.
16
OFFICIAL
9/21/2019
Preparing KVM Setup
12. Provide VM name and click Finish.
17
HNG Base ISO Installation
18
OFFICIAL
9/21/2019
HNG Base ISO Installation
• If you are using Bare‐metal server put ISO disk in CD/DVD drive and reboot it.
• In case of VM direct boot drive to CD/DVD drive as first boot option.
• After reboot it will take you to Installation Menu.
• Hit Enter and let system perform installation.
19
Installation
• For basic installation select Install a system from installation menu.
– For advance disk configuration select Install a system with advance disk options.
• Once you selected Install a system for installation, system will start installation wizard and screen shown
below will appear.
20
OFFICIAL
9/21/2019
Installation – Completed
Admin Log‐in
• Once installation completed log‐in
screen will appear. Login as admin with
admin as password.
This will take you to the HNG CLI.
• Alternatively you can log‐in as root user.
21
Installation – Completed
Root Log‐in
• Although root log‐in is not required in
HNG but sometimes you might need to
do advance network setting. Then you
can log in as root user.
• Supply Ctrl+Alt+F5 key combination
through keyboard or from Send Key
menu. This will take you to the root log‐
in screen.
• Use the password you set during the
installation of HNG ISO and log‐in as
root user.
22
OFFICIAL
9/21/2019
Installation Structure
• This installation will give you following partition structure:
Filesystem 1K‐blocks Used Available Use% Mounted on
/dev/mapper/VolGroup‐lv_root
36516556 4520476 30134448 14% /
tmpfs 4031300 0 4031300 0% /dev/shm
/dev/sda1 487652 94842 367210 21% /boot
• By default HNG application installed on /opt/pw folder.
23
Advance Installation
24
OFFICIAL
9/21/2019
Installation
• Connect your laptop to server console.
• Insert the software disk into CD‐ROM drive
of the server.
• Reboot the server, ensure that boot priority
is set to CD‐ROM.
• After POST, side screen will appear.
• For basic user select Install a system from
installation menu.
– For advance disk configuration select Install a
system with advance disk options.
• Once you selected Install a system for
installation, you are prompted for the
timezone parameters
25
• Once Installation files are checked
and installation begins, Installation
Summary screen appears.
NOTE: In this section please complete
the items marked with icon before
continuing to the next step.
26
OFFICIAL
9/21/2019
Installation ‐ Timezone
• Click Date and Time and set Date and Time‐zone.
27
Advance Installation – Installation Destination
• Click Installation Destination icon.
The Installation Destination screen
appears.
28
OFFICIAL
9/21/2019
• Click Installation Destination icon. The
Installation Destination screen
appears.
• Select I will configure partition.
29
• Assign most of the space to the /
partition and click Done.
30
OFFICIAL
9/21/2019
• Review and click Accept Changes.
31
• Click Begin Installation.
32
OFFICIAL
9/21/2019
Installation – Root Account
• Enter Root Password and confirm in Confirm field.
• Click Next. CentOS and PW HNG software installation will start.
33
• Now seat back and wait for installation completion.
34
OFFICIAL
9/21/2019
Advance Installation – Completed
Admin Log‐in
• Once installation completed log‐in
screen will appear. Login as admin
with admin as password.
This will take you to the HNG CLI.
• Alternatively you can log‐in as
root user.
35
Advance Installation – Completed
Root Log‐in
• Although root log‐in is not required in
HNG but sometimes you might need to
do advance network setting. Then you
can log in as root user.
• Supply Ctrl+Alt+F5 key combination
through keyboard or from Send Key
menu. This will take you to the root log‐
in screen.
• Use the password you set during the
installation of HNG ISO and log‐in as
root user.
36
OFFICIAL
9/21/2019
Installation Structure
• This installation will give you following partition structure:
Filesystem 1K‐blocks Used Available Use% Mounted on
/dev/mapper/VolGroup‐lv_root
36516556 4520476 30134448 14% /
tmpfs 4031300 0 4031300 0% /dev/shm
/dev/sda1 487652 94842 367210 21% /boot
• By default HNG application installed on /opt/pw folder.
37
CWS
• Verify Date and Time at the HNG
root@bbpms:~# date
root@bbpms:~# date -s “2017-06-19 15:23”
root@bbpms:~# hwclock -w
38
38
OFFICIAL
9/21/2019
Post Installation ‐ Login
• Once server rebooted following prompt will appear:
Parallel Wireless LTE Access Controller (3.1.2‐20170317.1611‐1‐0.x86_64)
localhost login: admin
password: *****
• By default HNG SW is configured for admin user with admin password.

• Enter admin for login and admin for password. You will land in to Operational Mode (#)
and following prompt will appear.
localhost
localhost#
39
Post Installation – Setting Up OAM Interface
• You must set up the OAM interface to replace factory–default OAM IP address.
• This helps user to connect to system in case of any eventuality where server became
unreachable due to interface collapse.
• Enter following command:
localhost# system factory-default oam-address <perm_OAM_IP>
oam-mask <netmask> oam-port <physical_port>
localhost# system factory-default oam-address 10.61.1.111

oam-mask 255.255.255.0 oam-port eth0
40
OFFICIAL
9/21/2019
Post Installation – Changing Hostname
• By default hostname prompt appears as localhost.
• Enter folloing command to set up host name in Config Mode.
# config
localhost (config)# system node <node_tage> hostname <hostname>
# config
localhost(config)# system node primary hostname Training1
Training1(config)#
41
Post Installation – Verification of OAM Interface
• Now you need to check the reachability of your OAM interface in your network.
• Disconnect your console from your laptop and Reboot the server.
• Connect your laptop to LAN interface and ssh to HNG server through console or putty:
ssh admin@<hng_server_ip>
# ssh admin@10.61.1.111
42
OFFICIAL
9/21/2019
Post Installation – What Next….
• Refer System Management course for user management at HNG.
• Refer HNG System Installation and Basic System Troubleshooting for HNG Configuration,
backup and restoration.
• Refer HNG Software Upgrade section for HNG Software Update.
43
HNG Software Upgrade
44
OFFICIAL
9/21/2019
Upgrading Stand‐alone HNG
Preparation
To upgrade the HNG software on a stand‐alone system complete the following:
1. Open a Terminal window (such as PuTTY) and log in as a admin user.
2. Verify if the system needs configuration backup:
#system configuration need-backup
• If the output is Yes, then system configuration backup is required, otherwise continue to step 5.
3. Enter the following command to see the current configuration backup file.
show system boot-option
4. Update the configuration file:
system configuration backup file-url file:///opt/pw/<configname>.tgz
OK
45
Upgrading Stand‐alone HNG
5. Enter the following command to in using the HetNet Gateway (HNG) CLI:
# system software install file-url
sftp://<user>:<password>@<build_server_IP>/<build_file_location>/<Build_file_nam
e>.bin
6. Following prompt will appear:
HNG Software Install Success
7. Reboot the HNG server using this command:
# system reboot
46
OFFICIAL
9/21/2019
Upgrading Clustered HNGs
Preparation on Standby Node
To upgrade the HNG software on a clustered system running in redundancy mode complete the following:
1. Go to the standby node and log in as a admin user.
• If the output is Yes then system configuration backup is required, otherwise continue to step 5.
OK
47
On Stand‐by HNG
5. Enter the following command using the HetNet Gateway (HNG) CLI:
sftp://<user>:<password>@<build_server_IP>/<build_file_location>/<Build_file_name>.bin
Following prompt will appear:
# system reboot
7. Verify if new software version is active on both the HNGs.
# show system version verbose
6. Verify redundancy has been correctly established.
# show redundancy status
6. Verify system cluster status.
# system cluster status
48
OFFICIAL
9/21/2019
Preparation on Active Node
To upgrade the HNG software on a clustered system running in redundancy mode complete the following:
1. Go to the active node and log in as a admin user.
• If the output is Yes do the system configuration backup, otherwise continue to step 5.
OK
49
On Active HNG
5. Perform cluster switchover by following command:
# system cluster switchover
6. Go to newly active node (where software upgrade was performed) and check if it is performing well.
7. If satisfied come back to standby node now.
8. Enter the following in using the HetNet Gateway (HNG) CLI:
sftp://<user>:<password>@<build_server_IP>/<build_file_location>/<Build_file_name>.bin
Following prompt will appear:
# system reboot
50
OFFICIAL
9/21/2019
Verifying HNG After Software Upgrade
1) Verify if new software version is active on both the HNGs.
# show system version verbose
2) Verify redundancy has been correctly established.
# show redundancy status
3) Verify system cluster status.
# system cluster status
4) Verify the EPC core checks.
# show vend s1ap venb instance <venb> peer-state mme
5) Verify the Access side checks.
# show vend s1ap venb instance <venb> peer-state cws
6) Run following commands to see alarms and events.
# show alarm list
There should be no new alarms on the system.
# show system crash list
There should be no new crashes on the system.
# show event history
There should be clear events for all the new events generated by the system.
51
Installation Troubleshooting
52
OFFICIAL
9/21/2019
Checking HNG Service
• HNG is not going to CLI mode
– Connect to VM console or ssh as root user and check the status of pwbootd service:
#service pwbootd status -l
Output would be similar to following if service is running in valid state.
53
Checking HNG Service
• HNG is not going to CLI mode
– If pwbootd is not running, start is using following set of command:
# service pwbootd stop
# service pwbootd start
After restoring of pwbootd service output would be like this:
54
OFFICIAL
9/21/2019
THANK YOU
55
OFFICIAL
9/21/2019
HNG Basic Configuration
and Management
Rel 4.3x
Parallel Wireless, Inc. Proprietary PW‐SYS‐S05‐PW System Admin ‐ HNG System Basic Configuration & Management‐4.3‐v1.0 1
Content
• HNG configuration concept
• Basic system configuration
• Node, Port and Virtual Network configuration
• HNG Management
– System performance
– Inventory management
– Managing system resource
– Managing Events, Alarms and SNMP Traps
1
9/21/2019
Configuration Concepts
Organization
Tx Power Mgmt
PCI Conflict Res
2G/3G/4G/Wi‐Fi
Mobility
Self
Access Node Configuration
ANR
ICIC
Network
IPSec
SON Function
Port Port
SCTP vRNC veNB GTP
Port GTP vBSC vPCU SCTP Port

RTP vePDG VTWANgw RTP
Port Port
Node – Tag and Host Name
System – Name / TZ
Basic System Configuration
2
9/21/2019
Check and Verify HNG Release
1
Command to check the boot‐option status
3
2
File path – this will be the location of file where
Current running Release current running configurations are saves
1 Before begin with the configuration, it is very important to check the current running Release and Backup location.
Later if required, admin can create a new Backup location or update the Release
2 Priority 0 is the current running Release. There are total 10 Priorities, where Admin can install other Releases/Build
in them. When required they can be switched to Priority 0 (Explained in next slide)
3 Use Backup is the file location. This can be created by the admin and it is important to save the file before rebooting
the system
Update/Change Release
Priority 0 will be updated with 4.1.0‐20180704.0408 build
BEFORE AFTER
3
9/21/2019
Create a Backup File and Attach
1 New file is created with name “NewFile.cfg.tgz” in “/opt/pw” directory
2 Update the Use Backup path in Priority 0
3 Newly created file (NewFile.cfg.tgz) has been attached
4 Reboot the system to remove previous configuration and begin with new
Node, Port and Virtual Network
Configuration
4
9/21/2019
System Node Configuration
Define a node for future reference. In this example it is
defined as “primary”
1
Hostname will be the name of HNG that is going to be configured 2
New host name
1 Defining node tag is important to understand the difference between Active and Standby HNG during redundancy
setup. Node tag that has been defined here will be used later while creating instance/instances. Node tag is important
config parameter which is always first basic check point while configuring a system.
2 Hostname will be a navigation for later
stage when the HNG has to be identified
in EMS. All the counters and alarms
related to specific HNG will be reflected
under the Hostname at UniManage (as
shown in the example here)
Port Configuration Snapshot of all configured ETH ports
Available Eth ports in the server
Default value
Type of Eth port that has to be activated Configured value
Towards Management
Example ‐ Representation of ETH ports in HNG server
that are connecting towards various interfaces Towards MME/MSC
ENS6 to CWS ens3 ens4
ENS3 to Management ens6 HNG
ENS4 to Core network (CS or MME) Towards Access node ens5
ENS5 to Core network (PS)
Towards SGSN/SGW
10
5
9/21/2019
Virtual Network Configuration
Defining INTERFACES and ROUTES
Virtual
Network hng(config)# virtual-network Test
CWS#n IP ‐ 10.52.255.254

CWS
Interfaces Routes
MME #1
(192.168.0.1)
(172.17.3.1)
SubNet Value SubNet Value
To CWS Interface ‐ 10.42.28.170 To MME Interface ‐ 10.22.28.170 192.168.0.0/16
10.52.0.0/16 MME #2
(192.168.0.2)
CWS#2 IP ‐ 10.52.0.2 Eth1

MME #3
Router
Eth3 HNG Router (192.168.0.3)
CWS Eth2
Gateway IP ‐ 10.22.28.171
SGW
SGW
To SGW Interface ‐ 10.32.28.170 (172.17.3.4)
(192.168.0.5)
Gateway IP ‐ 10.21.0.1
CWS#1 IP ‐ 10.52.0.1
CWS
11
Virtual Network Configuration
Understanding the CLI
Defining Interface To MME Interface ‐ 10.22.28.170 192.168.0.0/16
MME #1
ens4 (192.168.0.1)
HNG Router
MME #2
(192.168.0.2
Gateway IP ‐ 10.22.28.171
training(config)# virtual-network Training

interface to_MME
type local address 10.22.28.170
netmask 255.255.0.0 Defining Route
node primary
port ens4
virtual-network Training
route address 192.168.0.0
netmask 255.255.0.0
gateway 10.22.28.171
port ens4
12
6
9/21/2019
HNG Management
13
Access Levels
The HNG CLI supports following three user privilege levels:
Operator: Operator have read‐only privileges to a larger subset of the Operational
Mode commands. They can execute most of the commands in Operational Mode
including some system monitoring, statistics and fault management functions. They
can’t enter in Config Mode.
Config‐Administrator: Config‐Administrator have read‐write privileges and can
execute any commands in the CLI except for a few security‐related commands that
can only be configured by Administrators. Config‐Administrator can configure or
modify system settings and can execute all system commands including those
available to Operator.
Administrator: Administrator have read‐write privileges and can execute all
commands including those not available to Administrator.
14
7
9/21/2019
User Privileges
read‐write privileges and can execute all commands
read‐write Administrator
privileges and can
execute any Config‐Administrator
commands in the
CLI except for a few
security‐related Operation Mode Config Mode
commands
Operators
read‐only
privileges to a
larger subset of
the Operational
Mode
commands.
Config mode is used to create a new set of parameters or edit/delete existing ones
15
HNG User and User Group Configuration
Configure HNG‐level user group and users:
(config)# nacm groups

group {admin | configadmin | operator}
user-name <user_name>
nacm groups group admin

user-name train_admin
nacm groups group configadmin
user-name train_config
nacm groups group operator
user-name train_inspect
16
8
9/21/2019
HNG User Password Configuration
Configure user passwords and privilege level:
(config)# aaa authentication users
user <user_name>
uid <val> gid {0 | 1 | 2}
password <passkey>
ssh_keydir <ssh_key_directory>
homedire <path_to_user_dir)
aaa authentication users

user train_admin
uid 0 gid 0 password training
ssh_keydir /opt/pw/runtime/users
homedir /op/pw/runtime/users
aaa authentication users
user train_config
uid 0 gid 1 password configuration
ssh_keydir /opt/pw/runtime/users
homedir /op/pw/runtime/users
17
System Performance
18
9
9/21/2019
HNG Performance show system crash list
System Crash Files
Show system crash details crash-id <id>
19
HNG Performance
Log Files show system log list
show system log file
20
10
9/21/2019
HNG Performance
Node Info and Factory Defaults
• show system node-info {facory-defaults | tag}
• show system node-info
node-info tag primary
node-info factory-defaults oam-port eth0
node-info factory-defaults oam-address 192.168.1.1
node-info factory-defaults oam-netmask 255.255.255.0
21
HNG Performance
System Process List
• show system process {list | table}
• show system process table
22
11
9/21/2019
Viewing All System Processes
training1# show system process list
PID PPID PGID TID START ELAPSED STATE THREADS CPU MEM RSS VSZ COMMAND
--------------------------------------------------------------------------------------------------
1 0 1 1 Mar01 1-17:46:06 S 1 0.0 0.0 1520 19284 init
2 0 0 2 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 kthreadd
3 2 0 3 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 ksoftirqd/0
5 2 0 5 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 kworker/0:0H
6 2 0 6 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 kworker/u30:0
7 2 0 7 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 migration/0
8 2 0 8 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 rcu_bh
9 2 0 9 Mar01 1-17:46:06 S 1 0.6 0.0 0 0 rcu_sched
10 2 0 10 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 watchdog/0
11 2 0 11 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 khelper
12 2 0 12 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 kdevtmpfs
13 2 0 13 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 netns
14 2 0 14 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 xenwatch
15 2 0 15 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 xenbus
16 2 0 16 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 kworker/0:1
17 2 0 17 Mar01 1-17:46:06 S 1 0.0 0.0 0 0 writeback
23
HNG Management
Software Release List
• show system software release
HNG Software Release List

OUTPUT
-------------------------------------------------------------------
3.1.3.5-20180403.0556 Fri 04 May 2018 05:57:46 AM EST
3.1.2-20170731.0411 Mon 31 Jul 2017 03:28:42 PM EST
3.1.2-20170724.0411 Tue 25 Jul 2017 04:36:27 PM EST
3.1.2-20170627.1655 Tue 11 Jul 2017 12:55:24 PM EST
24
12
9/21/2019
HNG Management
System Support
• HNG Maintains as Support file for historical analysis. You can view this using following command:
• show system support details | more
25
HNG Management
System Time and Up time
• show system time
current-time Tue May 29 06:07:52 2018 EST

up-time 03:24:43
26
13
9/21/2019
HNG Management
NetConf Management
• show netconf-state session
• Show netconf-state datastores
27
HNG Management
NetConf Management
• show netconf-state statistics
28
14
9/21/2019
HNG Management
IPSec Child‐SA Management
• show ipsec childsa all
29
HNG Management
IPSec IKE‐SA
• show ipsec ikesa all
30
15
9/21/2019
HNG Management
IPSec Management
• show ipsec tunnel
31
HNG Management
Network Statistics
• show network netstat
NETSTAT TCP
OUTPUT
--------------------------------------------------------------------------------------------------------------
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 192.168.89.101:9085 0.0.0.0:* LISTEN 4671/bin/faultmgr
tcp 0 0 127.0.0.1:9085 0.0.0.0:* LISTEN 4671/bin/faultmgr
tcp 0 0 127.0.0.1:36442 127.0.0.1:4565 ESTABLISHED 4684/bin/configmgr
tcp 0 0 127.0.0.1:36446 127.0.0.1:4565 ESTABLISHED 6955/ntpd
tcp 0 0 10.40.60.10:9086 10.186.50.2:38128 ESTABLISHED 4908/bin/statsmgr
tcp 0 0 127.0.0.1:4565 127.0.0.1:36440 ESTABLISHED 2248/confd
tcp 0 0 10.60.30.4:2024 10.60.53.60:56567 ESTABLISHED 27858/sshd
tcp 0 0 10.40.60.10:9088 10.186.50.1:32914 ESTABLISHED 4721/bin/sonmgr
tcp 0 0 127.0.0.1:39660 127.0.0.1:9089 ESTABLISHED 4908/bin/statsmgr
tcp 0 0 127.0.0.1:36762 127.0.0.1:4565 ESTABLISHED 26833/bin/confd_cli
tcp 0 0 127.0.0.1:36407 127.0.0.1:4565 ESTABLISHED 4658/bin/sysmgr
tcp 0 0 10.40.60.10:9088 10.186.0.1:58917 ESTABLISHED 4721/bin/sonmgr
tcp 0 0 10.40.60.10:9089 10.186.50.2:52505 TIME_WAIT -
tcp 0 0 10.40.60.10:9089 10.186.50.4:53424 TIME_WAIT -
32
16
9/21/2019
HNG Management
Task Heap Memory Size
• show task debug stack1-heap-stats
33
HNG Management
Task Memory Usage Size
• show tasks debug stack1-mem-stats
34
17
9/21/2019
Inventory Management
35
HNG Management
• show system inventory
36
18
9/21/2019
HNG Management
• show accessnodes cws <cws_name> inventory
37
Performance Reports
• Calculate and present KPIs for the following types of reports:
Accessibility
Retainability
Integrity
Availability
Mobility
Utilization
Transport
Resources
• Available for LTE and WCDMA
• Report options: date/time period, granularity (15 minutes, hourly, daily), CWS/HNG id, output to file
38
19
9/21/2019
LTE Cell Performance
# show accessnodes cws <cws> lte cell <cell> counters
accessibility Display accessibility counters.

accessibility-failure Display accessibility failure counters.
accessibility-s1-setup Display accessibility S1 Setup related counters.
availability Cell Availability counters
capacity System Capacity in terms of PRB Usage
coverage Cell Coverage related counters
integrity Service Integrity related counters
mobility Mobility Counters
retainability Display retainability counters.
traffic Traffic Volume and max number of UE counters
39
LTE Cell Performance
show accessnodes cws <cws> lte cell <cell> counters accessibility
40
20
9/21/2019
Daily Check Commands
# show accessnodes cws oper-data
# show accessnodes cws lte cell oper-data
# show venb s1ap peer-state <venb_instance> cws
# show venb s1ap peer-state <venb_instance> mme
# show venb gtpu peer-state <venb_instance> cws
# show venb gtpu peer-state <venb_instance> sgw
# show accessnodes cws mesh
# show subscriber session [callid]
# show accessnodes cws <cws> uplink {connection-info modem-info signal-info}
# show redundancy stat
# show alarm list
# show events history
# show events history | tab | sort-by timestamp | include "CWS is disconnected“
# show system crash list
# show accessnodes cws <cws> lte cell <cell> counters accessibility-failure
# show accessnodes cws <cws> lte cell <cell> counters accessibility-s1-setup
# show accessnodes cws lte cell counters accessibility erab-setup-success-rate-all-attempt
# show accessnodes cws lte cell counters accessibility erab-setup-success-rate-all-success
# show subscriber session-info | select cws-name | select e-rab dl-bytes
#show subscriber umts-session-info | select cws-name | select rab dl-bytes
41
Showing Selective Counters in One Command Output
# show accessnodes cws lte cell counters accessibility attempt-mo-data | select
lte cell counters accessibility attempt-mo-signalling | select lte cell counters
accessibility-s1-setup s1-setup-request-success
S1
SETUP
ATTEMPT ATTEMPT MO REQUEST
NAME NAME MO DATA SIGNALLING SUCCESS
------------------------------------------------------------
Training_Cap1 TrainingCell1 0 0 1
training2 train2 - - -
42
21
9/21/2019
Managing System Resource
43
HNG Resource Management
• show resource {application | counter | cpu | disk | fastpath | memory |

network | system | task}
• application Resource monitoring application statistics.

• counter Resource monitoring counter information.
• cpu Resource monitoring of central processing unit (CPU) usage.
• disk Resource monitoring disk usage.
• fastpath Resource monitoring FastPath memory usage.
• memory Resource monitoring memory usage.
• network Resource monitoring network usage.
• system Resource monitoring system information.
• task Resource monitoring task statistics.b
44
22
9/21/2019
Application Management
• show resource application
45
CPU Management
• show resource cpu
46
23
9/21/2019
Disk Management
• show resource disk
47
Memory Management
• show resource memory
48
24
9/21/2019
System Management
• show resource system
49
Managing Events, Alarms and SNMP
Traps
50
25
9/21/2019
Alarms
List of Alarms
• To see complete Alarm list and definition ‐ # show alarm definition
• To see active alarms ‐ # show alarm list
51
Events
List of Historical Events
• To see the list of historical events ‐ # show event history
52
26
9/21/2019
SNMP‐MIB
Location of SNMP‐MIB
• HNG SNMP‐MIB Files are located at:
/opt/pw/release/3.1.2-
20170317.1611/etc/config/snmp
• MIB file can be seen using Uni‐Manage interface
53
Managing Files
Compare Two Files
• file compare <local_path/file1_name> <local_path/file2_name>
file compare audit_trail/20170719-151320.txt audit_trail/20170719-151700.txt
54
27
9/21/2019
Managing Files
Copy a File
• file copy <local_path/file1_name> <local_path/file_new_name>
file copy audit_trail/20170719-151320.txt audit_trail/temp.txt
Delete a File
• file delete <local_path/file_name>
file delete audit_trail/temp.txt
55
Managing Files
Listing Files From a Folder
• file list <local_path/file_name>
• betelgeuse-red1# file list

Possible completions:
<directory to list> audit_trail/ crashes/ debug/ statistics/ support/ | <cr>
• file list crashes/
56
28
9/21/2019
Managing Files
Renaming Files or Moving Files From One Location to Another
• file move <src_local_path/src_file_name> <dst_ocal_path/dst_file_name>

file move op.temp op.temp2
57
Managing Files
Showing the Content of File
• file show <local_path/file_name>
file show statistics/cws_cpu_20170719-215315.csvO
58
29
9/21/2019
Managing Files
Uploading/Exporting Local Files to Remote Location
• file upload local <local_path/file_name> remote sftp

<[s]ftp://<user>:<password>@<host|ip[:port]><path>
file upload local file:///opt/pw/runtime/users/audit_trail/20170619-

163341.txt remote sftp://root:password@10.61.1.112:2024/opt/pw/20170619-
163341.txt
59
Thank You
60
30
9/21/2019
CWS – nk
Management
Rel. 4.3.x
Parallel Wireless, Inc. Proprietary PW‐SYS‐S08‐PW‐CWS Software Installation & Provisioning From Scratch‐4.3‐v1.0 1
• CWS Provisioning in HNG
• CWS Installation and Upgrade Through HNG
• CWS – Troubleshooting and Monitoring
Parallel Wireless, Inc. Proprietary PW‐SYS‐S08‐PW‐CWS Software Installation & Provisioning From Scratch‐4.3‐v1.0 2 2
1
9/21/2019
CWS Radio Parameters
C L I C K H E R E TO A D D S U B T I T L E T E X T
Objectives
• To discuss in detail installation and operation of CWS node

• Purpose of CWS Software Upgrade and Roll-back
Parallel Wireless, Inc. Proprietary PW‐SYS‐S08‐PW‐CWS Software Installation & Provisioning From Scratch‐4.3‐v1.0
PW‐SYS‐S08‐PW‐CWS Software Installation & Provisioning From Scratch‐4.2‐v1.0 4
2
9/21/2019
Converged Wireless System (CWS)
• CWS Macro-cell nodes

• Multi-mode
• Compact, rugged, aesthetically pleasing
• Auto config , resource and spectrum management via HetNet Gateway
• Standards based, secure, carrier grade
CWS‐3000
• Backhaul and Meshing – External Module Outdoor Series
• Flexible backhaul: Fixed, Satellite, Wireless, Mesh
• Resilience: multi-radio,
multi-frequency, traffic re-routing
on link failures
• QoS enforcement: better QoE
Purpose of CWS Software Update
• To maintain compatible software release type/branch and build on CWS and HNG
node
• To enhance feature and function set
• To eliminate/patch an exiting bug or Issue
3
9/21/2019
Purpose of CWS Software Roll-back
• To downsize feature and functionality set for compatibility

• To resolve a failed upgrade issue
CWS‐nK Logical and Functional
Components
4
9/21/2019
CWS – nk Functional Components
TRX1
GPS
TRX2
RF
BBP-Master BBP-Slave
SFP (CWS/HNG) PoE ( To BHM/CWS/HNG)


GPS
• Performance Manager
(perfmgr)
• Config Manager (cfgmgr) 4G / 3G
• Fault Manager (faultmgr) Access
• Platform Manager (platmgr) Radio
• SON Client
BBP + RU
To CWS/HNG
Ethernet to BHM
10
5
9/21/2019
CWS – HNG Connectivity,
Provisioning, Installation and
Configuration
11
CWS – HNG Connectivity, Provisioning, and Configuration
• While using CWS and HNG in PW solution you need to perform following
operations in given sequence:
1. CWS Staging:
• Manual or Staging Server
2. Provisioning of staged CWS in HNG
3. CWS Hardware Installation – Refer CWS Hardware Installation course
4. CWS Connection Verification
5. VNF Configuration
6. CWS association with VNF (veNB/vRNC/vBSC/vPCU)
For #4 through #6 refer VNF (veNB/vRNC/vBSC/vPCU) configuration course.
12
6
9/21/2019
CWS Staging
13
CWS Staging
• CWS Staging is a preparation procedure of CWS before shipping out
from warehouse for installation in field. This can be done with
following procedures:
1. Automatic Staging through PW Staging Application
2. Manual Staging – Part of Advance course
14
7
9/21/2019
List of Tools and Software
Hardware Software Información
 Laptop  Putty
Parameter Values
UNIRANID
 Cable UTP Cat5e  Filezilla HWCLASSID
UNIRANADDR
BBPIPADDR
BBPMASTERIPADDR
BBPSLAVEIPADDR
ipaddr
 Fuente HLG‐600H‐48A  Notepad++ netmask
gateway
15
Before Deployment
Staging of CWS
Staging Server+
DHCP Server
Before shipping CWS/BHM onsite for deployment, it is first brought to PW Staging Lab or Operator Depot.
1. CWS/BHM then connected to the Staging Server where a DHCP service is running.
2. Upon power up, CWS/BHM attempts to obtain an IP via DHCP server running on staging server and sends CFG request to Staging
server
3. In Staging server, under Devices, CWS UniRAN ID will be populated, to which a profile can be applied.
4. A profile in Staging server, is a list of parameters like cloud/SON IP, Security gateway IP, Static/DHCP public IP, etc. that can be applied
to a CWS/BHM (devices) or a group of CWS/BHM that the operator might want to deploy in a particular area/TAC/LAC.
5. Upon applying profile, CWS state under Devices in staging Server will be in Configured State. At this point, the CWS is
ready/provisioned via Staging Server to connect to the HNG (with the cloud/Security gateway parameters).
6. Power off and Disconnect CWS from Staging network and send it for field installation for connect to operational network.
7. Send the list of provisioned CWS with UNIRAN ID and Hardware Class Id to the HNG Administration team for provisioning.
16
8
9/21/2019
CWS/BHM Staging Using Staging Server
CWS/ DHCP
DHCP Broadcast
Staging HNG
BHM DHCP Broadcast
Mesh CWS Server
DHCP Reply
DHCP Reply
Discover ( UDP with CWS address and port)
Discover ( UDP with CWS address and port)
Discover Response (UDP/Payload IP of Staging Server )
Discover Response (UDP/Payload IP of Staging Server )
Register (HTTP/Payload : RAN ID, Name, HW Class ID )
Register (HTTP/Payload : RAN ID, Name, HW Class ID )
Register Response
Register Response
Configuration Request ( HTTP/Payload : RAN ID, HW Class ID )
Configuration Request ( HTTP/Payload : RAN ID, HW Class ID )
Configuration Response (HTTP/Payload : Initial Parameter Values )
Configuration Response (HTTP/Payload : Initial Parameter Values )
CWS is connected to HNG
CWS is connected to HNG
17
Staging Parameters
Platform Independent Parameters Applicable to CWS/BHM/MWS/CCH
Field Value and Description
CLOUDSERVERADDR * HetNet Gateway SON Server IP Address
CLUSTER_INTF The CLAMP Interface. Select the Cluster Interface from the drop‐down list. The default is Wired Mesh Interface. This field is mandatory if you enter
a Cluster ID in the CLUSTERID field.
CLUSTERID The ID used to identify the cluster. Valid values are 0 to 41773. This is mandatory if a Cluster Interface is selected in the CLUSTER_INTF field.
GPPWANINTFNAME * Controls how the RANs role in the mesh network is determined. Select the GPP WAN Interface Name from the drop‐down list. The default is AUTO.
HAMMERINTERVAL Interval in minutes during which if cloud connectivity is not established/restored the CWS is rebooted.
IPSEC Select the checkbox to enable IPSEC. The default is enabled.
PKI Select the checkbox to enable PKI. The default is disabled.
MESH_ADMISSION_CTRL Select the checkbox to enable Mesh Admission Control. The default is disabled.
PUBLIC_IP * Method used to provision the IP address the CWS uses to communicate to the HetNet Gateway Applications. Select the Public IP type from the
drop‐down list. The default is STATIC.
SEC_GW_ADDR * IP Address/Domain Name of Security Gateway if selected mode is STATIC

WAN_PING_DEST Alternate destination for ICMP pings.
WANPUBLICIP Method used to provision the IP address the CWS uses to communicate to the Security Gateway. Select the WAN Public IP type from the drop‐down
list. The default is STATIC.
WAN_IP_PROVISION_TYPE* The method used to provision WAN IP (static or DHCP).

WAN_IP_ADDR – IP The IP address of the WAN Interface if selection STATIC.
WAN_NETMASK The netmask for the WAN Interface.
WAN_DEF_GATEWAY The default gateway for the WAN interface.
18
9
9/21/2019
Staging Parameters
Platform Dependent Parameters Applicable to CWS‐nK
LTESTACKMODE The LTE Stack Mode. Select the LTE stack
mode from the drop‐down list.
Options are:
 FDD_T2K (default)
 FDD_T3K
 TDD_T2K
 TDD_T3K
RATMODE  GSM
 UMTS
 LTE
19
Staging Parameters
BHM/CCH Specific Parameters – Mesh Interface
COUNTRY_NAME * The name of the country. Select the country from the drop‐down list.
COUNTRY_ID The ID for the country. This field is automatically populated based on the
selected COUNTRY_NAME.
COUNTRY_STRING The code for the country. This field is automatically populated based on
the selected COUNTRY_NAME.
ESSID List of backhaul networks.
WIFI_DFS_ADJUST Rx Sensitivity adjustment for DFS (wifi0, wifi1, wifi2, wifi3)
Must be between 0 and 63.
The recommended value is 10. The default value is 0.
WIFI_DFS_SP_THRESH Rx Sensitivity Threshold for Short pulses DFS (applies to all radios).
20
10
9/21/2019
Staging Parameters
CCH Specific Parameters – Wi‐Fi Access
COUNTRY_ID The ID for the country. This field is automatically populated based on the
selected COUNTRY_NAME.
COUNTRY_STRING The code for the country. This field is automatically populated based on
the selected COUNTRY_NAME.
ACCESSPHYINTERFACE Interface to be used for Wi‐Fi Access. Select the Access Physical Interface
form the drop‐down list. The default is NONE.
21
Provisioning of Staged
CWS in HNG
22
11
9/21/2019
CWS – BHM – Deployment with LTE BH
BHM LTE BH To HNG
PoE‐PSE
(Input)
PoE‐PSE
SFP (Output)
BH EPC
Serving EPC
PDN
23
CWS – Deployment without BHM
SFP
Serving EPC
PDN
Wired BH To HNG
24
12
9/21/2019
Provisioning of Staged CWS in HNG
1. Log‐in to HNG using management IP address with following command:
#ssh admin@<hng_ip>
2. Perform following commands to provision staged CWS:
#config
accessnodes cws <name> <Uniran-id> hardware-class-id <hw_class_id>
description “Training CAP for Band3“
end
• Prior to above procedure it is assumed that SecGW is enabled and ipsec‐endpoint is
configured and both the nodes (CWS and HNG) have valid certificates loaded.
• If IPSec is not required, then no need to have certificates and ipsec‐endpoint can be
skipped.
• Refer HNG and VNF (veNB/vRNC/vBSC/vPCU) configuration course for SecGW and IPSec‐
Endpoint configuration .
25
Provisioning of Staged CWS in HNG
3. Supply following command to check the connectivity:
#show accessnodes cws oper-data
4. If CWS is already installed, switched‐on, and accessible over network then following
output will appear:
If all network parameter requirements and IPSec requirements (certificated etc.) are
correct and still cws is not connected, then refer CWS Troubleshooting module in
advance course.
26
13
9/21/2019
Provisioning Connected CWS in SON
• Once your CWS is connected and configured for specific radio functionality as described in
VNF (veNB/vRNC/vBSC/vPCU) configuration course it must be provisioned in SON
• Once it is provisioned the CWS radio will be configured for specific RAT functionality and
its management will be started through SON.
• Refer HNG and VNF (veNB/vRNC/vBSC/vPCU) configuration course for LTE/UMTS/GSM
and SON configuration .
27
SON: Zero‐Touch Configuration
BHM and CCH `BHM/CCH is up and BH is now available.
BHM/CCH
• Determines the BH availability. If LTE BH, it attaches to • BHM/CCH Switched On
BH eNB using LTE Modem and SIM.
Core • POST Completed
• Reads INI file and decides IP allocation. DHCP server
discovery performed & IP addresses obtained.
• SecGW Identification from INI
• IPsec Procedure/Cert Exchange
• IPsec Tunnel Establishment
• BHM/CCH sends Id, HW Capability, Interface info to
HNG.
• Based on ID, HNG identifies the configuration and
sends the basic information to BHM/CCH (Mesh BH
SSIds, Security info, Wi‐Fi Access ESSID and
parameters).
• BHM/CCH sets the parameters sent by HNG SON and
starts serving the MWS with BH. Additionally Wi‐FI
access is activated, if configured.
28
14
9/21/2019
CWS‐nk and MWS
CWS‐nK MWS is Up and UMTS/LTE Cell is InService state
BHM/
CCH
CWS‐nk/MWS
• BHM/CCH is ready with BH. The CWSnK/MWS
identifies the eth0 as WAN interface.
• CWS‐nK/MWS Switched On
• Reads INI file and decides IP allocation. DHCP server
• SecGW Identification from INI
• CWS‐nk/MWS sends Id, GPS coordinates, HW Capability,
Interface info to HNG.
• LTE: eNB Id, Cell Id, PCI, PLMN, TAC, EAI,
MME list, Cell Tx Power, SIB Params etc.
• UMTS: RNC Id, Cell Id, PSC, LAC, SAC, Cell Tx Power
SIB Params etc.
• CWS—nK sets all configured parameters for 3G and 4G
and brings cell in service.
• MWS sets all configured parameters for 4G and brings
cell in service.
29
CWS‐210
CWS 1 is up and In‐service
CWS 1
• Reads INI file and decides IP allocation. DHCP server • CWS Installed
Core
• POST Completed
• SecGW/HNG Identification from INI
• CWS sends Id, GPS coordinates, HW Capability, Interface
info to HNG.
• Based on CWS ID, HNG identifies the configuration and
sends the basic information to CWS 1 :
SIB Params etc.
• Wi‐Fi AP: AP SSId
• Wireless BH: ESSId to broadcast for Mesh BH
• CWS sets all configured parameters and brings the
LTE/UMTS cell in service.
30
15
9/21/2019
CWS‐210
CWS 1 is up, running, and broadcasting BH SSID configured
during bulk configuration by HNG
• Another CWS comes in network. Looking for WAN
CWS 1
connection. No connection found.
• CWS 2 resorted back to Wireless mess and starts search for
ESSIDs configured in INI file. ESSID found with CWS 1.
• Authenticated & mesh established between CWS 1 & CWS 2
Core
• Using BH0/BH1 CWS2 starts DHCP discovery.
• IPsec tunnel established between HNG and CWS 2 as it was
done for CWS1.
• CWS 2 sends mesh interface and other information like
CWS Id and Hardware class id to HNG.
• Based on CWS Id, HNG sends basic LTE/UMTS
configuration and performs PCI/PSC resolution if
needed.
• In case of conflict in PCI/PSC, HNG resolves the conflict
using SON config and sends customized configuration for
CWS 1 and CWS 2 with updated parameter values (ANR,
Tx, PCI/PSC) CWS 2
• If mesh CWS is configured with mesh AP, an ESSID will
be pushed to broadcast.
Both the CWSs are updated and cells are in‐service
31
BHM/CCH
CCH PGW DNS SecGW HNG
Power
on
BH Intf
Identity
LTE Session Established
IP Allocation
Reaching DNS
Obtaining SecGW IP
IPSec Tunnel Established
Sent UNIRAN id, HW Class ID, GPS lat‐long
Bulk Configuration
WiFi‐
(Wi‐Fi Radio, Mesh BH, Access)
Service Up
Status Report
32
16
9/21/2019
MWS
DNS
MWS CCH Load SecGW HNG
Balancer
Power
on
BH If IPSec Over LTE BH

Identity
Reaching DNS (INI)
Obtaining HNGGW IP
Sent UNIRAN id, HW Class ID, GPS lat‐long
Bulk Configuration
(eNBID, TAC, PLMN, EAI, PCI, Tx Pwer etc.
LTE Cell
InService
Status Report
33
BHM and CCH
BHM/CCH is up and BH is now Connected.
BHM/CCH1
• BHM/CCH is already staged. • BHM/CCH1 Switched On
• Determines the BH availability. If LTE BH, it attaches to • POST Completed
BH eNB using LTE Modem and SIM.
Core
• If LTE BH it will get its WAN IP from PGW for
modem.
• Starts IPsec Procedure/Cert Exchange with SecGW
• IPsec Tunnel Establishment done
• BHM/CCH sends Id, HW Capability, Interface info to
HNG.
• BHM/CCH sets the parameters sent by HNG SON and
starts serving the CWS/MWS with BH. For CCH
additionally Wi‐FI access is activated, if configured.
34
17
9/21/2019
CWS‐nk and MWS
CWS‐nK MWS is Up and UMTS/LTE Cell is InService state
BHM/CCH1
CWS/MWS1
• BHM/CCH1 is ready with BH. The CWSnK/MWS
identifies the eth0 as WAN interface.
• CWS‐nK/MWS Switched On
• CWS‐nk/MWS sends Id, GPS coordinates, HW Capability,
Interface info to HNG.
SIB Params etc.
• CWS—nK sets all configured parameters for 3G and 4G
and brings cell in service.
• MWS sets all configured parameters for 4G and brings
cell in service.
35
Mesh Establishment
CWS 1 is up, running, and broadcasting BH SSID configured
BHM/CCH 1
during bulk configuration by HNG
• BHM/CCH1 is configured and broadcasting ESSID.
CWS/MWS1
• Another BHM/CCH comes in network. Looking for WAN
connection. No connection found.
• BHM/CCH2 resorted back to Wireless mesh and starts
search for ESSIDs configured during Staging.
Core
• Authentication started and after authentication, mesh
established between BHM/CCH1 & BHM/CCH2
• IPsec tunnel established between HNG and BHM/CCH2 as it
was done for BHM/CCH1.
• BHM/CCH2 sends mesh interface and other information
like CWS Id and Hardware class id to HNG.
• Now BH established and CWS/MWS2 sends starts the
configuration procedure with HNG.
• Based on UNIRAN Id, HNG sends basic LTE/UMTS CWS/MWS2
configuration and performs PCI/PSC resolution if
needed, to CWS/MWS.
• In case of conflict in PCI/PSC, HNG resolves the conflict
using SON config and sends customized configuration for
BHM/CCH2
CWS/MWS 1 and CWS/MWS 2 with updated parameter
values (ANR, Tx, PCI/PSC)
Both the CWSs are updated and cells are in‐service
36
18
9/21/2019
CWS SW Upgrade
Through HNG
37
Software Update Through HNG
Before beginning the CWS software upgrade, ensure the following:

• The CWS node is connected and operational within the HNG.
• There is a maintenance window available, as the CWS node will be taken offline.
• A compatibility matrix between the HNG and CWS software has been created.
• A software build server, containing the new or rollback software, is accessible using FTP/SFTP.
• A list of all CWS names, Build Server IP address, and build folders and file names.
• This process doesn’t need any physical access to CWS.
• CWSes in field can be updated using this method.
• It is a two step process:
• Obtaining software from build repository to HNG local disk
• Installing software update to CWS
Note: Only requirement is CWS must be reachable through HNG and showing connected with
“show accessnodes cws oper-data” command:
38
19
9/21/2019
CWS Software Update Through HNG

Obtaining Candidate Build
• Login to the Active HNG using floating IP where candidate CWS is connected and in service.
• Obtain candidate build using following command:

file download remote
sftp://<user>:<password>@<server_ip>//<file_repository>/<remote_build_file_name
>.tgz local file:///opt/pw/cws/download/<local_build_file_name>.tgz
• The server_ip is SON IP address of HNG.
• SON IP can be found using command:
show running-config self-organization son-endpoint

Son-endpoint
bind ipaddr 10.51.0.93
39

Updating CWS Software to CWS
• Enter following command to update CWS with obtained SW build:

accessnodes cws <cws_name> software update file-url
sftp://<user>:<password>@<HNG_IP>:2024/<local_location>/<local_filename>.tgz
reboot true
• Observe the software update status using following command:
accessnodes cws <cws_name> software update-status
For example:
40
20
9/21/2019

Checking CWS Software Update Status
During the software upgrade, various messages, depending on various conditions,

are displayed. Including the following:
• ISSU not in progress
• Success: Update started
• Error: Timed out downloading image
• Installing image
• Error: Timed out installing image
• Success: Abort started
• Aborting installation
• Installation complete, node armed
When the “Installation complete, node armed” message is displayed, the CWS
software has been upgraded.
41

Verifying SW Update
To verify the CWS is successfully updated to the desired software and functioning as expected.
1. show accessnodes cws <cws_name> version verbose
Component Name : pw-uniran-None
Release Number : 3.1.1.1
Release Target : p1
Username : parallel
Build Date : Tue Jan 31 06:08:13 2017
Branch Name : rel_3.1.1.1
Build Tag : CLWS_3.1.1.1.20170131.0608.p1
Build Mode : debug
2. show accessnodes cws <cws_name> oper-data

Expected output:
TrainingCap connected 88.88.88.1 88.88.88.2.0.223 10.65.0.223 44 71
42
21
9/21/2019

Verifying SW Update
To verify the CWS is successfully updated to the desired software and functioning as expected.
3. show accessnodes cws <cws_name> lte cell oper-data
Expected output:
5. SSH to each CWS and verify the following:

bash# tail -f /var/log/messages | grep -i AvgActiveConnUserCount
or
bash# tail -f /var/log/messages | grep -i ltecell
Look for following output:
011006 INF ltecellmgmt lterrm:1 ltecellmgmt.cpp:1842] avgActiveConnUserCount <Non zero value>
43

Verifying SW Update
• Now check if candidate CWS is connected and CWS cell is in service with following command:
#show accessnodes cws oper-data
• Configrm if cell is in service with following command:
#show accessnodes cws lte cell oper-data
* Cell InService takes approx. 2-3 mins. once CWS is connected.
44
22
9/21/2019
QUESTIONS?
45
23
9/21/2019
CWS Hardware
Installation
Rel. 4.3.x
Parallel Wireless, Inc. Proprietary PW‐SYS‐S11‐PW System Admin – CWS Hardware Installation‐4.3‐v1.0
• CWS Connectors and Deployment Model
• CWS Staging Before Installation
• Preparation Before Installation
• CWS Installation
Parallel Wireless, Inc. Proprietary PW‐SYS‐S11‐PW System Admin – CWS Hardware Installation‐4.3‐v1.0 2
1
9/21/2019
CWS Connectors and
Deplyment Models
CWS-3000 Connectors & Status Indicators
Component Port Label Description Component Description

RF (2 Ports) TRx1, Trx2 LTE / UMTS Access Alarm Alarm Port
Antenna Ports
DC Power Dc Power Connector
SFP Port Eth0 / Gig0 SFP port towards HNG
AISG Antenna Interface Standards Group Port
Power over Ethernet Eth1 / Gig1 Power over Ethernet
Alarm Alarm Port
(PoE) GigE (30 Watt) (PoE) GigE – Towards –
BHM / CWS / HNG
2
9/21/2019

Case – 1 – 3-sector – LTE 2x2 MIMO deployment with Wired BH

RJ‐45 RJ‐45 RJ‐45
BH To HNG

5

Case – 1 – 3-sector LTE 2x2 MIMO deployment with Wired BH and Wireless Mesh
BHM
PoE‐PSE
(Input)

PoE‐PSE
PDN
Wireless
Mesh
Serving EPC
BHM
PoE‐PSE
(Input)

PoE‐PSE
3
9/21/2019

BHM LTE BH To HNG
PoE‐PSE
(Input)

PoE‐PSE
BH EPC
Serving EPC
PDN

BHM
PoE‐PSE
(Input)
PoE‐PSE Wireless Mesh
BHM LTE BH To HNG
PoE‐PSE
(Input)
SFP Ethernet SFP Ethernet SFP PoE‐PSE

BH EPC
4
9/21/2019
CWS-3000 Connectivity Options

SFP for BH and RJ‐45 for Daisy‐Chain
Backhaul: 1000 Base‐X via SFP Backhaul: 1000 Base‐T via SFP
Daisy chain: 1000 Base‐T via RJ‐45 Daisy chain: 1000 Base‐T via RJ‐45

RJ‐45 for BH and SFP for Daisy‐Chain
Backhaul: 1000 Base‐T via RJ‐45 Backhaul: 1000 Base‐T via RJ‐45
Daisy chain: 1000 Base‐X via SFP Daisy chain: 1000 Base‐T via SFP
10
5
9/21/2019

Wireless Mesh
11
CWS-3000 Mounting Hardware & Connectors
12
6
9/21/2019
CWS-nk Connectivity Options
13
Multi-sector (wired backhaul, without mesh)
14
7
9/21/2019
Multi-sector (wired backhaul, with mesh)
15
Single-sector with BHM – Mesh and LTE Backhaul
16
8
9/21/2019
Multi-sector with BHM – Single Mesh
17
Multi-sector with 1 BHM – 3 Mesh Backhaul With Splitter
• In the proposed configuration, there are a number of options:

• If there are two CWS’s, use the POEs from the two CWS’s (as shown with dotted lines).
• If there is only one CWS present, then we must use a separate power-supply for the second BHM. For ethernet/data
connectivity, we can either:
• Use the SFP port on the CWS, or
• Daisy-chain from one BHM to the other.
18
9
9/21/2019
Multi-sector with 2 BHM – 3 Mesh Backhaul With 2 BHM
19
CWS Staging Before
Installation
20
10
9/21/2019
Staging of CWS
• Before shipping CWS/BHM onsite for deployment, it is first brought to PW Staging Lab or Operator Depot.
• CWS/BHM then connected to the Staging Server where a DHCP service is running.
• Upon power up, CWS/BHM attempts to obtain a IP via DHCP server running on staging server and sends CFG request to
Staging server
• In Staging server, under Devices, CWS UniRAN ID will be populated, to which a profile can be applied.
• A profile in Staging server, is a list of parameters like cloud/SON IP, Security gateway IP, Static/DHCP public IP, etc. that
can be applied to a CWS/BHM (devices) or a group of CWS/BHM that the operator might want to deploy in a particular
area/TAC/LAC.
• Upon applying profile, CWS state under Devices in staging Server will be in Configured State. At this point, the CWS is
ready/provisioned via Staging Server to connect to the HNG (with the cloud/Security gateway parameters)
• Power off and Disconnect CWS from Staging network, connect to operational network
• CWS should come up and establish IPsec connection to HNG and also establish cloud connectivity.
Staging Server+
DHCP Server
21
CWS/BHM Staging Using Staging Server
22
11
9/21/2019
Staging Parameters
Platform Independent Parameters Applicable to CWS/BHM/MWS/CCH
CLOUDSERVERADDR * HetNet Gateway SON Server IP Address
CLUSTER_INTF The CLAMP Interface. Select the Cluster Interface from the drop‐down list. The default is Wired Mesh Interface. This field is mandatory if you
enter a Cluster ID in the CLUSTERID field.
CLUSTERID The ID used to identify the cluster. Valid values are 0 to 41773. This is mandatory if a Cluster Interface is selected in the CLUSTER_INTF field.
GPPWANINTFNAME * Controls how the RANs role in the mesh network is determined. Select the GPP WAN Interface Name from the drop‐down list. The default is
AUTO.
HAMMERINTERVAL Interval in minutes during which if cloud connectivity is not established/restored the CWS is rebooted.
IPSEC Select the checkbox to enable IPSEC. The default is enabled.
PKI Select the checkbox to enable PKI. The default is disabled.
MESH_ADMISSION_CTRL Select the checkbox to enable Mesh Admission Control. The default is disabled.
PUBLIC_IP * Method used to provision the IP address the CWS uses to communicate to the HetNet Gateway Applications. Select the Public IP type from the
drop‐down list. The default is STATIC.
SEC_GW_ADDR * IP Address/Domain Name of Security Gateway if selected mode is STATIC

WAN_PING_DEST Alternate destination for ICMP pings.
WANPUBLICIP Method used to provision the IP address the CWS uses to communicate to the Security Gateway. Select the WAN Public IP type from the drop‐
down list. The default is STATIC.
WAN_IP_PROVISION_TYPE* The method used to provision WAN IP (static or DHCP).

WAN_IP_ADDR – IP The IP address of the WAN Interface if selection STATIC.
WAN_NETMASK The netmask for the WAN Interface.
WAN_DEF_GATEWAY The default gateway for the WAN interface.
23
Staging Parameters
• Platform Dependent Parameters Applicable to CWS‐nK
LTESTACKMODE The LTE Stack Mode. Select the LTE stack
mode from the drop‐down list.
Options are:
 FDD_T2K (default)
 FDD_T3K
 TDD_T2K
 TDD_T3K
RATMODE  GSM
 UMTS
 LTE
24
12
9/21/2019
Staging Parameters
BHM/CCH Specific Parameters – Mesh Interface
COUNTRY_ID The ID for the country. This field is automatically populated based on the selected
COUNTRY_NAME.
COUNTRY_STRING The code for the country. This field is automatically populated based on the selected
COUNTRY_NAME.
ESSID List of backhaul networks.
WIFI_DFS_ADJUST Rx Sensitivity adjustment for DFS (wifi0, wifi1, wifi2, wifi3)
WIFI_DFS_SP_THRESH Rx Sensitivity Threshold for Short pulses DFS (applies to all radios).
25
Staging Parameters
CCH Specific Parameters – Wi‐Fi Access
COUNTRY_ID The ID for the country. This field is automatically populated based on the selected
COUNTRY_NAME.
COUNTRY_STRING The code for the country. This field is automatically populated based on the selected
COUNTRY_NAME.
ACCESSPHYINTERFACE Interface to be used for Wi‐Fi Access. Select the Access Physical Interface form the
drop‐down list. The default is NONE.
26
13
9/21/2019
CWS‐nK Hardware
Installation
27
In This Section
• Pre‐Installation Preparations and Warnings
• Required Materials and Tools
• Pre‐Installation Procedure
• Mounting the CWS Outdoors
• Connecting the Protective Earth (PE) Ground
• Connecting the Ethernet Cable
• Routing and Connecting the AISG cable (Optional), User Alarm Cable (Optional), RF Cable,
and DC power cable
• Connecting the GPS Antenna
• Verifying the Installation
28
14
9/21/2019
CWSnk Preparation Before H/W
Installation
CLICK HERE TO ADD SUBTITLE TEXT
29
Pre‐Installation Preparations and Warnings
• Please refer CWS‐nk Hardware Installation Guide
30
15
9/21/2019
Product Overview ‐ Physical Interfaces
• This image is bottom view of CWS‐nk:
31
Product Overview ‐ Physical Interfaces
• This image is front view with solar shield:
32
16
9/21/2019
Installation Required Materials and Tools
Required materials
The following is a list of all supplies that may be utilized during the installation of the CWS:
• Antioxidant compound
• Cable labels (used to label both ends of cables before routing and installing cables)
• Power cable (customer provided, must meet product‐specific DC power requirements)
• Red tape or tags ‐ 145C or equivalent, for tagging of DC power cables
• Silicone caulk
• Tape ‐ Electrical
• Tie wraps
• Hose clamps (User Supplied)
• Ground lug kit (User Supplied)
• GPS Antenna (User Supplied)
• Lightning protector (User Supplied)
• Wall anchors (optional)
33
Required Tools 1/2
The following is a list of the required tools that may be utilized during the installation of the external
interfaces:
• Crimping tools 22‐16 gauge, 10‐4/0 gauge (5‐120 mm2) for installation of terminal lugs and c‐taps
• Electrical conduit installation equipment and materials
• ESD wrist strap
• Eye protection gear ‐ Safety goggles or glasses (R‐3055)
• Gloves ‐ Low‐voltage rubber lineman's gloves (R‐4285)
• Heat gun used for heat shrink tubing
• Insulated hand tools (for completing electrical connections)
• M10 eye bolts or hoisting rings
• Measuring tape
• Multi‐meter or Ohm‐meter
• Nut driver set (US system type) with 10‐inch extension, Nut driver set (metric) with 250‐mm
extension Ohmmeter (multi‐meter, volt/ohmmeter, or equivalent)
34
17
9/21/2019
Required Tools 2/2
• Screwdrivers (power and manual), flat‐blade, Phillips, and Torx
• Small and regular slip‐joint pliers Tongue‐and‐groove, slip‐joint pliers
• Socket sets (US system and metric) various drives
• Tie wrap tool
• Torque wrenches, 2 ‐ 34 N∙m(17.7 ‐ 300 lbf‐in)
• Torque wrenches, 6 ‐ 200 N∙m (4.4 ‐ 150 lbf‐ft)
• Wire cutter [capable of cutting up to 50 mm2(1/0 AWG)] Wire stripper
• Wrench ‐ Adjustable, (20 mm / 3/4 inch) open‐end wrench (or set of fixed open‐end
wrenches)
‐If fixed, open‐end wrenches are used, both metric (mm) and US system (in) wrenches will
be needed
35
Shipment Verification and Unpacking
• While unpacking the CWS, do not remove the foam blocks attached to the antenna connectors, as the foam protects
the antenna connectors during installation.
• To unpack the shipping container:
1. Open the shipping container and carefully remove the contents.
2. Make sure that all items listed in Packing Slip are included in the shipment and check for damaged items. If there is a
problem, call your Support Representative. Refer to the Product Technical Support chapter of this guide for contact
information.
3. Place the CWS on packing foam or an anti‐static mat and remove all packing foam that is between the solar shield
and body
Note: Save the shipping containers in
the event that you need to return
one or more components to Parallel
Wireless.
36
18
9/21/2019
Preparing the CWS for Installation
• Following figure provides the locations of the components contained on the CWS that will need to be
prepared before the actual installation.
37
Preparing the CWS for Installation
To prepare the CWS for installation, complete the following:
1. Remove the DC power port cover; GPS port cover, and two RF port covers.
2. Open the Optical port, Power over Ethernet (poE) port, AISG port, and ALARM port.
Note: Do not open unused ports.
3. Insert Open chain links. This component is not supplied with CWS.
38
19
9/21/2019
CWSnk H/W Installation
CLICK HERE TO ADD SUBTITLE TEXT
39
Mounting CWS Outdoor
The CWS can be mounted on almost any secure object or surface. However,
this chapter describes how to mount the CWS on an outside pole and wall,
only.
• Mounting the CWS on a Pole, Using a Hoist
• Mounting the CWS on a Pole, without Using a Hoist
• Mounting the CWS on an Outdoor Wall
40
20
9/21/2019
Mounting the CWS on a Pole, Using a Hoist
• The procedure that follows describes how to mount the CWS on an outside pole, using a
hoist to assist in the lifting.
• If you do not have a hoist or some other piece of lifting equipment, refer to the Mounting
the CWS on a Pole, Without Using a Hoist section.
41
To mount the CWS on an outside pole using a hoist, complete the following:
1. Using the Open Chain Links and a hoist, lift the CWS up and place it against the pole, as shown in left
image and Insert the user‐supplied bolts (M10 or 3/8”) into the slots on the mounting bracket as shown
in right‐side image.
42
21
9/21/2019
3. Tighten each clamp, as shown in figure to secure the CWS to the pole.
4. Remove the Open Chain Lins from the mounting bracket.
43
Mounting the CWS on a Pole Without Using a Hoist
To mount the CWS on an outside pole without using a hoist, perform the following:
1. Remove the mounting bracket from the CWS by loosening the four M8 screws (Do Not completely remove
the M8 screws from the holes), as shown below:
44
22
9/21/2019
Mounting the CWS on a Pole Without Using a Hoist
2. Place the mounting bracket against the pole and tighten each user‐supplied clamps to secure the CWS to
the pole.
3. Place the CWS on the mounting bracket and tighten the four M8 side screws as show in figure below and
reattach the solar shield onto the mounting bracket and tighten the 4 M5 screws:
45
Mounting the CWS on an Outdoor Wall
To mount the CWS on an outdoor wall, perform the following:
1. Using the following figure, drill four holes and install the user‐supplied wall anchors into each mounting
hole, as shown below:
NOTE:
• The mounting surface attaching
screws and the optional wall
anchors, must be able to support a
static weight of approximately 100
pounds.
• 1/4 inch, minimum, mounting
fasteners should be used for the flat
surface mounting.
• Appropriate wall anchors should be
used, dependent upon the mounting
wall material.
46
23
9/21/2019
2. Tighten each anchor nut to secure the anchor to the wall and remove anchor nuts and washers.
3. Install the mounting bracket on the anchor studs, install anchor washers and nuts, tighten each anchor nut
to secure mounting bracket to wall, as shown in figure below.
47
4. Place the CWS‐3050‐08 901‐2021 on the mounting bracket and tighten the four M8 side screws, as shown
in figure below:
48
24
9/21/2019
5. When mounting the CWS to a pole or wall, use an anti‐oxidant on the four arrow points shown in figure
below:
49
Connecting the Protective Earth (PE) Ground
WARNING: This ground MUST BE connected first, before any other port/cable is attached and before power
is applied. The 2‐hole, flex lug is user supplied and should be Panduit Part Number LCCX2‐14B‐E or similar.
To connect the PE to ground, perform the following:
1. Route the 35 mm2 (#4 AWG) ground cable pigtail from the ground system (installed during site preparation)
to the PE ground pad, located on the lower left side of the CWS.
2. At the CWS end, cut the ground cable to the proper length and strip the end of the cable.
3. Crimp the 35 mm2 (#4 AWG) two‐hole lug (from the user‐supplied ground lug kit) onto the end of the
ground cable. Clean the contact surface area and use antioxidant to prevent oxidation.
4. Connect the ground lug to the CWS PE ground pad using the supplied M6 screws, lock washers, and flat
washers. Use antioxidant at the ground pad.
50
25
9/21/2019
Connecting the Protective Earth (PE) Ground
is applied. The 2‐hole, flex lug is user supplied and should be Panduit Part Number LCCX2‐14B‐E or similar.
5. Torque each M6 screw (see figure below for the exact location) to 5.6 Nm (50 lbf‐in).
51
Connecting the SFP Transceiver and Ethernet Cables
Cat 6, shielded Ethernet cable must be used.
To connect the Ethernet cable to the CWS, perform the following:
1. Prepare the Cat 6, shielded Ethernet cable to include the Ethernet connectors (see Figure 14). Note that
weatherproof/IP67 terminations must be used. The following table provides information about the user
supplied weatherproof shell for the LAN connectors.
Usage Radiall Component Part Notes

Number
Copper (Cat 6), for R2CT.127.001 or R299.989.004 Note that cable diameter must
BH.1 or BH.2 port be between 6.5 mm to 7.1 mm
for weatherproof seal.
LC Duplex for SFP R2CT.117.000 or R2CT.117.009
(BH.1 port)
52
26
9/21/2019
NOTE: Cat 6 shielded Ethernet cable must be used.
2. Connect the SFP Transceiver cable to CWS optic port as shown below:
53
NOTE: Cat 6 shielded Ethernet cable must be used.
3. Connect the Ethernet cable to CWS Ethernet port as shown below:
54
27
9/21/2019
Routing and Connecting the AISG Cable (Optional)
To route and connect the AISG cable, complete the following:
1. Install and route the AISG cable from the AISG port on the bottom of the CWS to the respective external
antenna line device (ALD) port.
2. Remove the protective cover from the AISG port on the CWS, as shown below and connect the AISG
output port to the AISG in port of another ALD.
• NOTE:
• To connect the AISG cable to
the AISG port, plug the AISG
cable into the AISG port and
hand tighten the outer
connector shell to secure the
cable.
• Refer to CWS LEDs and
Connector Pinout section for
the connector pinouts.
55
Routing and Connecting the User Alarm Cable (Optional)
To route and connect the User Alarm cable, perform the following:
1. Install and route the alarm cable from the alarm port on the bottom of the CWS to the alarm distribution
frame (DF).
2. Connect the alarm cables to the DF.
3. Using an ohmmeter or multi‐meter, verify that there is continuity between the alarm cable connector pins
and the DF.
NOTE:
• This measurement is
performed on the alarm cable
connector (CWs side) with a
loop back of each pair (one‐
by‐one) on the alarm DF side.
• Using a multi‐meter, check
that no short circuits appear
between each pair and the
shielding wires.
56
28
9/21/2019
Routing and Connecting the User Alarm Cable (Optional)
4. Remove the protective cover from the alarm ports on the CWS, as shown in figure below.
5. Plug the alarm cable connectors into the alarm ports and hand tighten the outer connector shell to secure
the cables. Refer to CWS LEDs and Connector Pinout section for the connector pinouts.
57
Routing and Connecting the RF Cables
To route and connect the RF cable to the CWS, complete the following:
1. Install and route the RF cable to RF port.
NOTE: Ensure that the RF cable shielded grounding has been completed for all antenna
cables.
2. Providing adequate slack, cut each cable so it reaches its corresponding RF antenna connector or,
if applicable, its corresponding RF surge protector.
3. Terminate the end of each cable with a 4.3‐10 connector.
4. Remove the protective covers from the RF ports on the CWS.
5. Connect each RF antenna cable to its corresponding RF port on the CWS.
NOTE: RF Surge protectors are optional.
6. Torque each 4.3‐10 male connector to 25 Nm (18.4 lb‐in), at both ends (CWS and Antenna) of
each RF cable.
Important – Hold the body of the connector (part connected to the coaxial cable) with 22mm
open‐end wrench. Torque the rotating nut with a 32mm open‐end wrench.
58
29
9/21/2019
Routing and Connecting the RF Cables
7. Secure the RF cables along their route.
8. Now that the RF cable is routed, complete the following to connect the RF cable to the CWS. Following
figures show the location of RF ports in FDD and TDD model of CWS.
9. Connect the RF cables between CWS RF ports and the antenna.
RF Port in FDD Model
RF Port in FDD Model
• Connect the RF cables between CWS RF ports and the antenna.
• Connect the RF cables between CWS RF ports and the antenna.
59
Connecting the DC Power Cable
is applied. Also. for the power cable, it is recommended that you use 12‐18 gauge conductors in the cable
for safe operation. Using a power cable with an outer jacket diameter of 6‐18mm is required to produce
and maintain an IP67 seal with the power plug.
To connect the DC Power Cable, perform the following:
1. If not previously installed, route the customer provided DC power cable to the bottom of
CWS. Note that the conductors must be within an outer jacket to work with this DC plug.
2. Cut the DC power cable to an appropriate length and strip the ends of the wires.
3. Using the assembly instructions provided with the DC power plug, attach the DC power
cable to the DC power plug as follows:
‐Pin A to ‐48V
‐Pin B to 0V (return)
60
30
9/21/2019
Connecting the DC Power Cable
4. Open the DC power cover, plug the DC power cable into the ‐48V DC IN port, and hand
tighten the outer connector shell to secure the cable, as shown below.
61
Connecting the GPS Antenna
There are two types of GPS antenna connections provided:
1. Type 1 Antenna – For external GPS antenna installation
2. Type 2 Antenna – For integrated GPS antenna installation
NOTE: The antennas shown in this section are user provided and shown for
example purposes only. However, the antenna must be N‐type (male), 5 VDC.
62
31
9/21/2019
External GPS Installation
• Type 1 Antenna – This is accomplished by
connecting an extension cable between the
CWS and the items shown in figure here.
CWS‐nK
63
Integrated GPS Installation
• Type 2 Antenna – This is accomplished by
connecting directly from the GPS antenna to
the CWS as shown in figure here.
64
32
9/21/2019
Post Installation
To verify the CWS and its components installation, confirm the following:
• Inspect site and remove any loose tools, material, and parts.
• Verify that all the exterior mounting hardware and cable connections are
secure.
• Check the overall appearance of the CWS, ensuring there is nothing
unbalanced, unsecured, or out of alignment and that there is no unintended
mechanical alteration of CWS, mounting brackets, or support structure.
65
CWS LED and Connector Pinouts
CWS LED Indication
Priority Indication Mode LED Color LED State Comment
Highest
Boot Red Solid If going for 5 minutes or more, return to factory.
^
|
| Critical Red 1 Hz: On (0.5 sec) / Off (0.5 sec) Return to factory.
|
| Waiting for BH Amber 0.25 Hz: On (1 sec) / Off (3 sec) Check backhaul connection.
|
| VSWR Amber 0.25 Hz: On (3 sec) / Off (1 sec) Check antenna connection
|
|
Degraded on Run Amber Solid Check electronic alarm report / GPS *
|
|
| Standby for Cell Green 1 Hz: On (0.5 sec) / Off (0.5 sec) Ready
|
Lowest Run Green Solid In‐service
66
33
9/21/2019
CWS Connector Pinouts
• DC Power Connector
• The following table provides the locations and descriptions for the DC Power
connector (Amphenol C10‐730511‐Z2S) pinouts.
Pin Description
A ‐48 v Input
B Return
67
• SFP Transceiver Connector: The following SFP Transceiver RJ45 connector is
used with the CWS.
– 1000base‐T connections recommend using 201‐0009 (Foxconn/Avago ABCU‐5730ARZ)
• SFP Transceiver Optical Connector: The following SFP Transceiver optical
connector is used with the CWS.
– 1000base‐SX connections recommend using 201‐0007 (Finisar FTLF8526W4BTL)
– 1000base‐LX connections recommend using 201‐0008 (Finisar FTLF1426P2BTL)
68
34
9/21/2019
AISG Port
• The following diagram and table provides the locations and descriptions for the AISG Port
connector pinouts.
Pin Description
1 N/C
2 N/C
3 RS485B
4 RS 485B GND
5 RS 485B A
6 +10 to +30 VDC Output
7 DC Return
8 N/C
69
Alarm Port
• The following diagram and table provides the locations and descriptions for the Alarm
Port connector pinouts.
Pin Description
1 User_ALM_4_P
2 User_ALM_3_RTN
3 User_ALM_1_P
4 User_ALM_2_RTN
5 User_ALM_2_P
6 User_ALM_4_RTN
7 User_ALM_3_P
8 User_ALM_1_RTN
70
35
9/21/2019
CWS‐nK Hardware
Installation Examples
71
Key Requirements and how PW Meets Them
Innovative, Cost‐effective, Flexible, Future‐proofed
Cost‐effective Integrated Wired & Wireless Backhaul , all in‐one
Cost‐effective Low power consumption  OPEX savings
Self‐configuration, self‐optimization with SON
4 hours to install and commission one CWS
Plug‐n‐Play Under 3 days to light up a rural community with cluster of 4 CWS
Planning “Lite” – designed to be within notification rules
Eliminates backhaul challenge – can integrate capacity as becomes available
Flexible and Open Interoperates with any vendor core, any type of backhaul
Software defined Nodes – can be re‐configured UMTS & LTE
Future‐proofed Supporting 3G for voice now, VoLTE in the future,
Gateway is a key element for future 5G networks.
72
36
9/21/2019
Typical Installation Checklist / Steps
File for local permitting and ordinances
Landlord issues
Site Survey
Where is power coming from?
Traffic control
Grounding
Mounting
Testing and commissioning
Optimization
73
Parallel Wireless Approach: Simplifying Installation
Just connect to power, backhaul, & antennas, then power on!
File for local permitting and ordinances
Landlord issues
• Small form factor, no cabinet, less real estate
Site Survey
• Self‐configuring
Where is power coming from?
• Low‐power consumption; compatible with alternative power sources
Traffic control
• Automated by HNG
Grounding
Mounting
• Lightweight, small form factor, flexible mounting options
Testing and commissioning
Optimization
• Automated by HNG
74
37
9/21/2019
Parallel Wireless SON
Self‐Configuration Steps
1 New Cell Identified
Automatic B/H
2 configuration
3 Auto configuration
Initial PCI and RACH
4 configuration
INRT allocation and TX
5 power optimization
75
Multiple CWS Install
CWS 1 CWS 2 CWS 3
Backhaul
Backhaul + Power
Backhaul + PoE
Power Input 110/220 VAC or 48VDC
Modem Backhaul – Copper / Fibre
Fixed Backhaul – Ethernet Copper / Fibre
Wireless PtP Backhaul to other CWS
and/or
LTE 4G Backhaul to Core
BHM‐201
76
38
9/21/2019
Single CWS 1000 Install Option
100% Outdoor Implementation
No Need for additional Enclosure
Backhaul
Backhaul + PoE
Power Input 120/220 VAC
Fixed Backhaul – Copper / Fibre
and/or
BHM‐201
77
Single CWS 2000/3000 Install Option
100% Outdoor Implementation
No Need for additional Enclosure
Backhaul
Backhaul + PoE
Power Input – 48VDC
Fixed Backhaul – Copper / Fibre
and/or
BHM‐201
78
39
9/21/2019
Installation
Antenna Integration
79
Antenna options
Compatible with ANY configuration, ANY supplier
• Omni
• Directional
• Panel/sector
80
40
9/21/2019
Small form factor  can be
deployed anywhere
Easy and fast install: just plug
power and ANY backhaul
Panel AntennaDirectional panel antenna for
E x a m p l e : C a n a d a R o o f tlonger range signal
op Deployment
81
Panel/Sector Antenna
Example: LatAm Tower Deployment
82
41
9/21/2019
Omni Antenna
Example: Australian Rooftop Deployment
83
3-band RRA
All RATs All Bands Support
• Key components common
across radios
• Xylinx FPGA, ADI radio, NXP/FSL PAs
• Lego‐like design blocks for
rapid introduction of new
bands/power levels
• All RATs, all bands
84
42
9/21/2019
Easy Installation
• No complex equipment to
align
• Limited amount of parts to
install
• Light weight to carry up the
tower
• No complex cabling
• Plug‐n‐Play config via HetNet
Gateway
85
Cabling and Power Solution
Power
Optic
B1
Multi(Optic&Power) Connector
Triple Band B3
Antenna
1pair Multi cable
(1‐Power + 1‐Optic)
B8
Multi Junction Unit
3pair‐Multi cable
(3‐Power + 3‐Optic)
86
43
9/21/2019
Multi‐Band ANT PORT Solution
– 6 PORT ANT (W×H×D) = 305mm×1995mm×195mm
8 PORT Available (W×H×D) = 305mm×1995mm×195mm
1995mm
In the same dimension
305mm
Multi‐Band ANT PORT
LTE Band (Frequency) 6 PORT 8 PORT 10 PORT
Band 1 (2100M) 2T2R 2T2R 2T4R 2T4R 4T4R
eNB PORT
Note 6 Port ANT can be available 8, 10 Port using High Tech combining filter in the same dimension
87
Multi‐RET and Multi‐Band ANT Tilting
• Concept #4 : B1, B3, B8 each Tilt
• Concept #1, #2, #3 : B1 & B3 Tilt, B8 Tilt
B1,B3 B1
Phase Shifter Phase Shifter
Filter
B3
Phase Shifter
Multi Multi
RET RET
B8 B8
Phase Shifter Phase Shifter
 Note
‐ eNB(one among three) can control RET
‐ RF connector supply DC Power & Control. (No need AISG port)
88
44
9/21/2019
Multi‐Band ANT PORT Solution
– 6 PORT ANT (W×H×D) = 305mm×1995mm×195mm
1995mm
In the same dimension
305mm
Multi‐Band ANT PORT
LTE Band (Frequency) 6 PORT 8 PORT 10 PORT
eNB PORT
Note 6 Port ANT can be available 8, 10 Port using High Tech combining filter in the same dimension
89
Example of Simplifying the Network: Easy as Wi‐Fi
NEW approach
Traditional approach
Fully integrated
Just plug in IP
and power supply/back up
battery
vs.
Fully orchestrated by
HetNet Gateway
Not integrated,
Complex cabling 
RF power loss
90
45
9/21/2019
Triple Band RRA (Revolution Radio Antenna) vs Traditional Approach
Traditional Site RRA
TCO Savings
With limited site planning, minimum footprint, easy
installation & Site rental cost reduction
Scalability
Same Form factor (Standalone & 3‐band RRA)
Easy to add for additional capacity
Easy Maintenance
Self‐configuring, self‐optimizing, self‐healing via HetNet
Gateway
Simple Field Replacement
(No using Tool & Bolts)
High Throughput for Best Coverage
Complex and costly to deploy Minimum RF power loss
and maintain
91
Installation
Antenna Bundling
92
46
9/21/2019
Antenna Design
93
Antenna design
• Multiple antennae are
bundled under one cover
• Reduces zoning challenges
and simplifies site
acquisition
• Not an “eye sore” – easier
to work with the locals on
obtaining site right access
94
47
9/21/2019
Installation Example, UK
• Bundling Antennas to Solve Municipal Regulations
• Addresses challenges Simple (not obscure)
of node/antenna Discrete Compact Integrated
Antenna Bundle containing:
Mast Mounting
installation when no Similar to TV Mast
• Mesh
towers are available • Access Antennas
• Allows for
unobtrusive
installations on the
side of homes and
buildings Node ONLY Cabinet (nothing Cable Run in
else is in the cabinet) for
• Addresses municipal aesthetics and to meet zoning Matching Conduit
law regulations laws
95
Deployment
Site Solutions
96
48
9/21/2019
Deployment Use Cases
• One solution for many use cases

• Greenfield
• Network expansion
• Rural
• Communities, mesh connected communities
• Low-density or high-density villages
• Suburban
• Densification
• Mobile Black Spots (“Not Spots”)
• Offload
• Rapid deployment
• Smaller footprint w/lowest power consumption
• Eco-Friendly
97
Deployment models
Tower Site
Pole
Rooftop
Wall mount
Cabinet/Wall
mount
98
49
9/21/2019
Site Solution: Tower and Accessories

Greenfield and Rooftop sites Tower Site
• Tower & Accessories

• Electricals
• Antennas
• Fences & Gates
• Rectifiers / SMPSs
• DG & Batteries
• Power Management
• Cable Management
• Network Monitoring
• Thermal Management
99
Rural Tower Site

Chain link Fence, solar Tower Site
• Site area
• 10m * 10m approx
• Security Fence
• 2.2m Height
• 2m pole + anti climb razor wire)
• Entrance gate
• 1m wide
• Gravel Floor
• Low/Zero Maintenance
• Weed/Plant-Free
• Grounding System
• Equipment grounding and Lightning
• Concrete base for

• Solar
• Tower
• VSAT
100
50
9/21/2019
Rural Tower site

30M Tower Tower Site
• Tower
• Self support tower
• 30m (6 x 5m sections)
• Steel grade Q345 & Q234
• Galvanized – ISO 1461
• Template-based (for relocation option)
• RAN (2x40 multi-mode CWS)
• Carrier-grade
• Self-config
• Omni / Diversity Antennas
• Flexible transport options (incl. satellite and mesh)
• UL 67.79 km radius / DL 72.42 km
• Bandwidth management
• HetNet Gateway - local or cloud-based
• Local breakout, for local calls (to save on bandwidth)
Omni antennas
• QoS management
• SON to optimize RF and power consumption when no active calls
• EMS for reports, alarm indication
101
Tower Site
Solar System Tower Site
• Modular solar system to support future expansion

• 3 Day Autonomy
• Basic Solar configuration for Omni site
• Solar easily scaled for 3-sector site
• No need for diesel generator
• Noise, Pollution and Re-Fueling / Maintenance
102
51
9/21/2019
Chain Link Fence

Tower Site
• Chain-Linked Fence
• Safety and Security in Remote Locations
• Deter Human and large animal penetration of site
• Barbed-wire / razor wire
• Prevent climbing and unauthorized entry
103
Anti-Climb Fence
Chain link, galvanized + powder coated Tower Site
104
52
9/21/2019
Alternative Power Sources
Wind, diesel, fuel cell and other technologies can be used
Fuel cells:
• Could be coupled with solar
• No hazardous emissions
• Easy change of fuel cartridges
• Very quiet
• Fuel (if spilt) evaporates quickly and dilutes in water
• 1.4 kWh per kilogram
• Fuel cells can be easily hidden/camouflaged along with
quiet operation which reduces the impact in tourism
locations as part of rural coverage delivery.
105
Solar Site
Reduced TCO and smaller site footprint
• PW technology deliver an option for solar powered base

station sites
• Smallest power consumption at peak operation on the
market requires less solar panels and batteries for back
up
• A full solar solution is possible.
• With the low power consumption of the CWS nodes coupled with
the low power backhaul options, the power budget is reduced in
turn reducing infrastructure requirements and cost.
• For sites where local non‐powered rural buildings are used (barns,
etc.) the building roof can be used to mount solar equipment
without the need for additional poles, strut and mounting
arrangements.
106
53
9/21/2019
Battery Back up Requirements

Power Saving Mode
• Smart power saving modes, which has a drastic impact on power draw.
• During non-peak hours, base stations can go into energy saving mode/sleep
mode.
• Once the macro cell utilization is less than the threshold (and once the base
station’s proximity sensor no longer detects nearby users) these cells can be in
energy saving mode and may transmit only if required.
• Parallel Wireless SON self-learning algorithm senses traffic patterns, load
on each cell, and user proximity to the cell and can then instruct each cell
to go to power saving mode.
• With careful planning and analysis, battery backup requirements can be
reduced based on the savings from these smart power saving modes.
107
Example of Configuration
3 Sector configuration Pole
• Each sector (multi carrier/ band/ mode)

supported by single CWS.
• Sectors are orchestrated by HetNet GW
(virtual Base Station)
• CWS form resilient ring topology to add
resiliency/ diversity into backhaul. CWS
include cell edge routing functionality.
• CWS support wireless mesh backhaul.
• HetNet GW based SDN policy control for
backhaul traffic.
• No cabinets on the ground !
108
54
9/21/2019
Pole Mount Options

1 x Dual Mode CWS + 1 x BHM Pole
• Coverage Solution
• CWS provides 2G, 3G, 4G, 3G+4G ANT
• Remote software upgrade for new modes,
functionality and releases
• Antenna
• Low profile omnidirectional X antenna
• Mounting
•
BHM
Back‐to‐back CWS + BHM simplifies CWS
mounting, lowers visible profile and reduces
mast wind loading.
• Service Housing
• Power conditioning and surge protection) in
service housing
• Modem, PSU (DC), circuit‐breaker and
Ground Based Service Housing
metering (where needed) PSU, MCB, Meter, Modem
• Cabling
• BHM power from CWS PoE (simplifies power
and cabling) Ethernet connection up to
100m or fiber for extended reach.
48V Supply and Ether net as required) Mains Supply and Ether net as required)
can by 50 meters away
109
Leveraging Existing Rural Power Pole Assets

Pole
• The Parallel Wireless CWS Base Station has flexible

backhaul options including an integrated optical SFP
connector which allows a direct long-haul fiber
connection (back to a local or distant fiber aggregation
node).
• The CWS is All-in-One with a small form factor allowing a
low-impact installation in any rural environment.
• DC power could be trenched from a local power source
to a pole where infrastructure is installed. Additional
availability of fiber infrastructure in the rural locations will
allow more effective backhauls options
110
55
9/21/2019
CWS Installation on a Pole

Pole
• Lightweight and small form factor makes for easy

installation
• Small size allows CWS to be installed anywhere: towers,

street furniture, sides of buildings, etc.
• Reduces site acquisition costs
• Self-configuration capabilities further simplifies

installation: no need for RF planning, just plug in and
power on
• No specialized equipment required
• Little to no RF/engineering training required
• Can be installed by regular installers
111
APAC: Rooftop Installation

Rooftop
112
56
9/21/2019
Rooftop deployment
Rooftop
• Simple rooftop installation

• Easily mounted and anchored to existing rural Buildings
• Low visible impact
• Low wind-loading equipment orientation and structures
• Dust and Storm-proof
113
Building
Solves municipal law restrictions Wall mount
Discrete Compact Integrated
Antenna Bundle containing
Access and Mesh Antennas
Simple (not obscure)
Mast Mounting
Similar to existing TV
Aerial
Cable in matching
conduit to existing
pipes / gutters
Node‐ONLY Cabinet (noiseless / no fans
required for cooling) Aesthetic,
unobtrusive. Easily meets zoning laws
114
57
9/21/2019
Wall/rural
Wall mount
• All-in-one coverage solution + antenna for discrete rural deployment

• Cabinet blends with rural residential “furniture”
• Dual CWS provides 3G, 4G, 3G+4G with option for multiple bands in the same cabinet or sector solution
• Remote software upgrade for new modes, functionality and releases
• Antenna
• Low profile omnidirectional antenna
• Mounting
• Back-to-back CWS + BHM simplifies mounting, lowers visible profile and reduces mast wind loading.
• Service Housing
• Power conditioning and surge protection) in service housing
• Modem, PSU (DC), circuit-breaker and metering (where needed)
• Cabling
• BHM power from CWS PoE (simplifies power and cabling) Ethernet connection up to 100m or fiber for extended
reach
115
Wall Mount – Option

1 x Dual Mode CWS + 1 x BHM Wall mount
• CWS provides 3G, 4G, 3G+4G
• Remote software upgrade for new modes,
functionality and releases
• Antenna
• Low profile omnidirectional antenna
• Cabinet
• Wall mounting, secure cabinet
• Noiseless (no fans)
• Service Housing
• Power conditioning and surge protection,
• Modem, PSU (DC), circuit‐breaker and
metering (where needed)
• Cabling
• Ethernet connection up to 100m or fiber for
extended reach.
116
58
9/21/2019
Detail for Dual CWS Wall‐Mount Cabinet Cabinet/Wall
mount
Feeders for:
3G/4G CWS1 Feeders for:
Mesh
2 x In Band BH / Mesh 1
3G/4G CWS2
GPS To Antenna 2 x Access RF - 3G/4G Feeder
2 x Mesh 2 Feeder Conduit
550 mm 2 x GPS Conduit
220 mm
220VAC 220VAC
BT BT
Comb.
Comb. Combiner
Cable Entry
2x xCABLE ENTRY
1202
mm
1202 mm
CWS CWS CWS
CWS 2050 CWS 2050 PoE from CWS
to BHM
POE link CWS to BHM-2
BHM
BHM
Space For Modem
Housing
BHM-2
550 mm
117
Existing Dual CWS Install Cabinet/Wall

3G and 4G from Separate CWS 550 mm mount
1202 mm
CWS CWS
BHM
118
59
9/21/2019
Single CWS Cabinet Cabinet/Wall

3G and 4G in 2100 Band from Single Dual Band CWS mount
CWS & BHM Assembly CWS & BHM Assembly
With Cover Without Cover
CWS 2050
830 mm
BHM-2
190 280 mm
mm
Cover
Base
119
Detail for Single CWS Wall‐Mounting Cabinet Cabinet/Wall
mount
Feeder Feeder
Conduit Conduit
200 mm
MCBs
Breakers
220VAC 220VAC
B
BT T CWS CWS
BT
800 mm
BHM BHM-2
Modem Space for

Modem
Housing
PSU
420 mm
Cable Run
120
60
9/21/2019
Use Cases
Reimagine Rural Cellular
121
Images of team working on site
122
61
9/21/2019
Addresses federal and local regulations
UK Deployments
123
UK Deployments
124
62
9/21/2019
Asia Deployments – Satellite Backhaul
125
APAC: Rooftop Installation
126
63
9/21/2019
Aerial CWS via Weather Balloons
Coverage for public safety, rural, emergencies, or to extended capacity at events
CWS‐1050 small cell w/ Omni antennas
flexible backhaul Omni antennas
(TX/RX and RX)
• Provides LTE Access (TX/RX and RX)
• Low power consumption
(150W)
BHM: LTE backhaul
module
Mesh Antenna
127
Use Cases
Reimagine Urban Deployments
128
64
9/21/2019
Barriers for Deployment of Urban and Hyperdense Networks
• That Parallel Wireless Solutions help address
Simplify Reduce OPEX, Support Support

Flexible
Deployments Increase ROI Multi‐Vendor Network‐haring
Macro network Network sharing / new
Simplified deployment Reduce Backhaul costs Backhaul availability
interworking ownership models
Securing optimal site Reduce power Interoperability and

Power availability
locations consumption multi‐vendor
Streamlined approval Interference and
New Services
process macro interworking
Networking
SON and automation provisioning and site
costs
Site acquisition
129
Support for Multi-vendor deployment

Support Multi-
Vendor
Support Multi‐ • HNG provides standard S1 and X2 interfaces allowing it

to work with any vendor using standard 3GPP
Vendor interfaces.
• SON allows neighbor cell list management there
smoothly enabling hand-in’s and hand-out’s to macro
Macro network
cells.
interworking • Home NodeB and Home eNodeB gateways in the HNG
allow any kind of small cells to work with the existing
Interoperability and multi‐
vendor solution.
Interference and macro
interworking
130
65
9/21/2019
Support for Network-Sharing

Support Network-
Sharing
• HNG enables MOCN and MORAN RAN sharing thereby

allowing it to work as a neutral host solution.
Support Network‐
Sharing • Neutral host operators can also enable MVNO and other
innovative models in addition to MNO based RAN sharing.
Network sharing / new
ownership models
131
Solution Overview
Urban Deployment
• 1 HetNet Gateway (HNG)
EMS orchestrates all 3 scenarios
Wireless Mesh
IP Backhaul
• Self‐configuration enables instant
AAA deployment; easy to move the
4G interfaces
network
IPsec Core • HNG can be deployed locally or in
Gi the cloud
HetNet Gateway Internet • EPC Can be deployed locally or in
the cloud
1 2 3
Scenario 1) Network Capacity Scenario 2) Indoor Coverage Scenario 3) Seamless Mobility

132
66
9/21/2019
Traditional Approach vs. Reimagined Approach
Traditional Solution Reimagined Solution

 Smallest footprint
 Rapid deployment
 Passively cooled
 Low‐cost
 low power consumption
 Flexible backhaul
Simplify Reduce OPEX /

Flexible
Deployments Increase ROI
133
Small Cells on Bus Stop
• Multiple CWS supporting different bands Antenna location
Antenna location
Coverage &
Capacity
Flexible
CWS located in digital signage on a
bus stop Simplify
Deployments
134
67
9/21/2019
Hidden in plain sight

Using street furniture to mount/hide base stations
Source: ThinkSmallCell
135
Needs for successful urban deployment
• “… a multi-operator solution is much • CWS has multi-carrier capabilities to

more attractive – it reduces the cost enable RAN sharing
substantially for each operator while
providing service for everyone.”
• “We also believe that small cells will
be key for 5G and that operators need • Small form factor and lightweight
to anticipate site acquisition to enable characteristics of CWS requires less
future mass deployments.” real estate than traditional solutions,
thus reducing site acquisition time/cost
• “Some had a perception that they • Small size and all-in-one approach
could not share a small cell site reduces the amount of equipment at the
because there would be too much site
equipment at each site, but now
realize that this is possible”
136
68
9/21/2019
Post Installation Checklist
Adobe Acrobat
Document
137
Deployment Example at XYZ
3G+4G Radio Splitting
138
69
9/21/2019
Field Setup
CWS (3G and 4G) B1 [2100MHz]
3G Packet Core
3G SGSN,
GGSN
UM ‐EMS
CAP
3G Circuit Core
3G MSC/VLR SCP
HetNet Gateway
Iuh 4G Packet Core

MAP
3G Access
SMSC
EPC
TRx Master 4G only S1
3G+4G Parallel Wireless
S6
Gx
4G Access HLR/HSS
PCRF
Gm
IMS
AAA
OUTDOOR POWER SYSTEM
139
RF Setup
1 CWS (3G+4G) B1 [2100MHz]
BoM per site:

• RF Site KIT
• 2 Passive Splitters
• 8 jumpers
• shrink
• 3 High Gain
Panel
• Band 1 Kathrein
742215V01
• Siklu MW
backhaul
• Feeder Loss from CWS to Antenna
• 4.8dB + 2x0.3dB=5.4dB
140
70
9/21/2019
Click Here to Add Title
Text
Parallel Wireless, Inc. Proprietary PW‐SYS‐S11‐PW System Admin – CWS Hardware Installation‐4.3‐v1.0
141
142
71
9/21/2019
Uni‐Manage (4.2.x)
and AR (1.1.0) Installation ‐
Lab
4.2.X and 1.1.0
Parallel Wireless, Inc. Proprietary
PW‐EMS‐E02‐Uni‐Manage and AR Installation, Interfaces, and Connectivity‐4.3‐v1.0
Objectives
• Uni-Manage Installation
• AR ISO and Application Installation
Parallel Wireless, Inc. Proprietary PW‐EMS‐E02‐Uni‐Manage and AR Installation, Interfaces, and Connectivity‐4.3‐v1.0 2
1
9/21/2019
Standard Network Diagram 2G Core
3G SGSN 3G Core
CWS3050‐05
MSC
S1‐C SGSN
IuPS
S1‐U
S1 HP Proliant DL360P Gen8 IuPS
HNG SECONDARY
IuH eth1
eth2
MSC
IuCS
Red de eth3
HP Proliant DL380 G7 Intranet
Transporte HNG PRIMARY
eth3
S1‐C 4G Core
IuCS
4G eth1
eth0
CWS3050‐28 O&M
S1‐U MME
HP Proliant
DL360P Gen8 eth0
UNIMANAGE/AR
S/P
GW
VPN O&M
VPN Internet
client
Minimum Hardware Requirements for PoC

Uni‐Manage
HP PROLIANT DL360P Gen8
CPU 8 x Intel(R) Xeon(R) E5‐2609 0 @ 2.40GHz
RAM 16 GB / DISK 1200.2 GB
ETHERNET, 4 x 1 GB NIC (Broadcom NetXtreme BCM5719, embedded)
AR
HP PROLIANT DL360P Gen8
CPU 8 x Intel(R) Xeon(R) E5‐2609 0 @ 2.40GHz
RAM 16 GB / DISK 1200.2 GB
ETHERNET, 4 x 1 GB NIC (Broadcom NetXtreme BCM5719, embedded)
2
9/21/2019
Rack Installation of HNG and Uni‐Manage Servers
5
5
UNI‐MANAGE
• Uni‐Manage is a GUI based
Network Element
Management System (EMS).
• It monitors and manages
multiple HNG and connected
CWS with one interface.
• Its client interface is
compatible with all popular
internet browsers i.e. Google
Chrome, Mozilla Firefox, IE
3
9/21/2019
PW Advanced Reporting (AR)
• PW AR is an analytics system,
with a BI front‐end for reports
and dashboards used for
performance analysis.
• It also serves as advance
reporting system and part of Uni‐
Manage.
• It provides pre‐defined statistics
and KPIs for usage and resource
analysis.
• It also provides interface to
create customized KPIs based on
Operator’s logic and formula.
Uni‐Manage in PW Solution
Simplified mobile network topology
Outdoor CWS: 2G/3G/4G
Internet
Uni‐Manage with
2G/3G/4G Advanced Reporting
SON,
2X40W 2X20W 2X5W 2G/3G/4G
core
Enterprise Small Cells interfaces, IMS Core
HetNet Gateway EPC
RAN interface
M2M or IoT Devices
SP Network Internet
Trusted Public
Wi‐Fi Wi‐Fi
4
9/21/2019
EMS Reference Capabilities
Device
Fault
Mgmt
Mgmt
Device and
Network
Map
Customer
Uni‐Manage + AR OSS
Integration
Inventory
Mgmt
Advance
Reporting
System
Audit
& Backup
Security
Point and & User
Click Mgmt
Interface
Uni‐Manage Installation and
Configuration
10
5
9/21/2019
Uni-Manage Installation Procedure

• Before You Begin
• Uni‐Mange System Requirements
• Uni‐Manage Base‐ISO Installation
• Uni‐Mange Application Software Installation and Configuration
• Uni‐Manage Setup and Connectivity
• Installing Uni‐Manage Application Software in HA System
• Using Certificate within the Uni‐Manage
• Upgrading Uni‐Manage Application Software
• Uninstalling the Uni‐Manage Software
11
11
Before You Begin

Before installing the operating system or product software, obtain the
following:
• Laptop (for the Uni‐Manage Client), with Internet access
• Operating system and product software DVD (Refer to your Parallel Wireless
customer service representative to obtain the correct software versions.)
• All necessary network IP addresses
• Make sure that your laptop connections are established. This connection
must be made before you begin downloading software on the Uni‐Manage
server.
12
12
6
9/21/2019
Uni-Mange System Requirements for PoC
• Operating system
• CentOS Enterprise 7.x
• Minimum hardware requirements

• CPU 8 x Intel(R) Xeon(R) E5-2609 0 @
2.40GHz
• 32 GB RAM
• 2 x 600 GB hard drive
• ETHERNET, 2 x 1 GB NIC
(Broadcom NetXtreme BCM5719, embedded)
• Client side, Web browser access

• Latest version of Google Chrome, Mozilla
Firefox or Microsoft Internet Explorer
13
Uni-Mange System Requirements – For HA System
• Network Requirements for a two-node High Availability (HA) Cluster

• When installing and configuring software in a two-node HA cluster, the two
nodes must have a dedicated and isolated network link between them.
• Also, three IP addresses are needed; one is used for the floating Virtual IP
address and two are used for the physical nodes, which require a dedicated
IP address.
-----------------------------------------------------------------------------------------------------
NOTE: The procedures in this chapter assume that you have already connected a
KVM (keyboard, video, and mouse) to your servers or that you have network
access to them. If you have not done so, please do so now.
14
7
9/21/2019
Uni‐Manage Base ISO Installation
1. Insert the software disk into the
desired server.
2. Reboot the server. This ensures
that the server reboots from the
software disk.
The Welcome screen is displayed.
3. Select Install a system with
advanced disk options.
You will be prompted to select a
time zone for your server location.
15
Uni‐Manage Base ISO Installation (Cont.)
4. Select the desired
timezone from the
drop‐down list.
5. Click Next.
You are prompted to
create a root password.
16
8
9/21/2019
6. Enter the Root password and
confirm.
7. Click Next.
8. Select Use All Space from
given type of installation list.
9. Click Next.
Disk space management screen
is displayed.
17
10. Select the target
device from the Install
Target Devices list,
located at the right
side box.
11. Press the left Arrow
button to move the
selected device to the
left side under the
Data Storage Devices
group.
18
9
9/21/2019
12. Click Next.
The installation begins.
19
Once installation completes, the following screen is displayed.
6. Click Reboot. The system unmounts the DVD from the machine.
20
10
9/21/2019
Stand‐Alone Uni‐Manage
Application Installation
21
21
Stand-alone Uni-Manage Application Installation
• This process assumes that Uni‐Manage Base ISO has been installed on newly created
VM or machine and the Uni‐Manage is operational and accessible using SSH.
• To set up Uni‐Manage application follow the instructions as provided in next slides:
22
11
9/21/2019
1. Get the tarball of desired build that you want to install.

For example: pw-unimanage-4.2.0.3-20190806.0152.fcs.tgz
2. Open the terminal window on Uni‐Manage console and log in as root user.
3. Untar the file with following command:
tar –zxvf pw-unimanage-x.x.x.x-YYYYmmDD.HHmm.fcs.tgz
This command will create folder /uni‐manage extractes the installation files in this folder.
4. Change to the /uni‐manage directory using following command:
cd /uni-manage
5. Confirm that an installation script and an installation build is there:
- install.sh
- unimaange-x.x.x.x-Build2.Linux.tar.gz
(for ex. unimaange-4.2.0.3-Build2.Linux.tar.gz)
6. Install the Uni‐Manage application by running the following install script.
# ./install.sh /opt/ems unimanage-x.x.x.x-Build2-Linux.tar.gz
• Follow the prompts to specify the installation variables. Accept the default values for these prompts, as shown in the
following, except where marked for required values that must be changed and be correct.
• If an invalid value is entered, issue a Ctrl/C and start over.
23
• The install begins and various information is displayed: For ex:
scripts/postgres/dropDatabase.sh
scripts/postgres/dropDatabase0SX.sh
scripts/postgres/dropDatabaseSolaris.sh
scripts/postgres/dumpDatabase.bat
scripts/postgres/dumpDatabase.sh
scripts/postgres/installPostgres.bat
. . . .
. . . .
scripts/sqlserver/restoreDatabase.bat
versionInfo.properties
Done.
Platform = Linux
Product name is unimanage
Elements_Run directory is /opt/ems/unimanage/application
• Now install script will prompt for various inputs from user. Provide required inputs and parameters based on your
installation model.
24
12
9/21/2019
7. Enter Y for the embedded PostgreSQL database server. If N is entered, a remote PostgreSQL database
server is required.
Are you using the embedded PostgreSQL database? [Y/N]: Y
The Internal (embedded) PostgreSQL database has been chosen.
8. Enter the Database Process Password or press Enter to accept the default value “postgres.”
Be sure to write this value down for future reference.
Specify database process password [postgres]:
9. Enter the database ID.
Specify database ID (or name): [unimanage]:
10. Enter the Database Server Port or press Enter to accept the default value “5432.”
Specify database server port [5432]:
11. Enter the Database User Name or press Enter to accept the default value postgres.
Specify database user name [postgres]:
25
12. Enter the Database Password or press Enter to accept the default value postgres.

Specify database password [postgres]:
13. Specify database startup thread pool size or press Enter to accept the default value of [1].
Specify database start up thread pool size[1]:
The installation continues and various information is displayed. For example:
. . . .
. . . .
Done.
HA Configuration files modified successfully.
Configuration complete.
Starting unimanage service ..
Starting the unimanage service
Starting the Element Center
/opt/unimanage/application/bin/startup.sh
Run directory is /opt/ems/unimanage/application
. . . .
. . . .
26
13
9/21/2019
14. Once installation is done, an important message will appear to open some important ports at Firewall:
########################### IMPORTANT ###########################
Please enable your firewall to allow access to the following ports:
80 (TCP)
443 (TCP)
54327 (UDP)
5701:5708 (TCP)
####################################################################
Press any key to continue. . .
15. Specify the service user name or press Enter to accept the default value:
Specify service user name [unimanage]:
16. Specify the service password or press Enter to accept the default value:
Specify service password [unimanage]:
17. Specify the bulkstats upload root or press Enter to accept the default value:
Specify the new bulkstats upload root [/o
18. Enable the archiving of the bulkstats file by entering Y:
Do you want to enabled the archiving of the bulkstats files [Y/N]:
27
18. Specify the new bulkstats archive folder or press Enter to accept the default value:

Specify the bulkstats archive folder [/opt/ems/bulkstats-archive]:
19. Specify the IP address of the local interface:
Specify the IP address of the local interface:
Once IP address of local interface is supplied, system will ask for cluster information.
20. Confirm the deployment scenario. If this server is installed in Cluster‐HA environment, then
enter Y else press N and Enter.
(Refer Installation Uni‐Manage Application in HA System section for Cluster‐based installation.)
In this procedure we are installing standalone server so press N:
Is this server part of cluster? [Y/N]:
This will complete the configuration of Uni‐Manage application.
HA Configuration files modified successfully.
Configuration complete.
Configuring memory heap settings ..
Modifying startup scripts in directory: /opt/pw/ems/unimanage/application/bin
. . . .
. . . .
• Now refer to Uni‐Mange Setup and Connectivity section.
28
14
9/21/2019
Uni‐Manage Setup and
Connectivity
32
Uni‐Manage Setup and Connectivity
• Configuring the Management Interface and Routing
• Configuring DNS
33
15
9/21/2019
Uni‐Manage Setup and Connectivity (Cont.)
• After the system reboots, the localhost login prompt is displayed.
• Once the Uni‐Manage software is installed, configure the following parameters:
• Management IP address and routing table
• Hostname
• DNS resolve
34
Configure Management Interface and Routing table, if required:
1. Open ifcfg‐eth0 file with the following command:
# vi /etc/sysconfig/network-scripts/ifcfg-eth0
2. Edit the ifcfg‐eth0 file to ensure the following network parameter entries. For example:
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=10.60.234.251
PREFIX=16
GATEWAY=10.60.0.1
DNS1=10.60.0.77
DOMAIN=parallelwwireless.net
3. Reboot the system.
35
16
9/21/2019
HA Link Between 2 Uni‐Manage
• Configure the networking parameters for eth1, which will be the interconnect link
between the 2 HA nodes.
• This is typically something similar to 192.168.1.1 for Node1 and 192.168.1.2 for Node2
but any IP address that does not conflict with the networks routing rules can be used.
36
• Configure the Hostname, using any of the following commands:
• # echo <hostname> >> /etc/hostname
• # echo <hostname-ip-address> <hostname> >> /etc/hosts
• # vi /etc/sysconfig/network hostname <hostname>
• For Example:
• # echo unimanage-training >> /etc/hostname
• # echo 10.61.21.233 unimanage-training >> /etc/hosts
• # vi /etc/sysconfig/network hostname unimanage-training
37
17
9/21/2019
NTP Configuration
Configure the NTP timing source:
1. To start the NTP service, execute the following command:
# service ntpd start
2. To ensure that the NTP service is automatically started upon reboot of the
Uni‐Manage server, execute the following command:
# chkconfig ntpd on
38
Setting Up DNS servers
1. Open the resolve.conf file to edit DNS Resolve Nameserver using the
following commands:
• # vi /etc/resolv.conf
2. Add the IP addresses of your nameserver. For example:
• nameserver 10.11.10.25
• nameserver 10.11.10.3
39
18
9/21/2019
Checking the Uni‐Manage Service Status
1. Run following command to check the status of Uni‐Manage service:
# service unimanage status

Following screen will appear:
# service unimanage status
Checking the status of unimanage service
Checking status of unimanage pid 25108
unimanage service is ONLINE
2. This command can be used to start, stop, restart the Uni‐Mange service:
# service unimanage {start | stop | status | restart}
3. These command can be used to start, stop, restart the other services:
# service ec_watchdog stop
# service ec_postgres restart
# service ec_watchdog start
4. Disable IPtable : service iptables disable
5. Disable firewall : service firewalld stop
40
Checking NetConf Status on HNG
Training1# show netconf-state sessions
netconf-state sessions session 15
transport netconf-ssh
username admin
source-host 10.60.234.251
login-time 2017-07-25T02:17:14-05:00
in-rpcs 1
in-bad-rpcs 13690
out-rpc-errors 13690
out-notifications 133
netconf-state sessions session 35
transport cli-ssh
username admin
source-host 10.11.11.140
login-time 2017-07-30T04:44:48-05:00
41
19
9/21/2019
Network Configuration at HNG
• Solving network issues
show network policy-routing {route-table | rule}
show network port {information | statistics | status}
show network route
• To see route between CWS, HNG, and Uni‐Manage interface:
show accessnodes cws lac-route
show netconf-state {capabilities | datastores | sessions | statistics}
42
Installing Uni‐Manage
Application in HA System
43
20
9/21/2019
Installing Uni-Manage Application in HA System
• The procedures that follow are used to install and configure the Uni‐Manage
software in a two‐node HA clustered system.
• When installing the Uni‐manage software in a two‐node system it is critical
to install the software on the first node, ensuring it has completed installing,
before installing the software on the second node.
44
Uni-Manage HA Architecture
• The HA Implementation relies on two major components:

• Clustered database by mariadb.
• Hazelcast distributed map implementation.
VIP
eth0:1 eth0:1
eth0 eth0
EMS 1 EMS 1
eth1 eth1
eth1 eth1
eth1 eth1
Database Database
Primary Backup
45
21
9/21/2019
Uni-Manage HA Architecture
• Primary and Backup servers reside on the same or separate Physical Server.
• The database provides common (replicated between two nodes and is configured in Active-Active
configuration) data repository for application to store events, statistics and other operational
data.
• The Hazelcast library implements distributed map in memory to provide access of connectivity
information between EMS1 and EMS2.
• It is configured to send keep-alive messages with 5 seconds intervals.
• If more then 30 seconds replies are not received, the mastership of application will change
initiating the fail-over processing.
• The processing consists of releasing VIP from PRIMARY, initializing BACKUP to become PRIMARY,
and assigning VIP on newly started PRIMARY node.
• Depending on how long node was serving in Backup state, starting time may vary from up to 15
minutes or longer.
46
Before You Begin New Installation for HA
Prior to very first deployment, verify basic functionality of the box in terms of what we expect to be
there:
• We need to make sure that an appropriate ISO, controlled by Parallel Wireless is deployed on
that box. The ISO produced by Parallel Wireless contains minimum set of software packages
needed for operations.
• Determine the size of expected data-store in terms of how many devices this installation intends
to manage and duration of daily statistics to be kept.
• Depending on the expected size of data-store, make sure that adequate RAM is available on this
box: it should be at least 128GB or more.
• Connect to Internet to make sure that the time zone, date and time are set properly from
internet. You can disconnect internet after that.
• If this is to be a part of High Availability Installation, verify that network interfaces eth0 and eth1
defined and contain static IP assigned.
• Verify that network performs properly. A round trip ping should be in microseconds range
between nodes for HA.
47
22
9/21/2019

On the first node
To install the Uni-Manage application software on the first node (primary) of a cluster, complete the
following:
1. Create a directory that is used to contain the software and navigate to it using the following commands.
Note that the directory shown is for example purposes only.
mkdir /opt/Build
cd /opt/Build
2. Download the desired build that you want to install. For example:
pw-unimanage-x.x.x-20180214.2140.ps_1.5.tgz
3. Untar the pw-unimanage tgz file into the /Build directory. For example:
# tar -xvf pw-unimanage-4.0.0-105-20180215.2126.ps_1.5.tgz
4. Install the Maria Database (MariaDB) software packages on Node 1 from the opt/Build/ParallelWireless
directory and execute the mariadb install script, as follows:
# cd ParallelWireless
# ./mariadb_rpms_install.sh
The Mariadb database installation starts, and the installation logs are available in
/root/mariadb_rpms_install.sh.log.
48

On the first node
5. Install the Mariadb cluster using the following script:
Note that you may be prompted for the root password several times. If so, enter the password
as needed.
# mariadb_make_cluster.sh 192.168.1.1 192.168.1.2
The Mariadb database cluster installation starts, and the installation logs are available in
/root/mariadb_make_cluster.sh.log.
6. Change to the /uni-manage directory as follows:
# cd /uni-manage
7. Install the Uni-Manage application by running the following install script.
# ./install.sh /opt/ems unimanage-4.0.0.105-Build2-Linux.tar.gz
Follow the prompts to specify the installation variables. Accept the default values for these prompts, as shown
in the following, except where marked for required values that must be changed and be correct.
If an invalid value is entered, issue a Ctrl/C and start over.
49
23
9/21/2019

On the first node
Enter Service User Name (unimanage):
Enter Service User Password (unimanage):
Enter Create Partial Backup during Upgrade (true):
Enter Host public IP Address (no default): 10.60.10.142
This is typically the static IP address assigned to the eth0 interface.
Enter Bulkstats Upload Root Folder (/opt/ems/bulkstats):
Enter Bulkstats Enable Archive (true):
Enter Database User Name (unimanage):
Enter Database User Password (unimanage):
Enter Database Name for Application (unimanage):
Enter Database Segment Pool Size (200):
Enter Database Host IP (public IP as above):
Enter High Availability use Flag (false):
Enter Virtual IP Address (no default):
Enter Netmask Virtual IP Interface (255.255.0.0):
Enter Master IP Address (no default):
Enter Other IP Address (no default):
50

On the first node
9. After the installation completes, the application is running. The installation logs
are available in the /root/DoInstall.log file.
10. Verify the installation has completed using the following command:
# ps -ef|egrep 'mysql|tomcat’
11. At this point the Uni-Manage application is running. Wait for VIP address to be assigned.
To verify that the VIP address has been assigned, execute the following command:
#ifconfig eth0:1
While waiting for Virtual IP address to be assigned, a display similar to the following is displayed.
ifconfig eth0:1 ==========> IP is NOT Assigned
eth0:1 Link encap:Ethernet HWaddr 52:54:00:76:7F:A7
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
This process may take an extended period before the system is initialized for the first time.
ifconfig eth0:1 ==========> IP is Assigned
eth0:1 Link encap:Ethernet HWaddr 52:54:00:76:7F:A7
inet addr:10.60.234.2511 Bcast:10.60.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
51
24
9/21/2019

On the first node
12. Once initialized, using a web browser, log into the Uni-Manage using the VIP address assigned.
Login credentials are uesrname=admin, password=admin. It is recommended that when you are
prompted to change your password change it for security purpose.
13. From with the Uni-Manage GUI, the primary should be displayed as Running. For example:
14.You are now ready to install the Uni-Manage software on the second node.
52

On the second node
To install the Uni-Manage application software on the second node of the cluster, complete the following:
1. Complete all steps contained within the installation on the first node on the second node.
2. Check logs/unimanage.log file to make sure that it starts in BACKUP mode, you can do this
via 'HA Status' command from within the GUI or check the log file for a line like the following:
“enter:Transitioned from=UNKNOWN to role=BACKUP”
53
25
9/21/2019
Using Certificate within the Uni-Manage
• Parallel Wireless' self-signed certificate is installed during the Uni-Manage

software installation. If you desire to use a Signed Certificate from a Certificate
Authority, the following process must be used:
1. Create a local Certificate Signing Request (CSR).
2. Submit the CSR to the Certificate Authority (CA) for signing.
3. Import the signed certificate and CA certificate.
4. Restart the Uni-Manage.
54

Creating Local CSR
To create a local CSR, complete the following:

1. Login as root. For example:
# ssh 10.10.10.186
2. Create a directory where the certificates will be stored. For example:
# mkdir certs
4. Change to the newly created directory.
# cd certs
5. Run the Certification Tool Script on the Uni-Manage Machine.
For example:
# /opt/ems/unimanage/application/bin/unimanage_cert_tool.sh -gencsr
10.10.10.186
55
26
9/21/2019

Submitting the CSR to the CA for Signing
• Submit the CSR to the Certificate Authority (CA) for signing. After the signing,
the CA returns two files, a CA's Root certificate and your signed certificate.
56

Importing the CA and Signed Certificate
To import the CA and Signed certificates, complete the following:
1. From within the /unimanage/application/bin directory execute the following command:
#./unimanage_cert_tool -import_ca_cert ca.crt
2. Enter Yes to trust the certificate.
3. Execute the ./unimanage_cert_tool -import_cert command on the certificate.
For example:
# ./unimanage_cert_tool.sh -import_cert test.crt
4. Verify which certificates are contained in the database, using the following command:
# ./unimanage_cert_tool -list
There should be two certificates: CA and UniManage. For example:
5. Install the new certificate keystore, using the following command:
# /opt/ems/unimanage/application/bin/unimanage_cert_tool.sh -install
6. Restart the Uni-Manage.
# service unimanage restart
57
27
9/21/2019
Upgrading the Uni-Manage Application
• The upgrade procedure consists of the following operations:

• Stops the currently running unimanage service.
• Creates a compressed file of the unimanage application folder.
A file called unimanage-Backup-YYYYddMMHHmm.tar.gz is created, which
contains a snapshot of the existing installation.
• Renames the "application" folder to "application_original".
• Re-Uses installation variables used during previous installation session or create new
ones, obtained from product configuration from previous setup.
• Extracts the application files from the specified compressed install kit. You will now
have a (new) application folder, with the contents of the new kit.
• Restores configuration parameters and settings from previous installation.
• Restarts the unimanage service after upgrade.
• Next slide explains the upgrade command.
58
Upgrading the Uni-Manage Application
To upgrade the Uni-Manage application software, complete the following:

1. Get the desired build that you want to Upgrade.
For example:
pw-unimanage-4.2.0.3-20190806.0152.fcs.tgz
2. Remove the mariadb using following command:
./mariadb_cleanup_previous_version.sh
3. Un-tar the file. For example:
# tar –zxvf pw-unimanage-x.x.x.x-YYYYmmDD.HHmm.fcs.tgz
4. Change to the /uni-manage directory, using the following command:
5. Invoke the upgrade script, using the following command.
Use uncompressed build file for upgrade:
#./upgrade.sh unimanage-x.x.x.x-Build2-Linux.tar.gz
6. Once upgrade completed restart the services or reboot the system.
59
28
9/21/2019
Uninstalling the Uni-Manage Software
To uninstall Uni-Manage software:

1. Open terminal window (Putty or something similar) and login as root user.
2. At the root prompt, invoke the uninstallation script by entering the following
command:
# ./uninstall.sh /opt unimanage-x.x.x-Buildx-Linux.tar.gz
For example:
# ./uninstall.sh /opt unimanage-4.2.1.0-Build2-Linux.tar.gz
The uninstall continues and is complete when the following is displayed.
Uninstall completed successfully
• Upon the completion of the uninstall procedure, the firewall settings are
removed.
60
Uninstalling the Uni-Manage Software (Cont.)
4. Once the uninstallation starts, a prompt to enter database process password is
displayed:
Specify database process password [postgres] :
5. Specify the following in subsequent prompts:
• Database server port [5432]
• Database user name [postgres]
• Database password [postgres]
6. Once the parameters are provided, the uninstallation script uninstalls the Uni‐
Manage software and the following prompt appears after successful upgrade:
Uninstall completed successfully
61
29
9/21/2019
Accessing Uni-Manage
1. Once the Uni‐Manage package is installed, you can connect to the Uni‐Manage through a recommended web browser and
valid IP address. For example: https://10.60.235.255/login.zul
2. Enter the User Name and Password.
3. Click Login. The Dashboard view (Home) page is displayed. If home page does not display, disable IPTABLE using the
following command::
service iptables stop
62
Dashboard View (Home Screen)
63
30
9/21/2019
Connecting HNG with Uni-Manage
• Refer Uni-Manage Usage and Integration module.
64
AR Installation and
Configuration
65
31
9/21/2019
What We Cover
• Minimum System Requirements

• Lab Preparation
• Prerequisites for AR ISO Installation
• Preparing KVM Setup
• Base ISO Installation
• AR Application Installation
• Setting Up HNG
• Upgrading AR System
• Recovering from Failed Installation
66
AR: Minimum System Requirements

• Operating system
• CentOS Enterprise 7.0
• Minimum hardware requirements

• CPU 8 x Intel(R) Xeon(R) E5-2609 0 @
2.40GHz
• 32 GB RAM
• 1200 GB hard drive
• ETHERNET, 4 x 1 GB NIC
(Broadcom NetXtreme BCM5719, embedded)
• Client side, Web browser access

• Latest version of Google Chrome, Mozilla
Firefox or Microsoft Internet Explorer
67
32
9/21/2019
Lab Preparation
1. Management IP address of AR Node
2. IP Address and HTTP Port of AR Server
3. User ID and Password for AR Server
4. Web browser
68
Prerequisites for AR ISO Installation
• AR Installation is recommended in an VM environment:

• KVM-based VM Installation
• VMWare-Based VM
• In this session we will talk about KVM-VM based installation.
69
33
9/21/2019
Preparing KVM Setup

Pre-requisites
• KVM hypervisor should be installed on server where VM needs to be

created.
• At least 8 CPUs and 32 GB Memory allocate for VM
• At least 1.2 TB storage available for data
70
Preparing KVM Setup
1. Get identified AR Build ISO on your KVM server where new VM for AR is to be created.
2. SSH to KVM Hypervisor machine and launch virt-manager
3. Following window will appear:
71
34
9/21/2019
Preparing KVM Setup
4. Go to File -> New Virtual Machine
72
Preparing KVM Setup
5. New window Create a new virtual machine will appear.

6. Select Local install media (ISO image or CDROM) and click Forward.
73
35
9/21/2019
Preparing KVM Setup
7. Browse to the selected ISO.

8. Select Automatically detect operating system based on install media.
9. Click Forward.
74
Preparing KVM Setup
10. Allocate memory and CPUs and click Forward.
75
36
9/21/2019
Preparing KVM Setup
11. Allocate Disk Space and click Forward.
76
Preparing KVM Setup
12. Provide VM name and click Finish.
77
37
9/21/2019
AR Base ISO Installation
78
• If you are using Bare-metal server put ISO disk in CD/DVD drive and reboot it. After reboot it will take you
to
• Installation Menu will appear. Hit Enter and let system perform installation.
79
38
9/21/2019
• Select Language and click Continue.
80
• Click Date and Time and set Date and Time-zone.
81
39
9/21/2019
• Select the Disk Option as below.
82
• Perform Manual Partitioning.
• Allocate all space for / (root) partition.
83
40
9/21/2019
• Review and click Accept Changes.
84
• Configure Network and Host Name.
85
41
9/21/2019
• Enable Management Port and Configure.
86
• Provide Management IP address and netmask and click Save.
87
42
9/21/2019
• Once Network and Hostname configured, click Done.
88
• Click Begin Installation.
89
43
9/21/2019
• Set Root password and click Done. Installation will start.
90
• Sit back and let installation complete.
91
44
9/21/2019
4. Once Installation is done, following prompt will appear.
92
AR Application Installation and
HNG Configuration
93
45
9/21/2019
AR Application Installation and HNG Configuration
• This process assumes that AR ISO has been installed on newly created VM or machine and the AR is
operational and accessible using SSH.
• To set up AR software (ver 1.1.0 or later):
1. Get AR installer file pw‐ar‐<ver>‐<date>.<timestamp>.REL_<release>.sh and put it in /root folder
2. Got to /root folder and make installer file executable. (chmod u+x <filename>)
3. Run the installer:
# ./pw-ar-1.1.0-xxxx.xxx.sh --install all 4.3 --clean
The previous command deletes all data and users including the
/pw/data
directory, if you want to proceed further, please enter [Y]: y
• Select the pipeline from the below options, as required (The hng bulkstat pipeline will be installed by
default.)
Choose the pipeline which needs to be installed (hng bulkstat pipeline will be installed by
default.) :
To install femto processing : select 1
To install pwadjustment processing : select 2
To install both femto counter and pwadjustment processing : select 3
To install none of the above : select 4
94
AR Application Installation and HNG Configuration
• Select option 3 and once completed, perform following procedure to start Incorta:
# su incorta
$ cd /pw/app/incorta/
$ ./start.sh
$ exit
• Launch Incorta from your browser. For example:
http://<AR IP>:8080/incorta/#/login
Using the following credentials:
Tenant: nethealth
username: admin
password: <administration password>
Note: Delete the file data<##>.tgz from /pw directory of the AR server once the installation has
completed successfully. By deleting this file a backup file is created and can be used in the event the
installation fails.
95
46
9/21/2019
Logging into Incorta
• You can log in to Incorta by going to http://<AR_IP>:8080/incorta/#/login.

• Use nethealth as the tenant and admin as user with provided password.
96
AR Dashboard View (Home Screen)
97
47
9/21/2019
Setting Up HNG for AR
• Once Incorta is accessible and functional, log in to the HNG server.

• Go to the Config mode and set up the pull destination for AR server:
$ config
$ statistics upload pull-destinations <AR_IP_address> directory <Dir_Name>
Note: Use the same name for the directory, as the AR IP address for simplicity.
For example:
$ statistics upload pull-destinations 10.61.22.36 directory 10.61.22.36
98
Adding User
• Once pull‐destination at HNG is set, add a user using following procedure:
1) Login as hngcounter user, using the su command as follows:
$ su hngcounter
$sftp_setup -o adduser -s hng -f tgz -r yes -d /hng/stats/<AR IP_address> -n
<HNG-HOSTNAME> -H <HNG-IP> -u northbound -p nbsftp -P 2024
For example:
sftp_setup -o adduser -s hng -f tgz -r yes -d /hng/stats/10.60.234.101 -n
hng_vnh01 -H 10.60.235.101 -u northbound -p nbsftp -P 2024
2) Verify that the user has been added by checking the usrmgmt.log file.
$ tail /pw/data/logs/usrmgmt.log
3) Start the Pipeline by logging in as the hngcounter user.
$ /pw/app/analytics/pm/start.sh
4) Verify that the AR Pipeline can pull the data from HNG Bulkstats (allow 15 minutes, once the
pipeline starts, before checking the log).
$ tail -f /pw/data/logs/hngcounter.log
99
48
9/21/2019
Upgrading AR System
AR Versions 4.x to 4.3
100
Upgrading AR System
• Upgrading the AR software from any previous version to the current

Version 4.3 is accomplished in the following manner:
• Upgrade the AR software.
• Migrate all data.
• Note: The upgrade process requires the AR system to be shutdown.

Follow the steps listed to successfully migrate the system and data,
before starting the upgrade process.
101
49
9/21/2019
Preparing for Upgrade
• In order to prepare for the upgrade, make sure you have sufficient disk space
available to backup the data stored in the current system. Create a backup
directory on the AR server to contain the backed-up data from the server. To
prepare for the upgrade, complete the following:
• Backup any Custom Dashboards
• Stop the Pipeline and Incorta Services
• Backup Data Files
102
Backing up Custom Dashboard for Upgrade
• Log into the Incorta UI using your user credentials and select and
export the custom charts.
103
50
9/21/2019
Stopping the Pipeline and Incorta Services
To stop the pipeline and Incorta services, complete the following:

1. Log into the AR server as the root user.
2. Switch to the hngcounter user.
su hngcounter
3. Stop the pipeline process.
./da/scripts/stop.sh
4. Enter exit to return to root user.
exit
5. At the root prompt, change to the incorta user.
su incorta
6. Stop the incorta process.
./pwAnalyticsPlat/stop.sh
7. Enter exit to return to root user.
exit
104
Backing-up the AR Data Files
The data backup process is accomplished as the root user. This allows access to all the files and
directories. Backup the data files, as follows:
1. Change to the nethealth directory.
cd /data/dataLanding/nethealth/
2. Tar all the files contained in the nethealth directory.
tar -cvf <backup dir><backupfileHng.tar> archive/
3. Change to the dataStore directory.
cd /data/dataStore
4. Tar all the files in contained in the dataStore directory.
tar -cvf <backup dir><backupfileDS.tar> hngCounter/
5. Change to the parquet directory.
cd /data/pwanalytics/tenants/nethealth/parquet/
6. Tar all the files contained in the parquet directory.
tar -cvf <backup dir><backupfileIncorta.tar> Aggregate/
105
51
9/21/2019
Upgrading the AR Software for Ver 4.x to 4.3.0
To upgrade the AR software, complete the following:

1. Install the AR software by following the install instructions contained in the AR Application
Setup and Connectivity section.
2. Once the AR software upgrade has completed, change to the incorta user and start the
incorta services.
Note: Do not start the pipeline manager service now.
# su incorta
# /pw/app/incorta/start.sh
3. View the installation log file for any failed steps that have occurred during the installation
process.
# show /var/log/pw-ar-installation.log
4. Perform data migration. Refer to the next section to accomplish this.
106
Data Migration after Upgrade 1/2
• The Data Migration process is performed as the root user, unless indicated. To perform the Data Migration
process, complete the following:
1. Navigate to the backup directory and identify the .tar file created in the Backing-up the AR Data
Files section with the data from Data Store <backupfileDS.tar>.
2. Change to the hngCounter directory and remove the directory named current.
cd /pw/data/dataStore/hngCounter
3. Untar the files into the current directory
tar -xvf <backup dir> <backupfileDS.tar>
4. After expanding the tar bundle, a directory called hngCounter should be present.
5. Rename the directory hngCounter to current.
mv hngCounter current
6. Change the ownership of files in current directory to hngcounter user.
chown -R hngcounter:datamgmt current
7. Change to the hngcounter user.
su hngcounter
107
52
9/21/2019
Data Migration after Upgrade 2/2
8. Start the Pipeline Manager service.

/pw/app/analytics/pm/start.sh
9. Start the migration process.
cd /pw/app/analytics/pm; python3 add_pipeline.py hngmigrator_pipeline
-------------------------------------------------------------------------------------------------------------------
Note: The data migration process may take several hours, based on the data volume. The status of data
migration can be checked periodically by viewing the hngmigrator log file, using the following command.
tail -f /pw/data/logs/hngmigrator.log
---------------------------------------------------------------------------------------------------------------------------------------
10. Upon successful completion of the data migration process, the dashboards should be refreshed.
Verify the Migration process

• After the migration process has completed, the AR data will be loaded in to the Incorta service with all the
dashboards showing the migrated data. At this time, verify the dashboards for the correctness of migration
process and data completeness. During this process, the Pipeline Manager will continue to run, periodically
collecting data from the HNG and CAP.
108
Recovering from a Failed Installation 1/3
• If an upgrade process fails, the AR system can be reverted manually to the previous version of software
with all data sets restored.
• To revert to a previously installed version, you must have the software bundle for the previous version
available.
• If the previous version is not available, contact your Parallel Wireless service representative.
• To revert to a previous AR software version, perform the following:
1. Place the previous software version bundle into a staging directory and follow the installation steps
related to that software version (refer to AR Application Installation and Connectivity) to ensure that
Incorta is up and running.
2. Restore the data from the three backup directories created in the data backup process (refer to
Backing-up the AR Data Files) and replace the data files into the same directories in the new
installation.
3. After all the data files are placed in the correct directories, log on to Incorta UI, click on the
icon located at the left pane.
109
53
9/21/2019
4. From the Schema page, Click Aggregate as shown below.
5. From the banner select Load and then Load now from the drop-down menu.
110
6. A pop-up menu appears showing more options. Select option Staging.
7. A confirmation window appears. Click Load to start loading data from staging. The Loading process
may take from a few seconds to several minutes to complete the loading of the data.
8. After successfully loading of the data, verify the validity in the populated dashboards.
111
54
9/21/2019
QUESTIONS?
Parallel Wireless, Inc. Proprietary
PW‐EMS‐E02‐Uni‐Manage and AR Installation, Interfaces, and Connectivity‐4.3‐v1.0
112
55

Book 1 PW Ipt Ic Level 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Book 1 PW Ipt Ic Level 1

Uploaded by

Copyright:

Available Formats

LTE RAN Solution

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

SON ‐ The HetNet Gateway virtualized SON Server

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Virtual Compute Virtual Storage Virtual Network

Computing Storage Networking

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Computing Storage Networking

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Virtual Compute Virtual Storage Virtual Network

Computing Storage Networking

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

CWS • Intercell RRM • Intercell RRM Control

• RRC • S1AP • S1AP • S1AP

• PDCP • SCTP • SCTP • SCTP

• MAC • MAC • MAC • MAC

• PHY • PHY • PHY • PHY

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

• Iu Signalling Link Mgmt • UE Management for HNB

RLC SCCP SUA SCCP SUA

M3UA M3UA Signaling

PHY IP (IPSec) IP (IPSec)

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

SFP (CWS/HNG) PoE ( To BHM/CWS/HNG)

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

IP Sec Gateway in HNG PKI – Public Key Infrastructure

NodeB HNG UMTS

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

• HP DL360 Gen9 or equivalent 2 socket x86 server

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

CWS – 210 – In‐Vehicle CWS

Timing Support Built‐in GPS Dimensions  Height 6.99 cm (2.75 ins), Width 24.13 cm (9.5 ins),

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Single Mode ‐ CAP Dual Mode ‐ CAP

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Parallel Wireless, Inc. Proprietary PW‐SYS‐ S02‐ PW System Admin Hardware and Software ‐4.3‐v0.1

Model Modem(s) Mesh (dBm) LTE Backhaul (dBm)

BHM‐201‐01 Single LTE Wireless Backhaul ‐ 23dBm

BHM‐201‐02 Single Mesh 25dBm ‐

BHM‐201‐04 Mesh and LTE Backhaul 25dBm 23dBm1