Installation Prerequisites

Installation Prerequisites
Installation Prerequisites
This chapter provides the network size, hardware and software, and device configuration requirements that
must be met before installing the Cisco RAN Management System (RMS).
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
• RMS System Backup, page 17
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, RMS hardware and software, gateway, and virtualization requirements:
Note
Consult with your Cisco account representative for specific hardware and configuration details for your
APs, RMS, and gateway units.
Hardware requirements assume that Cisco RMS does not share the hardware with additional applications.
(This is the recommended installation.)
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
1
Installation Prerequisites
Femtocell Access Point Requirement
Femtocell Access Point Requirement
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 6732
(UMTS)
2 and 5
125 mW
Yes
Enterprise
Open
USC 6732
(LTE)
4, 2, 30, and 5
250 mW
Yes
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 Access Point 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 that are recommended for the RMS solution.
Supported UCS Hardware
• Cisco UCS C240 M3 Rack Server
Target RMS Nodes
All RMS nodes
• Cisco UCS 5108 Chassis Based Blade Server
Cisco RAN Management System Installation Guide, Release 5.1
2
July 6, 2015
Installation Prerequisites
Cisco RMS Hardware and Software Requirements
Cisco UCS C240 M3 Server
The following hardware configuration is used for all RMS nodes:
• Cisco Unified Computing System (UCS) C240 M3 Rack Server
• Rack-mount
• 2 x 2.3 Ghz x 6 Core x86 architecture
• 128 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 Enterprise Linux Edition, v6.6
• VMware vSphere Standard Edition v5.5
• VMware vCenter Standard Edition v5.5
Cisco UCS 5108 Chassis Based Blade Server
The following hardware configuration is used for all RMS nodes:
• Cisco UCS 5108 Chassis
• Rack-mount
• 6 rack unit (RU)
• Redundant AC power
• Red Hat Enterprise Linux Edition, v6.6
• VMware vSphere Standard Edition v5.5
• VMware vCenter Standard Edition v5.5
• SAN storage with sufficient disks (see, Data Storage for Cisco RMS VMs, on page 5)
Note
The Cisco UCS 5108 Chassis can house up to eight Cisco UCS B200 M3 Blade Servers.
Cisco UCS B200 M3 Blade Server
• Cisco UCS B200 M3 Blade Server
• Rack-mount
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
3
Installation Prerequisites
FAP Gateway Requirements
• 2 CPUs using 32 GB DIMMs
• 128 GB RAM
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 2,50,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 (on which RMS
will be installed) 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.
• 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.
Cisco RAN Management System Installation Guide, Release 5.1
4
July 6, 2015
Installation Prerequisites
Virtualization Requirements
Before you deploy the Cisco RAN Management System .ova file:
• Ensure that you install:
◦VMware vSphere Standard Edition v5.5
◦VMware vCenter Standard Edition v5.5
For the procedure to install VMware, see Installing VMware ESXi and vCenter for Cisco RMS.
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 2,50,000 devices.
Node
vCPU
Memory
8
16 GB
All -In-One Setup
Central Node
Serving Node
Upload Node
64 GB
Distributed Setup
Central Node
16
Serving Node
8
Upload Node
16
16 GB
64 GB
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, on page 5
• Serving VM, on page 6
• Upload VM, on page 7
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:
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
5
Installation Prerequisites
Virtualization Requirements
LUN Name
Purpose
RAID Set
Min Size
Calculation Logic
DATA
Database
#1
200 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; 200GB is the
recommended value.
TXN_LOG
Database
transaction logs
#2
200 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. 200 GB is
recommended.
SYSTEM
OS and
#3
application image
and application
logs
200 GB
Linux and applications need around
16 GB and application logs need 50
GB; Recommended value 200GB
considering Ops tools generated logs
and reports. It is independent of AP
deployment size.
BACKUP
Database backups #4
250 GB
To maintain minimum four backups
for upgrade considerations.
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:
Cisco RAN Management System Installation Guide, Release 5.1
6
July 6, 2015
Installation Prerequisites
Virtualization Requirements
LUN Name
Purpose
RAID Set
SYSTEM
OS and
#1
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, 200 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
Approximate size of performance monitoring (PM) 100 KB for Enterprise FAP and 7.5
statistics file in each log upload
MB for Residential FAP
2
Number of FAPs per ULS
2,50,000 (50,000 Enterprise +
2,00,000 Residential)
3
Frequency of PM uploads
Once in 15 minutes (4 x 24 = 96
per day) for Enterprise FAPs
Once in a day for Residential FAPs
The following disk-sizing of the Upoad VM is based on the calculation logic and size for SAN disk space for
each RAID set:
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
7
Installation Prerequisites
Virtualization Requirements
LUN Name
Purpose
RAID Set
Min Size
Calculation Logic
PM_RAW
For storing
RAW files
#1
350 GB
Calculation is for 2,50,000 APs
with the following assumptions:
• For Enterprise 3G FAP PM,
size of uploaded file at 15
min sampling frequency and
15 min upload interval is 100
KB
• For Residential 3G FAP PM,
size of uploaded file at 1 hour
sampling frequency and 1
day upload interval is 7.5 MB
• ULS has at the most last 2
hours files in raw format.
For a single mode AP:
Disk space required for PM files =
(50000*4*2*100)/(1024/1024) +
(200000*2*7.5)/(1024*24) = 39 +
122
= 161 GB
Additional space for storage of
other files like on-demand = 200
GB
PM_ARCHIVE For storing
ARCHIVED
files
#2
1000 GB
Considering the compression ratio
is down to 15% of total size and
ULS starts purging after 60% of
disk filled, disk space required by
compressed files uploaded in 1 hr
=
(50000*4*2*100)/(1024/1024) +
(200000*2*7.5)/(1024*24))*0.15
= 25 GB
To store 24 hrs data, space required
= 25*24 = 600 GB = 60% of total
disk space
Therefore, total disk space for PM
files = 1000 GB
Cisco RAN Management System Installation Guide, Release 5.1
8
July 6, 2015
Installation Prerequisites
Device Configurations
LUN Name
Purpose
SYSTEM
RAID Set
Min Size
Calculation Logic
OS and
#3
application
image and
application logs
200 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,
200 GB. It is independent of AP
deployment size.
LUN Name
Purpose
Min Size
Calculation Logic
SYSTEM
OS and
#1
application image
and application
logs
50 GB
Linux and Oracle applications need
around 25 GB. Considering backups
and swap space 50 GB is
recommended. 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.
Access Point Configuration
It is mandatory for all small cell access points 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.
USC 3000, 5000 and 7000 series access points initially connect to the public Ubiquisys cloud service, which
configures the enablement data on the AP and then directs them to the service provider Hosted & Managed
Services (HMS).
The minimum initial AP configuration includes the following:
• 1 to 3 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.
After each Factory recovery, the AP contacts the Ubiquisys cloud service and downloads the following four
minimum parameters:
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
9
Installation Prerequisites
Supported Operating System Services
1 RMS public key (certificates)
2 RMS ACS URL
3 Public NTP servers
4 AP software
With these four parameters, the AP validates the RMS certificate, loads the AP software from cloud server,
and talks to RMS.
Supported Operating System Services
Only following UNIX services are supported on Cisco RMS. The installer disables all other services.
Node Type
List of Services
RMS Central node
SSH,, HTTPS, NTP, SNMP, SAN, RSYSLOG
RMS Serving node
SSH, HTTPS, NTP, SNMP, SAN, RSYSLOG
RMS Upload Server node
SSH, HTTPS, NTP, SNMP, SAN, RSYSLOG
Cisco RMS Port Configuration
The following table lists the different ports used on the Cisco RMS nodes.
Node Type
Port
Source
Protocol
Usage
Cisco RAN Management System Installation Guide, Release 5.1
10
July 6, 2015
Installation Prerequisites
Cisco RMS Port Configuration
All Server
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
123
NTP Server
UDP
NTP for time
synchronization
514
Syslog
UDP
Syslog - used for
system logging
5488
Administrator
TCP
VMware VAMI
(Virtual Appliance
Management
Infrastructure)
services
5489
Administrator
TCP
VMware VAMI
(Virtual Appliance
Management
Infrastructure)
services
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
11
Installation Prerequisites
Cisco RMS Port Configuration
RMS Central
node
8083
OSS
TCP (HTTP) OSS<->PMG
communication
8084
RDU
TCP
443
UI
TCP (HTTPs) DCC UI
49187
DPE
TCP
8090
Administrator
TCP (HTTP) DHCP
administration
5439
Administrator
TCP
Postgres database
port
1244
RDU/PNR
TCP
DHCP internal
communication
8009
Administrator
TCP
Tomcat AJP
connector port
9006
Administrator
TCP
BAC Tomcat server
port
8015
Administrator
TCP
PNR Tomcat server
port
3799
ASR5K (AAA)
UDP
(RADIUS)
RADIUS
Change-of-Authorization
and Disconnect
flows from PMG to
ASR5K (Default
Port)
8001
RDU
UDP (SNMP) SNMP Internal
49887
RDU
TCP
Listening port (for
watchdog) for RDU
SNMP Agent
4698
PMG
TCP
Default listening port
for Alarm handler to
listen PMG events
Random
RDU/PNR/Postgres/PMG TCP/UDP
RDU Fault Manager
server
communication
Internal RMS
communication Request coming
from DPE
Cisco RAN Management System Installation Guide, Release 5.1
12
July 6, 2015
Installation Prerequisites
Cisco RMS Port Configuration
Random ports used
by internal
processes: java,
postmaster, ccmsrv,
cnrservagt, ruby,
RPCBind, and
NFS(Network File
system)
RMS Serving
node
443
HNB
TCP (HTTPs) TR-069 management
7550
HNB
TCP
(HTTPS)
Firmware download
49186
RDU
TCP
RDU<->DPE
communication
2323
DPE
TCP
DPE CLI
8001
DPE
UDP(SNMP) SNMP Internal
7551
DPE/PAR
TCP
DPE authorization
service with PAR
communication
Random
DPE/PNR/PAR
TCP/UDP
Random ports used
by internal
processes: java,
arservagt, armcdsvr,
cnrservagt, dhcp,
cnrsnmp, ccmsrv
,dpe, cnrservagt, and
arservagt
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
13
Installation Prerequisites
Cisco RMS Port Configuration
61610
HNB
UDP (DHCP) IP address
assignment
9443
Administrator
TCP
(HTTPS)
PNR GUI port
1234
RDU/PNR
TCP
DHCP internal
communication
RMS
Serving
Node
(PAR)
1812
ASR5K
(AAA)
UDP (RADIUS)
1234
RDU
TCP
DHCP internal
communication
647
RMS Serving Node
(PAR)
TCP
DHCP failover
communication.
Only used when
redundant RMS
Serving instances are
used.
8005
Administrator
TCP
Tomcat server port
8009
Administrator
TCP
Tomcat AJP
connector port
8443
Administrator
TCP
(HTTPS)
PAR GUI port
443
HNB
TCP
(HTTPS)
PM & PED file
upload
8082
RDU
TCP
Availability check
TCP
North Bound traffic
TCP/UDP
Random ports used
by internal
processes: java, ruby
RMS Serving
Node (PNR)
RMS Upload
Server node
8082
Random
Upload Server
Authentication
and
authorization
of HNB
during Iuh
HNB
register
Cisco RAN Management System Installation Guide, Release 5.1
14
July 6, 2015
Installation Prerequisites
Cisco UCS Node Configuration
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 Southbound (SB) IP address
Port 3
Central VM Northbound (NB) IP address
Serving and Upload 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
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
15
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 SB 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
Port 4
Central VM NB 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 2,50,000 APs that can be handled
by a Serving VM (or redundant pair).
To scale beyond 2,50,000 APs, the ASR 5000 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 2,50,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
2,50,000 APs or every PG (if smaller PGs are used). Each HNB-GW instance must:
◦Support different private IP addresses for APs to connect via IPSec tunnel
◦Associate with one SeGW context
◦Configure AAA traffic to be sent to different set of Serving VMs
◦Configure AAA traffic to be received from the Central VM (PMG) on a different port or IP
Cisco RAN Management System Installation Guide, Release 5.1
16
July 6, 2015
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.
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 of RMS nodes.
If FQDNs are used to configure target servers on the AP, then server certificates must contain the FQDN to
perform appropriate security handshake for TLS.
RMS System Backup
It is recommended to perform a backup of the system before proceeding with the RMS installation. For more
details, see System Backup.
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
17
Installation Prerequisites
RMS System Backup
Cisco RAN Management System Installation Guide, Release 5.1
18
July 6, 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