Installation Prerequisites
Installation Prerequisites
This chapter provides the network size, hardware and software, and device configuration requirements that
must be met before installing Cisco RAN Management System (RMS), 4.0.
Note
Ensure that all the requirements in the following sections are addressed.
• Sample Network Sizes, page 1
• Hardware and Software Requirements, page 1
• Device Configurations, page 9
Sample Network Sizes
While planning the network size, you must consider the following:
• Number of femtocell access points (FAPs or APs, used interchangeably in this guide) in your network
• Current network capacity and additional capacity to meet future needs.
For more information about the recommended deployment modes, see Cisco RMS Deployment Modes.
Hardware and Software Requirements
These topics describe the FAPs, hardware, gateway, and virtualization requirements:
Note
Consult with your Cisco account representative for specific hardware and configuration details for your
APs, hardware, gateway, and units before you acquire or use RMS.
Hardware requirements assume that Cisco RMS does not share the hardware with additional applications.
(This is the recommended installation.)
RAN Management System Installation Guide, Release 4.0
February 9, 2015
1
Installation Prerequisites
Femtocell Access Point Requirement
Femtocell Access Point Requirement
Before you install the Cisco RAN Management System, you must install the FAPs that you want to support
in your network. Cisco RMS supports the FAPs listed in the following table:
Hardware
Band
Power
GPS
Residential/
Enterprise
Access Mode
USC 3330
2 and 5
20 mW
Yes
Residential
Closed
USC 3331
1
20 mW
No
Residential
Closed
USC 3331
2 and 5
20 mW
No
Residential
Closed
USC 5330
1
100 mW
No
Enterprise
Open
USC 5330
2 and 5
100 mW
No
Enterprise
Open
USC 7330
1
250 mW
No
Enterprise
Open
USC 7330
2 and 5
250 mW
Yes
Enterprise
Open
USC 9330
1
1W
No
Enterprise
Open
USC 9330
2 and 5
1W
Yes
Enterprise
Open
For information about the AP configuration, see AP Configuration, on page 9.
Cisco RMS Hardware and Software Requirements
Cisco UCS x86 hardware is used for Cisco RAN Management System hardware nodes.
The table below establishes the supported server models and configurations that are recommended for the
RMS solution.
Supported UCS Hardware
• Cisco UCS C240 M3 Rack Server
• Cisco UCS 5108 Blade Server
Target RMS Nodes
Central RMS node or All-In-One RMS node
Serving RMS node and Upload RMS node
• Cisco UCS B200 M3 Blade Server
Cisco UCS C240 M3 Server
The following hardware configuration is used for All-In-One RMS Node and Central RMS Node:
RAN Management System Installation Guide, Release 4.0
2
February 9, 2015
Installation Prerequisites
Cisco RMS Hardware and Software Requirements
• Cisco Unified Computing System (UCS) C240 M3 Rack Server
• Rack-mount
• 2 x 2.3 Ghz x 6 Core x86 architecture
• 64 GB RAM
• 12 disks: 4 x 15,000 RPM 300 GB, 8 x 10,000 RPM 300 GB
• RAID array with battery backup and 1 GB cache
• 4 + 1 built-in Ethernet ports
• 2 rack unit (RU)
• Redundant AC power
• Red Hat Linux Enterprise Edition v6.1
• VMware vSphere Standard Edition v5.1
• VMware vCenter Standard Edition v5.1
Cisco UCS 5108 Blade Server
The following hardware configuration is used for All-In-One RMS Node and Central RMS Node:
• Cisco UCS 5108 Blade Server
• Rack-mount
• 6 rack unit (RU)
• Redundant AC power
• Red Hat Linux Enterprise Edition v6.1
• VMware vSphere Standard Edition v5.1
• VMware vCenter Standard Edition v5.1
Note
The Cisco UCS 5108 Blade Server can house up to eight Cisco UCS B200 M3 Blade Servers or a
combination of B200 M3 and other UCS blade servers.
Cisco UCS B200 M3 Blade Server
The following hardware configuration is used for Serving RMS nodes:
• Cisco UCS B200 M3 Blade Server
• Rack-mount
• 2 CPUs using 32 GB DIMMs
• Up to 768 GB RAM
RAN Management System Installation Guide, Release 4.0
February 9, 2015
3
Installation Prerequisites
FAP Gateway Requirements
• 6 rack unit (RU)
• Redundant AC power
• Red Hat Linux Enterprise Edition v6.1
• VMware vSphere Standard Edition v5.1
• VMware vCenter Standard Edition v5.1
Note
Ensure that the selected UCS server is physically connected and configured with the appropriate software
before proceeding with the Cisco RMS installation.
To install the UCS servers, see the following guides:
• Cisco UCS C240 M3 Server Installation and Service Guide
• Cisco UCS 5108 Server Chassis Installation Guide
• Cisco UCS B200 Blade Server Installation and Service Note
Note
The Cisco UCS servers must be pre-configured with standard user account privileges.
FAP Gateway Requirements
The Cisco ASR 5000 Small Cell Gateway serves as the HNB Gateway (HNB-GW) and Security Gateway
(SeGW) for the FAP in the Cisco RAN Management System solution.
It is recommended that the hardware node with the Serving VM is co-located with the Cisco ASR 5000
Gateway. The Cisco ASR 5000 Gateway utilizes the Serving VM for DHCP and AAA services. This gateway
provides unprecedented scale that can exceed 125,000 APs that can be handled by a Serving VM (or redundant
pair).
Ensure that the Cisco ASR 5000 Gateway is able to communicate with the Cisco UCS server before proceeding
with the Cisco RMS installation.
To install the Cisco ASR 5000 Small Cell Gateway, see the Cisco ASR 5000 Installation Guide.
Virtualization Requirements
The Cisco RAN Management System solution that is packaged in Virtual Machine (VM) images (.ova file)
requires to be deployed on the Cisco UCS hardware nodes, defined in the Cisco RMS Hardware and Software
Requirements, on page 2.
The virtualization framework of the VM enables the resources of a computer to be divided into multiple
execution environments, by applying one or more concepts or technologies such as hardware and software
partitioning, time-sharing, partial or complete machine simulation, emulation, quality of service, and so on.
The benefit of using VMs is load isolation, security isolation, and administration.
• Load isolation ensures that a single service does not take over all the hardware resources and compromise
other services.
RAN Management System Installation Guide, Release 4.0
4
February 9, 2015
Installation Prerequisites
Virtualization Requirements
• Security isolation enables flows between VMs to be routed via a firewall, if desired.
• Administration is simplified by centralizing the VM deployment, and monitoring and allocating the
hardware HW resources among the VMs.
Before you deploy the Cisco RAN Management System .ova file:
• Ensure that you install:
◦VMware vSphere Standard Edition version 5.1.0
◦VMware vCenter Standard Edition version 5.1.0
For the procedure to install VMware, see Installing VMware ESXi and vCenter for Cisco RMS .
• Ensure that you plan the data storage or disk sizing for each of the following Cisco RMS VMs:
◦Central VM
◦Serving VM
◦Upload VM
For more information about data storage, see Data Storage for Cisco RMS VMs, on page 6.
Note
Make sure that all Network 1 (eth0) interfaces (Central Node, Serving Node, and Upload Nodes) must be
in same VLAN.
Optimum CPU and Memory Configurations
Following are the optimal values of CPU and memory required for each VM of the All -In-One setup to
support from 50,000 and Distributed RMS setup to support from 1,50,000 devices.
Node
vCPU
Memory
8
16 GB
All -In-One Setup
Central Node
Serving Node
Upload Node
32 GB
Distributed Setup
Central Node
8
Serving Node
8
Upload Node
16
16 GB
32 GB
RAN Management System Installation Guide, Release 4.0
February 9, 2015
5
Installation Prerequisites
Virtualization Requirements
Data Storage for Cisco RMS VMs
Before installing the VMware, consider the data storage or disk sizing for each of the Cisco RMS VMs.
Central VM
The disk-sizing of the Central VM is based on the calculation logic and size for SAN disk space for each
RAID set:
LUN Name
Purpose
RAID Set
Min Size
Calculation Logic
DATA
Database
#1
100 GB
In lab tests file size for database is 1
GB for 10,000 devices and 3000
groups, static neighbors if fully
populated for each AP, will require
an additional database size of around
1.4 GB per 10,000 devices.
Considering future expansion plans
for 2 million devices and 30% for
fragmentation, around 73 GB of disk
space will be required; 100 GB is the
recommended value.
TXN_LOG
Database
transaction logs
#2
10 GB
25 MB is seen with residential, but
with Metrocell, transaction logs will
be very high because of Q-SON. It
does not depend on AP deployment
population size. 10 GB is
recommended.
SYSTEM
OS and
#3
application image
and application
logs
100 GB
Linux and applications need around
16 GB and logs need 10 GB; for
backups, swap space and to allow for
additional copies for upgrades, 100
GB. It is independent of AP
deployment size.
RAN Management System Installation Guide, Release 4.0
6
February 9, 2015
Installation Prerequisites
Virtualization Requirements
LUN Name
Purpose
RAID Set
BACKUP
Database backups #4
Min Size
Calculation Logic
250 GB
To maintain minimum three backups
for upgrade considerations plus one.
56 GB is the size of the database files
for 2 million devices, so minimum
required will be approximately 250
GB.
For 10,000 devices, approximately 5
GB will be required to maintain four
backups.
If number of backups needed are
more, calculate disk size accordingly.
Serving VM
The disk-sizing of the Serving VM is based on the calculation logic and size for SAN disk space for each
RAID set:
LUN Name
Purpose
RAID Set
SYSTEM
OS and
#3
application
image and
application logs
Min Size
Calculation Logic
300 GB
Linux and applications need
approximately 16 GB; logs need
10 GB; for backups, swap space
and to allow for additional copies
for upgrades, 100 GB. It is
independent of AP deployment
size.
50 GB for PAR and 150 GB for
PNR.
Upload VM
The disk-sizing of the Upload VM is based on the following factors:
Sl. No.
Upload VM
Disk Size
1
Size of performance monitoring (PM) and statistics 500 KB
file in each log upload
2
Number of FAPs
10,000
3
Frequency of uploads per day
15 minutes per day (4 x 24 = 96 per
day)
4
Upload retention period
2 days
RAN Management System Installation Guide, Release 4.0
February 9, 2015
7
Installation Prerequisites
Virtualization Requirements
Sl. No.
Upload VM
Disk Size
5
Total size of PM uploads per day
Approximately 500 GB
6
Space requirement for the retention period specified 500 x 2 = 1000 GB
7
Considering additional 100 GB for other file uploads 1000 + 100 = 1100 GB
such as call-drop, on-demand and so on.
Total disk size required for Upload VM
The following disk-sizing of the Upoad VM is based on the calculation logic and size for SAN disk space for
each RAID set:
LUN Name
Purpose
RAID Set
Min Size
Calculation Logic
PM_LOGS
PM files
#5
15 TB
Calculation is for 10,000 APs with
the following assumptions:
• For 3G PM, upload file size
at 15 minute sampling
frequency and 15 minute
upload interval is 500 KB
(recommended).
• Un-archived file retention
period is 24 hours
(minimum).
• Archived file retention period
is 14 days.
• Compression – down to 15%
of total.
For a single module AP:
=(10000*24*4*500+
10000*24*4*500*0.15*14)/(1024*1024)
GB
= 1.385 TB
100 GB is kept for 10,000 PED file
for diagnostic purposes.
Minimum recommendation is for
10,000 APs with two weeks of
retention.
RAN Management System Installation Guide, Release 4.0
8
February 9, 2015
Installation Prerequisites
Device Configurations
LUN Name
Purpose
SYSTEM
RAID Set
Min Size
Calculation Logic
OS and
#3
application
image and
application logs
100 GB
Linux and applications need around
16 GB and logs need 10 GB; for
backups, swap space and to allow
for additional copies for upgrades,
100 GB. It is independent of AP
deployment size.
LUN Name
Purpose
Min Size
Calculation Logic
LOCAL
Database
20 GB
Local disk for PMG DB
SYSTEM
OS and
#3
application image
and application
logs
100 GB
Linux and applications need around
16 GB and logs need 10 GB; for
backups, swap space and to allow for
additional copies for upgrades, 100
GB. It is independent of AP
deployment size.
PMG Database VM
RAID Set
Device Configurations
Before proceeding with the Cisco RAN Management System installation, it is mandatory to complete the
following device configurations to enable the various components to communicate with each other and with
the Cisco RMS system.
AP Configuration
It is mandatory for all APs to have the minimal configuration to contact Cisco RMS within the service provider
environment. This enables Cisco RMS to automatically install or upgrade the AP firmware and configure the
AP as required for service.
For Ubiquisys Small Cell (USC), the AP initially connects to the public Ubiquisys cloud service, which
configured the enablement data on the AP and then directs it to the service provider Hosted & Managed
Services (HMS).
The minimum initial AP configuration includes the following:
• 2 to 4 Network Time Protocol (NTP) server IP addresses or fully qualified domain names (FQDNs).
This must be a factory default because the AP has to obtain time in order to perform certificate expiration
verification during authentication with servers. HMS will reconfigure the appropriate list of NTP servers
on bootstrap.
• Unique AP private key and certificate signed by appropriate Certificate Authority (CA)
• Trust Store configured with public certificate chains of the CA which signs server certificates.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
9
Installation Prerequisites
Cisco RMS Port Configuration
After each Factory reset, the AP contacts the Ubiquisys cloud service and downloads the following four
minimum parameters:
1 RMS public key (certificates)
2 RMS FQDN
3 Public NTP servers
4 AP software
With all these four parameters, the AP validates the RMS certificate, loads the AP software from cloud server,
and talks to RMS FQDN .
TR-069 and TR-196
The APs are managed via the TR-069 protocol and the TR-196 data model. The RMM implements a large
subset of the TR-196 Issue 1 Amendment 1 data model plus a large set of vendor extension parameters which
provide additional enhanced functionality.
The DPH-SO16 also implements a large set of TR-196 Issue 1 parameters and vendor extensions. However,
the data model and its behavior can be different from the Ubiquisys AP.
Activation Parameters
In this release, only the TR-196 parameter that resides with the BAC extensions is used for AP activation.
The Device Provisioning Engine (DPE) extensions expect identical data model parameters from the APs,
which are used for activation. For example, BAC DPE extensions that perform location verification will use
only standard TR-196 parameters.
Model-Specific Class of Service
The BAC must be configured to discover device models (APs) and associate them with different Class of
Service (CoS) objects. This implies that devices also get associated with different configuration and firmware
templates. These templates can then utilize different mode-specific parameters.
Vendor-extension Parameters
DPH-153-LA and DPH-S16 APs have completely different vendor extension parameters. This implies that
when these parameters are retrieved from these devices using PMG API, Get Device Data Tool (GDDT), or
other tools, the clients need to request parameters that are specific to the device model.
Cisco RMS Port Configuration
Configure the Cisco RMS nodes with ports as shown in the following table.
Node Type
Port
Source
Protocol
Usage
RAN Management System Installation Guide, Release 4.0
10
February 9, 2015
Installation Prerequisites
Cisco RMS Port Configuration
22
Administrator
SSH
Remote log-in(SSH)
161
NMS
UDP (SNMP)
SNMP agent used to
support get/set
162
NMS
UDP (SNMP)
SNMP agent to
support trap
OSS
TCP (HTTP)
OSS<->PMG
communication
443
UI
TCP (HTTPs)
DCC UI
49187
DPE
TCP
Internal RMS
communication Request coming
from DPE
8090
Administrator
TCP (HTTP)
DHCP
administration
HNB
TCP (HTTPs)
TR-069
management
7550
HNB
TCP (HTTPS)
Firmware download
49186
RDU
TCP
RDU<->DPE
communication
8443
Administrator
TCP (HTTPS)
DHCP
administration
RMS Serving Node 61610
(PNR)
HNB
UDP (DHCP)
IP address
assignment
RMS Serving Node 1812
(PAR)
ASR5K (AAA)
UDP (RADIUS)
Authentication and
authorization of
HNB during Iuh
HNB register
1234
RDU
TCP
DHCP internal
communication
647
RMS Serving Node TCP
(PAR)
All Server
RMS Central node 8083
RMS serving node 443
DHCP failover
communication.
Only used when
redundant RMS
Serving instances
are used.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
11
Installation Prerequisites
Cisco UCS Node Configuration
RMS Upload
server node
443
HNB
TCP (HTTPS)
PM & PED file
upload
8082
RDU
TCP
Availability check
TCP
North Bound traffic
8082
Cisco UCS Node Configuration
Each Cisco UCS hardware node has a minimum of 4 +1 Ethernet ports that connect different services to
different networks as needed. It is recommended that the following binding of IP addresses to Ethernet ports
must be followed:
Central Node Port Bindings
Port
IP Addresses
UCS Management Port
Cisco Integrated Management Controller (CIMC) IP
address
CIMC is used to administer Cisco UCS
hardware.
Hypervisor IP address
Note
Port 1
Hypervisor access is used to administer VMs
via vCenter.
vCenter IP address
Note
Port 2
Central VM IP address
Serving Node Port Bindings
Port
IP Addresses
UCS Management Port
CIMC IP address
Port 1
Hypervisor IP Address
Port 2
Serving VM north-bound (NB) IP address
Upload VM NB IP address
Port 3
Serving VM south-bound (SB) IP address
Upload VM SB IP address
RAN Management System Installation Guide, Release 4.0
12
February 9, 2015
Installation Prerequisites
Cisco ASR 5000 Gateway Configuration
All-in-One Node Port Bindings
Port
IP Addresses
UCS Management Port
CIMC IP address
Port 1
Hypervisor IP Address
vCenter IP address
Port 2
Central VM IP address
Serving VM NB IP address
Upload VM NB IP address
Port 3
Serving VM south-bound (SB) IP address
Upload VM SB IP address
Cisco ASR 5000 Gateway Configuration
The Cisco ASR 5000 Gateway utilizes the Serving VM for DHCP and AAA services. The blade-based
architecture of the gateway provides unprecedented scale that can exceed 125,000 APs that can be handled
by a Serving VM (or redundant pair).
To scale beyond 125,000 APs, the ASR5000 uses several instances of SeGW and HNB-GW within the same
Cisco ASR 5000 chassis to direct DHCP and AAA traffic to the correct Serving VM.
• SeGW instances—A separate SeGW instance must be created in the Cisco ASR 5000 for every 125,000
APs or every provisioning group (PG) (if smaller PGs are used). Each SeGW instance must:
◦Have a separate public IP address for APs to connect to;
◦Configure DHCP requests to be sent to different set of Serving VMs.
The SeGW can be co-located with HNB-GW on the same physical ASR 5000 chassis or alternatively
SeGW can created on an external ASR 9000 or Cisco 7609 chassis.
• HNB-GW instances—A separate HNB-GW instance must be created in the Cisco ASR 5000 for every
125,000 APs or every PG (if smaller PGs are used). Each HNB-GW instance must:
◦Support different private IP address
◦Associate with one SeGW context
◦Configure AAA traffic to be sent to different Serving VM
◦Configure AAA traffic to be received from the Central VM (PMG) on a different port or IP port.
RAN Management System Installation Guide, Release 4.0
February 9, 2015
13
Installation Prerequisites
NTP Configuration
To configure the Cisco ASR 5000 Small Cell Gateway, see the Cisco ASR 5000 System Administration
Guide.
NTP Configuration
Network Time Protocol (NTP) synchronization must be configured on all devices in the network as well as
on the Cisco UCS servers. The NTP server can be specified during server installation. Failure to organize
time synchronization across your network can result in anomalous functioning and results in the Cisco RAN
Management System.
To configure NTP, see Preparing the OVA Descriptor Files.
Public Fully Qualified Domain Names
It is recommended to have fully qualified domain name (FQDNs) for all public and private IP addresses
because it can simplify IP renumbering. The DNS used by the operator must be configured to resolve these
FQDNs to IP addresses.
If FQDNs are used to configure target servers on the AP, then server certificates must contain both the FQDN
and IP address in order to perform appropriate security handshake for TLS and IPSec flows.
RAN Management System Installation Guide, Release 4.0
14
February 9, 2015
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising