Sci 1.0 User Guide - Lcs - 20131218

Ruckus Wireless SmartCell Insight

Release 1.0 User Guide

Part Number 800-70566-001 Rev APublished December 2013

www.ruckuswireless.com

SmartCell Insight User Guide, 800-70566-001 Rev A 3

Copyright Notice and Proprietary Information

Copyright 2013. Ruckus Wireless, Inc. All rights reserved. No part of this documentation may be used, reproduced, transmitted, or translated, in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without prior written permission of Ruckus Wireless, Inc. (Ruckus), or as expressly provided by under license from Ruckus.

Destination Control StatementTechnical data contained in this publication may be subject to the export control laws of the United States of America. Disclosure to nationals of other countries contrary to United States law is prohibited. It is the readers responsibility to determine the applicable regulations and to comply with them.

DisclaimerTHIS DOCUMENTATION AND ALL INFORMATION CONTAINED HEREIN (MATERIAL) IS PROVIDED FOR GENERAL INFORMATION PURPOSES ONLY. RUCKUS AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THE MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR THAT THE MATERIAL IS ERROR-FREE, ACCURATE OR RELIABLE. RUCKUS RESERVES THE RIGHT TO MAKE CHANGES OR UPDATES TO THE MATERIAL AT ANY TIME.

Limitation of LiabilityIN NO EVENT SHALL RUCKUS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUEN-TIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE OF, THE MATERIAL.

Trademarks Ruckus Wireless, Ruckus, the bark logo, ZoneFlex, FlexMaster, ZoneDirector, SmartMesh, Channelfly, Smartcell, Dynamic PSK, and Simply Better Wireless are trademarks of Ruckus Wireless, Inc. in the United States and other countries. All other product or company names may be trademarks of their respective owners.

4 Ruckus Wireless, Inc.


Contents

Copyright Notice and Proprietary Information

About This GuideDocument Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Documentation Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1 Introducing SmartCell InsightIntroducing SmartCell Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Off-the-shelf value and easy to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Greater Network Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Installing the SmartCell Insight ApplicationBefore You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SCI Architecture and Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Ports and Protocols that Must be Open for SCI-Data Source Communications . . . . . . . 22Quick Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Step 1: Install CentOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Step 2: Install the SmartCell Insight Package and the BI License . . . . . . . . . . . . . . . . . 25Step 3: Change the Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Step 4: Configure Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Step 5: Import the SCI License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Full CentOS Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28CentOS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28The actual installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3 Navigating the SmartCell Insight User InterfaceGetting Familiar with the SCI User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Interacting with Workspace Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Scheduling Email Report Delivery for Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . 60


4 Using the Built-In ReportsUsing the Built-In Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Client and Session Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Inventory Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Operational Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Traffic Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Report Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5 Configuring Custom ReportsOverview of Custom Report Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Creating a New Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Choosing a Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91The New Analyzer Report Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Adding Fields and Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Switching to Chart Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Changing the Chart Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Applying Filters to Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Adding a Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Saving the Report to a Shared Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Available Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6 Managing the SmartCell Insight SystemSetting Administrator Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Accessing the Administration Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Getting Familiar with the Administration Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Monitor Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110System Setup Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Diagnostics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Changing the Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Adding a FlexMaster Reporting User for SCI Reporting . . . . . . . . . . . . . . . . . . . . . . . . . 128A note about adding SCG to SmartCell Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128SCI Uninstall Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129SCI Backup & Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129SCI AP Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Uploading an SCI License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130System Timekeeping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Using the Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Creating Users and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Using the Scheduler to Define Public Schedules for Custom Reports. . . . . . . . . . . . . 136


Index


About This Guide

This User Guide provides information on installation, configuration and management of the Ruckus Wireless SmartCell Insight (SCI) application. Topics covered in this guide include SCI introduction, built-in report generation, custom report creation, application management and lists of metrics available for reporting.

This guide is intended for use by those responsible for managing Ruckus Wireless network equipment. Consequently, it assumes a basic working knowledge of local area networking, wireless networking, and wireless devices.

NOTE: If release notes are shipped with your product and the information there differs from the information in this guide, follow the instructions in the release notes.

Most user guides and release notes are available in Adobe Acrobat Reader Portable Document Format (PDF) or HTML on the Ruckus Wireless Support Web site at

https://support.ruckuswireless.com/documents.

Document Conventions


Document ConventionsTable 1 and Table 2 list the text and notice conventions that are used throughout this guide.

Table 1. Text conventions

Convention Description Example

monospace Represents information as it appears on screen

[Device name]>

monospace bold Represents information that you enter

[Device name]> set ipaddr 10.0.0.12

default font bold Keyboard keys, software buttons, and field names

On the Start menu, click All Programs.

italics Screen or page names Click Advanced Settings. The Advanced Settings page appears.

Table 2. Notice conventions

Notice Type Description

Note Information that describes important features or instructions

Caution Information that alerts you to potential loss of data or potential damage to an application, system, or device

Warning Information that alerts you to potential personal injury

Related Documentation


Related DocumentationIn addition to this User Guide, each SmartCell Insight documentation set includes the following:

Installation Guide: Provides detailed information on how to install SmartCell Insight. The Installation Guide is available for download on the Ruckus Wireless Support Web site at http://support.ruckuswireless.com.

Online Help: Provides instructions for performing tasks using the SmartCell Insight Web interface. The online help is accessible from the Web interface and is searchable.

Release Notes: Provide information about the current software release, including new features, enhancements, and known issues.

Documentation FeedbackRuckus Wireless is interested in improving its documentation and welcomes your comments and suggestions. You can email your comments to Ruckus Wireless at:

[email protected]

When contacting us, please include the following information:

Document title

Document part number (on the cover page)

Page number (if appropriate)

For example:

SmartCell Insight User Guide

Part number: 800-70566-001 Revision A

Page 88

Documentation Feedback



1Introducing SmartCell InsightIn this chapter:

Introducing SmartCell Insight

Overview

Off-the-shelf value and easy to use

Capabilities

Greater Network Visibility

Introducing SmartCell InsightOverview


Introducing SmartCell Insight

OverviewSmartCell Insight (SCI) is a massively scalable reporting and analytics engine, designed to collect data from Ruckus network equipment, analyze that data, and then present it using a wide variety of standard and custom reports.

Off-the-shelf value and easy to useTo facilitate immediate value, SmartCell Insight ships with pre-built reports that solve the most common use cases faced by Engineering, Operations, and Planning organizations. These reports cover themes such as traffic usage, client and session measurement, equipment uptime, network latency, etc. For example, some of the reports can highlight the most heavily utilized devices by both the number of subscribers as well as traffic load. If these reports are not sufficient or need to be tweaked, then additional reports can be generated on site.

Using any standard browser, network operators can create reports on the fly and get a deep insight into any Key Performance Indicator (KPI) that network equipment exposes to northbound systems. For example, compare subscriber equipment distribution (i.e., iPhone vs. Android vs. Windows Phone) market share growth today compared to last month or last year.

CapabilitiesSmartCell Insight can collect data from the entire line of Ruckus Access Points (APs) along with the Zone Directors (ZDs), FlexMasters (FMs), or the SmartCell Gateways (SCG). This data can be aggregated in an offline columnar database, which has been optimized for very high volume data retention and quick response time. Ruckus SmartCell Insight can provide a feed to upstream OSS/BSS applications using a wide variety of interfaces. This allows for further analysis of data collected in the Wi Fi RAN by upstream systems.

Greater Network VisibilityGetting the most from a carrier Wi-Fi network, once deployed, requires clear visibility into its performance and user activity, both at a very granular level of detail as well as aggregated to measure global trends spanning many years.

Introducing SmartCell InsightGreater Network Visibility


Operators need this level of visibility to assess the networks achievement of their business objectives. These include user experience metrics, traffic load on the Wi-Fi RAN, network uptime, etc.

SCI leverages two emerging trends: Firstly, Mobile Internet usage patterns, RAN strategies, and service models are all evolving rapidly, so the visibility required to address these questions must extend beyond typical short-horizon EMS/NMS health and statistics to enable long-term trend analysis that supports network and service evolution planning. With exploding volumes of users, devices, traffic, and radio nodes deployed, these two requirements spell a real scaling challenge for any network measurement and assessment tool.

Secondly, the emergence of Big Data brought to market by many popular applica-tions that facilitate the collection, storage, and efficient retrieval and analysis of data. These technologies, in SCI, have been brought to the management of network equipment resulting in a comprehensive offering that can facilitate additional capa-bilities in future releases.

Ruckus development of SmartCell Insight, in the same way with the SmartCell Gateway, is whole new approach to measurement and assessment, designed specifically to provide the visibility, trends analysis, and raw scale required to manage a successful carrier Wi-Fi network. The design of SmartCell Insight is informed by our experience powering the worlds largest and most advanced Wi-Fi networks.

Introducing SmartCell InsightGreater Network Visibility



2Installing the SmartCell Insight ApplicationIn this chapter:

Before You Begin

Minimum System Requirements

Quick Installation Instructions

Full CentOS Installation Instructions

Before You BeginSCI Architecture and Modules


Before You BeginSmartCell Insight is designed to be installed on a CentOS server and is distributed as a YUM repository for installation on CentOS.

SCI Architecture and ModulesThe following diagram illustrates the components of an SCI deployment, including the ZoneDirector (ZD), FlexMaster (FM), SmartCell Gateway (SCG) and ZoneFlex Access Points (APs) that provide data to the SCI system.

NOTE: SCI can collect data from either SCG or FlexMaster. If using SCG, then SCG is the only controller needed along with SCG-firmware APs. If you are using ZoneFlex APs, then both FlexMaster and ZoneDirector are required to send data from the APs to ZoneDirector to FlexMaster, then finally to SCI.

WARNING! SCI requires either SCG version 2.1.1 or later, or ZoneDirector/APs to be running ZoneFlex version 9.5.3.45 or 9.7 to operate.

For FlexMaster, the minimum firmware version is 9.5.3.0.4.

All APs (both ZF and SCG) and all zones (in SCG) must be running a supported firmware version to work with SCI.

ZF: This should be applied to all APs connected to the controller, and to all controllers connected to the FM managed by SCI.

SCG: This should be applied to all zones and APs connected to the controller. These should be taken care of prior to attaching these sources to SCI. Failing to do so will cause SCI to malfunction and unpredicted behavior.

Before You BeginSCI Architecture and Modules


Figure 1. SCI Architecture and Modules

A block diagram of the Ruckus system for measuring, aggregating and transport of statistics for use in SCI is shown in Figure 2. Statistics measurements are made at APs over a measurement interval (MI). AP measurements are reported to ZDs and SCGs.

When APs report the statistics to ZDs:

The MI = 90s. APs sends its measurements to the ZD once per MI.

ZDs then aggregates the measurements into an aggregate measurement reporting interval (AMRI), which is 15 minutes.

ZD saves these aggregated measurements in bins and saves the last 24-hours (5 bins).

SCI retrieves from ZD the bins it needs for its analytics reports. Typically, SCI sends a statistics query to ZD every 15 minutes with two query parameters, INTERVAL-START and INTERVAL-STOP. ZD provides all bins data spanning the time interval in the query parameters. Note that ZD overwrites each bin every 24 hours; therefore SCI is responsible for retrieving from ZD the data it needs before this happens, otherwise its forever lost.

Minimum System RequirementsSCI Architecture and Modules


When APs report the statistics to SCGs:

The MI = 15 minutes. APs sends its measurements to the SCG once per MI.

APs save these aggregated measurements in bins and save the last 24-hours (5 bins).

SCI retrieves from SCG the bins it needs for its analytics reports. SCG overwrites each bin every 24 hours.

Figure 2. Data source block diagram

NOTE: Note that when APs reboot, they lose all measurements and aggregated statistics. After an AP reboots, it re-initializes its real-time clock via NTP. Refer to System Timekeeping on page 131 for more information on system timekeeping.

Minimum System RequirementsTable 1 lists the minimum system requirements for SCI installation on a CentOS server.

Minimum System RequirementsSCI Architecture and Modules


Additional requirements:

When installed, the installation type must be set to Minimal

Ruckus Wireless SmartCell Insight Repository (sci-repo package)

CentOS installation media or an active Internet connection on the server to be installed

NOTE: CPU frequency scaling enabled may adversely affect the performance of the database. It is recommended that CPU frequency scaling be turned off or set to 'performance'.

Storage RecommendationsNote the following recommendations for storage capacity:

The required storage of 4TB is required as something that appears to the OS as a single 4TB (or larger) drive.

A hardware-RAID-based 4TB volume can be used. For maximum performance, it is better to avoid RAID levels that require expensive parity calculations (such as RAID5 and RAID6). For redundancy and performance, RAID10 gives both redundancy storing of the data, and striping that both increases performance and allows to construct a larger volume from multiple small drives. Of course, it is less cost-efficient than RAID5, due to the storage volume being N/2 * (total space of smallest drive), due to the RAID1 component of RAID10.

LVM volume management is not recommended. By default, when CentOS (or RHEL) is installed, it will partition the system using LVM. Therefore, when one installs the OS, s/he needs to manually partition the drive. Suggested sizing is as follows:

First partition: /boot - 100MB (fixed)

Table 1. Minimum System Requirements

CPU 2 x Intel Xeon CPU E5-2620 @ 2.0GHz or higher (6 cores)

Memory 48 GB RAM

Hard Drive 4 TB

OS CentOS 6.4 (64-bit), orRedHat Enterprise Linux 6.4 (64-bit)

Ports and Protocols that Must be Open for SCI-Data Source CommunicationsSCI Architecture and Modules


Second partition: / (grow to fill all free space) (so it will be close to 4TB on that volume... or more, if a larger RAID volume was provided...)

SecurityUpon successful installation of the product, the CentOS default Firewall configura-tion for IPv4 should be configured as depicted in the following table:

OUTPUT chain will not be restricted (ACCEPT default policy).

FORWARD chain will be restricted (DROP default policy, and no rules).

CentOS' IPv6 default Firewall rules are left intact.

NOTE: SCI does not support SELinux. SCI is supposed to detect SELinux if it is active and disable it. Customers should not turn it back on, as it will cause issues.

Ports and Protocols that Must be Open for SCI-Data Source CommunicationsNote that if SCI and its data sources are on the same subnet, you do not need to open any firewall ports for communication. If ZoneDirector, FlexMaster or SCG is behind NAT, the following ports must be open for SCI to retrieve its data.

Table 2. Chain INPUT (policy DROP)

Target Input Interface

Source Destination Protocol Port State

ACCEPT Any Any Any Any Any Related, Established

ACCEPT Any Any Any Any dpt:22 NEW




ACCEPT Io Any Any Any Any NEW

Quick Installation InstructionsStep 1: Install CentOS


Quick Installation InstructionsThis section provides a brief set of instructions to get the OS and SCI software up and running quickly. For detailed instructions on CentOS installation to meet SCI requirements, please see Full CentOS Installation Instructions on page 28.

WARNING! You must ensure that your CentOS installation is performed according to these instructions. If not, the SCI installation will fail.

Step 1: Install CentOS1 Install CentOS 6.x 64-bit Edition. When asked, choose Minimal installation

type.

2 Configure LAN connectivity. Verify DNS is correct. (e.g. ping www.google.com)

3 Set your machine hostname. For example, if you want your hostname to be 'sci-node-1':

a Edit your /etc/sysconfig/network file to look like this:

i. NETWORKING=yes

ii. HOSTNAME=sci-node-1

Table 3. Ports and Protocols that must be open for SCI-data source communications

Port Protocol Source > Destination

Notes

443 SSH ZD > SCI

***needs to be filled. FM > SCI

SCG > SCI

Quick Installation InstructionsStep 1: Install CentOS


b Edit (using your favorite editor) the file /etc/hosts, and add the hostname you have chosen during the installation to the list of hostnames mapped to 127.0.0.1, so that when you view the /etc/hosts file, it will look like this (assuming your hostname is 'sci-node-1', of course):

c Type 'reboot' to restart your server in order to apply your new hostname configuration.

4 Unpack the Ruckus Wireless SmartCell Insight Repository (sci-repo package). You may unpack it locally to the server you're going to install it on, or, on an HTTP server which is accessible to the server you'll run the installation on.

5 Create a YUM repository file /etc/yum.repos.d/ruckus-sci.repo

For example, if you unpacked the sci-repo directory to /root/ (so you have a /root/sci-repo directory):

[ruckus-sci]

name=Ruckus SCI Repository

baseurl=file:///root/sci-repo/

gpgcheck=0

enabled=1

If your sci-repo directory has been placed on a LAN webserver, you would use:

baseurl=http://http-server.companydomain.local/sci-repo

instead.

6 If you don't have an Internet connection, mount the CentOS installation DVD #1 in one of the following filesystem locations:

/media/CentOS

/media/cdrom

/media/cdrecorder

And edit the file /etc/yum.repos.d/CentOS-Media.repo, changing:

enabled=0

To:

enabled=1

Quick Installation InstructionsStep 2: Install the SmartCell Insight Package and the BI License


Step 2: Install the SmartCell Insight Package and the BI License 1 Run the following command to install the SCI package:

yum -y install rks-sci2 Run the following command to install the SCI Business Intelligence license:

yum -y install [license-package-filename.rpm]3 Verify that all packages were installed successfully in YUM's report.

4 Type: reboot.

Step 3: Change the Administrator PasswordTo change the admin password, use the following procedure:

1 Open an SSH connection to the SCI servers location and run the following commands to configure the password for the Root user: $ ssh -l root 172.21.127.226Password: Last login: Wed Nov 6 15:32:37 2013 from 172.21.10.181[root@sci-dev ~]# /opt/ruckuswireless/sci/scripts/sci_change_admin_pass-word.php

################################################### # Ruckus Wireless SmartCell Insight v1.0.0.0.1407 # ###################################################

This utility changes the password for the 'admin' user on Administrative Web Interface, User Console and Enterprise Console.

Please enter a new admin password (or hit Ctrl+C to abort)? Please enter the new admin password again to verify (or hit Ctrl+C to abort)?

New password accepted. Updating new password across all systems... Updating User Console... SUCCESS!Updating AdminWeb/User Console... SUCCESS! Restarting User Console...Waiting 10 seconds for service to go down... Utility finished.[root@sci-dev ~]#

Quick Installation InstructionsStep 4: Configure Data Sources


2 The next time you log in to the Administration Interface, User Console or Enterprise Console (as admin), use the new password to log in.

Step 4: Configure Data Sources1 Open your browser and browse to:

http://your-sci-server/

2 You will be prompted for a user name and password. Enter the following if you have not yet changed the default user name and password (see Step 3: Change the Administrator Password on page 25):

User name: admin

Password: secret

3 In the System Setup page, add all your FlexMaster and SCG servers, and configure your SMTP settings.

4 In the Monitor page, verify that all services are Up.

Step 5: Import the SCI License FileThe SCI license includes the customer name and the number of licensed APs. It is deployed from the System Setup page. After deployment the SCI User Console will reflect the license data. If a license violation (more APs report stats than the license level), SCI will display a warning message informing you to either upgrade your license or reduce the number of APs reporting to SCI.

1 Go to the System Setup page.

2 In the Licensing section, click Choose File to select a license file to import.

3 Select the file and click Import License.

Congratulations! You have completed the SCI installation and basic setup proce-dures.

Quick Installation InstructionsStep 5: Import the SCI License File


Figure 3. SCI User Console login page

Full CentOS Installation InstructionsCentOS Installation


Full CentOS Installation InstructionsThis section describes how to install and configure a CentOS system to meet Ruckus Wireless' SmartCell Insight requirements. It is assumed that the reader has the knowledge to interact with the Linux command line in a basic manner, i.e. viewing and modifying configuration files.

CentOS InstallationSmartCell Insight was designed and tested against CentOS 6.4. Installation on RedHat Enterprise Linux 6.4 (which is compatible) is also supported with minor changes to the following instructions (such as the location of the RHEL RPM repository on the installation media).

Installation MediaThe CentOS 6.4 64-bit ISO can be downloaded from the following URL: http://mirrors.kernel.org/centos/6.4/isos/x86_64/CentOS-6.4-x86_64-bin-DVD1.iso

NOTE: If your installation platform is physical hardware (recommended for maximum performance), you will need to burn the ISO to a DVD medium. Do NOT extract the ISO and burn its files! Use your CD burning softwares "Burn CD/DVD Image" feature, and provide it with the ISO file. If your burning software does not have that feature, use a different software; If you extract the ISO and burn its content, you will get an un-bootable medium, which will not be to helpful when you want to install an Operating System.

Full CentOS Installation InstructionsCentOS Installation


If your installation platform is a VMware virtual machine, you can provide the ISO directly in the Virtual CD-ROM drive, by uploading it to the Datastore, edit the VM settings, click on CD/DVD drive, and select the radio button "Datastore ISO File", then click on Browse to locate the file you uploaded into the Datastore. Don't forget to check the "Connect at power on" checkbox:

After you have placed the installation medium in the server DVD drive or placed the ISO in the VM virtual drive, power on the server and begin the actual OS installation.

Full CentOS Installation InstructionsThe actual installation


The actual installation1 You'll be greeted with the CentOS installation multiple-choice menu below. We'll

use the default, first selection, so click Enter now:

2 After the installer starts, you'll be asked if you want to test the media:

3 The above can be safely skipped.



4 The CentOS installation wizard will now appear:

5 Click Next.

6 The installation language selection dialog will appear:



7 Please leave the default English (English), so you'll see the same things depicted in this guide. Click Next.

8 A keyboard layout selection dialog will appear:

9 Please leave the default U.S. English. Click Next.



10 A dialog asking for which type of storage we'll be using:

11 Since SmartCell Insight is designed for Directly-Attached-Storage only, leave the default Basic Storage Devices, and click Next.



12 A dialog asking if you would like to discard all data on the storage device may appear:

13 If the above dialog appeared, click Yes, discard any data.



14 A network setup dialog appears:

15 Fill in the desired host name for your SmartCell Insight server next to the Hostname: label (in the above screenshot, the sci-node-1 host name has been entered). You must NOT use the hostname 'localhost'!

NOTE: The host name of your server will be embedded in numerous places during SmartCell Insight installation, and will be assumed to be the machine's host name during the lifetime of the system; You may not change the host name after SmartCell Insight has been installed; therefore, Ruckus strongly advises that you carefully consider which host name you would like to use at this stage.



16 Next, click on the Configure Network button. The following dialog will appear:

17 Click on System eth0. Then the Edit button will not be greyed out any more:

18 Click Edit...



19 The following dialog will appear:

20 Mark the checkbox Connect automatically.

21 Then click on the tab IPv4 Settings:



22 The following dialog will appear:

23 Click on the Method box to list IPv4 addressing methods.



24 Select Manual. An Add button will appear:

25 Click on the Add button. You'll see an input box, with the cursor positioned below the Address column.



26 Fill in SmartCell Insight's IP Address, Network Mask and Default Gateway, like in the example above.

27 Then, fill in the DNS server(s). If you have more than one, separate them by a comma sign, like in the below example:



28 Then click on Apply... :

29 Then click on Close:



30 Then click on Next:

31 A time zone selection screen will appear. Select the time zone you are located in. You can either click/zoom on the map, or select from the drop-down box:



32 After you have selected your time zone, click Next.

33 The root password dialog will appear. root is the Linux super-user (the user that can do everything - so consider who you share it with...). You should select a GOOD password (small letters, CAPITAL LETTERS, numbers (0-9), and special characters (@#$%^&*()) for the root user, and enter it twice, as depicted below:

34 Then click Next.



35 The disk partitioning choice dialog will appear:

36 Select Create Custom Layout, and click Next.

37 An empty partition layout will appear:



38 Click on Create.

39 A partition type creation dialog will appear:

40 Select Standard Partition, and click Create.



41 The following partition creation dialog will appear:

42 Fill in:

Mount Point: /boot

File System Type: ext4

Size (MB): 100

43 Select:

Fixed size

Force to be a primary partition

Click on OK.



44 You'll return to the partition layout, and see your newly created partition:

45 Click on Create again.

46 A partition type creation dialog will appear again:



47 Select Standard Partition, and click Create.

48 The following partition creation dialog will appear:

49 Fill in:

Mount Point: /

File System Type: ext4

50 Select:

Fill to maximum allowable size

Click on OK.



51 You'll return to the partition layout, and see your two created partitions:

52 Click on Next.

53 A warning that we have not set up a swap partition will appear:



54 The above is normal. We do not need swap; This is the reason the minimal requirements of the server include 48GB of RAM.

55 Click Yes.

56 You may now receive a warning that data will be destroyed when formatting:

57 If you have received the above warning, click Format.



58 A final confirmation warning dialog, before destroying all data currently on the hard drive, will appear:

59 Click Write changes to disk.



60 Formatting phase will now run:

61 Then a bootloader configuration dialog will appear:



62 If you would like to modify the listed booted OS name when your server boots, you can click on the CentOS line as depicted above, and click on Edit, and enter a different name in the dialog that opens.

63 If you have changed the OS name, it will look like this:

64 Click on Next.



65 An installation profile selection dialog will now appear:

66 Select Minimal. Click Next.



67 Installation phase will now run, and install all the operating system packages:

68 After packages installation has finished, the Installation Complete dialog will appear:



69 Click on Reboot.

70 The server will be rebooted, and you will be greeted with the following login console:

71 You may login to the server by using the username root with the password that you selected during the installation. You may also SSH into the server with an SSH client (ssh root@sci-ip from another Linux, or with a Windows client like PuTTY or SecureCRT).

Once your CentOS operating system is installed according to these instructions, perform the SCI installation procedure as described in Quick Installation Instruc-tions on page 23.


3Navigating the SmartCell Insight User InterfaceIn this chapter:

Getting Familiar with the SCI User Interface

Interacting with Workspace Elements

Getting Familiar with the SCI User Interface


Getting Familiar with the SCI User InterfaceThe SmartCell Insight User interface consists of 6 main elements, as shown in Figure 4. For a description of each UI element, see Table 4.

Figure 4. SmartCell Insight Web interface elements

Table 4. SCI User Console Web interface elements

Number Description

1 Menu: Contains Logout, Refresh and Help menu items

2 Action icons:

Workspace: Open the My Workspace view, which shows reports that you have submitted to run in the background on the server. You can cancel reports that have not run yet or view or delete completed reports.

Toggle Browser: Toggle the Report and Files browser panels.

New Analyzer Report: Create a new analyzer report. Clicking this button launches the report creation view.

3 Tabs: Displays the windows that are currently open. Click the x icon next to a tab name to close the window.

1

4

5

3

6

2

Interacting with Workspace Elements


Interacting with Workspace ElementsThe Workspace is typically used for viewing and manipulating reports. Table 5 lists the tools you can use to produce, deliver and interact with reports displayed in the workspace.

Figure 5. Report workspace elements

4 Report browser panel: Use this panel to select which category of report to view.

5 Files browser panel: Use this panel to select the individual report to view in the workspace.

6 Workspace: This large area is used to display the report you are currently viewing, or to create and manage custom reports. See Working with Report files for more information.

Table 4. SCI User Console Web interface elements

Number Description

1 2

3

4 5

Interacting with Workspace ElementsScheduling Email Report Delivery for Custom Reports


Scheduling Email Report Delivery for Custom ReportsFor custom reports, you can schedule email report delivery using the Options pull-down menu from the Files browser panel.

To do so, use the following procedure:

1 Select the report for which you want to schedule email delivery from the Files browser panel.

2 Click the Options icon, and select Schedule....

3 In the New Report Schedule dialog that appears, enter an email subject in the Subscription/Subject field, and enter comma separated destination addresses in the Email To field.

4 Select Report Type (PDF, XLS or CSV) and Public Schedule.

5 Click Schedule to confirm.

Table 5. Report workspace elements

Number Description

1 Report overview

2 Export this report:

Print this report

Download as PDF file

Send this report by email

Schedule email delivery of this report (see Scheduling Email Report Delivery for Custom Reports for more information on custom report delivery)

3 Filters: Use the drop-down menus to filter the report contents by report-specific fields.

4 Graph: Select an area on the graph to zoom. Click Reset Zoom to reset.

5 Pie chart: Click a segment of the pie chart to view an exploded view with the selected segment detached.



Figure 6. Scheduling email report delivery for custom reports


4Using the Built-In ReportsIn this chapter:

Using the Built-In Reports

Report Statistics

Using the Built-In ReportsClient and Session Reports


Using the Built-In ReportsSCI comes with a number of built-in reports to help you get started quickly using a wide variety of common use cases for analyzing network capacity, traffic trends, client statistics and device inventories. The following key assessments can be made using the built-in reports:

Network capacity, carried traffic and utilization

User experience (getting on the network, connection speed - simple high/low/average & CDF views)

User activity (devices, applications, sessions, bandwidth)

SON behaviors (channel changes, meshing, band steering, load balancing, ATF)

Network operating conditions (interference sources)

Usual network mechanics (uptime, alarms, jitter, latency, etc.)

Capability to view stats at multiple layers (AP, radio, SSID) and session

The built-in reports are organized according to the following categories:

Client and Session Reports

Inventory Reports

Operational Reports

Traffic Reports

Client and Session ReportsClient and Session Reports include number of sessions, session duration, client device type and traffic volume of the most active clients.

Client FingerprintThis report provides a list of the manufacturers of the mobile devices on the Wi-Fi network along with their OS type during a specific time interval.

Examples of how this report could be used by network administrators: Used to identify the device types on the Wi-Fi network.



Figure 7. Client Fingerprint report

First Experience of New ClientsThis report displays statistics about the user experience of the first connection for new clients, including average session duration, noise floor, RSSI and potential throughput.

Examples of how this report could be used by network administrators:Some service providers have conducted studies which show that if the users first experience is good, then the user tends to return and remain as a customer in the long run. Therefore, if metrics show a correlation between session duration and signal strength for new subscribers, then SCI can analytically predict where low RSSI will lead to customer satisfaction issues.

Notes: A new subscriber is one in which this report is for the first time they were observed

associated to the WLAN. SCI keeps a database of MAC addresses and detects the existence of statistics for new mobile devices, not in the database. Mobile devices thus detected are then selected for inclusion into the CSV file based on being joined to a particular controller, AP, AP group, SSID or radio.



Each record in the CSV file contains the mobile devices MAC address, authen-tication time, association time, session end time, client throughput, SNR+RSSI statistics and serving AP.

APs measure the SNR and noise floor on frames received from associated STAs. That is, uplink SNR is measured; downlink SNR is not reported by STAs nor is it estimated (in SCIv1.0) by APs. From these measurements RSSI is computed as RSSI (dBm) = SNR (dB) + NFE (dBm), where NFE = a noise floor estimate produced by the Wi-Fi silicon. Note that while the SNR measurement is quite accurate, the NFE is an uncalibrated estimate; the manufacturing process does not provide NFE calibration data due to cost reasons. Therefore, the error in the RSSI value can be significant (several dB).

Ruckus APs use BeamFlex technology. Indoor Ruckus APs employ omni-directional BeamFlex antennas (which can be controlled by BeamFlex algorithms to have omni-directional or directional patterns). Outdoor APs can have either omni-directional or directional antennas. The N SKUs have two 30 beamwidth directional antennas and do not use BeamFlex technology; the gain of a single, 30 beamwidth antenna is ~11dB greater than an omni-directional antenna. The S SKUs have two or three ~120 sector antennas and employ BeamFlex technology; each sector antenna has a gain ~5dB higher than the gain of an omni-directional antenna. Therefore for given set of link conditions, different SKUs will produce different RSSI values.

BeamFlex algorithms cause each AP antenna to have an approximately omni-directional pattern when receiving Wi-Fi signals. However, when transmitting Wi-Fi signals, the BeamFlex algorithm will typically control the antennas to have a directional pattern, producing several dB of gain compared to an omni-direc-tional pattern. Thus, the antenna gain in the downlink direction is typically different/higher than in the uplink direction. In addition, Ruckus APs usually have a higher transmitter power capability than STAs. The combination of higher transmitter power and higher antenna gain means that the received SNR at the STA (downlink direction) will typically be 3-6 dB higher than at the AP (uplink direction). This typically results in higher PHY rates in the downlink direction than in the uplink direction. In terms of user experience, higher downlink RSSI is better for the user because for many web services, the perceived quality is based on the time waiting for web pages to arrive.



Figure 8. First Experience of New Clients report

Number of SessionsThe Number of Sessions report displays sessions per radio over time, authenticated vs. associated clients, and session distribution per radio (2.4 GHz vs. 5 GHz).

Examples of how this report could be used by network administrators: Used to analyze the number of devices on the network at any given time. Can

be applied to network dimensioning, looking at possible revenue (e.g., from LBS or advertising), etc.

Notes: The definition of a session, including when a session begins and ends, is provided

in Report Statistics on page 85.

A user may have multiple devices on the network, e.g., an iPhone and iPad. In this case, the number of sessions would be reported as 2 (devices), not 1 (user).

A user may have one device on the network at two different times (e.g., from 1:03pm to 1:08pm and 2:25pm to 2:45pm). In this case, the number of sessions would be reported as 2 (sessions), not 1 (user).



Figure 9. Number of Sessions report

Number of Unique ClientsThis report displays the total number of unique subscriber devices during a specific time interval.

Examples of how this report could be used by network administrators: Used to analyze the number of unique subscriber devices using Wi-Fi. Can also

be used in conjunction with other reports to determine average number of devices/subscription.

Notes: A mobile device can associate to the WLAN during different time intervals and

thus have multiple sessions. The devices MAC address is used to bind these multiple sessions together.



Figure 10. Number of Unique Clients report

Session Bytes TransferredThis report shows cumulative unicast traffic volume transmitted to or received by VAPs from STAs whose sessions begin and end during a specific time interval. In addition, the report shows a CDF of cumulative session traffic.

Examples of how this report could be used by network administrators: Track the session usage to determine how much traffic and where users are

consuming data.

Notes: Included in session bytes are the number of bytes in successfully transmitted

MSDUs. For further details, refer to the descriptions of tx-msdus and rx-msdus in Table 6.



Figure 11. Session Bytes Transferred report

Session DurationThis report is a cumulative distribution function (CDF) of the mobile devices session durations that exceed a user-specified duration which occurred during a given time interval. The session duration length is defined by the user.

Examples of how this report could be used by network administrators: Used to analyze how long users are on the network. Service delivery can then

be optimized accordingly.



Figure 12. Session Duration report

Top Clients by Traffic VolumeThis report shows top N mobile devices having the greatest cumulative unicast traffic volume transmitted to or received from a VAP during a specific time interval.

Examples of how this report could be used by network administrators: Track the high-volume users, identify their subscriptions and potentially target

for throttling or band steering.

Discover natural break points in usage patterns. Make consequent future subscription price adjustments or set data caps.



Figure 13. Top Clients by Traffic Volume report

Using the Built-In ReportsInventory Reports


Inventory ReportsInventory reports consist of AP, Controller and Session inventories.

AP InventoryThis report shows the list of all currently reachable APs in the Wi-Fi network connected to a ZD or SCG (see note) controller during a given time interval.

Examples of how this report could be used by network administrators: Used to ensure all the APs in the network are administratively and operationally

online and enabled.

Notes: The following data is included in the report for each AP: name, serial number,

model type (e.g., ZF-7962), MAC address, IP address, external IP address, IPv6 address, last connection time, connected controller, location (string), latitude/longitude (if available) and uptime.

The SCG version of this report will be provided in a future release.

Figure 14. AP Inventory report



Controller InventoryThe Controller Inventory report displays the currently reachable controllers in the Wi-Fi network.

Examples of how this report could be used by network administrators: Used to ensure all the controllers in the network are administratively and

operationally online and enabled.

The following data is included in the report for each controller: name, SW version, MAC address, IP address, unique clients, connected APs, number of licenses and maximum license utilization.

Notes: The SCG version of this report will be provided in a future release.

Figure 15. Controller Inventory report

Session InventoryThis report is a CSV file which provides a session log for a set of mobile devices during a given time interval.



Examples of how this report could be used by network administrators: Used to analyze usage statistics using SP defined method; method takes CSV

file as input.

Notes: Each record in the CSV file contains the mobile devices MAC address, device

type, OS type, authentication time, association time, session end time, down-stream / upstream bytes transferred and serving AP.

Mobile devices are selected based on being joined to a particular controller, AP, AP group, SSID or radio.

Figure 16. Session Inventory report

Using the Built-In ReportsOperational Reports


Operational ReportsOperational Reports provide information on system operation statistics, such as AP response time, controller hardware resource utilization, and top 10 lists of AP reboots and topology changes.

AP Response TimeThis report shows the ping latency between the SCI and an AP during a specific time interval.

Examples of how this report could be used by network administrators: High latency and missing ping responses between the AP and SCI can be used

to identify congested links or overloaded/mis-configured switches/routers.

In mesh networks, it could be used to identify overloaded mesh APs perhaps indicating areas having sub-optimal mesh topology.

Notes: Ping latency measured between AP and SCI was used due to the lack of a ping

server on the SCG. Note: the SCI may not be on the normal data path taken by user traffic to/from a destination network. Therefore, this statistics relevance may be limited for some deployments.

Figure 17. AP Response Time



Controller Hardware UtilizationThis report shows a ZD or SCG (see note) controllers CPU, memory and disk utilization during a specific time interval.

Examples of how this report could be used by network administrators: Used to predict when a controller will no longer have sufficient processing

resources to adequately handle all its joined AP and users.

Used to identify a SW bug (e.g., memory leak or bug causing high cpu utilization).

Notes: The SCG version of this report will be provided in a future release.

Figure 18. Controller Hardware Utilization report

Top AP RebootsThis report shows which APs have been administratively or autonomously rebooted the most during a given time interval.

Examples of how this report could be used by network administrators: Used to identify APs having hardware or software defects.

Used to identify APs succumbing to attackers.



Figure 19. Top 10 AP Reboots report

Top APs with Most Topology ChangesThis report shows which mesh APs had the most topology change events during a given time interval.

Examples of how this report could be used by network administrators: Used to identify mesh APs having deployment issues needing remediation.



Figure 20. Top APs with Most Topology Changes

Top APs with the Longest Response TimeThis report shows the APs having the greatest ping latency between themselves and the SCI during a specific time interval.

Examples of how this report could be used by network administrators: Identify paths in the wired/wireless network having performance problems.

In mesh networks, identify mesh APs having excessive interference or supporting too many downlink mesh APs (e.g., poor mesh topology).



Figure 21. Top APs with the Longest Response Time report

Using the Built-In ReportsTraffic Reports


Traffic ReportsTraffic Reports consist of actual AP and client throughput reports as well as client throughput potential and top APs by traffic volume.

Access Point TrafficThis report provides the cumulative volume of unicast traffic transmitted to or received from mobile devices associated to any WLAN on a physical AP for a specific time interval. Note that the reported traffic is actually traffic density (traffic/time); the value of the traffic reported is scaled to the time dimension on the x-axis of the graph (e.g., traffic/15-min, traffic/hour, traffic/day).

Examples of how this report could be used by network administrators: How busy the AP is with traffic to/from users (includes unicast/multicast packets)

How much traffic is uploaded vs. downloaded

Find network locations which are the busy areas.

Notes: Data used to create the report includes STA session statistics from all VAPs

configured on a [physical] AP.

Includes both 2.4- and 5-GHz radios (if present) on an AP.

Includes backhaul traffic for a mesh AP.

Includes the following traffic:

IP datagrams carrying application traffic.

Non IP, layer-3 packets.

Includes network-layer management traffic a STA needs to access network resources (e.g., DHCP, ARP, DNS, FTP, IGMP, SIP, etc.).

Includes data link layer traffic above the 802.11 MAC (e.g., 802.1 frames such as LLDP (802.1ab)).

Does not (in version 1.0) include controller management traffic, multicast and broadcast traffic.



Figure 22. Access Point Traffic report

Client Potential ThroughputThe Client Potential Throughput report displays the saturated RF channel capacity between an AP radio and given STA. The saturated throughput can be thought of as the throughput an AP would achieve if there were a continuous stream of data for only this STA given the achievable over-the-air PHY layer data-rate and the local interference environment on the RF channel.

Examples of how this report could be used by network administrators: The report can be used to determine how much capacity is available to

subscribers at that location at that time of day. If throughputs are low in a given area (i.e., group of APs), it can indicate there is foreign interference present or too much 802.11 interference. The 802.11 interference could come from surrounding ESSs (i.e., not the ESS being analyzed by SCI) or self interference. Too much self interference could be the result of a poor channel plan or a difficult deployment area.

The report can be used to see if there is sufficient bandwidth available to subscribers and if the numbers are low, perhaps its a candidate for adding additional APs or moving the location, etc.



Figure 23. Client Potential Throughput report

Throughput Estimate of ClientsThe Throughput Estimate of Clients report displays the devices with the greatest cumulative unicast and multicast traffic volume transmitted to or received during a specific time interval. The data is represented as a Cumulative Distribution Function (CDF).

Examples of how this report could be used by network administrators: Provides a measure of network performance by identified the top throughput

speeds possible for users.

Can be used in conjunction with Client Fingerprint report to determine the best performing mobile devices in the WLAN.



Figure 24. Throughput Estimate of Clients report

Top APs by Traffic VolumeThis report shows the physical APs having the greatest cumulative volume of unicast traffic transmitted to or received from mobile devices associated to any of its WLAN during a specific time interval. Note that the reported traffic is actually traffic throughput (traffic/time); the value of the traffic reported is scaled to the time dimension on the x-axis of the graph (e.g., traffic/15-min, traffic/hour, traffic/day).

Examples of how this report could be used by network administrators: Find the busiest APs and locations in the network.

Report StatisticsTraffic Reports


Figure 25. Top APs by Traffic Volume report

Report StatisticsThe generation of each of the reports described in the previous section requires statistics aggregated on ZD, FM or SCG. A mapping of the statistics needed for report generation is provided in Table 6. Each metric in the table is given a unique name; by carefully tracking unique names throughout this table, the user can determine the exact source of data used in the generation of the report.

Table 6. Mapping of ZD and SCG Statistics to SCI Reports

No. SCI Report ZD Aggregated Statistics SCG Aggregated Statistics

1 AP traffic vap > interval-stats > tx-bytes, rx-bytes

Note: the following data does not seem to be used in the report despite the requirements: tx-mgmt-bytes, rx-mgmt-bytes

report > bin > radio > wlan > rxDataBytes_r, txDataBytes_r



2 Top APs by Traffic Volume

vap > interval-stats > tx-bytes, rx-bytes

report > bin > radio > wlan > rxDataBytes_r, txDataBytes_r

3 AP Response Time No ZD statistics are used for this report; statistics are SCI generated only.

No SCG statistics are used for this report; statistics are SCI generated only.

4 Top APs With The Longest Response Time

No ZD statistics are used for this report; statistics are SCI generated only.

No SCG statistics are used for this report; statistics are SCI generated only.

5 Session Bytes Transferred

client > interval-stats > tx-bytes, rx-bytes

ueSession > txBytes, rxBytes

6 Top Client Traffic Volume

client > interval-stats > tx-bytes, rx-bytes

ueSession > txBytes, rxBytes

7 Client Session Potential Throughput

client > interval-stats > throughput-est

ueSession > throughputEst

8 Client Potential Throughput

client > interval-stats > throughput-est

ueSession > throughputEst

9 First Experience of New Subscribers

session > session-sta > rssi, max-rssi, min-rssi, first-rssi, received-signal-strength, max-received-signal-strength, mini-received-signal-strength, first-received-signal-strength, noise-floor, associated-time, authorized-time, end-time, ap, ssid, vap-mac, radio-type, user

ueSession > rssi, firstRssi, maxRssi, minRssi, sessionID, multiSessionID, received-signal-strength, max-received-signal-strength, min-received-signal-strength, first-received-signal-strength, noisefloor





10 Number of Unique Subscribers

client > associated-time, authorized-time, end-time, acct-session-id, acct-multi-session-id, ap, ssid, vap-mac, radio-type

ueSession > firstConnection, authorizedTime, disconnectedTime, disconnectReason, sessionID, multiSessionID

Client > sta > clientMac

Client > radio > mode

11 Client Fingerprint client > user, hostname, vlan, dvcinfo, associated-time, authorized-time, end-time, disconnect-reason

ueSession > firstConnection, authorizedTime, disconnectedTime, reason, user, hostname, vlan, dvcInfo, disconnectReason

For manufacturer: check client's OUI in MAC address

12 Number of Sessions client > associated-time, authorized-time, end-time, acct-session-id, acct-multi-session-id, ap, ssid, radio-type, ap, ssid, vap-mac, radio-type




13 Session Duration client > associated-time, authorized-time, end-time, acct-session-id, acct-multi-session-id, ap, ssid, radio-type, ap, ssid, vap-mac, radio-type








14 Session Inventory client > interval-stats > tx-bytes, rx-bytes

ueSession > firstConnection, authorizedTime, disconnectedTime, reason, user, hostname, vlan, dvcInfo

15 Controller HW Utilization

Not available

16 Controller Inventory FlexMaster database Not available

17 AP Inventory Not available

18 Top AP Reboots FlexMaster database AP state events: 301, 302

19 Top APs with Most Topology Change Events

FlexMaster database: MSG_LAP_downlink_MAP_connected, MSG_LAP_downlink_MAP_disconnect, MSG_MAP_downlink_connected, MSG_LAP_downlink_MAP_disconnect, MSG_MAP_downlink_connected, MSG_MAP_root_downlink_connected

Monitor mesh events: 405, 406, 411, 412, 413, 414, 416




5Configuring Custom ReportsIn this chapter:

Overview of Custom Report Creation

Creating a New Report

Available Metrics

Overview of Custom Report Creation


Overview of Custom Report CreationThis chapter describes the procedures for creating custom reports using the New Analyzer Report feature. This feature allows you to query the data in a database without having to understand how the database is structured. You can drill down into the data to discover details that may help you make important business decisions. The Analyzer presents data multi-dimensionally and lets you select which dimensions and measures you want to explore.

The Report Analyzer is an interactive data analysis tool that provides you with a rich drag-and-drop user interface that makes it easy for you to create reports quickly based on your exploration of your data. Once your new report is created, you can display reports in a dashboard to make them available for other users.

To enter the New Analyzer Report creation interface and begin creating a new report, simply click the New Analyzer Report icon on the dashboard.

Figure 26. New Analyzer Report icon

Creating a New ReportChoosing a Data Source


Creating a New ReportCreating a new report consists of the following steps:

1 Choosing a Data Source

2 Adding Fields and Filters

3 Adding a Description

4 Changing the Chart Type

5 Adding a Description

6 Saving the Report to a Shared Folder

Choosing a Data SourceTo create a new blank report from scratch, complete the following steps:

1 Click the New Analyzer Report icon ( ) to open the Select Data Source dialog box.

2 Choose a Data Source which consists of a schema and data set from the list box in the Select Data Source dialog box. This choice determines which fields will be available when you build your report. For example, if you selected a data source called AP Statistics, all AP-related fields (e.g. number of APs) would be available.

3 Click OK to continue.

Creating a New ReportChoosing a Data Source


Figure 27. Select a Data Source

About Data SourcesEach report must use a single Data Source. The following built-in data sources are available:

AP Response Statistics: Includes measures such as packets transmitted, packets lost percentage, ping total time, minimum, maximum, average and deviance.

AP Statistics: Includes measures such as number of APs, Tx data bytes and Rx data bytes.

Client Complete Sessions: Includes measures such as number of sessions, number of unique clients, session length, Tx and Rx data bytes.

Client Session Intervals: Includes measures such as estimated throughput, maximum/minimum signal strength and RSSI, number of sessions and number of intervals.

Controller Resource Utilization: Includes measures such as CPU, memory and disk usage percentages.

Controller Statistics: Includes measures such as client count, license count and license utilization.

Events: Includes measures such as number of events.

Creating a New ReportThe New Analyzer Report Page


More about Data Sources: Each report is tied to one Data Source.

You cannot change the Data Source for a report.

Many Data Sources have overlapping fields. For example, the AP Model field exists in multiple Data Sources. Therefore, there could be more than one data source that would work for the report that you want to generate.

The reason you are asked to choose a Data Source before you add fields is that certain fields don't work well together, and using them in the same report leads to incorrect or confusing results. Therefore, Data Sources bundle the appropriate fields together so that your report will make more sense.

The New Analyzer Report PageOnce you have chosen a Data Source, the New Analyzer Report page appears. Figure 28 identifies the main sections of the New Analyzer Report page, and each of these page elements is described in Table 7.

Figure 28. The New Analyzer Report page

1

2

3

4

Creating a New ReportThe New Analyzer Report Page


Action IconsTable 8 describes the Action Icons available from the New Analyzer Report page.

Table 7. New Analyzer Report page elements

Number Description

1 Available Fields: Choose which fields to include in your report. You can drag fields to the Layout section, drag them directly onto the Report Preview.

2 Layout: Use this section to define the layout of your report.

3 Action Icons: See Table 8 for Action Icon descriptions.

4 Report Preview: Displays the actual report as it is currently defined.

Table 8. Action Icons

Icon Description

Save icon

Save as icon

Undo icon

Redo icon

Hide/show Available Fields icon

Hide/show Layout panel icon

Hide/show Filters icon

Disable/enable Auto refresh icon

More Actions and Options icon

Creating a New ReportAdding Fields and Filters


Adding Fields and FiltersOnce you are on the Analyzer Report page, you are ready to add fields and filters. You can do this in any order, but here is a good way to get started:

1 Drag a Time Period field (such as Year or Quarter) onto the report.

2 Add a Measure field (such as Number of Sessions, etc).

3 Click the Time Period field on the report, and select Filter from the menu. Choose the time periods you are interested in from the Filter dialog box.

NOTE: You can view the definition of a field by clicking on the field and selecting Tell me About... from the menu.

NOTE: Reports make the most sense when they display at least one measure field. (Measure fields are highlighted blue.)

NOTE: Add filters early on. To get the best response time and avoid too much data being displayed, add filters before you drag too many fields onto the report. For example, if you already have two or three fields in the report and you want to add another field that you suspect has hundreds or thousands of values, add a filter to this field before you add it to the report.

Creating a New ReportAdding Fields and Filters


Figure 29. Adding fields and measures

About FieldsExamples of Fields include "AP Model," "SSID," "OS Type," etc. Fields are what define the content of your report.

The following types of fields are available:

Level Fields (Names, Types, Categories, etc.): Level fields are usually text-based. OS Type is an example of a Level field. Android and Windows 7/Vista are examples of possible values for the OS Type field.

Time Period Fields: Year and Month are examples of Time Period fields. Possible values for these fields could be 2012 and Jan-2011, respectively.

Measure Fields: Measure fields are numeric and most often represent Access Point, client or controller metrics. Number of Unique Clients and Tx Data Bytes are examples of Measure fields.

Fields are color-coded by type in both the report and the Available Fields panes. The colors are assigned as follows:

Level Fields and Time Period Fields: Orange

Measure Fields: Blue

Creating a New ReportSwitching to Chart Format


Viewing the Definition of a FieldComplete the following steps to view the definition of a field:

1 Right-click the field name (in the report or in the list of available fields).

2 Select Tell me about... from the menu to open the About... dialog box.

The About... dialog box provides the following information:

Name: The name of the field as it appears in this report.

Type: The type of field. For more about field types, see About Fields on page 96.

Description: The description of the field.

MDX: The data source definition. For example, for the Controller Model field, the MDX value is [Controllers].[Controller Model].

Member Properties*: Certain fields contain member properties that can be used to constrain membership to specific values based on these properties.

NOTE: If a field has a number in parenthesis next to its name the field list, this means it has member properties associated with it. You can constrain the data displayed according to one or more of these member properties by selecting Show Properties from the drop-down menu of a field after dragging it onto the Layout pane.

Switching to Chart FormatBy default, new reports are displayed in table format according to the fields and layouts (rows and columns) that you selected. You can easily switch from table format to any of several chart formats by clicking the Chart Format icon.

Creating a New ReportChanging the Chart Type


Figure 30. The Chart Format icon

Changing the Chart TypeClick the Choose Another Chart Type icon and select a chart type from the list.

Figure 31. Choose another chart type

Creating a New ReportApplying Filters to Reports


Applying Filters to ReportsIf your report contains a large amount of data, it is a good idea to apply filters before you add too many additional fields and measures. Click the blue + icon (next to No filters if there are no filters applied so far).

Figure 32. Click the + icon to add a new filter

When you click the + icon to add a filter, the screen changes to display an area with the label To add a new filter, drag a field from the Available Fields to this area.



Figure 33. Drag a field to this area to add a new filter

For example, if you want to filter for only 2.4 GHz clients, drag the Frequency field to the add filter section. A Filter on Frequency dialog appears, from which you can select which values you want to filter for.

Select 2.4G from the list, and click the right arrow icon to add it to the filter list. Then click OK to confirm.



Figure 34. Add the 2.4G value to filter results for only 2.4G clients

After the filter is applied, you can see which filters are applied in the updated chart view.

Figure 35. Frequency includes 2.4G

Creating a New ReportAdding a Description


Adding a DescriptionA description of your report will help other users understand it. Complete the following steps to add, edit, or view a description of a report.

1 Open the report.

2 Click the More actions and options icon on the toolbar and select About this Report

3 Use the Description field to add, edit, or view the report description.

NOTE: You also can view the description on the Report Home page by clicking the Information symbol (i) next to the report.

Figure 36. Select About this Report... from the More Actions list

Creating a New ReportAdding a Description


Figure 37. Click the Edit icon to edit the report description\

Figure 38. Type your report description in the text box

Creating a New ReportSaving the Report to a Shared Folder


Saving the Report to a Shared FolderTo let other users access a report you create, save your report into a shared folder. In this example, we will save the new report to the existing Ruckus Reports folder.

1 Click the Save Current Report icon.

2 The Save dialog opens. Enter a recognizable name for this report. In this example, we created a report called OS Type by Day.

3 Browse to your preferred destination directory. In this example, we saved the report in the existing /ruckus-reports/subscriber-and-session folder.

4 Click Save to save your report.

Figure 39. Enter a filename for your report

Available MetricsSaving the Report to a Shared Folder


Figure 40. Save the report to the Subscriber and Session folder

Available MetricsThe following table lists the metrics available for report creation. You can create reports for any combination of these metrics, and filter results by any of the values that exist within each metric for each available data source.

Table 9. Available metrics

Category Metric

AP Stats AP Name, MAC, Description, Serial Number, GPS

Controller Name & MAC

# APs

Tx & Rx bytes



AP Response AP Name, MAC, Description, Serial #, GPS

Min, Max, Avg response time

Deviance

% Packets Lost

Tx & Rx Packets

Ping Total Response Time

Controller Controller Name & MAC

Client Count

License Count

License Utilization

Controller Resources CPU Util %

Disk Usage %

Mem Usage %

Client Sessions AP Name, MAC, Description, Serial #, GPS


Client Hostname & Username

# of sessions

# of subsessions

# of unique clients

Session Length

Tx & Rx bytes

Events AP Name, MAC, Description, Serial #, GPS


Number of Events


Category Metric



Client Session Intervals AP Name, MAC, Description, Serial #, GPS


Client Hostname & Username

Estimated Throughput

Min, Max RSSI

Max, Min Signal Strength

Noise Floor

Number of Intervals

Number of Sub-Sessions

Tx & Rx Bytes


Category Metric


6Managing the SmartCell Insight SystemIn this chapter:

Setting Administrator Preferences

Changing the Administrator Password

Adding a FlexMaster Reporting User for SCI Reporting

A note about adding SCG to SmartCell Insight

SCI Uninstall Procedure

SCI Backup & Restore

SCI AP Grouping

Uploading an SCI License

System Timekeeping

Using the Enterprise Console

Setting Administrator PreferencesAccessing the Administration Interface


Setting Administrator PreferencesThis section describes the settings and procedures used to configure administrator preferences, such as setting the admin user name and password, configuring data sources, data purge settings and SMTP settings.

Accessing the Administration InterfaceMany administration tasks can be performed through the administration interface. To access the administration interface, point your browser to: http://[SCI-IP-address] (without a port number), and enter your administrator user name and password.

NOTE: If you have not yet changed the default admin password, a warning message appears each time you access an admin interface page, prompting you to change the default password. See Changing the Administrator Password on page 127 for instructions on changing the admin password.

Getting Familiar with the Administration InterfaceThe administration interface consists of the following three pages:

Monitor Page

System Setup Page

Diagnostics Page

Monitor PageThe Monitor page displays currently configured SCI data sources, and provides options for deactivating/reactivating a data source, and enabling/disabling SCI > AP Reachability Tests. The Monitor page contains the following sections:

SCI Sources: Displays the data sources that have been configured from the System Setup page.

General Information: Includes services status and system information including OS version, system resources and uptime.

SCI Data SourcesThis section displays a list of the data sources configured from the System Setup page. Table 10 describes the information provided for each data source.

Setting Administrator PreferencesMonitor Page


Deactivating a Data SourceTo deactivate a data source, use the following procedure:

1 Locate the SCI System Name that you want to deactivate, and click the deactivate link on the same line.

2 The page refreshes and a confirmation message appears.

NOTE: Deactivating a system will not stop active data fetches, if there are any in progress; only future data fetches will be deactivated. SCI fetches data every 15 minutes from each data source.

Table 10. SCI Data Source information items

Item Description

SCI System Name The Name of the FM or SCG data source.

FM DB Host The IP address of the FM server.

FM DB Port The Port number of the FM server.

FM DB User The user name of the FM user account used to access the FM server.

FM DB Name The name of the FM database.

SCI > AP Reachability Tests Displays whether the Reachability Tests are enabled. This feature gathers data for a special SCI report (AP Response Time) that SCI measures by itself. This feature is only effective if the APs are reachable (i.e., they are not behind NAT, from the SCIs perspective in the network).

SCG Control Plane Nodes MGMT IPs

The Management IP address of the SCG Control Plane.

SCG User The SCG User name.

Status Displays OK if the data source is currently reachable by SCI, or Disconnected if the data source is currently unreachabl

Documents

Sci 1.0 User Guide - Lcs - 20131218