9771wce RNC VNPT

9771 Wireless Cloud Element Radio Network Controller
Course GS00641-C-1710 Bangkok

December 2017
Olivier Lenormand
1 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

Nokia INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
Agenda
1. 9771 Wireless Cloud Element RNC Introduction
2. Presentation of the Platform Management Server Hardware
3. Presentation of the 9771 WCE Platform Hardware
4. HP Intelligent Resilient Framework and multi chassis-link aggregations
5. HP switch Ethernet ports and LAGs
6. Platform and vRNC IP subnets
7. Platform VLANs
8. vCenter configuration of 9771 WCE RNC
9. Storage Array Network configuration

Agenda
10. Platform alarms monitoring

11. Software and license inventories
12. Customer Information Questionnaire (CIQ)
13. Vendors Documentation
14. Commissioning and Integration overview
15. 9771 WCE Platform Acceptance overview
16. Intra Release and Inter Release Software upgrade overview

9771 Wireless Cloud Element RNC
Introduction

Why a Cloud ?
5
Why Cloud?
ALU Controller Evolution Path Must Address:
10x scalability from current architectures
2G/3G/SCG convergence
Longevity recognizing that 2G and/or 3G will be
supported in networks for the next 10+ years,
even with LTE & LTE-A
Cloud Architectures promise:
Scalability
Hardware independence
Simplified integration of apps and functions
Cost Savings via multi-tenancy
Cloud + Controller: provides a perfect opportunity
for ALU to prove-in telecom functions (e.g. call-p)
on IT infrastructure

What is NFV?

NFV Reference Architecture
NFV Management
and Orchestration
Os-Ma
OSS/BSS Orchestrator
Se-Ma
Service, VNF and Infrastructure
Description
Or-Vnfm
EMS 1 EMS 2 WMS Ve-Vnfm VNF

LRCVNF
Mgr
Manager(s)
www.etsi.org
Manager(s)
(VNF Manager)
Or-Vi
VNF 1 VNF 2 RNC
Vn-Nf
Vi-Vnfm
WCE (NFVI)
Virtual Virtual Virtual
Computing Storage Network
Nf-Vi VMware vCenter,

ESXi/KVM (Virtualization Layer) OpenStack NOVA,
Vl-Ha HP Sim, NetApp
Santricity (VIMs)
Hardware resources
HP c7000 NetApp SAN HP 6125XLG
(Compute) (Storage) (Network)
Execution reference points Other reference points Main NFV reference points

WCE / NFV Reference Architecture
Relationship
NFV Management
and Orchestration
The WMS is an EMS that manages the 3G
Radio Access Network (RAN) composed of
both physical and virtual RNCs.
Os-Ma
OSS/BSS Orchestrator
LRC Manager is a VNF Manager responsible
for lifecycle management of WCE VNFs,
Se-Ma supports:
Service, VNF and Infrastructure
Description
Or-Vnfm
proprietary VMware vSphere API (Vi-
Vnfm), and
EMS 1 EMS 2 WMS Ve-Vnfm VNF
LRCVNF
Mgr Openstack Vi-Vnfm interface
Manager(s)
Manager(s)
(VNF Manager)
Or-Vi
VNF 1 VNF 2 RNC 1st VNF deployed to a Telco customer is
the virtual RNC
Vn-Nf
Vi-Vnfm
WCE (NFVI) WCE uses 3rd party Virtualized
Virtual Virtual Virtual
Infrastructure Manager(s):
Computing Storage Network
VM - VMwares vCenter (ESXi) / OpenStack
ESXi/KVM (Virtualization Layer) Nf-Vi VMware vCenter,
OpenStack NOVA,
(KVM)
Vl-Ha HP Sim, NetApp Compute / Switching - HP Sim
Santricity (VIMs)
Hardware resources Storage - NetApp Santricity
HP c7000 NetApp SAN HP 6125XLG
(Compute) (Storage) (Network)
WCE is NFVI providing a virtual computing,
storage and networking implemented with:
Execution reference points Other reference points Main NFV reference points
Compute 1 to 4 HP c7000 chassis /128
Xeon processors
Storage NetApp 5400 SAN with 24 x
600 GB drives
Network 2 to 8 HP 6125XLG
interconnected as a single, fully
9
duplicated layer 2 switch, multiple 10 &
COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.
40 G ports
Wireless Cloud Element Features
Multi-Tenancy ... server load is

uniform
Horizontal Scalability
Elastic Capacity
Reduced Power Usage

Dense Urban
Rural
Geographic Redundancy Sub-Urban
Zero Downtime Maintenance
As traffic shifts during the day ...

Wireless Cloud Element
3G 4G
ALU Provided
Wireless
Or
packet core Telco Provided

Computing Cloud
IP
Standard
Router
IP
IP
IP mobile
backhaul Centralized baseband
CPRI
IP IP
IP over fiber
Bringing NFV & vRAN to market Now Conventional

Metrocell
Macrocell RF only sites
BBU

From Controller to Radio Network Platform
One application
Multi - Tenancy Cloud architecture
Dedicated hardware
RNC RNC
SW
Virtualization
RNC
BSC RNC HW
RNC
Cloud in a box Cloud on a disk
Hardware independent scalable Software only solution can be

platform supporting multiple deployed in existing data center
tenants
Seamless capacity and scalability
Flexibility
From small single tenant to

large multi-tenant controller

The 9771 WIRELESS CLOUD ELEMENT
Elastic computing via

RNC RNC
virtualized servers
Virtualization
Common Servers
... server
load is
uniform
RNCa RNCb
VALUE WHY VIRTUALIZATION?
Shift from specialized Single asset

hardware to commodity Rural Dense Urban
Elastic capacity
HW (off the shelf) Sub-Urban
Scalability: Start small
Flexibility: any scale as necessary
Configuration, any HW,
anywhere Near Zero Outage during
S/W upgrade
Ability to host any
application Geo Redundancy
Operational simplification. Rapid application
Lower TCO deployment

The Advantages
Successfully operation with multiple tenants running on common platform:
Flexibility Up to 5 logical RNCs per WCE

Different applications: RNC, AAA, PCRF etc
Multi-shelf & Multi-Frame
Full horizontal scalability through role realignment
Scalability Increase of capacity through in service SW growth of roles

Flexible Reconfiguration:
In service re-allocation of processing between tenants grow and shrink
H/W No physical separation of applications. Leveraging resourcing where they are

available: cloud ready
Independence Full mix and match of HW blades, within the shelf. Leverage Intel tick-tock
First real time application, with full control and user plane virtualized
Innovation Full capacity with no latency or jitter issues

Shadow infrastructure
successful in-service SW Upgrades with less than 30 second service outage
5+X the Capacity of dedicated H/W with Unsurpassed Flexibility

Key Concepts of
Virtualization?
15
What is virtualization ?
Conventional dedicated physical resources
Physical resources
CPU Memory Storage Network

What is virtualization ?
A more efficient way to use the physical resources
Virtual
Guest Computer Guest Computer
machines
CPU Memory Storage Network CPU Memory Storage Network
Hypervisor Abstraction layer
Host

The Components of
the System
18
9771 Wireless Cloud Element overview
Multi-tenant RNC
The 9771 Wireless Cloud Element is

composed of 3 layers:
The Application layer hosting one or several
RNC tenants running on top of Virtualization
layer.
The Hardware platform composed of
NetApps and HP Hardware components
The Virtualization layer sharing the physical
resources (CPU, Storage, memory and
network resources) used by the virtual
machines

9771 WCE overview
Platform Hardware Elements
Wireless Management
Server Sun T5440 WCE Cloud Platform
HPTM and NetAppTM
OAM Network
Platform Management
Server DL380

9771 WCE overview
OAM of RNC and 9771 WCE platform

Presentation of the Platform
Management Server Hardware

Platform
Management
system
23
Access the WCE platform
Clients running in the platform management server
Platform Management Server
HP Systems Insight
vCenter server Manager
sql sql
SSH client
H C7000 enclosure H
P P
LRCMgr 3gOAM
O VM VM O
A A
1 ESXI 2
to switches through OA
HP BL460c
internal serial
HP 6125 G and 6125 XLG Switches

Ctrl A Ctrl B
NetApp Storage Array
9771 WCE Platform

DL380 G9
25
WCE Platform Management Server
Evolution
DL380 Gen9 Server with optional Security Bezel
DL380 Gen9 Server Faceplate

DL380 Gen9 Optional Insight Display on
WCE OAM Servers
DL380 Gen9 Server with Insight Display stowed away
DL380 Gen9 Server with Insight Display extended

WCE Gen9 OAM Servers
Rear view
DL380 Gen9 Server rear view, AC powered system
DL380 Gen9 Server rear view, DC powered system

WCE Gen9 OAM Server Disk Utilization

WCE Gen9
OAM Server Hardware Build Specification
3JR 52020AC (AC version) and 3JR 52021AC (DC version)
DL380 Gen 9 SFF OEM chassis
two Intel Xeon e5-2680v3 2.5GHz 12-core CPUs
eight 8GB PC4-14900 RDIMMs (four DIMMs per CPU, one DIMM
per memory channel)
four-port 331FLR Gigabit Ethernet network adapter
two 800W power supplies (available in either AC or DC variants)
P840 Smart Array RAID controller with 4GB Flash-backed Write
Cache
Two SFF disk cages and backplanes
six 300GB 15K RPM 12G SAS hard drives
six 1.2TB 10K RPM 12G SAS hard drives
one SATA DVD-RW optical drive

Connectivity
31
Local access to the Platform Management Server G9
Used before getting the OAM network remote access

DL380 G9
Ports connected to OAM network
ILO 1Gb Eth port 4 *1Gb Eth ports

(NIC)

Platform management server
Remote access to the Platform Management Server
Operation PC Platform management server
OAM Network
Operation Center Servers room

Presentation of the 9771 WCE Platform
Hardware

Hardware
components
36
9771 WCE platform
Hw configurations

9771 WCE platform
Cabinets content - front view
Primary cabinet Expansion cabinet
SAN
C7000 C7000
enclosure enclosure
2 4
C7000
C7000
enclosure
enclosure
1
3

9771 WCE platform
Cabinets content rear view
Primary cabinet Expansion cabinet
SAN
C7000 C7000
enclosure enclosure
2 4
C7000
C7000
enclosure
enclosure
1
3

9771 WCE platform
C7000 enclosure front view
Blade Blade
1 8
Blade Blade
9 16

9771 WCE platform
BL460c G8 Server blades
Up to 16 half-height BL460c G8 blades can

be plugged in at the front of the c7000
enclosure
The blades are equipped with 2 Intel Xeon

processors with 10 cores per CPU and 64
GB of RAM memory. The blade also uses a
dual 10G Ethernet port network module for
communication.

9771 WCE platform
C7000 enclosure primary n1 rear view (with 6125G
and 6125XLG switches)

9771 WCE platform
C7000 enclosure n 2,3,4 without 6125G

9771 WCE platform
On board Administrator (OA)
ILO port towards ILO port towards

6125G switch 6125G switch

9771 WCE platform
6125XLG switches
4 ports 40 GbE External ports 8 ports 10 GbE

(QSFP+) ports (SFP+) ports
The switch is also equipped with 20 internal ports (not visible on the face plate)
1 to 16 GE internal ports used to interconnect the switch to the BL460c blades
17 to 20 internal ports used as IRF physical ports to interconnect switches to each other

9771 WCE platform
6125XLG Switches Face plate ports assignment

9771 WCE platform
6125XLG Switches - Face plate ports assignment

Interface ID
How are named Ethernet ports in HP 6125 switches
Internal (downlink ports)
IRF Member ID / 0 / Port ID
External (uplink ports)
IRF Member ID / 1 / Port ID

9771 WCE platform
6125G OAM aggregation switches
SFP ports External ports 10/100/1000

Base ports
The switch is also endowed with 17 internal ports (no visible on the face plate)
16 GE internal unused ports
On IRF port (n17) used to interconnect the switches to each other

9771 WCE platform
6125G Switches face plate ports assignment

9771 WCE platform
NetApp e5400/e2700 Storage Array Network (SAN)
Front view
The NetApp e5400/e2700 SAN is a two-unit (2U) high controller drive tray.
One NetApp SAN is installed in each DC or AC Primary Cabinet.
It contains:
1 to 24 HDD ( 279 Gb usable capacity each)
2 controllers: Controller A and Controller B.
The NetAPP e5400 SAN is being replaced by e2700 due to NetApp e5400 SAN obsolescence.

9771 WCE platform
NetApp e5400 Storage Array Network (SAN)
Rear view

OAM Network
Connectivity
53
9771 WCE platform
6125G 6125 XLG OAM switches connectivity
6125XLG
6125G
Enc1 Enc2 Enc3 Enc4 SAN Enc1 Enc2 Enc3 Enc4 SAN
OA1 OA1 OA1 OA1 OA2 OA2 OA2 OA2
ILO ILO ILO Ctrl A ILO ILO ILO ILO Ctrl B
ILO
OAM network OAM network
Customers router Customers router

Transport
Network
External
Connectivity
55
9771 WCE Networking
Transport Network Connectivity - WCE 1 configuration
56
9771 WCE Networking
57
9771 WCE Networking
58
9771 WCE Networking
Transport Network Connectivity Slides from R&D Y. Brissette
WCE RNC Transport Connectivity for deployment
Oct, 2014
All Rights Reserved Alcatel-Lucent 2012.
59
HP intelligent Resilient Framework
and Multi-Chassis Link
Aggregations

IRF concepts
61
HP intelligent Resilient Framework (IRF)
IRF technology creates a large IRF fabric from
multiple devices to provide data center class
availability and scalability.
You can use LAGs to An IRF fabric appears
aggregate physical as one logical switch
links across the IRF and is accessible by
domain a single floating IP.
Simplified
Multi chassis topology and
LAG easy
management
1:N IRF Link

redundancy aggregation
One IRF member You can assign

works as the master several IRF physical
to manage and ports between
control the entire neighboring
fabric members

Principle
The figure shows an IRF fabric that has two devices, which appear as a
single logical switch node to the upper and lower layer devices

IRF Concepts
IRF topology
Ring topology is used in

WCE infrastructure to
interconnect and aggregate
2 or more switches to each
other.

IRF Concepts
IRF Fabric
One IRF fabric forms one IRF domain. IRF uses IRF domain IDs to uniquely identify IRF
fabrics and prevent IRF fabrics from interfering with one another.
IRF member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. This
member ID information is included as the first part of interface numbers and file paths to
uniquely identify interfaces and files in an IRF fabric. If two devices have the same IRF
member ID, they cannot form an IRF fabric.
IRF member roles

IRF uses two member roles: master and standby (called "subordinate).When devices form
an IRF fabric, they elect a master to manage and control the IRF fabric, and all the other
devices back up the master. When the master device fails, the other devices automatically
elect a new master.
Master election
The IRF fabric is formed on election on the master. There is an election of the Master each
time the IRF topology changes

IRF Concepts
Member priority
Member priority determines the possibility of a member device to be elected the
master. A member with higher priority is more likely to be elected the master. The default
member priority is 1. You can change the member priority of a member device to affect the
master election result.
Configuration synchronization mechanism

IRF uses a strict running-configuration synchronization mechanism so all chassis in an
IRF fabric can work as a single node, and after the master fails, other members can operate
correctly. In an IRF fabric, all chassis get and run the running configuration of the master. Any
configuration you have made is propagated to all members.

IRF Concepts
IRF port
An IRF port is a logical interface for the connection between IRF member devices. Every
IRF-capable device supports two IRF ports. The IRF logical ports are named: IRF-port
MemberID/1 and IRF-port MemberID/2.
To use an IRF port, you must bind at least one physical port to it. The physical ports
assigned to an IRF port automatically form an aggregate IRF link. An IRF port goes down
only if all its physical IRF ports are down.
Physical IRF port

Physical IRF ports connect IRF member devices and must be bound to an IRF port. They
forward the IRF protocol packets between IRF member devices and the data packets that
must travel across IRF member devices. When you connect 2 neighboring IRF members,
connect the physical ports of IRF port 1 on one member to the physical ports of IRF port 2
on the other as shown in the following figure
IRF ports of the 6125 XLG
and 6125G switches
are customized in factory

MAD Concepts
IRF multi-active detection (MAD)
An IRF link failure causes an IRF fabric to split in two IRF fabrics operating
with the same Layer 3 configurations, including the same IP address. To
avoid IP address collision and network problems, IRF uses multi-active
detection (MAD) mechanisms to detect the presence of multiple identical
IRF fabrics, handle collisions, and recover from faults.
The multi-active handling procedure includes detection, collision handling,
and failure recovery.
ARP MAD is configured in factory in 6125 switches

WCE platform
IRF domains
69
6125 XLG IRF Domain
All 6125 XLG switches are regrouped in a unique IRF domain
o6125XLG IRF domain ID = 1
oIRF member ID = 1,2,3,,8 with the following priorities:
irf member 1 priority 10
irf member 3 priority 6 IRF domain ID , member ID and
irf member 4 priority 5 priorities of the switches are
irf member 5 priority 4 customized in factory

6125 G IRF Domain
The pair of 6125G switches are regrouped in a unique IRF domain
oIRF domain ID = 1
oIRF member ID = 1,2 with the following priorities
IRF domain ID , member ID and
priorities of the switches are
customized in factory

WCE platform
IRF physical
ports
72
IRF&MAD 6125 XLG topology
Configuration WCE1 with one C7000 enclosure

IRF&MAD 6125 XLG topology
Configuration WC4 with 4 C7000 enclosures

IRF&MAD 6125 G topology
IRF port
MAD port

HP Switch Ethernet ports and LAGs

Types of HP
Switches
Ethernet Ports
77
Port link types
Port Properties Use

type
Access* Belongs to only one VLAN and sends Usually used to connect a
packets untagged. terminal device unable to
The PVID is the VLAN to which the recognize VLAN tagged packets
access port belongs to. or when there is no need to
segregate the flows per VLAN
Trunk Can carry multiple VLANs to received Usually, ports connecting
and send packets for them. network devices are configured
Packets sent through trunk ports are as trunk ports
VLAN tagged (except PVID tagged
frames)
Hybrid* Allows traffic of some VLANs to pass Hybrid ports can connect
through untagged and traffic of some network devices or terminal
other VLANs to pass through tagged. devices
* Used in 6125XLG/G switches in WCE platform

How ports of different link types handle
frames
Action Access Trunk Hybrid
In the inbound Tags the frame with the
direction for an PVID tag
untagged frame If the PVID is permitted, tags the frame with the PVID tag
If not, drops the frame
P Switch
P
In the inbound Receives the frame if the Receives the frame if its VLAN is permitted on the port
direction for a VLAN Id is the same as Drops the frame if its VLAN is not permitted on the port
tagged frame the PVID
Drops the frame it its
VLAN Id is different from
P Switch the PVID
P
In the outbound Removes the VLAN tag Removes the tag and sends the frame if Sends the frame if its VLAN is
direction and sends the frame the frame carries the PVID tag and if the permitted on the port.
port belongs to the PVID The frame is sent with the
P Sends the frame without removing the VLAN tag removed or intact
Switch tag if its VLAN is carried on the port but depending on the
is different to the PVID configuration set by t he
command port hybrid vlan
P Nokia INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION
(tagged or untagged)
Link
Aggregations
80
Link aggregations benefits
Ethernet link aggregation bundles multiple physical Ethernet

links into one logical link, called an aggregate link
Link aggregation delivers the following benefits
Increases bandwidth beyond the limits of any single link. In an aggregate link,
traffic is distributed across the member ports.
Improves link reliability. The member ports dynamically back up one another.
When a member port fails, its traffic is automatically switched to other member
ports.
Deletes switch topological loops (by the use of Multi-chassis LAG)
81
Link aggregations principle
S
1 1
S
2 2
System 1
System 2
S
3 3
U
4 4
S
5 5
LACP System Priority high LACP System Priority low
Local Partner (remote)
Sends the port status in
dynamic mode
Mode = Dynamic
Lacp period = 3 sec Legend:
Min Number of selected port = 3 S: Selected
Max number of selected port = 4 U : Unselected
82
failure
U
1 1
S
2 2
System 1
System 2
S
3 3
U S
4 4
S
5 5
LACP System Priority high LACP System Priority low
dynamic mode
Mode = Dynamic
83
failure
U
1 1
failure
U
2 2
System 1
System 2
S
3 3
S
4 4
S
5 5
LACP System Priority high
The LAG is still UP LACP System Priority low
dynamic mode
Mode = Dynamic
84
failure
U
1 1
failure
U
2 2
System 1
System 2
U failure
3 3
S => U
4 4
S => U
5 5
LACP System Priority high
LAG is DOWN LACP System Priority low
Mode = Dynamic
85
Transport Network Connectivity
The link aggregation parameters in the 6125 XLG switches
86
Platform and vRNC IP subnets

Platform
internal subnets
88
9771 WCE Networking
Platform internal subnets Components layers: Platform layer RNC layer
CMU UMU PC LMU
VM VM VM VM
RNC internal subnet VLAN 3002,3003,etc
DA 0 VM DA VM internal subnet= DA 1 VM LRC Mgr 3gOAM

169.254.0.0/30 - VLAN 3001
.1 .2 VM VM
initiator initiator
DA Floating IP
169.254.221.254
.10 .11 .1 LRCMgr internal subnet = 169.254.220.0 /23 VLAN 3000
.2 .4 .5 I-SCSI subnet= 169.254.223.0/24 - VLAN 4094

.250 .3 .251
Blade Blade Blade

Ctrl A1 Ctrl A2 Ctrl B1 Ctrl B2
target target target target initiator initiator initiator
SAN C7000

9771 WCE Networking
Platform internal subnets and IP addresses
I SCSI subnet
Target I-SCSI IPs hosted in SAN Controllers A/B : <I-SCSI port [A| B] [1| 2] IP>
Initiator I-SCSI IPs hosted in BL460c : <Enc[X]_blade [N ]_Port[1| 2]_ISCSI_IP>
Initiator I-SCSI IPs hosted in DA 0 and DA1 VMs: <DA-[0| 1] I-SCSI IP>
DA VM internal subnet
<Inter_DA0_IP>
<Inter_DA1_IP>
LRCMgr internal subnet

<LR CM gr_VM _internal_IP>
3gOAM internal IP * N (N is the num ber of 3gOAM VM )
<Floating _DA_IP_address>
<DA0_internal_IP>
<DA1_internal_IP>
RNC internal subnet

IPs addresses schem e depend on the num ber of R NC created.

OAM IP
subnets
91
Example - OAM Subnets&IP - LR14
92
Telecom IP
subnets
93
9771 WCE overview
Interfaces of the 9771 RNC

9771 WCE Networking
Virtual machines and external interfaces

9771 WCE Networking
Traffic subnet size rules (LR14.2)
Interface Subnet Size Subnet Mask Number Reserved Comments
of IP@ IP@
IuCS Cplane /28 255.255.255.240 13 16
Can be configured as one subnet for all
IuPs Cplane /28 13 16 3 interfaces or one subnet for each
IuR Cplane /28 13 16 interface.
OR Maximum Number of CMUs is 13; with
1 NI IP@ per CMU instance.
Iu Cplane /28 13 16
IuCS Uplane /26, 255.255.255.192, 60, 64,
IuPS Uplane /27, 255.255.255.224, 28, 32, Maximum number of PC is 30; with 2
/28 255.255.255.240 12, 16 IP@ per PC instance.
IuR Uplane
Similar to Cplane; the Uplane
OR terminations can also be shared.
Iu Uplane /26, /27, /28 60, 28, 12 64, 32, 16
Iub Cplane /26, 255.255.255.192, 39, 64,
Iub CC Uplane /27 255.255.255.224 27 32
Maximum Number of CMUs is 13; with
OR 3 Iub IP@ per CMU instance.
Iub Cplane + Iub CC /26, /27 39, 26 64, 32
Uplane
Iub Uplane /26, 255.255.255.192, 60, 64, Maximum Number of PC is 30; with 2
/27, 225.255.255.224, 28, 32, IP@ per PC instance.
/28 255.255.255.240 12 16
IuPC
96 /29 255.255.255.248 5 96 8
Can be its own subnet or can reuse one
Nokia INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION of the Iu Cplane subnets.
Platform VLANs

OAM Flows
tagged on
Customers
Network
98
OAM port groups
OAM flows tagged on customers network
LRCMgr VM ESXI kernel RNC 3gOAM VM
OAM -ESXI Mgt port group RNC OAM port group

(ESXI Mgt VLAN = LRCMgr Ext VLAN) (3gOAM External VLAN) vDS port groups
4093
Internal ports: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Internal ports: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Enc1 Enc2 Enc3 Enc4 SAN Enc1 Enc2 Enc3 Enc4 SAN
OA1 OA1 OA1 OA1 Ctrl A OA2 OA2 OA2 OA2 Ctrl B
untagged
ESXI Mgt VLAN

OAM network OAM network
LRCMgr Ext VLAN
3gOAM Ext. VLAN

VLANs in switches OAM flows tagged in customers network
6125XLG 1 (H) 2 (H) Internal ports 16 (H)
4093;4094;3000;3001;3002 to 3007 ; RNC OAM VLAN ; traffic VLAN [x] tagged

PVID = 4093
Traffic VLAN [x] 3000 3001 3002 3004 3006 4094 4093 RNC 1 OAM VLAN
x = 0,1,2,3,4,5,6,7,8 RNC 2 OAM VLAN
3003 3005 3007
RNC 3 OAM VLAN
2
RNC1 RNC2 RNC3

1(A) 2(A) 3(A) 5 (H) 6 (H) 9 (A) 10 (A) 11 (H)
2 untagged 2 untagged Traffic vlan[x] tagged 4094 untagged 4093; RNC OAM VLAN tagged
ARP MAD to IRF to ARP MAD to Traffic Lag X SAN A SAN B

Lag 128
6125 XLG 6125 XLG 6125 XLG I SCSI I SCSI
4093; RNC OAM VLAN tagged
6 (H)
Router
Traffic 6125G
RNC 1 OAM VLAN
Legend 4093 RNC 2 OAM VLAN
ESXi Mgt VLAN 3 RNC RNC 3 OAM VLAN
3gOAM External VLAN 2
LRCEMgr external
VLAN 3 RNC-internal
VLANs
Hw Mgt VLAN 1 (A) 2 (A) 3 (A) 4 (A) 5 (A) 7(A) 8 (H)
MAD VLAN
4093 untagged 2 untagged 4093; RNC OAM VLAN tagged
I-SCSI TRAFFIC VLAN 4093 untagged
Traffic VLAN
LRCMgr internal VLAN OA Mgt OA Mgt OA Mgt OA Mgt SAN A/B Mate 6125G
enc1 enc2 enc3 enc4 Controller Mgt port7 (MAD)
Disk Access internal OAM network
(H) Hybrid port tenant VLAN Router
(A) Access port
100
vCenter configuration of 9771
WCE RNC
Consult VMware 5.5 documentation center web site:
http://pubs.vmware.com/vsphere-55/index.jsp?lang=en

vSphere client and vCenter server
vSphere Client
Platform
management
server
vCenter server
Virtual
VM VM VM VM VM VM machines
ESXI hosts
Storage

ESXI &Virtual Machines
Overview
103
Overview of the virtualization concepts
ESXI architecture
VMware ESXi is an operating system-independent hypervisor based on

the VMkernel operating system interfacing with agents that run atop it.
ESXi is the exclusive hypervisor for VMware vSphere 5.x licenses.

Virtual machine
What is a Virtual machine?
A virtual machine is a software computer that, like a physical computer, runs an operating system and
applications. The virtual machine consists of a set of specification and configuration files and is backed by
the physical resources of a host. Every virtual machine has virtual devices that provide the same
functionality as physical hardware are more portable, more secure and easier to manage.

Virtual machine files
Each virtual machine is a

set of files stored in a data
store in the VM directory
See the following link to get more details on the files of the VMs

File name Short name Description
VM_Name.vmx Configuration This file contains all of the configuration information
file and hardware settings of the virtual machine
VM_Name.vmtx Template file This file is the configuration file of a template of
virtual machine
VM_Name.nvram BIOS file This small file contains the BIOS that is used when
the VM boots
VM_Name.vmdk Disk descriptor The descriptor file also contains a pointer to the
file large data file as well as information on the virtual
disks drive sectors, heads, cylinders and disk adapter
type
VM_Name-flat.vmdk Disk data file Large data file containing the data used by the VM
VM_Name--rdm.vmdk Raw device This is the mapping file for the raw device mapping
map file format that manages mapping data for the RDM
device.
VM_Name-delta .vmdk Snapshot disk These virtual disk data files are only used when
file making snapshots. Changes to the virtual disk are
written in these delta files instead of begin stored in
107
the original flat file
File name Short name Description
Vmware-#.log (where Log Files LOG files are created to log information
# is a number starting about the virtual machine and are often
with 1) used for troubleshooting purposes
VM_Name.vswp Swap memory file When you power on a VM, a memory swap
file is created that can be used in lieu of
physical host memory if an ESX host
exhausts all of its physical memory
VM_Name.vmss Suspend state file This file is used when virtual machines are
suspended and is used to preserve the
memory contents of the VM so it can start
up again where it left off
VM_Name.vmsd Snapshot data file This file is used with snapshots to store
metadata and other information about each
snapshot that is active on a VM
VM_Name.vmsn Snapshot state file This file is used with snapshots to store the
state of a virtual machine when a snapshot
is taken

Virtual machine templates
A template is a master copy of a virtual

machine.
It is used to create and provision new virtual
machine. We call this operation: Deploy a VM
from a template.
The template is an image which includes the
guest operating system, as set of applications
and specific virtual machine configuration.
Virtual machine can be changed into
templates without the need to make a full
copy of the virtual machine files.

Clusters -
High Availability-
Distributed Resource
Scheduler
Overview
110
Cluster of ESXI hosts
111
Using Clusters
112
Clusters of Hosts
113
How find the host capacity
Note: The example given here is not a blade used for commercial deployment of 9771 WCE RNC
114
How High Availability work
vSphere HA provides high availability for virtual machines by

pooling the virtual machines and the hosts they reside on into
a cluster. Hosts in the cluster are monitored and in the event
of a failure, the virtual machines on a failed host are restarted
on alternate hosts.
When you create a vSphere HA cluster, a single host is
automatically elected as the master host. The master host
communicates with vCenter Server and monitors the state of
all protected virtual machines and of the slave hosts. Different
types of host failures are possible, and the master host must
detect and appropriately deal with the failure.

Where find the HA state of a host

Cluster status
Hosts connected to Protected VMs Data store used for heart

master beating

Cluster configuration issues
Re-initialize the master /slave

configuration

How Distributed Resource Scheduler (DRS) works
A DRS Distributed Resource Scheduler is managed by

VMware vCenter and has this resource management
capabilities:
Initial placement
Load balancing
Power management (unused in 9771 WCE)

Host to VM Map

Configuration of
clusters in 9771
WCE
121
Dimension clusters in a 9771 WCE RNC
When configuring the clusters of ESXI hosts on site, we need to respect
some recommendations and rules:
Each cluster contains a maximum of 32 ESXI hosts*
Each vRNC is hosted in a cluster => each vRNC cannot be hosted in more
than 32 blades.
LRCMgr VM and Disk Access VMs are in the same cluster
(recommendation)
If more than one cluster exist and if we have several vRNC to configure,
we pile up the vRNC in clusters in accordance with the number of blades
per cluster and the number of VMs per vRNC.
* VMWare version V5.5 and lower

Inventory Hosts and Clusters
123
Clusters of Hosts in 9771 WCE
HA and DRS enabled
124
High Availability configuration
Enable host monitoring to allow

hosts in the cluster to exchange
network heartbeats and to allow
vSphere HA to take action when it
detects failures.
Disable: Allow VM power on

operations that violate
availability constraints means that
no admission control is performed to
accept/reject a migration of VM due to
a failure
Admission Control Policy helps

ensure sufficient resources to provide
HA. It Refers to the amount of
available resources that can be used
to start VM on the ESXI host
125
The VM restart priority determines
the order in which virtual machines
are restarted when the host fails.
Higher priority virtual machines are
started first. This priority applies only
on a per-host basis. If multiple hosts
fail, all virtual machines are migrated
from the first host in order of priority,
then all virtual machines from the
second host in order of priority, and so
on.
The Host isolation response

determines what happens to VMs
when a host loses the management
network (ESXI VM kernel port) but
continues running
126
Failure interval
The interval (in seconds) after which a

failure is declared if no heartbeats were
received from the virtual machine.
Minimum uptime
The time (in seconds) after the virtual

machine starts up before the failure
interval is enforced. No heartbeats are The VM monitoring
monitored during this time
sensitivity defines how
Maximum per VM reset quickly the failures are
detected
The number of times the virtual
machine can be reset after a failure.
Maximum resets time window
The time (in hours) in which the

Maximum per-VM resets setting is
enforced.
127
128
Distributed Resource Scheduler configuration
Partially automated
When you power on a VM, DRS
places it on the best-suited host.
When the cluster becomes
unbalanced, DRS displays
recommendations for virtual
machine migration but doesnt
trigger any migration automatically
129
130
The VMware DRS system (in semi-automatic mode) will distribute these
VMs to physical servers following the VM to VM anti-affinity rules that we
define. These rules are:
no more than one 3gOAM can reside on a single ESXI host,
no more than one CMU can reside on a single ESXI host,
no more than one PC can reside on a single ESXI host,
a 3gOAM and a CMU cannot reside on the same ESXI host.

132
133
The Resource
pools of the
platform
134
Resource pool

Resource pool
Resource pools allow you to delegate control of host resources, but the
benefits are especially evident when resource pools are used to
compartmentalize all resources in a cluster. You can create multiple
resource pools as direct children of the host or cluster and configure
them, and delegate their control to other individuals or organizations.
You can create a child resource pool of any host, resource pool, or DRS
cluster. When you create a child resource pool, you are prompted for
resource pool attribute information. The managing server analyzes the
resources that are allocated to the parent and the siblings (resource pools
or virtual machines) and uses admission control to prevent you from
allocating unavailable resources to the resource pool.

The resource pools in the WCE
oOne DA resource pool
oOne resource pool per vRNC

Disk Access resource pool
Resource pool Name :

DiskAccess<NodeId>
The resource pool
contains a vApp which
correspond to a tenant
with 2 Disk Access VMs
138
RNC resource pool RNC resource pool
Service providing
Resource pool Name : RNC tenant instance
RNC<RNC_ID>
The service providing RNC tenant
instance is a vApp containing all RNC
VMs : 3gOAM,CMUs,UMUs, PCs
The shadow RNC tenant instance
exists only when using the shadow
mechanisms ( Critical DB change, Sw
upgrade..) contains the same VMs
139
RNC resource pool
Reserved memory
RNC resource pool reserved memory (MByte)=
Nb_3gOAM*6000+Nb_CMU*6656+Nb_PC*6144+Nb_UMU*6656
Reserved CPU
RNC resource pool reserved CPU (Mhz) = Nb_3gOAM*2*2799 + Nb_CMU*4*2799 +
Nb_UMU*4*2799+ Nb_PC*4*2799 + Nb_LMU* 4*2799
Nb_3OAM = 2
Nb_LMU = 1
140
The vApps
141
What is a vApp?
A vApp is a group of virtual machines that can be managed as a single

object.
vApp simplify management of complex applications that run on multiple
inter-dependant virtual machines
Vapp have the same basic operations as virtual machines: Power on /
power off

The vApps in 9771 WCE RNC
Disk Access vApp
RNC vApp

The virtual
machines of
the platform
144
9771 WCE RNC
ESXI architecture
In the ESXI architecture the applications running in virtual machines access CPU, memory, disk and network interfaces
without direct access to the underlying hardware. The ESXI hypervisor is called the VM Kernel. The VM kernel receives
requests from the virtual machine monitor (VMM) and presents the requests to the physical hardware. The VMM presents
the virtual hardware to the virtual machine and receiving the requests.
Note: LMU VM (LR15.3) is not represented in this figure

9771 WCE virtual resources
The virtual machines installed in the 9771 WCE
Component Application /VM Brief description
Platform LRC Manager LRCMgr VM has interfaces with the WMS, with the
vCenter server and also with the tenants. It
provides services of VM and tenant managements
Platform Disk Access Provides NFS Access to RNC VM
RNC UMU Provides the entire control and user plane
UE Management Unit processing for individual UEs.
RNC CMU Maintains UMTS cells, acts as the SS7 termination
Cell Management Unit point and provides a proxy to the platform for
transport resource management.
RNC PC Provides both UDP and GTP-U NAT points and
Protocol Converter transport bandwidth management for Wireless
Cloud Element applications.
RNC 3gOAM The 3gOAM role acts as the termination point for
Operation and Maintenance of the RNC.
RNC LMU Log Management Unit. This VM gathers the Logs

from the RNC VMs and make them available in a
146
web server which is consultable with a browser.
The Virtual
Distributed
Switch
147
Networking
A virtual machine can be

configured with one or more
virtual Ethernet adapters each
of which has its own IP address
and MAC address.
Virtual
As a result the VM have the Distributed
same properties as physical Switch
machines from a network
standpoint.
Virtual distributed switches
allow virtual machines to
communicate to one another
inside the same server or
across multiple ESX hosts.

vDS Virtual Distributed switch principle
BL460c board 1 BL460c board 2
VM A VM B
Vm kernel Vm kernel
vmk0 vNIC vNIC vmk0

Virtual Distributed Switch
port group 1 (VLAN ID= 4093)
vmnic0 vmnic1 vmnic0 vmnic1
NIC adapter 1 NIC adapter 2 NIC adapter 1 NIC adapter 2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
6125 XLG Left 6125 XLG Right

vDS Virtual Distributed switch port groups (1 RNC)
vRNC Platform
3gOAM LMU VM
PC UMU CMU DA LrcMgr
kernel
vNIC vNIC vmk0

vNIC vNIC vNIC vNIC vNIC vNIC vNIC vmk0
Internal RNC 1-1 3002 LRCMgr internal 3000 i-SCSI traffic 4094 Inter-DA 3001 OAM-ESXI 4093
3GOAM Ext
Internal RNC 1-2 3003
Iub UP IubCC UP Iur UP IuPS UP IuCS UP Iub CP Iur CP IuPS CP IuCS CP
User plane Control plane

vmnic0 vmnic1
116
C7000 enclosure
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
6125 XLG Left 6125 XLG Right

9771 WCE Networking
VLAN tagging and configuration

9771 WCE Networking
Vmware Virtual Distributed Switch
One unique vDS per WCE platform
Named : <Platform Name>_vDS

9771 WCE Networking
Vmware Virtual Distributed Switch
Platform port groups VMs and VLAN
Parameter Description Connected VLAN
VMs (system
constant)
<ESXi m anagem ent access This is the ESXI Mgt port group. The LRCMgr 4093
port group> LRC Mgr VM is attached to this port
OAM_ESXI_Mgt-LRC_ _ _ group as well as the VM Kernel through
the VM kernel ports.
<LR CM gr m anagem ent port This port group is automatically created Disk Access 3000
group> when deploying the LRCMgr. It allows 3gOAM
LRC_ _ _ _LRCEMgr the LRCMgr to communicate to the LRCMgr
3gOAM and the DA VMs
<Disk Access internal tenant This port group is used by DA VMs to Disk Access 3001
port group> communicate to each other. This port
LRC_ _ _ _DiskAccess_ _ _ - group is automatically created while
1_TenantInternal deploying the DA VMs
<Disk Access I SCSI traffic Name of the port group used by each Disk Access 4094
port group> DA VM to carry i-SCSI traffic to the SAN
LRC_ _ _ _DiskAccess_ _ _ - and blades
1_ISCSI_TRAFFIC

9771 WCE Networking
RNC platform port groups VMS and VLAN
Parameter Description Connected VLAN
VM (system
constant)
<3gOAM Ex ternal VLAN> VLAN tag used by the 3gOAM VMs to UMU 4093 (OAM
RNC<RNC ID>-1|2-PG-VLAN_ _ _ communicate to the WMS. CMU untagged)
3gOAM Customer
value
(tagged)
<R NC-1- internal VLAN> VLAN tagging the internal flows UMU 3002
RNC<RNC ID>-1|2-PG-VLAN_ _ _ between the 3GOAM VMs and all CMU
other VMs (PC, UMU, CMU) for the
first service providing instance 1 3gOAM
PC
<R NC-2- internal VLAN> VLAN tagging the internal flows UMU 3003
RNC<RNC ID>-1|2-PG-VLAN_ _ _ between the 3GOAM VMs and all CMU
other VMs (PC, UMU, CMU) for the
instance 2 3gOAM
PC

9771 WCE Networking
RNC port groups carrying telecom traffic VMS and VLAN
Parameter Description Connected Port group
VM
<Iub_CP VLAN> Telecom - Iub Control plan flow 3gOAM RNC<RNC ID>-1|2-PG-VLAN_ _ _
CMU
<Iub_UP VLAN> Telecom - Iub User plan flow PC RNC<RNC ID>-1|2-PG-VLAN_ _ _
<IuPS_CP VLAN> Telecom - IuPS Control plan flow CMU RNC<RNC ID>-1|2-PG-VLAN_ _ _
<IuPS_UP VLAN> Telecom - IuPS User plan flow PC RNC<RNC ID>-1|2-PG-VLAN_ _ _
<Iur_CP VLAN> Telecom - Iur Control plan flow CMU RNC<RNC ID>-1|2-PG-VLAN_ _ _
<Iur_UP VLAN> Telecom - Iur User plan flow PC RNC<RNC ID>-1|2-PG-VLAN_ _ _
<IuCS_CP VLAN> Telecom - IuCS Control Plan flow CMU RNC<RNC ID>-1|2-PG-VLAN_ _ _
<IuCS_UP VLAN> Telecom - IuCS User plan flow CMU RNC<RNC ID>-1|2-PG-VLAN_ _ _
<IuB_CC_UP VLAN> Telecom - IuB User plane CMU RNC<RNC ID>-1|2-PG-VLAN_ _ _

Cell Common Channel flow

The Storage
concepts
156
Storage - VMFS
VMFS leverages shared

storage to allow multiple
VMware vSphere hosts to
read and write to the same
storage concurrently.

The datastores

iSCSI components

Storage Architecture
Virtual machines use virtual disks for their
operating system, application software, and other
data files. A virtual disk is stored as a VMDK file
on a datastore. The virtual disk hides the physical
storage layer from the virtual machines operating
system. Regardless of the type of storage device
that your host uses, the virtual disk always
appears to the virtual machine as a local SCSI
device. As a result, you can run operating
systems that are not certified for specific storage
equipment, such as SAN, in the virtual machine.
When a virtual machine communicates with its
virtual disk stored on a datastore, it issues SCSI
commands. Because datastores can exist on
different types of physical storage, these
commands are encapsulated into other forms,
depending on the protocol that the ESX/ESXi host
uses to connect to the physical storage device.
See more at :
http://pubs.vmware.com/vsphere-
55/index.jsp?topic=%2Fcom.vmware.wssdk.pg.d
oc%2FPG_Storage.10.3.html

Storage Data Stores
A data Store represents a storage location for virtual machine files. A storage location
can be a VMFS volume, a directory on Network Attached Storage, or a local file
system path. A data store is platform-independent and host-independent. Therefore,
data stores do not change when the virtual machines they contain are moved
between hosts. The scope of a data store is a datacenter; the data store is uniquely
named within the datacenter.
Any reference to a virtual machine or file accessed by any host within the datacenter
must use a data store path. A data store path has the form "[<datastore>] <path>",
where <datastore> is the data store name, and <path> is a slash-delimited path
from the root of the datastore. An example data store path is "[storage]
path/to/config.vmx".

Storage Data Stores
When a client creates a virtual machine, it may specify the name of the data store,
omitting the path; the system, meaning Virtual Center or the host, automatically assigns
filenames and creates directories on the given data store. For example, specifying My
Data store as a location for a virtual machine called MyVm results in a data store
location of My Datastore\MyVm\MyVm.vmx.
Data stores are configured per host. As part of host configuration, Multiple hosts may
be configured to point to the same storage location.
Thus, managing data store is done both at the host level and the datacenter level. Each
host is configured explicitly with the set of data stores it can access. At the datacenter,
a view of the data store across the data center is shown.
See more at: link
https://www.vmware.com/support/developer/vcsdk/visdk2xpubs/ReferenceGuide/vim.D
atastore.html

Summary of the main concepts
See the following site to get a summary of the different concepts:
http://www.doxer.org/vmware-vsphere-esx-cloud-computing-terminology/

Data Stores in
VCenter
164
Data Stores declared in the vCenter
DS1
Ds1 is connected to LUN 101 through target SAN controller i-scsi ports
AllVM files and templates of VMs are stored in DS1
vSwp
vSwp is connected to LUN 100 through target SAN controller i-scsi port
The vSwp volume is only used if necessary for showdown upgrade in case
the swap memory fills up it will then overflow to this volume. This was a
recommendation from VMware that we create this volume in case swap
memory fills up.
Storage configuration
Mapping of Data Stores to Hosts

Data Store properties
Access to multi-
Partition
pathing
configuration

Data Stores DS1 connection to LUN 101 through I-SCSI
target nodes with load balancing across the paths
Round-Robin Algorithm used to

share the load across the paths
4 i-scsi target nodes iqn
Initiator i-scsi node iqn

Disk files of
VMs
169
Virtual Disks of VMs
VM Virtual disk files Type
LRCEMgrDataAndLogsV2.vmdk (persistent)
LrcMgr
LRCMgr.vmdk
LRC001-DiskAccess001-1-DA-0 LRC001-DiskAccess001-1-DA-0_1.vmdk
LRC001-DiskAccess001-1-DA-0_2.vmdk Thick
LRC001-DiskAccess001-1-DA-1 LRC001-DiskAccess001-1-DA-1_1.vmdk provisioned
LRC001-DiskAccess001-1-DA-1_2.vmdk eager zeroed
3gOAM-0 3gOAM-0.vmdk
3gOAM-1 3gOAM-1.vmdk
LMU (Log Management Unit) LMUDisk.vmdk (100 GB)
CMU,PC,UMU Not applicable Not applicable

Storage Array Network Configuration

i-scsi initiators
and targets
172
I-SCSI Hosts declared in the SAN
DA 0 VM DA 1 VM
I scsi initiator I scsi initiator
.2 .4 .5 I-SCSI subnet= 169.254.223.0/2 4 - VLAN 4094 .1

.250 .3 .251
Blade Blade Blade

Ctrl A1 Ctrl A2 Ctrl B1 Ctrl B2
target target target target initiator initiator initiator
SAN C7000
I SCSI hosts declared in SAN

Definition of Host in SAN :
A computer that is attached to a storage array. A host accesses volumes assigned to it on the storage array.
The access is through the target i-SCSI host ports on the storage array.

Hosts and
Volumes in SAN
174
I-SCSI Hosts declared in the SAN
Hosts are regrouped in Host groups in the

configuration tab called Host Mapping
WCEx_Host group contains the

BL460 I scsi initiator hosts (1 per
blade). This Host group is created in
factory
The DA_Hostgroup is filled during

the platform commissioning. It
contains the 2 initiator DA I scsi
hosts

The volumes declared in SAN
Disk Access IO Fence volume. 3 per WCE platform.

LUN = 11,12,13
DataStore 1 volume. One per WCE platform. Attached to the

VMware DataStore DS1. LUN = 101
LRCMgr Software volume. One per WCE platform. LUN = 10
RNC Sw volume. One per RNC tenant.
vSwap volume. One per WCE platform. LUN = 100. vSwp Datastore is
attached to it. This volume is configured with thin provisioning
Boot volume. One for each initiator blade. LUN = 1
Definition of volume in SAN :

The logical component created for the host to access storage on the storage array. A volume is created from the capacity
available on a disk pool or a volume group. Although a volume might consist of more than one drive, a volume appears as
one logical component to the host. Each volume is identified by a Logical Unit Number (LUN).

Host mapping to volumes in the SAN
DA Hosts Volumes accessed by DA

group i-scsi nodes
WCE Hosts
group
Volumes accessed by
blade i-scsi nodes

I SCSI
configuration
178
Configuration of i-SCSI host ports

Target nodes i-SCSI ports
I scsi port 1 of the

Controller A
IP address target
iscsi node

I-SCSI Setting

I-SCSI Setting
Target configuration Remote initiator configuration

Out-of-band management IP address

Out-of-band management IP address

Platform Alarms monitoring

HP devices monitoring
SNMP Manager SNMP Agents
On Board Administrators
Platform management
server
HP 6125G & XLG switches
BL460c

HP devices monitoring
Platform management server
SNMP Manager
Received
SNMP traps

Storage Array Network monitoring

Vmware monitoring

Software & License Inventories

Inventories
Tools installed in Platform Management Server
Name Use
freeFTPd SFTP Client / Server
Putty SSH Client
Client connected the
vSphere Desktop client
vCenter Server
Client used to manage
NetApp Santricity client
the Storage Array
Network

Inventories
Platform Software licenses
License Description Vendor License Keys Instructions
vCenter license License used when you VMware License key: The product key is
install the vCenter Server in received by R&D and
the platform management shipped to the Site TPM
server (out of the scope of
this IEH)
Mandatory
vSphere license This license is given for a VMware License key: The product key is
ESXI specific number of CPU. received by R&D and
Each blade contains 2 CPU. shipped to the Site TPM
The license key is
provisioned in the section
302 procedure install
vSphere License
Mandatory
HP insight This license is necessary to HP License key: The key can be retrieved
Manager get HP support access for once you registered to
HP SIM HP Passport.
Optional
NetApp thin Necessary to create thin NetApps Feature Retrieve an NetApps
provisioning provisioning swap volume in Activation Code originating envelop on
the SAN. The thin Feature site where the Feature
provisioning license key file Enable Activation Code is
is entered in the system in Identifier mentioned together with
the section 302 in the instructions how to
procedure Customize the Chassis retrieve the Feature
array serial number Enable Identifier (32
Mandatory => characters ID) and the
Key File final Key File
HP iLO This license key is HP EON: An envelope is received

Advanced 1 - provisioned during the on site inside which is
Srv incl 1yr installation of the platform written the Entitlement
TS&U management server (out of Order Number (EON)
the scope of this IEH) Read the HP instructions
Mandatory License key: in the envelope to get the
ILO license key

Inventories
Platform Software licenses
License Description Vendor License Keys Instructions

SQL server License used when you install Microsoft License key: License arrives together with the platform management
the SQL DB in the platform server
management server
Mandatory
Microsoft server Microsoft server OS license Microsoft License key: License arrive together with the platform management
OS license server
Mandatory

Customer Information Questionnaire
(CIQ)

Customer Input Questionnaire
Introduction
Purpose
Gather in a single file all parameters necessary to make the work orders, to
perform the installation of the platform and RNC
Providers
Domain architects in service teams
Users
Field engineers, TPM and PM in service teams

Classification of parameters
Platform WPS
Attributes Attributes
WCE Platform
WCE Platform
Management RNC Node B
Platform RNC
Server
Provisioned in the platform during the platform Provisioned in the WMS Database during
commissioning and RNC tenant installation. RNC and Node B integration
Means used to provision the parameters: vSphere Means used to provision parameters: WMS
client, SANtricity client, SSH client, HP proliant Web and WPS
client.

Platform Attributes
WCE Platform
Management server
Management Computer
ILO IP
IP Name
Regular IP IP used for Name used
used to emergency when
connect to access accessing
the server the server

Platform Attributes
WCE Platform
Storage Array
Vcenter Transport Platform OAM
Network
SAN Name Data Platform VLANs Active/Standby
Volumes Center&Platform Link OA IP
I-scsi hosts names Aggregations 6125 XLG/G
Cluster of Hosts Switch IP
Resource pools SAN controllers
and vApp A/B IP
Virtual machines ESXI IP
vDS Blade ILO IP
Port groups LRCMgr VM IP
DataStores NTP primary IP

Platform Attributes
RNC platform
Storage Array
Vcenter Transport RNC&WMS OAM
Network
RNC Volume Nb of RNC VMs RNC platform

Name (UMU,PC,CMU) VLANs RNC OAM
RNC Volume LUN RNC resource pool RNC Telecom 3gOAM VM IP
Name and VLANs Cnode IP
dimensioning
Call Trace IP
RNC Id
WMS OAM
OAM NE WMS
IP
OAM OAM
WMS IP

Site Installation and Provisioning process
Installation stages Category of data
in CIQ
Install and commission

the Platform
WCE Platform
management server
Mgt Server
Commission the
WCE platform WCE Platform
Platform RNC
Install the RNC
Tenant
RNC

Customer Information Questionnaire (CIQ)
Fill out the CIQ before the platform commissioning
Dictionary of
parameters
Network Design
Document IP addressing plan
and IP design
Ready to fill out
the CIQ Form
Project
documents

Customer Information Questionnaire (CIQ)
Example

Vendors Documentation

Documentation
Thirdparty vendor websites
Vmware
vSphere 5.5
Knowledge base
HP
HP document
NetApp
5400 Documentation

Commissioning and
Integration overview

WCE platform
commissioning
work flow
206
Commissioning and integration workflow
WCE Platform Commissioning workflow
Back Office -Commissioning

Preparation Tasks
Preparation
Site - Commissioning Preparation

tasks
Commissioning
Site - Platform Commissioning

tasks

BackOffice - Commissioning preparation tasks
Design the UTRAN

Network
Fill out the Customer Study the Site installation

Information Questionnaire
(CIQ)

Site -Commissioning preparation tasks
Configure OAM Complement or Install and power up the
transport network adjust the CIQ 9771 WCE platform and
the platform
(Licenses, Software
management server
files)
Install the Software

on Platform
Management server
Check and upload

the platform
software
Check the OAM

transport network

Site WCE Platform Commissioning tasks

RNC tenant
integration
211
RNC integration work flow
Back Office
RNC integration Preparation Tasks
Site
RNC integration preparation tasks
Site
RNC integration tasks

Back office RNC integration preparation tasks
Design the UTRAN Network
Fill out the CIQ

Site RNC integration preparation tasks
Fill out the RNC

Check and upload
configuration
the platform
parameters form
software
Configure
OAM&Telecom
transport network

Site RNC integration tasks

9771 WCE Platform
Acceptance Overview

9771 WCE Acceptance book
Test cases
Domain Sub-Domain Title Duration
Conformity Software CON001 - Check the third-party 15 minutes
platform software
Conformity License CON002 Check 9771 WCE 15 minutes
platform software licenses
Conformity Connectivity CON003 Check the external 20 minutes
connectivity
Sanity System Health SAN001 Check the DC Breaker 5 minutes
Sanity System Health SAN002- Check C7000 Health 15 minutes
Sanity System Health SAN003 Check NetApp 5400 5 minutes
Storage Array Network Health
Sanity Time SAN004 Check the Time 20 minutes
synchronization
Robustness Power ROB001 - Check power redundancy 15 minutes

Redundancy
Robustness Equipment ROB002 - Check 6125XLG 15 minutes
Redundancy redundancy
Robustness Equipment ROB003 - Check 6125G redundancy 15 minutes
Redundancy
Robustness Equipment ROB004 Check the Storage Array 10 minutes
Redundancy Controller redundancy

9771 WCE Acceptance book
Test cases
Domain Sub-Domain Title Duration
Robustness Equipment ROB005 Check OA redundancy 10 minutes
Redundancy
Robustness Port Redundancy ROB006 Check the uplink OAM 10 minutes
port redundancy
Robustness Port Redundancy ROB007 Check the traffic port 15 minutes
redundancy
Robustness Equipment ROB008 Check VM migration on 15 minutes
Redundancy board failure
Robustness VM Redundancy ROB009 Check the redundancy of 15 minutes
3gOAM VM
Robustness RNC health ROB010 Check the RNC rebuild 45 minutes
Robustness Platform VM ROB011 Check the impact of 10 minutes
health LRCMgr VM loss

Intra Release and inter
release software upgrade
overview

Intra-Release and Inter-Release software upgrade
General Work flow

Preparation Tasks

Field Operation workflow

Impacted components versus migration path
Release Upgrade Paths Impacted components
ITS Upgrade Paths Impacted components

Thank you !


9771wce RNC VNPT

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

9771wce RNC VNPT

Uploaded by

Copyright:

Available Formats

9771 Wireless Cloud Element Radio Network Controller

Course GS00641-C-1710 Bangkok

1 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

2 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

10. Platform alarms monitoring

3 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

4 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

6 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

7 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

EMS 1 EMS 2 WMS Ve-Vnfm VNF

Nf-Vi VMware vCenter,

8 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

Multi-Tenancy ... server load is

Reduced Power Usage

Zero Downtime Maintenance

As traffic shifts during the day ...

10 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

packet core Telco Provided

backhaul Centralized baseband

Bringing NFV & vRAN to market Now Conventional

11 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

Cloud in a box Cloud on a disk

Hardware independent scalable Software only solution can be

From small single tenant to

12 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

Elastic computing via

VALUE WHY VIRTUALIZATION?

Shift from specialized Single asset

13 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

Flexibility Up to 5 logical RNCs per WCE

Full horizontal scalability through role realignment

Scalability Increase of capacity through in service SW growth of roles

H/W No physical separation of applications. Leveraging resourcing where they are

Innovation Full capacity with no latency or jitter issues

5+X the Capacity of dedicated H/W with Unsurpassed Flexibility

14 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

16 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

CPU Memory Storage Network CPU Memory Storage Network

Hypervisor Abstraction layer

17 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

The 9771 Wireless Cloud Element is

19 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

HPTM and NetAppTM

20 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

21 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

22 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

HP 6125 G and 6125 XLG Switches

NetApp Storage Array

9771 WCE Platform

DL380 Gen9 Server with optional Security Bezel

DL380 Gen9 Server Faceplate

26 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

DL380 Gen9 Server with Insight Display stowed away

DL380 Gen9 Server with Insight Display extended

DL380 Gen9 Server rear view, AC powered system

DL380 Gen9 Server rear view, DC powered system

28 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

29 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

30 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

Used before getting the OAM network remote access

32 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.

ILO 1Gb Eth port 4 *1Gb Eth ports

33 COPYRIGHT 2011 Nokia. ALL RIGHTS RESERVED.