High Performance Wireless Networks

Xirrus Management
System
October 28, 2013
Release 6.6
USERS GUIDE
Copyright Notice
All rights reserved. This document may not be reproduced or
disclosed in whole or in part by any means without the written
consent of Xirrus, Inc.
Part Number: 800-0007-003
(Revision J)
Xirrus Management System
XMS 6.6
Trademarks
is a registered trademark of Xirrus, Inc. All other trademarks and
brand names are marks of their respective holders.
Xirrus, Inc.
2101 Corporate Center Drive
Thousand Oaks, CA 91320
USA
Tel: 1.805.262.1600
1.800.947.7871 Toll Free in the US
Fax: 1.866.462.3980
www.xirrus.com
Management System
i
Table of Contents
List of Figures.................................................................................... xiii
Introduction......................................................................................... 1
The Xirrus Family of Products ............................................................................... 1
XMS Product Overview .......................................................................................... 3
Extended Management Capability ................................................................. 3
A Scalable Solution ........................................................................................... 3
Key Features and Benefits ....................................................................................... 4
Centralized Configuration and Management .............................................. 4
Scalability ........................................................................................................... 4
Security Management ...................................................................................... 4
Powerful Graphical Interface .......................................................................... 4
Performance Monitoring ................................................................................. 5
Centralized Upgrade Management ................................................................ 5
Network Monitoring and Reporting .............................................................. 5
About this Users Guide .......................................................................................... 6
Organization ...................................................................................................... 6
Notes and Cautions .......................................................................................... 8
Hyperlinks ......................................................................................................... 8
Xirrus Management System Products ............................................ 9
XMS Cloud ................................................................................................................ 9
XMS-9000-VM Virtual Appliance ........................................................................ 10
XMS-9000-VM System Requirements .......................................................... 10
Installing the XMS-9000-VM Virtual Appliance ................................................ 11
Install VMware Tools ..................................................................................... 15
Correct Network Port Problems ................................................................... 16
Getting Started with XMS................................................................ 19
XMS Port Requirements ........................................................................................ 20
Getting Started with XMS Cloud ......................................................................... 23
Starting and Managing the XMS Server ............................................................. 24
Management System
ii
Managing XMS on a Management Appliance or Virtual Appliance ...... 24
Managing XMS on XM-3300 and XMS-9000-WIN ..................................... 26
Initial Server Setup for Virtual Appliances ........................................................ 28
About the XMS User Interface ............................................................................. 28
Shutting Down the XMS Server ........................................................................... 29
The XMS Web Client......................................................................... 31
Starting the Web Client ......................................................................................... 31
Web Client Menus .................................................................................................. 32
About Monitor Pages ..................................................................................... 32
About Configure Pages .................................................................................. 34
About Reports Pages ...................................................................................... 37
About Settings Pages ...................................................................................... 39
Settings for Cloud Platforms ......................................................................... 40
Settings for All non-Cloud Platforms .......................................................... 41
Settings for Management Appliance and Virtual Appliance ................... 42
Dashboard ............................................................................................................... 44
Dashboard Overview ..................................................................................... 45
About Dashboard Data .................................................................................. 46
Application Control ........................................................................................ 47
Array and IAP Status ..................................................................................... 51
Most Recent Active Alarms ........................................................................... 52
Stations ............................................................................................................. 53
Rogue Overview ............................................................................................. 57
Array Software and License Versions .......................................................... 58
Arrays ...................................................................................................................... 60
About Using the Arrays Page ....................................................................... 60
The Arrays List ................................................................................................ 65
The Arrays Toolbar ......................................................................................... 66
Array Details ................................................................................................... 67
Switches ................................................................................................................... 78
IAPs .......................................................................................................................... 79
About Using the IAPs Page ........................................................................... 79
The IAPs List ................................................................................................... 80
Management System
iii
SSID .......................................................................................................................... 81
About Using the SSID Page ........................................................................... 81
The SSID List ................................................................................................... 82
Stations .................................................................................................................... 84
About Using the Stations Page ..................................................................... 84
The Stations List .............................................................................................. 85
Legacy APs .............................................................................................................. 88
Rogues ..................................................................................................................... 89
About Using the Rogues Page ...................................................................... 90
The Rogues List ............................................................................................... 90
IDS Events ............................................................................................................... 93
Station Assurance ................................................................................................... 95
Alarms ..................................................................................................................... 97
About Using the Alarms Page ...................................................................... 98
The Alarms List ............................................................................................... 98
Events ..................................................................................................................... 100
About Using the Events Page ..................................................................... 101
The Events List .............................................................................................. 102
PoGE ...................................................................................................................... 103
Application ControlOverview ....................................................................... 104
About Application Control ......................................................................... 104
About Risk and Productivity ...................................................................... 104
The Application ControlOverview Page ............................................... 105
Arrays (Configure) ............................................................................................... 107
The Configure Arrays Toolbar .................................................................... 107
Profiles ................................................................................................................... 113
Array Groups ........................................................................................................ 114
Config Templates ................................................................................................. 116
About Config Template Files ...................................................................... 116
Edit Config Templates ......................................................................................... 117
Load Config Template ......................................................................................... 120
Deploy Config Template ..................................................................................... 123
Custom Field Values ............................................................................................ 125
Port Mappings by Injectors ................................................................................ 127
Managing PoGE injectors with XMS .......................................................... 127
Management System
iv
Add the Injector to XMS .............................................................................. 128
Associate the Injector with an Array .......................................................... 129
Manage the Injector with XMS ................................................................... 130
Port Mappings by Arrays ................................................................................... 131
Port Mappings by Switches ................................................................................ 132
Array Upgrade ..................................................................................................... 134
Perform or Schedule Upgrade .......................................................................... 134
Scheduled Upgrades ............................................................................................ 140
Configure Wireless Settings ............................................................................... 141
Export Wireless Settings ..................................................................................... 143
Import Wireless Settings ..................................................................................... 144
Configure Network Settings ............................................................................... 145
About Using the Network Settings Page ................................................... 145
Individual vs. Bulk Edits ............................................................................. 146
Modify Network Settings (Basic) ............................................................... 148
Modify Network Settings (Advanced) ...................................................... 149
Export Network Settings ..................................................................................... 153
Import Network Settings .................................................................................... 155
Alarm Definitions ................................................................................................ 157
Notification Settings ............................................................................................ 160
Discovery ............................................................................................................... 162
How Discovery Works ................................................................................. 163
How to Perform Discovery .......................................................................... 165
Add Devices .......................................................................................................... 167
SNMPv2 Settings .................................................................................................. 172
SNMPv3 Users ...................................................................................................... 174
SSH Users .............................................................................................................. 176
View Networks ..................................................................................................... 177
What If My Device Is Not Discovered? ............................................................ 179
SecurityRogue Rules ........................................................................................ 180
Populating the XMS Rogues and Rogue Rules Windows ...................... 183
SSID Spoofing Auto Block .................................................................................. 184
Xirrus Access ManagerArray Configuration ............................................... 185
Array Licenses ...................................................................................................... 194
About Licensing and Upgrades .................................................................. 194
Management System
v
Deployed Licenses ............................................................................................... 196
Export Licenses ..................................................................................................... 197
Import Licenses .................................................................................................... 199
Edit Licenses ......................................................................................................... 201
Pending Licenses .................................................................................................. 203
Managing by Profiles .................................................................... 205
Profiles ................................................................................................................... 206
About Using the Profiles Page .................................................................... 207
The Profiles List ............................................................................................. 207
The Profiles Toolbar ..................................................................................... 208
Profile Details ................................................................................................ 214
Profile DetailsArrays ................................................................................ 215
Profile DetailsConfiguration ................................................................... 216
Profile DetailsJob Status ........................................................................... 220
Managing Switches....................................................................... 223
Switch Discovery .................................................................................................. 224
Monitoring Switches ............................................................................................ 224
Configuring Switches .......................................................................................... 225
Switch Details ....................................................................................................... 226
SwitchGeneral Information ............................................................................ 227
SwitchConfiguration ....................................................................................... 228
Switch ConfigurationSystem .......................................................................... 228
Switch ConfigurationIP ................................................................................... 229
Switch ConfigurationPoE Configuration ..................................................... 231
Switch ConfigurationVLAN ........................................................................... 235
Switch ConfigurationVLAN Membership ................................................... 235
Switch ConfigurationVLAN Ports ................................................................ 237
SwitchPoE Status .............................................................................................. 240
Working with Maps ....................................................................... 243
About Maps .......................................................................................................... 244
Getting Started with Maps .................................................................................. 244
Management System
vi
The Map Window and Heat Contour Map ...................................................... 246
The Map List .................................................................................................. 247
RF Heat Contour Map .................................................................................. 248
Performance Plan .......................................................................................... 250
Map Modes of Operation and User Privileges ......................................... 251
Overview of Map Features .......................................................................... 252
Migrating Maps from Earlier Releases ............................................................. 254
Preparing Background Images for New Maps ................................................ 254
Adding a New Map ............................................................................................. 256
Setting the Map Scale and North Direction ..................................................... 258
Adding Arrays to Maps ...................................................................................... 261
Saving a Map ........................................................................................................ 263
Viewing Array, Station, or Rogue Details ........................................................ 264
Locating Devices .................................................................................................. 267
Deleting a Map ..................................................................................................... 271
Managing Arrays Within Maps ......................................................................... 272
Zooming or Moving the Map ............................................................................. 275
Edit Mode Toolbar ............................................................................................... 276
Map Options Panel .............................................................................................. 278
Map Options .................................................................................................. 279
Heatmap Options .......................................................................................... 279
Performance Plan Options ........................................................................... 281
Floorplan Options ......................................................................................... 282
Rogue Location ............................................................................................. 283
Station Location ............................................................................................. 284
Channel Configuration ................................................................................ 284
Map Layers Panel ................................................................................................. 286
Floorplan ........................................................................................................ 287
Heatmap ......................................................................................................... 287
Performance Plan .......................................................................................... 287
Arrays ............................................................................................................. 287
IAP Info .......................................................................................................... 287
Stations ........................................................................................................... 288
Rogues ............................................................................................................ 288
Map Scale ....................................................................................................... 288
Management System
vii
Managing Reports......................................................................... 289
About Reports ....................................................................................................... 289
View Reports ................................................................................................. 291
Viewing a Report .......................................................................................... 293
Create Report ................................................................................................. 297
Selection Criteria ........................................................................................... 304
Customize Report Header ........................................................................... 308
Application Control Reports .............................................................................. 309
Application Category Traffic ...................................................................... 310
Application Traffic ........................................................................................ 313
Station Application Category Traffic ......................................................... 316
Station Application Traffic .......................................................................... 319
Traffic Reports ...................................................................................................... 322
Top Arrays by Wired Traffic ....................................................................... 323
Top Arrays by Wireless Traffic ................................................................... 325
Wireless Traffic .............................................................................................. 327
Wireless Errors .............................................................................................. 330
Station Traffic ................................................................................................ 333
Station Errors ................................................................................................. 337
Ethernet Traffic .............................................................................................. 340
Ethernet Errors .............................................................................................. 343
Top Station Types by Throughput ............................................................. 346
Station Reports ..................................................................................................... 349
Stations by Wi-Fi Band ................................................................................. 351
Station Counts by SSID ................................................................................ 353
Station Activity Over Time Period ............................................................. 355
Station Sessions ............................................................................................. 358
Station Classification .................................................................................... 361
Station Manufacturers .................................................................................. 364
Station Assurance ......................................................................................... 367
Associated Stations ....................................................................................... 370
Stations By Array .......................................................................................... 373
Unique Station Count ................................................................................... 375
Array Reports ....................................................................................................... 378
Management System
viii
Array Inventory ............................................................................................ 378
Array Availability ......................................................................................... 380
RF Reports ............................................................................................................. 383
Channel Usage .............................................................................................. 383
Security Reports ................................................................................................... 386
IDS Events ...................................................................................................... 387
Rogue List ...................................................................................................... 390
Configuring a Wireless Array ....................................................... 393
The Configuration Tab ........................................................................................ 394
General ................................................................................................................... 395
Network ................................................................................................................. 396
Interfaces ........................................................................................................ 397
Bonds .............................................................................................................. 399
DNS Settings .................................................................................................. 406
CDP Settings .................................................................................................. 407
VLAN ..................................................................................................................... 409
VLAN Management ..................................................................................... 410
Services .................................................................................................................. 414
Time Settings (NTP) ..................................................................................... 414
NetFlow .......................................................................................................... 416
Wi-Fi Tag ........................................................................................................ 418
System Log ..................................................................................................... 419
SNMP .............................................................................................................. 424
DHCP Server ................................................................................................. 427
Location .......................................................................................................... 429
Security .................................................................................................................. 432
Admin Management .................................................................................... 435
Admin Privileges .......................................................................................... 436
Admin RADIUS ............................................................................................ 438
Management Control ................................................................................... 441
Global Settings .............................................................................................. 446
Access Control List ....................................................................................... 449
External Radius ............................................................................................. 451
Management System
ix
Internal Radius .............................................................................................. 456
Airwatch ......................................................................................................... 458
SSIDs ...................................................................................................................... 463
SSID Management ........................................................................................ 471
SSID ManagementGeneral Settings ....................................................... 472
SSID ManagementAuthentication/Encryption .................................... 474
SSID ManagementLimits ......................................................................... 476
SSID ManagementTraffic Shaping ......................................................... 477
SSID ManagementCaptive Portal ........................................................... 478
SSID ManagementHoneypot Service Whitelist .................................... 492
Per-SSID Access Control List ...................................................................... 493
Active IAPs .................................................................................................... 495
Groups ................................................................................................................... 496
Group Management ..................................................................................... 498
IAPs ........................................................................................................................ 503
IAP Settings ................................................................................................... 504
Global Settings (IAP) .................................................................................... 509
Global Settings .11a ...................................................................................... 521
Global Settings .11bg .................................................................................... 524
Global Settings .11n ...................................................................................... 528
Advanced RF Settings .................................................................................. 531
Intrusion Detection ....................................................................................... 537
LED Settings .................................................................................................. 543
DSCP Mappings ............................................................................................ 544
Roaming Assist .............................................................................................. 545
Filters ..................................................................................................................... 549
Filter Lists ....................................................................................................... 550
Filter Management ........................................................................................ 551
Tunnels .................................................................................................................. 554
Tunnel Management .................................................................................... 556
SSID Assignments ......................................................................................... 558
XMS Administration...................................................................... 561
About Managing the XMS Server ...................................................................... 562
Management System
x
About the XMS Database .................................................................................... 563
Managing XMS on XM-3320/3340/3360 and Virtual Appliances ............... 564
Accessing the Web Client ............................................................................ 565
Initial Server Setup ....................................................................................... 567
Viewing XMS Server Status ......................................................................... 569
Network Settings .......................................................................................... 571
Date and Time Settings ................................................................................ 572
RAID Status ................................................................................................... 574
Database Backup Settings ............................................................................ 575
Manage Locations ......................................................................................... 575
Manage Schedules or Backup Now ........................................................... 579
Restore ............................................................................................................ 581
Import Backup Archive ................................................................................ 582
Backup Status ................................................................................................ 583
XMS Users ...................................................................................................... 584
Customization ...................................................................................................... 586
Create Custom Fields ................................................................................... 587
Create Custom Actions ................................................................................ 588
Support .................................................................................................................. 590
Array Diag Log Upload ............................................................................... 590
XMS API ................................................................................................................ 592
API Settings ................................................................................................... 593
Obtaining an OAuth Token ......................................................................... 593
Using the API Interface ................................................................................ 594
API Documentation ...................................................................................... 595
API Documentation Toolbar ....................................................................... 599
Applications .......................................................................................................... 600
Email Settings ................................................................................................ 600
Polling Settings .............................................................................................. 601
Changing the SSH Server Address ............................................................. 603
Web Server ..................................................................................................... 604
SNMP Trap Receivers .................................................................................. 605
XMS Setup Wizard ....................................................................................... 606
Audit Log ....................................................................................................... 617
Viewing Server Log Files ............................................................................. 618
Management System
xi
Managing the XMS Server License ............................................................. 620
Performing Server Upgrades ...................................................................... 621
Resetting the XMS Server ............................................................................ 622
Managing XMS on XM-3300 and XMS-9000-WIN Systems .......................... 624
Starting the XMS Server on XM-3300 and XMS-9000-WIN .................... 625
Xirrus Server Management Tool (for XM-3300 and XMS-9000-WIN) .......... 627
XSMT - XMS Server Manager Tool ............................................................ 628
XSMT - Starting the XMS Server ................................................................ 630
XSMT - Shutting Down the XMS Server ................................................... 632
XSMT - Database Tools ................................................................................ 633
Re-initialize Database ................................................................................... 633
Repair Database ............................................................................................ 634
XSMT - Software Manager .......................................................................... 635
About the Installed Patch List ..................................................................... 636
To Install a New Version of the XMS Server ............................................ 636
XSMT - Advanced Settings .......................................................................... 638
Changing Polling Frequency ....................................................................... 638
Changing the SSH Server Address ............................................................. 640
Managing XMS Server Settings via the Web Client ........................................ 641
Technical Support.......................................................................... 643
General Hints and Tips for Xirrus Management Appliances ........................ 643
Frequently Asked Questions .............................................................................. 644
Location Service Data Formats .......................................................................... 646
Euclid Location Server ................................................................................. 646
Non-Euclid Location Server ........................................................................ 646
Contact Information ............................................................................................ 648
Glossary of Terms.......................................................................... 649
Index................................................................................................ 659
Management System
xii
Management System
ListofFigures xiii
List of Figures
Figure 1. XMS Cloud .................................................................................................. 1
Figure 2. XMS Dashboard.......................................................................................... 5
Figure 3. Opening the XMS Virtual Appliance in VMware Player ................... 12
Figure 4. Opening the XMS Virtual Appliance in VMware ESXi ...................... 13
Figure 5. Starting the XMS Server on the Virtual Appliance.............................. 14
Figure 6. VMware Tools Installation Reminder ................................................... 15
Figure 7. Using vmnetcfg.exe.................................................................................. 17
Figure 8. Sample Port Requirements for XMS (non-Cloud Versions)............... 20
Figure 9. Logging in to the Web Client .................................................................. 23
Figure 10. The Web Client Menu.............................................................................. 24
Figure 11. Server Management using the Web Client ........................................... 25
Figure 12. XSMT Window, Showing Typical Running Status ............................. 27
Figure 13. XMS Start Window Showing XMS Cloud Login................................. 31
Figure 14. Mode Selection in XMS Web Client ....................................................... 32
Figure 15. XMS Cloud Web Client Monitor Functions.......................................... 32
Figure 16. XMS Web Client Monitor Functions (non-Cloud)............................... 33
Figure 17. XMS Cloud Web Client Configure Functions ...................................... 34
Figure 18. XMS Web Client Configure Functions (non-Cloud) ........................... 35
Figure 19. XMS Web Client Reports Functions....................................................... 37
Figure 20. Settings Menus for XMS Server Platforms............................................ 39
Figure 21. Dashboard.................................................................................................. 44
Figure 22. Three-column Arrangement of Widgets ............................................... 45
Figure 23. Change Widget Settings .......................................................................... 46
Figure 24. Dashboard - Station Application Category Usage Breakdown......... 48
Figure 25. Dashboard - Station Application Usage Breakdown .......................... 49
Figure 26. Dashboard - Station Application Category Usage over Time............ 49
Figure 27. Dashboard - Station Application Usage over Time............................. 50
Figure 28. Dashboard - Array and IAP Status ........................................................ 51
Figure 29. Dashboard - Recent Alarms .................................................................... 52
Figure 30. Dashboard - Station Count...................................................................... 53
Figure 31. Dashboard - Station Counts by Operating Mode ................................ 54
Management System
xiv ListofFigures
Figure 32. Dashboard - Station Count by Capability............................................. 55
Figure 33. Dashboard - Station Count by Class...................................................... 55
Figure 34. Dashboard - Station Count by Manufacturer....................................... 56
Figure 35. Dashboard - Station Counts by SSID..................................................... 56
Figure 36. Dashboard - Station Throughput ........................................................... 57
Figure 37. Dashboard - Rogue Overview................................................................ 57
Figure 38. Dashboard - Array Software Versions................................................... 58
Figure 39. Dashboard - Array License Versions ..................................................... 59
Figure 40. Arrays Page (non-Cloud version shown) ............................................. 60
Figure 41. Table Column Chooser ............................................................................ 62
Figure 42. Sorting on a Column ................................................................................ 64
Figure 43. Search Results............................................................................................ 64
Figure 44. Search Results include Web Client Menu Options.............................. 65
Figure 45. The MonitorArrays Page Toolbar ...................................................... 66
Figure 46. Array Details: General ............................................................................. 68
Figure 47. Array Details: Configuration .................................................................. 69
Figure 48. Array Details: System.............................................................................. 70
Figure 49. Array Details: Groups.............................................................................. 71
Figure 50. Array Details: IAPs................................................................................... 71
Figure 51. Array Details: Stations ............................................................................. 72
Figure 52. Array Details: SSIDs................................................................................. 72
Figure 53. Array Details: Station Assurance ........................................................... 73
Figure 54. Array Details: Application Control........................................................ 74
Figure 55. Array Details: IDS..................................................................................... 75
Figure 56. Array Details: Rogues .............................................................................. 76
Figure 57. Array Details: Events ............................................................................... 76
Figure 58. Array Details: Uptime.............................................................................. 77
Figure 59. IAPs Page................................................................................................... 79
Figure 60. IAP DetailsGeneral ............................................................................... 80
Figure 61. SSID Page................................................................................................... 81
Figure 62. SSID DetailsSummary.......................................................................... 83
Figure 63. Stations Page ............................................................................................. 84
Figure 64. Station DetailsGeneral ......................................................................... 87
Figure 65. Legacy APs Page....................................................................................... 88
Figure 66. Rogues Page .............................................................................................. 90
Management System
ListofFigures xv
Figure 67. Classifying Rogues ................................................................................... 92
Figure 68. IDS Events.................................................................................................. 93
Figure 69. Station Assurance History....................................................................... 95
Figure 70. Alarms Page .............................................................................................. 97
Figure 71. Events Page.............................................................................................. 100
Figure 72. Power over Gigabit Ethernet Page....................................................... 103
Figure 73. Application ControlOverview.......................................................... 105
Figure 74. The Configure Arrays Toolbar ............................................................. 107
Figure 75. Pull Diagnostic Logs .............................................................................. 108
Figure 76. Adding Arrays to a Group.................................................................... 109
Figure 77. Packet Capture Dialog ........................................................................... 112
Figure 78. Packet Capture in Progress ................................................................... 112
Figure 79. Array Group Page .................................................................................. 114
Figure 80. Add or Edit Group ................................................................................. 115
Figure 81. Edit Config Template Page ................................................................... 117
Figure 82. Config Template Editor ......................................................................... 118
Figure 83. Load from Array..................................................................................... 120
Figure 84. Load from Array - Config File Options............................................... 121
Figure 85. Select Config Template File to Deploy ................................................ 123
Figure 86. Select Arrays for Deployment............................................................... 123
Figure 87. Select Deployment Options................................................................... 124
Figure 88. Deployment Results ............................................................................... 124
Figure 89. Custom Field Values Adding a single value .................................. 125
Figure 90. Bulk Configuration (Custom Field Values) ........................................ 126
Figure 91. PoGE Port Mappings by Injector.......................................................... 127
Figure 92. Injector and Array Associations ........................................................... 129
Figure 93. Associating Injector and Array Ports................................................... 129
Figure 94. PoGE Port Mappings by Array............................................................. 131
Figure 95. PoGE Port Mappings by Array............................................................. 132
Figure 96. Array Upgrade........................................................................................ 135
Figure 97. Select Upgrade Source ........................................................................... 136
Figure 98. Select Software Versions........................................................................ 137
Figure 99. Upgrade Summary................................................................................. 139
Figure 100. Scheduled Upgrades .............................................................................. 140
Figure 101. Configure Wireless Settings Page ........................................................ 141
Management System
xvi ListofFigures
Figure 102. Editing the IAP Settings Page............................................................... 142
Figure 103. Editing Individual Rows ....................................................................... 146
Figure 104. Bulk Configuration (Network Settings) .............................................. 147
Figure 105. Configure Network Settings Page (Basic) ........................................... 148
Figure 106. Editing the Network Settings Page (Basic) ......................................... 149
Figure 107. Configure Network Settings Page (Advanced).................................. 149
Figure 108. Editing the Array Network Settings Page (Advanced)..................... 150
Figure 109. Editing the Array Network Settings Page (Ethernet)........................ 151
Figure 110. Editing the Array Network Settings Page (IP) ................................... 151
Figure 111. Editing the Array Network Settings Page (Bond) ............................. 152
Figure 112. Export Network Settings ....................................................................... 153
Figure 113. Exported Network Settings File ........................................................... 154
Figure 114. Import Network Settings....................................................................... 155
Figure 115. Verify Imported Network Setting Values........................................... 156
Figure 116. Custom Alarms Page ............................................................................. 157
Figure 117. Add a Discrete Alarm............................................................................ 157
Figure 118. Add an Analog Alarm........................................................................... 159
Figure 119. Alarm Notification Settings .................................................................. 160
Figure 120. Add a Notification.................................................................................. 161
Figure 121. Discovering Networks ........................................................................... 166
Figure 122. Discover a Single Device ....................................................................... 167
Figure 123. Discovery ResultsSingle Device ....................................................... 168
Figure 124. Discover a Range of IP Addresses ....................................................... 168
Figure 125. Discover a List of IP Addresses ............................................................ 169
Figure 126. Discover Networks................................................................................. 170
Figure 127. Review Results of Adding Devices...................................................... 171
Figure 128. SNMPv2 Settings .................................................................................... 173
Figure 129. SNMPv3 Users ........................................................................................ 174
Figure 130. Adding SSH Users.................................................................................. 176
Figure 131. View Discovered Networks .................................................................. 177
Figure 132. Rogue Rules............................................................................................. 180
Figure 133. Adding a Rogue Rule............................................................................. 181
Figure 134. Auto Blocking SSID Spoofing Attacks................................................. 184
Figure 135. XAM WizardSelect Targets............................................................... 187
Figure 136. XAM WizardXAM Details ................................................................ 187
Management System
ListofFigures xvii
Figure 137. XAM WizardSSID............................................................................... 189
Figure 138. XAM WizardTunneling..................................................................... 191
Figure 139. XAM WizardResults .......................................................................... 192
Figure 140. Array License Management - Deployed Licenses ............................. 196
Figure 141. Exporting Array Licenses...................................................................... 198
Figure 142. Sample Export File.................................................................................. 198
Figure 143. Importing Array Licenses...................................................................... 200
Figure 144. Select Array Licenses to Edit................................................................. 201
Figure 145. Editing Array Licenses........................................................................... 202
Figure 146. Array Licenses Pending Deployment.................................................. 203
Figure 147. Profiles Page ............................................................................................ 206
Figure 148. The MonitorArrays Page Toolbar .................................................... 208
Figure 149. Add a Profile ........................................................................................... 208
Figure 150. Edit a Profile............................................................................................ 209
Figure 151. Copy a Profile.......................................................................................... 211
Figure 152. Create a Profile from an Array ............................................................. 211
Figure 153. Set Profiles Software Image ................................................................. 213
Figure 154. Profile Details: General .......................................................................... 215
Figure 155. Profile Details: Configuration............................................................... 216
Figure 156. Profile Details: Job Status ...................................................................... 220
Figure 157. Switches List (Monitor).......................................................................... 224
Figure 158. Switches List (Configure) ...................................................................... 225
Figure 159. Switch DetailsGeneral Information ................................................. 227
Figure 160. Switch DetailsSystem Information................................................... 228
Figure 161. Switch DetailsIPv4.............................................................................. 229
Figure 162. Switch DetailsPoE Configuration..................................................... 231
Figure 163. Switch DetailsPoE Bulk Edit ............................................................. 233
Figure 164. Switch DetailsVLAN Membership .................................................. 235
Figure 165. Switch DetailsVLAN: Create/Membership ................................... 236
Figure 166. Switch DetailsVLAN Ports................................................................ 237
Figure 167. Switch DetailsVLAN Ports Bulk Edit .............................................. 239
Figure 168. PoE Status tab (Configure) .................................................................... 240
Figure 169. Main Map with RF Heat Contours Enabled....................................... 246
Figure 170. The Map List and Map Options Panel................................................. 247
Figure 171. Main Map Showing RF Heat Contours............................................... 248
Management System
xviii ListofFigures
Figure 172. Performance Plan Map .......................................................................... 250
Figure 173. Add/Delete a Map and Edit/Monitor Mode Buttons ...................... 252
Figure 174. Maps List.................................................................................................. 256
Figure 175. Add New Map Window........................................................................ 256
Figure 176. New Map (showing prompt for scaling the map) ............................. 258
Figure 177. Calibrating the Map Scale ..................................................................... 259
Figure 178. Edit Map Scale......................................................................................... 260
Figure 179. XMS Prompts You to Set North on the Map ...................................... 260
Figure 180. Adding Arrays to a Map ....................................................................... 261
Figure 181. Arrays Added to Map............................................................................ 262
Figure 182. Orienting an Array................................................................................. 262
Figure 183. Map Array Details .................................................................................. 264
Figure 184. Map Station Details ................................................................................ 265
Figure 185. Map Rogue Details ................................................................................. 266
Figure 186. Using the Location Feature ................................................................... 267
Figure 187. Determining Position............................................................................. 268
Figure 188. Array Management Panel ..................................................................... 272
Figure 189. Map Zoom and Move Controls ............................................................ 275
Figure 190. Map Edit Mode Toolbar ........................................................................ 276
Figure 191. Map Options Panel ................................................................................. 278
Figure 192. Heatmap Options ................................................................................... 279
Figure 193. Map Channel Selection.......................................................................... 280
Figure 194. Performance Plan Options .................................................................... 281
Figure 195. Map Floorplan Options ......................................................................... 282
Figure 196. Map Rogue Location Options............................................................... 283
Figure 197. Map Station Location Options.............................................................. 284
Figure 198. Auto Channel Configuration................................................................ 284
Figure 199. Map Auto Channel Options.................................................................. 285
Figure 200. Map Layers Panel ................................................................................... 286
Figure 201. IAP Info Layer (XR-1000 shown).......................................................... 287
Figure 202. View Reports Window........................................................................... 291
Figure 203. Actions for Reports................................................................................. 292
Figure 204. Archived Reports List ............................................................................ 293
Figure 205. Viewing a Report .................................................................................... 293
Figure 206. Report Including Charts ........................................................................ 294
Management System
ListofFigures xix
Figure 207. Emailing a Report ................................................................................... 296
Figure 208. List of Create Report Types................................................................... 297
Figure 209. Create Report Page................................................................................. 298
Figure 210. Report Queue .......................................................................................... 304
Figure 211. Customize Report Header Page ........................................................... 308
Figure 212. Application Category Traffic Report ................................................... 311
Figure 213. Application Traffic Report .................................................................... 314
Figure 214. Station Application Category Traffic Report (All Categories)......... 317
Figure 215. Station Application Traffic Report (All Applications) ...................... 320
Figure 216. Top Arrays by Wired Traffic Report.................................................... 324
Figure 217. Top Arrays by Wireless Traffic Report................................................ 326
Figure 218. Wireless Traffic Report .......................................................................... 328
Figure 219. Wireless Errors Report........................................................................... 331
Figure 220. Station Traffic Report (Tx+Rx).............................................................. 335
Figure 221. Station Errors Report.............................................................................. 338
Figure 222. Ethernet Traffic Report .......................................................................... 341
Figure 223. Ethernet Errors Report........................................................................... 344
Figure 224. Top Station Types by Throughput Report.......................................... 347
Figure 225. Stations by Wi-Fi Band Report ............................................................. 352
Figure 226. Station Counts by SSID Report............................................................. 354
Figure 227. Station Activity Over Time Period Report.......................................... 356
Figure 228. Station Sessions Report.......................................................................... 359
Figure 229. Station Classification Report................................................................. 362
Figure 230. Station Manufacturers Report............................................................... 365
Figure 231. Station Assurance Report ...................................................................... 368
Figure 232. Station Association................................................................................. 371
Figure 233. Station Association (By Array) Report ................................................ 374
Figure 234. Unique Station Count Report ............................................................... 376
Figure 235. Array Inventory Report ......................................................................... 379
Figure 236. Array Availability Report...................................................................... 381
Figure 237. Channel Usage Report ........................................................................... 384
Figure 238. IDS Events Report................................................................................... 388
Figure 239. Rogue List Report................................................................................... 391
Figure 240. Opening the Configuration Window................................................... 394
Figure 241. General Information............................................................................... 395
Management System
xx ListofFigures
Figure 242. Network Configuration Menu.............................................................. 396
Figure 243. Network Interface Settings.................................................................... 397
Figure 244. Network Bonds ....................................................................................... 400
Figure 245. Port Modes (a, b)..................................................................................... 401
Figure 246. Port Modes (c) ......................................................................................... 402
Figure 247. Port Modes (d) ........................................................................................ 403
Figure 248. Select Active VLANs for this Bond...................................................... 404
Figure 249. Mirroring Traffic..................................................................................... 405
Figure 250. DNS Settings............................................................................................ 406
Figure 251. CDP Settings............................................................................................ 407
Figure 252. VLAN Management ............................................................................... 410
Figure 253. Creating a VLAN.................................................................................... 412
Figure 254. Time Settings (Using NTP).................................................................... 415
Figure 255. NetFlow.................................................................................................... 416
Figure 256. Wi-Fi Tag.................................................................................................. 418
Figure 257. System Log .............................................................................................. 419
Figure 258. SNMP ....................................................................................................... 424
Figure 259. DHCP Management ............................................................................... 427
Figure 260. Adding a DHCP Pool............................................................................. 428
Figure 261. Location.................................................................................................... 430
Figure 262. Admin Management .............................................................................. 435
Figure 263. Admin Privileges.................................................................................... 437
Figure 264. Admin RADIUS...................................................................................... 439
Figure 265. Management Control ............................................................................. 442
Figure 266. Pre-login Banner ..................................................................................... 442
Figure 267. Global Settings (Security) ...................................................................... 446
Figure 268. Access Control List ................................................................................. 449
Figure 269. External RADIUS Server ....................................................................... 451
Figure 270. Internal RADIUS Server ........................................................................ 456
Figure 271. Add an Internal RADIUS User ............................................................. 457
Figure 272. AirWatch Settings................................................................................... 458
Figure 273. SSIDs......................................................................................................... 463
Figure 274. Four Traffic Classes ................................................................................ 467
Figure 275. Priority LevelIEEE 802.1p (Layer 2)................................................. 467
Figure 276. Priority LevelDSCP (DiffServ - Layer 3) ......................................... 468
Management System
ListofFigures xxi
Figure 277. SSID Management .................................................................................. 471
Figure 278. SSID Management: Authentication/Encryption ............................... 474
Figure 279. SSID Management: Limits..................................................................... 476
Figure 280. SSID Management: Traffic Shaping..................................................... 477
Figure 281. SSID Management: Captive Portal (Internal Login page) ................ 478
Figure 282. Captive Portal Server Types ................................................................. 479
Figure 283. Captive PortalInternal Splash Page ................................................. 481
Figure 284. Captive PortalInternal Login Page................................................... 482
Figure 285. Captive PortalExternal Login Page.................................................. 484
Figure 286. Captive PortalExternal Splash Page ................................................ 485
Figure 287. Captive PortalLanding Page Only ................................................... 486
Figure 288. Using the Captive Portal Editor ........................................................... 487
Figure 289. Captive Portal Editor Buttons............................................................... 488
Figure 290. Captive Portal Image Selection............................................................. 489
Figure 291. White List Configuration for Captive Portal ...................................... 491
Figure 292. SSID Management: Honeypot Whitelist ............................................. 492
Figure 293. Per-SSID Access Control List ................................................................ 493
Figure 294. Setting Active IAPs per SSID................................................................ 495
Figure 295. Groups...................................................................................................... 496
Figure 296. Adding a Group...................................................................................... 498
Figure 297. IAP Settings ............................................................................................. 504
Figure 298. Changing IAP Settings........................................................................... 505
Figure 299. Global Settings (IAPs) ............................................................................ 509
Figure 300. Global Settings .11an.............................................................................. 521
Figure 301. Global Settings .11bg.............................................................................. 524
Figure 302. Global Settings .11n................................................................................ 529
Figure 303. Advanced RF Settings............................................................................ 531
Figure 304. Intrusion Detection Settings.................................................................. 537
Figure 305. LED Settings ............................................................................................ 543
Figure 306. DSCP Mappings...................................................................................... 545
Figure 307. Roaming Assist ....................................................................................... 547
Figure 308. Filter Lists ................................................................................................ 549
Figure 309. Filter Management ................................................................................. 551
Figure 310. Tunnel Management .............................................................................. 556
Figure 311. Tunnel SSID Assignments..................................................................... 558
Management System
xxii ListofFigures
Figure 312. Server Management using the Web Client ......................................... 564
Figure 313. Starting the Web Client.......................................................................... 565
Figure 314. Changing Network Settings.................................................................. 567
Figure 315. The Status Page....................................................................................... 569
Figure 316. Changing Network Settings.................................................................. 571
Figure 317. Changing Date and Time Settings ....................................................... 572
Figure 318. RAID Status ............................................................................................. 574
Figure 319. Backup Locations List ............................................................................ 575
Figure 320. Backup LocationWindows File Share.............................................. 576
Figure 321. Backup LocationFTP .......................................................................... 577
Figure 322. Backup LocationSCP.......................................................................... 578
Figure 323. Backup Schedule List ............................................................................. 579
Figure 324. Backup Now............................................................................................ 579
Figure 325. Enter a Backup Schedule ....................................................................... 580
Figure 326. Restoring Backups .................................................................................. 581
Figure 327. Import Backup Archive ......................................................................... 582
Figure 328. Backup Status.......................................................................................... 583
Figure 329. Managing XMS User Accounts............................................................. 584
Figure 330. Add an XMS User Account (XMS Cloud)........................................... 584
Figure 331. Custom Fields Page................................................................................ 587
Figure 332. Custom Actions Page............................................................................. 588
Figure 333. Array Diagnostic Log Upload .............................................................. 590
Figure 334. API Settings ............................................................................................. 593
Figure 335. XMS API Documentation...................................................................... 595
Figure 336. API Settings Requests List................................................................ 596
Figure 337. API GET Request Details.................................................................. 597
Figure 338. API GET Request Response ............................................................. 598
Figure 339. API Documentation Toolbar................................................................. 599
Figure 340. Changing the Email Server ................................................................... 600
Figure 341. Changing Polling Rate .......................................................................... 601
Figure 342. Changing the SSH Server ...................................................................... 603
Figure 343. Web Server............................................................................................... 604
Figure 344. SNMP Trap Receivers ............................................................................ 605
Figure 345. XMS Setup WizardXMS License ...................................................... 607
Figure 346. XMS Setup WizardCommunity Names .......................................... 608
Management System
ListofFigures xxiii
Figure 347. XMS Setup WizardSSH Users........................................................... 609
Figure 348. XMS Setup WizardNetwork ............................................................. 610
Figure 349. XMS Setup WizardTime Zone.......................................................... 611
Figure 350. XMS Setup WizardBackup................................................................ 612
Figure 351. XMS Setup WizardEmail ................................................................... 613
Figure 352. XMS Setup WizardSNMP Trap Receivers ...................................... 614
Figure 353. XMS Setup WizardDiscover Devices............................................... 615
Figure 354. XMS Setup WizardResults ................................................................ 616
Figure 355. Audit Log................................................................................................. 617
Figure 356. Viewing Log Files ................................................................................... 618
Figure 357. Viewing a Selected Log File .................................................................. 619
Figure 358. Multiple Log Files................................................................................... 619
Figure 359. XMS Server License................................................................................ 620
Figure 360. Upgrading XMS Software ..................................................................... 621
Figure 361. Resetting XMS......................................................................................... 622
Figure 362. Xirrus Server Management Tool - XMS Server Manager ................. 624
Figure 363. Start XMS as a Windows Service.......................................................... 625
Figure 364. Xirrus Server Management Tool - XMS Server Manager ................. 627
Figure 365. Status of Services, Showing Normal Status ........................................ 628
Figure 366. Status of Offline Activities..................................................................... 629
Figure 367. Server Startup Progress ......................................................................... 631
Figure 368. Server is Up (XSMT)............................................................................... 631
Figure 369. Server Shutdown Progress.................................................................... 632
Figure 370. Status for Stopped XMS Server............................................................. 633
Figure 371. XSMT Software Manager ...................................................................... 635
Figure 372. Select a Patch File.................................................................................... 636
Figure 373. XSMT Advanced Menu Options .......................................................... 638
Figure 374. Changing Polling Frequency ................................................................ 639
Figure 375. Changing the SSH Server ...................................................................... 640
Management System
xxiv ListofFigures
Management System
Introduction 1
Introduction
This section introduces the Xirrus Management System (XMS), including an
overview of key features and benefits. It also includes an outline of how this
Users Guide is organized. Section headings for this chapter include:
The Xirrus Family of Products on page 1
XMS Product Overview on page 3
Key Features and Benefits on page 4
About this Users Guide on page 6
The Xirrus Family of Products
Xirrus Management System (XMS)
XMS is a powerful management tool, designed to manage your wireless
Arrays from anywhere in the network ideal for large scale wireless
deployments. XMS supports all Array models including the XR and XN
series. XMS-hosted and on-premises versions are available:
Xirrus Management SystemCloud (XMS-C)
Figure 1. XMS Cloud
Management System
2 Introduction
XMS-C is a cloud-based wireless network management platform
that provides full monitoring and management of the Xirrus
wireless Array network via a cloud-hosted web based interface
with graphical map views. XMS-C scales from small to large
networks and from one location to multiple locations, as well as
large campus environments with thousands of wireless users.
Because the Xirrus Management SystemCloud is hosted in the
cloud and operationally maintained by Xirrus, XMS-C feature
updates, XMS-C performance improvements, and firmware
upgrades to wireless Arrays are all handled by Xirrus without the
need for IT staff scheduling or intervention.
Management traffic between Arrays and XMS-C is conducted via a
secure tunnel using challenge-based authentication, and encryption
with a 128 bit key.
Xirrus Virtual Appliance Virtualized XMS Server Software
(Xirrus Part Number XMS-9000-VM)
XMS-9000-VM allows you to install and run the XMS server
software on your own virtual server under VMware.
Xirrus Wireless Array
The Xirrus wireless Array is specifically designed for the Enterprise
market, utilizing up to 16 Integrated Access Points (IAPs). Multiple
versions of the Array with different numbers of Integrated Access Points
(IAPs) support a variety of deployment applications. For more
information, refer to the Xirrus Wireless Array Users Guide.
Management System
Introduction 3
XMS Product Overview
The Xirrus Management System is a wireless network management application
for managing a network of Xirrus arrays. XMS provides centralized monitoring,
configuration, reporting, and management functions for Arrayseither
individually, by group, or for all Arrays. If you are an XMS Cloud customer, XMS
is maintained by Xirrus, and firmware upgrades to wireless Arrays are
automatically managed by Xirrus.
Extended Management Capability
XMS provides a dashboard overview of wireless network health, as well as maps
and other views to monitor and manage the network. You may drill down to see
detailed information about individual Arrays, IAPs, stations, and rogue devices.
With its powerful discovery feature and map-based organization of your wireless
Arrays, XMS streamlines the management of Array configurations.
XMS allows IT administrators to manage configurations, schedule firmware
upgrades across multiple wireless Arrays, and create groups of wireless Arrays to
simplify repetitive tasks. XMS also offers different administrative levels that allow
Help Desk staff to monitor their network and its client activity, and restrict
network setting changes to specific staff members. All of these features allow the
IT department to actively monitor and manage the health of their wireless
network from anywhere using a browser.
A Scalable Solution
The Xirrus centralized management technology scales from small to large
networks and from one location to multiple locations, as well as large campus
environments with thousands of wireless users. Together with its family of
wireless Arrays, Xirrus developed XMS to facilitate faster and more cost-effective
high capacity Wi-Fi rollouts across large campus environments.
XMS monitors wireless performance and gathers detailed reporting and statistical
data for each Array residing in the network, or for the entire network as a whole.
It also allows you to schedule firmware updates for individual wireless Arrays or
groups of Arrays to ensure that your firmware is up-to-date and consistent across
the network.
Management System
4 Introduction
Key Features and Benefits
This section describes some of the key product features and the benefits you can
expect when deploying the XMS to configure and manage your network of
Arrays.
Centralized Configuration and Management
Allows you to view and manage your entire wireless network at Layer 3 using
your existing Ethernet infrastructure. In addition, XMS discovers, authenticates
and configures new wireless Arrays, making large scale deployments quick and
easy. Configuration templates ensure consistent configuration of Arrays across
the network, and they are easily created by copying the configuration of a
known-good Array.
Scalability
With its ability to support thousands of wireless Array access points and many
more concurrent wireless clients per XMS server, XMS allows your network to
grow as your business grows.
Security Management
Defines and distributes security policies for the entire Array network, and allows
you to set encryption, authentication, access times, and guest user access policies
for secure wireless Array rollouts.
Powerful Graphical Interface
XMSs client interfaces provide all the tools and features that are necessary to
ensure your Array network is configured and managed effectively and securely.
The interfaces are easy to use and can be accessed from any location using a Web
browser.
The XMS Dashboard (Figure 2) provides an at-a-glance overview of the security
and performance of your Array network.
Management System
Introduction 5
Figure 2. XMS Dashboard
Performance Monitoring
Continually monitors and displays wireless performance.
Centralized Upgrade Management
Allows you to schedule firmware updates for individual wireless Arrays or
groups of Arrays at specific times.
Network Monitoring and Reporting
XMS displays all Array alerts and alarms to allow you to determine how to
respond to faults in the Array network. It also monitors your Array networks
performance and provides detailed reporting and statistical data for Arrays
individually, by group of Arrays, by SSID, or by individual IAPs (Integrated
Access Points).
Management System
6 Introduction
About this Users Guide
Detailed information and procedures have been provided in this Users Guide
that will enable network administrators to use cloud-based XMS or to install and
run XMS on their own virtual environment, to understand and navigate the XMS
client interface, and to successfully manage their network of wireless Arrays with
a browser-based interface. XMS may be installed on your own VMware-based
platform. This Guide does not cover the installation or management of Arrays in
isolation from XMS. For procedures that deal with Arrays not centrally managed
by XMS, refer to the Xirrus Wireless Array Users Guide.
Organization
This Users Guide is organized by function under the following headings:
Introduction
Provides an overview of the product, including its key features and
benefits.
Xirrus Management System Products
This chapter provides an overview of what you can expect when you
install your Xirrus management product for the first time information
you need to know if you want to make informed decisions when using
the system. It also provides instructions to help you complete a successful
installation.
Getting Started with XMS
Discusses starting, stopping, and managing the XMS server and client
software. Provides procedures for initial setup of XMS, such as setting a
network address and discovering the wireless network.
The XMS Web Client
Describes how to use the web client interface, including the wireless
network monitoring and configuration tools, and XMS server
management tools.
Managing by Profiles
Describes how to organize sets of Arrays as profile networks to ensure the
deployment of consistent software and settings across each profile.
Management System
Introduction 7
Managing Switches
Describes how to configure and manage Xirrus PoE+ Gigabit wired
switches.
Working with Maps
Introduces you to the location/RF heat map in the web client, and
provides instructions for managing your maps and map layouts. It also
shows you how to prepare map background images.
Managing Reports
XMS generates detailed performance and status reports about the
wireless network, all Arrays within the network, individual IAPs
contained within each Array, and their client stations. This chapter
provides instructions for reviewing and managing these reports in the
web client.
Configuring a Wireless Array
XMS provides a configuration window that has options that allow you to
easily to configure settings on an Array.
XMS Administration
Provides instructions for managing the XMS database and other
administrative tasks, including how to review the current status of the
database, how to schedule and create backups, and how to restore the
database from the server.
Technical Support
Offers guidance to resolve technical issues, some general hints and tips to
enhance your product experience, and Xirrus contact information.
Glossary of Terms
Provides an explanation of terms directly related to XMS product
technology, organized alphabetically.
Management System
8 Introduction
Notes and Cautions
The following symbol is used throughout this Users Guide:
Hyperlinks
If you click on body text that appears in the color TEAL (with the exception of
headings or notes) the embedded hyperlink within the text will immediately take
you to the referenced destination. All cross-references, including the Table of
Contents, page numbers within the List of Figures and the Index, and embedded
text have associated hyperlinks. If you want to return to the reference source, you
can do this by clicking on Acrobats previous page button.
!
This symbol is used for cautions. Cautions provide critical information that
may adversely affect the performance of the product.

General notes provide useful supplemental information.
Management System
XirrusManagementSystemProducts 9
Xirrus Management System
Products
The Xirrus Management System is offered in two forms:
XMS Clouda cloud hosted version of XMS that allows your wireless
network to be managed for you by Xirrus.
XMS-9000-VM Virtual Appliance a virtualized XMS server software
application package that allows you to install and run the XMS server
software on your own virtual server under VMware.
XMS Cloud
XMS Cloud is a hosted deployment option for the Xirrus Management System
(XMS). This cloud-based solution provides a simpler and faster way to deploy
and manage your Xirrus wireless network. Deployment times are significantly
reduced with zero touch equipment activation. Installation and ongoing
maintenance efforts are eliminated.
Xirrus Arrays and APs come out of the box with automated online activation.
Once activated, they connect automatically to the XMS system purchased,
whether cloud-based or on-premise.
The XMS Cloud hosted network management system includes:
Web-based interface for complete monitoring and management of a
Xirrus wireless network.
Cloud-based activation with zero touch initialization out-of-the-box.
Complete monitoring of wireless network status, traffic and clients.
Complete configuration management of the wireless network.

Wireless Arrays must be running ArrayOS Release 6.4 or above to be
managed by XMS Cloud. You cannot use XMS Cloud to upgrade Arrays
to Release 6.4 from an earlier release.
Management System
10 XirrusManagementSystemProducts
Graphical maps depicting wireless coverage, wireless performance, and
user/rogue location.
Comprehensive management reports on wireless performance, security,
users, applications, RF, and more.
Security monitoring, alerting and mitigation for rogues and security
events.
Troubleshooting tools diagnose connectivity and performance issues.
Proceed to the next chapter, Getting Started with XMS, to start using XMS Cloud.
XMS-9000-VM Virtual Appliance
The XMS-9000-VM Virtual Appliance is designed to be run on a virtual platform.
The application package allows you to install and run the XMS server software on
your own virtual server under VMware. For installation instructions, see
Installing the XMS-9000-VM Virtual Appliance on page 11.
XMS-9000-VM System Requirements
The recommended requirements for the system hosting the virtual XMS server
are based on the scale of the Wi-Fi Array network to be managed small,
medium, or large. The Virtual Appliance package must be installed on a server
running VMware. The versions that are supported are:
VMware ESXi (recommended)
VMware Player
VMware vSphere
VMware Workstation
Please see product information on www.xirrus.com for specifications and system
requirements for the scale of the network to be managed.

Take care not over-subscribe RAM when using a Virtual XMS Appliance - e.g.,
if there are three VM instances on the system that are provisioned for 8GB each,
then the total system must have no less than 3 x 8GB = 24 GB provisioned for it.
Management System
XirrusManagementSystemProducts 11
Installing the XMS-9000-VM Virtual Appliance
The XMS Virtual Appliance is supplied as an .ova file (Open Virtual Appliance),
for example, xms-vm-6.1.0-2680.ova. It contains all the software that you need to
run an XMS server on a virtual machine.
1. One of the following versions of VMware must already be installed on
the server platform: VMware Player, VMware Workstation, VMware
ESXi, or VMware vSphere. Please refer to documentation supplied for
your VMware product for exact instructions for using the .ova file.
Documentation is available online at http://www.vmware.com/support/
pubs/.
2. Open the client for managing your VMware product. For example, open
VMware Player or VMware vSphere.
3. Open the .ova file in your VMware product.

You must ensure that the BIOS on the computer running VMware has
Virtualization Technology (VT) enabled. VMware requires this setting for
XMS, which runs as a 64-bit guest operating system. Different BIOS versions
may have a different name for this setting. Please see VMware support for more
information. The knowledge base topic, Ensuring Virtualization Technology is
enabled on your VMware host is especially useful. kb.vmware.com
Management System
12 XirrusManagementSystemProducts
a. For VMware Player: select Open a Virtual Machine. Browse to the
.ova file. In the browse dialog, be sure to set Files of type so that the
.ova file will be listed.
Figure 3. Opening the XMS Virtual Appliance in VMware Player
Management System
XirrusManagementSystemProducts 13
b. For VMware ESXi Versions 4 and 5: select File > Deploy OVF
Template. Browse to the .ova file. In the browse dialog, be sure to set
Files of type so that the .ova file will be listed.
Figure 4. Opening the XMS Virtual Appliance in VMware ESXi
4. Follow the prompts to import the XMS Virtual Appliance.
5. Select the XMS Virtual Appliance from the list at the left and select Power
on this virtual machine.
6. Select the XMS Virtual Appliance from the list at the left, right click, and
select Settings. Adjust the hardware specifications as necessary. For
larger wireless networks, increase the amount of Memory and Processors
dedicated to the XMS Appliance.
7. Follow the instructions in the next section to Install VMware Tools,
which will improve XMS Virtual Appliance performance.
8. Type Ctrl+g to direct commands to the XMS server in the Virtual
Appliance. Log in with the login/password admin/admin. (Figure 5)
Type show ip, and note the IP address of the port that you are using for
management.
Management System
14 XirrusManagementSystemProducts
Figure 5. Starting the XMS Server on the Virtual Appliance
9. To access the web client, set your browsers URL to this IP address,
followed by a:9090. For example, http://192.168.1.110:9090. When the
splash page appears, log in. The default username and password are
admin/admin.
For VMware Player or VMware Workstation, if you have problems with
network connectivity, see Correct Network Port Problems on page 16.
10. Continue to Initial Server Setup for Virtual Appliances on page 28 to
configure and begin using the XMS server.
Management System
XirrusManagementSystemProducts 15
Install VMware Tools
To improve performance of the XMS Virtual Appliance, we highly recommend
that you install VMware Tools. Depending on which version of VMware you are
using, follow the appropriate instructions below.
For VMware Workstation or VMware Player:
1. In the menu bar of the VMware window, click VM or Virtual Machine
and then select Install VMware Tools... from the drop down menu.
2. Click the Install button when prompted.
3. Now launch the XMS web client to finish the installation. (See Starting
the Web Client on page 31.) The web client will display the following
message.
Figure 6. VMware Tools Installation Reminder
4. Click the Details link below the message. This takes you to the Settings >
General > Status page. Click on the Install button in the VMware Tools
section.
For ESXi and VSphere:
1. Log in to the VSphere client.
2. Click to select the running virtual machine. From the Inventory menu on
the menu bar, select Virtual Machine > Guest > Install/Upgrade
VMware Tools and proceed as prompted.

Licensing - The XMS server requires a license for full operation. The license is
entered via the client, and will automatically be requested the first time you
start the client.
Management System
16 XirrusManagementSystemProducts
3. Now launch the XMS web client to finish the installation. (See Starting
the Web Client on page 31.) The web client will display the message
shown in Figure 6.
4. Click the Details link below the message. This takes you to the Settings >
General > Status page. Click on the Install button in the VMware Tools
section.
Correct Network Port Problems
The XMS Virtual Appliance obtains network connectivity by binding interfaces
on the virtual machine with physical ports on the host computer. In some
installations, VMware Player and VMware Workstation may associate the XMS
Virtual Appliance with a physical port that is not connected to the network, and
the Appliance will have no connectivity.
VMware Player and VMware Workstation have a separate utility, vmnetcfg.exe,
that you may use to set the interface bindings explicitly to correct this problem.
The following commands are for a Windows-based host computer. For other
operating systems, modify them accordingly.
1. Current versions of VMware Player and VMware Workstation require
you to extract vmnetcfg.exe from the installation file manually, using the
following steps. Older versions of these products may have made the
utility accessible automatically. Search your computers VMware
installation directory (well call it <VMware> in these instructions) and
subdirectories for the file vmnetcfg.exe. If found, skip to Step 5.
If not found, continue to the next step.
2. Open an elevated command prompt (Run as Administrator). Browse to
the directory that contains the VMware installation file.
3. Run the installation file with the following options to extract the contents
of the installation file to the c:\vmware folder (create the c:\vmware
folder first if necessary):
<install-file.exe> /e c:\vmware
For example:
Management System
XirrusManagementSystemProducts 17
VMware-player-3.0.0-203739.exe /e c:\vmware -or-
VMware-workstation-full-8.0.1-528992.exe /e c:\vmware
Use the actual name of the installation file supplied to you by VMware,
which may be different than the names shown above.
4. Browse to c:\vmware and open the file network.cab. This is a
compressed file that should open in most file compression software.
Extract the contents of the cab file to the <VMware> directory. For
example:
C:\Program Files\VMware\VMware Player -or-
C:\Program Files\VMware\VMware Workstation
5. Browse your <VMware> directory. Find and run vmnetcfg.exe.
.
Figure 7. Using vmnetcfg.exe
6. Highlight the VMnet0 interface (at the top of the page).
7. Under VMnet Information, select Bridged (connect VMs directly to the
external network).
Management System
18 XirrusManagementSystemProducts
8. On the Bridged to: line, select the physical interface that provides
network connectivity on your host computer.
9. Click OK.
Management System
GettingStartedwithXMS 19
Getting Started with XMS
This chapter describes how to get started using XMS.
Section headings for this chapter include:
XMS Port Requirements on page 20
If you are running XMS Cloud, see:
Getting Started with XMS Cloud on page 23
If you are running your own XMS server, see:
Starting and Managing the XMS Server on page 24
Initial Server Setup for Virtual Appliances on page 28
About the XMS User Interface on page 28
Shutting Down the XMS Server on page 29
Management System
20 GettingStartedwithXMS
XMS Port Requirements
A number of ports are used by XMS and by various Array features and must not
be blocked by firewalls.
For XMS Cloud
XMS Cloud requires outbound TCP port 443 for activation and outbound TCP
port 5000 for ongoing management of the Arrays. (It is possible to customize port
5000 at the time you place your order.) All other ports listed in the table on the
next page are not applicable to XMS Cloud.
For Customer-Hosted XMS
Firewall
XMS Server XMS Client*
L2 Switching
Infrastructure
SMTP Server*
Internal
Resources
External Network /
Internet
Ports:
9090, 9091
Ports:
161, 162, 443
SSID Traf7c on
VLANs A, B, etc.
Management over
Native VLAN
Traf7c from Arrays
VLAN B
Traf7c from Arrays
VLAN A
Trunked 802.1q
VLAN Connection
Ports:
25
* XMS Client and SMTP Server may be internal or external resources.

The Port Requirements table on page 21 lists ports and the features that require
them.
Figure 8. Sample Port Requirements for XMS (non-Cloud Versions)
Management System
GettingStartedwithXMS 21
Note that Array port requirements are included in the table for your
convenience some of the Array ports shown are unrelated to communication
with XMS. If you are using a feature, please make sure that the ports that it
requires are not blocked by firewalls or other policies, and that they do not
conflict with any other port assignments.
As an example, some XMS port requirements are illustrated in Figure 8. XMS
requires ports 161, 162, and 443 to be passed between Arrays and the XMS server.
Similarly, ports 9443, 9090, 9091, and 9092 are required for communication
between the XMS server and XMS clients, and port 25 is typically used by the
XMS server to access an SMTP server to send email notifications.
The following table lists port requirements for the Array and for XMS, how they
are used, and whether they may be changed.
Port Application Peer Configurable
XMS
22 tcp SSH Arrays Yes
25 tcp SMTP Mail Server Yes
123 udp NTP NTP Server No
161 udp SNMP Arrays No
162 udp SNMP Trap Receiver Arrays Yes
514 udp Syslog server Arrays
Via XMS
config file
Ping Arrays No
1099 tcp RMI Registry Internal* No
2000 tcp XMS Back-end Server Internal* No
2022 tcp SSH XM-3320/3340/3360 Yes
3306 tcp MySQL Database Internal* No
8001 tcp Status Viewer Internal* No
Management System
22 GettingStartedwithXMS
8007 tcp Tomcat Shutdown Internal*
During
installation
8009 tcp Web Container Internal*
During
installation
9090 tcp XMS Client Server XMS client
Via XMS
config file
9091 tcp XMS Client Server XMS client
Via XMS
config file
9092 tcp XMS Client Server XMS client
Via XMS
config file
9443 tcp XMS WMI SSL XMS web client Yes
* Internal to XMS Server, no ports need to be unblocked on other network devices
Array
icmp Ping XMS server No
20 tcp
21 tcp
FTP Client Yes
22 tcp SSH Client Yes
23 tcp Telnet Client Yes
25 tcp SMTP Mail Server Yes
69 udp TFTP TFTP Server No
123 udp NTP NTP Server No
161 udp SNMP XMS Server No
162 udp
SNMP Traphost Note -
Up to four Traphosts
may be configured.
XMS Server
Yes - but
required by
XMS
443 tcp HTTPS (WMI,WPR) Client Yes
514 udp Syslog Syslog Server Yes
Port Application Peer Configurable
Management System
GettingStartedwithXMS 23
Getting Started with XMS Cloud
Use the browser-based XMS web client to manage your Xirrus network.
.
Figure 9. Logging in to the Web Client
To access the web client, set your browsers URL to cloud.xirrus.com. Log in with
the User name (this will be an email address) and Password assigned to you by
Xirrus. The first time you log in, you are prompted to read and accept the End
User License Agreement for XMS Cloud. After you accept, you are prompted to
1812, 1645
udp
RADIUS (some servers
use 1645)
RADIUS Server Yes
1813, 1646
udp
RADIUS Accounting
(some servers still use
1646)
RADIUS Accounting
Server
Yes
2055 udp Netflow Client Yes
5000 tcp Virtual Tunnel VTUN Server Yes
22610 udp XRP (Xirrus Roaming) Arrays Yes
22612 udp Xircon (Console Utility) Admin Workstation Yes

Wireless Arrays must be running ArrayOS Release 6.4 or above to be
managed by XMS Cloud. You cannot use XMS Cloud to upgrade Arrays
to Release 6.4 from an earlier release.
Port Application Peer Configurable
Menulinks
Management System
24 GettingStartedwithXMS
change your password from the one initially assigned to you. Once you have
done so, the Dashboard is displayed.
Figure 10. The Web Client Menu
To view other pages and see the choices for managing your wireless network, use
the main menu bar, as shown above.
Proceed to the next chapter, The XMS Web Client, to begin managing your
network.
Starting and Managing the XMS Server
Non-XMS Cloud users may manage the XMS server using its management tools:
Managing XMS on a Management Appliance or Virtual Appliance
Managing XMS on XM-3300 and XMS-9000-WIN
NOTE: For full operation, the XMS server must have a license installed.
Managing XMS on a Management Appliance or Virtual Appliance
On the XM-3320/3340/3360 and the Virtual Appliance, the XMS server is started
automatically when your computer is restarted. (For other platforms, see
Managing XMS on XM-3300 and XMS-9000-WIN on page 26). Use the
browser-based XMS web client (Figure 11) to perform mandatory initial
configuration, to restart or reboot the server, and for server maintenance.
Management System
GettingStartedwithXMS 25
.
Management
links
Figure 11. Server Management using the Web Client
To access the web client, set your browsers URL to the XMS server machines IP
address or host/domain name, followed by a:9090. For example, http://
192.168.10.40:9090. You will be redirected to a secure connection (https://
<server>:9443), and the login page will be displayed.
NOTE: XMS web client access to the XMS server requires access to ports 9090 and
9443. Make sure that these ports are open in any firewalls between clients and the XMS
server.
Log in to the web client (the default for both fields is admin). In a few moments it
will prompt you to run the XMS Setup Wizard. This will lead you through
entering your XMS server license and setting up discovery for your network of
wireless Arrays. Proceed to Initial Server Setup for Virtual Appliances on
page 28 to perform required initial setup on the server.
NOTE: You may use the Command Line Interface (CLI) to manage the XMS server via
SSH. Access it at port 2022 and log in using admin/admin. Do not use port 22 for CLI.
If XMS is not running properly, you may click the Restart Application button on
the lower left of the Status page to restart the XMS server software. If the server is
currently running, an orderly shutdown will be performed first.
The Reboot Appliance button will reboot the Appliance this will shut down
XMS related processes in an orderly manner before rebooting. Rebooting and
restarting will take about two minutes on a new Appliance. As XMS is used and
Management System
26 GettingStartedwithXMS
the database grows, startup integrity checks will take longer. (For shutdown, see
Shutting Down the XMS Server on page 29.)
Managing XMS on XM-3300 and XMS-9000-WIN
The XMS server is started automatically when the XM-3300 is restarted.
Alternatively, you may start the XMS server using the Xirrus Server Management
Tool (XSMT). XSMT is used to start, stop, or view the status of the server. To start
XSMT, use the Windows Start button > All Programs > Xirrus > Xirrus
Management System > XA-3300-CC. The Server Console window is displayed,
and then the XSMT window. When the Start button (at the bottom of the XMS
Server Manager tab of XSMT) is enabled, click it to start the server.
During the server initialization process, the XSMT Logs panel displays high-level
progress messages, and the Server Console displays detailed messages.
(Figure 12)
During the installation process, there are options to have XSMT start the XMS
server automatically, or to wait for the administrator to explicitly start it. If all four
Required Services indicators do not turn green, you may start the XMS server by
clicking the Start button on the lower left when XSMT enables it.
Console
XSMT
Management System
GettingStartedwithXMS 27

Figure 12. XSMT Window, Showing Typical Running Status
When XMS server startup is finished, the XMS Server Manager tab of XSMT will
indicate that the server is up and running. Figure 12 shows an example of a
successful server initialization process. The state of the topmost three servers is
Running, and they are shown in green.
When the XMS server is ready for clients to be started, the Logs section on the
right of the window will display:
*** The XMS Ser ver i s now r unni ng
Poi nt your br owser t o ht t p: / / <XMS Ser ver I P>: 9090/
or l ocal l y f r omt hi s comput er , use ht t p: / / l ocal host : 9090/
To access the web client, set your browsers URL to the XMS server machines IP
address or host/domain name, followed by a:9090. For example, http://
192.168.10.40:9090.
NOTE: XMS web client access to the XMS server requires access to ports 9090 and
9443. Make sure that these ports are open in any firewalls that exist between clients and
the XMS server.
Management System
28 GettingStartedwithXMS
Log in to the web client (the default for both fields is admin). In a few moments it
will prompt you to run the XMS Setup Wizard. This will lead you through
entering your XMS server license and setting up discovery for your network of
wireless Arrays.
When the server starts for the first time, it will initialize the database.
For more information on using XSMT, see Managing XMS on XM-3300 and
XMS-9000-WIN Systems on page 624.
NOTE: The XMS server does not have a default backup schedule, so it is very important
for you to create a backup schedule after installation. After you start an XMS client, see
Database Backup Settings on page 575.
Initial Server Setup for Virtual Appliances
Use the XMS web client to complete the following steps on the XM-3320/XM-
3340/XM-3360 and on virtual appliances in order to configure XMS for proper
operation.
When you start the XMS server for the first time, you must configure basic
settings by following the steps in:
XMS Setup Wizard
When those steps are complete, proceed to:
Set the XMS polling interval based on your deployment size (see Polling
Settings on page 601.
About the XMS User Interface
The XMS Web Client is a very fast and efficient application for viewing the status
of your Array network and performing network management tasks.
The Dashboard provides an at-a-glance overview of the health of your Array
network; network discovery may be fine-tuned; RF heat maps display the RF
coverage provided by your Arrays; alarms and events are displayed; pages for
Arrays, IAPs, Stations, and SSIDs show detailed information and allow
configuration; rogue devices are monitored; and Array configuration policies may
Management System
GettingStartedwithXMS 29
be configured. The web client has special features such as bulk editing, which
allows you to quickly configure selected identical settings on a number of Arrays
in one step. Reports on system performance may be created.
In XMS Release 6.5 and above, XMS no longer has a Java client interface.
Shutting Down the XMS Server
There is a correct way and an incorrect way to shut down the XMS server.
Shutting down the server incorrectly can cause problems the next time you start
XMS. If you need to shut down the server, you must use the following procedure:
1. Terminate all clients .
2. For the XM-3320/3340/3360 and Virtual Appliance servers in the
Status page of the XMS web client, click the Shutdown Appliance button
at the bottom of the window.
For XM-3300 and XMS-9000-WIN servers click the Stop button in the
XMS Server Manager tab of the Xirrus Server Management Tool (XSMT).
When prompted, enter your password. The default username and
password are both admin (all lowercase). See XSMT - Shutting Down
the XMS Server on page 632 for more information.
3. You will be notified when the server has shut down successfully. Note
that on XM-3300 and XMS-9000-WIN servers the database will remain
running this is not a problem. On all other servers, the database server
will be shut down as well.
4. When the XMS server has shutdown successfully you may shut down
your computer.
Management System
30 GettingStartedwithXMS
Management System
TheXMSWebClient 31
The XMS Web Client
The Web Client provides a fast, efficient interface for checking wireless network
performance and for selected management tasks.
Starting the Web Client
Xirrus supports the latest version of the following browsers: Internet Explorer,
Mozilla Firefox, Chrome, or Safari. A secure web browser is required.
.
Figure 13. XMS Start Window Showing XMS Cloud Login
To start the web client for XMS Cloud, point your workstations browser to
cloud.xirrus.com. Log in with your User name and Password. (Figure 13)
To start the web client for other XMS servers, point your workstations browser to
the IP address or hostname for the XMS server machine followed bya:9090. For
example, if the IP address is 192.168.10.40, point your browser to http://
192.168.10.40:9090. You will automatically be redirected to an HTTPS connection
(if you prefer, you may connect directly via HTTPS using port 9443, with a URL in
the form https://<ip address or hostname>:9443). When the XMS splash window

Wireless Arrays must be running ArrayOS Release 6.4 or above to be
managed by XMS Cloud. You cannot use XMS Cloud to upgrade Arrays
to Release 6.4 from an earlier release.
Management System
32 TheXMSWebClient
appears, log in with your User name and Password. The default login is admin/
admin.
Web Client Menus
The web client has four major menus, selected by links at the top of the window.
Each menu offers a selection of pages which manage different XMS functions. The
menus are described in the following sections:
About Monitor Pages on page 32
About Configure Pages on page 34
About Reports Pages on page 37
About Settings Pages on page 39
Figure 14. Mode Selection in XMS Web Client
About Monitor Pages
Monitor Menu
These pages display information about the current status of the network. Click
the Monitor link at the top of the window to see the list of pages.
Figure 15. XMS Cloud Web Client Monitor Functions
Monitor Menu
Management System
TheXMSWebClient 33
Figure 16. XMS Web Client Monitor Functions (non-Cloud)
The monitor options for XMS Cloud are shown in Figure 15; the options for non-
Cloud versions are shown in Figure 16. These are primarily read-only pages,
although most of the pages have links to click to drill down for details, and allow
you to export data to a file. The Monitor link always opens to the Dashboard
page.
Monitor pages include the following. Click one of the links below for more
information.
Overview
Dashboard
Maps
Arrays
Switches
IAPs
SSID
Stations
Legacy APs (not available in XMS Cloud)
Management System
34 TheXMSWebClient
Security
Rogues
IDS Events (not available in XMS Cloud)
Troubleshooting
Station Assurance (not available in XMS Cloud)
Alarms
Events
Power
PoGE (not available in XMS Cloud)
Application Control
Application ControlOverview
About Configure Pages
Configure Menu (requires read-write privileges)
Figure 17. XMS Cloud Web Client Configure Functions
Configure Menu (requires read-write privileges)
Management System
TheXMSWebClient 35
Figure 18. XMS Web Client Configure Functions (non-Cloud)
These pages perform specific wireless network configuration actions. Some of
these pages are particularly powerful, allowing you to make bulk configuration
changes over multiple IAPs and Arrays in one step. Click the Configure link at
the top of the window to see the list of configure pages. The configure options for
XMS Cloud are shown in Figure 17; the options for non-Cloud versions are
shown in Figure 18. The Configure link always opens to the Arrays page, which
is the same as the Monitor > Arrays page. You must be logged in to XMS as an
administrator with read-write privileges to see the Configure link.
Configure pages include the following. Click a link below for more information.
Array Configuration
Arrays (Configure)
Profiles
Array Groups
Edit Config Templates
Load Config Template
Deploy Config Template
Custom Field Values
Management System
36 TheXMSWebClient
Switch Configuration
Switches
Power
Port Mappings by Injectors (not available in XMS Cloud)
Port Mappings by Arrays (not available in XMS Cloud)
Port Mappings by Switches (not available in XMS Cloud)
Wireless Configuration
Configure Wireless Settings
Export Wireless Settings
Import Wireless Settings
Network Configuration
Configure Network Settings
Export Network Settings
Import Network Settings
Alarms
Alarm Definitions
Notification Settings
Discovery
Add Devices (not available in XMS CloudXirrus does this for you)
SNMPv2 Settings (not available in XMS Cloud)
SNMPv3 Users (not available in XMS Cloud)
SSH Users (not available in XMS Cloud)
View Networks (not available in XMS Cloud)
Security
SecurityRogue Rules
SSID Spoofing Auto Block
Management System
TheXMSWebClient 37
Xirrus Access Manager
Xirrus Access ManagerArray Configuration
Array Licenses
Deployed Licenses (not available in XMS Cloud)
Export Licenses (not available in XMS Cloud)
Import Licenses (not available in XMS Cloud)
Edit Licenses (not available in XMS Cloud)
Pending Licenses (not available in XMS Cloud)
Array Upgrade
Perform or Schedule Upgrade (not available in XMS Cloud)
Scheduled Upgrades (not available in XMS Cloud)
About Reports Pages
These pages are used to generate reports on the operation of your wireless
network. XMS offers an extensive suite of reports on performance and status,
including such aspects as throughput, error rates, station information, availability,
RF usage, and security.
All of these reports are discussed in detail in Managing Reports on page 289.
Figure 19. XMS Web Client Reports Functions
Click the Reports link at the top of the window to see the list of reports pages.
Reports Mode
Management System
38 TheXMSWebClient
General
View Reports on page 291
The web clients Reports link opens to this page, listing the reports you
have already created and allowing you to view or run these reports.
Create Report on page 297
This page lists all the types of reports available in XMS. Click on a report,
and enter the desired selection criteria. You may then save the report and
run it now or schedule it for later.
Customization
Customize Report Header on page 308
Click this link to customize the appearance of reports by changing the
logo at the top of the report.
Management System
TheXMSWebClient 39
About Settings Pages
For XMS Cloud
For Xirrus Virtual Appliance
or Management Appliance
(XM-3320/3340/3360)
For XMS-9000-WIN
Settings Mode
Figure 20. Settings Menus for XMS Server Platforms
These pages are used to change XMS server settings, such as managing user
accounts. Click the Settings link at the top of the window to see the list of settings
pages. The settings options for XMS differ significantly depending on what type
of XMS server you are using. (Figure 20)
Management System
40 TheXMSWebClient
For example, XMS Cloud includes few server management options, since Xirrus
does almost all of those functions for you, such as database backups and server
software upgrades. For non-Cloud servers, settings include the XMS Setup
Wizard, which guides you through the initial steps for licensing the server and
discovering the network. In addition, if you are using a Xirrus Management
Appliance or Virtual Appliance, pages are offered to configure the appliance. As
shown in Figure 20, these include setting the network address and system date
and time. All of these server administration functions are discussed in detail in
About Managing the XMS Server on page 562.
Settings for Cloud Platforms
The following settings are the only ones offered for XMS Cloud.
General
About XMS Click this to display the current running XMS version as
well as contact information.
Status Shows the running status of the XMS server. For details, see
Viewing XMS Server Status on page 569.
XMS Users
Manage Users manages accounts for XMS users/administrators. See
XMS Users on page 584.
Application
Audit Logshows all of the configuration changes that have occurred on
managed Arrays. For details, see Audit Log on page 617.
Customization
Create Custom Fieldsdefines custom columns to be displayed on
Arrays pages. See Create Custom Fields on page 587.
Create Custom Actionsdefines custom actions to be offered on Arrays
pages. See Create Custom Actions on page 588.
XMS API
API SettingsControls API access to the XMS server. For details, see
API Settings on page 593.
Management System
TheXMSWebClient 41
API Documentationdescribes the API and provides a sandbox for
making sample calls. For details, see API Documentation on page 595.
Settings for All non-Cloud Platforms
The following settings are supported on all platforms other than XMS Cloud.
General
About XMS Click this to display the current running XMS version as
well as contact information.
Status Shows the running status of the XMS server. For details, see
Viewing XMS Server Status on page 569.
Server Logs shows XMS servers operational logs. For details, see
Viewing Server Log Files on page 618.
XMS License manages the license for the XMS software. For details, see
Managing the XMS Server License on page 620.
XMS Users
Manage Users manages accounts for XMS users/administrators. See
XMS Users on page 584.
Backup
Backup sets up XMS database backups. For details, see Database
Backup Settings on page 575.
Application
Email specifies the SMTP server that XMS uses for sending emails. For
details, see Email Settings on page 600.
Polling changes the frequency of polling Arrays. For details, see
Polling Settings on page 601.
SSH Server changes the server address provided to Arrays. For details,
see Changing the SSH Server Address on page 603.
SNMP Trap Receivers the XMS server sends traps to supervisory
software at these addresses when an alarm occurs. For details, see
SNMP Trap Receivers on page 605.
Management System
42 TheXMSWebClient
XMS Setup Wizard initial setup steps for XMS server to enter license
and discover Array network. For details, see XMS Setup Wizard on
page 606.
Audit Logshows all of the configuration changes that have occurred on
managed Arrays. For details, see Audit Log on page 617.
Customization
Create Custom Fieldsdefines custom columns to be displayed on
Arrays pages. See Create Custom Fields on page 587.
Create Custom Actionsdefines custom actions to be offered on Arrays
pages. See Create Custom Actions on page 588.
Support
Array Diag Log Uploaduploads diagnostic information from selected
Arrays to an FTP server.
XMS API
API SettingsControls API access to the XMS server. For details, see
API Settings on page 593.
API Documentationdescribes the API and provides a sandbox for
making sample calls. For details, see API Documentation on page 595.
Settings for Management Appliance and Virtual Appliance
The following settings are only supported on the XM-3320/3340/3360 models of
the Xirrus Management Appliance and on the Virtual Appliance. They provide
functions such as setting the network address and the system time for the host.
Web ServerConfigures HTTP and HTTPS access to the XMS server,
including the ports used. For details, see Web Server on page 604.
System
Network Configures IP and other port settings on the Appliance. For
details, see Network Settings on page 571.
Date & Time Configures system time on the Appliance. For details, see
Date and Time Settings on page 572.
Management System
TheXMSWebClient 43
RAID StatusShows status of the servers RAID storage device, if the
server machine is using one. For details, see RAID Status on page 574.
Maintenance
Upgrade Upgrade the XMS server software. For details, see
Performing Server Upgrades on page 621.
Factory Reset Reinitializes the XMS server and database. For details,
see Resetting the XMS Server on page 622.
Management System
44 TheXMSWebClient
Dashboard
The web client Dashboard gives you an at-a-glance overview of all system status
and activity. Administrators can quickly assess system health and overall system
usage, as well as viewing alarm status.
Figure 21. Dashboard
Most Recent Active Alarms
Application Control
Stations
Time of last update; Add Widget
Rogue Overview
Array and IAP Status
Management System
TheXMSWebClient 45
The following sections describe the use of the Dashboard:
Dashboard Overview on page 45
About Dashboard Data on page 46
Application Control on page 47
Array and IAP Status on page 51
Most Recent Active Alarms on page 52
Stations on page 53
Rogue Overview on page 57
Array Software and License Versions on page 58
Dashboard Overview
When you start the web client, the Dashboard is initially displayed. To navigate to
it when you have another page displayed, simply click the Monitor link at the top
of the page and then select Overview: Dashboard (Figure 16 on page 33).
Figure 22. Three-column Arrangement of Widgets
You may customize the Dashboard to your liking. To rearrange the widgets (i.e.,
sections), simply click the title bar of a widget and drag and drop it to the desired
location. You may even move widgets to the right to make a third or a fourth
column to make a horizontal display as shown in Figure 22, or arrange them in
Management System
46 TheXMSWebClient
two columns to make a vertical display. Click the Restore Defaults link near the
top to return the layout to its original appearance. Changes that you make will
only apply to logins by your accountother users dashboard views will not be
affected.
Click the settings link in the widgets title bar to change the title of any
widget and/or have it display only data from a selected SSID or Array Scope
(profile network or group of Arrays). You may delete any widget using the delete
link in its title bar. Use the Add Widget link near the top of the Dashboard to
restore deleted widgets or add others. You may even add the same widget
multiple times with different settings, for example, to show a different profile
network in each.
Figure 23. Change Widget Settings
In general, a count is faded if its value is zero. For example, if no Arrays are down
in the Status widget, then the count and its icon are faded. This helps present the
at-a-glance health of the wireless network by eliminating the display of red
symbols when there are no devices down.
About Dashboard Data
The Dashboard displays data for all Arrays in the XMS managed network by
default, although you may have a widget display data for just a selected Array
Scope or a selected SSID by changing its settings. All widgets are updated to
contain only data related to the selected Arrays (except for Alarms, which always
Management System
TheXMSWebClient 47
shows all alarms). This will not affect data display on other pagesthey will
continue to display data for all Arrays.
The Dashboard is automatically refreshed at frequent intervals you do not have
to refresh explicitly. The time of the most recent update is shown towards the
upper left, as seen in Figure 21. Note that some values displayed in the
Dashboard may lag with respect to actual current values items in the XMS
database are polled (updated) at differing intervals. When the Dashboard is
refreshed, it simply picks up the current values in the database. The XMS server
does not poll Arrays to update all status or statistics in the database specifically
for a Dashboard refresh. Each data item in the database will be refreshed at
whatever rate is defined for it. For more details on the polling rate and how to
change it, please see Polling Settings on page 601 or XSMT - Advanced
Settings on page 638.
The Dashboard refreshes data at the following rates by default:
Performance data is updated on the Dashboard every 30 seconds. (This is
true for Arrays running Release 3.1 and higher software images.)
Data for the Dashboard is updated at least every two minutes.
Alarms occur in real time. Traps generated by Arrays and other events
with a severity greater than informational are displayed as alarms.
Application Control
The Application Control widgets provide real-time visibility of application usage
by users across the wireless network for the selected Array Scope (see About
Dashboard Data on page 46), categorized in a number of ways. Each XR Array
uses Deep Packet Inspection (DPIavailable only on XR Arrays) to determine
what applications are being used and by whom, and how much bandwidth they
are consuming. For more information, see Application ControlOverview on
page 104.
Four widgets describe Application Control:
Station Application Category Usage Breakdown
Station Application Usage Breakdown
Station Application Category Usage over Time
Management System
48 TheXMSWebClient
Station Application Usage over Time
Station Application Category Usage Breakdown
Figure 24. Dashboard - Station Application Category Usage Breakdown
This provides a breakdown of the categories of applications being used on the
selected Arrays. Traffic is analyzed by what types of applications are in use, such
as Games or Collaboration, rather than by specific application names. This gives
you an overview of the categories of work (or not work!) for which the wireless
network is being used.
Management System
TheXMSWebClient 49
Station Application Usage Breakdown
Figure 25. Dashboard - Station Application Usage Breakdown
This provides a breakdown of the applications being used on the selected Arrays.
Traffic is analyzed for the applications in use, such as SNMP or Facebook.
Station Application Category Usage over Time
Click here to select a Category
Click here to select a Time Period
Figure 26. Dashboard - Station Application Category Usage over Time
Management System
50 TheXMSWebClient
This graph shows the amount of network traffic used by a selected category of
application over time, on the selected Arrays. Select a Category of application and
a time period as shown in Figure 26.
Station Application Usage over Time
T
Click here to select an Application
Click here to select a Time Period
Figure 27. Dashboard - Station Application Usage over Time
This graph shows the amount of network traffic used by a selected application
over time, on the selected Arrays. Select an application and a time period as
shown in Figure 27. When selecting an application, select a category first - this
helps narrow down the final selection of application, as Arrays recognize
hundreds of applications.
Management System
TheXMSWebClient 51
Array and IAP Status
The Array and IAP Status widget summarizes the number of each that are up or
down. Use the settings link on the title bar if you wish to filter the results to
display values for a selected Array Group only (see Array Groups on
page 114).
Figure 28. Dashboard - Array and IAP Status
Array Status Details
This is a summary of the status of the selected Arrays that are known to XMS. The
entries show the count of Arrays that are up or down, and the total count. Click
on a count, and the web client will display the Arrays or IAPs page, filtered to
show only entries that have the status that you selected.
The following status counts are shown:
Up (green) the number of Arrays that are up, in the selected group.
Click this button to show only Arrays whose status is up in the Arrays
page.
Down (red) the number of Arrays that are down, in the selected group.
An Array is considered to be down if XMS has been unable to
communicate with it for over three minutes. Click this button to show
only Arrays that are down in the Arrays page.
Total the total number of Arrays in the group that are known to XMS.
Click this button to show all Arrays in the Arrays page, regardless of
status.
Management System
52 TheXMSWebClient
IAP Status Details
This is a summary of the status of all radios (IAPs) on Arrays that are known to
XMS in the selected Array group. The entries show the count of IAPs at each
status value. Each entry is a linkclick it to display the IAPs page, with the IAP
list filtered to show only those IAPs that have the selected status value.
The following status counts are shown:
Up (green) the number of IAPs that are up. Click this button to show
only IAPs whose status is up in the IAPs page.
Down (red) the number of IAPs that are down. Click this button to
show only IAPs that are down in the IAPs page.
Disabled (gray) the number of IAPs that are not enabled on Arrays.
Click this button to show only IAPs that are disabled in the IAPs page.
Most Recent Active Alarms
This table lists the most recent alarms generated by your wireless network. For
each alarm, the dashboard shows the severity, the date, and the beginning of the
description. To see more information for an alarm in the list, click it to view the
Alarm Details. All severity levels are displayed Critical, Major, Minor, Warning,
and Clear. Alarms are shown only for Arrays in the selected Array Group.
Figure 29. Dashboard - Recent Alarms
Management System
TheXMSWebClient 53
To see a complete list of wireless network alarms, use the web client Alarms page
(see Alarms on page 97).
Alarm severity classifications
Critical Red
Major Orange
Minor Gold
Warning Yellow
Clear Green
Each entry is a link. Click it, and additional details are displayed.
Stations
The Stations widgets summarize the number of stations associated to Arrays for
the selected Array Group (see About Dashboard Data on page 46), categorized
in a number of ways.
Figure 30. Dashboard - Station Count
Seven widgets describe stations:
Station Count
Station Counts by Operating Mode
Station Counts by Capability
Management System
54 TheXMSWebClient
Station Counts by Manufacturer
Station Counts by Class
Station Counts by SSID
Station Throughput
Station Count
This shows the total number of stations associated to Arrays known to XMS, and
plots the number of stations over time. (Figure 30) Select the desired time period
for the graph 24 hours is the default.
Station Counts by Operating Mode
Figure 31. Dashboard - Station Counts by Operating Mode
This provides a breakdown of stations by band and by Wi-Fi mode: the number of
802.11n stations (in the 5GHz and 2.4 GHz bands), 802.11a, 802.11bg, and 802.11b
stations that are currently associated to the selected Arrays.
Management System
TheXMSWebClient 55
Station Counts by Capability
Figure 32. Dashboard - Station Count by Capability
This widget is similar to Station Counts by Operating Mode. Instead of
displaying the types of station connections, this widget shows the wireless
capabilities of the connected stations.
Station Counts by Class
Figure 33. Dashboard - Station Count by Class
This provides a breakdown of the number of stations by class of device, for
example, phone, tablet, notebook, etc. A pie chart shows the proportion of each
type.
Management System
56 TheXMSWebClient
Station Counts by Manufacturer
Figure 34. Dashboard - Station Count by Manufacturer
This provides a breakdown by station manufacturer of the number of stations that
are currently associated to the selected Arrays. The most common manufacturers
of stations in your network environment are listed, with those having the highest
number of stations listed first. Up to ten manufacturers are listed.
Station Counts by SSID
Figure 35. Dashboard - Station Counts by SSID
This provides a network breakdown of the number of stations by the SSID to
which they have associated, in both tabular and graphical form. Each SSID is
listed by name, along with its station count and the percentage of stations
connected to it.
Management System
TheXMSWebClient 57
Station Throughput
Figure 36. Dashboard - Station Throughput
This graphs the aggregate station throughput of your wireless network over time.
Select the desired time period for the graph 24 hours is the default.
Rogue Overview
This widget provides a quick snapshot of the security status of the selected Array
Group in the wireless network (see About Dashboard Data on page 46),
including counts of rogue APs. Each entry is a link click it to display on the
selected items on the Rogues page.
Figure 37. Dashboard - Rogue Overview
For more information about security and intrusion detection, please see Rogues
on page 89.
This is a summary of the more dangerous APs that have been detected by the
selected Arrays. Categories that have a zero count are shown with a green check
mark; categories that have a non-zero count are flagged in orange. Rogues that
you have already classified are not shown. The categories shown are:
Management System
58 TheXMSWebClient
Unclassified: When a device is initially detected, it is unclassified, which
simply means that no one has classified it yet. To classify a device, see
Rogues on page 89.
Ad hoc: An ad hoc wireless network is typically a network formed
between two or more stations that are communicating with each other
directly without going through a normal AP. This line shows a count of
ad hoc nodes detected by Array APs. Ad hoc networks can disrupt the
performance of your wireless network by contributing additional RF
interference to the environment.
On my channels: This is the number of detected rogues that are on
channels that are the same as or adjacent to the channels used by Array
IAPs that are in operation. All classes of rogues are included except for
Approved and Known devices.
Spoofing my SSIDs: This is the number of detected rogues that are using
the same SSIDs as your wireless network. All classes of rogues are
included except for Approved and Known devices.
Array Software and License Versions
These widgets summarize the software versions and license versions for Arrays
in the selected Array Group (see About Dashboard Data on page 46).
Figure 38. Dashboard - Array Software Versions
Management System
TheXMSWebClient 59
Two widgets describe versions:
Array Software Versions
Array License Versions
Array Software Versions
This shows the total number of Arrays running recent ArrayOS software versions,
in both tabular and graphical form. (Figure 38)
Array License Versions
Figure 39. Dashboard - Array License Versions
This shows the total number of Arrays having various ArrayOS license versions,
in both tabular and graphical form.
Management System
60 TheXMSWebClient
Arrays
The web client Arrays page lists all of the Arrays being managed by XMS, and
allows you to perform selected management functions on them. You may reboot
Arrays, gather diagnostic logs, or remove Arrays from the XMS database.
The following sections describe the Arrays page:
About Using the Arrays Page
The Arrays List
The Arrays Toolbar
Array Details
To perform bulk configuration on Arrays, please see Configure Network
Settings on page 145 and Discovery on page 162.
Figure 40. Arrays Page (non-Cloud version shown)
About Using the Arrays Page
A number of basic operations are available on the Arrays page to allow you to
customize it for your own use:
Current Array Scope
Select Columns
Export
Select Rows
Rearranging and Resizing Columns in a Table
Management System
TheXMSWebClient 61
Sorting
Searching
Current Array Scope
In the web client, Current Array Scope allows you to filter the data displayed so
that only information for members of the selected Array group or profile network
is presented. Select the desired Array Group or Profile from the drop-down list.
For example, if you select a profile network on the The Arrays List window, then
only the Arrays that are members of the selected profile are displayed.
This selection is persistent when you browse to other pages, until you change
Current Array Scope. Thus, if you select a profile on the The Arrays List window
and then open the IAPs window, it will only list IAPs that belong to the selected
Arrays.
Select Columns
The page may be customized by changing the columns that are displayed and the
order of display. If you prefer to use a smaller browser window for XMS and
theres not enough room for all the columns to display, you can use this feature to
select your preferred columns. Click the Select Columns link on the upper right
to display the table column chooser. (
The left hand column shows the columns that will be displayed, with the number
of items selected at the top. To hide a column, select it from the list and drag it to
the right hand (non-selected) list. Similarly, to display a column, select it from the
right hand list and drag it to the desired display order in the selected columns list.
Management System
62 TheXMSWebClient
Figure 41. Table Column Chooser
You may type text into the Search Box shown above the right hand list in
Figure 41 to filter the unused columns list to show only column headers that
contain the specified string. For example, type ip and the list will show three
options: Eth0 IP Address, Gig1 IP Address, and Gig2 IP Address. You may drag
selected items up or down to rearrange the order in which they will be displayed.
There is also a button to Restore Default display settings. Click OK when done.
These changes are persistent on a per-user basis if you log out, they will still
apply the next time that you open the web client.
Export
The Export link above the list may be used to export rows from this page to an
Excel file or to a CSV file a set of comma-separated values that are compatible
with Microsoft Excel. The exported file may be used to provide Xirrus Customer
Support with a snapshot of the configuration of your network, at their request. All
rows will be exported, but only the displayed columns will be exported.
Rearrange
column
display order
Displayed Columns Search Box Unused Columns
Management System
TheXMSWebClient 63
When you click Export, a dialog box allows you to select the file format. Click the
Export button again to browse to the destination folder and specify the filename.
Select Rows
Simply click the checkboxes of the rows you wish to select. You may then click
function buttons to perform operations on the selected entries. You may click the
checkbox in the header row to select all rows. Click again to deselect all rows. To
select a number of consecutive rows, you may click the checkbox of the first
desired row. Then use Shift+Click to select the checkbox of the last desired row.
If the list contains many entries, use the scroll bar on the right to find the desired
entries (or use Searching).
Rearranging and Resizing Columns in a Table
For easier viewing of list data, you may rearrange columns by dragging the
column header and moving it to the desired position. This is helpful if you wish
to view particular columns in close proximity, or to move less viewed columns to
the right. The new arrangement is saved per user. The next time you log in, you
will see the columns in the same order.
To resize a column, simply drag the right-side edge of the column to expand or
reduce the width of the column. You may auto-size a column by double clicking
on its right edge. The column will automatically expand or shrink to the correct
size so that all data in the displayed rows is visible.
Sorting
To change how the table is sorted, click in any column header to define that
column as the sort criteria. You may click in any column (except the checkbox
column). Click the header for the status column (red or green dots on the left of
the table) to sort Arrays by operating status. In addition, you can choose to have
the results displayed in ascending order or descending order. To do this, simply
click in the same header again to toggle between ascending and descending order.
An arrow in the column header indicates which column was used for sorting and
which order the grid is sorted in.
Management System
64 TheXMSWebClient
Figure 42. Sorting on a Column
Searching
Search
Enter a string in the Search box, and XMS will display a list of matching entries as
you type. The list appears after you type a couple of characters, and is refined as
you continue typing. Results are displayed as links that you may click to go to the
corresponding entry. (Figure 43)
Figure 43. Search Results
Arrays, Stations, Rogues, Group Names, Profile Names, and even WMI menu
options are shown. (Figure 44) If no results are displayed, then no matching
entries could be found.
Management System
TheXMSWebClient 65
The following fields are searched:
ArraysHostname, Location, Gigabit1 IP Address, Ethernet0 IP Address,
Management IP Address, Software Version, Ethernet0 MAC Address,
Gigabit1 MAC Address, Gigabit2 MAC Address, Serial Number, License
Key, Profile.
RoguesSSID, BSSID, Manufacturer.
StationsMAC Address, IP Address, NetBIOS, Hostname, Username,
Device Type, Device Class, SSID, Manufacturer.
Figure 44. Search Results include Web Client Menu Options
The Arrays List
The Arrays List (Figure 40 on page 60) shows Arrays that have been discovered
by XMS. Only Arrays that belong to the group selected in Current Array Scope
are displayed. To search for a particular Array, see Searching on page 64. The
Arrays Toolbar allows you to perform a number of operations selected Arrays.
Click on an Arrays Hostname to access a variety of Array Details pages.
For each Array, the following information is shown by default:
A green or red dot showing the current status of each Array
The Hostname
The Management IP Address of the Array
The Location of the Array (if this information was configured on the
Array)
The Model of the Array
The number of Stations associated to this Array
Management System
66 TheXMSWebClient
The AOS version running on the Array
The Profile network that the Array is a member of, if any (see Managing
by Profiles on page 205)
You may customize the columns shown in this list many more columns are
available. For example, in XMS Cloud, selecting the Licensed Features column is
the best way to see the features supported on all of your Arrays. See Select
Columns on page 61.
The Arrays Toolbar
The Arrays toolbar offers functions for Array management, including
configuration, gathering diagnostic information, rebooting selected Arrays, and
capturing packets. This toolbar is visible to XMS users with read-write privileges.
XMS users with read-only privileges will see a restricted toolbar that only
includes options for Refresh, Pull Diagnostic Logs, Pull Config, and Packet
Capture.
Figure 45. The MonitorArrays Page Toolbar

A newly discovered Array will automatically be added to the default profile
network, if one has been specified. See Managing by Profiles on
page 205 and the Default button in The Profiles Toolbar on
page 208.

An Arrays Host Name will typically be used to identify the Array
throughout the XMS user interface. In places where a specific attribute such
as IP address is called out, then that value will be shown.
Management System
TheXMSWebClient 67
Select one or more Arrays in the list by clicking their checkboxes in the first
column. You may click the checkbox in the header row to select all Arrays, or click
again to deselect all. The operations available are very similar to those offered on
the Configure Arrays Toolbar. See The Configure Arrays Toolbar on page 107
for details.
Array Details
By clicking the Hostname of an Array in The Arrays List, you may view a variety
of details about the selected unit.
Array DetailsGeneral on page 68
Array DetailsConfiguration on page 69
Array DetailsSystem on page 70
Array DetailsArray Groups on page 71
Array DetailsIAPs on page 71
Array DetailsStations on page 72
Array DetailsSSIDs on page 72
Array DetailsStation Assurance on page 73
Array DetailsApplication Control on page 73
Array DetailsIDS on page 75 (not available for XMS Cloud)
Array DetailsRogues on page 76
Array DetailsEvents on page 76
Array DetailsUptime on page 77
Management System
68 TheXMSWebClient
Array DetailsGeneral
This page shows the status of the Array, time of the current and previous boot,
and graphs over time of wired and wireless throughput and station counts.
Figure 46. Array Details: General
It also offers a number of useful Array management functions. For more
information on these functions, see The Configure Arrays Toolbar on
page 107. One function, the Array WMI button, is only available on non-Cloud
XMS servers. Click this button to open a browser window for the current Arrays
Web Management Interface.
Management System
TheXMSWebClient 69
Array DetailsConfiguration
This page has an extensive menu of options for changing settings on the selected
Array. It is described in its own chapter. See Configuring a Wireless Array on
page 393.
Figure 47. Array Details: Configuration
Management System
70 TheXMSWebClient
Array DetailsSystem
This page shows system information for the Array, including serial numbers for
major components, software versions and licensed features, and MAC addresses
for wired and wireless interfaces. IAP MAC addresses are shown as a range. For
example, if an Array shows MAC addresses from 00:0f:7d:30:69:00-30:69:ff,
addresses are assigned from this pool, starting at 00:0f:7d:30:69:00. Each SSID on
an IAP will have its own address assigned.
Figure 48. Array Details: System
Management System
TheXMSWebClient 71
Array DetailsArray Groups
This page lists the groups to which the Array belongs, if any. An Array may
belong to multiple groups. To add this Array to an additional group, click Add to
Group and select the desired group from the drop-down list. You may also choose
to Create a new group. Enter the name of the new group in the dialog box and
click OK. For more details, see Array Groups on page 114.
You may also remove this Array from membership in one or more groups. Select
the groups from which the Array should be removed by clicking their checkboxes
in the first column in the list. Then click Remove from Group(s).
Figure 49. Array Details: Groups
Array DetailsIAPs
This page shows IAP information for the Array, including band and channel
assignments. Each IAP is a linkclick on it to see details for this IAP (see The
IAPs List on page 80). For more information, see IAPs on page 79 and IAP
Settings on page 504.
Figure 50. Array Details: IAPs
Management System
72 TheXMSWebClient
Array DetailsStations
This page lists stations associated to the Array, including station MAC and IP
addresses and hostname, and the device type and class (iPod, laptop, etc.). Each
Station MAC is a linkclick on it to see details for this station. For more
information, see Stations on page 84. Many other columns may be chosen
using Select Columns on page 61.
Figure 51. Array Details: Stations
Array DetailsSSIDs
This page shows SSID information for the Array, including security settings. Each
SSID Name is a linkclick on it to see details for this SSID. Note that the Captive
Portal tab displays the settings for the portal, if any, defined for this SSID on this
Array. Internal Splash or Internal Login portals are shown as the client will see
them . For more information, see SSID on page 81. See SSID Management
Captive Portal on page 478 to create a captive portal on an Arrays SSID.
Figure 52. Array Details: SSIDs
Management System
TheXMSWebClient 73
Array DetailsStation Assurance
This page shows station assurance events for this Array, listing any detected
connectivity issues. For descriptions of the types of problems detected, as well as
the settings to fine-tune station assurance on the Array, please see Station
Assurance on page 95 and the Array Users Guide.
Figure 53. Array Details: Station Assurance
Array DetailsApplication Control
Application control data (Figure 54) provides detailed information about how
your wireless bandwidth is being used on an Array, by application. The category
of each application is also shown. You may select which Time Span to show, and
which VLAN Name or Number to show (or All VLANs).

This page is not available for XMS Cloud.

This feature is only available if the Array license includes Application

Control. See About Licensing and Upgrades on page 194.
Application Control data is only available on XR Series Array models. It is
not available on XN Arrays. For an Array to produce Application Control
data, you must enable the Application Control option in the Configure
menu on the Arrays Toolbar. See The Arrays Toolbar on page 66.
Management System
74 TheXMSWebClient
Figure 54. Array Details: Application Control
In addition to showing traffic statistics, there are two unique and highly useful
columns. Risk estimates the likelihood of an application causing problems for
your business, rated from 1 (low risk, e.g., Google) to 5 (high risk, e.g., BitTorrent).
Risky applications (rated at 4 or 5) are flagged for your attention by highlighting
the entry in red. Productivity estimates the value of an activity to your business,
from 1 (unproductive, e.g., Y8 gaming site) to 5 (productive, e.g., WebEx). Please
see Application ControlOverview on page 104 for more details.
You may click the heading of any column to sort based on that column. Click
again to sort in the reverse order.
Management System
TheXMSWebClient 75
Each Application Name in the list is a link. You may hover over it to display a
tool tip with more information about the application, including a description of
what it does. You may click the link to display a table listing the Arrays on which
this application has been used, and the amount of traffic that it has generated. You
may specify the desired Time Span and/or VLANs to show. If you prefer, you
may show the Stations on which this application has been used instead.
When you find risky or unproductive applications taking up bandwidth on the
network, you can create filters to control them. See Filter Lists on page 550.
Array DetailsIDS
This page shows Intrusion Detection System (IDS) events for this Array, listing
any detected attacks. For descriptions of the types of attacks detected, as well as
the settings to fine-tune IDS on the Array, please see the Array Users Guide.
Figure 55. Array Details: IDS

This page is not available for XMS Cloud.
Management System
76 TheXMSWebClient
Array DetailsRogues
This page shows rogue APs that have been detected by this Array, including band
and channel assignments. For detailed information about a rogue, click its SSID.
For more information about rogues, see Rogues on page 89. To use the Classify
or Locate buttons, see The Rogues List on page 90.
Figure 56. Array Details: Rogues
Array DetailsEvents
This page shows network events detected on this Array. The Message column on
the right describes the event.
Figure 57. Array Details: Events
Management System
TheXMSWebClient 77
Array DetailsUptime
This page shows down time information for the Array. For each down interval, it
shows when the Array went down and came back up, and how long the Array
was down.
Figure 58. Array Details: Uptime
Management System
78 TheXMSWebClient
Switches
These pages are used to manage the Xirrus 24-port XT-5024 and 48-port XT-5048
PoE+ Gigabit wired access switches, as described in Managing Switches on
page 223. You may click on any switch in the list to view Switch Details,
including:
SwitchGeneral Information on page 227
SwitchConfiguration on page 228
SwitchPoE Status on page 240
To specify which Array is being powered by each switch port, see Port
Mappings by Switches on page 132.
Management System
TheXMSWebClient 79
IAPs
The web client IAPs page lists the IAPs on all of the Arrays being managed by
XMS. This is a display-only page, but values may be exported. To change settings
on IAPs, please see Configure Wireless Settings on page 141.
The following sections describe the IAPs page:
About Using the IAPs Page
The IAPs List
Figure 59. IAPs Page
About Using the IAPs Page
A number of basic operations are available on the IAPs page to allow you to
customize it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Export on page 62
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
Searching on page 64
Management System
80 TheXMSWebClient
The IAPs List
The IAPs List (Figure 59 on page 79) shows all of the IAPs on Arrays that have
been discovered by XMS. Only IAPs that belong to the Current Array Scope
(selected on the upper right) are displayed.
For each IAP, the following information is shown by default.
The Array Hostname. Click on this link to show the Array Details page.
The IAP name (e.g., iap4, abgn2, an3, etc.). Click on this link for the IAP
DetailsGeneral page that shows the settings for this IAP. Click the
Stations tab to list the stations that are associated to this IAP.
Figure 60. IAP DetailsGeneral
Whether the IAP is Enabled.
The Band that the IAP is using.
The IAPs current Channel number.
For IEEE 802.11n IAPs, the Bonded Channel for this IAP.
For IEEE 802.11n IAPs, the Bond Mode that was set for this IAP.
The IAPs current Cell Size.
The IAPs current Tx dBm (transmit power) setting.
The IAPs current Rx dBm (receive threshold) setting.
The IAPs current Antenna setting (internal or external).
Management System
TheXMSWebClient 81
SSID
The web client SSID page lists the SSIDs defined in your Array network. This is a
display-only page, but values may be exported.
The following sections describe the SSID page:
About Using the SSID Page
The SSID List
Figure 61. SSID Page
About Using the SSID Page
A number of basic operations are available on this page to allow you to customize
it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Export on page 62
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
Searching on page 64
Management System
82 TheXMSWebClient
The SSID List
The SSID List (Figure 61 on page 81) shows all of the SSIDs defined on Arrays in
your managed network. Only SSIDs defined on Arrays that belong to the Current
Array Scope are displayed.
For each SSID, the following information is shown by default:
The SSID Name.
Click on this link for the SSID DetailsSummary page that shows
performance information including graphs for station count, wireless
throughput and error percentage. (Figure 62 on page 83)
Click the SSID DetailsArrays tab to list all of the Arrays on which this
SSID is defined. You may click the link for any of the Array Host Names
or IP Addresses to show Array Details for that Array.
Click the SSID DetailsStations tab to list all of the stations which have
associated to this SSID. You may click the link for any of the Station MAC
Addresses to show station details for that Array.
Click the SSID DetailsCaptive Portal tab to list all of the Arrays on
which this SSID is defined that also have captive portals defined. Settings
are listed, to make it easy to compare the portal configuration on these
Arrays. See SSID ManagementCaptive Portal on page 478 to create
a captive portal on an Arrays SSID.
The Array Count shows the number of Arrays on which this SSID is
defined.
The Station Count shows the number of stations associated to this SSID.
Management System
TheXMSWebClient 83
Figure 62. SSID DetailsSummary
Management System
84 TheXMSWebClient
Stations
The web client Stations page lists the stations that are associated to all Arrays
within your managed network. This is a display-only page, but values may be
exported.
The following sections describe the Stations page:
About Using the Stations Page
The Stations List
Figure 63. Stations Page
About Using the Stations Page
A number of basic operations are available on the Stations page to allow you to
customize it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Export on page 62
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
Searching on page 64
Management System
TheXMSWebClient 85
The Stations List
The Stations List (Figure 63 on page 84) shows all of the stations associated to
Arrays that have been discovered by XMS. Only Arrays that belong to the
Current Array Scope are displayed.
This list shows information about each station associated to the wireless network.
You may use the Show Stations option to select whether to show the stations that
are Online now (i.e., currently connected to Arrays), or to show historical
information as well by including all stations that are currently connected or have
been connected Within 24 hours, Within the last week, or Within the last month.
There are two actions offered for stations:
Click the Deauthenticate button to send a deauth signal to the selected
Arrays. This will terminate the current connections between each selected
station and the Array to which it is associated.
Select one station and click the Locate button to have XMS find the
stations physical location and display it on a map. In order for this
command to work, the selected station must be detected by Arrays that
have been placed accurately on maps. See Adding Arrays to Maps on
page 261.
For each station, the following information is shown by default:
The Station MAC address.
Click on this link for the Station DetailsGeneral page that shows
information about the type of connection and performance information
including graphs for session throughput and error percentage. (Figure 64
on page 87)
Click the Station DetailsPast Associations tab to show Association and
Disassociation timestamps for this station, along with the SSID for the
connection. If the station is having difficulty staying connected to the
Array or SSID, this provides valuable details.
Click the Station DetailsAssurance History tab to show connection
problems (if any) experienced by this station. The information shown is
the same as described in Station Assurance on page 95.
Management System
86 TheXMSWebClient
Click the Station DetailsApplication Control tab to show application
usage by this station. The information shown is the same as described in
Application ControlOverview on page 104.
The Station MAC Address of the station.
The Station Hostname.
The Station IP Address of the station.
The wireless Capability of the station: n for 802.11n, a for 802.11a, b for
802.11b, and g for 802.11g.
The Operating Mode of the connection: 802.11n (5 GHz or 2.4 GHz),
802.11a, 802.11b, or 802.11g.
The Array Hostname and Array Location of the Array to which the
station is associated. Click the hostname to go to Array Details.
The Last Seen Date The last time the station was associated to the
Array.
The User Name under which the station was authenticated.
The Device Type (for example, iPad, Android, Windows)
The Device Class (Notebook, phone, tablet, etc.)
The Assoc Time How long (in days:hours:minutes) the station has been
associated to the Array.
The current RSSI (signal strength) of the connection as measured by the
IAP.

Application Control data is only available from XR Series Array models, and
only if the Array license includes Application Control. See About
Licensing and Upgrades on page 194. In order for an Array to produce
Application Control data, you must have enabled the Application Control
option in the Configure menu on the Arrays Toolbar. See The Arrays
Toolbar on page 66.
Management System
TheXMSWebClient 87
Figure 64. Station DetailsGeneral
Management System
88 TheXMSWebClient
Legacy APs
The Legacy APs page lists the non-Xirrus access points known to XMS as part of
your Wi-Fi network, and shows whether the devices are up or down. To discover
these devices, make sure to add their SNMP community strings to XMS. See
Discovery on page 162 for more information. (Note that XMS discovers legacy
APs that use the standard MIB: IEEE802dot11-MIB. It will not discover other
manufacturers controller-based APs.)
This is a display-only page, but values may be exported.
Figure 65. Legacy APs Page
You may customize the columns shown in this list see Select Columns on
page 61.

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 89
Rogues
The web client Rogues page lists the potential rogue access points detected by
Arrays in the network, and types of encryption in use. When you configure an
IAP on the Xirrus wireless Array to be in monitor mode, it can detect APs in its
vicinity.
If you set blocking on for one of these rogue APs, the Arrays monitor radio sends
out signals that will make it difficult for stations to associate to the rogue. Devices
start out as Unclassified when first detected, and you may then classify them as
Blocked, Unknown, Known, or Approved.
We suggest that you use the following classifications:
Use Approved for devices in the operational network.
Use Known for other devices not in the operational network but whose
operation is known about, e.g., a neighbor or adjunct network.
Use Blocked to counter rogues that you believe may be malicious.
Use Unknown for other rogue or unapproved devices.
When you classify a device as known, blocked, etc., that information is sent to
every Array managed by XMS as soon as possible. Also, XMS sends its latest
device classifications to all managed Arrays daily at 3 AM.
The rogues list identifies the Arrays that detected the intruding APs. Values may
be exported.

In order for Arrays to detect rogue APs, the Arrays must have an IAP set to
monitor as described in IAP Settings on page 504. Intrusion Detection
Mode must be set to Standard, as described in Intrusion Detection on
page 537.

Arrays have an Auto Block feature, described in About Blocking Rogue
APs on page 540. You may use the Auto Block Unknown Rogue AP
parameters so that when unknown APs are discovered, they will get the same
treatment as explicitly blocked rogues.
Management System
90 TheXMSWebClient
XMS adds rogues to this list as described in Populating the XMS Rogues and
Rogue Rules Windows on page 183.
The following sections describe the Rogues page:
About Using the Rogues Page
The Rogues List
Figure 66. Rogues Page
About Using the Rogues Page
A number of basic operations are available on the Rogues page to allow you to
customize it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Export on page 62
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
Searching on page 64
The Rogues List
The Rogues List (Figure 66 on page 90) shows all of the rogues that have been
detected by XMS. You may Classify entries by selecting them and using the
provided button. To search for a particular rogue, see Searching on page 64.
You may use the Classification drop-down list to select only rogues of one class
Management System
TheXMSWebClient 91
to display. You may use the Type drop-down list to display only Ad Hoc rogues,
or only those that are part of network Infrastructure. An ad hoc wireless network
is typically a network formed between two stations that are communicating with
each other directly without going through a normal AP.
You may use the Locate button to display the location of one selected rogue on a
map. There are some prerequisites for this feature to operate properlythe rogue
must be detected by more than one Array, and a number of detecting Arrays must
be members of the same map. See Locating Devices on page 267 for details.
This list shows information about each rogue and the Array that detected it. For
each rogue, the following information is shown by default:
The rogues Classification (Unclassified, Approved, Known, Blocked,
or Unknown).
Approved: These are rogues that you have designated as
Approved.
Known: These are rogues that you have designated as Known.
Unclassified: When a device is initially detected, it is unclassified,
which simply means that no one has classified it yet.
Unknown/Rogue: These are rogues that you have designated as
Unknown.
Blocked: These are rogues that you have designated as Blocked. If
you classify a rogue AP as blocked, then the Array will take
measures to prevent stations from staying associated to the rogue.
When the monitor radio is scanning, any time it hears a beacon
from a blocked rogue the monitor sends out a broadcast deauth
signal using the rogue's BSSID and source address. This has the
effect of disconnecting all of a rogue APs clients approximately
every 5 to 10 seconds, which is enough to make the rogue
frustratingly unusable.
To set or modify the classification of rogues, select the desired entries
using the checkbox to the left of the entries and click the Classify button.
In the dialog box, select the desired Classification value from the drop-
down list and click OK. This value will be set for all selected rogues.
Management System
92 TheXMSWebClient
Figure 67. Classifying Rogues
To set up rules to automatically classify groups of rogues (for example, by
SSID, MAC address, or manufacturer), see SecurityRogue Rules on
page 180.
The rogues SSID. Click the SSID to display the Rogue DetailsGeneral
tab, showing additional details about this device. Click the Detecting
Arrays tab for a list of Arrays that have detected this device. Click the
Channel/SSID History tab for a list of the channels and SSIDs that have
been used by this device.
The rogues BSSID (MAC address).
The Channel being used for the connection.
The Band (5 GHz or 2.4 GHz) being used for the connection.
The Manufacturer of the rogue device.
The current RSSI (signal strength) of the rogues signal as measured by
the Array that detected it.
The MAC Address of the Array that detected the rogue.
The host name of the Array that detected the rogue. If the same rogue
device is detected by a number of Arrays, it will only be listed once in this
table.
The Type of the rogue's wireless networkAd Hoc or Infrastructure.
Management System
TheXMSWebClient 93
IDS Events
This page displays the Intrusion Detection System (IDS) Event log, listing any
attacks detected on your network for your Current Array Scope. For descriptions
of the types of attacks detected, as well as the settings to fine-tune IDS on the
Array, please see the Array User's Guide.
Note that IDS Event polling is not enabled by default. If you wish to use the IDS
Event log, you must enable the optional polling for IDS Events as described in
Polling Settings on page 601.
Figure 68. IDS Events
The IDS Events page has a number of search fields that allow you to filter the log
messages to be displayed. This is a very useful feature, since the list may contain a
large number of messages. To search for the desired messages, use any or all of
the following fields, then click Search:
Specify a time period (optional) enter the Date from/Time from and/or
Date to/Time to fields. The Dates are entered by clicking in the field and
selecting the desired date from the popup calendar, or by typing the date
in mm/dd/yyyy format. Times are specified by clicking in the field and
using the drag bars to select the Hour and Minute.

This page is not available for XMS Cloud.
Management System
94 TheXMSWebClient
Enter Event Type (optional) XMS will search for entries of this type.
If you wish to see information for a particular Array, click its Hostname and select
the tab for the Array DetailsIDS page.
The following fields are displayed on the IDS Events page by default:
Array Hostname of the Array on which the event occurred.
Event Type the type of attack, as described in Intrusion Detection on
page 537.
Time the time that the event occurred.
IAP the affected radio.
Channel the affected channel.
Period the length of the window used to determine whether the count
of this type of event exceeded the threshold.
MAC Address the MAC address of the attacker.
SSID the SSID that was attacked.
Management System
TheXMSWebClient 95
Station Assurance
Station assurance monitors the connection quality that users are experiencing on
the wireless network. This window shows client stations for your Current Array
Scope that have had connectivity issues, such as excessive packet retry or packet
error rates, or stations that are unable to stay associated to the Array. When the
Array detects that a station has reached the threshold value for one or more of the
problems that it checks, it adds the station to this page. In addition, an event is
triggered and a Syslog message is logged. If you wish to see information for a
particular Array, click its Hostname and select the tab for the Array Details
Station Assurance page. Similarly, if you wish to see information for a particular
station, click its Station MAC Address and select the tab for Station Assurance
History.
Note that Station Assurance event polling is not enabled by default. If you wish to
use the Station Assurance event log, you must enable the optional polling for it as
described in Polling Settings on page 601.
Figure 69. Station Assurance History
For each station, the following information is shown by default:
The Array Hostname of the Array to which the station is associated.
The Array IP Address.
The Station Hostname.

This page is not available for XMS Cloud.
Management System
96 TheXMSWebClient
The Station MAC address.
The IP Address of the station.
The Device Type (for example, iPad, Android, Windows)
The Device Class (Notebook, phone, tablet, etc.)
The Alarm Typethe connection criterion that was not within acceptable
thresholds.
The Start Time of the session (i.e., when the client associated to the
Array).
The End Time of the session. This will be blank if the session is still active.
Management System
TheXMSWebClient 97
Alarms
The web client Alarms page lists the alarms received by XMS for your Current
Array Scope. All alarm levels are displayed Critical, Major, Minor, Warning,
and Clear. Values may be exported.
XMS allows you to define your own custom alarms. See Alarm Definitions on
page 157. You may also send email notifications when alarms of a particular
severity occur, as described in Notification Settings on page 160.
Figure 70. Alarms Page
The following sections describe the Alarms page:
About Using the Alarms Page
The Alarms List
Management System
98 TheXMSWebClient
About Using the Alarms Page
A number of basic operations are available on the Alarms page to allow you to
customize it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Export on page 62
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
The Alarms page has a number of tailored search fields that allow you to filter the
items to be displayed. This is a very useful feature, since the list may contain a
large number of alarms. To search for the desired messages, use any or all of the
following fields, then click Search:
Specify a time period (optional) enter the Date from/Time from and/or
Date to/Time to fields. The Dates are entered by clicking in the field and
selecting the desired date from the popup calendar, or by typing the date
in mm/dd/yyyy format. Times are specified by clicking in the field and
using the drag bars to select the Hour and Minute.
Enter Search Text (optional) XMS will search for entries that contain
this text in any position in any field.
Select the desired Severity. If you select a particular severity level, only
messages at that level will be displayed (rather than displaying messages
at that level and above). The default value is Any, which shows all
alarms.
The Alarms List
The Alarms List (Figure 70) shows the alarms that have been received by XMS.
Only alarms on Arrays that belong to the Current Array Scope are displayed.
Only the current (most recent) alarm with a given description for each device will
be shown in this list.
You may Clear or Delete alarms by selecting the check boxes to the left of the
desired entries and clicking the appropriate button on the upper left.
Management System
TheXMSWebClient 99
This list shows information about each alarm and the Array that generated it. For
each alarm, the following information is shown by default:
The alarms Severity (Critical, Major, Minor, Warning, or Clear),
preceded by a color indicator of the severity.
Red Critical: A critical failure has occurred within the network
and the problem must be resolved immediately.
Orange Major: A major problem exists. If this problem is ignored
there is a likelihood that the problem will escalate to a critical
condition.
Gold Minor: A minor problem exists and should be investigated.
Yellow Warning: This informs you that some action needs to be
taken to avoid an alarm (an alarm has not yet been invoked, but
probably will be if the warning is ignored).
Green Clear: This state is reported when any problem that
previously caused a critical (red) alarm has been resolved.
The Time and date of the alarm.
The IP Address of the Array that generated the alarm.
The Hostname of the Array that generated the alarm.
The Source MAC address of the Array that generated the alarm.
A text Description of the alarm.
Management System
100 TheXMSWebClient
Events
The web client Events page lists the log and syslog messages received by XMS for
your Current Array Scope. Syslog is a protocol that allows a machine to send
event notification messages across IP networks to event message collectors,
known as syslog servers. Syslog messages are based on the User Datagram
Protocol (UDP). They are received on UDP port 514 and cannot exceed 1,024 bytes
in length (they have no minimum length). For more information about
configuring Arrays to send syslog messages to XMS, refer to System Log on
page 419.
XMS reconciles syslog activity on all wireless Arrays in the network. Syslog
reporting is time-stamped, and to ensure that all syslog time-stamping is
maintained by a universal clock for all Arrays, an NTP (Network Time Protocol)
server should be used for the XMS server and for all managed Arrays. Without an
NTP server assigned (no universal clock), each Array will use its own internal
clock and stamp syslog event times accordingly, which may result in
discrepancies. For more information about using an NTP server, refer to Time
Settings (NTP) on page 414.
Figure 71. Events Page
Only events on Arrays that belong to the Current Array Scope are displayed. All
severity levels at or above the informational level are shown by default. Values
Management System
TheXMSWebClient 101
may be exported. A set of search fields above the list allow you to select the
messages to be displayed. If you wish to see information for a particular Array,
click its Hostname and select the tab for the Array DetailsEvents page.
The Events page has a special search feature for finding particular log messages.
This is described in About Using the Events Page on page 101.
The following sections describe the Events page:
About Using the Events Page
The Events List
About Using the Events Page
A number of basic operations are available on the Events page to allow you to
customize it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Export on page 62
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
The Events page has a number of tailored search fields that allow you to filter the
log messages to be displayed. This is a very useful feature, since the list may
contain a large number of messages. To search for the desired messages, use any
or all of the following fields, then click Search:
Specify a time period (optional) enter the Date from/Time from and/or
Date to/Time to fields. The Dates are entered by clicking in the field and
selecting the desired date from the popup calendar, or by typing the date
in mm/dd/yyyy format. Times are specified by clicking in the field and
using the drag bars to select the Hour and Minute.
Enter Search Text (optional) XMS will search for entries that contain
this text in any position in any field.
Select the desired Severity. If you select a particular severity level, only
messages at that level will be displayed (rather than displaying messages
Management System
102 TheXMSWebClient
at that level and above). The default value is All Severities, which shows
all messages at the informational level and above.
Select the Log Type. The default is All Logs, which displays all XMS log
files including syslog messages.
The Events List
The Events List (Figure 70) shows the events that have been received by XMS.
Only events on Arrays that belong to the Current Array Scope are displayed.
Events that trigger alarms are also shown in the Alarms window. This list shows
information about each event and the Array that generated it. For each event, the
following information is shown by default:
The Time and date of the event.
The events Severity. All syslog messages are categorized by their levels
of severity, which include:
Emergency
Alerts
Critical
Error
Warning
Notice
Information (default)
Debug (not to be used for routine syslog monitoring)
The Array IP Address of the Array that generated the event.
The MAC Address of the Array that generated the event.
The Array Hostname of the Array that generated the event.
The Message a text description of the event.
Management System
TheXMSWebClient 103
PoGE
This page lists the Power over Gigabit Ethernet (PoGE) injectors in your Xirrus
network. Only the PoGE models that have remote management capability are
listed. Address and firmware information is shown. If you wish to view or
manage associations between injector ports and Arrays, please see Discovery
on page 162.
Figure 72. Power over Gigabit Ethernet Page
For each injector, the following information is shown by default:
A green or red dot showing the current status of the injector.
The Injector Hostname.
The IP Address of the injector.
The MAC Address of the injector.
The Firmware version that is running on the injector.

This page is not available for XMS Cloud.

Discovery on page 162 is used to associate Array ports with injector
ports so that the XMS database reflects the physical connections powering
Arrays in your network. You must specify these connections explicitly in
XMS they are not discovered automatically.
Management System
104 TheXMSWebClient
Application ControlOverview
This page analyzes application usage over your entire Xirrus wireless network, or
for your Current Array Scope. If you wish to see information for just one
particular Array, please see Array DetailsApplication Control on page 73.
About Application Control
Arrays use Deep Packet Inspection (DPI) to determine what applications are
being used and by whom, and how much bandwidth they are consuming. These
applications are rated by their degree of risk and productivity. Filters may then be
put in place to implement per-application policies that keep network usage
focused on productive uses.
Application Control can track application usage over time to monitor trends.
Many hundreds of applications are recognized and grouped into a number of
categories. The distributed architecture of Xirrus Arrays allows Application
Control to scale naturally as you grow the network.
For more information about Application Control and using Filters to prioritize
mission-critical application and reduce/eliminate traffic from undesirable
applications, see the Wireless Array Users Guide.
About Risk and Productivity
Application Control ranks applications in terms of their levels of risk and
productivity. Productivity indicates how appropriate an application is for
business purposes. The higher the rating number, the more business-oriented an
application is. Risk indicates how likely an application is to pose a threat to the
security of your network. The higher the rating number, the more risky an
application is.

This feature is only available on Arrays whose licenses include Application

Control. See About Licensing and Upgrades on page 194.
Application Control data is available from XR Series Array models, but not
on XN Arrays. In order for an Array to produce Application Control data,
you must enable the Application Control option in the Configure menu
on the Arrays Toolbar. See The Arrays Toolbar on page 66.
Management System
TheXMSWebClient 105
The Application ControlOverview Page
Figure 73. Application ControlOverview
This table provides detailed information about how your wireless bandwidth is
being used on the selected Array Group, by application. The category of each
application is also shown. You may select which Time Span to show, and which
VLAN Name or Number to show (or All VLANs).
In addition to showing traffic statistics, there are two unique and highly useful
columns. Risk estimates the likelihood of an application causing problems for
your business, rated from 1 (low risk, e.g., Google) to 5 (high risk, e.g., BitTorrent).
Risky applications (rated at 4 or 5) are flagged for your attention by highlighting
the entry in red. Productivity estimates the value of an activity to your business,
from 1 (unproductive, e.g., Y8 gaming site) to 5 (productive, e.g., WebEx).
Management System
106 TheXMSWebClient
You may click the heading of any column to sort based on that column. Click
again to sort in the reverse order.
Each Application Name in the list is a link. You may hover over it to display a
tool tip with more information about the application, including a description of
what it does. You may click the link to display a table listing the Arrays on which
this application has been used, and the amount of traffic that it has generated. You
may specify the desired Time Span and/or VLANs to show. If you wish to drill
sown further, you may show the Stations on which this application has been used
instead. This information is available on the Station DetailsApplication Control
page. See The Stations List on page 85.
When you find risky or unproductive applications taking up bandwidth on the
network, you can create filters to control them. See Filter Lists on page 550.
Management System
TheXMSWebClient 107
Arrays (Configure)
This page lists the Arrays in the XMS database and offers a number of operations
on the selected Arrays. To display this page, click the Arrays link in the Array
Configuration section under Configure at the top of the page. This page is
identical to the Monitor Arrays page (see Arrays on page 60).
The Arrays List shows Arrays that have been discovered by XMS. When you click
on an Arrays Hostname, you can access a variety of Array Details pages. These
pages offer some very powerful features, including the Configuration page,
which allows you configure most settings on that Array. See Array Details on
page 67 and Configuring a Wireless Array on page 393 for more information.
The Configure Arrays Toolbar
The Configure Arrays toolbar offers several functions for Array management,
including gathering diagnostic information, rebooting selected Arrays, and
capturing packets. The diagnostic logs and packet capture functions are also
available on the The Arrays Toolbar on the MonitorArrays page.
Figure 74. The Configure Arrays Toolbar
Select one or more Arrays in the list by clicking their checkboxes in the first
column. You may click the checkbox in the header row to select all Arrays, or click
again to deselect all. The following operations are available:
Refresh this option refreshes discovery on the selected Arrays.
Reboot this option reboots the selected Arrays. You will be asked to
confirm the operation.
Assign to Profilethis option assigns the selected Arrays to the profile
that you specify. Since an Array may not be a member of more than one
Management System
108 TheXMSWebClient
profile, the selected Arrays will be removed from any other profiles to
which they belong. Arrays may also be assigned to profiles using the Add
button on The Profiles Toolbar.
Pull Diagnostic Logs this option initiates a task that instructs the
selected Arrays to create a diagnostic log file. When the diagnostic log is
complete, a link will appear. Click it to download the requested
diagnostic results as a zip file. (Figure 75)
Figure 75. Pull Diagnostic Logs
Pull Config this option pulls configuration files from the selected
Arrays, containing each Arrays current configuration. When the files are
available, a link will appear. Click it to download the requested files as a
zip file.
Packet Capture this option initiates packet capture on one or more
selected Arrays. See About Packet Capture on page 110.
Configureselect an option from this drop-down list to perform
configuration on the selected Arrays. The following options are available:
Network Settings on the selected Arrays. See Configure Network
Settings on page 145.
IAP Settings on the selected Arrays. See Configure Wireless
Settings on page 141.
Auto Configure Channels this option computes the best channel
assignments for the selected Arrays in the local RF environment. You
will be asked to confirm the operation. Note that the best way to run
auto channel is from a map. See the Auto Configure Channels option
(in the Configure drop-down menu) in Managing Arrays Within
Maps on page 272. See also, RF Spectrum Management (Auto
Channel Configuration) on page 534.
Auto Band Automatic band configuration is the recommended
method for assigning bands to the abgn IAPs. It runs only on
Management System
TheXMSWebClient 109
command, assigning IAPs to the 2.4GHz or 5GHz band. The Array
uses its radios to listen for other APs on the same channel, and it
assigns bands based on where it finds the least interference.
Enable Application Control this option enables deep packet
inspection for traffic on the selected Arrays. See Application
ControlOverview on page 104.
Disable Application Control this option disables deep packet
inspection for traffic on the selected Arrays. No data is collected, and
you will not be able to display Application Control analysis for those
Arrays.
Quick Configselect an option from this drop-down list to apply a
predefined configuration that uses best practices on the selected Arrays.
The following options are available: Classroom or High Density.
Power (not available for XMS Cloud users) select an option from this
drop-down list to control power on the selected Arrays. Actually, these
commands are implemented by controlling the Power over Gigabit
Ethernet (PoGE) injector that powers each target Array. These functions
may only be applied to Arrays that are powered by managed PoGE
injectors, and that already have mappings configured as described in
Port Mappings by Injectors on page 127. You may choose to Power
On or Power Off the selected Arrays. The Power Cycle option will turn
power off and back on again, thus rebooting the Array.
Figure 76. Adding Arrays to a Group
More
Choose the Add to Array Group option to add the selected Arrays to
a group. (Figure 76) A dialog box allows you to select an existing
Management System
110 TheXMSWebClient
group or Create a new group. For XMS Cloud users, this is the only
option offered under More.
Choose the Create Profile option from the More drop-down list to
create a new profile network containing the selected Arrays. See
Managing by Profiles on page 205.
Array WMI (not available for XMS Cloud users) connects to the Web
Management Interface for the selected Array (only one Array may be
selected when using this command). After logging in to the Array, if
you make any configuration changes, they apply only to that Array.
They will not be propagated to other Arrays being managed by XMS.
For detailed information about configuring an Array, refer to the
Wireless Array Users Guide. Note that you may also use XMS to
configure an individual Array. See Configuring a Wireless Array
on page 393.
Choose the Delete option from the More drop-down list to delete the
selected Arrays from the XMS database (not available for XMS Cloud
users).
Custom If you have created any Custom Actions, the Custom button
will be displayed. Your Custom Actions will appear in this drop-down
list. Click on the desired action to apply it to the selected Arrays. See
Create Custom Actions on page 588 for more information.
About Packet Capture
Capture is performed on the selected Arrays according to your specified filter
settings. (Figure 77) The capture includes 802.11 header information (for Arrays
running ArrayOS version 5.1 or higher). The capture is performed in promiscuous
mode, which means that it can include all of the packets that are transmitted on
the selected channel regardless of the origin or destination.
When the capture is complete, a download link will appear. Click it to download
the requested capture as a zip file. You can also have the option to download an
individual file for each Array in the list.
In the Packet Capture Parameters dialog, specify the following:
Management System
TheXMSWebClient 111
Capture Sourcethe Ethernet port or Wi-Fi channel (with optional
bonded channel) for the capture.
Stop Capturestop capturing after the specified number of seconds or
packet count.
802.11 Filtercapture a selected combination of types of traffic: control,
management, data, or BSSID (specified by MAC address).
MAC Address Filter(optional) capture only packets with a source or
destination of the specified MAC address (or both).
IP Address Filter(optional) capture only packets with a source or
destination of the specified IP address (or both).
Protocol Filter(optional) capture only packets with the specified
protocol.
Advanced Filter(optional) This uses the same syntax as tcpdump.
Management System
112 TheXMSWebClient
Figure 77. Packet Capture Dialog
Figure 78. Packet Capture in Progress
Management System
TheXMSWebClient 113
Profiles
Please see Managing by Profiles on page 205.
Management System
114 TheXMSWebClient
Array Groups
In XMS, you can create Array groups and assign the desired Arrays to be
members of a group. In the web client, Array groups allow you to filter the data
displayed so that only information for members of the selected Array group is
presented.
The Array Groups page lists all of the Array groups that have been defined in
XMS. It allows you to Add, Edit, or Delete groups. To display this page, click the
Array Groups link in the Array Configuration section under Configure at the top
of the page. Note that you may also create new groups in the web client from the
Arrays (Configure) page, using the More > Add to Group option on the The
Configure Arrays Toolbar. Similarly, you may use the same link on the Arrays
(Configure) to add an Array to a group.
Figure 79. Array Group Page
To modify an existing group, click Edit. The web client displays a list of all
Arrays, with check marks in front of those that belong to the group. (Figure 80)
You may check additional Arrays to add them to the group, or uncheck them to
remove them from the group. Click OK when done.
To add a new group, click Add. Enter the new Group Name. The web client
displays a list of all Arrays. Check the Arrays that you wish to add to the group.
Click OK when done.
Click the Delete button if you wish to remove a group.
Management System
TheXMSWebClient 115
Figure 80. Add or Edit Group
Management System
116 TheXMSWebClient
Config Templates
The Config Template pages allow you to apply a file containing a complete or
partial configuration to an Array. Using config templates is described in the
following topics:
About Config Template Files on page 116
Edit Config Templates on page 117
Load Config Template on page 120
Deploy Config Template on page 123
About Config Template Files
A config template (or config file) is a set of CLI commands to configure an Array.
It may consist of:
a complete set of commands to define every setting on the Array,
an almost complete set that just omits a few items, like leaving out the IP
address commands in order to leave the Array address as is,
or a partial set of commands that just deal with particular aspects of the
Arrays configuration.
The file may be copied from the existing configuration of an Array that you select
as a model, or may be entirely typed in. For example, if Xirrus Customer Support
sends you a config template, you may copy that file and paste it in to the config
template editor to create your file.
If you start with a config template copied from the existing configuration of an
Array, you may edit the file to contain only the settings that you wish to copy to
other Arrays. The file makes incremental changes to the settings on an Array
when it is deployed. Thus, settings not defined in the config template will be left
unchanged.
config templates are useful in a number of situations. In particular, they are the
only way to apply new features to Arrays before those features have been
incorporated in XMS.
Management System
TheXMSWebClient 117
Edit Config Templates
Use this page to type in the entire config template from beginning to end (i.e.,
from scratch), to modify an existing file, and to manage your config templates.
Only expert users should create a config template from scratch. As an alternative,
we strongly recommend that you use the Load Config Template page to
download a config template from an Array. It may then be managed with this
page.
Open this page by clicking the Configure link near the top of the window, then
select Edit Config Template from the Array Configuration section.
Figure 81. Edit Config Template Page
To create a config template from beginning to end (from scratch)
This procedure opens the config template editor so that you can type in the CLI
command lines of the config template, or cut and paste commands from an
existing config template into the editor.
Click the Add button on the upper left of the Edit Config Template page. The
config template editor appears. (Figure 82)
Enter Configuration Name, a name for this config template. Then enter an
optional Description. You may type, paste text, or edit your commands in the
large gray box at the bottom of the page. It is especially useful to copy large

This feature is intended for advanced users who are familiar with use of
the Xirrus Wireless Array CLI and configuration files. Only expert users
should use the option to create the entire configuration file.
Management System
118 TheXMSWebClient
sections of text from a configuration file that has been quality-tested elsewhere,
and paste the text into the editor box.
Editing the Configuration Template
You may type text to enter it in the box, and use the Backspace and Delete keys.
You may use common selection and cut and paste keys:
Ctrl+a: select all
Ctrl+c: copy selected text
Ctrl+x: cut selected text
Ctrl+v: paste text (may be from an application other than XMS)
Shift+Click: select contiguous text up to clicked location
Shift+Arrow: select contiguous text in direction of arrow
Use your browsers search functions if you want to search for text
Figure 82. Config Template Editor
Management System
TheXMSWebClient 119
Click Save when done. The editor closes, and your new file appears in the list of
config templates. (Figure 81) Each Configuration Name in this list is a link. To
edit a file, simply click the link. If you wish to remove a config template, select the
checkbox to the left of it and click the Delete button.
Management System
120 TheXMSWebClient
Load Config Template
Use this page to create a config template by downloading the configuration of an
Array that you wish to use as a model. This method of creating a config template
is highly recommended for most users. Only expert users should type in the entire
file as described in Edit Config Templates on page 117!
Open this page by clicking the Configure link near the top of the window, then
select Load Config Template from the Array Configuration section.
Figure 83. Load from Array
1. Step 1 - Select Arrays: The web client displays a list of the Arrays in the
XMS database (for your Current Array Scope). Select the checkbox to the
left of the model Array in the list, then click Next. The web client
displays a Loading message while the download proceeds.
2. Step 2 - Config File Options: (Figure 84) Set Config Type according to
the type of usage for this file.
factory.conf: The factory default settings.
lastboot.conf: The setting values from just before the last reboot.
saved.conf: The last settings that were explicitly saved using the Save
changes to flash button at the top of each window.
Management System
TheXMSWebClient 121
Click the Include Defaults checkbox if you wish settings that are at their
default value to be explicitly included in the file as well.
Select All Sections if you wish to keep the entire config file. Select
Specific Sections to choose only specific settings for inclusion in the file.
Click Next when done.
Figure 84. Load from Array - Config File Options
3. Step 3 - Review: When the download is complete, you are returned to the
Edit Config Template Page and may review the file and make any
desired changes as described in Edit Config Templates on page 117.
The new template will appear on the Edit Config Template Page. The
new files name is the same as the host name of the Array from which it
was downloaded.
Management System
122 TheXMSWebClient
When you download a config template from an Array, the file represents the
entire configuration of the Array, except that XMS makes certain modifications to
the file for your convenience:
CLI commands are added to reset all the IAPs and then bring them back
up. Similarly, other settings such as SSID, User Group, DHCP Server, and
VLAN will be reset and brought back up. This guarantees that when the
config template is deployed to another Array, all of these settings will be
applied to an Array starting from a known baseline, due to the resets.
All other radio (IAP) settings are commented out, so that no radio
settings will change. Certain other settings, such as Host Name, Location,
and ArrayOS primary and backup software images will be commented
out as well in order to prevent these device-specific settings from being
applied to multiple Arrays.
The entire VLAN section, VTUN section, and the IP address are
commented out. Since these settings can vary from one Array to another,
it would be easy to create problems if they were copied to other Arrays.
Management System
TheXMSWebClient 123
Deploy Config Template
Use this page to apply one of the config template files that you have already
created to one or more Arrays.
Figure 85. Select Config Template File to Deploy
Open this page by clicking the Configure link near the top of the window, then
select Deploy Config Template from the Array Configuration section. The web
client displays a list of the available config templates. (Figure 85)
Select the checkbox to the left of the desired config template, then click Next. The
web client displays a list of the Arrays in the XMS database (for your Current
Array Scope). (Figure 86)
Figure 86. Select Arrays for Deployment
Management System
124 TheXMSWebClient
Select the checkbox of one or more Arrays in the list to which the config template
is to be deployed, then click Next. The web client displays deployment options.
(Figure 87)
Figure 87. Select Deployment Options
Select the checkbox to Permanently save this configuration on the Array. If you
do not check this box, the commands in the config template will be deployed on
the selected Arrays, but they will not be saved. Thus, they will not be reapplied if
you reboot the Array. Click Deploy to apply the config template to the selected
Arrays. The web client displays deployment results. (Figure 88)
Figure 88. Deployment Results
The Message list indicates when the deployment is in progress for each of the
selected Arrays, and then shows whether the deployment has been completed.
Management System
TheXMSWebClient 125
Custom Field Values
This page populates a new column (created with Create Custom Fields on
page 587) with data values. There is also a Bulk Edit option that allows you to
enter identical data for multiple Arrays in one step, in the same way that you can
use Bulk Edit for the Configure Network Settings and Configure Wireless
Settings pages.
Open this page by clicking the Configure link near the top of the window, then
select Custom Field Values from the Array Configuration section. You may filter
the Arrays displayed using Current Array Scope.
Figure 89. Custom Field Values Adding a single value
Before you add values, you must make sure that the desired custom column is
displayed. If you have scrolled all the way to the right of the Arrays list and the
new column is not visible, the use the Select Columns link to add it to your
display. You may also wish to change the custom columns position to be further
to the left. See Select Columns on page 61 if you need more details. Note that
you can also change the new columns position by simply dragging its column
header in the Array list (see Rearranging and Resizing Columns in a Table on
page 63).
To enter a value for an individual Array, simply click a cell in the custom column.
(Figure 89) You may need to click at the beginning of the cell (i.e., towards the
left-hand side of the cell). A dialog box is displayed where you can type the
desired string, up to 255 characters long. Click OK when done to save the value,
or click Cancel to abort.
Management System
126 TheXMSWebClient
Use Bulk Edit to quickly configure multiple Arrays to have the same value. Select
the checkbox at the beginning of each row that is to contain this value. To select all
rows, click the checkbox in the header row. Click again to deselect all rows.
Click Bulk Edit when the desired rows are selected. The Bulk Edit Custom Field
Values dialog box appears. Enter the desired string, up to 255 characters, and click
OK. (Figure 90)
Figure 90. Bulk Configuration (Custom Field Values)
The value that you entered will be displayed in the Arrays list for the selected
Arrays.
Management System
TheXMSWebClient 127
Port Mappings by Injectors
This page shows the Power over Gigabit Ethernet (PoGE) injectors in your Xirrus
network. (Only the PoGE models that have remote management capability are
listed.) Tools are provided for associating each PoGE injector port with the Array
port to which it is physically connected. You may then use XMS to monitor the
status of injectors and to power down or power-cycle Arrays by controlling the
injector ports that drive them. (See SNMPv2 Settings on page 172.)
This page shows all injector ports and indicates if ports are free or shows the
Array ports to which they are connected.
Figure 91. PoGE Port Mappings by Injector
Managing PoGE injectors with XMS
The following steps are required.
1. You must set up each injector that will be managed by XMS. The injector
must meet these criteria:

This page is not available for XMS Cloud.

The PoE page is used to associate Array ports with injector ports so that the
XMS database reflects the physical connections powering Arrays in your
network. You must specify these connections explicitly in XMS they are
not discovered automatically.
Management System
128 TheXMSWebClient
Must be manageable must be one of the Xirrus managed PoGE
injector models. The injectors use SNMPv2.
Must have a static IP address may be assigned a static address via
DHCP or manually.
Must be powered on to allow XMS to discover it.
All injector configuration may be performed using the injectors Web
Management Interface (WMI), as described in the Power over Gigabit
Ethernet Installation and User Guide (PN 812-0057-001, Rev J or higher).
SNMP Community Names must match those expected by XMS for
discovery (see SNMPv2 Settings on page 172). Change these
strings from their factory default values to enhance security.
(Recommended) The injectors user name and password should be
changed from their factory default values to enhance security.
Now you may perform the following steps to start managing the injector
with XMS. Each step is described in its own section below.
2. Add the Injector to XMS the XMS Discovery process adds the injector
to XMSs managed devices database.
3. Associate the Injector with an Array tell XMS which Array port is
connected to each injector output port.
4. Manage the Injector with XMS turn the injector on or off to save
power at night or reboot the Array. See the Power menu options of The
Configure Arrays Toolbar on page 107.
Add the Injector to XMS
XMS Discovery can find powered-up Xirrus injectors that are SNMP-capable and
are reachable from the networks specified for discovery. The SNMP Community
Name of an injector must match one of those listed for SNMPv2. See SNMPv2
Settings on page 172.
When the injector has been discovered, it will appear in the list of PoGE devices
on the Port Mappings by Injector page (Figure 91), and you may proceed to the
next section. If the injector has not yet been discovered, you may enter it manually
as described in Add Devices on page 167.
Management System
TheXMSWebClient 129
Associate the Injector with an Array
Once XMS has discovered the injector, you must tell XMS which Array(s) are
connected to it. Both the injector and the Array(s) must already be discovered
before you may proceed.
1. From the web client click Configure, then click Port Mappings by
Injectors. The Port Mappings by Injector page appears.
Figure 92. Injector and Array Associations
2. Find the row for the desired injector. The row shows the number of ports
on the injector. Note that the icons indicate ports that are available for
connection injector ports that are not yet associated with an Array port.
If a port already has an association, then the connected Array port is
displayed. You may hover the mouse over the port to display the IP and
MAC address of the Array being powered by the injector.
Click the port to be associated with an Array. The mapping dialog
appears, showing Array ports that are not mapped to an injector port.
Figure 93. Associating Injector and Array Ports
Management System
130 TheXMSWebClient
The mapping dialog lists Arrays, and shows an icon for ports that
have not yet been associated with an injector port. Some older Array
models are not directly compatible with Xirrus managed PoGE injector
models. Since power for these Arrays cannot be managed with XMS, no
port icons are shown for them.
3. Find the row for the desired Array. Click the unused port icon for
the Array port that is physically powered by the selected injector port.
The PoGE Injector and Array Port Mapping window (Figure 92) shows
the new connection.
4. To delete a connection from XMS, click the Delete Mapping link for that
port. To view the associations by Array in the web client, click the
Configure > Port Mappings by Arrays link.
Manage the Injector with XMS
Once a Xirrus PoGE injector output port has been mapped to an Array port, you
may turn the PoGE port on and off, and view its status. This is done via the Power
menu options of The Configure Arrays Toolbar on page 107.
Management System
TheXMSWebClient 131
Port Mappings by Arrays
This page lists Arrays for your Current Array Scope, showing the power-capable
Gigabit ports for each. Each port shows the injector port to which it is mapped, if
any. (Only the PoGE models that have remote management capability are listed
on this page.) Tools are provided for associating each Array port with the injector
port which powers it. You may then use XMS to monitor the status of injectors
and to power down or power-cycle Arrays by controlling the injector ports that
drive them. (See The Arrays Toolbar on page 66.)
Figure 94. PoGE Port Mappings by Array
The procedure for mapping the connection between an Array port and a PoGE
injector port using this page is almost identical to the procedure described in
Managing PoGE injectors with XMS on page 127. In the section titled,

This page is not available for XMS Cloud.

The PoE page is used to associate Array ports with injector ports so that the
XMS database reflects the physical connections powering Arrays in your
network. You must specify these connections explicitly in XMS they are
not discovered automatically.
Management System
132 TheXMSWebClient
Associate the Injector with an Array on page 129, simply use the Port
Mappings by Array page instead. (Figure 94)
Select the desired Array port on this page, and click on the port icon. A list of
PoGE injectors is displayed. Select the injector port that is physically connected to
this Array port.
Port Mappings by Switches
This read-only page lists all of the switch ports that are powering Xirrus Arrays/
APs, for all of the switches being managed by XMS. Each switch port that has a
Xirrus device drawing power from it is listed, and shows the Array port to which
it is connected. XMS gathers this information automaticallyyou do not need to
(and cannot) manually map switch ports to Array ports. When a switch port
begins supplying power to the PoE port of a Xirrus Array or AP, the switch
determines the MAC address and IP address of the connected device.
You may use other XMS pages to configure/monitor switches (see Managing
Switches on page 223), and to view power consumption and to power-cycle
ports in order to reboot Arrays (see SwitchPoE Status on page 240).
Figure 95. PoGE Port Mappings by Array

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 133
For each connected switch port, the following information is shown by default:
The Switch Name
The Switch IP Address
The Switch MAC Address
The Switch Portthe number of a port on the switch
The Array Host Name
The Array IP Address
The Array MAC Address
The Array Portthe name of the Array port that is connected to this
switch port

To change settings on switches, please see Managing Switches on
page 223.

If a Xirrus wireless device is unplugged from a switch port, its entry in this
table is not removed. The entry will persist until that same Array port is
connected to another switch port that is managed by XMS. In this case the table
is properly updated, and will reflect only the new connection.
Management System
134 TheXMSWebClient
Array Upgrade
The Array Upgrade pages allow you to specify a software upgrade to apply to
selected Arrays immediately or at a scheduled time, and then view pending and
in-progress upgrades, and the results of finished operations.
This is described on the following pages:
Perform or Schedule Upgrade on page 134
Scheduled Upgrades on page 140
Perform or Schedule Upgrade
This page allows you to upgrade one or more Arrays to a new software release. To
display this page, click the Perform or Schedule Upgrade link in the Array
Upgrade section under Configure at the top of the page. You may perform the
upgrades immediately, or schedule them for a later time.
If you are upgrading an Array to add new features that are not supported by your
existing license, the Array must have the new license key that includes the
upgrades features before upgrading. Similarly, if you are upgrading an Array for
a new software release, the Array must have the new license key that enables the
operation of that release before upgrading.
Arrays have a license Auto-provisioning and activation capability. An Array can
contact the Mobilize server at Xirrus with its serial number and MAC address to
obtain and install its latest license. If you are managing your network with XMS
Cloud, license updates and software upgrades are performed for you by Xirrus.
Otherwise, license updates are performed automatically as part of the XMS
upgrade process. For each selected Array, XMS will check if the requested
upgrade requires a new license. If so, it will send a command to the Array to
activate the license update process, and then wait to allow the license update to
proceed. Note that this license activation process is supported on Arrays running
ArrayOS version 6.4 and above, and XMS will not attempt to activate a license

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 135
auto-update for Arrays running earlier software. For Arrays running older
software and needing a license update (or if the Arrays do not have access to the
Xirrus Mobilize server), you will need to explicitly update their licenses with XMS
as described in About Licensing and Upgrades on page 194. If an Array is not
able to contact the Xirrus Mobilize server, note that the upgrade will proceed
anyway.
Major and minor releases will need a new license key, but patch releases will not.
For example, to upgrade from ArrayOS Release 6.4.5 to Release 6.5 requires a new
license. To upgrade from ArrayOS Release 6.4.1 to Release 6.4.2, use the existing
license.
Figure 96. Array Upgrade
1. Step 1 - Select Arrays: Select all of the Arrays that are to be updated with
the new software image. (Figure 96) Check that they all have licenses
installed that will support the new release (see Deployed Licenses on
page 196). Note that only Arrays in the selected Current Array Scope are
listed. Click Next.
2. Step 2 - Select Upgrade Source: (Figure 97)
a. XMS SCP Server: By default, the upload uses Secure Channel
Protocol (SCP) to upload files (specified in the next step) to each
Array.
Management System
136 TheXMSWebClient
b. External FTP Server: If you select FTP instead, fields will appear
where you must specify Server Name or IP Address, Remote
Directory, and login details. When using an external FTP server, any
System Software, SCD Firmware and Boot Loader images selected in
the next step must be present on the FTP server specified.
Figure 97. Select Upgrade Source
c. External HTTP(S) Server: If you select HTTP, you will specify the
URL of the new software and other details in the next step. Arrays
must be running ArrayOS version 6.4 or higher to support upgrade
via HTTP.
Click Next> when done to proceed to the next step.
3. Step 3 - Select Software Versions: (Figure 98)
a. System Software / URL:
If the Upgrade Source is HTTPEnter the URL of the new System
Software file.
If the Upgrade Source is SCP or FTPIf you have already uploaded
this software image to XMS, then select it from the drop-down list in

XS and XN Series Arrays do not support ArrayOS Release 6.5 or above. If you
attempt to upgrade XN or XS Arrays to Release 6.5 or above, the upgrades will
still be scheduled. These upgrades will fail and display the following error:
AOS version is not supported by this Array model.
Management System
TheXMSWebClient 137
this field. Otherwise, make sure that you have the software image file
in a location that you can access from your file system. Click
and then click Choose File, and browse to the software image file.
Next, click the Upload button, then click Close when the upload is
complete. Make sure that the desired file is selected in the System
Software field.
Figure 98. Select Software Versions
b. Reboot: Check this if you want the Arrays to be rebooted when the
upgrade is complete. This will cause the selected Arrays to run the
new image. If this is left unchecked, then the new images will be
uploaded to the selected Arrays but they will not be run until the
Arrays are rebooted at a later time.
c. Use Custom Login: Use these fields to specify an administrator login
for the upgrade. Custom Login is optional if SNMP is enabled on the
Array and it is running an ArrayOS release greater than 3.5.
Management System
138 TheXMSWebClient
Check this box and set up the login parameters required for
uploading the image to Arrays. These values must match an admin
account that is configured on the Array, else the upload to the Array
will fail. By default, the upload uses Secure Channel Protocol (SCP) to
authenticate access to each Array. The Array will accept logins that
match any of its Admin accounts with write privileges. These
accounts may be entered either directly on the Array or using XMS.
Also, this process will use any Array Shell Authentication
information defined in the discovery dialog (see SSH Users on
page 176). Note that Arrays are shipped with the factory default login
admin/admin.
d. Enable Schedule: If you want to perform this upgrade at a later time,
rather than immediately, check this box and set the time for the
upgrade. Click in the Date Scheduled field, and select the date. Click
in the Time Scheduled field, and use the Hour and Minute sliders to
select the time (on a 24 hour clock).
e. Show Advanced: Click this link for certain advanced features on the
advice of Xirrus Customer Support personnel, and enter the
following fields as needed.
Allow non-standard ArrayOS file names: If Xirrus advises you
that your files will have non-standard names, check this box.
Remove all unused images from Array: If you wish to clean up old
images from the Array, check this box. Only the active and backup
images are keptall others are removed.
Ignore certificate warnings (for HTTP upgrade only): If you wish
to ignore any SSL certificate warnings on the URL that you entered
as the Upgrade Source, check this box.
SCD Firmware (for SCP and FTP upgrade only): This is the
software on the Array that controls low-level hardware functions
such as the fan, the environment controller, and the watchdog
timer. If you have been advised to upgrade your SCD Firmware,
then upload it and select it here, as described in Step 3. For
Management System
TheXMSWebClient 139
ArrayOS Release 6.4 and above, this file is part of the system
software and is automatically updated along with it.
Boot Loader (for SCP and FTP upgrade only): If you have been
advised to upgrade your Boot Loader, then upload it and select it
here, as described in Step 3. For ArrayOS Release 6.4 and above,
this file is part of the system software and is automatically updated
along with it.
4. Step 4 - Upgrade Summary: This page shows the details that you
specified for the upgrade. (Figure 99) Review these values carefully. Click
the Previous button if you need to change anything.
Click the Upgrade button when you are done making changes.
Figure 99. Upgrade Summary
The web client will apply the upgrades you entered, and display the
success or failure of the operation on the selected Arrays.
Management System
140 TheXMSWebClient
Scheduled Upgrades
Use this page to view or cancel pending upgrades that you have scheduled, as
well as checking the results of upgrades that are in progress or have already
completed. Both upgrades that were scheduled for a specific time and those that
were performed immediately without a schedule are shown. To display this page,
click the Scheduled Upgrades link in the Array Upgrade section under
Configure at the top of the page.
Only Arrays in the selected Current Array Scope are listed. If you wish to see all
of the scheduled/performed operations, set Current Array Scope to All Arrays.
To delete scheduled upgrades, select the desired Arrays and click the Cancel
Upgrades button. You may only cancel upgrades that have not yet begun.
Figure 100. Scheduled Upgrades
The following information is show for each Array, by default:
Hostname, MAC Address, IP Addressthese identify the Array to
upgrade.
AOS Versionthe software version that was running on the Array
before the upgrade.
Target AOSthe new software version to which the Array is to be
upgraded.
Schedulethe date and time for which the upgrade is scheduled.
Messagethe status of the pending, in-progress, or scheduled upgrade.

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 141
Configure Wireless Settings
The Configure Wireless Settings page provides very convenient options for
configuring settings on a per-radio (IAP) basis. Bulk IAP configuration and the
ability to set different values on multiple IAPs easily at one time are available only
from this web client window. Bulk configuration is a particularly valuable feature,
allowing you to apply the same settings to multiple IAPs in one step. Individual
and bulk editing are used in the same way as on the Configure Network Settings
page. See Individual vs. Bulk Edits on page 146 for usage instructions.
Open the Configure Wireless Settings page by clicking the Configure link near
the top of the window. In the Wireless Configuration section, select Configure
Wireless Settings.
Figure 101. Configure Wireless Settings Page
Pages that Export Wireless Settings and Import Wireless Settings are also
available.
To Modify Wireless Settings
1. Select Arrays: For each IAP that you wish to modify, select the checkbox
at the beginning of the row. You may click the checkbox in the header row
to select or deselect all rows. Note that only Arrays in the selected
Current Array Scope are listed. Click Next> when the desired rows are
selected.
Management System
142 TheXMSWebClient
2. Edit IAP Settings: You may edit the values in the following columns:
Enable, Band, Channel, Bond Mode, Locked, Cell Size, Tx dBm, Rx
dBm, Antenna, and Wi-Fi Mode. Simply click a table cell that you wish
to modify. A text box will be displayed where you may type the desired
value, then click OK. (Figure 102) You may change as many cells in as
many rows as you wish. There is no need to click the check boxes on
modified rows. Modifications will be highlighted on the page. To set a
field to the same value in multiple Arrays, use the Bulk Edit button. See
To modify multiple rows at once with Bulk Edit on page 146.
Click Finish when done. XMS applies the changes to the selected Arrays.
Figure 102. Editing the IAP Settings Page
3. Apply Settings: The web client will display the success or failure of the
configuration operation on the selected Arrays.
Management System
TheXMSWebClient 143
Export Wireless Settings
This option exports channel and other IAP settings on selected Arrays to an Excel
file or to a CSV file a set of comma-separated values that are compatible with
Microsoft Excel. This file is useful in a number of ways:
As a backup of the current configuration, especially since the settings in
the file may be imported to restore this configuration.
To provide Xirrus Customer Support with a snapshot of the configuration
of your network, at their request.
You may edit the settings in this file and then import the changed values.
Take care only to modify the fields that are editable on the Bulk
Configuration page.
This feature is used in exactly the same way as the export feature for network
settings. Please see Export Network Settings on page 153 for instructions. To
import a file that was exported from the Wireless Settings page, see Import
Wireless Settings on page 144.
Management System
144 TheXMSWebClient
Import Wireless Settings
This option allows you to change settings on IAPs by importing a file that was
exported from the Wireless Settings page. (See Export Wireless Settings on
page 143 for details). This feature is used in exactly the same way as the import
feature for network settings. Please see Import Network Settings on page 155
for instructions.
Management System
TheXMSWebClient 145
Configure Network Settings
The Configure Network Settings page provides very convenient options for
configuring Array network settings for the Ethernet ports. Some of these
functions are also available from the Configure menu on The Arrays Toolbar.
Bulk configuration is a particularly valuable feature, allowing you to change
network settings on a number of Arrays in one step. Individual vs. Bulk Edits
on page 146 describes usage of the two methods for changing settings on this
page.
Open the Network Settings page by clicking the Configure link near the top of the
page. In the Network Configuration section, select Configure Network Settings.
Note that only Arrays in the selected Current Array Scope are listed.
You have two major options for network settingsModify Network Settings
(Basic) or Modify Network Settings (Advanced). The Basic option mainly
changes IP settings. The Advanced option adds management of settings for DNS,
Ethernet, and Gigabit port bonding.
Pages that Export Network Settings, and Import Network Settings are also
available.
The following topics describe configuring network settings:
About Using the Network Settings Page on page 145
Individual vs. Bulk Edits on page 146
Modify Network Settings (Basic) on page 148
Modify Network Settings (Advanced) on page 149
About Using the Network Settings Page
A number of basic operations are available on this page to allow you to customize
it for your own use:
Current Array Scope on page 61
Select Columns on page 61
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
Management System
146 TheXMSWebClient
Individual vs. Bulk Edits
Network settings pages offer the option of modifying rows individually, or
modifying multiple rows with bulk configuration. The bulk option is a very
useful shortcut that applies identical settings to the selected Arrays. In some
cases, bulk configuration has an additional intelligent capabilityfor example,
when setting the IP Address, the value you enter is used as a starting point for a
range of addresses, since you cannot assign the same IP address to multiple
Arrays. (Figure 105)
To modify rows individually
Simply click a table cell that you wish to modify. A text box will be displayed
where you may type the desired value. (Figure 103) Click OK when done. You
may change as many cells in as many rows as you wish. There is no need to click
the check boxes on modified rows. Modifications will be highlighted on the page.
All changes will be accumulated, but will not be applied until you complete the
Apply Settings step.
Figure 103. Editing Individual Rows
To modify multiple rows at once with Bulk Edit
Select the Arrays that you wish to edit by clicking their check boxes. Then click
the Bulk Edit button. This displays blank fields for all of the settings that are
modifiable in bulk on this page. For example, Figure 104 shows the Bulk Edit
dialog for the Edit Network Settings step in Basic mode. Enter the values that
you want applied to all of the Arrays that you selected.
Management System
TheXMSWebClient 147
For the IP Address field, enter the starting value for a range of addresses. Then
select an Increment by value for the range. Note that Array Host Names cannot
be bulk configured. Bulk edit fields that are left blank will be unchanged on
Arrays.
Figure 104. Bulk Configuration (Network Settings)
Click OK when done. The Bulk Edit dialog closes, and your desired changes will
be displayed in the network settings table. Note that the new values have not yet
been sent to the Arrays. Take a moment to review your changes. In particular,
make sure that the IP addresses that were assigned are correct. You may
individually edit any incorrect settings.
Click Finish when satisfied with the changes.
Management System
148 TheXMSWebClient
Modify Network Settings (Basic)
1. Select Arrays: Ensure that the Basic option is selected (to the right of the
Next> button).
For each row that you wish to modify, select the checkbox at the
beginning of the row. Click the checkbox in the header row to select all
rows. Click again to deselect all rows.
Click Next> when the desired rows are selected.
Figure 105. Configure Network Settings Page (Basic)
2. Edit Network Settings: You may edit the values in the following columns
individually: Hostname, Gig1 DHCP, Gig1 IP Address, Gig1 Mask,
Gig1 Gateway, Location. Simply click a table cell that you wish to
modify. A text box will be displayed where you may type the desired
value. (Figure 106) You may change as many cells in as many rows as you
wish. There is no need to click the check boxes on modified rows.
Modifications will be highlighted on the page. To set a field to the same
value in multiple Arrays, use the Bulk Edit button. See To modify
multiple rows at once with Bulk Edit on page 146.
Click Finish when done. XMS applies the changes to the selected Arrays.
Management System
TheXMSWebClient 149
Figure 106. Editing the Network Settings Page (Basic)
3. Apply Settings: The web client will display the success or failure of the
configuration operation on the selected Arrays.
Modify Network Settings (Advanced)
1. Select Arrays: Select the Advanced option (to the right of the Next>
button). Select the checkbox to the left of each Array row that you wish to
modify. You may click the checkbox in the header row to select or deselect
all rows. Click Next> when the desired rows are selected.
Figure 107. Configure Network Settings Page (Advanced)
Management System
150 TheXMSWebClient
2. Array Network Settings: You may edit the values in the following
columns individually: Hostname, Location, Domain, DNS Server 1,
DNS Server 2, DNS Server 3. Simply click a table cell that you wish to
modify. (Figure 108) A text box will be displayed where you may type the
desired value. You may change as many cells in as many rows as you
wish. There is no need to click the check boxes on modified rows.
Modifications will be highlighted on the page. To set a field to the same
value in multiple Arrays, use the Bulk Edit button. See To modify
multiple rows at once with Bulk Edit on page 146.
Figure 108. Editing the Array Network Settings Page (Advanced)
Click Next> when done.
3. Ethernet Settings: You may edit the values in the following columns
(individually or using the Bulk Edit button, as described above): Enabled,
Auto Negotiate, and MTU. If Auto Negotiate is disabled, then you may
also modify Duplex and Speed.
Management System
TheXMSWebClient 151
Figure 109. Editing the Array Network Settings Page (Ethernet)
Click Next> when done.
4. IP Settings: You may edit the values in the following columns
(individually or using the Bulk Edit button, as described above): DHCP
Enabled, IP Address, Subnet Mask, Default Gateway. Note that DHCP
Enabled must be false in order to edit any of the other three columns.
Figure 110. Editing the Array Network Settings Page (IP)
Click Next> when done.
Management System
152 TheXMSWebClient
5. Bond Settings: You may edit the values in the following columns
(individually or using the Bulk Edit button, as described above): Mode.
See Bonds on page 399 for an explanation of the Port Mode options.
Figure 111. Editing the Array Network Settings Page (Bond)
Click Finish when done. XMS applies the changes to the selected Arrays.
6. Apply Settings: The web client will display the success or failure of the
configuration operation on the selected Arrays.
Management System
TheXMSWebClient 153
Export Network Settings
This option exports IP and other network settings on selected Arrays to an Excel
file or to a CSV file a set of comma-separated values that are compatible with
Microsoft Excel. This file is useful in a number of ways:
As a backup of the current configuration, especially since the settings in
the file may be imported to restore this configuration.
To provide Xirrus Customer Support with a snapshot of the configuration
of your network, at their request.
You may edit the settings in this file and then import the changed values.
Take care only to modify the fields that are editable on the Bulk
Configuration page.
To import a file that was exported from the Export Network Settings page, see
Import Network Settings on page 155.
1. Step 1 - Select Arrays: Open the Export Network Settings page by
clicking the Configure link near the top of the window, then click the
Export Network Settings link that appears under Network
Configuration. Note that only Arrays in the selected Current Array
Scope are listed.
Figure 112. Export Network Settings
Management System
154 TheXMSWebClient
For each row that you wish to export, select the checkbox at the beginning
of the row. To select all rows, click the checkbox in the header row. Click
again to deselect all rows. (Figure 112) Click Next> when the desired
rows are selected. Only the Basic Network Settings columns are
exported.
2. Step 2 - Download Settings File: Select the desired output file format:
Excel or CSV, and change the File name for the download as desired.
Click the Export button again to browse to the destination folder and
filename.
Figure 113. Exported Network Settings File
3. You may choose to save the results in a file or open them in Excel. Click
Cancel when done to close the Export dialog.
Management System
TheXMSWebClient 155
Import Network Settings
This option allows you to change IP and other network settings on Arrays by
importing a file that was exported from the Export Network Settings page. See
Export Network Settings on page 153 for instructions on exporting settings to
a file.
1. Step 1 - Upload Settings File: Open the Import Network Settings page by
clicking the Configure link near the top of the window, then click the
Import Network Settings link that appears under Network
Configuration.
Click Choose File, and browse to the desired .xls or .csv file. (Figure 114)
Next, click the Upload button.
Click Next> when the Upload Complete message appears.
Figure 114. Import Network Settings
2. Step 2 - Verify Settings: This page lists network settings for all of the
Arrays that were included in the imported file. (Figure 115) Review these
values carefully. Click a setting to change it. An edit field will appear if
the setting is modifiable. There is also a Bulk Edit option which may be
used as described in To modify multiple rows at once with Bulk Edit
on page 146. Note that you dont need to click the checkboxes at the front
of the rows to be changed unless you are using the Bulk Edit option.
Click the Finish button when you are done making changes.
Management System
156 TheXMSWebClient
Figure 115. Verify Imported Network Setting Values
3. Step 3 - Apply Settings: The web client will apply the changes you
entered, and display the success or failure of the configuration operation
on the selected Arrays.
Management System
TheXMSWebClient 157
Alarm Definitions
The Custom Alarms page allows you to define your own alarms. You can instruct
XMS to monitor a specified operating condition on all Arrays and issue an alarm
if your stated criteria are met on any Array. For example, you may set application
traffic alarms to send a notification when usage of an application or application
category exceeds the defined threshold, either system-wide or per-Array.
Open this configuration page by clicking the Configure link near the top of the
window, then select Alarm Definitions from the Alarms section. (Figure 116)
This page lists all of the alarms that you have created.
Figure 116. Custom Alarms Page
Click the Add button to display the Add Alarm dialog and create a new custom
alarm. Select an Alarm Category from the list, and one or more Alarm Types will
be shown based on your selection. (Figure 117)
Figure 117. Add a Discrete Alarm
Management System
158 TheXMSWebClient
Choose an Alarm Type, and additional fields will be displayed based on your
choice. There are two kinds of alarms:
Discrete Alarma discrete alarm is issued if the condition described in
Alarm Type becomes true. For example, in Figure 117, the selected Alarm
Category is IAP Status. If you select IAP Disabled as the alarm type,
fields will be displayed allowing you to select a specific IAP Name to
monitor and specify the Severity of the resulting alarm. In this example,
an alarm will be issued if the specified IAP on any managed Array goes
down. Note that the IAP must transition from enabled to disabled to
trigger the alarm, and another alarm will not be triggered for that IAP
until the IAP cycles through the enabled state first. Click the Enabled
check box to activate your new alarm. Note that you may enter additional
custom alarms of the same type to monitor additional named IAPs.
Analog Alarman analog alarm is triggered any time its value is not
within the specified range (subject to the deadband restrictions described
below). You must specify additional parameters to define a Low Alarm
Threshold and/or a High Alarm Threshold.
The alarm is triggered when the value is greater than or equal to the
upper threshold, or less than or equal to the lower threshold. To clear the
alarm, the value must be less than the upper limit minus the deadband, or
greater than the lower limit plus the deadband.
For an analog alarm, you may also set a Deadband value. This value
keeps the alarm from being reissued multiple times by the same event.
The default value is 0. The alarm will not be cleared until the value from
the Array recovers into the non-alarm range by the amount set in
deadband.
For example, in Figure 118, the selected Alarm Category is Ethernet
Errors. If you select Ethernet Interface retry percentage as the Alarm
Type, fields will be displayed allowing you to select a specific Ethernet
Interface Name to monitor, and specify the Severity of the resulting
alarm. In this example, an alarm will be issued if retry percentage on the
specified interface on any managed Array equals or exceeds the High
Alarm Threshold. If you had also specified a Low Alarm Threshold,
Management System
TheXMSWebClient 159
then reaching or going below that value would also trigger the alarm. The
Deadband value of 10 ensures that the alarm will not be cleared until the
retry percentage recovers an additional 10% back into the non-alarm
value range.
Figure 118. Add an Analog Alarm
Click the Enabled check box to activate your new alarm, and click OK
when done to save it. Alarm conditions are checked every time the
corresponding data is polled. (See Polling Settings on page 601.)
Looking for Something?
One interesting alarm type may be used to help find iPads and other devices that
have gone missing. Under Alarm Category select Station Status. Then set Alarm
Type to Alarm when a particular station is associated to an Array. Enter the
MAC address of the missing device. XMS will issue an alarm of the specified
Severity if the device associates to an Array in the managed network.
Management System
160 TheXMSWebClient
Notification Settings
You can set up email notifications to be sent when alarms occur. The email will
identify the notifying Array by host name, IP address, and MAC address.
Notifications may be restricted to apply only to a selected Array scopea set of
Arrays belonging to a selected profile or Array group. For example, say XMS is
managing multiple Array networks at sites in different cities, and that you have
defined a profile network for each city. When an alarm occurs for an Array, you
may wish to notify only the IT personnel managing that Arrays site. You may
accomplish this by setting up a separate notification for each profile.
Open this configuration page by clicking the Configure link near the top of the
window, then select Notification Settings from the Alarms section. (Figure 119)
This page lists all of the notifications that you have created.
Figure 119. Alarm Notification Settings
Click the Add button to display the Add Notification dialog and create a new
entry. (Figure 120) Enter a meaningful Notification Name. Select an alarm
Severity from the list. An exact match of this severity level will trigger the sending
of the notification.
Select the Array Scope for this notification. Only alarms on Arrays that are
members of the selected group or profile will trigger this notification. Select ALL
to allow an alarm of the selected severity on any XMS-managed device to send
this notification. If you wish to notify one set of personnel about a critical alarm
on Profile A, and notify a different set of personnel about a critical alarm on
Management System
TheXMSWebClient 161
Profile B, then you may simply create a separate notification for each profile by
setting the Array Scope field appropriately.
Check the Enabled checkbox to enable this email notification to be sent when the
selected condition occurs. You can use the Edit button later to disable and re-
enable this notification if desired, without having to delete and re-enter it.
In the Email Notification To field, enter a recipients email address, then click
Add. You may repeat this step to add additional recipient email addresses. The
email addresses will be listed as you add them. To remove an address, click the X
in front of it. Click OK when you are done, and the new notification is complete.
You must specify the SMTP server for XMS to use for sending email notifications,
along with the email account to use and the name of the sender. See Email
Settings on page 600.
Figure 120. Add a Notification
You may select an existing entry and modify or delete it using the Edit or Delete
buttons.
Management System
162 TheXMSWebClient
Discovery
Use the Discovery configuration pages to enter all the settings necessary to have
XMS find the Xirrus Arrays/APs, wired switches, and managed Power over
Gigabit Ethernet (PoGE) injectors on your wireless network and add them to its
database of managed devices. When a device has been discovered, ti will appear
on the on the Arrays list, the Switches list, or the Port Mappings by Injectors list.
You can enter SNMP settings, add devices and networks, and enter Array SSH
user information.
For an overview of how discovery adds devices and how SNMP must be
configured on Arrays and on XMS to support it, please see:
How Discovery Works
For a summary of the steps for starting discovery of your network, please see:
How to Perform Discovery
Each of the discovery pages is separately discussed in the following topics:
Add Devices on page 167
Adds a specific device, range of devices, list of devices, or subnetwork to
XMS.
SNMPv2 Settings on page 172
Adds or deletes SNMPv2 community names.
SNMPv3 Users on page 174
Adds or deletes SNMPv3 users.
SSH Users on page 176
Add user accounts that XMS can use when it must log in to Arrays for
some management functions.

These web client pages are not available for XMS Cloud. Arrays/APs are
automatically discovered by XMS Cloud soon after they come online. All other
configuration in this section is automatically performed for you as part of XMS
Cloud service.
Management System
TheXMSWebClient 163
View Networks on page 177
Adds a subnetwork for XMS to scan for Xirrus devices.
What If My Device Is Not Discovered? on page 179
What to do if XMS has not discovered a device that you expected to find
on the Arrays list, the Switches list, or the Port Mappings by Injectors
list.
Note that in this chapter, the term device refers to a Xirrus Array/AP or wired
switch, or a Xirrus-supplied managed PoGE injector.
How Discovery Works

To allow XMS to find a Xirrus device (Array, switch, or PoGE injector), the
device must have SNMP enabled and its community string must match one of
the strings listed in the Discovery window. See SNMPv2 Settings on
page 172. The default SNMPv2 community string in XMS matches the Array
default value.

When an Array boots up, it sends an SNMP trap to the XMS servers default
hostname, xirrus-xms. XMS can then add it to its managed devices list. This
Phone Home feature requires DNS to resolve the hostname xirrus-xms correctly.
Thus, if you change the host name of the XMS server, you must configure DNS
to resolve xirrus-xms to the actual name of the XMS server host.

NOTE: To use SNMPv3 successfully, system time must be set using an NTP
server on both the XMS server host machine and all Arrays using SNMPv3.
This is because SNMPv3 requires synchronization between the XMS server
and the Arrays so that the system time difference between them never exceeds
more than 150 seconds. If the time difference exceeds 150 seconds, SNMPv3
suspects a security breach and removes the SNMPv3 credentials for affected
Arrays from the database. This means that the Array will appear to be down
and statistics will not be polled until the Array is re-discovered. A manual
refresh of the Array should remedy the situation. See Add Devices on
page 167.
Management System
164 TheXMSWebClient
XMS has two main ways of getting devices added to its database: the Phone
Home feature that relies on an Array sending an SNMP trap to the XMS servers
hostname, and the Discovery tool that uses SNMP.
Phone Home
Any time an Array boots up or its IP address changes, it announces its presence
on the network. It does this by sending an SNMP trap to the XMS servers default
hostname, xirrus-xms (this name is not case-sensitive). XMS can then
communicate with the device, and add it to the Arrays window. The Phone Home
feature requires DNS to be properly configured in the network, so that the
hostname xirrus-xms can be resolved to the IP address of the XMS server.
As soon as a new device is plugged in, it adds itself to XMS without waiting for
the next time discovery is run on the network. This reduces network overhead by
greatly reducing the need for discovery and the traffic overhead that accompanies
the process. Any devices that phone home to XMS are added to the Arrays
window or the PoGE injectors list in Port Mappings by Injectors and become
part of the XMS managed network.
Discovery
XMSs discovery feature uses SNMP to find networks and devices that are
reachable from the servers network. Despite the advantages of the Phone Home
feature, discovery is still needed when you first start using XMS, and later for
finding added Xirrus-supplied managed power injectors and wired switches.
Discovery will find your current network of Xirrus devices, without waiting for
them to announce themselves as a result of being booted up. In some networks,
discovery must be used because DNS is not configured to allow devices to resolve
the hostname xirrus-xms.
Devices that do not have SNMP enabled will not be discovered by XMS in this
case, go to Single Device (Figure 122) on page 167.

If you do not have a valid license for the XMS server, you are limited to
managing one Array. Valid XMS licenses are typically for a particular number
of Array IAPs. In either case, when XMS has discovered the maximum
permitted number of IAPs, no additional Arrays will be discovered.
Management System
TheXMSWebClient 165
Once a discovered network or device is included in the list of managed items, you
can then modify (edit) or delete the item, as needed. Only devices that are
included in the list of manageable items on the Arrays list, the Switches list, or
the Port Mappings by Injectors list can be managed by XMS. Only Arrays APs
that are listed can be added to maps that you create.
How to Perform Discovery
This section provides a quick summary of the steps required to start adding
devices to XMS.
Once started, this process uses SNMP to automatically find Xirrus Arrays, wired
switches, and PoGE injectors in the subnets that you specify. (Figure 121) No
networks are discovered by default, so you must add the subnets containing your
Arrays.
1. To add SNMPv2 Community Names or SNMPv3 Users to match the
strings being used by your devices, click SNMPv2 Settings or SNMPv3
Users. For XMS to discover and manage a device, the device must have
SNMP v2 and/or v3 enabled. The devices SNMPv2 community string or
SNMPv3 read-write authentication settings must match one of those
defined here for discovery.
The default SNMPv2 community name (xirrus) allows XMS to discover
new Arrays that still have default SNMP settings (SNMPv2 is enabled by
default with its Read Write Community String set to xirrus).
Enter the appropriate SNMP settings. For more details, see SNMPv2
Settings on page 172.

This section is not applicable to XMS Cloud.
Management System
166 TheXMSWebClient
2. To add networks to be discovered, click the Add Devices link under
Discovery. (Figure 121) When the page appears, click the Networks
button as shown. In the Network Address field, enter the subnets
Network Address and Subnet Mask and click Add. Use the subnet mask
to define the addresses for discovery as narrowly as possible, to avoid
creating excess traffic by discovering a needlessly large network. Add
additional subnets as required. Note that the newly entered networks are
displayed in the list of networks for discovery. Click Discover> so that
the discovery process will be initiated.
Discovery begins soon after adding a network.
To add individual Arrays or power supplies, use the Single Device or
Multiple Devices link instead.
.
Figure 121. Discovering Networks
Management System
TheXMSWebClient 167
Add Devices
This page is used to add subnetworks or devices to XMS. It allows a great deal of
flexibility in adding devices. You may individually add one or more devices to
XMS, rather than specifying a network and having XMS discover them. You may
enter a single device IP address, a range of addresses, or a list of addresses. The
list option is especially useful if you have an Excel spreadsheet with a list of
Arrays and their addresses. Simply copy and paste the single column that has the
device IP addresses. You may also add subnetworks for discovery.
Open this configuration page by clicking the Configure link near the top of the
window, then select Add Devices from the Discovery section.
Select whether to add a Single Device, an IP Range, Multiple Devices, or
Networks by clicking the appropriate tab.
Single Device (Figure 122)
Enter the IP Address of the single device to be added to XMS. Click the
Discover button.
Figure 122. Discover a Single Device
XMS will display the results of discovery for the device. (Figure 123)

This page is not available for XMS Cloud.
Management System
168 TheXMSWebClient
Figure 123. Discovery ResultsSingle Device
IP Range (Figure 124)
Enter the start of the range in the From IP Address field. Enter the end of
the range in the To field. XMS will check every address in the range, up to
and including the To address. Click the Discover button. At each address,
if it finds a Xirrus Array/AP, wired switch, or management-capable PoGE
power supply, XMS will add the device to its list of discovered devices.
Figure 124. Discover a Range of IP Addresses
XMS will display the results of discovery for the IP range. You may click
the Cancel button to stop discovery. (Figure 123) Canceling will not
remove devices that have already been discovered for this range.
Management System
TheXMSWebClient 169
Multiple Devices (Figure 125)
Type or paste a list of as many IP addresses as you like in the box,
separated by commas or carriage returns. You may paste a list of IP
addresses obtained from an Excel .csv (comma-separated values) file.
Click the Discover button. XMS will check every address in the list. At
each address, if it finds a Xirrus Array/AP, wired switch, or
management-capable PoGE power supply, XMS will add the device to its
list of discovered devices.
Figure 125. Discover a List of IP Addresses
XMS displays the results of discovery, listing whether it succeeded or
failed at each address. If discovery fails at an address, XMS will still try all
the rest of the addresses that you entered. Note that if you enter a device
that is already in the XMS database, XMS will attempt to refresh the
device by obtaining up-to-date information about it.
You may use the Cancel button if you wish to abort discovery while still
in progress. This will stop XMS from finding any additional devices, but
will not remove any devices that have just been discovered.
Management System
170 TheXMSWebClient
Networks (Figure 126)
Enter the subnets Network Address and Subnet Mask, then click Add.
Continue adding subnetworks as required. Click Discover to initiate the
discovery process. The newly entered network will be displayed in the
list of networks for discovery.
Be careful to specify the smallest subnet that includes the devices, to
avoid creating excess traffic by discovering a needlessly large network.
Take care not to accidentally specify a Class A network.
Figure 126. Discover Networks
After you click the Discover button, XMS will attempt to discover a
Xirrus Array or managed power supply at all of the IP addresses in the
specified subnetworks. It will display the results for each network, listing
whether discovery is In Progress, Completed, Disabled, or Failed.
(Figure 127)
You may use the Cancel button if you wish to abort discovery while still
in progress. This will stop XMS from finding any additional devices, but
will not remove any devices that have just been discovered.
Management System
TheXMSWebClient 171
If XMS has not discovered a device that you expected to find on the Arrays list,
the Switches list, or the Port Mappings by Injectors page, see What If My
Device Is Not Discovered? on page 179.
Figure 127. Review Results of Adding Devices
From the discovery results window, you may click the Add button to add more
networks. Discover Now will restart discovery on all listed networks. You may
check the checkboxes for the desired rows and then do any of the following:
Click Edit to modify the specification of a subnetwork.
Click Delete to remove a subnetwork from discovery from this point
onwards.
Click On/Off to enable or disable the discovery of a subnetwork, without
deleting the entry. Discovery occurs on a daily basis if the network
discovery is enabled here.
Management System
172 TheXMSWebClient
SNMPv2 Settings
This page is used to add or delete SNMPv2 community names.
The XMS discovery process searches networks using both SNMPv2 and SNMPv3.
Discovery will search for devices using SNMPv3 first. See SNMPv3 Users on
page 174 for more information. When an Array is discovered using SNMPv3, then
XMS uses that version for communication with the Array from then on. When an
Array or PoGE injector is discovered via SNMPv2, then XMS uses SNMPv2 to
communicate with the device. Injectors support SNMPv2 only.
XMS discovery has default SNMPv2 entries which match the factory default
SNMP v2 settings in Arrays and PoGE injectors. However, for proper security on
your Xirrus devices, we recommend that you improve security on Xirrus devices
by entering your own SNMPv2 community strings and/or SNMPv3 user names
and passwords. Thus, you must add those community strings or user names/
passwords to XMS for discovery to find those devices.
To add an SNMPv2 Community Name, click the Configure link near the top of
the window, then click the SNMPv2 Settings link in the Discovery section.
(Figure 128)
Enter the new Community Name and click Add. The new Community Name
will be added to the list, located under the dialog box.

This page is not available for XMS Cloud.

For a device to successfully Phone Home (announce its presence to XMS) or
be discovered, SNMPv2 must be enabled on the device. For SNMPv2, the read-
write community string (i.e., community name) must match one of the strings
listed in the Discovery window.
Management System
TheXMSWebClient 173
Figure 128. SNMPv2 Settings
The next time that the discovery process runs after adding a new SNMP v2 entry,
XMS will use all of the Community Names listed. Adding or deleting a name on a
list will not trigger discovery to run immediately. The new name will be used by
the next discovery process (but will not be used now, if discovery is currently
running). To trigger a discovery process using the new entry, use the Discover
Now button described in View Networks on page 177.
To delete an entry from the list, click the Delete button to its right. You will be
asked to confirm the deletion. The next time that the discovery process runs, it
will use the Community and User Names listed at that time. Note that discovery
will not remove devices from its device list if they have a community name that
was deleted. Once a device is discovered, it stays on the device list even if you
remove the community or user name or disable discovery. The device remains
until you delete it manually. You cannot modify an entry in the Community
Names list, but you may delete it and then add the new value. The next time that
the discovery process runs, it will use the new value. XMS will continue to
manage the device using the original community name as long as the device is
still configured to use it.
Management System
174 TheXMSWebClient
SNMPv3 Users
This page is used to add or delete SNMPv3 users. The XMS discovery process
searches networks using both SNMPv2 and SNMPv3. Since SNMPv3 offers
improved security, this version is recommended if you need an added layer of
security. Note that SNMPv3 has an overhead for encryption, so it will have an
impact on larger systems.
XMS discovery searches for devices using SNMPv3 first. If an Array is discovered
using SNMPv3, then XMS uses that version for communication with the Array
from then on.
XMS discovery has default SNMPv2 entries which match the factory default
SNMPv2 settings in Arrays and PoGE injectors. However, for proper security on
your Xirrus devices, we recommend that you improve security on Xirrus devices
by entering your own SNMPv2 community strings and/or SNMPv3 user names
and passwords. Thus, you must add those community strings or user names/
passwords to XMS for discovery to find those devices.
Figure 129. SNMPv3 Users

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 175
NOTE: Although XMS does not have any SNMPv3 usernames or passwords defined by
default, Xirrus Arrays do have default entries. The Arrays default read-write username
and password are xirrus-rw; the default read-only username and password are xirrus-ro.
To add an SNMPv3 User, open this configuration page by clicking the Configure
link near the top of the window, then select SNMPv3 Users from the Discovery
section. (Figure 129)
Enter the new User Name and Authentication and Privacy Passwords. Set the
Authentication Type to match your Arrays. Select the Privacy Type: DES or AES.
Click Add when done. The new user will be added to the list, located under the
dialog box.
The next time that the discovery process runs after adding a new SNMP v2 or v3
entry, XMS will use all of the Community Names and Users listed. Adding or
deleting a name on a list will not trigger discovery to run immediately. The new
name will be used by the next discovery process (but will not be used now, if
discovery is currently running). To trigger a discovery process using the new
entry, use the Discover Now button described in View Networks on page 177.
To delete an entry from the list, click the Delete button to its right. You will be
asked to confirm the deletion. The next time that the discovery process runs, it
will use the User Names listed at that time. Note that discovery will not remove
devices from its device list if they have a user name that was deleted. Once a
device is discovered, it stays on the device list even if you remove the user name
or disable discovery. The device remains until you delete it manually. You cannot
modify an entry in the User Names list, but you may delete it and then add the
new value. The next time that the discovery process runs, it will use the new
value. XMS will continue to manage the device using the original user name as
long as the device is still configured to use it.
Management System
176 TheXMSWebClient
SSH Users
Some setting changes, such as Perform or Schedule Upgrade, require Arrays to
download files. When it instructs an Array to fetch a file from the server, XMS
must log in to the Array shell. Depending on the configuration of the Array,
authentication may use the Arrays local accounts or may use a RADIUS server. In
either case, the XMS server needs to know a Username and Password to gain
access to the Array shell.
To define this Array login information, use the SSH Users page. Click the
Configure link near the top of the window, then click the SSH Users link under
Discovery. (Figure 130)
Enter an Arrays User Name and Password, and click Add. The new entry will
appear in the Array Shell Authentication list, located under the dialog box. You
may use the Delete button to remove a selected entry, if necessary.
Figure 130. Adding SSH Users
These authentication entries are not used by the discovery process itself, but are
managed on this page for convenience. When XMS needs to log in to an Arrays
shell, it tries entries from the list until it finds one that works. Then it will
remember to use this login for this Array. On future login attempts to the same
Array, it will try the remembered login first.

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 177
View Networks
To view discovered networks, click the Configure link near the top of the
window, then click View Networks from the Discovery section. (Figure 131)
This page is very similar to the page shown in Figure 127 on page 171.
.
Figure 131. View Discovered Networks
The list of networks for discovery shows the following information.
Address the Network Address that you entered. The icon to the left of
the address is green if you enabled Start Discovery, and yellow if you
have disabled discovery for this network. Note that you may use the Edit
button to toggle Start Discovery.
Subnet Mask the mask that you entered.
Status the status of the discovery process. The status may be Finished
(discovery complete), Disabled (Start Discovery not enabled for this
network), or In Progress (discovery is still in progress for this network).
Array Count the number of Arrays discovered on this network so far.

This page is not available for XMS Cloud.
Management System
178 TheXMSWebClient
PoGE Count the number of PoGE power injectors discovered on this
network so far.
Legacy AP Count the number of non-Xirrus APs discovered on this
network so far. (Devices will only be discovered if they use a standard
MIB.)
The toolbar above the list of networks provides a number of functions:
Add Network add a network for discovery (enter Network Address,
Subnet Mask, and whether Start Discovery is enabled).
Discover Now click this button to start discovery immediately. This
will start discovery on the selected networks only. You may use this to
rediscover a network.
Edit to change a network (Network Address, Subnet Mask, and
whether Start Discovery is enabled), select the network and click Edit.
Delete to remove networks, select the desired networks and click
Delete. You will be asked to confirm the deletion.
On/Off this button toggles whether Start Discovery is enabled on the
selected networks. If you use this button to enable Start Discovery, then
the discovery process will be started immediately on the selected
networks.
Note that discovery will not remove devices from the XMS database if you delete
their network, if they are on a network where discovery has been disabled, or if
you have edited the IP address so that their original network is no longer listed
for discovery. Devices remain on the list until you delete them manually.
Management System
TheXMSWebClient 179
What If My Device Is Not Discovered?
XMS Discovery will find devices that are reachable from the XMS servers
network if their SNMP settings match those configured on the XMS server. If your
Array or PoGE injector has not been discovered, check the following.
1. Have you discovered the maximum number of Arrays allowed by your
XMS license?
2. Is the device powered up and fully booted?
3. For an Array /AP/wired switch is SNMP enabled? (SNMPv2 is always
enabled on Xirrus managed PoGE injector models.)
4. Does the XMS server have connectivity to the device (i.e., is the device
connected and can you ping it?).
5. In the SNMPv2 Community Names and SNMPv3 Users sections, verify
that one of the listed entries matches the SNMP values configured on the
device. If not, click Add under the appropriate list if you need to create a
new entry. It is crucial that the values used by the device and by XMS
match.
6. In the Search Networks section, verify that the subnetwork containing the
device is listed, and that it is enabled. If not, click Add to enter it. After a
few seconds the system generates a message informing you that
discovery has started on the newly added network.

This discussion is not applicable for XMS Cloud, which will automatically
discover your Arrays soon after they come online.

If you do not have a valid license for the XMS server, you are limited to
managing one Array. Valid XMS licenses are typically for a particular number
of Array IAPs. In either case, when XMS has discovered the maximum
permitted number of IAPs, no additional Arrays will be discovered. See
Managing the XMS Server License on page 620.
Management System
180 TheXMSWebClient
7. To launch discovery immediately on a network, see Add Devices on
page 167.
8. You may add a device explicitly, using its IP address. See Discover a
Single Device on page 167. If the device is detected by XMS it is added,
otherwise an error message is displayed. In this case, check the IP address
that you entered.
SecurityRogue Rules
This page allows you to set up and manage rules to automatically classify rogue
APs (see Rogues on page 89), based on SSID, BSSID, or manufacturer. You may
classify rogues as Blocked, so that the Array will take steps to prevent stations
from associating with the blocked AP. To open this page, click the Configure link
at the top of the page. Then select Rogue Rules from the Security section.
Figure 132. Rogue Rules
To classify current rogues individually rather than using rules as they are
discovered, please see Rogues on page 89. Note that if a rogue is
classified by a rule, it cannot be individually overridden.
Rogues may be automatically blocked, as described in SSID Spoofing
Auto Block on page 184, and Intrusion Detection on page 537.
Management System
TheXMSWebClient 181
Rogue rules allow you to classify groups of devices, rather than classifying each
selected device individually. Rules may be enforced (pushed out to all Arrays) or
unenforced, as described later in this section. Rules may be created as described
below, or may appear as a result of being read from Arrays (see Populating the
XMS Rogues and Rogue Rules Windows on page 183). You may edit existing
rules, if you wish.
To create a rogue rule, click the Add button on the upper left. (Figure 132) In the
Add Rogue Classification Rule dialog box (Figure 133), enter a unique Rule
Name for your new rule.
Figure 133. Adding a Rogue Rule
The Rule Type field specifies the characteristic of the rogue to be matched, which
determines what to enter in the Data field as described below. The wild card
character (*) may be used in the Data field for any of the types. Rule Type options
are:
BSSID set Data to a MAC address (typically including * for a wild
card) that describes the devices to be matched. When entering a MAC
address, the string often specifies the OUI of a manufacturer the first
three octets of the device MAC address are a unique identifier for the
manufacturer. For example, 00:0f:7d and 50:60:28 are the OUIs of Xirrus,
so the strings 00:0f:7d:* and 50:60:28:* will uniquely match all Xirrus
Arrays.
Management System
182 TheXMSWebClient
To match a device individually (i.e., a specific rogue, rather than a set of
rogues specified with a wild card), enter the BSSID (MAC address) of the
device, and specify its classification.
SSID set Data to any legal SSID name to be matched. For example, to
match the SSIDs named xirrus-student or xirrus-staff, enter the string
xirrus*.
BSSID_OR_SSID set Data to either of the types above. This type is
provided for backwards compatibility with rules that are read from some
older Arrays. Note that rules created on newer Arrays have a Match
Only setting that will specify either a BSSID or an SSID, although these
Arrays will still process the old-style rules. On older Arrays, rules with
type set to SSID, BSSID/SSID, or BSSID will all be processed on the Array
as though they were BSSID/SSID rules. Rules with type set to
Manufacturer will be dropped on older Arrays. (Manufacturer is
supported on ArrayOS 4.0.6 or higher, and on ArrayOS Release 3 builds
of 3.5.1 or higher.)
Manufacturer enter the manufacturer name as an ASCII string.
From the Classification drop-down list, select the classification to be applied to
these devices. For example, you might set all Xirrus Arrays to Known. See The
Rogues List on page 90 for an explanation of rogue classifications.
Leave the Enforced checkbox checked if you wish to have the rule pushed to all
managed Arrays, otherwise clear the checkbox.
Enforced rules are pushed (sent) to all managed Arrays to become part of
the Arrays Rogue Control Lists. If the Array has a conflicting rule (for the
same wildcard pattern, but with a different classification), the XMS rule
will replace the Array rule.
Unenforced rules are not pushed to managed Arrays. This way, if an
Array already has a rule for the same BSSID, SSID, or manufacturer, it
will not be overridden.
Keeping unenforced rules in the database provides a single place where
you can see a global view of all rules in the managed network, without
Management System
TheXMSWebClient 183
necessarily applying all the rules universally. You may change a rule to
Enforced if you wish.
Click OK when done.
To change an existing rule, select it in the list and click Edit, or to delete the rule
click Delete.
Populating the XMS Rogues and Rogue Rules Windows
When the XMS server is first started, the Rogues list is empty (see Rogues on
page 89), and there are only two default rules: all Xirrus Arrays (BSSID 00:0f:7d.*
or 50:60:28:*) are Known. This rule is Enforced it is sent out to all Arrays.
In order to populate the Rogues list, XMS fetches the rogue devices and Rogue
Control List entries from each discovered Array. Thereafter during operation of
XMS, Arrays are polled for new entries. Also during operation, when a new
Array is discovered, XMS fetches its rogue devices and Rogue Control List entries
and adds them to its database.
When a classification of an individual device is read from an Array and added to
the XMS database it is marked as Enforced, and thus it will be pushed to all
managed Arrays. On the other hand, when a rule is read from an Array and added
to the XMS database, it is marked as Unenforced. This prevents the rule from
being sent out to all managed Arrays, possibly overriding existing rules that were
explicitly configured in Arrays. Once a rule has been added to the XMS database,
if additional rules for the same BSSID/SSID are later read from other Arrays, they
are ignored.
If you set a rule to Enforced, it will be sent out to each managed Array and
become part of its Rogue Control List.
Management System
184 TheXMSWebClient
SSID Spoofing Auto Block
XMS can automatically block rogue APs that launch spoofing (evil twin) attacks
on your SSIDsthat is, rogues that impersonate one of your SSIDs. This blocking
is performed on a system-wide basis, for all managed Arrays rather than for a
particular AP or Profile network. To enable auto blocking of rogue APs that spoof
your SSIDs, check the box for Enable Auto Blocking of SSID Spoofing (Evil
Twin) Attack. Clear the checkbox to disable this feature.
Spoofing is detected by Arrays managed by XMS. In order to be able to detect this
type of attack, Arrays must have Intrusion Detection Mode set to Standard, and
have detection of Evil Twin Attacks enabled. These settings may be made by
XMS for individual Arrays or for Profile networks. See Intrusion Detection on
page 537 and Profile DetailsConfiguration on page 216.
Figure 134. Auto Blocking SSID Spoofing Attacks
For more information about Rogue APs and Auto Blocking, you may also wish to
see:
Rogues on page 89
SecurityRogue Rules on page 180
About Blocking Rogue APs on page 540
Suppose you add a new SSID to your Array network and a previously
identified rogue AP already has that SSID. If SSID Spoofing Auto Block is
enabled, then it will block that SSID on the rogue AP.
Management System
TheXMSWebClient 185
Xirrus Access ManagerArray Configuration
This link opens a wizard that configures Array settings required to allow
operation with the Xirrus Access Manager (XAM), in order to provide secure
guest access facilities on your wireless network. To open this page, click the
Configure link at the top of the page. Then select Array Configuration from the
Xirrus Access Manager section. The wizard does not do any configuration of the
XAM server itselfit simply configures the proper settings on the selected profile
networks or Arrays.
About XAM
XAM allows you to offer guest access to the Internet without compromising
the security of your wireless network for users that are part of your organization.
The onboarding option allows known users to register additional devices (such as
tablets and smartphones) for use on the network. When a user completes the
onboarding process for a device, that device is then allowed to connect to the
organizations Secure SSID.
Arrays must be configured in a particular way to support use of XAM, and the
wizard takes care of those details for you on all of the Arrays that you choose. For
example, when stations associate to a guest or onboarding SSID, XAM assigns
them to the appropriate user group after they have authenticated: either an
isolation user group (XAM-isolation) or an access user group (XAM-access). The
wizard takes care of configuring the required user groups on Arrays. Each user
group is enforced with a number of filters on each Array. If you enable
Onboarding, the wizard defines an additional onboarding group (XAM-access-
onbrd), and if you define a separate Onboarding SSID, the wizard defines a
fourth onboarding group (XAM-isolation-onbrd). The filters for these
onboarding groups are the same as for the XAM-access and XAM-isolation
groups, respectively. For step-by-step instructions for setting up XAM for guest
access and for onboarding new devices for known users, please see the Xirrus
The XAM wizard will work with both XR and XN Arrays, but the Arrays
must be running ArrayOS Release 6.4 or higher.
Management System
186 TheXMSWebClient
Access Manager Application Note in the Xirrus Resource Center. Complete
information for XAM is found in the Xirrus Access Manager Users Guide.
The wizard will configure the following Array settings for you:
Select Targetsdesignate the profile networks or individual Arrays
which will offer guest and onboarding access via XAM. The wizard
configures the following settings on these Arrays per your specifications:
guest, onboarding, and secure SSIDs; access, isolation, and onboarding
user groups, access, isolation, and onboarding filter lists and filters, and
associated VLANs and tunnels.
XAM Detailsenter the IP addresses of the XAM server and other
information. The XAM server is used as a RADIUS server for
authentication of guest users and users who belong to your organization.
SSIDenter the SSID name to be used by your guests and/or by
onboarding, and the VLAN(s) on the wired network (if any) on which
that traffic is sent or received.
Tunnelingguest and onboarding traffic may be tunneled directly to the
Internet via GRE tunnels, if you wish. A Xirrus Tunnel Server (XTS) is
used for this purpose. Enter the address of the XTS.
Using the XAM Wizard
1. Select Targets
Set the Choose Targets drop-down to Profiles to specify profile networks
to participate in your guest network, or select Arrays to specify Arrays
individually. Check the box of each desired profile network or Array.
Selected Arrays may be any XR or XN Series Array model, but each must
be running ArrayOS Release 6.4 or higher, and you may not select Arrays
that are members of profiles. Note that only Arrays in the selected
Current Array Scope are listed.
Management System
TheXMSWebClient 187
Figure 135. XAM WizardSelect Targets
If you select profiles, then the XAM wizards final step will perform
synchronization jobs on all member Arrays of the selected profiles.
Click the Next button when done.
2. XAM Details
Figure 136. XAM WizardXAM Details
Management System
188 TheXMSWebClient
XAM Management Address (eth0)the management IP address of
the VM-based XAM server, which must be the address of the virtual
machine's eth0 port. Arrays selected above will use this address as
their RADIUS server.
XAM Isolation Address (eth1)the IP address of the isolation
network.
SSID RADIUS Shared Secret /Confirm Radius SecretThe XAM
wizard ensures that the RADIUS Secret used is exactly the same on
Arrays, on the RADIUS server and in the Xirrus Access Manager
software under RADIUS Settings. The wizard will set this value for
the targets selected in Step 1.
Use Guest Accesscheck this box to configure Arrays for guest
access management via XAM.
Use Onboardingcheck this box to configure Arrays for guest access
management via XAM.
Either or both of the checkboxes above may be enabled. You must select
at least one of these options.
3. SSID
Enter the settings for up to three SSIDs in this step: a guest access SSID, an
onboarding SSID that known users can use to register new devices, and a
secure SSID that known users will use with known devices. (Figure 137)
Guest SSID
This SSID is intended for guest login to obtain access to the Internet. This
is created as an open SSID, i.e., with no encryption. Radius MAC
authentication is configured, pointing to the XAM Isolation Address as
the RADIUS server used. The Guest SSID may also be used for
onboarding if this option is selected under Onboard SSID.
Guest SSID Nameenter a unique name for the guest SSID.
VLANSpecify the VLAN on your wired network that will carry
traffic from the guest SSID when it is passed to Array trunk
(Ethernet) ports.
Management System
TheXMSWebClient 189
Specify None if you are not using a VLAN for this purpose.
Click Create New to create a new VLAN, then enter a VLAN Name
or Number for it. This VLAN will be defined on each target
selected in Step 1.
You may select Use Existing, and enter the VLAN Name or
Number. This VLAN must already be defined on each target
selected in Step 1.
Figure 137. XAM WizardSSID
Onboard SSID
This SSID is provided for known users to obtain access to your network
using new devices, such as smartphones or tablets. You may use the
Guest SSID for this purpose instead if you wish.
Using the same Guest SSID for both guests and onboarding (rather than
setting up the separate onboarding SSID) is typically easier for your
users. It prevents guests from mistakenly connecting to the Onboarding
Management System
190 TheXMSWebClient
SSID and getting stuck there. Both corporate users onboarding a new
device and guests connect to the Guest SSID (open/Radius MAC) and
then open a browser. The page includes a hyperlink for onboardingfor
example, Corporate Users or User with Credentials. Following the
link takes the corporate user through the steps of onboarding.
Use Guest SSIDcheck this box to use the guest SSID for both
guests and onboarding. In this case, there will be no separate
Onboard SSID, and you will not be able to enter any settings for it.
Onboarding SSID Nameenter a unique name for the onboard
SSID.
VLANSpecify the VLAN on your wired network that will carry
traffic from the onboard SSID when it is passed to Array trunk
(Ethernet) ports. The settings are configured in the same way as for
the guest SSID, above.
Secure SSID
Once a known user has successfully onboarded a device, this SSID is used
for network access, thus it is required for onboarding.
Secure SSID Nameenter a unique name for the onboard SSID.
Broadcastcheck this box if you wish the SSID to broadcast its
presence to potential clients. Leave it unchecked if you want the
secure SSID to be hidden. Note that some clients (such as Broadcom)
do not automatically connect to the secure SSID when it is hidden.
EncryptionSpecify the type of WPA encryption for this SSID: WPA,
WPA2, or WPA Both. In all cases, 802.1x is used for authentication.
WPASpecify the encryption protocol usedTKIP or AES. If you
enable both, the station determines which will be used.
VLANSpecify the VLAN on your wired network that will carry
traffic from the secure SSID when it is passed to Array trunk
(Ethernet) ports. The settings are configured in the same way as for
the guest SSID, above.
Management System
TheXMSWebClient 191
4. Tunneling
Figure 138. XAM WizardTunneling
If this option is selected, a GRE tunnel is used from the Array trunk
(wired) port for the specified SSID. Its remote endpoint is the Xirrus
Tunnel Server (XTS) address that you enter. The wizard performs no
configuration on the XTS server itselfyou must configure that server
separately. For details, please see the Xirrus Tunneling Solutions Application
Note in the Xirrus Resource Center and the Xirrus Tunnel Server Users
Guide.
Use Tunnel for Guest SSIDif you will be tunneling all Guest SSID
traffic for additional security, check this box and enter the following
settings.
XTS AddressEnter the tunnel endpoint IP address on a Xirrus
Tunnel Server.
Use Tunnel for Onboarding SSIDif you will be tunneling all
Onboard SSID traffic for additional security, check this box and enter
the following setting.
XTS AddressEnter the tunnel endpoint IP address on a Xirrus
Tunnel Server.
Click Finish when done.
5. Results
Management System
192 TheXMSWebClient
The success or failure of the wizard is displayed. In particular, Arrays that
are not supported because they are running too old a release of ArrayOS
are identified. Arrays must be running at least Release 6.4 in order to be
configured for XAM by the wizard.
Figure 139. XAM WizardResults
More XAM Wizard Results
The XAM wizard takes care of all of the settings that you need for your wireless
network to work with the Xirrus Access Manager. Should you wish to customize
the wireless networks operation with XAM, here is some additional information.
In addition to the settings mentioned previously, the XAM wizard configures the
following settings on the selected Arrays:
A filter list named XAM-isolation is created, with the following filters (in
this order):
Allow XAM Isolation Address
Allow DHCP ports
Allow OCSP traffic (Online Certificate Status Protocol)
Allow all HTTP traffic from any to any
Allow all HTTPS traffic from any to any
Deny All
A filter list for XAM-access is created with just one filter:
Deny XAM Isolation Address
A user group named XAM-isolation is created. It is linked to the XAM-
isolation filter list.
Management System
TheXMSWebClient 193
A user group named XAM-access is created and linked to the XAM-
access filter list.
Onboarding filter lists and user groups are configured, if you are using a
separate onboarding SSID.
Management System
194 TheXMSWebClient
Array Licenses
These pages display and manage the licenses for Arrays in your Xirrus network.
You may view the license of each Array and deploy new or upgraded licenses.
Working with licenses is described in the following topics:
About Licensing and Upgrades
Deployed Licenses
Export Licenses
Import Licenses
Edit Licenses
Pending Licenses
About Licensing and Upgrades
For ArrayOS Release 6.4 and above, when a newly deployed Array boots up, it
automatically contacts Xirrus with its serial number and MAC address and
obtains its license key. Any unlicensed Array will auto-license in this way after it
boots up, if it has Internet connectivity.
XMS manages the licenses for large numbers of Arrays. You can easily view
licensing information for your Arrays and manage individual licenses. The
license utility can apply bulk licenses in one step, by simply reading in the .csv
license file issued by Xirrus. Similarly, when its time to upgrade all of your

These pages are not available for XMS Cloud. ArrayOS maintenance is
included as part of XMS Cloud, so your wireless network is always entitled to
the latest software. XMS Cloud automatically manages license deployment and
the software upgrade process so you dont have to worry about it.

This section describes using XMS to manage Array licenses. If you are
looking for information regarding the XMS servers license, please see
Managing the XMS Server License.

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 195
Arrays with new features or a major software release, the required licenses may
all be installed in one step.
An Arrays license determines many of the features that are available on the
Array. For example, automatic cell sizing and channel allocation require a license
that includes the Xirrus Advanced RF Performance Manager (RPM). Also, IEEE
802.11n operation on Arrays is a licensed feature. To check the features supported
by your license, see the next section Deployed Licenses. For more information
on the features that require a license, please see Advanced Feature Sets in the
Introduction chapter of the Xirrus Wireless Arrays Users Guide.
If you are upgrading an Array to add new features that are not supported by your
existing license, the Array must have the new license key that includes the
upgrades features before upgrading.
Similarly, if you are upgrading an Array for a new software release, the Array
must have the new license key that enables the operation of that release before
upgrading. Major releases will need a new license key, but minor releases will
not. For example, to upgrade from ArrayOS Release 5.0.5 to Release 5.1, you need
a new license. To upgrade from ArrayOS Release 5.0.5 to Release 5.0.8, use the
existing license.
Management System
196 TheXMSWebClient
Deployed Licenses
This window is displayed by your browser when you select Configure on the top
of the window, and then select the Deployed Licenses page from the Licenses
section. Note that only Arrays in the selected Current Array Scope are listed.
Initially, this page displays a list of all deployed Array licenses being managed by
XMS. This is a list of all discovered Arrays and their licenses. By default the
following is shown for each Array: the License Key, the Hostname along with the
Array Serial Number; the License Version, License Features, Product Type, and
Max Radios supported by the license, and the license Expiration date. You may
use the Select Columns option to choose which information you wish to display.
.
Figure 140. Array License Management - Deployed Licenses
The License Features column shows the advanced features that are enabled by
this license, such as the RF Performance Manager (RPM), RF Security Manager
(RSM), RF Analysis Manager (RAM), or IEEE 802.11n operation.

This page is not available for XMS Cloud.
Management System
TheXMSWebClient 197
The following main operations are available for managing licenses:
Viewing deployed licenses on discovered Arrays, described above.
Export Licenses
Import Licenses
Edit Licenses
Pending Licenses
Export Licenses
At times, you may wish to export Array licenses to a file. For example, you may
want a consolidated record of some or all of your licenses, or Xirrus Customer
Service may request this information to resolve a support issue. This feature
exports the selected licenses shown on the Deployed Licenses window into a file
that can be imported by Excel either a .csv file or an .xls file. This file may also
be used to Import Licenses. To export Pending licenses, see Pending Licenses
on page 203.
To export deployed licenses from the web client, select the Export Licenses page
from the Licenses section of the Configure menu. Note that only Arrays in the
selected Current Array Scope are listed.
To proceed, select the desired licenses by checking them off in the first column.
Click the Next > button at the top of the page. (Figure 141)

If you change a license directly using the CLI or WMI on an Array whose
license status is Deployed, XMS will detect the change and display the
changed license in the list of deployed licenses.
However, if XMS has a license pending for that Array, that license will be
deployed as soon as XMS is able to do so, replacing the license in the Array.

This page is not available for XMS Cloud.
Management System
198 TheXMSWebClient
.
Figure 141. Exporting Array Licenses
To export an .xls file, click the Excel radio button. To export a file of comma-
separated values (.csv), click the Csv radio button. Then click Export. The File
Download dialog box will allow you to open the file, or save it to the location you
select.
Figure 142. Sample Export File
This exports the selected deployed licenses into a file of the selected format. A
sample export file is shown in Figure 142.
Management System
TheXMSWebClient 199
Import Licenses
Use this feature to import a .csv or .xls file with licensing information for any
number of Arrays. For example, to upgrade your entire Xirrus wireless network
to a new major software release, you must first deploy licenses for that release.
Xirrus will furnish these licenses to you in the form of an Excel (.csv) file. Simply
click to import the file and click Finish to deploy the licenses to the appropriate
Arrays.
After your license file has been imported, any licenses that are for XMS managed
Arrays (i.e., those that have been discovered) will be deployed to those Arrays.
The Array is not rebooted but the radios will go down and up, so that station
associations will be disrupted briefly. The Array will start using the new license,
and will support the capabilities shown in the Features column.
A license for an Array that is not yet under XMS management will be deployed as
soon as the target Array is discovered. Similarly, a license for a managed Array
that is down will be deployed shortly after it comes back on line.
To import licenses using the web client, select the Import Licenses page from the
Licenses section of the Configure menu. Fields are displayed to allow you to
specify the license file.
.Click the Choose file button to browse to the license file. It must be either an .xls
or a .csv (comma-separated values) file. To see an example of the format, you may
export a sample license file (see Export Licenses on page 197). The File
Download dialog box will allow you to open the file, or save it to the location you
select. Click the Upload button. When the upload is complete, click Next > at the
top of the page.
The imported licenses will be displayed on the Verify Licenses page. (Figure 143)
Check that the licenses imported correctly. If necessary, you may edit any License
Key by clicking on it.

This page is not available for XMS Cloud.
Management System
200 TheXMSWebClient
Figure 143. Importing Array Licenses
Click Finish to complete the import process. Any license that cannot be deployed
now either because the Array has not yet been discovered by XMS or because the
array is off line will be placed in the pending list and will be deployed when the
Array is available. The Status field will show the results for each Array.
Management System
TheXMSWebClient 201
Edit Licenses
To modify deployed licenses from the web client, select the Edit Licenses page
from the Licenses section of the Configure menu to display all deployed licenses.
(Figure 144) Note that only Arrays in the selected Current Array Scope are listed.
.
Figure 144. Select Array Licenses to Edit
Select the licenses to be edited by checking the box to the left of each desired row.
To select all entries at once, click the checkbox in the header row. To deselect all
entries, click the checkbox in the header row again. When the desired entries are
selected, click the Next > button at the top of the page. The Edit Licenses page
appears. (Figure 145)
To modify a license, click the Arrays License Key field and edit it or type the new
license into the field. This is the only field that may be edited. Repeat for as many
entries as you need to change.

This page is not available for XMS Cloud.
Management System
202 TheXMSWebClient
When you are done editing, click the Finish button. The license modifications will
be deployed to the selected Arrays, and the status of the operation will be
displayed for each Array.
.
Figure 145. Editing Array Licenses
You may not delete deployed licenses, but you may delete those that have not yet
been deployed. See Pending Licenses on page 203.
Also note that you may not enter new licenses by hand. To add a new license,
please see Import Licenses on page 199 and Pending Licenses on page 203.
Management System
TheXMSWebClient 203
Pending Licenses
Pending licenses are those that XMS has imported but has not yet been able to
deploy. Select the Pending Licenses page from the Licenses section of the
Configure menu to display all non-deployed licenses that have been imported.
(Figure 146)
Note that if an Array is running with a valid license, but a new license was
imported for it, it will be listed on both the Deployed Licenses page and the
Licenses Pending Deployment page until the new license has been deployed.
.
Figure 146. Array Licenses Pending Deployment
License Status may have the following values:
Array Not Discovered a new license that has not been installed because
the designated Array has not been discovered yet (i.e., the Array is not
listed in the Arrays page). This does not mean that XMS cannot find the
Array in your network, but rather that the discovery process has not yet
added it. To add the Array to XMS using the web client, see Add
Devices on page 167 or View Networks on page 177. When the Array
is discovered, XMS will automatically check whether there is a license
pending for it and if so, will attempt to deploy it.

This page is not available for XMS Cloud.
Management System
204 TheXMSWebClient
Invalid License Key the license is not valid. You may edit the License
Key as described in Edit Licenses on page 201. Use the Deploy Now
button to push the corrected license to the Array.
Pending Deployment a previously discovered Array is currently
unreachable or down, and XMS cannot deploy the license.
You may use the Deploy Now or Delete buttons to manage licenses. Select the
desired licenses by checking the box to the left of each desired row. To select all
entries at once, click the checkbox in the header row. To deselect all entries, click
the checkbox in the header row again.
Click the Deploy Now button at the top of the page to have XMS immediately
attempt to deploy the selected licenses on their target Arrays. You will be
informed of the results of the operation. The License Status field will show the
results quickly, typically well within a few minutes. If successful, the entry will be
moved to the list of deployed licenses. The Array is not rebooted but the radios
will go down and up, so that station associations will be disrupted briefly. The
Array will start using the new license, and will support the capabilities shown in
the Features column.
Click the Delete button to remove the selected pending licenses. (Deployed
licenses may not be deleted.)
You may click the Export link at the top of the page to export all pending licenses.
It is not necessary to select any entries first all pending licenses will be
exported. To export an .xls file, click the Excel radio button. To export a file of
comma-separated values (.csv), click the Csv radio button. Then click Export. The
File Download dialog box will allow you to open the file, or save it to the location
you select.
Management System
ManagingbyProfiles 205
Managing by Profiles
XMS provides profiles for ease of management. A profile allows you to specify a
set of Arrays and manage them as a group. After creating a profile and adding
Arrays to it, you then define a uniform configuration and ArrayOS software
release to be applied to all of the member Arrays. This manage by network
feature eliminates the time-consuming and error-prone task of configuring and
managing Arrays individually, and ensures the deployment of consistent
software and settings across each profile.
To guarantee the uniformity of a profile, member Arrays cannot be configured
individually directly via their CLI or WMI. User interfaces on these Arrays only
allow read access. Note that member Arrays can be configured individually via
XMS, but this is not recommendedwith the exception of changing settings that
cannot be managed as part of the profile network, such as individual IAP
Settings.
Settings that must be unique per Array are automatically excluded from
management by the profile network. For example, the Array IP address and
hostname must be different for each Array, and are thus not changed by updates
to the profile. Individual IAP settings (channel, cell size, etc.) are also not
changed, since these are tailored to the environment of each Array.
Member Arrays need not be running ArrayOS Release 6.5 or above to be
managed as part of a profile.
Management System
206 ManagingbyProfiles
Profiles
The web client Profiles page lists all of the profile networks being managed by
XMS, and allows you define new ones and perform selected functions on them. To
display this page, click the Profiles link in the Array Configuration section under
Configure at the top of the page.
To start using profiles, follow these basic steps:
1. Create a profile network and assign Arrays to it. See Add in the The
Profiles Toolbar on page 208.
2. Specify the software release to be run on the profile network. See Set
AOS Version in the The Profiles Toolbar on page 208.
3. Specify the configuration to be enforced on membersclick the profile
network to go to its detail pages and enter configuration settings. See
Profile DetailsConfiguration on page 216.
The following sections describe the Profiles page:
About Using the Profiles Page
The Profiles List
The Profiles Toolbar
Profile Details
Profile DetailsArrays
Profile DetailsConfiguration
Profile DetailsJob Status
Figure 147. Profiles Page
Management System
ManagingbyProfiles 207
About Using the Profiles Page
A number of basic operations are available on the Arrays page to allow you to
customize it for your own use:
Select Columns on page 61
Export on page 62
Select Rows on page 63
Rearranging and Resizing Columns in a Table on page 63
Sorting on page 63
Searching on page 64
The Profiles List
The Profiles List (Figure 147 on page 206) shows the profile networks that you
have already created. The Profiles Toolbar allows you to add new profiles, define
the software version for member Arrays, and perform a number of other
operations on the profiles that you select.
Click on a profiles Name to access Profile Details pages that manage the
configuration of member Arrays and show the status of the operations performed
on them.
For each profile network, the following information is shown by default:
The Name
The Array Count of member Arrays
Whether or not there is a Configuration Assigned to the profile network
Whether or not there is an AOS Version Assigned to the profile network
Whether this is the Default profile network. When new Arrays are first
discovered, they will be assigned automatically to the default profile
network, if one has been selected.
Management System
208 ManagingbyProfiles
The Profiles Toolbar
This toolbar offers functions for profile network management, including creating
profiles, editing their membership, and specifying their software version.
Figure 148. The MonitorArrays Page Toolbar
Select one or more profiles in the list by clicking their checkboxes in the first
column, and then click one of the toolbar buttons. You may click the checkbox in
the header row to select all profiles, or click again to deselect all. The operations
available are:
Add Create a new profile network using the selected Arrays. Note that
you may also create a new profile from The Arrays List, using the Create
Profile option under the More drop-down in The Configure Arrays
Toolbar.
Figure 149. Add a Profile
Management System
ManagingbyProfiles 209
Enter the new Profile Name, then select the Arrays that are to be
members of this profile. Only Arrays that are not already assigned to
another profile are listed. For your convenience, the current software
version running on each Array is shown. Click OK when done.
Note that you may also add Arrays to a profile from The Arrays List,
using the Assign to Profile button in The Configure Arrays Toolbar.
An Array may not be a member of more than one profile. If you wish to
move an Array from another profile to this one, it must be removed from
the old profile first. The easiest way to do this is by using the Assign to
Profile button in The Configure Arrays Toolbar. The Assign to Profile
button will remove each selected Array from its old profile assignment (if
any) and add it to the specified profile in one step. See The Configure
Arrays Toolbar on page 107.
Edit this option allows you to change which Arrays are members of the
profile. The Arrays listed include both the profile's current members, and
Arrays that are not already assigned to another profile.
Figure 150. Edit a Profile
Management System
210 ManagingbyProfiles
You may check Arrays to add them to the profile, or uncheck them to
remove them from the profile. Click OK when done. This does not delete
the unchecked Arrays from the XMS database - they just cease to be
assigned to a profile network, and their configuration and software
version are untouched by this action.
When you add an Array to an existing profile network that has a software
version and or configuration defined, the new member is checked for
compliance with this profile. If needed, jobs are triggered to upgrade the
software version and/or update the configuration. Note that if both are
needed, the software upgrade is always performed first. Then, if the
configuration update involves new settings that are only implemented in
the new software version, they will be handled properly.
Deletethis option deletes the selected profiles. It does not delete the
member Arrays from the XMS database - they just cease to be assigned to
a profile network. The configuration and software version of these Arrays
are untouched by this deletion. You will be asked to confirm the
operation.
Default this option sets one selected profile as the default. When
Arrays are discovered, they are automatically added as members of the
default profile. These Arrays are automatically checked for compliance
with the profile and updated as described above for the Edit button.
Copy Profilethis option creates a duplicate of one selected profile.
This feature is handy if you have already configured some profile
network and then you want to define another profile whose configuration
is just slightly different. Select the checkbox of the profile to be duplicated
and click this button. Enter the name of the new profile.

If a software upgrade is required, all associated stations will lose connection to
the Array for a period of time while the Array is rebooting. Use caution when
assigning Arrays to profiles on a production network.
Management System
ManagingbyProfiles 211
Figure 151. Copy a Profile
The new profile is created with no member Arrays. Use the Edit button to
add the desired Arrays to it. The new profiles Configuration and AOS
Version are identical to those of the original profile until you change
them.
Create From Arraythis option creates a new profile with an initial
configuration that is copied from the selected Array. This is useful if you
already have a Xirrus network deployed and wish to create profiles to
mirror the existing settings, or if you prefer to perform configuration
directly on an Array and then create a profile based on it.
Figure 152. Create a Profile from an Array
You may also create a profile from a selected Array in The Arrays List or
from an Array Details page, by selecting More > Create Profile from The
Configure Arrays Toolbar.
Management System
212 ManagingbyProfiles
The new profile is created with no member Arrays and no AOS Version.
Use the Edit button to add the desired Arrays to it. The new profiles
Configuration settings are identical to those of the prototype Array until
you change them, except as noted below.
The rules listed in Settings that are omitted from profile
configuration on page 218 are observed.
VLANs are copied, and Enable VLAN Management For This Profile
is enabled.
Profiles may have lower limits for the number of entries allowed for
certain settings than some Arrays do. For example, if the prototype
Array has more than 8 SSIDs configured, you will see an error
message.
Admin Management accounts and Admin Privileges are not copied
from the prototype Array. Only the default admin account will be
created. Configure other accounts or privileges separately in the
profile. Also, the settings shown in Settings that are omitted from
profile configuration on page 218 are not included in the profile.
The profile is created using the configuration data for the Array that
is already in the XMS database, rather than reading the configuration
directly from Array. If you wish, you may refresh the Array prior to
creating the profile, using the Refresh button on The Arrays List
pagethis will update XMS with the latest configuration.
Set AOS Version

The model Array selected for the Create from Array feature must be an XN or
XR Array model. The profile cannot be created from an XS Array
Management System
ManagingbyProfiles 213
Click this button to set up the desired ArrayOS software version for this
profile network. You can specify the software version regardless of
whether or not the profile contains any member Arrays.
Follow the same steps described in Perform or Schedule Upgrade on
page 134, except that you will not be asked to specify the Arrays to be
upgraded since the software version selected here will be enforced on all
members of the profile network. Similarly, you do not specify a scheduled
time for the upgrade. Note that Array licenses will be updated if
necessary prior to the upgrade, also as described in Perform or
Schedule Upgrade on page 134.
Figure 153. Set Profiles Software Image
Member Arrays will be checked for the correct ArrayOS software version
when:
You enter a different software version in Set AOS Version.
An Array is added to the profile network either via discovery, or by
using the Edit button.
You click the Sync Arrays button.

The Set AOS Version button is not available for XMS Cloud. Array upgrades
are managed by Xirrus personnel.

XS and XN Series Arrays do not support ArrayOS Release 6.5 or above. If you
attempt to upgrade XN or XS Arrays to Release 6.5 or above, the upgrades will
still be scheduled. These upgrades will fail and display the following error:
AOS version is not supported by this Array model.
Management System
214 ManagingbyProfiles
To reset the AOS version back to none, choose the blank entry in the
System Software drop-down list (in Step 2 - Select Software Versions).
In this case, the profile network will not require member Arrays to run a
specific software version.
Sync ArraysClick this button to check that all member Arrays comply
with the profile. Software and then configuration are updated if needed,
as described above for the Edit button. Any configuration changes
performed can be seen in the job status tab. Use this feature if you have
used XMS to make configuration changes to individual member Arrays
and wish to revert to the standard profile configuration.
Profile Details
By clicking the Name of a profile in The Profiles List, you may view a variety of
details about the selected profile network.
Profile DetailsArrays on page 215a list of member Arrays.
Profile DetailsConfiguration on page 216this tab allows you to
define the configuration settings for all member Arrays.
Profile DetailsJob Status on page 220this tab shows all the
configuration/software upgrade jobs for member Arrays, along with
their status.
Management System
ManagingbyProfiles 215
Profile DetailsArrays
This page lists the member Arrays of this profile network. By default, it shows the
Hostname, Management IP Address, Location, Model, count of associated
Stations, and current running AOS Version for each. The Edit button allows you
to change which Arrays are members of this profile, as described for the Edit
button in The Profiles Toolbar on page 208.
Figure 154. Profile Details: General
Click the Configuration tab to define the Array settings for this network.
Management System
216 ManagingbyProfiles
Profile DetailsConfiguration
This page has an extensive menu of options for defining the configuration profile
on the member Arrays. Almost all of the settings that are available in the Array
Web Management Interface (WMI) are also available here.
Figure 155. Profile Details: Configuration
The configuration profile is a complete configuration rather than an incremental
one. This means that the profile entirely replaces all settings on each member
Array, rather than simply updating a few settings that you entered. Any settings
that you havent specified are set to the default value, shown on this
Management System
ManagingbyProfiles 217
Configuration tab, except for Settings that are omitted from profile
configuration on page 218.
For an explanation of all of the settings available on the Configuration tab, see
Configuring a Wireless Array on page 393. When you create a new profile, it
will have the default configuration setting values shown in Default Profile
Configuration, below.
Default Profile Configuration
All configuration setting values for new profiles will be the default Array values,
except for the following:

If you plan to define a required ArrayOS version for this profile network, we
strongly recommend that you do that first using the Set AOS Version button,
as described in The Profiles Toolbar. The profile network performs the
required software upgrades before updating configuration on member Arrays.
This ensures that settings for new features in the specified software version are
handled correctly.
Tab Setting Value
Security> Admin
Management
User Name/Password admin/admin
Network>DNS Hostname
DNS Servers
Not displayed
0.0.0.0
Services> SNMP Context Engine ID Not displayed
Services> Location Location Support Disabled
SSIDs> SSID
Management
Name xirrus
IAPs> Advanced RF
Settings
Enable Standby Mode
Standby Target Address
Not displayed
Not displayed
(Array specific
settings)
Management System
218 ManagingbyProfiles
Settings that are omitted from profile configuration
Some settings cannot be configured as part of a profile. Settings such as the Array
IP address must be unique, and the assigned address must not be changed when
the profile configuration is pushed to the Array. For this reason, such settings
are not shown anywhere on this Configuration tab at all. Individual IAP settings
(channel, cell size, etc.) are also not changed, since these are tailored to the
environment of each Array.
The following settings are not part of the profile configuration and are left
unchanged (i.e., not included) in the profile.
General: Location, License Key
Network> Interfaces: IP Address, Subnet Mask, Default Gateway
Network> DNS: Hostname
Network Bonds: all settings (i.e, this page is not present for profiles)
Services> SNMP: Context Engine ID
SSIDs > Active IAPs: all settings (i.e, this page is not present for profiles)
IAPs > IAP Settings: Individual IAP settings are not changed, but you
may enable or disable all IAPs at the same time.
IAPs> Global Settings: Country
IAPs> Advanced RF Settings: Enable Standby Mode, Standby Target
Address
Tunnel Management: Local Endpoint
IAPs> Global Settings Country Not set
IAPs> Global Settings 11n TX and RX Chains 3
Filters> Filter Lists Filter List Name global
Tunnels> Tunnel
Management
Local Endpoint Not displayed
Tab Setting Value
Management System
ManagingbyProfiles 219
If you need to modify settings listed above, you may do this using other XMS
configuration options. For example, for IAP settings, see Configure Wireless
Settings on page 141. For IP settings, see Configure Network Settings on
page 145.
Settings that are only present in profile configuration
Some settings are only used as part of a profile, and you will not see them in
Configuring a Wireless Array on page 393. These are special settings that deal
with the differences in the range of Array/AP models. Currently, there is only one
such setting.
IAPs > Advanced RF Settings: Enable Timeshare for 2-Radio Arrays
By default, the RF Monitor Mode on profile-member Arrays is
Dedicated, which means that the IAP that is set as the monitor radio
observes the RF-environment full-time for problems. This is very good for
larger Arrays, but it is inefficient usage of radio resources for Arrays/APs
that only have two radios.
If RF Monitor Mode is set to Dedicated for the profile, then you may set
Enable Timeshare for 2-Radio Arrays to Yes. Then Arrays/APs that are
members of the profile and that have only two radios will use Timeshare
mode for the monitor IAP. This allows that IAP to spend part of its time
as a monitor radio, and function as a normal radio providing wireless
service to stations the rest of the time. See RF Monitor on page 532 for
other settings that control timeshared use of the monitor radio. This
setting defaults to Yes when RF Monitor Mode is set to Dedicated.
Management System
220 ManagingbyProfiles
Profile DetailsJob Status
This page shows jobs launched for member Arrays by the profile. You may select
whether to show AOS Upgrades, Array Config updates, Discovery, or All Jobs.
Note that if AOS Upgrades and Array Config updates need to be performed for
the same Array, the software upgrade is performed first. This ensures that any
configuration settings related to new features in the upgraded software will be
handled properly.
Figure 156. Profile Details: Job Status
By default, this page shows the following columns:
Status Indicatorgreen for success, red for failure.
Status Updatedthe last time this status was updated.
Hostnamethe host name of the member Array that is being updated by
this job.
Management IP Addressthe IP address of the member Array that is
being updated by this job.
Job Typethe type of update that this job is performingAOS Upgrade
or Array Config.
Management System
ManagingbyProfiles 221
AOS Versionthe current ArrayOS version running on the member
Array that is being updated by this job.
Target AOSthe ArrayOS version defined for this profile network, if
any.
Messageinformation about the job performed on the Array, if
successful; or the type of failure, otherwise.
Management System
222 ManagingbyProfiles
Management System
ManagingSwitches 223
Managing Switches
XMS manages Xirrus 24-port XT-5024 and 48-port XT-5048 PoE+ Gigabit wired
access switches. Pages are provided for monitoring these switches, and for
common configuration tasks. Switch management pages are very similar to Array
management pages, for ease of use.
Xirrus 24- and 48-port switches offer intelligent power distribution across all
ports. IEEE802.3at (PoE+) and 802.3af (PoE) is available on every port. These
switches may be used to power Xirrus Arrays and APs that are compatible with
802.3af or 802.3at, such as the XR-520 AP.
Switch management is discussed in the following topics:
Switch Discovery on page 224
Monitoring Switches on page 224
Configuring Switches on page 225
Switch Details on page 226
SwitchGeneral Information on page 227
SwitchConfiguration on page 228
Switch ConfigurationSystem on page 228
Switch ConfigurationIP on page 229
Switch ConfigurationPoE Configuration on page 231
Switch ConfigurationVLAN on page 235
SwitchPoE Status on page 240
To see which Array port is being powered by each switch port, see Port
Mappings by Switches on page 132.

Many Xirrus Array models require Xirrus-supplied injectors. Their power
requirements are not compatible with the XT-5024/XT-5048. See the Quick
Installation Guide for the Array model for more information about powering it.
Management System
224 ManagingSwitches
Switch Discovery
Xirrus wired switches are discovered in exactly the same way as Arrays/APs.
When you tell XMS what subnets to run discovery on to find Arrays, it will find
XT-5024 and XT-5048 switches and Xirrus-supplied managed power injectors at
the same time. Please see the discussion starting with Discovery on page 162
for complete details.
When a wired switch has been discovered, it will appear on the Switches List
(Monitor) as shown below.
Monitoring Switches
This page lists the switches in the XMS database. To display it, click the Switches
link under Monitor at the top of the page. This page is identical to the
Configure Switches page (see Configuring Switches on page 225).
The Switches List shows Xirrus wired PoE+ switches that have been discovered
by XMS (see Switch Discovery). Each switch entry is identified by its MAC
address, and also displays the units HostName, Model (XT-5024 and XT-5048),
IP Address, and running Firmware Version. A green or red dot shows the current
status of each switch. For detailed information on the status of the switch and its
individual ports, see SwitchPoE Status on page 240.
Figure 157. Switches List (Monitor)
Please see Configuring Switches on page 225 for the operations available on
this page. To see which Array port is being powered by each switch port, see
Port Mappings by Switches on page 132.
Management System
ManagingSwitches 225
Configuring Switches
This page lists the switches in the XMS database. To display it, click the Switches
link in the Switch Configuration section under Configure at the top of the page.
This page is identical to the Monitor Switches page (see Monitoring
Switches on page 224).
Figure 158. Switches List (Configure)
The switches list offers the following functions:
Click on a switchs Name (MAC Address) to access the Switch Details
pages. These offer some powerful features, especially the Configuration
page, which allows you configure the most commonly used settings on
that switch. See Switch Details on page 226 for more information.
Click the Refresh button to refresh discovery and status on the selected
switches. Status is automatically polled every 30 seconds.
Click the Delete button if you wish to remove the selected switches from
the database.
In addition, a number of common operations are available on the Switches page
to allow you to customize it for your own use. These functions are similar to the
functions available on the The Arrays List:
Select Columns on page 61
Export on page 62
Select Rows on page 63
Rearranging and Resizing Columns in a Table on page 63
Management System
226 ManagingSwitches
Sorting on page 63
Searching on page 64
Switch Details
By clicking the MAC Address of a switch in the Switches List (from either the
monitor page or the configure page), you may view or configure a variety of
details about the selected unit. The details page for a switch has three tabs:
The General tab shows status and version information. See Switch
General Information on page 227.
Configuration tabconfigures the most commonly used switch settings
for system information, IP network and VLAN settings, and PoE settings.
See SwitchConfiguration on page 228.
PoE Status tabthis tab shows details of power usage for each individual
port and for the switch as a whole, as well as the status of each port. See
SwitchPoE Status on page 240.
To specify which Array is being powered by each switch port, see Port
Mappings by Switches on page 132.
Management System
ManagingSwitches 227
SwitchGeneral Information
Select the General tab to display status and version details.
Figure 159. Switch DetailsGeneral Information
The running status of the switch is indicated as Status Up or Status
Down.
The time since the last boot is shown in Up Time.
Running software versions are indicated in Bios Version and Firmware
Version.
Management System
228 ManagingSwitches
SwitchConfiguration
The Configuration tab allows you to manage the following settings:
Switch ConfigurationSystem on page 228 sets the hostname and
contact information.
Switch ConfigurationIP on page 229 configures IP network settings.
Switch ConfigurationPoE Configuration on page 231 sets port
priority and enables/disables each port.
Switch ConfigurationVLAN on page 235 configures VLAN settings.
Switch ConfigurationSystem
This window allows you to set general information about this switch, including
changing its host name and setting administrator contact information.
Figure 160. Switch DetailsSystem Information
Procedure for Configuring System Information
1. Hostname: Specify a unique host name for this switch. The host name is
used to identify the switch on the Layer 3 network. Use a name that will
be meaningful within your network environment.
2. Location Information: Enter a brief but meaningful description that
accurately defines the physical location of the switch. In an environment
Management System
ManagingSwitches 229
where multiple units are installed, clear definitions for their locations are
important if you want to identify a specific unit.
3. Admin Contact: Enter name and contact information for the person
responsible for administering the switch at the designated location.
4. Click the Apply Config button at the top of the configuration window to
apply these changes to the switch. To make these changes permanent,
check Save to flash before using the Apply Config button.
Switch ConfigurationIP
This window manages network interface settings. For each setting, the Current
value on the switch is shown on the right. In the Configured column on the left,
there are fields where you may change IP settingsthese fields simply display
the last values that you typed in, and they initially show factory default values. If
you change any values, they will not be applied on the switch and reflected in the
Current values until after you click the Apply Config button.
Figure 161. Switch DetailsIPv4
Management System
230 ManagingSwitches
Procedure for Configuring the Network Interfaces
1. Use DHCP Client: use this option to instruct the switch to use DHCP to
obtain its IP address, or turn off this option if you intend to perform IP
configuration manually. If you turn off Use DHCP client, you must
specify a static IP address, subnet mask, and default gateway below. If
Use DHCP Client is enabled, then all of the fields below it are disabled
except for VLAN ID.
2. IP Address: If you turned off the DHCP Client option, enter a valid static
IP address for the switch. To use remote management (Web or SNMP), a
valid IP address must be established.
3. IP Mask: If you turned off the DHCP Client option, enter the subnet
mask (the default for Class C is 255.255.255.0). The subnet mask defines
the range of IP addresses that are available on the routed subnet where
the switch is located.
4. IP Gateway: If you turned off the DHCP Client option, enter a valid IP
address for the default gateway. This is the IP address of the router that
the switch uses to transmit data to other networks.
5. VLAN ID: Specify the VLAN number to be used as the switch
management VLAN. By default, all ports are in VLAN 1. This VLAN is
untagged. Be very careful when changing this value. Changing the VLAN
ID can cause you to be unable to connect to the switch if the network
interface is not correct. We recommend that you leave this unchanged
unless you have determined that a change is required.
6. DNS Server: Enter the IP address of a DNS server to be used to resolve
domain names and host names to IP addresses.
7. Click the Apply Config button at the top of the configuration window to
apply these changes to the switch. To make these changes permanent,
check Save to flash before using the Apply Config button.

If Use DHCP Client is enabled but the switch is unable to obtain an IP
address via DHCP, the switch will use the settings that are shown in the
Configured column.
Management System
ManagingSwitches 231
Switch ConfigurationPoE Configuration
This window displays power settings for switch ports. You may manage power
injection for each port, and set the priority for allocating power to the port.
Above the list of ports, Primary Power Supply (W) shows the maximum total
power that is available for ports on this switch model. (See SwitchPoE Status
on page 240 for details of how much power each port is using at this time.)
Figure 162. Switch DetailsPoE Configuration
Retry Timewhen a port draws more power than permitted by its Maximum
Power setting (see below), the switch turns off power to that port. The switch
waits Retry Time seconds before trying to turn power back on to an overloaded
port. If Retry Time is set to 0, the switch will not attempt to turn power back on to
ports, and overloaded ports will remain off until you turn them back on manually.
For each switch port, the following settings are shown. They may be modified
with the Bulk Edit button.
PoE Mode: Enable allows the injection of power on this port. Disable
turns off the injection of power on this portonly data traffic is
transmitted on the port.
Management System
232 ManagingSwitches
Priority: This is the priority of this port for power allocation, if the power
drawn by all ports exceeds the power available on the switch (as shown
in Primary Power Supply). If there is insufficient power, the switch will
first turn off ports assigned Low priority, then ports assigned High
priority. Power will be dropped last from ports that have Critical priority.
One of the ports with the lowest priority will be turned off, starting from
the highest port number. Additional ports are turned off one at a time as
necessary, following the same rule. When the over power-budget
situation ends, the switch will automatically reallocate power to ports
that were turned off due to insufficient total power. The ports that were
turned off last are normally restored first, since they are the higher
priority ports. Note that this process for restoring ports is not related to
Retry Time.
Maximum Power (W): This is the maximum amount of power that this
port is allowed to supply. If the connected device begins to exceed this
maximum, power is cut off to this port. You may specify a different
maximum for each of the switchs copper ports, if you wish. The default
value is 30W.
The maximum power that the switch can supply to a port is normally
30Whowever, on the XT-5024 and XT-5048, the first twelve copper ports
(Ports 1-12) can each be set to supply up to 38W. Standard power is 15.4W
for IEEE802.3af compliant devices, and 30W for IEEE802.3at compliant
devices.
Switch power is dynamically pooled from the power supply across all of
the switchs ports. Over-subscription of power is permitted, i.e., the sum
of the maximum power specified for all of the ports may exceed the value
shown for Primary Power Supply. For example, the maximum power

You must set Maximum Power to the highest level that the Array or AP may
need to draw. If the Array/AP becomes heavily loaded and requires more power
than you have set in Maximum Power, the powered device will reboot as the
overload causes the port to be turned off and then on again after a delay of Retry
Time seconds.
Management System
ManagingSwitches 233
that an XT-5024 can supply is 370 W. As an example, you may enable PoE
on 15 ports and set maximum power on each of them to 30W, a total of
450W. Lets say that each of your powered devices typically draws 20W,
and may occasionally require peak power of up to 30W when very busy.
Since the typical total power usage is 15 x 20 = 300W and power is pooled
across the ports, the switch has 70W to spare that may be drawn by
devices needing more power.
We recommend that you do not over-subscribe the switchs available power by
more than 20%. If connected devices attempt to draw more power than the
switch can deliver, power will be turned off on ports as described above,
based on the Priority setting of each port.
The switch waits Retry Time seconds before trying to restore power to
overloaded ports.
Procedure for PoE Configuration
1. Retry Time: The switch waits this number of seconds before trying to
turn power back on to overloaded ports. Adjust this time if needed. The
default is 60 seconds.
2. Bulk Edit: Click this button to change the settings of one or more ports at
the same time. Select the checkboxes of the ports that you wish to edit to
have identical settings. All of these ports will be configured to have the
settings that you specify in the Bulk Edit dialog box. (Figure 163)
Figure 163. Switch DetailsPoE Bulk Edit
Management System
234 ManagingSwitches
3. Configure PoE settings as follows. For detailed explanations of these
settings, see the discussion above.
PoE Mode: Select Enable to make PoE power available on this port.
Priority: Select the priority of this port for power allocation, Low,
High, or Critical.
Maximum Power (W): Select the maximum power that this port is
allowed to supply. The default value is 30W. Decimal numbers are
allowed, e.g., 15.4. Exceeding this peak value causes the switch to
detect an overload and shut off power to the port. Standard power is
15.4W for IEEE802.3af compliant devices, and 30W for IEEE802.3at
compliant devices. The maximum power is 30Whowever, on the
XT-5024 and XT-5048, Ports 1-12 can each be set to supply up to 38W.
See the discussion following Figure 162 on page 231 for more
information.
4. Click the Apply Config button at the top of the configuration window to
apply these changes to the switch. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
ManagingSwitches 235
Switch ConfigurationVLAN
This window allows you to create and manage VLANs, including defining the
ports that are members of each VLAN. The following pages are used to manage
VLANs:
Switch ConfigurationVLAN Membership on page 235used to
create VLANs and specify the ports that are members.
Switch ConfigurationVLAN Ports on page 237used to configure a
number of attributes of VLAN behavior, on a per port basis.
Switch ConfigurationVLAN Membership
This page creates and modifies VLANs, and specifies the ports that are included
in the VLAN.
The list of VLANs shows the VLANs that you have already created, identifying
them by VLAN Name and VLAN ID. Each VLANs entry indicates the ports that
it includes, represented by green dots . You may Add new VLANs, and Edit or
Delete existing VLANs.
Figure 164. Switch DetailsVLAN Membership
Procedure for VLAN Creation and Membership Configuration
1. To create a VLAN, click the Add button.
2. Enter the Name of the VLAN, and a unique VLAN ID number. The
Name may be up to 32 alphanumeric characters long.
Management System
236 ManagingSwitches
Figure 165. Switch DetailsVLAN: Create/Membership
3. Select the membership setting for each port:
blankleave the setting blank to exclude this port from the VLAN.
This is the default for all ports.
memberselect this to make the port a member of the VLAN.
forbiddenthis port is forbidden to join the VLAN. GVRP cannot
automatically add this port to the VLAN.
4. You may select the checkbox to the left of a VLAN and click the Edit or
Delete button to modify or remove a VLAN.
5. Click the Apply Config button at the top of the configuration window to
apply these changes to the switch. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
ManagingSwitches 237
Switch ConfigurationVLAN Ports
This page configures the VLAN settings for switch ports. For each port, the
following settings are shown. They may be modified with the Bulk Edit button.
Figure 166. Switch DetailsVLAN Ports
Native VLAN: The VLAN that carries untagged traffic on this port. When
multiple VLANs are trunked on the same port, traffic for each VLAN is
tagged with its VLAN number as specified in IEEE802.1q. Untagged
traffic is automatically assigned to the native VLAN, and native VLAN
traffic is not tagged when the port transmits it. The allowed values are 1
through 4094. The default value is 1. Note: The port must be included as a
member of the Native VLAN (see Switch ConfigurationVLAN
Membership on page 235).
Port Type: Port type should normally be set to C-port.
C-port is a Customer Port. This is the default setting, and you should
normally leave the port type as C-port.
The following settings are for special situations, such as QinQ, and are
not typically used. These settings support IEEE 802.1ad Provider
Bridging, also known as Stacked VLANs or QinQ. It essentially
implements multiple levels of VLANs by supporting multiple tags in a
Management System
238 ManagingSwitches
frame, allowing customers to run their own VLANs inside a VLAN
established for them by a service provider. Thus, the service provider can
just configure one VLAN for the customer and the customer can then
treat that VLAN as if it was a trunk.
Unaware classifies all frames to the Port VLAN ID and tags are not
removed.
S-port is a Service port.
Custom S-port is an S-port with a Custom TPID (tag protocol
identifier).
Ingress Filtering: This setting determines the ports VLAN ingress
processing. If ingress filtering is Enabled and this port is not a member of
the VLAN specified in a frame, the frame is discarded.
Frame Type: This setting determines the types of frames that are accepted
by VLAN ingress processingAll frames, only Tagged frames, or only
Untagged frames. If the port only accepts tagged frames, untagged
frames received on that port are discarded.
Egress Rule: This setting determines VLAN egress processingit
controls whether and how VLAN tagging occurs on outgoing frames.
If Trunk is selected, outgoing VLAN traffic is tagged with the
VLANs ID. This mode is normally used for ports connected to
VLAN-aware switches.
If Hybrid (the default value) is selected, this VLANs tag is inserted
in the frame unless the frame is belongs to the Native VLAN.
If Access is selected, all frames transmitted on the port are sent
untagged.
Procedure for VLAN Port Configuration
1. To configure identical VLAN Port settings for one or more ports, click
their checkboxes and then click the Bulk Edit button.
2. The Bulk Edit dialog box allows you to configure settings for Native
VLAN, Port Type, Ingress Filtering, Frame Type, and Egress Rule. See
the discussion above for descriptions of these settings.
Management System
ManagingSwitches 239
Figure 167. Switch DetailsVLAN Ports Bulk Edit
3. Click OK when done.
4. Click the Apply Config button at the top of the configuration window to
apply these changes to the switch. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
240 ManagingSwitches
SwitchPoE Status
Select the PoE Status tab to view details of power usage for each individual port
and for the switch as a whole, as well as the status of each port. This page also has
a Power Cycle button that allows you to turn the selected ports off and on in one
step, to perform a reset of the devices being powered by those ports.
Figure 168. PoE Status tab (Configure)
This page displays the following information.
Switch Power Statistics
PD Class: The class of the powered device (PD) that the switch has
detected on this port. The class indicates the maximum level of power
expected to be supplied by the switch port for the PD.
Class 015.4 W
Class 14 W
Class 27 W
Class 315.4 W
Class 430 W
Management System
ManagingSwitches 241
Power Requested (W): the amount of power that the PD has requested to
have reserved. This is based on the PD, rather than the Maximum Power
setting that you configured on this port.
Power Allocated (W): the amount of power that the switch has allocated
for the PD.
Power Used (W): how much power the PD is currently using.
Current Used (mA): how much current the PD is currently drawing.
Priority: the priority setting that you configured on this port.
Port Status: the operating status of this port. May be one of:
PoE disabledthe PoE Mode setting for this port is Disabled.
No PD detectedthe PoE Mode setting for this port is Enabled, but
no compliant PD has been detected.
PoE turned ONa PD has been detected, and power is being
supplied.
PD Overloadthe PD has attempted to draw more power than the
Maximum Power setting allows, and the port has been turned off.
The switch will attempt to turn the port back on at an interval defined
by the Retry Time setting.
To see which Array port is being powered by each switch port, see Port
Mappings by Switches on page 132.
Management System
242 ManagingSwitches
Management System
WorkingwithMaps 243
Working with Maps
This chapter takes you on a tour of the web clients map window and its features.
It walks you through creating a map, and shows you how to display a heat map of
your RF coverage. Section headings for this chapter include:
About Maps on page 244
Getting Started with Maps on page 244
The Map Window and Heat Contour Map on page 246
Migrating Maps from Earlier Releases on page 254
Preparing Background Images for New Maps on page 254
Adding a New Map on page 256
Setting the Map Scale and North Direction on page 258
Adding Arrays to Maps on page 261
Saving a Map on page 263
Viewing Array, Station, or Rogue Details on page 264
Locating Devices on page 267
Deleting a Map on page 271
Managing Arrays Within Maps on page 272
Zooming or Moving the Map on page 275
Edit Mode Toolbar on page 276
Map Options Panel on page 278
Map Layers Panel on page 286
Management System
244 WorkingwithMaps
About Maps
Maps offer a topographical view of your wireless network and the RF coverage it
provides. From a map you may view a variety of information about each Array,
its radios and associated stations. Array management functions may also be
applied from the map.
A heat map shows wireless coverage at your site, and is based on measurements
observed by Arrays. It visualizes the RF environment provided by your wireless
network. The map incorporates directional antenna coverage on a per radio basis,
and readings are enhanced by means of inter-Array correction. By leveraging the
RF analysis capabilities available on the Array, XMS makes it easy to view the
changing RF environment.
A performance plan shows the predicted throughput of the wireless network
under various types of usage, for network planning and troubleshooting.
The XMS Location capability displays the position of a station or rogue device on
the map for you, facilitating asset tracking and security policy enforcement.
Getting Started with Maps
This overview describes how to get started using maps, and points you to topics
that describe each step in detail.
The Map Window and Heat Contour Map on page 246 provides an
overview of the map window.
Migrating Maps from Earlier Releases on page 254 XMS is
furnished without any default maps. However, if you have already
created maps in pre-6.2 releases of XMS, they will automatically be
migrated to the current release.
To add a new map (and modify existing ones):
Preparing Background Images for New Maps on page 254 you
must supply a background image for your map, such as a floor plan
or a site layout of buildings.
Adding a New Map on page 256 follow these instructions to
create a new map.
Management System
WorkingwithMaps 245
Setting the Map Scale and North Direction on page 258 set the
distance scale for the map, so that RF contours will display
accurately.
Select the Arrays that belong on the map. Rotate each Array on the map
so that the monitor radio has the correct orientation (Note that many XR
Arrays can automatically detect North, and XMS places these on the map
in the correct orientation). See Adding Arrays to Maps on page 261.
After completing the steps above, you may use the RF Heat Contour Map
to present a live display of RF coverage by Array. To manage Arrays, see
Managing Arrays Within Maps on page 272.
After completing the steps above, you may use the Performance Plan to
predict the performance of the network under different usage scenarios.
You may customize your display. See Map Options Panel on page 278
and Map Layers Panel on page 286.
Management System
246 WorkingwithMaps
The Map Window and Heat Contour Map
Map List
Add/Delete Map
Monitor/Edit Mode
Map Layers to display
Show/Hide Map Options Panel
Map Options Panel
Heat Map RSSI Legend
Selected Map showing
RF Heat Contour
Edit Mode Toolbar
Set North, Move & Zoom Map
Show/Hide Map Layers
To display the map window, click the Maps link in the Overview section under
Monitor at the top of the page. Select the desired map from the Map List.
Figure 169. Main Map with RF Heat Contours Enabled
No default maps are provided. If you have created maps in a previous release of
XMS, they will be present after you upgrade. When you upgrade to a new release
Management System
WorkingwithMaps 247
of XMS, maps created in earlier releases will be automatically migrated. See
Migrating Maps from Earlier Releases on page 254. You may create new maps
as described in Adding a New Map on page 256.
The map window has the following parts:
The Map List
RF Heat Contour Map
Performance Plan
Map Options Panel
Map Layers Panel
Array Management Panel
The Map List
Map List
Map Options
Map
Options Tab
Add/Delete Map Monitor/Edit Mode
This list shows all of the maps in the XMS database. If the Map List is not visible
at the left of the map, click the Map Options tab as shown in Figure 170.
Figure 170. The Map List and Map Options Panel
The Map List has a tree structure, with child maps displayed under parent maps.
If the desired map name is not visible, click the + sign to the left of its parent to
expand the parent entry.
Management System
248 WorkingwithMaps
Click on a map to display it. If the currently displayed map has unsaved changes,
you will be asked whether to save the changes before displaying the new map.
RF Heat Contour Map
Heat Map RSSI Legend/
Minimum Acceptable RSSI
Edit Mode Tool Bar
Show Contour Lines
The heat map gives an at-a-glance representation of the Arrays in an area, their
locations, and the RF coverage that they provide. Areas of low coverage are
immediately visible. In order to display this view, enable Heatmap in the Map
Layers Panel. You may hover over an Array to display a popup identifying the
Array, or double-click an Array to show more information about it. See Viewing
Array, Station, or Rogue Details on page 264.
Figure 171. Main Map Showing RF Heat Contours
When enabled, RF contour lines are displayed on this map to show the strength of
RF signals broadcast by each Array. To display contours, enable Show Contour
Lines in Heatmap Options in the Map Options panel (see Map Options Panel
Management System
WorkingwithMaps 249
on page 278). If an Arrays radios are disabled, no contours are displayed for that
Array. Signal strength is displayed using the colors shown in the Heat Map RSSI
Values legend under the map.
The bottom of the map also has a heat map RSSI legend, which defines the signal
strength indicated by each color. You may define a minimum acceptable signal
strength by clicking that value on the legend. The map will only display RSSI
levels above that value in color. Areas with unacceptable signal strength are
obvious, as they have no color, as shown in Figure 171.

You may add any model of Xirrus Arrays or Access Points to a map (see
Adding Arrays to Maps on page 261). However, units that use
external antennas (such as XR-520H, XR-1230H, etc.) will not display heat
contours.
Management System
250 WorkingwithMaps
Performance Plan
Performance Plan Throughput Legend
The performance plan offers a visual representation of the predicted throughput
of the wireless network over your site for different station/user profiles. Use this
as a resource to plan for network expansion and troubleshoot network
performance issues. In order to display this view, enable Performance Plan in the
Map Layers Panel.
Figure 172. Performance Plan Map
The Performance Plan shows expected performance of your network, using color
to indicate whether the level of throughput in an area will be excellent, good,
okay, poor, or non-existent. The prediction is calculated based on selectable
station characteristics including: number of stations on the map, station device
type, band, WiFi mode, and typical application. Expected throughput is
computed using these characteristics and observed performance of the network.

This is a Beta release feature in Release 6.6.
Management System
WorkingwithMaps 251
See Performance Plan Options on page 281 to set the characteristics of your
network.
In addition, settings on the Array IAPs can also impact the plan, including: band,
channel, bond mode, WiFi mode, cell size, Tx dBm, Rx dBm, Tx chains, and status
(enabled/disabled). Predicted throughput is computed based on the current
settings of your IAPs, rather than their maximum settings. For example, any of
the following settings will result in computed throughput that is less than the
maximum that the Arrays can support: having radios disabled, setting reduced
transmit/receive power, reduced cell size, etc.
The bottom of the map has a performance legend that defines the throughput and
user satisfaction level indicated by each color.
Map Modes of Operation and User Privileges
XMS maps have two modes of operation:
Edit Modethis mode displays the Edit Mode Toolbar (Figure 171) and
allows you to make basic changes to a map, such as adding, moving,
orienting, and deleting Arrays, changing map settings like the RF
environment, and setting the map scale. In edit mode, you may use the
Map Options Panel and Map Layers Panel to customize the map display.
Monitor Modethis mode does not allow you to make basic changes
such as adding and deleting Arrays. In monitor mode, you may use the
Map Options Panel and Map Layers Panel to customize the map display.
You may also use the Array Management Panel to manage the maps
Arrays with functions such as rebooting or configuring settings on
Arrays. See Managing Arrays Within Maps on page 272. The Array
Management panel is not available in edit mode.
XMS users with read-write privileges may use edit mode and monitor mode.
Users with read-only privileges may only use monitor mode; also, these users
have access to a restricted set of functions on the Array Management Panel.
Management System
252 WorkingwithMaps
Use the button shown below to change modes. (Figure 173) The Monitor Mode
button appears when you are in Edit Mode. Use it to switch to Monitor Mode.
Similarly, the Edit Mode button appears when you are in Monitor Mode. Use it to
switch to Edit Mode.
Figure 173. Add/Delete a Map and Edit/Monitor Mode Buttons
Overview of Map Features
The operations available in the map window depend on your XMS account
privileges and the selected map mode, as discussed above in Map Modes of
Operation and User Privileges.
XMS offers the following map functions:
Add or Delete Map (edit mode and monitor mode)the plus and minus
buttons provide these functions. (Figure 173) See Adding a New Map
on page 256.
Edit or Monitor Modemap modes determine the operations that are
available. (Figure 173) See Map Modes of Operation and User
Privileges on page 251.
Map List (edit mode and monitor mode)select the desired map from
this tree structured list. (Figure 170) See The Map List on page 247.
Array, Station, or Rogue Infodouble-click an Array on the map (single
click a station or rogue) to show detailed information about the item. See
Viewing Array, Station, or Rogue Details on page 264.
Map Options Panel (edit mode and monitor mode)these options affect
a number of aspects of the map display. (Figure 170) Some of the options
include:
Heatmap Options select the bands displayed (2.4 GHz/5 GHz), the
transparency of the heat map, and whether to show contour lines.
Floorplan Options select the transparency of the background floor
map, the size of Array icons, and how much information to display
for individual Array radios.
Management System
WorkingwithMaps 253
Rogue Location shows rogues that have been detected.
Station Location shows stations that are associated to Arrays.
Channel Configuration performs an automatic channel
configuration on Arrays.
See Map Options Panel on page 278 for a detailed discussion of the
Map Options panel.
Map Layers Panel (edit mode and monitor mode)there are options to
select whether or not to show the following items on the map display:
(Figure 169)
Floorplan
Heatmap
Performance Plan
Arrays
IAP Info
Stations
Rogues
Map Scale
See Map Layers Panel on page 286 for a detailed discussion of the Map
Layers panel.
Array Management Panel (monitor mode only)allows you to perform
the following operations on the selected Arrays:
Refresh
Reboot
Pull Diagnostic Logs
Packet Capture
Configure allows changes to Network Settings, IAP Settings,
Channel and Band Autoconfigure, and enabling Application Control.
Quick Config allows some preset configurations to be applied.
Power allows you to perform Power On, Power Off, and Power Cycle
(power off, then on again).
Management System
254 WorkingwithMaps
More offers Add to Group and Delete operations, and allows access
to the Arrays WMI.
See Managing Arrays Within Maps on page 272 for a detailed
discussion of the Map Layers panel.
Zoom/Move mapYou may perform operations which change your
view of the map, such as zooming in and dragging the map to view
different regions. See Zooming or Moving the Map on page 275.
Migrating Maps from Earlier Releases
When you upgrade your XMS server, any maps that you have already created are
automatically migrated to new maps that are compatible with the current XMS
release. They are immediately available for use with the new software. Migrated
maps will be listed in the Map List under the same names that they previously
had.
Note that the old map information is kept in the XMS database. If you should
wish to revert to an older release of the server, the old-style maps will still be
available. If you have maps that are from a release prior to 6.0, please call
Customer Support.
Before you begin using a migrated map be sure to perform these steps so that the
map will accurately represent your environment:
Setting the Map Scale and North Direction on page 258
Environment Settings
Preparing Background Images for New Maps
You will typically want to present maps with a background image such as a floor
plan or a site layout of buildings, a geographic area, a functional domain within
your corporation, or any combination of map designs whichever suits your
needs.
XMS will accept most graphic file formats for your background images, though
we recommend using either GIF, PNG, or JPG (these formats are the most suitable
for online use). In particular, whenever possible, optimize your image files and
Management System
WorkingwithMaps 255
try to keep the file size between 50KB and 100KB. Files in this size range will load
into the client quickly, give reasonable image resolution, and will perform well
when zooming in.
Preferred Image Formats
GIF (Graphics Interchange Format)
This is the file format most commonly used to display indexed-color
graphics and images in HTML documents over the Web and other online
services. Simple graphics (for example, floor plans) with or without spot
colors are considered most suitable for the GIF file format, which is
designed to minimize the image file size and electronic transfer time.
PNG (Portable Network Graphics)
This format is an alternative to the GIF format but supports 24-bit images
with no loss compression and produces background transparency
without jagged edges. However, some older Web browsers do not
support this format.
JPEG (Joint Photographic Experts Group)
This format is commonly used to display photographs and other
continuous-tone images. Unlike GIF images, the JPEG format retains all
color information in an RGB graphic, but compresses the file size by
selectively discarding data without serious degradation to the quality of
the original image.
Physical Size
The physical size of the image is not critical because XMS scales the image
automatically. However, the more scaling that is required the greater the loss in
quality. We recommend a physical size of between 10 inches and 14 inches wide,
while maintaining the aspect ratio of the original image (when scaled, the vertical
axis will retain the correct proportion with the horizontal axis).
Resolution
The preferred resolution for your map background images is 72 dpi (standard for
online viewing). A higher resolution will generate a smoother image, but the file
size will be increased relative to the resolution you choose.
Management System
256 WorkingwithMaps
Adding a New Map
XMS allows you to add maps. Existing maps are displayed in the Maps list. Note
that the currently selected map is highlighted in orange.
Figure 174. Maps List
To add a new map, use the following procedure:
1. The background image file for your map should be optimized for the
smallest size possible. For more information about creating background
images, go to Preparing Background Images for New Maps on
page 254.
2. Click the Add Map button above the Maps List. (You do not need to
be in edit mode to add a map. XMS will automatically switch you to edit
mode once you click OK at the end of the Add New Map dialog.) The
Add New Map window is displayed.
Figure 175. Add New Map Window
3. Enter the Name for the new map.
Management System
WorkingwithMaps 257
4. Select the desired Display Units (feet or meters).
5. Environment settings customize your map for the type of construction in
the area represented by the map. XMS uses these values to determine the
degree of RF signal attenuation at your site. This increases the accuracy of
RF heat map contours. See the discussion of Planning your Installation -
General Deployment Considerations in Chapter 2 of the Xirrus Wi-Fi
Array Users Guide.
Select the typical Environment Type for your type of construction, for
example, Office (Cubicles), Office (Walled), School, or Warehouse.
6. Now, use Environment Adjustment to tune the environment settings for
the area included in the map. To set the adjustment properly, you should
take a few data points and compare them to the values on the heat map
without any adjustment. If the heat map shows -75dB at a particular spot
but your reading is -70dB, then you should set an adjustment of +5dB.
Likewise, if the map shows -50dB, but your measurement is -55dB, then
set an adjustment of -5dB.
7. Select the desired Parent Map from the drop-down list. The Maps List has
a tree structure that allows you to organize related maps. If you want this
map to be at the top level, select None.
8. Under Floor Plan image, click the Choose File button and browse to
select the image file. Note that the file should be located on your file
system (accessible from the computer where you are running the XMS
client). Click Upload.
9. Click OK to create the new map. If you were not already in edit mode,
XMS will switch you to edit mode automatically once you click OK.
10. The new map will be displayed. Prompting messages will walk you
through a series of additional steps to prepare the map for use.
Management System
258 WorkingwithMaps
Figure 176. New Map (showing prompt for scaling the map)
11. You may modify the map later. Click the Map Settings button on the
Edit Mode Toolbar. You may change the Environment Type and
Adjustment, Display Units, or even the Name.
You can now start to build your map by performing these steps, as the prompts
from XMS direct you.
Setting the Map Scale and North Direction on page 258
Adding Arrays to Maps on page 261
To work with the Arrays that you have placed on the map, see Managing Arrays
Within Maps on page 272.
Setting the Map Scale and North Direction
It is important to set the scale of each map in order for the RF heat map contours
to display accurately and for location information to be as precise as possible.
You should also adjust the orientation of North on your map. Some Arrays (XR
models) contain hardware capable of sensing their orientation and are
automatically placed on the map with the correct orientation. This feature
requires North to be set correctly on the map.
A B
Management System
WorkingwithMaps 259
It is very easy to set the scale. Before you start, measure the actual length of a wall
or other feature represented on the map. The longer the object being measured is,
the more accurate the scale will be.
Figure 177. Calibrating the Map Scale
1. Measure a wall or other feature that is represented accurately on the map.
Figure 177 shows both ends (A and B) of a wall being measured.
2. Click the Scale Map button. The mouse pointer will change to a
cross-hair tool in the next step.
3. On the map, move the cursor to one end of the wall or other feature that
you measured (A) and click the mouse. Now click at the other end of the
feature (B). A line will be drawn between the endpoints.
The Scale dialog box appears.
Management System
260 WorkingwithMaps
Figure 178. Edit Map Scale
Click and drag N until
it points to the direction
of North at your site.
4. Enter the measured length of the wall. Click OK.
5. Now XMS prompts you to set North on the map.
Figure 179. XMS Prompts You to Set North on the Map
6. Determine the direction of north at the site represented by the floor map.
Click and drag the N symbol on the map until it points in that
direction.
XMS will now prompt you to add Arrays to the map.
Management System
WorkingwithMaps 261
Adding Arrays to Maps
After you create a map and set its scale and set its north, the next step is to add
Arrays to the map, locating them to match their physical locations as closely as
possible. Each Array may only belong to one map at a time.
The procedure below describes how to add an Array to the map, move it, or
delete it.
To add an Array to the map, use the following procedure.
1. Click the Add Arrays button. XMS displays the Select Arrays list.
2. Check the desired Arrays in the Select Arrays list as shown in Figure 180.
If an Array already belongs to another map, it will not be shown on this
list. If you need to add such an Array to this map, you will need to
explicitly delete it from its current map first.
3. Click to select Arrays from the list.
Figure 180. Adding Arrays to a Map
4. Click the OK button when done.
The Arrays will appear on the map, and XMS prompts you to orient the
Arrays. You must rotate each Array on the map to match the actual
orientation of its monitor radio. This is critical for accurately calculating
Management System
262 WorkingwithMaps
and displaying locations of stations and rogues. This also allows the heat
contours to be correctly displayed on the map.
The red line on each Array indicates its orientation. For XR Array models,
this line shows the orientation of radio iap1. For XN and XS models, this
line shows the orientation of radio abg(n)2. Note that XMS may
automatically determine the orientation of XR models with respect to the
map. In this case you do not need to explicitly orient them. If the
orientation is inaccurate or the Array does not support this feature, you
should manually adjust the Array to correctly indicate the direction of the
monitor radio.
Figure 181. Arrays Added to Map
Click and drag
red dot
5. Click an Array to select it. A large red dot appears outside the Array,
indicating its orientation. Drag the red dot to the desired angle.
Figure 182. Orienting an Array
6. Move the Arrays to the proper location on the map. Click each Array and
drag it to the desired position.
Management System
WorkingwithMaps 263
7. To remove one or more Arrays from the current map, select them and
click the Remove Arrays button. You will be ask to verify the
deletions. This will remove Arrays from the map without deleting them
from the XMS database.
8. Remember to click the Save Map button to save your work.
Saving a Map
Always remember to save your map after making changes, since some map
features may not be up to date until you save the map.
To save a map after making changes, click the Save Map button. Saving
your map makes it available to all users of the XMS server.
XMS will prompt you to save the map before it will allow you to switch to another
web client page.
Management System
264 WorkingwithMaps
Viewing Array, Station, or Rogue Details
If you hover the mouse over an item on the map (Array, station, or rogue), XMS
will show the hostname of the device and its IP address (or MAC address for
rogue devices). To see additional information about an Array, double-click it
(single click a station or rogue). The details shown differ according to the type of
device.
Array Details
Double-clicking on an Array allows you to select from three tabs showing general
Array Info, Station Count, or Station Throughput. (Figure 183) This is an
abbreviated presentation of the same information that is shown on the Array
Details page that you reach when you click on an entry on the Arrays page. In
fact, you can go to that page by clicking the Visit Array Details link on the Info
tab. For a description of any of the information presented on these tabs, please see
Array Details on page 67.
Figure 183. Map Array Details
Management System
WorkingwithMaps 265
Station Details
Clicking on a station allows you to select from two tabs showing general Info or
Throughput. (Figure 184) This is an abbreviated presentation of the same
information that is shown on the Station Details page that you reach when you
click on an entry on the Stations page. For a description of the information
presented on these tabs, please see Stations on page 84.
Figure 184. Map Station Details
Management System
266 WorkingwithMaps
Rogue Details
Clicking on a rogue shows general Info about the rogue. (Figure 185) This is an
abbreviated presentation of the same information that is shown on the Rogue
Details page that you reach when you click on an entry on the Rogues page. For a
description of the information presented, please see The Rogues List on
page 90.
Figure 185. Map Rogue Details
Management System
WorkingwithMaps 267
Locating Devices
Located Station
The XMS Location feature leverages the RF capability of the wireless Array to
determine the position of a device to within a few meters and display it on the
map. With this capability, you can track stations or rogues using your existing
wireless infrastructure. XMS Location is available for stations that are associated
to an Array that is a member of a map. For accuracy, this feature requires at least
three Arrays, and the station or rogue should be located inside the region formed
by the Arrays.
Figure 186. Using the Location Feature
The location feature is described in the following sections:
Understanding Locationing
Preparing to Use XMS Location
Using XMS Location
Management System
268 WorkingwithMaps
Understanding Locationing
-60dB
-70dB
-85dB
Intersection of
RSSI contours
Figure 187. Determining Position
XMS uses a technique called trilateration based on received signal strength to
determine the location of stations or rogues. When you request the location of
stations, each Array that can hear a stations signal reports back, giving the
received signal strength. The signal strength indicates the approximate distance of
each station from the Array. A simplified representation of this is illustrated in
Figure 187, showing the RF contour of the observed signal strength as a circle
around the Array. Each circle shows possible locations of a station, based on that
Arrays signal strength observation. In the diagram, if there were only two Arrays
reporting, the circles would intersect at two points, giving two possible locations
for that station. When you add additional Array observations, the intersection of
the circles defines the stations most likely location. Actually, XMS has much more
information than a simple radius (circle) to work with, due to the advanced
design of the WiFi Array. The Arrays multiple directional radios also give
information on the direction of the station. Rather than modeling the location of
the station as a circle, the RF contour map is used. This map incorporates
Management System
WorkingwithMaps 269
directional antenna coverage on a per radio basis, and readings are enhanced by
means of inter-Array correction and take RF attenuation due to building
construction into account.
Preparing to Use XMS Location
You must complete the following steps before locating a device to get the best
results.
Planning XMS is able to locate a device most accurately when Arrays
are located around the perimeter of the area to be monitored, as shown in
Figure 186 on page 267. This is in contrast to placement of Arrays for
greatest Wi-Fi coverage, where we recommend that you place Arrays
away from exterior walls.
Adding a New Map Create an XMS map, using the most accurate
graphic representation possible.
Environment Settings Set this according to the type of construction at
your deployment site.
Setting the Map Scale and North Direction It is very important to set
the scale accurately, as the placement of a located device depends
critically on the scale of the map.
Adding Arrays to Maps As you place your Arrays on the map, be
certain to get their locations as precise as possible. XMS will only locate
stations that are associated to an Array that is a member of a map. The
orientation of the Arrays must also be as accurate as possible.
Management System
270 WorkingwithMaps
Using XMS Location
There are two ways to use the Location feature:
locate one specific station or rogue
display all stations and/or rogues
Locate one specific station or rogue
The XMS location algorithm will locate a selected station that is associated to an
Array on a map or a selected rogue that has been detected by an Array on a map.
1. Go to the Monitor > Stations window or the Monitor > Rogues window
in the web client.
2. Select only one station or rogue that you wish to locate. Click the Locate
button above the list.
3. XMS determines which map contains the Array to which the station is
associated (for a rogue, it finds a map that has an Array that detected the
rogue). That map window will be displayed, and the location of the
station or rogue is displayed. See Figure 186 on page 267. You may click
the station or rogue to see detailed information about it, as described in
Viewing Array, Station, or Rogue Details on page 264.
4. If the associated Array is not a member of any map, an error message will
inform you of this problem. You must add the Array to a map in order to
locate the stations that are associated to it.
Only one station or rogue location may be displayed at a time using this method.
Display all stations and/or rogues
The XMS location algorithm will locate all stations and/or all rogues on a map.
This method uses the Map Options panel.
1. Open the Map Options panel. See Map Options Panel on page 278.
2. To display stations, see Station Location on page 284.
3. To display rogues, see Rogue Location on page 283.
Management System
WorkingwithMaps 271
Deleting a Map
If you delete a map, the map is permanently removed from the database. Make
sure you want to permanently delete the map before doing so.
1. Select the map that you want to delete. Click the Delete Map button
above the Maps List. You do not need to be in edit mode to delete a map.
XMS will ask you to verify that you wish to delete the map.
If the selected map has any child maps, they will also be deleted.
Management System
272 WorkingwithMaps
Managing Arrays Within Maps
Click to Show or Hide Panel Array Management Panel
The map offers management functions for the Arrays shown on the map. These
are the same actions that may be performed from the Arrays (Configure)
window. Use the following procedure to manage Arrays from the map.
1. The map must be in Monitor Mode to perform Array management. Click
the Monitor Mode button if necessary to switch to this mode. See Map
Modes of Operation and User Privileges on page 251.
2. Select the Arrays that you wish to manage. You may use Ctrl + click to
select multiple Arrays.
3. Click the tab as shown in Figure 188 to display the Array
Management Panel, which lists all of the available Array
operations.
Figure 188. Array Management Panel
4. Select the desired operation from the Array Management Panel. The
results of the operation will be displayed. Some operations may take you
to a different web client page so that you may enter additional
information. For example, if you select Configure > IAP Settings..., you
will be taken to the Configure Wireless Settings page to complete the
Management System
WorkingwithMaps 273
operation. In this example, the new page will list all IAPs that belong to
the Arrays that you selected on the map.
The Array operations are summarized below. Please see The Configure Arrays
Toolbar on page 107 for detailed usage information.
Refresh this option refreshes discovery on the selected Arrays.
Reboot this option reboots the selected Arrays. You will be asked to
confirm the operation.
Pull Diagnostic Logs this option initiates a task that instructs the
selected Arrays to create a diagnostic log file. When the diagnostic log is
complete, a link will appear. Click it to download the requested
diagnostic results as a zip file.
Pull config this option pulls configuration files from the selected
Arrays, containing each Arrays current configuration. When the files are
available, a link will appear. Click it to download the requested files as a
zip file.
Packet Capture this option initiates packet capture on one or more
selected Arrays. See About Packet Capture on page 110.
Configure select an option from this drop-down list to configure the
selected Arrays.
You may modify Network Settings as described in Configure
Network Settings on page 145.
You may modify IAP Settings as described in Configure Wireless
Settings on page 141.
The Auto Configure Channels option computes the best channel
assignments for the selected Arrays in the local RF environment. See
RF Spectrum Management (Auto Channel Configuration) on
page 534. The map is actually the best place to perform an auto
channel. Since the map has information locating where the Arrays are
in relationship to each other, auto channel is performed on the Arrays
in the correct order to yield the best results. The options for auto
channel are described in Channel Configuration on page 284.
Management System
274 WorkingwithMaps
Auto Band configuration is the recommended method for assigning
bands to the abgn IAPs. It runs only on command, assigning IAPs to
the 2.4GHz or 5GHz band when you click this link. The Array uses its
radios to listen for other APs on the same channel, and it assigns
bands based on where it finds the least interference. Auto band
assigns as many IAPs to the 5 GHz band as possible when there are
other Arrays within earshot. It does this by determining how many
Arrays are in range and then picking the number of radios to place in
the 2.4 GHz band. Auto band runs separately from auto channel
configuration. If the band is changed for an IAP, associated stations
will be disconnected and will then reconnect.
Enable/Disable Application Controlthis feature analyzes the
application usage on your Array. Use these links to turn this feature
on or off. See Application ControlOverview on page 104 for
more information. Application Control is only available on an Array
if its license supports this feature.
Quick Configthis offers predefined configuration options such as
Classroom and High-Density that capture best practices from years of
field experience. If one of the options in the drop-down list is appropriate
to your deployment, select it. For example, the High-Density option uses
best practices to configure the Array for high density settings such as
lecture halls, convention centers, stadiums, etc.
Power select an option from this drop-down list to control power on
the selected Arrays. Actually, these commands are implemented by
controlling the Power over Gigabit Ethernet (PoGE) injector that powers
each target Array. These functions may only be applied to Arrays that are
powered by managed PoGE injectors, and that already have mappings
configured as described in Managing PoGE injectors with XMS on
page 127. You may choose to Power On or Power Off the selected Arrays.
The Power Cycle option will turn power off and back on again, thus
rebooting the Array.
More Choose the Add to Group option to add the selected Arrays to a
group. A dialog box allows you to select an existing group or Create a
new group. Choose Array WMI to open a WMI session with the Array in
Management System
WorkingwithMaps 275
a new browser window. Or choose the Delete option from the More
drop-down list to delete the selected Arrays from the XMS database.
Custom Any Custom Actions that you have created will appear in this
drop-down list. Click on the desired action to apply it to the selected
Arrays. See Create Custom Actions on page 588 for more information.
Zooming or Moving the Map
Move left, right, up, down
Zoom to Fit
North indicator
Zoom slider
Scale
The zoom and move controls (Figure 189) are located at the lower left of the map
window.
Figure 189. Map Zoom and Move Controls
Moving the Map
There are two ways to move the map:
Click the arrow controls shown in Figure 189 to move the map left, right,
up, or down.
Simply use the mouse to drag the map in the desired direction.
Zooming the Map
There are three ways to zoom the map:
Management System
276 WorkingwithMaps
Click and drag the zoom slider shown in Figure 189 to zoom in or out.
Use the mouse wheel to expand or shrink map size.
Click the Zoom to Fit square shown in Figure 189 to resize the map so
that the entire floorplan image fits in the current browser window.
The current scale of the map is indicated below the zoom slider.
Edit Mode Toolbar
Save Map
Map Settings
Add Arrays
Redo
Undo
Scale Map
Remove Arrays
This toolbar appears above the map when you click the Edit Mode button to
switch to Edit Mode, as described in Map Modes of Operation and User
Privileges on page 251.
Figure 190. Map Edit Mode Toolbar
The following buttons are available, from left to right:
Save Map
Click to save changes to a map, as described in Saving a Map on
page 263.
Edit Map Settings
Click here to change the Environment Type and Adjustment,
Display Units, or even the Name. See Adding a New Map on
page 256.
Management System
WorkingwithMaps 277
Undo
Click to undo the last change to a map, for example to undo the
removal of an Array. This button is grayed out if there is nothing to
undo.
Redo
Click to redo the undo that was just performed. This button is grayed
out if there is nothing to redo.
Add Array
Click to add Arrays to a map, as described in Adding Arrays to
Maps on page 261.
Remove Arrays
Click to remove the selected Arrays (one or more) from a map. Note
that the Arrays are only removed from the map. They are not deleted
from the database.
Scale Map
Click to set the scale of the floor plan of the map, as described in
Setting the Map Scale and North Direction on page 258.
Management System
278 WorkingwithMaps
Map Options Panel
Map List
Map Options
Map
Options Tab
Figure 191. Map Options Panel
This panel is located to the left of the map. It may be accessed from both Edit
Mode and Monitor Mode (see Map Modes of Operation and User Privileges
on page 251). Click the Map Options tab to show or hide the panel. (Figure 191)
Its options affect a number of aspects of the map display. The types of options
include:
Map Options select whether to show help pop-ups, and also summarize
the number of Arrays and stations shown on the map.
Heatmap Options select the bands displayed (2.4 GHz/5 GHz) or
channels displayed, the transparency of the heat map, and whether to
show contour lines.
Performance Plan Options specify the target usage for this plan. Select
the number of stations, the bands in use(2.4 GHz/5 GHz/both), station
device types (laptops, tablets, etc.), WiFi mode (802.11b, 802.11n 2x2, etc.),
and the application in use (Browsing, VoIP, video HD, etc.).
Floorplan Options select the transparency of the background floor map,
the size of Array icons, and how much information to display for
individual Array radios.
Management System
WorkingwithMaps 279
Rogue Location shows rogues that have been detected.
Station Location shows stations that are associated to Arrays.
Channel Configuration performs an automated channel allocation
procedure.
Map Options
See Figure 191.
Map Informationshows the name of the map and the time it was last
refreshed. If you wish to update the map immediately, click the refresh
link. This section also lists the number of Arrays, IAPs, and stations
included on this map.
Check the Show Help Popups box if you wish to see the helpful, red
arrows that walk you step-by-step through setting up a new map (set
north, scale, add Arrays, etc.).
Heatmap Options
Figure 192. Heatmap Options
Channelsshows the Bands or Channels included on the map. If you
wish to filter the heat map to include signal strength for only a selected
band or only particular channels, click the change link.

If you have made any changes to the map, its is a good idea to save them
using Save Map on page 276 before clicking the refresh link.
Management System
280 WorkingwithMaps
Figure 193. Map Channel Selection
You may click the By Band radio button to select the 2.4GHz or 5GHz
band. By default, both of these are shown on the map.
To show only selected channels, click the By Channel radio button and
check off the desired channels. (Figure 193)
The Opacity slider adjusts the transparency of the heat map colors. Slide
it to the left to make the colors more transparent, or to the right to make
them more opaque (darker). To restore the map to the default level of
color display, click the default link.
Check the Show Contour Lines box if you wish to see lines separating the
regions of different signal strength gradation on the heat map.
Management System
WorkingwithMaps 281
Performance Plan Options
Expected throughput is computed using the following characteristics. Note that
observed performance of the network and current settings on Array IAPs are also
used as inputs to the predictive analysis.
Figure 194. Performance Plan Options
Stationsnumber of stations on the map. This starts out as the actual
number of stations currently associated to Arrays on the map (or one, if
there are no stations). To increase the number of stations to observe the
predicted decrease in performance or to experiment with how far you
should decrease the station count to improve performance, click the
change link. To restore the number of stations to the default value, click
the default link. The maximum number of stations that you can enter is
240 times the number of IAPs on the map.
Device Typeselect the type of device that you wish to analyze, e.g.,
smartphone, tablet, business computer. Note that devices have preset
parameters. For example, the smart phones band is set to 2.4GHz. If you
change any of these preset values, the device type automatically changes
to Custom.
Bandsselect the wireless band that you wish to analyze, 2.4 GHz, 5
GHz, or both.
Management System
282 WorkingwithMaps
WiFi Modeselect the Wi-Fi mode that you wish to analyze, e.g.,
802.11b. Then select the type of device that you wish to analyze, e.g.,
802.11n (3x3 bonded), etc. Your choices will vary based on the Bands
setting. For example, 802.11b and 802.11g will not be offered if you
selected 5 GHz only. For 802.11n, select the number of antennas assumed
for all of the IAPs (1x1, 2x2, or 3x3). Bonded and unbonded channel
choices are offered.
Applicationselect the type of usage that you wish to model for this
plan. The various options are listed together with the assumed load that
they put on the network. For example, VoIP is 0.5 Mbps, while file
transfer is 10 Mbps.
Opacitythis slider simply adjusts the transparency of the plan colors.
Slide it to the left to make the colors more transparent, or to the right to
make them more opaque (darker). To restore the plan to the default level
of color display, click the default link.
Floorplan Options
Figure 195. Map Floorplan Options
The Opacity slider adjusts the transparency of the background floorplan
image. Slide it to the left to make the image more transparent, or to the
right to make it more opaque (darker). To restore the map to the default
display, click the default link.
The Array Size slider adjusts the display size of the Array icons. To
restore Arrays to the default display size, click the default link.
Management System
WorkingwithMaps 283
Check the IAP Info boxes to customize the information shown if you
enable display of the IAP Info layer (see IAP Info on page 287). You
may show or hide display of IAP Name, Station Count, and Channel on
the radios.
Rogue Location
Figure 196. Map Rogue Location Options
Click Locate Rogues to show rogues that have been detected by Arrays
on this map. Rogues will not be shown until you click this button. XMS
will also enable the Rogues in order to display rogues on the map. Up to
100 rogues will be shown.
Click the Filter link if you wish to display only rogues that meet certain
criteria. You may filter by Classification, Type, or both.
The Classification Filter allows you to select rogues that match the
selected classifications: Unclassified, Unknown, Known, Approved, or
Blocked. See Rogues on page 89 for more information.
The Type Filter allows you to select rogues that have the selected types of
wireless network: Ad Hoc, Infrastructure, or Both.
Management System
284 WorkingwithMaps
Station Location
Figure 197. Map Station Location Options
Click Locate Stations to show stations that are associated to Arrays on
this map. Stations will not be shown until you click this button. XMS will
also enable the Stations in order to display stations on the map. Up to 100
stations will be shown.
Click the Filter link if you wish to display only stations that meet certain
criteria. You may filter by Type. Select as many of the following as you
wish: Notebook, Phone, Player, Game, or Tablet.
Channel Configuration
Figure 198. Auto Channel Configuration
Click Channel ConfigurationAutomatic channel configuration is the
recommended method for channel allocation, and the map is the best
place to perform this process. Since the map has information locating
where the Arrays are in relationship to each other, auto channel is
performed on all of the Arrays on the map (regardless of which are

If the monitor radios of some Arrays on this map are set to Timeshare mode,
rogue location information from these Arrays may not be sufficient to
identify and locate rogues. See RF Monitor on page 532.
Management System
WorkingwithMaps 285
selected) in the correct order to yield the best results. Each Array
determines the best channel allocation settings for each enabled IAP and
selects the channel automatically, based on changes in the environment. A
dialog allows you to specify the following options. (Figure 199)
Negotiate: negotiate air-time with other Arrays before performing a
full scan. Negotiating is slower, but if multiple Arrays are configuring
channels at the same time the Negotiate option ensures that multiple
Arrays don't select the same channels. Turning off the Negotiate
option allows the Auto Configure button to manually perform auto
channel without waiting, and may be used when you know that no
other nearby Arrays are configuring their channels.
Full Scan: perform a full traffic scan on all channels on all IAPs to
determine the best channel allocation.
Non-Radar: give preference to channels without radar-detect. See
table in Procedure for Configuring Global 802.11an IAP Settings
on page 522.
Include WDS: automatically assign 5GHz to WDS client links.
Figure 199. Map Auto Channel Options
Management System
286 WorkingwithMaps
Map Layers Panel
Map Layers Tab
Map Layers
Figure 200. Map Layers Panel
This panel is located to the right of the map. It may be accessed from both Edit
Mode and Monitor Mode (see Map Modes of Operation and User Privileges
on page 251). Click the Map Layers tab to show or hide the panel. (Figure 200) Its
options enable or disable the display of a number of types of information on the
map. The types of layers include:
Floorplan
Heatmap
Performance Plan
Arrays
IAP Info
Stations
Rogues
Map Scale
Management System
WorkingwithMaps 287
Floorplan
When enabled, this layer shows your floorplan image in the background. Note
that you can modify the transparency of this image. See Floorplan Options on
page 282.
Heatmap
When enabled, this layer indicates RF signal strength with a color heat map. Note
that you can modify the transparency of the color display and enable or disable
the display of contour lines. See Heatmap Options on page 279.
Performance Plan
When enabled, this layer shows predicted throughput over the map based on the
type of usage you select.
Arrays
When enabled, this layer shows the location of Arrays on the map.
IAP Info
IAP Name
Station Count
Channel(s)
Enabled radios are
shown in green
Disabled radios are
shown in gray
Figure 201. IAP Info Layer (XR-1000 shown)
Management System
288 WorkingwithMaps
When enabled, this layer shows each Arrays radios on the map. Active radios are
green, disabled radios are gray, and radio failure is shown in red. (Figure 201) By
default, each radio is labeled with its name, its station count (the number of
stations associated to it), and the channel that it is using. Note that IEEE 802.11n
radios may use a bonded pair of channels, and may show two channel numbers.
You may customize the information shown. See IAP Info Floorplan Options
on page 282.
Stations
This enables and disables the display of stations on the map. After you enable this
layer, you must take one more action to display stations:
To view all stations, you must also use the Locate Stations button once so
that XMS will locate all the stations on the map. If you have selected any
Filters, then only the stations meeting the criteria will be shown. See
Display all stations and/or rogues on page 270.
To view only one selected station, you must also select that station on the
Monitor > Stations window, and use the Locate button. See Locate one
specific station or rogue on page 270.
Rogues
This enables and disables the display of rogues on the map. After you enable this
layer, you must take one more action to display rogues:
To view all rogues, you must also use the Locate Rogues button once so
that XMS will locate all the rogues on the map. If you have selected any
Filters, then only the rogues meeting the criteria will be shown. See
Display all stations and/or rogues on page 270.
To view only one selected rogue, you must also select that rogue on the
Monitor > Rogues window, and use the Locate button. See Locate one
specific station or rogue on page 270.
Map Scale
If you wish to show the map scale, you must enable this.
Management System
ManagingReports 289
Managing Reports
XMS generates performance reports about the network, all wireless Arrays within
the network, the individual IAPs (Integrated Access Points) contained within
each Array, and wireless data (channels, throughput, signal strength, etc.).
Selection criteria allow you to focus your reports on just the data that is of interest.
Click the Reports link in the main menu at the top of the page to access the
reports pages.
This chapter provides instructions for managing and reviewing these reports via
the web client. Section headings for this chapter include:
About Reports on page 289
Application Control Reports on page 309
Traffic Reports on page 322
Station Reports on page 349
Array Reports on page 378
RF Reports on page 383
Security Reports on page 386
About Reports
Reports provide information about the content, performance and usage of your
network(s) and Arrays. Most reports display a combination of graphs and text-
based information organized in tabular form.
There are three main reports pages:
View Reports The web clients Reports button opens to the View
Reports page, listing all of the reports you have already created and
allowing you to view or run these reports.
Create Report Click this link to list all the types of reports that you can
create. Click on a report, and a form allows you to enter all the selection
criteria for your report. You may then save the report setup, and run it
now or schedule it for later.
Management System
290 ManagingReports
Customize Report Header Click this link to customize the appearance
of reports by changing the logo at the top of the report.
Selection Criteria differ according to the type of report, but most reports use
similar criteria such as defining the group of Arrays and time period to consider
for the report.
Reports are not to be confused with events and alarms, which provide alerts when
the system encounters problems. For information about events and alarms, go to
Alarms on page 97 and Events on page 100.
Sample reports shown in this chapter may show multiple Arrays managed by
XMS. In some cases you may see examples where only one Array is under
management. The results are the same regardless of how many Arrays are being
addressed.
Topics for this section include:
View Reports on page 291
Viewing a Report on page 293
Create Report on page 297
Selection Criteria on page 304
Customize Report Header on page 308

The data in most reports is delayed by 30 minutes. Exceptions are Array
Inventory, Array Availability, Station Assurance, and IDS Events, which
show current data. If a report is based on delayed data, it will state that fact.
Management System
ManagingReports 291
View Reports
Report Title Run/ Edit/ Delete
Reports View Archive
View Existing Report Scheduled to Run?
To access reports, click the Reports button at the top of the web client window.
The initial window always defaults to the View Reports page. If you are on one of
the other Reports pages, click the View Reports link to return to this page.
This page lists all of the reports that you have already created using the Create
Report link. You may view latest or archived report results, run the report, or edit
report parameters from this page. The list of reports may be sorted by clicking on
the column header for the Report, Last Run, or Scheduled columns. Click again
to reverse the sort order.
Figure 202. View Reports Window
The following information is displayed for each report:
Report this is the Name that you assigned when you created the report.
To delete a report, select the checkbox to the left of it, then click the Delete
button at the top left. Select as many reports as you wish for deletion. You
may click the checkbox in the header row to select or deselect all reports.
Description this is a general description of this type of report.
Management System
292 ManagingReports
Last Run this column lists the time that the report was most recently
run, if any. Click the View link to see that report. For a description of the
options available, see Viewing a Report on page 293).
Scheduled true indicates that the report has been scheduled to run at
some time in the future.
Figure 203. Actions for Reports
Actions (Figure 203) this column allows you run or edit this report, or
see all of its saved runs.
Click Run Now to start a report immediately. The Report Queue page
will be displayed, showing the status of the report. You may go to other
web client pages to perform tasks while the report is generated.
Generating reports may take some time on large Array networks.
Click Edit to change the selection criteria for the report. This displays the
same fields you entered when you originally used Create Report to create
the report, as described in Selection Criteria on page 304. You may
change any field, including the reports Name. Note that this report will
replace the edited report, even if you change the name (i.e., you will not
have entries listed on the View Reports page for the old name and the
edited name the Archive entries that were created with the old name
will still be there under the new name).
Click Archive to list all of the saved copies of this report. (Figure 204)
Each time a report is run, it is automatically saved with a date/time
stamp. The archive lists these reports in the order that they were run.
Click the desired format for a report: html, Excel, pdf, or csv. You may
choose to save the resulting file to your file system, or display it
immediately (the appropriate software is automatically used). For
Management System
ManagingReports 293
example, a CSV file is displayed by Excel. See Viewing a Report on
page 293 for more details. You may click the Delete link in front of a
report if you wish to remove it.
Figure 204. Archived Reports List
Viewing a Report
Figure 205. Viewing a Report
You may select a report for viewing from two places on the View Reports page:
Click the desired reports View link in the Last Run column. (Figure 205)
Management System
294 ManagingReports
Click the desired reports Archive link in the Actions column to choose
the report with the desired time stamp. Click the html link to view the
report as shown in Figure 204.
When you create and run a report from the Create Report page, it is automatically
displayed when it is complete. To view the report again at a later time, go to the
View Reports page to view the report in one of the two ways just described.
The selected report is displayed in the web client. Some types of report only have
text (Figure 205), while others may include charts (Figure 206). Information
included in the report is determined by the Selection Criteria that you set up
when creating the report.
Figure 206. Report Including Charts
If the report had a time span setting, then the Time Span that you selected is
shown underneath the title. It also identifies the data collection Sample Period
used for the report. The sample period is automatically determined based on the
Management System
ManagingReports 295
Time Span. For long time spans, such as a year, the period will be longer (e.g., one
day). Short reporting periods, such as an hour, will be more granular and may
have a period of 5 minutes.
The report may only be viewed as presented. You cannot sort columns or resize
their width. Note that for very long reports, the HTML version is truncated to
three pages so it will be able to be loaded in a browser. To view the full report,
download it in PDF format as described below.
To download or view the report in a format other than HTML, select pdf, xls, or
csv from the top of the page. The File Download dialog box will ask whether you
wish to Open or Save the file. Select Save to specify where to save the file in your
file system. Select Open to view the file using the appropriate software. By
default, Acrobat is used to open PDFs and Excel is used for .csv and .xls files
(unless you have changed the settings on your computer to open these files with a
different application).
To print the report, we recommend that you download it as a PDF and print it
from Acrobat.
To email the report, click the Email Report button at the top. (Figure 207) (Note
that this button may not be displayed if you have not specified a mail server that
XMS can use to send emails, as described in Email Settings on page 600.)
Management System
296 ManagingReports
Figure 207. Emailing a Report
The web client will prompt you to enter the email address, then click OK. A
message will appear near the top of the page when the email has been
successfully sent. The email displays the report in the same format shown on the
web client page (i.e., HTML format), and there will be three attachments, one for
each other format (PDF, .xls, .csv). Be aware that for large reports, the email size
may be quite large.
Management System
ManagingReports 297
Create Report
To create a new report, click the Reports button at the top of the web client
window, then click the Create Report link.
Figure 208. List of Create Report Types
Management System
298 ManagingReports
This page lists all of the report types offered by the web client. Click the desired
report type, and the Create Report page for the chosen report type is displayed.
(Figure 209)
Figure 209. Create Report Page
The Create Report page sets up the name and parameters for a report, especially
the selection criteria use to filter the data included in the report. You may choose
Management System
ManagingReports 299
to run the report immediately after creating it, schedule it to run later at a specific
time, or just save it without running it. Regardless, the report setup is always
saved to the View Reports list, where you may run it or view previous results at
any time. You may also choose to email the report after it runs.
The following topics are discussed for the Create Reports page:
Types of Reports on page 299
To create a report on page 301
Report Queue on page 303
Types of Reports
There are five categories of reports, listed below. Each report type may be filtered
to select only the desired data. For example, you may select only certain Arrays or
Array groups to include in the report. For details, see Selection Criteria on
page 304. The available selection criteria vary for each report. They are listed in
the detailed description of each report.
Application Control Reports
These reports display wireless traffic statistics for selected applications or
categories of applications.
Application Category Trafficshows Tx and Rx averages or peak total
wireless traffic for a category of applications.
Application Trafficshows Tx and Rx averages or peak total wireless
traffic for selected applications.
Station Application Category Trafficshows the top 10 stations by
either Total, Tx or RX Application Category Traffic.
Station Application Trafficshows the top 10 stations by either Total, Tx
or RX Application Traffic.
Management System
300 ManagingReports
Traffic Reports
These reports display wireless traffic and error statistics for IAPs, Ethernet ports,
and stations.
Top Arrays by Wired Trafficshows the ten Arrays with the highest
level of wired traffic.
Top Arrays by Wireless Trafficshows the ten Arrays with the highest
level of wireless traffic (not including management traffic).
Wireless TrafficTx and Rx average or peak megabits per second.
The wireless reports include all the data from the station reports (below)
plus Wi-Fi management traffic such as beacons, probe requests, etc.
Wireless Errorstotal wireless drops and errors.
Station TrafficTx and Rx average or peak megabits per second for
traffic that flows to or from all associated stations.
Station Errorstotal station drops and errors.
Ethernet TrafficTx and Rx averages or peak total megabits per second
for the Array gigabit Ethernet ports.
Ethernet Errorstotal drops and errors for the Array gigabit Ethernet
ports.
Top Station Types by Throughputthe types of stations generating the
highest traffic demand (Tx+Rx Mbps).
Station Reports
These reports display statistics related to station counts and Array-to-Station
associations.
Stations by Wi-Fi Banda count of stations by Wi-Fi Band.
Station Counts by SSIDa pie chart and table of unique station counts
by SSID.
Station Activity Over Time Perioda list of stations that had active
sessions, along with the total time that the station was connected and
traffic usage statistics.
Station Sessionsa list of active sessions along with station information
for each.
Management System
ManagingReports 301
Station Classificationa list of stations by unique device class and type.
Station Manufacturersa list of stations by manufacturer.
Station Assurancea list of Station Assurance events, showing stations
experiencing poor connectivity.
Associated Stationsa list of stations associated to the wireless network.
Stations By ArrayArray-to-Station association counts.
Unique Station Countwireless station counts.
Array Reports
These reports display information about managed Arrays and their reliability
statistics.
Array Inventoryan inventory of Arrays.
Array Availabilitytable of Array availability statistics.
RF Reports
This report displays information about channel usage.
Channel UsageIAP counts on 2.4 GHz and 5 GHz channels.
Security Reports
This report displays information about intrusion attacks and detected rogue APs.
IDS Eventslist of intrusion attacks detected by the wireless network.
Rogue Listlist of rogue access points detected by the wireless network.
To create a report
Enter the following information to set up the report.
Name
This is a unique name that will identify this report on the View Reports
page. You may create different reports of the same report type, with
different options defined for each. Each report must have its own name.
XMS will not allow you to create a new report using a name that is
already in the View Reports list.
Management System
302 ManagingReports
Options
These settings define the selection criteria for the report. The types of
criteria shown will differ by report type. They typically select criteria
such as the Arrays and time period to be included in the report. For
details on setting up these options for the report, please see Selection
Criteria on page 304.
Schedule
You may schedule the report to be automatically run on a recurring
schedule. Click Enable Schedule to display time settings. Select one of
the following options:
HourlySelect the minutes after the hour when the report is to be run
every hour. For example, to run the report on the hour, every hour,
select 00.
DailyEnter the Time of Day when the report is to be run every day,
based on a 24-hour time notation. For example, midnight is 00:00, half
past noon is 12:30 and 4 PM is 16:00.
WeeklySelect the day of the week when the report is to be run, and
then enter the Time of Day when the report is to be run, as described
above.
MonthlySelect the day of the month when the report is to run, and then
enter the Time of Day for the run, as described above.
Email Report To
If you wish to have this report emailed to yourself or other recipients each
time it runs, enter an email address and click the Add button. You may
add multiple addresses. To remove an address from the email list, click
the X in front of the entry. The email will display the report in the same
format that is used to display it on the web client page (i.e., HTML
format), and there will also be three attachments, one for each other

You should use the Time Span option when scheduling reports,
because the Specific Date Range option will just generate the same
report over and over again.
Management System
ManagingReports 303
format (PDF, .xls, .csv). Be aware that for large reports, the email size may
be quite large.
Save Report / Save& Run
When the settings for the report are complete, click Save Report to simply
add it to the View Reports list without running it. Click Save & Run to
add it to the View Reports list and run it immediately. The Report Queue
page will be displayed, showing the status of the report. You may
navigate to another page while the report is being generated. Use the
View Reports page to view the report later on.
Report Queue
When you run a new or saved report, or when the time comes to run a scheduled
report, it is added to the Report Queue. Reports are run one at a time, in the order
in which they are added to the queue. The queue displays the status of each report
that is waiting to be run Pending or In progress.
The report queue page is displayed only when you run a new or saved report
immediately, but not when you schedule a report. On the report queue page, you
may wait for an in progress report to complete, at which time the report will
automatically be displayed. Or you may navigate away from the report queue
page to perform other tasks with the web client. In this case, you may view the
report later after it completes by using its entry on the View Reports page.

You must specify the email server that XMS will use to send the email.
Please see Email Settings on page 600.
Management System
304 ManagingReports
Figure 210. Report Queue
Selection Criteria
The web client presents you with a set of options for filtering (restricting) the data
that it includes in a report. Different selection criteria are appropriate for different
report types, thus the settings that you may specify are tailored for each type of
report. This section will describe how to use selection criteria. The detailed
description of each report type later in this chapter will list the selection criteria
that are available for that report.
Open the Create Report Page for the desired type of report as described in
Create Report on page 297. Choose your selection criteria in the Options
section. You may select no options, or one or more options. Remember that each
type of report will use its own subset of these settings. In all cases, you may select
only one entry from each drop-down list.
When you choose values for a number of different selection criteria, the report
will use only data that satisfies of all of them in other words, the report is based
on the intersection of the conditions that you set. For example, if you select a
Array Group and an IAP, the report will show results for just the selected IAP on
all Arrays in that group. Take some care so that you dont choose criteria that will
yield no results.
The following criteria are used in most report types.
Array Scope the drop-down list shows all of the profile networks and
Array groups that you have defined in XMS. Select an entry to report on
Management System
ManagingReports 305
just the Arrays that are members of the group or profile, or select All
Arrays. For more information, see Array Groups on page 114 or
Profiles on page 206.
Map the drop-down list shows all of the maps that you have defined in
XMS. Each map may have multiple Arrays located on it, and an Array
may only belong to one map. Select a map to report on just the Arrays
that are assigned to the map, or select All Maps. For more information,
see Working with Maps on page 243.
Array the drop-down list shows all of the Arrays being managed in
XMS. Select an Array to report on just that one Array, or select All Arrays.
You cannot make more than one choice from the drop-down list. If you
have selected a Group, then this list will only contain Arrays that are
members of the group.
Detail on this setting specifies how you would like to break out report
results. It is used by the Unique Station Count report. Select Total to
show the total station count only, or you may break out detailed counts
by Array Name, VLAN Name, VLAN Number, SSID, Media Type, IAP,
or Association Type. The drop-down list allows you to select one of these
parameters for detailing. For example, if you select detail on VLAN, the
chart and the table will each will show one line for each VLAN.
Display traffic by the drop-down list allows you to select Tx+Rx to
display transmit, receive, and total traffic broken out separately into three
lines, or select Total to display only the totals. Total will show two lines:
the average value of Tx+Rx, and the peak value of Tx+Rx.
Order table by the drop-down list allows you to select the column to
use for sorting results: Array Name (the default), MAC Address, IP
Address, Map, or Serial Number.
Order direction select Ascending or Descending sort order from the
drop-down list.
Table row limit select the total number of rows to display in the report
from the drop-down list: 10, 20, 50, or Show all.
Date/Time this defines the time interval covered by the report,
specified in terms of Time Span or Specific Date Range. In either case,
Management System
306 ManagingReports
the report will state the start time and end time of the period that it
covers.
Select Time Span to specify a period ending at the reports run time. For
example, if you select Last Hour, then the report will include data from
the 60 minutes prior to the time when the report runs. You may select any
entry in the drop-down list, for example Last 24 Hours or Last 30 Days.
You should use the Time Span option when scheduling reports, because
the Specific Date Range option will just generate the same report over
and over again.
Select Specific Date Range to specify a start time and end time for the
data to be included in the report. Click in the Date From field and then
click the desired starting date using the drop-down calendar. Click in the
Time From field and the Choose Time drop-down appears. Set the
desired starting time by dragging the sliders for Hour and Minute. Set
the Date to and Time to fields in the same way.
The remainder of the criteria are shown in alphabetical order.
Association select Authenticated from the drop-down list to show only
stations that have been authenticated, or select Any to show all stations.
Classification the drop-down list allows you to select whether to report
only on rogue IAPs whose classification matches your selection (select
one of Approved, Known, Unknown, Unclassified, Blocked, or Ad Hoc)
or select All to display rogues of any classification.
Device Class the drop-down list shows general classes of stations, for
example Notebook, Tablet, Phone, etc. If you are using WDS (Wireless
Distributed System) links to carry traffic between Arrays wirelessly, then
the client device class is Array.
Select a class to report on just that one class, or select All Device Classes.
You cannot make more than one choice from the drop-down list.
Device Type the drop-down list shows more detailed types of stations.
For example, if the Device Class is Notebook, then the Device Type might
be Mac or Windows. If you are using WDS, then the client type is WDS
Link.
Management System
ManagingReports 307
Select a type to report on just that one type, or select All Device Types.
You cannot make more than one choice from the drop-down list.
IDS Event Type the drop-down list allows you to select whether to
report only on intrusion detection events of the selected type (for
example, Beacon Flood or Authentication Flood) or select All IDS Event
Types to display all events.
Media Type the drop-down list shows the IAP modes that are available
on Arrays: 802.11b, 802.11g, 802.11a, 802.11n. Select a mode to report on
just data for Array IAPs operating in that mode, or select All Modes.
IAP Select an IAP if you wish to report on just data for that one IAP, or
select All IAPs. For more information, see IAPs on page 79.
SSID the drop-down list shows all of the SSIDs that you have defined
in XMS. Select an SSID to report on just data for that one SSID, or select
All SSIDs. For more information, see SSID on page 81.
Station Assurance Event Type the drop-down list allows you to select
whether to report only on station assurance events of the selected type
(for example, Authentication Failures or Error Rate) or select All Station
Assurance Event Types to display all events.
VLAN the drop-down list shows all of the VLANs that you have
defined in XMS. You may choose to display them by VLAN Number or
by VLAN Name. Select a VLAN to report on just data for that one VLAN,
or select All VLANs. For more information, see VLAN on page 409.
Management System
308 ManagingReports
Customize Report Header
This page allows you to change the appearance of the report by modifying its
header. Use this page to add your custom logo to the header.
To create a new report, click the Reports button at the top of the web client
window, then click the Customize Report Header link. The Customize Report
Header page appears. (Figure 211)
Figure 211. Customize Report Header Page
Select Default Image to use the default Xirrus logo at the top of all reports. Select
Custom Image to upload your own logo to be used at the top of all reports. Click
Choose File to browse to the desired image file. It must be one of the following
types: .bmp, .jpg, .png. Then click the Upload button. Click Save Settings when
done. Note that XMS does not impose a particular size limit on the image file, but
the Xirrus logo is approximately 200 x 50 pixels, if you wish to use it as a guide.
The currently selected image will apply to all subsequent report runs (from either
Create Report or View Reports). It will not affect any previously run reports
they will use the customization settings that were current at the time they were
run.
Management System
ManagingReports 309
Application Control Reports
Application Control reports analyze the amount of traffic generated on Arrays by
the selected applications. Each XR Array uses Deep Packet Inspection (DPI
available only on XR Arrays) to determine what applications are being used, and
how much bandwidth they are consuming. For more information, see
Application ControlOverview on page 104.
The results returned for all reports in this section are dependent on the reporting
period you specify. Application Control reports include:
Application Category Traffic
Shows Tx and Rx averages or peak total wireless traffic for a category of
applications.
Application Traffic
Shows Tx and Rx averages or peak total wireless traffic for selected
applications.
Station Application Category Traffic
Shows the ten stations with the highest wireless traffic for a category of
applications.
Station Application Traffic
Shows the ten stations with the highest wireless traffic for selected
applications.

Application Control data is only available from Arrays whose licenses

include Application Control. See About Licensing and Upgrades
on page 194.
Application Control data is available from XR Series Array models, but not
on XN Arrays. In order for an Array to produce Application Control data,
you must enable the Application Control option in the Configure menu
on the Arrays Toolbar. See The Arrays Toolbar on page 66.
Management System
310 ManagingReports
Application Category Traffic
This report provides statistical data for wireless traffic flow generated by a
selected category of applications. (Figure 212) The graph at the top of the window
displays wireless traffic for that category, summed over the selected Arrays for
the selected time range.
A table shows traffic generated by this application category on each Array. The
information displayed in this window and in the graph is dependent on the
selection criteria you specify, summarized below. Note that the report includes
only Arrays capable of generating application control data.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Category Include only traffic for the selected category of
applications, such as File Transfer or Social
Networking.
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array. If it is not an X
VLAN Include only the selected VLAN.
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 311
If you have a large network, the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Figure 212. Application Category Traffic Report
Table Details for the Application Category Traffic Report
The table portion of the report shows traffic statistics for each selected Array,
organized by the following column headers:
Management System
312 ManagingReports
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Array MAC Address
This is the Arrays MAC address.
Management IP Address
This is the Arrays IP address.
Throughput data shown in the table depends on your Selection Criteria. If you
set Display Traffic by to Tx+Rx, these columns are shown:
Average Tx (Mbps)
Shows the average traffic transmitted (in megabits per second) by the
application category for the time period you specified.
Average Rx (Mbps)
Shows the average traffic received (in megabits per second) by the
application category for the time period you specified.
Average Tx+Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the application category for the time period you specified.
If you set Display Traffic by to Total, these columns are shown:
Average Tx/Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the application category for the time period you specified.
Peak Tx/Rx (Mbps)
Shows the maximum total throughput (in megabits per second) achieved
by the application category for the time period you specified.
Management System
ManagingReports 313
Application Traffic
This report provides statistical data for wireless traffic flow generated by a
selected set of applications. (Figure 213) The graph at the top of the window
displays wireless traffic for those applications, summed over the selected Arrays
for the selected time range.
A table shows traffic generated by each application on each Array. The
information displayed in this window and in the graph is dependent on the
selection criteria you specify, summarized below. Note that the report includes
only Arrays capable of generating application control data.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Applications Include only traffic for the selected applications, for
example, Facebook and FTP.
For each desired application, first select its Category,
then select the Application and click Add. For
example, for Facebook, first select the category
Social Networking and then select Facebook from
the application list.
You may unselect an application with the Delete
button. Click Reset to delete all applications from
your selected list.
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array. If it is not an X
VLAN Include only the selected VLAN.
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Management System
314 ManagingReports
If you have a large network, the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Figure 213. Application Traffic Report
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Management System
ManagingReports 315
Table Details for the Application Traffic Report
The table portion of the report shows traffic averages or peak values for each
selected application on each selected Array, organized by the following column
headers:
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Array MAC Address
This is the Arrays MAC address.
Array IP Address
This is the Arrays IP address.
Application
This table row shows traffic for this selected application.
Throughput data shown in the table depends on your Selection Criteria. If you
set Display Traffic by to Tx+Rx, these columns are shown:
Average Tx (Mbps)
Shows the average traffic transmitted (in megabits per second) by the
application for the time period you specified.
Average Rx (Mbps)
Shows the average traffic received (in megabits per second) by the
application for the time period you specified.
Average Tx+Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the application for the time period you specified.
If you set Display Traffic by to Total, these columns are shown:
Average Tx/Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the application for the time period you specified.
Peak Tx/Rx (Mbps)
Shows the maximum total throughput (in megabits per second) achieved
by the application for the time period you specified.
Management System
316 ManagingReports
Station Application Category Traffic
This report shows the ten stations with the highest level of wireless traffic for the
selected category of applications. (Figure 214) The graph at the top of the window
displays wireless traffic for that category for those stations over the specified time
period. You may select the Arrays to consider. If no category is specified, then all
categories are included.
A table shows average traffic generated by this application category on each
station. The information displayed in this window and in the graph is dependent
on the selection criteria you specify, summarized below. Note that the report
includes only Arrays capable of generating application control data (i.e., XR Series
Arrays running ArrayOS Release 6.4 or higher). If you select other Arrays, they
will not generate any information for this report.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Category Include only traffic for the selected category of
applications, such as File Transfer or Social
Networking, or select All.
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array. If it is not an X
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 317
Figure 214. Station Application Category Traffic Report (All Categories)
Table Details for the Station Application Category Traffic Report
The table portion of the report shows average traffic statistics for each of the top
ten stations, organized by the following column headers:
Station MAC Address
This is the stations MAC address.
Station Hostname
The host name of the station. Only stations associated to Arrays that meet
your selection criteria are included.
Station Device Type/Class
The type and class of station device, e.g., Notebook/Mac. For a WDS Link
session, WDS Link/Array are shown here.
Management System
318 ManagingReports
Manufacturer
The manufacturer of the station device, e.g., Apple, Motorola, etc.
Throughput data shown in the table depends on your Selection Criteria, and
may be one of:
Average Tx (Mbps)
Shows the average traffic transmitted (in megabits per second) by the
application category for the time period you specified.
Average Rx (Mbps)
Shows the average traffic received (in megabits per second) by the
application category for the time period you specified.
Average Tx+Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the application category for the time period you specified.
Management System
ManagingReports 319
Station Application Traffic
This report shows the ten stations with the highest level of wireless traffic for the
selected applications. (Figure 215) The graph at the top of the window displays
wireless traffic for those applications for those stations over the specified time
period. You may select the Arrays to consider. If no applications are specified,
then all applications are included.
A table shows average traffic generated by each selected application on each of
the ten stations, in decreasing order of the amount of traffic. The information
displayed in this window and in the graph is dependent on the selection criteria
you specify, summarized below. Note that the report includes only Arrays
capable of generating application control data (i.e., XR Series Arrays running
ArrayOS Release 6.4 or higher). If you select other Arrays, they will not generate
any information for this report.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Applications Include only traffic for the selected applications, for
example, Facebook and FTP.
For each desired application, first select its Category,
then select the Application and click Add. For
example, for Facebook, first select the category
Social Networking and then select Facebook from
the application list.
If no applications are listed, then all applications will
be included. You may unselect an application with
the Delete button. Click Reset to delete all
applications from your selected list.
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array. If it is not an X
Management System
320 ManagingReports
Figure 215. Station Application Traffic Report (All Applications)
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Management System
ManagingReports 321
Table Details for the Station Application Traffic Report
The table portion of the report shows traffic averages for each of the top ten
stations for each of the selected applications that generated any traffic, organized
by the following column headers:
Station MAC Address
This is the stations MAC address.
Station Hostname
The host name of the station. Only stations associated to Arrays that meet
your selection criteria are included.
Station Device Type/Class
The type and class of station device, e.g., Notebook/Mac. For a WDS Link
session, WDS Link/Array are shown here.
Manufacturer
The manufacturer of the station device, e.g., Apple, Motorola, etc.
Application
The name of the application generating this traffic.
Throughput data shown in the table depends on your Selection Criteria, and
may be one of:
Average Tx (Mbps)
Shows the average traffic transmitted (in megabits per second) by the
application for the time period you specified.
Average Rx (Mbps)
Shows the average traffic received (in megabits per second) by the
application for the time period you specified.
Average Tx+Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the application for the time period you specified.
Management System
322 ManagingReports
Traffic Reports
Throughput is a measure of the amount of data that is transmitted in a given
amount of time, expressed in bits per second (bps). Wireless Arrays are designed
to handle Gigabit Ethernet speeds.
With their high-speed capability, your Arrays can easily handle time-sensitive
traffic, such as voice and video. The high capacity XR-6000 Series Wireless Array
has four Gigabit uplink ports, an optional 10 Gigabit fiber connection, and up to
16 IAPs, providing a maximum wireless capacity of up to 7.2 Gbps, which offers
ample reserves for the high demands of current and future applications.
The results returned for all reports in this section are dependent on the reporting
period you specify. Throughput reports include:
Top Arrays by Wired Traffic
Shows the ten Arrays with the highest level of wired traffic.
Top Arrays by Wireless Traffic
Shows the ten Arrays with the highest level of wireless traffic (not
including management traffic).
Wireless Traffic
Shows wireless throughput statistics for Arrays.
Wireless Errors
Shows wireless error statistics for Arrays.
Station Traffic
Tx and Rx average or peak megabits per second for traffic that flows to or
from all associated stations.
Station Errors
Provides wireless error statistics for stations.
Ethernet Traffic
Shows Ethernet throughput statistics for Arrays.
Ethernet Errors
Shows Ethernet error statistics for Arrays.
Top Station Types by Throughput
Shows station types generating the highest traffic demand (Tx+Rx Mbps).
Management System
ManagingReports 323
Top Arrays by Wired Traffic
This report displays the ten Arrays with the highest level of wired traffic, based
on the traffic flow through the Gigabit ports on each wireless Array for the
selected time period. (Figure 216) The bar chart at the top of the window
identifies the Arrays (among the set you selected) with the highest throughput on
the wired ports for the selected time range. If you selected less than ten Arrays,
then all of them will be shown.
A table shows throughput on the wired ports for each Array managed by XMS
(not just the selected Arrays). The information displayed in this window and in
the graph is dependent on the selection criteria you specify, summarized below.
If you have a large network, the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
324 ManagingReports
Figure 216. Top Arrays by Wired Traffic Report
Table Details for the Top Arrays by Wired Traffic Report
The table portion of the report shows throughput for all managed Arrays (not just
the selected Arrays), organized by the following column headers:
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Throughput (Mbps)
Shows the throughput (in megabits per second) achieved by the Arrays
wired ports for the time period you specified.
Management System
ManagingReports 325
Top Arrays by Wireless Traffic
This report shows the ten Arrays with the highest level of wireless traffic for the
selected Arrays and devices (not including management traffic). The bar chart at
the top of the window identifies the Arrays (among the set you selected) with the
highest wireless throughput for the selected time range. If you selected less than
ten Arrays, then all of them will be shown. (Figure 217)
A table shows wireless throughput for each Array. The information displayed in
this window and in the graph is dependent on the selection criteria you specify,
summarized below.
If you have a large network, the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
326 ManagingReports
Figure 217. Top Arrays by Wireless Traffic Report
Table Details for the Top Arrays by Wireless Traffic Report
The table portion of the report shows throughput for the selected Arrays,
organized by the following column headers:
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Throughput (Mbps)
Shows the wireless throughput (in megabits per second) achieved by the
Array for the devices and time period you specified.
Management System
ManagingReports 327
Wireless Traffic
This report provides statistical data for wireless throughput, based on the traffic
flow achieved by each wireless Array. (Figure 218) The graph at the top of the
window displays wireless data summed over the selected Arrays for the selected
time range.
A table shows throughput for each Array, broken out by individual IAPs. The
information displayed in this window and in the graph is dependent on the
selection criteria you specify, summarized below.
If you have a large network, the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
IAP Include only the selected IAP.
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
328 ManagingReports
Figure 218. Wireless Traffic Report
Table Details for the Wireless Traffic Report
The table portion of the report shows traffic statistics for each IAP on the selected
Arrays, organized by the following column headers:
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Array IP Address
This is the Arrays IP address.
Management System
ManagingReports 329
IAP Name
Each IAP in each Array is listed.
IAP MAC Address
This is the IAPs MAC address.
Throughput data shown in the table depends on your Selection Criteria. If you
set Display Traffic by to Tx+Rx, these columns are shown:
Min. (Mbps)
Shows the minimum throughput (in megabits per second) achieved by
the IAP for the time period you specified.
Max. (Mbps)
Shows the maximum throughput (in megabits per second) achieved by
the IAP for the time period you specified.
Avg. (Mbps)
Shows the average throughput (in megabits per second) achieved by the
IAP for the time period you specified.
If you set Display Traffic by to Total, these columns are shown:
Average Tx/Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the IAP for the time period you specified.
Peak Tx/Rx (Mbps)
Shows the maximum total throughput (in megabits per second) achieved
by the IAP for the time period you specified.
Management System
330 ManagingReports
Wireless Errors
This report shows wireless communication error statistics for Array IAPs in the
XMS managed network, based on your Selection Criteria.
Array errors reported are packet error rate, packet retry rate, and encryption retry
rate, shown as a percentage of the total number of packets. (Figure 219) The graph
shows the weighted average wireless error percentages for all Arrays, using this
formula:
Errors / (Retries + Errors + Encryption Errors)
Table Details for the Wireless Errors Report
The results shown in this report are organized by the following column headers,
which can be sorted to best suit your viewing needs:
Array Hostname
The host name assigned to the Array.
Array MAC Address
This is the Arrays MAC address.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
IAP Include only errors for the selected IAP.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 331
Array IP Address
The IP address assigned to the Array.
Packet Error Rate
The packet error rate shown in this window reflects the bit errors detected
by the system during the time period that you specified. The percentage
shown is the number of bit errored packets divided by the total number
of packets.
Figure 219. Wireless Errors Report
Management System
332 ManagingReports
Packet Retry Rate
Shows how many attempts were made to re-send dropped packets
during the time period you specified. The percentage shown is the
number of packet retries divided by the total number of packets.
Encryption Error Rate
Shows how many attempts were made to reconcile security issues.
The percentage shown is the number of received encryption errors
divided by the total number of received packets.
Management System
ManagingReports 333
Station Traffic
This report provides statistical data for throughput for the selected time period,
based on the traffic flow achieved by each client station associated to the selected
Arrays. (Figure 220) Throughput summed over all stations is represented in a
graph at the top of the window. Throughput broken out by station is detailed in a
table underneath.
The information displayed in this window is dependent on your Selection
Criteria. There are two types of throughput data displayed, based on your choice
for Display Traffic by:
If you select Tx+Rx, both graph and table display average transmit,
receive, and total traffic broken out separately into three lines. Transmit
throughput is shown in red (Tx), receive throughput is shown in blue
(Rx), and total throughput is shown in green (Tx+Rx).
Select Total to display two lines: the average value of Tx+Rx in green, and
the peak value of Tx+Rx in magenta.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only member Arrays of the selected map.
Array Include only the selected Array.
SSID Include only the selected SSID.
IAP Include only the selected IAP.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Management System
334 ManagingReports
If you have a large network the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Table Details for the Station Traffic Report
The results shown in this report are organized by the following column headers:
Array Hostname
The host name of the Array to which the station is associated.
IAP Name
The IAP to which the station is associated.
Station Hostname
This column shows the host name for each client station listed in the
report. The Station Hostname is specified for a device (in this case, a client
station) when its networking is installed and configured. In order to
connect to a computer running the TCP/IP protocol via its hostname (or
Windows NetBIOS name), the name must be resolved to an IP address.
Station MAC Address
This is the stations MAC address.
Station IP Address
This is the stations IP address.
Device Class/Type
The class and type of station device, e.g., Notebook/Mac. For a WDS Link
session, Array/WDS Link are shown here.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Management System
ManagingReports 335
Figure 220. Station Traffic Report (Tx+Rx)
Throughput data shown in the table depends on your Selection Criteria. If you
set Display Traffic by to Tx+Rx, these columns are shown:
Average Tx (Mbps)
Shows the average transmit throughput (in megabits per second)
achieved by the station for the time period you specified.
Average Rx (Mbps)
Shows the average receive throughput (in megabits per second) achieved
by the station for the time period you specified.
Management System
336 ManagingReports
Average Tx+Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the station for the time period you specified.
If you set Display Traffic by to Total, these columns are shown:
Average Tx/Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the station for the time period you specified.
Peak Tx/Rx (Mbps)
Shows the maximum total throughput (in megabits per second) achieved
by the station for the time period you specified.
Management System
ManagingReports 337
Station Errors
This report lists all stations with errors that were detected by XMS, based on your
Selection Criteria.
Station errors reported in this window include weighted averages for the packet
error rate and packet retry rate, where both categories are based on a percentage
of the total number of these events detected by the system. Figure 221 shows an
example of the error report for stations. The graph shows the packet error and
packet dropped error percentages for all Arrays.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
IAP Include only the selected IAP.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
SSID Include only the selected SSID.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
338 ManagingReports
Table Details for the Station Errors Report
The results shown in this report are organized by the following column headers:
Array Hostname
The host name of the Array that the station is associated with.
IAP Name
The IAP that the station is associated with.
Station Hostname
This column shows the host name of each client station in the report.
Station MAC Address
This is the stations MAC address.
Figure 221. Station Errors Report
Management System
ManagingReports 339
Station IP Address
The IP address assigned to the station.
Device Class/Type
The class and type of station device, e.g., Notebook/Mac. For a WDS Link
session, Array/WDS Link are shown here.
Packet Error Rate%
The packet error rate shown in this window reflects the bit errors detected
by the system during the time period you specified. The percentage
shown is the number of packet errors divided by the total number of
packets.
Packet Retry Rate%
Shows how many attempts were made to re-send failed packets during
the time period you specified. The percentage shown is the number of
packet retries divided by the total number of packets.
Management System
340 ManagingReports
Ethernet Traffic
This report provides statistical data for Ethernet throughput, based on the speeds
achieved by the Gigabit1 Ethernet port on wireless Arrays. (Figure 222) The
graph at the top of the window displays aggregate data throughput across all
Arrays for the selected time range.
A table shows average and peak Ethernet rates for each Array. The information
displayed in this window and in the graph is dependent on the selection criteria
you specify, summarized below.
If you have a large network, the results returned in this report may span many
pages. The browser display of the report will truncate to three pages to give you a
preview to see the entire report open the PDF version.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
VLAN Include only the selected VLAN (specified by name
or number)
Display Traffic by Break out transmit and receive traffic separately, or
show only totals.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 341
Figure 222. Ethernet Traffic Report
Table Details for the Ethernet Traffic Report
The table portion of the report shows traffic statistics for the Gigabit1 port on
selected Arrays, organized by the following column headers:
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Array MAC Address
This is the Arrays MAC address.
Management System
342 ManagingReports
Management IP Address
This is the Arrays management IP address.
Throughput data shown in the table depends on your Selection Criteria. If you
set Display Traffic by to Tx+Rx, these columns are shown:
Average Tx (Mbps)
Shows the average transmit throughput (in megabits per second)
achieved by the Array for the time period you specified.
Average Rx (Mbps)
Shows the average receive throughput (in megabits per second) achieved
by the Array for the time period you specified.
Average Tx+Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the Array for the time period you specified.
If you set Display Traffic by to Total, these columns are shown:
Average Tx/Rx (Mbps)
Shows the average total throughput (in megabits per second) achieved by
the Array for the time period you specified.
Peak Tx/Rx (Mbps)
Shows the maximum total throughput (in megabits per second) achieved
by the Array for the time period you specified.
Management System
ManagingReports 343
Ethernet Errors
This report shows Ethernet communication errors for the Gigabit ports for Arrays
in the XMS managed network, based on your Selection Criteria.
Ethernet errors reported include packet error rate and packet retry rate, where
both categories are based on a percentage of the total number of packets.
(Figure 223)
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
VLAN Include only the selected VLAN (specified by name
or number)
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
344 ManagingReports
Figure 223. Ethernet Errors Report
Table Details for the Ethernet Errors Report
The results shown in this report are organized by the following column headers:
Array Hostname
The host name assigned to the Array.
Array MAC Address
This is the Arrays MAC address.
Management IP Address
The IP address assigned to the Array.
Management System
ManagingReports 345
Array Packets Error Rate
The packet error rate reflects the bit errors detected by the system during
the time period you specified. The percentage shown is the number of bit
errors divided by the total number of packets.
Array Packets Drop Rate
Shows how many packets failed due to being dropped during the time
period you specified. The percentage shown is the number of packets
dropped divided by the total number of packets.
Management System
346 ManagingReports
Top Station Types by Throughput
This report shows the types of stations generating the highest traffic demand
(both transmitted and received). The bar chart summarizes throughput of
connected stations by their Device Class and Type. It includes all stations
matching the selected device classes and types that were associated to the selected
Arrays at any time during the specified time period.
Note that if you are using WDS (Wireless Distributed System) links to carry traffic
between Arrays wirelessly, client link stations will be included. These stations can
be recognized by their Device Class and TypeArray and WDS Link.
The information displayed in this window is based on your Selection Criteria.
Use the bar chart for an at-a-glance overview of the station devices generating the
most traffic in your wireless network.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 347
Figure 224. Top Station Types by Throughput Report
Table Details for the Station Types by Throughput Report
The table below the graph shows the overall throughput for each combination of
device type and class for the stations included in the selection criteria.
Device Class
The class of station device, e.g., Notebook, Tablet, Phone, etc. For a WDS
Link session, Array is shown here.
Management System
348 ManagingReports
Device Type
The type of station device, e.g., Blackberry, Android, Windows, Mac, etc.
For a WDS Link session, WDS Link is shown here.
Through put
The combined throughput of stations with this combination of device
class and type.
Management System
ManagingReports 349
Station Reports
A basic wireless network consists of an Access Point (AP) and client stations that
are associated to the network via the AP. Each wireless Array includes a number
of IAPs (Integrated Access Points), with each IAP capable of associating up to 96
client stations. The high capacity XN16 wireless Array has 16 IAPs, which means
the Array can associate up to 1536 stations (16 x 96). And because XMS can
support many Arrays, the number of clients that can be associated may be quite
large. Note that typically, the monitor IAP is enabled for monitoring only
(default), and client stations cannot associate with this IAP.
The following reports are available in this section:
Stations by Wi-Fi Band
Displays a count of stations by Wi-Fi Band.
Station Counts by SSID
Displays a pie chart and table of unique station counts by SSID.
Station Activity Over Time Period
Displays a table of stations with the total time that the stations were
connected and traffic usage statistics.
Station Sessions
Displays information about current sessions and their duration.
Station Classification
Displays stations by unique device class and type.
Station Assurance
Displays Station Assurance events, showing stations that are having
problems with connection quality.
Associated Stations
Provides station association data for the selected Arrays.
Stations By Array
Allows you to review station association data based on selected Arrays,
including how many stations were associated at the busiest (peak) time.
Management System
350 ManagingReports
Unique Station Count
This report displays a line graph showing station counts over time,
broken out into categories by your choice of categories such as SSID and
VLAN.
Management System
ManagingReports 351
Stations by Wi-Fi Band
This report summarizes connected stations by their wireless band2.4GHz or 5
GHz. It includes all stations of the selected Device Class and Type that were
associated to the selected Arrays at any time during the specified time period. A
pie chart shows the distribution of stations by band. (Figure 225)
The information displayed in this window is based on your Selection Criteria.
Use the pie chart for an at-a-glance overview of the proportion of stations
connected at 2.4GHz or 5GHz in your wireless network.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
352 ManagingReports
Figure 225. Stations by Wi-Fi Band Report
Table Details for the Stations by Wi-Fi Band Report
The table below the graph shows the station count for each Wi-Fi band for the
stations included in the selection criteria.
Wi-Fi Band
The wireless band used by the stations2.4GHz or 5 GHz.
Station Count
The number of stations using this band.
Management System
ManagingReports 353
Station Counts by SSID
This report summarizes stations by the SSID to which they are connected. It
includes all stations of the chosen Device Class and Type that were associated to
the selected Arrays at any time during the specified time period. A pie chart
shows the distribution of SSID usage. (Figure 226)
If you are using WDS (Wireless Distributed System) links to carry traffic between
Arrays wirelessly, client link stations will be included. The Device Class and Type
of these stations are Array and WDS Link, respectively.
The information displayed in this window is based on your Selection Criteria.
Use the pie chart for an at-a-glance overview of the proportion of stations using
each SSID.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
354 ManagingReports
Figure 226. Station Counts by SSID Report
Table Details for the Stations by SSID Report
The table below the graph shows the station count for each SSID, for the stations
included in the selection criteria.
SSID
The SSIDs available on the selected Arrays are listed.
Station Count
The number of stations connected using this SSID.
Management System
ManagingReports 355
Station Activity Over Time Period
This report lists stations that had active sessions during the specified time period,
along with the time that the session was active and traffic usage statistics.
Note that if you are using WDS (Wireless Distributed System) links to carry traffic
between Arrays wirelessly, client link sessions will be displayed. These sessions
can be recognized by their Device Class and TypeArray and WDS Link.
The information displayed in this window is based on your Selection Criteria.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
SSID Include only the selected SSID.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
356 ManagingReports
Figure 227. Station Activity Over Time Period Report
Table Details for the Station Activity Over Time Period Report
The table shows the total session length and traffic statistics for each station
included in the selection criteria.
Station MAC Address
This column shows the MAC address for each client station included in
the report.
Station Hostname
This column shows the name for each client station.
Device Class/Type
The class and type of station device, e.g., Notebook/Mac. For a WDS Link
session, Array/WDS Link are shown here.
SSID
The SSID to which each station was associated.
Management System
ManagingReports 357
Total Session Duration
The total length of time that each station was associated. If the station
connected multiple times during the selected time range, then all such
sessions are totaled in this number. The entire length of each session that
occurred during the time period is included. For example, say you specify
a time period of one hour. If a station was associated during that hour and
the total length of that session was ten hours, then all ten hours of that
session will be included in the Total Session Duration statistic.
Tx (Mb)
Shows the total amount of traffic transmitted by this station (in megabits)
for the time period you specified.
Rx (Mb)
Shows the total amount of traffic received by this station (in megabits) for
the time period you specified.
Management System
358 ManagingReports
Station Sessions
This report lists stations that have currently active sessions, along with the time
that the session has been active. A pie chart shows the distribution of session
lengths.
Note that if you are using WDS (Wireless Distributed System) links to carry traffic
between Arrays wirelessly, client link sessions will be displayed. These sessions
can be recognized by their Device Class and TypeArray and WDS Link.
The information displayed in this window is based on your Selection Criteria.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 359
Figure 228. Station Sessions Report
Use the pie chart for an at-a-glance overview of session lengths for Wi-Fi clients.
Management System
360 ManagingReports
Table Details for the Station Sessions Report
The table below the graph shows the session start time and length for each station
included in the selection criteria.
Station MAC Address
This column shows the MAC address for each client station included in
the report.
Station Hostname
This column shows the name for each client station.
Station IP Address
The IP address assigned to the station.
Array Hostname
The host name of the Array to which the station is associated.
Array IP Address
The IP address of the Array to which the station is associated.
Device Class/Type
The class and type of station device, e.g., Notebook/Mac. For a WDS Link
session, Array/WDS Link are shown here.
Time Associated and Session Duration
The time that the session started (i.e., when the client associated to the
Array), and the current length of the session.
Management System
ManagingReports 361
Station Classification
This report summarizes connected stations by their Device Class and Device
Type. It includes all stations that were associated to the selected Arrays at any
time during the specified time period. A pie chart shows the distribution of device
classes.
Note that if you are using WDS (Wireless Distributed System) links to carry traffic
between Arrays wirelessly, client link stations will be included. These stations can
be recognized by their Device Class and TypeArray and WDS Link.
The information displayed in this window is based on your Selection Criteria.
Use the pie chart for an at-a-glance overview of the proportion of station device
classes in your wireless network.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
362 ManagingReports
Figure 229. Station Classification Report
Table Details for the Station Classification Report
The table below the graph shows the station count for each combination of device
type and class for the stations included in the selection criteria.
Device Class
The class of station device, e.g., Notebook, Tablet, Phone, etc. For a WDS
Link session, Array is shown here.
Device Type
The type of station device, e.g., Blackberry, Android, Windows, Mac, etc.
For a WDS Link session, WDS Link is shown here.
Management System
ManagingReports 363
Station Count
The number of stations with this combination of device class and type.
For example, Phone/Blackberry and Phone/Android will each have a
separate row with their own count.
Management System
364 ManagingReports
Station Manufacturers
This report summarizes connected stations by their manufacturer. It includes all
stations that were associated to the selected Arrays at any time during the
specified time period. A pie chart shows the distribution of device manufacturers.
The information displayed in this window is based on your Selection Criteria.
Use the pie chart for an at-a-glance overview of the proportion of manufacturers
in your wireless network.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 365
Figure 230. Station Manufacturers Report
Table Details for the Station Manufacturers Report
The table below the graph shows the station count for each combination of device
type and class for the stations included in the selection criteria.
Manufacturer
The manufacturer of the station device, e.g., Apple, Motorola, etc.
Device Class
The class of station device, e.g., Notebook, Tablet, Phone, etc.
Management System
366 ManagingReports
Device Type
The type of station device, e.g., Blackberry, Android, Windows, Mac, etc.
Station Count
The number of stations with this manufacturer.
Management System
ManagingReports 367
Station Assurance
This report displays a list of Station Assurance events that have been detected in
the wireless network. Station assurance monitors the connection quality that
users are experiencing. The report shows client stations that have had
connectivity issues, such as excessive packet retry or packet error rates, or stations
that are unable to stay associated to the Array. When an Array detects that a
station has reached the threshold value for one or more of the problems that it
checks, an event is triggered. Please see Station Assurance on page 95 and the
Wireless Array Users Guide for more information.
The information displayed in this window is based on your Selection Criteria.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Station Assurance
Event Type
Include only this type of station connectivity
problem.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
368 ManagingReports
Figure 231. Station Assurance Report
Table Details for the Station Assurance Report
For each station assurance event included in the selection criteria, the table shows
the station and its device information, the Array to which it is associated, the type
of connectivity problem, and the session start and end time.
Array Hostname
The host name of the Array to which the station is associated.
Array IP Address
The IP address of the Array to which the station is associated.
Station MAC and IP Address
This column shows the MAC and IP address for each station included in
the report.
Station Hostname
This column shows the name of the station.
Management System
ManagingReports 369
Type
The connection criterion that was not within acceptable thresholds.
Device Class/Type
The class and type of station device, e.g., Notebook/Mac. For a WDS Link
session, Array/WDS Link are shown here.
Start Time
When the problem started.
End Time
When the affected session ended. This will show Currently Active if the
session is still active.
Management System
370 ManagingReports
Associated Stations
This report consists of a table listing stations that are associated to your wireless
network. (Figure 232) The information displayed in this window is based on your
Selection Criteria. You may use the criteria to report on just those stations that are
associated to the selected Arrays, selected IAPs, and/or selected device type/
class.
Station Classification Chart
This pie chart provides a quick overview of Wi-Fi clients, showing the
proportions of different device classes.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
IAP Include only the selected IAP.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 371
Figure 232. Station Association
Discrete Array to Station Association
This table presents a list of all stations associated to the selected Arrays/IAPs/
devices based on the time period you specify. The results shown in this window
are organized by the following column headers:
Array Hostname
The host name of the Array that the station is associated with.
IAP Name
The IAP that the station is associated with.
Management System
372 ManagingReports
Station Hostname
This column shows the name for each client station listed in the report.
Station MAC Address
This is the stations MAC address.
Station IP Address
The IP address assigned to the station.
Username
The session was authenticated under this user name.
Manufacturer
The manufacturer of the station device.
Device Class/Type
The class and type of station device, e.g., Notebook/Mac. For a WDS Link
session, Array/WDS Link are shown here.
Management System
ManagingReports 373
Stations By Array
This report displays a bar chart showing the number of stations associated to
those Arrays that have the highest station count. (Figure 233) The table
underneath gives minimum and maximum counts of clients per Array. The
information displayed in this window is based on your Selection Criteria.
Total Array to Station Associations
This table shows the minimum and maximum number of stations that have been
associated to each Array, with the following information:
Array Name
The host name assigned to the Array.
Array MAC Address
This is the Arrays MAC address.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
IAP Include only the selected IAP.
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
374 ManagingReports
Array IP Address
The IP address assigned to the Array.
Min Stations in 5 Minutes
Shows the lowest number of stations concurrently associated to each
Array over any five minute interval during the time period.
Max Stations in 5 Minutes
Shows the number of stations that were concurrently associated to each
Array at the busiest (peak) five minute interval during the time period.
Unique Stations
Shows the total number of different stations that have associated to each
Array over the time period. Unique means that if the same station
disconnects and then reconnects, it will not be counted more than once.
Max Simultaneous Stations
Shows the maximum number of stations that were concurrently
associated to each Array during the time period.
Figure 233. Station Association (By Array) Report
Management System
ManagingReports 375
Unique Station Count
This report displays a line graph showing unique station counts over time.
Unique means that if the same station disconnects and then reconnects, it will
not be counted more than once in any sum displayed.
The information displayed in this window is based on your Selection Criteria.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
SSID Include only the selected SSID.
VLAN Include only the selected VLAN (specified by name
or number)
Media Type Include only IAPs operating in the selected mode
(802.11b, 802.11g, 802.11a, or 802.11n)
Device Class Include only this class of station device, e.g.,
Notebook, Phone, etc.
Device Type Include only this type of station device, e.g.,
Windows, Mac, etc.
Association Include only authenticated stations, or all stations.
Detail on Break out counts by the selected category, or show
only totals.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
376 ManagingReports
Figure 234. Unique Station Count Report
The graph is detailed on (i.e., broken out into categories by) your choice of
category:
Total show totals only.
Array Name show station count by Array.
VLAN (by name or number) show station count by VLAN.
SSID show station count by SSID.
Media Type show station count by IAP mode: 802.11n, 802.11a, etc.
IAP show station count by IAP: iap1, an1, abgn1, etc.
Association Type show station count according to whether the
connection is authenticated.
Management System
ManagingReports 377
The graph has a separate line for each member of the detailing category. For
example, if you detail on IAP as shown in Figure 234, then there will be a separate
line graph for each IAP: an1, an2, and so on. This report also shows you how
many stations are currently online, and includes minimum (Lowest) and
maximum (Peak) activity. A table at the bottom lists peak station counts broken
out by your requested category.
Table Details for the Station Count Report
The table below the graph simply shows the peak station count for each member
of the Detail on category.
Management System
378 ManagingReports
Array Reports
Array status reports provide utility functions, such as listing all Arrays for you
and showing reliability statistics.
The following reports are available in this section:
Array Inventory
Provides a list of all Arrays in your managed wireless network, including
serial numbers.
Array Availability
This report shows reliability statistics for your managed wireless
network, including MTBF and MTTR figures.
Array Inventory
This report creates an inventory list for your use. (Figure 235) The result is a list of
all your managed wireless Arrays for your reference. You may find it very useful
to save this report as a .csv or .xls file as a starting point for working with Excel.
The report is based on your Selection Criteria.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Order table by Sort table by selected column.
Order Direction Sort in ascending or descending order.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 379
Table Details for the Array Inventory Report
The table portion of the report shows the name, addresses, and serial number of
the selected Arrays, organized by the following column headers:
Array Hostname
The host name assigned to the Array. Only Arrays that meet your
selection criteria are included.
Array MAC Address
This is the Arrays MAC address.
IP Address
This is the Arrays IP address.
Location
The physical location information that you entered for this Array, if any.
Serial Number
This is the Arrays serial number.
Figure 235. Array Inventory Report
Management System
380 ManagingReports
Array Availability
This report shows system reliability statistics for your wireless network, based on
your Selection Criteria. Figure 236 shows an example of the Array Availability
report.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 381
Figure 236. Array Availability Report
Table Details for the Array Availability Report
The Array Availability report is generated as a table. The results are organized by
the following column headers:
Hostname
The host name assigned to the Array.
IP Address
The IP address assigned to the Array.
Total Down Time
Shows the total time (in minutes) that this Array has been down within
the time range specified for this report.
MTBF (Mean Time Between Failures)
Shows the average length of time that elapsed between failures of the
Array within the time range specified for this report shown in days/
hours/minutes.
Management System
382 ManagingReports
MTTR (Mean Time To Repair)
Shows the average length of time that elapsed before functionality to the
Array was restored following a failure within the time range specified for
this report shown in days/hours/minutes.
Up Time%
This is the time that the Array has been up and running successfully,
based on a percentage of the total time for the time period specified for
this report.

If XMS is non-operational for a period of time, Array availability
information for this report is extrapolated from the last known state of
the Array prior to XMS going off-line.
Management System
ManagingReports 383
RF Reports
RF reports provide information on RF (channel) usage in your network. For more
information about assigning channels, see IAPs on page 503. The following RF
report is available:
Channel Usage
Shows which channels each IAP is using.
Channel Usage
This report generates a table of current channel assignments for each IAP and for
all media types (2.4 and 5 GHz channels), based on your Selection Criteria.
The Channel Usage report also provides separate bar charts for the 2.4 GHz and 5
GHz bands, highlighting at a glance the number of IAPs using each channel.
Table Details for the Channel Usage Report
The results shown in this report are organized by the following column headers:
Array Hostname
The host name assigned to the Array that the IAP belongs to.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
Table Row Limit Total number of rows.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
384 ManagingReports
Figure 237. Channel Usage Report
Array IP Address
The IP address assigned to the host Array.
IAP
The name of the access point (for example, iap1, iap3, abg4, an3, a7, etc.).
Management System
ManagingReports 385
Channel(s)
This column shows the channel(s) used by the IAP. IEEE 802.11n IAPs
use two adjacent bonded channels for improved performance, so those
IAPs will show two channels if they have bonding in operation.
Wi-Fi Mode
This shows the IEEE 802.11 media in use by the IAP. Note that client
stations cannot associate with the monitor IAP.
MAC Address / BSSID
This is the IAPs MAC address.
Management System
386 ManagingReports
Security Reports
The level of security you introduce into your network depends on the
requirements of your deployment, though we strongly recommend that you do
not configure your Arrays as Open Systems (no authentication required and no
data encryption). An Access Control List (ACL) and/or WEP (Wired Equivalent
Privacy) should be your minimum requirement for security. WPA and WPA2 offer
even stronger security. The wireless Arrays line rate encryption ensures high
performance when encryption is in use. For more information about security, go
to Rogues on page 89 and IDS Events on page 93.
Security reports provide data based on the security parameters defined for your
network of Arrays, including authentication and data encryption. The following
security reports are available:
IDS Events
Displays a list of intrusion detection events.
Rogue List
Shows all rogue APs that are visible on your network and provides charts
that distinguish between Unclassified, Approved, Known or Unknown
rogue devices.
Management System
ManagingReports 387
IDS Events
This report displays a list of Intrusion Detection System (IDS) events, such as
flood attacks, that have been detected in the wireless network. For descriptions of
the types of attacks detected, as well as the settings to fine-tune IDS on Arrays,
please see the Array User's Guide.
The information displayed in this window is based on your Selection Criteria.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only member Arrays of the selected Array
group.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
IDS Event Type Include only this type of intrusion detection
problem.
Table Row Limit Total number of rows.
Date/Time Include only this time range.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
388 ManagingReports
Figure 238. IDS Events Report
Table Details for the IDS Events Report
For each IDS event included in the selection criteria, the table shows the detecting
Array, the time and channel on which the attack occurred, and the SSID and MAC
address of the attacker, if appropriate.
Array MAC Address
The MAC address of the detecting Array.
Array Hostname
The host name of the detecting Array.
Management System
ManagingReports 389
Type
The type of attack detected.
Channel
The channel on which the attack occurred.
Event MAC Address
This column shows the MAC address of the attacker.
Event SSID
The SSID that was attacked.
Event Time
The date and time that the attack occurred.
Management System
390 ManagingReports
Rogue List
A rogue is any wireless device that is visible on your network but not recognized
as being an integral part of the network. Rogue detection is performed
automatically and constantly by the built-in threat-sensing monitor IAP in each
Array (if monitoring is enabled). XMS collects this information from the Arrays in
its managed network. As access points are switched off and on, the list of detected
rogues changes. Please see Rogues on page 89 for more information about
rogues and their classifications and handling.
This report displays a color-coded pie chart representation of all rogue devices
that have been detected by the portions of your network that you selected.
The chart (Figure 239) shows the percentages of rogue devices based on their
classifications.
Unclassified
These rogues have not yet been classified.
Selection
Criterion
Description
(see Selection Criteria on page 304 for details)
Array Scope Include only Arrays that are members of the selected
Array group or profile.
Map Include only Arrays that are members of the selected
map.
Array Include only the selected Array.
SSID Include only the selected SSID.
Classification Include only rogue IAPs whose classification is
Approved, Known, Unknown, Unclassified,
Blocked, or Ad Hoc.
Schedule Run the report at this time. See Schedule on
page 302.
Email Report To After running, email the report. See Email Report
To on page 302.
Management System
ManagingReports 391
Figure 239. Rogue List Report
Approved
When a rogue is designated as Approved the system stops reporting on it
and no longer displays it in the rogue list.
Known
When a rogue is designated as Known the system stops reporting on this
rogue, but still displays it in the rogue list.
Unknown
These rogues are always displayed in the rogue list.
Management System
392 ManagingReports
Blocked
These rogues have been designated as blocked. An Array can block this
AP by preventing stations from staying associated to the rogue.
Table Details for the Security Report (Rogue List)
Below the pie chart is a table identifying all of the rogues included in the pie chart.
The results are sorted by the Last Active time column, in descending order.
BSSID Vendor ID SSID
This shows the BSSID of the rogue (typically its MAC address), the name
of its equipment manufacturer, and the SSID (network name) that it is
broadcasting. If the rogues SSID is set to default and is being broadcast,
then the entry in this field will be default. If the rogue is configured not to
broadcast its SSID, then the entry in this field will be (empty).
Detecting Array IP Address
Shows the host name and IP address of the Array that is detecting the
rogue device.
Security
Shows the authentication and encryption security levels detected on the
rogue device (for example, AES+TKIP+EAP). If the rogue is running an
open system no security the entry in this field is none.
Channel
This is the channel that the rogue is detected on.
RSSI (Received Signal Strength Indicator)
Shows the strength of the signal being observed from the rogue device by
the detecting Array.
Discovered
This is the date and time that the rogue was discovered by the detecting
Array.
Last Active
This is the date and time that the rogue was last seen by the detecting
Array, or Active if the rogue is still active.
Class
The classification of the rogue, as defined above.
Management System
ConfiguringaWirelessArray 393
Configuring a Wireless Array
The following topics describe how to configure a selected Array using the
Configuration tab on the Array Details window. This tab provides a menu with
an extensive set of convenient options for changing Array settings.
The following WMI windows allow you to establish configuration parameters for
your Array, and include:
General on page 395
Network on page 396
VLAN on page 409
Services on page 414
Security on page 432
SSIDs on page 463
Groups on page 496
IAPs on page 503
Filters on page 549
Tunnels on page 554

Some of these windows are not available for XMS Cloud, as indicated in the
text.
Management System
394 ConfiguringaWirelessArray
The Configuration Tab
To reach this window, select the Arrays link in the Array Configuration section
under Configure at the top of the window. You may also arrive at this window by
selecting the Arrays link in the Overview section under Monitor at the top of the
window. Locate the desired Array in the list. Its Hostname field is a linkclick it
to go to the Array Details window, and then select the Configuration tab.
(Figure 240)
Figure 240. Opening the Configuration Window
Use the menu at the left of this window to go to the desired configuration page.
Note that as long as you remain on the Configuration tab, you may go from
window to window to configure different groups of settings on the Array, and all
of your changes will be accumulated. Click the Apply Config button at the top of
the configuration window to apply these changes to the Arrays running
configuration. If you wish to make these changes permanent, check Save to flash
before you click Apply Config, otherwise the changes you made will not be
applied the next time the Array is rebooted. If you leave the Configuration tab
without saving, your changes will be lost.
Management System
ConfiguringaWirelessArray 395
General
This window allows you to set general information about this Array, including
changing its host name and license, and setting administrator contact
information.
Figure 241. General Information
Procedure for Configuring General Information
1. Hostname: Specify a unique host name for this Array. The host name is
used to identify the Array on the network. Use a name that will be
meaningful within your network environment, up to 64 alphanumeric
characters. The default is the Arrays serial number.
2. Location Information: Enter a brief but meaningful description that
accurately defines the physical location of the Array. In an environment
where multiple units are installed, clear definitions for their locations are
important if you want to identify a specific unit.
3. Admin Contact: Enter the name and contact information of the person
who is responsible for administering the Array at the designated location.

On XN Arrays, some settings are only available if the Arrays license

includes appropriate Xirrus Advanced Feature Sets. For more information
on the features that require a license, please see Advanced Feature Sets in
the Introduction chapter of the Xirrus Wireless Arrays Users Guide.
Management System
396 ConfiguringaWirelessArray
4. Admin Email: Enter the email address of the admin contact you entered
in Step 3.
5. Admin Phone: Enter the telephone number of the admin contact you
entered in Step 3.
6. License Key: If Xirrus issued you a license that differs from the current
value shown, enter it now. If you are an XMS Cloud customer, your
license is automatically managed for you.
Network
Figure 242. Network Configuration Menu
Windows that allow you to change or view configuration settings associated with
the network interfaces include:
Interfaces on page 397
Bonds on page 399
DNS Settings on page 406
CDP Settings on page 407
Management System
ConfiguringaWirelessArray 397
Interfaces
This window allows you to view or change network interface settings. It shows
only the interfaces that are actually on this Array.
Figure 243. Network Interface Settings
Procedure for Configuring the Network Interfaces
1. Enable Interface: Choose Yes to enable this network interface, or choose
No to disable the interface.
2. Allow Management on Interface: Choose Yes to allow management of
this Array via the selected network interface, or choose No to deny all
management privileges for this interface. This option is only available for
the Gigabit interfaces on XN Arrays, management is always enabled on
the 10/100 interface (sometimes called the Management Port).
Management System
398 ConfiguringaWirelessArray
3. Auto Negotiate: This feature allows the Array to negotiate the best
transmission rates automatically. Choose Yes to enable this feature, or
choose No to disable this feature the default is enabled. If you disable
the Auto Negotiate feature, you must define the Duplex and Speed
options manually (otherwise these options are not available).
a. Duplex: Full-duplex mode transmits data in two directions
simultaneously (for example, a telephone is a full-duplex device
because both parties can talk and be heard at the same time). Half-
duplex allows data transmission in one direction at a time only (for
example, a walkie-talkie is a half-duplex device). If the Auto-
Negotiate feature is disabled, you can manually choose Half or Full
duplex for your data transmission preference.
b. MTU: the Maximum Transmission Unit size. This is the largest packet
size (in bytes) that the interface can pass along.
c. Speed: If the Auto-Negotiate feature is disabled, you must manually
choose the desired data transmission speed from the pull-down list. If
configuring the Fast Ethernet interface on XN Arrays, the options are
10 Megabit or 100 Megabit. For configuring the Gigabit interfaces the
options are 10 Megabit or 100 Megabit. (Note that 1000 Megabit
speed can only be set by Auto-Negotiation.)
4. Configuration Server Protocol / IP Settings: Choose DHCP to instruct
the Array to use DHCP when assigning IP addresses to the Array, or
choose Static IP if you intend to enter IP addresses manually. If you select
the Static IP option you must specify the IP address, IP subnet mask and
default gateway.
a. IP Address: If you selected the Static IP option, enter a valid IP
address for the Array. To use any of the remote connections (Web,
SNMP, or SSH), a valid IP address must be established.
b. Subnet Mask: If you selected the Static IP option, enter the subnet
mask (the default for Class C is 255.255.255.0). The subnet mask
defines the range of IP addresses that are available on the routed
subnet where the Array is located.
Management System
ConfiguringaWirelessArray 399
c. Default Gateway: If you selected the Static IP option, enter a valid IP
address for the default gateway. This is the IP address of the router
that the Array uses to transmit data to other networks.
5. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Bonds
On models with more than one Gigabit port these ports may be bonded, i.e.
configured to work together in sets. For example, one port may provide active
backup or load balancing for another, or other options as described in this section.
XR-6000 Series Arrays have four Gigabit ports, and you may specify which ports
are bonded to work together as a pair. You may also select more than two ports to
work together in one group.
You may use the mirror option to have all the traffic that is ingressing and
egressing one bond be transmitted by the bond you are configuring. For example,
if you configure Bond2 to mirror Bond1, then all traffic going in and out of
Bond1s Gigabit ports will be transmitted out of Bond2s Gigabit ports. This way
of duplicating one bonds traffic to another bond is very useful for
troubleshooting with a network analyzer.

If a set of Gigabit ports have been bonded, the IP address, IP mask, IP

gateway, IP DHCP, and Management settings are shared between bonded
ports. Any changes you make to these settings on one member will be
reflected in the settings of the other members. Other settings may be
configured individually.
Management System
400 ConfiguringaWirelessArray
Figure 244. Network Bonds
Procedure for Configuring Network Bonds
Configure the bonding behavior of the Gigabit network interfaces. The fields for
each of these bonds are the same, and include:
1. Bond Mode: Select the desired behavior for a set of bonded Gigabit
Ethernet ports from the following options. For a more detailed discussion
of the use of the Gigabit ports and the options below, please see the Xirrus
Gigabit Ethernet Port Modes Application Note in the Xirrus Resource Center.
The modes below describe the relationship between a set of Gigabit
portsfor example, load balancing or active backup. Use the Ports field
to select the ports that are bonded (set in Step 2). Two or more ports may
be bonded. You may also include just one single port in a bondthis is
useful for mirroring one Gigabit port to another port (Step 4 on page 404).
In Arrays that have four Gigabit ports, you have the option of bonding
three or four ports together. In this discussion, we call two ports that are
bonded Gigx and Gigy.
a. Active Backup (gig ports fail over to each other) This mode
provides fault tolerance and is the default mode. Gigx acts as the
primary link. Gigy is the backup link and is passive. Gigy assumes
the IP properties of Gigx. If Gigx fails, the Array automatically fails
(a) Active backup (b) Aggregate using 802.3ad
Management System
ConfiguringaWirelessArray 401
over to Gigy. When a failover occurs in this mode, Gigy issues
gratuitous ARPs to allow it to substitute for Gigx at Layer 3 as well as
Layer 2. See Figure 245 (a). You may include more than two ports in
the bond with Active Backup to provide additional fault tolerance.
For example, if you have three Gigabit ports configured in a bond, if
the first two ports in the bond were to go down, the Array would fail
over traffic to the third Gigabit port.
Figure 245. Port Modes (a, b)
b. Aggregate Traffic from gig ports using 802.3ad The Array sends
network traffic across all member Gigabit ports to increase link speed
to the network. These ports act as a single logical interface (trunk),
using a load balancing algorithm to balance traffic across the ports.
For non-IP traffic (such as ARP), the last byte of the destination MAC
address is used to do the calculation. If the packet is a fragment or not
TCP or UDP, the source and destination IP addresses are used to do
the calculation. If the packet is TCP or UDP over IP then the source IP
address, destination IP address, source port number and destination
port number are all used to do the calculation. The network switch
(c) Transmit on all ports
Management System
402 ConfiguringaWirelessArray
must also support 802.3ad. If a port fails, the trunk degrades
gracefully the other port still transmits. See Figure 245 (b).
c. Transmit Traffic on all gig ports Transmits incoming traffic on all
Gigabit ports. Any traffic received on Gigabit ports is sent to the
onboard processor. This mode provides fault tolerance. See
Figure 246 (c).
Figure 246. Port Modes (c)
(d) Load balance traffic
Management System
ConfiguringaWirelessArray 403
Figure 247. Port Modes (d)
d. Load balance traffic between gig ports This option provides
trunking, similar to option (b) Aggregate Traffic from gig1 & gig2
using 802.3ad, but it does not use 802.3ad and it uses a different load
balancing algorithm to determine the outgoing Gigabit port. The
outgoing port used is based on an exclusive OR of the source and
destination MAC address. Like option (b), this mode also provides
load balancing and fault tolerance. See Figure 247 (d).
2. Ports: Select the ports to be members of this bond for the behavior
specified by Bond Mode. By default, Bond1 contains Gig1 and Gig2. You
may also set up a bond with a single port, for example, if you wish to
mirror one Gigabit port to another. In Arrays that have four Gigabit ports,
you also have the option of bonding three or four ports together.
When you check off a port to be a member of a bond, that port is
automatically removed from any other bonds that contain it.
3. Active VLANs: Create and manage the list of VLANs that are allowed to
be passed through this port. Traffic will be dropped for VLANs that are
not in this list. The default setting is to pass All VLANs.
Management System
404 ConfiguringaWirelessArray
a. To view or modify the list of allowed VLANs, click Select. The
currently selected (i.e., active) VLANs are listed. Click the minus sign
to remove a VLAN from the list, or the plus sign to add it. There are
also links to Remove all or Add all. A link near the bottom allows
you to Display by VLAN name rather than by number.
Figure 248. Select Active VLANs for this Bond
b. To allow all VLANs (current or future) to be passed, click the All
button. To allow no VLANs (current or future) to be passed, click the
None button.
c. To allow only the set of currently defined VLANs (see VLAN on
page 409) to be passed, click the Current button. Essentially, this
fixes the Active VLANs list to contain the Arrays currently defined
VLANs, and only this set, until you make explicit changes to the
Active VLANs list. If you create new VLANs, they will not be passed
unless you take action to add them to the list.
4. Bond Mirror Specify one of the active bonds (Bondx) that is to be
mirrored by this bond (Bondy), or select Off to disable mirroring.
(Figure 249) All wireless traffic received on the Array is transmitted out
both Bondx and Bondy. All traffic received on Bondx is passed on to the
Management System
ConfiguringaWirelessArray 405
onboard processor as well as out Bondy. All traffic received on Bondy is
passed on to the onboard processor as well as out Bondx. This allows a
network analyzer to be plugged into Bondy to capture traffic for
troubleshooting, while the bonded ports provide network connectivity
for data traffic.
If each bond contains just one port, then you have the simple case of one
port mirroring another.
Figure 249. Mirroring Traffic
5. When done configuring bonds as desired, click the Apply Config button
at the top of the configuration window to apply these changes to the
Array. To make these changes permanent, check Save to flash before
using the Apply Config button.
Management System
406 ConfiguringaWirelessArray
DNS Settings
This window allows you to establish your DNS (Domain Name System) settings.
The Array uses these DNS servers to resolve host names into IP addresses. The
Array also registers its own Host Name with these DNS servers, so that others
may address the Array using its name rather than its IP address. An option allows
you to specify that the Arrays DNS servers will be assigned via a DHCP server
on the wired network.
Note that the DNS servers defined here are not used by wireless clients servers
for stations associated to the Array are defined along with DHCP pools. See
DHCP Server on page 427. At least one DNS server must be set up if you want
to offer clients associating with the Array the ability to use meaningful host
names instead of numerical IP addresses.
Figure 250. DNS Settings
Procedure for Configuring DNS Servers
1. DNS Host Name: Enter a valid DNS host name.
2. DNS Domain: Enter the DNS domain name.
3. DNS Server 1: Enter the IP address of the primary DNS server.
4. DNS Server 2 and DNS Server 3: Enter the IP address of the secondary
and tertiary DNS servers (if required).
5. Use DNS settings assigned by DHCP: If you are using DHCP to assign
the Arrays IP address, click Yes. The Array will then obtain its DNS
domain and server settings from the network DHCP server that assigns
Management System
ConfiguringaWirelessArray 407
an IP address to the Array, rather than using the DNS Server fields above.
You may also configure that DHCP server to assign a host name to the
Array.
6. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
CDP Settings
CDP (Cisco Discovery Protocol) is a layer 2 network protocol used to share
information (such as the device manufacturer and model, network capabilities,
and IP address) with other directly connected network devices. Wireless Arrays
can both advertise their presence by sending CDP announcements, and gather
and display information sent by neighbors.
This window allows you to establish your CDP settings.
Figure 251. CDP Settings
Procedure for Configuring CDP Settings
1. Enable CDP: When CDP is enabled, the Array sends out CDP
announcements of the Arrays presence, and gathers CDP data sent by
neighbors. When disabled, it does neither. CDP is enabled by default.
2. CDP Interval: The Array sends out CDP announcements advertising its
presence at this interval. The default is 60 seconds.
Management System
408 ConfiguringaWirelessArray
3. CDP Hold Time: CDP information received from neighbors is retained
for this period of time before aging out of the Arrays neighbor list. The
default is 180 seconds.
4. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.

CDP works on untagged interfaces. It will not always work with tagged
interfaces on Cisco devices, since they might switch from using CDP to DTP
on tagged trunk links.
Management System
ConfiguringaWirelessArray 409
VLAN
A VLAN (Virtual LAN) is comprised of a group of devices that communicate as a
single network, even though they are physically located on different LAN
segments. Because VLANs are based on logical rather than physical connections,
they are extremely flexible. A device that is moved to another location can remain
on the same VLAN without any hardware reconfiguration.
Understanding Virtual Tunnels
Xirrus Arrays support Layer 2 tunneling with Virtual Tunnels. This allows an
Array to use tunnels to transport traffic for one or more SSID-VLAN pairs onto a
single destination network through the Layer 3 core network.
The Array has low overhead and latency for virtual tunnel connections, with high
resilience. The Array performs all encryption and decryption in hardware,
maintaining wire-rate encryption performance on the tunnel.
Virtual Tunnel Server (VTS)
Tunneling capability is provided by a Virtual Tunnel Server. You supply the server
and deploy it in your network using open-source VTun software, available from
vtun.sourceforge.net. For detailed information on setting up a server, please see
the Xirrus Tunneling Solutions Application Note in the Xirrus Resource Center. To
enable the Array to use tunneling for a VLAN, simply enter the IP address, port
and secret for the tunnel server as described in Step 12 on page 412.
VTun may be configured for a number of different tunnel types, protocols, and
encryption types. For use with Arrays, we recommend the following
configuration choices:
Tunnel Type: Ether (Ethernet tunnel)
Protocol: UDP

For a complete discussion of implementing Voice over Wi-Fi on the Array,

see the Xirrus Voice over Wireless Application Note in the Xirrus
Resource Center.
Management System
410 ConfiguringaWirelessArray
Encryption Type: select one of the encryption types supported by VTun
(AES and Blowfish options are available)
Keepalive: yes
Client-Server Interaction
The Array is a client of the Virtual Tunnel Server. When you specify a VTS for a an
active VLAN-SSID pair, the Array contacts the VTS. The server then creates a
tunnel session to the Array. VTun encapsulated packets will cross the Layer 3
network from the Array to the VTS. When packets arrive at the VTS, they will be
de-encapsulated and the resultant packets will be passed to your switch with
802.1q VLAN tags for final Layer 2 processing. The process occurs in reverse for
packets traveling in the other direction.
We recommend that you enable the VTun keep-alive option. This will send a
keep-alive packet once per second to ensure that the tunnel remains active.
Tunnels can be configured to come up on demand but this is a poor choice for
wireless, since tunnel setup can take roughly 5-20 seconds and present a problem
for authentication.
VLAN Management
This window allows you to assign and configure VLANs. After creating a new
VLAN (added to the list of VLANs), you can modify the configuration
parameters of an existing VLAN or delete a selected VLAN.
Figure 252. VLAN Management
Management System
ConfiguringaWirelessArray 411
The maximum number of VLANs that you may create is determined by the limit
for this Array/AP. It depends on the type of Array/AP, and the release version of
ArrayOS that it is running.
Procedure for Managing VLANs
1. Default Route: This option sets a default route from the Array. The Array
supports a default route on native and tagged interfaces. Once the default
route is configured the Array will attempt to use Address Resolution
Protocol (ARP) to find the default router. ARP finds the MAC address of a
device with a given IP address by sending out a broadcast message
requesting this information. This option allows you to choose a default
VLAN route from the pull-down list. The IP Gateway must be established
for this function to work. After changing the Default Route, you must
check Save to flash, click Apply Config, and then reboot.
2. Native VLAN: This option sets whether the Array management is tagged
or untagged. If you select a Native VLAN, then that VLAN will use an
untagged (Native) link. Otherwise, the Array will use 802.1Q tagging and
a specific VLAN ID with management enabled for management of the
Array.
3. To Edit or Delete a VLAN, select it in the list and click the desired button.
To create a new VLAN:
4. Click the Add button and enter the following fields, as needed.

The Wireless Array supports dynamic VLAN assignments specified by

RADIUS policy settings. When RADIUS sends these assignments, the
Array dynamically assigns wireless stations to VLANs as requested.
VLAN tags on traffic are passed through the Array (i.e., VLAN tags are
not stripped).
It is critical to configure all VLANs to be used on the Array, even those
that will be dynamically assigned.
Management System
412 ConfiguringaWirelessArray
Figure 253. Creating a VLAN
5. Name/VLAN ID: Enter a name and number for the new VLAN (1-4094).
6. Management: Check this box to allow management over this VLAN.
7. DHCP: Check this box if you want the DHCP server to assign the IP
address, subnet mask and gateway address to the VLAN automatically,
otherwise you must go to the next step and assign these parameters
manually.
8. Xirrus Roaming: Check this box to allow roaming over this VLAN.
9. IP Address: If the DHCP option is disabled, enter a valid IP address for
this VLAN association.
10. Subnet Mask: If the DHCP option is disabled, enter the subnet mask IP
address for this VLAN association.
11. Gateway: If the DHCP option is disabled, enter the IP gateway address
for this VLAN association.
Management System
ConfiguringaWirelessArray 413
12. Tunnel Server: If this VLAN is to be tunneled, enter the IP address or
host name of the tunnel server that will perform the tunneling. For more
information on virtual tunnels, please see Understanding Virtual
Tunnels on page 409.
13. New Secret/Confirm Secret: Enter the password expected by the tunnel
server.
14. Port: If this VLAN is to be tunneled, enter the port number of the tunnel
server.
15. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
414 ConfiguringaWirelessArray
Services
Services on the Array include DHCP, SNMP, Syslog, Netflow, WiFi Tag, and
Network Time Protocol (NTP) services.
The following sections discuss configuring services on the Array:
Time Settings (NTP) on page 414
NetFlow on page 416
Wi-Fi Tag on page 418
System Log on page 419
SNMP on page 424 (not available in XMS Cloud)
DHCP Server on page 427
Location on page 429
Time Settings (NTP)
This window allows you to manage the Arrays time settings, including
synchronizing the Arrays clock with a universal clock from an NTP (Network
Time Protocol) server. We recommend that you use NTP for proper operation of
SNMP in XMS, since a lack of synchronization will cause errors to be detected.
Synchronizing the Arrays clock with an NTP server also ensures that Syslog
time-stamping is maintained across all units.
It is possible to use authentication with NTP to ensure that you are receiving
synchronization from a known source. For example, the instructions for
requesting a key for the NIST Authenticated NTP server are available at
http://www.nist.gov/pml/div688/grp00/upload/ntp_instructions.pdf.
The Array allows you to enter optional authentication information.
Management System
ConfiguringaWirelessArray 415
Figure 254. Time Settings (Using NTP)
Procedure for Managing the Time Settings
1. Time Zone: Select the time zone you want to use (normally your local
time zone) from the pull-down list.
2. Auto Adjust Daylight Savings: Check this box if you want the system to
adjust for daylight savings automatically, otherwise leave this box
unchecked (default).
3. Use Network Time Protocol: You must use NTP, since XMS works best
when synced to a time server. Arrays managed by XMS should also use
NTP.
4. Using an NTP Server
a. NTP Primary Server: To use NTP, enter the IP address or domain
name of the NTP server.
b. NTP Primary Authentication: (optional) If you are using
authentication with NTP, select the type of key: MD5 or SHA1. Select
None if you are not using authentication (this is the default).
c. NTP Primary Authentication Key ID: Enter the key ID, which is a
decimal integer.
Management System
416 ConfiguringaWirelessArray
d. NTP Primary Authentication Key: Enter your key, which is a string
of characters.
e. NTP Secondary Server: Enter the IP address or domain name of an
optional secondary NTP server to be used in case the Array is unable
to contact the primary server. You may use the authentication fields
as described above if you wish to set up authentication for the
secondary server.
NetFlow
This window allows you to enable or disable the sending of NetFlow information
to a designated collector. NetFlow is a proprietary but open network protocol
developed by Cisco Systems for collecting IP traffic information. When NetFlow
is enabled, the Array will send IP flow information (traffic statistics) to the
designated collector.
NetFlow sends per-flow network traffic information from the Array. Network
managers can use a NetFlow collector to view the statistics on a per-flow basis
and use this information to make key decisions. Knowing how many packets and
bytes are sent to and from certain IP addresses or across specific network
interfaces allows administrators to track usage by various areas. Traffic flow
information may be used to engineer networks for better performance.
Figure 255. NetFlow
Management System
ConfiguringaWirelessArray 417
Procedure for Configuring NetFlow
1. Enable NetFlow: Select one of the Netflow versions to enable NetFlow
functionality: v5, v9, or IPFIX. Internet Protocol Flow Information Export
(IPFIX) is an IETF protocol (www.ietf.org) performing many of the same
functions as Netflow. Choose Disable if you wish to disable this feature.
2. NetFlow Collector Host (Domain or IP): If you enabled NetFlow, enter
the domain name or IP address of the collector.
3. NetFlow Collector Port: If you enabled NetFlow, enter the port on the
collector host to which to send data.

On XN Arrays, some features, such as Netflow, are only available if the

Arrays license includes the Xirrus Advanced RF Analysis Manager
(RAM). See Array DetailsSystem on page 70 to see if the Array
license includes this feature.
Management System
418 ConfiguringaWirelessArray
Wi-Fi Tag
This window allows you to enable or disable Wi-Fi tag capabilities. When
enabled, the Array listens for and collects information about Wi-Fi RFID tags sent
on the designated channel. These tags are transmitted by specialized tag devices
(for example, AeroScout or Ekahau tags). A Wi-Fi tagging server then queries the
Array for a report on the tags that it has received. The Wi-Fi tagging server uses
proprietary algorithms to determine locations for devices sending tag signals.
Figure 256. Wi-Fi Tag
Procedure for Configuring Wi-Fi Tag
1. Enable Wi-Fi Tag: Choose Yes to enable Wi-Fi tag functionality, or choose
No to disable this feature.
2. Wi-Fi Tag UDP Port: If you enabled Wi-Fi tagging, enter the port on the
Array which the Wi-Fi tagging server will use to query the Array for
tagging data. When queried, the Array will send back information on the
tags it has observed. For each, the Array sends information such as the
MAC address of the tag transmitting device, and the RSSI and noise floor
observed.
3. Wi-Fi Tag Channel: If you enabled Wi-Fi tagging, enter the 802.11
channel on which the Array will listen for tags. The tag devices must be
set up to transmit on this channel. Only one channel may be configured,
and it must be an 802.11b/g channel in the range of Channel 1 to 11.
Management System
ConfiguringaWirelessArray 419
4. Ekahau Server: If you enabled Wi-Fi tagging and you are using an
Ekahau server, enter its IP address or hostname. Ekahau Wi-Fi Tag
packets received by the Array will be encapsulated as expected by
Ekahau, and forwarded to the server.
System Log
This window allows you to enable or disable the Syslog server, define primary,
secondary, and tertiary servers, set up email notification, and set the level for
Syslog reporting for each of the servers and for email notification the Syslog
service will send Syslog messages that are at the selected severity or above to the
defined Syslog servers and email address. An option allows you to use a Splunk
application to analyze Array events.
Figure 257. System Log
Management System
420 ConfiguringaWirelessArray
Procedure for Configuring Syslog
1. Enable Syslog Server: Choose Yes to enable Syslog functionality, or
choose No to disable this feature.
2. Console Logging: If you enabled Syslog, select whether or not to echo
Syslog messages to the console as they occur. If you enable console
logging, be sure to set the Console Logging level (see Step 7 below).
3. Local File Size (1-2000 lines): Enter a value in this field to define how
many Syslog records are retained locally on the Arrays internal Syslog
file. The default is 2000.
4. Primary Server Address (Hostname or IP) and Port: If you enabled
Syslog, enter the hostname or IP address of the primary Syslog server.
You may also change the port used on the server if you do not wish to use
514, the default port.
5. Secondary/Tertiary Server Address (Hostname or IP) and Port:
(Optional) If you enabled Syslog, you may enter the hostname or IP
address of one or two additional Syslog servers to which messages will
also be sent. You may also change the port used on each server if you do
not wish to use 514, the default port. You may set one of the server
addresses to the address of a server for Splunk (see About Using the
Splunk Application for Xirrus Arrays on page 422).
6. Email Notification: (Optional) The following parameters allow you to
send an email to a designated address each time a Syslog message is
generated. The email will include the text of the Syslog message.
a. Email Syslog SMTP Server Address (Hostname or IP) and Port: The
hostname or the IP address of the SMTP server to be used for sending
the email. Note that this specifies the mail server, not the email
recipient. You may also change the port used on the server if you do
not wish to use 25, the default SMTP port.
b. Email Syslog SMTP User Name: Specify a user name for logging in
to an account on the mail server designated in Step a.
Management System
ConfiguringaWirelessArray 421
c. Email Syslog SMTP User Password: Specify a password for logging
in to an account on the mail server designated in Step a.
d. Email Syslog SMTP From: Specify the From email address to be
displayed in the email.
e. Email Syslog SMTP Recipient Addresses: Specify the entire email
address of the recipient of the email notification. You may specify
additional recipients by separating the email addresses with
semicolons (;).
7. Station Formatting: If you are sending event information to a Splunk
server, select Key/Value to send data in Splunks expected format,
otherwise leave this at the default value of Standard. See About Using
the Splunk Application for Xirrus Arrays on page 422.
8. Station URL Logging: When enabled, Syslog messages are sent for each
URL that each station visits. Only HTTP destinations (port 80) are logged;
HTTPS destinations (port 443) are not logged. All URLs in a domain are
logged, so for example, if an HTTP request to yahoo.com generates
requests to 57 other URLs, all are logged. Furthermore, each visit to the
same URL generates an additional log message. No deep packet
inspection is performed by the URL logging, so no Application Control
information is included in the Syslog message.
The following information is included in the syslog message:
Date / Time
Source Device MAC and IP address
Destination Port
Destination Site address (e.g., 20.20.20.1)
The specific URL (e.g., http://20.20.20.1.24online/images/img2.jpg)
Station URL Logging is disabled by default.
Management System
422 ConfiguringaWirelessArray
9. Syslog Levels: For each of the Syslog destinations, choose your preferred
level of Syslog reporting from the pull-down list. Messages with
criticality at the selected level and above will be shown. The default level
varies depending on the destination.
a. Console Logging: For messages to be echoed to the console, the
default level is Critical and more serious. This prevents large
numbers of non-critical messages from being displayed on the
console. If you set this level too low, the volume of messages may
make it very difficult to work with the CLI or view other output on
the console.
b. Local File: For records to be stored on the Arrays internal Syslog file,
choose your preferred level of Syslog reporting from the pull-down
list. The default level is Debugging and more serious.
c. Primary Server: Choose the preferred level of Syslog reporting for the
primary server. The default level is Debugging and more serious.
d. Secondary/Tertiary Server: Choose the preferred level of reporting
for the secondary/tertiary server. The default level is Information
and more serious. (Optional)
e. Email SMTP Server: Choose the preferred level of Syslog reporting
for the email notifications. The default level is Warning and more
serious. This prevents your mailbox from being filled up with a large
number of less severe messages such as informational messages.
10. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
About Using the Splunk Application for Xirrus Arrays
Splunk may be used to provide visibility into client experience and analyze usage
on XR Series Wireless Arrays. A Splunk application (Splunk for Xirrus XR
Wireless Arrays) has been developed to present this operational intelligence at a
glance. The app includes field extractions, event types, searches and dashboards
to help shine a light on station status and activity.
Management System
ConfiguringaWirelessArray 423
To use Splunk, set up your Splunk server with the Splunk applicationavailable
from www.splunk.com at Splunk for Xirrus XR Wireless Arrays. Configure the
Array to send data to Splunk by setting a Primary, Secondary, or Tertiary Server
Address to the IP address or hostname of your Splunk server. Then set Station
Formatting to Key/Value to send data in Splunks expected format.
You may specify Server Addresses for Syslog servers and a Splunk server on the
same Array. Selecting the Key/Value option will not cause any problems with
Syslog.
Management System
424 ConfiguringaWirelessArray
SNMP
This window allows you to enable or disable SNMP v2 and SNMP v3 and define
the SNMP parameters. SNMP allows remote management of the Array by the
Xirrus Management System (XMS) and other SNMP management tools. SNMP v3
was designed to offer much stronger security. You may enable either SNMP
version, or both.
Figure 258. SNMP
Complete SNMP details for the Array, including trap descriptions, are found in
the Xirrus MIB, available at support.xirrus.com, in the Downloads section (login
is required to download the MIB).

This page is not available for XMS Cloud.
Management System
ConfiguringaWirelessArray 425
NOTE: If you are managing your Arrays with XMS (the Xirrus Management System),
it is very important to make sure that your SNMP settings match those that you have
configured for XMS. XMS uses both SNMP v2 and v3, with v3 given preference.
Procedure for Configuring SNMP
SNMPv2 Settings
1. Enable SNMPv2: Choose Yes to enable SNMP v2 functionality, or choose
No to disable this feature. When used in conjunction with the Xirrus
Management System, SNMP v2 (not SNMP v3) must be enabled on each
Array to be managed with XMS. The default for this feature is Yes
(enabled).
2. Read-Write Community String: Enter the read-write community string.
The default is xirrus.
3. Read-Only Community String: Enter the read-only community string.
The default is xirrus_read_only.
SNMPv3 Settings
4. Enable SNMPv3: Choose Yes to enable SNMP v3 functionality, or choose
No to disable this feature. The default for this feature is Yes (enabled).
5. Authentication: Select the desired method for authenticating SNMPv3
packets: SHA (Secure Hash Algorithm) or MD5 (Message Digest
Algorithm 5).
6. Privacy: Select the desired method for encrypting data: DES (Data
Encryption Standard) or the stronger AES (Advanced Encryption
Standard).
7. Context Engine ID: The unique identifier for this SNMP server. This
value may not be changed from this window. The Context Engine ID
must be set if data collection is to be done via a proxy agent. This ID helps
the proxy agent to identify the target agent from which data is to be
collected.
Management System
426 ConfiguringaWirelessArray
8. Read-Write Username: Enter the read-write user name. This username
and password allow configuration changes to be made on the Array. The
default is xirrus-rw.
9. Read-Write Authentication Password: Enter the read-write password for
authentication (i.e., logging in). The default is xirrus-rw.
10. Read-Write Privacy Password: Enter the read-write password for privacy
(i.e., a key for encryption). The default is xirrus-rw.
11. Read-Only Username: Enter the read-only user name. This username
and password do not allow configuration changes to be made on the
Array. The default is xirrus-ro.
12. Read-Only Authentication Password: Enter the read-only password for
authentication (i.e., logging in). The default is xirrus-ro.
13. Read-Only Privacy Password: Enter the read-only password for privacy
(i.e., a key for encryption). The default is xirrus-ro.
SNMP Trap Settings
14. Trap Host IP Address: Enter the IP Address or hostname, as well as the
Port number, of an SNMP management station that is to receive SNMP
traps. You may specify up to four hosts that are to receive traps. Note that
by default, Trap Host 1 sends traps to Xirrus-XMS. Thus, the Array will
automatically communicate its presence to XMS (as long as the network is
configured correctly to allow this host name to be resolved note that
DNS is not normally case-sensitive).
For a definition of the traps sent by Xirrus Wireless Arrays, you may
download the Xirrus MIB from support.xirrus.com (login required).
Search for the string TRAP in the MIB file.
15. Keepalive Trap Interval (minutes): Traps are sent out at this interval to
indicate the presence of the Array on the network. Keepalive traps are
required for proper operation with XMS. To disable keepalive traps, set
the value to 0.
Management System
ConfiguringaWirelessArray 427
16. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
DHCP Server
This window allows you to create, enable, modify and delete DHCP (Dynamic
Host Configuration Protocol) address pools. DHCP allows the Array to provide
wireless clients with IP addresses and other networking information. The DHCP
server will not provide DHCP services to the wired side of the network. If you do
not use the DHCP server on the Array, then your wired network must be
configured to supply DHCP addresses and gateway and DNS server addresses to
wireless clients.
When you create a DHCP pool, you must define the DHCP lease time (default
and maximum), the IP address ranges (pools) that the DHCP server can assign,
and the gateway address and DNS servers to be used by clients.
Figure 259. DHCP Management
DHCP usage is determined in several windows see SSID Management, Group
Management, and VLAN Management.
Procedure for Configuring the DHCP Server
1. Click the Add button to create a new DHCP pool.
2. Enabled: Click this checkbox to make this pool of addresses available, or
clear it to disable the pool.
Management System
428 ConfiguringaWirelessArray
3. Name: Enter a name for the new DHCP pool. The new pool ID is added
to the list of available DHCP pools.
Figure 260. Adding a DHCP Pool
4. NAT Enabled (Network Address Translation): Check this box to enable
the Network Address Translation feature.
5. Default Lease (sec): This field defines the default DHCP Lease time (in
seconds). The factory default is 300 seconds, but you can change the
default at any time.
6. Max Lease: Enter a value (in seconds) to define the maximum allowable
DHCP lease time. The default is 300 seconds.
7. Start IP Range: Enter an IP address to define the start of the IP range that
will be used by the DHCP server. The default is 192.168.1.100.
Management System
ConfiguringaWirelessArray 429
8. End IP Range: Enter an IP address to define the end of the IP range that
will be used by the DHCP server. The DHCP server will only use IP
addresses that fall between the start and end range that you define on this
page. The default is 192.168.1.200.
9. Default Subnet Mask: Enter the subnet mask for this IP range for the
DHCP server. The default is 255.255.255.0.
10. Gateway: If necessary, enter the IP address of the gateway.
11. Default Domain: Enter the DNS domain name. See DNS Settings on
page 406.
12. Default DNS Servers (1 to 3): Enter the IP address of the primary DNS
server, secondary DNS server and tertiary DNS server. These DNS server
addresses will be passed to stations when they associate, along with the
assigned IP address. Note that if you leave these blank, no DNS
information is sent to the stations. DHCP will not default to sending the
DNS servers that are configured in DNS Settings. See also, DNS
Settings on page 406.
13. Click OK to add this entry to the list.
14. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Location
Xirrus Arrays offer an integrated capability for capturing and uploading visitor
analytics data, eliminating the need to install a standalone sensor network. This
data can be used to characterize information such as guest or customer traffic and
location, visit duration, and frequency. Use this Location window to configure the
Array to send collected data to an analytics server, such as Euclid.
When Location Support is enabled, the Array collects information about stations,
including the station ID and manufacturer, time and length of the visit and related
time interval statistics, and signal strength and its related statistics. Data collected
from stations comprises only basic device information that is broadcast by Wi-Fi
enabled devices. Devices that are only detected are included, as well as those that
Management System
430 ConfiguringaWirelessArray
actually connect to the Array. The Array sending the data also sends its own ID so
that the server knows where the visitors were detected. All data messages are
encrypted, and they are uploaded via HTTPS. The message format used is
described in Location Service Data Formats on page 646.
Figure 261. Location
Procedure for Configuring Location
1. Enable Location Support: Choose Enabled to enable the collection and
upload of visitor analytic data, or choose Disabled to disable this feature.
2. Location URL: If you enabled Location Support, enter the IP address or
hostname of the location/analytics server. For a Euclid analytics server,
the Array will send JSON-formatted messages in the form required by
Euclid via HTTPS. Use the URL that was assigned to you as a customer
by Euclid.
3. Location Key: Enter your customer ID for the location/analytics server.
4. Location Period: If you enabled Location Support, specify how often data
is to be sent to the server, in seconds.
Management System
ConfiguringaWirelessArray 431
5. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
432 ConfiguringaWirelessArray
Security
Array security settings include administration accounts, Access Control List
(ACL), management settings, encryption and authentication protocol settings,
and RADIUS configuration settings. For additional information about wireless
network security, refer to Understanding Security on page 432.
For information about secure use of the WMI on the Array, refer to:
About Creating Admin Accounts on the RADIUS Server on page 439
About Creating User Accounts on the RADIUS Server on page 452
Security settings are configured with the following windows on all XMS versions
except XMS Cloud:
Admin Management on page 435
Admin Privileges on page 436
Admin RADIUS on page 438
Management Control on page 441
Security settings are configured with the following windows on all XMS versions:
Global Settings on page 446
Access Control List on page 449
External Radius on page 451
Internal Radius on page 456
Airwatch on page 458
Understanding Security
The Xirrus Wireless Array incorporates many configurable security features.
After initially installing an Array, always change the default administrator
password (the default is admin), and choose a strong replacement password
(containing letters, numbers and special characters). When appropriate, issue
read-only administrator accounts.
Other security considerations include:
SSH versus Telnet: Be aware that Telnet is not secure over network
connections and should be used only with a direct serial port connection.
Management System
ConfiguringaWirelessArray 433
When connecting to the units Command Line Interface over a network
connection, you must use a Secure SHell version 2 (SSH-2) utility. SSH-2
provides stronger security than SSH-1. The most commonly used
freeware providing SSH tools is PuTTY.
Configuration auditing: The optional Xirrus Management System (XMS)
offers powerful management features for small or large Xirrus wireless
deployments, and can audit your configuration settings automatically. In
addition, using the XMS eliminates the need for an FTP server.
Choosing an encryption method: Wireless data encryption prevents
eavesdropping on data being transmitted or received over the airwaves.
The Array allows you to establish the following data encryption
configuration options:
Open this option offers no data encryption and is not
recommended, though you might choose this option if clients are
required to use a VPN connection through a secure SSH utility,
like PuTTy.
WEP (Wired Equivalent Privacy) this option provides minimal
protection (though much better than using an open network). An
early standard for wireless data encryption and supported by all
Wi-Fi certified equipment, WEP is vulnerable to hacking and is
therefore not recommended for use by Enterprise networks.
WPA (Wi-Fi Protected Access) and WPA2 these are much
stronger encryption modes than WEP, using TKIP (Temporal Key
Integrity Protocol) or AES (Advanced Encryption Standard) to
encrypt data.
WPA solves security issues with WEP. It also allows you to
establish encryption keys on a per-user-basis, with key rotation
for added security. In addition, TKIP provides Message Integrity
Check (MIC) functionality and prevents active attacks on the
wireless network.
AES is the strongest encryption standard and is used by
government agencies; however, old legacy hardware may not be
capable of supporting the AES mode (it probably wont work on
Management System
434 ConfiguringaWirelessArray
older wireless clients). Because AES is the strongest encryption
standard currently available, WPA2 with AES is highly
recommended for Enterprise networks.
Any of the above encryption methods can be used and an Array can
support multiple encryption methods simultaneously, but only one
method may be selected per SSID (except that selecting WPA-Both allows
WPA and WPA2 to be used at the same time on the same SSID).
Otherwise, if multiple security methods are needed, you must define
multiple SSIDs.
The encryption mode (WEP, WPA, etc.) is selected in the SSIDs >SSID
Management window (see SSID Management on page 471).
The encryption standard used with WPA or WPA2 (AES or TKIP) is
selected in the Security>Global Settings window under WPA Settings
(see Global Settings on page 446).
Choosing an authentication method: User authentication ensures that
users are who they say they are. For this purpose, the Array allows you to
choose between the following user authentication methods:
Pre-Shared Key users must manually enter a key (passphrase)
on the client side of the wireless network that matches the key
stored by the administrator in the Array.
This method should be used only for smaller networks when a
RADIUS server is unavailable. If PSK must be used, choose a
strong passphrase containing between 8 and 63 characters (20 is
preferred). Always use a combination of letters, numbers and
special characters. Never use English words separated by spaces.
RADIUS 802.1x with EAP 802.1x uses a RADIUS server to
authenticate large numbers of clients, and can handle different
EAP (Extensible Authentication Protocol) authentication
methods, including EAP-TLS, EAP-TTLS, EAP-PEAP, and LEAP-
Passthrough. The RADIUS server can be internal (provided by
the wireless Array) or external. An external RADIUS server offers
more functionality and security, and is recommended for large
Management System
ConfiguringaWirelessArray 435
deployments. When using this method, user names and
passwords must be entered into the RADIUS server for user
authentication.
MAC Address ACLs (Access Control Lists) MAC address
ACLs provide a list of client adapter MAC addresses that are
allowed or denied access to the wireless network. Access Control
Lists work well when there are a limited number of users in
this case, enter the MAC address of each user in the Allow list. In
the event of a lost or stolen MAC adapter, enter the affected MAC
address in the Deny list.
The wireless Array will accept up to 1,000 ACL entries.
Admin Management
This window allows you to manage network administrator accounts (create,
modify and delete). It also allows you to limit account access to a read only status.
Figure 262. Admin Management
Procedure for Creating or Modifying Network Administrator Accounts
1. To create a new account, click the Add button and enter the User Name
for a new network administrator ID. The length of the ID must be
between 5 and 50 characters, inclusive.

This page is not available for XMS Cloud.
Management System
436 ConfiguringaWirelessArray
2. Privilege Level: Choose read-write if you want to give this administrator
ID full read/write privileges, or choose read-only to restrict this user to
read only status. In the read only mode, administrators cannot save
changes to configurations. Or you may select one of your custom-defined
privilege levels (see Admin Privileges on page 436).
3. Password: Enter a password for this ID. The length of the password must
be between 5 and 50 characters, inclusive.
4. Confirm Password: Re-enter the password in this field to verify that you
typed the password correctly. If you do not re-enter the correct password,
an error message is displayed.
5. Click OK to add this administrator ID to the list.
6. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Admin Privileges
This window provides a detailed level of control over the privileges of Array
administrators. Administrators may be assigned one of eight Privilege Levels.
You may define the privilege level of each major feature (Configuration Section)
that may be configured on the Array. For example, say that you set the privilege
level to 4 for Reboot Array, Security, Radius Server, and SNMP, and you leave all
other configuration sections at the default privilege level of 1. In this case, any
administrator with a privilege level of 4 or higher may perform any operation on
the Array, while an administrator with a privilege level lower than 4 but at least 1
may perform any operation except those whose level was set to 4. An error
message will be displayed if an operation is attempted without a sufficient
privilege level.

This page is not available for XMS Cloud.
Management System
ConfiguringaWirelessArray 437
Privilege level 0 is read-only. As a minimum, all administrators have permission
for read access to all areas of Array configuration. Higher privilege levels may be
used to define additional privileges for specific configuration sections.

Figure 263. Admin Privileges
Procedure for Configuring Admin Privileges
1. Privilege Levels (optional): You may assign a Name to a Privilege Level
by selecting it and clicking the Edit button. The name may be used to
describe the access granted by this level. By default, levels 0 and 1 are
named read-only and read-write, respectively, and levels 2 through 7
have the same name as their level number.
Management System
438 ConfiguringaWirelessArray
2. Configuration Section Privilege Levels: Use this section to assign a
Privilege Level to Section Names as desired. By default, all sections are
assigned level 1. When you select a higher privilege level for a
configuration section, then only administrators who have at least that
privilege level will be able to make configuration changes to that section.
3. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Admin RADIUS
This window allows you to set up authentication of network administrators via
RADIUS. Using RADIUS to control administrator accounts for logging in to
Arrays has these benefits:
Centralized control of administrator accounts.
Less effort you don't have to set up user names and passwords on each
Array; just enter them once on the RADIUS server and then all of the
Arrays can pull from the RADIUS server.
Enforced policies you may set password rules (e.g., passwords must
contain at least one number and be at least 12 characters in length), and
you may set expiration times for passwords.
Admin RADIUS settings override any local administrator accounts configured on
the Admin Management window. If you have Admin RADIUS enabled, all
administrator authentication is done via the configured RADIUS servers. The
only exception to this is when you are connected via the Console port (using CLI).
If you are using the Console port, the Array will authenticate administrators
using accounts configured on the Admin Management window first, and then use
the RADIUS servers. This provides a safety net to be ensure that you are not
completely locked out of an Array if the RADIUS server is down.

This page is not available for XMS Cloud.
Management System
ConfiguringaWirelessArray 439
About Creating Admin Accounts on the RADIUS Server
Permissions for RADIUS administrator accounts are controlled by the RADIUS
Xirrus-Admin-Role attribute. This is a Vendor Specific Attribute (VSA). To define
the privileges permitted to an administrator account, set the value of its Xirrus-
Admin-Role attribute to the desired Privilege Level Name string, as defined in
Admin Privileges on page 436. For more information about the RADIUS VSAs
used by Xirrus, see RADIUS Vendor Specific Attribute (VSA) for Xirrus in the
Technical Support Appendix of the Xirrus Wireless Array Users Guide.
When configuring administrator accounts on the RADIUS server, you must
observe the same restrictions for length and legal characters as when creating
these accounts on the Array using the Admin Management window: the user
name and password must be between 5 and 50 characters, inclusive.
Figure 264. Admin RADIUS
Procedure for Configuring Admin RADIUS
Use this window to enable/disable administrator authentication via RADIUS,
and to set up primary and secondary servers to use for authentication of
administrators attempting to log in to the Array.
Management System
440 ConfiguringaWirelessArray
1. Admin RADIUS Settings:
a. Enable Admin RADIUS: Click Yes to enable the use of RADIUS to
authenticate administrators logging in to the Array. You will need to
specify the RADIUS server(s) to be used.
b. Authentication Type: Select the protocol used for authentication of
administrators, CHAP or PAP (the default).
PAP (Password Authentication Protocol), is a simple protocol.
PAP transmits ASCII passwords over the network in the clear
(unencrypted) and is therefore considered insecure.
CHAP (Challenge-Handshake Authentication Protocol) is a more
secure protocol. The login request is sent using a one-way hash
function.
MS-CHAP (Microsoft Challenge-Handshake Authentication
Protocol)
c. Timeout (seconds): Define the maximum idle time (in seconds)
before the RADIUS servers session times out. The default is 600
seconds.
2. Admin RADIUS Primary Server: This is the RADIUS server that you
intend to use as your primary server.
a. Host Name / IP Address: Enter the IP address or domain name of this
external RADIUS server.
b. Port Number: Enter the port number of this RADIUS server. The
default is 1812.
c. Shared Secret / Verify Secret: Enter the shared secret that this
RADIUS server will be using, then re-enter the shared secret to verify
that you typed it correctly.

The shared secret that you define must match the secret used by the
RADIUS server.
Management System
ConfiguringaWirelessArray 441
3. Admin RADIUS Secondary Server (optional): If desired, enter an
alternative external RADIUS server. If the primary RADIUS server
becomes unreachable, the Array will failover to the secondary RADIUS
server (defined here).
a. Host Name / IP Address: Enter the IP address or domain name of this
RADIUS server.
b. Port Number: Enter the port number of this RADIUS server.
The default is 1812.
c. Shared Secret / Verify Secret: Enter the shared secret that this
RADIUS server will be using, then re-enter the shared secret to verify
that you typed it correctly.
Management Control
This window allows you to enable or disable the Array management interfaces
and set their inactivity time-outs. The supported range is 300 (default) to 100,000
seconds. (Figure 265)
Procedure for Configuring Management Control
1. Management Settings:
a. Maximum login attempts allowed (1-255): After this number of
consecutive failing administrator login attempts via ssh or telnet, the
Failed login retry period is enforced. The default is 3.
b. Failed login retry period (0-65535 seconds): After the maximum
number (defined above) of consecutive failing administrator login
attempts via ssh or telnet, the administrators IP address is denied
access to the array for the specified period of time (in seconds). The
default is 0.

This page is not available for XMS Cloud.
Management System
442 ConfiguringaWirelessArray
Figure 265. Management Control
c. Pre-login Banner: Text that you enter here will be displayed above
the WMI login prompt. (Figure 266)
Figure 266. Pre-login Banner
Management System
ConfiguringaWirelessArray 443
d. Post-login Banner: Text that you enter here will be displayed in a
message box after a user logs in to the WMI.
2. SSH
a. On/Off: Choose On to enable management of the Array over a Secure
Shell (SSH-2) connection, or Off to disable this feature. Be aware that
only SSH-2 connections are supported by the Array. SSH clients used
for connecting to the Array must be configured to use SSH-2.
b. Timeout 30-100000 (Seconds): Enter a value in this field to define the
timeout (in seconds) before your SSH connection is disconnected. The
value you enter here must be between 30 seconds and 100,000
seconds.
c. Port: Enter a value in this field to define the port used by SSH.
The default port is 22.
3. Telnet:
a. On/Off: Choose On to enable Array management over a Telnet
connection, or Off to disable this feature. SSH offers a more secure
connection than Telnet, and is recommended over Telnet.
b. Timeout 30-100000 (Seconds): Enter a value in this field to define the
timeout (in seconds) before your Telnet connection is disconnected.
The value you enter here must be between 30 seconds and 100,000
seconds.
c. Port: Enter a value in this field to define the port used by Telnet.
The default port is 23.
4. HTTPS
a. Timeout 30-100000 (Seconds): Enter a value in this field to define the
timeout (in seconds) before your HTTPS connection is disconnected.
The value you enter here must be between 30 seconds and 100,000
seconds. Management via HTTPS (i.e., the Web Management
Interface) cannot be disabled on this window. To disable management
over HTTPS, you must use the Command Line Interface.
Management System
444 ConfiguringaWirelessArray
b. Port: Enter a value in this field to define the port used by SSH.
The default port is 443.
5. Xircon
The Xircon utility connects to Xirrus XR Series Arrays that are not
reachable via the normal access methods (such as SSH or WMI) and that
do not have a physical console port, or whose console port is not
accessible. Xircon is not used with earlier Array models (XN or XS Series).
Please see the Xircon Users Guide for more information. You can enable or
disable Xircon access to the Array as instructed below.
a. On/Off: Choose On to enable Xircon access to the Array at the
ArrayOS (CLI) and Xirrus Boot Loader (XBL) levels, or Off to disable
access at both levels. On models that have no console port, Xircon
access is On by default. On all other Array models, Xircon access is
Off by default.
b. ArrayOS only: Choose this radio button to enable Xircon access at the
ArrayOS level only (i.e., Xircon can access CLI only). Access to the
Array at the Xirrus Boot Loader (XBL) level is disabled.
c. Boot only: Choose this radio button to enable Xircon access at the
Xirrus Boot Loader (XBL) level only. ArrayOS level (CLI) access to the
Array is disabled.
d. Connection Timeout 30-100000 (Seconds): Enter a value in this field
to define the timeout (in seconds) before your Xircon connection is
disconnected. The value you enter here must be between 30 seconds
and 100,000 seconds.
e. Port: Enter a value in this field to define the port used by Xircon.
The default port is 22612.
!
Warning: If you disable Xircon access completely on models with no console
port, you must ensure that you do not lose track of the username and password
to log in to CLI/WMI! There is no way to recover from a lost password, other
than returning the Array to Xirrus.
Management System
ConfiguringaWirelessArray 445
6. Serial
This setting is only available for Arrays that have a Console (serial) port.
a. On/Off: Choose On to enable management of the Array via a serial
connection, or choose Off to disable this feature.
b. Connection Timeout 30-100000 (Seconds): Enter a value in this field
to define the timeout (in seconds) before your serial connection is
disconnected. The value you enter here must be between 30 seconds
and 100,000 seconds.
7. Management Modes
a. Network Assurance: Click the On button to enable this mode.
Network assurance checks network connectivity to each server that
you configure, such as the NTP server, RADIUS servers, SNMP trap
hosts, etc. By proactively identifying network resources that are
unavailable, the network manager can be alerted of problems
potentially before end-users notice an issue. The distributed
intelligence of Arrays provides this monitoring at multiple points
across the network, adding to the ability to isolate the problem and
expedite the resolution.
Connectivity is checked when you configure a server. If a newly
configured server is unreachable, you will be notified directly and a
Syslog entry is created. Configured servers are checked once per
Period which by default is 300 seconds (five minutes). Servers are
checked regardless of whether they are configured as IP addresses or
host names.
If a server becomes unreachable, a Syslog message is generated.
When the server again becomes reachable, another Syslog message is
generated.
b. PCI Audit Mode: Click On if you wish this Array to enforce PCI-DSS
restrictions. See the Xirrus Wireless Array Users Guide for more
information.
Management System
446 ConfiguringaWirelessArray
c. FIPS 140-2, Level 2 Security: Click On if you wish this Array to
enforce FIPS 140-2, Level 2 Security restrictions. See the Xirrus
Wireless Array Users Guide for more information.
8. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Global Settings
This window allows you to establish the security parameters for your wireless
network, including WEP, WPA, WPA2 and RADIUS authentication.
For additional information about wireless network security, refer to
Understanding Security on page 432.
Figure 267. Global Settings (Security)
Management System
ConfiguringaWirelessArray 447
Procedure for Configuring Network Security
1. RADIUS Server Mode: Choose the RADIUS server mode you want to
use, either Internal or External. Parameters for these modes are
configured in External Radius on page 451 and Internal Radius on
page 456.
WPA Settings
These settings are used if the WPA or WPA2 encryption type is selected on the
SSIDs >SSID Management window or the Express Setup window (on this
window, encryption type is set in the SSID Settings: Wireless Security field).
2. TKIP Enabled: Choose Yes to enable TKIP (Temporal Key Integrity
Protocol), or choose No to disable TKIP.
3. AES Enabled: Choose Yes to enable AES (Advanced Encryption
Standard), or choose No to disable AES. If both AES and TKIP are
enabled, the station determines which will be used.
4. WPA Group Rekey Enabled: The Group Key (Group Transient Key) is a
shared key among all stations connected to the same IAP, and is used to
secure multicast/broadcast traffic. It is not used for normal unicast traffic.
Group Key Rekey Time (below) controls how often this key is changed.
The default is No.
5. WPA Group Rekey Time (seconds): Enter a value to specify the group
rekey time (in seconds). The default is 100 (if enabled).
6. WPA Authentication: Select the type of authentication to be used, PSK or
EAP.
7. WPA Preshared Key / Verify Key: If you enabled PSK, enter a passphrase
here, then re-enter the passphrase to verify that you typed it correctly.

TKIP encryption does not support high throughput rates, per the IEEE
802.11n specification (see IEEE 802.11n Deployment Considerations
Improved MAC Throughput in the Xirrus Wireless Array Users Guide).
TKIP should never be used for WDS links on Arrays.
Management System
448 ConfiguringaWirelessArray
WEP Settings
These settings are used if the WEP encryption type is selected on the SSIDs >
SSID Management window or the Arrays Express Setup window (on this
window, encryption type is set in the SSID Settings: Wireless Security field).
8. Encryption Key 1 / Verify Key 1:
Key length is automatically computed based on the Encryption Key that
you enter
5 ASCII characters (10 hex) for 40 bits (WEP-64)
13 ASCII characters for (26 hex) 104 bits (WEP-128)
Encryption Key 1 / Verify Key 1: Enter an encryption key in ASCII or
hexadecimal.
Re-enter the key to verify that you typed it correctly. You may include
special ASCII characters, except for the double quote symbol ().
9. Encryption Key 2 to 4/ Verify Key 2 to 4/ Key Mode/Length (optional): If
desired, enter up to four encryption keys, in the same way that you
entered the first key.
10. Default Key: Choose which key you want to assign as the default key.
Make your selection from the pull-down list.
11. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.

WEP encryption does not support high throughput rates or features like
frame aggregation or block acknowledgments, per the IEEE 802.11n
specification (see IEEE 802.11n Deployment ConsiderationsImproved
MAC Throughput in the Xirrus Wireless Array Users Guide).
WEP should never be used for WDS links on Arrays.

After configuring network security, the configuration must be

applied to an SSID on the Array for the new functionality to take
effect.
Management System
ConfiguringaWirelessArray 449
Access Control List
This window allows you to enable or disable the use of the global Access Control
List (ACL), which controls whether a station with a particular MAC address may
associate to the Array. You may create station access control list entries and delete
existing entries, and control the type of list.
There is only one global ACL, and you may select whether its type is an Allow
List or a Deny List, or whether use of the list is disabled.
There is also a per-SSID ACL (see Per-SSID Access Control List on page 493).
If the same MAC address is listed in both the global ACL and in an SSIDs ACL,
and if either ACL would deny that station access to that SSID, then access will be
denied.
Figure 268. Access Control List
Procedure for Configuring Access Control Lists
1. Access Control List Type: Select Disable to disable use of the Access
Control List, or select the ACL type either Allow or Deny.
Allow: Only allows the listed MAC addresses to associate to the
Array. All others are denied.
Management System
450 ConfiguringaWirelessArray
Deny: Denies the listed MAC addresses permission to associate
to the Array. All others are allowed.
2. MAC Address: If you want to add a MAC address to the ACL, click the
Add button and enter the new MAC address in the dialog box, then click
OK. The MAC address is added to the ACL. You may use a wildcard (*)
for one or more digits to match a range of addresses. You may create up to
1000 entries.
3. Delete: You can delete the selected MAC addresses from this list by
clicking the Delete button.
4. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.

In addition to these lists, other authentication methods (for

example, RADIUS) are still enforced for users.
Management System
ConfiguringaWirelessArray 451
External Radius
This window allows you to define the parameters of an external RADIUS server
for user authentication. To set up an external RADIUS server, you must choose
External as the RADIUS server mode in Global Settings. Refer to Global
Settings on page 446.
Figure 269. External RADIUS Server
Management System
452 ConfiguringaWirelessArray
If you want to include user group membership in the RADIUS account
information for users, see Understanding Groups on page 496. User groups
allow you to easily apply a uniform configuration to a user on the Array.
About Creating User Accounts on the RADIUS Server
A number of attributes of user (wireless client) accounts are controlled by
RADIUS Vendor Specific Attributes () defined by Xirrus. For example, you would
use the VSA named Xirrus-User-VLAN if you wish to set the VLAN for a user
account in RADIUS. For more information about the RADIUS VSAs used by
Xirrus, see RADIUS Vendor Specific Attribute (VSA) for Xirrus in the Technical
Support Appendix of the Xirrus Wireless Array Users Guide.
Procedure for Configuring an External RADIUS Server
1. External RADIUS Primary Server: This is the external RADIUS server
that you intend to use as your primary server.
a. Host Name / IP Address: Enter the IP address or domain name of this
external RADIUS server.
b. Port Number: Enter the port number of this external RADIUS server.
The default is 1812.
c. Shared Secret / Verify Secret: Enter the shared secret that this
external RADIUS server will be using, then re-enter the shared secret
to verify that you typed it correctly.
2. External RADIUS Secondary Server (optional): If desired, enter an
alternative external RADIUS server. If the primary RADIUS server
becomes unreachable, the Array will failover to the secondary RADIUS
server (defined here).
a. Host Name / IP Address: Enter the IP address or domain name of this
external RADIUS server.

The shared secret that you define must match the secret used by the
external RADIUS server.
Management System
ConfiguringaWirelessArray 453
b. Port Number: Enter the port number of this external RADIUS server.
The default is 1812.
c. Shared Secret / Verify Secret: Enter the shared secret that this
external RADIUS server will be using, then re-enter the shared secret
to verify that you typed it correctly.
3. External RADIUS Settings: Define the settings used for RADIUS
Dynamic Authorization.
a. Enable External RADIUS: Enable or disable use of external RADIUS.
b. Timeout (seconds): Define the maximum idle time (in seconds)
before the external RADIUS servers session times out. The default is
600 seconds.
c. DAS Port: RADIUS Dynamic Authorization port. Some RADIUS
servers have the ability to contact the Array (referred to as an NAS,
see below) to terminate a user with a Disconnect Message (DM). Or
RADIUS may send a Change-of-Authorization (CoA) Message to the
Array to change a users privileges due to dynamically changing
session authorizations. RADIUS will use the DAS port on the Array
for this purpose. The default is port 3799.
d. DAS Event-Timestamp: The Event-Timestamp Attribute provides a
form of protection against replay attacks. If you select Required, both
the RADIUS server and the Array will use the Event-Timestamp
Attribute and check that it is current within the DAS Time Window.
If the Event-Timestamp is not current, then the DM or CoA Message
will be silently discarded.
e. DAS Time Window: This is the time window used with the DAS
Event-Timestamp, above.
f. NAS Identifier: From the point of view of a RADIUS server, the
Array is a client, also called a network access server (NAS). Enter the
NAS Identifier (IP address) that the RADIUS servers expect the Array
to use this is normally the IP address of the Arrays Gigabit1 port.
Management System
454 ConfiguringaWirelessArray
4. RADIUS Attribute Formatting Settings: Some RADIUS servers,
especially older versions, expect information to be sent to them in a
legacy format. These settings are provided for the unusual situation that
requires special formatting of specific types of information sent to the
RADIUS server. Most users will not need to change these settings.
a. Called-Station-Id Attribute Format: Define the format of the Called-
Station-Id RADIUS attribute sent from the ArrayBSSID:SSID
(default) or BSSID.
b. Station MAC Format: Define the format of the Station MAC
RADIUS attribute sent from the Arraylower-case or upper-case,
hyphenated or not. The default is lower-case, not hyphenated.
5. Accounting:
Note that RADIUS accounting start packets sent by the Array will include
the client station's Framed-IP-Address attribute.
a. Enable RADIUS Accounting: If you would like the Array to send
RADIUS Start, Stop, and Interim records to a RADIUS accounting
server, click the Yes button. The account settings appear, and must be
configured.
b. Accounting Interval (seconds): Specify how often Interim records are
to be sent to the server. The default is 300 seconds.
c. RADIUS Accounting Primary Server Host Name / IP Address:
Enter the IP address or domain name of the primary RADIUS
accounting server that you intend to use.
d. Port Number: Enter the port number of the primary RADIUS
accounting server. The default is 1813.
e. Primary Shared Secret / Verify Secret: Enter the shared secret that
the primary RADIUS accounting server will be using, then re-enter
the shared secret to verify that you typed it correctly.
f. RADIUS Accounting Secondary Server Host Name / IP Address
(optional): If desired, enter an IP address or domain name for an
Management System
ConfiguringaWirelessArray 455
alternative RADIUS accounting server. If the primary server becomes
unreachable, the Array will failover to this secondary server
(defined here).
g. Port Number: If using a secondary accounting server, enter its port
number. The default is 1813.
h. Shared Secret / Verify Secret: If using a secondary accounting server,
enter the shared secret that it will be using, then re-enter the shared
secret to verify that you typed it correctly.
6. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
456 ConfiguringaWirelessArray
Internal Radius
This window allows you to define the parameters for the Arrays internal
RADIUS server for user authentication. However, the internal RADIUS server
will only authenticate wireless clients that want to associate to the Array. This can
be useful if an external RADIUS server is not available. To set up the internal
RADIUS server, you must choose Internal as the RADIUS server mode in Global
Settings. Refer to Global Settings on page 446.
Figure 270. Internal RADIUS Server

Clients using PEAP may have difficulty authenticating to the Array using
the Internal RADIUS server due to invalid security certificate errors. To
prevent this problem, the user may disable the Validate Server Certificate
option on the station. Do this by displaying the stations wireless devices and
then displaying the properties of the desired wireless interface. In the
security properties, disable Validate server certificate. In some systems,
this may be found by setting the authentication method to PEAP and
changing the associated settings.
Management System
ConfiguringaWirelessArray 457
Procedure for Creating a New User
1. Click the Add button to create a new user entry. The Add Internal
RADIUS User dialog appears.
Figure 271. Add an Internal RADIUS User
2. User Name: Enter the name of the user that you want to authenticate to
the internal RADIUS server.
3. SSID Filter: (Optional) If you want to restrict this user to associating to a
particular SSID, choose an SSID from the pull-down list.
4. User Configuration Group: (Optional) If you want to make this user a
member of a previously defined user group, choose a group from the
pull-down list. This will apply all of the user groups settings to the user.
See Understanding Groups on page 496.
5. Password: (Optional) Enter a password for the user.
6. Confirm Password: (Optional) Retype the user password to verify that
you typed it correctly.
7. Click on the OK button to add the new user to the list.
8. If you want to delete a user, select it and click Delete.
9. If you want to modify a user entry, select it and click Edit.
10. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
458 ConfiguringaWirelessArray
Airwatch
Mobile Device Management (MDM) servers such as Airwatch enable you to
manage large-scale deployments of mobile devices. They may include capabilities
to handle tasks such as enrolling devices in your environment, configuring and
updating device settings over-the-air, enforcing security policies and compliance,
securing mobile access to your resources, and remotely locking and wiping
managed devices.
Figure 272. AirWatch Settings
Xirrus Arrays/APs (running ArrayOS Release 6.5 or higher) support the
AirWatch MDM, using an AirWatch API call to determine the status of a users
device and allow access to the wireless network only if the device is enrolled and
compliant with the policies of the service.
Management System
ConfiguringaWirelessArray 459
Individual SSIDs may be configured to require AirWatch enrollment and
compliance before a mobile device such as a smartphone or tablet is admitted to
the wireless network. The Array uses the AirWatch API with the settings below to
request that AirWatch check whether the mobile device is enrolled and compliant
with your wireless policies.
Before configuring AirWatch settings on the Array, you must have an AirWatch
account, already set up with your organizations compliance policies and other
configuration as required by AirWatch.
The Array settings entered on this page are mostly taken from AirWatch. Once
you have entered these settings, your users will be constrained to follow a set of
steps to access the wireless network, as described in User Procedure for
Wireless Access on page 460.
Procedure for Managing AirWatch
If you have configured the Mobile Device Management setting on one or more
SSIDs to use AirWatch, then the API specified below will be used to determine
the admissibility of a mobile device requesting a connection to the wireless
network.
1. API URL/Hostname: Obtain this from your AirWatch servers System /
Advanced / Site URLs page. Copy the REST API URL string into this
field. This specifies the AirWatch API that the Array will call to determine
the enrollment and compliance status of a mobile device attempting to
connect to the Array. The steps that the user will need to take are
described in User Procedure for Wireless Access on page 460.
2. API Username: Enter the user name for your account on the AirWatch
server.
3. API Password/Verify Password: Enter the password for your account on
the AirWatch server.
4. API Key: Obtain this from your AirWatch server. Go to the System /
Advanced / API / REST page, General tab, and copy the API Key string
into this field. The key is required for access to the API.
Management System
460 ConfiguringaWirelessArray
5. API Timeout: (seconds) If AirWatch does not respond within this many
seconds, the request fails.
6. API Poll Period: (seconds) Mobile device enrollment and compliance
status will be checked via polling at this interval. Note that there may
thus be a delay before the mobile device will be admitted.
7. API Access Error Action: Specify whether or not to allow access if
AirWatch fails to respond. The default is to Block access.
8. Redirect URL: Obtain this from your AirWatch server. Go to the System /
Advanced / Site URLs page, and copy the Enrollment URL string into
this field. When a mobile device that is not currently enrolled with
AirWatch attempts to connect to the Array, the device displays a page
directing the user to install the AirWatch agent and go to the AirWatch
enrollment page. Note that Android devices will need another form of
network access (i.e. cellular) to download the agent, since un-enrolled
devices will not have access to download it via the Array. See User
Procedure for Wireless Access on page 460 for more details.
9. You must configure the Mobile Device Management setting on one or
more SSIDs to use AirWatch, as described in Procedure for Managing
General Settings (Step 12 on page 474).
User Procedure for Wireless Access
1. A user attempts to connect a mobile device to an SSID that uses AirWatch.
2. The device will authenticate according to the SSIDs authentication
settings (Open, Radius MAC, 802.1x).
3. The user browses to any destination on the Internet.
The Array asks the user to wait while it checks device enrollment and
compliance status by querying the AirWatch API with the device MAC
address.
Management System
ConfiguringaWirelessArray 461
4. If AirWatch responds that the device is enrolled and compliant, the
device will be allowed into the network. The device will be considered
compliant if AirWatch finds that the device does not violate any
applicable policies for that device. (If no policies are assigned to the
device in AirWatch, then the device is compliant by default.)
5. If the device is not enrolled, all user traffic will be blocked, except that
HTTP traffic is redirected to an intermediate page on the Array that tells
the user to download and install the AirWatch agent. The page displays a
link to the AirWatch-provided device enrollment URL. This link is a pass-
though that allows the user to go through the enrollment process. The
user will need to enter your organizations AirWatch Group ID and
individual account credentials when requested.
Once the agent is installed, the user must start again at Step 1.
6. If the device is enrolled with AirWatch but not compliant with applicable
policies, all traffic will be blocked as in Step 5 above, and the HTTP traffic
will be redirected to an intermediate page on the Array that tells the user
which policies are out of compliance.
This page contains a button for the user to click when the compliance
issues have been corrected. This button causes AirWatch to again check
device compliance. The user's browser is redirected to a wait page until
the Array has confirmed compliance with AirWatch. The users browser

Device enrollment and compliance status will be checked via polling so there
may be a delay before the device will be allowed in. That delay will depend on
the API Polling Period setting.

Android devices must go to the PlayStore to install the agent BEFORE they
can go through the enrollment process. This means un-enrolled devices need
another form of network access (i.e., cellular or an unrestricted SSID) to
download this agent, as they are not permitted access to the PlayStore.
Once the agent is installed, the user must start again at Step 1.
Management System
462 ConfiguringaWirelessArray
is then redirected to a page announcing that the device is now allowed
network access.
7. If the Array is unable to access AirWatch to obtain enrollment and
compliance status (for example, due to bad credentials, timeout, etc.),
device access to the network will be granted according to the API Access
Error setting (Allow or Block). If this field is set to Block, traffic will be
blocked as in Step 5 above and HTTP traffic will be redirected to an
informational page that informs the user that AirWatch cannot be
contacted at this time and advises the user to contact the network
administrator. If this field is set to Allow, then the device will be allowed
network access.
Management System
ConfiguringaWirelessArray 463
SSIDs
This window allows you to manage SSID (Service Set IDentifier) assignments.
You may add or delete SSIDs. Choose the Currently selected SSID to view or
change an entrys settings.
Figure 273. SSIDs
Settings are organized into five sections, and you can expand one section at a time
to manage that group of settings:
SSID ManagementGeneral Settingsincludes whether or not an SSID
is enabled and visible on the network, which bands it is available on,
which wired VLAN it is associated with, DHCP pools defined per SSID,
and other settings.
SSID ManagementAuthentication/Encryptionspecifies the type of
authentication and encryption, and whether to use global security
settings or specify individual settings for the SSID here.
SSID ManagementLimitsspecifies station limits and operating
periods for the SSID.
Management System
464 ConfiguringaWirelessArray
SSID ManagementTraffic Shapingspecifies how much traffic is
allowed, per SSID and station.
SSID ManagementCaptive Portalspecifies settings for a captive
portal (formerly called WPR) for logins.
For information to help you understand SSIDs and how multiple SSIDs are
managed by the wireless Array, go to Understanding SSIDs on page 464. For a
description of how QoS operates on the Array, see Understanding QoS Priority
on the Wireless Array on page 467.
SSIDs are managed with the following windows:
SSID Management on page 471
Per-SSID Access Control List on page 493
Active IAPs on page 495
SSIDs are discussed in the following topics:
Understanding SSIDs on page 464
High Density 2.4G EnhancementHoneypot SSID on page 465
Understanding QoS Priority on the Wireless Array on page 467
Understanding SSIDs
The SSID (Service Set Identifier) is a unique identifier that wireless networking
devices use to establish and maintain wireless connectivity. Multiple access points
on a network or sub-network can use the same SSIDs. SSIDs are case-sensitive
and can contain up to 32 alphanumeric characters (do not include spaces when
defining SSIDs).
Multiple SSIDs
A BSSID (Basic SSID) refers to an individual access point radio and its associated
clients. The identifier is the MAC address of the access point radio that forms the
BSS. A group of BSSs can be formed to allow stations in one BSS to communicate
to stations in another BSS via a backbone that interconnects each access point.
The Extended Service Set (ESS) refers to the group of BSSIDs that are grouped
together to form one ESS. The ESSID (often referred to as SSID or wireless
Management System
ConfiguringaWirelessArray 465
network name) identifies the Extended Service Set. Clients must associate to a
single ESS at any given time. Clients ignore traffic from other Extended Service
Sets that do not have the same SSID.
Legacy access points typically support one SSID per access point. Wireless Arrays
support the ability to define and use multiple SSIDs simultaneously.
Using SSIDs
The creation of different wireless network names allows system administrators to
separate types of users with different requirements. The following policies can be
tied to an SSID:
The wireless security mode needed to join this SSID.
The wireless Quality of Service (QoS) desired for this SSID.
The wired VLAN associated with this SSID.
As an example, one SSID named accounting might require the highest level of
security, while another named guests might have low security requirements.
Another example may define an SSID named voice that supports voice over
Wireless LAN phones with the highest Quality of Service (QoS) definition. This
SSID might also forward traffic to specific VLANs on the wired network.
High Density 2.4G EnhancementHoneypot SSID
Some situations pose problems for all wireless APs. For example, iPhones will
remember every SSID and flood the airwaves with probes, even when the user
doesnt request or desire this behavior. In very high density deployments, these
probes can consume a significant amount of the available wireless bandwidth.
The Array offers a feature targeting this problema honeypot SSID. Simply
create an SSID named honeypot (lower-case) on the Array, with no encryption or
authentication (select None/Open). Once this SSID is created and enabled, it will
respond to any station probe looking for a named open SSID (unencrypted and
unauthenticated) that is not configured on the Array. It will make the station go
through its natural authentication and association process.
Management System
466 ConfiguringaWirelessArray
The following SSIDs are excluded from being honeypotted:
Explicitly whitelisted SSIDs. See SSID ManagementHoneypot
Service Whitelist on page 492.
SSIDs that are encrypted and/or authenticated.
SSIDs that are configured on this Array, whether or not they are enabled.
Traffic for a station connected to the honeypot SSID may be handled in various
ways using other Array features:
it may be directed to a captive portal (web page redirect) to display a
splash page or offer the user the opportunity to sign in to your service
(see SSID ManagementCaptive Portal on page 478);
it may be filtered (see Filters on page 549);
or it may be dead-ended by defining a specific dead-end VLAN on the
honeypot SSID to trap stations (see VLAN on page 409).
Use the honeypot feature carefully as it could interfere with legitimate SSIDs and
prevent clients from associating to another available network. You may define a
whitelist of allowed SSIDs which are not to be honeypotted. See SSID
ManagementHoneypot Service Whitelist on page 492.
Management System
ConfiguringaWirelessArray 467
Understanding QoS Priority on the Wireless Array
Mapping to
Traffic Class
Four Transmit
Queues
Per queue
channel access
Application Data
Voice
Data
Video
Data
Background
Data
Best Effort
Data
IAP (Transmit)
Highest
Priority
Lowest
Priority
Figure 274. Four Traffic Classes
The wireless Arrays Quality of Service Priority feature (preamble) allows traffic
to be prioritized according to your requirements. For example, you typically
assign the highest priority to voice traffic, since this type of traffic requires delay
to be under 10 ms. The Array has four separate queues for handling wireless
traffic at different priorities, and thus it supports four traffic classes (QoS levels).
Figure 275. Priority LevelIEEE 802.1p (Layer 2)

For a discussion of implementing Voice over Wi-Fi on the Array, see the
Xirrus Voice over Wireless Application Note in the Xirrus Resource
Center.
Management System
468 ConfiguringaWirelessArray
IEEE802.1p uses three bits in an Ethernet frame header to define eight priority
levels at the MAC level (Layer 2) for wired networks. Each data packet may be
tagged with a priority level, i.e., a user priority tag. Since there are eight possible
user priority levels and the Array implements four wireless QoS levels, user
priorities are mapped to QoS as described below.
Figure 276. Priority LevelDSCP (DiffServ - Layer 3)
DSCP (Differentiated Services Code Point or DiffServ) uses 6 bits in the IPv4 or
IPv6 packet header, defined in RFC2474 and RFC2475. The DSCP value classifies
a Layer 3 packet to determine the Quality of Service (QoS) required. DSCP
replaces the outdated Type of Service (TOS) field.
The description below describes how both of these priority levels are mapped to
the Arrays four traffic classes.
End-to-End QoS Handling
Wired QoS - Ethernet Port:
Ingress: Incoming wired packets are assigned QoS priority based on their
SSID and 802.1p tag (if any), as shown in the table below. This table
follows the mapping recommended by IEEE802.11e.
Management System
ConfiguringaWirelessArray 469

Egress: Outgoing wired packets are IEEE 802.1p tagged at the Ethernet
port for upstream traffic, thus enabling QoS at the edge of the network.
FROM
Priority Tag
802.1p (Wired)
TO
Array QoS
(Wireless)
Typical Use
0 0 (Lowest
priority)
Best Effort
1 1 Background explicitly designated as
low-priority and non-delay sensitive
2 1 Spare
3 0 Excellent Effort
4 2 Controlled Load
5 2 Video
6 3 Voice - requires delay <10ms
7 (Highest
priority)
3 (Highest
priority)
Network control
FROM
Array QoS (Wireless)
TO
Priority Tag 802.1p (Wired)
1 (Lowest priority) 1
0 0
2 (Default) 5
3 (Highest priority) 6
Management System
470 ConfiguringaWirelessArray
Wireless QoS - IAPs:
Each SSID can be assigned a separate QoS priority (i.e., traffic class) from
0 to 3, where 3 is highest priority and 2 is the default. See SSID
Management on page 471. If multiple SSIDs are used, packets from the
SSID with higher priority are transmitted first.
The Array supports IEEE802.11e Wireless QoS for downstream traffic.
Higher priority packets wait a shorter time before gaining access to the
air and contend less with all other 802.11 devices on a channel.
How QoS is set for a packet in case of conflicting values:
a. If an SSID has a QoS setting, and an incoming wired packets user
priority tag is mapped to a higher QoS value, then the higher QoS
value is used.
b. If a group or filter has a QoS setting, this overrides the QoS value
above. See Groups on page 496, and Filters on page 549.
c. Voice packets have the highest priority (see Voice Support, below).
d. If DSCP to QoS Mapping Mode is enabled, the IP packet is mapped
to QoS level 0 to 3 as specified in the DSCP Mappings table. This
value overrides any of the settings in cases a to c above.
In particular, by default:
DSCP 8 is set to QoS level 1.
DSCP 40 is typically used for video traffic and is set to QoS
level 2.
DSCP 48 is typically used for voice traffic and is set to QoS
level 3the highest level
All other DSCP values are set to QoS level 0 (the lowest level
Best Effort).
Packet Filtering QoS classification
Filter rules can be used to redefine the QoS priority level to override
defaults. See Filter Management on page 551. This allows the QoS
priority level to be assigned based on protocol, source, or destination.
Management System
ConfiguringaWirelessArray 471
Voice Support
The QoS priority implementation on the Array give voice packets the
highest priority to support voice applications.
SSID Management
This window manages SSIDs (create, edit and delete), assigns security parameters
and VLANs on a per SSID basis, and configures the Captive Portal (Web Page
RedirectWPR) functionality.
Figure 277. SSID Management
This page has the following sections. Click a section heading to expand that
section.
SSID ManagementGeneral Settings on page 472
SSID ManagementAuthentication/Encryption on page 474
SSID ManagementLimits on page 476
SSID ManagementTraffic Shaping on page 477
Management System
472 ConfiguringaWirelessArray
SSID ManagementCaptive Portal on page 478
SSID ManagementHoneypot Service Whitelist on page 492
When done, click the Apply Config button near the top of the window to apply
these changes to the Array. To make these changes permanent, check Save to
flash before using the Apply Config button.
SSID ManagementGeneral Settings
This section manages all SSID settings other than those related to security, station
limits, traffic shaping, and captive portal setup.
Procedure for Managing General Settings
1. To create a new SSID, enter its name to the right of the Add SSID button,
and click the button. (Figure 277)) The SSID Name may only consist of the
characters A-Z, a-z, 0-9, dash, and underscore. You may create up to 16
SSIDs.
2. Currently selected SSID: The drop-down list shows all currently defined
SSIDs. Click any SSID in the list to select it. All the rest of the settings
shown and modified on this page will apply to that SSID. When you
create a new SSID, the SSID name is added to the list.
If you wish to delete the currently selected SSID, click Delete selected
SSID.
3. Enabled: Check this box to activate this SSID or clear it to deactivate it.
4. Broadcast: Check this box to make the selected SSID visible to all clients
on the network. Although the wireless Array will not broadcast SSIDs
that are hidden, clients can still associate to a hidden SSID if they know
the SSID name to connect to it. Clear this box if you do not want this SSID
to be visible on the network.
5. Band: Choose which wireless band the SSID will be beaconed on. Select
either 5 GHz 802.11an, 2.4 GHz 802.11bgn or Both.
6. VLAN Number: (Optional) From the pull-down list, select a VLAN that
you want this traffic to be forwarded to on the wired network.
Management System
ConfiguringaWirelessArray 473
7. QoS: (Optional) Select a value in this field for QoS (Quality of Service)
priority filtering. The QoS value must be one of the following:
0 The lowest QoS priority setting, where QoS makes its best effort
at filtering and prioritizing data, video and voice traffic without
compromising the performance of the network. Use this setting in
environments where traffic prioritization is not a concern.
1 Medium, with QoS prioritization aggregated across all traffic
types.
2 High, normally used to give priority to video traffic.
3 The highest QoS priority setting, normally used to give priority to
voice traffic.
The QoS setting you define here will prioritize wireless traffic for this
SSID over other SSID traffic, as described in Understanding QoS
Priority on the Wireless Array on page 467. The default value for this
field is 2.
8. DHCP Pool: If you want to associate an internal DHCP pool to this SSID,
choose the pool from the pull--down list. An internal DHCP pool must be
created before it can be assigned. To create an internal DHCP pool, go to
DHCP Server on page 427.
9. Filter List: If you wish to apply a set a filters to this SSIDs traffic, select
the desired Filter List. See Filters on page 549.
10. Xirrus Roaming: For this SSID, select whether to enable fast roaming
between IAPs or Arrays at L2&L3 (Layer 2 and Layer 3), at L2 (Layer 2
only), or disable roaming (Off). You may only select fast roaming at
Layers 2 and 3 if this has been selected in Global Settings (IAP). See
Understanding Fast Roaming on page 503.
11. Fallback: Network Assurance checks network connectivity for the Array.
When Network Assurance detects a failure, perhaps due to a bad link or
WDS failure, if Fallback is set to Disable the Array will automatically
disable this SSID. This will disassociate current clients, and prevent new
clients from associating. Since the Arrays network connectivity has
Management System
474 ConfiguringaWirelessArray
failed, this gives clients a chance to connect to other, operational parts of
the wireless network. No changes are made to WDS configuration. See
Step a on page 445 for more information on Network Assurance.
12. Mobile Device Management (MDM): If you are an AirWatch customer
and wish to have AirWatch manage mobile device access to the wireless
network on this SSID, select AirWatch from the drop-down list. Before
selecting this option, you must configure your Airwatch settings. See
Airwatch on page 458.
SSID ManagementAuthentication/Encryption
This section manages all SSID settings related to security.
Figure 278. SSID Management: Authentication/Encryption
Note that you cannot use MDM and Captive Portal on the same SSID.
Management System
ConfiguringaWirelessArray 475
Procedure for Managing Authentication/Encryption
1. Encryption/Authentication: only valid combinations are listed.
The following authentication options are available:
Open: This option provides no authentication and is not
recommended.
RADIUS MAC: Uses an external RADIUS server to authenticate
stations onto the wireless network, based on the users MAC address.
Accounting for these stations is performed according to the
accounting options that you have configured specifically for this SSID
or globally (see Step 2 below).
802.1x: Authenticates stations onto the wireless network via a
RADIUS server using 802.1x with EAP. The RADIUS server can be
internal (provided by the wireless Array) or external.
From the pull-down list, choose the encryption that will be required
specific to this SSID either None, WEP, WPA, WPA2 or WPA-Both. The
None option provides no security and is not recommended; WPA2
provides the best practice Wi-Fi security.
Each SSID supports only one encryption type at a time (except that WPA
and WPA2 are both supported on an SSID if you select WPA-Both). If you
need to support other encryption types, you must define additional
SSIDs. The encryption standard used with WPA or WPA2 is selected in
the Security>Global Settings window (page 446). For an overview of the
security options, see Understanding Security on page 432.

If this SSID is on a VLAN, the VLAN must have management turned on in

order to pass CHAP authentication challenges from the client station to the
RADIUS server.

XN model Arrays cannot use the SSID-specific WEP keys specified in this
step. They can only use the global WEP keys specified in the Global
Settings window.
Management System
476 ConfiguringaWirelessArray
2. Global: Check the checkbox if you want this SSID to use the security
settings established at the global level (refer to Global Settings on
page 446). Clear the checkbox if you want the settings established here to
take precedence. Additional sections will be displayed to allow you to
configure encryption, RADIUS, and RADIUS accounting settings. The
WPA Configuration encryption settings have the same parameters as
those described in Procedure for Configuring Network Security on
page 447. The external RADIUS and accounting settings are configured in
the same way as for an external RADIUS server (see Procedure for
Configuring an External RADIUS Server on page 452). External
RADIUS servers may be specified using IP addresses or domain names.
SSID ManagementLimits
This section manages station limits for this SSID. See Group Limits on page 501
for a discussion of the interaction of SSID limits and group limits. To eliminate
confusion, we recommend that you configure one set of limits or the other, but not
both.
Figure 279. SSID Management: Limits
Management System
ConfiguringaWirelessArray 477
Procedure for Managing Limits
1. Stations: Enter the maximum number of stations allowed on this SSID.
This step is optional. Note that station limits may be set in several
placessee Step 13 on page 512 in Global Settings (IAP) for details. If
multiple limits are set, all will be enforced. As soon as any limit is
reached, no new stations can associate until some other station has
terminated its association.
2. Days Active: Choose Everyday if you want this SSID to be active every
day of the week, or select only the specific days that you want this SSID to
be active. Days that are not checked are considered to be the inactive
days.
3. Time Active: Choose Always if you want this SSID active without
interruption, or enter values in the Time On and Time Off fields to limit
the time that this SSID is active.
SSID ManagementTraffic Shaping
This section manages traffic limits for this SSID.
Figure 280. SSID Management: Traffic Shaping
Management System
478 ConfiguringaWirelessArray
Procedure for Managing Traffic Shaping
1. Overall Traffic: Choose Unlimited if you do not want to place a
restriction on the traffic for this SSID, or enter a value in the Packets/Sec
field or the Kbps field to force a traffic restriction. If you set both values,
the Array will enforce the limit it reaches first.
2. Traffic per Station: Choose Unlimited if you do not want to place a
restriction on the traffic per station for this SSID, or enter a value in the
Packets/Sec field or the Kbps field to force a traffic restriction. If you set
both values, the Array will enforce the limit it reaches first.
SSID ManagementCaptive Portal
This section manages captive portal settings for this SSID, and includes a
WYSIWYG (What You See Is What You Get) HTML editor for creating a splash
page or login page for the portal.
Figure 281. SSID Management: Captive Portal (Internal Login page)
Captive Portal (formerly called WPRWeb Page Redirect): This feature may be
used to provide a portal for an alternate mode of authentication, or to simply
display a splash screen when a user first associates to the wireless network. After
that, it can optionally redirect the user to a landing page at an alternate URL.
Example applications are:
Management System
ConfiguringaWirelessArray 479
As an authentication device requiring a user to enter a username and
password (and possibly, a method of payment) before accessing network
resources.
To inform the user about the Terms and Conditions of using the network
before allowing access.
To intercept a web page request by the client device and redirect to a
specific web page before accessing the network.
You may specify a white lista list of Internet destinations that stations can
access without having to pass the captive portal first. For example, you may make
your organization's public web site accessible without redirection to the captive
portal. See White List Configuration for Captive Portal on page 491.
Procedure for Managing Captive Portal Settings
Enable a captive portal by setting the Server type to any choice other than
Disabled. The SSID Management window displays additional fields to be
configured, based on your selection. The captive portal HTML editor is displayed,
when needed, to create a splash or login page with a WYSIWYG editor.
Figure 282. Captive Portal Server Types

When using a captive portal, it is particularly important to adhere to the

SSID naming restrictions detailed in Step 1 on page 472.
Management System
480 ConfiguringaWirelessArray
If enabled, the captive portal displays a splash or login page when a user
associates to the wireless network and opens a browser to any URL (provided the
URL does not point to a resource directly on the users machine). The user-
requested URL is captured, the users browser is redirected to the specified splash
or login page, and then the browser is redirected either to your specified landing
page, if any, or else back to the captured URL. The landing page may be specified
for a user group as well. See Group Management on page 498. Note that if you
change the management HTTPS port, captive portal uses that port, too. See
HTTPS on page 443.
When users roam between Arrays, their captive portal authentication will follow
them so that re-authentication is not required.
When you are done making changes to captive portal settings, save the changes to
the Array by clicking Apply Config with Save to flash enabled.
You may select among five different modes for use of the Captive Portal feature,
each displaying a different set of parameters that must be entered.
Internal Splash page on page 481
Internal Login page on page 482
External Login page on page 484
External Splash page on page 485
Landing Page Only on page 486
After you specify the captive portal, you may specify a white list of Internet
destinations that may be accessed without passing through the captive portal
flowsee White List Configuration for Captive Portal on page 491.
Management System
ConfiguringaWirelessArray 481
Internal Splash page
Figure 283. Captive PortalInternal Splash Page
This option displays a splash page instead of the first user-requested
URL. The splash page files reside on the Array. Create the splash page
using the captive portal editor. The HTML editor can add text and images
and insert a Proceed button. See Editing an Internal Login or Internal
Splash Page on page 486.
To use an internal splash page, set Server to Internal Splash. Enter a
value in the Timeout field to define how many seconds the splash screen
is displayed before timing out, or select Never to prevent the page from
timing out automatically (be sure to add a Proceed button in this case
Figure 289 on page 488). After the splash page, the user is redirected to
the captured URL. If you want the user redirected to a specific landing
page instead, enter its address in Landing Page.
If you have a CSS file defining the styles for the splash page, use the Style
Sheet field to specify it. Select one of the previously uploaded CSS files
from the drop-down list, or click the Import button to select the desired
CSS file and upload it to the XMS server. You may remove files from the
list with the Delete button. Only one CSS file may be applied to each
captive portal, and the same file may be used by different portals. The file
Management System
482 ConfiguringaWirelessArray
must end in a .css extension and be under 1 MB. The HTML files
uploaded to an Array for the captive portal will include the CSS file.
Internal Login page
Figure 284. Captive PortalInternal Login Page
This option displays a login page instead of the first user-requested URL.
Create the login page (which resides on the Array) using the captive
portal editor. The HTML editor can add text and images and insert a
section containing fields to capture user credentials, or you may insert a
default login page and customize it. See Editing an Internal Login or
Internal Splash Page on page 486.
To set up internal login, set Server to Internal Login. If you have a CSS
file defining the styles for the login page, use the Style Sheet field to
specify it. Select one of the previously uploaded CSS files from the drop-
down list, or click the Import button to select the desired CSS file and
upload it to the XMS server. You may remove a CSS file from the list by
using the Delete button. Only one CSS file may be applied to each captive
portal, and the same file may be used by different portals. The file must
end in a .css extension and be under 1 MB. The HTML files uploaded to
an Array for the captive portal will include the CSS file.
Management System
ConfiguringaWirelessArray 483
Check the HTTPS checkbox for a secure login, or uncheck it to use HTTP.
Select the RADIUS Authentication Type to use for the client. This is the
protocol used for authentication of users, CHAP (the default), MS-CHAP,
or PAP.
PAP (Password Authentication Protocol), is a simple protocol. PAP
transmits ASCII passwords over the network in the clear
(unencrypted) and is therefore considered insecure.
CHAP (Challenge-Handshake Authentication Protocol) is a more
secure Protocol. The login request is sent using a one-way hash
function.
MS-CHAP is the Microsoft version of Challenge-Handshake
Authentication Protocol.
The user name and password are obtained by the login page, and
authentication occurs according to your configured authentication
information (see SSID ManagementAuthentication/Encryption on
page 474).
After authentication, the browser is redirected back to the captured URL.
If you want the user redirected to a specific landing page instead, enter its
address in Landing Page.

Both the Internal Login and External Login options of Captive Portal
perform authentication using your configured RADIUS servers.
Management System
484 ConfiguringaWirelessArray
External Login page
This option redirects the user to a login page on an external web server
for authentication, instead of the first user-requested URL. Login
information (user name and password) must be obtained by that page,
and returned to the Array for authentication.
Figure 285. Captive PortalExternal Login Page
Authentication occurs according to your configured authentication
information (see SSID ManagementAuthentication/Encryption on
page 474). After authentication, the browser is redirected back to the
captured URL. If you want the user redirected to a specific landing page
instead, enter its address in Landing Page.
To set up external login page usage, set Server to External Login. Enter
the URL of the external web server in Redirect URL, and enter that
servers shared secret in Redirect Secret.
Management System
ConfiguringaWirelessArray 485
External Splash page
This option displays a splash page instead of the first user-requested
URL. The splash page files reside on an external web server.
Figure 286. Captive PortalExternal Splash Page
To set up external splash page usage, set Server to External Splash. Enter
the URL of the external web server in Redirect URL, and enter that
servers shared secret in Redirect Secret.
After the splash page, the user is redirected to the captured URL. If you
want the user redirected to a specific landing page instead, enter its
address in Landing Page.
Management System
486 ConfiguringaWirelessArray
Landing Page Only
This option redirects the user to a specific landing page. If you select this
option, enter the desired address in Landing Page URL.
Figure 287. Captive PortalLanding Page Only
Editing an Internal Login or Internal Splash Page
If you set the Captive Portal Server to Internal Login or Internal Splash, the
captive portal editor appears. Use it to create the captive portal page displayed
when a user associates to this SSID.
The captive portal editor initially displays the current splash or login page that is
defined on the Array, if any. If you switch SSIDs, your splash or login page will be
automatically saved in a temporary workspacehowever, we recommend that
you work on the page until you are satisfied with it, and then apply it to the Array
as described below to save the page. Otherwise, if you leave The Configuration
Tab, your changes will be lost.
A note above the captive portal editor will inform you that Arrays running
ArrayOS versions older than Release 6.6.0 must be rebooted for changes in the
splash or login page to take effect. When you are done editing the captive portal
page, save the changes to the Array by clicking Apply Config with Save to flash
enabled. If a reboot is required, it does not occur automaticallyyou must initiate
it yourself. See The Configure Arrays Toolbar on page 107.
The captive portal editor is an HTML editor. Since it is a WYSIWYG editor (What
You See Is What You Get), it shows you exactly the way the page will appear.
Management System
ConfiguringaWirelessArray 487

Figure 288. Using the Captive Portal Editor
The rows of buttons at the top of the editor provide the editing features. Many of
these buttons provide text editing functions that will be familiar, especially for
users of Microsoft Word style editors. Other buttons add images, work with
layers, or allow you to edit HTML source. Some of the more powerful buttons are
highlighted in Figure 289, below. Two buttons are tailored especially for the
captive portal pagethey insert special purpose buttons on the captive portal
page or create default login or splash pages.
Cancel All Changes (since last save)
New Document (clear page)
Default Splash or Login Page
Add a Proceed Button (for Internal Splash page only)
Insert/Edit Image
Edit HTML Source
Add Credentials Block (for Internal Login page only)
Management System
488 ConfiguringaWirelessArray

Figure 289. Captive Portal Editor Buttons
To use the Captive Portal Editor
Hover the mouse over any button to display a tool tip describing the
buttons purpose.
Use the Default Splash or Login Page button if you wish to use a default
page. If your portal server type is Internal Splash, then the default page
will have a Proceed button. If your portal page type is Internal Login,
then the default page will have fields for entering Username and
Password. You may delete the Xirrus logo. Use the Insert/Edit Image
button as described below to add your own logo at the cursor location. If
you wish to add content before or after the default page, you may use the
Edit HTML Source button described below.
To create your own page instead, start typing in the blank display portion
of the window, then use any of the provided text editing buttons to
format and edit the text.
Paste an image in place at the current cursor location, or click the Insert/
Edit Image button to open the Insert/Edit Image dialog. Use the
Browse button to open the Captive Portal Image Selection dialog.
Select one of the previously uploaded images and click OK, or click
Management System
ConfiguringaWirelessArray 489
Import Image to browse to the desired image and upload it to the XMS
server. The image is inserted as a reference rather than directly inline. The
HTML files uploaded to an Array for the captive portal will include the
files for embedded images. Images may be in jpg, gif, or png format, and
the size may be up to 2 MB. Click Delete Image if you wish to remove the
selected image from the XMS server.
Figure 290. Captive Portal Image Selection
When you return to the Insert/Edit Image dialog, you may enter an
Image Description to present if the image cannot be displayed when
viewed by the user. If you enter a Title, it will pop up like a tool tip when
the user hovers the mouse over the image.
The Appearance and Advanced tabs allow you to change other attributes
of the image as displayed to the user. For example, the Appearance tab
allows you to specify a style from your Style Sheet (.css), if you are using
one, for the image display. Click Insert or Update at the lower left when
done.
Click the image and drag the handles to resize.
Make changes directly in the HTML by using the Edit HTML Source
button. In the HTML Source Editor window, make the desired changes. If
Management System
490 ConfiguringaWirelessArray
you have HTML from another source that you want to use, you may
paste it into this window. Click Update at the lower left when done. There
is also an Edit CSS Style button to tweak many aspects of text display.
The Insert/Edit Attributes button allows you to add HTML attributes
and/or JavaScript events to the content on your page.
Add necessary controls to the portal page using the Add a Proceed
Button/ Add Credentials Block button. If your portal page type is
Internal Splash and your Timeout setting is Never, then this will add a
Proceed button to your portal at the current line (at the left of the
window). If your portal page type is Internal Splash and the Timeout
setting is a non-zero number of seconds, then the Add a Proceed Button
icon will not appearthe splash page will automatically close after the
specified timeout and a proceed button is not needed.
If your portal page type is Internal Login, then the Credentials Block
button will add fields for entering Username and Password.
There are Undo and Redo buttons. The Cancel All Changes button
reverts the page to the last version that you saved. The New Document
button restores you to a blank page.
Remember that when you are done making changes to the internal splash
or login page, you must click Apply Config with Save to flash enabled.
Then the Array must be explicitly rebooted for the changes to take effect.
You may find more information on using the features of the captive portal
editor here.
Management System
ConfiguringaWirelessArray 491
White List Configuration for Captive Portal
On a per-SSID basis, the white list allows you to specify Internet destinations that
stations can access without first having to pass the captive portal login/splash
page. Note that a white list may be specified for a user group as well. See Group
Management on page 498.
Figure 291. White List Configuration for Captive Portal
To add a web site to the white list for this SSID, enter it in the provided field, then
click Create. You may enter an IP address or a domain name. Up to 32 entries may
be created.
Example white list entries:
Hostname: www.yahoo.com (but not www.yahoo.com/abc/def.html)
Wildcards are supported: *.yahoo.com
IP address: 121.122.123.124
Some typical applications for this feature are:
to add allowed links to the captive portal page
to add a link to terms of use that may be hosted on another site
to allow embedded video on captive portal page
Note the following details of the operation of this feature:
The list is configured on a per-SSID basis. You must have captive portal
enabled for the SSID to see this section of the SSID Management page.
When a station that has not yet passed the captive portal login/splash
page attempts to access one of the white-listed addresses, it will be
allowed access to that site as many times as requested.
Management System
492 ConfiguringaWirelessArray
The station will still be required to pass through the configured captive
portal flow for all other Internet addresses.
The white list will work against all traffic -- not just http or https
Indirect access to other web sites is not permitted. For example, if you
add www.yahoo.com to the white list, you can see that page, but not all
the ads that it attempts to display.
The white list feature does not cause traffic to be redirected to the white
list addresses.
SSID ManagementHoneypot Service Whitelist
This section only appears if you have created an SSID named honeypot. You may
define a whitelist of allowed SSIDs which are not to be honeypotted, as described
in High Density 2.4G EnhancementHoneypot SSID on page 465. Type in
each SSID name, and click Add to add it to the whitelist. Up to 50 SSIDs may be
listed. The SSID names entered in this list are not case-sensitive.
Figure 292. SSID Management: Honeypot Whitelist
You may use the * character as a wildcard to match any string at this position.
For example, xir* matches any string that starts with XIR or xir. You may use a ?
as a wildcard to match a single character by surrounding the SSID name in
Management System
ConfiguringaWirelessArray 493
quotes. For example, xirru? will match any six-character long string that starts
with xirru (again, the match is not case-sensitive). If you do not use a wildcard,
then the SSID name entered must be matched exactly in order to be whitelisted
(except that case is not considered).
Use the honeypot feature carefully as it could interfere with legitimate SSIDs.
Per-SSID Access Control List
This window allows you to enable or disable the use of the per-SSID Access
Control List (ACL), which controls whether a station with a particular MAC
address may associate to this SSID. You may create access control list entries and
delete existing entries, and control the type of list.
Figure 293. Per-SSID Access Control List
There is one ACL per SSID, and you may select whether its type is an Allow List
or a Deny List, or whether use of this list is disabled. You may create up to 1000
entries per SSID.
There is also a global ACL (see Access Control List on page 449). If the same
MAC address is listed in both the global ACL and in an SSIDs ACL, and if either
ACL would deny that station access to that SSID, then access will be denied.
Management System
494 ConfiguringaWirelessArray
Procedure for Configuring Access Control Lists
1. SSID: Select the SSID whose ACL you wish to manage.
2. Access Control List Type: Select Disabled to disable use of the Access
Control List for this SSID, or select the ACL type either Allow List or
Deny List.
Allow List: Only allows the listed MAC addresses to associate to
the Array. All others are denied.
Deny List: Denies the listed MAC addresses permission to
associate to the Array. All others are allowed.
3. MAC Address: If you want to add a MAC address to the ACL, enter the
new MAC address here, then click the Add button. The MAC address is
added to the ACL. You may use a wildcard (*) for one or more digits to
match a range of addresses.
4. Delete: You may delete selected MAC addresses from this list by clicking
their Delete buttons.
5. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.

In addition to these lists, other authentication methods (for

example, RADIUS) are still enforced for users.
Management System
ConfiguringaWirelessArray 495
Active IAPs
By default, when a new SSID is created, that SSID is active on all IAPs. This
window allows you to specify which IAPs will offer that SSID. Put differently,
you can specify which SSIDs are active on each IAP.
This feature is useful in conjunction with WDS. You may use this window to
configure the WDS link IAPs so that only the WDS link SSIDs are active on them.
Figure 294. Setting Active IAPs per SSID
Procedure for Specifying Active IAPs
1. SSID: For a given SSID row, check off the IAPs on which that SSID is to
be active. Uncheck any IAPs which should not offer that SSID.
2. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
496 ConfiguringaWirelessArray
Groups
This is a status-only window that allows you to review user (i.e., wireless client)
Group assignments. It includes the group name, Radius ID, Device ID, VLAN IDs
and QoS parameters and roaming layer defined for each group, and DHCP pools
and captive portal information defined for the group. You may click on a groups
name to jump to the edit page for the group. There are no configuration options
available on this page, but if you are experiencing problems or reviewing group
management parameters, you may want to print this page for your records.
The Limits section of this window shows any limitations configured for your
defined groups. For example, this window shows the current state of a group
(enabled or disabled), how much group and per-station traffic is allowed, time on
and time off, and days on and off.
For information to help you understand groups, see Understanding Groups
below. For an in-depth discussion, please see the Xirrus User Groups Application
Note in the Xirrus Resource Center.
Figure 295. Groups
Understanding Groups
User groups allow administrators to assign specific network parameters to users
(wireless clients) through RADIUS privileges rather than having to map users to
an SSID tailored for that set of privileges. Groups provide flexible control over
user privileges without the need to create large numbers of SSIDs.
Management System
ConfiguringaWirelessArray 497
A group allows you to define a set of parameter values to be applied to selected
users. For example, you might define the user group Students, and set its VLAN,
security parameters, captive portal, and traffic limits. When a new user is created,
you can apply all of these settings just by making the user a member of the group.
The group allows you to apply a uniform configuration to a set of users in one
step.
In addition, you can restrict the group so that it only applies its settings to group
members who are connecting using a specific device type, such as iPad or phone.
Thus, you could define a group named Student-Phone with Device ID set to
Phone, and set the groups VLAN Number to 100. This groups settings will only
be applied to group members who connect using a phone, and they will all use
VLAN 100. Note that settings for the group in the RADIUS server will override
any settings on this WMI page.
Almost all of the parameters that can be set for a group are the same as SSID
parameters. This allows you to configure features at the user group level, rather
than for an entire SSID. If you set parameter values for an SSID, and then enter
different values for the same parameters for a user group, the user group values
have priority (i.e., group settings will override SSID settings).
Group names are case-sensitive and can contain up to 32 alphanumeric characters
(do not include spaces when defining Groups).
Using Groups
User accounts are used to authenticate wireless clients that want to associate to
the Array. These accounts are established in one of two ways, using the Security>
Internal Radius window or the Security> External Radius window. In either
case, you may select a user group for the user, and that user groups settings will
apply to the user:
Internal Radius when you add or modify a user entry, select a user
group to which the user will belong.
External Radius when you add or modify a user account, specify the
Radius ID for the user group to which the user will belong. This must be
the same Radius ID that was entered in the Group Management window.
When the user is authenticated, the external Radius server will send the
Management System
498 ConfiguringaWirelessArray
Radius ID to the Array. This will allow the Array to identify the group to
which the user belongs.
Group Management
This window allows you to manage groups (create, edit and delete), assign usage
limits and other parameters on a per group basis, and configure the Captive
Portal functionality.
Figure 296. Adding a Group
Procedure for Managing Groups
1. To create a new group, click the Add button. The Add User Group dialog
appears. You may create up to 16 groups.
To configure and enable this group, proceed with the following steps.
Management System
ConfiguringaWirelessArray 499
2. Enabled: Check this box to enable this group or leave it blank to disable
it. When a group is disabled, users that are members of the group will
behave as if the group did not exist. In other words, the options
configured for the SSID will apply to the users, rather than the options
configured for the group.
3. Name: Enter a new group name. Y
4. RADIUS ID: Enter a unique Radius ID for the group, to be used on an
external Radius server. When adding a user account to the external
server, this Radius ID value should be entered for the user. When the user
is authenticated, Radius sends this value to the Array. This tells the Array
that the user is a member of the group having this Radius ID.
5. Device ID: You may select a device type from this drop-down list, for
example, Notebook, phone, iPhone, or Android. This allows you to
apply the group settings only if a station authenticates as a user that is a
member of the group and the stations device type matches Device ID.
Select none if you do not want to consider the device type. If you have a
Radius ID you should not enter a Device ID.
6. VLAN Name: (Optional) From the pull-down list, select a previously
defined VLAN for this users traffic to use (see VLAN on
page 409).This user groups VLAN settings supersede Dynamic VLAN
settings (which are passed to the Array by the Radius server). To avoid
confusion, we recommend that you avoid specifying the VLAN for a user
in two places.
7. QoS: (Optional) Select a value in this field for QoS (Quality of Service)
priority filtering. The QoS value must be one of the following:
0 The lowest QoS priority setting, where QoS makes its best effort
at filtering and prioritizing data, video and voice traffic without
compromising the performance of the network. Use this setting in
environments where traffic prioritization is not a concern.
1 Medium; QoS prioritization is aggregated across all traffic types.
2 High, normally used to give priority to video traffic.
Management System
500 ConfiguringaWirelessArray
3 The highest QoS priority setting, normally used to give priority to
voice traffic.
The QoS setting you define here will prioritize wireless traffic for this
group versus other traffic, as described in Understanding QoS Priority
on the Wireless Array on page 467. The default value for this field is 2.
8. DHCP Pool: (Optional) To associate an internal DHCP pool to this group,
select it from the pull--down list. Only one pool may be assigned. An
internal DHCP pool must be created before it can be assigned. To create a
DHCP pool, go to DHCP Server on page 427.
9. Filter: (Optional) If you wish to apply a set of filters to this user groups
traffic, select the desired Filter List. See Filters on page 549.
10. Xirrus Roaming: (Optional) For this group, select roaming behavior.
Select L2&L3 to enable fast roaming between IAPs or Arrays at Layer 2
and Layer 3. If you select L2, then roaming uses Layer 2 only. You may
only select fast roaming at Layers 2 and 3 if this has been selected in
Global Settings (IAP). You may select Off to disable fast roaming. See
Understanding Fast Roaming on page 503.
11. Fallback: Network Assurance checks network connectivity for the Array.
When Network Assurance detects a failure, perhaps due to a bad link or
WDS failure, if Fallback is set to Disable the Array will automatically
disable this group of users. This will disassociate current clients, and
prevent new clients from associating. Since the Arrays network
connectivity has failed, this gives clients a chance to connect to other,
operational parts of the wireless network. No changes are made to WDS
configuration. See Step a on page 445 for more information on Network
Assurance.
12. Captive Portal: (Optional) Check this box if you wish to enable the
Captive Portal functionality. This will open a Captive Portal details
section in the window, where your captive portal parameters may be
entered. This feature may be used to display a splash screen when a user
first associates to the wireless network. After that, it can (optionally)
redirect the user to an alternate URL. See SSID ManagementCaptive
Management System
ConfiguringaWirelessArray 501
Portal on page 478 for details of captive portal usage and configuration.
Note that the Group Management window only allows you to set up an
Internal Splash page and a Landing Page URL. The authentication
options that are offered on the SSID Management page are not offered
here. Since the group membership of a user is provided to the Array by a
Radius server, this means the user has already been authenticated.
Group Limits
The Limits section allows you to limit the traffic or connection times allowed for
this user group. Note that the IAPs Global Settings window and the SSID
management windows also have options to limit the number of stations, limit
traffic, and/or limit connection times. If limits are set in more than one place, all
limits will be enforced:
As soon as any station limit is reached, no new stations can associate until
some other station has terminated its association. See Step 13 on page 512
in Global Settings (IAP) for a list of places where station limits are set.
As soon as any traffic limit is reached, it is enforced.
If any connection date/time restriction applies, it is enforced.
You can picture this as a logical AND of all restrictions. For example, suppose that
a stations SSID is available MTWTF between 8:00am and 5:00pm, and the User
Group is available MWF between 6:00am and 8:00pm, then the station will be
allowed on MWF between 8:00am and 5:00pm.
To eliminate confusion, we recommend that you configure one set of limits, but
not multiple limits.
13. Stations: Enter the maximum number of stations allowed on this group.
The default is 2000.
14. Overall Traffic: Check the Unlimited checkbox if you do not want to
place a restriction on the traffic for this group, or enter a value in the
Packets/Sec or Kbps field and make sure that the Unlimited box is
unchecked to force a traffic restriction.
Management System
502 ConfiguringaWirelessArray
15. Traffic per Station: Check the Unlimited checkbox if you do not want to
place a restriction on the traffic per station for this group, or enter a value
in the Packets/Sec or Kbps field and make sure that the Unlimited box is
unchecked to force a traffic restriction.
16. Days Active: Choose Everyday if you want this group to be active every
day of the week, or select only the specific days that you want this group
to be active. Days that are not checked are considered to be the inactive
days.
17. Time Active: Choose Always if you want this group active without
interruption, or enter values in the Time On and Time Off fields to limit
the time that group members may associate.
18. Click OK when done.
19. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
ConfiguringaWirelessArray 503
IAPs
The IAP windows allow you to configure individual IAPs, establish settings for
classes of IAPs, configure advanced RF features, and more.
Arrays have a fast roaming feature, allowing them to maintain sessions for
applications such as voice, even while users cross boundaries between Arrays.
Fast roaming is set up in the Global Settings (IAP) window and is discussed in:
Understanding Fast Roaming on page 503
IAPs are configured using the following windows:
IAP Settings on page 504
Global Settings (IAP) on page 509
Global Settings .11a on page 521
Global Settings .11bg on page 524
Global Settings .11n on page 528
Advanced RF Settings on page 531
Intrusion Detection on page 537
LED Settings on page 543
DSCP Mappings on page 544
Roaming Assist on page 545
Understanding Fast Roaming
To maintain sessions for real-time data traffic, such as voice and video, users must
be able to maintain the same IP address through the entire session. With
traditional networks, if a user crosses VLAN or subnet boundaries (i.e., roaming
between domains), a new IP address must be obtained.
Mobile wireless users are likely to cross multiple roaming domains during a
single session (especially wireless users of VoIP phones). Layer 3 roaming allows
a user to maintain the same IP address through an entire real-time data session.
The user may be associated to any of the VLANs defined on the Array. The Layer
3 session is maintained by establishing a tunnel back to the originating Array. You
should decide whether or not to use Layer 3 roaming based on your wired
Management System
504 ConfiguringaWirelessArray
network design. Layer 3 roaming incurs extra overhead and may result in
additional traffic delays.
Fast Roaming is configured on two pages. To enable the fast roaming options that
you want to make available on your Array, see Step 25 to Step 27 in Global
Settings (IAP) on page 509. To choose which of the enabled options are used by
an SSID or Group, see Procedure for Managing General Settings on page 472
(Step 10) or Procedure for Managing Groups on page 498.
IAP Settings
This window allows you to enable/disable IAPs, define the wireless mode for
each IAP, specify the channel to be used and the cell size for each IAP, lock the
channel selection, establish transmit/receive parameters, select antennas, and
reset channels.

Figure 297. IAP Settings
Procedure for Manually Configuring an IAP
1. Select the desired IAPs checkbox on the left, and then click the Edit
button. The Edit IAP dialog appears.
2. Enabled: set this to Yes to enable the IAP, or set it to No to disable it.
Management System
ConfiguringaWirelessArray 505
Figure 298. Changing IAP Settings
3. Band: select the wireless band for this IAP from the choices available in
the pull-down menu, either 2.4GHz or 5 GHz. Note that the band will
change automatically, if necessary, based on the channel that you select.
Choosing the 5GHz band will automatically select an adjacent channel
for bonding.
One of the IAPs must be set to monitor mode to support Spectrum
Analyzer, Radio Assurance (loopback testing), and Intrusion Detection
features.
Management System
506 ConfiguringaWirelessArray
4. In the Channel column, select the channel you want this IAP to use from
the channels available in the pull-down list.
5. Bond: this works together with the channel bonding options selected on
the Global Settings .11n page.
Off Do not bond his channel to another channel.
On Bond this channel to an adjacent channel. The bonded channel
is selected automatically by the Array based on the Channel (Step 4).
The choice of banded channel is static fixed once the selection is
made.
6. WiFi Mode: select the IEEE 802.11 wireless mode (or combination) that
you want to allow on this IAP. When you select a WiFi Mode for an IAP,
your selection in the Channel column will be checked to ensure that it is a
valid choice for that WiFi Mode.
By selecting appropriate WiFi Modes for the IAPs on your Arrays, you
can greatly improve wireless network performance. For example, if you
have 802.11b and 802.11n stations using the same IAP, throughput on that
IAP is reduced greatly for the 802.11n stations. By supporting 802.11b
stations only on selected IAPs in your network, the rest of your 802.11a or
11n IAPs will have greatly improved performance. Take care to ensure
that your network provides adequate coverage for the types of stations
that you need to support.
7. Antenna: choose the antenna you want this IAP to use from the pull-
down list. The list of available antennas will be different (or no choices
will be available), depending on the wireless mode you selected for the
IAP.

As mandated by FCC/IC law, Arrays continually scan for signatures of

military radar. If such a signature is detected, the Array will switch
operation from conflicting channels to new ones. The Array will switch back
to the original channel after 30 minutes if the channel is clear. If an IAP was
turned off because there were no available channels not affected by radar, the
Array will now bring that IAP back up after 30 minutes if that channel is
clear. The 30 minute time frame complies with FCC/IC regulations.
Management System
ConfiguringaWirelessArray 507
8. Cell Size: Select auto to allow the optimal cell size to be automatically
computed. To set the cell size yourself, choose either small, medium,
large, or max to use the desired pre-configured cell size, or choose
manual to define the wireless cell size manually. If you choose Manual,
you must specify the transmit and receive power in dB in the Tx dBm
(transmit) and Rx dBm (receive) fields. The default is max. If you select a
value other than auto, the cell size will not be affected by cell size auto
configuration. Note that ultra low power Tx dBm settings are possible.
Values from -15dB to 5dB are provided specifically to help in high density
2.4 GHz environments. Note that some older Array models will only
accept 0dBm as a minimum value.
When other Arrays are within listening range of this one, setting cell sizes
to Auto allows the Array to change cell sizes so that coverage between
cells is maintained. Each cell size is optimized to limit interference
between sectors of other Arrays on the same channel. This eliminates the
need for a network administrator to manually tune the size of each cell
when installing multiple Arrays. In the event that an Array or an IAP
goes offline, an adjacent Array can increase its cell size to help
compensate.
The number of users and their applications are major drivers of
bandwidth requirements. The network architect must account for the
number of users within the Arrays cell diameter. In a large office, or if
multiple Arrays are in use, you may choose Small cells to achieve a
higher data rate, since walls and other objects will not define the cells
naturally.
9. Locked: select Yes if you want to lock in your channel selection so that the
autochannel operation (see Advanced RF Settings) cannot change it.
10. Click OK when done.
11. Buttons at the bottom of the list allow you to Enable All or Disable All
IAPs.
Management System
508 ConfiguringaWirelessArray
12. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
ConfiguringaWirelessArray 509
Global Settings (IAP)
This window allows you to establish global IAP settings. Global IAP settings
include enabling or disabling all IAPs (regardless of their operating mode), and
changing settings for beacons, station management, and advanced traffic
optimization including multicast processing, load balancing, and roaming.
Changes you make on this page are applied to all IAPs, without exception.

Figure 299. Global Settings (IAPs)
Management System
510 ConfiguringaWirelessArray
Procedure for Configuring Global IAP Settings
1. Country: This is a display-only value. Once a country has been set, it may
not be changed.
The channels that are available for assignment to an IAP will differ,
depending on the country of operation. If Country is set to United States,
then 21 channels are available for 802.11a/n.
If no country is displayed, the channel set defaults to channels and power
levels that are legal worldwide this set only includes the lower eight 5
GHz channels.
2. Short Retries: This sets the maximum number of transmission attempts
for a frame, the length of which is less than or equal to the RTS Threshold,
before a failure condition is indicated. The default value is 7. Enter a new
value (1 to 128) in the Short Retry Limit field if you want to increase or
decrease this attribute.
3. Long Retries: This sets the maximum number of transmission attempts
for a frame, the length of which is greater than the RTS Threshold, before
a failure condition is indicated. The default value is 4. Enter a new value
(1 to 128) in the Long Retry Limit field if you want to increase or decrease
this attribute.
4. Wi-Fi Alliance Mode: Set this On if you need Array behavior to conform
completely to Wi-Fi Alliance standards. This mode is normally set to Off.

On XN Arrays, some of the features below, such as Load Balancing, are only
available if the Arrays license includes the Xirrus Advanced RF
Performance Manager (RPM). See Array DetailsSystem on page 70
to check whether the Array license includes this feature.
Management System
ConfiguringaWirelessArray 511
Beacon Configuration
5. Beacon Interval: When the Array sends a beacon, it includes with it a
beacon interval, which specifies the period of time before it will send the
beacon again. Enter the desired value in the Beacon Interval field,
between 20 and 1000 Kusecs. A Kusec is 1000 microseconds =
1 millisecond. The value you enter here is applied to all IAPs.
6. DTIM Period: A DTIM (Delivery Traffic Indication Message) is a signal
sent as part of a beacon by the Array to a client device in sleep mode,
alerting the device to broadcast traffic awaiting delivery. The DTIM
Period is a multiple of the Beacon Interval, and it determines how often
DTIMs are sent out. By default, the DTIM period is 1, which means that it
is the same as the beacon interval. Enter the desired multiple, between 1
and 255. The value you enter here is applied to all IAPs.
7. 802.11h Beacon Support: This option enables beacons on all of the
Arrays IAPs to conform to 802.11h requirements, supporting dynamic
frequency selection (DFS) and transmit power control (TPC) to satisfy
regulatory requirements for operation in Europe.
8. 802.11k Beacon Support: 802.11k offers faster and more efficient roaming.
When enabled, each beacon lists the channels that nearby APs offer. This
supports improved channel scanning, resulting in faster roam times and
increased battery life due to shorter scan times since the station knows
where to look for nearby APs. The Array will also respond to requests
from stations for an 802.11K Neighbor Report with additional
information about nearby APs. This setting is only available for Arrays
running ArrayOS Release 6.6 and above. It is disabled by default.
9. WMM Power Save: Click On to enable Wireless Multimedia Power Save
support, as defined in IEEE802.11e. This option saves power and
increases battery life by allowing the client device to doze between
packets to save power, while the Array buffers downlink frames.
Management System
512 ConfiguringaWirelessArray
Station Management
10. Station Re-Authentication Period: This specifies an interval (in seconds)
for station reauthentications. This is the minimum time period between
station authentication attempts, enforced by the Array. This feature is part
of the Xirrus Advanced RF Security Manager (RSM).
11. Station Timeout Period: Specify a time (in seconds) in this field to define
the timeout period for station associations.
12. Max Station Association per Array: This option allows you to define
how many station associations are allowed per Array. Note that the Max
Station Association per IAP limit (below) may not be exceeded. If you
have an unlicensed Array, this value is set to 1, which simply allows you
to test the ability to connect to the Array.
13. Max Station Association per IAP: This defines how many station
associations are allowed per IAP. Note that in addition to Max Station
Association per Array above, the SSID ManagementLimits and Group
Management windows also have a station limit option, and the windows
for Global Settings .11a and Global Settings .11bg also have Max Stations
settings. If multiple station limits are set, all will be enforced. As soon as
any limit is reached, no new stations can associate until some other
station has terminated its association.
14. Block Inter-Station Traffic: This option allows you to block or allow
traffic between wireless clients that are associated to the Array. Choose
either Yes (to block traffic) or No (to allow traffic).
15. Allow Over Air Management: Choose Yes to enable management of the
Array via the IAPs, or choose No (recommended) to disable this feature.
Advanced Traffic Optimization
16. Multicast Processing: This sets how multicast traffic is handled.
Multicast traffic can be received by a number of subscribing stations at
the same time, thus saving a great deal of bandwidth. In some of the
options below, the Array uses IGMP snooping to determine the stations
Management System
ConfiguringaWirelessArray 513
that are subscribed to the multicast traffic. IGMP (Internet Group
Management Protocol) is used to establish and manage the membership
of multicast groups.
Multicast packet handling options are only applicable to downstream
traffic transmitted from the Array to wireless stations. Select one of the
following options:
Send multicasts unmodified. This option is useful when multicast is
not needed because no video or audio streaming is required or when
it is used only for discovering services in the network. An example of
this type of multicast usage is the Bonjour protocol used by AppleOS
devices.
The next three options convert multicast to unicast. Packets are sent
directly to the stations at the best possible data rates. Because they are
unicast packets, they will also benefit from 802.11 acknowledges. This
approach significantly improves the quality of the voice and video
multicast streams.
Convert to unicast and send unicast packets to all stations. This
option is useful when you need to stream voice or video traffic and
none of the associated stations have the capability to subscribe to the
multicast group through the use of IGMP join messages, but all of
them need to receive the stream with good quality.
Convert to unicast, snoop IGMP, and only send to stations
subscribed (send as multicast if no subscription). This option is
useful when you need to stream voice or video multicast traffic to all
stations, but some stations are capable of subscribing to multicast
groups while other stations are not. The stations that do not subscribe
will not benefit from conversion to unicast; their video or voice
quality may be compromised.
Convert to unicast, snoop IGMP, and only send to stations
subscribed (don't send packet if no subscription). This option is
useful in well controlled environments when you need to stream
voice or video multicast traffic only to stations that are capable of
Management System
514 ConfiguringaWirelessArray
subscribing to multicast groups and there is no need for the rest of the
stations to receive the data stream.
17. Multicast Exclude: This is a list of multicast IP addresses that will not be
subject to multicast-to-unicast conversion. This list is useful on networks
where applications such as those using multicast Domain Name System
(mDNS) are in use. For example, Apple Bonjour finds local network
devices such as printers or other computers using mDNS. By default, the
list contains the IPv4 multicast address for Apple Bonjour/ mDNS:
224.0.0.251.
To add a new IP address to the list, type it in the field and click the Add
button to its right. You may only enter IP addresses - host names are not
allowed. This is because mDNS is a link local multicast address, and does
not require IGMP to the gateway.
To remove an entry, select it in the list and click Delete. To reset the list to
the values in the XMS database, click Reset (i.e., any unsaved changes are
erased from the list).
18. Multicast Forwarding
Multicast Forwarding is a Xirrus feature that forwards selected multicast
traffic between wired VLANs and wireless SSIDs. For example, Apple
devices use mDNS to advertise and find services, using local network
multicasts that are not routed. This creates an issue when you are using
Apple devices on the Wireless LAN, and have other devices that provide
services connected on the wired infrastructure in a different VLAN, for
example, printers and AppleTV devices. One way to address this issue is
to set up multicast forwarding between the wireless SSID and the wired
VLAN. This requires the wired VLAN to be trunked to the Array. Once
configured correctly, mDNS traffic will be forwarded from the specified
wireless network(s) to the specified wired VLANs and vice-versa, subject
to any mDNS service filtering defined (Step 20).
Management System
ConfiguringaWirelessArray 515
Use multicast forwarding together with multicast VLAN forwarding
(Step 19) and mDNS filtering (Step 20) to make services available across
VLANs as follows:
In Multicast Forwarding, enter a list of multicast addresses that you
want forwarded, for example, 224.0.0.251 (the multicast address for
Bonjour).
In Multicast VLAN Forwarding, enter a list of VLANs that
participate in the multicast forwarding.
In MDNS Filter, specify the mDNS service types that are allowed to
be forwarded.
If you leave this field blank, then there is no filter, and mDNS
packets for all service types are passed.
If you enter service types, then this acts as an allow filter, and
mDNS packets are passed only for the listed service types.
Note that mDNS filtering may be used to filter the mDNS packet
types that are forwarded within the same VLAN. Also, in conjunction
with multicast forwarding, it may be used to filter the mDNS packet
types that are forwarded across configured VLANs.
After you have entered these settings, when multicast packets arrive from
the wired network from one of the Multicast Forwarding Addresses on
any VLAN specified in Multicast VLAN Forwarding, they are forwarded
to the corresponding wireless SSID for that VLAN.
Multicast packets coming in from the wireless network on an SSID tied to
one of the specified VLANs and matching one of the Multicast
Forwarding Addresses are forwarded to the specified VLANs on the
wired network.
No modifications are made to the forwarded packets they are just
forwarded between specified VLANs and associated SSIDs.
Management System
516 ConfiguringaWirelessArray
To specify Multicast Forwarding Addresses: enter each IP address in the
top field and click the Add button to its right. You may only enter IPv4
multicast addresses - host names are not allowed. To remove an entry,
select it in the list and click Delete. To reset the list to the values in the
XMS database, click Reset (i.e., any unsaved changes are erased from the
list).
19. Multicast VLAN Forwarding: This is a list of VLANs that participate in
the multicast forwarding. Please see the description of multicast
forwarding in Step 18 above.
To add a new VLAN to the list, enter its number or name in the top field
and click the Add button to its right. You may enter multiple VLANs at
once, separated by a space. To remove an entry, select it in the list and
click Delete. To reset the list to what is in the XMS database, click Reset
(i.e., any unsaved changes are erased from the list).
These VLANs must be trunked to the Array from the LAN switch, and be
defined on the Array. See VLAN Management on page 410 and SSID
Management on page 471.

Xirrus strongly recommends the use of MDNS Filters (Step ) when using
multicast forwarding. Only allow required services to be forwarded.
Carefully monitor results, as forwarding may flood your network with
multicast traffic. Experience has shown Bonjour devices to be very chatty.
Also note that since this is link local multicast traffic, it will be sent to every
wired port in the VLAN, as IGMP snooping does not work with link local
multicast addresses.

The VLANs you enter must be explicitly defined (see VLAN on

page 409) in order to participate in multicast forwarding. In fact, the Array
discards packets from undefined VLANs.
Management System
ConfiguringaWirelessArray 517
20. MDNS Filter: There are many different types of services that may be
specified in multicast query and response packets. The mDNS filters let
you restrict forwarding, so that multicast packets are forwarded only for
the services that you explicitly specify. This list may be used to restrict the
amount of Apple Bonjour multicast traffic forwarding. For example, you
may restrict forwarding to just AppleTV and printing services. Please see
the description of multicast forwarding in Step 18 above.
The MDNS Filter operates as follows:
If you leave this field blank, then there is no filter, and mDNS
packets for all service types are passed.
If you enter service types, then this acts as an allow filter, and
mDNS packets are passed only for the listed service types.
To add an mDNS packet type to the list of packets that may be forwarded,
type it in the top field, or select an option from the drop-down list and
click the Add button to its right. The drop-down list offers packet types

Note that Multicast Forwarding and mDNS Filtering capabilities also work
if both devices are wireless. For example, lets say that AppleTV is using
wireless to connect to an SSID that is associated with VLAN 56, and the
wireless client is on an SSID that is associated with VLAN 58. Normally the
wireless client would not be able to use Bonjour to discover the AppleTV
because they are on separate VLANs. But if you add 224.0.0.251 to the
Multicast Forwarding list, then add VLANs 56 and 58 to the Multicast
VLAN Forwarding list, then the wireless client will be able to discover the
AppleTV. In this same scenario you could add AppleTV to the MDNS Filter
list so that only MDNS packets for the AppleTV service type would be
forwarded between VLANs 56 and 58.

Note that all the VLANs that you add to this list do not have to be associated
with SSIDs. As an example, say that AppleTV is on the wired network on
VLAN 56, while the wireless device is connected to an SSID that is
associated to VLAN 58. In this case, VLAN 56 and 58 need to be defined on
the Array but only VLAN 58 needs to be associated to a SSID.
Management System
518 ConfiguringaWirelessArray
such as AirTunes, Apple-TV, iChat, iPhoto, iTunes, iTunes-Home-
Sharing, Internet-Printing, Mobile-Device-Sync, and Secure-Telnet.
For example, to allow mirroring of an iPad on an Apple-TV, select Apple-
TV.
You may define your own type if you do not see the service you want in
the drop-down list. Simply enter the mDNS service name that you would
like to allow through. Custom mDNS packet types must be prefixed with
an underscore, e.g., _airvideoserver.
To remove an entry, select it in the list and click Delete. To reset the list to
the values in the XMS database, click Reset (i.e., any unsaved changes are
erased from the list).
21. Broadcast Rates: This changes the rates of broadcast traffic sent by the
Array (including beacons). When set to Optimized, each broadcast or
multicast packet that is transmitted on each IAP is sent at the lowest
transmit rate used by any client associated to that IAP at that time. This
results in each IAP broadcasting at the highest Array TX data rate that can
be heard by all associated stations, improving system performance. The
rate is determined dynamically to ensure the best broadcast/multicast
performance possible. The benefit is dramatic. Consider a properly
designed network (having -70db or better everywhere), where virtually
every client should have a 54Mbps connection. In this case, broadcasts
and multicasts will all go out at 54Mbps vs. the standard rate. Thus, with
broadcast rate optimization on, broadcasts and multicasts use between
2% and 10% of the bandwidth that they would in Standard mode.
When set to Standard (the default), broadcasts are sent out at the lowest
basic rate only 6 Mbps for 5GHz clients, or 1 Mbps for 2.4GHz clients.
The option you select here is applied to all IAPs.
22. Load Balancing: The Xirrus Wireless Array supports an automatic load
balancing feature designed to distribute wireless stations across multiple
IAPs rather than having stations associate to the closest IAPs with the
strongest signal strength, as they normally would. In wireless networks,
the station decides to which IAP it will associate. The Array cannot
Management System
ConfiguringaWirelessArray 519
actually force load balancing, however the Array can encourage
stations to associate in a more uniform fashion across all of the IAPs of the
Array. This option enables or disables active load balancing between the
Array IAPs. For an in-depth discussion, see the Xirrus Station Load
Balancing Application Note in the Xirrus Resource Center.
If you select On and an IAP is overloaded, that IAP will send an AP
Full message in response to Probe, Association, or Authentication
requests. This prevents determined clients from forcing their way onto
overloaded IAPs. Note that some clients are so determined to associate to
a particular IAP that they will not try to associate to another IAP, and thus
they never get on the network.
Choose Off to disable load balancing.
23. IPv6 Filtering: this setting allows blocking of IPv6 traffic which may be a
concern for IT managers. The Xirrus Array currently bridges IPv6 traffic.
Set IPv6 filtering On if you wish to prevent the forwarding of IPv6
packets through the Array in both directionswired network to wireless
and wireless network to wired. The default is Off.
24. ARP Filtering: Address Resolution Protocol finds the MAC address of a
device with a given IP address by sending out a broadcast message
requesting this information. ARP filtering allows you to reduce the
proliferation of ARP messages by restricting how they are forwarded
across the network.
You may select from the following options for handling ARP requests:
Off: ARP filtering is disabled. ARP requests are broadcast to IAPs
that have stations associated to them.
Pass-thru: The Array forwards the ARP request. It passes along only
ARP messages that target the stations that are associated to it. This is
the default value.
Proxy: The Array replies on behalf of the stations that are associated
to it. The ARP request is not broadcast to the stations.
Management System
520 ConfiguringaWirelessArray
Note that the Array has a broadcast optimization feature that is always on
(it is not configurable). Broadcast optimization restricts all broadcast
packets (not just ARP broadcasts) to only those IAPs that need to forward
them. For instance, if a broadcast comes in from VLAN 10, and there are
no VLAN 10 users on an IAP, then that IAP will not send out that
broadcast. This increases available air time for other traffic.
25. Xirrus Roaming Layer: Select whether to enable roaming capabilities
between IAPs or Arrays at Layer 2 and 3, or at Layer 2 only. Depending
on your wired network, you may wish to allow fast roaming at Layer 3.
This may result in delayed traffic.
26. Xirrus Roaming Mode: This feature utilizes the Xirrus Roaming Protocol
(XRP) ensuring fast and seamless roaming capabilities between IAPs or
Arrays at Layer 2 and Layer 3 (as specified in Step 27), while maintaining
security. Fast roaming eliminates long delays for re-authentication, thus
supporting time-sensitive applications such as Voice over Wi-Fi (see
Understanding Fast Roaming on page 503 for a discussion of this
feature). XRP uses a discovery process to identify other Xirrus Arrays as
fast roaming targets. This process has two modes:
Broadcast the Array uses a broadcast technique to discover other
Arrays that may be targets for fast roaming.
Tunneled in this Layer 3 technique, fast roaming target Arrays
must be explicitly specified.
To enable fast roaming, choose Broadcast or Tunneled, and set additional
fast roaming attributes (Step 27). To disable fast roaming, choose Off. If
you enable Fast Roaming, the following ports cannot be blocked:
Port 22610 reserved for Layer 2 roaming using UDP to share PMK
information between Arrays.
Ports 15000 to 17999 reserved for Layer 3 roaming (tunneling
between subnets).
Management System
ConfiguringaWirelessArray 521
27. Share Roaming Info With: Three options allow your Array to share
roaming information with all Arrays; just with those that are within
range; or with specifically targeted Arrays. Choose either All, In Range
or Target Only, respectively.
a. Xirrus Roaming Targets: If you chose Target Only, use this option to
add target MAC addresses. Enter the MAC address of each target
Array, then click on Add (add as many targets as you like). To find a
targets MAC address, open the Array Info window on the target
Array and look for IAP MAC Range, then use the starting address of
this range.
To delete a target, select it from the list, then click Delete.
Global Settings .11a
This window allows you to establish global 802.11a IAP settings. These settings
include defining which 802.11a data rates are supported, enabling or disabling all
802.11an IAPs, and specifying the fragmentation and RTS thresholds for all
802.11an IAPs.
Figure 300. Global Settings .11an
Management System
522 ConfiguringaWirelessArray
Procedure for Configuring Global 802.11an IAP Settings
1. 802.11a Data Rates: The Array allows you to define which data rates are
supported for all 802.11an IAPs. Select (or deselect) data rates by clicking
in the corresponding Supported and Basic data rate check boxes.
Basic Rate a wireless station (client) must support this rate in order
to associate.
Supported Rate data rates that can be used to transmit to clients.
2. Data Rate Presets: The wireless Array can optimize your 802.11a data
rates automatically, based on range or throughput. Click Optimize Range
to optimize data rates based on range, or click Optimize Throughput to
optimize data rates based on throughput. The Default button will take
you back to the factory default rate settings.
3. Auto Cell Period (seconds): You may set up auto-configuration to run
periodically, readjusting optimal cell sizes for the current conditions.
Enter a number of seconds to specify how often auto-configuration will
run. If you select None, then auto-configuration of cell sizing will not be
run periodically. You do not need to run Auto Cell often unless there are a

On XN Arrays, some of the features below, such as Auto Configure for Cell
Size and Channel Configuration, are only available if the Arrays license
includes the Xirrus Advanced RF Performance Manager (RPM). See
Array DetailsSystem on page 70 to check whether the Array license
includes this feature.

To use the Auto Cell Size feature, the following additional settings are
required:
RF Monitor Mode must be turned On. See RF Monitor on page 532
One of the IAPs must be in monitor mode with the default RxdBm setting
of -95, and all other IAPs that will use Auto Cell must have Cell Size set to
auto. See Procedure for Manually Configuring an IAP on
page 504.
Management System
ConfiguringaWirelessArray 523
lot of changes in the environment. If the RF environment is changing
often, running Auto Cell every twenty-four hours (86400 seconds) should
be sufficient). The default value is None.
4. Auto Cell Size Overlap (%): Enter the percentage of cell overlap that will
be allowed when the Array is determining automatic cell sizes. For 100%
overlap, the power is adjusted such that neighboring Arrays that hear
each other best will hear each other at -70dB. For 0% overlap, that number
is -90dB. The default value is 50%.
5. Auto Cell Min Tx Power (dBm): Enter the minimum transmit power that
the Array can assign to an IAP when adjusting automatic cell sizes. The
default value is 10. You may also set this in terms of minimum cell size:
Default, Large, Medium, or Small.
6. Fragmentation Threshold: This is the maximum size for directed data
packets transmitted over the 802.11an IAP. Larger frames fragment into
several packets, their maximum size defined by the value you enter here.
Smaller fragmentation numbers can help to squeeze packets through in
noisy environments. Enter the desired Fragmentation Threshold value in
this field, between 256 and 2346.
7. RTS Threshold: The RTS (Request To Send) Threshold specifies the
packet size. Packets larger than the RTS threshold will use CTS/RTS prior
to transmitting the packet useful for larger packets to help ensure the
success of their transmission. Enter a value between 1 and 2347.
8. Max Stations per Array: This defines how many total concurrent station
associations are allowed for all 802.11an IAPs. If multiple station limits
are set, all will be enforced. As soon as any limit is reached, no new
stations can associate until some other station has terminated its
association. See Step 13 on page 512 in Global Settings (IAP) for a list of
places where station limits are set.
9. Max Stations per IAP: This defines how many station associations are
allowed per 802.11an IAP. If multiple station limits are set, all will be
enforced. As soon as any limit is reached, no new stations can associate
until some other station has terminated its association. See Step 13 on
Management System
524 ConfiguringaWirelessArray
page 512 in Global Settings (IAP) for a list of places where station limits
are set.
Global Settings .11bg
This window allows you to establish global 802.11b/g IAP settings. These settings
include defining which 802.11b and 802.11g data rates are supported, enabling or
disabling all 802.11b/g IAPs, and specifying the fragmentation and RTS
thresholds for all 802.11b/g IAPs.
Figure 301. Global Settings .11bg
Management System
ConfiguringaWirelessArray 525
Procedure for Configuring Global 802.11b/g IAP Settings
1. 802.11g Data Rates: The Array allows you to define which data rates are
supported for all 802.11g IAPs. Select (or deselect) 11g data rates by
clicking in the corresponding Supported and Basic data rate check boxes.
Basic Rate a wireless station (client) must support this rate in
order to associate.
Supported Rate data rates that can be used to transmit to
clients.
2. 802.11b Data Rates: This task is similar to Step 1, but these data rates
apply only to 802.11b IAPs.
3. Data Rate Presets: The wireless Array can optimize your 802.11b/g data
rates automatically, based on range or throughput. Click Optimize Range
button to optimize data rates based on range, or click on the Optimize
Throughput to optimize data rates based on throughput. Default will
take you back to the factory default rate settings.
4. Auto Cell Period (seconds): You may set up auto-configuration to run
periodically, readjusting optimal cell sizes for the current conditions.
Enter a number of seconds to specify how often auto-configuration will
run. If you enter 0, then auto-configuration of cell sizing will not be run
periodically. You do not need to run Auto Cell often unless there are a lot
of changes in the environment. If the RF environment is changing often,
running Auto Cell every twenty-four hours (86400 seconds) should be
sufficient). The default value is 0.

On XN Arrays, some of the features below, such as Auto Configure for Cell
Size and Channel Configuration, are only available if the Arrays license
includes the Xirrus Advanced RF Performance Manager (RPM). See
Array DetailsSystem on page 70 to check whether the Array license
includes this feature.
Management System
526 ConfiguringaWirelessArray
5. Auto Cell Size Overlap (%): Enter the percentage of cell overlap that will
be allowed when the Array is determining automatic cell sizes. For 100%
overlap, the power is adjusted such that neighboring Arrays that hear
each other best will hear each other at -70dB. For 0% overlap, that number
is -90dB. The default value is 50%.
6. Auto Cell Min Tx Power (dBm): Enter the minimum transmit power that
the Array can assign to an IAP when adjusting automatic cell sizes. The
default value is 10. You may also set this in terms of minimum cell size:
Default, Large, Medium, or Small.
7. 802.11g Only: Choose On to restrict use to 802.11g mode only. In this
mode, no 802.11b rates are transmitted. Stations that only support 802.11b
will not be able to associate.
8. 802.11g Protection: You should select Auto CTS or Auto RTS to provide
automatic protection for all 802.11g IAPs in mixed networks (802.11
b and g). You may select Off to disable this feature, but this is not
recommended. Protection allows 802.11g stations to share an IAP with
older, slower 802.11b stations. Protection avoids collisions by preventing
802.11b and 802.11g stations from transmitting simultaneously. When
Auto CTS or Auto RTS is enabled and any 802.11b station is associated to
the IAP, additional frames are sent to gain access to the wireless network.
Auto CTS requires 802.11g stations to send a slow Clear To Send
frame that locks out other stations. Automatic protection reduces
802.11g throughput when 802.11b stations are present Auto CTS
adds less overhead than Auto RTS. The default value is Auto CTS.
With Auto RTS, 802.11g stations reserve the wireless media using a
Request To Send/Clear To Send cycle. This mode is useful when you
have dispersed nodes. It was originally used in 802.11b only
networks to avoid collisions from hidden nodes nodes that are so
widely dispersed that they can hear the Array, but not each other.
When there are no 11b stations associated and an auto-protection mode is
enabled, the Array will not send the extra frames, thus avoiding
unnecessary overhead.
Management System
ConfiguringaWirelessArray 527
9. 802.11g Slot: Choose Auto to instruct the Array to manage the 802.11g
slot times automatically, or choose Short Only. Xirrus recommends using
Auto for this setting, especially if 802.11b devices are present.
10. 802.11b Preamble: The preamble contains information that the Array and
client devices need when sending and receiving packets. All compliant
802.11b systems have to support the long preamble. A short preamble
improves the efficiency of a network's throughput when transmitting
special data, such as voice, VoIP (Voice-over IP) and streaming video.
Select Auto to instruct the Array to manage the preamble (long and short)
automatically, or choose Long Only.
11. Fragmentation Threshold: This is the maximum size for directed data
packets transmitted over the 802.11b/g IAP. Larger frames fragment into
several packets, their maximum size defined by the value you enter here.
Enter the desired Fragmentation Threshold value, between 256 and 2346.
12. RTS Threshold: The RTS (Request To Send) Threshold specifies the
packet size. Packets larger than the RTS threshold will use CTS/RTS prior
to transmitting the packet useful for larger packets to help ensure the
success of their transmission. Enter a value between 1 and 2347.
13. Max Stations per Array: This defines how many total concurrent station
associations are allowed for all 802.11bgn IAPs. If multiple station limits
are set, all will be enforced. As soon as any limit is reached, no new
stations can associate until some other station has terminated its
association. See Step 13 on page 512 in Global Settings (IAP) for a list of
places where station limits are set.
14. Max Stations per IAP: This defines how many station associations are
allowed per 802.11bgn IAP. If multiple station limits are set, all will be
enforced. As soon as any limit is reached, no new stations can associate
until some other station has terminated its association. See Step 13 on
page 512 in Global Settings (IAP) for a list of places where station limits
are set.
Management System
528 ConfiguringaWirelessArray
Global Settings .11n
This window is displayed only for XN Array models. It allows you to establish
global 802.11n IAP settings. These settings include enabling or disabling 802.11n
mode for the entire Array, specifying the number of transmit and receive chains
(data stream) used for spatial multiplexing, setting a short or standard guard
interval, auto-configuring channel bonding, and specifying whether auto-
configured channel bonding will be static or dynamic.
Before changing your settings for 802.11n, please read the discussion in IEEE
802.11n Deployment Considerations in the Xirrus Wireless Array Users Guide.
Procedure for Configuring Global 802.11n IAP Settings
1. 802.11n Data Rates: The Array allows you to define which data rates are
supported for all 802.11n IAPs. Select (or deselect) 11n data rates by
clicking in the corresponding Supported and Basic data rate check boxes.
Basic Rate a wireless station (client) must support this rate in
order to associate.
Supported Rate data rates that can be used to transmit to
clients.

802.11n operation is allowed only if the Arrays license includes

this feature.
Management System
ConfiguringaWirelessArray 529
Figure 302. Global Settings .11n
2. 802.11n Mode: Select Enabled to operate in 802.11n mode, with four
802.11b/g/n mode ports and the remaining IAPs operating in 802.11a/n
mode. Use of this mode is controlled by the Arrays license key. The key
must include 802.11n capability, or you will not be able to enable this
mode. See Array DetailsSystem on page 70 to view the features
supported by your license key. Contact Xirrus Customer support for
questions about your license.
If you select Disabled, then 802.11n operation is disabled on the Array.
3. TX Chains: Select the number of separate data streams transmitted by the
antennas of each IAP. The maximum number offered is determined by
how many streams your Array supports.
4. RX Chains: Select the number of separate data streams received by the
antennas of each IAP. The maximum number offered is determined by
how many streams your Array supports.
Management System
530 ConfiguringaWirelessArray
5. Guard interval: Select Short to increase the data transmission rate by
decreasing wait intervals in signal transmission. Select Long to use the
standard interval. The default is Short.
6. Auto bond 5 GHz channels: Select Enabled to use Channel Bonding on
5 GHz channels and automatically select the best channels for bonding.
The default is Enabled. See IEEE 802.11n Deployment Considerations
in the Xirrus Wireless Array Users Guide.
7. 5 GHz channel bonding: Select Dynamic to have auto-configuration for
bonded 5 GHz channels be automatically updated as conditions change.
For example, if there are too many clients to be supported by a bonded
channel, dynamic mode will automatically break the bonded channel into
two channels. Select Static to have the bonded channels remain the same
once they are selected. The Dynamic option is only available when Auto
bond 5 GHz channels is enabled. The default is Dynamic. See IEEE
802.11n Deployment Considerations in the Xirrus Wireless Array Users
Guide.
8. 2.4 GHz channel bonding: Select Dynamic to have auto-configuration
for bonded 2.4 GHz channels be automatically updated as conditions
change. Select Static to have the bonded channels remain the same once
they are selected. The default is Dynamic. See IEEE 802.11n Deployment
Considerations in the Xirrus Wireless Array Users Guide.
Management System
ConfiguringaWirelessArray 531
Advanced RF Settings
This window allows you to establish RF settings, including automatically
configuring channel allocation and cell size, and configuring radio assurance and
standby modes. Changes you make on this page are applied to all IAPs, without
exception.

Figure 303. Advanced RF Settings
About Standby Mode
Standby Mode supports the Array-to-Array fail-over capability. When you enable
Standby Mode, the Array functions as a backup unit, and it enables its IAPs if it
detects that its designated target Array has failed. The use of redundant Arrays to
Management System
532 ConfiguringaWirelessArray
provide this fail-over capability allows Arrays to be used in mission-critical
applications. In Standby Mode, an Array monitors beacons from the target Array.
When the target has not been heard from for 40 seconds, the standby Array
enables its IAPs until it detects that the target Array has come back online.
Standby Mode is off by default. Note that you must ensure that the configuration
of the standby Array is correct. This window allows you to enable or disable
Standby Mode and specify the primary Array that is the target of the backup unit.
Procedure for Configuring Advanced RF Settings
RF Monitor
1. RF Monitor Mode: RF monitoring permits the operation of features like
intrusion detection. The monitor may operate in Dedicated mode, or in
Timeshare mode which allows the IAP to divide its time between
monitoring and acting as a standard IAP that allows stations to associate
to it.
Note that if you are performing configuration for Profiles and you select
Dedicated mode, you will also see a setting for Enable Timeshare for 2-

On XN Arrays, some of the features below, such as Auto Configure for Cell
Size and Channel Configuration, are only available if the Arrays license
includes the Xirrus Advanced RF Performance Manager (RPM). See
Array DetailsSystem on page 70 to check whether the Array license
includes this feature.
Other features below, such as RF Intrusion Detection, are only available if
the Arrays license includes the Xirrus Advanced RF Security Manager
(RSM).

In Timeshare mode, monitor functions are performed less frequently and

thoroughly, which is likely to impact some features that rely on the monitor.
In particular, rogue location information from this Array may not be
frequent enough to identify and locate rogues. See Rogue Location on
page 283.
Management System
ConfiguringaWirelessArray 533
Radio Arrays. For details, see Settings that are only present in profile
configuration on page 219.
If Timeshare mode is selected, you may adjust the following settings:
Timeshare Scanning Interval (6-600): number of seconds between
monitor (off-channel) scans.
Timeshare Station Threshold (0-240): when the number of stations
associated to the monitor IAP exceeds this threshold, scanning is
halted.
Timeshare Traffic Threshold (0-50000): when the number of packets
per second handled by the monitor IAP exceeds this threshold,
scanning is halted.
RF Resilience
2. Radio Assurance Mode: When this mode is enabled, the monitor IAP
performs loopback tests on the Array. This mode requires RF Monitor
Mode to be enabled (Step 1) to enable self-monitoring functions. It also
requires an IAP to be set to monitoring mode.
The Radio Assurance mode scans and sends out probe requests on each
channel, in turn. It listens for all probe responses and beacons. These tests
are performed continuously (24/7). If no beacons or probe responses are
observed from an IAP for a predetermined period, Radio Assurance
mode will take action according to the preference that you have specified:
Alert only The Array will issue alerts in the Syslog, but will not
initiate repairs or reboots.
Repairs without reboot The Array will issue alerts and perform
resets of one or all of the IAPs if needed.
Reboots allowed The Array will issue alerts, perform resets, and
schedule reboots if needed.
Disabled Disable IAP radio assurance tests (no self-monitoring
occurs). Loopback tests are disabled by default.
Management System
534 ConfiguringaWirelessArray
3. Enable Standby Mode: Choose Yes to enable this Array to function as a
backup unit for the target Array, or choose No to disable this feature. See
About Standby Mode on page 531.
4. Standby Target Address: If you enabled the Standby Mode, enter the
MAC address of the target Array (i.e., the address of the primary Array
that is being monitored and backed up by this Array). To find this MAC
address, open the Array Info window on the target Array, and use the
Gigabit1 MAC Address.
RF Power & Resilience
5. Sharp Cell: This feature reduces interference between neighboring
Arrays or other Access Points by limiting to a defined boundary (cell size)
the trailing edge bleed of RF energy. Choose On to enable the Sharp Cell
functionality, or choose Off to disable this feature. See also, Planning
Your InstallationCoverage and Capacity Planning in the Xirrus
Wireless Array Users Guide.
The Sharp Cell feature only works when the cell size is Small, Medium, or
Large (or Auto) but not Max. If an IAP cell size is set to Max, the Sharp
Cell feature will be disabled for that IAP.
RF Spectrum Management (Auto Channel Configuration)
Auto Channel assignment is the preferred way to select channel assignments for
an Arrays IAPs, and has significant advantages. When you start an Arrays auto
channel feature, the Array scans the surrounding area for RF activity on all
channels and then automatically selects and sets its channels to the best available.
This function is typically executed when initially installing Arrays in a new
location. You may wish to repeat it periodically to account for changes in the RF
environment over time. Note that the best way to run auto channel is from a map.
See the Auto Configure Channels option (and also see the Auto Band option) in
the Configure drop-down menu in Managing Arrays Within Maps on
page 272 and Channel Configuration on page 284.
Management System
ConfiguringaWirelessArray 535
When running auto channel on multiple Arrays, XMS will shut down IAPs on all
of the Arrays being configured. It will then run auto channel on one Array at a
time, and bring its IAPs back up when channels have been selected.
6. Auto Channel Configuration Mode: This option allows you to instruct
the Array to auto-configure channel selection for each enabled IAP when
the Array is powered up. Choose On Array PowerUp to enable this
feature, or choose Disabled to disable this feature.
7. Auto Channel Schedule: This option allows you to instruct the Array to
auto-configure channel selection for each enabled IAP at the times you
specify here. Leave this field blank unless you want to specify one or
more times at which the auto-configuration process is initiated. Auto
Channel will run on the selected day[s} at the specified times. Time is
specified in hours and minutes, using the format: hh:mm [am|pm]. If
you omit the optional day specification, channel configuration will run
daily at the specified time. If you do not specify am or pm, time is
interpreted in 24-hour military time. For example, Sat 11:00 pm and
Saturday 23:00 are both acceptable and specify the same time.
Station Assurance
Station assurance monitors the quality of the connections that users are
experiencing on the wireless network. You can quickly detect stations that are
having problems and take steps to correct them. Use these settings to establish
threshold values for errors and other problems. Station assurance is enabled by
default, with a set of useful default thresholds that you may adjust as desired.
When a connection is experiencing problems and reaches one of these thresholds
in the specified period of time, the Array responds with several actions: an event
is triggered, a trap is generated, and a Syslog message is logged. For example, if a
client falls below the threshold for Min Average Associated Time, this
bouncing behavior might indicate roaming problems with the networks RF
design, causing the client to bounce between multiple arrays and not stay
connected longer than the time to re-associate and then jump again. This can be
corrected with RF adjustments. Station assurance alerts you to the fact that this
station is encountering problems.
Management System
536 ConfiguringaWirelessArray
8. Enable Station Assurance: This is enabled by default. Click No if you
wish to disable it, and click Yes to re-enable it. When station assurance is
enabled, the Array will monitor connection quality indicators listed
below and will display associated information on the Station Assurance
window. When a threshold is reached, an event is triggered, a trap is
generated, and a Syslog message is logged.
9. Period: In seconds, the period of time for a threshold to be reached. For
example, the Array will check whether Max Authentication Failures has
been reached in this number of seconds.
10. Min Average Associated Time: (seconds) Station assurance detects
whether the average length of station associations falls below this
threshold during a period.
11. Max Authentication Failures: Station assurance detects whether the
number of failed login attempts reaches this threshold during a period.
12. Max Packet Error Rate: (%) Station assurance detects whether the packet
error rate percentage reaches this threshold during a period.
13. Max Packet Retry Rate: (%) Station assurance detects whether the packet
retry rate percentage reaches this threshold during a period.
14. Min Packet Data Rate: (Mbps) Station assurance detects whether the
packet data rate falls below this threshold during a period.
15. Min Received Signal Strength: (dB) Station assurance detects whether
the strength of the signal received from the station falls below this
threshold during a period.
16. Min Signal to Noise Ratio: (dB) Station assurance detects whether the
ratio of signal to noise received from the station falls below this threshold
during a period.
17. Max Distance from Array: Min Received Signal Strength: (feet) Station
assurance detects whether the distance of the station from the Array
reaches this threshold during a period.
Management System
ConfiguringaWirelessArray 537
Intrusion Detection
Arrays employ a number of IDS/IPS (Intrusion Detection System/ Intrusion
Prevention System) strategies to detect and prevent malicious attacks on the
wireless network. This window allows you to adjust intrusion detection settings.
Figure 304. Intrusion Detection Settings
The Array provides a suite of intrusion detection and prevention options to
improve network security. You can separately enable detection of the following
types of problems:
Rogue Access Point Detection and Blocking
Unknown access points are detected, and may be automatically blocked
based on a number of criteria. See About Blocking Rogue APs on
page 540.
Management System
538 ConfiguringaWirelessArray
Denial of Service (DoS) or Availability Attack Detection
A DoS attack attempts to flood an Array with communications requests
so that it cannot respond to legitimate traffic, or responds so slowly that it
becomes effectively unavailable. The Array can detect a number of types
of DoS attacks, as described in the table below. When an attack is
detected, the Array logs a Syslog message at the Alert level.
Impersonation Detection
These malicious attacks use various techniques to impersonate a
legitimate AP or station, often in order to eavesdrop on wireless
communications. The Array detects a number of types of impersonation
attacks, as described in the table below. When an attack is detected, the
Array logs a Syslog message at the Alert level.
Type of Attack Description
DoS Attacks
Beacon Flood Generating thousands of counterfeit 802.11 beacons to
make it hard for stations to find a legitimate AP.
Probe Request
Flood
Generating thousands of counterfeit 802.11 probe requests
to overburden the Array.
Authentication
Flood
Sending forged Authenticates from random MAC
addresses to fill the Array's association table.
Association
Flood
Sending forged Associates from random MAC addresses
to fill the Array's association table.
Disassociation
Flood
Flooding the Array with forged Disassociation packets.
Deauthentication
Flood
Flooding the Array with forged Deauthenticates.
EAP Handshake
Flood
Flooding an AP with EAP-Start messages to consume
resources or crash the target.
Management System
ConfiguringaWirelessArray 539
Null Probe
Response
Answering a station probe-request frame with a null SSID.
Many types of popular NIC cards cannot handle this
situation, and will freeze up.
MIC Error Attack Generating invalid TKIP data to exceed the Array's MIC
error threshold, suspending WLAN service.
Disassociation
Attack (Omerta)
Sending forged disassociation frames to all stations on a
channel in response to data frames.
Deauthentication
Attack
Sending forged deauthentication frames to all stations on
a channel in response to data frames.
Duration Attack
(Duration Field
Spoofing)
Injecting packets into the WLAN with huge duration
values. This forces the other nodes in the WLAN to keep
quiet, since they cannot send any packet until this value
counts down to zero. If the attacker sends such frames
continuously it silences other nodes in the WLAN for long
periods, thereby disrupting the entire wireless service.
Impersonation Attacks
AP
impersonation
Reconfiguring an attacker's MAC address to pose as an
authorized AP. Administrators should take immediate
steps to prevent the attacker from entering the WLAN.
Station
impersonation
Reconfiguring an attacker's MAC address to pose as an
authorized station. Administrators should take immediate
steps to prevent the attacker from entering the WLAN.
Evil twin attack
(SSID Spoofing)
Masquerading as an authorized AP by beaconing the
WLAN's service set identifier (SSID) to lure users. Rogue
APs engaging in this type of attack may be auto blocked.
See SSID Spoofing Auto Block on page 184.
Sequence
number anomaly
A sender may use an Add Block Address request (ADDBA
- part of the Block ACK mechanism) to specify a sequence
number range for packets that the receiver can accept.
An attacker spoofs an ADDBA request, asking the receiver
to reset its sequence number window to a new range. This
causes the receiver to drop legitimate frames, since their
sequence numbers will not fall in that range.
Type of Attack Description
Management System
540 ConfiguringaWirelessArray
About Blocking Rogue APs
If you classify a rogue AP as blocked, then the Array will take measures to
prevent stations from staying associated to the rogue. When the monitor IAP is
scanning, any time it hears a beacon from a blocked rogue it sends out a broadcast
deauth signal using the rogue's BSSID and source address. This has the effect
of disconnecting all of a rogue APs clients approximately every 5 to 10 seconds,
which is enough to make the rogue frustratingly unusable.
The Intrusion Detection window allows you to set up Auto Block parameters so
that unknown APs get the same treatment as explicitly blocked APs. This is
basically a shoot first and ask questions later mode. By default, auto blocking is
turned off. Auto blocking provides two parameters for qualifying blocking so that
APs must meet certain criteria before being blocked. This keeps the Array from
blocking every AP that it detects. You may:
Set a minimum RSSI value for the AP for example, if an AP has an RSSI
value of -90, it is probably a harmless AP belonging to a neighbor and not
in your building.
Block based on encryption level.
Block based on whether the AP is part of an ad hoc network or
infrastructure network.
XMS can also auto block rogue APs that are engaging in spoofing (evil twin)
attacks on your SSIDs. This is done on a system-wide basis, for all managed
Arrays rather than for a particular AP or Profile network. See SSID Spoofing
Auto Block on page 184.
Procedure for Configuring Intrusion Detection
RF Intrusion Detection and Auto Block Mode
1. Intrusion Detection Mode: This option allows you to choose the
Standard intrusion detection method, or you can choose Off to disable
this feature. See Array Monitor and Radio Assurance Capabilities in the
Technical Support Appendix of the Xirrus Wireless Array Users Guide for
more information.
Standard enables the monitor IAP to collect Rogue AP information.
Management System
ConfiguringaWirelessArray 541
Off intrusion detection is disabled.
2. Auto Block Unknown Rogue APs: Enable or disable auto blocking (see
About Blocking Rogue APs on page 540). Note that in order to set
Auto Block RSSI and Auto Block Level, you must set Auto Block
Unknown Rogue APs to On. Then the remaining Auto Block fields will
be active.
3. Auto Block RSSI: Set the minimum RSSI for rogue APs to be blocked.
APs with lower RSSI values will not be blocked. They are assumed to be
farther away, and probably belonging to neighbors and posing a minimal
threat.
4. Auto Block Level: Select rogue APs to block based on the level of
encryption that they are using. The choices are:
Automatically block unknown rogue APs regardless of encryption.
Automatically block unknown rogue APs with no encryption.
Automatically block unknown rogue APs with WEP or no
encryption.
5. Auto Block Network Types: Select rogues to automatically block by
applying the criteria above only to networks of the type specified below.
The choices are:
All the unknown rogues may be part of any wireless network.
IBSS/AD Hoc only only consider auto blocking rogues if they
belong to an ad hoc wireless network (a network of client devices
without a controlling Access Point, also called an Independent Basic
Service Set IBSS).
ESS/Infrastructure only only consider auto blocking rogue APs if
they are in infrastructure mode rather than ad hoc mode.
6. Auto Block White list: Use this list to specify channels to be excluded
from automatic blocking. If you have enabled Auto Block, it will not be
applied to rogues detected on the whitelisted channels. Use the Add
Management System
542 ConfiguringaWirelessArray
Channel drop-down to add entries to the Channels list, one at a time.
You can delete entries from the list by selecting them from the Remove
Channel drop-down list.
DoS Attack Detection Settings
7. Attack/Event: The types of DoS attack that you may detect are described
in the Type of Attack Table on page 538. Detection of each attack type
may be separately enabled or disabled. For each attack, a default
Threshold and Period (seconds) are specified. If the number of
occurrences of the type of packet being detected exceeds the threshold in
the specified number of seconds, then the Array declares that an attack
has been detected. You may modify the Threshold and Period.
For the Flood attack settings, you also have a choice of Auto or Manual.
Manual mode threshold and period settings are used to detect a
flood. Packets received are simply counted for the specified time
period and compared against the flood threshold. The default for all
of the floods is Manual mode.
Auto mode the Array analyzes current traffic for packets of a given
type versus traffic over the past hour to determine whether a packet
flood should be detected. In this mode, threshold and period settings
are ignored. This mode is useful for floods like beacon or probe
floods, where the numbers of such packets detected in the air can
vary greatly from installation to installation.
8. Duration Attack NAV (ms): For the duration attack, you may also modify
the default duration value that is used to determine whether a packet
may be part of an attack. If the number of packets having at least this
duration value exceeds the Threshold number in the specified Period, an
attack is detected.
Impersonation Detection Settings
9. Attack/Event: The types of impersonation attack that you may detect are
described in Impersonation Attacks on page 539. Detection of each attack
type may be turned On or Off separately. For AP or Station
Management System
ConfiguringaWirelessArray 543
Impersonation attacks, a default Threshold and Period (seconds) are
specified. If the number of occurrences of the type of packet being
detected exceeds the threshold in the specified number of seconds, then
the Array declares that an attack has been detected. You may modify the
Threshold and Period.
10. Sequence number anomaly: You may specify whether to detect this type
of attack in Data traffic or in Management traffic, or turn Off this type of
detection.
11. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
LED Settings
This window assigns behavior preferences for the Arrays IAP LEDs.
Figure 305. LED Settings
Management System
544 ConfiguringaWirelessArray
Procedure for Configuring the IAP LEDs
1. LED State: This option determines which event triggers the LEDs, either
when an IAP is enabled or when an IAP first associates with the network.
Choose On when radio enabled or On when station associated, as
desired. You may also choose Disabled to keep the LEDs from being lit.
The LEDs will still light during the boot sequence, then turn off.
2. LED Blink Behavior: This option allows you to select when the IAP LEDs
blink, based on the activities you check here. From the choices available,
select one or more activities to trigger when the LEDs blink.
3. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
DSCP Mappings
DSCP is the 6-bit Differentiated Services Code Point (DiffServ) field in the IPv4 or
IPv6 packet header, defined in RFC2474 and RFC2475. The DSCP value classifies
the packet to determine the Quality of Service (QoS) required. DSCP replaces the
outdated Type of Service (TOS) field.
The DSCP Mappings page shows the default mapping of each of the 64 DSCP
values to one of the Arrays four QoS levels, and allows you to change these
mappings.
For a detailed discussion of the operation of QoS and DSCP mappings, please see
Understanding QoS Priority on the Wireless Array on page 467.
Management System
ConfiguringaWirelessArray 545
Figure 306. DSCP Mappings
Procedure for Configuring DSCP Mappings
1. DSCP to QoS Mapping Mode: Use the On and Off buttons to enable or
disable the use of the DSCP mapping table to determine the QoS level
applied to each packet.
2. DSCP to QoS Mapping: The radio buttons in this table show all DSCP
values (0 to 63), and the QoS level to which each is mapped. To change the
QoS level applied to a DSCP value, click the desired QoS level (0 to 3)
underneath it.
Roaming Assist
Roaming assist is a Xirrus feature that helps clients roam to Arrays that will give
them high quality connections. Some smart phones and tablets will stay
connected to an IAP with poor signal quality, even when theres an IAP with
better signal strength within range. When roaming assist is enabled, the Array
Management System
546 ConfiguringaWirelessArray
assists the device by deauthenticating it when certain parameters are met. This
encourages a client with a high roaming threshold (i.e., a device that may not
roam until signal quality has seriously dropped) to move to an Array that gives it
a better signal. The deauthentication is meant to cause the client to choose a
different IAP. You can specify the device types that will be assisted in roaming.
The roaming threshold is the difference in signal strength between IAPs that will
trigger a deauthentication. If the clients signal is lower than the sum of the
threshold and the stronger neighbor IAPs RSSI, then we assist the client. For
example:
Threshold = -5
RSSI of neighbor Array = -65
RSSI of client = -75
-75 < (-5 + -65) : Client will roam
Another example:
Threshold = -15
RSSI of neighbor array = -60
RSSI of station = -70
-70 > (-15 + -60) : Client will not roam
Management System
ConfiguringaWirelessArray 547
Figure 307. Roaming Assist
Procedure for Configuring Roaming Assist
1. Enable Roaming Assist: Use the Yes and No buttons to enable or disable
this feature.
2. Backoff Period: After deauthenticating a station, it may re-associate to
the same IAP. To prevent the Array from repeatedly deauthenticating the
station when it comes back, there is a backoff period. This is the number
of seconds the station is allowed to stay connected before another
deauthentication.
3. Roaming Threshold: This is the difference in signal strength between
IAPs that will trigger a deauthentication, as described in the discussion
above. In most cases, this will be a negative number.
Management System
548 ConfiguringaWirelessArray
4. Minimum Data Rate: If the stations data rate (either Tx or Rx) falls
below this rate, it will trigger a deauthentication.
5. Device Classes and Device Types: You can configure the device classes
or types that will be assisted in roaming. Many small, embedded devices
(such as the default device types: phones, tablets, music players) are
stickythey have high roaming thresholds that tend to keep them
attached to the same IAP despite the presence of IAPs with better signal
strength. You may check off one or more entries, but use care since
roaming assist may cause poor results in some cases.
Management System
ConfiguringaWirelessArray 549
Filters
The wireless Arrays integrated firewall uses stateful inspection to speed the
decision of whether to allow or deny traffic. Filters are used to define the rules
used for blocking or passing traffic. Filters can also set the VLAN and QoS level
for selected traffic.
Figure 308. Filter Lists
User connections managed by the firewall are maintained statefully once a user
flow is established through the Array, it is recognized and passed through
without application of all defined filtering rules. Stateful inspection runs
automatically on the Array. The rest of this section describes how to view and
manage filters.

On XN Arrays, this feature is only available if the Arrays license includes

the Xirrus Advanced RF Security Manager (RSM). See Array Details
System on page 70 to check whether the Array license includes this
feature.

The air cleaner feature (Preset Filters) offers a number of predetermined

filter rules that eliminate a great deal of unnecessary wireless traffic.
Management System
550 ConfiguringaWirelessArray
Filters are organized in groups, called Filter Lists. A filter list allows you to apply
a uniform set of filters to SSIDs or Groups very easily.
Filter Lists
This window shows existing filter lists and allows you to create new ones. The
Array comes with one predefined list, named Global, which cannot be deleted.
Filter lists (including Global) may be applied to SSIDs or to Groups. Only one
filter list at a time may be applied to a group or SSID (although the filter list may
contain a number of filters). All filters are created within filter lists.
Procedure for Managing Filter Lists
1. Enable Stateful Filtering: Stateful operation of the integrated firewall can
be enabled or disabled. If you have a large number of filters and you
dont want to apply them in a stateful manner, you may use this option to
turn the firewall off.
2. Enable Stateful Filtering: Operation of the Application Control feature
can be enabled or disabled. See Application ControlOverview on
page 104.
3. The list of Filter Lists shows the following information:
a. Filter List Name
b. Array Filter Count: The number of filters in this list.
c. Edited Filter Count
d. State: If the list is disabled, you may still add filters to it or modify it,
but none of the filters will be applied to data traffic.
4. Add: Click this button to create a filter list. Enter its name in the dialog
box, and optionally, enable it.
5. Edit: Click this button to edit one selected filter list.
6. Delete: Click this button to delete the selected filter lists. The Global filter
list may not be deleted.
Management System
ConfiguringaWirelessArray 551
7. Enable/Disable Filter Lists: Use these buttons to enable or disable all of
the selected filter lists.
8. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Filter Management
Filters are applied in order, starting with Priority 1.
Click Move buttons to change the order.
This window allows you to create and manage filters that belong to a selected
filter list, based on the filter criteria you specify.
Figure 309. Filter Management
Management System
552 ConfiguringaWirelessArray
Note that filtering is secondary to the stateful inspection performed by the
integrated firewall. Traffic for established connections is passed through without
the application of these filtering rules.
Procedure for Managing Filters
1. Filter List: Select the filter list to display and manage on this window. All
of the filters already defined for this list are shown, and you may create
additional filters for this list.
2. Add Preset Filters: A number of predefined Air Cleaner filters are
available using these buttons, as shown in You can use these very useful
rules to eliminate a great deal of unnecessary wireless traffic, resulting in
improved performance. For more information, please see the Xirrus
Wireless Array Users Guide.
To create a new filter entry:
3. Click the Add button to display the New Filter dialog, showing the Filter
List Name to which the new entry will belong. Enter the new Filter
Name. The filter name must be unique within the list, but it may have the
same name as a filter in a different filter list. Two filters with the same
name in different filter lists will be completely unrelated to each other
they may be defined with different parameter values.
4. Layer: Select the network layer at which this filter will operate.
5. Enable: Use this field to enable or disable this filter.
6. Type: Choose whether this filter will be an Allow filter or a Deny filter. If
you define the filter as an Allow filter, then any associations that meet the
filter criteria will be allowed. If you define the filter as a Deny filter, any
associations that meet the filter criteria will be denied.
All of the remaining fields are optional.
7. Traffic Limit Type/Traffic Limit: Instead of prohibiting or allowing the
specified traffic type, you may cap the amount of traffic allowed that
matches this filter. First choose the units for the limit: kilobits per second
Management System
ConfiguringaWirelessArray 553
(Kbps) for all stations in total or per station, or packets per second (pps)
for all stations in total or per station. Then enter the numeric limit in the
Traffic Limit field underneath.
8. Protocol/Number: Choose a specific filter protocol from the pull-down
list, or choose numeric and enter a Number, or choose ANY to instruct
the Array to use the best filter. This is a match criterion.
9. Port/Number: This is a match criterion. From the pull-down list, choose
the target port for this filter. Choose ANY to instruct the Array to apply
the filter to any port, or choose NUMERIC or RANGE and enter the port
number or range in the provided fields.
10. Source: Define a source address to match as a filter criterion. Click the
radio button for the desired type of address (or other attribute) to match.
Then specify the value to match in the fields which appear. Choose Any
to use any source address. Check Not to match any address except for the
specified address.
11. Destination: Define a destination address to match as a filter criterion.
Select the desired type of address (or other attribute) to match. Then
specify the value to match in the fields which appear. Choose any to use
any source address. Check Not to match any address except for the
specified address.
12. DSCP: (Differentiated Services Code Point or DiffServOptional) Set
packets ingressing from the wireless network that match the filter criteria
to this DSCP level (0 to 63) before sending them out on the wired
network. Select the level from the pull-down list. Level 0 has the lowest
priority; level 63 has the highest priority. By default, this field is blank
and the filter does not modify DSCP level. See Understanding QoS
Priority on the Wireless Array on page 467.
13. QoS: Set packets that match the filter criteria to this QoS level (0 to 3),
selected from the pull-down list. Level 0 has the lowest priority; level 3
has the highest priority. By default, this field is blank and the filter does
not modify QoS level. See Understanding QoS Priority on the Wireless
Array on page 467.
Management System
554 ConfiguringaWirelessArray
14. VLAN/Number: Set packets that match the filter criteria to this VLAN.
Select a VLAN from the list, or select numeric and enter the number of a
previously defined VLAN (see VLAN on page 409). By default, this
field is blank and the filter does not modify the VLAN.
15. Filter Log: If selected, log usage of this filter to Syslog.
16. Click OK when done.
Viewing, modifying, or deleting existing filter entries:
17. Select the desired filter entry. Click Edit to view or modify it.
18. Move Up/Down: The filters are applied in the order, starting with
Priority level 1. To change an entrys position in the list, select it and click
the Move Up or Move Down button.
19. Delete: Click this button to delete the selected filters.
Click the Apply Config button at the top of the configuration window to apply
these changes to the Array. To make these changes permanent, check Save to
flash before using the Apply Config button.
Tunnels
Xirrus XR Arrays offer GRE (Generic Routing Encapsulation) tunneling with
VLAN support. This allows an Array to use tunnels to bridge Layer 2 traffic for
one or more SSID-VLAN pairs onto a single destination network through the
Layer 3 network. GRE tunneling is quite flexible, and can encapsulate many
network layer protocols. As a result, it can support a variety of applications. For
example, a Wi-Fi hotspot can allow guest logins and use the tunnel to give guests
direct access to the Internet, without allowing access to the local network. In a
small office, you may define a tunnel to connect users to the corporate office
network. Tunnels may also used when providing cellular offload capability.
Tunnels may be implemented with:
The Xirrus Tunnel Server (XTS)see the Xirrus Tunnel Server Users Guide.
VTS see Virtual Tunnel Server (VTS) on page 409.
Management System
ConfiguringaWirelessArray 555
To create a tunnel, you specify the Local Endpoint, which should be one of the
Arrays wired ports, and the Primary Remote Endpoint. A Secondary Remote
Endpoint may also be specified in case of a failure at the first endpoint. Traffic for
a VLAN-SSID pair is sent in GRE encapsulated packets across the Layer 3
network from the Array to the remote endpoint. When packets arrive, the
encapsulation is stripped and the resultant packets are passed to your switch with
802.1q VLAN tags for final Layer 2 processing. The process occurs in reverse for
packets traveling in the other direction. One tunnel is able to transport up to 16
VLANs.
The following pages are used to manage tunnels
Tunnel Managementcreates and manages tunnels
SSID Assignmentsselects the SSIDs to be bridged by each tunnel

This feature is only available on XR Series Arrays and Access Points.

Management System
556 ConfiguringaWirelessArray
Tunnel Management
This window allows you to create and manage tunnels.
Figure 310. Tunnel Management
Procedure for Managing Tunnels
To create a new filter entry:
1. Click the Add button to display the Add Tunnel dialog. Enter the new
tunnels Name.
2. Type: Enter the type of tunnel, none or gre.
3. Enabled: The new tunnel is created in the disabled state. Click this
checkbox to enable it.
4. Local Endpoint: Enter the IP address of the Array Gigabit or 10 Gigabit
port where the tunnel is to begin.
Management System
ConfiguringaWirelessArray 557
5. Primary Remote Endpoint: Enter the IP address of the remote endpoint
of the tunnel.
6. Secondary Remote Endpoint: This provides a failover capability. If the
primary tunnel fails, traffic is switched over to the secondary tunnel.
Enter the IP address of the remote endpoint of the secondary tunnel.
7. DHCP Option: When this option is enabled, the Array snoops station
DHCP requests and inserts relay agent information (option 82, in the
circuit-ID sub-option) into these DHCP packets. Information inserted
includes Array BSSID, SSID name, and SSID encryption type.
8. MTU: Set maximum transmission unit (MTU) size.
9. Failover Ping Interval: The tunnel mechanism will ping the current
remote endpoint periodically to ensure that it is still reachable. Enter the
ping interval (in seconds).
10. Failover Ping Failures: Enter the number of consecutive ping failures that
will cause the Array to consider the tunnel to be down.
11. Click OK when done.
12. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
13. Proceed to SSID Assignments to define the SSIDs (and associated
VLANs) for which each tunnel will bridge data. You may create up to 16
tunnels. Each will need an SSID/VLAN pair assigned to it so that it can
function properly.
Viewing, modifying, or deleting existing filter entries:
14. Select the desired tunnel entry. Click Edit to view or modify it. Click the
Apply Config button at the top of the configuration window to apply
these changes to the Array.
15. Delete: Click this button to delete the selected filters.
Management System
558 ConfiguringaWirelessArray
SSID Assignments
This window allows you to select the SSIDs to be bridged by each tunnel. Station
traffic for SSIDs assigned will be bridged through a tunnel regardless of whether
these SSIDs have VLANs defined for them. If there is a VLAN defined for an SSID
that is assigned to a tunnel, then station traffic bridged through that tunnel will be
tagged accordingly.
Figure 311. Tunnel SSID Assignments
Procedure for Assigning SSIDs
This window lists the tunnels and SSIDs that you have defined. SSIDs to be
tunneled do not need to be associated with a VLAN (see SSID Management on
page 471).
1. For each tunnel, select the SSIDs that are to be bridged to the remote
endpoint. Clear the checkbox for any SSID that you no longer wish to
include in the tunnel.
Management System
ConfiguringaWirelessArray 559
2. Click the Apply Config button at the top of the configuration window to
apply these changes to the Array. To make these changes permanent,
check Save to flash before using the Apply Config button.
Management System
560 ConfiguringaWirelessArray
Management System
XMSAdministration 561
XMS Administration
XMS may be administered from the The XMS Web Client, and from a special tool
provided with the server for XM-3300 and XMS-9000-WIN only: the Xirrus Server
Management Tool (XSMT). The XMS web client and XSMT have tools for XMS
server administration both include advanced management operations.
An overview of managing the server is given in the following sections:
About Managing the XMS Server on page 562
About the XMS Database on page 563
Details of managing a server hosted on a Management Appliance (XM-3320/
3340/3360) or a Virtual Appliance are discussed in:
Managing XMS on XM-3320/3340/3360 and Virtual Appliances on
page 564

If you are an XMS Cloud customer, Xirrus automatically performs almost all
of the tasks in this chapter for youtasks that are reserved for Xirrus
personnel. The following Settings pages are the only ones that are available
for management by Cloud customers:
About XMS
Viewing XMS Server Status on page 569
XMS Users on page 584
Audit Log on page 617
Create Custom Fields on page 587
Create Custom Actions on page 588
The rest of this chapter (other than the web client pages mentioned above) is not
applicable to XMS Cloud customers.

Wireless Arrays must be running ArrayOS Release 6.4 or above to be
managed by XMS Cloud. You cannot use XMS Cloud to upgrade Arrays
to Release 6.4 from an earlier release.
Management System
562 XMSAdministration
Details of managing a server hosted on the XM-3300 or XMS-9000-WIN are
discussed in:
Managing XMS on XM-3300 and XMS-9000-WIN Systems on
page 624
About Managing the XMS Server
The tools for managing the XMS server are different, depending on the servers
host platform.
Managing the XM-3320/XM-3340/XM-3360 and the Virtual Appliance
The Virtual Appliance running under VMware and the Linux-based
Management Appliances use the browser-based XMS web client
(Figure 312 on page 564) to manage the server. Database management
functions are available in the web client.
See the sections starting with Managing XMS on XM-3320/3340/3360
and Virtual Appliances on page 564.
Managing the XM-3300 and the XMS-9000-WIN
These Windows-based products use the Xirrus Server Management Tool
(XSMT Figure 364 on page 627) for advanced XMS server and database
management. Other server management functions are available in the
web client.
See the sections starting with Managing XMS on XM-3300 and XMS-
9000-WIN Systems on page 624.
Management System
XMSAdministration 563
About the XMS Database
The XMS database maintains the properties, status, and statistics for all the
managed wireless Arrays represented in the network, as well as configured maps,
events and reports. It is important to back up your database regularly, which
means establishing a schedule that suits your networks activity.
Note: The XMS server does not have a default backup schedule, so it is very important
for you to create a backup schedule after installation.
You may set up a backup schedule to best suit your needs the time required for
a backup depends on the size of the database. And because XMS provides a client
option for managing backups, they can be initiated from any client.
To manage the database, see:
Database Backup Settings on page 575
XSMT - Database Tools on page 633.
XMS does not purge old backups automatically. We recommend that you
periodically review the backup files on your file server and delete older ones as
needed, depending on the space available on the server.
Management System
564 XMSAdministration
Managing XMS on XM-3320/3340/3360 and Virtual Appliances
Use the browser-based XMS web client (Figure 312) to manage the XMS server on
the Xirrus XM-3320/3340/3360 Management Appliances and on the VMware-
based Virtual Appliance. Use the web client to perform mandatory initial
configuration, to restart or reboot the server, and for server maintenance. The
XMS server is started automatically when your Appliance is restarted.
.
Figure 312. Server Management using the Web Client
The web client has multiple pages that manage settings for different XMS
functions. Click Settings on the top of the page, then click one of the displayed
links to go to the desired page. How to access the web client and descriptions of
its pages are found in the following sections.
Accessing the Web Client on page 565
Initial Server Setup on page 567
Viewing XMS Server Status on page 569
Network Settings on page 571
Date and Time Settings on page 572
RAID Status on page 574
Database Backup Settings on page 575
XMS Users on page 584
Email Settings on page 600
Polling Settings on page 601
Management System
XMSAdministration 565
Changing the SSH Server Address on page 603
SNMP Trap Receivers on page 605
XMS Setup Wizard on page 606
Audit Log on page 617
Viewing Server Log Files on page 618
Managing the XMS Server License on page 620
Performing Server Upgrades on page 621
Resetting the XMS Server on page 622
Accessing the Web Client
Note: Web client access to the XMS server requires access to port 9090 and 9443.
Ensure that this port is open in any firewalls that exist between your browser and the
XMS server.
To access the web client, set your browsers URL to the XMS server machines IP
address or host/domain name, followed by a:9090. For example, http://
192.168.10.40:9090.
.
Figure 313. Starting the Web Client
Log in to the web client the default for both fields is admin. In a few moments
the web client Dashboard page appears. Click the Settings button at the top to
display the Status page. (Figure 312) It shows a summary of the running state of
Management System
566 XMSAdministration
the server. If you have not already performed the required initial setup for a
newly installed server, proceed to Initial Server Setup, below. Otherwise, you
may skip that section.
Note: You may use the Command Line Interface (CLI) to manage the XMS server. Access
it at port 2022 and log in using admin/admin. Do not use port 22.
Management System
XMSAdministration 567
Initial Server Setup
The following steps must be completed to configure the XMS server for proper
performance. If you have already completed these steps, you may skip this
section.
1. XMS Setup Wizard on page 606use the XMS Setup Wizard to enter
the license for the XMS server and start discovery of the wireless
network.
IMPORTANT! The XMS server does not have a default backup schedule, so you must
create one after installation.
2. XMS Users on page 584set up user accounts for XMS.
Initial Network Settings
Note: The XMS Server requires a valid license for full operation. If one is not present, it
will be requested when you open a client. See Managing the XMS Server License
on page 620.
1. Select Settings >Network to display the Network Settings window.
Figure 314. Changing Network Settings
Management System
568 XMSAdministration
Note: You may use one or both of the XMS Management Appliances Ethernet ports. If
using both, then one of the ports is typically reserved for management.
2. We recommend that you assign a Static IP address to each Ethernet port
that is connected. The Appliance uses DHCP by default. If you have
configured reserved leases for the ports in your DHCP server, skip to
Step 3 below. If you leave the DNS fields on this page blank and you are
using DHCP, then the gateway and DNS servers configured in your
DHCP server will be used.
If you have not assigned a reserved DHCP lease to the Appliance, select
the Static option in Configuration Server Protocol under Network
Interfaces for each Ethernet port that you are using. Make sure that
Enable Interface is set to Yes, and enter the IP Address and Subnet
Mask. Under General Network Settings, enter the Default Gateway
Address and the DNS Domain and DNS Servers.
Note: The default IP address for eth0 is 10.0.2.10; for eth1 it is 10.0.2.11.
3. The Hostname of the Appliance is set to Xirrus-XMS by default. If you
wish to change the Appliances DNS Hostname, please see General
Network Settings on page 571 for other changes that you should make
to ensure proper operation of XMS in your network.
Management System
XMSAdministration 569
Viewing XMS Server Status
Click the Status link to review the status and version number of the XMS Server,
and the status and size of the Database (in bytes). The status of the RMI Registry
is also indicated. XMS Uptime indicates how long the server has been running,
while Appliance Uptime indicates how long the host computer has been running
since its last reboot.
Figure 315. The Status Page
Restart Application
If XMS is not running properly, you may click the Restart Application
button on the lower left to restart the XMS server software. If the server is
currently running, an orderly shutdown will be performed first.
Reboot Appliance
The Reboot Appliance button will reboot the Management Appliance
this will shut down XMS related processes in an orderly manner before
rebooting. Rebooting and restarting will take about two minutes on a new
Management System
570 XMSAdministration
Management Appliance. As XMS is used and the database grows, startup
integrity checks will take longer. (For shutdown, see below.)
Shutting down the XMS Server
Shutting down the server incorrectly can cause problems the next time you start
XMS. Use the following procedure:
1. Close all clients.
2. On the Status page, click the Shutdown Appliance button.
3. The Management Appliance will then gracefully shut down. A
confirmation notice is displayed immediately when the shutdown
process is initiated. It may take a few minutes for the Appliance to
actually shut down and power itself off.
Management System
XMSAdministration 571
Network Settings
Select the Network link to display the Network Settings page. This page allows
you to manage DNS settings for the server, and set the IP address and
transmission parameters for the Ethernet ports.
Figure 316. Changing Network Settings
Note: You may use one or both of the XMS Management Appliances Ethernet ports. If
using both, then one of the ports is typically reserved for management.
Network Interfaces Settings for eth0 and eth1
Check that Enable Interface is set to Yes for each Ethernet port that you
plan to use. Auto Negotiate should normally be left enabled, which is the
default. This will correctly set the Ethernet ports speed and duplex mode
automatically in most cases.
For recommended IP addressing, please see Initial Network Settings
on page 567.
General Network Settings
The Hostname of the Appliance is set to xirrus-xms by default. Note that
hostnames are not case-sensitive. Xirrus Arrays send traps to the
Management System
572 XMSAdministration
hostname Xirrus-XMS to announce their presence on the network and
speed discovery. Thus, if you change the Appliances DNS Hostname,
you should create an alias in your networks DNS server to ensure that
the Appliance is accessible using both the name Xirrus-XMS and your
new name.
If you have clicked the Static radio button under Network Interfaces -
Configuration Server Protocol, you must enter the Default Gateway
Address for this Appliance, and enter the DNS Domain and DNS
Servers.
Click the Save button when you have finished making your changes.
Date and Time Settings
NOTE: To use SNMPv3 successfully, system time must be set using an NTP server on
both the XMS server host machine and all Arrays using SNMPv3. This is because
SNMPv3 requires synchronization between the XMS server and the Arrays so that the
system time difference between them never exceeds more than 150 seconds. If the time
difference exceeds 150 seconds, SNMPv3 suspects a security breach and removes the
SNMPv3 credentials for affected Arrays from the database. This means that the Array
will appear to be down and statistics will not be polled until the Array is re-discovered. A
manual refresh of the Array should remedy the situation. See Add Devices on
page 167.
Figure 317. Changing Date and Time Settings
Management System
XMSAdministration 573
Click the Date & Time link to display the Date & Time page. This page manages
your time zone and sets the time manually or sets up Network Time Protocol
usage to obtain accurate time settings automatically.
Time Zone and Daylight Savings Time
Select your local Time Zone from the pull-down list.
Enable Auto Adjust Daylight Savings if you want the system to adjust
for daylight savings automatically, otherwise click No.
Using Network Time Protocol
To have the time of day set automatically from an accurate time server, set
Use Network Time Protocol to Yes (this is the default). You may modify
the NTP Servers (primary, secondary, tertiary), or leave them at the
default values which use NTP Pool time servers (http://
www.pool.ntp.org/).
Setting time manually
Set Use Network Time Protocol to No. Use the Adjust Time and Adjust
Date fields that appear to set the correct time and date.
Click the Save button when you have finished making your changes.
Management System
574 XMSAdministration
RAID Status
If a Redundant Array of Independent Disks (RAID device) is part of your XMS
server, this page shows its status. This is only present for XM-3340 and XM-3360
Appliances. Click the RAID Status link in the System section of the Settings
menu to display this status page.
Figure 318. RAID Status
The following information is shown:
RAID Levelthe scheme used to manage the disks.
Array sizeshown in three different units: kB, GiB (1 gibibyte= 2**30
bytes= 1,073,741,824 bytes) and GB (10**9 bytes = 1,000,000,000 bytes).
Total Drivesthe number of drives deployed as part of your storage
system.
Failed Drivesthe number of drives that have failed.
Persistenceshows whether you have a persistent superblock. This
contains RAID configuration information and is written on all RAID
disks.
Statethe status of the RAID device.
Management System
XMSAdministration 575
Database Backup Settings
The XMS server does not have a default backup schedule, so you should perform
the following steps soon after you have installed the XMS server:
Manage Locationsset up one or more locations for storing backup files.
Manage Schedules or Backup Nowset up a schedule for performing
backups.
The following pages are used to manage XMS backups:
Manage Locations on page 575
Manage Schedules or Backup Now on page 579
Restore on page 581
Import Backup Archive on page 582
Backup Status on page 583
Note: On the Xirrus Management Appliance (XM-3320/3340/3360) and Virtual
Appliance servers, the database and all configuration files are backed up, including any
uploaded files for captive portals, software update, etc.
Manage Locations
This page sets backup locations for the XMS database. To display this page, click
the Manage Locations link in the Backup section under Settings at the top of the
web client page.
The Backup Locations list shows the entries that you have already created.
Figure 319. Backup Locations List
Management System
576 XMSAdministration
The XMS server has one predefined location, local, which is stored on the server
machines file system (although it does not appear in the Backup Locations list).
For improved data protection, we recommend that you define and use at least one
location for backups, other than on the server. For example, you might perform an
on-site backup weekly and an off-site backup monthly.
To specify a backup location, click Add Location. Enter a Name for this location
entry. The remainder of the entry depends on the Location Type that you select.
Location Type: Windows File Share (Figure 320)
Specify the Path for the folder where files are to be stored. The path
must use the Windows Uniform Naming Convention (UNC) format
(\\ComputerName\SharedFolder\Resource) or the Server Message
Block Protocol (SMB) format (smb://URL).
You may enter a Domain name if necessary. If the backup location is
on a standalone server, you should normally leave the domain field
blank.
Enter a User Name and Password/Confirm Password that will give
you write privileges for that folder. While the username and
password are optional, we highly recommend that the backup file
server be configured to require password protection.
Figure 320. Backup LocationWindows File Share
Management System
XMSAdministration 577
Location Type: FTP (Figure 321)
Specify the FTP Server where files are to be stored, for example,
ftp.xyzcorp.com.
Specify the FTP Directory for the backup files.
If you do not select Anonymous FTP, enter an FTP Username and
FTP Password/Confirm FTP Password that will give you write
privileges for that folder.
Figure 321. Backup LocationFTP
Location Type: SCP (Figure 322)
SCP uses the Secure Copy Protocol, based on SSH, for data transfer.
Specify the SCP Server where files are to be storedthe hostname,
DNS name, or IP address of the SCP server.
Specify the SCP Directory for the backup files.
If you need to change the SCP Port from the default value of 22, enter
it here.
Enter an SCP Username and SCP Password/Confirm SCP Password
that will give you write privileges for that folder.
Management System
578 XMSAdministration
Figure 322. Backup LocationSCP
Click OK when done. XMS will verify that it is able to access the location and will
inform you of its success or failure. This location will be added to the displayed
list of backup locations. Click Add Location again if you wish to enter another
backup location.
Note that you may change a location entry by selecting it and clicking Edit
Location. You may delete one or more location entries by selecting them and
clicking Delete Location(s).
Once you have successfully specified the backup location, you may proceed to
use the other Backup pages.
Management System
XMSAdministration 579
Manage Schedules or Backup Now
This page specifies when scheduled backups are to be performed automatically.
To display it, click the Manage Schedules link or the Backup Now link in the
Backup section under Settings at the top of the web client page.
The Schedule Name list shows the schedules that you have already created.
Figure 323. Backup Schedule List
If you wish to perform a one-time immediate backup, click the Backup Now link.
Enter a Backup Name and select a Location Name specifying where to put the
file. Click OK. You will automatically be taken to the Backup Status page to view
the results.
Figure 324. Backup Now
To enter a schedule, click the Schedule a Backup button. (Figure 325) We
recommend that you schedule backups for off-peak usage hours since they can
generate significant activity on the server.
Management System
580 XMSAdministration
Enter a Backup Schedule Name for this schedule entry and select a Location
Name to use for the backup. (Figure 325) If you wish the backup to go to multiple
locations, you can schedule another backup for that location (or copy the backup
file).
Select the Schedule Type: Daily, Weekly, or Monthly.
Figure 325. Enter a Backup Schedule
Depending on the selected Schedule Type, different fields will be displayed. For a
monthly backup, specify the day of the month (only one day may be selected, but
you can always specify more schedule entries for additional monthly backup
days). For a weekly backup, check all of the days of the week on which the
backup is to be performed (one or more days are allowed).
Regardless of the selected Schedule Type, enter the Time of Day for the backup.
Then click the OK button underneath. Your new schedule entry will be listed,
showing its name and scheduled days and time. For example, Figure 325 shows
an entry named Backup-Mon which will be performed every Monday at 1:59AM.
Management System
XMSAdministration 581
To remove schedule entries, select them and then click Delete Backup
Schedule(s). This deletes schedule entries, not backups (like those that are listed
on the Restore page).
To edit a schedule entry, select it and then click Edit Backup Schedule.
To see the status of backups, including current and completed backups, use the
Backup Status page.
Restore
This page lists completed backups and allows you to select and restore one of
them. To display it, click the Restore link in the Backup section under Settings at
the top of the web client page.
Choose a value from the drop-down list in Select Backup Location to display a
list of all the backup files found in the specified location. Each backup is identified
by its Backup Name, Backup Date/Time, and Backup Size. (Figure 326) The
most recent backup is listed first.
Figure 326. Restoring Backups
If you wish to restore your XMS database from a previously saved version, select
that entry and click the Restore button. You will be asked enter your password to
verify your permission to proceed.
Management System
582 XMSAdministration
The restore operation can impact system performance and should be scheduled
for off-peak hours. After the restore operation is complete, you must take these
actions:
Close all XMS client applications.
Reboot the XMS Appliance.
Note: To delete backups on all platforms, perform the deletions directly from the file
system. They are found in the Backup Location that you specified.
Import Backup Archive
This feature uploads a backup archive from a specified location to the XMS server
so that it can be restored. This is instead of using a backup location. For example,
you can back up an XMS server using the local backup location and then
download the entire archive to another location via HTTP in the browser. You can
then take that backup archive and import it to another XMS server.
Figure 327. Import Backup Archive
Backups are archive zip files that have a specialized XMS format. Only files in this
XMS-generated backup format are accepted for import.
To import a backup, click Choose File and browse to the desired file. Then click
Upload.
Management System
XMSAdministration 583
Backup Status
This page lists current and recent backups and shows their status. To display it,
click the Backup Status link in the Backup section under Settings at the top of the
web client page.
Figure 328. Backup Status
Management System
584 XMSAdministration
XMS Users
This page allows you to control access to XMS by managing XMS user accounts.
You may add, edit, delete, or export accounts, or change passwords.
Open the XMS Users page by clicking the Settings link near the top of the
window, then select XMS Users. You may export values, or modify the display of
this page (sorting, selecting columns, etc.) in the same way described in About
Using the Arrays Page on page 60.
Figure 329. Managing XMS User Accounts
This page contains a list of all user accounts currently available. (Figure 329) To
create an account for a new XMS user, click the Add button on the upper left. The
Add New User dialog is displayed. (Figure 330)
Figure 330. Add an XMS User Account (XMS Cloud)
Management System
XMSAdministration 585
Enter the following fields, then click OK when done.
User NameEnter a unique name for the new user. For XMS Cloud, the
user name must be in the form of an email address, so that the users
domain is specified, i.e., [email protected]. For non-Cloud XMS
servers, just a user name is sufficient, e.g., jsmith.
GroupChoose the privilege level from the pull-down list, either admins
with read/write privileges (called Network Admins for XMS Cloud, or
Super Admins for non-Cloud XMS), or Users with read-only privileges.
Read-only users can not make changes to XMS settings or to Array
configuration.
PasswordEnter a password for this user.
Confirm PasswordRepeat the password for this user.
Idle Time OutIf a user session is idle for this length of time, the user is
logged out. Select an idle time from the drop-down list, or select Never to
prevent the user from timing out.
Force user to set new passwordat the first login, the user will be
prompted (and required) to enter a new password.
To modify the permissions or timeout for a user account, select the checkbox to
the left of the entry and click the Edit button on the upper left. Make the desired
changes and click OK. The changes will be applied the next time that the user logs
in, but will not affect a currently logged in user.
To modify a users password, select the checkbox to the left of the entry and click
the Change Password button. You must correctly enter the users Old Password,
then enter the New Password and retype it in Confirm Password, then click OK.
To remove one or more user accounts, select the checkboxes to the left of the
entries and click the Delete button. You will be asked to verify this action.
Management System
586 XMSAdministration
Customization
The Customization pages allow you to define your own custom fields and action
buttons for the Monitor Arrays and Arrays (Configure) pages. These fields
allow you to add all kinds of information and functionality to XMS for Arrays.
For example, you might use extra columns to add an Asset Tag to each Array, or
to add notes on support cases.
Using a Custom Action, you might add a button to access your companys web
portal for managing assets. Then you can open the portal to manage a selected
Array with a click of the button.
These features are discussed in the following pages:
Create Custom Fields
Use this page to define a new column to add to the Arrays table, where
you can place Array information that your company uses.
Create Custom Actions
Use this page to add a button for a new function. Define the action that
the button will take by specifying a URL. The URL can start your desired
web application with data based on the currently selected Array.
Management System
XMSAdministration 587
Create Custom Fields
This page is used to define a new column for the Arrays list. This column will be
available on the Monitor Arrays page and the Arrays (Configure) page. You
may add up to five new columns and use them for any sort of information that
youd like to keep with each Array. For example, you might add an asset tag
column, or a column for notes regarding support actions for this Array.
Open this page by selecting Create Custom Fields from the Settings menu near
the top of the window.
Figure 331. Custom Fields Page
Enter the desired Field Name for the new column (this name will be used as the
header for this column in the Arrays list), and add an optional Description for
your reference if you wish. The description will only appear in the list of fields on
the Custom Fields page it is not used anywhere else. Click Add when done. You
may repeat the procedure to create up to a total of five new fields. Each new
column may be used to contain strings up to 255 characters long.
The new field will be displayed in the list below the Add button. You may remove
an entry by clicking the Delete button to its right. You may modify the Field
Name or Description by clicking the Edit button to its right. If you have
populated this custom column with data, the data will be unaffected and will still
exist under the edited Field Name.
The new column is not automatically displayed on the Arrays list. To display it,
go to the Monitor Arrays page or the Arrays (Configure) page and use the
Select Columns function. The new field is typically found by scrolling to the
Management System
588 XMSAdministration
bottom of the Hidden Columns list. See Select Columns on page 61 for more
details.
To populate the new column with data for as many Arrays as you like, see
Custom Field Values on page 125.
Create Custom Actions
This page allows you to define a custom button that adds a new function to the
Arrays list. Associate an action with the button by specifying a URL to open when
the button is pushed. The URL can include variables. For example, suppose you
added the new column titled assetTag to the Arrays list using the Create Custom
Fields, and then you entered values for this field for each Array using the Create
Custom Actions page. You could then define a new button labeled Asset
Tracking, for example, that would go to your Asset Tracking Manager with a
selected Arrays asset tag, using the URL:
http://track.xyzcorp.com/?assettagno=%assetTag%
Figure 332. Custom Actions Page
You may choose to add the custom action button to the Monitor Arrays page
and/or to the Arrays (Configure) page. You may add a number of new custom
actions.
Management System
XMSAdministration 589
Open this page by selecting Create Custom Actions from the Settings menu near
the top of the window. (Figure 332)
Enter the desired Name for the new button (this name will be used as the buttons
label), and add an optional Description for your reference if you wish. The
description will only appear in the list of entries on the Custom Actions page it
is not used anywhere else.
Enter the URL to go to when this custom button is pushed. The URL may include
one or more variables:
http://track.xyzcorp.com/?assettagno=%assetTag%
You may use http or https. To pass a custom field name to a variable in the URL,
just surround the name with % signs, as shown above for the custom field that we
defined named assetTag.
XMS provides four predefined variables for your use:
%ipaddress%
%hostname%
%macaddress%
%serialnumber%
Select the page(s) where you want the new custom action button to appear. Select
Show in Monitor View to add the custom action to the Monitor Arrays page.
Select Show in Configure View to add the custom action to the Arrays
(Configure) page. You may add the action to either, or to both.
Click Add when done.
The new custom action will be displayed in the list below the Add button. You
may remove an entry by clicking the Delete button to its right. You may modify
any of the actions settings by clicking the Edit button to its right.
Management System
590 XMSAdministration
Support
The support pages provide automated processes for Xirrus personnel to quickly
gather the information they need to check on beta software performance and to
provide information for future improvement. Currently, there is only one support
page.
Array Diag Log Upload
This page is provided as a utility for gathering data from Arrays in your network
that are running beta release software, although it may be used with Arrays
running older ArrayOS versions as well. It provides a mechanism that can
automatically upload Array diagnostic logs to Xirrus so that the information
required to monitor and improve beta product performance is available. You may
also use this page to upload diagnostic files to your own FTP server.
The settings allow you to specify an FTP server for uploading log files, test the
connection to the server, optionally set a schedule for uploading times, and select
the Arrays from which to gather diagnostic logs. When an Array Diag Log
Upload starts, all of the selected Arrays will generate diagnostic information,
which is then uploaded by this utility.
Figure 333. Array Diagnostic Log Upload
Management System
XMSAdministration 591
The settings for this page are described in the following sections:
Set Up FTP Server
Enter a Schedule (optional)
Select Arrays and Test Connection
Set Up FTP Server
Specify Server Name or IP Address, the Directory, and login details. Typically, if
Xirrus personnel request your diagnostic logs, they will provide you all the
details for connecting to the proper FTP server.
Enter a Schedule (optional)
If you want diagnostic logs to be sent automatically on a regular schedule, specify
the Schedule Type: Hourly, Daily, Weekly or Monthly. Additional fields will be
displayed as appropriate. For example, Time of Day is requested for a daily
schedule.
Select Arrays and Test Connection
Select the check boxes to the left of the Arrays whose diagnostic files are to be
collected. If you are sending data for a set of Arrays that are running a particular
software release, you may find it handy to sort the Arrays by clicking on the
Software Version column header.
When you are done, click the Test Connection button to check that the Arrays can
connect to the specified FTP server and write files to it. When this test runs
correctly, click the Save Settings button to save the FTP Server information,
schedule (if any), and your other settings. Once you have selected the Arrays and
verified the connection to the server, you may use the Upload Now button to do a
one-shot collection and upload of diagnostic files.
Management System
592 XMSAdministration
XMS API
XMS provides an API interface conforming to the RESTful API model. Developers
of custom applications may use this read-only API to fetch information from the
XMS database. The interactive API Documentation page provides documentation
for the API. Security for the XMS RESTful API is provided with tokens granted
using an OAuth 2.0 mechanism.
Your custom application may use the XMS API for purposes such as integrating
with third party applications or creating your own applications for network
analysis. Using the RESTful API eliminates the need to use SNMP which can be
cumbersome for polling large amounts of data. Results are returned in JSON
format (JavaScript Object Notation), a text-based open standard for human-
readable data interchange. API documentation is tightly integrated with the
server code. The API Documentation page allows you to interact with the API in
a sandbox UI that gives clear insight into the API response to parameters and
options.
The XMS API is described in the following topics:
API Settings on page 593
Obtaining an OAuth Token on page 593
Using the API Interface on page 594
API Documentation on page 595
API Documentation Toolbar on page 599
Management System
XMSAdministration 593
API Settings
The XMS RESTful API is disabled by default. Use this page to enable granting of
tokens and access to the XMS API. To open this page, click Settings at the top of
the page and then use the API Settings link.
Figure 334. API Settings
Make sure that the checkbox for Enable API access to XMS is checked, then click
the Submit button.
Obtaining an OAuth Token
Security for the XMS RESTful API is provided with OAuth 2.0. Your custom
application must request a token from an authorization server on the XMS server.
That token is then presented to access the XMS API. The authorization server uses
the OAuth 2.0 standards client credential grant model. This allows you to obtain
a token by presenting credentials from an admin or user account. Please note that
the authorization server will issue only one token on behalf on of any account at
any given time. If you have a need for multiple tokens, then you will need
multiple accounts.
Presenting User Credentials for a Token
Enable API access to XMS as described in API Settings before requesting a token.
A user-developed application must request a token by presenting the following
information to this URL:
https://<xms-server hostname or IP addr>:9443/oauth/token
Management System
594 XMSAdministration
client_id: username of an administrator or user account on the Array
(username and client_id must match).
client_secret: password for the same account on the Array.
grant_type: client_credentials
The authorization server provides a token that your application may use for read-
only access the XMS API. This token remains valid for 7 days (604800 seconds).
The token will not be affected by deletion of the original account associated with
it, or by a password change on that account.
For example, you might use the cURL command below to request a token. In this
example, the command is executed on the XMS server directly (localhost).
curl -X -v -d
'client_id=<username>&client_secret=<password>&grant_type=
client_credentials' -X POST https://localhost:9443/oauth/token
Example result:
{"access_token":"be0f81fb-b41f-44fa-b56a-c8979fdef949",
"token_type":"bearer","expires_in":604799,"scope":"read"}
Using the API Interface
Once registration is completed and a token has been obtained, your application
may access the RESTful API at the following URL. This is displayed on the
bottom of the API Documentation page as BASE URL. Use the token that you
obtained above, your client credentials, and the <api-name> and parameters
described in the API Documentation.
https://<XMS-server hostname or IP addr>:9443/api/v1/<api-name>
The API response is described in detail in the API Documentation, and you may
click the Try it out button to see the actual response to a particular call.
Management System
XMSAdministration 595
API Documentation
The API Documentation page lists all of the APIs that are available along with
their calling parameters, if any, and allows you to perform sample calls and view
sample output.
Figure 335. XMS API Documentation
The XMS API is read-only and consists almost entirely of GET methods. It may
include POST methods, but the purpose of these is to fetch information in
unusual cases.
Management System
596 XMSAdministration
API Types
The RESTful API on XMS is broken into a number of headings by type, such as:
applications, arrays, and profiles. Each heading is a node that may be clicked to
expand or collapse the list of corresponding API requests available in XMS. Since
this is a read-only API, the list consists almost exclusively of GET operations.
The figure below shows part of the list displayed by clicking /arrays. Click again
to collapse (hide) the list. The .json string in the names shown, for example GET /
arrays.json/{array-name}/ssids, indicates that the return values use JSON
formatting. A parameter in brackets, e.g., {array-name}, indicates that information
is returned for a particular item (in this case, the named Array), rather than for all
Arrays.
Figure 336. API Settings Requests List
GET requests are available for data shown in many of the monitor pages
described in the section titled, About Monitor Pages on page 32.
The search GET requests can be used to find a particular kind of object with an
attribute that includes the search string. This search feature is quite similar to
Searching on page 64. For example, if you use GET /search.json/arrays/
{search-query} to search for 100, then the results would include Arrays whose
IP Address or Hostname have 100 anywhere.
Management System
XMSAdministration 597
GET Requests
Each request name in the list is a link. To the right of the name is a brief summary
of the commands function. Click the link to see more information and to try the
operation and see its output.
The figure below shows the request for GET /arrays.json/{array-name}/ssids.
Click again to collapse (hide) the API details.
he
Figure 337. API GET Request Details
High-level details are shown, including:
Implementation Notes: additional information about the function of this
operation.
Response Class: a list of the items returned and their types. Click Model
Schema to show them as a JSON Schema (http://json-schema.org/).
Response Content Type (limited to JSON at this time).
Parameters: a list of the parameters for this operation. The Description
field gives additional information about the expected value. Parameters
that are not flagged as (required) are optional. Some parameters may
Management System
598 XMSAdministration
constrain you to choosing values from a drop-down list. For example,
sortOrder offers the options of ascending or descending. In some cases,
there may be two versions of a request, with and without parameters. For
example, GET /arrays.json/{array-name} returns data for a particular
Array, while GET /arrays.json/ returns data for all Arrays.
Trying a GET Request
The Try it out! button allows you to send the GET request to the XMS API and see
its response. Developers can use this feature to design and implement
applications that use this response.
Figure 338. API GET Request Response
Management System
XMSAdministration 599
Enter the desired Parameters and click the Try it out! button. An example is
shown in Figure 338.
The figure above shows the response for GET /arrays.json/{array-name}/ssids.
The response is produced in the human-readable JSON format. The data shown
are as described in The Arrays List on page 65. Click Hide Response if you
wish to hide the output.
The Request URL field shows the exact form of the URL used to perform this
operation. The Response Code and the Response Header are standard for
HTTP(S).
The exact format of the returned data is displayed in the Response Body field.
Use its scroll bar to view the entire response.
API Documentation Toolbar
Figure 339. API Documentation Toolbar
The Status and Settings sections each have a toolbar as shown above, offering the
following options.
Show/Hideexpands or collapses this list of GET requests. Hiding and
then showing again displays the requests as they were before, i.e.,
expanded GET requests will still be expanded when displayed again.
List Operationsexpands this list of GET requests. Each individual
entry is collapsed.
Expand Operationsshows all of the GET requests in this list. Each
individual entry is expanded.
Rawshows the source XML code for this list of GET requests. Click the
link for the API Documentation page again to return to the normal
display.
Management System
600 XMSAdministration
Applications
Email Settings
Some features, such as Viewing a Report, allow you to email information from
XMS to yourself or others. When XMS needs to send email, it uses an SMTP
server to do so. Before XMS can send any emails, you must specify which server
to use and provide authentication information.
Figure 340. Changing the Email Server
To specify the SMTP server for XMS to use, click Settings at the top of the page
and then use the Email link. (Figure 340)
Enter your SMTP Server Address and SMTP Server Port. Specify the User and
Password that XMS must use to access the server. Select an Encryption type.
When XMS sends an email, it will identify it as being sent from the email address
that you specify in the Sender Email field. You may click the Test Email button to
verify that you have specified the SMTP server correctly. Enter your email address
in the dialog box that appears to check that XMS is able to use SMTP to
successfully send an email.
Click Save when done.
Management System
XMSAdministration 601
Polling Settings
Figure 341. Changing Polling Rate
Click the Polling link to display the Polling page. This page changes the rate at
which various types of network information are updated. Note that for XM-3300
and XMS-9000-WIN servers, you may change polling frequency using XSMT as
described in Changing Polling Frequency on page 638.
Note that polling for IDS Events and Station Assurance Events is disabled by
default, and must be explicitly enabled if you wish to use either of these event
logs.
XMS offers a rich set of statistics in its Dashboard, Reports, and other windows.
These statistics are obtained by polling the managed Arrays using SNMP. The
default polling rate is FAST, providing near real-time data. If you have a large
number of Arrays under management, we recommend that you decrease the
polling speed to enhance XMS performance. Select FAST, MEDIUM, or SLOW
from the drop-down list and click the Save button.
The following table summarizes the polling intervals used for the three polling
rates.
Item
Polling Interval
FAST
Polling Interval
MEDIUM
Polling Interval
SLOW
Array Up/Down
Status
1 minute 5 minutes 5 minutes
Statistics 40 seconds 80 seconds 120 seconds
Management System
602 XMSAdministration
The following table summarizes the recommended polling intervals for various
network sizes.
After you change the polling rate, each Array will be reconfigured for the new
polling interval. Depending on the number of Arrays under management, it
might take some time to process the change on all Arrays (up to 10 seconds per
Array). You may continue to use XMS while this change is proceeding.
Station Counts 40 seconds 80 seconds 120 seconds
Rogues 150 seconds 300 seconds 450 seconds
Polling Rate Number of Arrays
Fast up to 100
Medium up to 250
Slow over 250
Item
Polling Interval
FAST
Polling Interval
MEDIUM
Polling Interval
SLOW
Management System
XMSAdministration 603
Changing the SSH Server Address
Figure 342. Changing the SSH Server
Some actions, such as Perform or Schedule Upgrade require Arrays to download
files. When XMS instructs an Array to fetch a file from the server, the Array opens
an SSH session with the XMS server to perform a secure transfer of the file. By
default, XMS instructs the Array to connect to the XMS servers IP address. In
some situations you may need to specify a different externally accessible IP
address, for example if NAT is in use on the XMS servers network.
To change the IP address that Arrays will be instructed to use for an SSH
connection, use the SSH Server link. Note that the current SSH server address is
displayed. (Figure 342) Click the Use alternate IP address checkbox and enter the
desired IP Address. Click Save when done.
Note that Arrays will use Port 22 for SSH to the XMS server.
Management System
604 XMSAdministration
Web Server
This page allows you to change default settings for HTTP and HTTPS access to
the XMS server, including the ports used. This page is only available on the XM-
3320/3340/3360 models of the Xirrus Management Appliance and on the Virtual
Appliance.
Figure 343. Web Server
By default, only HTTPS access is enabled, and it uses port 9443.
Note that the old URL for accessing XMS at http://<xms-server>:9090 may still be
used. It will automatically redirect you HTTPS at the port configured above.
Management System
XMSAdministration 605
SNMP Trap Receivers
Just as Arrays send SNMP traps to the XMS server, the XMS server can send traps
to top-level supervisory software. Any Array event that gets escalated to an alarm
will be forwarded to the trap receivers that you set up. The receiver for these traps
might be a Manager of Managers (MOM) or an application like HP OpenView
running at the NOC. Use the SNMP Trap Receivers page to set up one or more
destinations for these traps.
Figure 344. SNMP Trap Receivers
To open this page, click the Settings link at the top of the page. Then select SNMP
Trap Receivers from the Application section. (Figure 344) Enter the Host Name
or IP Address of the destination that is to receive traps sent by the XMS server. If
needed, change the Port Number from its default value of 162. Set the
Community Name needed for access to this destination. Add a Description for
this receiver if desired, and set Enabled to make this entry active. Click Add when
done. The new entry will be displayed in the list of trap receivers.
If necessary, you may use the Remove button to the right of an entry to remove
this trap receiver from the list.
Management System
606 XMSAdministration
XMS Setup Wizard
The XMS Setup Wizard takes you through the basic starting steps for provisioning
your server. All of these steps are available in their own web client pages, but the
wizard guides you through the essential initial steps for licensing the server and
then starting discovery of your wireless network.
If there are no Arrays in the XMS database (for example, the first time you start
the web client), you will automatically be taken to the wizard. To open this page
at other times, click the Settings link at the top of the page. Then select XMS
Setup Wizard from the Application section.
Perform the wizards steps as discussed in the following sections.
Management System
XMSAdministration 607
1. XMS License (Figure 345)
Figure 345. XMS Setup WizardXMS License
Xirrus will supply you with a License Key and Serial Number for your
server. Enter both of these fields exactly as they were provided to you
(the fields are not case-sensitive), and click Apply.
After processing the license, the web client displays the following:
Product Name XMS servers product name.
Max Version the highest release number supported by this license.
All incremental upgrades to the release shown are also supported.
For example, if Max Version is 5.0, then this license will run Release
5.0.999, but Release 5.1 will require an updated license.
Max Array Count the server is licensed to manage a specific
maximum number of Arrays. To manage additional Arrays, please
contact Xirrus to upgrade your license.
Expiration Date the date that this license expires.
Click Next > to proceed to the next step. For more information, please see
Managing the XMS Server License on page 620.
Management System
608 XMSAdministration
2. Community Names (Figure 346)
Figure 346. XMS Setup WizardCommunity Names
This page is used to add or delete SNMPv2 community names. The XMS
discovery process searches networks using both SNMPv2 and SNMPv3.
XMS discovery has default SNMPv2 entries which match the factory
default SNMP v2 settings in Arrays and PoGE injectors. However, for
proper security on your Xirrus devices, we recommend that you change
these defaults by setting your own SNMPv2 community strings on Xirrus
Arrays. Thus, you must add those community names or user names/
passwords to XMS so that discovery can find those devices.
Enter the new Community Name and click Add.
Click Next > to proceed to the next step. For more information, please see
SNMPv2 Settings on page 172.
Management System
XMSAdministration 609
3. SSH Users (Figure 347)
Figure 347. XMS Setup WizardSSH Users
Some actions, such as Perform or Schedule Upgrade and Deploy Config
Template, require Arrays to download files. When it instructs an Array to
fetch a file from the server, XMS needs to know a User Name and
Password to gain access to the Array shell. Enter an Arrays User Name
and Password, and click Add. Repeat this for all of the accounts needed
to gain access to all of your Arrays. When XMS needs access to an Array,
it will try username/password pairs until it succeeds. It then records the
values that worked, for the next time it needs to access that Array.
Click Next > to proceed to the next step. For more information, please see
SSH Users on page 176.
Management System
610 XMSAdministration
4. Network (Figure 348)
Figure 348. XMS Setup WizardNetwork
This step manages IP configuration for the server. For recommended IP
addressing, please see Initial Network Settings on page 567.
Hostname defaults to xirrus-xms. Xirrus Arrays send traps to xirrus-xms
to announce their presence and speed discovery. Thus, if you change the
servers Hostname, you should create an alias in your DNS server so that
the server is accessible using both xirrus-xms and the new host name.
Check that Enable Interface is set to Yes for each Ethernet port that you
plan to use. Auto Negotiate should normally be left enabled.
The server uses DHCP by default. To set a static address, click Static. In
this case, you must also enter the XMS servers Default Gateway
Address, and enter the DNS Domain and DNS Servers.
Click Next > to proceed to the next step.
Management System
XMSAdministration 611
5. Time Zone (Figure 349)
Figure 349. XMS Setup WizardTime Zone
Select your local Time Zone from the pull-down list. Enable Auto Adjust
Daylight Savings if you want the system to adjust for daylight savings
automatically, otherwise click No.
Leave Use Network Time Protocol enabled. You may modify the NTP
Servers or leave them at the default values which use NTP Pool time
servers (http://www.pool.ntp.org/). All Arrays must use the same NTP
server to be managed successfully.
Click Next > to proceed to the next step. For more information, please see
Date and Time Settings on page 572.

To use SNMPv3 successfully, system time must be set using the same NTP
server on both the XMS server host machine and all Arrays using SNMPv3.
Management System
612 XMSAdministration
6. Backup (Figure 350)
Figure 350. XMS Setup WizardBackup
This page sets backup locations for the XMS database. For data
protection, define and use at least one location for backups other than on
the XMS server. When you are finished specifying the server type, path
and account to use, XMS will verify that it is able to access the location
and log in. See Manage Locations on page 575 for more information.
Click Add Location. Enter the entrys Name and select a Location Type.
Windows File Share: specify the Path for the folder where files are to be
stored. Use the Windows Uniform Naming Convention (UNC) format
(\\ComputerName\SharedFolder\Resource) or the Server Message Block
(SMB) format (smb://URL).
You may enter a Domain name if necessary. If the location is on a
standalone server, you should normally leave the domain field blank.
Enter a User Name and Password/Confirm Password that will give you
write privileges.
FTP: specify the FTP Server used for backup, for example,
ftp.xyzcorp.com. Specify the FTP Directory for the backup files. If you do
not select Anonymous FTP, enter an FTP Username and FTP Password/
Confirm FTP Password that will give you write privileges.
Management System
XMSAdministration 613
SCP (Secure Copy Protocol): specify the SCP Server used for backup,
entering its hostname, DNS name, or IP address. Specify the SCP
Directory for the backup files. Enter an SCP Username and SCP
Password/Confirm SCP Password that will give you write privileges.
Once you have specified backup locations and you are done with the
wizard, see Manage Schedules or Backup Now on page 579 to
schedule automatic backups.
Click Next > to proceed to the next step.
7. Email (Figure 351)
Figure 351. XMS Setup WizardEmail
Some XMS features, such as reports and alarm notifications, send emails
to specified recipients. XMS uses an SMTP server to send the emails. For
more information, please see Email Settings on page 600.
Enter your SMTP Server Address and Port. Specify the User and
Password for access to the server. Select an Encryption type. Emails will
be identified as being sent from the address that you specify in Sender
Email. Click Test Email to verify that you can successfully send an email.
Click Next > to proceed to the next step.
Management System
614 XMSAdministration
8. SNMP Trap Receivers (Figure 352)
Figure 352. XMS Setup WizardSNMP Trap Receivers
The XMS server can send traps to top-level supervisory software. Array
alarms will be forwarded to these trap receivers. Enter the Host Name or
IP Address of the destination that is to receive traps sent by the XMS
server. Set the Community Name needed for access to this destination.
Add a Description for this receiver if desired, and set Enabled. Click Add
when done with each entry.
Click Next > to proceed to the next step. For more information, please see
SNMP Trap Receivers on page 605.
Management System
XMSAdministration 615
9. Discover Devices (Figure 353)
Figure 353. XMS Setup WizardDiscover Devices
This step is used to add subnetworks or devices to XMS. You may
individually add one or more Arrays and/or Xirrus-supplied switches or
managed power injectors to XMS, or specify a network and have XMS
discover them. You may enter a single device IP address, a range of
addresses, a list of addresses (the Multiple Devices option), or a
subnetwork. The list option is useful if you have an Excel spreadsheet
with a list of Arrays and their addresses.
Select whether to add a Single Device, an IP Range, Multiple Devices,
or Networks by clicking the appropriate tab, then enter the requested IP
information. If you enter a network, be careful to specify the smallest
subnet that includes the Arrays, to avoid creating excess traffic by
discovering a needlessly large network.
For more information, please see Discovery on page 162 and Add
Devices on page 167.
Click the Discover button to start discovery.
Management System
616 XMSAdministration
10. Results (Figure 354)
Figure 354. XMS Setup WizardResults
The Results step will display the discovery results for each requested
address or network, listing whether discovery is In Progress, Completed,
Disabled, or Failed.
You may use the Cancel button if you wish to abort discovery while still
in progress. This will stop XMS from finding any additional devices, but
will not remove any devices that have just been discovered.
Management System
XMSAdministration 617
Audit Log
This page shows an audit trail (record) of all configuration changes that have been
performed on your Arrays. Use the Audit Log link under Settings (in the
Application section) to display the Audit Log page. This page displays the Task
Name of each configuration change, its Start and End Time, the IP and MAC
Address and Host Name of the Array, and the Status of the task. (Figure 355)
Figure 355. Audit Log
Management System
618 XMSAdministration
Viewing Server Log Files
Figure 356. Viewing Log Files
Use the Server Logs link under Settings (in the General section) to display the
Logs page. This page displays a link for each of the working log (message) files
generated by the XMS server while it is running. Click a link to view the contents
of that file. (Figure 357) These files journal the operation of the XMS server
software, rather than reporting on the operation of the wireless network.
Log files are intended for use by Xirrus Customer Support personnel. In certain
situations, Support personnel may ask you to send them some of these files. Use
the Export button to save log files to your file system. If you click this button on
the Logs page (the page showing the list of log files), then XMS creates a zip file
containing all of the logs. If you click Export on a page for a particular log file,
then XMS creates a .csv file for that log. In either case, a dialog allows you to open
or save the file and browse to the desired location for saving the export file. If you
choose to open a .csv file rather than saving it and you have Excel installed on
your workstation, an Excel window opens and displays the log file contents.
Management System
XMSAdministration 619
Figure 357. Viewing a Selected Log File
If a listed log files grows too large, it is closed and renamed and a new file is
started. The following example illustrates this. As shown in Figure 358, there are
four xirrusout.txt files.
xirrusout.txt contains the most recent entries.
xirrusout.txt.1 the first time that xirrusout.txt grows too large, it is
closed and renamed to xirrusout.txt.1. A new xirrusout.txt is created to
capture ongoing new entries.
xirrusout.txt.2 the second time that xirrusout.txt grows too large, it is
closed and renamed to xirrusout.txt.2. Thus xirrusout.txt.1 contains the
oldest entries, and xirrusout.txt.2 has the next oldest entries, etc. The
number of log files is limited to 10 or 20 instances, depending on the log
file type.
Figure 358. Multiple Log Files
Management System
620 XMSAdministration
Managing the XMS Server License
For full operation, the XMS server must have a license installed. Until the license
is installed, the server will operate in a default mode that allows it to manage only
one Array. Thus, without an appropriate license, Discovery will stop at one Array
and will not allow more Arrays to be added. If you do not have a valid license,
you will be notified each time you start an XMS client.
Use the following steps to enter your license.
1. Click the Settings button, then click XMS License. The XMS License Info
page appears.
Figure 359. XMS Server License
2. Xirrus will supply you with a License Key and Serial Number for your
server. Enter both of these fields exactly as they were provided to you
(the fields are not case-sensitive), and click Apply.

This section describes the license to use the XMS server. If you are looking for
information regarding using XMS to manage Array licenses, please see
Array Licenses on page 194.

Valid XMS licenses are typically for a particular number of IAPs. When XMS
has discovered the maximum permitted number of IAPs, no additional Arrays
will be discovered.
Management System
XMSAdministration 621
3. After processing the license information, the following additional fields
will be shown:
Product Name XMS servers product name.
Max Version the highest release number supported by this license.
All incremental upgrades to the release shown are also supported.
For example, if Max Version is 5.0, then this license will run Release
5.0.999, but Release 5.1 will require an updated license.
Max Array Count the server is licensed to manage a specific
maximum number of Arrays. To manage additional Arrays, please
contact Xirrus to upgrade your license.
Expiration Date the date that this license expires.
Performing Server Upgrades
Figure 360. Upgrading XMS Software
This page is used to update the XMS server on the Xirrus Management Appliance
(XM-3320/3340/3360 only) and on the Virtual Appliance. Select the Upgrade link
to display the Upgrade page.
When you receive updated software from Xirrus, it comes in one of two forms:
For the Management Appliance (XM-3320/3340/3360)a .tar file. For
example:
xms-6.1.0-2695.tar
Management System
622 XMSAdministration
For the Virtual Appliance an .xau file. For example:
xms-6.1.0-2695.xau
The upgrade file contains an entire software upgrade, rather than having an
incremental patch that depends on previous patches being installed. Please follow
the instructions furnished with the release carefully.
1. When you receive a new release file from Xirrus, place it where you will
be able to browse to it from the web browser where you are running the
web client.
2. Click Settings at the top of the page, then select the Upgrade link from
the Maintenance section.
3. Next, click the Choose File button to browse to the .tar or .xau file. Click
Upload to move the file to the server.
4. Click Upgrade to install the new software.
When the process is complete, a pop-up message will be displayed. It will inform
you that you must reboot the Appliance. Click the OK button to close it. The new
release becomes the current version of the XMS server.
NOTE: In Release 6.2 and later releases, Heat Maps are part of the web client. If you have
maps from pre 6.2 versions of XMS, they will automatically be migrated to the current
XMS version. See Migrating Maps from Earlier Releases on page 254.
Resetting the XMS Server
Figure 361. Resetting XMS
Use the Factory Reset link to display the Reset page. This page allows you to
perform a reset on the server. This deletes all data in the XMS database (but it
does not delete backup files). It also returns the XMS server back to all of its
Management System
XMSAdministration 623
factory default settings, except that Network Settings and Date and Time
Settings are retained.
Click the Perform XMS Reset button to perform the reset. You will be asked to
verify that you wish to proceed.
When the reset is complete, your first action should be to specify Database
Backup Settings.
Management System
624 XMSAdministration
Managing XMS on XM-3300 and XMS-9000-WIN Systems
On the XM-3300 and XA-3300-CC, the Xirrus Server Management Tool (XSMT) is
used to start, stop, or view the status of the server, install patches, and for
advanced settings and database management. The web client may also be used
for managing some settings. XMS server management is discussed in the
following sections.
Starting the XMS Server on XM-3300 and XMS-9000-WIN on
page 625
Xirrus Server Management Tool (for XM-3300 and XMS-9000-WIN)
on page 627
Managing XMS Server Settings via the Web Client on page 641
Figure 362 shows XSMTs XMS Server Manager window when the server is up.
Figure 362. Xirrus Server Management Tool - XMS Server Manager
The XMS server typically runs as a Windows service, and is listed along with
other Windows services accessible from Windows Administrative Tools. You may
Management System
XMSAdministration 625
view the status of the XMS server in this way, but we recommend that you start or
stop the server using XSMT rather than as a Windows Service, so that you can
monitor status.
Starting the XMS Server on XM-3300 and XMS-9000-WIN
In the installation process, there are options to have the XMS server start
automatically, or to wait for the administrator to explicitly start it. To see whether
the XMS server is running correctly, use XSMT.
If XSMT is not running, start it using the Windows Start button > All Programs >
Xirrus > Xirrus Management System > XA-3300-CC. The XSMT window is
displayed. (Figure 362)
Starting XSMT on the XM-3300
When you log in to the XM-3300 (the default login is Administrator/
Xirrus!23), the Xirrus Server Management Tool is automatically started
and the XSMT window is displayed.
Starting XSMT on your server with XMS-9000-WIN installed
From the Windows Start menu, select All Programs > Xirrus > Xirrus
Management System > XA-3300-CC.
The first time that you start XSMT, a message will appear asking whether
you wish to configure XMS to run as a Windows Service. Click Yes.
Figure 363. Start XMS as a Windows Service
Wait for the Start button on the lower left to be enabled, then click it to
start the XMS server.
At other times, if XSMT is not running, you may start it by clicking
the XSMT shortcut icon on the Windows desktop.
Management System
626 XMSAdministration
During server initialization, the XSMT Logs panel displays high-level progress
messages.
When XMS server startup is finished, the XMS Server Manager tab of XSMT will
indicate that the server is up and running. Figure 362 on page 624 shows an
example of a successful server initialization process. The state of all servers is
Running and they are shown in green.
When the XMS server is ready for clients to be started, the Logs section on the
right of the window will display:
*** The XMS Server is now running
Point your browser to http://<XMS Server IP>:9090/
or locally from this computer, use http://localhost:9090/
When the server starts for the first time, it will initialize the database. Discovery is
not started automatically you should start the discovery process to add Xirrus
Arrays and PoGE injectors to the XMS database (see Discovery on page 162).
The first time that XMS starts, you should use the Backup Manager to establish a
backup schedule for the database. See About Managing the XMS Server on
page 562. For more information on using XSMT, see Xirrus Server Management
Tool (for XM-3300 and XMS-9000-WIN) on page 627.
Management System
XMSAdministration 627
Xirrus Server Management Tool (for XM-3300 and XMS-9000-
WIN)
Start&Stop
buttons
Status
messages
Managertabs:
XMSServer Software
This tool is provided to manage the XMS server and to perform certain advanced
operations.
Figure 364. Xirrus Server Management Tool - XMS Server Manager
XSMT has two major functions, each one with its own tab, plus advanced menu
options:
XSMT - XMS Server Manager Tool displays server status and starts
and stops the server.
XSMT - Software Manager updates XMS server software with new
releases.
XSMT - Database Tools these menu options initialize or repair the
database.
Management System
628 XMSAdministration
XSMT - Advanced Settings these menu options change polling
intervals and the SSH server address.
Note: XMS has a browser-based interface which may be used to manage some server
settings. See Managing XMS Server Settings via the Web Client on page 641.
XSMT - XMS Server Manager Tool
The XMS Server Manager window is divided into two distinct areas:
Status The Required Services and Offline Activities sections show the
status of the various services that are part of or associated with the XMS
server. The Start / Stop XMS Server section at the bottom starts or stops
the server.
Logs shows the actions taken such as starting and stopping services,
and when the action is complete.
Required Services
This section shows the running status of the major XMS services.
Figure 365. Status of Services, Showing Normal Status
Required services include:
Web Server the main server used by XMS clients.
Client Login Page authenticates XMS client login requests. If this
service is down, clients will be unable to log in even if the rest of the XMS
server is running.
Management System
XMSAdministration 629
Database Server all XMS data is handled by this server. You may
manage it from the client or the server. See About Managing the XMS
Server on page 562 and XSMT - Database Tools on page 633.
RMI Registry used internally for communication between XMS
subsystems.
The possible status values for these services may be:
Running (Green) the service is running properly.
Not Running (Yellow) the service has been stopped, either by
administrator request or by error. Yellow is also used during the start-up
and shut-down transition states. Check the Logs portion of the window
for more information.
Checking(Gray) shown during startup as XSMT is checking the state
of the service and starting it if necessary.
Offline Activities
This section shows the running status of XMS managers. Activity on a manager
may be started by an XMS administrator.
Figure 366. Status of Offline Activities
Offline activities include:
Software Manager used to install XMS software updates. See XSMT -
Software Manager on page 635.
Database Manager this is used to manage backups. See About
Managing the XMS Server on page 562.
The possible status values for these services may be:
Checking(Gray) shown during startup as XSMT is checking the state
of the manager and starting it if necessary.
Management System
630 XMSAdministration
OK (Green) there is currently no action in progress (idle but ready).
Not Running (Yellow) the service has been stopped, either by
administrator request or by error. Yellow is also used during the start-up
and shut-down transition states. Check the Logs portion of the window
for more information.
Restore In Progress (Database Manager, Yellow) a database restore is
running. It must complete before the XMS server can be started.
Patch In Progress (Software Manager, Yellow) a software update is in
progress. It must complete before the XMS server can be started.
XSMT - Starting the XMS Server
The XMS server must be running if you want to serve XMS clients, but remember
that the server must be stopped if you want to perform advanced database
operations (Re-initialize and Repair).
To start the server from the Xirrus Server Management Tool any time the server is
down, select the XMS Server Manager tab and click the Start button on the lower
left. When the server begins its startup process, the Logs section on the right of the
window displays the progress of the system operations that are completed. XSMT
also opens a system console window in which you can watch progress in more
detail (Figure 367). To review the full content of the console window, use the scroll
bar.
Note that the Start button will be disabled if the server is running or if the current
status of the server is not properly shut down. To stop the server, see XSMT -
Shutting Down the XMS Server on page 632.
Scroll Bar
Management System
XMSAdministration 631
Figure 367. Server Startup Progress
Server is Up
When the server has been started successfully, the status of all the Required
Services will be Running (green) as shown in Figure 368.
When the XMS server is up, the Logs portion of the window will show the
following messages:
*** The XMS Server is now running
Point your browser to http://<XMS Server IP>:9090/
or locally from this computer, use http://localhost:9090/
Figure 368. Server is Up (XSMT)
Management System
632 XMSAdministration
XSMT - Shutting Down the XMS Server
Scroll Bar
You can shut down the server at any time using the Xirrus Server Management
Tool, or the server can shut down automatically if it detects a problem. The server
must be shut down before you can initiate the following advanced database
operations: Re-initialize and Repair.
To shut down the server, select the XMS Server Manager tab in the XSMT window
and click the Stop button on the lower left. The Shutdown Server window is
displayed, which requires you to enter a user name and password the default
for both is admin. Click on the Submit button to initiate the server shutdown
process. Note that the Stop button will be disabled if the server is not running or
if the current status of the server will not permit shut down.
Note: In rare instances, the XMS server may be unable to start, and the Stop button will
be disabled. In this case, you may use the File > Kill server menu option to kill all server
processes. This should be used only as a last resort! The Stop button does an orderly
shutdown if it is enabled, it should always be used instead of the Kill option.
When the server begins its shutdown process, the Logs section on the right of the
XSMT window displays the progress of the system operations that are completed.
(Figure 369) XSMT displays the system console window, in which you can watch
progress in more detail. To review the full content of the console window, use the
scroll bar.

Figure 369. Server Shutdown Progress
Management System
XMSAdministration 633
When the server has shut down successfully, the Start button in XSMT will be
enabled, and the system console window will say:
WebNMS Ser ver Successf ul l y Shut Down
The database server will still be running after the XMS server is shutdown.
Figure 370. Status for Stopped XMS Server
XSMT - Database Tools
Although you can view, schedule, or restore database backups from any client
using the Database Backup Settings, you can only Re-initialize or Repair the
XMS database using XSMT. These management tasks are available on the
Database menu in XSMT. For an overview of other database features, please see
About the XMS Database on page 563.
When the XMS server is up and running (i.e., the Web Server, Client Login Page,
and RMI Registry are running), the initialize and repair options are disabled. You
will receive an informational message if you try to use them, notifying you that
you must stop the server first.
Re-initialize Database
Choose this option if you want to re-initialize the current database, which
means clearing the database. See Re-initialize Database on page 633.
Repair Database
Choose this option to attempt to repair the current database. See Repair
Database on page 634.
Re-initialize Database
This operation clears the database. All of your configuration, discovery, statistics,
and other data will be lost. When you select this operation, XMS starts the
Management System
634 XMSAdministration
database server if its not already running, and deletes all XMS tables. When the
XMS server restarts, it finds that the database is empty and initializes the database
for its use.
Although this tool is available in XSMT, re-initializing a database should only be
performed in these situations:
When the Release Notes for a new version of XMS explicitly instruct you
to re-initialize the database when upgrading from your currently running
release.
As a last resort, it can be used to recover from catastrophic database
corruption. Please call Xirrus Customer Support before re-initializing.
To re-initialize the database, first shut down the XMS server and then select
Re-initialize from the XSMT Database menu. You are presented with a message
warning you that all data and configuration information stored in the database
will be deleted before it can be re-initialized. Click on the Yes button to proceed
with the re-initialization process, or click on the No button to abort the process.
If you clicked on the Yes button and started the re-initialization process, the server
console window displays the progress of the system operations that are
completed. You can review the full content of the console window by using the
scroll bar. When the database initialization process is completed, a confirmation
window is displayed. Click on the OK button to close the window.
Repair Database
This operation checks the internal indexing in the database and attempts to repair
any problems.
Although this tool is available in XSMT, you should only repair the database if it
has been corrupted. If the database is damaged, it may not allow you to restore
from a backup. So if there is actual table corruption, it needs to be repaired prior
to restoring any backup. Please contact Xirrus Customer Support before repairing
the database.
To repair the database, first shut down the server and then select Repair database
from the Database menu. You are presented with a message verifying that you
wish to proceed. Click Yes to proceed, or click No to abort the process.
Management System
XMSAdministration 635
When the database repair process is completed, a confirmation window is
displayed. Click on the OK button to close the window. You may then restart XMS
(see XSMT - Starting the XMS Server on page 630).
Note: There is an optional external script available for performing repair operations. The
advantage of using the script is that it creates a log file that can be reviewed to determine if
any problems remain, and which problems were actually repaired. Contact Xirrus
customer support for more information. See Contact Information on page 648.
XSMT - Software Manager
The Software Manager tab of XSMT allows you to install new release versions
(called patches) of the XMS server, or revert to a previously installed release.
Figure 371. XSMT Software Manager
When you receive updated software from Xirrus, it comes in the form of a patch
file with a .ppm file extension. For example:
xms-XA-patch-5.0.0-1953.ppm
Management System
636 XMSAdministration
Patches may be dependent on each other - i.e., one release may depend on other
files being installed first, and the order in which they are installed may be
important. Please follow the instructions furnished with the release carefully.
The XMS server must be stopped before you can perform any Software Manager
operations.
About the Installed Patch List
When a new release is installed, it is added to the bottom of the Installed Patch
List and becomes the running version of the XMS server. The last (bottom) release
in this list is always the running version.
If you select a release in the list and click the Remove Patch button, that release
and all later releases (all the entries below it) are removed. When you start the
XMS server again, it will run the release version that is currently at the bottom of
the Installed Patch List.
To Install a New Version of the XMS Server
When you receive a new release file from Xirrus, place it where you will be able to
browse to it from the XMS server computer. Then shut down the XMS server and
go to the Software Manager tab in XSMT. Then click the Install Patch button. The
Select Patch File dialog box appears.
Figure 372. Select a Patch File
Management System
XMSAdministration 637
Browse to the new .ppm file and click Open. The new release will be installed.
The Logs section of the Software Manager window shows output from the
installation process. When the process is complete, a pop-up message will be
displayed. Click the OK button to close it. The new release becomes the current
version of the XMS server. The file appears at the bottom of the Installed Patch
List.
Close XSMT if it doesnt close automatically after installing a patch, and relaunch
it (since the patch may have affected XSMT). You may then start the XMS server
(see XSMT - Starting the XMS Server on page 630).
To Remove a Patch
The Remove Patch button may be used to remove the most recently installed
release, or the last few releases installed. The release remaining at the bottom of
the Installed Patch List will be used as the running version when the XMS server
is restarted. See About the Installed Patch List on page 636. You cannot
remove the first (top) entry in the list.
To remove one or more releases, shut down the XMS server and go to the
Software Manager tab in XSMT. Decide which of the installed releases you would
like to have as the running version, and click the entry beneath that in the
Installed Patch List. Then click the Remove Patch button. You will be asked to
verify the removal. The selected file and all of the files underneath it will be
removed from the Installed Patch List. A pop-up message will inform you when
the removal is complete. Click OK to close it.
When the removal is complete, XSMT shuts down. (If it does not close
automatically, you should shut it down it manually.) Relaunch XSMT before
proceeding to do anything else with XMS. You may then start the XMS server (see
XSMT - Starting the XMS Server on page 630). The version at the bottom of
the Installed Patch list will be used.
Management System
638 XMSAdministration
XSMT - Advanced Settings
The Advanced menu in XSMT allows you to change settings in the XMS server, in
order to modify the polling interval for Arrays and to change how the server
communicates with Arrays via SSH.

Figure 373. XSMT Advanced Menu Options
The Advanced menu provides two functions:
Changing Polling Frequency
Changing the SSH Server Address
There is also a browser-based interface that allows you to change XMS server
settings:
Managing XMS Server Settings via the Web Client
Changing Polling Frequency
XMS offers a rich set of statistics in its Dashboard, Reports, and other windows.
These statistics are obtained by polling the managed Arrays using SNMP. The
default polling rate is Fast, providing near real-time data. The Advanced >
Polling menu option allows you to change the polling interval that the XMS
server uses. Note that you may also change polling frequency using the web
client, as described in Polling Settings on page 601.
If you have a large number of Arrays under management, we recommend that
you increase the polling interval to enhance XMS performance. The following
table summarizes the recommended polling intervals for various network sizes.
Management System
XMSAdministration 639
To change the polling interval at any time when the XMS Server is running, select
Polling from the Advanced menu. Drag the slider (Figure 374) to the preferred
polling speed, as suggested in the table above. Click Save when done. The polling
rate may only be changed when the XMS server is running.
Figure 374. Changing Polling Frequency
After you change the polling rate, each Array will be reconfigured for the new
polling interval. The Polling Rate window will display the progress of this
process. Depending on the number of Arrays under management, it might take
some time to process the change on all Arrays (up to 10 seconds per Array). You
may continue to use XMS while this change is proceeding.
If you are using the browser interface to manage polling speed, proceed as
described in Polling Settings on page 601.
Polling Rate Number of Arrays Base interval multiplied by
Fast 0 to 100 1
Medium 100 to 250 2
Slow Over 250 3
Management System
640 XMSAdministration
Changing the SSH Server Address
Some actions such as Perform or Schedule Upgrade require Arrays to download
files. When XMS instructs an Array to download a file from the server, the Array
opens an SSH session with the XMS server to perform a secure transfer of the file.
By default, XMS instructs the Array to connect to the XMS servers IP address. In
some situations you may need to specify a different externally accessible IP
address, for example if NAT is in use on the XMS servers network.
Figure 375. Changing the SSH Server
To change the IP address that Arrays will be instructed to use for an SSH
connection, select SSH Server from the Advanced menu. Note that the dialog box
displays the current SSH server address. (Figure 375) Click the Use alternate IP
address checkbox and enter the desired Alternate IP Address.
If you need to reset the SSH servers login because you think the name and
password may have been compromised, click the Reset Login button. Click Save
when done.
Note that the Arrays always use Port 22 for SSH.
If you are using the browser interface to change the SSH server settings, proceed
as described in Changing the SSH Server Address on page 603.
Management System
XMSAdministration 641
Managing XMS Server Settings via the Web Client
The XMS web client allows you to change many XMS server settings on all
platforms, including the XM-3300 and XMS-9000-WIN. Access it in the same way
as described in Accessing the Web Client on page 565.
This interface is the same as the one used for Managing XMS on XM-3320/3340/
3360 and Virtual Appliances, except that it omits a few pages that are not used
for the XM-3300 and XMS-9000-WIN, such as setting system network address and
time and date. It has the following links:
XMS Users see XMS Users on page 584.
Email see Email Settings on page 600.
Polling see Polling Settings on page 601.
SSH Server see Changing the SSH Server Address on page 603.
SNMP Trap Receivers see SNMP Trap Receivers on page 605.
Backup see Database Backup Settings on page 575.
Server Logs see Viewing Server Log Files on page 618.
XMS License see Managing the XMS Server License on page 620.
Management System
642 XMSAdministration
Management System
TechnicalSupport 643
Technical Support
This chapter provides valuable support information that can help you resolve
technical difficulties. Before contacting Xirrus, review all sections in this chapter
and try to determine if your problem resides with XMS, the server platform, or
your network infrastructure. Section headings for this chapter include:
General Hints and Tips for Xirrus Management Appliances on
page 643
Frequently Asked Questions on page 644
Contact Information on page 648
General Hints and Tips for Xirrus Management Appliances
This section provides some useful tips that will optimize the reliability and
performance of XMS.
You must terminate all applications before shutting down the server
Appliance. This includes closing down the client interface and the server.
For more information, go to Shutting Down the XMS Server on
page 29.
For best performance, the Management Appliance should be mounted in
a dust-free and temperature-controlled environment.
Ensure that the Management Appliance receives adequate ventilation at
all times. The units cooling fans are mounted on the rear panel. Do not
obstruct the fans.
Never use the Management Appliance chassis as a base for heavy
monitors or other equipment.
Some Appliance management operations may take a few minutes to
complete. Always be patient and wait for these operations to finish before
attempting another task.
Management System
644 TechnicalSupport
Frequently Asked Questions
This section answers some of the most frequently asked questions regarding the
functions and operation of XMS.
Q. Why wont my browser connect to the XMS server to start the XMS
client? I can ping the server.
A. Remember to point the browser to Port 9090 on the server by appending
:9090 to the server address. For example:
http://192.168.10.40:9090
You will automatically be redirected to an HTTPS connection at port 9443,
for example, https://192.168.10.40:9443.
Also note that if you selected a different port for accessing the XMS server
during installation of the XMS server software, then you must append
that port number to the URL instead of 9090. You may also use the web
client to change the ports used for connections to XMS. See Web Server
on page 604.
Q. Why will XMS not discover an Array, even though the Array is
connected to the network and functioning correctly?
A. SNMPv2 or v3 (Simple Network Management Protocol) must be enabled
on the Array. Log in to the Array and check the SNMP settings. If the
problem persists, check that the Array is on the same subnet as the XMS
server.
For discovery of a device (Array or PoGE injector), the device must have
SNMP enabled and its community string must match one of the strings
listed in the Discovery window. See SNMPv2 Settings on page 172.
The default SNMPv2 community string in XMS matches the Array
default value.
When an Array boots up, it sends an SNMP trap to the XMS servers
default hostname, xirrus-xms. XMS can then add it to its discovered
devices list. This Phone Home feature requires DNS to resolve the
hostname xirrus-xms correctly. Thus, if you change the host name of the
Management System
TechnicalSupport 645
XMS server, you must configure DNS to resolve xirrus-xms to the actual
name of the XMS server host.
Q. XMS discovered my Array using SNMPv3, and the Array has
connectivity and is running OK, but XMS reports that the Array is
down.
A. To use SNMPv3 successfully, system time must be set using an NTP
server on both the XMS server host machine and on all Arrays using
SNMPv3. This is because SNMPv3 requires synchronization between the
XMS server and the Arrays so that the system time difference between
them never exceeds more than 150 seconds. If the time difference exceeds
150 seconds, SNMPv3 suspects a security breach and removes the
SNMPv3 credentials for affected Arrays from the database. This means
that the Array will appear to be down and statistics will not be polled
until the Array is re-discovered. A manual refresh of the Array will
remedy the situation. See Add Devices on page 167.
Q. When managing large Array deployments, will the performance of the
network be compromised?
A. No. XMS resides outside the data path, so performance bottlenecks and
points of failure are eliminated.
Q. Why didnt the maps I created appear the next time I logged in?
A. You must always save your maps. Also, if you make changes and you
want your changes to appear on all clients (not just your local machine)
you must save the changes to the server.
Q. Why cant I access the BIOS screen when the system boots up? (XM-
3300 only)
A. You must have a PS/2 keyboard attached to the XM-3300 to access the
BIOS screen. A USB keyboard is dependent on Windows and only
becomes effective after the Windows environment has loaded.
Management System
646 TechnicalSupport
Location Service Data Formats
Xirrus Arrays are able to capture and upload visitor analytics data, acting as a
sensor network in addition to providing wireless connectivity. This data is sent to
the location server in different formats, based on the type of server. The Location
Server URL, Location Customer Key, and Location Period for reporting data are
configured under Location settings. See Location on page 429 for details. If a
Location Customer Key has been entered, data is sent encrypted using AES with
that key.
Euclid Location Server
If the Location Server URL contains the string euclid, then it specifies a Euclid
server. Data is sent at the specified intervals, in the proprietary format expected
by the Euclid location server.
Non-Euclid Location Server
If the Location Server URL doesnt contain the string euclid, then data is sent as
a JSON object at the specified intervals, with the following fields.
Field Name Description
ln Location Name Array location string
ld Location Data Defined below
vn Version Number Set to 1
ma MAC Address Base IAP MAC Address
mc Message Count Running message count (resets to 0 when array
is rebooted)
lt Location Table Table of Stations and APs heard during this
window
si Station ID Station MAC address (AES encrypted if cust-
key is not blank)
bi BSSID BSSID station is on (AES encrypted if cust-key
is not blank)
Management System
TechnicalSupport 647
ap AP Flag 1=AP, 0=Station
cn Count Count of frames heard from device during this
window
ot Origin Time Timestamp of first frame in this window (Unix
time in seconds)
ct Current Time Timestamp of last frame in this window (Unix
time in seconds)
cf Current
Frequency
Frequency (MHz) last frame was heard on
il Interval Low Minimum interval between frames (within 24
hr period)
ih Interval High Maximum interval between frames (within 24
hr period)
sl Signal Low Minimum signal strength (within 24 hr period)
sh Signal High Maximum signal strength (within 24 hr period)
so Signal Origin Signal strength of first frame heard
sc Signal Current Signal strength of last frame heard
Field Name Description
Management System
648 TechnicalSupport
Contact Information
Xirrus, Inc. is located in Thousand Oaks, California, just 55 minutes northwest of
downtown Los Angeles and 40 minutes southeast of Santa Barbara.
Xirrus, Inc.
2101 Corporate Center Drive
Thousand Oaks, CA 91320
USA
Tel: 1.805.262.1600
1.800.947.7871 Toll Free in the US
Fax: 1.866.462.3980
www.xirrus.com
support.xirrus.com
Management System
GlossaryofTerms 649
Glossary of Terms
802.11a
A supplement to the IEEE 802.11 WLAN specification that describes radio
transmissions at a frequency of 5 GHz and data rates of up to 54 Mbps.
802.11b
A supplement to the IEEE 802.11 WLAN specification that describes radio
transmissions at a frequency of 2.4 GHz and data rates of up to 11 Mbps.
802.11g
A supplement to the IEEE 802.11 WLAN specification that describes radio
transmissions at a frequency of 2.4 GHz and data rates of up to 54 Mbps.
802.11n
A supplement to the IEEE 802.11 WLAN specification that describes
enhancements to 802.11a/b/g to greatly enhance reach, speed, and capacity.
AES
(Advanced Encryption Standard) A data encryption scheme that uses three
different key sizes (128-bit, 192-bit, and 256-bit). AES was adopted by the U.S.
government in 2002 as the encryption standard for protecting sensitive but
unclassified electronic data.
alarm
An alarm results from the correlation of events and represents a failure or fault in
the network that may need immediate attention.
application client
An applet that resides on the local machine where the XMS server resides that
provides access to the client interface.
Array
A Xirrus proprietary high capacity wireless access point utilizing Gigabit LAN
speeds and multiple wireless channels, specifically designed for the Enterprise
market.
Management System
650 GlossaryofTerms
authentication
The process that a station, device, or user employs to announce its identify to the
network which validates it. IEEE 802.11 specifies two forms of authentication,
open system and shared key.
bandwidth
Specifies the amount of the frequency spectrum that is usable for data transfer. In
other words, it identifies the maximum data rate a signal can attain on the
medium without encountering significant attenuation (loss of power).
browser client
A web-based application that provides remote access to the XMS client interface
from a Web browser.
BSS
(Basic Service Set) When a WLAN is operating in infrastructure mode, each access
point and its connected devices are called the Basic Service Set.
BSSID
The unique identifier for an access point in a BSS network. See also, SSID.
CDP
(Cisco Discovery Protocol) CDP is a layer 2 network protocol which runs on most
Cisco equipment and some other network equipment. It is used to share
information with other directly connected network devices. Information such as
the model, network capabilities, and IP address is shared. Wireless Arrays can
both advertise their presence by sending CDP announcements, and gather and
display information sent by neighbors.
cell
The basic geographical unit of a cellular communications system. Service
coverage of a given area is based on an interlocking network of cells, each with a
radio base station (transmitter/receiver) at its center. The size of each cell is
determined by the terrain and forecasted number of users.
channel
A specific portion of the radio spectrum the channels allotted to one of the
wireless networking protocols. For example, 802.11b and 802.11g use 14 channels
in the 2.4 GHz band, only 3 of which don't overlap (1, 6, and 11). In the 5 GHz
Management System
GlossaryofTerms 651
band, 802.11a uses 8 channels for indoor use and 4 for outdoor use, none of which
overlap.
CoS
(Class of Service) A category based on the type of user, type of application, or
some other criteria that QoS systems can use to provide differentiated classes of
service.
default gateway
The gateway in a network that a computer will use to access another network if
a gateway is not specified for use. In a network using subnets, a default gateway
is the router that forwards traffic to a destination outside of the subnet of
the transmitting device.
DHCP
(Dynamic Host Configuration Protocol) A method for dynamically assigning IP
addresses to devices on a network. DHCP issues IP addresses automatically
within a specified range to client devices when they are first powered up.
DHCP lease
The DHCP lease is the amount of time that the DHCP server grants to the DHCP
client for permission to use a particular IP address. A typical DHCP server allows
its administrator to set the lease time.
DNS
(Domain Name System) A system that maps meaningful domain names with
complex numeric IP addresses. DNS is actually a separate network if one DNS
server cannot translate a domain name, it will ask a second or third until a server
is found with the correct IP address.
domain
The main name/Internet address of a user's Internet site as registered with
the InterNIC organization, which handles domain registration on the Internet. For
example, the domain address for Xirrus is: http://www.xirrus.com, broken
down as follows:
http:// represents the Hyper Text Teleprocessing Protocol used by all Web
pages.
www is a reference to the World Wide Web.
Management System
652 GlossaryofTerms
xirrus refers to the company.
com specifies that the domain belongs to a commercial enterprise.
encryption
Any procedure used in cryptography to translate data into a form that can be
decrypted and read only by its intended receiver.
frame
A packet encapsulated to travel on a physical medium, like Ethernet or Wi-Fi. If a
packet is like a shipping container, a frame is the boat on which the shipping
container is loaded.
gateway
The gateway in a network that a computer will use to access another network if a
gateway is not specified for use. In a network using subnets, a default gateway is
the router that forwards traffic to a destination outside of the subnet of the
transmitting device.
Gigabit Ethernet
The newest version of Ethernet, with data transfer rates of 1 Gigabit (1,000 Mbps).
host name
Each computer running TCP/IP (regardless of the operating system) has a host
name also known as a machine name. Host names are used by networking
applications, such as Telnet, FTP, Web browsers, etc. In order to connect to a
computer running the TCP/IP protocol using its host name, the host name must
be resolved to an IP address. Host name resolution is typically done by the
Domain Name System (DNS). Changing a computer's host name does not change
its NetBIOS name. See also, DHCP lease and NetBIOS.
IAP
(Integrated Access Point) A configurable wireless module (radio) dedicated to the
Xirrus Wireless Array family of products.
icon
A graphical symbol used in the XMS client interface to represent objects, such as
Arrays within a map, alarms and events. See also, map symbol.
Management System
GlossaryofTerms 653
Intrusion Detection System
A Xirrus proprietary application that scans and monitors the XMS database for
intruders.
MAC Address
(Media Access Control Address) A 6-byte hexadecimal address assigned by a
manufacturer to a device.
managed network
The network under management by XMS. This includes all the Arrays discovered
by XMS, and all of their IAPs and the devices that are associated to them.
map
A pictorial representation of your network or subnet. The background image for
the default main map supplied with XMS is a global map of the world, but you
can change the background image of any map at any time. For example, you may
want to organize your maps to reflect a corporate organization based on
functional areas, physical site layouts, or geographic areas.
map symbol
Also known simply as symbols, these are graphical representations of Arrays in
the XMS client interface maps. The symbol for an Array is a pictorial image of the
Xirrus Wireless Array. See also, icon.
Mbps
(Megabits per second) A standard measure for data transmission speeds (for
example, the rate at which information travels over the Internet). 1 Mbps denotes
one million bits per second.
MTBF
(Mean Time Between Failures) Used in reports, this shows the average time (in
hours and minutes) between failures of an Array.
MTTR
(Mean Time To Repair) Used in reports, this shows the average time (in minutes)
to restore functionality to the Array following a failure.
Management System
654 GlossaryofTerms
NetBIOS
(Network Basic Input Output System) All computers running the Windows
operating system have a NetBIOS name. The NetBIOS name is specified by the
user when Windows networking is installed and configured. In order to connect
to a computer running TCP/IP via its NetBIOS name, the name must be resolved
to an IP address. A computer's NetBIOS name is often the same as the computer's
host name, because most users accept the default settings when installing their
Windows operating system.
NTP
(Network Time Protocol) An Internet standard protocol (built on top of TCP/IP)
that ensures the accurate synchronization (to the millisecond) of computer clock
times in a network of computers. Running as a continuous background client
program on a computer, NTP sends periodic time requests to servers, obtaining
server time stamps and using them to adjust the client's clock.
packet
Data sent over a network is broken down into many small pieces packets by
the Transmission Control Protocol layer of TCP/IP. Each packet contains the
address of its destination as well the data. Packets may be sent on any number of
routes to their destination, where they are reassembled into the original data. This
system is optimal for connectionless networks, such as the Internet, where there
are no fixed connections between two locations.
PoGE
This refers to the optional Xirrus-supplied Power over Gigabit Ethernet modules
that provide DC power to Arrays. Power is supplied over the same Cat 5e or Cat 6
cable that supplies the data connection to your gigabit Ethernet switch, thus
eliminating the need to run a power cable.
polling
The process of contacting a network, Array or group of Arrays and collecting
statistical data about the device(s).
Management System
GlossaryofTerms 655
preamble
Preamble (sometimes called a header) is a section of data at the head of a packet
that contains information that the access point and client devices need when
sending and receiving packets. PLCP Has two structures, a long and a short
preamble. All compliant 802.11b systems have to support the long preamble.
The short preamble option is provided in the standard to improve the efficiency
of a network's throughput when transmitting special data, such as voice, VoIP
(Voice-over IP) and streaming video.
private key
In cryptography, one of a pair of keys (one public and one private) that are created
with the same algorithm for encrypting and decrypting messages and digital
signatures. The private key is provided only to the requestor and never shared.
The requestor uses the private key to decrypt text that has been encrypted with
the public key by someone else.
PSK
(Pre-Shared Key) A TKIP passphrase used to protect your network traffic in WPA.
public key
In cryptography, one of a pair of keys (one public and one private) that are created
with the same algorithm for encrypting and decrypting messages and digital
signatures. The public key is made publicly available for encryption and
decryption.
QoS
(Quality of Service) QoS can be used to describe any number of ways in which a
network provider guarantees a service's performance, such as an average or
minimum throughput rate.
RADIUS
(Remote Authentication Dial-In User Service) A client-server security protocol,
developed to authenticate, authorize, and account for dial-up users. The RADIUS
server stores user profiles, which include passwords and authorization attributes.
rogue
Any wireless device that is visible on your network but not recognized. You have
the option of defining all rogue devices as either Unknown, Known, or Approved.
Management System
656 GlossaryofTerms
Based on your definition, you can deny or allow access to the network for any
rogue device.
RSSI
(Received Signal Strength Indicator) A measure of the energy observed by an
antenna when receiving a signal.
SNMP
(Simple Network Management Protocol) A standard protocol that regulates
network management over the Internet.
SNTP
(Simple Network Time Protocol) A simplified version of NTP. SNTP can be used
when the ultimate performance of the full NTP implementation described in RFC
1305 is not needed or justified.
SSID
(Service Set IDentifier) Every wireless network or network subset (such as a BSS)
has a unique identifier called an SSID. Every device connected to that part of the
network uses the same SSID to identify itself as part of the family when it wants
to gain access to the network or verify the origin of a data packet it is sending over
the network. In short, it is the unique name shared among all devices in a WLAN.
subnet mask
A mask used to determine what subnet an IP address belongs to. An IP address
has two components: (1) the network address and (2) the host address. For
example, consider the IP address 150.215.017.009. Assuming this is part of a Class
B network, the first two numbers (150.215) represent the Class B network address,
and the second two numbers (017.009) identify a particular host on this network.
symbol
Refer to map symbol and icon.
Syslog
(SYStem LOGging) A protocol that allows a machine to send event notification
messages across IP networks to event message collectors, known as Syslog
servers. Syslog messages are based on the User Datagram Protocol (UDP). They
are received on UDP port 514 and cannot exceed 1,024 bytes in length (they have
no minimum length). See also, UDP.
Management System
GlossaryofTerms 657
threshold
A value that determines the minimum and maximum limit for collected data. If
the collected data violates a defined threshold, the system reports the fault as
needing attention.
TKIP
(Temporal Key Integrity Protocol) Provides improved data encryption by
scrambling the keys using a hashing algorithm and, by adding an integrity-
checking feature, ensures that the encryption keys havent been tampered with.
transmit power
The amount of power used by an IAP transceiver to send the signal out. Transmit
power is generally measured in milliwatts, which you can convert to dBm.
UDP
(User Data Protocol) A connectionless protocol that works at the OSI transport
layer. UDP provides datagram transport but does not acknowledge their receipt.
UDP is the protocol used for processing Syslog messages. See also, Syslog.
VLAN
(Virtual LAN) A group of devices that communicate as a single network, even
though they are physically located on different LAN segments. Because VLANs
are based on logical rather than physical connections, they are extremely flexible.
A device that is moved to another location can remain on the same VLAN
without any hardware reconfiguration.
Wireless Array
A family of Xirrus proprietary high capacity wireless access points utilizing
multiple channels, specifically designed for the Enterprise market. See also,
Array.
Management System
658 GlossaryofTerms
Management System
Index 659
Index
Numerics
2-radio Arrays/APs
timeshare monitor 219
802.11a 504, 521
802.11a/n 471, 477
SSID 472
802.11b 524
802.11b/g 504, 524
802.11b/g/n 471, 477
SSID 472
802.11g 524
802.11n
WMI page 528
A
abg(n)2
intrusion detection 540
self-monitoring
radio assurance (loopback
mode) 532, 533
about this guide 6
organization 6
Access Control List 432
access control lists (ACLs) 449, 493
ACLs 432
active IAPs
per SSID 495
adding a map 256
Address Resolution Protocol (ARP)
519
Admin ID 435
admin ID
authentication via RADIUS 438
Admin Management 435
admin privileges
in admin RADIUS account 439
admin RADIUS account
if using Console port 438
admin RADIUS authentication 438
administration 432
XMS cloud 561
administrator
Windows login 24
Advanced Feature Sets 195
AeroScout
see WiFi tag 418
allow traffic
see filters 549
AOS
see ArrayOS 133, 212, 213
Appliance
virtual 10
APs
rogues, blocking 540
white list 541
APs, rogue
see rogue APs 531, 540
ARP filtering 519
Array 397
license, deleting 204
license, exporting 197
license, importing 199
license, pending 203
license, updating 201
licensing window 196
Array icon 272
ArrayOS
release supported on XN, XS 136
ArrayOS version
set for profile 133, 212, 213
Arrays
discovery for XMS Cloud 179
host name 66
how identified 66
label 66
maps, adding to 261
Management System
660 Index
maps, moving 262
Arrays, XN, XS
ArrayOS supported 136
assurance
network server connectivity 445
assurance (radio loopback testing) 531
assurance, station
see station assurance 535
attack (DoS)
see DoS attack 542
attack (impersonation)
see impersonation attack 542
attack (SSID spoofing, evil twin)
auto block 184
authentication
of admin via RADIUS 438
SSID 474
auto block
rogue APs, settings 540
SSID spoofing (evil twin) 184
auto negotiate 397
auto-blocking
rogue APs 540
white list 541
auto-configuration 509, 521, 524
channel and cell size 531
B
background images
changing, for maps 258, 276
for maps 254
formats 255
physical size 255
resolution 255
backup
deleting from database 582
backup unit
see standby mode 531
band association 471, 477
SSID 472
bandwidth reports 322
beacon interval 509
Beacon World Mode 509
benefits 4
block
rogue APs, settings 537
block (rogue APs)
see auto block 540
blocked devices 91
blocking
rogue APs 540, 541
blocking rogue APs 531
blocking, rogue APs, reports 392
broadcast 520
fast roaming 520
browser login 28
C
capacity 3
captive portal
editor 486
see web page redirect 478
white list 491
cautions 8
CDP (Cisco Discovery Protocol)
settings 407
cell
sharp cell 531
cell size 504
auto-configuration 531
cell size configuration 531
centralized management 4
channel
auto-configuration 531
configuration 531
list selection 531
channel usage
report 383
channels 504, 509, 521, 524
CHAP (Challenge-Handshake Au-
Management System
Index 661
thentication Protocol)
Admin RADIUS settings 440
web page redirect 483
Cisco Discovery Protocol (CDP) 407
client
connecting to XMS server 644
Web Start Client 28
client interface
logging in 28
client login 28
Cloud, see XMS Cloud 561
config file
editing 118
configuration 393
profile, network 206
configuration management 5
connecting to XMS server
problems 644
connectivity
servers, see network assurance 445
Console port
login via 438
contact information 648
contour map
see RF Heat Map 245
creating a map 256
CSV
exporting Array licenses 197
importing Array licenses 199
CTS/RTS 521, 524
D
data rate 521, 524
database
about 563
backups, deleting 582
repairing 634
database server
and XMS server shutdown 633
date/time restrictions
and interactions 501
DB operations 563
dedicated monitor in profile
timeshare 2-radio Arrays 219
default gateway 397
default password 25, 28, 565
default profile 66
default user name 25, 28, 565
delete
Array licenses 204
database backups 582
Delivery Traffic Indication Message
509
denial of service
see DoS attack 542
deny traffic
see filters 549
desktop icon
Web Start Client 28
detection
intrusion 540
see DoS attack 542
see impersonation attack 542
see impersonation detection 542
see intrusion detection 542
devices
blocking 91
DHCP 397
discovery
default profile 66
for XMS Cloud 179
SNMPv3 requires NTP 163, 572,
611, 645
distance (scale)
setting on map 258
DNS 406
DNS domain 406
DNS server 406
Domain Name System 406
DoS attack detection
Management System
662 Index
settings 542
DTIM 509
DTIM period 509
duplex 397
dynamic VLAN
overridden by group 499
E
EDCF 509
editor
captive portal 486
encryption
SSID 474
encryption method
recommended (WPA2 with AES)
434
setting 434
support of multiple methods 434
encryption method (encryption mode)
Open, WEP, WPA, WPA2, WPA-
Both 433
encryption standard
AES, TKIP, both 433
setting 434
Euclid
location service
data format 646
evil twin attack (SSID spoofing)
auto block 184
Excel file
exporting Array licenses 197
importing Array licenses 199
export
Array licenses 197
external login page
web page redirect 484
external splash page
web page redirect 485
F
fail-over
standby mode 531
family of products 1
FAQs 644
Fast Ethernet 397
fast roaming 520
about 503
and VLANs 503
features 4, 397, 416, 419, 509
about licensing 194
supported by license 195
figures
list of xiii
filter list 550
filter name 551
filtering
IPv6 519
filters 549, 550, 551
stateful filtering, disabling 550
firewall 549
and port usage 20
stateful filtering, disabling 550
floor plan 244
for map 254
fragmentation threshold 521, 524
frequently asked questions 644
G
Gigabit 397
global settings 509, 521, 524
glossary of terms 649
Group
management 498
group 496
VLAN overrides dynamic VLAN
499
group limits and interactions 501
Management System
Index 663
H
Heat Map (RF) 245
heat maps
migrating older maps 254
honeypot
whitelist 492
honeypot SSID
whitelist settings 492
host name 406
Array 66
HTTPS port
web page redirect 479
hutting 29, 570
hyperlinks 8
I
IAP 504, 521, 524, 543
active SSIDs 495
fast roaming 503
Intrusion Detection (IDS/IPS) 537
settings 504
IAP LED 543
IAP LED settings 543
IAPs
auto block rogues 540
intrusion detection 540
icon 272
icon, desktop
Web Start Client 28
identifying an Array 66
IDS
see Intrusion Detection 537
IEEE 802.11n
WMI page 528
image
physical size 255
image file size
minimizing 254
image formats 255
image resolution 255
image resolution, for map 255
impersonation attack detection
settings 542
implementing Voice over Wi-Fi 409,
467
import
Array licenses 199
installation 19
installation prerequisites
VM 10
internal login page
web page redirect 482
web page redirect, customize 486
internal splash page
web page redirect 481
web page redirect, customize 486
introduction 1
intrusion detection 540
and auto block settings 540
configuration 531
Intrusion Detection (IDS/IPS) 537
Intrusion Detection System (IDS) 29
IP Address 397, 406, 419, 424
IP address 25, 28, 565
IPS
see Intrusion Detection 537
IPv6
filtering 519
K
key features 4
L
label
for an Array 66
landing page
web page redirect 486
Layer 3
fast roaming 503
LEDs
Management System
664 Index
settings 543
license
and features 194
and upgrades 194
Array, deleting 204
Array, exporting 197
Array, importing 199
Array, pending 203
Array, updating 201
Array, window 196
Licensed Features
viewing in XMS Cloud 66
limits
group 501
interactions 501
station 501
traffic 501
list of figures xiii
list, access control
see access control list 449, 493
list, MAC access
see access control list 449
list, SSID access
see access control list 493
location service
data formats 646
log
see Syslog 419
logging in 28
login 28
via Console port 438
windows, for XMS 24
login page
web page redirect 482, 484
web page redirect, customize 486
long retry limit 509
loopback testing
radio assurance mode 531
M
MAC Access List 449
MAC address 449
managed network
profile 206
management 393
XMS administration 561
management capacity 3
managing Arrays 272
map
RF Heat Map 245
maps
about 243
adding a new map 256
Arrays
moving 262
Arrays, adding 261
background image, changing 258,
276
background images 254
deleting 271
distance (setting scale) 258
editable 256
floor plan 254
managing Arrays 272
map window, about 246
migrating to new release 254
properties, modifying 258
renaming 258
saving 263
scale, setting 258
working with 243
migrating older maps 254
minimizing image file sizes 254
modify
map properties 258
monitor
timeshare for 2-radio Arrays 219
monitoring 5
see intrusion detection 540
Management System
Index 665
MTU 397
size 397
MySQL
port usage 15
N
NetBIOS 338
Netflow 416
network
interfaces 396
managing by profile 206
settings 397
network assurance 445
network interfaces 397
network monitoring 5
network reporting 5
Network Time Protocol 414
network topology 3
new map 256
notes 8
NTP 414
required with SNMPv3 163, 572,
611, 645
NTP Server 414
O
Open (encryption method) 433
optimization, VLAN 520
organization of this guide 6
overview 3
P
PAP (Password Authentication Proto-
col)
Admin RADIUS settings 440
web page redirect 483
password 25, 28, 565
Windows, for XMS 24
XSMT 29
performance monitoring 5
PoE 8, 9, 11, 15, 23, 31, 103, 127, 131,
163, 164, 172, 179, 223, 382, 561, 611
PoE+ 223
PoGE 8, 9, 11, 15, 23, 31, 103, 127, 131,
163, 164, 172, 179, 382, 561, 611
port requirements 20
portal, captive 478
ports 15
prerequisites
VM 10
probe
see Netflow 416
product family 1
product overview 3
profile
ArrayOS version 133, 212, 213
dedicated monitor in profile
timeshare for 2-radio Arrays
219
default 66
network 206
properties
map, modifying 258
Q
QoS 471, 477
conflicting values 470
levels defined 473, 499
priority 471, 472, 477
SSID 465, 472, 473
user group 499
quality
of user experience 535
Quality of Service
see QoS 473, 499
queue
report 303
Management System
666 Index
R
radio
assurance (self-test) 532, 533
radio assurance (loopback testing) 531
radio assurance (loopback) mode 532,
533
RADIUS 432, 449, 493
admin authentication 438
setting admin privileges 439
setting user VSAs 452
SSID 474
RADIUS settings
web page redirect 483
reauthentication 509
remote login 28
renaming
maps 258
repairing database 634
report
queue 303
reporting 5
reports 289
about 289
Array availability 378
bandwidth 322
by Array speed 323, 325, 327,
330, 343
by Array utilization 383, 386
by station speed 333
error
by station 337
list of 289
main window 291
RF 383
schedule
specific date range 290, 302,
303
security 386
rogue list 390
station
by Array 373
by station 370
station association 349
requirements, system
VM 10
restrictions
date/time 501
stations 501
traffic 501
RF
intrusion detection 531
spectrum management 531
RF configuration 531
RF Heat Map 245
RF management
see channel 531
RF reports 383
RF resilience 531
roaming 520
see fast roaming 503
rogue AP
blocking 540
white list 541
settings for blocking 537
rogue APs
auto block settings 540
blocking 531
blocking, reports 392
rogues
clocking 91
RTS 521, 524
RTS threshold 521, 524
S
save
maps 263
scalability 4
scale, setting
for map 258
schedule
Management System
Index 667
auto channel configuration 531
security 432
security management 4
security reports 386
see group 496
see web page 478
self-monitoring 540
radio assurance options 532, 533
self-test
radio assurance mode 532, 533
server
database
repairing 634
login 632
port assignments 632
shut down 632
server console 26, 626
server, VTun
see VTun 412
servers
connectivity, see network assur-
ance 445
service
XMS server as Windows service
624
Services 414
Set AOS version button
for profile 133, 212, 213
sharp cell 531
setting in WMI 534
short retry limit 509
shutting down the unit 29, 570
shutting down the XM-3300 570
shutting down XMS server 29
SNMP 397, 414, 424
port usage 15
required for XMS 425
SNMPv3
NTP usage required 163, 572, 611,
645
time sync with Arrays 163, 572,
611, 645
software image
profile, network 206
software update
SSH port 603, 640
software upgrade
user impact 210
spectrum (RF) management 531
speed 397
splash page
web page redirect 481
web page redirect, customize 486
splash page (external)
web page redirect 485
spoofing, of SSIDs (evil twin)
auto block 184
SSH 397, 432
port for software updates 603, 640
SSH-2 432
SSID 471, 472, 477
active IAPs 495
honeypot, whitelist 492
QoS 465, 473
web page redirect settings 478
web page redirect settings, about
479
SSID Access List 493
SSID address 493
SSID Management 471, 472, 477
authentication/encryption 474
honeypot whitelist 492
RADIUS 474
RADIUS accounting 474
station limits 476
time of day limits 476
SSID spoofing (evil twin)
auto block 184
standby mode 531
starting client
Management System
668 Index
starting Web Start Client 28
stateful filtering
disabling 550
static IP 397
station
assurance 535
station association reports 349
station assurance 535
station timeout period 509
station URL logging
see Syslog 421
stations
limits and interactions 501
statistics
netflow 416
stopping the server 29, 570
subnet 397
switch (XT-5024/XT-5048)
managing 223
synchronize 414
Syslog 414, 419
station URL logging 421
syslog
port usage 15
Syslog reporting 419
Syslog Server 419, 421
System Log 419
see Syslog 421
system requirements
vm 10
T
tag, WiFi 418
TCP
port requirements 20
technical support 643
contact information 648
frequently asked questions 644
Telnet 432
time zone 414
timeout 509
timeshare
in profiles 219
TKIP encryption
and XN Arrays 447
topography 244
topology 3
traffic
filtering 549
limits and interactions 501
trap port 424
tunneled
fast roaming 520
tunnels
see VTun 409, 412
twin attack (SSID spoofing)
auto block 184
U
UDP
port requirements 20
upgrade
about licensing 194
upgrade packs 3
upgrade, software
user impact 210
URL logging
see Syslog 421
used by XMS server 15
user accounts
setting RADIUS VSAs 452
user group 496
QoS 499
user group limits and interactions 501
user name 25, 28, 565
V
version, ArrayOS 206
Virtual Appliance 10
system requirements 10
Management System
Index 669
virtual tunnels
see VTun 412
VLAN 471, 477
broadcast optimization 520
dynamic
overridden by group 499
group (vs. dynamic VLAN) 499
SSID 472
VLAN ID 471, 477
VLANs 409
and fast roaming 503
VMware
Virtual Appliance 10
voice
fast roaming 503
implementing on Array 409, 467
Voice-over IP 524
VoIP 524
VTS
Virtual Tunnel Server 409, 412
VTun
specifying tunnel server 409, 412
understanding 409
W
web page redirect
captive portal 478
CHAP (Challenge-Handshake Au-
thentication Protocol) 483
customize internal login/splash
page 486
editor 486
external login page 484
external splash page 485
HTTPS port 479
internal login page 482
internal splash page 481
landing page 486
PAP, CHAP 483
RADIUS settings 483
SSID settings 478
SSID settings, about 479
white list 491
Web Start Client 28
WEP 432, 471, 477
WEP (Wired Equivalent Privacy)
encryption method 433
WEP encryption
and XN Arrays 448
white list
captive portal 491
rogue auto blocking 541
web page redirect 491
whitelist
honeypot 492
WiFi tag 418
window
Array licensing 196
Windows
login 24
Windows server
shutting down 29, 570
Windows service 624
WMI 504
WPA 432, 471, 477
WPA (Wi-Fi Protected Access) and
WPA2
encryption method 433
WPR
see web page redirect 478
X
Xirrus Advanced Feature Sets 195
Xirrus Management System
SNMP required 425
Xirrus Roaming Protocol 520
Xirrus Server Management Tool
see XSMT 29
Xirrus Virtual Appliance
see Virtual Appliance 10
Management System
670 Index
XM-3300 1, 2, 9
(Xirrus Management Platform) 1
shutting down 29, 570
stopping the server 29, 570
XMS
port requirements 20
setting IP address of 424
SNMP required 425
XMS client
connecting to XMS server 644
XMS Cloud
administration 561
discovery 179
XMS server
as Windows service 624
managing - see XSMT 29
port usage 15
problems connecting client 644
shutting down 29
Virtual Appliance 10
XMS server login 24
XMS-9000-VM 10
XN Array
management 393
XN Arrays
ArrayOS supported 136
XRP 520
XS Arrays
ArrayOS supported 136
XSMT
password 29
shutdown XMS server 29
Xirrus Server Management Tool 29
XT-5024 223
XT-5048 223
High Performance Wireless Networks
1.800.947.7871 Toll Free in the US
+1.805.262.1600 Sales
+1.805.262.1601 Fax
2101 Corporate Center Drive
Thousand Oaks, CA 91320, USA
To learn more visit:
xirrus.com or
email [email protected]
201 Xirrus, Inc. All Rights Reserved. The Xirrus logo is a registered trademark of Xirrus, Inc.
All other trademarks are the property of their respective owners. Content subject to change without notice.
800-0007-003J