Test Procedure and Plan

(1)

This document contains proprietary information of MSA and is provided upon the condition that the information contained herein will be held in confidence and will not be duplicated or disseminated to others, in whole or in part, without the written permission of MSA.

1

Aruba WLAN, ClearPass & AirWave Deployment

WLAN Test Procedure

&

Test Plan

(2)

2 Aruba Architecture for “Company”

WLAN

Controllers & IAPs

SSIDs:

Voyager

– PEAP-TLS - Primary Employee

Openspace

– Guest Access and Device Registration/Provisioning

0nb0ard

– EAP-TLS For onboard devices.

1p3t

– WPA2-PSK - Used for Cisco Phones – WPA2

Enterprise

– 802.1x WEP – Old Employee SSID, to be decommissioned

NCC

-1701 – MSCHAPv2 – Old Employee SSID, to be decommissioned

CLEARPASS

– SJ & Japan – functions:

TLS Certificate based authentication to active directory.

Guest sponsored registration, and filtered lookup to “Company” ADAM box.

Device registration at web portal pages.

Specific role-based authentication to controller by device-type

AIRWAVE

– SJ & Japan

(3)

(4)

4 WLAN turn-up Tuning /Optimization /Testing for Aruba WLAN

1. WLAN turn-up, tuning, optimization

Required Equipment & SW Laptop for configuration Laptop Win XP & 8.1 Droid

MAC OSX & IOS iPad & iPhone Representative Devices to fully test Integrated

System & all AAA cases with ClearPass

Pre-requisites AP Layout, with AP Names,

Certified

Table of AP MACs, Names Certified As Built of APs Locations /Names as installed at by cabling Vendor

# Detail Notes /Issue Owner Time/Date Status 1.1 Confirm LAN LLD

Implemented “Company”

1.2 Confirm Management VLAN & IP

Structure

“Company” 1.3 Confirm DHCP Server

functionality “Company”

1.4 Confirm Controllers Racked, Stacked,

Power on, Connectivity

“Company” 1.5 Add Initial Controller config

details in turn on sequence

MSA 1.6 Load “Company” Base Config

to Controller

MSA 1.7 Add Specific LLD parameters

for this

location & LAN to Controller from

LLD

MSA

1.8 Set up designed redundancy

And Master Controller MSA

1.9 Confirm APs Groups and RF Profiles

are added for this location

MSA 1.10 Add Test APs to local access

switch ”Company”

1.11 Confirm test APs home to Controller

with DHCP Server

MSA 1.12 Confirm Test APs provisioned

and

fully functional in controller

MSA 1.13 Confirm VLAN Connectivity of

Controller to LAN Switch Core MSA

1.14 Confirm Controller FireWall

(5)

5

1.15 Confirm DHCP /DNS for

Client Devices

MSA 1.16 Perform Fail-over Tests of

Controller

With all SSIDs operational

MSA 1.17 Perform individual device tests,

on all

SSIDs through Test APs

MSA/”Company” 1.18 Set up iPerf Server with 1G

wired connection

”Company” 1.19 Perform iPerf Testing through

Test

APs. These Laptops will be used for

audit during WLAN turn-up

MSA

1.20 Perform Testing with all other device

types –for Internet & functions

MSA

IAPs

2. IAP WLAN turn-up, tuning, optimization

CLI program like “putty” Or Browser for Web Interface With CLI access to NIC Aruba Utilities

# Detail Notes /Issue Owner Time/Date Status

2.1 Prime IAP Access and “Company”

2.2 Load “Company” Config &

confirm other IAPs installed MSA

2.3 Populate Config to other IAPs

locally MSA

2.4 Add Specific LLD parameters

for this location & LAN MSA

2.5 Confirm IAPs Groups and RF Profiles

are available for this location, & Set up

in AirWave.

MSA

2.6 Allow fully functional IAPs to

settle MSA

2.7 Attach Testing Droid with Aruba Utilities to AirWave, so it can pull down floor-plan and show channel and power settings while testing

MSA

2.8 Walk floors, with Laptops and Droids running Aruba Utilities and analyze RF levels and

(6)

6

Roaming performance as

previously described 2.9 Make Max & Min RF Profile

adjustments for each frequency from findings and allow to settle again

MSA

2.10 REPEAT as required, document

all changes and iterations MSA

2.11 RF profile should now be OPTIMAL for location and device types

MSA

2.12 Allow WLAN to settle MSA

2.13 Check SSIDs operational and devices available for individual device tests, through Test Aps Voyager Openspace 0nb0ard 1p3t Enterprise NCC-1701 Mac OSX

Windows XP and Windows 8.1 IOS iPads & Phones Android Tablet & Phones

MSA/”Company”

2.14 Set up iPerf Server with 1G

wired connection “Company”

2.15 Perform iPerf Testing through Test APs. These Laptops will then be used at audit portions of the site during WLAN turn-up

MSA/”Company”

2.16 Perform Testing with all other device types –for Internet & functions

(7)

7 ClearPass Integration

3. ClearPass integration to Controller

3.1 Set Controller config to use

ClearPass MSA

3.2 Check all Roles and Config

details set MSA

3.3 Use test APs to check all ClearPass Functionality OnBoarding

TLS Certificate based authentication to active directory.

Guest sponsor registration and filtered lookup to “Company” ADAM box. Device registration landing pages. Specific role-based authentication to controller by device-type With each appropriate SSID Voyager Openspace 0nb0ard 1p3t Enterprise NCC-1701

Each with all representative devices in testing sample Mac OSX

(8)

8 AirWave Integration

4. AirWave Integration with Controller

4.1 Confirm any required Network

FireWall Ports open “Company”

4.2 Set Up Controller to send AirWave its Polled and AMON data

MSA 4.3 Check Controller that it is

reporting to AirWave for Master & Local Normal + AMON

MSA 4.4 Add AW (Server) IP &

Community String MSA

4.5 AMON review if is enabled

show mgmt-servers MSA

4.6 To enable AMON config t

mgmt-server type amp primary-server <IP

ADDRESS of AMP Server> profile

default-amp exit write mem

MSA

4.7 Check FireWall Visibility

show firewall-visibility status MSA

4.8 To enable FW Visibility config t firewall-visibility exit write mem MSA

4.9 Add to correct Aruba Controller

& AP Groups in AIRWAVE MSA

4.10 Create site Folder in AIRWAVE MSA

4.11 Enter Floor-Plans, locate and

name APs in AIRWAVE MSA

4.12 Check and Confirm Data is populating in AirWave from Controller and Test APs

(9)

9 Targets for Performance Results and Testing

Aruba WLAN RF Levels & Range of AP individual coverage

The general level of RF coverage goal is -50 dBm to -55 dBm levels for ~.ac (likely

- 55 to -60dBm on Droids). Take note about receive sensitivity comments below!

Individual APs “cells” goal is for well-defined and localized coverage for each AP

to maintain devices on high MCS rates. Then as you move away roaming is

promoted for devices so again they maintain high rates and transition to other APs

before degrading service by sticking to an AP for too long.

In a discrete location, several APs offer excellent coverage at graduated power

levels (-5 to -10dBm lower each) on orthogonal channels, so load can be shared

between adjacent APs.

Power settings – all devices types will be used, laptops tablets & phones, all devices

have different transmit & receive sensitivities, so tablets and phones can register

received level -5 to -10dBm lower than PCs. AP power will look to mirror or be

lower than the medium device – here a Tablet @ +12 to +15dBm Tx Power.

Roaming

As a computer /device moves and transitions away from an AP, it needs to change to a new

AP which now is closer and has a stronger signal to maintain the best PHY and Data rates for

throughput and performance.

Devices should roam as they move 2-3 APs away on a well optimized network.

Note: as a device roams on a ~.1x WLAN a re-auth is required.

Initial Tuning after Turn-on

AOS Systems and Dashboard Review

After APs have been turned on and allowed to settle for a short period, initial

AOS Dashboard metrics should be reviewed. These reviews are the power levels

APs are settling at, the channel choices APs are making for 2.4 & 5

GHz frequencies, and AP statistics such as channel busy, noise floor and other data

in there.

These metrics and Client data are reviewed in the AOS Dashboard throughout the

Tuning Cycle.

(10)

10 WLAN Floor Power Levels, RF Propagation and Client Review

Next an initial device walks of WLAN are performed – with Laptops, Tablets and

Phones.

These walk-throughs review the WLAN Power levels the devices see, and their

network characteristics are assessed (PHY rates, roaming, # of Aps seen, relative

power levels in the two frequencies, occurrence of orthogonal, same or adjacent RF

channels).

Tuning Performance Tests

In this initial tuning period, a selection of performance tests on various devices are

conducted for assessment of configuration settings and performance.

Note on testing techniques are in a later section.

Initial settings

In this initial testing period for Aruba WLAN, power levels will likely start to be

adjusted from:

(min /max ARM settings)

15 dBm /9 dBm for 5GHz

and

(11)

11

4. AirWave Integration with Controller

5.1 Controller Accessible to Test

Engineer MSA/“Company”

5.2 Confirm Controller has gone through the

turn-up and testing controls – from part 1

MSA

5.3 Locate APs, cabled & installed, directed to

controller by DHCP Server & Management VLAN

MSA

5.4 Enable APs in Controller from whole

building

MSA 5.5 Name APs and move to correct

AP

Group, with assigned RF Profile

MSA

5.6 Allow APs to settle and stabilize MSA

5.7 Attach Testing Droid with Aruba Utilities to AirWave, so it can pull down floor-plan and show channel and power settings while testing

MSA

5.8 Walk floors, with Laptops and Droids running Aruba Utilities and analyze RF levels and Roaming performance as previously described

MSA

5.9 Make Max & Min RF Profile adjustments for each frequency from findings and allow to settle again

MSA

5.10 REPEAT as required, document

all changes and iterations MSA

5.11 RF profile should now be OPTIMAL for location and device types

MSA

(12)

12 Network Device Access & Testing to Networks Servers and Applications

2

nd

Stage Testing

After initial stage testing and changes, the network should be allowed to settle before

the next stage of testing is performed.

This testing is a review of device authentication, performance, access to the network,

access to network services, applications used – with tests performed throughout the

building space.

Network Services & Applications

Access needs to be checked & validated to network servers, applications, and

DBs at many locations.

A selection of normally used devices need to be taken through the floors and tested

for typical use cases of access to the different network servers and applications, from

various representative locations - open spaces, cubes, offices and meeting rooms

each floor etc.

Typical applications might be: Biz Apps, SharePoint, PPM, SAP, Oracle

EBS, Horizon Workspace, Source, VPN (Guest ), WebEx, WebEx (steaming ) and

Helpzilla etc.

Communication Voice & Video Applications

Some limited testing should be performed with Skype, Facetime & Lync, under the

following scenarios:

Facetime & Skype

o Stationary Calls – using Voice & Video

o Moving Device to Stationary – using Voice & Video

o Stationary Device to Internet Device – using Voice & Video

Lync – using Voice. Video & presentations including PPTs, streaming video etc.

Up to 6 devices should be used. (Note comments ahout devices roaming on ~.1x

and re-auth’ing.)

o Stationary Calls

o Moving Device to Stationary

o Stationary Device to Internet Device

Formal AirMagnet Surveys

AirMagnet Survey, does not represent these high capacity networks well, they are

tuned by power and config. It can be used after the network has “settled” to review

(13)

13 the floor dBm RF levels, but these can also be reviewed by a Droid running Aruba

Utilities, noting the different receive sensitivities. If it is used during tuning, then it

can be interesting to see the raw files and APs seen at different locations; and the

prescribed reports can be used to show the “effective” cell size of each AP.

Specific Testing at Cube /Meeting Room /Office Locations

iPerf and internet speed testing can also be performed at specific locations, to audit

network performance.

Roaming Tests

Roaming tests are very important, if devices roam well, then the WALN will be

optimally used, if not poor and patchy performance will occur in some devices. Ideal

results will be a roam by every 2

nd

- 3

rd

/4

th

AP, to maintain the highest MCS rates.

Roams should let the device remain on the 5GHz frequency without transferring to

2.4GHz.

These tests are easily performed on Droids running Aruba Utilities, and on Win

Laptops with a CMD window and show commands for the summary of NIC

information.

Other Testing and Applications used for Network Assessment and

Testing

Other testing processes not fully described elsewhere

Of the different types of devices, many devices have different OS’s, wireless NICs

(network interface cards), and maximum power levels they typically transmit at, and

consequently effective range they are able to “talk” bi-directionally to APs. The

graded power curve for device types is (most powerful to least): laptops, tablets,

phones & other handheld devices.

Laptops

A variety of CMD commands can be run to access connection WLAN /NICs, ping,

while moving around through the HTF floors to access PHY rates and roaming

characteristics the device choose, and connectivity for the WLAN config settings

during testing. This is dynamic testing, and observations are used to review results

for Surveys and Roam results.

Tablets /Phones

Aruba Utilities is a useful application for Droids and review of networks designed for

capacity; it lists all the SSIDs, channels and frequencies (device must be b/g/a – n &

ac useful) that the device can see, colour codes similar VAPs, and shows the dBm

power levels visible for each at that location. It also clearly shows PHY rates &

(14)

14 roaming activities for these devices as they move through the floor space and

network; and can pull AirWave floor plan data and metrics.

(15)

15

6. Further WLAN Functionality Testing & Full Systems Reviews throughout Office Space

Pre-requisites AP Layout, with AP Names,

Certified

Table of AP MACs, Names Certified As Built of APs Locations /Names as installed at by cabling Vendor

# Detail Notes /Issue Owner Time/Date Status 6.1 The following test should be

performed through the site on an audit basis

MSA 6.2 Walk around testing each 15000

– 20000 sq ft, multiple devices carried together;

MSA 6.3 Check all SSID /ClearPass

Functionality OnBoarding TLS Certificate based authentication to active directory.

Guest sponsor registration and filtered

lookup to “Company” ADAM box.

Device registration landing pages.

Specific role-based authentication to controller by device-type With each appropriate SSID Voyager Openspace 0nb0ard 1p3t Enterprise NCC-1701

Each with all representative devices

in testing sample Mac OSX

MSA/“Company”

6.4 Further Roam Tests with

various devices MSA

6.5 Stream Video to Tablet while

moving throughout MSA

(16)

16

Testing

6.7 Access to designated Server,

Storage & Network Locations “Company”

6.8 Access and Functionality to Network/Cloud Business Applications

“Company” 6.9 Use of a VoIP Phone in Survey

mode to review choice of APs it can make

MSA

6.10 Hold a VoIP call traversing site ”Company”

6.11 Review RF Levels and AirWave Maps for Power and Channel Choices with Droid Aruba Utilities

MSA

6.12 Choose a selection of

representative use spaces for the following comprehensive test suite different from above

MSA

6.13 iPerf tests to Laptop MSA/”Company”

6.14 Data Downloads Network “Company”

6.15 Data Downloads Internet MSA

6.16 Stream Video MSA

6.17 Access to designated Server,

Storage & Network Locations ”Company”

6.18 Access and Functionality to Network/Cloud Business Applications

”Company”

6.19 Hold a VoIP Call ”Company”

6.20 Review RF Levels and AirWave Maps for Power and Channel Choices with Droid Aruba Utilities

MSA

6.21 Voice and Video Test Cases 6.22 Test as descriptions from early

descriptive section MSA

Go-Live, Site inhabitants return and use System

Knowledgeable Device Technicians should be available at the site to work with with returning

Employees /Contractors. They should be backed up by Engineers with Access to AirWave,

ClearPass and Controllers; and other Network Elements that might need troubleshooting.

Sites are now open to all types of devices that are made with uncontrolled OS’s and revision

levels

The majority of issues found on return are “Desktop Device Trouble-shooting” cases

These should be grouped and “bucketised” fast to evaluate if there are any wider cases

needing evaluation.

An Issues Log should be maintained and closed-out, finding the route cause for each device

with problems

ISSUE LOG

(17)

17

(18)

18 ClearPass Appliances Turn-up

Publisher

# Detail Notes /Issue Owner Time/Date Status 7.1 Prepare VM or

Rack & Stack Appliance “Company”

7.2 Check Network Connectivity “Company”

7.3 Load ClearPass VM Image or

Turn on Appliance “Company”

7.4 Load Base Config & LLD parameters:

IP

Resolvable DNS Hostname Licences

Path & Upgrade SW Join Domain Admin Psswd User/Device Psswd Add Server Secrets Controllers Credentials Load Public Trust SSL Server Certs

Open FW ports if required

MSA

7.5 Load Design Services and Config

Or

Create Config and Scripts With connection to Controller /IAPs

MSA

7.6 Perform individual device tests, on all

SSIDs through Test APs for ALL Roles

and ClearPass Design Cases

MSA

7.7 Check all SSID /ClearPass Functionality

OnBoarding TLS Certificate based authentication to active directory.

Specific role-based authentication to controller by device-type With each appropriate SSID

(19)

19

Voyager Openspace 0nb0ard 1p3t Enterprise NCC-1701

Windows XP and Windows 8.1 IOS iPads & Phones Android Tablet & Phones 7.8 Back-up Appliance for

restoration if required

MSA

Subscriber

# Detail Notes /Issue Owner Time/Date Status 8.1 Prepare VM or

Rack & Stack Appliance “Company”

8.2 Check Network Connectivity “Company”

8.3 Load ClearPass VM Image or

Turn on Appliance “Company”

8.4 Load Base Config & LLD parameters:

IP

Resolvable DNS Hostname Licences

Path & Upgrade SW Join Domain Admin Psswd User/Device Psswd Add Server Secrets Controllers Credentials Load Public Trust SSL Server Certs

Open FW ports if required

MSA

8.5 Connect to Publisher MSA

8.6 Load Design Services and

Config MSA

8.7 Connect to a local Controller for

Testing MSA

8.8 Set up Controller For ClearPass Roles etc.

MSA 8.9 Check all SSID /ClearPass

Functionality OnBoarding TLS Certificate based authentication to active directory. MSA

(20)

20

Guest sponsor registration and

filtered

Specific role-based

authentication to controller by device-type

With each appropriate SSID Voyager Openspace 0nb0ard 1p3t Enterprise NCC-1701

Windows XP and Windows 8.1 IOS iPads & Phones Android Tablet & Phones 8.10 Back-up Appliance for

restoration if required

MSA

AirWave Server Turn-up

# Detail Notes /Issue Owner Time/Date Status 9.1 Prepare VM or rack, stack,

power up appliance, and network connectivity

“Company” 9.2 Load AirWave ISO

Same level if other Airwave Servers in Network

“Company” 9.3 Set base config and Network

LLD during turn up MSA/“Company”

9.4 Save Passwords Especially CLI Root

MSA

9.5 Add Licences MSA

9.6 Either import or set up Groups

Folders Floor-Plans

AP Names and Locations Base Report’s

Config Optimisations Alerts

(21)

21

Rogue Events

9.7 Check Data being populated from

Network Elements

MSA

9.8 Check over all pages and tabs MSA

Pilot Network

Code Upgrade Trials & Changes in Services or Processes

Isolated Pilot WLAN Controller (pair) & Representative Site Location

# Detail Notes /Issue Owner Time/Date Status Check all SSID /ClearPass

Guest sponsor registration and filtered lookup to “Company” ADAM box.

Isolated IAP CLuster & Representative Site Location

(22)

22

Required Equipment & SW

Laptop Win XP & 8.1 Droid

Isolated ClearPass Appliance for use with Pilot Controller (Pair) and IAPs

Guest sponsor registration and filtered lookup to “Company” ADAM box.

(23)

23

Specific role-based

authentication to controller by device-type With each appropriate SSID Voyager Openspace 0nb0ard 1p3t Enterprise NCC-1701