OmniVista 3600 Air Manager 7.4

Transcription

1 OmniVista 3600 Air Manager 7.4 User Guide

2 Copyright 2012 Alcatel-Lucent. All rights reserved. Specifications in this manual are subject to change without notice. Originated in the USA. AOS-W, Alcatel 4302, Alcatel 4304, Alcatel 4306, Alcatel 4308, Alcatel 4324, Alcatel 4504, Alcatel 4604, Alcatel 4704, Alcatel 6000, OAW-AP41, OAW-AP68, OAW-AP60/61/65, OAW-AP70, OAW-AP80, OAW-AP92/93, OAW-AP105, OAW-AP120/121, OAW-AP124/ 125, OAW-AP175, OAW-IAP92/93/105, OAW-RAP2, OAW-RAP5, and Omnivista 3600 Air Manager are trademarks of Alcatel-Lucent in the United States and certain other countries. Any other trademarks appearing in this manual are the property of their respective companies. Legal Notice The use of Alcatel-Lucent switching platforms and software, by all individuals or corporations, to terminate Cisco or Nortel VPN client devices constitutes complete acceptance of liability by that individual or corporation for this action and indemnifies, in full, Alcatel- Lucent from any and all legal actions that might be taken against it with respect to infringement of copyright on behalf of Cisco Systems West Agoura Road Calabasas, CA OmniVista AirManager OV User Guide January 2012

3 Contents Preface...11 Document Organization...11 Note, Caution, and Warning Icons...12 Contacting Support...12 Chapter 1 Introduction...13 A Unified Wireless Network Command Center...13 OV3600 Management Platform...13 Alcatel-Lucent Configuration...14 VisualRF...14 RAPIDS...14 Master Console and Failover...14 Integrating OV3600 into the Network and Organizational Hierarchy...15 Chapter 2 Installing and Getting Started...17 Hardware Requirements and Installation Media...17 Supported Browsers...17 Installing Linux CentOS 5 (Phase 1)...18 Installing OV3600 Software (Phase 2)...18 Getting Started...18 Step 1: Configuring Date and Time, Checking for Prior Installations...18 Date and Time...18 Previous OV3600 Installations...19 Step 2: Installing OV3600 Software...19 Step 3: Checking the OV3600 Installation...19 Step 4: Assigning an IP Address to the OV3600 System...19 Step 5: Naming the OV3600 Network Administration System...20 Step 6: Assigning a Host Name to OV Step 7: Changing the Default Root Password...20 Completing the Installation...21 Configuring and Mapping Port Usage for OV OV3600 Navigation Basics...22 Status Section...22 Navigation Section...23 Activity Section...26 Help Links in the UI...26 Common List Settings...26 Buttons and Icons...27 Getting Started with OV Chapter 3 Configuring OV Before You Begin...31 Formatting the Top Header...31 Customizing Columns in Lists...32 Resetting Pagination Records...33 Using the Pagination Widget...33 OmniVista 3600 Air Manager 7.4 User Guide Contents 3

4 Using Export CSV for Lists and Reports...34 Defining Graph Display Preferences...34 Customizing the Dashboard...34 Customized Search...36 Setting Severe Alert Warning Behavior...36 Defining General OV3600 Server Settings...37 Defining OV3600 Network Settings...44 Creating OV3600 Users...45 Creating OV3600 User Roles...47 Configuring Login Message, TACACS+ and RADIUS Authentication...49 Setting Up Login Configuration Options...50 Setting up Single Sign-On...50 Configuring TACACS+ Authentication...51 Configuring RADIUS Authentication and Authorization...52 Integrating a RADIUS Accounting Server...53 Enabling OV3600 to Manage Your Devices...54 Configuring Communication Settings for Discovered Devices...54 Loading Device Firmware Onto OV3600 (optional)...56 Overview of the Device Setup > Upload Firmware & Files Page...56 Loading Firmware Files to OV Using Web Auth Bundles in OV Setting Up Device Types...59 Configuring Cisco WLSE and WLSE Rogue Scanning...59 Introduction to Cisco WLSE...60 Configuring WLSE Initially in OV Adding an ACS Server for WLSE...60 Enabling Rogue Alerts for Cisco WLSE...61 Configuring WLSE to Communicate with APs...61 Discovering Devices...61 Managing Devices...61 Inventory Reporting...61 Defining Access...62 Grouping...62 Configuring IOS APs for WDS Participation...62 WDS Participation...62 Primary or Secondary WDS...62 Configuring ACS for WDS Authentication...63 Configuring Cisco WLSE Rogue Scanning...63 Configuring ACS Servers...64 Integrating OV3600 with an Existing Network Management Solution (NMS)...65 Auditing PCI Compliance on the Network...66 Introduction to PCI Requirements...66 PCI Auditing in the OV3600 Interface...67 Enabling or Disabling PCI Auditing...68 Deploying WMS Offload...69 Overview of WMS Offload in OV General Configuration Tasks Supporting WMS Offload in OV Additional Information Supporting WMS Offload...70 Chapter 4 Configuring and Using Device Groups...71 OV3600 Groups Overview...72 Viewing All Defined Device Groups...72 Configuring Basic Group Settings...74 Adding and Configuring Group AAA Servers Contents OmniVista 3600 Air Manager 7.4 Version 7.4

5 Configuring Group Security Settings...82 Configuring Group SSIDs and VLANs...84 Configuring Radio Settings for Device Groups...88 Cisco WLC Group Configuration...92 Accessing Cisco WLC Configuration...92 Navigating Cisco WLC Configuration...92 Configuring WLANs for Cisco WLC Devices...93 Defining and Configuring LWAPP AP Groups for Cisco Devices...95 Viewing and Creating Cisco AP Groups...95 Configuring Cisco Controller Settings...95 Configuring Wireless Parameters for Cisco Controllers...96 Configuring Cisco WLC Security Parameters and Functions...96 Configuring Management Settings for Cisco WLC...96 Configuring Group PTMP Settings...97 Configuring Proxim Mesh Radio Settings...98 Configuring Group MAC Access Control Lists...99 Specifying Minimum Firmware Versions for APs in a Group...99 Comparing Device Groups Deleting a Group Changing Multiple Group Configurations Modifying Multiple Devices Using Global Groups for Group Configuration Chapter 5 Discovering, Adding, and Managing Devices Device Discovery Overview Discovering and Adding Devices SNMP/HTTP Scanning Adding Networks for SNMP/HTTP Scanning Adding Credentials for Scanning Defining a Scan Set Running a Scan Set Enabling Cisco Discovery Protocol (CDP) Authorizing Devices to OV3600 from APs/Devices > New Page Manually Adding Individual Devices Adding Devices with the Device Setup > Add Page Adding Multiple Devices from a CSV File Adding Universal Devices Assigning Devices to the Ignored Page Monitoring Devices Viewing Device Monitoring Statistics Understanding the APs/Devices > Monitor Pages for All Device Types Monitoring Data Specific to Wireless Devices Evaluating Radio Statistics for an AP Overview of the Radio Statistics Page Viewing Real-Time ARM Statistics Issues Summary section Radio Counters Summary Radio Statistics Interactive Graphs Recent ARM Events Log Detected Interfering Devices Table Active BSSIDs Table Monitoring Data for Mesh Devices Monitoring Data for Wired Devices (Routers and Switches) Understanding the APs/Devices > Interfaces Page Auditing Device Configuration OmniVista 3600 Air Manager 7.4 User Guide Contents 5

6 Using Device Folders (Optional) Configuring and Managing Devices Moving a Device from Monitor Only to Manage Read/Write Mode Configuring AP Settings Setting a Maintenance Window for a Device Configuring Device Interfaces for Switches Individual Device Support and Firmware Upgrades Troubleshooting a Newly Discovered Down Device Setting up Alcatel-Lucent Spectrum Analysis in OV Spectrum Configurations and Prerequisites Setting up a Permanent Spectrum Alcatel-Lucent AP Group Configuring an Individual AP to run in Spectrum Mode Configuring a Switch to use the Spectrum Profile Chapter 6 Creating and Using Templates Group Templates Supported Device Templates Template Variables Viewing and Adding Templates Configuring General Template Files and Variables Configuring General Templates IOS Configuration File Template Device Configuration File on APs/Devices > Audit Configuration Page Using Template Syntax Using Directives to Eliminate Reporting of Configuration Mismatches Ignore_and_do_not_push Command Push_and_exclude Command Using Conditional Variables in Templates Using Substitution Variables in Templates Using AP-Specific Variables Configuring Cisco IOS Templates Applying Startup-config Files WDS Settings in Templates SCP Required Settings in Templates Supporting Multiple Radio Types via a Single IOS Template Configuring Single and Dual-Radio APs via a Single IOS Template Configuring Cisco Catalyst Switch Templates Configuring Symbol Controller / HP WESM Templates Configuring a Global Template Chapter 7 Using RAPIDS and Rogue Classification Introduction to RAPIDS Viewing Overall Network Health on RAPIDS > Overview Setting Up RAPIDS Basic Configuration Rogue Containment Options Additional Settings Defining RAPIDS Rules Switch Classification with WMS Offload Device OUI Score Rogue Device Threat Level Viewing and Configuring RAPIDS Rules Deleting or Editing a Rule Recommended RAPIDS Rules Using RAPIDS Rules with Additional OV3600 Functions Contents OmniVista 3600 Air Manager 7.4 Version 7.4

7 Viewing Rogues on the RAPIDS > List Page Overview of the RAPIDS > Detail Page Viewing Ignored Rogue Devices Using RAPIDS Workflow to Process Rogue Devices Score Override Using the Audit Log Additional Resources Chapter 8 Performing Daily Administration in OV Monitoring and Supporting OV3600 with the System Pages Using the System > Status Page Viewing Device Events in System > Syslog & Traps Using the System > Event Log Page Viewing, Delivering and Responding to Triggers and Alerts Viewing Triggers Creating New Triggers Setting Triggers for Devices Setting Triggers for Interfaces and Radios Setting Triggers for Discovery Setting Triggers for Clients Setting Triggers for RADIUS Authentication Issues Setting Triggers for IDS Events Setting Triggers for OV3600 Health Delivering Triggered Alerts Viewing Alerts Responding to Alerts Monitoring and Supporting WLAN Clients Overview of the Clients Pages Monitoring WLAN Users in the Clients > Connected and Clients > All Pages Supporting Guest WLAN Users With the Clients > Guest Users Page Supporting VPN Users with the Clients > VPN Sessions Page Supporting RFID Tags With the Clients > Tags Page Evaluating and Diagnosing User Status and Issues Evaluating User Status with the Clients > Client Detail Page Mobile Device Access Control in Clients > Client Detail and Clients > Connected..205 Classifying Alcatel-Lucent Devices in Client Detail Quick Links for Clients on Alcatel-Lucent Devices Using the Deauthenticate Client Feature Viewing a Client s Association History Viewing the Rogue Association History for a Client Evaluating Client Status with the Clients > Diagnostics Page Managing Mobile Devices with SOTI MobiControl and OV Overview of SOTI MobiControl Prerequisites for Using MobiControl with OV Adding a Mobile Device Management Server for MobiControl Accessing MobiControl from the Clients > Client Detail Page Monitoring and Supporting OV3600 with the Home Pages Monitoring OV3600 with the Home > Overview Page Viewing and Updating License Information Searching OV3600 with the Home > Search Page Accessing OV3600 Documentation Configuring Your Own User Information with the Home > User Info Page Using the System > Configuration Change Jobs Page Using the System > Firmware Upgrade Jobs Page Using the System > Performance Page Supporting OV3600 Servers with the Master Console OmniVista 3600 Air Manager 7.4 User Guide Contents 7

8 Using the Public Portal on Master Console Adding a Managed OV3600 with the Master Console Using Global Groups with Master Console Upgrading OV Upgrade Instructions Upgrading Without Internet Access Backing Up OV Viewing and Downloading Backups Running Backup on Demand Restoring from a Backup Using OV3600 Failover for Backup Navigation Section of OV3600 Failover Adding Watched OV3600 Stations Logging out of OV Chapter 9 Chapter 10 Creating, Running, and ing Reports Overview of OV3600 Reports Reports > Definitions Page Overview Reports > Generated Page Overview Using Daily Reports Viewing Generated Reports Using Custom Reports Using the License Report Using the Capacity Planning Report Using the Configuration Audit Report Using the Device Summary Report Using the Device Uptime Report Using the IDS Events Report Using the Inventory Report Using the Memory and CPU Utilization Report Using the Network Usage Report Using the New Rogue Devices Report Using the New Users Report Using the PCI Compliance Report Using the Port Usage Report Using the RADIUS Authentication Issues Report Using the RF Health Report Using the Rogue Clients Report Using the Rogue Containment Audit Report Using the Client Session Report Defining Reports ing and Exporting Reports ing Reports in General Applications ing Reports to Smarthost Exporting Reports to XML or CSV Transferring Reports Using FTP Using VisualRF Features Useful Terms Starting VisualRF Basic QuickView Navigation Network View Navigation Overlays Display Menu Contents OmniVista 3600 Air Manager 7.4 Version 7.4

9 Edit Menu Mesh View Navigation Using the Settings in the VisualRF > Setup Page VisualRF Resource Utilization Configuring QuickView Personal Preferences Increasing Location Accuracy Adding Exterior Walls Location Training for Stationary Devices Adding Client Surveys Adding Location Probability Regions Adding an IDF Viewing Port Status on Deployed Switches Fine-Tuning Location Service in VisualRF > Setup Configuring Infrastructure Deploying APs for Client Location Accuracy Using QuickView to Assess RF Environments Viewing a Wireless User's RF Environment Tracking Location History Checking Signal Strength to Client Location Viewing an AP s Wireless RF Environment Viewing a Floor Plan s RF Environment Viewing a Network, Campus, Building s RF Environment Viewing Campuses, Buildings, or Floors from a Tree View Planning and Provisioning Creating a New Campus Creating a New Building in a Campus Importing a Floor Plan Editing a Floor Plan Image Cropping the Floor Plan Image Sizing a Non-CAD Floor Plan Removing Color from a Floor Plan Image Assigning Campus, Building and Floor Numbers Assigning Optional Planner, Owner, or Installer Information for the Floor Plan Controlling the Layers in the Uploaded Floor Plan (CAD only) Error Checking of CAD Images Last Steps in Editing an Uploaded Image Provisioning Existing Access Points onto the Floor Plan Automatically Provisioning APs onto a Floor Plan Tweaking a Planning Region Auto-Matching Planned Devices Printing a Bill of Materials Report Importing and Exporting in VisualRF Exporting a campus Importing from CAD Batch Importing CAD Files Requirements Pre Processing Steps Upload Processing Steps Post Processing Steps Sample Upload Instruction XML File Common Importation Problems Importing from an Alcatel-Lucent Controller Pre-Conversion Checklist Process on Controller Process on AMP VisualRF Location APIs Sample Device Location Response OmniVista 3600 Air Manager 7.4 User Guide Contents 9

10 Sample Site Inventory Response About VisualRF Plan Overview Minimum requirements Installation Differences between VisualRF Plan and VisualRF online Appendix A Setting Up Alcatel-Lucent Instant in OV Overview of Alcatel-Lucent Instant Using Alcatel-Lucent Instant with OV Workflow of the Alcatel-Lucent Instant and OV3600 Integration Process Setting up Alcatel-Lucent Instant Hardware Required Personnel Creating your Organization String The Shared Secret Key Entering the Organization String and OV3600 Information into the IAP Receiving the Alcatel-Lucent Instant Virtual Controller as a New Device in OV Verifying the Shared Secret and Adding the Device Remaining Manual Admin Tasks in OV OV3600 Pages with Instant-Specific Features Other Available Features Firmware Image Management Intrusion Detection System Known Issues of the Alcatel-Lucent Instant Integration with OV Appendix B Installing OV3600 on VMware ESX (3i v. 3.5) Creating a New Virtual Machine to Run OV Installing OV3600 on the Virtual Machine OV3600 Post-Installation Issues on VMware Index Contents OmniVista 3600 Air Manager 7.4 Version 7.4

11 Preface The preface provides an overview of the user guide and contact information for Alcatel-Lucent in the following sections: Document Organization on page 11 Note, Caution, and Warning Icons on page 12 Contacting Support on page 12 Document Organization The user guide includes instructions and examples of the graphical user interface (GUI) for installation, configuration, and daily operation of OV3600. This includes wide deployment of wired and wireless devices, rogue detection and classification, security, reports, and additional features. Table 1 Document Organization and Purposes Chapter Chapter 1, Introduction Chapter 2, Installing and Getting Started Chapter 3, Configuring OV3600 Chapter 4, Configuring and Using Device Groups Chapter 5, Discovering, Adding, and Managing Devices Chapter 6, Creating and Using Templates Chapter 7, Using RAPIDS and Rogue Classification Chapter 8, Performing Daily Administration in OV3600 Chapter 9, Creating, Running, and ing Reports Chapter 10, Using VisualRF Appendix A, Setting Up Alcatel-Lucent Instant in OV3600 on page 299 Appendix B, Installing OV3600 on VMware ESX (3i v. 3.5) on page 305 Index Description Introduces and presents OV3600, its components, and general network functions. Describes system and network requirements, Linux OS installation, and OV3600 installation. Describes the primary and required configurations for startup and launch of OV3600, with frequently used optional configurations. Describes configuration and deployment for group device profiles. Describes how to discover and manage devices on the network. Describes and illustrates the use of templates in group and global device configuration. Describes RAPIDS module of OV3600, and enhanced rogue classification supported in OV3600. Describes common daily operations and tools in OV3600, to include general user administration, the use of triggers and alerts, network monitoring, and backups. Describes OV3600 reports, scheduling and generation options, and distribution of reports from OV3600. Describes how to use VisualRF. Describes how to set up and use Alcatel-Lucent Instants in OV3600. Describes the procedure to install OV3600 on VMware ESX (3i v. 3.5). Provides extensive citation of and links to document topics, with emphasis on the OV3600 GUI and tasks relating to OV3600 installation and operation. OmniVista 3600 Air Manager 7.4 User Guide Preface 11

12 Note, Caution, and Warning Icons This document uses the following note, caution, and warning icons to emphasize advisories for certain actions, configurations, or concepts: Indicates helpful suggestions, pertinent information, and important things to remember. Indicates a risk of damage to your hardware or loss of data. A Indicates a risk of personal injury or death. Contacting Support Contact Center Online Main Site Support Site support@ind.alcatel.com Service & Support Contact Center Telephone North America Latin America Europe +33 (0) Asia Pacific Worldwide Preface OmniVista 3600 Air Manager 7.4 User Guide

13 Chapter 1 Introduction Thank you for choosing OmniVista 3600 Air Manager. OV3600 makes it easy and efficient to manage your wireless network by combining industry-leading functionality with an intuitive user interface, enabling network administrators and helpdesk staff to support and control even the largest wireless networks in the world. The User Guide provides instructions for the installation, configuration, and operation of OV3600. This chapter includes the following topics: A Unified Wireless Network Command Center on page 13 Integrating OV3600 into the Network and Organizational Hierarchy on page 15 If you have any questions or comments, please contact Alcatel-Lucent support. A Unified Wireless Network Command Center OmniVista 3600 Air Manager is the only network management software that offers you a single intelligent console from which to monitor, analyze, and configure wireless networks in automatic fashion. Whether your wireless network is simple or a large, complex, multi-vendor installation, OV3600 manages it all. OV3600 supports hardware from leading wireless vendors including Alcatel-Lucent, Aruba Networks, Avaya, Cisco (Aironet and WLC), Dell PowerConnect W-Series, Enterasys, Juniper Networks, LANCOM Systems, Meru, Nortel, ProCurve by HP, Proxim, Symbol, Trapeze, Tropos, and many others. The components of the OV3600 are detailed below: OV3600 Management Platform OV3600 is the centerpiece of OmniVista 3600 Air Manager, offering the following functions and benefits: Core network management functionality: Network discovery Configuration of APs & controllers Automated compliance audits Firmware distribution Monitoring of every device and user connected to the network Real-time and historical trend reports Granular administrative access Role-based (for example, Administrator contrasted with Help Desk) Network segment (for example, Retail Store network contrasted with Corporate HQ network) Flexible device support Thin, thick, mesh network architecture Multi-vendor support Current and legacy hardware support OmniVista 3600 Air Manager 7.4 User Guide Introduction 13

14 Alcatel-Lucent Configuration OV3600 supports global and group-level configuration of AOS-W, the operating system, software suite, and application engine that operates mobility and centralizes control over the entire mobile environment. For a complete description of AOS-W, refer to the AOS-W 7.4 User Guide. OV3600 consolidates and pushes global Alcatel-Lucent configurations from within OV3600. Two pages in OV3600 support Alcatel-Lucent Configuration: Device Setup > Alcatel-Lucent Configuration for global Alcatel-Lucent Configuration Groups > Alcatel-Lucent Config for group-level Alcatel-Lucent Configuration For additional information that includes a comprehensive inventory of all pages and settings that support Alcatel-Lucent Configuration, refer to the OmniVista 3600 Air Manager 7.4 Configuration Guide. VisualRF VisualRF is a powerful tool for monitoring and managing radio frequency (RF) dynamics within your wireless network, to include the following functions and benefits: Accurate location information for all wireless users and devices Up-to-date heat maps and channel maps for RF diagnostics Adjusts for building materials. Supports multiple antenna types. Floor plan, building, and campus views Visual display of errors and alerts Easy import of existing floor plans and building maps Planning of new floor plans and AP placement recommendations RAPIDS RAPIDS is a powerful and easy-to-use tool for monitoring and managing security on your wireless network, to include the following features and benefits: Automatic detection of unauthorized wireless devices Rogue device classification that supports multiple methods of rogue detection Wireless detection: Uses authorized wireless APs to report other devices within range. Calculates and displays rogue location on VisualRF map. Wired network detection: Discovers rogue APs located beyond the range of authorized APs/sensors. Queries routers and switches. Ranks devices according to the likelihood they are rogues. Multiple tests to eliminate false positive results. Provides rogue discovery that identifies the switch and port to which a rogue device is connected. Master Console and Failover The OV3600 Master Console and Failover tools enable network-wide information in easy-to-understand presentation, to entail operational information and high-availability for failover scenarios. The benefits of these tools include the following: Provides network-wide visibility, even when the WLAN grows to 50,000+ devices Executive Portal allows executives to view high-level usage and performance data Aggregated alerts 14 Introduction OmniVista 3600 Air Manager 7.4 User Guide

15 Failover Many-to-one failover One-to-one failover The Master Console and Failover servers can be configured with a Device Down trigger that generates an alert if communication is lost. In addition to generating an alert, the Master Console or Failover server can also send or NMS notifications about the event. Integrating OV3600 into the Network and Organizational Hierarchy OmniVista 3600 Air Manager generally resides in the NOC and communicates with various components of your WLAN infrastructure. In basic deployments, OV3600 communicates solely with indoor wireless access points (and WLAN controllers over the wired network. In more complex deployments, OV3600 seamlessly integrates and communicates with authentication servers, accounting servers, TACACS+ servers, routers, switches, network management servers, wireless IDS solutions, helpdesk systems, indoor wireless access points, mesh devices. OV3600 has the flexibility to manage devices on local networks, remote networks, and networks using Network Address Translation (NAT). OV3600 communicates over-the-air or over-thewire using a variety of protocols. The power, performance, and usability of OV3600 become more apparent when considering the diverse components within a WLAN. Table 3 itemizes some example network components. Table 3 Components of a WLAN Component Autonomous AP Thin AP WLAN switch NMS RADIUS Authentication RADIUS Accounting Wireless Gateways TACACS+ Routers/Switches Help Desk Systems Rogue APs Description Standalone device which performs radio and authentication functions Radio-only device coupled with WLAN controller to perform authentication Used in conjunction with thin APs to coordinate authentication and roaming Network Management Systems and Event Correlation (OpenView, Tivoli, and so forth) RADIUS authentication servers (Funk, FreeRADIUS, ACS, or IAS) OV3600 itself serves as a RADIUS accounting client Provide HTML redirect and/or wireless VPNs Used to authenticate OV3600 administrative users Provide OV3600 with data for user information and AP and Rogue discovery Remedy EPICOR Unauthorized APs not registered in the OV3600 database of managed APs The flexibility of OV3600 enables it to integrate seamlessly into your business hierarchy as well as your network topology. OV3600 facilitates various administrative roles to match each individual user's role and responsibility: A Help Desk user may be given read-only access to monitoring data without being permitted to make configuration changes. A U.S.-based network engineer may be given read-write access to manage device configurations in North America, but not to control devices in the rest of the world. A security auditor may be given read-write access to configure security policies across the entire WLAN. NOC personnel may be given read-only access to monitoring all devices from the Master Console. OmniVista 3600 Air Manager 7.4 User Guide Introduction 15

16 16 Introduction OmniVista 3600 Air Manager 7.4 User Guide

17 Chapter 2 Installing and Getting Started This chapter contains information and procedures for installing and launching OV3600, and includes the following topics: Hardware Requirements and Installation Media on page 17 Supported Browsers on page 17 Installing Linux CentOS 5 (Phase 1) on page 18 Installing OV3600 Software (Phase 2) on page 18 Configuring and Mapping Port Usage for OV3600 on page 21 OV3600 Navigation Basics on page 22 Getting Started with OV3600 on page 28 OV3600 does not support downgrading to older versions. Significant data could be lost or compromised in such a downgrade. In unusual circumstances requiring that you return to an earlier version of OV3600, we recommend you perform a fresh installation of the earlier OV3600 version, and then restore data from a pre-upgrade backup. Hardware Requirements and Installation Media The OV3600 installation CD includes all software (including the Linux OS) required to complete the installation of OV3600. OV3600 supports any hardware that is Red Hat Enterprise Linux 5 certified. By default, all installs are based on a 64-bit operating system. OV3600 hardware requirements vary by version. As additional features are added to OV3600, increased hardware resources become necessary. For the most recent hardware requirements, refer to the OmniVista 3600 Air Manager 7.4 Server Sizing Guide at Home > Documentation. OV3600 is intended to operate as a soft appliance. Other applications should not run on the same installation. Additionally, local shell users can access data on OV3600, so it is important to restrict access to the shell only to authorized users. You can create sudo users in place of root for companies that don't allow root logins. Supported Browsers Windows (XP, Vista, Windows 7) Internet Explorer 7/8/9 Firefox 3.x Google Chrome 9.x (stable) Mac (OS X, 10.5, 10.6) Safari 4.x and higher, Firefox 3.x Google Chrome 9.x OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 17

18 Installing Linux CentOS 5 (Phase 1) Perform the following steps to install the Linux CentOS 5 operating system. The Linux installation is a prerequisite to installing OV3600 on the network management system. Caution: This procedure erases the hard drive(s) on the server. 1. Insert the OV3600 installation CD-ROM into the drive and boot the server. 2. If this is a new installation of the OV3600 software, type install and press Enter. To configure the partitions manually, type expert and press Enter. The following message appears on the screen: Welcome to OV3600 Installer Phase I - To install a new OV3600, type install <ENTER>. WARNING: This will ERASE all data on your hard drive. - To install OV3600 and manually configure hard drive settings, type expert <ENTER>. boot: 3. Allow the installation process to continue. Installing the CentOS software (Phase I) takes 10 to 20 minutes to complete. This process formats the hard drive and launches Anaconda to install all necessary packages. Anaconda gauges the progress of the installation. Upon completion, the system will prompt you to eject the installation CD and reboot the system. 4. Remove the CD from the drive and store in a safe location. Installing OV3600 Software (Phase 2) Getting Started After the reboot, the GRUB screen appears. 1. Press Enter or wait six seconds, and the system automatically loads the kernel. 2. When the kernel is loaded, log into the server using the following credentials: login = root password = admin 3. Start the OV3600 software installation script by executing the./ov3600-install command. Type./ov3600-install at the command prompt and press Enter to execute the script. Step 1: Configuring Date and Time, Checking for Prior Installations Date and Time The following message appears, and this step ensures the proper date and time are set on the server Date and Time Configuration Current Time: Fri Nov 21 09:18:12 PST ) Change Date and Time 2) Change Time Zone 0) Finish Ensure that you enter the accurate date and time during this process. Errors will arise later in the installation if the specified date varies significantly from the actual date, especially if the specified 18 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

19 date is in the future and it is fixed later. Best practices is to configure NTPD to gradually adjust your clock to the correct time. 1. Select 1 to set the date and select 2 to set the time zone. Press Enter after each configuration to return to the message menu above. Caution: Changing these settings after the installation can cause data loss, especially for time-series data such as Client and Usage graphs. Avoid delayed configuration. 2. Press 0 to complete the configuration of date and time information, and to continue to the next step. Previous OV3600 Installations The following message appears after date and time are set: Welcome to OV3600 Installer Phase 2 STEP 1: Checking for previous OV3600 installations If a previous version of OV3600 software is not discovered, the installation program automatically proceeds to Step 2: Installing OV3600 Software on page 19. If a previous version of the software is discovered, the following message appears on the screen. The installation program discovered a previous version of the software. Would you like to reinstall OV3600? This will erase OV3600's database. Reinstall (y/n)? Type y and press Enter to proceed. Caution: This action erases the current database, including all historical information. To ensure that the OV3600 database is backed up prior to reinstallation, answer `n` at the prompt above and contact your Value Added Reseller or directly contact Alcatel-Lucent support. Step 2: Installing OV3600 Software The following message appears while OV3600 software is transferred and compiled. STEP 2: Installing OV3600 software This will take a few minutes. Press Alt-F9 to see detailed messages. Press Alt-F1 return to this screen. This step requires no user input, but you can follow the instructions to monitor its progress and switch back to the installation screen. Step 3: Checking the OV3600 Installation After the OV3600 software installation is complete, the following message appears: STEP 3: Checking OV3600 installation Database is up. OV3600 is running version: (version number) This step requires no user input. Proceed to the next step as prompted to do so. Step 4: Assigning an IP Address to the OV3600 System While the OV3600 primary network interface accepts a DHCP address initially during installation, OV3600 does not function when launched unless a static IP is assigned. Complete these tasks to assign the static IP address. The following message appears: STEP 4: Assigning OV3600's address OV3600 must be configured with a static IP Primary Network Interface Configuration ) IP Address : xxx.xxx.xxx.xxx OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 19

20 2) Netmask : xxx.xxx.xxx.xxx 3) Gateway : xxx.xxx.xxx.xxx 4) Primary DNS : xxx.xxx.xxx.xxx 5) Secondary DNS: xxx.xxx.xxx.xxx 9) Commit Changes 0) Exit (discard changes) If you want to configure a second network interface, please use OV3600's web interface, AMP Setup --> Network Tab 1. Enter the network information. The Secondary DNS setting is an optional field. 2. Commit the changes by typing 9 and pressing Enter. To discard the changes, type 0 and press Enter. Step 5: Naming the OV3600 Network Administration System Upon completion of the previous step, the following message appears. STEP 5: Naming OV3600 OV3600 name is currently set to: New OV3600 Please enter a name for your OV3600: At the prompt, enter a name for your OV3600 server and press Enter. Step 6: Assigning a Host Name to OV3600 Upon completion of the previous step, the following message appears on the screen. STEP 6: Assigning OV3600's hostname Does OV3600 have a valid DNS name on your network (y/n)? 1. If OV3600 does not have a valid host name on the network, enter n at the prompt. The following appears: Generating SSL certificate for < IP Address > 2. If OV3600 does have a valid host name on the network, enter y at the prompt. The following appears: Enter OV3600's DNS name: 3. Type the OV3600 DNS name and press Enter. The following message appears: Generating SSL certificate for < IP Address > Proceed to the next step as the system prompts you. Step 7: Changing the Default Root Password Upon completion of the prior step, the following message appears. STEP 7: Changing default root password. You will now change the password for the 'root' shell user. Changing password for user root. New Password: Enter the new root password and press Enter. The Linux root password is similar to a Windows administrator password. The root user is a super user who has full access to all commands and directories on the computer. This password should be kept as secure as possible because it allows full access to the machine. This password is not often needed on a day-to-day basis, but is required to perform OV3600 upgrades and 20 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

21 advanced troubleshooting. If you lose this password, contact Alcatel-Lucent support for resetting instructions. Completing the Installation Upon completion of all previous steps, the following message appears. CONGRATULATIONS! OV3600 is configured properly. To access OV3600 web console, browse to Address> Login with the following credentials: Username: admin Password: admin To view the Phase 1 installation log file, type cat /root/install.log. To view the Phase 2 installation log file, type cat /tmp/amp-install.log. To access the OV3600 GUI, enter the OV3600 IP address in the address bar of any browser. The OV3600 GUI then prompts for your license key. If you are entering a dedicated Master Console or OV3600 Failover license, refer to Supporting OV3600 Servers with the Master Console on page 222 for additional information. Configuring and Mapping Port Usage for OV3600 The following diagram itemizes the communication protocols and ports necessary for OV3600 to communicate with wireless LAN infrastructure devices, including access points (APs), controllers, routers, switches, and RADIUS servers. Assign or adjust port usage on the network administration system as required to support these components. Table 4 OV3600 Protocol and Port Chart Port Type Protocol Description Direction Device Type 21 TCP FTP Firmware distribution > APs or controllers 22 TCP SSH Configure devices > APs or controllers 22 TCP SSH Configure OV3600 from CLI < Laptop or workstation 22 TCP VTUN Support connection (optional) > Alcatel-Lucent support home office 22 TCP SCP Transfer configuration files or FW < APs or controllers 23 TCP Telnet Configure devices > APs or controllers 23 TCP VTUN Support connection (Optional) > Alcatel-Lucent support home office 25 TCP SMTP Support (optional) > Alcatel-Lucent support server 49 UDP TACACS OV3600 Administrative Authentication > Cisco TACACS+ 53 UDP DNS DNS lookup from OV3600 > DNS Server 69 UDP TFTP Transfer configuration files or FW < APs or controllers 80 TCP HTTP Configure devices > Legacy APs 80 TCP VTUN Support connection (optional) > Alcatel-Lucent support home office 161 UDP SNMP Get and Set operations > APs or controllers 162 UDP SNMP Traps from devices < APs or controllers 162 UDP SNMP Traps from OV3600 > NMS OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 21

22 Table 4 OV3600 Protocol and Port Chart (Continued) Port Type Protocol Description Direction Device Type 443 TCP HTTPS Web management < Laptop or workstation 443 TCP HTTPS WLSE polling > WLSE 443 TCP VTUN Support connection (optional) > Alcatel-Lucent support home office 1701 TCP HTTPS AP and rogue discovery > WLSE 1741 TCP HTTP WLSE polling > WLSE 1812 UDP RADIUS Auth 1813 UDP RADIUS accounting Authenticate & authorize AMP administrative users on a RADIUS server. Retrieve usernames for authenticated WLAN clients from NAS (captive portal, controller, autonomous AP). Only used when usernames are not available in the SNMP MIB of a controller or autonomous AP. > RADIUS auth server 2002 TCP HTTPS Retrieve client authentication info > ACS < RADIUS accounting client 5050 UDP RTLS Real Time Location Feed < Alcatel-Lucent thin APs 8211 UDP PAPI Real Time Feed < > WLAN switches ICMP Ping Probe > APs or controllers OV3600 Navigation Basics Every OV3600 page contains the following three basic sections: Status Section Navigation Section Activity Section The OV3600 pages also contain Help links with GUI-specific help information and certain standard buttons. Status Section The Status section is a snapshot view of overall WLAN performance and provides direct links for immediate access to key system components. OV3600 includes the ability to customize the contents of the Status section from the Home > User Info page, to include support for both wireless and wired network components. Refer to Configuring Your Own User Information with the Home > User Info Page on page 214. Figure 1 Status section of the Home > Overview Page The table below describes these elements in further detail. Table 5 Status Section Components of the OV3600 GUI Field New Devices Up Description The number of wireless APs or wireless LAN controllers that have been discovered by OV3600 but not yet managed by network administrators. When selected, OV3600 directs you to a page that displays a detailed list of devices awaiting authorization. The number of managed authorized devices that are currently responding to OV3600 requests. When selected, OV3600 shows a detailed list of all Up devices. 22 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

23 Table 5 Status Section Components of the OV3600 GUI (Continued) Field Down Mismatched Rogue Clients Alerts Severe Alerts (conditional) Device Types to Include in Header Stats Search Description The number of managed, authorized devices that are not currently responding to OV3600 SNMP requests. When selected, OV3600 shows a detailed list of all Down devices. The total number of Mismatched devices. A device is considered mismatched when the desired configuration in OV3600 does not match the actual device configuration read from the device. The number of devices that have been classified by the RAPIDS rules engine above the threshold defined on the Home > User Info page. The number of wireless users currently associated to the wireless network via all the APs managed by OV3600. When selected, OV3600 shows a list of users that are associated. Prior to AMP 7.4, this was called Users. Displays the number of non-acknowledged OV3600 alerts generated by user-configured triggers. When selected, OV3600 shows a detailed list of active alerts. When triggers are given a severity of Critical, they generate Severe Alerts. When a Severe Alert exists, a new component appears at the right of the Status field in bold red font. Only users configured on the Home > User Info page to be enabled to view critical alerts can see Severe Alerts. The functionality of Severe Alerts is the same as that described above for Alerts. Unlike Alerts, the Severe Alerts section is hidden if there are no Severe Alerts. You can support statistics for any combination of the following device types: Autonomous APs Controllers Routers/Switches Thin APs Others Refer to Configuring Your Own User Information with the Home > User Info Page on page 214. In the Search field, you can perform partial string searches on a large number of fields including the notes, version, secondary version, radio serial number, device serial number, LAN MAC, radio MAC and apparent IP of all the APs as well as the client MAC, VPN user, LAN IP, VPN IP fields. Entering a search string displays search in two phases: Fast search results - display quickly and divide the results into Clients, APs, Controllers, and Switches, and shows only basic columns relevant to each search category Full search results - accessed by selecting the Click here to perform a Full Search to expand the results link at the top of the Fast search results. This action sends the earlier search term to a much deeper search of AMP, expanding the results to include all types of devices, clients (connected and historical), folders, groups, tags, rogue devices, VPN sessions (connected and historical), and rogue clients. You can customize search categories displayed in the Full search in Home > User Info. Navigation Section The Navigation Section displays tabs for all main GUI pages within OV3600. The top bar is a static navigation bar containing tabs for the main components of OV3600, while the lower bar is context-sensitive and displays the subtabs for the highlighted tab. Figure 2 Navigation section of the Home > Overview Page OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 23

24 The table below describes these elements in further detail.. Table 6 Components and Subtabs of the OV3600 Navigation Main Tab Description SubTabs Home Groups APs/Devices Clients The Home tab provides basic OV3600 information including system name, host name, IP address, current time, running time, and software version. The Home page also provides a central point for network status information and monitoring tools, giving graphical display of network activity, and links to many of the most frequent tools in OV3600. For additional information, refer to Monitoring and Supporting OV3600 with the Home Pages on page 210. The Groups pages provide information on the logical groups of devices that have been established for efficient monitoring and configuration. For additional information, see Configuring and Using Device Groups on page 71. Some of the focused subtabs will not appear for all groups. Focused subtabs are visible based on the device type field on the Groups > Basic page. This subtab is the first page to appear when adding or editing groups. NOTE: When individual device configurations are specified, device-level settings override the Group-level settings to which a device belongs. The APs/Devices pages provide detailed information about all authorized APs and wireless LAN switches or controllers on the network, including all configuration and current monitoring data. These pages interact with several additional pages in OV3600. Refer to Chapter 5, Discovering, Adding, and Managing Devices on page 107. NOTE: When specified, device-level settings override the default Group-level settings. The Clients pages provide detailed information about all client devices and users currently and historically associated to the WLAN, including VPN users. Prior to 7.4, this tab was called Users. For additional information, refer to Monitoring and Supporting WLAN Clients on page 198 Overview Search Documentation License User Info List Focused Subtabs: Monitor Basic Templates Security SSIDs AAA Servers Radio Alcatel-Lucent Config Cisco WLC Config PTMP Proxim Mesh MAC ACL Firmware Compare List New Up Down Mismatched Ignored Focused Subtabs: Monitor Manage Interfaces Audit Compliance Rogues Contained Connected All Rogue Clients Guest Users VPN Sessions VPN Users Tags Guest Users Subtabs: Client Detail Diagnostics VPN Users Subtab: VPN Client Detail 24 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

25 Table 6 Components and Subtabs of the OV3600 Navigation (Continued) Main Tab Description SubTabs Reports System Device Setup OV3600 Setup RAPIDS VisualRF The Reports pages list all the standard and custom reports generated by OV3600. For additional information, refer to Chapter 9, Creating, Running, and ing Reports on page 229. The System page provides information about OV3600 operation and administration, including overall system status, the job scheduler, trigger/alert administration, and so forth. For additional information, refer to Monitoring and Supporting OV3600 with the System Pages on page 185. The Device Setup pages provide the ability to add, configure, and monitor devices, to include setting AP discovery parameters, performing firmware management, defining VLANs, and so forth. For additional information, refer to Enabling OV3600 to Manage Your Devices on page 54. The OV3600 Setup pages provide all information relating to the configuration of OV3600 itself and its connection to your network. This page entails several processes, configurations, or tools in OV3600. For additional information, start with Chapter 3, Configuring OV3600 on page 31. NOTE: Some OV3600 Setup pages may not be visible depending on the role of the logged-in user set in OV3600. The RAPIDS pages provide all information relating to rogue access points, including methods of discovery and lists of discovered and possible rogues. For additional information, refer to Chapter 7, Using RAPIDS and Rogue Classification on page 169. NOTE: The RAPIDS pages may not be visible to the logged-in user, depending on their role set in OV3600. VisualRF pages provide graphical access to floor plans, client location, and RF visualization for floors, buildings, and campuses that host your network. Refer to Chapter 10, Using VisualRF on page 259. Generated Definition Definition Subtab: Detail Status Syslog & Traps Event Log Triggers Alerts Backups Configuration Change Jobs Firmware Upgrade Jobs Performance Discover Add Communication Alcatel-Lucent Configuration (if global Alcatel-Lucent Configuration is enabled) Upload Firmware & Files General Network Users Roles Guest Users Authentication MDM Server Device Type Setup WLSE ACS NMS RADIUS Accounting PCI Compliance Overview List IDS Events Setup Rules Score Override Audit Log Floor Plans Setup Import Audit Log The OV3600 Setup tab varies with user role. The RAPIDS and VisualRF tabs appear based on the license entered on the Home > License page, and might not be visible on your OV3600 view. OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 25

26 Activity Section The Activity section displays all detailed configuration and monitoring information, and is where you implement changes. Figure 3 Activity section of the Home>Overview Page Help Links in the UI The Help link is available on every page within OV3600. When selected, this launches the OmniVista 3600 Air Manager 7.4 User Guide PDF with information describing the OV3600 page that is currently displayed. Adobe Reader must be installed to view the settings and default values in the PDF help file. Common List Settings All of the lists in OV3600 have some common options. All lists are paginated with a configurable number of items per page. Selecting the Records Per Page dropdown menu (which usually looks like a range such as 1-20 on the upper left hand side of a list table) enables you select or enter the number of rows that appear at a time in the list. The next down arrow displays a dropdown menu that allows you to select the exact page you would like to view, as shown in Figure 4. The Choose Columns option, illustrated on Figure 4, allows you to configure the columns that are presented in the list and the order in which they are presented. To disable a column, clear its checkbox. To reorder the columns, drag a row to the appropriate new position. When you are satisfied with the enabled columns and their order, select Save at the top of the columns list. 26 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

27 Figure 4 Common List Settings Choose Columns Illustration These settings are user specific. To reset them, select Reset List Preferences on Home > User Info. Buttons and Icons Standard buttons and icons are used throughout OV3600 as follows: Table 7 Standard Buttons and Icons of the OV3600 User Page Function Image a Description Acknowledge Add Add Folder Alert Apply Audit Choose Clients Create Customize Delete Down Drag and Drop Duplicate Edit Filter (Funnel icon) Google Earth Ignore Import Manage Mismatched Monitor New Devices Poll Now Acknowledges and clears an OV3600 alert. Adds the object to both OV3600's database and the onscreen display list. Adds a new folder to hierarchically organize APs. Indicates an alert. Applies all saved configuration changes to devices on the WLAN. Reads device configuration, compare to desired, and update status. Chooses a new Helpdesk incident to be the Current Incident. Indicates WLAN users. Select this number to see a list of connected clients. Creates a new Helpdesk incident. Ignores selected settings when calculating the configuration status. Deletes an object from OV3600's database. Indicates Down devices and radios. Dragging and dropping objects with this icon changes the sequence of items in relation to each other. Refer to Using RAPIDS and Rogue Classification on page 169 as one example of drag-and-drop. Duplicates or makes a copy of the configuration of an OV3600 object. Edits the object properties. Links to reports. Filters list by values of the selected column. To reset all filters in all columns, click Reset filters link at the bottom of the table. Views device's location in Google Earth (requires plug-in). Ignores specific device(s) - devices selected with check boxes. Updates a Group's desired settings to match current settings. Manages the object properties. Indicates mismatched device configuration, in which the most recent configuration in OV3600 and the current configuration on a device are mismatched. Indicates an access point is in monitor only mode. Indicates new access points and devices. Polls device (or controller) immediately, override group polling settings. OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 27

28 Table 7 Standard Buttons and Icons of the OV3600 User Page (Continued) Function Image a Description Preview Print Reboot Refresh Relate Replace Hardware Revert Rogue Run Save Save & Apply Scan Schedule Search Set Time Range Up Update Firmware Usage View Historical Graph in New Window VisualRF XML Displays a preview of changes applicable to multiple groups. Prints the report. Reboots devices or OV3600. Refreshes the display of interactive graphs when settings have changed. Relates an AP, Group or Client to a Helpdesk incident. Confers configuration and history of one AP to a replacement device. Returns all configurable data on the screen to its original status. Indicates a rogue AP, and links to RAPIDS. Runs a new user-defined report. Saves the information on the page in the OV3600 database. Saves changes to OV3600 s database and apply all changes to devices. Scans for devices and rogues using selected networks. Schedules a window for reports, device changes, or maintenance. Searches OV3600 for the specified client, device, rogue, group, folder, tag, or session. Sets the time range for interactive graphs to the range specified. Indicates devices which are in the Up status. Applies a new firmware image to an AP/device. Displays current bandwidth. Displays all data series for the selected graph over the last two hours, last day, last week, last month, and last year in one new pop-up window. Links to VisualRF - real time visualization. Links to export XHTML versions of reports. a. Not all OV3600 GUI components are itemized in graphic format in this table. Getting Started with OV3600 This topic describes how to perform an initial launch of the OV3600 network management solution on the session-based authentication scheme introduced in OV When an OV3600 URL is accessed either interactively using a browser or programmatically using an API, a sent cookie may match a session stored in the database, granting authentication (but not necessarily access, depending on how the user s role matches the required role for the URL). If the cookie is not present or the session in the database has expired, the request is denied. For browser requests, this results in a login form being displayed. When you submit the login form, the supplied credentials are checked against the AMP s user database, an external RADIUS server, or external 28 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

29 TACACS+ server per the AMP s configuration. If the credentials are valid, the user s browser is sent a session cookie to use in subsequent requests. Use your browser to navigate to the static IP address assigned to the internal page of the OV3600, as shown in Figure 5. Enter the User Name and Password as admin/admin for your initial login, and then select Log In. Figure 5 OV3600 Login Form If desired, you can set one of the available languages for your login. OV3600 will remember your selected language until you log out and select another. After successful authentication, your browser launches the OV3600 Home > Overview page. OV3600 pages are protected via SSL. Some browsers will display a confirmation dialog for your self-signed certificate. Signing your certificate will prevent this dialog from displaying. Changing the default login and password on the OV3600 Setup > Users page is recommended. Refer to the procedure Creating OV3600 User Roles on page 47 for additional information. OmniVista 3600 Air Manager 7.4 User Guide Installing and Getting Started 29

30 30 Installing and Getting Started OmniVista 3600 Air Manager 7.4 User Guide

31 Chapter 3 Configuring OV3600 This chapter contains the following procedures to deploy initial OV3600 configuration: Formatting the Top Header on page 31 Customizing Columns in Lists on page 32 Resetting Pagination Records on page 33 Using the Pagination Widget on page 33 Using Export CSV for Lists and Reports on page 34 Defining Graph Display Preferences on page 34 Customizing the Dashboard on page 34 Customized Search on page 36 Setting Severe Alert Warning Behavior on page 36 Defining General OV3600 Server Settings on page 37 Defining OV3600 Network Settings on page 44 Creating OV3600 Users on page 45 Creating OV3600 User Roles on page 47 Configuring Login Message, TACACS+ and RADIUS Authentication on page 49 Enabling OV3600 to Manage Your Devices on page 54 Setting Up Device Types on page 59 Configuring Cisco WLSE and WLSE Rogue Scanning on page 59 Configuring ACS Servers on page 64 Integrating OV3600 with an Existing Network Management Solution (NMS) on page 65 Auditing PCI Compliance on the Network on page 66 Deploying WMS Offload on page 69 Additional configurations of multiple types are available after basic configuration is complete. Before You Begin Remember to complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. Formatting the Top Header The OmniVista 3600 Air Manager 7.4 interface centers around a horizontal row of tabs with nested subtabs. A row of statistics hyperlinks called Top Header Stats above the tabs represents commonly used subtabs. These hyperlinks provide the ability to view certain key statistics by mousing over, such as number and type of Down devices, and serve as shortcuts to frequently viewed subtabs. Figure 6 illustrates the navigation bar. For more details on hyperlinks, tabs and subtabs, see OV3600 Navigation Basics on page 22. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

32 Figure 6 Navigation Bar Displaying Down Device Statistics You can control which Top Header Stats links appear from the OV3600 Setup > General page, as described in Defining General OV3600 Server Settings on page 37. Top Header Stats can also be customized for individual user on the Home > User Info page. There you can select the statistics to display for certain device types, and override the OV3600 Setup page. All possible display options for users are shown in Figure 7, and these fields are described in detail in Configuring Your Own User Information with the Home > User Info Page on page 214. Figure 7 Home > User Info Top Header Stats Display Options You can also set the severity level of critical alerts displayed for a user role. For details including a description of what constitutes a severe alert, see Setting Severe Alert Warning Behavior on page 36. Customizing Columns in Lists Customize the columns for any list table selecting Choose Columns as shown in Figure 8. Use the up/down arrows to change the order in which the column heads appear. Figure 8 Choose Columns Dropdown List For more information on the universal list elements, see Common List Settings on page 26. You can also control which column heads appear for each user role by selecting Yes in the Customize Header Columns field in Home > User Info, as also appears in Figure 7. This exposes the Choose Columns for Roles dropdown menu in all tables shown in Figure 9. The first column shows the user roles that were customized, if any. The second column allows you to establish left to right columns and order them using the arrows. 32 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

33 Figure 9 Table With Choose Columns for Roles Menu Selected Resetting Pagination Records To control the number of records in any individual list, select the link with Records Per Page mouseover text at the top left of the table, as shown in Figure 10. OV3600 remembers each list table s pagination preferences. Figure 10 Records Per Page Drop Down Menu To reset all Records Per Page preferences, select Reset in the Display Preferences section of the Home > User Info page, as shown in Figure 11. Figure 11 Home > User Info Display Preferences section Using the Pagination Widget The pagination widget is located at the top and bottom of every list table, as shown in Figure 12. Figure 12 Pagination Widget Use the down arrow next to Page 1 to see all the page numbers for that table in a dropdown menu. From here, you can jump to any portion of the table. Select the > symbol to jump to the next page, and > to jump to the last page. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

34 Using Export CSV for Lists and Reports Some tables have a Export CSV setting you can use export the data as a spreadsheet. See Figure 13 for an example of a list with the Export CSV option selected. Figure 13 List with CSV Export Selected OV3600 also enables CSV exporting of all report types. For more information, see Exporting Reports to XML or CSV on page 258. Defining Graph Display Preferences Many of the graphs in OV3600 are Flash-based which allows you adjust the graph settings attributes, as shown in Figure 14. Figure 14 Interactive Graphs on the Home > Overview Page This Flash-enabled GUI allows for custom settings and adjustments, as follows: Drag the slider at the bottom of the screen to move the scope of the graph between one year ago and the current time. Drag the slider between graphs to change the relative sizes of each. Deselect checkboxes to change the data displayed on each graph. The button with green arrows refreshes data on the graph. The Show All link displays all of the available checkboxes supporting the Flash graphs. Once a change to the slider bars or to the display boxes has been made, the same change can be applied to all other Flash graphs with an apply button (appears on mouse-over only). For non-flash graphs, select the graph to open a popup window that shows historical data. A non-flash version of the OV3600 user page is available if desired; instead of Flash it uses the RRD graphs that were used in earlier versions of OV3600. Contact Alcatel-Lucent support for more information on activating this feature in the OV3600 database. Customizing the Dashboard You can rearrange or remove widgets appearing on the Home > Overview dashboard by selecting the Customize link to the right of this window, as shown in Figure 15. Figure 15 Customize Button on the Home > Overview Page 34 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

35 The Customize workspace that appears is shown in Figure 16. Figure 16 Customize Overview Page The Available Widgets section section on the left with no gridlines holds all possible (available) graphical elements (widgets). Select any blue widget tile with a verbal description enclosed, and it immediately turns into a graphical element with a description. Drag the widgets you want to appear on the Overview dashboard across to the gridlines and arrange them in the right section, within the gridlines. A widget snaps back to the nearest available gridline if you drop it across two or more lines, and turns red if you attempt to place it over gridlines already occupied by widgets. Green widgets are properly placed and set to appear when you select Save. Widgets that remain in the left section will not appear (although they can be reinstated by selecting Restore Defaults). OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

36 Customized Search You can customize the Full search results to display only desired categories of matches on the Home > User Info page. Go to the Search Preferences section and select Yes in the Customize Search field, then select or unselect categories of results and save your changes. Customized search is turned off by default, and all boxes are selected. Figure 17 Home > User Info Customized Search Preferences Setting Severe Alert Warning Behavior You can control the alert levels you can see on the Alerts top header stats link from the Home > User Info page. When a trigger is assigned a severity of Critical, it generates a severe alert. When a severe alert exists, a new component named Severe Alerts appears at the right of the Status field in bold red font. Only users who are enabled for viewing critical alerts on the Home > User Info page can see severe alerts. The Severe Alert Threshold dropdown menu, located in the Top Header Stats section of the Home > User Info page is shown in Figure 18. Figure 18 Home > User Info > Severe Alert Threshold Dropdown Menu 36 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

37 Defining General OV3600 Server Settings This section describes all pages accessed from the OV3600 Setup tab and describes two pages in the Device Setup tab, the Communication and Upload Files pages. Once required and optional configuration tasks in this chapter are complete, continue to later chapters in this document to create and deploy device groups and device configuration and discovery on the network. The first step in configuring OV3600 is to specify the general settings for the OV3600 server. Figure 19 illustrates the OV3600 Setup > General page: Figure 19 OV3600 Setup > General Page Illustration (Partial View) Perform the following steps to configure OV3600 server settings globally across the product (for all users). 1. Browse to the OV3600 Setup > General page, locate the General section, and enter the information described in Table 8: Table 8 OV3600 Setup > General > General Section Fields and Default Values Setting Default Description System Name Defines your name for the OV3600 server, with a maximum limit of 20 alphanumeric characters. Automatically monitor/manage new devices Default Group Device Configuration Audit Interval Automatically repair misconfigured devices Send debugging messages No Access Points Daily Disabled Enabled Launches a drop-down menu that specifies the behavior OV3600 should follow when it discovers a new device. Devices are placed in the default group which is defined in the next field. Choose one of these options: Monitor Only: OV3600 compares the current configuration with the policy, and displays any discrepancies on the APs/Devices > Audit page, but does not change the configuration of the device. Manage Read/Write: OV3600 compares the device's current configuration settings with the Group configuration settings and automatically updates the device's configuration to match the Group policy. Automatically placing devices in Managed Read/Write mode will overwrite the configuration with the desired configuration in OV3600, and should only be used when you are certain OV3600 has the correct configuration. This can be risky, and generally, devices should be placed in Monitor Only mode as the default. Thin APs Only: Only thin APs will be automatically authorized in Monitor Only mode. This setting is ideal for mixed environments of thin and autonomous APs, or for very large subnets in which you don t want to auto-monitor all switches. Sets the device group that this OV3600 server uses as the default for device-level configuration. Select a device group from the drop-down menu. A group must first be defined on the Groups > List page to appear in this drop-down menu. For additional information, refer to Chapter 4, Configuring and Using Device Groups on page 71. If enabled, this setting defines the interval of queries which compares actual device settings to the Group configuration policies stored in the OV3600 database. If the settings do not match, the AP is flagged as mismatched and OV3600 sends an alert via , log, or SNMP. NOTE: Enabling this feature with a frequency of Daily or more frequently is recommended to ensure that your AP configurations comply with your established policies. If enabled, this setting automatically reconfigures the settings on the device when the device is in Manage mode and OV3600 detects a variance between actual device settings and the Group configuration policy in the OV3600 database. If enabled, OV3600 automatically s any system errors to Alcatel-Lucent Support to assist in debugging. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

38 Table 8 OV3600 Setup > General > General Section Fields and Default Values (Continued) Setting Default Description Nightly Maintenance Time (00:00-23:59) Check for software updates 04:15 Specifies the local time of day OV3600 should perform daily maintenance. During maintenance, OV3600 cleans the database, performs backups, and completes a few other housekeeping tasks. Such processes should not be performed during peak hours of demand. Yes Enables OV3600 to check automatically for multiple update types. Check daily for OV3600 updates, to include enhancements, device template files, important security updates, and other important news. This setting requires a direct internet connection via OV On the OV3600 Setup > General page, locate the Automatic Authorization section. These settings allow you to control the conditions by which devices are automatically authorized into AP groups and folders. AMP validates the Folder and Group to ensure that both settings have been set to valid dropdown options. Table 9 describes the settings and default values in this section. Table 9 OV3600 Setup > General > Automatic Authorization Fields and Default Values Setting Default Description Add New Controllers and Autonomous Devices Location Add New Thin APs Location New Device List New Device List Globally add new controllers and autonomous devices to: The New Devices list (located in APs/Devices > New). The same folder and group as the discovering device. The same group and folder of their closest IP neighbor on the same subnet. Choose a group and folder. If you select this option, enter the folder/ group in the Auto Authorization Group and Auto Authorization Folder fields that display. NOTE: This setting can be overridden in Groups > Basic. Globally add new thin APs to: The New Devices list. The same folder and group as the discovering device. The same group and folder of their closest IP neighbor on the same subnet. Choose a group and folder. If you select this option, enter the folder/ group in the Auto Authorization Group and Auto Authorization Folder fields that display. NOTE: This setting can be overridden in Groups > Basic. 3. On the OV3600 Setup > General page, locate the Top Header section to select the Top Header Stats to be displayed at the top of the interface. For more detailed information about each option, refer to Table 5 on page On the OV3600 Setup > General page, locate the Search Preferences section. Select the search categories to include in a Full search of AMP such APs/devices, clients (connected and/or historical), VPN sessions (connected and/or historical), rogues, rogue clients, tags, folders, and groups. All are selected by default. Per-user search preferences can be set in the Home > User Info page; refer to Customized Search on page On the OV3600 Setup > General page, locate the Home Overview Preferences section. Table 11 describes the settings and default values in this section. Table 10 OV3600 Setup > General > Home Overview Preferences Fields and Default Values Setting Default Description Configure Channel Busy Threshold Channel Busy Threshold (%) Yes Whether you want to configure the threshold at which a channel is considered to be busy at the Top Folders By Radio Channel Usage Overview widget. 10 The threshold percent at which the radio channel is considered busier than normal. 38 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

39 6. On the OV3600 Setup > General page, locate the Display section and select the Group tabs and options to appear by default in new device groups. Changes to this section apply across all of OV3600. These changes affect all users and all new device groups. Table 11 describes the settings and default values in this section. Table 11 OV3600 Setup > General > Display Fields and Default Values Setting Default Description Use fully qualified domain names Show vendorspecific device settings for Look up wireless user hostnames DNS Hostname Lifetime Device Troubleshooting Hint No All Devices Yes Sets OV3600 to use fully qualified domain names for APs instead of the AP name. For example, "testap.yourdomain.com" would be used instead of "testap." This option is supported only for Cisco IOS, Dell PowerConnect W, Aruba Networks, and Alcatel-Lucent devices. Displays a drop-down menu that determines which Group tabs and options are viewable by default in new groups, and selects the device types that use fully qualified domain names. This field has three options, as follows: All devices When selected, OV3600 displays all Group tabs and setting options. Only devices on this OV3600 When selected, OV3600 hides all options and tabs that do not apply to the APs and devices currently on OV3600. Selected device type When selected, a new field appears listing many device types. This option allows you to specify the device types for which OV3600 displays group settings. You can override this setting. Enables OV3600 to look up the DNS for new user hostnames. This setting can be turned off to troubleshoot performance issues. 24 hours Defines the length of time, in hours, for which a DNS server hostname remains valid on OV3600, after which OV3600 refreshes DNS lookup: 1 hour 2 hours 4 hours 12 hours 24 hours N/A The message included in this field is displayed along with the Down if a device s upstream device is up. This applies to all APs and controllers but not to routers and switches. 7. Locate the Device Configuration section and adjust the settings. Table 12 describes the settings and default values of this section. Table 12 OV3600 Setup > General > Device Configuration Section Fields and Default Values Setting Default Description Guest User Configuration Allow WMS Offload configuration in monitor-only mode Allow disconnecting users while in monitor-only mode Allow non-utf8 characters Disabled No No No Enables or prevents guest users to/from pushing configurations to devices. Options are Disabled (default), Enabled for Devices in Manage (Read/ Write), Enabled for all Devices. When Yes is selected, you can enable the AOS-W WMS offload feature on the Groups > Basic page for WLAN switches in Monitor Only mode. Enabling WMS offload does not cause a controller to reboot. This option is supported only for Alcatel-Lucent and Dell PowerConnect W-Series devices. Sets whether you can deauthenticate a user for a device in monitor-only mode. If set to No, the Deauthenticate Client button for in a Clients > Client Detail page is enabled only for Managed devices. Whether AMP can use character sets other than UTF-8 for configuration settings. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

40 Table 12 OV3600 Setup > General > Device Configuration Section Fields and Default Values (Continued) Setting Default Description Use Global Configuration Yes Enables Alcatel-Lucent configuration profile settings to be globally configured and then assigned to device groups. If disabled, settings can be defined entirely within Groups > Alcatel-Lucent Config instead of globally. NOTE: Changing this setting may require importing configuration on your devices. When an existing Alcatel-Lucent configuration setup is to be converted from global to group, follow these steps: 1. Set all the devices to Monitor Only mode before setting the flag. 2. Each device Group will need to have an import performed from the Audit page of a controller in the AMP group. 3. All of the thin APs need to have their settings imported after the device group settings have finished importing. 4. If the devices were set to Monitor Only mode, set them back to Managed mode. 5. Locate the AMP Features section and adjust settings to enable or disable VisualRF and RAPIDS. Table 13 describes these settings and default values. Table 13 OV3600 Setup > General > AMP Features Fields and Default Values Setting Default Description Display VisualRF No Enable or disable the VisualRF navigation tab. Display RAPIDS No Enable or disable the RAPIDS navigation tab. Hide setup pages from non-admin users Allow role based report visibility Yes Yes Restrict access to following pages to users with the AMP Administration role only: VisualRF > Setup OV3600 Setup > NMS RAPIDS > Score Override RAPIDS > Rules RAPIDS > Setup System > Triggers Enable or disable role-based reporting in AMP. When disabled, reports can only be generated with by-subject visibility. 6. Locate the External Logging section and adjust settings to send audit and system events to an external syslog server. Table 14 describes these settings and default values. You can send a test message using the Send Test Message button once any of the logging options are enabled. Table 14 OV3600 Setup > General > External Logging Section Fields and Default Values Setting Default Description Include event log messages No Select Yes to send event log messages to an external syslog server. Syslog Server N/A Enter the IP address of the syslog server. Syslog Port 514 Enter the port of the syslog server. Event log facility local1 Select the facility for the event log from the drop-down menu. Include audit log messages No Select Yes to send audit log messages to an external syslog server. Audit log facility local1 Select the facility for the audit log from the drop-down menu. 40 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

41 7. Locate the Historical Data Retention section and specify the number of days you wish to keep client session records and rogue discovery events. Table 15 describes the settings and default values of this section. Many settings can be set to have no expiration date. Table 15 OV3600 Setup > General > Historical Data Retention Fields and Default Values Setting Default Description Inactive Client and VPN User Data ( days, zero disables) Client Association and VPN Session History (2-550 days) Tag History (2-550 days) Rogue AP Discovery Events (2-550 days) Reports (2-550 days) Automatically Acknowledge Alerts (0-550 days, zero disables) Acknowledged Alerts (2-550 days) Radius/ARM/IDS Events (0-550 days, zero disables) Archive device configs even if they only have rogue classifications (1-100) Guest Users (0-550 days, zero disables) Inactive SSIDs (0-550 days, zero disables) Inactive Interfaces (0-550 days, zero disables) Interface Status History (0-550 days, zero disables) Interfering Devices (0-550 days, zero disables) Device Events (Syslog, Traps) 60 Defines the number of days OV3600 stores basic information about inactive clients and VPN users. A shorter setting of 60 days is recommended for customers with high user turnover such as hotels. The longer you store inactive user data, the more hard disk space you require. 14 Defines the number of days OV3600 stores client and VPN session records. The longer you store client session records, the more hard disk space you require. 14 Sets the number of days OV3600 retains location history for Wi-Fi tags. 14 Defines the number of days OV3600 stores Rogue Discovery Events. The longer you store discovery event records, the more hard disk space you require. 60 Defines the number of days OV3600 stores Reports. Large numbers of reports, over 1000, can cause the Reports > Generated page to be slow to respond. 14 Defines automatically acknowledged alerts as the number of days OV3600 retains alerts that have been automatically acknowledged. Setting this value to 0 disables this function, and alerts will never expire or be deleted from the database. 60 Defines the number of days OV3600 retains information about acknowledged alerts. Large numbers of Alerts, over 2000, can cause the System > Alerts page to be slow to respond. 14 Defines the number of days OV3600 retains information about RADIUS, ARM, and IDS events. Setting this value to 0 disables this function, and the information will never expire or be deleted from the database. No Sets whether to archive device configurations even if the device only has rogue classifications. 30 Sets the number of days that OV3600 is to support any guest user. A value of 0 disables this function, and guest users will never expire or be deleted from the OV3600 database. 425 Sets the number of days OV3600 retains historical information after OV3600 last saw a client on a specific SSID. Setting this value to 0 disables this function, and inactive SSIDs will never expire or be deleted from the database. 425 Sets the number of days OV3600 retains inactive interface information after the interface has been removed or deleted from the device. Setting this value to 0 disables this function, and inactive interface information will never expire or be deleted from the database. 425 Sets the number of days OV3600 retains historical information on interface status. Setting this value to 0 disables this function. 14 Sets the number of days OV3600 retains historical information on interfering devices. Setting this value to 0 disables this function. 2 Sets the number of days OV3600 retains historical information on device events such as syslog entries and SNMP traps. Setting this value to 0 disables this function. Refer to Viewing Device Events in System > Syslog & Traps on page 187. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

42 Table 15 OV3600 Setup > General > Historical Data Retention Fields and Default Values (Continued) Setting Default Description Device Uptime (0-120 months, zero disables) 60 Sets the number of months OV3600 retains historical information on device uptime. Setting this value to 0 disables this function. 8. Locate the Firmware Upgrade Defaults section and adjust settings as required. This section allows you to configure the default firmware upgrade behavior for OV3600. Table 16 describes the settings and default values of this section. Table 16 OV3600 Setup > General > Firmware Upgrade Defaults Fields and Default Values Setting Default Description Allow firmware upgrades in monitor-only mode Simultaneous Jobs (1-20) Simultaneous Devices Per Job (1-1000) Failures before stopping (0-20) No If Yes is selected, OV3600 upgrades the firmware for APs in Monitor Only mode. When OV3600 upgrades the firmware in this mode, the desired configuration are not be pushed to OV3600. Only the firmware is applied. The firmware upgrade may result in configuration changes. OV3600 does not correct those changes when the AP is in Monitor Only mode. 20 Defines the number of jobs OV3600 runs at the same time. A job can include multiple APs. 20 Defines the number of devices that can be in the process of upgrading at the same time. OV3600 only runs one TFTP transfer at a time. As soon as the transfer to a device has completed, the next transfer begins, even if the first device is still in the process of rebooting or verifying configuration. 1 Sets the default number of upgrade failures before OV3600 pauses the upgrade process. User intervention is required to resume the upgrade process. Setting this value to 0 disables this function. 9. Locate the Additional OV3600 Services section, and adjust settings as required. Table 17 describes the settings and default values of this section. Table 17 OV3600 Setup > General > Additional OV3600 Services Fields and Default Values Setting Default Description Enable FTP Server No Enables or disables the FTP server on OV3600. The FTP server is only used to manage Cisco Aironet 4800 APs. Best practices is to disable the FTP server if you do not have any Cisco Aironet 4800 APs in the network. Enable RTLS Collector Use embedded mail server Process user roaming traps from Cisco WLC No Yes Yes Enables or disables the RTLS Collector, which is used to allow AOS-W switches to send signed and encrypted RTLS (real time locating system) packets to VisualRF-- in other words, OV3600 becomes the acting RTLS server. The RTLS server IP address must be configured on each switch. This function is used for VisualRF to improve location accuracy and to locate chirping asset tags. This function is supported only for Dell PowerConnect W, Alcatel-Lucent and Aruba Networks devices. With selection of Yes, the following additional fields appear, which you should populate to match the settings configured on the switch: RTLS Port Specify the port for the OV3600 RTLS server. RTLS Username Enter the user name used by the switch to decode RTLS messages. RTLS Password Enter the RTLS server password that matches the switches value. Enables or disables the embedded mail server that is included with OV3600.This field supports a Send Test button for testing server functionality. This button prompts you with a To and From field in which you must enter valid addresses, and a button to send a test . Whether OV3600 should parse client association and authentication traps from Cisco WLC controllers to give real time information on users connected to the wireless network. 42 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

43 Table 17 OV3600 Setup > General > Additional OV3600 Services Fields and Default Values (Continued) Setting Default Description Enable AMON data collection Yes Allows OV3600 to collect enhanced data from Alcatel-Lucent devices on certain firmware versions; see the Best Practices Guide in Home > Documentation for more details. 10. Locate the Performance section. Performance tuning is unlikely to be necessary for many OV3600 implementations, and likely provides the most improvements for customers with extremely large Pro or Enterprise installations. Please contact Alcatel-Lucent support if you think you might need to change any of these settings. Table 18 describes the settings and default values of this section. Table 18 OV3600 Setup > General > Performance Fields and Default Values Setting Default Description Monitoring Processes Maximum number of configuration processes Maximum number of audit processes Verbose Logging of SNMP Configuration SNMP Rate Limiting for Monitored Devices RAPIDS Processing Priority Based on the number of cores for your server Optional setting configures the throughput of monitoring data. Increasing this setting allows OV3600 to process more data per second, but it can take resources away from other OV3600 processes. Contact Alcatel-Lucent support if you think you might need to increase this setting for your network. 5 Increases the number of processes that are pushing configurations to your devices, as an option. The optimal setting for your network depends on the resources available, especially RAM. Contact Alcatel-Lucent support if you think you might need to increase this setting for your network. 3 Increases the number of processes that audit configurations for your devices, as an option. The optimal setting for your network depends on the resources available, especially RAM. Contact Alcatel-Lucent support if you are considering increasing this setting for your network. No No Low Enables or disables logging detailed records of SNMP configuration information. When enabled, OV3600 fetches SNMP data more slowly, potentially reducing device CPU load. Alcatel-Lucent recommends enabling this global setting when monitoring Alcatel-Lucent switches only if your network contains a majority of legacy switches. If your network mainly uses newer switches ( OAW-4306 Series, or the OAW-S3 module in the OAW-6000 series), Alcatel-Lucent strongly recommends disabling this setting. Defines the processing and system resource priority for RAPIDS in relation to OV3600 as a whole. When OV3600 is processing data at or near its maximum capacity, reducing the priority of RAPIDS can ensure that processing of other data (such as client connections and bandwidth usage) is not adversely impacted. The default priority is Low. You can also tune your system performance by changing group poll periods. 11. Select Save when the General Server settings are complete and whenever making subsequent changes. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

44 Defining OV3600 Network Settings The next step in configuring OV3600 is to confirm the OV3600 network settings. Define these settings by navigating to the OV3600 Setup > Network page. Figure 20 illustrates the contents of this page. Figure 20 OV3600 Setup > Network Page Illustration Perform the following steps to define the OV3600 network settings: 1. Locate the Primary and Secondary Network Interface sections. The information in these sections should match what you defined during initial network configuration and should not require changes. Table 19 describes the settings and default values. Table 19 Primary and Secondary Network Interface Fields and Default Values Setting Default Description IP Address None Sets the IP address of the OV3600 network interface. NOTE: This address must be a static IP address. Hostname None Sets the DNS name assigned to the OV3600 server. Subnet Mask None Sets the subnet mask for the primary network interface. Gateway None Sets the default gateway for the network interface. Primary DNS IP None Sets the primary DNS IP address for the network interface. Secondary DNS IP None Sets the secondary DNS IP address for the network interface. Secondary Network Interface No Select Yes to enable a secondary network interface. You must also define the IP address and subnet mask. 2. On the OV3600 Setup > Network page, locate the Network Time Protocol (NTP) section. The Network Time Protocol is used to synchronize the time between OV3600 and your network reference NTP server. NTP servers synchronize with external reference time sources, such as satellites, radios, or modems. Specifying NTP servers is optional. NTP servers synchronize the time on the OV3600 server, not on individual access points. To disable NTP services, clear both the Primary and Secondary NTP server fields. Any problem related to communication between OV3600 and the NTP servers creates an entry in the event log. Table 20 describes the settings and default values in more detail. For more information on ensuring that OV3600 servers have the correct time, please see Table 20 OV3600 Setup > Network > Secondary Network Fields and Default Values Setting Default Description Primary ntp1.yourdomain.com Sets the IP address or DNS name for the primary NTP server. Secondary ntp2.yourdomain.com Sets the IP address or DNS name for the secondary NTP server. 44 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

45 3. On the OV3600 Setup > Network page, locate the Static Routes area. This section displays network, subnet mask, and gateway settings that you have defined elsewhere from a command-line interface. This section does not enable you to configure new routes or remove existing routes. 4. Select Save when you have completed all changes on the OV3600 Setup > Network page, or select Revert to return to the last settings. Save restarts any affected services and may temporarily disrupt your network connection. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 configuration. Creating OV3600 Users OV3600 installs with only one OV3600 user the admin, who is authorized to: define additional users with varying levels of privilege, be it manage read/write or monitoring. limit the viewable devices as well as the level of access a user has to the devices. Each general user that you add needs a Username, a Password, and a Role. Use unique and meaningful user names as they are recorded in the log files when you or other users make changes in OV3600. Username and password are not required if you configure OV3600 to use RADIUS or TACACS authentication. You do not need to add individual users to the OV3600 server if you use RADIUS or TACACS authentication. The user role defines the user type, access level, and the top folder for that user. User roles are defined on the OV3600 Setup > Roles page. Refer to the next procedure in this chapter for additional information, Creating OV3600 User Roles on page 47. The admin user can provide optional additional information about the user including the user's real name, address, phone number, and so forth. Perform the following steps to display, add, edit, or delete OV3600 users of any privilege level. You must be an admin user to complete these steps. 1. Go to the OV3600 Setup > Users page. This page displays all users currently configured in OV3600. Figure 21 illustrates the contents and layout of this page. Figure 21 OV3600 Setup > Users Page Illustration OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

46 2. Select Add to create a new user, select the pencil icon to edit an existing user, or select a user and select Delete to remove that user from OV3600. When you select Add or the edit icon, the Add User page appears, illustrated in Figure 22. Figure 22 OV3600 Setup > Users > Add/Edit User Page Illustration 3. Enter or edit the settings on this page. Table 21 describes these settings in additional detail. Table 21 OV3600 Setup > Users > Add/Edit User Fields and Default Values Setting Default Description Username None Sets the username as an alphanumeric string. The Username is used when logging in to OV3600 and appears in OV3600 log files. Role None Specifies the User Role that defines the Top viewable folder, type and access level of the user specified in the previous field. The admin user defines user roles on the OV3600 Setup > Roles page, and each user in the system is assigned to a role. Password None Sets the password for the user being created or edited. Enter an alphanumeric string without spaces, and enter the password again in the Confirm Password field. NOTE: Because the default user's password is identical to the name, it is strongly recommended that you change this password. Name None Allows you to define an optional and alphanumeric text field that takes note of the user's actual name. Address None Allows you to specify a specific address that will propagate throughout many additional pages in OV3600 for that user, including reports, triggers, and alerts. Phone None Allows you to enter an optional phone number for the user. Notes None Enables you to cite any additional notes about the user, including the reason they were granted access, the user's department, or job title. 4. Select Add to create the new user, Save to retain changes to an existing user, or Cancel to cancel out of this screen. The user information you have configured appears on the OV3600 Setup > Users page and the user propagates to all other OV3600 pages and relevant functions. OV3600 enables user roles to be created with access to folders within multiple branches of the overall hierarchy. This feature assists non-administrator users who support a subset of accounts or sites within a single OV3600 deployment, such as help desk or IT staff. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. 46 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

47 Creating OV3600 User Roles The OV3600 Setup > Roles page defines the viewable devices, the operations that can be performed on devices, and general OV3600 access. VisualRF uses the same user roles as defined for OV3600 users can see floor plans that contain an AP to which they have access in OV3600, although only visible APs appear on the floor plan. Users can also see any building that contains a visible floor plan, and any campus that contains a visible building. In VisualRF > Setup > Server Settings, a new flag added in OV allows you to restrict the visibility of empty floor plans to the role of the user who created them. In previous versions, a floor plan without APs could be visible to all users. By default, this setting is set to No. When a new role is added to OV3600, VisualRF must be restarted for the new user to be enabled. Refer to Chapter 10, Using VisualRF on page 259 for additional information. User roles can be created that have access to folders within multiple branches of the overall hierarchy. This feature assists non-administrative users, such as help desk or IT staff, who support a subset of accounts or sites within a single OV3600 deployment. You can restrict user roles to multiple folders within the overall hierarchy even if they do not share the same top-level folder. Non-admin users are only able to see data and users for devices within their assigned subset of folders. Perform the following steps to view, add, edit, or delete user roles: 1. Go to the OV3600 Setup > Roles page. This page displays all roles currently configured in OV3600. Figure 23 illustrates the contents and layout of this page. Figure 23 OV3600 Setup > Roles Page Illustration OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

48 2. Select Add to create a new role, select the pencil icon to edit an existing role, or select a checkbox and select Delete to remove that role from OV3600. When you select Add or the edit icon, the Add/Edit Role page appears, illustrated in Figure 24. Figure 24 OV3600 Setup > Roles > Add/Edit Role Page Illustration 3. Enter or edit the settings on this page. Table 22 describes these settings in additional detail. As explained earlier in this section, Roles define the type of user-level access, the user-level privileges, and the view available to the user for device groups and devices in OV3600. Table 22 describes the settings and default values of this section. Table 22 OV3600 Setup > Roles > Add/Edit Roles Fields and Default Values Setting Default Description Name None Sets the administrator-definable string that names the role. The role name should indicate the devices and groups that are viewable, as well as the privileges granted to that role. Enabled Yes Disables or enables the role. Disabling a role prevents all users of that role from logging in to OV3600. Type AP/Device Access Level AP/Device Manager None Defines the type of role. OV3600 supports the following role types: OV3600 Administrator The OV3600 Administrator has full access to OV3600 and all of the devices. Only the OV3600 Administrator can create new users or access the OV3600 Setup page, the VisualRF > Setup page, VisualRF > Audit Log page, System > AMP Events, and System > Performance. AP/Device Manager AP/Device Managers have access to a limited number of devices and groups based on the Top folder and varying levels of control based on the Access Level. Guest Access Sponsor Limited-functionality role to allow helpdesk or reception desk staff to grant wireless access to temporary personnel. This role only has access to the defined top folder of APs. Defines the privileges the role has over the viewable APs. OV3600 supports three privilege levels, as follows: Manage (Read/Write) Manage users can view and modify devices and Groups. Selecting this option causes a new field, Allow authorization of APs/Devices, to appear on the page, and is enabled by default. Audit (Read Only) Audit users have read only access to the viewable devices and Groups. Audit users have access to the APs/Devices > Audit page, which may contain sensitive information including AP passwords. Monitor (Read Only) Monitor users have read-only access to devices and groups and VisualRF. Monitor users cannot view the APs/Devices > Audit page which may contain sensitive information, including passwords. 48 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

49 Table 22 OV3600 Setup > Roles > Add/Edit Roles Fields and Default Values (Continued) Setting Default Description Top Folder None Defines the Top viewable folder for the role. The role is able to view all devices and groups contained by the Top folder. The top folder and its subfolders must contain all of the devices in any of the groups it can view. NOTE: OV3600 enables user roles to be created with access to folders within multiple branches of the overall hierarchy. This feature assists non-administrator users who support a subset of accounts or sites within a single OV3600 deployment, such as help desk or IT staff. User roles can be restricted to multiple folders within the overall hierarchy, even if they do not share the same top-level folder. Non-administrator users are only able to see data and users for devices within their assigned subset of folders. RAPIDS None Sets the RAPIDS privileges, which are set separately from the APs/Devices. This field specifies the RAPIDS privileges for the role, and options are as follows: None Cannot view the RAPIDS tab or any Rogue APs. Read Only The user can view the RAPIDS pages but cannot make any changes to rogue APs or perform OS scans. Read/Write The user may edit individual rogues, classification, threat levels and notes, and perform OS scans. Administrator Has the same privileges as the Read/Write user, but can also set up RAPIDS rules, override scores, and is the only user who can access the RAPIDS > Setup page. VisualRF None Sets the VisualRF privileges, which are set separately from the APs/Devices, for this role. Options are as follows: Read Only The user can view the VisualRF pages but cannot make any changes to floor plans. Read/Write The user may edit individual floor plans, buildings, and campuses. Alcatel-Luc ent Controller Role Display client diagnostics screens by default No No Enables or disables Single Sign-On for the role. If enabled, allows the role to directly access Alcatel-Lucent controller UIs from the Quick Links or IP Address hypertext throughout AMP without having to enter credentials for the controller. Sets the role to support helpdesk users, with parameters that are specific to the needs of helpdesk personnel supporting users on a wireless network. Enable Adobe Flash Allow creation of Guest Users Yes Enables the Adobe Flash application for all users who are assigned this role. Adobe Flash supports interactive graphics on the Home > Overview page, VisualRF, QuickView functions, the Radio Statistics page for thin AP radios, and additional OV3600 pages. NOTE: This field is only visible if a specific flag is set in the OV3600 database. By default this option is hidden and Flash is enabled for all users. Yes If this option is enabled, users with an assigned role of Monitoring or Audit can be given access to guest user account creation along with the option to allow a sponsor to change its username. A custom message can also be included. The Guest User Preferences section does not appear if Guest User Configuration is disabled in OV3600 Setup > General. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 configuration. Configuring Login Message, TACACS+ and RADIUS Authentication AMP uses session-based authentication with a configurable login message and idle timeout. As an option, you can set OV3600 to use an external user database to simplify password management for OV3600 OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

50 administrators and users. This section contains the following procedures to be followed in OV3600 Setup > Authentication: Setting Up Login Configuration Options Setting Up Login Configuration Options Configuring RADIUS Authentication and Authorization Integrating a RADIUS Accounting Server Setting Up Login Configuration Options Administrators can optionally configure AMP s user idle timeout or a message-of-the-day that appears when a user first logs in, as shown in Figure 25: Figure 25 Login configuration field and results in AMP Login page 1. Go to OV3600 Setup > Authentication. 2. Complete the fields described on Table 23: Table 23 Login Configuration section of OV3600 Setup > Authentication Field Default Description Max AMP User Idle Timeout Login message 60 Number of minutes of idle time until AMP automatically ends the user session. Affects all users of this AMP. The range is minutes. A persistent message that will appear for all of this AMP s users after they log in. 3. Select Save if you are finished, or you can follow the next procedure to configure Single Sign-On, TACACS+ and RADIUS Authentication options. Setting up Single Sign-On Administrators can set up single sign-on (SSO) for users that have access to Alcatel-Lucent controllers. This allows users to log in to an AMP and use the IP Address or Quick Links hypertext links across AMP to access the controller s UI, without having to enter credentials again. The links the user can select to access a controller can be found on the APs/Devices > Monitor page in the Device Info section, and on device list pages. This feature must be enabled per role in OV3600 Setup > Roles. To enable this feature for this AMP, locate the Single Sign-On section in OV3600 Setup > Authentication. In the Enable Single Sign-On field, select Yes. Then select Save if you are finished, or you can follow the next procedure to configure TACACS+ and RADIUS Authentication options. 50 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

51 Configuring TACACS+ Authentication For TACACS+ capability, you must configure the IP/Hostname of the TACACS+ server, the TCP port, and the server shared secret. This TACACS+ configuration is for OV3600 users, and does not affect APs or users logging into APs. 1. Go to the OV3600 Setup > Authentication page. This page displays current status of TACACS+. Figure 26 illustrates this page when neither TACACS+ nor RADIUS authentication is enabled in OV3600. Figure 26 TACACS+ section OV3600 Setup > Authentication 2. Select No to disable or Yes to enable TACACS+ authentication. If you select Yes, several new fields appear. Complete the fields described in Table 24. Table 24 OV3600 Setup > Authentication Fields and Default Values Field Default Description Primary Server Hostname/IP Address N/A Enter the IP address or the hostname of the primary TACACS+ server. Primary Server Port 49 Enter the port for the primary TACACS+ server. Primary Server Secret N/A Specify and confirm the primary shared secret for the primary TACACS+ server. Secondary Server Hostname/ IP Address N/A Enter the IP address or hostname of the secondary TACACS+ server. Secondary Server Port 49 Enter the port for the secondary TACACS+ server. Secondary Server Secret N/A Enter the shared secret for the secondary TACACS+ server. 3. Select Save and continue with additional steps. 4. To configure Cisco ACS to work with OV3600, you must define a new service named OV3600 that uses https on the ACS server. The OV3600 https service is added to the TACACS+ (Cisco) interface under the Interface Configuration tab. Select a checkbox for a new service. Enter OV3600 in the service column and https in the protocol column. Select Save. 5. Edit the existing groups or users in TACACS to use the OV3600 service and define a role for the group or user. The role defined on the Group Setup page in ACS must match the exact name of the role defined on the OV3600 Setup > Roles page. The defined role should use the following format: role=<name_of_ov3600_role>. One example is as follows: role=dormmonitoring As with routers and switches, OV3600 does not need to know usernames. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

52 6. OV3600 also needs to be configured as an AAA client. On the Network Configuration page, select Add Entry. Enter the IP address of OV3600 as the AAA Client IP Address. The secret should be the same value that was entered on the OV3600 Setup > TACACS+ page. 7. Select TACACS+ (Cisco IOS) in the Authenticate Using drop down menu and select submit + restart. OV3600 checks the local username and password store before checking with the TACACS+ server. If the user is found locally, the local password and local role apply. When using TACAS+, it is not necessary or recommended to define users on the OV3600 server. The only recommended user is the backup administrator, in the event that the TACAS+ server goes down. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. Configuring RADIUS Authentication and Authorization For RADIUS capability, you must configure the IP/Hostname of the RADIUS server, the TCP port, and the server shared secret. Perform these steps to configuration RADIUS authentication: 1. Go to the OV3600 Setup > Authentication page. This page displays current status of RADIUS. Figure 27 illustrates this page. Figure 27 OV3600 Setup > Authentication Page Illustration 2. Select No to disable or Yes to enable TACACS+ or RADIUS authentication. If you select Yes, several new fields appear. Complete the fields described in Table 25. Table 25 OV3600 Setup > Authentication Fields and Default Values Field Default Description Primary Server Hostname/IP Address N/A Enter the IP address or the hostname of the primary RADIUS server. Primary Server Port 1812 Enter the TCP port for the primary RADIUS server. Primary Server Secret N/A Specify and confirm the primary shared secret for the primary RADIUS server. Secondary Server Hostname/IP Address N/A Enter the IP address or the hostname of the secondary RADIUS server. Secondary Server Port 1812 Enter the TCP port for the secondary RADIUS server. Secondary Server Secret N/A Enter the shared secret for the secondary RADIUS server. 3. Select Save to retain these configurations, and continue with additional steps in the next procedure. 52 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

53 Integrating a RADIUS Accounting Server OV3600 checks the local username and password before checking with the RADIUS server. If the user is found locally, the local password and role apply. When using RADIUS, it s not necessary or recommended to define users on the OV3600 server. The only recommended user is the backup admin, in case the RADIUS server goes down. Optionally, you can configure RADIUS server accounting on OV3600 Setup > RADIUS Accounting. This capability is not required for basic OV3600 operation, but can increase the user-friendliness of OV3600 administration in large networks. Figure 28 illustrates the settings of this optional configuration interface. Perform the following steps and configurations to enable OV3600 to receive accounting records from a separate RADIUS server. Figure 28 illustrates the display of RADIUS accounting clients already configured, and Figure 29 illustrates the Add RADIUS Accounting Client page. Figure 28 OV3600 Setup > RADIUS Accounting Page Illustration Figure 29 OV3600 Setup > RADIUS > Add RADIUS Accounting Client Page Illustration 1. To specify the RADIUS authentication server or network, browse to the OV3600 Setup > RADIUS Accounting page and select Add, illustrated in Figure 29, and provide the information in Table Select Add, then complete the following fields: Table 26 OV3600 Setup > Radius Accounting Fields and Default Values Setting Default Description Nickname None Sets a user-defined name for the authentication server. IP/Network None Cites the IP address or DNS Hostname for the authentication server if you only want to accept packets from one device. To accept packets from an entire network enter the IP/Netmask of the network (for example, /24). Shared Secret (Confirm) None Sets the Shared Secret that is used to establish communication between OV3600 and the RADIUS authentication server. What Next? Go to additional subtabs in OV3600 Setup to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

54 Enabling OV3600 to Manage Your Devices Once OV3600 is installed and active on the network, the next task is to define the basic settings that allow OV3600 to communicate with and manage your devices. Device-specific firmware files are often required or are highly desirable. Furthermore, the use of Web Auth bundles is advantageous for deployment of Cisco WLC wireless LAN controllers when they are present on the network. This section contains the following procedures: Configuring Communication Settings for Discovered Devices Loading Device Firmware Onto OV3600 (optional) Overview of the Device Setup > Upload Firmware & Files Page Loading Firmware Files to OV3600 Configuring Communication Settings for Discovered Devices To configure OV3600 to communicate with your devices, to define the default shared secrets, and to set SNMP polling information, navigate to the Device Setup > Communication page, illustrated in Figure 30. Figure 30 Device Setup > Communication Page Illustration Perform the following steps to define the default credentials and SNMP settings for the wireless network. 1. On the Device Setup > Communication page, locate the Default Credentials area. Enter the credentials for each device model on your network. The default credentials are assigned to all newly discovered APs. 54 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

55 The Edit button edits the default credentials for newly discovered devices. To modify the credentials for existing devices, use the APs/Devices > Manage page or the Modify Devices link on the APs/Devices > List page. Community strings and shared secrets must have read-write access for OV3600 to configure the devices. Without read-write access, OV3600 may be able to monitor the devices but cannot apply any configuration changes. 2. Browse to the Device Setup > Communication page, locate the SNMP Settings section, and enter or revise the following information. Table 27 lists the settings and default values. Table 27 Device Setup > Communication > SNMP Settings Fields and Default Values Setting Default Description SNMP Timeout 3 Sets the time, in seconds, that OV3600 waits for a response from a device after sending an SNMP request. SNMP Retries 3 Sets the number of times OV3600 tries to poll a device when it does not receive a response within the SNMP Timeout Period or the Group's Missed SNMP Poll Threshold setting (1-100). If OV3600 does not receive an SNMP response from the device after the specified number of retries, OV3600 classifies that device as Down. 3. Locate the SNMP v3 Informs section. Select Add New SNMP v3 User to reveal its configuration section. OV3600 users will need to configure all v3 users that are configured on the controller; the SNMP Inform receiver in the OV3600 will be restarted when users are changed or added to the controller. Username - Username of the SNMP v3 user as configured on the controller. Auth Protocol - Can be MD5 or SHA. The default setting is SHA. Auth and Priv Passphrases - Enter the auth and priv passphrases for the user as configured on the controller. Priv Protocol - Can be DES or AES. The default setting is DES. 4. Locate the Telnet/SSH Settings section, and complete or adjust the default value for the field. Table 28 shows the setting and default value. Table 28 Device Setup > Communication > Telnet/SSH Settings Fields and Default Values Setting Default Description Telnet/SSH Timeout (3-120 sec) 10 Sets the timeout period in seconds used when performing Telnet and SSH commands. 5. Locate the HTTP Discovery Settings section and adjust the default value. Table 29 shows the setting and default value. Table 29 Device Setup > Communication > HTTP Discovery Settings Fields and Default Values Setting Default Description HTTP Timeout (3-120 sec) 5 Sets the timeout period in seconds used when running an HTTP discovery scan. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

56 6. Locate the ICMP Settings section and adjust the default value as required. Table 30 shows the setting and default value. Table 30 Device Setup > Communication > ICMP Settings Fields and Default Values Setting Default Description Attempt to ping devices that were unreachable via SNMP Yes When Yes is selected, OV3600 attempts to ping the AP device. Select No if performance is affected in negative fashion by this function. If a large number of APs are unreachable by ICMP, likely to occur where there is in excess of 100 APs, the timeouts start to impede network performance. NOTE: If ICMP is disabled on the network, select No to avoid the performance penalty caused by numerous ping requests. 7. Locate the Symbol 4131 and Cisco Aironet IOS SNMP Initialization area. Select one of the options listed. Table 31 describes the settings and default values: Table 31 Device Setup > Communication > Symbol 4131 and Cisco Aironet IOS SNMP Initialization Fields and Default Values Setting Default Description Do Not Modify SNMP Settings Enable readwrite SNMP Yes No When selected, specifies that OV3600 not modify any SNMP settings. If SNMP is not already initialized on the Symbol, Nomadix, and Cisco IOS APs, OV3600 is not able to manage them. When selected, and when on networks where the Symbol, Nomadix, and Cisco IOS APs do not have SNMP initialized, this setting enables SNMP so the devices can be managed by OV3600. Loading Device Firmware Onto OV3600 (optional) Overview of the Device Setup > Upload Firmware & Files Page OV3600 enables automated firmware distribution to the devices on your network. Once you have downloaded the firmware files from the vendor, you can upload this firmware to OV3600 for distribution to devices via the Device Setup > Upload Firmware & Files page. This page lists all firmware files on OV3600 with file information. This page also enables you to add new firmware files, to delete firmware files, and to add New Web Auth Bundle files. The following additional pages support firmware file information: Firmware files uploaded to OV3600 appear as options in the drop-down menus on the Group > Firmware page and on individual APs/Devices > Manage pages. Use the OV3600 Setup page to configure OV3600-wide default firmware options. Table 32 below itemizes the contents, settings, and default values for the Upload Firmware & Files page. Table 32 Device Setup > Upload Firmware & Files Fields and Default Values Setting Default Description Type Alcatel-Luc ent switch (any model) Displays a drop-down list of the primary AP makes and models that OV3600 supports with automated firmware distribution. Owner Role None Displays the user role that uploaded the firmware file. This is the role that has access to the file when an upgrade is attempted. Description None Displays a user-configurable text description of the firmware file. Server Protocol None Displays the file transfer protocol by which the firmware file was obtained from the server. 56 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

57 Table 32 Device Setup > Upload Firmware & Files Fields and Default Values (Continued) Setting Default Description Use Group File Server None Displays the name of the file server supporting the group. Firmware Filename Firmware Version Firmware MD5 Checksum Firmware File Size None None None None Loading Firmware Files to OV3600 Displays the name of the file that was uploaded to OV3600 and to be transferred to an AP when the file is used in an upgrade. Displays the firmware version number. This is a user-configurable field. Displays the MD5 checksum of the file after it was uploaded to OV3600. The MD5 checksum is used to verify that the file was uploaded to OV3600 without issue. The checksum should match the checksum of the file before it was uploaded. Displays the size of the firmware file in bytes. HTML Filename None Supporting HTML, displays the name of the file that was uploaded to OV3600 and to be transferred to an AP when the file is used in an upgrade. HTML Version None Supporting HTML, displays the version of HTML used for file transfer. HTML MD5 Checksum None Supporting HTML, displays the MD5 checksum of the file after it was uploaded to OV3600. The MD5 checksum is used to verify that the file was uploaded to OV3600 without issue. The checksum should match the checksum of the file before it was uploaded. HTML File Size None Supporting HTML, displays the size of the file in bytes. Desired Firmware File for Specified Groups None The firmware file is set as the desired firmware version on the Groups > Firmware Files page of the specified groups. You cannot delete a firmware file that is set as the desired firmware version for a group. Perform the following steps to load a device firmware file onto OV3600: 1. Go to the Device Setup > Upload Firmware & Files page. 2. Select Add. The Add Firmware File page appears. Figure 31 illustrates this page. Figure 31 Device Setup > Upload Firmware and Files > Add Page Illustration 3. Select Supported Firmware Versions and Features to view supported firmware versions. Unsupported and untested firmware may cause device mismatches and other problems. Please contact Alcatel-Lucent support before installing non-certified firmware. 4. Enter the appropriate information and select Add. The file uploads to OV3600 and once complete, this file appears on the Device Setup > Upload Firmware & Files page. This file also appears on additional pages that display firmware files (such as the Group > Firmware page and on individual APs/Devices > Manage pages). OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

58 5. You can also import a CSV list of groups and their external TFTP firmware servers. Table 33 itemizes the settings of this page. Table 33 Supported Firmware Versions and Features Fields and Default Values Setting Default Description Type Alcatel- Lucent Switch Indicates the firmware file is used with the specified type. If you select an IOS device from the Type drop-down menu, you have the option of choosing a server protocol of TFTP or FTP. If you choose FTP, you may later notice that the firmware files are pushed to the device more quickly. With selection of some types, particularly Cisco controllers, you can specify the boot software version. Firmware Version None Provides a user-configurable field to specify the firmware version number. Appears if you did not select the default Alcatel-Lucent Switch type. Description None Provides a user-configurable text description of the firmware file. Upload firmware files (and use built-in firmware) Use an external firmware file server Use Group File Server Firmware File Server IP Address Firmware Filename Built-in N/A Disabled None None Selects the TFTP server that access points use to download their firmware. The built-in TFTP server is recommended. If you choose to use an external TFTP server, enter the File Server IP Address and the Firmware Filename. You can also choose to assign the external TFTP server on a per-group basis. If you select this option, you must enter the IP address on the Groups > Firmware page. Complete the Firmware File Server IP Address field. NOTE: With selection of some Types, you are prompted with the Server Protocol field that lets you select which protocol to use, and this varies from device to device. If you select FTP, OV3600 uses an anonymous user for file upload. If you opt to use an external firmware file server, this additional option appears. This setting instructs OV3600 to use the server that is associated with the group instead of defining a server. Provides the IP address of the External TFTP Server (like SolarWinds) used for the firmware upgrade. This option displays when the user selects the Use an external firmware file option. Enter the name of the firmware file that needs to be uploaded. Ensure that the firmware file is in the TFTP root directory. If you are using a non-external server, you select Choose File to find your local copy of the file. Additional fields may appear for multiple device types. OV3600 prompts you for additional firmware information as required. For example, Intel and Symbol distribute their firmware in two separate files: an image file and an HTML file. Both files must be uploaded to OV3600 for the firmware to be distributed successfully via OV Select Add to import the firmware file. To delete a firmware file that has already been uploaded to OV3600, return to the Device Setup > Upload Firmware & Files page, select the checkbox for the firmware file and select Delete. A firmware file may not be deleted if it is the desired version for a group. Use the Group > Firmware page to investigate this potential setting and status. Using Web Auth Bundles in OV3600 Web authentication bundles are configuration files that support Cisco WLC wireless LAN controllers. This procedure requires that you have local or network access to a Web Auth configuration file for Cisco WLC devices. Perform these steps to add or edit Web Auth bundles in OV Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

59 1. Go to the Device Setup > Upload Firmware & Files page. This page displays any existing Web Auth bundles that are currently configured in OV3600, and allows you to add or delete Web Auth bundles. 2. Scroll to the bottom of the page. Select Add New Web Auth Bundle to create a new Web Auth bundle (see Figure 32), or select the pencil icon next to an existing bundle to edit. You may also delete Web Auth bundles by selecting that bundle with the checkbox, and selecting Delete. Figure 32 Add Web Auth Bundle Page Illustration 3. Enter a descriptive label in the description field. This is the label used to identify and track Web Auth bundles on the page. 4. Enter the path and filename of the Web Auth configuration file in the Web Auth Bundle field or select Choose File to locate the file. 5. Select Add to complete the Web Auth bundle creation, or Save if replacing a previous Web Auth configuration file, or Cancel to abort the Web Auth integration. For additional information and a case study that illustrates the use of Web Auth bundles with Cisco WLC controllers, refer to the following document on Cisco.com: Wireless LAN controller Web Authentication Configuration Example, Document ID: Setting Up Device Types On OV3600 Setup > Device Type Setup, you can define how the Device Type displayed for users on your network is calculated from available data. The first matching property is used. These rules cannot be edited or deleted, but only reordered or enabled. You can change the priority order of rules by dragging and dropping rows, as shown in Figure 33. Check or uncheck the checkbox under the Enabled column to turn device setup rules on or off. Refer to Monitoring and Supporting WLAN Clients on page 198 for more information on the Device Type column that appears in Clients list tables. Figure 33 OV3600 Setup > Device Type Setup Page Illustration Configuring Cisco WLSE and WLSE Rogue Scanning The Cisco Wireless LAN Solution Engine (WLSE) includes rogue scanning functions that OV3600 supports. This section contains the following topics and procedures, and several of these sections have additional sub-procedures: OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

60 Introduction to Cisco WLSE Configuring WLSE Initially in OV3600 Configuring IOS APs for WDS Participation Configuring ACS for WDS Authentication Configuring Cisco WLSE Rogue Scanning You must enter one or more CiscoWorks WLSE hosts to be polled for discovery of Cisco devices and rogue AP information. Introduction to Cisco WLSE Cisco WLSE functions as an integral part of the Cisco Structured Wireless-Aware Network (SWAN) architecture, which includes IOS Access Points, a Wireless Domain Service, an Access Control Server, and a WLSE. In order for OV3600 to obtain Rogue AP information from the WLSE, all SWAN components must be properly configured. Table 34 describes these components. Table 34 Cisco SWAN Architecture Components SWAN Component WDS (Wireless Domain Services) WLSE (Wireless LAN Solution Engine) ACS (Access Control Server) Requirements WDS Name Primary and backup IP address for WDS devices (IOS AP or WLSM) WDS Credentials APs within WDS Group NOTE: WDS can be either a WLSM or an IOS AP. WLSM (WDS) can control up to 250 access points. AP (WDS) can control up to 30 access points. IP Address Login IP Address Login APs APs within WDS Group Configuring WLSE Initially in OV3600 Use the following general procedures to configure and deploy a WLSE device in OV3600: Adding an ACS Server for WLSE Enabling Rogue Alerts for Cisco WLSE Configuring WLSE to Communicate with APs Discovering Devices Managing Devices Inventory Reporting Defining Access Grouping WDS Participation Primary or Secondary WDS Adding an ACS Server for WLSE 1. Go to the Devices > Discover > AAA Server page. 2. Select New from the drop-down list. 3. Enter the Server Name, Server Port (default 2002), Username, Password, and Secret. 4. Select Save. 60 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

61 Enabling Rogue Alerts for Cisco WLSE 1. Go to the Faults > Network Wide Settings > Rogue AP Detection page. 2. Select the Enable. 3. Select Apply. Additional information about rogue device detection is available in Configuring Cisco WLSE Rogue Scanning on page 63. Configuring WLSE to Communicate with APs 1. Go to the Device Setup > Discover page. 2. Configure SNMP Information. 3. Configure HTTP Information. 4. Configure Telnet/SSH Credentials. 5. Configure HTTP ports for IOS access points. 6. Configure WLCCP credentials. 7. Configure AAA information. Discovering Devices There are three methods to discover access points within WLSE, as follows: Using Cisco Discovery Protocol (CDP) Importing from a file Importing from CiscoWorks Perform these steps to discover access points. 1. Go to the Device > Managed Devices > Discovery Wizard page. 2. Import devices from a file. 3. Import devices from Cisco Works. 4. Import using CDP. Managing Devices Prior to enabling radio resource management on IOS access points, the access points must be under WLSE management. OV3600 becomes the primary management/monitoring vehicle for IOS access points, but for OV3600 to gather Rogue information, the WLSE must be an NMS manager to the APs. Use these pages to make such configurations: 1. Go to Device > Discover > Advanced Options. 2. Select the method to bring APs into management Auto, or specify via filter. Inventory Reporting When new devices are managed, the WLSE generates an inventory report detailing the new APs. OV3600 accesses the inventory report via the SOAP API to auto-discover access points. This is an optional step to enable another form of AP discovery in addition to OV3600' CDP, SNMP scanning, and HTTP scanning discovery for Cisco IOS access points. Perform these steps for inventory reporting. 1. Go to Devices > Inventory > Run Inventory. 2. Run Inventory executes immediately between WLSE polling cycles. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

62 Defining Access OV3600 requires System Admin access to WLSE. Use these pages to make these configurations. 1. Go to Administration > User Admin. 2. Configure Role and User. Grouping It s much easier to generate reports or faults if APs are grouped in WLSE. Use these pages to make such configurations. 1. Go to Devices > Group Management. 2. Configure Role and User. Configuring IOS APs for WDS Participation IOS APs (1100, 1200) can function in three roles within SWAN: Primary WDS Backup WDS WDS Member OV3600 monitors AP WDS role and displays this information on AP Monitoring page. APs functioning as WDS Master or Primary WDS will no longer show up as Down is the radios are enabled. WDS Participation Perform these steps to configure WDS participation. 1. Log in to the AP. 2. Go to the Wireless Services > AP page. 3. Select Enable participation in SWAN Infrastructure. 4. Select Specified Discovery and enter the IP address of the Primary WDS device (AP or WLSM). 5. Enter the Username and Password for the WLSE server. Primary or Secondary WDS Perform these steps to configure primary or secondary functions for WDS. 1. Go to the Wireless Services > WDS > General Setup page. 2. If the AP is the Primary or Backup WDS, select Use the AP as Wireless Domain Services. Select Priority (set 200 for Primary, 100 for Secondary). Configure the Wireless Network Manager (configure the IP address of WLSE). 3. If the AP is Member Only, leave all options unchecked. 4. Go to the Security > Server Manager page. 5. Enter the IP address and Shared Secret for the ACS server and select Apply. 6. Go to the Wireless Services > WDS > Server Group page. 7. Enter the WDS Group of AP. 8. Select the ACS server in the Priority 1 drop-down menu and select Apply. 62 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

63 Configuring ACS for WDS Authentication ACS authenticates all components of the WDS and must be configured first. Perform these steps to make this configuration. 1. Login to the ACS. 2. Go to the System Configuration > ACS Certificate Setup page. 3. Install a New Certificate by selecting the Install New Certificate button, or skip to the next step if the certificate was previously installed. 4. Select User Setup in the left frame. 5. Enter the Username that will be used to authenticate into the WDS and select Add/Edit. 6. Enter the Password that will be used to authenticate into the WDS and select Submit. 7. Go to the Network Configuration > Add AAA Client page. 8. Add AP Hostname, AP IP Address, and Community String (for the key). 9. Enter the Password that will be used to authenticate into the WDS and select Submit. For additional and more general information about ACS, refer to Configuring ACS Servers on page 64. Configuring Cisco WLSE Rogue Scanning The OV3600 Setup > WLSE page allows OV3600 to integrate with the Cisco Wireless LAN Solution Engine (WLSE). OV3600 can discover APs and gather rogue scanning data from the Cisco WLSE. Figure 34 illustrates and itemizes the OV3600 settings for communication that is enabled between OV3600 and WLSE. Figure 34 OV3600 Setup > WLSE > Add WLSE Page Illustration Perform the following steps for optional configuration of OV3600 for support of Cisco WLSE rogue scanning. 1. To add a Cisco WLSE server to OV3600, navigate to the OV3600 Setup > WLSE page and select Add. Complete the fields in this page. Table 35 describes the settings and default values. Table 35 OV3600 Setup > WLSE Fields and Default Values Setting Default Description Hostname/IP Address None Designates the IP address or DNS Hostname for the WLSE server, which must already be configured on the Cisco WLSE server. Protocol HTTP Specifies the protocol to be used when polling the WLSE. Port 1741 Defines the port OV3600 uses to communicate with the WLSE server. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

64 Table 35 OV3600 Setup > WLSE Fields and Default Values (Continued) Setting Default Description Username None Defines the username OV3600 uses to communicate with the WLSE server. The username and password must be configured the same way on the WLSE server and on OV3600. The user needs permission to display faults to discover rogues and inventory API (XML API) to discover manageable APs. As derived from a Cisco limitation, only credentials with alphanumeric characters (that have only letters and numbers, not other symbols) allow OV3600 to pull the necessary XML APIs. Password None Defines the password OV3600 uses to communicate with the WLSE server. The username and password must be configured the same way on the WLSE server and on OV3600. As derived from a Cisco limitation, only credentials with alphanumeric characters (that have only letters and numbers, not other symbols) allow OV3600 to pull the necessary XML APIs. Poll for AP Discovery; Poll for Rogue Discovery Yes Sets the method by which OV3600 uses WLSE to poll for discovery of new APs and/or new rogue devices on the network. Last Contacted None Displays the last time OV3600 was able to contact the WLSE server. Polling Period 10 minutes Determines how frequently OV3600 polls WLSE to gather rogue scanning data. 2. After you have completed all fields, select Save. OV3600 is now configured to gather rogue information from WLSE rogue scans. As a result of this configuration, any rogues found by WLSE appear on the RAPIDS > List page. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. Configuring ACS Servers This is an optional configuration. The OV3600 Setup > ACS page allows OV3600 to poll one or more Cisco ACS servers for wireless username information. When you specify an ACS server, OV3600 gathers information about your wireless users. Refer to on page 59 if you want to use your ACS server to manage your OV3600 users. Perform these steps to configure ACS servers: 1. Go to the OV3600 Setup > ACS page. This page displays current ACS setup, as illustrated in Figure 35. Figure 35 OV3600 Setup > ACS Page Illustration 2. Select Add to create a new ACS server, or select a pencil icon to edit an existing server. To delete an ACS server, select that server and select Delete. When selecting Add or edit, the Details page appears, as illustrated in Figure Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

65 Figure 36 OV3600 Setup > ACS > Add/Edit Details Page Illustration 3. Complete the settings on OV3600 Setup > ACS > Add/Edit Details. Table 36 describes these fields: Table 36 OV3600 Setup > ACS > Add/Edit Details Fields and Default Values Field Default Description IP/Hostname None Sets the DNS name or the IP address of the ACS Server. Protocol HTTP Launches a drop-down menu specifying the protocol OV3600 uses when it polls the ACS server. Port 2002 Sets the port through which OV3600 communicates with the ACS. OV3600 generally communicates via SNMP traps on port 162. Username None Sets the Username of the account OV3600 uses to poll the ACS server. Password None Sets the password of the account OV3600 uses to poll the ACS server. Polling Period 10 min Launches a drop-down menu that specifies how frequently OV3600 polls the ACS server for username information. 4. Select Add to finish creating the new ACS server, or Save to finish editing an existing ACS server. 5. The ACS server must have logging enabled for passed authentications. Enable the Log to CSV Passed Authentications report option, as follows: Log in to the ACS server, select System Configuration, then in the Select frame, select Logging. Under Enable Logging, select CSV Passed Authentications. The default logging options function and support OV3600. These include the two columns OV3600 requires: User-Name and Caller-ID. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. Integrating OV3600 with an Existing Network Management Solution (NMS) This is an optional configuration. The OV3600 Setup > NMS configuration page allows OV3600 to integrate with other Network Management Solution (NMS) consoles. This configuration enables advanced and interoperable functionality as follows: OV3600 can forward WLAN-related SNMP traps to the NMS, or OV3600 can send SNMPv1 or SNMPv2 traps to the NMS. OV3600 can be used in conjunction with Hewlett-Packard s ProCurve Manager. The necessary files for either type of NMS interoperability are downloaded from the OV3600 Setup > NMS page as follows. For additional information, contact support. Perform these steps to configure NMS support in OV3600: OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

66 1. Go to OV3600 Setup > NMS, illustrated in Figure 37. Figure 37 OV3600 Setup > NMS Page Illustration 2. Select Add to integrate a new NMS server, or select the pencil icon to edit an existing server. Provide the information described in Table 37: Table 37 OV3600 Setup > NMS Integration Add/Edit Fields and Default Values Setting Default Description Hostname None Cites the DNS name or the IP address of the NMS. Port 162 Sets the port OV3600 uses to communicate with the NMS. NOTE: OV3600 generally communicates via SNMP traps on port 162. Community String None Sets the community string used to communicate with the NMS. SNMP Version v2c Sets the SNMP version of the traps sent to the Host. Enabled Yes Enables or disables trap logging to the specified NMS. Send Configuration Traps Yes Enables NMS servers to transmit SNMP configuration traps. 3. The NMS Integration Add/Edit page includes the Netcool/OMNIbus Integration link to information and instructions. The IBM Tivoli Netcool/OMNIbus operations management software enables automated event correlation and additional features resulting in optimized network uptime. 4. The NMS Integration Add/Edit page includes the HP ProCurve Manager Integration link. Select this link for additional information, zip file download, and brief instructions for installation with OV3600. Select Add to finish creating the NMS server, or Save to configure an existing NMS server. What Next? Go to additional tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you for any phase of OV3600 installation. Auditing PCI Compliance on the Network This section describes PCI requirements and auditing functions in OV3600, with the following topics: Introduction to PCI Requirements PCI Auditing in the OV3600 Interface Enabling or Disabling PCI Auditing Introduction to PCI Requirements OV3600 supports wide security standards and functions in the wireless network. One component of network security is the optional deployment of Payment Card Industry (PCI) Auditing. The Payment Card Industry (PCI) Data Security Standard (DSS) establishes multiple levels in which payment cardholder data is protected in a wireless network. OV3600 supports PCI requirements according to the standards and specifications set forth by the following authority: Payment Card Industry (PCI) Data Security Standard (DSS) PCI Security Standards Council Website PCI Quick Reference Guide, Version 1.2 (October 2008) 66 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

67 PCI Auditing in the OV3600 Interface PCI Auditing in OV3600 allows you to monitor, audit, and demonstrate PCI compliance on the network. There are five primary pages in which you establish, monitor, and access PCI auditing, as follows: The OV3600 Setup > PCI Compliance page enables or disables PCI Compliance monitoring on the network, and displays the current compliance status on the network. See Enabling or Disabling PCI Auditing on page 68. The Reports > Definitions page allows you to create custom-configured and custom-scheduled PCI Compliance reports. See Reports > Definitions Page Overview on page 229. The Reports > Generated page lists PCI Compliance reports currently available, and allows you to generate the latest daily version of the PCI Compliance Report with a single select. Refer to Reports > Generated Page Overview on page 231. The APs/Devices > PCI Compliance page enables you to analyze PCI Compliance for any specific device on the network. This page is accessible when you select a specific device from the APs/Devices > Monitor page. First, you must enable this function through OV3600 Setup. See Enabling or Disabling PCI Auditing on page 68. The PCI Compliance Report offers additional information. Refer to Using the PCI Compliance Report on page 247. This report not only contains Pass or Fail status for each PCI requirement, but cites the action required to resolve a Fail status when sufficient information is available. When any PCI requirement is enabled on OV3600, then OV3600 grades the network as pass or fail for the respective PCI requirement. Whenever a PCI requirement is not enabled in OV3600, then OV3600 does not monitor the network s status in relation to that requirement, and cannot designate Pass or Fail network status. OV3600 users without RAPIDS visibility enabled will not see the 11.1 PCI requirements in the PCI Compliance Report. Table 38 PCI Requirements and Support in OV3600 Requirement Description 1.1 Monitoring configuration standards for network firewall devices When Enabled: PCI Requirement 1.1 establishes firewall and router configuration standards. A device fails Requirement 1.1 if there are mismatches between the desired configuration and the configuration on the device. When Disabled: firewall router and device configurations are not checked for PCI compliance, and Pass or Fail status is not reported or monitored Monitoring firewall installation between any wireless networks and the cardholder data environment When Enabled: A device passes requirement if it can function as a stateful firewall. When Disabled: firewall router and device installation are not checked for PCI compliance. 2.1 Monitoring the presence of vendor-supplied default security settings When Enabled: PCI Requirement 2 establishes the standard in which all vendor-supplied default passwords are changed prior to a device s presence and operation in the network. A device fails requirement 2.1 if the username, passwords or SNMP credentials being used by OV3600 to communicate with the device are on a list of forbidden default credentials. The list includes common vendor default passwords, for example. When Disabled: device passwords and other vendor default settings are not checked for PCI compliance Changing vendor-supplied defaults for wireless environments When Enabled: A device fails requirement if the passphrases, SSIDs, or other securityrelated settings are on a list of forbidden values that OV3600 establishes and tracks. The list includes common vendor default passwords. The user can input new values to achieve compliance. When Disabled: network devices are not checked for forbidden information and PCI Compliance is not established. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

68 Table 38 PCI Requirements and Support in OV3600 (Continued) Requirement Description Using strong encryption in wireless networks When Enabled: PCI Requirement 4 establishes the standard by which payment cardholder data is encrypted prior to transmission across open public networks. PCI disallows WEP encryption as an approved encryption method after June 20, A device fails requirement if the desired or actual configuration reflect that WEP is enabled on the network, or if associated users can connect with WEP. When Disabled: OV3600 cannot establish a pass or fail status with regard to PCI encryption requirements on the network Using intrusion-detection or intrusion-prevention systems to monitor all traffic When Enabled: OV3600 reports pass or fail status when monitoring devices capable of reporting IDS events. Recent IDS events are summarized in the PCI Compliance report or the IDS Report. When Disabled: OV3600 does not monitor the presence of PCI-compliant intrusion detection or prevention systems, nor can it report Pass or Fail status with regard to IDS events. Enabling or Disabling PCI Auditing Perform these steps to verify status and to enable or disable OV3600 support for PCI 1.2 requirements. enabling one or all PCI standards on OV3600 enables real-time information and generated reports that advise on Pass or Fail status. The PCI auditing supported in OV3600 is reported in Table To determine what PCI Compliance standards are enabled or disabled on OV3600, navigate to the OV3600 Setup > PCI Compliance page, illustrated in Figure 38. Figure 38 OV3600 Setup > PCI Compliance Page Illustration 2. To enable, disable, or edit any category of PCI Compliance monitoring in OV3600, select the pencil icon next to the category. The Default Credential Compliance page displays for the respective PCI standard. 3. Create changes as required. Specific credentials can be cited in the Forbidden Credentials section of any Edit page to enforce PCI requirements in OV3600. Figure 39 shows one example. 68 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

69 Figure 39 Default Credential Compliance for PCI Requirements 4. Select Save. 5. To view and monitor PCI auditing on the network, use generated or daily reports. See Chapter 9, Creating, Running, and ing Reports. In addition, you can view the real-time PCI auditing of any given device online. Perform these steps: a. Go to the APs/Devices > List page, select a specific device, and the Monitor page for that device displays. The Monitor page displays a PCI Compliance subtab in the menu bar. b. Select PCI Compliance to view complete PCI compliance auditing for that specific device. What Next? Go to other tabs in the OV3600 Setup section to continue additional setup configurations. Complete the required configurations in this chapter before proceeding. Alcatel-Lucent support remains available to you in any phase of OV3600 installation. Deploying WMS Offload Overview of WMS Offload in OV3600 This section describes the Wireless LAN Management Server (WMS) offload infrastructure. WMS Offload is supported with the following two requirements: AOS-W Version or later OV3600 Version 6.0 or later The WMS feature is an enterprise-level hardware device and server architecture with managing software for security and network policy. There are three primary components of the WMS deployment: Air Monitor AP devices establish and monitor RF activity on the network. The WMS server manages devices and network activity, to include rogue AP detection and enforcement of network policy. The OV3600 graphical user interface (GUI) allows users to access and use the WMS functionality. WMS Offload is the ability to place the burden of the WMS server data and GUI functions on OV3600. WMS master switches provide this data so that OV3600 can support rigorous network monitoring capabilities. General Configuration Tasks Supporting WMS Offload in OV3600 WMS Offload must be enabled with a six-fold process and related configuration tasks, as follows: 1. Configure WLAN switches for optimal OV3600 monitoring. Disable debugging. Ensure OV3600 server is a trap receiver host. OmniVista 3600 Air Manager 7.4 User Guide Configuring OV

70 Ensure proper traps are enabled. 2. Configure OV3600 to optimally monitor the OV3600 infrastructure. Enable WMS offload. Configure SNMP communication. Create a proper policy for monitoring OV3600 infrastructure. Discover the infrastructure. 3. Configure device classification. Set up rogue classification. Set up rogue classification override. Establish user classification override devices. 4. Deploy AOS-W-specific monitoring features. Enable remote AP and wired network monitoring. View switch license information. 5. Convert existing floor plans to VisualRF, to include the following elements: AOS-W RF Plan 6. Use RTLS for increasing location accuracy (optional). Enable RTLS service on the OV3600 server. Enable RTLS on AOS-W Infrastructure. Additional Information Supporting WMS Offload For additional information, including detailed concepts, configuration procedures, restrictions, AOS-W infrastructure, and OV3600 version differences in support of WMS Offload, refer to the OmniVista 3600 Air Manager 7.4 Best Practices Guide. 70 Configuring OV3600 OmniVista 3600 Air Manager 7.4 User Guide

71 Chapter 4 Configuring and Using Device Groups This chapter describes the deployment of device groups within OV3600. The section below describes the pages or focused subtabs available on the Groups tab. Note that the available subtabs can vary significantly from one device group to another one or more subtabs may not appear, depending on the Default Group display option selected on the OV3600 Setup > General page and the types of devices you add to OV3600. Figure 40 Subtabs under the Group tab List This page is the default page in the Groups section of OV3600. It lists all groups currently configured in OV3600 and provides the foundation for all group-level configurations. See Viewing All Defined Device Groups on page 72. Monitor This page displays client and bandwidth usage information, lists devices in a given group, provides an Alert Summary table for monitoring alerts for the group, and provides a detailed Audit Log for group-level activity. Basic This page appears when you create a new group on the Groups > List page. Once you define a group name, OV3600 displays the Basic page from which you configure many group-level settings. This page remains available for any device group configured in OV3600. Refer to Configuring Basic Group Settings on page 74. Templates This page manages templates for any device group. Templates allow you to manage the configuration of Dell PowerConnect W, 3Com, Alcatel-Lucent, Aruba Networks, Cisco Aironet IOS, Cisco Catalyst switches, Enterasys, HP, Nortel, Symbol and Trapeze devices in a given group using a configuration file. Variables in such templates configure device-specific properties, such as name, IP address and channel. Variables also define group-level properties. For additional information about using the Templates page, refer to Chapter 6, Creating and Using Templates on page 153. Security This page defines general security settings for device groups, to include RADIUS, encryption, and additional security settings on devices. Refer to Configuring Group Security Settings on page 82. SSIDs This page sets SSIDs, VLANs, and related parameters in device groups. Refer to Configuring Group SSIDs and VLANs on page 84. AAA Servers This page configures authentication, authorization, and accounting settings in support of RADIUS servers for device groups. Refer to Adding and Configuring Group AAA Servers on page 81. Radio This page defines general radio settings for device groups. Refer to Configuring Radio Settings for Device Groups on page 88. Alcatel-Lucent Config This page manages AOS-W Device Groups, AP Overrides, and other profiles specific to Alcatel-Lucent devices on the network. Use this page as an alternative to the Device Setup > Alcatel-Lucent Configuration page. The appearance of this page varies depending on whether OV3600 is configured for global configuration or group configuration. For additional information, refer to the AOS-W Configuration Guide. Cisco WLC Config This page consolidates controller-level settings from the Group Radio, Security, SSIDs, Cisco WLC Radio and AAA Server pages into one navigation tree that is easier to navigate, and has familiar layout and terminology. Bulk configuration for per-thin AP settings, previously configured on the Group LWAPP APs tab, can now be performed from Modify Devices on the APs/Devices > List page. Refer to Cisco WLC Group Configuration on page 92. PTMP This page defines settings specific to Proxim MP devices when present. Refer to Configuring Group PTMP Settings on page 97. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 71

72 Proxim Mesh This page defines mesh AP settings specific to Proxim devices when present. Refer to Configuring Proxim Mesh Radio Settings on page 98. MAC ACL This page defines MAC-specific settings that apply to Proxim, Symbol, and ProCurve 520 devices when present. Refer to Configuring Group MAC Access Control Lists on page 99. Firmware This page manages firmware files for many devices. Specifying Minimum Firmware Versions for APs in a Group on page 99. Compare This page allows you to compare line item-settings between two device groups. On the Groups > List page, select Compare Two Groups, select the two groups from the drop-down menus, then select Compare. Comparing Device Groups on page 100. This chapter also provides the following additional procedures for group-level configurations: Deleting a Group on page 101 Changing Multiple Group Configurations on page 102 Modifying Multiple Devices on page 103 Using Global Groups for Group Configuration on page 105 OV3600 Groups Overview Enterprise APs, controllers, routers, and switches have hundreds of variable settings that must be configured precisely to achieve optimal performance and network security. Configuring all settings on each device individually is time consuming and error prone. OV3600 addresses this challenge by automating the processes of device configuration and compliance auditing. At the core of this approach is the concept of Device Groups, with the following functions and benefits: OV3600 allows certain settings to be managed efficiently at Group-level while others are managed at an individual device level. OV3600 defines a Group as a subset of the devices on the wireless LAN, ranging in size from one device to hundreds of devices that share certain common configuration settings. Groups may be defined based on geography (such as 5th Floor APs ), usage or security policies (such as Guest Access APs ), function (such as Manufacturing APs ), or any other appropriate variable. Devices within a group may be from different vendors or hardware models. All devices within a Group share certain basic configuration settings. Typical group configuration variables include basic settings (SSID, SNMP polling interval, and so forth), security settings (VLANs, WEP, 802.1x, ACLs, and so forth), and some radio settings (data rates, fragmentation threshold, RTS threshold, DTIM, preamble, and so forth). When configuration changes are applied at a group level, they are assigned automatically to every device within that group. Such changes must be applied with every device in Managed mode. Monitor mode is the more common mode. Always review the Audit page before pushing configuration to a device or group. Individual device settings such as device name, RF channel selection, RF transmission power, antenna settings, and so forth typically should not be managed at a group level and must be individually configured for optimal performance. Individual AP settings are configured on the APs/Devices > Manage page. You can create as many different groups as required. Administrators usually establish groups that range in size from five to 100 wireless devices. Group configuration can be enhanced with the OV3600 Global Groups feature, which lets you create Global Groups with configurations that are pushed to individual Subscriber Groups. Viewing All Defined Device Groups To display a list of all defined groups, browse to the Groups > List page, illustrated in Figure Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

73 Figure 41 Groups > List Page Illustration Table 39 describes the columns in the Groups > List page. Table 39 Groups > List Columns Column Add New Group Changes Manage (wrench icon) Name Is Global Group Global Group SSID Total Devices Down Mismatched Ignored Clients Usage VPN Sessions Duplicate Up/Down Status Polling Period Description Launches a page that enables you to add a new group by name and to define group parameters for devices in that group. For additional information, refer to Configuring Basic Group Settings on page 74. Whether the group has unapplied changes. Goes to the Groups > Basic configuration page for that group. Hover your mouse over the icon to see a list of shortcuts to group-specific subtabs that would appear across the navigation section if this group is selected. Uniquely identifies the group by location, vendor, department or any other identifier (such as Accounting APs, Floor 1 APs, Cisco devices, 802.1x APs, and so forth). If a group is designated as global, it may not contain APs but it may be used as a template for other groups. This column may also indicate Yes if this group has been pushed to the OV3600 from a Master Console. Specifies which group this Subscriber Group is using as its template. The SSID assigned to supported device types within the group. Total number of devices contained in the group including APs, controllers, routers, or switches. The number of access points within the group that are not reachable via SNMP or are no longer associated to a controller. Note that thin APs are not directly polled with SNMP, but are polled through the controller. That controller may report that the thin AP is down or is no longer on the controller. At this point, OV3600 classifies the device as down. The number of devices within the group that are in a mismatched state. The number of ignored devices in that group. The number of mobile users associated with all access points within the group. To avoid double counting of clients, clients are only listed in the group of the AP with which they are associated. Note that device groups with only controllers in them report no clients. A running average of the sum of bytes in and bytes out for the managed radio page. Number of active (connected) VPN sessions under this group. Creates a new group with the name Copy of <Group Name> with configuration settings. (Alcatel-Lucent configuration settings will have to be manually added back.) The time between Up/Down SNMP polling periods for each device in the group. Detailed SNMP polling period information is available on the Groups > Basic configuration page. Note that by default, most polling intervals do not match the up/down period. When you first configure OV3600, there is only one default group labeled Access Points. If you have no other groups configured, refer to Configuring Basic Group Settings on page 74. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 73

74 Configuring Basic Group Settings The first default device group that OV3600 sets up is the Access Points group, but you can use this procedure to add and configure any device group. Perform these steps to configure basic group settings, then continue to additional procedures to define additional settings as required. 1. Go to the Groups > List page. Existing device groups appear on this page. 2. To create a new group, select Add. Enter a group name and select Add. The Groups > Basic page appears. To edit an existing device group, select the manage (wrench) icon next to the group. The Groups > Basic page appears. If you mouse over an existing group s wrench, a popup menu allows you to select Basic, Templates, Security, SSIDs, AAA Servers, Radio, Alcatel-Lucent Config or Cisco WLC Config to edit those pages as desired, as illustrated in Figure 42. Figure 42 Pop-up When Hovering over Wrench Icon in Groups > List Figure 43 illustrates an example Groups > Basic page. 74 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

75 Figure 43 Groups > Basic Page Illustration 3. Define the settings in the Basic and Global Group sections. Table 40 describes several typical settings and default values of this Basic section. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 75

76 Table 40 Basic and Global Groups Fields and Default Values Setting Default Description Name Missed SNMP Poll Threshold Regulatory Domain Timezone Allow One-to- One NAT Audit Configuration on Devices Use Global Group Defined when first adding the group Displays or changes the group name. As desired, use this field to set the name to uniquely identify the group by location, vendor, department, or any other identifier (such as Accounting APs, Cisco devices, 802.1x APs, and so forth). 1 Sets the number of Up/Down SNMP polls that must be missed before OV3600 considers a device to be down. The number of SNMP retries and the SNMP timeout of a poll can be set on the Device Setup > Communication page. United States OV3600 System Time No Yes No Sets the regulatory domain in OV3600, limiting the selectable channels for APs in the group. Allows group configuration changes to be scheduled relative to the time zone in which the devices are located. This setting is used for scheduling group-level configuration changes. Allows OV3600 to talk to the devices on a different IP address than the one configured on the device. NOTE: If enabled, the LAN IP Address listed on the AP/Devices > Manage configuration page under the Settings area is different than the IP Address under the Device Communication area. Auditing and pushing of configuration to devices can be disabled on all the devices in the group. Once disabled, all the devices in the groups will not be counted towards mismatched devices. When enabled, this field allows you to define the device group to be a Global Group. Refer to Using Global Groups for Group Configuration on page Complete the SNMP Polling Periods section. The information in this section overrides default settings. Table 41 describes the SNMP polling settings. Table 41 SNMP Polling Periods Fields and Default Values Setting Default Description Up/Down Status Polling Period Override Polling Period for Other Services AP Interface Polling Period Client Data Polling Period Thin AP Discovery Polling Period Device-to-Device link Polling Period Counters Polling Period Rogue AP and Device Location Data Polling Period CDP Neighbor Data Polling Period 5 minutes Sets time between Up/Down SNMP polling for each device in the group. The Group SNMP Polling Interval overrides the global parameter configured on the Device Setup > Communication page. An initial polling interval of 5 minutes is best for most networks. No Enables or disables overriding the base SNMP Polling Period. If you select Yes, the other settings in the SNMP Polling Periods section are activated, and you can override default values. 5 minutes Sets the interval at which OV3600 polls for radio monitoring and bandwidth being used by a device. 5 minutes Sets time between SNMP polls for client data for devices in the group. 5 minutes Sets time between SNMP polls for Thin AP Device Discovery. Controllers are the only devices affected by this polling interval. 5 minutes Sets time between SNMP polls for Device-to-Device link polling. Mesh APs are the only devices affected by this polling interval. 5 minutes Sets time between SNMP polls for Counter information. 5 minutes Sets time between SNMP polls for Rogue AP and Device Location Data polling. 30 minutes Sets the frequency in which this group polls the network for Cisco Discovery Protocol (CDP) neighbors. 5. Record additional information and comments about the group in the Notes section. 76 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

77 6. To configure which options and tabs are visible for the group, complete the settings in the Group Display Options section. Table 42 describes the settings and default values. Table 42 Group Display Options Fields and Default Values Setting Default Description Show device settings for: Selected Device Types Only devices on this OV3600 N/A Drop-down menu determines which Group tabs and options are to be viewable by default in new groups. Settings include the following: All Devices OV3600 displays all Group tabs and setting options. Only devices in this group OV3600 hides all options and tabs that do not apply to the devices in the group. If you use this setting, then to get the group list to display the correct SSIDs for the group, you must Save and Apply on the group. Only devices on this OV3600 hides all options and tabs that do not apply to the APs and devices currently on OV3600. Use system defaults Use the default settings on OV3600 Setup > General Selected device types Allows you to specify the device types for which OV3600 displays Group settings. This option appears if you chose to display selected device types, allowing you to select the device types to display group settings. Use Select devices in this group to display only devices in the group being configured. 7. To assign dynamically a range of static IP addresses to new devices as they are added into the group, locate the Automatic Static IP Assignment section on the Groups > Basic configuration page. If you select Yes in this section, additional fields appear. Complete these fields as required. Table 43 describes the settings and default values This section is only relevant for a small number of device types, and will appear when they are present. Table 43 Automatic Static IP Assignment Fields and Default Values Setting Default Description Assign Static IP Addresses to Devices Start IP Address No Blank Enables OV3600 to statically assign IP addresses from a specified range to all devices in the Group. Sets the first address OV3600 assigns to the devices in the Group. Number of Addresses Blank Sets the number of addresses in the pool from which OV3600 can assign IP addresses. Subnet Mask Blank Sets the subnet mask to be assigned to the devices in the Group. Subnet Gateway Next IP Address Blank Blank Sets the gateway to be assigned to the devices in the Group. Defines the next IP address queued for assignment. This field is disabled for the initial Access Points group. 8. To configure Spanning Tree Protocol on WLC devices and Proxim APs, locate the Spanning Tree Protocol section on the Groups > Basic configuration page. Adjust these settings as required. Table 44 describes the settings and default values. Table 44 Spanning Tree Protocol Fields and Default Values Setting Default Description Spanning Tree Protocol No Enables or disables Spanning Tree Protocol on Proxim APs. Bridge Priority Sets the priority for the AP. Values range from 0 to Lower values have higher priority. The lowest value is the root of the spanning tree. If all devices are at default the device with the lowest MAC address will become the root. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 77

78 Table 44 Spanning Tree Protocol Fields and Default Values (Continued) Setting Default Description Bridge Maximum Age Bridge Hello Time Bridge Forward Delay 20 Sets the maximum time, in seconds, that the device stores protocol information. The supported range is from 6 to Sets the time, in seconds, between Hello message broadcasts. 15 Sets the time, in seconds, that the port spends in listening and learning mode if the spanning tree has changed. 9. To configure NTP settings locate the NTP section and adjust these settings as required. Table 45 describes the settings and default values. Table 45 NTP Fields and Default Values Setting Default Description NTP Server #1,2,3 None Sets the IP address of the NTP server to be configured on the AP. UTC Time Zone Daylight Saving Time 0 Sets the hour offset from UTC time to local time for the AP. Times displayed in OV3600 graphs and logs use the time set on the OV3600 server. No Enables or disables the advanced daylight saving time settings in the Proxim section of the Groups > Basic configuration page. 10. To configure settings specific to Cisco IOS/Catalyst, locate the Cisco IOS/Catalyst section and adjust these settings as required. Table 46 describes the settings and default values. Table 46 Cisco IOS/Catalyst Fields and Default Values Setting Default Description SNMP Version 2c The version of SNMP used by OV3600 to communicate to the AP. Cisco IOS CLI Communication Cisco IOS Config File Communication Telnet TFTP The protocol OV3600 uses to communicate with Cisco IOS devices. Selecting SSH uses the secure shell for command line page (CLI) communication. Selecting Telnet sends the data in clear text via Telnet. The protocol OV3600 uses to communicate with Cisco IOS devices. Selecting SCP uses the secure copy protocol for file transfers and displays the SCP Version option. Selecting TFTP will use the insecure trivial file transfer protocol. The SCP login and password should be entered in the Telnet username and password fields. 11. To configure settings specific to Cisco WLC, locate the Cisco WLC section and adjust these settings as required. Table 47 describes the settings and default values. Table 47 Cisco WLC Fields and Default Values Setting Default Description SNMP Version 2c Sets the version of SNMP used by OV3600 to communicate to WLC controllers. CLI Communication Telnet Sets the protocol OV3600 uses to communicate with Cisco IOS devices. Selecting SSH uses the secure shell for command line page (CLI) communication. Selecting Telnet sends the data in clear text via Telnet. When configuring Cisco WLC controllers, refer to Configuring Wireless Parameters for Cisco Controllers on page Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

79 12. To configure Proxim/Avaya specific settings locate the Proxim/Avaya section and adjust these settings as required. Table 48 describes the settings and default values. Table 48 Proxim/Avaya Fields and Default Values Setting Default Description SNMP Version 1 Sets the version of SNMP used by OV3600 to communicate to the AP. Enable DNS Client Primary DNS server Secondary DNS server Default DNS domains HTTP Server Port Country Code No Blank Blank Blank Enables the DNS client on the AP. Enabling the DNS client allows you to set some values on the AP by hostname instead of IP address. If you select Yes for this setting, additional DNS fields display. Sets the IP address of the Primary DNS server. Sets the IP address of the Secondary DNS server. Sets the default DNS domain used by the AP. 80 Sets this port as the HTTP server port on all Proxim APs in the group. United States Configures OV3600 to derive its time settings based on the country of location, as specified in this field. 13. To configure HP ProCurve specific settings, locate the HP ProCurve section and adjust these settings as required. Table 49 describes the settings and default values. Table 49 HP ProCurve Fields and Default Values Setting Default Description SNMP Version 2c Sets the version of SNMP used by OV3600 to communicate to the AP. ProCurve XL/ZWeSM CLI Communication Controller SNMP Version Telnet 2c Sets the protocol OV3600 uses to communicate with ProCurve XLWeSM devices. Selecting SSH will use the secure shell for command line (CLI) communication. Selecting Telnet will send the data in clear text via telnet. Specifies the version of SNMP used by OV3600 to communicate to the controller. DST Start Month, Start Day, End Month, End Day, and DST Offset are only visible if Daylight Saving Time is enabled in the NTP section of the Groups > Basic configuration page. 14. To configure Symbol/Motorola settings, locate the Symbol section and adjust these settings as required. Table 50 describes the settings and default values of this section. Table 50 Symbol Fields and Default Values Setting Default Description SNMP Version 2c Specifies the version of SNMP used by OV3600 to communicate to the device. Client Inactivity Timeout (3-600 min) Symbol Controller CLI Communication Web Config Interface 3 Sets the minutes of inactivity after which a client associated to a Symbol AP will be considered inactive. A lower value typically provides a more accurate representation of current WLAN usage. NOTE: For other APs, OV3600 has more precise methods to determine when inactive clients are no longer associated to an AP. Telnet Yes The connection type to support the command-line interface (CLI) connection. The options are Telnet and secure shell (SSH). This is supported for WS5100, RFS4000, RFS6000 and RFS7000 devices only. Enables or disables the http/https configuration page for the Symbol 4131 devices. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 79

80 15. To configure settings specific to Alcatel-Lucent, locate the Aruba/Alcatel-Lucent section and adjust these settings as required. Table 51 describes the settings and default values of this section. Table 51 Alcatel-Lucent Fields and Default Values Setting Default Description SNMP Version 2c The version of SNMP used by OV3600 to communicate to the AP. Offload WMS Database Alcatel-Lucent GUI Config Ignore Rogues Discovered by Remote APs No Yes No Configures commands previously documented in the OmniVista 3600 Air Manager 7.4 Best Practices Guide. When enabled, this feature allows OV3600 to display historical information for WLAN switches. Changing the setting to Yes pushes commands via SSH to all WLAN switches in Monitor Only mode without rebooting the switch. The command can be pushed to switches in manage mode (also without rebooting the switch) if the Allow WMS Offload setting on OV3600 Setup > General is changed to Yes. This setting selects whether you'd like to configure your Alcatel-Lucent devices using the Groups > Alcatel-Lucent Config method (either global or group) or using Templates. Configures whether to turn off RAPIDS rogue classification and rogue reporting for RAPs in this group. 16. To configure settings for 3Com, Enterasys, Nortel, or Trapeze devices, locate the 3Com/Enterasys/ Nortel/Trapeze section and define the version of SNMP to be supported. 17. To configure support for routers and switches in the group, locate the Routers and Switches section and adjust these settings as required. This section defines the frequency in which all devices in the group polled. These settings can be disabled entirely as desired. Table 52 describes the settings and default values of this section. Table 52 Routers and Switches Fields and Default Values Setting Default Description Read ARP Table 4 hours Sets the frequency in which devices poll routers and switches for Address Resolution Protocol (ARP) table information. This setting can be disabled, or set to poll for ARP information in a range from every 15 seconds to 12 hours. Read CDP Table for Device Discovery Read Bridge Forwarding Table Interface Up/ Down Polling Period Interface Bandwidth Polling Period Interface Error Counter Polling Period Poll error counters Poll Cisco interface error counters 4 hours For Cisco devices, sets the frequency in which devices poll routers and switches for Cisco Discovery Protocol (CDP) information. This setting can be disabled, or set to poll for CDP neighbor information in a range from every 15 seconds to 12 hours. 4 hours Sets the frequency in which devices poll the network for bridge forwarding information. This setting can be disabled, or set to poll bridge forwarding tables from switches in a range from every 15 seconds to 12 hours. 5 minutes 15 minutes 30 minutes No No Sets the frequency in which network interfaces are polled for up/down status. This setting can be disabled, or set to poll from switches in a range from every 15 seconds to 30 minutes. Sets the frequency in which network interfaces are polled for bandwidth usage. This setting can be disabled, or set to poll from switches in a range from every 5 minutes to 30 minutes. Sets the frequency in which network interfaces are polled for up/down status. This setting can be disabled, or set to poll bridge forwarding tables from switches in a range from every 5 minutes to 30 minutes. Sets whether error counters should be polled. Sets whether the interface error counters for Cisco devices should be polled. 80 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

81 18. To configure settings for universal devices on the network, including routers and switches that support both wired and wireless networks, locate the Universal Devices, Routers and Switches section of the Groups > Basic page and define the version of SNMP to be supported. 19. To control the conditions by which devices are automatically authorized into this group, locate the Automatic Authorization settings section and adjust these settings as required. Table 53 describes the settings and default values. Table 53 Automatic Authorization Fields and Default Values Setting Default Description Add New Controllers and Autonomous Devices Location Add New Thin APs Location Use Global Setting Use Global Setting Whether to auto authorize new controllers to the New Devices List, the same Group/Folder as the discovering devices, the same Group/Folder as the closest IP neighbor, and/or a specified auto-authorization group and folder. The Current Global Setting set in OV3600 Setup > General is shown below this field. Selecting a different option overrides the global setting. Whether to auto authorize new thin APs to the New Devices List, the same Group/Folder as the discovering devices, the same Group/Folder as the closest IP neighbor, and/or a specified auto-authorization group and folder. The Current Global Setting set in OV3600 Setup > General is shown below. Selecting a different option overrides the global setting for this group. 20. To automate putting multiple devices in this group into Manage mode at once so that changes can be applied and have the devices revert to Monitor-Only mode after the maintenance period is over, locate the Maintenance Windows option and define a new AP Group Maintenance Window. 21. Select Save when the configurations of the Groups > Basic configuration page are complete to retain these settings, but without pushing these settings to all devices in the group. Save is a good option if you intend to make additional device changes in the group, and wish to wait until all configurations are complete before you push all configurations at one time. Select Save and Apply to make the changes permanent, or select Revert to discard all unapplied changes. What Next? Continue to additional sections in this chapter to create new groups or to edit existing groups. Once general group-level configurations are complete, continue to later chapters in this document to add or edit additional device-level configurations and to use several additional OV3600 functions. Adding and Configuring Group AAA Servers Configure RADIUS servers on the Groups > AAA Servers page. Once defined on this page, RADIUS servers are selectable in the drop-down menus on the Groups > Security and Groups > SSIDs configuration pages. Perform these steps to create RADIUS servers. TACACS+ servers are configurable only for Cisco WLC devices. Refer to Configuring Cisco WLC Security Parameters and Functions on page Go to the Groups > List page and select the group for which to define AAA servers by selecting the group name. The Monitor page appears. 2. Select the AAA Servers page. The AAA Servers page appears, enabling you to add a RADIUS server. Figure 44 illustrate this page for AAA RADIUS Servers: OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 81

82 Figure 44 Groups > AAA Servers Page Illustration 3. To add a RADIUS server or edit an existing server, select Add New RADIUS Server or the corresponding pencil icon to edit an existing server. Table 54 describes the settings and default values of the Add/Edit page. Table 54 Adding a RADIUS Server Fields and Default Values Setting Default Description Hostname/IP Address Secret and Confirm Secret None None Sets the IP Address or DNS name for RADIUS Server. NOTE: IP Address is required for Proxim/ORiNOCO and Cisco Aironet IOS APs. Sets the shared secret that is used to establish communication between OV3600 and the RADIUS server. NOTE: The shared secret entered in OV3600 must match the shared secret on the server. Authentication No Sets the RADIUS server to perform authentication when this setting is enabled with Yes. Authorization Port 1812 Appears when Authentication is enabled. Sets the port used for communication between the AP and the RADIUS server. Accounting No Sets the RADIUS server to perform accounting functions when enabled with Yes. Accounting Port No Appears when Accounting is enabled.sets the port used for communication between the AP and the RADIUS server. Timeout ( ) None Sets the time (in seconds) that the access point waits for a response from the RADIUS server. Max Retries (0-20) None Sets the number of times a RADIUS request is resent to a RADIUS server before failing. NOTE: If a RADIUS server is not responding or appears to be responding slowly, consider increasing the number of retries. 4. Select Add to complete the creation of the RADIUS server, or select Save if editing an existing RADIUS server. The Groups > AAA Servers page displays this new or edited server. You can now reference this server on the Groups > Security page. OV3600 supports reports for subsequent RADIUS Authentication. These are viewable by selecting Reports > Generated, scrolling to the bottom of the page, and selecting Latest RADIUS Authentication Issues Report. 5. To make additional RADIUS configurations for device groups, use the Groups > Security page and continue to the next topic. Configuring Group Security Settings The Groups > Security page allows you to set security policies for APs in a device group: 1. Select the device group for which to define security settings from the Groups > List page. 82 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

83 2. Go to Groups > Security. Some controls on this page interact with additional OV3600 pages. Figure 45 illustrates this page and Table 55 explains the fields and default values. Figure 45 Groups > Security Page Illustration Table 55 Groups > Security Page Fields and Default Values Setting Default Description VLANs Section VLAN Tagging and Multiple SSIDs Enabled This field enables support for VLANs and multiple SSIDs on the wireless network. If this setting is enabled, define additional VLANs and SSIDs on the Groups > SSIDs page. Refer to Configuring Group SSIDs and VLANs on page 84. Management VLAN ID Untagged This setting sets the ID for the management VLAN when VLANs are enabled in OV3600. This setting is supported only for the following devices: Proxim AP-600, AP-700, AP-2000, AP-4000 Avaya AP-3, Avaya AP-7, AP-4/5/6, AP-8 ProCurve520WL General Section Create Closed Network No If enabled, the APs in the Group do not broadcast their SSIDs. NOTE: Creating a closed network will make it more difficult for intruders to detect your wireless network. Block All Inter-client Communication EAP Options Section WEP Key Rotation Interval No RADIUS Authentication Servers Section RADIUS Authentication Server #1 - #4 If enabled, this setting blocks client devices associated with an AP from communicating with other client devices on the wireless network. NOTE: This option may also be identified as PSPF (Publicly Secure Packet Forwarding), which can be useful for enhanced security on public wireless networks. 300 Sets the frequency at which the Wired Equivalent Privacy (WEP) keys are rotated in the device group being configured. The supported range is from 0 to 10,000,000 seconds. Not selected Defines one or more RADIUS Authentication servers to be supported in this device group. Select up to four RADIUS authentication servers from the four drop-down menus. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 83

84 Table 55 Groups > Security Page Fields and Default Values (Continued) Setting Default Description Authentication Profile Name Authentication Profile Index OV3600- Defined Server #1 RADIUS Accounting Servers Section RADIUS Accounting Server #1 - #4 Authentication Profile Name Authentication Profile Index For Proxim devices only, this field sets the name of the authentication profile to be supported in this device group. 1 For Proxim devices only, this field sets the name of the authentication profile index to be supported in this device group. Not selected MAC Address Authentication Section MAC Address Authentication MAC Address Format Defines one or more RADIUS Accounting servers to be supported in this device group. Select up to four RADIUS accounting servers from the four drop-down menus. For Proxim devices only, this field sets the name of the accounting profile to be supported in this device group. 3 For Proxim devices only, this field sets the name of the accounting profile index to be supported in this device group. No Single Dash If enabled, only MAC addresses known to the RADIUS server are permitted to associate to APs in the Group. Allows selection of the format for MAC addresses used in RADIUS authentication and accounting requests: Dash Delimited: xx-xx-xx-xx-xx-xx (default) Colon Delimited: xx:xx:xx:xx:xx:xx Single-Dash: xxxxxx-xxxxxx No Delimiter: xxxxxxxxxxxx This option is supported only for Proxim AP-600, AP-700, AP-2000, AP- 4000, Avaya AP3/4/5/6/7/8, HP ProCurve 520WL Authorization Lifetime 1800 Sets the amount of time a user can be connected before reauthorization is required. The supported range is from 900 to 43,200 seconds. Primary RADIUS Server Reattempt Period 0 Specifies the time (in minutes) that the AP awaits responses from the primary RADIUS server before communicating with the secondary RADIUS server, and so forth 3. Select Save to retain these security configurations for the group, select Save and Apply to make the changes permanent, or select Revert to discard all unapplied changes. 4. Continue with additional security-related procedures in this document for additional RADIUS and SSID settings for device groups, as required. Configuring Group SSIDs and VLANs The Groups > SSIDs configuration page allows you to create and edit SSIDs and VLANs that apply to a device group. Perform these steps to create or edit VLANs and to set SSIDs. WLANs that are supported from one or more Cisco WLC controllers can be configured on the Groups > Cisco WLC Config page. 84 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

85 Figure 46 illustrates an example of the Groups > SSIDs page. Figure 46 Groups > SSIDs Page Illustration OV3600 reports users by radio and by SSID. Graphs on the AP and controller monitoring pages display bandwidth in and out based on SSID. OV3600 reports can also be run and filtered by SSID. An option on the OV3600 Setup > General page can age out SSIDs and their associated graphical data; by default, this is set to 365 days. 1. Go to Groups > List and select the group name for which to define SSIDs/VLANs. 2. Select the Groups > SSIDs configuration page. Table 56 describes the information that appears for SSIDs and VLANs that are currently configured for the device group. Table 56 Groups > SSIDs Fields and Descriptions Field SSID VLAN ID Name Encryption Mode First or Second Radio Enabled First or Second Radio Primary Native VLAN Description Displays the SSID associated with the VLAN. Identifies the number of the primary VLAN SSID on which encrypted or unencrypted packets can pass between the AP and the switch. Displays the name of the VLAN. Displays the encryption on the VLAN. Enables the VLAN, SSID and Encryption Mode on the radio control. Specifies which VLAN to be used as the primary VLAN. A primary VLAN is required. NOTE: If you create an open network (see the Create Closed Network setting below) in which the APs broadcast an SSID, the primary SSID is broadcast. Sets this VLAN to be the native VLAN. Native VLANs are untagged and typically used for management traffic only. OV3600 requires a Native VLAN to be set. For AP types do not require a native VLAN, create a dummy VLAN, disable it on both radio controls, and ensure that it has the highest VLAN ID. 3. Select Add to create a new SSID or VLAN, or select the pencil icon next to an existing SSID/VLAN to edit that existing SSID or VLAN. The Add SSID/VLAN configuration page appears as illustrated in Figure 47 and explained in Table 57. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 85

86 Figure 47 Groups > SSIDs > Add SSID/VLAN Page Illustration 4. Locate the SSID/VLAN section on the Groups > SSIDs configuration page and adjust these settings as required. This section encompasses the basic VLAN configuration. Table 57 describes the settings and default values. Note that the displayed settings can vary. Table 57 Groups > SSIDs > SSID/VLAN Section Fields and Default Values Setting Default Description Specify Interface Name Yes Enables or disables an interface name for the VLAN interface. Selecting No for this option displays the Enable VLAN Tagging and VLAN ID options. Interface None Sets the interface to support the SSID/VLAN combination. SSID None Sets the Service Set Identifier (SSID), which is a 32-character user-defined identifier attached to the header of packets sent over a WLAN. It acts as a password when a mobile device tries to connect to the network through the AP, and a device is not permitted to join the network unless it can provide the unique SSID. Name None Sets a user-definable name associated with SSID/VLAN combination. VLAN ID (1-4094) None Indicates the number of the VLAN designated as the Native VLAN, typically for management purposes. Displays if Specify Interface Name is set to No. Maximum Allowed Associations (0-2007) Broadcast SSID (Cisco WLC, Proxim and Symbol 4131 only) Partial Closed System (Proxim only) Unique Beacon (Proxim only) Block All Inter-Client Communication 255 Indicates the maximum number of mobile users which can associate with the specified VLAN/SSID. NOTE: 0 means unlimited for Cisco. No No No Yes For specific devices as cited, this setting enables the AP to broadcast the SSID for the specified VLAN/SSID. This setting works in conjunction with the Create Closed Network setting on the Groups > Security configuration page. Proxim devices support a maximum of four SSIDs. NOTE: This option should be enabled to ensure support of legacy users. For Proxim only, this setting enables to AP to send its SSID in every beacon, but it does not respond to any probe requests. For Proxim only, if more than one SSID is enabled, this option enables them to be sent in separate beacons. This setting blocks communication between client devices based on SSID. 86 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

87 5. Locate the Encryption area on the Groups > SSIDs page and adjust these settings as required. Table 58 describes the settings and default values. Table 58 Groups > SSIDs > Encryption Section Field and Default Values Setting Default Description Encryption Mode No Encryption Drop-down menu determines the level of encryption required for devices to associate to the APs. The drop-down menu options are as follows. Each option displays additional encryption settings that must be defined. Complete the associated settings for any encryption type chosen: No Encryption Optional WEP Wired Equivalent Privacy, not PCI compliant as of 2010 Require WEP Wired Equivalent Privacy, not PCI compliant as of 2010 Require 802.1x Based on the WEP algorithm Require Leap Lightweight Extensible Authentication Protocol 802.1x+WEP Combines the two encryption types shown 802.1x+LEAP Combines the two encryption types shown LEAP+WEP Combines the two encryption types shown Static CKIP Cisco Key Integrity Protocol WPA Wi-Fi Protected Access protocol WPA/PSK Combines WPA with Pre-Shared Key encryption WPA2 Wi-Fi Protected Access 2 encryption WPA2/PSK Combines the two encryption methods shown xsec FIPS-compliant encryption including Layer 2 header info 6. Locate the EAP Options area on the Groups > SSIDs page, and complete the settings. Table 59 describes the settings and default values. Table 59 Groups > SSIDs > EAP Options Section Field and Default Value Setting Default Description WEP Key Rotation Interval 120 Time (in seconds) between WEP key rotation on the AP. 7. Locate the RADIUS Authentication Servers area on the Groups > SSIDs configuration page and define the settings. Table 60 describes the settings and default values. Table 60 Groups > SSIDs > RADIUS Authentication Servers Fields and Default Values Setting Default Description RADIUS Authentication Server 1-3 (Cisco WLC, Proxim only) Authentication Profile Name (Proxim Only) Authentication Profile Index (Proxim Only) None None None Drop-down menu to select RADIUS Authentication servers previously entered on the Groups > RADIUS configuration page. These RADIUS servers dictate how wireless clients authenticate onto the network. Sets the Authentication Profile Name for Proxim AP-600, AP-700, AP- 2000, AP Sets the Authentication Profile Index for Proxim AP-600, AP-700, AP- 2000, AP Select Save when the security settings and configurations in this procedure are complete. You may need to return to the Groups > Security configuration page to configure or reconfigure RADIUS servers. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 87

88 9. Locate the RADIUS Accounting Servers area on the Groups > SSIDs configuration page and define the settings. Table 61 describes the settings and default values. Table 61 Groups > SSIDs > Radius Accounting Servers Fields and Default Values Setting Default Description RADIUS Accounting Server 1-3 (Cisco WLC, Proxim Only) Accounting Profile Name (Proxim Only) Accounting Profile Index (Proxim Only) None None None Pull-down menu selects RADIUS Accounting servers previously entered on the Groups > RADIUS configuration page. These RADIUS servers dictate where the AP sends RADIUS Accounting packets for this SSID/VLAN. Sets the Accounting Profile Name for Proxim AP-600, AP-700, AP-2000, AP Sets the Accounting Profile Index for Proxim AP-600, AP-700, AP-2000, AP Select Save to retain these Security configurations for the group, select Save and Apply to make the changes permanent, or select Revert to discard all unapplied changes. 11. Continue with additional security-related procedures in this document for additional RADIUS, and SSID settings for device groups, as required. Configuring Radio Settings for Device Groups The Groups > Radio configuration page allows you to specify detailed RF-related settings for devices in a particular group. If you have existing deployed devices, you may want to use the current RF settings on those devices as a guide for configuring the settings in your default Group. Perform the following steps to define RF-related radio settings for groups. 1. Go to the Groups > List page and select the group for which to define radio settings by selecting the group name. Alternatively, select Add from the Groups > List page to create a new group, define a group name. In either case, the Monitor page appears. 2. Go to the Groups > Radio page. Figure 48 illustrates this page. 88 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

89 Figure 48 Groups > Radio Page Illustration 3. Locate the Radio Settings area and adjust these settings as required. Table 62 describes the settings and default values. Table 62 Groups > Radio > Radio Settings Fields and Default Values Setting Default Description Allow Automatic Channel Selection (2.4, 5, and 4.9GHz Public Safety) b Data Rates (Mbps) Frag Threshold Enabled No Required: Optional: No If enabled, whenever the AP is rebooted it uses its radio to scan the airspace and select its optimal RF channel based on observed signal strength from other radios. NOTE: If you enable this feature, OV3600 automatically reboots the APs in the group when the change is implemented. Displays pull-down menus for various data rates for transmitting data. NOTE: This setting does not apply to Cisco LWAPP devices. The three values in each of the pull-down menus are as follows: Required The AP transmits only unicast packets at the specified data rate; multicast packets are sent at a higher data rate set to optional. (Corresponds to a setting of yes on Cisco devices.) Optional The AP transmits both unicast and multicast at the specified data rate. (Corresponds to a setting of basic on Cisco devices.) Not Used The AP does not transmit data at the specified data rate. (Corresponds to a setting of no on Cisco devices.) If enabled, this setting enables packets to be sent as several pieces instead of as one block. In most cases, leave this option disabled. Threshold Value 2337 If Fragmentation Threshold is enabled, this specifies the size (in bytes) at which packets are fragmented. A lower Fragmentation Threshold setting might be required if there is a great deal of radio interference. RTS/CTS Threshold Enabled RTS/CTS Threshold Value RTS/CTS Maximum Retries No If enabled, this setting configures the AP to issue a RTS (Request to Send) before sending a packet. In most cases, leave this option disabled If RTS/CTS is enabled, this specifies the size of the packet (in bytes) at which the AP sends the RTS before sending the packet. 32 If RTS/CTS is enabled, this specifies the maximum number of times the AP issues an RTS before stopping the attempt to send the packet through the radio. Acceptable values range from 1 to 128. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 89

90 Table 62 Groups > Radio > Radio Settings Fields and Default Values (Continued) Setting Default Description Maximum Data Retries Beacon Period ( msec) 32 The maximum number of attempts the AP makes to send a packet before giving up and dropping the packet. Acceptable values range from 1 to Time between beacons (in microseconds). DTIM Period (1-255) 2 DTIM alerts power-save devices that a packet is waiting for them. This setting configures DTIM packet frequency as a multiple of the number of beacon packets. The DTIM Interval indicates how many beacons equal one cycle. Ethernet Encapsulation RFC1042 This setting selects either the RFC1042 or 802.1h Ethernet encapsulation standard for use by the group. Radio Preamble Long This setting determines whether the APs uses a short or long preamble. The preamble is generated by the AP and attached to the packet prior to transmission. The short preamble is 50 percent shorter than the long preamble and thus may improve wireless network performance. NOTE: Because older WLAN hardware may not support the short preamble, the long preamble is recommended as a default setting in most environments. 4. Certain wireless access points offer proprietary settings or advanced functionality that differ from prevailing industry standards. If you use these APs in the device group, you may wish to take advantage of this proprietary functionality. To configure these settings, locate the proprietary settings areas on the Groups > Radio page and continue with the additional steps in this procedure. Proprietary settings are only applied to devices in the group from the specific vendor and are not configured on devices from vendors that do not support the functionality. 5. To configure settings specific to the Proxim AP-600, AP-700, AP-2000, AP-4000; Avaya AP-3/4/5/6//7/8, and ProCurve 520WL, locate the appropriate section of Groups > Radio page and define the required fields. Table 63 describes the settings and default values. Table 63 Groups > Radio > Proxim AP-600, AP-700, AP-2000, AP-4000; Avaya AP-3, Avaya AP-7, AP-4/5/6, AP- 8; ProCurve520WL Fields and Default Values Setting Default Description Load Balancing No If enabled, this setting allows client devices associating to an AP with two radio cards to determine which card to associate with, based on the load (# of clients) on each card. NOTE: This feature is only available when two b wireless cards are used in an AP Interference Robustness Distance Between APs g Operational Mode abg Operational Mode b Transmit Rate No Large b g b g Auto Fallback If enabled, this option will fragment packets greater than 500 bytes in size to reduce the impact of radio frequency interference on wireless data throughput. This setting adjusts the receiver sensitivity. Reducing receiver sensitivity from its maximum may help reduce the amount of crosstalk between wireless stations to better support roaming users. Reducing the receiver sensitivity, user stations will be more likely to connect with the nearest access point. This setting sets the operational mode of all g radios in the group to either b only, g only or b + g. This setting sets the operational mode of all a/b/g radios in the group to either a only, b only, g only or b + g. This setting specifies the minimum transmit rate required for the AP to permit a user device to associate. 90 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

91 Table 63 Groups > Radio > Proxim AP-600, AP-700, AP-2000, AP-4000; Avaya AP-3, Avaya AP-7, AP-4/5/6, AP- 8; ProCurve520WL Fields and Default Values (Continued) Setting Default Description g Transmit Rate a Transmit Rate Auto Fallback Auto Fallback This setting specifies the minimum transmit rate required for the AP to permit a user device to associate. This setting specifies the minimum transmit rate required for the AP to permit a user device to associate. Rogue Scanning Yes If enabled, any ORiNOCO or Avaya APs in the group (with the appropriate firmware) will passively scan for rogue access points at the specified interval. This rogue scan will not break users' association to the network. NOTE: This feature can affect the data performance of the access point. Rogue Scanning Interval 15 minutes If rogue scanning is enabled, this setting controls the frequency with which scans are conducted (in minutes). Frequent scans provide the greatest security, but AP performance and throughput available to user devices may be impacted modestly during a rogue scan. 6. To configure settings specific to Proxim 4900M, locate the Proxim 4900M section and define the required fields. Table 64 describes the settings and default values. Table 64 Groups > Radio > Proxim 4900M Fields and Default Values Setting Default Description 4.9GHz Public Safety Channel Bandwidth a/4.9GHz Public Safety Operational Mode 20 This setting specifies the channel bandwidth for the 4.9 GHz radio. It is only applicable if you are running the a/4.9GHz radio in 4.9GHz mode a This setting specifies if the AP will run the a/4.9GHz radio in a mode or in 4.9 GHz mode. Please note that 4.9 GHz is a licensed frequency used for public safety. 7. To configure Symbol-only settings, locate the Symbol section and define the required fields. Table 65 describes the settings and default values. Table 65 Groups > Radio > Symbol Fields and Default Values Setting Default Description Rogue Scanning Yes If enabled, Symbol access points with or later firmware in the group will passively scan for rogue access points at the specified interval. This rogue scan will not break a user s association to the network. Rogue Scanning Interval (5-480 min) 240 If rogue scanning is enabled, this setting controls the frequency with which scans are conducted (in minutes). Frequent scans provide the greatest security, but AP performance and throughput available to user devices may be impacted modestly during a rogue scan. 8. Select Save when radio configurations as described above are complete, select Save and Apply to make the changes permanent, or select Revert to discard all unapplied changes. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 91

92 Cisco WLC Group Configuration The Groups > Cisco WLC Config page consolidates the settings for Cisco WLC devices from all group pages. The Groups > SSIDs subtab applies to all device types except for Cisco WLC, which have WLANs configured on the Cisco WLC Config page. It is not recommended to have Symbol 4131 and Proxim APs in the same group as Cisco devices. Also, it is recommended that users set device preferences to Only devices in this group. This topic describes how to access and navigate the Groups > Cisco WLC Config page. Accessing Cisco WLC Configuration Go to the Cisco WLC Config page in one of these two ways: 1. In Groups > List, select a group that has been defined to support Cisco devices and the Cisco WLC Config option appears in the subtabs. 2. In Groups > List, create a new group to support Cisco devices with these steps: Select Add from the Groups > List page to create a new group, enter a group name, and select Add. Once OV3600 prompts you with the Groups > Basic page, ensure that you enable device-specific settings for Cisco WLC. Once you select Save or Save and Apply, then the Groups > Cisco WLC Config subtab appears in the navigation pane at the top in association with that group. Navigating Cisco WLC Configuration The navigation pane on the left side of the Groups > Cisco WLC Config page is expandable, and displays the Cisco configurations supported and deployed. Figure 49 and Figure 50 illustrate this navigation pane. You can pre-populate the group WLC settings from a controller in the same group by performing an import on the controller s Audit page. Figure 49 Groups > Cisco WLC Config Page Illustration, collapsed view Figure 50 Groups > Cisco WLC Config Page Illustration, expanded view 92 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

93 Configuring WLANs for Cisco WLC Devices In Cisco WLC Config, WLANs are based on SSIDs or VLANs that are dedicated to Cisco WLC controllers. Perform the following steps to define and configure WLANs for Cisco WLC controllers. 1. Go to the Groups > Cisco WLC Config page, and select WLANs in the navigation pane at left. This page displays the SSIDs or VLANs that are available for use with Cisco WLC devices, and enables you to define new SSIDs or VLANs. Figure 51 illustrates this page. 2. To change the ID/position of a WLAN on the controller by dragging and dropping, set the toggle to yes. Note that the by setting this flag to yes, OV3600 will display a mismatch if the WLANs in the desired and device config differ only on the order. Figure 51 Groups > Cisco WLC Config > WLANS page illustration 3. To add or edit SSIDs or VLANs that are dedicated to Cisco WLC devices, either select the Add New SSID/VLAN button, or select the pencil icon for an existing SSID/VLAN. A new page appears comprised of four tabs, as follows: General Defines general administrative parameters for the Cisco WLC WLAN. Security Defines encryption and RADIUS servers. QoS Defines quality of service (QoS) parameters for the Cisco WLC WLAN. Advanced Defines advanced settings that are available only with Cisco WLC devices, for example, AAA override, coverage, DHCP and DTIM period. Refer to Cisco documentation for additional information about Cisco WLC devices and related features. Figure 52 Groups > Cisco WLC Config > WLANs > Add New SSID/VLAN > General Tab Illustration OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 93

94 Figure 53 Groups > Cisco WLC Config > WLANs > Add New SSID/VLAN > Security Tab Illustration Figure 54 Groups > Cisco WLC Config > WLANs > Add New SSID/VLAN > QoS Tab Illustration Figure 55 Groups > Cisco WLC Config > WLANs > Add New SSID/VLAN > Advanced Tab Illustration 94 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

95 Defining and Configuring LWAPP AP Groups for Cisco Devices The Groups > Cisco WLC Config > WLANs > Advanced > AP Groups page allows you to add/edit/ delete AP Groups on the Cisco WLC. LWAPP AP Groups are used to limit the WLANs available on each AP. Cisco thin APs are assigned to LWAPP AP Groups. Viewing and Creating Cisco AP Groups 1. Go to the Groups > Cisco WLC Config page, and select WLANs > Advanced > AP Groups in the navigation pane at left. This page displays the configured LWAPP APs. Figure 56 illustrates this page. Figure 56 Groups > Cisco WLC Config > WLANS > Advanced > AP Groups Page Illustration 2. To add a new LWAPP AP group, select Yes in the AP Groups section. Additional controls appear. 3. Select Add to create a new LWAPP AP group. To edit an existing LWAPP AP group, select the pencil icon next to that group. Add one or more SSIDs and the interface/vlan ID mapping on the Add/Edit page of the LWAPP AP Group. 4. Select Save and Apply to make these changes permanent, or select Save to retain these changes to be pushed to controllers at a later time. Configuring Cisco Controller Settings The Groups > Cisco WLC Config > Controller page defines general Cisco WLC settings, Multicast settings, Cisco mobility groups to be supported on Cisco controllers, Network Transfer Protocol (NTP), and Spanning Tree Protocol settings. Go to the Groups > Cisco WLC Config > Controller page. This navigation is illustrated in Figure 57. Figure 57 Groups > Cisco WLC Config > Controller Navigation OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 95

96 Configuring Wireless Parameters for Cisco Controllers This section illustrates the configuration of Wireless settings in support of Cisco WLC controllers. The navigation for Wireless settings is illustrated in Figure 58. Figure 58 Groups > Cisco WLC Config > Wireless Navigation Illustration Configuring Cisco WLC Security Parameters and Functions OV3600 enables you to configure many security settings that are specific to Cisco WLC controllers. This section supports four overriding types of configuration, as follows: AAA, to cover both RADIUS and TACACS+ server configuration Priority Order Wireless Protection Policies Web Auth Figure 59 illustrates these components and this navigation: Figure 59 Groups > Cisco WLC Config > Security Navigation Illustration Configuring Management Settings for Cisco WLC OV3600 allows you to configure of SNMP and Syslog Server settings for Cisco WLC controllers. You can configure up to four trap receivers on the Cisco WLC including the OV3600 IP that can be used in Global Groups. To define SNMP and server settings, go to the Groups > Cisco WLC Config > Management page, illustrated in Figure Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

97 Figure 60 Groups > Cisco WLC Config > Management Navigation Illustration Configuring Group PTMP Settings The Groups > PTMP configuration page configures Point-to-Multipoint (PTMP) for all subscriber and base stations in the device group. Subscriber stations must be in the same group as all base stations with which they might connect. Perform the following steps to configure these functions. 1. Go to the Groups > List page and select the group for which to define PTMP settings by selecting the group name. Alternatively, select Add from the Groups > List page to create a new group, define a group name. In either case, the Monitor page appears. 2. Select the PTMP tab in the OV3600 navigation menu. Figure 61 illustrates this page. Figure 61 Groups > PTMP Page Illustration 3. Define the settings on this page. Table 66 describes the settings and default values. Table 66 Groups > PTMP Fields and Default Values Setting Default Description a Radio Channel 58 Selects the channel used for a radios by the devices in this group g Radio Channel 10 Selects the channel used for g radios by the devices in this group. Channel Bandwidth 20 Defines the channel bandwidth used by the devices in this group. Network Name Wireless Network Sets the Network name, with a range of length supported from two to 32 alphanumeric characters. Network Secret None Sets a shared password to authenticate clients to the network. 4. Select Save and Apply when configurations are complete to make them permanent, or select Save to retain these settings prior to pushing to controllers at a later time. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 97

98 Configuring Proxim Mesh Radio Settings 1. Go to the Groups > Proxim Mesh configuration page to configure Mesh-specific radio settings. 2. Define the settings as required for your network. Figure 62 illustrates this page. Table 67 and Table 68 describe the settings and default values. Figure 62 Groups > Proxim Mesh Page Illustration The General section contains settings for mesh radio, number of mesh links, RSSI smoothing, roaming threshold and de-auth client. Table 67 Groups > Proxim Mesh > General Fields and Default Values Setting Default Description Mesh Radio 4.9/5Ghz Drop-down selects the radio that acts as the backhaul to the network. Maximum Mesh Links Neighbor RSSI Smoothing 6 Sets the maximum number of mesh links allowed on an AP. This number includes the uplink to the portal as well as downlinks to other mesh APs. 16 Specifies the number of beacons to wait before switching to a new link. Roaming Threshold 80 Specifies the difference in cost between two paths that must be exceeded before the AP roams. To switch to a new path it must have a cost that is less by at least the roaming threshold. A high threshold results in fewer mesh roams. Deauth Client when Uplink is Down Yes With Yes selected, clients have authentication removed (are deauthenticated) if the uplink is lost. The Security section contains settings for SSID and enabling AES encryption. Table 68 Groups > Proxim Mesh > Security Fields and Default Values Setting Default Description SSID None Sets the SSID used by the Mesh Radio to connect to the mesh network. Enable AES No Enable or disable AES encryption. 3. The Mesh Cost Matrix configuration section contains settings for hop factor and maximum hops to portal, RSSI factor and cut-off, medium occupancy factor and current medium occupancy weight. Adjust these settings as required for your network. Table 69 describes these settings and default values. Table 69 Groups > Proxim Mesh > Mesh Cost Matrix Fields and Default Values Setting Default Description Hop Factor 5 Sets the factor associated with each hop when calculating the best path to the portal AP. Higher factors will have more impact when deciding the best uplink. Maximum Hops to Portal 4 Set the maximum number of hops for the AP to reach the Portal AP. 98 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

99 Table 69 Groups > Proxim Mesh > Mesh Cost Matrix Fields and Default Values (Continued) Setting Default Description RSSI Factor 5 Sets the factor associated with the RSSI values used when calculating the best path to the portal AP. Higher factors will have more impact when deciding the best uplink. RSSI Cutoff 10 Specifies the minimum RSSI needed to become a mesh neighbor. Medium Occupancy Factor Current Medium Occupancy Weight 5 Sets the factor associated with Medium Occupancy when calculating the best path to the portal AP. Higher factors will have more impact when deciding the best uplink. 7 Specifies the importance given to the most recently observed Medium Occupancy against all of the previously viewed medium occupancies. Lower values place more importance on previously observed Medium Occupancies. 4. Select Save when configurations are complete to retain these settings. Select Save and Apply to make the changes permanent, or select Revert to discard all unapplied changes. Configuring Group MAC Access Control Lists This configuration is optional. If you use Symbol, Proxim, or ProCurve 520WL wireless access points, OV3600 enables you to specify the MAC addresses of devices that are permitted to associate with APs in the Group. Other devices are not able to associate to APs in the Group, even if the users of those devices are authorized users on the network. Perform the following steps to use the MAC ACL function. 1. Browse to the Groups > MAC ACL configuration page. Figure 63 illustrates this page. Figure 63 Groups > MAC ACL Page Illustration 2. Select Yes on the Use MAC ACL drop-down menu. Enter all authorized MAC addresses, separated by white spaces. 3. Select Save when configurations are complete to retain these settings. Select Save and Apply to make the changes permanent, or select Revert to discard all unapplied changes. Specifying Minimum Firmware Versions for APs in a Group This configuration is optional. OV3600 allows you the option of defining the minimum firmware version for each AP type in a group on the Groups > Firmware configuration page. At the time that you define the minimum version, OV3600 automatically upgrades all eligible APs. When you add APs into the group in the future, you will be able to upgrade APs manually. The firmware for an AP is not upgraded automatically when it is added to a group. Perform the following steps to make this firmware configuration. 1. Browse to the Groups > Firmware configuration page. Figure 64 illustrates this page. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 99

100 Figure 64 Groups > Firmware Page Illustration 2. For each device type in the group, specify the minimum acceptable firmware version. If no firmware versions are listed, go to the Device Setup > Upload Firmware & Files configuration page to upload the firmware files to OV Select Upgrade to apply firmware preferences to devices in the group. 4. Select Save to save the firmware file as the desired version for the group. 5. If you have opted to assign an external TFTP server on a per-group basis on the Device Setup > Upload Firmware & Files configuration page, you can enter the IP address in the Firmware Upgrade Options field on the top of this configuration page. 6. Once you have defined your first group, you can configure that group to be the default group on your network. When OV3600 discovers new devices that need to be assigned to a management group, the default group appears at the top of all drop-down menus and lists. Newly discovered devices are place automatically in the default group if OV3600 is set to Automatically Monitor/Manage New Devices on the OV3600 configuration page. 7. Browse to the Groups > List configuration page. 8. From the list of groups, check the Default radio button next to the desired default group to make it the default. Comparing Device Groups You can compare two existing device groups with a detailed line-item comparison. Group comparison allows several levels of analysis to include the following: compare performance, bandwidth consumption, or troubleshooting metrics between two groups debug one device group against the settings of a similar and better performing device group use one group as a model by which to fine-tune configurations for additional device groups This topic presumes that at least two device groups are at least partly configured in OV3600, each with saved configurations. Perform the following steps to compare two existing device groups: 1. From the Groups > List page, select Compare two groups. Two drop-down menus appear. 2. Select the two groups to compare to each other in the drop-down menus, and select Compare. The Compare page appears, displaying some or many configuration categories. Figure 65 illustrates this page. 100 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

101 Figure 65 Comparing Two Devices Groups on the Groups > List > Compare Page (Partial View) 3. Note the following factors when using the Compare page: The Compare page can be very long or very abbreviated, depending on how many configurations the device groups share or do not share. When a configuration differs between two groups, the setting is flagged in red text for the group on the right. The default setting of the Compare page is to highlight settings that differ between two groups. To display settings that are similar or identical between two device groups, select Show Similar Fields at the top left of the page. The result may be a high volume of information. Select Hide Similar Fields to return to the default display, emphasizing configuration settings that differ between two groups. You can change the configuration for either or both groups by selecting Edit in the corresponding column heading. The appropriate configuration page appears. If you make and save changes to either or both groups, go back to the Groups > List page and select Compare two groups. Select the same two groups again for updated information. Additional topics in this document describe the many fields that can appear on the Groups > List > Compare page. Deleting a Group Perform the following steps to delete an existing Group from the OV3600 database: 1. Browse to the Groups > List configuration page. 2. Ensure that the Group you wish to delete is not marked as the default group. OV3600 does not permit you to delete the current default Group. 3. Ensure that there are no devices in the Group you wish to delete. OV3600 does not permit you to delete a Group that still contains managed devices. You must move all devices to other Groups before deleting a Group. 4. Ensure that the Group is not a Global Group which has Subscriber Groups, and is not a Group that was pushed from a Master Console. OV3600 will not delete a Group in which either of those is true. 5. Select the checkbox and select Delete. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 101

102 Changing Multiple Group Configurations Perform the following steps to make any changes to an existing group's configuration: 1. Browse to the Groups > List configuration page. 2. Select the Manage link (the pencil icon) for the group you wish to edit. The Groups > Basic configuration page appears. 3. Select the fields to be edited on the Basic configuration page or go to Radio, Security, VLANs, or MAC ACL configuration page and edit the fields. Use the Save button to store the changes prior to applying them. 4. When all changes for the group are complete select the Save and Apply button to make the changes permanent. Figure 66 illustrates the confirmation message that appears. Figure 66 Groups > Basic Configuration Change Confirmation Page Illustration 5. OV3600 displays a Configuration Change screen confirming the changes that will be applied to the group's settings. 6. There are several action possibilities from within this confirmation configuration page. Apply Changes Now Applies the changes immediately to access points within the group. If you wish to edit multiple groups, you must use the Preview button. You cannot apply Alcatel-Lucent Config changes to other groups. If the only changes on the configuration page are to Alcatel-Lucent devices, the list of groups and the preview button will not appear. Schedule Schedules the changes to be applied to this group in the future. Enter the desired change date in the Start Date/Time field. OV3600 takes the time zone into account for the group if a time zone other than OV3600 System Time has been configured on the Groups > Basic configuration page. Cancel Cancels the application of changes (immediately or scheduled). To completely nullify the change request, select Revert on one of the group configuration pages after you have selected Cancel. 7. Apply changes to multiple groups by selecting the appropriate group or groups and selecting Preview. 102 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

103 Modifying Multiple Devices OV3600 provides a very powerful utility that modifies all APs or a subset of access points unrelated to the typical OV3600 group construct. This utility provides the ability to delete simultaneously multiple devices, migrate multiple devices to another group and/or folder, update credentials and optimize channels. Perform these steps to modify multiple devices. 1. To modify multiple devices, go to one of the following pages with a device list: APs/Devices > List APs/Devices > Up APs/Devices > Down APs/Devices > Mismatched Groups > Monitor configuration pages Each of these pages displays a list of devices. Controller monitoring pages also have lists of their thin APs which can be modified using Modify Devices. 2. Select Modify Devices to make the checkboxes at the left of all devices appear. In addition, a new section appears in this page location to display various settings that can be configured for multiple devices at one time (some operations cannot be performed on the selected devices). Figure 67 illustrates this page. Figure 67 Modify Multiple Devices Section Illustration OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 103

104 3. Select one or more devices that are to share the configurations. Select the checkbox for each device to modify. 4. In the Modify Multiple Devices section, select any button or use any drop-down menu for the supported changes. Any action you take applies to all selected devices. Each action you take will direct you to a new configuration page, or prompt you with a confirmation page to confirm your changes. 5. You are taken to a confirmation configuration page that allows you to schedule the change for a time in the future. Enter a start date and time in the scheduling field and select when the change should occur from the drop-down menu (one time is the default, but you may select recurring options for many of the actions). Scheduled jobs can be viewed and edited in the System > Configuration Change Jobs tab. 6. Using the neighbor lists, OV3600 is able to optimize channel selection for APs. Select the APs to optimize and OV3600 minimizes the channel interference while giving channel priority to the most heavily used APs. Table 70 describes these actions and controls. Table 70 Modify Multiple Devices Section Fields and Default Values Action OV3600 Group/Folder Alcatel-Lucent AP Group Management Level Planned Maintenance Mode Desired Radio Status Update Cisco Thin AP Settings Poll now Audit selected devices Run report on selected devices Update the credentials OV3600 uses to communicate with these devices Add Maintenance Window Delete all Maintenance Windows Description Move the selected devices to a new group or folder. If the AP is in managed mode when it is moved to a new group, it will be reconfigured. Moves the selected APs to a new group or folder. If the AP is in managed mode when it is moved to a new group it will be reconfigured. Move the selected devices into Monitor Only or Manage Read/Write Mode. Puts the selected devices into Planned Maintenance. During the maintenance mode, no AP Down triggers will be deployed on these devices. Users will not be able to delete folders that contain devices in Planned Maintenance. The devices in Planned Maintenance will show the Up status, but will not be tracked in historical graphs and logs as Up. Enables or disables the radios on the selected device. Does not apply Cisco IOS APs. Bulk configuration for per-thin AP settings, previously configured on the Group LWAPP AP tab, can be performed from Modify Devices on the APs/Devices List page. Make changes to LWAPP AP groups, including the option that was under Modify Devices. Polls selected devices for current user count and bandwidth data; overrides default poll settings for the group. Polling numerous devices may create a temporary performance load on your OV3600 server. Fetches the current configuration from the device and compares it to the desired OV3600 configuration. The audit action updates the Configuration Status. NOTE: In versions of OV3600 previous to 7.3, the Audit button appeared on Groups > List for groups with audit disabled. Now, if a group has audit disabled for its devices, OV3600 doesn't show the Audit button in the Modify devices list. Takes you to the Reports > Definitions page where you can define or run a custom report for selected devices. For more details and a procedure, see Using Custom Reports on page 232. Update changes the credentials OV3600 uses to communicate with the device. It does not change the credentials on the AP. Automate the manual action of putting the selected devices into Manage mode at once so that changes can be applied, and after the maintenance period is over, the devices automatically revert to Monitor-Only mode. Maintenance windows can be set as a one-time or recurring event. Deletes all maintenance windows set for these devices. 104 Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

105 Table 70 Modify Multiple Devices Section Fields and Default Values (Continued) Action Import settings from selected devices (and discard current predevice desired settings) Reboot selected devices Reprovision selected Alcatel-Lucent devices Upgrade firmware for selected devices Cancel firmware upgrade for selected devices Rename devices Delete selected devices from OV3600 Description Audit updates a number of the AP specific settings OV3600 initially read off of the AP including channel, power, antenna settings and SSL certifications. OV3600 recommends using this setting if APs have been updated outside of OV3600. Most settings on the APs/Devices Manage configuration page are set to the values currently read off of the devices. Reboots the selected devices. Use caution when rebooting devices because this can disrupt wireless users. Configures the switch to send provisioning parameters such as radio, antenna, and IP address settings to the selected APs. Please note that APs will be rebooted as part of reprovisioning. Upgrades firmware for the selected devices. Refer to the firmware upgrade help under APs/Devices > Manage configuration page for detailed help on Firmware job options. Cancels any firmware upgrades that are scheduled or in progress for the selected APs. Rename all the selected devices in bulk. Note that you can also rename the devices one at a time using the editable Name fields in each row. Removes the selected APs from OV3600. The deletes will be performed in the background and may take a minute to be removed from the list. Using Global Groups for Group Configuration To apply group configurations using the OV3600 Global Groups feature, first go to the Groups > List configuration page. Select Add to add a new group, or select the name of the group to edit settings for an existing group. Select the Duplicate icon (usually near the last column of the list) to create a new group with identical configuration to an existing group. To have Global Group status, a group must contain no devices; accordingly, access points can never be added to a Global Group. Global groups are visible to users of all roles, so they may not contain devices, which can be made visible only to certain roles. Figure 68 illustrates the Groups > List page. Figure 68 Groups > List Page Illustration To set a group as a Global Group, go to the Groups > Basic configuration page for an existing or a newly created group. Select Yes for the Is Global Group field under the Global Group section. When the change is saved and applied, the group will have a checkbox next to fields. Figure 69 illustrates this configuration page. OmniVista 3600 Air Manager 7.4 User Guide Configuring and Using Device Groups 105

106 Figure 69 Groups > Basic Page for a Global Group (partial view) When a Global Group configuration is pushed to Subscriber Groups, all settings are static except for settings with the checkbox selected; for fields with checkboxes selected, the value or setting can be changed on the corresponding tab for each managed group. In the case of the Groups > SSIDs configuration page, override options are available only on the Add configuration page (go to the Groups > SSIDs configuration page and select Add). Global templates are also configurable as part of Global Groups; for more information, see Creating and Using Templates on page 153. Once Global Groups have been configured, groups may be created or configured to subscribe to a particular Global Group. Go to the Groups > Basic configuration page of a group and locate the Use Global Groups section. Select the Yes radio button and select the name of the Global Group from the drop-down menu. Then select Save and Apply to make the changes permanent. Figure 70 illustrates this page. Figure 70 Groups > Basic > Managed Page Illustration Once the configuration is pushed, the unchecked fields from the Global Group appears on the Subscriber Group as static values and settings. Only fields that had the override checkbox selected in the Global Group appear as fields that can be set at the level of the Subscriber Group. Any changes to a static field must be made on the Global Group. If a Global Group has Subscriber Groups, it cannot be changed to a non-global Group. A Global Group without Subscriber Groups can be changed to a regular Group by updating the setting on the Groups > Basic configuration interface. The Global Groups feature can also be used with the Master Console. For more information about this feature, refer to Supporting OV3600 Servers with the Master Console on page Configuring and Using Device Groups OmniVista 3600 Air Manager 7.4 User Guide

107 Chapter 5 Discovering, Adding, and Managing Devices This chapter describes how to add, configure, and monitor wired and wireless devices, and contains the following sections corresponding to features of the Device Setup and APs/Devices tabs: Device Discovery Overview on page 107 Discovering and Adding Devices on page 107 Monitoring Devices on page 116 Configuring and Managing Devices on page 134 Troubleshooting a Newly Discovered Down Device on page 146 Setting up Alcatel-Lucent Spectrum Analysis in OV3600 on page 148 Device Discovery Overview Once you have deployed OV3600 on the network, the next step is to discover all existing devices connected to your network. OV3600 allows device discovery in the following ways, all of which are described in this chapter: SNMP/HTTP discovery scanning This is the primary method to discover devices on your network, configured in the Device Setup > Discover page. See SNMP/HTTP Scanning on page 108. Cisco Discovery Protocol (CDP) OV3600 enhances support for CDP by discovering a Cisco device s CDP neighbors. See Enabling Cisco Discovery Protocol (CDP) on page 111. Manual device entry This admin-supported method of discovery applies when you know of devices that are already on your network. See the following sections for information and procedures: Manually Adding Individual Devices on page 112 Adding Multiple Devices from a CSV File on page 114 Adding Universal Devices on page 115 Controller-driven device discovery Thin APs will automatically be discovered in the network and added to the New Devices list when you add their controller to OV3600. To add the thin APs, refer to Authorizing Devices to OV3600 from APs/Devices > New Page on page 111. Discovering and Adding Devices This section describes the following topics: SNMP/HTTP Scanning Enabling Cisco Discovery Protocol (CDP) Authorizing Devices to OV3600 from APs/Devices > New Page Manually Adding Individual Devices OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 107

108 SNMP/HTTP Scanning SNMP/HTTP discovery scanning is the primary method for discovering devices on your network, including rogue devices. Enable this scanning method from the Device Setup > Discover page. This page is only visible to users with the AMP Administrator role, or roles that have Allow authorization of APs/ Devices enabled in OV3600 Setup > Roles. SNMP/HTTP scanning information is provided in these sections: Adding Networks for SNMP/HTTP Scanning explains how to enable networks that have been defined for scanning. Adding Credentials for Scanning explains how to define network credentials for scanning. Credentials must be defined before using them in scan sets. Defining a Scan Set explains how to create a scan set by combining networks and credentials when scanning for devices. Running a Scan Set provides a procedure for running a scan set. Adding Networks for SNMP/HTTP Scanning The first step when enabling SNMP/HTTP scanning for devices is to define the network segments to be scanned. Perform these steps. 1. Go to the Device Setup > Discover page, and locate the Networks section. 2. In the Networks section, select Add New Scan Network. The Scan Network page appears, as shown in Figure 71. Alternatively, you can edit an existing scan network by selecting the corresponding pencil icon. The New/Edit Networks page also appears in this instance. Figure 71 Device Setup > Discover > New Network Section Illustration 3. In the Name field, provide a name for the network to be scanned (for example, Accounting Network). 4. In the Network field, define the IP network range, or the first IP address on the network, to be scanned. One example would be Enter the Subnet Mask for the network to be scanned (for example, ). The largest subnet OV3600 supports is Select Add. 7. Repeat these steps to add as many networks for which to enable device scanning. All network segments configured in this way appear in the Network section of the Device Setup > Discover page. 8. Complete the configuration of scan credentials, then combine scan networks and scan credentials to create scan sets. The next two procedures in this section describe these tasks. Adding Credentials for Scanning The next step in SNMP/HTTP device discovery is to define the scan credentials that govern scanning of a given network. New APs inherit scan credentials from the System Credentials that you configure on the Device Setup > Communications page. Perform these steps to define scan credentials for SNMP/HTTP scanning: 108 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

109 1. Locate the Credentials section on the Device Setup > Discover page. This page displays scan sets, networks, and credentials that have been configured so far, and allows you to define new elements for device scanning. 2. To create a new scan credential, select Add New Scan Credential. Figure 72 illustrates this page. Figure 72 Device Setup > Discover > Add/Edit New Scan Credential Section Illustration 3. Enter a name for the credential in the Name field (for example, Default). This field supports alphanumeric characters, both upper and lower case, blank spaces, hyphens, and underscore characters. 4. Choose the type of scan to be completed (SNMPv1, SNMPv2, or HTTP). In most cases, perform scans using SNMP for device discovery, but consider the following factors in your decision: SNMPv1 and SNMP v2 differ between in their supported traps, supported MIBs, and network query elements used in device scanning. HTTP discovers devices using the HyperText Transfer Protocol in communications between servers and additional network components. HTTP is not as robust in processing network events as is SNMP, but HTTP may be sufficient, simpler, or preferable in certain scenarios. 5. Define and confirm the Community String to be used during scanning. In this section, the community string used can be either read-only or read/write, as OV3600 only uses it for discovering APs. To bring APs under management, OV3600 uses the credentials supplied in the Device Setup > Communication SNMP section. Once the device is authorized, it will use the non-scanning credentials. OV3600 automatically appends the type of scan (SNMP or HTTP) to the Label. 6. Select Add. The Device Setup > Discover page displays the new scan credential or credentials just created or edited. 7. Repeat these steps to add as many credentials as you require. 8. Once scan networks and scan credentials are defined, combine them by creating scan sets using the next procedure: Defining a Scan Set on page 109. Defining a Scan Set Once you have defined at least one network and one scan credential, you can create a scan set that combines the two for device discovery. Perform these steps to create a scan set. 1. Locate the Scan Set area at the top of the Device Setup > Discover page. 2. Select Add New Scan Set to see all scan components configured so far. If you wish to create a new network, or new scanning credentials, you can select Add in either of these fields to create new components prior to creating a scan set. 3. Select the Network(s) to be scanned and the Credential(s) to be used. OV3600 defines a unique scan for each Network-Credential combination. 4. In the Automatic Authorization section, select whether to override the global setting in OV3600 Setup > General and have New Devices be automatically authorized into the New Device List, the same Group/Folder as the discovering devices, the same Group/Folder as the closest IP neighbor, and/or a specified auto-authorization group and folder. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 109

110 5. Select Add to create the selected scans, which then appear in a list at the top of the Device Setup > Discover page. 6. To edit an existing scan, select the pencil icon next to the scan on the Device Setup > Discover page. 7. When ready, proceed to the next task, Running a Scan Set on page 110. Scheduling an HTTP scan to run daily on your network can help you to discover rogues. Some consumer APs, like most D-Link, Linksys, and NetGear models, do not support SNMP and are found only on the wired side with an HTTP scan. These devices are discovered only if they have a valid IP address. Proper credentials are not required to discover these APs. Wireless scans discover these rogues without any special changes. Running a Scan Set Once a scan has been defined on the Device Setup > Discover page, OV3600 can now scan for devices. Perform these steps. 1. Browse to the Device Setup > Discover page and locate the list of all scan sets that have been defined so far. Figure 73 illustrates this page. Figure 73 Device Setup > Discover Executing a Scan Illustration 2. Check the box next to the scan(s) that you would like to execute. 3. Select Scan to execute the selected scans, and the scan immediately begins. The last column indicates the scan is In Progress. 4. For future scans, select Show Scheduling Options and enter the desired date and time to schedule a future scan. 5. After several minutes have passed, refresh the browser page and view the results of the scan. When the Start and Stop columns display date and time information, the scan is available to display the results. 6. Select the pencil icon for the scan to display the results. Table 71 describes the scan results and related information. Table 71 Device Setup > Discover > Discovery Execution Fields Column Network Credentials Total Devices Found New Devices Found Total Rogues Found New Rogues Found Description Displays the network to be scanned. Displays the credentials used in the scan. Displays the total number of APs detected during the scan that OV3600 can configure and monitor. Total includes both APs that are currently being managed by OV3600 as well as newly discovered APs that are not yet being managed. Displays the number of discovered APs that are not yet managed, but are available. Displays the total number of APs detected during the scan that OV3600 could not configure or monitor. Total includes both APs that have been discovered in earlier scans as well as newly discovered APs from the most recent scan. Displays the number of rogue APs discovered on the most recent scan. 110 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

111 Table 71 Device Setup > Discover > Discovery Execution Fields (Continued) Column Start Stop Scheduled Description Displays the date and time the most recent scan was started. Displays the date and time the scan most recently completed. Displays the scheduled date and time for scans that are scheduled to be run. 7. Go to the APs/Devices > New page to see a full list of the newly discovered devices that the scan detected. Figure 74 illustrates this page. This page is only visible to users with the AMP Administrator role, or roles that have Allow authorization of APs/ Devices enabled in OV3600 Setup > Roles. Figure 74 APs/Devices > New Page Illustration What Next? To authorize one or more devices to a group, see Authorizing Devices to OV3600 from APs/Devices > New Page on page 111. To delete a device altogether from OV3600, select the corresponding check box for each device, and select Delete. Alcatel-Lucent thin APs can have Alcatel-Lucent AP Group specified, and Cisco thin APs can have LWAPP AP Group specified when they are authorized. Enabling Cisco Discovery Protocol (CDP) CDP uses the polling interval configured for each individual Cisco switch or router on the Groups > List page. OV3600 requires read-only access to a router or switch for all subnets that contain wired or wireless devices. The polling interval is specified on the Group > Basic page. Authorizing Devices to OV3600 from APs/Devices > New Page Once you have discovered devices on your network, add these devices to a group and specify whether the device is to be placed in Manage Read/Write or Monitor Only mode. To configure a new group, refer to Configuring and Using Device Groups on page 71. In Manage Read/Write mode, OV3600 compares the device's current configuration settings with the Group configuration settings and automatically updates the device's configuration to match the Group policy. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 111

112 In Monitor Only mode, OV3600 updates the firmware, compares the current configuration with the policy, and displays any discrepancies on the APs/Devices > Audit page, but does not change the configuration of the device. Caution: Put devices in Monitor Only mode when they are added to a newly established device group. This avoids overwriting any important existing configuration settings. Once you have added several devices to the Group, and verified that no unexpected or undesired configuration changes will be made to the devices, you can begin to put the devices in Manage Read/Write mode using the APs/Devices > Manage or the Modify these devices link on any list page. Perform the following steps to add a newly discovered device to a group: 1. Browse to the APs/Devices > New page. The APs/Devices > New page displays all newly discovered devices, the related controller (when known/applicable) and the device vendor, model, LAN MAC Address, IP Address, and the date/time of discovery. 2. Select the group and folder to which the device will be added from the drop-down menu (the default group appears at the top of the Group listing). Devices cannot be added to a Global Group; groups designated as Global Groups cannot contain access points. 3. Select either the Monitor Only or the Manage Read/Write radio button and select Add. At this point, you can go to the APs/Devices > List page and select the folder(s) to which you have assigned one or more devices to verify that your device has been properly assigned. If you wish to assign a device to the Ignored page, or delete it entirely from OV3600, go to step 4. If you select Manage Select Devices, OV3600 automatically overwrites existing device settings with the specified Group settings. Placing newly discovered devices in Monitor mode is strongly recommended until you can confirm that all group configuration settings are appropriate for that device. 4. If you do not wish to manage or monitor a discovered device, you may select the device(s) from the list and select either Ignore or Delete. If you choose to Ignore the devices, they will not be displayed in the APs/Devices > New list, even if they are discovered in subsequent scans. You can view a list of all Ignored devices on the APs/Devices > Ignored page. If you choose to Delete the device, it will be listed on the APs/Devices > New list if discovered by OV3600 in a subsequent scan. Refer to Assigning Devices to the Ignored Page on page 116. Manually Adding Individual Devices Some deployment situations may require that you manually add devices to OV3600. You can add devices manually by uploading a CSV file, or from the Device Setup > Add page. This section describes the following procedures: Adding Devices with the Device Setup > Add Page Adding Multiple Devices from a CSV File Adding Universal Devices Adding Devices with the Device Setup > Add Page Manually adding devices from the Device Setup > Add page to OV3600 is an option for adding all device types. You only need to select device vendor information from a drop down menu for Cisco and Alcatel-Lucent devices, and OV3600 automatically finds and adds specific make and model information into its database. 112 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

113 Perform these steps to manually add devices to OV3600: 1. The first step to add a device manually is to select the vendor and model. Browse to the Device Setup > Add page and select the vendor and model of the device to add. Figure 75 illustrates this page. Figure 75 Device Setup > Add Page Illustration 2. Select Add, and the Device Communications and Location sections appear, illustrated in Figure 76. Figure 76 Device Setup > Add > Device Communications and Location Sections 3. Complete these Device Communications and Location settings for the new device. Table 72 further describes the contents of this page. Settings may differ from device to device. In several cases, the default values from any given device derive from the Device Setup > Communication page. Table 72 Device Communication and Location Fields and Default Values Setting Default Description Name None User-configurable name for the AP (maximum of 20 characters). IP Address None IP address of the device. This field is required. SNMP Port 161 Port OV3600 uses to communicate with the AP using SNMP. Community String (Confirm) Taken from Device Setup > Communication Community string used to communicate with the AP. NOTE: The Community String should have RW (Read-Write) capability. New, out-of-the-box Cisco devices typically have SNMP disabled and a blank username and password combination for HTTP and Telnet. Cisco supports multiple community strings per AP. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 113

114 Table 72 Device Communication and Location Fields and Default Values (Continued) Setting Default Description SNMPv3 Username Auth Password (Confirm) Privacy Password (Confirm) SNMPv3 Auth Protocol SNMPv3 Privacy Protocol Telnet/SSH Username & Password (Confirm) enable Password (Confirm) HTTP Username & Password Auth Password Privacy Password Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication Taken from Device Setup > Communication If you are going to manage configuration for the device, this field provides a read-write user account (SNMP, HTTP, and Telnet) within the Cisco Security System for access to existing APs. OV3600 initially uses this username and password combination to control the Cisco AP. OV3600 creates a user-specified account with which to manage the AP if the User Creation Options are set to Create and user Specified as User. SNMPv3 privacy password. Drop-down menu that allows you to enable the SNMPv3 authentication protocol to the device being added. Drop-down menu that allows you to enable SNMPv3 privacy protocol to the device being added. Telnet username and password for existing Cisco IOS APs. OV3600 uses the Telnet username/password combination to manage the AP and to enable SNMP if desired. NOTE: New, out-of-the-box Cisco IOS-based APs typically have SNMP disabled with a default telnet username of Cisco and default password of Cisco. This value is required for management of any existing Cisco IOS-based APs. Password that allows OV3600 to enter enable mode on the device. HTTP password used to manage the device initially, and to enable SNMP if desired. SNMPv3 authentication password. NOTE: SNMPv3 supports three security levels: (1) no authentication and no encryption, (2) authentication and no encryption, and (3) authentication and encryption. OV3600 currently only supports authentication and encryption. SNMPv3 privacy password. NOTE: SNMPv3 supports three security levels: (1) no authentication and no encryption, (2) authentication and no encryption, and (3) authentication and encryption. OV3600 currently only supports authentication and encryption. 4. In the Location field, select the appropriate group and folder for the device. 5. At the bottom of the page, select either the Monitor Only or Management read/write radio button. The choice depends on whether or not you wish to overwrite the Group settings for the device being added. For more information and a detailed procedure, see Authorizing Devices to OV3600 from APs/ Devices > New Page on page 111. If you select Manage read/write, OV3600 overwrites existing device settings with the Group settings. Place newly discovered devices in Monitor read/only mode to enable auditing of actual settings instead of Group Policy settings. 6. Select Add to finish adding the devices to the network. Adding Multiple Devices from a CSV File You can add devices in bulk from a CSV file to OV3600. Here you also have the option of specifying vendor name only, and OV3600 will automatically determine the correct type while bringing up the device. If your 114 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

115 CSV file includes make and model information, OV3600 will add the information provided in the CSV file as it did before. It will not override what you have specified in this file in any way. The CSV list must contain the following columns: IP Address SNMP Community String Name Type Auth Password SNMPv3 Auth Protocol Privacy Password SNMPv3 Username Telnet Username Telnet Password Enable Password SNMP Port You can download a CSV file and customize it as you like. A sample CSV file is illustrated in Figure 77. Figure 77 Sample CSV File 1. To import a CSV file, go to the Device Setup > Add page. 2. Select the Import Devices via CSV link. The Upload a list of devices page displays; see Figure 78. Figure 78 Device Setup > Add > Import Devices via CSV Page Illustration 3. Select a group and folder into which to import the list of devices. 4. Select Choose File and select the CSV list file on your computer. 5. Select Upload to add the list of devices into OV3600. Adding Universal Devices OV3600 gets basic monitoring information from any device including switches, routers and APs whether or not they are supported devices. Entering SNMP credentials is optional. If no SNMP credentials are entered, OV3600 will provide ICMP monitoring of universal devices. This allows you to monitor key elements of the OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 115

116 wired network infrastructure, including upstream switches, RADIUS servers and other devices. While OV3600 can manage most leading brands and models of wireless infrastructure, universal device support also enables basic monitoring of many of the less commonly used devices. Perform the same steps to add universal devices to OV3600 that were detailed in Adding Devices with the Device Setup > Add Page on page 112. OV3600 collects basic information about universal devices including name, contact, uptime and location. Once you have added a universal device, you can view a list of its interfaces on APs/Devices > Manage. By selecting the pencil icon next to an interface, you can assign it to be non-monitored or monitored as Interface 1 or 2. OV3600 collects this information and displays it on the APs/Devices > Monitor page in the Interface section. OV3600 supports MIB-II interfaces and polls in/out byte counts for up to two interfaces. OV3600 also monitors sysuptime. Assigning Devices to the Ignored Page A device can be assigned to the Ignored page from the APs/Devices > New page. The advantage of having the device be designated in this way, as in the case of a device that is temporarily down for a known reason, is that when you take it off the ignored list, it returns immediately to the location in OV3600 where it had resided before it was marked Ignored. Ignored devices are not displayed in APs/Devices > New if discovered in subsequent scans. Deleted devices will be listed on the APs/Devices > New if discovered in subsequent scans. Perform these steps to further process or return an ignored device to a managed status. 1. To view all devices that are ignored, go to the APs/Devices > Ignored page, illustrated in Figure 79. Figure 79 APs/Devices > Ignored Page Illustration This page provides the following information for any ignored device: device name or MAC address, when known controller associated with that device device type device IP address LAN MAC address for the LAN on which the device is located date and time of device discovery 2. To change the device parameters for a given device, select its checkbox and adjust group, folder, monitor, and manage settings as desired. 3. Select Add to add the device to OV3600 so that it appears on the APs/Devices > New list. 4. The Unignore button will either return the device to its regular folder or group, or send it to the APs/ Devices > New page. Monitoring Devices This section discusses various device monitoring options and includes the following sections: 116 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

117 Viewing Device Monitoring Statistics Understanding the APs/Devices > Monitor Pages for All Device Types Evaluating Radio Statistics for an AP Monitoring Data for Mesh Devices Monitoring Data for Wired Devices (Routers and Switches) Understanding the APs/Devices > Interfaces Page Auditing Device Configuration Using Device Folders (Optional) Viewing Device Monitoring Statistics You can view many useful device monitoring statistics in the APs/Devices > List page. The APs/Devices > List page displays Clients and Usage interactive graphs (formerly Users and Bandwidth prior to 7.4) and lists all devices that are managed or monitored by OV3600. To see only the Up devices, you can click the Up link in the Top Header Stats bar (next to the green arrow). This displays the APs/Devices > Up page with the same information, but only containing active devices. You can do the same with the Down and Mismatched top header stats links. Use the Go to folder field to filter the list by folder, or click Expand folders to show all APs/Devices if you are looking at a filtered device list. A lock icon in the Configuration column indicates that the device in that row is in Monitor only mode. Figure 80 illustrates this page. Figure 80 APs/Devices > List (partial view) Verify that the devices you added are now appearing in the devices list with a Status of Up. Newly added devices will be status Down until they have been polled the first time. They will be configuration Unknown until they have finished verification. The Up status is not contingent on verification. The same section also appears on the Groups > Monitor page, and is hyperlinked from a controller's monitoring interface. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 117

118 The Alert Summary section of APs/Devices > List cites the number of events that have occurred in the last two hours, the last 24 hours, and total. There are three categories of alerts as listed below: OV3600 Alerts IDS Events RADIUS Authentication Issues The Alert Summary table is also a feature of the Home > Overview page, and has the same links in that location. For more information on the Alert Summary table, refer to Viewing Alerts on page 196. Understanding the APs/Devices > Monitor Pages for All Device Types You can quickly go to any device s monitoring page once you go to its specific folder or group on the APs/ Devices > List page, by selecting its hyperlinked name in the Device column. All Monitor pages include a section at the top displaying information such as monitoring/configuration status, serial number, total users, firmware version and so on, as shown in Figure 81. Figure 81 Monitoring Page Top Level Data Common to All Device Types The alert summary, recent events, and audit log sections are also the same regardless of device type and these sections appear at the bottom of these pages, a portion of which is shown in Figure 82. Figure 82 Monitoring Page Bottom Level Data Common to All Device Types Monitoring pages vary according to whether they are wired routers/switches or controllers/wlan switches, or thin or fat APs, whether the device is a Mesh device, and whether Spectrum is enabled. These differences are discussed in the sections that follow. 118 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

119 Monitoring Data Specific to Wireless Devices The APs/Devices > Monitor page for controllers and APs include a graph for users and bandwidth. The controller graph lists the APs connected to it, while the APs include a list of users it has connected. When available, lists of CDP and RF neighbors are also listed. A sample monitoring page for wireless devices is shown in Figure 83. Figure 83 APs/Devices > Monitor Page for Wireless Devices (partial view of an AP) Table 73 describes the fields and information displayed in the Device Info section. The displayed fields vary from device to device. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 119

120 Table 73 APs/Devices > Monitor > Device Info Fields and Default Values Field Poll Now Status Configuration Firmware Licenses (Appears for Alcatel-Lucent switches) Controller (Appears for APs) Mesh Gateway * Mesh Mode* Mesh ID * View in Google Earth* Type Last Contacted Uptime LAN MAC Address Serial Radio Serial Location Contact IP Address Outer IP Remote LAN IP Description Button above the Device Info section that, when pressed, immediately polls the individual AP or the controller for a thin AP; this overrides the group's preset polling intervals to force an immediate update of all data except for rogue information. Shows attempt status and last polling times. Displays ability of OV3600 to connect to the AP. Up (no issue) means everything is working as it should. Down (SNMP get failed) means OV3600 can get to the device but not speak with it using SNMP. Check the SNMP credentials OV3600 is using the view secrets link on the APs/ Devices > Manage page and verify SNMP is enabled on the AP. Many APs ship with SNMP disabled. Down (ICMP ping failed after SNMP get failed) means OV3600 is unable to connect to the AP using SNMP and is unable to ping the AP. This usually means OV3600 is blocked from connecting to the AP or the AP needs to be rebooted or reset. Good means all the settings on the AP agree with the settings OV3600 wants them to have. Mismatched means there is a configuration mismatch between what is on the AP and what OV3600 wants to push to the AP. The Mismatched link directs you to this specific APs/ Devices > Audit page where each mismatch is highlighted. Unknown means the device configuration has not yet been fetched (possible issue with credentials). Verifying means it's fetching configuration to be compared to desired settings. Displays the firmware version running on the AP. Selecting this link opens a pop-up window that lists the licenses installed for this controller, and whether they have expired. Displays the controller for the associated AP device as a link. Select the link to display the APs/ Devices > Monitor page for that controller. Specifies the mesh AP acting as the wired connection to the network. Specifies whether the AP is a portal device or a mesh node. The portal device is connected to the network over a wired connection. A node is a device downstream of the portal that uses wireless connections to reach the portal device. The name of the mesh device. Selecting the Google Earth icon opens the mesh network view in Google Earth. Displays the make and model of the device. Displays the most recent time OV3600 has polled the AP for information. The polling interval can be set on the Groups > Basic page. Displays the amount of time since the AP has been rebooted. This is the amount of time the AP reports and is not based on any connectivity with OV3600. Displays the MAC address of the Ethernet interface on the device. Displays the serial number of the device. Displays the serial number of the radios in the device. This field is not available for all APs. Displays the SNMP location of the device. Displays the SNMP contact of the device. Displays the IP address that OV3600 uses to communicate to the device. This number is also a link to the AP web interface. When the link is moused over a pop-up menu will appear allowing you to http, https, telnet or SSH to the device. NOTE: For Alcatel-Lucent controllers, if Single Sign-On is enabled for your role in this AMP and you have access to this controller, you will not have to enter the credentials for this controller again after selecting this link. Public IP address for a RAP device. LAN IP address for a RAP. This address is useful for troubleshooting from the local network. 120 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

121 Table 73 APs/Devices > Monitor > Device Info Fields and Default Values (Continued) Field Quick Links Open controller web UI: A drop-down menu that allows you to jump to the controller s UI in a new window. NOTE: For Alcatel-Lucent controllers, if Single Sign-On is enabled for your role in this AMP and you have access to this controller, you will not have to enter the credentials for this controller again after selecting this link. Run a command: A drop-down menu with a list of CLI commands you can run directly from the APs/Devices > Monitor page. APs Clients Usage Description For controllers, displays the number of APs managed by this device at the time of the last polling. Displays the total number of users associated to the device or its APs regardless of which radio they are associated to, at the time of the last polling. Combined bandwidth through the device at time of polling. *This field is only available for mesh APs. To see an example of mesh monitoring, see Monitoring Data for Mesh Devices on page 128. Table 74 describes the information in the Radio table for APs: Table 74 APs/Devices > Monitor > Radio Fields and Descriptions Field Index Name MAC Address Clients Usage (Kbps) Channel Tx Power Antenna Type Channel Width* Mesh Links Role Active SSIDs Description The number of the radio, used to distinguish radios that may be of the same type on a device. The Radio type (802.11a/b/g/n) as a link to the Radio Statistics page for that radio. The MAC address of the corresponding radio in the AP. The number of users associated to the corresponding radio at the time of the last polling. The amount of bandwidth being pushed through the corresponding radio interface or device at the time of the last polling. The channel of the corresponding radio. Some devices report transmit power reduction rather than transmit power; no value is reported for those devices. Indicates Internal or External radio. For devices where antenna type is defined per AP, the same antenna type will be listed for each radio. The bandwidth of the channel used by stations. Legacy devices use 20 MHz channels, and newer devices that support the n standard can use 40 MHz channels to increase throughput. The total number of mesh links to the device including uplinks and downlinks. Whether the radio acts as a Mesh Node or Access The SSID(s) of the radio. Devices with wired interfaces will display the Wired Interfaces table, which is described in Table 75: Table 75 APs/Devices > Monitor > Wired Interfaces Fields and Descriptions Field Name MAC Address Clients Type Admin Status Description Displays the name of the interface. Displays the MAC address of the corresponding interface in the device. Displays the number of users associated to the corresponding interface at the time of the last polling. Indicates the type of interface - gigabit Ethernet or fast Ethernet for wired interfaces. The administrator setting that determined whether the port is on or off. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 121

122 Table 75 APs/Devices > Monitor > Wired Interfaces Fields and Descriptions (Continued) Field Operational Status Duplex Alcatel-Lucent Port Mode Input Capacity Output Capacity Description Displays the current status of the interface. If an interface is Up, then OV3600 is able to ping it and fetch SNMP information. If the AP is listed Down then OV3600 is either unable to ping the interface or unable to read the necessary SNMP information from the device. Duplex mode of the link, full or half. Either Active Standby (which provides redundancy so that when an active interface fails, the user traffic can failover to the standby interface) or one of the forwarding modes (Split, Bridge). The input capacity of the interface. The output capacity of the interface. Figure 84 illustrates the interactive graphs, and Table 76 describes the graphs on this page. Figure 84 Interactive Graphs for an Alcatel-Lucent Switch Table 76 APs/Devices > Monitor Graphical Data Graph Clients Usage CPU Utilization (controllers only) Memory Utilization (controllers only) Description Formerly Users. Shows the max and average client count reported by the device radios for a configurable period of time. User count for controllers are the sum of the user count on the associated APs. Checkboxes below the graph can be used to limit the data displayed. Formerly Bandwidth. Shows the bandwidth in and out reported by the device for a configurable period of time. Bandwidth for controllers is the sum of the associated APs. Checkboxes below the graph can be used to limit the data displayed. Reports overall CPU utilization (not on a per-cpu basis) of the device. Reports average used and free memory and average max memory for the device. 122 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

123 Table 77 describes the fields and information displayed for the Connected Clients display. Table 77 APs/Devices > Monitor > Connected Clients Fields and Default Values Field Username Device Type Role MAC Address Radio Association Time Duration Auth Type Cipher Description Provides the name of the User associated to the AP. OV3600 gathers this data in a variety of ways. It can be taken from RADIUS accounting data or traps. The type of device the user is using as determined by the Device Type Rules set up by an administrator in OV3600 Setup > Device Type Setup. For more information, refer to Setting Up Device Types on page 59. The role of the connected client such as employee, perforce, or logon (captive portal). Displays the Radio MAC address of the user associated to the AP. Also provides a link that redirects to the Users > Detail page. Displays the radio to which the user is associated. Displays the first time OV3600 recorded the MAC address as being associated. Displays the length of time the MAC address has been associated. Displays the type of authentication employed by the user. Supported auth types include: EAP Extensible Authentication Protocol. RADIUS accounting RADIUS accounting servers integrated with OV3600 provide the RADIUS Accounting Auth type. WPA2 Wi-Fi Protected Access 2 encryption No Encryption OV3600 considers all other types as not authenticated. The information OV3600 displays in Auth Type and Cipher columns depends on what information the server receives from the devices it is monitoring. The client devices may all be similar, but if the APs to which they are associated are of different models, or if security is set up differently between them, then different Auth Type or Cipher values may be reported to OV3600. If all APs are the same model and all are set up the same way, then another reason for differing Auth Types might be the use of multiple VLANs or SSIDs. One client device might authenticate on one SSID using one Auth Type and another client device might authenticate on a second SSID using a different Auth Type. Displays the encryption or decryption cipher supporting the user, when this information is available. The client devices may all be similar, but if the APs to which they are associated are of different models, or if security is set up differently between them, then different Auth Type or Cipher values may be reported to OV3600. Auth Time Shows how long the user has been authenticated, in minutes. A negative number (such as -17 min) indicates that the user has not authenticated for the duration displayed. Signal Quality Usage Goodput Location LAN IP Addresses LAN Hostnames Displays the average signal quality the user experienced. Displays the average bandwidth consumed by the MAC address. The ratio of the total bytes transmitted or received in the network to the total air time required for transmitting or receiving the bytes. Displays the QuickView box allows users to view features including heatmap for a device and location history for a user. Displays the IP assigned to the user MAC. This information is not always available. OV3600 can gather it from the ARP cache of switches discovered by OV3600. As of AMP 7.4, this column can accommodate multiple IP addresses for a client if it has both IPv4 and IPv6. The DNS hostname(s) broadcast by the client. As of 7.4, this column can accommodate multiple hostnames for a client if it has both IPv4 and IPv6. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 123

124 The Recent Events area lists the most recent events specific to the device. This information also appears on the System > Events Log page (refer to Using the System > Event Log Page on page 188). Table 78 describes the fields in this page that display in the Recent Events table. Table 78 APs/Devices > Monitor > Recent Events Fields and Default Values Field Time User Event Description Displays the day and time the event was recorded. Displays the user that triggered the event. Configuration changes are logged as the OV3600 user that submitted them. Automated OV3600 events are logged as the System user. Displays a short text description of the event. Evaluating Radio Statistics for an AP The APs/Devices > Monitor > Radio Statistics page contains useful data for pinpointing network issues at the AP radio level for Alcatel-Lucent APs and Cisco WLC thin APs (firmware 4.2 or greater). To see radio statistics details, navigate to the APs/Devices > Monitoring page for a supported AP and select the linked radio under the Name column in the Radios list table, as illustrated in Figure 85. Figure 85 Links to the Radio Statistics page on APs/Devices > Monitoring for an AP Overview of the Radio Statistics Page The Radio Statistics page displays transmit and receive statistics about the communication quality of individual radios. Depending on the AP, assigned group profiles, and recent activity on this radio, this data gives visibility into recent and historical changes in the network, fetches real-time statistics from the AP s controller, indicates actively interfering devices (requires Alcatel-Lucent APs set to Spectrum mode), and summarizes major issues. Viewing Real-Time ARM Statistics Alcatel-Lucent AP Groups that have the Adaptive Radio Management (ARM) feature enabled continuously optimize each AP to use the best channel and transmission power settings available. An AP configured with ARM will automatically adjust to a better channel if it reaches a configured threshold for noise, MAC errors, or PHY errors; additionally, it can attenuate transmit power and switch between radio modes as needed. For more information, refer to the ARM chapter in the AOS-W User Guide. Complete ARM statistics from Alcatel-Lucent switches can be retrieved from the Radio Statistics page by selecting the Run a command drop-down menu and choosing button, as illustrated in Figure 86. Figure 86 Fetch additional radio stats by running a show command When this button is selected, a new browser window launches with the statistics in plain text. Other ARMtracked metrics are visible in the Radio Statistics page for Alcatel-Lucent APs. 124 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

125 Issues Summary section The Issues Summary section only displays when noise, client count, non interfering devices, channel utilization, usage, and MAC and PHY errors reach a certain threshold of concern, as described in Table 79 and illustrated in Figure 87: Table 79 Issues Summary labels and thresholds Issue Triggering Threshold High Noise > -80 High Number of Clients > 15 High Channel Utilization > 75% High Usage Interfering Devices Detected High MAC/Phy Errors > 75% of max Detected within the last 5 minutes > 1000 frames/sec Figure 87 Issues Summary Section Illustration These issues highlighted in this section can be examined in detail using the corresponding interactive graphs on the same page. See the Radio Statistics Interactive Graphs section of this chapter for details Radio Counters Summary This table appears for radios with counters and summarizes the number of times an expected acknowledgement frame was not received, the number of duplicate frames, the number of frames containing Frame Check Sequence (FCS) errors, and the number of frame/packet transmission retries and failures. These aggregate error counts are broken down by Current, Last Hour, Last Day, and Last Week time frames, as illustrated in Figure 88. Figure Radio Counters Summary table The frame- per-second rate of these and other errors over time are tracked and compared in the Counters graph on the same page. Radio Statistics Interactive Graphs Time-series graphs for the radio are displayed across a tabbed, dual-pane interface to show changes recorded at every polling interval over time. Clients and Usage data are polled based on the AP's group's User Data Polling Period. Channel, Noise, and Power are based on AP Interface Polling Period Counters data are based on the AP's group's Counters Polling Period. You can adjust the attributes of these graphs as follows: Drag the horizontal slider under the graphs to move the scope of all graphs between one year ago and the current time. Drag the vertical slider between graphs to change the relative width of each. The Show All link displays all of the available data series. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 125

126 The bar-graph icon on the upper right-hand corner of each graph opens a new window and displays all data series for the selected graph over the last two hours, last day, last week, last month, and last year in one page. The graphs that display depend on the AP and/or its controller. Select the checkbox next to any metric to remove its data from the graph. Select Collapse to remove unchecked metrics from the legend, and Show All to restore them. The two graph panes enable simultaneous display of two different information sets, as detailed in : Table 80 Radio Statistics Interactive Graphs Descriptions Graph Title Description Clients Usage Channel Noise A line graph that displays the maximum users associated to the corresponding radio at polling intervals over the time range set in the slider. Select Show All for other metrics such as average users and max users for various individual devices. An area graph displaying the average bandwidth in each direction for the radio. Select Show All for other metrics such as max bandwidth in and out, average and max mesh/overhead or overhead bandwidth, and average/max Enet0. An area graph that displays the channel changes (if any) of the radio over time. Frequent, regular channel changes on an Alcatel-Lucent or Cisco WLC AP radio usually indicate that the Adaptive Radio Management feature (ARM) in AOS-W is compensating for high noise levels from interfering devices. An area graph that displays signal interference (noise floor) levels in units of dbm. Noise from interfering devices above your AP's noise threshold can result in dropped packets. For ARMenabled Alcatel-Lucent APs, crossing the noise threshold triggers an automatic channel change. Power A line graph that displays the average and maximum radio transmit power, between 0 and 30 dbm, over the time range set in the slider. You can adjust the transmit power manually in the APs/Devices > Manage page for this radio's AP, or enable ARM on Alcatel-Lucent APs to dynamically adjust the power toward your acceptable Coverage Index as needed. For more information, see the Adaptive Radio Management chapter of the AOS-W User Guide. MAC/Phy Errors A line graph displaying the frame reception rate, physical layer error rate (resulting from poor signal reception or broken antennas), and the data link (MAC) layer (corrupt frames, driver decoding issues) for the radio Counters A line graph that displays statistics such as frame rate, fragment rate, retry rate, duplicate frame rate, and other metrics tracked by counters. Utilization (Alcatel-Lucent and Cisco WLC thin APs on supported firmware versions only) Displays max and average percentages on this radio for busy, interfering receiving and transmitting signals. Special configuration on the controller is required to enable this data; consult the OmniVista 3600 Air Manager Best Practices Guide in Home > Documentation for details. 126 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

127 Figure 89 Radio Statistics Interactive Graphs Illustration Bandwidth and Counters displayed Recent ARM Events Log If this radio references an active and enabled ARM profile, and if your OV3600 is enabled as a trap host (see Best Practices Guide for instructions), ARM-initiated events such as automatic channel changes, power changes, and mode changes are displayed in the ARM Events table with the original and modified values; these values can be selected for filtering the results. You can export the table in CSV format. The columns and values are described in, and illustrated in Figure 90. Figure 90 ARM Events Table Illustration Table 81 ARM Events table Columns and Values Column Time Trap Type Previous Tx Power Current Tx Power Previous Radio Mode Current Radio Mode Previous Channel Current Channel Previous Secondary Channel Description The time of the ARM event. The type of trap that delivered the change information. Current ARM trap types that display in OV3600 are: Power Change Mode Change Channel Change Values that display in the following columns depend on the Trap Type. Old value for transmit power before the Power Change event took place. New transmit power value after the change. Old value for radio mode before the Mode Change event took place. New radio mode value after the change. Old primary channel value before the Channel Change event took place. New primary channel value after the change. Old secondary channel value (for 40Mhz channels on n devices) before the Channel Change event took place. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 127

128 Table 81 ARM Events table Columns and Values (Continued) Column Current Secondary Channel Change Reason Description New secondary channel value after the change. If the noise and interference cause for the change can be determined, they will be displayed here. Mode change reasons are not yet tracked. Detected Interfering Devices Table For Alcatel-Lucent APs running in Spectrum mode, the same non interfering devices identified in the Issues Summary section are classified in the Detected Interfering Devices table along with the timestamp of its last detection, the start and end channels of the interference, the signal to noise ratio, and the percentage of time the interference takes place, as illustrated in Figure 91. This table can be exported to CSV format, and the displayed columns can be moved or hidden as needed. Figure 91 Detected Interfering Devices Table Illustration Possible device types for the Detected Interfering Devices table are: Wi-Fi Microwave Bluetooth Generic Fixed Freq Cordless Phone Fixed Freq Video Device Fixed Freq Audio Device Fixed Freq Generic Freq Hopper Cordless Phone Freq Hopper XBox Freq Hopper Microwave Inverter Cordless Base Freq Hopper Unknown Active BSSIDs Table The Active BSSIDs table maps the BSSIDs on a radio with the SSID it broadcasts to the network, as illustrated in Figure 92. This table appears only for Alcatel-Lucent AP radios. Figure 92 Active BSSIDs Table Illustration Monitoring Data for Mesh Devices The monitoring page for mesh devices includes basic device information at the top, two tables for Radios and Wired Interfaces, a Users interactive graph and a Bandwidth interactive graph. Under these graphs are a list of associated Users, Mesh Links, RF Neighbors, and other common event logs and information. 128 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

129 Figure 93 APs/Devices > Monitor page for a Mesh Device These fields are described in detail in Viewing Device Monitoring Statistics on page 117. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 129

130 Monitoring Data for Wired Devices (Routers and Switches) The monitoring page for routers and switches includes basic device information at the top, a bandwidth graph depicting the sum of all the physical interfaces, and beneath that, CPU/Memory usage graphs as shown in Figure 94. Figure 94 APs/Devices > Monitor Page for an Aruba Mobility Access Switch 130 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

131 All managed wired devices also include an Interfaces subtab, as shown in Figure 95. Figure 95 APs/Devices > Interfaces Page for Wired Devices (partial view). The Interfaces page includes a summary of all the interfaces at the top. In case of the stacked switches, the master includes the interfaces of all the members including its own. The physical and the virtual interfaces are displayed in separate tables, labeled Physical Interfaces and Virtual Interfaces. VLANs are listed below the interface. OV3600 monitors Up/Down status and bandwidth information on all interfaces. You can edit multiple interfaces concurrently by selecting one of the two Edit Interfaces hyperlinks. Interface labels are used to group one or more interfaces for the purpose of defining interface bandwidth triggers. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 131

132 Understanding the APs/Devices > Interfaces Page Monitoring Data for Wired Devices (Routers and Switches) on page 130 showed you how to view highlevel interface information for all physical and virtual interfaces on an entire router or switch. Select any interface hotlink in the Interface column of the Physical or Virtual Interfaces tables on the stacked switches to go to an Interface Monitoring page displaying data relevant to that specific interface, as shown Figure 96. Figure 96 Interface Monitoring Page for a Wired Device An Interface Monitoring page is comprised of three sections: Interface Information, Usage and Interface Frame Counters graphs, and Connected Clients. Specifics of the interface are in the Interface Information section, as depicted in Figure 97. Figure 97 Individual Interface Information Section Bandwidth, and various standard and enterprise specific error counting information is displayed in the lower section in a tabbed graph, which are shown in Figure 96 above. Connected Clients, if any, are listed in a table below the interactive graphs as shown in Figure 98. Figure 98 Connected Clients list in APs/Devices > Interface Monitoring for a selected interface 132 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

133 What Next? All device lists in OV3600 act as portals to management pages if you have the proper read/write privileges. Selecting the wrench or pencil icon next to a device table entry, or selecting Modify Devices where appropriate above a device table, will take you to the appropriate Management page (APs/Devices > Manage). For more information, see Configuring and Managing Devices on page 134. Auditing Device Configuration When you have added a newly discovered device successfully to a Group in Monitor mode, the next step is to verify device configuration status. Determine whether any changes will be applied to that device when you convert it to Managed read/write mode. OV3600 uses SNMP or Telnet to read a device s configuration. SNMP is used for Cisco controllers. Alcatel-Lucent devices and wired routers and switches use Telnet/SSH to read device configuration. See Individual Device Support and Firmware Upgrades on page 144 for more details. Perform these steps to verify the device configuration status: 1. Browse to the APs/Devices > List page. 2. Locate the device in the list and check the information in the Configuration column. 3. If the device is in Monitor mode, the lock symbol appears in the Configuration column, indicating that the device is locked and will not be configured by OV Verify the additional information in the Configuration column for that device. A status of Good indicates that all of the device's current settings match the group policy settings, and that no changes will be applied when the device is shifted to Manage mode. A status of Mismatched indicates that at least one of the device's current configuration settings do not match the group policy, and will be changed when the device is shifted to Manage mode. 5. If the device configuration is Mismatched, select the Mismatched link to go to the APs/Devices > Audit page. The APs/Devices > Audit page lists detailed information on all existing configuration parameters and settings for an individual device. The group configuration settings are displayed on the right side of the page. If the device is moved from Monitor to Manage mode, the settings on the right side of the page overwrite the settings on the left. Figure 99 illustrates this page. Figure 99 APs/Devices > Audit Page Illustration 6. Review the list of changes to be applied to the device to determine whether the changes are appropriate. If not, you need to change the Group settings or reassign the device to another Group. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 133

134 Using Device Folders (Optional) The devices on the APs/Devices List pages include List, Up, Down, and Mismatched fields. These devices are arranged in groups called folders. Folders provide a logical organization of devices unrelated to the configuration groups of the devices. Using folders, you can quickly view basic statistics about devices. You must use folders if you want to limit the APs and devices OV3600 users can see. Folder views are persistent in OV3600. If you select the Top folder and then select the Down link at the top of the page, you are taken to all of the down devices in the folder. If you want to see every down device, select the Expand folders to show all devices link. When the folders are expanded, you see all of the devices on OV3600 that satisfy the criteria of the page. You also see an additional column that lists the folder containing the AP. Perform the following steps to add a device folder to OV To add a folder, select the Add New Folder link at the bottom of APs/Devices > List, > Up, > Down, or > Mismatched. Figure 100 illustrates the page. Figure 100 Folder Creation Page Illustration 2. Enter the name of the new folder. 3. Select the Parent folder. 4. Select Add. Once a new folder has been created, devices can be moved into it using the Modify Devices link or when New Devices are added into OV3600. Configuring and Managing Devices This section contains the following topics describing individual device configuration within device groups: Moving a Device from Monitor Only to Manage Read/Write Mode Configuring AP Settings Configuring Device Interfaces for Switches Individual Device Support and Firmware Upgrades While most device configuration settings can be efficiently managed by OV3600 at a Group level, certain settings must be managed at the individual device level. For example, because devices within a Group are often contiguous with one another, and have overlapping coverage areas, it makes sense to manage these devices individually to avoid RF interference. Any changes made at an individual device level will automatically override Group level settings. OV3600 automatically saves the last 10 device configurations for reference and compliance purposes. Archived device configurations are linked on the APs/Devices > Audit page and identified by name. By default, configuration is tracked by the date and time it was created; device configurations are also archived by date. It is not possible to push archived configurations to devices, but archived configurations can be compared to the current configuration, the desired configuration, or to other archived configurations using the dropdown menus on the APs/Devices > Audit page. This applies to startup or to running configuration files. 134 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

135 Compare two configurations to highlight the specific lines that are mismatched. The Audit page provides links to the OV3600 pages where any mismatched settings can be configured. These procedures assume you are familiar with the function buttons available to save, apply, revert, and so on. For details on button functions, see Buttons and Icons on page 27. Moving a Device from Monitor Only to Manage Read/Write Mode Once the device configuration status is Good on the APs/Devices > List page, or once you have verified all changes that will be applied to the device on the APs/Devices > Audit page, you can safely shift the device from Monitor Only mode to Manage Read/Write mode. Once a device is in Manage mode, OV3600 will push a new configuration to the device in the event that the actual device configuration does not match the OV3600 configuration for that device. To move a device from Monitor Only to Manage Read/Write mode, perform the following steps. 1. Go to the APs/Devices > List page and select the wrench icon next to the name of the AP to be shifted from Monitor Only mode to Manage Read/Write mode. This directs you to the APs/Devices > Manage page. 2. Locate the General area as shown in Figure 101. Figure 101 APs/Devices > Manage > General Section Illustration 3. Select Manage Read/Write on the Management Mode field. 4. Select Save and Apply, then Confirm Edit on the confirmation page to retain these settings and to push configuration to the device. 5. For device configuration changes that require the device to reboot, use the Schedule function to push the changes at a time when WLAN users will not be affected. 6. To move multiple devices into managed mode at once, use the Modify Devices link on an AP list page. For more information, refer to Modifying Multiple Devices on page 103. Use the Enable Planned Maintenance Mode field in APs/Devices > Manage > General to put this device into planned maintenance. During the maintenance mode, no AP Down triggers will be deployed on these devices. Users will not be able to delete folders that contain devices in Planned Maintenance. The devices in Planned Maintenance will show the Up status, but will not be tracked in historical graphs and logs as Up. You can set multiple devices into Planned Maintenance Mode in the Modify Devices link on an AP list page. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 135

136 Configuring AP Settings 1. Browse to the APs/Devices > List page and select the wrench icon next to the device whose AP settings you want to edit. This directs you to the Manage page for that device. Figure 102 illustrates this page. Figure 102 APs/Devices > Manage Page Illustration If any changes are scheduled for this AP, they appear in a Scheduled Changes section at the top of the page above the other fields. The linked name of the job takes you to its System > Configuration Change Job Detail page. 136 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

137 2. Locate the General section for information about the AP s current status. Table 82 describes the fields, information, and settings. Table 82 APs/Devices > Manage > General Fields and Descriptions Field Name Status Configuration Last Contacted Type Firmware Group Template Folder Management Mode Enable Planned Maintenance Mode Notes Description Displays the name currently set on the device. Displays the current status of an AP. If an AP is Up, then OV3600 is able to ping it and fetch SNMP information from the AP. If the AP is listed Down then OV3600 is either unable to ping the AP or unable to read the necessary SNMP information from the device. Displays the current configuration status of the AP. To update the status, select Audit on the APs/Devices > Audit page. Displays the last time OV3600 successfully contacted the AP. Displays the type of AP. Displays the version of firmware running on the AP. Links to the Group > Monitoring page for the AP. Displays the name of the group template currently configuring the AP. Also displays a link to the Groups > Template page. This is only visible for APs that are managed by templates. Displays the name of the folder containing the AP. Also displays a link to the APs/Devices > List page for the folder. Displays the current management mode of the AP. No changes are made to the AP when it is in Monitor Only mode. OV3600 pushes configurations and makes changes to an AP when it is in Manage Read/Write mode. Put this device into planned maintenance. During the maintenance mode, no AP Down triggers will be deployed on these devices. Users will not be able to delete folders that contain devices in Planned Maintenance. The devices in Planned Maintenance will show the Up status, but will not be tracked in historical graphs and logs as Up. You can set multiple devices into Planned Maintenance Mode in the Modify Devices link on an AP list page. Provides a free-form text field to describe device information. 3. Review and provide the following information in the Settings area. Devices with dual radios display radio-specific settings in the Slot A and Slot B area. If a device is dual-radio capable but only has one device installed, OV3600 manages that device as if it were a single slot device. Devices from different vendors have different RF settings and capabilities. The fields in the Settings section of the APs/Devices > Manage page are context-sensitive and only present the information relevant for the particular device vendor and model. Table 83 describes field settings, default values, and information for the Settings section of this page. Table 83 APs/Devices > Manage > Settings Fields and Default Values Setting Default Device Type Description Name None All User-configurable name for the device (max. 20 characters) Domain Name None IOS Field populated upon initial device discovery or upon refreshing settings. Enable this option from OV3600 Setup > Network page to display this field on the APs/Devices > Manage page, with fully-qualified domain names for IOS APs. This field is used in conjunction with Domain variable in IOS templates. Location Read from the device All The SNMP location set on the device. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 137

138 Table 83 APs/Devices > Manage > Settings Fields and Default Values (Continued) Setting Default Device Type Description Latitude None All Text field for entering the latitude of the device. The latitude is used with the Google Earth integration. Longitude None All Text field for entering the longitude of the device. The longitude is used with the Google Earth integration. Altitude (meters) Group None All Text field for entering the altitude of the device when known. This setting is used with the Google Earth integration. Specify altitude in meters. Default Group All Drop-down menu that can be used to assign the device to another Group. Folder Top All Drop-down menu that can be used to assign the device to another Group. Auto Detect Upstream Device Down Status Message Automatically clear Down Status Message when device comes back up Administrative Status Yes All Selecting Yes enables automatic detection of upstream device, which is automatically updated when the device is polled. Selecting No displays a drop-down menu of upstream devices. None All Enter a text message that provides information to be conveyed if the device goes down. None All Whether the message entered in the Down Status Message field should be removed after the device returns to the Up status. Enable All Enables or disables administrative mode for the device. Mode Local All Designates the mode in which the device should operate. Options include the following: Local H-REAP Monitor Rogue Detector Sniffer 4. Complete additional settings on the APs/Devices > Manage page, to include H-REAP, certificates, radio settings, and network settings. Table 84 describes many of the possible fields. For complete listing and discussion of settings applicable only to Alcatel-Lucent devices, see the OmniVista 3600 Air Manager Configuration Guide. Table 84 APs/Devices > Manage, Additional Settings Setting Default Device Type Description Mesh Role Mesh AP Mesh Devices Drop-down menu specifies the mesh role for the AP as shown: Mesh AP The AP will act like a mesh client. It will use other APs as its uplink to the network. Portal AP The AP will become a portal AP. It will use a wired connection as its uplink to the network and serve it over the radio to other APs. None The AP will act like a standard AP. It will not perform meshing functions 138 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

139 Table 84 APs/Devices > Manage, Additional Settings (Continued) Setting Default Device Type Description Mesh Mobility Static Mesh Devices Select Static if the AP is static, as in the case of a device mounted on a light pole or in the ceiling. Select Roaming if the AP is mobile. Two examples would be an AP mounted in a police car or utility truck. Receive Antenna Diversity Cisco Drop-down menu for the receive antenna provides three options: Diversity Device will use the antenna that receives the best signal. If the device has two fixed (non-removable) antennas, the Diversity setting should be used for both receive and transmit antennas. Right If your device has removable antennas and you install a high-gain antenna on the device's right connector (the connector on the right side when viewing the back panel of the device), use this setting for receive and transmit. Left If your device has removable antennas and you install a high-gain antenna on the device's left connector, use this setting for both receive and transmit. Transmit Antenna Diversity Cisco See description in Receive Antenna above. Antenna Diversity Transmit Power Reduction Primary Only Symbol 4131 Drop-down menu provides the following options: Full Diversity The AP receives information on the antenna with the best signal strength and quality. The AP transmits on the antenna from which it last received information. Primary Only The AP transmits and receives on the primary antenna only. Secondary Only: The AP transmits and receives on the secondary antenna only. Rx Diversity The AP receives information on the antenna with the best signal strength and quality. The AP transmits information on the primary antenna only. 0 Proxim Transmit Power Reduction determines the APs transmit power. The max transmit power is reduced by the number of decibels specified. Channel 6 All Represents the AP's current RF channel setting. The number relates to the center frequency output by the AP's RF synthesizer. Contiguous APs should be set to different channels to minimize "crosstalk," which occurs when the signals from APs overlap and interfere with each other. This RF interference negatively influences WLAN performance b's 2.4-GHz range has a total bandwidth of 80-MHz, separated into 11 center channels. Of these channels, only 3 are non-overlapping (1, 6, and 11). In the United States, most organizations use only these non-overlapping channels. Transmit Power Level Highest power level supported by the radio in the regulatory domain (country) Cisco, Symbol, Proxim AP- 600, AP-700, AP-2000 (802.11g) Determines the power level of radio transmission. Government regulations define the highest allowable power level for radio devices. This setting must conform to established standards for the country in which you use the device. You can increase the coverage radius of the access point by increasing the Transmit Power Level. However, while this increases the zone of coverage, it also makes it more likely that the AP will interfere with neighboring APs. Supported values are: Cisco (100mW, 50mW, 30mW, 20mW, 5mW, 1mW) Symbol (Full or 50mW, 30mW, 15mW, 5mW, 1mW) OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 139

140 Table 84 APs/Devices > Manage, Additional Settings (Continued) Setting Default Device Type Description Radio Enabled Yes All The Radio Enabled option allows you to disable the radio's ability to transmit or receive data while still maintaining Ethernet connectivity to the network. OV3600 will still monitor the Ethernet page and ensure the AP stays online. Customers typically use this option to temporarily disable wireless access in particular locations. This setting can be scheduled at an AP-Level or Group-Level. NOTE: You cannot disable radios unless rogue scanning is disabled in Groups > Radio. Use DHCP Yes All If enabled, the AP will be assigned a new IP address using DHCP. If disabled, the AP will use a static IP address. For improved security and manageability, disable DHCP and using static IP addresses. LAN IP None All The IP Address of the AP Ethernet interface. If One-to-One NAT is enabled, OV3600 will communicate with the AP on a different address (the IP Address defined in the Device Communication section). If DHCP is enabled, the current assigned address will appear grayed out and the field cannot be updated in this area. Subnet Mask None All Provides the IP subnet mask to identify the sub-network so the IP address can be recognized on the LAN. If DHCP is enabled, the current assigned address will appear grayed out and the field cannot be updated in this area. Gateway None All The IP address of the default internet gateway. If DHCP is enabled, the current assigned address will appear grayed out and the field cannot be updated in this area. 5. Locate the Template Options area on the APs/Devices > Manage page. This section only appears for IOS APs, Symbol and Alcatel-Lucent switches in groups with Alcatel-Lucent GUI Config disabled. Table 85 describes field settings, default values, and additional information for this page. Table 85 APs/Devices > Manage > Template Options Fields and Default Values Setting Default Device Type Description WDS Role Client Cisco IOS Wireless LAN Controllers only Set the WDS role for this AP. Select Master for the WDS master APs and Client for the WDS Client. Once this is done you can use the %if wds_role= % to push the client, master, or backup lines to appropriate WDS APs. SSL Certificate None Cisco IOS OV3600 will read the SSL Certificate off of the AP when it comes UP in OV3600. The information in this field will defines what will be used in place of %certificate%. Extra Device Commands None Cisco IOS Defines the lines that will replace the %ap_include_1% variable in the IOS template. This field allows for unique commands to be run on individual APs. If you have any settings that are unique per AP like a MOTD you can set them here. switch_command None Cisco Catalyst switches Defines lines included for each of the members in the stack. This field appears only on the master's Manage page. The information in this field will determine what is used in place of the %switch_command% variable. 6. For Cisco WLC devices, go to the interfaces section of the APs/Devices > Manage page. Select Add new Interface to add another controller interface, or select the pencil icon to edit an existing 140 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

141 controller interface. Table 86 describes the settings and default values. For detailed descriptions of Cisco WLC devices supported by OV3600, refer to the Cisco WLC product documentation. Table 86 APs/Devices > Manage > Interface Fields and Descriptions for Cisco WLC Devices Field Default Description Name None The name of the interface on the controller. VLAN ID None The VLAN ID for the interface on the controller. Port None The port on the controller to access the interface. IP Address None The IP address of the controller. Subnet Mask None The subnet mask for the controller. Gateway None The controller's gateway. Primary and Secondary DHCP Servers None The DHCP servers for the controller. Guest LAN Disabled Indicates a guest LAN. Quarantine VLAN ID Disabled Enabled indicates it is a quarantine VLAN; used only for H-REAP-associated clients. Dynamic Device Management Enabled When enabled, makes the interface an AP-manager interface. Cisco calls this feature Dynamic AP Management. Setting a Maintenance Window for a Device OmniVista 3600 Air Manager can automate the manual action of putting multiple devices into Manage mode at once so that changes can be applied, and after the maintenance period is over, the devices automatically revert to Monitor-Only mode. Maintenance windows can be set as a one-time or recurring event on the APs/Devices > Manage and Groups > Basic page. You can also use the Modify Devices link to add or delete maintenance windows to multiple selected devices at once. Additionally, this feature can be used on Master Console to set maintenance windows for multiple AMPs. To set a maintenance window for a single device in APs/Devices > Manage, follow these steps: 1. Navigate to the APs/Devices > Manage page for a device. 2. At the bottom of the page, locate the Maintenance Windows section. 3. Select Add New AP Maintenance Window. Figure 103 Add New Maintenance Window in APs/Devices > Manage page 4. Enter a name for the maintenance window. 5. In the Occurs field, specify whether the maintenance window should occur one time, or daily, weekly, monthly, or annually. 6. Set the desired start time and the duration (in minutes) of the maintenance window. 7. Select Add. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 141

142 Configuring Device Interfaces for Switches When you go to the APs/Devices > Interfaces page for a switch, you can add a Virtual interface by selecting Add and entering the appropriate information in the page that then appears, as shown in Figure 104. Figure 104 Add Virtual Interfaces Page for Wired Devices. New physical and virtual interfaces are discovered using SNMP polling as described in SNMP/HTTP Scanning on page 108. To refresh and reload all current interface information from a device, select Import Interfaces on the bottom of the page as shown in Figure 105. Figure 105 Import Interfaces for Refresh and Reload (lower portion of page) You can view details for each interface on a wired device from its individual interface page as well. For details, see Understanding the APs/Devices > Interfaces Page on page 132. You can configure interface settings individually or in groups. For individual settings, select the pencil icon next the interface name in AP/Devices > Interfaces. This takes you to the Interfaces Monitoring and Configuration window which has a slightly different appearance depending on whether you are configuring a physical or virtual interface, as shown in Figure 106 and Figure Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

143 Figure 106 Physical Interfaces Monitoring and Configuration Sections Figure 107 Virtual Individual Interfaces Configuration Section To configure interfaces as a group, select Edit Interfaces above the Physical or Virtual Interfaces table as shown in Figure 108. Figure 108 Edit Multiple Interfaces OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 143

144 You will remain on the same page, but will have the option to make changes to the most commonly edited settings in batch mode, as shown in Figure 109. Figure 109 Multiple Interface Editing Page Illustration OV3600 assembles the entire running configuration using templates and your modifications to these pages. For a more detailed discussion on templates, see Chapter 6, Creating and Using Templates on page 153. Individual Device Support and Firmware Upgrades Perform the following steps to configure AP communication settings for individual Alcatel-Lucent device types. 1. Locate the Device Communication area on the APs/Devices > Manage page. 2. Specify the credentials to be used to manage the AP. Figure 110 illustrates this page. Figure 110 APs/Devices > Manage > Device Communication The Device Communication area may appear slightly different depending on the particular vendor and model of the APs being used. 3. Enter and confirm the appropriate Auth Password and Privacy Password. 4. You can disable the View AP Credentials link in OV3600 by the root user. Contact Alcatel-Lucent support for detailed instructions to disable the link. 5. (Optional.) Enter the appropriate SSH and Telnet credentials if you are configuring Dell, Aruba Networks, Alcatel-Lucent or any Cisco device except Cisco WLAN controllers. 6. Select Apply, then Confirm Edit to apply the changes to the AP immediately, Schedule to schedule the changes during a specific time, or Cancel to return to APs/Devices > Manage. Some AP configuration changes may require the AP to be rebooted. Use the Schedule function to schedule these changes to occur at a time when WLAN users will not be affected. 144 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

145 Select the Update Firmware button at the bottom right of the page to upgrade the device's firmware. Figure 111 illustrates the page that opens and Table 87 describes the settings and default values. The Update Firmware button only appears if 1) the AMP Administrator has enabled Allow firmware upgrades in monitor-only mode in OV3600 Setup > General, 2) if you are looking at an APs/Devices > Manage page for a controller or autonomous AP that supports firmware upgrades in AMP. See the Supported Wireless Firmware Versions document (the AMP Firmware Matrix) in Home > Documentation to see all of the AMP-supported devices that can perform firmware upgrades. In most cases, you cannot upgrade firmware directly on thin APs. Note that for Alcatel-Lucent firmware upgrades, OV3600 does not check whether a device is in Master or Local configuration, and it does not schedule rebooting after the upgrade. OV3600 users should consult Alcatel-Lucent s best practices for firmware upgrades and plan their upgrades using OV3600 accordingly. Table 87 APs/Devices > Manage > Firmware Upgrade Fields and Default Values Setting Default Description Desired Version None Specifies the firmware to be used in the upgrade. Firmware can be added to this drop-down menu on the Device Setup > Upload Firmware & Files page. Job Name None Sets a user-defined name for the upgrade job. Use a meaningful and descriptive name. Use /safe flag for Cisco IOS firmware upgrade command No Enables or disables the /safe flag when upgrading IOS APs. The /safe flag must be disabled on older APs for the firmware file to fit in flash memory. Recipients None Displays a list of addresses that should receive alert s if a firmware upgrade fails. Sender Address None Displays the From address in the alert . OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 145

146 Figure 111 APs/Devices > Manage Firmware Upgrades Initiating a firmware upgrade will change the Firmware Status column for the device to Pending in APs/ Devices > List. You can review the status of all recent firmware upgrade jobs in System > Firmware Upgrade Jobs. Troubleshooting a Newly Discovered Down Device If the device status on the APs/Devices > List page remains Down after it has been added to a group, the most likely source of the problem is an error in the SNMP community string being used to manage the device. Perform the following steps to troubleshoot this scenario. 1. Select the Name of the down device in the list of devices on the APs/Devices > List or APs/Devices > Down page. This automatically directs you to the APs/Device > Monitor page for that device. 2. Locate the Status field in the Device Info section. If the Status is Down, it includes a description of the cause of the problem. Some of the common system messages are as follows in Table 88: Table 88 Common System Messages for Down Status Message AP is no longer associated with controller Controller is Down Downloading Error fetching existing configuration Meaning This means the AP no longer shows up in any controller's AP list (on the OV3600 server). Either the AP was removed from the controller, or it has roamed to another controller that OV3600 does not have visibility to, or it is offline. When a controller goes down, AMP automatically marks all associated thin APs down (because communication to thin APs are via the controller and OV3600 assumes that if the Controller has gone offline then all associated APs are down as well until reassociated another Controller). The AP is in the process of downloading firmware or configuration (only applies to Cisco WLC thin APs and some Symbol APs). AMP could not fetch a config for the AP. Usually this is because the AMP has incorrect credentials and was not able to log in. 146 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

147 Table 88 Common System Messages for Down Status (Continued) Message ICMP Ping Failed (after SNMP Get Failed) SNMP Get Failed SNMP Trap Telnet Error: command timed out Unexpected LAN MAC Address found at this device s IP address Meaning The device is not responding and is likely offline. SNMP credentials and/or configuration may be incorrect. Verify that SNMP is enabled and that credentials and access ports are configured correctly on both the target device and in OV3600. AMP received an SNMP trap from the controller indicating that the AP is no longer associated to the controller. Telnet/SSH username and password specified for that device is incorrect. If AMP detects that the LAN MAC address of a device has changed this error message will appear. This usually indicates that a physical hardware change has occurred (while reusing the same IP Address) without using the Replace Hardware feature in OV3600. This error may also indicate an IP address conflict between two or more devices. When an unexpected LAN MAC address is seen in a device's IP address, its APs/ Devices > Manage page displays the message Click Replace Hardware (preferred) or Reset MAC Address to reset the LAN MAC address if this device has been replaced with new hardware at the top of the page. Use the Replace Hardware button at the bottom of that page in order to avoid this message. To view the detailed status of all your down devices at once, navigate to APs/Devices > Down (try the Down top header stats link) and look at the Detailed Status column for the list of down devices. This column can be sorted using the Filter icon ( ). 3. If the SNMP Get Failed message appears, select the APs/Devices > Manage tab to go to the management page for that device. 4. If visible, select the View Device Credentials link in the Device Communications section of APs/ Devices > Manage. This displays the credentials OV3600 is using unsuccessfully to communicate with the device. This link can be removed from OV3600 for security reasons by setting a flag in OV3600. Only users with root access to the OV3600 command line can show or hide this link. To disable this feature, please contact Alcatel-Lucent support. Figure 112 illustrates this page. Figure 112 View Device Credentials Window The View Device Credentials message may appear slightly different depending on the vendor and model. 5. If the credentials are incorrect, return to the Device Communications area on the APs/Devices > Manage page. Enter the appropriate credentials, and select Apply. 6. Return to the APs/Devices > List page to see if the device appears with a Status of Up. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 147

148 Setting up Alcatel-Lucent Spectrum Analysis in OV3600 The spectrum analysis software modules on Alcatel-Lucent AP models AP-105, RAP-5WN, the AP-12x series, the AP-13x series and the AP-9x series can examine the radio frequency (RF) environment in which the Wi-Fi network is operating, identify interference and classify its sources. The spectrum analyzer is used in conjunction with Alcatel-Lucent's Adaptive Radio Management (ARM) technology. While the spectrum analyzer identifies and classifies Wi-Fi and non-wi-fi sources of interference, ARM automatically ensures that APs serving clients will stay clear of interference. Individual APs or groups of APs can be converted to dedicated spectrum monitors through the dot11a and dot11g radio profiles of that AP or AP group, or through a special spectrum override profile. Each a and g radio profile references a spectrum profile, which identifies the spectrum band the radio will monitor and analyze, and defines the default ageout times for each monitored device type. By default, an a radio profile references a spectrum profile named default-a (which configures the radio to monitor the upper channels of the 5 GHz radio band), and an g radio profile references a spectrum profile named default-g (which configures the radio to monitor all channels the 2.4 GHz radio band). Most interference will occur in the 2.4 GHz radio band. For more information about Spectrum analysis and ARM technology, refer to the AOS-W User Guide. Spectrum Configurations and Prerequisites The following prerequisites must be in place to configure an AP to run in spectrum mode in OV3600: The AP must be in Manage Read/Write mode. The AP s associated switch must have an RFprotect license, and must run AOS-W 6.0 or later. Alcatel-Lucent GUI Config must be enabled for that AP s group in the Groups > Basic page. There are three main situations in which you would set one or more devices to Spectrum mode in OV3600: Alcatel-Lucent AP Groups running permanently with the default Spectrum profile Individual APs running temporarily in Spectrum mode while part of an Alcatel-Lucent AP Group set to ap-mode Switch-level Spectrum Overrides (an alternative to creating new Alcatel-Lucent AP groups or new radio profiles for temporary changes) Setting up a Permanent Spectrum Alcatel-Lucent AP Group If you have multiple supported Alcatel-Lucent APs in multiple switches that you want to run in Spectrum mode over the long run, you create a special Alcatel-Lucent AP group and set up a profile that is set to spectrum-mode and references the default Spectrum profile. Set up more than one profile if you want to utilize both radio bands in Spectrum mode. If you use an a or g radio profile to create a group of spectrum monitors, all APs in any AP group referencing that radio profile will be set to spectrum mode. Therefore, best practices are to create a new a or g radio profile just for spectrum monitors. If you have Global Alcatel-Lucent Configuration enabled in OV3600 Setup > General, create the configuration below, then go to the switch group's Alcatel-Lucent Config page and select the newly created Alcatel-Lucent AP Group. Perform these steps to set the AP group to use the default Spectrum profile settings: 1. In Groups > Alcatel-Lucent Config, select Add New Alcatel-Lucent AP Group. 2. Give the new Group a name (like Spectrum APs ) and select the plus sign next to the a Radio Profile to create a new radio profile. 3. Enter a name under the General Settings section of Profiles > RF > a/g Radio. 148 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

149 4. In the Other Settings section, change the Mode field from ap-mode to spectrum-mode, as illustrated in Figure 113. Then select Save. Figure 113 Spectrum mode in Alcatel-Lucent Configuration The above steps will use the defaults in the referenced Spectrum Profile. To change the defaults, navigate to Groups > Alcatel-Lucent Config > Profiles > RF > a/g Radio > Spectrum and create a new Spectrum profile with non-default settings. In most cases, you should not change the settings in the default profile. If all of the devices in this Alcatel-Lucent AP Group are managed by the same switch and you want to temporarily override one or more profile settings in your spectrum-mode APs, you can set up a switch override. To disable spectrum mode in this group, change the referenced radio profile back to default. Configuring an Individual AP to run in Spectrum Mode If you want to temporarily set an individual radio in an AP to run in Spectrum mode without creating or changing Alcatel-Lucent AP Groups or radio profiles, perform these steps to set up a Spectrum Override on a supported Alcatel-Lucent AP: 1. Go to the APs/Devices > Manage page for a Spectrum-supported AP (OAW-AP105, OAW-AP120 Series, OAW-AP90 and OAW-AP130 Series). 2. After checking the Audit page, set the AP to Manage Read/Write mode. 3. Select Yes on the Spectrum Override field for one or both radios, depending on the band and channels you want it to analyze. 4. Select the band that should run in spectrum. If you selected the 5GHz band in the an Radio section, choose the lower, middle, or upper range of channels that you want to be analyzed by this radio. 5. Select Save and Apply and confirm your edit. This overrides the current Mode setting for that AP (ap-mode or am-mode). After making this change, you can view the Radio Role field that will appear in the Radios section of the APs/Devices > Monitor page. The new role, Spectrum Sensor, is a link to the Spectrum Analysis page for the switch that manages this AP, as illustrated in Figure 114. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 149

150 Figure 114 Spectrum Analysis on Switch Dashboard This chart is only available for AP models AP-105, AP-90, and the AP-130 Series. To disable Spectrum mode on this individual AP after it has collected data, return to the APs/Devices > Manage page for this AP and set the Spectrum Override field back to No. Configuring a Switch to use the Spectrum Profile You can use OV3600 to customize individual fields in the profile instance used by a particular switch without having to create new Alcatel-Lucent AP groups and new radio profiles. To do this, you can set a switch-level override for its referenced Spectrum profile, as illustrated in Figure 115. This will affect all Spectrum-supported APs managed by this switch. Figure 115 Override Section of a Supported Switch s Manage Page Perform these steps to override individual profile settings for an Alcatel-Lucent switch that is part of a spectrum-mode Alcatel-Lucent AP group: 1. Select a Spectrum-supported Alcatel-Lucent switch that is referencing a Spectrum profile, and go to its APs/Devices > Manage page. Set it to Manage Read/Write mode. 2. Under the Alcatel-Lucent Overrides section, select Add New Alcatel-Lucent Switch Override. 3. In the Profile drop-down menu, select the Spectrum Profile type. 4. In the Profile Instance drop-down menu, select the instance of the Spectrum profile used by the switch. 150 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

151 5. In the Field drop-down menu, select the setting you would like to change (such as an Age-Out setting or a Spectrum Band), and enter the overriding value below it. 6. Select Add to save your changes. 7. To create additional overrides for this switch, select Add New Alcatel-Lucent Switch Override again. 8. When you have finished, select Save and Apply. You can also use the above procedure to turn on Spectrum mode for radio profiles on one particular switch, or use the overrides to point your radio profile to a non-default Spectrum profile for just this switch. OmniVista 3600 Air Manager 7.4 User Guide Discovering, Adding, and Managing Devices 151

152 152 Discovering, Adding, and Managing Devices OmniVista 3600 Air Manager 7.4 User Guide

153 Chapter 6 Creating and Using Templates This chapter provides an overview and several tasks supporting the use of device configuration templates in OV3600, and contains the following topics: Group Templates on page 153 Viewing and Adding Templates on page 154 Configuring General Template Files and Variables on page 157 Configuring Cisco IOS Templates on page 162 Configuring Cisco Catalyst Switch Templates on page 164 Configuring Symbol Controller / HP WESM Templates on page 165 Configuring a Global Template on page 166 Group Templates Supported Device Templates Templates are helpful configuration tools that allow OV3600 to manage virtually all device settings. A template uses variables to adjust for minor configuration differences between devices. The Groups > Templates configuration page allows you to create configuration templates for the following types of devices: Dell PowerConnect W Aruba Alcatel-Lucent Use the graphical Alcatel-Lucent Config feature in support of Alcatel-Lucent devices, particularly for AOS-W x and later. Refer to the OmniVista 3600 Air Manager 7.4 Configuration Guide for additional information. Cisco Aironet IOS autonomous APs Cisco Catalyst switches HP ProCurve 530 and WeSM controllers Nomadix Symbol Trapeze 3Com Nortel Enterasys Template Variables Variables in templates configure device-specific properties, such as name, IP address and channel. Variables can also be used to configure group-level properties, such as SSID and RADIUS server, which may differ from one group to the next. The OV3600 template understands many variables including the following: OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 153

154 %ap_include_1% through %ap_include_10% %channel% %hostname% %ip_address% %ofdmpower% The variable settings correspond to device-specific values on the APs/Devices > Manage configuration page for the specific AP that is getting configured. Changes made on the other Group pages (Radio, Security, VLANs, SSIDs, and so forth) are not applied to any APs that are configured by templates. Viewing and Adding Templates Perform these steps to display, add, or edit templates. 1. Go to the Groups > List page, and select a group for which to add or edit templates. This can be a new group, created with the Add button, or you can edit an existing group by selecting the corresponding pencil icon. The Groups > Basic page for that group appears.additional information about adding and editing groups is described in Configuring and Using Device Groups on page From the OV3600 navigation pane, select Templates. The Templates page appears. Figure 116 illustrates the Groups > Templates configuration page, and Table 89 describes the columns. Figure 116 Groups > Templates Page Illustration for a Sample Device Group Table 89 Groups > Templates Fields and Default Values Setting Notes Name Device Type Status Fetch Date Description When applicable, this section lists devices that are active on the network with no template available for the respective firmware. Select the link from such a note to launch the Add Template configuration page for that device. Displays the template name. Displays the template that applies to APs or devices of the specified type. If vendor (Any Model) is selected, the template applies to all models from that vendor that do not have a version specific template defined. If there are two templates that might apply to a device, the template with the most restrictions takes precedence. Displays the status of the template. Sets the date that the template was originally fetched from a device. 154 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

155 Table 89 Groups > Templates Fields and Default Values (Continued) Setting Version Restriction Description Designates that the template only applies to APs running the version of firmware specified. If the restriction is None, then the template applies to all the devices of the specified type in the group. If there are two templates that might apply to a device the template with the most restrictions takes precedence. If there is a template that matches a devices firmware it will be used instead of a template that does not have a version restriction. 3. To create a new template and add it to the OV3600 template inventory, go to the Groups > List page, and select the group name, and the Details page appears. Select Templates, then Add. 4. Complete the configurations illustrated in Figure 117, and the settings described in Table 90. OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 155

156 Figure 117 Groups > Templates > Add Template Page Illustration Table 90 Groups > Templates > Add Template Fields and Default Values Setting Default Description Use Global Template No Uses a global template that has been previously configured on the Groups > Templates configuration page. Available templates will appear in the drop-down menu. If Yes is selected you can also configure global template variables. For Symbol devices you can select the groups of thin APs to which the template should be applied. For more information about global templates, see the Groups > Templates section of the User Guide. 156 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

157 Table 90 Groups > Templates > Add Template Fields and Default Values (Continued) Setting Default Description Fetch None Selects an AP from which to fetch a configuration. The configuration will be turned into a template with basic AP specific settings like channel and power turned into variables. The variables are filled with the data on the APs/Devices > Manage page for each AP. Name None Defines the template display name. AP Type Reboot APs After Configuration Changes Restrict to this version Template firmware version Cisco IOS (Any Model) No No None Determines that the template applies to APs or devices of the specified type. If Cisco IOS (Any Model) is selected, the template applies to all IOS APs that do not have a version specific template specified. Determines reboot when OV3600 applies the template, copied from the new configuration file to the startup configuration file on the AP. If No is selected, OV3600 uses the AP to merge the startup and running configurations. If Yes is selected, the configuration is copied to the startup configuration file and the AP is rebooted. This field is only visible for some devices. Restricts the template to APs of the specified firmware version. If Yes is selected, the template only applies to APs on the version of firmware specified in the Template Firmware Version field. Designates that the template only applies to APs running the version of firmware specified. Community String None If the template is updating the community strings on the AP, enter the new community string OV3600 should use here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. Telnet/SSH Username Telnet/SSH Password None None If the template is updating the Telnet/SSH Username on the AP, enter the new username OV3600 should use here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. If the template is updating the Telnet/SSH password on the AP, enter the new Telnet/SSH password OV3600 should use here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. "enable" Password None If the template is updating the enable password on the AP, enter the new enable password OV3600 should use here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. SNMPv3 Username None If the template is updating the SNMP v3 Username password on the AP, enter the new SNMP Username password here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. Auth Password None If the template is updating the SNMP v3 Auth password on the AP, enter the new SNMP Username password here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. Privacy Password None If the template is updating the SNMP v3 Privacy password on the AP, enter the new SNMP Username password here. OV3600 updates the credentials it is using to communicate to the device after the device has been managed. SNMPv3 Auth Protocol SNMPv3 Privacy Protocol MD5 DES Specifies the SNMPv3 Auth protocol, either MD5 or SHA-1. Specifies the SNMPv3 Privacy protocol, either DES or AES. Configuring General Template Files and Variables This section describes the most general aspects of configuring AP device templates and the most common variables: Configuring General Templates Using Template Syntax Using Directives to Eliminate Reporting of Configuration Mismatches Using Conditional Variables in Templates OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 157

158 Using Substitution Variables in Templates Using AP-Specific Variables Configuring General Templates Perform the following steps to configure Templates within a Group. 1. Select a Group to configure. Start with a small group of access points and placing these APs in Monitor Only mode, which is read-only. Do this using the Modify Devices link until you are fully familiar with the template configuration process. This prevents configuration changes from being applied to the APs until you are sure you have the correct configuration specified. 2. Select an AP from the Group to serve as a model AP for the others in the Group. You should select a device that is configured currently with all the desired settings. If any APs in the group have two radios, make sure to select a model AP that has two radios and that both are configured in proper and operational fashion. 3. Go to the Groups > Templates configuration page. Select Add to add a new template. 4. Select the type of device that will be configured by this template. 5. Select the model AP from the drop-down list, and select Fetch. 6. OV3600 automatically attempts to replace some values from the configuration of that AP with variables to enable AP-specific options to be set on an AP-by-AP basis. Refer to Using Template Syntax on page 159 These variables are always encapsulated between % signs. On the right side of the configuration page is the Additional Variables section. This section lists all available variables for your template. Variables that are in use in a template are green, while variables that are not yet in use are black. Verify these substitutions to ensure that all of the settings that you believe should be managed on an AP-by-AP basis are labeled as variables in this fashion. If you believe that any AP-level settings are not marked correctly, please contact AlcatelOV3600 support before proceeding. 7. Specify the device types for the template. The templates only apply to devices of the specified type. Specify whether OV3600 should reboot the devices after a configuration push. If the Reboot Devices after Configuration Changes option is selected, then OV3600 instructs the AP to copy the configuration from OV3600 to the startup configuration file of the AP and reboot the AP. If the Reboot Devices after Configuration Changes option is not selected, then OV3600 instructs the AP to copy the configuration to the startup configuration file and then tell the AP to copy the startup configuration file to the running configuration file. Use the reboot option when there are changes requiring reboot to take effect, for example, removing a new SSID from a Cisco IOS device. Copying the configuration from startup configuration file to running configuration file merges the two configurations and can cause undesired configuration lines to remain active on the AP. 8. Restrict the template to apply only to the specified version of firmware. If the template should only apply to a specific version of firmware, select Yes and enter the firmware version in the Template Firmware Version text field. 9. Select Save and Apply to push the configuration to all of the devices in the group. If the devices are in monitor-only mode (which is recommended while you are crafting changes to a template or creating a new one), then OV3600 will audit the devices and compare their current configuration to the one defined in the template. If you set the reboot flag to No, then some changes could result in configuration mismatches until the AP is rebooted. 158 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

159 For example, changing the SSID on Cisco IOS APs requires the AP to be rebooted. Two other settings that require the AP to be rebooted for configuration change are Logging and NTP. A configuration mismatch results if the AP is not rebooted. If logging and NTP service are not required according to the Group configuration, but are enabled on the AP, you would see a configuration file mismatch as follows if the AP is not rebooted: IOS Configuration File Template (no logging queue-limit) Device Configuration File on APs/Devices > Audit Configuration Page line con 0 line vty 5 15 actual logging actual logging actual logging facility local6 actual logging queue-limit 100 actual logging trap debugging no service pad actual ntp clock-period actual ntp server radius-server attribute 32 include-in-access-req format %h 10. Once the template is correct and all mismatches are verified on the APs/Devices > Audit configuration page, use the Modify Devices link on the Groups > Monitor configuration page to place the desired devices into Management mode. This removes the APs from Monitor mode (read-only) and instructs the AP to pull down its new startup configuration file from OV3600. Devices can be placed into Management mode individually from the APs/Devices > Manage configuration page. Using Template Syntax Template syntax is comprised of the following components, described in this section: Using AP-Specific Variables Using Directives to Eliminate Reporting of Configuration Mismatches Using Conditional Variables in Templates Using Substitution Variables in Templates Using Directives to Eliminate Reporting of Configuration Mismatches OV3600 is designed to audit AP configurations to ensure that the actual configuration of the access point exactly matches the Group template. When a configuration mismatch is detected, OV3600 generates an automatic alert and flags the AP as having a Mismatched configuration status on the user page. However, when using the templates configuration function, there will be times when the running-config file and the startup-config file do not match under normal circumstances. For example, the ntp clock-period setting is almost never identical in the running-config file and the startup-config file. You can use directives such as <ignore_and_do_not_push> to customize the template to keep OV3600 from reporting mismatches for this type of variance. OV3600 provides two types of directives that can be used within a template to control how OV3600 constructs the startup-config file to send to each AP and whether it reports variances between the runningconfig file and the startup-config file as "configuration mismatches. Lines enclosed in <push_and_exclude> are included in the AP startup-config file but OV3600 ignores them when verifying OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 159

160 configurations. Lines enclosed in <ignore_and_do_not_push> cause OV3600 to ignore those lines during configuration verification. Ignore_and_do_not_push Command The ignore and do not push directive should typically be used when a value cannot be configured on the device, but always appears in the running-config file. Lines enclosed in the ignore and do not push directive will not be included in the startup-config file that is copied to each AP. When OV3600 is comparing the running-config file to the startup-config file for configuration verification, it will ignore any lines in the running-config file that start with the text within the directive. Lines belonging to an ignored and unpushed line, the lines immediately below the line and indented, are ignored as well. In the example below, if you were to bracket NTP server, the NTP clock period would behave as if it were bracketed because it belongs or is associated with the NTP server line. The line <ignore_and_do_not_push>ntp clock-period</ignore_and_do_not_push> will cause lines starting with "ntp clock-period" to be ignored. However, the line <ignore_and_do_not_push>ntp </ignore_and_do_not_push> causes all lines starting with "ntp" to be ignored, so it is important to be as specific as possible. Push_and_exclude Command Instead of using the full tags you may use the parenthesis shorthand, (substring). The push and exclude directive is used to push commands to the AP that will not appear in the running-config file. For example, some no commands that are used to remove SSIDs or remove configuration parameters do not appear in the running-config file of a device. A command inside the push and exclude directive are included in the startup-config file pushed to a device, but OV3600 excludes them when calculating and reporting configuration mismatches. The opening tag may have leading spaces. Below are some examples of using directives: line con 0 </push_and_exclude>no stopbits</push_and_exclude> line vty 5 15! ntp server <ignore_and_do_not_push>ntp clock-period</ignore_and_do_not_push> end Using Conditional Variables in Templates Conditional variables allow lines in the template to be applied only to access points where the enclosed commands will be applicable and not to any other access points within the Group. For example, if a group of APs consists of dual-radio Cisco 1200 devices (802.11a/b) and single-radio Cisco 1100 (802.11b) devices, it is necessary to make commands related to the a device in the 1200 APs conditional. Conditional variables are listed in the table below. The syntax for conditional variables is as follows, and syntax components are described in Table 91: %if variable=value% %endif% 160 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

161 Table 91 Conditional Variable Syntax Components Variable Values Meaning interface Dot11Radio0 2.4GHz radio module is installed Dot11Radio1 5GHz external radio module is installed radio_type a Installed 5GHz radio module is a b g Installed 2.4GHz radio module is b only Installed 2.4GHz radio module is g capable wds_role backup The WDS role of the AP is the value selected in the dropdown menu on the client APs/Devices > Manage configuration page for the device. master IP Static IP address of the device is set statically on the AP Manage configuration page. DHCP IP address of the device is set dynamically using DHCP Using Substitution Variables in Templates Substitution variables are used to set AP-specific values on each AP in the group. It is obviously not desirable to set the IP address, hostname, and channel to the same values on every AP within a Group. The variables in Table 92 are substituted with values specified on each access point's APs/Devices > Manage configuration page within the OV3600 User page. Sometimes, the running-config file on the AP does not include the command for one of these variables because the value is set to the default. For example, when the transmission power is set to maximum (the default), the line power local maximum will not appear in the AP running-config file, although it will appear in the startup-config file. OV3600 would typically detect and flag this variance between the runningconfig file and startup-config file as a configuration mismatch. To prevent OV3600 from reporting a configuration mismatch between the desired startup-config file and the running-config file on the AP, OV3600 suppresses the lines in the desired configuration when auditing the AP configuration (similar to the way OV3600 suppresses lines enclosed in parentheses, which is explained below). A list of the default values that causes lines to be suppressed when reporting configuration mismatches is shown in Table 92. Table 92 Substitution Variables in Templates Variable Meaning Command Suppressed Default hostname Name hostname %hostname% - channel Channel channel %channel% - ip_address netmask IP address Subnet mask ip address %ip_address% %netmask% or ip address dhcp gateway Gateway ip default-gateway %gateway% antenna_ receive Receive antenna antenna receive %antenna_receive% antenna_transmit Transmit antenna antenna transmit %antenna_transmit% cck_power ofdm_power g radio module CCK power level g radio module OFDM power level power local cck %cck_power% power local ofdm %ofdm_power% - - diversity diversity maximum maximum OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 161

162 Table 92 Substitution Variables in Templates (Continued) Variable Meaning Command Suppressed Default power location a and b radio module power level The location of the SNMP server. power local %power% snmp-server location %location% contact The SNMP server contact. snmp-server contact %contact% certificate ap include The SSL Certificate used by the AP The AP include fields allow for configurable variables. Any lines placed in the AP Include field on the APs/Devices > Manage configuration page replace this variable. %certificate% - %ap_include_1% through %ap_include_10% chassis id Serial Number of the device %chassis_id% - domain dns-domain of the device %domain% - interfaces Interfaces of the device %interfaces% - maximum Using AP-Specific Variables When a template is applied to an AP all variables are replaced with the corresponding settings from the APs/Devices > Manage configuration page. This enables AP-specific settings (such as Channel) to be managed effectively on an AP-by-AP basis. The list of used and available variables appears on the template detail configuration page. Variables are always encapsulated between % signs. The following example illustrates this usage: hostname %hostname% interface Dot11Radio0 power local cck %CCK_POWER% power local ofdm %OFDM_POWER% channel %CHANNEL% The hostname line sets the AP hostname to the hostname stored in OV3600. The power lines set the power local cck and ofdm values to the numerical values that are stored in OV3600. Configuring Cisco IOS Templates Cisco IOS access points have hundreds of configurable settings. OV3600 enables you to control them via the Groups > Templates configuration page. This page defines the startup-config file of the devices rather than using the OV3600 normal Group configuration pages. OV3600 no longer supports making changes for these devices via the browser-based page, but rather uses templates to configure all settings, including settings that were controlled formerly on the OV3600 Group configuration pages. Perform these steps to configure a Cisco IOS Template for use with one or more groups, and the associated devices. This section includes the following topics: Applying Startup-config Files WDS Settings in Templates SCP Required Settings in Templates 162 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

163 Supporting Multiple Radio Types via a Single IOS Template Configuring Single and Dual-Radio APs via a Single IOS Template Applying Startup-config Files Each of the APs in the Group copies its unique startup-config file from OV3600 via TFTP or SCP. If the Reboot Devices after Configuration Changes option is selected, then OV3600 instructs the AP to copy the configuration from OV3600 to the startup-config file of the AP and reboot the AP. If the Reboot Devices after Configuration Changes option is not selected, then OV3600 instructs the AP to copy the configuration to the startup-config file and then tell the AP to copy the startup config file to the running-config file. Use the reboot option when possible. Copying the configuration from startup to running merges the two configurations and can cause undesired configuration lines to remain active on the AP. Changes made on the standard OV3600 Group configuration pages, to include Basic, Radio, Security, VLANs, and so forth, are not applied to any template-based APs. WDS Settings in Templates A group template supports Cisco WDS settings. APs functioning in a WDS environment communicate with the Cisco WLSE via a WDS master. IOS APs can function in Master or Slave mode. Slave APs report their rogue findings to the WDS Master (AP or WLSM which reports the data back to the WLSE. On the APs/ Devices > Manage configuration page, select the proper role for the AP in the WDS Role drop down menu. The following example sets an AP as a WDS Slave with the following lines: %if wds_role=client% wlccp ap username wlse password 7 XXXXXXXXXX %endif% The following example sets an AP as a WDS Master with the following lines: %if wds_role=master% aaa authentication login method_wds group wds aaa group server radius wds server auth-port 1645 acct-port 1646 wlccp authentication-server infrastructure method_wds wlccp wds priority 200 interface BVI1 wlccp ap username wlse password 7 095B421A1C %endif% The following example sets an AP as a WDS Master Backup with the following lines: %if wds_role=backup% aaa authentication login method_wds group wds aaa group server radius wds server auth-port 1645 acct-port 1646 wlccp authentication-server infrastructure method_wds wlccp wds priority 250 interface BVI1 wlccp ap username wlse password 7 095B421A1C %endif% SCP Required Settings in Templates A few things must be set up before enabling SCP on the Groups > Basic configuration page. The credentials used by OV3600 to login to the AP must have level 15 privileges. Without them OV3600 is not able to communicate with the AP via SCP. The line "aaa authorization exec default local" must be in the APs configuration file and the AP must have the SCP server enabled. These three settings correspond to the following lines in the AP s configuration file: username Cisco privilege 15 password D0A16 OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 163

164 aaa authorization exec default local ip scp server enable The username line is a guideline and will vary based on the username being set, in this case Cisco, and the password and encoding type, in this case D0A16 and 7 respectively. These values can be set on a group wide level using Templates and TFTP. Once these lines are set, SCP can be enabled on the Groups > Basic configuration page without problems. Supporting Multiple Radio Types via a Single IOS Template Some lines in an IOS configuration file should only apply to g vs b. For instance, lines related to speed rates that mention rates above 11.0Mb/s do not work for b radios that cannot support these speeds.use the "%IF variable=value% %ENDIF%" construct to allow a single IOS configuration template to configure APs with different radio types within the same Group as illustrated below: interface Dot11Radio0 %IF radio_type=g% speed basic-1.0 basic-2.0 basic %ENDIF% %IF radio_type=b% speed basic %ENDIF% %IF radio_type=g% power local cck %CCK_POWER% power local ofdm %OFDM_POWER% %ENDIF% Configuring Single and Dual-Radio APs via a Single IOS Template To configure single and dual-radio APs using the same IOS config template, you can use the interface variable within the %IF % construct. The below example illustrates this usage: %IF interface=dot11radio1% interface Dot11Radio1 bridge-group 1 bridge-group 1 block-unknown-source bridge-group 1 spanning-disabled bridge-group 1 subscriber-loop-control no bridge-group 1 source-learning no bridge-group 1 unicast-flooding no ip address no ip route-cache rts threshold 2312 speed basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic ssid decibel-ios-a authentication open guest-mode station-role root %ENDIF% Configuring Cisco Catalyst Switch Templates Cisco Catalyst Switch templates are configured much like Cisco IOS templates with the addition of the interfaces and switch_command (for stacked switches) variables. Interfaces can be configured on the Device Interface pages, as shown in Configuring Device Interfaces for Switches on page 142. You can import interface information as described in this section or by fetching a template from that device, as described in Configuring General Templates on page 158. Just one template is used for any type of Cisco IOS device, and another is used for any type of Catalyst Switch regardless of individual model. 164 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

165 Configuring Symbol Controller / HP WESM Templates This section describes the configuration of templates for Symbol controllers and HP WESM devices. Symbol switches (RFS x000, 5100 and 2000) can be configured in OV3600 using templates. OV3600 supports Symbol thin AP firmware upgrades from the controller s manage page. A sample running-configuration file template is provided in this topic for reference. A template can be fetched from a model device using the Cisco IOS device procedure described in Configuring Cisco IOS Templates on page 162. Cisco IOS template directives such as ignore_and_do_not_push can also be applied to Symbol templates. Certain parameters such as hostname and location are turned into variables with the % tags so that devicespecific values can be read from the individual manage pages and inserted into the template. They are listed in Available Variable boxes on the right-hand side of the template fields. Certain settings have integrated variables, including ap-license and adoption-preference-id. The radio preamble has been template-integrated as well. An option on the Group > Templates page reboots the device after pushing a configuration to it. A sample Symbol controller partial template is included below for reference.!! configuration of RFS4000 version R! version 1.4!! aaa authentication login default local none service prompt crash-info! network-element-id RFS4000! username admin password 1 5baa61e4c9b93f3f b6cf8331b7ee68fd8 username admin privilege superuser username operator password 1 fe96dd39756ac41b74283a d366d73931f!! access-list 100 permit ip /24 any rule-precedence 10! spanning-tree mst cisco-interoperability enable spanning-tree mst configuration name My Name! ip dns-server-forward wwan auth-type chap no bridge multiple-spanning-tree enable bridge-forward country-code us aap-ipfilter-list no port 3333 plz aap-ipfilter-list no port 3333 tcp plz deny tcp src-start-ip src-end-ip dst-start-ip dst-end-ip dst-start-port 3333 dst-end-port 3334 rule 1 %redundancy_config% logging buffered 4 logging console 4 snmp-server engineid netsnmp 6b8b45674b30f176 snmp-server location %location% snmp-server contact %contact% snmp-server sysname %hostname% snmp-server manager v2 snmp-server manager v3 snmp-server user snmptrap v3 encrypted auth md5 0x1aa491f4ca7c55df0f57801bece9044c snmp-server user snmpmanager v3 encrypted auth md5 0x1aa491f4ca7c55df0f57801bece9044c snmp-server user snmpoperator v3 encrypted auth md5 0xb03b1ebfa0e3d02f50e2b1c092ab7c9f A sample Symbol Smart RF template is provided below for reference: radio %radio_index% radio-mac %radio_mac% %if radio_type=11a% radio %radio_index% coverage-rate 18 OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 165

166 %endif% %if radio_type=11an% radio %radio_index% coverage-rate 18 %endif% %if radio_type=11b% radio %radio_index% coverage-rate 5p5 %endif% %if radio_type=11bg% radio %radio_index% coverage-rate 6 %endif% %if radio_type=11bgn% radio %radio_index% coverage-rate 18 %endif% A sample Symbol thin AP template is provided below for reference and for the formatting of if statements. radio add %radio_index% %lan_mac% %radio_type% %ap_type% radio %radio_index% radio-number %radio_number% radio %radio_index% description %description% %if radio_type=11a% radio %radio_index% speed basic6 9 basic12 18 basic radio %radio_index% antenna-mode primary radio %radio_index% self-heal-offset 1 radio %radio_index% beacon-interval 99 radio %radio_index% rts-threshold 2345 radio %radio_index% max-mobile-units 25 radio %radio_index% admission-control voice max-perc 76 radio %radio_index% admission-control voice res-roam-perc 11 radio %radio_index% admission-control voice max-mus 101 radio %radio_index% admission-control voice max-roamed-mus 11 %endif% %if radio_type=11an% radio %radio_index% speed basic11a mcs 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %endif% %if radio_type=11b% radio %radio_index% speed basic1 basic2 basic5p5 basic11 %endif% %if radio_type=11bg% radio %radio_index% speed basic1 basic2 basic5p5 6 9 basic radio %radio_index% on-channel-scan radio %radio_index% adoption-pref-id 7 radio %radio_index% enhanced-beacon-table radio %radio_index% enhanced-probe-table %endif% %if radio_type=11bgn% radio %radio_index% speed basic11b mcs 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 %endif% radio %radio_index% channel-power indoor %channel% %transmit_power% %channel_attribute% %detector% %adoption_pref_id% radio %radio_index% enhanced-beacon-table radio %radio_index% on-channel-scan %ap_include_4% Configuring a Global Template Global templates allow OV3600 users to define a single template in a global group that can be used to manage APs in subscriber groups. They turn settings like group RADIUS servers and encryption keys into variables that can be configured on a per-group basis. Perform the following steps to create a global template, or to view or edit an existing global template: 1. Go to the Group > Templates configuration page for the global group that owns it. 2. Select Add to add a new template, or select the pencil icon next to an existing template to edit it. 3. Examine the configurations illustrated in Figure Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

167 Figure 118 Group > Templates > Add Page Illustration 4. Use the drop-down menu to select a device from which to build the global template and select Fetch. The menus are populated with all devices that are contained in any group that subscribes to the global group. The fetched configuration populates the template field. Global template variables can be configured with the Add button in the Template Variables box, illustrated in Figure 119. Figure 119 Template Variables Illustration The variable name cannot have any spaces or non-alphanumeric characters. The initial variable value entered is the default value, but can be changed on a per-group basis later. You can also populate global template variables by uploading a CSV file (see below). 5. Once you have configured your global template, select Add. You are taken to a confirmation configuration page where you can review your changes. 6. If you want to add the global template, select Apply Changes Now. If you do not want to add the template, select Cancel and Discard Changes. Canceling from the confirmation configuration page causes the template and all of the template variables to be lost. 7. Once you have added a new global template, you can use a CSV upload option to configure global template variables. Go to the Groups > Templates configuration page and select the CSV upload icon for the template. The CSV file must contain columns for Group Name and Variable Name. All fields must be completed. Group Name the name of the subscriber group that you wish to update. Variable Name the name of the group template variable you wish to update. Variable Value the value to set. For example, for a global template with a variable called "ssid_1", the CSV file might resemble what follows: Group Name, ssid_1 Subscriber 1, Value 0 8. Once you have defined and saved a global template, it is available for use by any local group that subscribes to the global group. Go to the Groups > Template configuration page for the local group and select the pencil icon next to the global template in the list. Figure 120 illustrates this page. OmniVista 3600 Air Manager 7.4 User Guide Creating and Using Templates 167

168 Figure 120 Groups > Templates Edit, Upper Portion 9. To make template changes, go to the Groups > Template configuration page for the global group and select the pencil icon next to the template you wish to edit. Note that you cannot edit the template itself from the subscriber group's Groups > Templates tab. 10. If group template variables have been defined, you are able to edit the value for the group on the Groups > Templates, Add configuration page in the Group Template Variables box. For Symbol devices, you are also able to define the template per group of APs. For more information on using templates in OV3600, see the previous section of this chapter. It is also possible to create local templates in a subscriber group using global groups does not mean that global templates are mandatory. 168 Creating and Using Templates OmniVista 3600 Air Manager 7.4 User Guide

169 Chapter 7 Using RAPIDS and Rogue Classification This chapter provides an overview to rogue device and IDS event detection, alerting, and analysis using RAPIDS, and contains the following sections: Introduction to RAPIDS on page 169 Viewing Rogues on the RAPIDS > List Page on page 178 Setting Up RAPIDS on page 171 Defining RAPIDS Rules on page 174 Score Override on page 182 Using the Audit Log on page 183 Additional Resources on page 184 Introduction to RAPIDS Rogue device detection is a core component of wireless security. With RAPIDS rules engine and containment options, you can create a detailed definition of what constitutes a rogue device, and quickly act on a rogue AP for investigation, restrictive action, or both. Once rogue devices are discovered, RAPIDS alerts your security team of the possible threat and provides essential information needed to locate and manage the threat. RAPIDS discovers unauthorized devices in your WLAN network in the following ways: Over the Air, using your existing enterprise APs. On the Wire, by polling routers and switches to identify, classify, and locate unknown APs, using the switch s wired discovery information or via HTTP and SNMP scanning To set up a scan, refer to Discovering and Adding Devices on page 107. Furthermore, RAPIDS integrates with external intrusion detection systems (IDS), as follows: Alcatel-Lucent WIP The Wireless Intrusion Protection (WIP) module integrates wireless intrusion protection into the mobile edge infrastructure. The WIP module provides wired and wireless AP detection, classification and containment; detects DoS and impersonation attacks; and prevents client and network intrusions. Cisco WLSE (1100 and 1200 IOS) OV3600 fetches rogue information from the HTTP interface and gets new AP information from SOAP API. This system provides wireless discovery information rather than rogue detection information. AirMagnet Enterprise Retrieves a list of managed APs from OV3600. AirDefense Uses the OV3600 XML API to keep its list of managed devices up to date. WildPackets OmniPeek Retrieves a list of managed APs from OV3600. Viewing Overall Network Health on RAPIDS > Overview The RAPIDS > Overview page displays a page of RAPIDS summary information (see Figure 121). Table 93 defines the summary information that appears on the page. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 169

170 Figure 121 RAPIDS > Overview Page Illustration Table 93 RAPIDS > Overview Fields and Descriptions Summary IDS Events Description Displays a list of attack types for the designated folder and subfolders. Field displays events from the past two hours, the past 24 hours, and total IDS events. Names of attacks link to summary pages with more details. NOTE: OV3600 should be configured as the SNMP trap receiver on the controllers to receive IDS traps. See the Alcatel-Lucent Best Practices Guide for details. 170 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

171 Table 93 RAPIDS > Overview Fields and Descriptions (Continued) Summary Device Count by RAPIDS Classification RAPIDS Classification RAPIDS Devices by OS Operating System Acknowledged RAPIDS Devices RAPIDS Changes Description A pie chart of rogue device percentages by RAPIDS classification. A summary list with details of the statistics depicted in the Device Count by RAPIDS Classification pie chart. Click the linked classification name to be taken to a filtered rogue list. A pie chart of RAPIDS percentages by the detected operating system. Detected operating systems represented in this summary listing. Click on the linked Operating System name to see the rogues list filtered by that classification. OS scans can be run manually or enabled to run automatically on the RAPIDS > Setup page. A color coded pie chart comparing the number of acknowledged devices to the unacknowledged devices. Tracks every change made to RAPIDS including changes to rules, manual classification, and components on the RAPIDS > Setup page. A link at the top of the list directs you to the RAPIDS > Audit Log page. Setting Up RAPIDS The RAPIDS > Setup page allows you to configure your OV3600 server for RAPIDS. Complete the settings on this page as desired, and select Save. Most of the settings are internal to how OV3600 will process rogues. Basic Configuration On the RAPIDS > Setup page, the Basic Configuration section allows you to define RAPIDS behavior settings. Figure 122 illustrates this page and Figure 122 describes the fields: OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 171

172 Figure 122 RAPIDS > Setup Page Illustration Table 94 RAPIDS > Setup > Basic Configuration Fields Field Default Description ARP IP Match Timeout 24 If you have routers and switches on the OV3600, and it's scanning them for ARP tables, this can assign a rogue IP address information. This timeout specifies how recent that information needs to be for the IP address to be considered valid. Note that the default ARP poll period is long (several hours). RAPIDS Export Threshold Wired-to-Wireless MAC Address Correlation Wireless BSSID Correlation Delete Rogues not detected for (0-14 days, zero disables): Automatically OS scan rogue devices Suspected Rogue Exported rogues will be sent to VisualRF for location calculation. 4 Discovered BSSIDs and LAN MAC addresses which are within this bitmask will be combined into one device. 4 requires all but the last digit match (aa:bb:cc:dd:ee:fx). 8 requires all but the last two digits match (aa:bb:cc:dd:ee:xx). 4 Similar BSSIDs will be combined into one device when they fall within this bitmask. Setting this value too high may result in identifying two different physical devices as the same rogue. NOTE: When you change this value, RAPIDS will not immediately combine (or un-combine) rogue records. Changes will occur during subsequent processing of discovery events. 0 This value cannot be larger than the rogue discovery event expiration (14) configured on the OV3600 Setup page, unless that value is set to 0. No Whether to scan the operating system of rogues. Enabling this feature will cause RAPIDS to perform an OS scan when it gets in IP address for a rogue device. The OS scan will be run when a rogue gets an IP address for the first time or if the IP address changes. Table 95 RAPIDS > Setup > Classification Options Fields Field Default Description Acknowledge Rogues by Default Manually Classifying Rogues Automatically Acknowledges them No Yes Sets RAPIDS to acknowledge rogue devices upon initial detection, prior to their classification. Defines whether acknowledgement happens automatically whenever a rogue device receives a manual classification. 172 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

173 Filtered rogues are dropped from the system before they are processed through the rules engine. This can speed up overall performance but will eliminate all visibility into these types of devices. Table 96 RAPIDS > Setup > Filtering Options Field Default Description Ignore Ad-hoc rogues No Filters rogues according to ad-hoc status. Ignore Rogues by Signal Strength Ignore Rogues Discovered by Remote APs Ignore IDS Events from Remote APs No No No Filters rogues according to signal strength. Since anything below the established threshold will be ignored and possibly dangerous, best practices is to keep this setting disabled. Instead, incorporate signal strength into the classification rules on the RAPIDS > Rules page. Filters rogues according to the remote AP that discovers them. Enabling this option causes OV3600 to drop all rogue discovery information coming from remote APs. Filters IDS Events discovered by remote APs. Rogue Containment Options Using RAPIDS, OV3600 can shield rogue devices from associating to Cisco WLC controllers (versions and later), and Alcatel-Lucent switches (running AOS-W versions 3.x and later). OV3600 will alert you to the appearance of the rogue device and identify any mismatch between switch configuration and the desired configuration. WMS Offload is not required to manage containment in OV3600. Table 97 shows the Containment Options section of the RAPIDS > Setup page. Table 97 RAPIDS > Setup > Containment Options Fields and Default Values Field Default Description Manage rogue AP Containment Manage rogue AP containment in monitoronly mode Maximum number of APs to contain a rogue Yes No Rogue APs on Cisco WLC and Alcatel-Lucent controllers as defined by the Rules engine will be classified as a Contained Rogue. OV3600 pushes the containment status of a rogue device to the controller and the controller takes the appropriate action. For the rogue device to be contained, you may need to configure containment on the controller. If disabled, OV3600 will display the desired containment settings but will not push them to devices. This may result in mismatches in device classifications. This can be useful for administrators that want to see what RAPIDS would push to the controller without making any changes to their network. If enabled, OV3600 will push the desired containment settings to the controllers in Monitor-Only mode, as well as the devices in Managed mode. 3 Sets the maximum number of APs that will contain a rogue on Cisco WLC controllers. 1. Navigate to the RAPIDS > Setup page. 2. From the Containment Options section, select Yes in the Manage rogue AP containment field. Once this is done, the Contained Rogue classification will appear as an option in the classification drop down menu as shown in Figure 123. Additionally, once this option been enabled, the option to manage contained APs in Monitor-Only mode becomes available. Containment in Monitor-Only mode means configuration changes will still be pushed to the controller, even though it is in monitor-only mode. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 173

174 Figure 123 RAPIDS > Classification Rule Menu with Containment From the APs/Devices > Rogues Contained page, you can see the containment status information, as shown in Figure 124. The Rogue Containment device tab is only present for devices that support containment. Figure 124 Rogue Containment Status Page Additional Settings Additional RAPIDS settings such as role filtering and performance tuning are available in the following locations: Use the OV3600 Setup > Roles > Add/Edit Role Page to define the ability to use RAPIDS by user role. Refer to Creating OV3600 User Roles on page 47. Use the OV3600 Setup > General > Performance Tuning page to define the processing priority of RAPIDS in relation to OV3600 as a whole (see Table 18 on page 43). Defining RAPIDS Rules The RAPIDS > Rules page is one of the core components of RAPIDS. This feature allows you to define rules by which any detected device on the network is classified. This section describes how to define, use, and monitor RAPIDS rules, provides examples of such rules, and demonstrates how they are helpful. This section contains the following topics: Switch Classification with WMS Offload on page 174 Device OUI Score on page 175 Rogue Device Threat Level on page 175 Viewing and Configuring RAPIDS Rules on page 176 Recommended RAPIDS Rules on page 178 Using RAPIDS Rules with Additional OV3600 Functions on page 178 Switch Classification with WMS Offload This classification method is supported only when WMS offload is enabled on Alcatel-Lucent WLAN switches. Switch classification of this type remains distinct from RAPIDS classification. WLAN switches 174 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

175 feed wireless device information to OV3600, which OV3600 then processes. OV3600 then pushes the WMS classification to all of the AOS-W switches that are WMS offload enabled. WMS Offload ensures that a particular BSSID has the same classification on all of the switches. WMS Offload removes some load from master switches and feeds 'connected-to-lan' information to the RAPIDS classification engine. RAPIDS classifications and switch classifications are separate and often are not synchronized. RAPIDS classification is not pushed to the devices. The following table compares how default classification may differ between OV3600 and AOS-W for scenarios involving WMS Offload. Table 98 Rogue Device Classification Matrix OV3600 Unclassified (default state) Rogue Suspected Neighbor Neighbor Valid Contained Rogue AOS-W (ARM) Unknown Rogue Interfering Known Interfering Valid DOS For additional information about WMS Offload, refer to the OmniVista 3600 Air Manager 7.4 Best Practices Guide in Home > Documentation. Device OUI Score The Organizationally Unique Identifier (OUI) score is based on the LAN MAC address of a device. RAPIDS can be configured to poll your routers and switches for the bridge forwarding tables. RAPIDS then takes the MAC addresses from those tables and runs them through a proprietary database to derive the OUI score. The OUI score of each device is viewable from each rogue s detail page. Table 99 provides list the OUI scores definitions. Table 99 Device OUI Scores Score Description Score of 1 Indicates any device on the network; this is the lowest threat level on the network. Score of 2 Indicates any device in which the OUI belongs to a manufacturer that produces wireless (802.11) equipment. Score of 3 Score of 4 Indicates that the OUI matches a block that contains APs from vendors in the Enterprise and small office/ small home market. Indicates that the OUI matches a block that belonged to a manufacturer that produces small office/ small home access points. Rogue Device Threat Level The threat level classification adds granularity for each general RAPIDS classification. Devices of the same classification can have differing threat scores based on the classifying rule, ranging from 1 to 10 with a default value of 5. This classification process can help identify the greater threat. Alerts can be defined and sorted by threat level. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 175

176 Threat level and classification are both assigned to a device when a device matches a rule. Once classified, a device s classification and threat level change only if it is classified by a new rule or is manually changed. Threats levels can be manually defined on the RAPIDS > Detail page when the RAPIDS classification is manually overridden or you can edit the rule to have a higher threat level. Viewing and Configuring RAPIDS Rules To view the RAPIDS rules that are currently configured on OV3600, navigate to the RAPIDS > Rules page (Figure 125). Figure 125 RAPIDS > Rules Page Illustration Table 100 defines the fields in the RAPIDS > Rules page. Table 100 RAPIDS > Rules Page Field Default Classification Add New RAPIDS Classification Rule Rule Name Classification Threat Level Enabled Reorder Drag and Drop Icon Description Sets the classification that a rogue device receives when it does not match any rules. Select this button to create a RAPIDS classification rule. Displays the name of any rule that has been configured. Rule names should be descriptive and should convey the core purpose for which it was created. Displays the classification that devices receive if they meeting the rule criteria. Displays the numeric threat level for the rogue device that pertains to the rule. Refer to Rogue Device Threat Level on page 175 for additional information. Displays the status of the rule, whether enabled or disabled. Changes the sequence of rules in relation to each other. Select, then drag and drop, the icon for any rule to move it up or down in relation to other rules. A revised sequence of rules must be saved before rogues are classified in the revised sequence. NOTE: The sequence of rules is very important for proper rogue classification. A device gets classified by the first rule to which it complies, even if it conforms to additional rules later in the sequence. To create a new rule, select the Add button next to New RAPIDS Classification Rule to launch the RAPIDS Classification Rule page (see Figure 126). Figure 126 Classification Rule Page 176 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

177 Fill in the settings described in Table 100 then select an option from the drop down menu. Table 101 defines the drop down menu options that are at the bottom left of the RAPIDS Classification Rule dialog box (see Figure 126). Once all rule settings are defined, select Add. The new rule automatically appears in the RAPIDS > Rules page. Table 101 Properties Drop Down Menu Option Description Wireless Properties Detected on WLAN Detecting AP Count Encryption Network type Signal Strength SSID Detected Client Count Classifies based on how the rogue is detected on the wireless LAN. Classifies based on the number of managed devices that can hear the rogue. Enter a numeric value and select At Least or At Most. Classifies based on the rogue matching a specified encryption method. Note that you can select for 'no encryption' with a rule that says Encryption does not match WEP or better. Rogue is running on the selected network type, either Ad-hoc or Infrastructure. Rogue matches signal strength parameters. Specify a minimum and maximum value in dbm. Classifies the rogue when it matches or does not match the specified string for the SSID or a specified regular expression. NOTE: For SSID matching functions, OV3600 processes only alpha-numeric characters and the asterisk wildcard character (*). OV3600 ignores all other non-alpha-numeric characters. For example, the string of ethersphere-* matches the SSID of ethersphere-wpa2 but also the SSID of ethersphere_this_is_an_example (without any dashes). Classifies based on the number of valid clients. Wireline Properties Detected on LAN Fingerprint Scan IP Address OUI Score Operating System Rogue is detected on the wired network. Select Yes or No. Rogue matches fingerprint parameters. Rogue matches a specified IP address or subnet. Enter IP address or subnet information as explained by the fields. Rogue matches manufacturer OUI criteria. You can specify minimum and maximum OUI score settings from two drop-down lists. Select remove to remove one or both criteria, as desired. Rogue matches OS criteria. Specify matching or non-matching OS criteria as prompted by the fields. Wireless/Wireline Properties Manufacturer MAC Address Rogue matches the manufacturer information of the rogue device. Specify matching or non-matching manufacturer criteria. Rogue matches the MAC address. Specify matching or non-matching address criteria, or use a wildcard (*) for partial matches. Alcatel-Lucent Controller Properties Controller Classification Rogue matches the specified controller classification. Confidence Rogue falls within a specified minimum and maximum confidence level, ranging from 1 to 100. After creating a new rule, select Add to return to the RAPIDS > Rules page. Select Save and Apply to have the new rule take effect. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 177

178 Deleting or Editing a Rule To delete a rule from the RAPIDS rules list, go to the RAPIDS > Rules page. Select the check box next to the rule you want to delete, and select Delete. The rule is automatically deleted from RAPIDS > Rules. To edit any existing rule, select its pencil icon to launch the RAPIDS Classification Rule page (see Figure 126). Edit or revise the fields as necessary, then select Save. To change the sequence in which rules apply to any rogue device, drag and drop the rule to a new position in the rules sequence. Recommended RAPIDS Rules If Any Device Has Your SSID, Then Classify as Rogue The only devices broadcasting your corporate SSID should be devices that you are aware of and are managed by OV3600. Rogue devices often broadcast your official SSID in an attempt to get access to your users, or to trick your users into providing their authentication credentials. Devices with your SSID generally pose a severe threat. This rule helps to discover, flag, and emphasize such a device for prompt response on your part. If Any Device Has Your SSID and is Not an Ad-Hoc Network Type, Then Classify as Rogue This rule classifies a device as a rogue when the SSID for a given device is your SSID and is not an Ad- Hoc device. Windows XP automatically tries to create an Ad-hoc network if it can not find the SSID for which it is searching. This means that user s laptops on your network may appear as Ad-Hoc devices that are broadcasting your SSID. If this happens too frequently, you can restrict the rule to apply to non-adhoc devices. If More Than Four APs Have Discovered a Device, Then Classify as Rogue By default, OV3600 tries to use Signal Strength to determine if a device is on your premises. Hearing device count is another metric that can be used. The important concept in this scenario is that legitimate neighboring devices are only heard by a few APs on the edge of your network. Devices that are heard by a large number of your APs are likely to be in the heart of your campus. This rule works best for scenarios in large campuses or that occupy an entire building. For additional rules that may help you in your specific network scenario, contact Alcatel support. Using RAPIDS Rules with Additional OV3600 Functions Rules that you configure on the RAPIDS > Rules page establish an important way of processing rogue devices on your network, and flagging them for attention as required. Such devices appear on the following pages in OV3600, with additional information: RAPIDS > List Lists rogue devices as classified by rules. RAPIDS > Rules Displays the rules that classify rogue devices. RAPIDS > Overview Displays general rogue device count and statistical information. System > Triggers Displays triggers that are currently configured, including any triggers that have been defined for rogue events. Reports > Definitions Allows you to run New Rogue Devices Report with custom settings. VisualRF Displays physical location information for rogue devices. Viewing Rogues on the RAPIDS > List Page To view a rogue AP, select the RAPIDS > List tab and select a rogue device type from the Minimum Classification drop-down menu (see Figure 127). You can sort the table columns (up/down) by selecting the column head. Most columns can be filtered using the funnel icon ( ). The active links on this page launch additional pages for RAPIDS configuration or device processing. 178 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

179 Figure 127 RAPIDS > List Page Illustration (partial view) Table 102 details the column information displayed in Figure 127. For additional information about RAPIDS rules, refer to Defining RAPIDS Rules on page 174. Table 102 RAPIDS > List Column Definitions Column Ack RAPIDS Classification Threat Level Name Classifying Rule Current Associations Max associations Controller Classification WMS Classification AP WMS Classification Date Confidence Wired Detecting APs Location Description Displays whether or not the rogue device has been acknowledged. Devices can be acknowledged manually or you can configure RAPIDS so that manually classifying rogues will automatically acknowledges them. Additionally, devices can be acknowledged by using Modify Devices link at the top of the RAPIDS > List page. Rogues should be acknowledged when the OV3600 user has investigated them and determined that they are not a threat (see Basic Configuration on page 171). Displays the current RAPIDS classification. This classification is determined by the rules defined on the RAPIDS > Rules page. This field displays the numeric threat level of the device, in a range from 1 to 10. The definition of threat level is configurable, as described in Rogue Device Threat Level on page 175. The threat level is also supported with Triggers (see Monitoring and Supporting OV3600 with the System Pages on page 185). Displays the alpha-numeric name of the rogue device, as known. By default, OV3600 assigns each rogue device a name derived from the OUI vendor and the final six digits of the MAC address. Clicking the linked name will redirect you to the RAPIDS > Detail page for that rogue device. Refer to Overview of the RAPIDS > Detail Page on page 181. Displays the RAPIDS Rule that classified the rogue device (see Viewing and Configuring RAPIDS Rules on page 176). The number of current rogue client associations to this device. The highest number of rogue client associations ever detected at one time. Displays the classification of the device based on the controller s hard-coded rules. NOTE: This column is hidden unless Offload WMS Database is enabled by at least one group on the Groups > Basic page. The AP that provided the information used to classify the device. Click the linked device name to be redirected to the APs/Devices > Monitor page for that AP. The date that WMS set the classification. The confidence level of the suspected rogue. How confidence is calculated varies based on the version of AOS-W. When an AOS-W switch sees evidence that a device might be on the wire it will up the confidence level. If AOS-W is completely sure that it is on the wire, it gets classified as a rogue. Displays whether the rogue device has been discovered on one of your wired networks by polling routers/switches, your SNMP/HTTP scans, or Alcatel-Lucent WIP information. This column displays Yes or is blank if wired information was not detected. Displays the number of AP devices that have wirelessly detected the rogue device. A designation of heard implies the device was heard over the air. If the rogue has been placed in VisualRF, this column will display the name of the floor plan the rogue is on as a link to the VisualRF Floor Plan View page. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 179

180 Table 102 RAPIDS > List Column Definitions (Continued) Column SSID Signal RSSI Network Type Encryption Type Ch LAN MAC Address LAN Vendor Radio MAC Address Radio Vendor OS Model IP Address Last Discovering AP Switch/Router Port Notes Last Seen Description Displays the most recent SSID that was heard from the rogue device. Displays the strongest signal strength detected for the rogue device. Displays Received Signal Strength Indication (RSSI) designation, a measure of the power present in a received radio signal. Displays the type of network in which the rogue is present, for example: Ad-hoc This type of network usually indicates that the rogue is a laptop that attempts to create a network with neighboring laptops, and is less likely to be a threat. AP This type of network usually indicates an infrastructure network, for example. This may be more of a threat. Unknown The network type is not known. Displays the encryption that is used by the device. Possible contents of this field include the following encryption types: Open No encryption WEP Wired Equivalent Privacy WPA Wi-Fi Protected Access Generally, this field alone does not provide enough information to determine if a device is a rogue, but it is a useful attribute. If a rogue is not running any encryption method, you have a wider security hole than with an AP that is using encryption. Indicates the most recent RF channel on which the rogue was detected. Note: it may be detected on more than one channel if it contains more than one radio. The LAN MAC address of the rogue device. Indicates the LAN vendor of the rogue device, when known. Displays the MAC address for the radio device, when known. Indicates the radio vendor of the rogue device, when known. This field displays the OS of the device, as known. OS is the result of a running an OS port scan on a device. An IP addresses is required to run an OS scan. The OS reported here is based on the results of the scan. Displays the model of rogue device, if known. This is determined with a fingerprint scan, and this information may not always be available. Displays the IP address of the rogue device. The IP address data comes from fingerprint scans or ARP polling of routers and switches. Displays the most recent AP to discover the rogue device. The device name in this column is taken from the device name in OV3600. Click the linked device name to be redirected to the APs/Devices > Monitor page for that AP. Displays the switch or router where the device s LAN MAC address was last seen. Indicates the physical port of the switch or router where the rogue was last seen. Indicates any notes about the rogue device that may have been added. Indicates the date and time the rogue device was last seen. 180 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

181 Overview of the RAPIDS > Detail Page Select a device Name in the RAPIDS > List page to view the Detail page (Figure 128). Figure 128 RAPIDS > Detail Page Illustration Important things to remember regarding the information in the device detail page are: Users with the role of Admin can see all rogue AP devices. Active rogue clients associated with this AP are listed in the Current Rogue Client Associations table. Selecting a linked MAC address will take you to the Clients > Client Detail page, where you can view fingerprinting and device details. Users with roles limited by folder can see a rogue AP if there is at least one discovering device that they can see. The discovery events displayed are from APs that you can see on the network. There may be additional discovery events that remain hidden to certain user roles. Each rogue device frequently has multiple discovery methods, all of which are listed. As you work through the rogue devices, use the Name and Notes fields to identify the AP and document its location. You can use the global filtering options on the RAPIDS > Setup page to filter rogue devices according to signal strength, ad-hoc status, and discovered by remote APs. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 181

182 VisualRF uses the heard signal information to calculate the physical location of the device. If the device is seen on the wire, RAPIDS reports the switch and port for easy isolation. If you find that the rogue belongs to a neighboring business, for example, you can override the classification to a neighbor and acknowledge the device. Otherwise, it is strongly recommended that you extract the device from your building and delete the rogue device from your system. If you delete a rogue, you will be notified the next time it is discovered. Most columns in the Discovery Events list table on this page can be filtered using the funnel icon ( ). To update a rogue device: 1. Select the Identify OS for Suspected Rogues option if an IP address is available to obtain operating system information using an nmap scan. Note that if you are running wireline security software on your network, it may identify your OV3600 as a threat, which you can ignore. 2. Select the Ignore button if the rogue device is to be ignored. Ignored devices will not trigger alerts if they are rediscovered or reclassified. 3. Select the Delete button if the rogue device is to be removed from OV3600 processing. Viewing Ignored Rogue Devices The RAPIDS > List page allows you to view ignored rogues devices that have been removed from the rogue count displayed by OV3600. Such devices do not trigger alerts and do not display on lists of rogue devices. To display ignored rogue devices, select View Ignored Rogues at the bottom left of the page. Once a classification that has rogue devices is chosen from the drop-down menu, a detailed table displays all known information. Using RAPIDS Workflow to Process Rogue Devices One suggested workflow for using RAPIDS is as follows: Start from the RAPIDS > List page. Sort the devices on this page based on classification type. Begin with Rogue APs, working your way through the devices listed. Select Modify Devices, then select all devices that have an IP address and select Identify OS. OV3600 performs a port scan on the device and attempts to determine the operating system (see Setting Up RAPIDS on page 171) You should investigate devices running an embedded Linux OS installation. The OS scan can help identify false positives and isolate some devices that should receive the most attention. Find the port and switch at which the device is located and shut down the port or follow wiring to the device. To manage the rogue, remove it from the network and acknowledge the rogue record. If you want to allow it on the network, classify the device as valid and update with notes that describe it. Not all rogue discovery methods will have all information required for resolution. For example, the switch/router information, port, or IP address are found only through switch or router polling. Furthermore, RSSI, signal, channel, SSID, WEP, or network type information only appear through wireless scanning. Such information can vary according to the device type that performs the scan. Score Override On RAPIDS > Score Override page you can change the OUI scores that are given to MAC addresses detected during scans of bridge forwarding tables on routers or switches. Figure 129, Figure 130, and Table 103 illustrate and describe RAPIDS Score Override. Perform these steps to create a score override. 182 Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

183 Once a new score is assigned, all devices with the specified MAC address prefix receive the new score. Note that rescoring a MAC Address Prefix poses a security risk. The block has received its score for a reason. Any devices that fall within this block receive the new score. 1. Navigate to the RAPIDS > Score Override page. This page lists all existing overrides if they have been created. Figure 129 RAPIDS > Score Override Page 2. Select Add to create a new override or select the pencil icon next to an existing override to edit that override. The Score Override add or edit page appears (Figure 130). Figure 130 Add/Edit Score Override Page Table 103 RAPIDS > Add/Edit Score Override Page Fields Field MAC Address Prefix Score Description Use this field to define the OUI prefix to be re-scored. Use this field to set the score that a device, with the specified MAC address prefix, will receive. 3. Enter in the six-digit MAC prefix for which to define a score, and select the desired score. Once the new score has been saved, all detected devices with that prefix receive the new score. 4. Select Add to create the new override, or select Save to retain changes to an existing override. The new or revised override appears on the RAPIDS > Score Override page. 5. To remove any override, select that override in the checkbox and select Delete. Using the Audit Log The Audit Log is a record of any changes made to the RAPIDS rules, setup page, and manual changes to specific rogues. This allows you to see how something is changes, when it changed, and who made the alteration. The Audit Log can be found at RAPIDS > Audit Log. For more information, see Figure 131. OmniVista 3600 Air Manager 7.4 User Guide Using RAPIDS and Rogue Classification 183

184 Figure 131 Audit Log Page Illustration Additional Resources The following OV3600 tools support RAPIDS: System Triggers and Alerts Triggers and Alerts that are associated with rogue devices follow the classification-based system described in this chapter. For additional information about triggers that support rogue device detection, see to Viewing, Delivering and Responding to Triggers and Alerts on page 188. Reports The New Rogue Devices Report displays summary and detail information about all rogues first discovered in a given time period. For more information, see Using the New Rogue Devices Report on page 244. For additional security-related features and functions, see the following topics in this guide. Configuring Group Security Settings on page 82 Configuring Cisco WLC Security Parameters and Functions on page 96 Configuring Group SSIDs and VLANs on page 84 Monitoring and Supporting OV3600 with the System Pages on page Using RAPIDS and Rogue Classification OmniVista 3600 Air Manager 7.4 User Guide

185 Chapter 8 Performing Daily Administration in OV3600 Daily WLAN administration often entails network monitoring, supporting WLAN and OV3600 users, and monitoring OV3600 system operations. This chapter contains the following administration procedures: Monitoring and Supporting OV3600 with the System Pages on page 185 Monitoring and Supporting WLAN Clients on page 198 Evaluating and Diagnosing User Status and Issues on page 204 Managing Mobile Devices with SOTI MobiControl and OV3600 on page 208 Monitoring and Supporting OV3600 with the Home Pages on page 210 Supporting OV3600 Servers with the Master Console on page 222 Upgrading OV3600 on page 224 Backing Up OV3600 on page 225 Using OV3600 Failover for Backup on page 226 Logging out of OV3600 on page 227 Monitoring and Supporting OV3600 with the System Pages The System pages provide a centralized location for system-wide OV3600 data and settings. Apart from Triggers, Alerts, and Backups pages that are described elsewhere in this chapter, the remaining pages of the System section are as follows: System > Status Displays status of all OV3600 services and links to their log pages. Refer to Using the System > Status Page on page 186. System > Syslog & Traps Displays all syslog messages and SNMP traps that AMP receives. Refer to Viewing Device Events in System > Syslog & Traps on page 187. System > Event Log This useful debugging tool keeps a list of recent OV3600 events, including APs coming up and down, services restarting, and most OV3600-related errors as well as the user that initiated the action. Refer to Using the System > Event Log Page on page 188. System > Triggers View and edit triggering conditions that cause AMP to send out alert notifications. Refer to Viewing, Delivering and Responding to Triggers and Alerts on page 188. System > Alerts View or acknowledge alerts sent out by the system and use the Triggering Agent links to drill down to the device that triggered the alert. Refer to Viewing Alerts on page 196. System > Backups View the backup files that are run nightly. Refer to Backing Up OV3600 on page 225. System > Configuration Change Jobs Manages configuration changes in OV3600. Refer to Using the System > Configuration Change Jobs Page on page 216. System > Firmware Upgrade Jobs Displays information about current and scheduled firmware upgrades. Refer to Using the System > Firmware Upgrade Jobs Page on page 217. System > Performance Displays basic OV3600 hardware information as well as resource usage over time. Refer to Using the System > Performance Page on page 218. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

186 Using the System > Status Page The System > Status page displays the status of all of OV3600 services. Services will either be OK, Disabled, or Down. If any service is Down (displayed in red) please contact Alcatel-Lucent support. The Reboot System button provides a graceful way to power cycle your OV3600 remotely when it is needed. The Restart OV3600 button will restart the OV3600 services without power cycling the server or reloading the OS. Figure 132 illustrates this page. Figure 132 System > Status Page Illustration The link diagnostics.tar.gz contains reports and logs that are helpful to Alcatel-Lucent support in troubleshooting and solving problems. Your Alcatel-Lucent support representative may ask for this file along with other logs that are linked on this page. Similarly, the VisualRFdiag.zip link contains VisualRF diagnostic information that might be requested by Alcatel-Lucent support. A summary table lists logs that appear on the System > Status page. These are used to diagnose OV3600 problems. Additional logs are available via SSH access in the /var/log and /tmp directories; Alcatel-Lucent support engineers may request these logs for help in troubleshooting problems and will 186 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

187 provide detailed instructions on how to retrieve them. Table 104 describes some of the most important logs: Table 104 A Sample of Important Status Logs Log pgsql error_log maillog radius async_logger async_logger_client config_pusher visualrf.log Description Logs database activity. Reports problems with the web server. Also linked from the internal server error page that displays on the web page; please send this log to Alcatel-Lucent support whenever reporting an internal server error. Applies in cases where ed reports or alerts do not arrive at the intended recipient's address. Displays error messages associated with RADIUS accounting. Tracks many device monitoring processes, including user-ap association. Logs device configuration checks. Logs errors in pushing configuration to devices. Details errors and messages associated with the VisualRF application. Viewing Device Events in System > Syslog & Traps Admins can use the System > Syslog & Traps page to review all syslog messages and SNMP traps that AMP receives from the trigger type Device Event. These device events are listed by time, type, source device, AP, severity, facility, category, and message. Most columns can be filtered using the funnel icon ( ), and messages can be filtered by substring using the Search field, as seen in Figure 133. You can change the historical data retention from the Device Events (Syslog, Traps) field in AMP Setup > General. Figure 133 System > Syslog & Traps Page Illustration Table 105 describes the columns and the information provided in each: Table 105 System > Syslog & Traps Columns and Descriptions Column Time Type Source Device Description The timestamp of the device event. Either Syslog or SNMP Trap. The name of the device that sent the message. Will be a link if you have visibility to the device. Can be empty if AMP could not correlate the source IP. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

188 Table 105 System > Syslog & Traps Columns and Descriptions (Continued) Column AP Client Severity Facility Category Message Description Contains a link to the APs/Devices > Monitor page for a device other than the source device that was correlated from some data contained in the message (by LAN MAC, BSSID, or IP Address). Can be blank, and will only be a link if you have visibility to the device. Displays a user's MAC address if one was found in the message. Can be blank, and will be a link if you have visibility to the user's AP. The severity level of the event: Emergency, Alert, Critical, Bug, Error, Warning, Notice, or Info Part of the syslog spec - sort of the logical source of the message. From controllers, will always be one of local0-local7 (you can configure on the controller when sending syslog messages to a particular receiver which facility you want to use in the messages). If SNMP Trap: Hardware, IDS, Client Security, AP Security, AP Status, Software, or Rogue Detection. For Syslog messages, a category is based on the process name on the controller that sent the syslog message. The categorization for traps and syslog messages only works for events from an Alcatel-Lucent switch. The raw trap message including the AP MAC Address, time sent, and other information. For syslogs, AMP does not display the numbers at the beginning of the message that indicate the severity and facility. For traps, AMP will attempt to translate them to human-readable format when possible. AMP will not receive processed SNMP traps into the Device Event framework if the AMP doesn't have MIB file to translate the trap. Use the Search field at the top of the column to filter the messages by a substring. Syslog messages also appear in the APs/Devices > Monitor page for controllers and in Clients > Client Detail pages under the Association History section. Using the System > Event Log Page The System > Event Log page is a very useful debugging tool containing a list of recent OV3600 events including APs coming up and down, services restarting, and most OV3600-related errors as well as the user that initiated the action. Figure 134 illustrates this page, and Table 106 describes the page components. Figure 134 System > Event Log Page Illustration Table 106 Event Log Fields Column Time User Type Event Description Date and time of the event. The OV3600 user that triggered the event. When OV3600 itself is responsible, System is displayed. Displays the Type of event recorded, which is one of four types, as follows: Device An event localized to one specific device. Group A group-wide event. System A system-wide event. Alert If a trigger is configured to report to the log, an Alert type event will be logged here. The event OV3600 observed; useful for debugging, user tracking, and change tracking. Viewing, Delivering and Responding to Triggers and Alerts This section describes triggers and alerts and contain the following topics: Viewing Triggers Creating New Triggers 188 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

189 Delivering Triggered Alerts Viewing Alerts Responding to Alerts OV3600 monitors key aspects of wireless LAN performance. When certain parameters or conditions arise that are outside normal bounds, OV3600 generates (or triggers) alerts that enable you to address problems, frequently before users have a chance to report them. Viewing Triggers To view defined system triggers, navigate to the System > Triggers page. Figure 135 illustrates this page. Figure 135 System > Triggers Page Illustration (partial view) Creating New Triggers Perform the following steps to create and configure one or more new triggers. These steps define settings that are required for any type of trigger. 1. To create a new trigger, select the Add New Trigger button from the System > Triggers page. The page that appears is illustrated in Figure 136. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

190 Figure 136 Add New Trigger Page Illustration 2. Configure the Trigger Restrictions and Alert Notifications. This configuration is consistent regardless of the trigger type to be defined. a. The Trigger Restrictions settings establishes how widely or how narrowly the trigger applies. Define the folder, subfolder, and Group covered by this trigger. Table 107 describes the options for trigger restrictions. Table 107 System > Trigger Details Fields and Default Values Notification Option Folder Include Subfolders Group Description Sets the trigger to apply only to APs/Devices in the specified folder or subfolders depending on the Include Subfolders option. NOTE: If the trigger is restricted by folder and group, it only applies to the intersection of the two it only applies to APs in the group and in the folder. Sets the trigger to apply to all devices in the specified folder and all of the devices in folders under the specified folder. Sets the trigger to apply only to APs/Devices in the specified group. NOTE: If the trigger is restricted by folder and group, it only applies to the intersection of the two it only applies to APs in the group and in the folder. b. In addition to appearing on the System > Alerts page, the Alert Notifications settings can be configured to distribute to or to a network management system (NMS), or to both. If you select , you are prompted to set the sender and recipient addresses. If you select NMS, you are prompted to choose one or more of the pre-defined trap destinations, which are configured on the OV3600 Setup > NMS page. 190 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

191 Define the Logged Alert Visibility, in which you can choose how this trigger is distributed. The trigger can distribute according to how is it generated (triggering agent), or by the role with which it is associated. The Suppress Until Acknowledged setting defines whether the trigger requires manual and administrative acknowledgement to gain visibility. If No, a new alert will be created every time the trigger criteria are met. If Yes, an alert will only be received the first time the criteria is met. A new alert for the device is not created until the initial one is acknowledged. 3. In the Trigger section, choose the desired trigger Type and Severity. Figure 137 illustrates some of the supported trigger types. Severity levels are indicated in the alerts. The alert summary information at the top of the OV3600 screen can be configured to separately display severe alerts. Refer to Configuring Your Own User Information with the Home > User Info Page on page 214 for more details. Figure 137 System > Triggers > Add Trigger Type Drop-down Menu Once you have selected a trigger type, the Add Trigger page changes. In many cases, you must configure at least one Condition setting. Conditions, settings, and default values vary according to trigger type. Triggers with conditions can be configured to fire if any criteria match as well as if all criteria match. Some trigger types share common settings, such as Duration (which can be expressed in hours, minutes, seconds, or a combination of these) and Severity (from Normal to Critical). After you select Save, the trigger appears on your next viewing of the System > Triggers page with all other active triggers. You can edit or delete any trigger as desired from the System > Triggers page. To edit an existing trigger, select the pencil icon next to the respective trigger and edit settings in the Trigger Detail page described in Table 108. To delete a trigger, check the box next to the trigger to remove, and select Delete. Repeat this procedure for as many triggers and conditions as desired. Complete the creation of your trigger type using one of the following procedures for each trigger: Setting Triggers for Devices on page 192 Setting Triggers for Interfaces and Radios on page 193 Setting Triggers for Discovery on page 193 Setting Triggers for Clients on page 194 Setting Triggers for RADIUS Authentication Issues on page 195 Setting Triggers for IDS Events on page 195 Setting Triggers for OV3600 Health on page 196 OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

192 Setting Triggers for Devices Perform the following steps to configure device-related triggers. a. Choose a device type from the Devices listed in the Type drop-down menu. See Figure 137. Table 108 itemizes and describes device trigger options and condition settings. Table 108 Device Trigger Types Option Description Device Down Device Up Configuration Mismatch Device Client Count AP Usage Device Resources Device Event Device Uplink Status This is the default type whenever configuring a new trigger. This type of trigger activates when an authorized, monitored AP has failed to respond to SNMP queries from OV3600. To set the conditions for this trigger type, select Add in the Conditions section. Complete the conditions with the Option, Condition, and Value drop-down menus. The conditions establish the device type. Multiple conditions can apply to this type of trigger. The Device Down trigger can be configured to send alerts for thin APs when the controller is down; this behavior is turned off by default. Triggers with the Minutes Down condition enabled will compare the amount of time an AP has been down to the value (in minutes) set for the condition. When the Limit by number of down events is enabled, you can set the number of down events that activate the trigger, as well as the duration of the time window to be measured. AMP will then count the number of times that the device has gone from Up to Down in the specified span of time and display this in the Device Down alert. This trigger type activates when an authorized, previously down AP is now responding to SNMP queries. To set the conditions for this trigger type, select Add in the Conditions section. This trigger type activates when the actual configuration on the AP does not match the defined Group configuration policy. To set the conditions for this trigger type, select Add in the Conditions section. Activates when a device reaches a user-count threshold for more than a specified period (such as more than 10 users associated for more than 60 seconds). Activates when the total bandwidth through the device has exceeded a predefined threshold for more than a specified period (such as more than 1500kbps for more than 120 seconds). You can also select bandwidth direction and page/radio. Selecting this type displays the following new fields in the Type section. Define these settings. Alert if Device Bandwidth >= (kbps) This threshold establishes a device-specific bandwidth policy, not a bandwidth policy on the network as a whole. Bandwidth Direction Choose In, Out, or Combined. This bandwidth is monitored on the device itself, not on the network as a whole. This type of trigger indicates that the CPU or memory utilization for a device (including router or switch) has exceeded a defined percentage for a specified period of time. This trigger is used for alerting based on SNMP traps and syslog messages, which are displayed in System > Syslogs & Traps, APs/Devices > Monitor for affected devices, and in Clients > Client Detail. The conditions supported are: Event Contents (case insensitive substring matches on message content) Event Type (syslog or trap) Syslog Severity: Emergency, Alert, Critical, Bug, Error, Warning, Notice, or Info Syslog Category SNMP Trap Category: Hardware, IDS, Client Security, AP Security, AP Status, Software, or Rogue Detection NOTE: During the process of upgrading or installation for non-master Console/Failover AMPs, AMP creates two default trigger definitions for Device Events: SNMP Trap Category of Hardware or Software Event Type is Syslog and Syslog Severity >= Critical This trigger deploys whenever a RAP s active uplink changes from Ethernet to USB or vice versa. The corresponding events are captured in a RAP s APs/Devices > Monitor page. b. Repeat this procedure for as many triggers and conditions as desired. Refer to the start of Creating New Triggers on page 189 to create a new trigger. 192 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

193 Setting Triggers for Interfaces and Radios To configure radio- and interface-related triggers, choose a trigger type from the Interfaces/Radios category, listed in the Type drop-down menu. Table 109 itemizes and describes the radio trigger types and condition settings. Table 109 Radio-Related Trigger Types Radio Trigger Options Description Radio Down Indicates that a device s radio is down on the network. Once you choose this trigger type, select Add New Trigger Condition to create at least one condition. This type requires that a radio capability be set as a condition. The Value drop-down menu supports several condition options Frame Counters Enables monitoring of traffic levels. There are multiple rate-related parameters for which you define conditions including ACK Failures, Retry Rate, and Rx Fragment Rate. See the Option drop-down menu in the Conditions section of the trigger page for a complete list of parameters. Select Add New Trigger Condition to access these settings. Define at least one condition for this trigger type QoS Counters Enables monitoring of Quality of Service (QoS) parameters on the network, according to traffic type. The rate of different parameters includes ACK Failures, Duplicated Frames and Transmitted Fragments. See the drop-down field menu in the conditions section of the trigger page for a complete list of parameters. Select Add New Trigger Condition to access these settings. Define at least one condition for this trigger type. Interface Usage Channel Utilization Interface labels defined on the trigger page will be used to set up triggers on one or more interfaces and/or radios. Available conditions are Device Type, Interface Description, Interface Label, Interface Mode, Interface Speed In (Mbps), Interface Speed Out (Mbps), Interface Type, and Radio Type. Indicates that channel utilization has crossed particular thresholds. Available conditions are Interference (%), Radio Type, Time Busy (%), Time Receiving (%), and Time Transmitting (%). Setting Triggers for Discovery Perform the following steps to configure triggers related to device discovery. a. Choose a trigger type from the Discovery category, listed in the Type drop-down menu. See Figure 137. Table 110 Discovery Trigger Types and Condition Settings Discovery Trigger Options New Device Discovered Description This trigger type flags the discovery of a new AP, router or switch connected to the network (an device that OV3600 can monitor and configure). Once you choose this trigger type, select Add New Trigger Condition to specify a Device Type (Access Point, Controller, Remote AP, or Router/Switch) b. Repeat this procedure for as many triggers and conditions as desired. Refer to the start of Creating New Triggers on page 189 to create a new trigger. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

194 Setting Triggers for Clients Perform the following steps to configure user-related triggers. a. Choose a trigger type from the Clients category, listed in the Type drop-down menu. See Figure 137. Table 111 itemizes and describes the Client-related trigger types, and condition settings for each discovery trigger type. Table 111 Client Trigger Types and Condition Settings Client Trigger Option New Client Connected Clients Client Usage New VPN User Connected VPN Users VPN Session Usage Inactive Tag IPv4 Link-Local Addresses Client Goodput Client Speed Description This trigger type indicates a new user has associated to a device within a defined set of groups or folders. A Filter on connection mode field appears to allow you to filter by Wired or Wireless clients. Note that the New Client trigger type does not require the configuration of any condition settings, so the Condition section disappears. This trigger type indicates a device (based on an input list of MAC addresses) has associated to the wireless network. It is required to define one or more MAC addresses with the field that appears. This trigger type indicates that the sustained rate of bandwidth used by an individual user has exceeded a predefined threshold for more than a specified period, in seconds (such as more than 1500kbps for more than 120 seconds). Once you choose this trigger type, select Add New Trigger Condition to specify the bandwidth characteristics that triggers an alert. You can apply multiple conditions to this type of trigger. The Value field requires that you input a numerical figure for kilobits per second (kbps). This trigger type indicates a new VPN user has associated to a device within a defined set of groups or folders. Note that the New VPN User trigger type does not require the configuration of any condition settings, so the Condition section disappears. This trigger type indicates a VPN device (based on an input list of MAC addresses) has associated to the VPN network. It is required to define one or more VPN usernames with the field that appears. This trigger type indicates that the sustained rate of bandwidth used in an individual VPN session has exceeded a predefined threshold for more than a specified period, in seconds (such as more than 1500kbps for more than 120 seconds). Once you choose this trigger type, select Add New Trigger Condition to specify the bandwidth characteristics that triggers an alert. You can apply multiple conditions to this type of trigger. The Value field requires that you input a numerical figure for kilobits per second (kbps). This trigger type flags events in which an RFID tag has not been reported back to OV3600 by a controller for more than a certain number of hours. This trigger can be used to help identify inventory that might be lost or stolen. Set the time duration for this trigger type if not already completed. When enabled, this trigger checks whether the total count of self-assigned IP addresses has crossed a set threshold for clients within a selected folder or group. The alert deployed by this trigger includes a link to search for IP addresses containing x.x. This trigger type indicates that the goodput for an individual client has exceeded a predefined threshold. Available conditions are Usage Kbps (combined), Usage Kbps (in), and Usage Kbps (out). This trigger type indicates that the speed for an individual client has exceeded a predefined threshold. The available condition for this trigger is Speed Mbps. b. Repeat this procedure for as many triggers and conditions as desired. Refer to the start of Creating New Triggers on page 189 to create a new trigger. 194 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

195 Setting Triggers for RADIUS Authentication Issues Perform the following steps to configure RADIUS-related triggers. a. Choose a trigger type from the RADIUS Authentication Issues list in the drop-down Type menu. Table 112 itemizes and describes the condition settings for each RADIUS Authentication trigger type. Table 112 RADIUS Authentication Trigger Types and Condition Settings Option Client RADIUS Authentication Issues Device RADIUS Authentication Issues Total RADIUS Authentication Issues Description This trigger type sets the threshold for the maximum number of failures before an alert is issued for a user. Select Add New Trigger Condition to specify the count characteristics that trigger an alert. The Option, Condition, and Value fields allow you to define the numeric value of user issues. This trigger type sets the threshold for the maximum number of failures before an alert is issued for a device. The Option, Condition, and Value fields allow you to define the numeric value of user issues. This trigger sets the threshold for the maximum number of failures before an alert is issued for both users and devices. b. Repeat this procedure for as many triggers and conditions as desired. Refer to the start of Creating New Triggers on page 189 to create a new trigger. Setting Triggers for IDS Events Perform the following steps to configure Intrusion Detection System (IDS)-related triggers. a. Choose the Device IDS Events trigger type from the drop-down Type menu. See Figure 137. Table 113 describes condition settings for this trigger type. Table 113 Device IDS Events Authentication Trigger Types and Condition Settings IDS Trigger Options Device IDS Events Rogue Device Classified Client on Rogue AP Description This trigger type is based on the number of IDS events has exceeded the threshold specified as Count in the Condition within the period of time specified in seconds in Duration. Alerts can also be generated for traps based on name, category or severity. Select Add New Trigger Condition to specify the count characteristics that trigger an IDS alert. This trigger type indicates that a device has been discovered with the specified Rogue Score. Ad-hoc devices can be excluded automatically from this trigger by selecting Yes. See Using RAPIDS and Rogue Classification on page 169 for more information on score definitions and discovery methods. Once you choose this trigger type, select Add New Trigger Condition to create one or more conditions. A condition for this trigger enables you to specify the nature of the rogue device in multiple ways. This trigger type indicates that a client has associated to a rogue AP. Available conditions include rogue classification, and whether the client is valid. b. Repeat this procedure for as many triggers and conditions as desired. Refer to the start of Creating New Triggers on page 189 to create a new trigger. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

196 Setting Triggers for OV3600 Health After completing steps 1-3 in Creating New Triggers on page 189, perform the following steps to configure IDS-related triggers. a. Choose the Disk Usage trigger type from the drop-down Type menu. See Figure 137 for trigger types. Table 114 describes the condition settings for this trigger type. Table 114 Disk Usage Trigger and Condition Settings OV3600 Health Trigger Disk Usage Description This trigger type is based on the disk usage of OV3600. This type of trigger indicates that disk usage for the OV3600 server has met or surpassed a defined threshold. Select Add New Trigger Condition to specify the disk usage characteristics that trigger an alert. Set one of these triggers at 90% so you receive a warning before OV3600 suffers performance degradation due to lack of disk space. b. Repeat this procedure for as many triggers and conditions as desired. Refer to the start of Creating New Triggers on page 189 to create a new trigger. Delivering Triggered Alerts OV3600 uses Postfix to deliver alerts and reports via because it provides a high level of security and queues locally until delivery. If OV3600 is located behind a firewall, preventing it from sending directly to a specified recipient, use the following procedures to forward to a smarthost. 1. Add the following line to /etc/postfix/main.cf: relayhost = [mail.example.com] where mail.example.com is the IP address or hostname of your smarthost 2. Run service postfix restart. 3. Send a test message to an address: Mail -v user@example.com Subject: test mail. CC: 4. Press Enter. 5. Check the mail log to ensure mail was sent: tail -f /var/log/maillog Viewing Alerts Apart from visiting System > Alerts, OV3600 displays alerts and provides alert details in two additional ways: 1. The Alert Summary table is available on the following OV3600 pages, and is illustrated in Figure 138: APs/Devices > List Groups > Monitor Home > Overview Clients > Connected or Client Detail 196 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

197 Figure 138 Alert Summary Table Illustration This table displays alerts as follows; select the alert Type to display alert details: OV3600 Alerts Displays details for all device alerts. IDS Events Displays details of all Intrusion Detection System (IDS) events and attacks under the RAPIDS tab. You must be enabled as a RAPIDS user to see this page. RADIUS Authentication Issues Displays RADIUS-related alerts for devices in the top viewable folder available to the OV3600 user. The detailed list displays the MAC address, username, AP, radio, controller, RADIUS server, and time of each event. Alerts can be sorted by any column. 2. The Alerts and Severe Alerts top header stats in the Status bar at the top of all OV3600 pages, illustrated in Figure 139. The Severe Alert Threshold can be configured on the Home > User Info page.refer to Setting Severe Alert Warning Behavior on page 36. Figure 139 Alerts in the OV3600 Status Bar (highlighted) Select the Alerts or the Severe Alerts counter or navigate to the System > Alerts page. Figure 140 illustrates this page. Figure 140 System > Alerts Page Illustration For each new alert, the System > Alerts page displays the items listed in Table 115. Table 115 System > Alerts Fields and Default Settings Field Trigger Type Trigger Summary Triggering Agent Time Severity Description Displays and sorts triggers by the type of trigger. Provides an additional summary information related to the trigger. Lists the name of the AP that generated the trigger. Select the name to display its APs/ Devices > Manage page. Displays the date and time the trigger was generated. Displays the severity code associated with that trigger. Responding to Alerts Once you have viewed an alert, you may take one of the following courses of action: Leave it in active status if it is unresolved. The alert remains on the New Alerts list until you acknowledge or delete it. If an alert already exists, the trigger for that AP or user does not create another alert until the existing alert has been acknowledged or deleted. Move the alert to the Alert Log by selecting it and selecting Acknowledge. You may see all logged alerts by selecting the View logged alerts link at the top of the System > Alerts page. Select the New Alerts link to return to the list of new alerts. Delete the alert by selecting it from the list and selecting Delete. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

198 Monitoring and Supporting WLAN Clients The OV3600 Users pages support WLAN users in OV3600. This section describes the Clients pages as follows: Overview of the Clients Pages Monitoring WLAN Users in the Clients > Connected and Clients > All Pages Supporting Guest WLAN Users With the Clients > Guest Users Page Supporting RFID Tags With the Clients > Tags Page See also Evaluating and Diagnosing User Status and Issues. For information about creating OV3600 users and OV3600 user roles, refer to: Creating OV3600 Users Creating OV3600 User Roles If you need to create an OV3600 user account for frontline personnel who are to support Guest WLAN users, refer to Supporting Guest WLAN Users With the Clients > Guest Users Page on page 201. Overview of the Clients Pages The Clients pages display multiple types of user data for existing WLAN clients and VPN users. The data comes from a number of locations, including data tables on the access points, information from RADIUS accounting servers, and OV3600-generated data. OV3600 supports the following Clients pages: Clients > Connected Displays active users that are currently connected to the WLAN. Refer to Monitoring WLAN Users in the Clients > Connected and Clients > All Pages on page 198. Clients > All Displays all users of which OV3600 is aware, with related information. Non-active users are listed in gray text. For a description of the information supported on this page, refer to Monitoring WLAN Users in the Clients > Connected and Clients > All Pages on page 198. Clients > Guest Users Displays all guest users in OV3600 and allows you to create, edit, or delete guest users. See Supporting Guest WLAN Users With the Clients > Guest Users Page on page 201. Clients > Client Detail Displays client device information, alerts, signal quality, bandwidth, and association history. This page appears when you select a user s MAC address link from these list tables: Clients > Connected Clients > All Home > Search page results that display the user MAC address See Evaluating User Status with the Clients > Client Detail Page on page 205. Clients > Diagnostics Displays possible client device issues, diagnostic summary data, user counts, AP information, counters summary, and additional information. This page appears when you select a user s MAC address from one of the following pages: Clients > Connected Clients > All Home > Search page results or Search field results that display the user MAC address See Evaluating Client Status with the Clients > Diagnostics Page on page 208. Clients > Tags Displays a list of wireless tags, such as Aeroscout, PanGo and Newbury, that are heard by thin APs, and reported back to a controller that is monitored by OV3600. Supporting RFID Tags With the Clients > Tags Page on page 204. Monitoring WLAN Users in the Clients > Connected and Clients > All Pages The Clients > Connected page displays all users currently connected in OV3600, and is illustrated in Figure 141 and described in Table 116. This page contains the following information at a glance: 198 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

199 The Folder field shows the current folder of Connected Clients you are viewing. You can view users under a particular folder from the Go to folder dropdown menu. Links under the Folder fields showing the Total Devices, Mismatched, Clients, and Bandwidth (a static, unlinked statistic) summarize the device information for this folder. Select these links to be taken to detail pages for each: Total Devices redirects to the APs/Devices > List for that folder, Mismatched redirects to the list in APs/Devices > Mismatched for that folder, and selecting Clients refreshes the page but expands to include users in the subfolders. Interactive graphs display average and max Clients over time, and Usage in and out for the selected folder over time. Below the Clients and Usage graphs is the list of connected users The information on this page can be adjusted in the following ways: Drag the slider to pick the time range on the interactive graphs, and select Show All to select other options to display. The Alert Summary section displays custom configured alerts that were defined in the System > Alerts page. Use the Filter icon ( ) next to certain columns (AP/Device, Role, VLAN, Connection Mode, and others) to filter the results by one of the values under that column.you can filter the list by substring match under the Username column. The Clients > Connected page includes SSID information for users, and can display wired users using remote Access Point (RAP) devices in tunnel and split-tunnel mode. Figure 141 Clients > Connected Page Illustration (Partial View) Table 116 Clients > Connected Table Columns and Links (Alphabetical) Field AOS Device Type AP/Device Description The type of client device determined by the Alcatel-Lucent controller -- a fallback in case the rules set in AMP Setup > Device Type Setup were unable to determine the device type. Displays the name of the AP to which the MAC address is associated as a link to this AP's APs/ Devices > Monitor page. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

200 Table 116 Clients > Connected Table Columns and Links (Continued)(Alphabetical) Field Association Time Auth. Time Auth. Type Usage Ch BW Cipher Connection Mode Device Type Duration EAP Supplicant Forward Mode Goodput Group Guest User Interface LAN Hostname LAN IP Address Location MAC Address Manufacturer Model Name Network Chipset Network Driver Notes OS OS Detail Description The first time OV3600 recorded the user for this association. The how long ago the user authenticated. NOTE: This value displays as a negative number for unauthenticated users. The type of authentication employed by the user: WPA2 (EAP-PEAP) is the standard setting. EAP is reported by Alcatel-Lucent devices via SNMP traps. RADIUS accounting servers integrated with OV3600 will provide the RADIUS Accounting Auth type. Web (PAP) - Captive Portal. All others are considered to be not authenticated. The average bandwidth consumed by the MAC address. The channel bandwidth that currently supports n users. Displays WEP with keys. This data is also displayed in the Client Session report in the Session Data By Client section. The Radio mode used by the user to associate to the AP for n clients. The type of device determined by AMP Setup > Device Type Setup rules. The length of time the MAC address has been associated. The party being authenticated in the Extensible Authentication Protocol. Forwarding mode for the port: Bridge, Tunnel, or Split Tunnel. The ratio of the total bytes transmitted or received in the network to the total air time required for transmitting or receiving the bytes. The group containing the AP that the user is associated with. Specifies whether the user is a guest. The interface on the device to which the user is connected. The LAN hostname of the user MAC. The IP assigned to the user MAC. OV3600 gathers it from the association table of APs. If a value appears here, the location of this user s client has been mapped on VisualRF. Select the location to open a new VisualRF Floor Plan Location window. The radio MAC address of the user associated to APs as a link to the Users > Detail page for this user. The manufacturer of the user s device. The model of the user s device. The product of the user s device. The chipset indicates the functions the device was designed to perform. Driver name or other information. Free notes about the user. The device s operating system type. Additional information on the operating system such as version numbers. 200 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

201 Table 116 Clients > Connected Table Columns and Links (Continued)(Alphabetical) Field Phone Number Role Serial Number Service End Service Start Sig. Qual. SSID Speed Tunneled Controller Username VLAN Description Contact number for the user. Specifies the role that an Alcatel-Lucent controller assigned to the connected user, such as employee. Serial number of the device. Ending timestamp of the device usage. Beginning timestamp of the device usage. The average signal quality the user experienced. The SSID with which the user is associated. The packet and byte counts of data frames successfully transmitted to and received from associated stations. If a user is connected to an Alcatel-Lucent Mobility Switch, indicates which controller the user is authenticated to. Displays the name of the user associated to the AP. OV3600 gathers this data from device traps, SNMP polling, or RADIUS accounting. Usernames appear in italics when a username for that MAC address has been stored in the database from a previous association, but OV3600 is not getting a username for the current association. This may indicate that the user has not yet been authenticated for this session or OV3600 may not be getting a username from an external source. Displays the VLAN assigned to the user, if available. Supporting Guest WLAN Users With the Clients > Guest Users Page OV3600 supports guest user provisioning for Dell PowerConnect W, Alcatel-Lucent, Inc., Alcatel-Lucent and Cisco WLC devices. This allows frontline staff such as receptionists or help desk technicians to grant wireless access to WLAN visitors or other temporary personnel. Perform the following steps in the pages described to configure these settings. 1. Navigate to the OV3600 Setup > Roles page and select the Read-Only Monitoring & Auditing role type. Under Guest User Preferences, enable Allow creation of Guest Users. 2. Next, navigate to the OV3600 Setup > Users page and create a new user with the role that was just created. Figure 142 illustrates this page. Figure 142 OV3600 Setup > Users Page Illustration 3. The newly created login information should be provided to the person or people who will be responsible for creating guest access users. 4. The next step in creating a guest access user is to navigate to the Users > Guest Clients tab. From this tab, you can add new guest users, you can edit existing users, and you can repair guest user errors. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

202 This page displays a list of guest users and data, to include the expiration date, the SSID (for Cisco WLC) and other information. Figure 143 illustrates this page and Table 117 describes the information. Figure 143 Clients > Guest Users Page Illustration Table 117 Clients > Guest Users Fields Field Repair Guest User Errors Add New Guest User Username Enabled Company Name Sponsor Name Expiration WLAN Profile Status Description Sets OV3600 to attempt to push the guest user again in an attempt to repair any errors in the Status column. Adds a new guest user to a controller via OV3600. Randomly generates a user name for privacy protection. This name appears on the Guest User detail page. Enables or disables the user status. Set the status of the guest user as active (enabled) or expired (disabled). Displays the optional address of the user. Displays the optional company name for the user. Displays the name of the sponsor for the guest user. This setting is optional. Displays the date the guest user's access is to expire. Sets the SSID that the guest user can access. This setting applies to Cisco WLC only. Reports current status by the controller. If error messages appear in this column, select the user with the checkbox at left, and select the Repair guest user errors button. Guest users associated to the wireless network appear on the same list as other wireless users, but are identified as guest users in the Guest User column. The Client Detail page for a guest user also contains a box with the same guest information that appears for each user on the Clients > Guest Users list. The Enabled, Sponsor Name, WLAN Profile, and Status columns can be filtered using the funnel icon ( ). 5. To add a new guest user, select Add, and complete the fields illustrated in Figure 144. Table 117 above describes most fields. The first three fields are required, and the remaining fields are optional. 202 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

203 Figure 144 Clients > Guest Users > Add New Guest User Page Illustration To make the Username or Password anonymous and to increase security, complete these fields then select Generate. The anonymous and secure Username and Password appear in the respective fields. 6. Select Add to complete the new guest user, or select Cancel to back out of new user creation. The Clients > Guest Users page appears and displays results, as applicable. Supporting VPN Users with the Clients > VPN Sessions Page The Clients > VPN Sessions page shows active VPN Sessions along with device type and HTTP fingerprinting information. Figure 145 Clients > VPN Sessions Page Illustration When a VPN username is selected, a Clients > VPN User Detail displays with current VPN sessions, a user and bandwidth interactive graph, and a historical VPN sessions list table. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

204 Supporting RFID Tags With the Clients > Tags Page Radio Frequency Identification (RFID) supports identifying and tracking wireless devices with radio waves. RFID uses radio wave tags for these and additional functions. Active tags have a battery and transmit signals autonomously, and passive tags have no battery. RFID tags often support additional and proprietary improvements to network integration, battery life, and other functions. The Clients > Tags page displays a list of wireless tags, such as Aeroscout, PanGo and Newbury, that are heard by thin APs, and reported back to a controller that OV3600 monitors. OV3600 displays the information it receives from the controller in a table on this page. Figure 146 illustrates this page, and Table 118 describes fields and information displayed. The Vendor, Battery Level, and Chirp Interval columns can be filtered using the funnel icon ( ). Figure 146 Clients > Tags Page Illustration Table 118 Clients > Tags Fields Field Name MAC Address Vendor Battery Level Chirp Interval Last Seen Closest AP Description Displays the user-editable name associated with the tag. Displays the MAC address of the AP that reported the tag. Displays the vendor of the tag (Aeroscout, PanGo and Newbury) display all or filter by type. Displays battery information filterable in drop-down menu at the top of the column; is not displayed for Aeroscout tags. Displays the tag chirp frequency or interval, filterable from the drop-down menu at the top of the column. Note that the chirp interval from the RFID tag influences the battery life of active tags as well as search times. If a tag chirps with very long chirp interval, it may take longer time for the location engine to accurately measure x and y coordinates. Date and time the tag was last reported to OV3600. The AP that last reported the tag to the controller (linked to the AP monitoring page in OV3600). To edit the name of the tag, or to add notes to the tag's record, select the pencil icon next to the entry in the list. You can then add or change the name and add notes like maternity ward inventory or Chicago warehouse, as two examples. The Inactive Tag trigger can be used to generate an alert if a tag is not reported to OV3600 after a certain interval. This can help to identify lost or stolen inventory. For more information about enabling this trigger, refer to the section Monitoring and Supporting OV3600 with the System Pages on page 185. Evaluating and Diagnosing User Status and Issues If a WLAN user reports difficulty with the wireless network, the administration or Helpdesk personnel can view and process related user information from the Client Detail and Diagnostic pages. This section describes these two pages as follows: Evaluating User Status with the Clients > Client Detail Page Evaluating Client Status with the Clients > Diagnostics Page 204 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

205 Evaluating User Status with the Clients > Client Detail Page The Clients > Client Detail page is a focused subtab that becomes visible when you select a specific WLAN user. Access the Clients > Client Detail page by selecting the MAC Address link for a specific user from one of the following pages: Clients > Connected Clients > All Home > Search page results or Search field Client results that display the user MAC address This page provides information for the wireless device, signal quality, and bandwidth consumption. This page also provides an AP association history and current association status. Finally, if VisualRF is enabled in AMP Setup > General, this page provides a graphical map of the user location and facility information. Figure 147 illustrates the contents of Clients > Client Details page. Figure 147 Clients > Client Detail Page Illustration (partial view) Mobile Device Access Control in Clients > Client Detail and Clients > Connected Mobile Device Access Control (MDAC) secures, provisions and manages network access for Apple ios and other employee-owned mobile devices by enabling device fingerprinting, device registration, and increased device visibility. Use the checkbox next to these fields to enable them in Clients > Client Detail: Device Type OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

206 OS OS Detail Manufacturer To see more options, select the Show additional properties link. The results are illustrated in Figure 148: Figure 148 Device Info section in Clients > Client Detail after Show additional properties is selected Classifying Alcatel-Lucent Devices in Client Detail If you have deployed Alcatel-Lucent switches and have WMS Offload enabled on the network, the Clients > Client Detail page allows you to classify the device in the Device Information section, and to push this configuration to the Alcatel-Lucent switches that govern the devices. The classifications are as follows: Unclassified Devices are unclassified by default. Valid If the Protect Valid Stations option is enabled, this setting designates the device as a legitimate network device. Once this Valid setting is pushed, this setting prevents valid stations from connecting to a non-valid AP. Contained When this status is pushed to the device, Alcatel-Lucent switches will attempt to keep it contained from the network. You can classify the user regardless of whether WMS Offload is enabled. If WMS Offload is enabled, the classification will get pushed up to the switch. 206 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

207 Quick Links for Clients on Alcatel-Lucent Devices In Clients > Client Detail, the following two drop-down menus appear next to the Save button in the Device Info section: Open controller web UI: A drop-down menu that allows you to jump to the controller s UI in a new window. Thin APs link to Controller > Access Points when not operating in mesh mode, or Controller > Mesh Nodes otherwise. Controllers show several more pages in this menu (Security Dashboard, for instance) if the controller is running AOS-W version 6.1 or greater. Run a command: A drop-down menu with a list of CLI commands you can run directly from the APs/ Devices > Monitor page. Figure 149 Open controller web UI and Run a command Menus Using the Deauthenticate Client Feature Some displays of the Clients > Client Detail page include the Deauthenticate Client feature in the Current Association section. Specifically, those displays are for devices which support this operation, namely Alcatel-Lucent and Cisco WLC with firmware version v or later. Select Deauthenticate Client to use this feature, as shown in Figure 150: Figure 150 Deauthenticate Client button in Current Association section of Clients > Client Detail Viewing a Client s Association History Past association details of a client are tracked in the Association History table, which is located under the VRF QuickView illustration (if available) and the Alert Summary in Clients > Client Detail. The columns in this table, shown in Figure 151, are the same as the fields in the Current Association section for this user. Figure 151 Association History in Clients > Client Detail Viewing the Rogue Association History for a Client Past association details of a rogue client are tracked in the Rogue Association History table, which is located under the Association History table in Clients > Client Detail. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

208 Figure 152 Rogue Association History table in Clients > Client Detail Evaluating Client Status with the Clients > Diagnostics Page The Clients > Diagnostics page is accessible from the Clients > Client Detail page. You can also search for a user and select the associated MAC address from the search results. This page provides an overview of a WLAN user s general status and connectivity on the network, as illustrated in Figure 153. Figure 153 Clients > Diagnostics Page Illustration Each section of the Clients > Diagnostics page displays information by which to evaluate possible user issues. Managing Mobile Devices with SOTI MobiControl and OV3600 Overview of SOTI MobiControl SOTI MobiControl, the mobile device management platform for Windows Mobile, Apple, and Android devices, has been integrated into OV3600 to provide direct access to the MobiControl Web Console. MobiControl runs on your Mobile Device Manager (MDM) server. This server provisions mobile devices to configure connectivity settings, enforce security policies, restore lost data, and other administrative services. Information gathered from mobile devices can include policy breaches, data consumption, and existing configuration settings. Prerequisites for Using MobiControl with OV3600 In order to use the MobiControl integration in OV3600, the following is required: An OV3600 running version or later An MDM server with SOTI MobiControl Console 8.0x 208 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

209 A client device that is: associated with WLAN infrastructure managed by the OV3600 server running or later being actively managed by the SOTI MobiControl server For more information about setting up MobiControl, please see In order to use SOTI MobiControl from within OV3600, you must first add your MDM server and designate it as a MobiControl. Adding a Mobile Device Management Server for MobiControl 1. To add an MDM server to OV3600, navigate to OV3600 Setup > MDM Server and select Add. Complete the fields on this page. Table 119 describes the settings and default values: Table 119 OV3600 Setup > MDM Server > Add Fields and Descriptions Field Hostname/IP Address Protocol URL Context Enabled Username/ Password Polling Period Description The address or DNS hostname configured for your MobiControl Web Console. Whether HTTP or HTTPS is to be used when polling the MDM server. The port on which to connect to the MDM server is inferred from the protocol: with HTTP, OV3600 will connect to port 80 of the SOTI server; with HTTPS, OV3600 will connect to port 443. The URL context appended to the server URL to build the URL when connecting with the SOTI server. For MobiControl v8.0x the default URL Context is "MobiControlWeb". For MobiControl v8.5x the default URL Context is MobiControl. Whether this server can be polled by OV3600. Make sure it is set to Yes. The login credentials for accessing the web console of the MobiControl system. The frequency in which OV3600 polls the MDM server. The default is 5 minutes. 2. When finished, select Add. The list page for the MDM server also displays: Last Contacted The last time OV3600 was able to contact the MDM server. Errors Issues, if any, encountered during the last contact. During each polling period, OV3600 will obtain a list of all device IDs and their WLAN MAC addresses. The information about device OS, device OS Detail, Manufacturer, Model, Name are retrieved from MobiControl and populated to the Clients > Client Detail page for supported mobile devices. A View device in SOTI MobiControl link provides direct access to the MobiControl Web Console for additional details about the device. MobiControl information overrides data obtained from AOS-W 6.0 switches. Accessing MobiControl from the Clients > Client Detail Page In order to access the MobiControl web console for a SOTI-managed mobile device from within OV3600, follow these steps: 1. Navigate to a page that lists clients. This can include: Clients > Connected or Clients > All Search results that display user MAC address 2. Select the MAC address in the Clients list table. The Clients > Client Detail page displays. 3. Under the Classification field, select the View device in SOTI MobiControl link. A new window will display the MobiControl Web Console for this device. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

210 Monitoring and Supporting OV3600 with the Home Pages The Home tab of OV3600 provides the most frequent starting point for monitoring network status and establishing primary OV3600 functions once OV3600 configuration is complete. From the Home tab, you can access the following pages: The Home > Overview page condenses a large amount of information about your OV3600. You can view the health and usage of your network and use shortcuts to view system information. Refer to Monitoring OV3600 with the Home > Overview Page on page 210 below. The Home > Search page provides a simple way to find users. managed devices, groups, and rogues. Refer to Searching OV3600 with the Home > Search Page on page 213. The Home > Documentation page contains all relevant OV3600 documentation. See Accessing OV3600 Documentation on page 214. The Home > License page provides product licensing information. See Viewing and Updating License Information on page 212. The Home > User Info page is where logged-in users can configure their name, contact information, rogue count filter level, customized header columns, severe alert threshold, personalized search preferences, record display preferences, and the refresh rate of the console. See Configuring Your Own User Information with the Home > User Info Page on page 214. Monitoring OV3600 with the Home > Overview Page To view your overall network health, navigate to Home > Overview page. Figure 154 illustrates this page, and Table 120 describes the contents. The information that displays varies depending on your role. Figure 154 Home > Overview Page Illustration 210 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

211 Table 120 Home > Overview Sections and Charts Section Clients Usage Monitoring Status Configuration Compliance Alert Summary Quick Links Description This chart is a graphical summary of the number of users on the network during a period of time. The time can be adjusted. Select Show All to display a list of data series that this graph can display, such as the user count by SSID. Clear the Max Clients or Avg Clients checkbox to change the display of the graph. The graph displays the maximum number of users by default. To view historical graphs in a new window, select the three-bar icon on the upper right of the chart. This adjustable chart displays bandwidth data over time. To remove bandwidth in or out from the graphical display, clear the check box for Avg Bits Per Second In or Out. To display details for specific devices, select Show All and select the devices to be included in the graphical bandwidth summary chart. To view historical graphs in a new window, select the three-bar icon on the upper right of the chart. This pie chart shows the percentage of all devices that are up and down on the network. To review devices that are down, select Down in the legend or the chart, and the APs/Devices > Down page displays. The pie chart displays all known device configuration status on the network. Devices are classified as Good, Unknown, Mismatched, or Audit Disabled. Select the Mismatched link to see the APs/Devices > Mismatched page. This section displays all known and current alerts configured and enabled in the System > Alerts page (refer to Viewing, Delivering and Responding to Triggers and Alerts on page 188). Alerts can be sorted using the column headers (Type, Last 2 Hours, Last Day, Total, or Last Event). The Alert Summary field displays three types of alerts: OV3600 Alerts IDS Events RADIUS Authentication Issues Select any alert type for more information. The Quick Links section provides drop-down menus that enable you to move to the most common and frequently used pages in OV3600, as follows: Go to folder This menu lists all folders defined in OV3600 from the APs/Devices List page. See Using Device Folders (Optional) on page 134. Go to group This menu lists all groups defined in OV3600, and enables you to display information for any or all of them. Use the Groups pages to edit, add, or delete groups that appear in this section. See Configuring and Using Device Groups on page 71. View Latest Reports OV3600 supports creating custom reports or viewing the latest daily version of any report. Select any report type to display the daily version. See Creating, Running, and ing Reports on page 229. Common Tasks This menu lists quick links to the most heavily used task-oriented pages in OV3600, to include the following: Configure Alert Thresholds This link takes you to the System > Triggers page. See System > Performance Displays basic OV3600 hardware information as well as resource usage over time. Refer to Using the System > Performance Page on page 218. on page 185. Configure Default Credentials This link takes you to the Device Setup > Communication page. See Configuring Communication Settings for Discovered Devices on page 54. Discover New Devices on Your Network This link takes you to the Device Setup > Discover page. See Discovering, Adding, and Managing Devices on page 107. Supported Devices and Features This link displays a PDF that summarizes all supported devices and features in chart format for OV3600. Upload Device Firmware This link displays the Device Setup > Upload Firmware & Files & Files Upload page. See Overview of the Device Setup > Upload Firmware & Files Page on page 56. View Event Log This link displays the System > Event Log page. See Using the System > Event Log Page on page 188. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

212 The Customize link on the upper-right side of the page allows you to customize the widgets on the Home > Overview page. See Customizing the Dashboard on page 34. Viewing and Updating License Information Navigate to the Home > License page using the standard OV3600 menu. Figure 155 illustrates this page, and Table 121 describes the contents. Please be aware that you cannot enter multiple licenses. To combine multiple license entitlements into one new license, contact Alcatel-Lucent support. Figure 155 Home > License Page Illustration 212 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

213 Table 121 Home > License Static Fields and Descriptions Field System Name Organization Hostname IP Address Time Uptime Version OS Description Displays a user-definable name for OV3600. The System Name can be configured from the OV3600 Setup > General page. Displays the organization listed on your license key. Displays the DNS name assigned to OV3600. Displays the static IP address assigned to OV3600. The IP Address can be configured from the OV3600 Setup > Network page. Displays the current date and time set on OV3600. Displays the amount of time since the operating system was last booted. Displays the version number of OV3600 code currently running. Displays the version of Linux installed on the server. Searching OV3600 with the Home > Search Page While the Search field at the top of every AMP page allows you to perform a quick search across a small number of common categories, the Home > Search page conducts a deep system-wide search to find connected and historical clients, VPN users, managed devices, rogue devices, rogue clients, groups, folders, and tags. Search performs partial string searches on a large number of fields including the notes, version, secondary version, radio serial number, device serial number, LAN MAC, radio MAC and apparent IP address of all the APs, as well as the client MAC, VPN user, Client, LAN IP and VPN IP fields. Figure 156 illustrates this page. Figure 156 Home > Search Page Illustration with Sample Hits on 00: OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

214 1. Enter the keyword or text with which to search. If searching for a MAC address, enter it in colondelimited format. The OV3600 Search utility is case-insensitive when single or double quotes are not used. For exact case-sensitive matches, use quotes around the search phrase. 2. Select Search, and the results display after a short moment. Results support several hypertext links to additional pages, and the Filter icon over some columns allow for additional filtering of search returns. Search results are categorized in the following sequence. Categories of search results can be customized on the Home > User Info page to limit the scope of information returned. Not all categories below may offer returns for a given search: Devices Clients VPN Users Rogues and Rogue Clients Tags Folders and Groups Accessing OV3600 Documentation Figure 157 The Home > Documentation page provides easy access to all relevant OV3600 documentation. All of the documents on this page are hosted locally by your OV3600 server and can be viewed by any PDF viewer. Home > Documentation Page Illustration If you have any questions that are not answered by the documentation, please contact Alcatel support. Configuring Your Own User Information with the Home > User Info Page The Home > User Info page displays information about the user that is logged into OV3600. This page includes the authentication type (local user, RADIUS, or TACACS+) and access level. This page enables customization some of the information displayed in OV3600, and is the place to change your password. The logged-in users can customize the information displayed in the OV3600 header. Figure 158 illustrates the Home > User Info page, and Table 122 lists the fields. 214 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

215 Figure 158 Home > User Info Page Illustration Table 122 Home > User Info Fields and Descriptions Field Description Top Header Stats Filter Level For Rogue Count Customize Header Columns Specifies the minimum classification that will cause a device to be included in the rogue count header information. More about the classifications can be found in Switch Classification with WMS Offload on page 174. Enables/disables the ability to control which statistics hyperlinks (also known as Top Header Stats) are displayed at the top of every OV3600 screen. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

216 Table 122 Home > User Info Fields and Descriptions (Continued) Field Stats Severe Alert Threshold Include Device Types Description Select the specific data you would like to see in the Top Header Stats. Refer to Status section of the Home > Overview Page on page 22. Note: This field only appears if you selected Yes in the previous field. Configures the minimum severity of an alert to be included in the Severe Alerts count. See Setting Severe Alert Warning Behavior on page 36 for details. Note: The severe alerts count header info will only be displayed if Severe Alerts is selected in the Stats section above. Note: This field only appears if you selected Yes in the Customize Header Columns field. Configures the types of devices that should be included in the header stats. If a device type is not selected then it will not be included in the header stats. Note: This field only appears if you selected Yes in Customize Header Columns. Search Preferences Customize Search Set to No by default; when set to Yes, you can select which search categories to display when Full search results are returned. Display Preferences Default Number of Records per List Reset List Preferences Customize Columns for Other Roles Console Refresh Rate Idle Timeout (5 mins to 240 mins) Defines the number of rows to appear in any list by default. If a row count is manually set, it will override the default setting. Reset all list preferences including number of records per list, column order and hidden column information. Allows admin users to determine the columns that should be displayed and the order they should be displayed for specific user roles. To customize lists for other users, navigate to that list and select Choose Columns for roles above the list. Make the desired column changes; select the roles to update and Save. The frequency in which lists and charts automatically refresh on a page. Number of minutes of idle time until AMP automatically ends the user session. This setting only the logged-in user of this AMP. The default is 60 minutes. To set the max idle timeout for all users of this AMP, see Setting Up Login Configuration Options on page 50. Perform the following steps to configure your own user account with the Home > User Info page: 1. In the User Information section, enter the following information: Name Enter the ID by which you log into and operate in OV Address Enter the address to be used for alerts, triggers, and additional OV3600 functions that support an address. Phone Enter the area code and phone number, if desired. Notes Enter any additional text-based information that helps other OV3600 users or administrators to understand the functions, roles, or other rights of the user being created. Using the System > Configuration Change Jobs Page Schedule configuration change jobs are summarized on the System > Configuration Change Jobs page. Perform the following steps to use this page, illustrated in Figure Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

217 Figure 159 System > Configuration Change Jobs Page Illustration 1. To edit an existing configuration change job select on the linked description name. On the subsequent edit page you can choose to run the job immediately by selecting Apply Changes Now, reschedule the job by selecting Schedule, Delete the job, or Cancel the job edit. 2. Select the linked AP or group name under the Subject column to go to its monitoring page. 3. Select the linked group and folder names under Folder or Group to go to the AP's folder or group page. 4. Scheduled configuration change jobs will also appear on the Manage page for an AP or the Monitoring page for a group. Using the System > Firmware Upgrade Jobs Page The System > Firmware Upgrade Jobs page displays a list of recent firmware upgrade jobs that have been initiated in the APs/Devices > Manage page or Modify Devices page for a controller or autonomous AP that supports firmware upgrades in AMP. Successful upgrade jobs are not archived on this page -- generally you visit this page to review failed or pending firmware upgrade jobs. Users with the AP/Device Manager role and higher can view this page. Audit-only users cannot view this page or tab. Figure 160 System > Firmware Upgrade Jobs Page Illustration You can perform the following operations on this page: To restart failed firmware upgrade jobs, select the checkboxes next to the rows you want to restart and select the Restart Failed Jobs button. To stop a pending upgrade job and remove it from the list, select the Cancel and Delete Jobs button. Use additional links on the page as shortcuts to the Device Setup > Upload Firmware & Files page, or the complete raw text of the Firmware Server Log To view additional details about an individual upgrade job including the devices being upgraded, select the name of an upgrade job from the Name column to go to the System > Firmware Upgrade Job Detail page, illustrated in Figure 161. From here you can click the device name to go to its APs/Devices > Monitor page, or the link under Firmware File column to go to the Device Setup > Upload Firmware & Files page. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

218 Figure 161 System > Firmware Upgrade Job Detail Page Illustration Using the System > Performance Page The System > Performance page displays basic OV3600 hardware information as well as resource usage over time. OV3600 logs performance statistics such as load average, memory and swap data every minute. The historical logging is useful to determine the best usable polling period and track the health of OV3600 over time. The page is divided into four sections: System Information Performance Graphs Database Statistics Disk Usage Figure 162 illustrates this page and Table 123 describes fields and information displayed. 218 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

219 Figure 162 System > Performance Page Illustration (Partial Screen) OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

220 Table 123 System > Performance Page Fields and Graphs Field Description System Information CPU(s) Memory Kernel Architecture Device Polling Performance Graphs System Load Average System Memory Usage System Disk Utilization System Disk IOPs System Disk Throughput System Disk Outstanding I/O Requests System Swap Usage System CPU Utilization I/O Throughput by Worker/by Service CPU Utilization by Worker/by Service System Network Bandwidth Bandwidth by Protocol Legacy SNMP Fetcher Requests Legacy SNMP Fetcher Responses High Performance SNMP Fetcher Requests High Performance SNMP Fetcher Responses Basic CPU information as reported by the operating system. The amount of physical RAM and Swap space seen by the operating system. Refer to the OV3600 Server Hardware Guide for hardware requirements. The version of the Linux kernel running on the box. The AMP s architecture information. Displays some AP/Device polling statistics. The number of jobs currently waiting to be processed. Load is a rough metric that will tell you how busy a server is. A typical OV3600 load is around 2-3 times the number of CPU cores you have in your system. A constant load of 4x to 5x is cause for concern. A load above 6x is a serious issue and will probably result in OV3600 becoming unusable. To lower the load average, try increasing a few polling periods in the Groups > Basic page. The amount of RAM that is currently used broken down by usage. It is normal for OV3600 to have very little free RAM. Linux automatically allocates all free RAM as cache and buffer. If the kernel needs additional RAM for process it will dynamically take it from the cache and buffer. The amount of data read from the disk and written to the disk. The number of disk reads and writes per second. The rate of reading and writing from and to the disk in bytes per second. The average number of outstanding I/O requests (queue depth). If it's high, it means that I/O requests (disk reads/writes) aren't being serviced as fast as they're being asked for. The amount of Swap memory used by OV3600. Swap is used when the there is no more free physical RAM. A large performance penalty is paid when swap is used. If an OV3600 consistently uses swap, you should consider installing additional RAM. The percentage of CPU that has been used by the user and the system as well as the amount that was idle. Displays reads and writes for workers (OV3600 services, database, VisualRF, web server, RRD tool and AWRRD tool) and for services (OV3600, VisualRF and web server). Displays reads and writes for workers (OV3600 services, database, VisualRF, web server, RRD tool and AWRRD tool) and for services (OV3600, VisualRF and web server). All traffic in and out measured in bits per second of your primary network interface (Eth0 being the most common). Displays the amount of traffic used by Telnet, HTTPS and SNMP used by your primary network interface (Eth0 being the most common). The number of SNMP get and walk requests per second performed by the legacy (v1 and v3) SNMP fetcher. The number of SNMP OIDs received per second performed by the legacy (v1 and v3) SNMP fetcher. The number of SNMP get and walk requests per second performed by the high performance SNMP (v2c) fetcher. The number of SNMP OIDs received per second performed by the high performance SNMP (v2c) fetcher. 220 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

221 Table 123 System > Performance Page Fields and Graphs (Continued) Field Description Database Statistics Top 5 Tables (by row count) Database Table Scans Database Row Activity Database Transaction Activity Disk Space Disk Space The five largest tables in OV3600. Degraded performance has been noticed for in some cases for tables over 200,000 rows. Decreasing the length of time client data is stored on the OV3600 page is recommended if a user/client table exceeds 250,000 rows. The number of database table scans performed by the database. The number of insertions, deletions and updates performed to the database. The number of commits and rollbacks performed by the database. Pie charts that display the amount of used and free hard drive space for each partition. If a drive reaches over 80% full, you may want to lower the Historical Data Retention settings on the OV3600 Setup > General page or consider additional drive space. There are several initial steps that you can take to troubleshoot OV3600 performance problems, including slow page loads and timeout errors. Initial troubleshooting steps would include the following: Increasing the polling period settings on the Groups > Basic page. Increasing the polling period time for groups with routers and switches. Adding additional memory to the server. Please consult the sizing information in the latest edition of the OV3600 Server Sizing Guide or contact Alcatel support for the latest recommendations. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

222 Supporting OV3600 Servers with the Master Console The Master Console (MC) is used to monitor multiple OV3600 stations from one central location. The Master Console is designed for customers running multiple OV3600 servers. Once an OV3600 station has been added to the MC, it will be polled for basic OV3600 information. Much like the normal Home > Overview page, the Master Console Home > Overview page provides summary statistics for the entire network at a glance. Figure 163 illustrates the Overview page: Figure 163 Master Console Home > Overview Page Illustration Reports can be run from the Master Console to display information from multiple OV3600 stations; because such reports can be extremely large, reports can also be run as summary only so that they generate more quickly and finish as a manageable file size. The Master Console can also be used to populate group-level configuration on managed OV3600 installations using the Global Groups feature. The Master Console offers a display of devices that are in a Down or Error state anywhere on the network. This information is supported on Master Console pages that display device lists such as Home > Overview and APs Devices > List. The Master Console and Failover servers can be configured with a Managed OV3600 Down trigger that generates an alert if communication is lost to a managed or watched OV3600 station. The Master Console or Failover server can also send or NMS notifications about the event.. The license key determines if the server will behave as a Master Console or as a standard OV3600 server. Using the Public Portal on Master Console The Master Console also contains an optional Public Portal which allows any user to view basic group-level data for each managed OV3600. This feature is disabled by default for security reasons; no OV3600 or Master Console login is required to view the public portal. The Public Portal can be enabled in OV3600 Setup > General in the Master Console section. Once enabled, a new Portal tab will appear to the right of the Groups tab (refer to the navigation section in Figure 163 in the previous page). The URL of the public 222 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

223 portal will be When you upgrade to the latest version of OV3600, the public portal is disabled by default, regardless of the type of license. Figure 164 Public Portal Page Illustration The Public Portal supports configuration of the iphone interface. This can be configured using the Master Console OV3600 page. See Defining General OV3600 Server Settings on page 37. Adding a Managed OV3600 with the Master Console Perform the following steps to add a managed OV3600 console. 1. Navigate to the Home > Managed OV3600s page. 2. Select the pencil icon to edit or reconfigure an existing OV3600 console, or select Add New Managed OV3600 to create a new OV3600 console. The Managed OV3600 page appears. Complete the settings on this page as described in Table 124. Table 124 Managed OV3600 Fields and Default Values Field Default Description Hostname / IP Address N/A Enter the IP address or Hostname of the OV3600 server to be managed. Polling Enabled Yes Enables or disables the Master Console polling of managed OV3600 server. Polling Period 5 minutes Determines how frequently the Master Console polls the managed OV3600 server. Username N/A The username used by the Master Console to login to the managed OV3600 server. The user needs to be an AP/Device Manager or OV3600 Administrator. Password (Confirm Password) HTTP Timeout ( sec) Manage Group Configuration N/A The password used by the Master Console to login to the managed OV Defines the timeout period used when polling the managed OV3600 server. No Defines whether the Master Console can manage device groups on the managed OV3600 server. 3. When finished, select Add to return to the Managed OV3600s list page. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

224 Using Global Groups with Master Console To push configurations to managed groups using the OV3600 Global Groups feature, follow these steps: 1. Navigate to the Master Console's Groups > List page. 2. Select Add to add a new group, or select the name of the group to edit settings for an existing group. 3. Select the Duplicate icon to create a new group with identical configuration to an existing group. Groups created on the Master Console will act as Global Groups, or groups with master configurations that can be pushed out to subscriber groups on managed OV3600s. Global groups are visible to all users, so they cannot contain APs (which can be restricted based on user role). 4. Selecting the name of an existing group on the Master Console loads the subtabs for Basic, Security, SSIDs, AAA Servers, Templates, Radio, Cisco WLC Config, Proxim Mesh, and MAC ACL pages, if such pages and configurations are active for the devices in that group. These subtabs contain the same fields as the group subtabs on a monitored OV3600, but each field also has a checkbox. The Master Console can also configure global templates that can be used in subscriber groups. The process is the same as described in the Chapter 6, Creating and Using Templates, except that there is no process by which templates can be fetched from devices in the subscriber group on managed OV3600s. Instead, the template must be copied and pasted into the Master Console Global Group. When a Global Group is pushed from the Master Console to subscriber groups on managed OV3600s, all settings will be static except for settings with the checkbox selected; for fields with checkboxes selected, the value or setting can be changed on the corresponding tab for each managed group. For list pages, override options are available only on the Add page for each list. It will take several minutes for changes to Global Groups on the Master Console to be pushed to the managed OV3600s; make sure that the Manage Group Configuration option is enabled for each managed OV3600. Once Global Groups have been configured on the Master Console, groups must be created or configured on the managed OV3600s to subscribe to a particular Global Group. To configure subscriber groups, enable Use Global Groups on the Group > Basic page of a group on a managed OV3600. Select the name of the Global Group from the drop-down menu, and then select Save and Apply. Note that the MC doesn't push anything when you create new subscriber groups; the copy of the Global Group already on the managed OV3600 provides the information. Once the configuration is pushed, the non-overridden fields from the Global Group will appear on the subscriber group as static values and settings. Only fields that had the override checkbox selected in the Global Group will appear as fields that can be set at the level of the subscriber group. Any changes to a static field must be made on the Global Group. The Global Groups feature can also be used without the Master Console. For more information about how this feature works, refer to Configuring and Using Device Groups on page 71. Upgrading OV3600 The OV3600 upgrade process may change. Please contact support and consult the latest OV3600 release announcement for detailed instructions and changes. Upgrade Instructions To upgrade OV3600: 1. Log in to the OV3600 server as the root user. 2. Run the following command (where x.x.x is equal to the latest OV3600 version) # start_ov3600_upgrade -v x.x.x 224 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

225 Upgrading Without Internet Access If your OV3600 cannot get to the Internet: 1. Download the latest OV3600 version from the download page: Copy the file to OV3600 /root directory using WinSCP. 3. On the OV3600, run the following command: # start_ov3600_upgrade -v x.x.x The start_ov3600_upgrade script will check the /root directory for the latest update. If the update is not found, the script will attempt to download it from the AirWave support page. The script will then extract the version specific upgrade script. The version specific script will deploy all needed files, update the database, perform any data migrations and restart the OV3600 services. Backing Up OV3600 OV3600 creates nightly archives of all relational data, statistical data, and log files. This occurs by default at 4:15 AM, but is configurable on the OV3600 Setup > General page under Nightly Maintenance Time. Although OV3600 only keeps the last four sets of archives, the archives can be downloaded manually or automatically off-site for more extensive backup strategies. OV3600 creates one data backup file each night. The data backup file contains all of the device and group information as well as historical data and system files, including IP address, NTP information, mail relay hosts, and other OV3600 settings. Viewing and Downloading Backups To view current OV3600 backup files, go to the System > Backups page. Figure 165 illustrates this page. Figure 165 System > Backups Page Illustration To download a backup file, select the filename URL and the File Download popup page appears. Regularly save the data backup file to another machine or media. This process can be automated easily with a nightly script. Nightly maintenance and amp_backup scripts back up the full OV3600 data and save the file as nightly_data00[1-4].tar.gz. In previous OV3600 versions, the scripts created both config backup and data backup files. In order to restore the OV3600 data, it is only necessary to have most recent data backup file, and OV3600 no longer uses or supports the config backup file, effective as of OV and later OV3600 versions. Running Backup on Demand To create an immediate backup: 1. Log into the OV3600 system as root. 2. Run the backup script by typing ov3600_backup. This creates a backup of the system located in /alternative/databackup.tar.gz. Restoring from a Backup To restore a backup file on a new machine: OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

226 1. Use your OV3600 Installation CD to build a new machine. The new machine must be running the same version as the OV3600 that created the backup file. 2. Copy the nightly_data00[1-4].tar.gz file to the /tmp directory in the new OV3600. A file transfer client that supports SFTP/SCP for Windows is WinSCP: WinSCP allows you to transfer the nightly00[1-4].tar.gz file from your local PC to the new OV3600 using the secure copy protocol (SCP). 3. Log onto the new server as root. 4. Change to the scripts directory by typing scripts. 5. Run the restore script by typing./ov3600_restore -d /tmp/nightly_data00[1-4].tar.gz. Network administrators can now use the nightly backup from a 32-bit OV3600 to restore OV3600 on a 64-bit installation, rather than having to create a special backup file or use the special restore script. Using OV3600 Failover for Backup The failover version of OV3600 provides a many to one hot backup server. The Failover OV3600 polls the watched OV3600s to verify that each is up and running. If the watched OV3600 is unreachable for the specified number of polls, the Failover OV3600 automatically restores the most recent saved backup from the watched OV3600 and begins polling its APs. Navigation Section of OV3600 Failover The Navigation section displays tabs to all main GUI pages within OV3600 Failover. The top bar is a static navigation bar containing tabs for the main components of OV3600, while the lower bar is context-sensitive and displays the subtabs for the highlighted tab. Table 125 describes the contents of this page. Table 125 Contents of the Navigation Section of Failover Main Tab Description Subtabs Home System OV3600 Setup The Home page provides basic OV3600 Failover information including system name, hostname, IP address, current time, running time, software version, and watched OV3600 information. The System page provides information related to OV3600 operation and administration including overall system status, performance monitoring, and backups. The Setup page provides all information relating to the configuration of OV3600 itself and its connection to your network. Overview User Info Watched AMPs License Status Triggers Alerts Event Log Backups Performance General Network Users TACACS+ Adding Watched OV3600 Stations Navigate to the Home > Watched OV3600s page to begin backing up and monitoring OV3600 stations. Once an OV3600 installation has been added to the Watched OV3600 list, the Failover OV3600 will download the most recent backup and begin polling. The Failover OV3600 and the Watched OV3600 must be on the same version or else the watched OV3600 will be unable to restore properly. If any of the watched OV3600s are not on the same version of OV3600, you will need to upgrade. The Failover OV3600 will need HTTPS access (port 443) to the watched OV3600 to verify that the web page is active and to fetch downloads. 226 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

227 Once the Failover OV3600 determines that the Watched OV3600 is not up (based on the user-defined missed poll threshold) it will restore the data backup of the Watched OV3600 and begin monitoring the watched OV3600 APs and devices. There are many variables that affect how long this will take including how long client historical data is being retained, but for an OV3600 with 1,000 APs it might take up to 10 minutes. For an OV3600 with 2,500 APs, it might take as long as 20 minutes. The Failover OV3600 will retain its original IP address. In summary, the Failover OV3600 could take over for the Watched OV3600 in as little as five minutes; it might take up to an additional minutes to unpack the watched OV3600 data and begin monitoring APs. The most important factors are the missed poll threshold, which is defined by the user, and the size of the watched OV3600 backup, which is affected by the total number of APs and by the amount of data being saved, especially client historical data. To restore the Watched OV3600, run the backup script from the command line and copy the current data file and the old Watched OV3600 configuration file to the Watched OV3600. Then run the restore script. More information about backups and restores can be found in Backing Up OV3600 on page 225. Table 126 Home > Watched Page Fields and Default Values Setting Default Description IP/Hostname None The IP address or Hostname of the watched OV3600. The Failover OV3600 needs HTTPS access to the watched OV3600s. Username None A username with management rights on the watched OV3600. Password None The password for the username with management rights specified above. HTTP Timeout ( Sec) 60 The amount of time before OV3600 considers a polling attempt failed. Polling Enabled Yes Enables or disables polling of the Watched OV3600. NOTE: You do not need to disable polling of the watched OV3600 system if it is set to be down during nightly maintenance or is being upgraded. Polling Period 5 minutes The amount of time between polls of the Watched OV3600. Missed Poll Threshold None The number of polls that can be missed before the failover OV3600 will begin actively monitoring the Watched OV3600 APs. Logging out of OV3600 To log out of OV3600, select the Logout link on the upper right hand corner of every OV3600 page. You will be logged off automatically based on the number of minutes set in the Idle Timeout setting of Home > User Info. Refer to Configuring Login Message, TACACS+ and RADIUS Authentication on page 49. OmniVista 3600 Air Manager 7.4 User Guide Performing Daily Administration in OV

228 228 Performing Daily Administration in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

229 Chapter 9 Creating, Running, and ing Reports This chapter describes OV3600 reports, including access, creation, scheduling, and distribution. This chapter includes the following sections: Overview of OV3600 Reports on page 229 Using Daily Reports on page 232 Defining Reports on page 254 ing and Exporting Reports on page 257 OV3600 ships with several reports enabled by default. Default reports may run nightly or weekly, depending on the OV3600 release. Review the list of defined and scheduled reports with the Reports > Generated and Reports > Definition pages to determine if default reports are desired. If not, you can delete, disable, or reschedule any of them. OV3600 supports additional specialized reports as follows: System > Status page supports the diagnostic report file for sending to customer support: diagnostics.tar.gz. System > Status page supports the VisualRF diagnostics report file: VisualRFdiag.tar.gz. VisualRF > Network View supports the Bill of Materials (BOM) report. Refer to Chapter 10, Using VisualRF on page 259. Overview of OV3600 Reports Reports are powerful tools in network analysis, user configuration, device optimization, and network monitoring on multiple levels. Among their benefits, reports provide an interface for multiple configurations. OV3600 reports have the following general parameters: OV3600 runs daily versions of all reports during predefined windows of time. All reports can be scheduled to run in the background. The daily version of any report is available instantly in the Reports > Generated page. The Inventory and the Configuration Audit reports are the only reports that don t span a period of time. Instead, these two reports provide a snapshot of the current state of the network. Users can create all other reports over a custom time period on the Reports > Definitions page. All reports can be ed or exported to XML format for easy data manipulation using a spreadsheet. Reports > Definitions Page Overview The Reports > Definitions page allows you to define new reports and see the reports already defined. The Definitions page includes these sections: Report definitions section The Add button allows you to define a custom report using the Custom Options drag and drop interface, or from any of the report types in the dropdown menu. The Report Definitions table has a complete list of all saved report definitions with an option to return to each definition s table to further customize your report. Add and Run allows you to create a report definition and run that report immediately. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 229

230 Run Now (visible from the expanded Report Definitions menu) allows immediate running of a custom report as soon as you set the parameters. You must save its definition separately, if you want to remember the parameters. Report definitions for other roles section This section, supported for admin users, displays additional reports that have been scheduled for other roles. This section of the page adds the Role column, and other columns are the same. Each pane includes a Latest Report column with the most recently run reports for each definition and role created. Run and Delete buttons allow you to select a report from the definitions table to run or delete. Once you define a report from the Definition page, it appears on the Generated page. The Reports > Definition page is shown in Figure 166, and Table 127 describes the fields available when you select a specific report definition. Table 127 Reports > Definition Page Fields and Descriptions Field Description Report Definition Displays a field for entering report title and dropdown menu, shown in Figure 167, displaying all possible report types. Report Restrictions Scheduling Options Report Visibility Options Add and Run Run Now Add Displays dynamic fields that include spaces for selecting attributes and entering data relevant to your selected report type scope such as groups, folders, SSID, Device Search filter, report start and end times. Reveals options for one time or regularly scheduled reporting by selecting Yes. Options include report frequency, start time, and current system time. Allows you to determine a report s visibility according to user role. Reveals address preferences for sending reports by selecting Yes. Allows you to create a report definition and run that report right then. Allows you to run any report that has been defined on the spot without saving settings or creating a new report definition. Saves report definition you just created. Figure 166 Reports > Definitions Page Illustration (Split View) 230 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

231 Figure 167 Report Type Drop-down Menu in Reports > Definitions Illustration Only admin users have complete access to all report information. The OV3600 reports and online displays of information can vary with configuration, User Roles, and Folders. Reports > Generated Page Overview The Reports > Generated page displays reports that have been run, as well as the most recent daily version of any report. An Admin user can see and edit all report definitions in OV3600. Users with Monitor Only roles can see reports and definitions only if they have access to all devices in the reports. The Reports > Generated page contains three primary sections, as follows: Generated reports configured for the current role and for additional roles Generated reports for other roles The latest daily reports for immediate online viewing Figure 168 Reports > Generated Page Example OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 231

232 Figure 169 Reports > Generated Page with Single-click Report Viewing Options Using Daily Reports This section describes the default and custom-scheduled reports supported in OV3600. These reports can be accessed from the Reports > Generated page. Viewing Generated Reports The Reports > Generated page supports the following general viewing options: By default, the reports on the Reports > Generated page are sorted by Generation Time. You can sort reports by any other column header in sequential or reverse sequential order. You can also choose columns, export the Generated Reports list in CSV, and modify the pagination of this list. The Reports > Detail page launches when you select any report title from this page. The Generated Reports page contains fewer columns and information than the Definitions page. Table 128 describes each column for the Reports > Generated page. Table 128 Reports > Generated Page Fields and Descriptions Field Generated Time Title Type Subject Report Start Report End Role Description Displays the date and time of the last time the report was run, or when the latest report is available. Selecting the link in this field displays the latest version of a given report. When the latest version of a given report is not available, this field is blank. In this case, a report can be run by selecting the report title and selecting Run. Displays title of the report. This is a user-configured field when creating the report. Displays the type of the report. Displays the scope of the report, to include groups, folders, SSIDs, or any combination of these that are included in the report. Displays the beginning of the time period covered in the report. Displays the end of the time period covered in the report. In the Reports definitions for other roles section, this column indicates the roles for which additional reports are defined. Using Custom Reports Custom reports allow users to specify the data that should be included in a report. Perform these steps to create a Custom Report. 1. Navigate to the Reports > Definitions page. 2. Select Add. 3. By default, the Custom option will be selected in the Type drop-down menu, and the Custom Options section appears below as shown in Figure Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

233 Figure 170 OV3600 Custom Options Page Illustration The left pane of the Custom Options section lists all available data that can be included in the report. For example, if the data you want to include is in the RF Health report, select RF Health to view a list of all available radio frequency information. Then, simply drag the desired data from the Available Options list on the left to the Selected Options pane on the right. The order of the data in the Selected Options section is the order that it will appear in the report. The data can be reordered by dragging an item up or down the list. 4. Below the Custom Options panes are the Report Restrictions, Scheduling Options, Report Visibility, and Options sections. Choose the parameters as needed for your report, especially a Report Start and Report End. 5. When finished, select Add and Run to add the report to your list and run it immediately, Run Now to run without being added to the list, Add to add but not run the report, or Cancel to exit this page. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 233

234 Using the License Report A new License Report has been added in the Reports tab to track licenses on Alcatel-Lucent devices in your network. This report includes information on the type, quantity, percent used, installation date, expiration date, and the license keys. Figure 171 License Report Detail Page Using the Capacity Planning Report The Capacity Planning Report tracks device bandwidth capacity and throughput in device groups, folders, and SSIDs. This report assists in analyzing device capacity and performance on the network, and such analysis can help to achieve network efficiency and improved experience for users. This report is based on interface-level activity. The information in this report can be sorted by any column header in sequential or reverse-sequential order by selecting the column heading. Refer also to the Using the Network Usage Report on page 243 for additional bandwidth information. The following figures and Table 129 illustrate and describe the contents of the Capacity Planning Report. 234 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

235 Figure 172 Capacity Planning Report Detail Page Table 129 Capacity Planning Report Fields and Contents, Top Portion Field Device Interface Group Folder Controller Time Above 1% of Capacity Capacity Combined (b/s) Description Displays the device type or name. Displays the type of wireless service supported by the device. Displays the device group with which the device is associated. Displays the folder with which the device is associated. Displays the controller with which a device operates. Displays the time duration in which the device has functioned above 0% of capacity. A low percentage of use in this field may indicate that a device is underused or poorly configured in relation to its capacity, or in relation to user needs. Displays the combined capacity in and out of the device, in bits-per-second. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 235

236 Table 129 Capacity Planning Report Fields and Contents, Top Portion (Continued) Field Usage While > Threshold (Combined) Overall Usage (Combined) Usage While > Threshold (in) Overall Usage (In) Usage While > Threshold (Out) Overall Usage (Out) Description Displays the time in which a device has functioned above defined threshold capacity, both in and out. Displays the overall usage of the device, both combined in and out traffic. Displays device usage that exceeds the defined and incoming threshold capacity. Displays overall device usage for incoming data. Displays device usage for outgoing data that exceeds defined thresholds. Displays device usage for outgoing data. Using the Configuration Audit Report The Configuration Audit Report provides an inventory of device configurations on the network, enabling you to display information one device at a time, one folder at a time, or one device group at a time. This report links to additional configuration pages. Perform these steps to view the most recent version of the report, then to configure a given device using this report. 1. Navigate to the Reports > Generated page. 2. Scroll to the bottom, and select Latest Configuration Audit Report to display Detail device configuration information for all devices. The ensuing Detail report can be very large in size, and provides multiple links to additional device configuration or information display pages. 3. You can display device-specific configuration to reduce report size and to focus on a specific device. When viewing configured devices on the Detail page, select a device in the Name column. The devicespecific configuration appears. 4. You can create or assign a template for a given device from the Detail page. Select Add a Template when viewing device-specific configuration information. 5. You can audit the current device configuration from the Detail page. Select Audit when viewing devicespecific information. 6. You can display archived configuration about a given device from the Detail page. Select Show Archived Device Configuration. Figure 173 and Table 130 illustrate and describe the general Configuration Audit report and related contents. 236 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

237 Figure 173 Reports > Generated > Daily Configuration Audit Report Page, abbreviated example Table 130 Daily Configuration Audit Report Field Name Folder Group Mismatches Description Displays the device name for every device on the network. Selecting a given device name in this column allows you to display device-specific configuration. Displays the folder in which the device is configured in OV3600. Selecting the folder name in this report displays the APs/Devices > List page for additional device, folder and configuration options. Displays the group with which any given device associates. Selecting the group for a given device takes you to the Groups > Monitor page for that specific group, to display graphical group information, modification options, alerts, and an audit log for the related group. This field displays configuration mismatch information. When a device configuration does not match ideal configuration, this field displays the ideal device settings compared to current settings. Using the Device Summary Report The Device Summary Report identifies devices that are the most or least used devices, and a comprehensive list of all devices. One potential use of this report is to establish more equal bandwidth distribution across multiple devices. This report contains the following five lists of devices. Most Utilized by Maximum Number of Simultaneous Users By default, this list displays the 10 devices that support the highest numbers of users. This list provides links to additional information or configuration pages for each device to make adjustments, as desired. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 237

238 Most Utilized by Bandwidth By default, this list displays the 10 devices that consistently have the highest bandwidth consumption during the time period defined for the report. This list provides links to additional information or configuration pages for each device. Least Utilized by Maximum Number of Simultaneous Users By default, this list displays the 10 devices that are the least used, according to the number of users. Least Utilized by Bandwidth By default, this list displays the 10 devices that are the least used, according to the bandwidth throughput. Devices This list displays all devices in OV3600. By default it is sorted alphabetically by device name. You can specify the number of devices that appear in each of the first four categories in the Reports > Definitions > Add page. Any section of this report can be sorted by any of the columns. For example, you can specify a location and then sort the Devices list by the Location column to see details by location, or you can see all of the APs associated with a particular controller by sorting on the Controller column. If the AP name contains information about the location of the AP, you can sort by AP name. If sorting the Devices list does not provide you with sufficient detail, you can specify a Group or Folder in the report Definition of a custom report. If you create a separate Group or Folder for each set of master and local controllers, you can generate a separate report for each Group or Folder. With this method, the summary sections of each report contain only devices from that Group or Folder. and Table 131 illustrate and describe the Reports > Generated > Device Summary Detail page. 238 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

239 Figure 174 Reports > Generated > Daily Device Summary Report Illustration (partial view) Table 131 Reports > Generated > Daily Device Summary Report Unique Fields and Descriptions Field Max Simultaneous Users Total Bandwidth (MB) Average Bandwidth (kbps) Description Displays the maximum number of users that were active on the associated device during the period of time that the report covers. Displays the bandwidth in megabytes that the device supported during the period of time covered by the report. Displays the average bandwidth throughput for the device during the period of time covered by the report. Using the Device Uptime Report The Device Uptime Report monitors device performance and availability on the network, tracking uptime by multiple criteria to include the following: Total average uptime by SNMP and ICMP Average uptime by device group Average uptime by device folder OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 239

240 You can use this report as the central starting point to improve uptime by multiple criteria. This report covers protocol-oriented, device-oriented, or SSID-oriented information. This report can help to monitor and optimize the network in multiple ways. It can demonstrate service parameters, can establish locations that have superior or problematic uptime availability, and can help with additional analysis in multiple ways. Locations, device groups, or other groupings within a network can be identified as needing attention or can be proven to have superior performance when using this report. As of AirWave 7.4, the Device Uptime Report contains four new columns that track bootstrap count (number of times the device has gone down for a firmware change), reboot count, downtime duration, and downtime duration percent. As mentioned above, you can optionally ignore device downtime during planned maintenance periods in this report, and you can restrict the report to business days only. Figure 175 and Table 131 illustrate and describe the Device Uptime report. Figure 175 Device Uptime Report Illustration Table 132 Reports > Generated > Device Uptime Report Unique Fields and Descriptions Field SNMP Uptime ICMP Uptime Time Since Last Boot Description Displays the percentage of time the device was reachable via ICMP. OV3600 polls the device via SNMP at the rate specified on the Groups > Basic page. Displays the percentage of time the device was reachable via ICMP. If the device is reachable via SNMP it is assumed to be reachable via ICMP. OV3600 only pings the device if SNMP fails and then it pings at the SNMP polling interval rate. The uptime as reported by the device at the end of the time period covered by the report. 240 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

241 Using the IDS Events Report The IDS Events Report lists and tracks IDS events on the network involving APs or controller devices. This report cites the number of IDS events for devices that have experienced the most instances in the prior 24 hours, and provides links to support additional analysis or configuration in response. Your role must be enabled to view RAPIDS to see this report. The Home > Overview page also cites IDS events, and triggers can be configured for IDS events. Refer to Setting Triggers for IDS Events on page 195 for additional information. Selecting the AP device or controller name takes you to the APs/Devices > List page. Figure 176 and Table 133 illustrate and describe the Reports > Generated > IDS Events Detail page. Figure 176 Reports > Generated > IDS Events Report Illustration Table 133 Reports > Generated > IDS Events Detail Unique Fields and Descriptions Field Attack Controllers Attacker Radio Channel SNR Precedence Time Description Displays the name or label for the IDS event. This column lists the controllers for which IDS events have occurred in the prior 24 hours, and provides a link to the APs/Devices > Monitor page for each. Displays the MAC address of the device that generated the IDS event. Displays the radio type associated with the IDS event. Displays the radio channel associated with the IDS event, when known. Displays the signal-to-noise (SNR) radio associated with the IDS event. Displays precedence information associated with the IDS event, when known. Displays the time of the IDS event. Using the Inventory Report The Inventory Report itemizes all devices and firmware versions on the network, to include vendor information and graphical pie-chart summaries. The primary sections of this report are as follows: Vendor Summary Lists the vendors for all devices or firmware on the network. Firmware Version Summary Lists the firmware version for all firmware used on the network. Model Summary Lists the model numbers for all devices or firmware on the network. See Figure 177 for an illustration of a sample report. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 241

242 Figure 177 Reports > Generated > Inventory Report Illustration (Edited View) 242 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

243 Using the Memory and CPU Utilization Report The Memory and CPU Utilization Report displays the top memory usage by device, and CPU usage on the network by device. Both are by percentage. To create a scheduled and generated report of this type, refer to Using Daily Reports on page 232. Figure 178 illustrates the Reports > Detail page for this report. Figure 178 Reports > Generated > Daily Memory and CPU Usage Report Illustration (Contents Rearranged for Space) Using the Network Usage Report The Network Usage Report contains network-wide information in two categories: Bandwidth usage by device maximum and average bandwidth in kbps Number of users by time period average bandwidth in and out Figure 179 illustrates the Reports > Detail page for the Daily Network Usage. Figure 179 Reports > Generated > Network Usage Report Illustration OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 243

244 Using the New Rogue Devices Report The New Rogue Devices Report summarizes rogue device information including the following categories of information: Rogue devices by RAPIDS classification described in Using RAPIDS and Rogue Classification on page 169 Top rogue devices by number of discovering APs Top rogue devices by signal strength Graphical summary of rogue devices by LAN MAC address vendor Graphical summary of rogue devices by radio MAC address vendor Text-based table summary of rogue device counts Detailed and text-based table of rogue devices discovered only wirelessly with extensive device parameters and hyperlink interoperability to additional OV3600 pages Detailed and text-based table of all rogue devices supporting all discovery methods with extensive device parameters and hyperlink interoperability to additional OV3600 pages Detailed and text-based table of discovery events pertaining to the discovery of rogue devices with extensive parameters and hyperlink interoperability to additional OV3600 pages This report is not run by default, but is available after you define it. Refer to Figure 180 for a sample illustration of this report. 244 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

245 Figure 180 Reports > Generated > New Rogue Devices Report Illustration The rogue device inventories that comprise this report contain many fields, described in Table 134. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 245

246 Table 134 New Rogue Devices Report Fields Field Name RAPIDS Classification Threat Level Ack First Discovered First Discovery Method First Discovery Agent Last Discovering AP Model Operating System IP Address SSID Network Type Channel WEP RSSI Signal LAN MAC Address LAN Vendor Radio MAC Address Radio Vendor Port Last Seen Total Discovering APs Total Discovery Events Description Displays the device name, as able to be determined. Displays the RAPIDS classification for the rogue device, as classified by rules defined on the RAPIDS > Rules page. Refer to Using RAPIDS and Rogue Classification on page 169 for additional information. Displays the numeric threat level by which the device has been classified, according to rules defined on the RAPIDS > Rules page. Refer to Using RAPIDS and Rogue Classification on page 169 for additional information. Displays whether the device has been acknowledged with the network. Displays the date and time that the rogue device was first discovered on the network. Displays the method by which the rogue device was discovered. Displays the network device that first discovered the rogue device. Displays the network device that most recently discovered the rogue device. Displays the rogue device type when known. Displays the operating system for the device type, when known. Displays the IP address of the rogue device when known. Displays the SSID for the rogue device when known. Displays the network type on which the rogue was detected, when known. Displays the wireless RF channel on which the rogue device was detected. Displays WEP encryption usage when known. Displays Received Signal Strength (RSSI) information for radio signal strength when known. Displays signal strength when known. Displays the MAC address for the associated LAN when known. Displays LAN vendor information associated with the rogue device, when known. Displays the MAC address for the radio device, when known. Displays the vendor information for the radio device when known. Displays the router or switch port associated with the rogue device when known. Displays the last time in which the rogue device was seen on the network. Displays the total number of APs that detected the rogue device. Displays the total number of instances in which the rogue device was discovered. 246 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

247 Using the New Users Report The New Users Report lists all new users that have appeared on the network during the time duration defined for the report. This report covers the user identifier, the associated role when known, device information and more. The report definition can filter on connection mode (wired, wireless or both). Figure 181 illustrates the fields and information in the New Users Report. Figure 181 Reports > Generated > New Users Report Illustration Using the PCI Compliance Report OV3600 supports PCI requirements in accordance with the Payment Card Industry (PCI) Data Security Standard (DSS). The PCI Compliance Report displays current PCI configurations and status as enabled on the network. Verify that OV3600 is enabled to monitor compliance with PCI requirements, as described in the Enabling or Disabling PCI Auditing on page 68. In addition to citing simple pass or fail status with regard to each PCI requirement, OV3600 introduces very detailed diagnostic information to recommend the specific action or actions required to achieve Pass status, when sufficient information is available. Refer to the Auditing PCI Compliance on the Network on page 66 for information about enabling PCI on the network. The configurations in that section enable or disable the contents of the PCI Compliance Report that is viewable on the Reports > Generated page. Figure 182 illustrates the fields and information in a PCI Compliance Report. Figure 182 Reports > Generated > PCI Compliance Report Illustration Example OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 247

248 Using the Port Usage Report You can generate a wide array of port usage statistics from the Port Usage Report including each of the following: List of all the switches and ports in your network by folder List of unused ports List of access and distribution ports Histogram displaying unused ports vs. unused switches by type (access or distribution) List of most used switches List of most used ports A sample of the types of information used to generate in a Port Usage Report appears in Figure 183. Figure 183 Reports > Generated > Port Usage Report Detail Page (partial view) Using the RADIUS Authentication Issues Report The RADIUS Authentication Issues Report contains issues that may appear with controllers, RADIUS servers, and users. Figure 184 illustrates the fields and information in the RADIUS Authentication Issues Report. 248 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

249 Figure 184 Reports > Generated > RADIUS Authentication Issues Detail Page Illustration Using the RF Health Report The RF Health Report tracks the top AP radio issues by noise, MAC/Phy errors, channel changes, transmit power changes, mode changes, and interfering devices (the last two apply only if there are ARM events). This report assists in pinpointing the most problematic devices on your network, and lists the top 10 devices by problem type. Problematic APs are displayed in two separate lists Problem Radios lists, grouped by radio frequency. A device will make it into the list if it violates two or more thresholds. (For more on the thresholds that indicate problems, refer to Evaluating Radio Statistics for an AP on page 124.) Other lists grouped by radio frequency include Most Noise, Most/Least Utilized by Channel Usage, Most MAC/Phy Errors, Most Channel Changes, Most Transmit Power Changes. If an RF Health Report has not been generated before, you can create it by following the instructions on the Defining Reports section of this chapter. Figure 185 illustrates a sample RF Health Report. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 249

250 Figure 185 Reports > Detail > Daily RF Health Report Page Illustration All tables in RF Health indicate the rank, device type, number of users, bandwidth, location, controller, 250 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

251 folder, and group, and all are sorted according to rank. Selecting a value under the Device column in any table will take you to the APs/Devices > Monitor > Radio Statistics page for the band indicated in the table title (5 GHz or 2.4 GHz). Every list contains Rank, Device (name, not type), Channel Changes, Average Noise, Average Channel Utilization, Clients, Usage, Location, Controller name, Speed, Goodput, Folder, and Group. The third column in the list (after Device) will be the column the list is sorted by. If that column would otherwise be in the list (Channel Changes), it does not show up in the list where it would otherwise. Note that sometimes the sorted column is not one of those common ones, such as the Interfering Devices section. OV3600 limits data storage to 183 days (approximately six months) per radio. If you create an RF Health Report with a date range longer than 183 days, it will only include Channel Changes, Transmit Power Changes, Average Utilization, Mac/Phy Errors and Average Noise based on whatever part of the report intersects the last 183 days. This differs from most reports because other data (like bandwidth and users) maxes out at 425 days, and OV3600 validates reports so you can only run them over a 366-day duration. Using the Rogue Clients Report The Rogue Clients report tracks the number of valid users that connected to rogues in the specified time frame, and can be filtered by rogue classification. Ad-hoc devices can be included, and specific details that should be included about the clients can be selected. By default, the minimum RAPIDS classification is Suspected Rogue, and the maximum is Contained Rogue. Figure 186 Reports > Detail > Rogue Clients Report Page Illustration OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 251

252 Using the Rogue Containment Audit Report The rogue containment audit report that lets you know if any containment is failing. Figure 187 illustrates the fields and information in this report type. Figure 187 Reports > Detail > Rogue Containment Audit Report Page Illustration Using the Client Session Report The Client Session Report extensively itemizes user-level activity by session- any instance in which a user connects to the network. In list and chart form, this report tracks and display session information that can include any or all of the following: Session Data by OS (List or Chart) Session Data by OS Detail (List or Chart) Session Data by Model (List or Chart) Session Data by Manufacturer (List or Chart) Session Data by Device Type (List or Chart) Session Data by AOS Device Type (List or Chart) Session Data by Network Interface Vendor (List or Chart) Session Data by Network Chipset (List or Chart) Session Data by Network Driver (List or Chart) Session Data by EAP Supplicant (List or Chart) Session Data by Asset Group (List or Chart) Session Data by Asset Category (List or Chart) Session Data by Connection Mode (List or Chart) Session Data by SSID (List or Chart) Session Data by Role (List or Chart) Session Data by VLAN (List or Chart) Session Data by Cipher (List or Chart) Summary Sessions Session Data By Client 252 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

253 Figure 188 Client Session Detail, Partial View OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 253

254 Defining Reports You can create reports in OV3600 for any time period you wish, to be run when you wish, and distributed to recipients that you define. Perform these steps to create and run custom reports. Reports created with the Reports > Definition page appear on this and on the Reports > Generated page once defined. 1. To create or edit a report, browse to the Reports > Definition page and select the Add button, or select the pencil icon to edit an existing report definition. Figure 189 illustrates one view of the Reports > Definition page. Figure 189 Defining a Report with Reports > Definitions > Add Button 2. Complete the fields described in Table 135 and any additional Report Restrictions. The Report Restrictions section changes according to the report type you choose. Additional information about each report type is described in Using Daily Reports on page 232. Table 135 Reports > Definitions > Add Page Fields Field Default Description Title Empty Enter a Report Title. Use a title that is a meaningful and descriptive, so it may be found easily on the lists of reports that appear on either Generated or Definitions pages. Type Capacity Choose the type of report you wish to create in the Report Type drop-down menu. Group All Groups Specify the groups and folders to be covered in the report by choosing All Groups (or Folder All Folders All Folders) or specifying Use selected groups (or Use selected folders) in the dropdown menu. If Use selected groups is chosen, a menu with checkboxes appears, allowing you to choose the groups to include in the report. Device Search Filter Filter by device type Blank All Device Types Add a specific alpha numeric string for finding devices that match that which you entered. Note that once you enter a search string, new or deleted devices that match the search string will automatically be included or excluded in all future reports generated until you delete or change the search string. For certain reports, such as New User and Client Session, will allow you to search devices associated with a specific user or device. Filter this report by device type. By selecting the second option - Use selected device types - you can select the checkboxes next to the specific device types you want to filter on: Access Points (such as campus APs remote APs, and different types of Mesh APs), Controllers (Master, Local, Standby, and Virtual), Switches & Routers (Acatel- Lucent and non-alcatel-lucent), and Universal & Custom Devices. SSID All SSIDs This field displays for most report types. When this field appears, and when you select Use Selected IDs, a new list of SSIDs displays. Check (select) the specific SSIDs to be included in the report. 254 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

255 Table 135 Reports > Definitions > Add Page Fields (Continued) Field Default Description Report Start Report End Blank In the report restrictions section you can customize any detailed information contained in a chosen report. Figure 190 shows a sample Report Restrictions page. Figure 190 Report Restrictions Illustration These fields establish the time period to be covered by the report. These fields are supported for most report types. When these fields do not appear, the report provides a snapshot of current status rather than information covering a period of time Times can be entered in relative or absolute form. A start date of 6 months 3 weeks 5 days 9 hours ago and an end time of 4 months 2 weeks 1 day ago is valid, as is a start date of 5/5/ :00 and an end date of 6/6/2008 9:00. Absolute times must be entered in a 24-hour format. Other reports, like the Inventory Report, give a snapshot picture of the OV3600 at the present time. Schedule No When you select Yes, new fields display that allow you to define a specific time for report creation. The report schedule setting is distinct from the Report Start and Report End fields, as these define the period of time to be covered by the report. These Schedule fields establish the time that a report runs, independent of report scope: Current Local Time Displays for reference the time of the OV3600 system. Desired Start Date/Time Sets the time the report runs, which may often be separate from the time period covered by the report. This allows you to run a report during less busy hours. Occurs Select whether the report is to be run one time, daily, weekly, monthly, or annually. Depending on the recurrence pattern selected, you get an additional dropdown menu. For example, if you select a recurrence of monthly, you get an additional drop-down menu that allows you to pick which day of the month (day 1, day 2, and so forth) the report should run. Generated Report Visibility Report By Role No This field allows you to display the report either by user role, with the report appearing in User Role lists on the Reports > Generated page. Alternatively, this field allows you to display reports by Subject on the Reports > Generated page. Select Yes to display sender and recipient fields. Enter the Sender Address where marked to indicate the address that appears in the From field of the ed report. Enter recipient addresses separated by commas when using multiple addresses. NOTE: OV3600 will not attempt to a report with an excessively large number of rows in the detail section. By default all data will be included. Deselect the checkbox to hide specific information. The list can also be reordered by dragging and dropping the separate lines. The order displayed here will match the column order in the report. OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 255

256 3. Do one of the following: Select Add and Run to generate the report immediately, in addition to saving report settings. Select Run Now to generate the report immediately without creating a new report definition or saving the report settings. Select Add (only) to complete the report creation, to be run at the time scheduled. Select Cancel to exit from the Add page. Table 136 describes the configurable settings for the custom report to be created. Select any of the report names to view additional information on that report type. Table 136 Report Types and Scheduling Options Supported for Custom Reports Report Type Can by Run by Time Period Can be Run by Group/Folder Description Using Custom Reports Using the Capacity Planning Report Using the Configuration Audit Report Using the Device Summary Report Using the Device Uptime Report Using the IDS Events Report Using the Inventory Report Using the Memory and CPU Utilization Report Using the Network Usage Report Using the New Rogue Devices Report Using the New Users Report Using the PCI Compliance Report Using the Port Usage Report Using the RADIUS Authentication Issues Report Using the RF Health Report Yes Yes Summarizes devices based on which have exceeded a defined percentage of their maximum bandwidth capacity. Pulls data for AP radios or interfaces of universal devices (ifspeed value). Yes Yes Tracks bandwidth capacity and consumption according to thresholds for data throughput. This is a device-oriented report. No Yes Provides a snapshot of the configuration of all specified access points in OV3600, at report run time. Yes Yes Summarizes user and bandwidth statistics and lists devices in OV3600. Yes Yes Summarizes device uptime within defined groups or folders. Yes Yes Summarizes IDS events; can be limited to a summary of a certain number of events. No Yes Provides an audit of vendors, models and firmware versions of devices in OV3600. Yes Yes Summarizes usage for controllers for defined top number of devices; can be run with or without per-cpu details and details about device memory usage. Yes Yes Summarizes bandwidth data and number of users. Yes No Shows new rogue devices by score, discovering AP, and MAC address vendor. Yes No Provides a summary list of new users, including username, role, MAC address, discovering AP, and association time. Yes Yes Provides a summary of network compliance with PCI requirements, according to the PCI requirements enabled in OV3600 using the OV3600 Setup > PCI Compliance page. Yes Yes Summarizes switch and port information across the network. Generates information on the unused ports. Provides a detailed list of all available switches and ports in the network. Yes Yes Summarizes RADIUS authentication issues by controller and by user, as well as a list of all issues. Yes Yes Tracks problematic radios, changes, errors, and interfering devices. 256 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

257 Table 136 Report Types and Scheduling Options Supported for Custom Reports (Continued) Report Type Can by Run by Time Period Can be Run by Group/Folder Description Using the RF Health Report Using the Client Session Report No Yes Identifies discrepancies between access point containment status specified in OV3600 compared to containment status identified by the controller at report run time. Yes Yes Summarizes user data by radio mode, SSID and VLAN, as well as lists all sessions. ing and Exporting Reports This section describes three ways in which distribute reports from OV3600: ing Reports in General Applications ing Reports to Smarthost Exporting Reports to XML or CSV ing Reports in General Applications Perform these steps to set up distribution of reports in OV3600: All reports contain a link to export the report to an XML file and a text box where you may specify addresses, separated by commas, to which reports are sent. Select This Report to the report to the address specified in the text box above the button. Additional information about -based report generation is described in Defining Reports on page 254, and in ing Reports to Smarthost on page ing Reports to Smarthost OV3600 uses Postfix to deliver alerts and reports via , because it provides a high level of security and locally queues until delivery. If OV3600 sits behind a firewall, which prevents it from sending directly to the specified recipient, use the following procedure to forward to a smarthost. 1. Add the following line to /etc/postfix/main.cf: relayhost = [mail.example.com] Where: mail.example.com is the IP address or hostname of your smarthost. 2. Run service postfix restart 3. Send a test message to an address. Mail -v xxx@xxx.com Subject: test mail. CC: 4. Press Enter. 5. Check the mail log to ensure mail was sent by running this command: tail -f /var/log/maillog OmniVista 3600 Air Manager 7.4 User Guide Creating, Running, and ing Reports 257

258 Exporting Reports to XML or CSV OV3600 allows you to export individual reports in XML (xhtml) or CSV. You can also export all reports at once and a zip file will be generated with all of the files in CSV format included. These files may be read by an HTML browser or opened in Excel. The CSV files can be opened in any text editor. This method of exporting files supports graphics and links, and prevents Missing File C:\filename.css error messages. Transferring Reports Using FTP Once reports are generated, you can also copy them to any ftp accessible destination using a sample script. For more information, contact Alcatel support. 258 Creating, Running, and ing Reports OmniVista 3600 Air Manager 7.4 User Guide

259 Chapter 10 Using VisualRF This chapter contains information about VisualRF, and includes the following topics: Features on page 260 Useful Terms on page 260 Starting VisualRF on page 261 Basic QuickView Navigation on page 261 Using the Settings in the VisualRF > Setup Page on page 266 Configuring QuickView Personal Preferences on page 270 Increasing Location Accuracy on page 271 Using QuickView to Assess RF Environments on page 278 Planning and Provisioning on page 283 Importing and Exporting in VisualRF on page 293 VisualRF Location APIs on page 296 About VisualRF Plan on page 297 The VisualRF module provides a real-time picture of the actual radio environment of your wireless network and the ability to plan the wireless coverage of new sites. To understand what is happening on your wireless network, you need to know where your users and devices are located, and you need to monitor the RF environment in those areas. VisualRF puts this information at your fingertips through integrated mapping and location data. VisualRF uses sophisticated RF fingerprinting to accurately display coverage patterns and calculate the location of every wireless device in range. Moreover, VisualRF does not require dedicated RF sensors or a costly additional location appliance - all the necessary information is gathered from your existing wireless access points and controllers. Figure 191 Example VisualRF Page Showing all networks OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 259

260 Features VisualRF 7.3 adds a new Mesh monitoring page specially for viewing Alcatel-Lucent AirMesh devices. It automatically renders Mesh APs based on GPS coordinates. Floor plan upload wizard enables direct importation of JPEG, GIF, PNG, PDF and CAD files for floor plans. Batch upload wizard enables batch uploads of multiple CAD files with corresponding walls, and access points. Accurate calculation of the location of all client devices (laptops, RFID Tags, PDAs, Phones) using RF data from your existing APs and controllers. Further improvements in accuracy can be achieved with site surveys. Graphical navigation allows your Help Desk to view floor plans simply by clicking on the appropriate campus, building, or floor. Tree view allows you to navigate to a specific campus, building, or floor via a tree navigation. Heatmaps depict the strength of RF coverage in each location. Speed (data rate) view which depicts the highest possible speed at every location on a floor plan. Built into the OmniVista 3600 Air Manager for onscreen display of alerts and error conditions. For instance, an AP icon will display in red when a critical alert is active or when usage conditions exceed pre-defined thresholds. Location playback viewer which allows visual tracking of up to 24 hours of location history. Dynamically recalculates path loss and device locations based on real-time data from your wireless LAN, for increased location accuracy. Calibrates RF data from multiple vendors' APs (and across different product lines from the same vendor) for accurate display even in multi-vendor and multi-architecture environments. Full planning capabilities based on speed or signal requirements. Useful Terms VisualRF - The OV3600 service that calculates location, calculates path loss, and provides floor plan editing capabilities. VisualRF Plan - Makes the planning portions of VisualRF available in an offline software package that does not require a server. For more information about VisualRF Plan, see About VisualRF Plan on page 297. QuickView - Flash front-end for VisualRF which displays information generated by the backend service. mw - 1/1000 of a Watt. It is a linear measurement (always positive) generally used to represent transmission. db (Decibels) - difference/ratio between two signal levels. dbm - db as compared to 1 mw. It is a logarithmic measurement (integer) which is typically used in place of mw to represent receive-power level. AMP normalizes all signals to dbm, so it is easy to evaluate performance between various vendors. RSSI (Received Signal Strength Indicator) - IEEE defines RSSI is a mechanism by which RF energy is to be measured by the circuitry on a wireless NIC (0-255). RSSI is not standard across vendors. Each vendor determines their own RSSI scale/values. AP-to-AP Signal (Neighbor) - Some APs/Controllers have the ability to report the signal strength of APs that they hear. AMP uses these signal strength readings to dynamically attenuate floor plans to increase the accuracy of client locations and heat maps. Unassociated Client Information - Some APs/Controllers have the ability to report the signal strength clients they hear, but that are associated to a radio on a neighboring AP. AMP also uses these signal strength readings to more accurately place clients. 260 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

261 Client Surveys - Client surveys within VisualRF use access points to understand which clients they hear and at what signal strength. Rogue Surveys - Rogue surveys are facilitated by VisualRF and the client's radio to understand which access points they hear and what signal strength. Starting VisualRF In order to launch VisualRF, it must be enabled within OV3600 Setup to display the VisualRF tab, and the VisualRF engine must be switched on in VisualRF > Setup. Both of these pages are visible to logged-in administrators only. By default, VisualRF is disabled in new AMP installations. To enable VisualRF, follow these instructions while logged in as an administrator: 1. Go to AMP Setup > General. 2. Scroll down to the AMP Features section as shown in Figure 192. In the field Display VisualRF, select Yes. Then select Save. Figure 192 AMP Setup > General > AMP Features Page Illustration 3. After the VisualRF tab is visible, navigate to VisualRF > Setup. 4. In the Server Settings section, select Yes in the Enable VisualRF Engine field. Then select Save. Figure 193 VisualRF > Setup > Server Settings Section Basic QuickView Navigation The top-level menus of VisualRF are split into two major categories: Network and Mesh, as shown in Figure 194 and Figure 195. Selecting these menus will cause relevant submenus and sections to display below: Figure 194 Default VisualRF Top Level Menu - Network View Figure 195 Default VisualRF Top Level Menu - Mesh View Table 137 describes the top level icons and their functions on VisualRF. Table 137 Top Level Icons and Descriptions Operation Icon Description Refresh Refresh the floor plan to see changes. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 261

262 Table 137 Top Level Icons and Descriptions (Continued) Operation Icon Description Open Site Tree Preferences Help Display the Network Tree View Window on top of the floor plan. Configure personal viewing preferences. The Preferences menu allows you to configure user preferences (overlay types, grid lines, alerts, icon sizes). See Configuring QuickView Personal Preferences on page 270 for more details. Launch the online help. NOTE: This User Guide currently contains the most up-to-date help information for the VisualRF interface. Network View Navigation When viewing a floor plan in Network View, the top-level menu changes to Overlays, Display, and Edit toggles. Overlays Figure 196 Overlays Menu - Speed selected The Overlays menu contains three common sections: Type, Floors, and Frequencies. Selecting options in these sections can display additional menu sections that affect the data overlays on the floor plan you are viewing. Type section Heatmap - Evaluate coverage based on signal levels by providing the highest dbm (energy level) for all areas of a floor plan. When this option is selected, the Signal Cutoff drop-down menu displays. Speed - Evaluate coverage based on xmit power of client by providing the highest data rate a user will receive for all areas of a floor plan. When this option is selected, the Client Transmit Power dropdown menu displays. Additionally, a Rates interface appears with 54Mbps, 300Mbps, and 450Mbps. Ch. Utilization - View how much airtime is used in the environment. Airtime usage is a good measure of how busy an area is. When you select this option, a new Data Set menu appears where you can select the Current or Maximum Total, Receive, Transmit, or Interference information to display on the Floor Plan. Sensor Coverage - Provides the farthest area which a sensor can hear. When this option is selected, the Client Transmit Power drop-down menu displays. Voice - Provides color-coded overlay based on number of radios covering each grid cell based on the selected signal cutoff. When this option is selected, the Signal Cutoff drop-down menu displays. Wired Range - Displays the distance an Ethernet cable can be pulled from an IDF. The max range is equal to 300 feet minus 5 percent minus 1.1x the floor height. Floors section The Floors section shows the overlay information for adjacent floors to determine how the bleed through from adjacent floors affects the viewed floor. Select all options to see all floors, or one or more of the following options: Above - show the data from APs located on the floor above Current (default) Below - show the data from APs located on the floor below 262 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

263 Frequencies section Select the desired frequency from the following options: 5 GHz (lines are always green) 2.4 GHz (lines are always blue) GHz (lines are yellow) Display Menu Figure 197 Display Menu Device Types section Clients - Turns the display of wireless users on or off. Clients on the floor plan are indicated by the icon. Rogues - Toggle rogue devices on or off. Rogues on the floor plan are indicated by the icon. Tags - Toggle WiFi Tags on or off. Tags on the floor plan are indicated by the icon. Sensors - Toggle sensors on or off. Sensors on the floor plan are indicated by the icon. Interferers - Toggle interferers on or off. Interferers on the floor plan are indicated by the icon. Interferer indicators works for AOS customers running 6.1 or newer that have run the mgmt-server type AMP command, and have APs performing Spectrum analysis through hybrid scanning or dedicated spectrum monitors. Floorplan Features section Regions - Toggle regions on or off. Surveys - Toggle surveys on or off. Walls - Toggle walls on or off. Labels - Toggle labels on or off. Relations section User Association - Toggle line between the wireless user and AP of association. Rogues - Toggle lines between rogue APs and radios which hear the AP. User Neighbors - Toggle lines between client and radios which hear the client excluding the radio of association. APs - Toggle lines between APs which heard each other. Tags - Toggle lines between WiFi Tags and radios which hear the Tags. For Tags there is no radio of association. Wired - Toggle lines between APs/sensors and their IDF. Mesh - Toggle lines between Mesh portals and nodes. Surveys - Toggle lines between client (x,y) to APs by client during survey. Interferers - Toggle lines between interferers and the radios that have discovered them. For interferers, there is no radio of association. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 263

264 Edit Menu Figure 198 Edit Menu Options Options in the Edit menu allow you to add information to the floor plan. Table 138 explains the options in the Edit menu: Table 138 Edit Icons and Descriptions Operation Edit Locked/ Unlocked Description Lock a floor plan for editing. Draw Walls Add walls onto a floor plan. Refer to Adding Exterior Walls on page 272. Draw Region Resize Building Orientation Set Origin Add Deployed Device Add Planned Device Delete Planned Devices/Delete Deployed Device Delete Surveys Add region onto a floor plan. Region types include Planning, IDF, Location Probability, Location Testing and Informational. Update the scale of the floor plan to properly reflect the accurate dimensions of the floor plan. Place the location of two GPS points in order to set latitude and longitude of a building. This will allow VisualRF to calculate the GPS coordinates for APs, clients, rogues, and RFID tags. Set Orientation for proper vertical floor plan alignment. Provision APs onto a floor plan (APs monitored by AMP). Manually plan APs onto a floor plan (APs not monitored by AMP). Remove all specified devices on a floor plan. Remove all surveys (rogue and client) on floor plan. Figure 199 shows additional navigation controls when viewing floor plans. In the bottom left corner of the window is the Search box. In the top right corner is the zoom control. You can also zoom by using Ctrl + your mouse wheel as well as the + and - keys. In the bottom right corner are navigation tools related to network, campus, and building. 264 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

265 Figure 199 On-Screen Navigation Options Mesh View Navigation Mesh view provides a visual Mesh monitoring page specially for viewing Alcatel-Lucent AirMesh devices. It automatically renders Mesh APs based on GPS coordinates. Figure 200 displays an example of a Mesh Network view with a mouseover above a network icon: Figure 200 Viewing Mesh Networks in VisualRF You can mouse over each mesh network icon to view the number of APs, Users, and Bandwidth. Clicking on an AirMesh network will display the APs with labels: OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 265

266 Figure 201 APs in a mesh network Select an AirMesh s AP icon to bring up the popup menu showing the Mesh Node Properties by default. This window shows the node s name, MeshID, MAC, Manufacturer, and other information. Click the blue Monitor link inside this window to be taken to the APs/Devices > Monitor page for more details. Figure 202 Properties for a Mesh Gateway Illustration For radio-level status information on the AirMesh device in your network, select the menus in the AP s popup window for each radio (11na Radio, Access, and so forth). Using the Settings in the VisualRF > Setup Page The VisualRF > Setup page, illustrated in Figure 203, configures advanced settings for VisualRF. Please reconfigure these settings very carefully because these settings can impact your server's performance as well as your location accuracy. Selecting Save will cause VisualRF to restart, disrupting or delaying the usability for up to 5 minutes. 266 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

267 Figure 203 The VisualRF > Setup Page To enable VisualRF and tune memory and performance, navigate to the Server Settings section on this page. The settings in this section are detailed in Table 139: Table 139 Server Settings Section of the VisualRF > Setup Page Setting Default Description Enable VisualRF Engine Enable Multi-floor Bleed-Through Dynamic Attenuation No Yes Yes Enables or disables the VisualRF engine. This setting must be enabled to use VisualRF. If you do not have a license for VisualRF, this page will not appear. Enables or disables calculating the impact APs on floors above and below the currently viewed floor in the Quick View. Incorporate AP to AP readings as well as site survey information and dynamically recalculate the path loss of each radio to every grid cell on the floor plan, increasing coverage and location accuracy. Use Metric Units No Instructs the VisualRF engine to display all units of measurements in metric OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 267

268 Table 139 Server Settings Section of the VisualRF > Setup Page (Continued) Setting Default Description Memory Allocation 512 MB The amount of memory dedicate to VisualRF. It is not dynamically allocated and all the memory is consumed upon starting the service. Be sure to check the memory and swap utilization in the Systems > Performance page before making any changes. The exact amount of memory used per floor plan will vary heavily based on the size, number of devices and number of grid cells on the floor plan. 25 floors or less 512 MB 50 to 75 floors 1 GB 75 to 100 floors 1.5 GB 100 to 200 floors 3GB 200 to 300 floors 5 GB (64-bit only) Above GB (64-bit only) NOTE: If you see Out of Memory errors in the SSL error log on the System > Status page, you should increase memory allocation. Core Threads Location Caching Threads UI Threads Synchronization Timer Restrict visibility of empty floor plans to the role of the user who created them 1x number of cores 1x number of cores 1x number of cores Number of threads that calculate path loss for each floor. These threads also regenerate a floor's RF properties when new APs, walls, or regions are added to a floor plan. Number of threads that calculate the location of all clients associated with access points on this floor plan. Number of threads that service the users accessing QuickView, as well as AMP-to-VisualRF communication. NOTE: If users experience timeout errors while using QuickView, allocate additional UI Threads. 15 minutes This timer indicates how often VisualRF will synchronize security for APs within AMP. No When enabled, only the creator can view an empty floor plan. To tune location accuracy, go to the Location Settings section on this page as described in Table 140: Table 140 Location Settings Section in VisualRF > Setup Setting Default Description Allowed deviation for client placement 4 db When VisualRF locates a client or rogue it utilizes signal metrics from all the APs that hear the client or rogue device. VisualRF builds a fingerprint location for all clients with similar transmit-power capability. All subsequent clients that fall within the deviation is placed on the same location fingerprint or x, y coordinates. Example: AP #1 hears client1 at -72, and AP #2 hears client 1 at -64. VisualRF calculates the client's location to be at coordinates 100, 200. Client2 is heard by AP#1 at -71 and AP#2 at -65. VisualRF will use the average of the difference in signals (AP#1-72 and -71) to see if the client matches a pre-calculated location fingerprint (differences in signals) / 2 (# of APs) = 1 which falls within the deviation of 2, hence the client would be located at 100,200. Maximum Rogue APs per Floor Plan 20 Sets the maximum number of rogues AMP will place on a Floor. Use this filter in combination with the RAPIDS Export Threshold configured on the RAPIDS > Setup page to intelligently control the number of rogue devices displayed per floor. NOTE: Increasing this value could increase the load on the server and the clutter on the screen. 268 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

269 To tune the frequency for calculating device locations within the VisualRF UI, navigate to the Location Calculation Timer Settings section as described in Table 142: Table 141 Location Calculation Timer Settings Section of VisualRF > Setup Setting Default Description Legacy Laptop Min/ Max (sec) 90/360 This timer determines how often to calculate location for legacy laptop devices. Taken with the data samples the calculation would follow: After minimum timer (90 seconds) check to see if the number of data samples received from all APs that hear this client are greater than or equal to the number of samples setting for legacy laptop devices (default of 3 data samples). If so (Yes to question above) then recalculate the client device's location based on the samples received. If not (No to the question above) then wait until the number of sample setting is met and recalculate. If the number of samples is never met, wait until the maximum timer (360 seconds) and recalculate. Legacy Laptop Number of Samples 3 See definition above. All of the other device types (phone, printer, scale, and so on) use the same methodology as detailed above. To edit the wall settings and select a color for wall types within the VisualRF UI, navigate to the Wall Attenuation Settings section and select the pencil icon next to each of these settings as described in Table 142: Table 142 Wall Attenuation Settings in VisualRF > Setup Setting Default Description Glass Attenuation (db) 2 Specifies the attenuation for any glass walls that are drawn in VisualRF. NOTE: All of these values are global variables that cannot be overridden for individual floor plans. VisualRF uses these values to calculate path loss and client locations. Walls within VisualRF are interpreted as pure db loss without adjusting for wall thickness. Cubicle Attenuation (db) 4 Specifies the attenuation for any cubicle walls drawn in VisualRF. Drywall Attenuation (db) 6 Specifies the attenuation for any drywall walls drawn in VisualRF. Concrete Attenuation (db) 15 Specifies the attenuation for any concrete walls drawn in VisualRF. VisualRF Resource Utilization When tuning the VisualRF server, use the default settings as recommended. If you do change any of these settings above, change one at a time and see how the system performs. Each time you restart VisualRF, it will take at least 30 minutes to return to normal processing. If you use the 'top' command to check on VisualRF resource utilization, ensure you use the '1' and 'H' flags to show cores and threads. Remember 'top' also takes 1-2 minutes to normalize and provide accurate data. It is normal for VisualRF to consume 20% of each core with a combination of threads. It will utilize excess CPU cycles on all cores when required. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 269

270 Configuring QuickView Personal Preferences To configure your personal preferences in QuickView, select the Preferences icon and choose from the following configuration options: General - select from the Configure Preferences drop-down menu, as shown in Figure 204: Enable auto-refresh toggle Refresh Interval in minutes Show Scale Hide neighbor lines ignored in location calculation High Quality Background Image - you can disable to increase rendering speed Label Transparency Figure 204 QuickView Preferences Page Illustration (General preferences selected) APs - select from the Configure Preferences drop-down menu: BW - select the kbps threshold for normal (green), high (yellow), and excessive (red) # of Users - select the number of users threshold for normal (green), high (yellow), and excessive (red) % of Uptime for the last 24 hours for normal (green) and excessive (red) Radio Status - display red or green depending on the status of the radios within the AP AP Status - display red or green in relation to up/down status of AP Icon Size - select the size of the AP icon display on the floor plan Show Channel in Label Show Transmit Power in Label Users - select from the Configure Preferences drop-down menu: BW - select the kbps threshold for normal (green), high (yellow), and excessive (red). Signal Strength - select the dbm client threshold between excellent and poor Icon Size - select the size of the client device icon display on the floor plan Overlays - select display type for Heatmaps, Speed, Sensor, Voice, and Ch. Utilization Grid - non vector overlay Vector - provides a more smooth overlay with mouse-over capabilities Grid Lines - Toggle grid lines on or off Distance between grid lines Color of grid lines 270 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

271 Navigation - select from the Configure Preferences drop-down menu (campus and buildings): % of APs Up for the last 24 hours for normal (green) and excessive (red) Icon Size for campus, building and floor These preferences are stored in the database, so they will be retained across browsers and machines. The remaining sections in this chapter apply to networks, campuses, buildings, and floor plans that have already been set up in VisualRF. If you do not yet have any of this information in VisualRF for your network, refer to Planning and Provisioning on page 283. Increasing Location Accuracy The Location Service will use all RF information available to increase location accuracy of clients, tags, and rogue devices. Understanding your infrastructure's inherent capabilities helps you learn the extra effort required to ensure location accuracy. There are three key elements read from controllers or access points that increase location accuracy: signal strength of a client as heard by the AP of association, signal strength of a client as heard by APs other than the AP of association, and signal strength at which an AP hears other APs. These factors are detailed further in Table 143: Table 143 Elements Read From Controllers to Increase Location Accuracy MFG/Model Client Signal Associated AP AP-to-AP Signals (Dynamic Attenuation) Unassociated Client Signal Rogue AP Signal Alcatel-Lucent Yes Yes Yes Yes Cisco LWAPP Yes Yes Yes Yes Cisco IOS Yes No No With WLSE Cisco VxWorks Yes No No No Trapeze Yes No No Yes Meru No No No Yes Proxim Yes Yes Yes Yes Symbol Auton. AP Yes No No Yes Symbol Thin AP Yes No Yes Yes Proxim AP-2000 Yes No Yes Yes Proxim AP-4000 Yes Yes Yes Yes ProCurve WeSM Yes Yes No Yes ProCurve 530 Yes Yes Yes Yes ProCurve 420 Yes Yes No Yes OV3600 provides four main methods to increase accuracy once your access points are deployed: Adding Exterior Walls - increases location accuracy by reducing the statistical probability of placements outside the office confines. See Adding Exterior Walls on page 272. Client Training for Stationary Devices - ensures non-mobile clients like desktops or scales will always remain in a defined static location. Statically assigning non-mobile devices reduces the CPU load on OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 271

272 your server because VisualRF does not evaluate any signal metrics for this MAC address when associated with an AP on the floor plan. See Location Training for Stationary Devices on page 272. Remote Client Surveys - provides additional attenuation inputs for corners and low-coverage areas without the burden of actually carrying a laptop to the physical location. See Adding Client Surveys on page 273. Location Probability Regions - Probability regions will increase or decrease the chances of a device being located within the region. See Adding Location Probability Regions on page 274. Adding Exterior Walls Because VisualRF utilizes much existing RF information, generally only external walls are required for accurate client locations. VisualRF's Dynamic Attenuation feature uses AP-to-AP information to calculate attenuation for interior areas, negating the need to enter interior walls. If your devices support AP-to-AP information in the table above, you should only draw exterior walls. 1. Select Draw Walls icon in the Edit menu. 2. The cursor changes to a crosshair. Use this to draw the wall directly over the floor plan, as shown in Figure 205: Figure 205 Drawing a wall 3. To move or resize the wall, select the Wall icon in the Edit menu again. The cursor changes to a hand, and the ends of the wall is highlighted. Click and drag the end point handles to change the wall, as shown in Figure 206: Figure 206 Moving and resizing an existing wall To change the attenuation of a wall, right-click the wall and select the appropriate building material. To delete a wall, select the wall and press the Delete key. 4. Once all walls are provisioned on the floor plan, select Save (floppy disk icon above the zoom bar). Drawing only outside walls is recommended. If you are seeing inaccurate client locations or heat maps after entering exterior walls, proceed to Client Surveys. If you still experience problems, then you can proceed to adding interior walls. Location Training for Stationary Devices QuickView provides the ability to statically assign a permanent x, y coordinate to stationary devices like PCs, Scales, and Point-of-Sale terminals. This will reduce the calculation requirements on the VisualRF location service and increase the accuracy of the RF characteristics of individual floor plans. 1. Drag the client device to the proper location. 2. Select the device and a popup menu appears. From that menu, select Surveys and Training. 3. Click the Add button for Static Training, as shown in Figure 207: 272 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

273 Figure 207 Surveys and Training menu for a client device To remove a statically trained device, select client, and select the Surveys and Training option. Select Delete button (which will have replaced the Add button) for Static Training. The static locations are automatically saved, so the Save icon (floppy disk) will not appear. Adding Client Surveys Client surveys provide a method for increasing the accuracy of the attenuation grid by taking real signal samplings from client devices associated with the WLAN. Key differentiators of AMP s client surveys are: 1. They take readings from the access points and not the client. 2. They take numerous samples. This produces a more accurate representation because signals obtained from the client's card (the signal level at which a client hears the AP) can vary from vendor to vendor. The signal levels at which APs can hear a client are already normalized. Using multiple samples alleviates spikes or troughs that come from using a single sample. To start a client survey, follow these steps: 1. Drag the client to the proper location. 2. Select the client to see the Properties pop-up menu, as shown in Figure 208: Figure 208 Client Surveys 3. Select the Surveys and Training option. 4. Select the appropriate transmit power for the wireless client. Leave the default to 30mW if you are unsure. 5. Select the Duration or the time that you want to sample the client's signal measurements. Longer durations will increase Path Loss accuracy and location accuracy. 6. Select OK to begin the survey. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 273

274 To display survey locations, select the Display menu and select Surveys. Note the following information about this procedure: Ensure the client will remain in the same location for at least the duration of the survey. You should delete and resurvey an area or a floor plan after a remodel or significant interior movement. Surveys should be conducted during normal business hours to reflect normal RF activity on the floor. 11a clients automatically inherit the proper transmit power from the 11g configuration. Example: 30mW Pre-2006 laptops equate to 20mW for 11a clients. AMP dynamically assigns a transmit power to every client based on OUI as shown in Table 144. This step increases the accuracy for surveys by allowing an override. Table 144 Auto-assigned Client Type and Transmit Power Client Type Pre-2006 Laptops Post Laptops SOHO WLAN Cards (D-Link, Net Gear, LINKSYS) RFID Tags PDA iphone Desktop Cisco Cards Transmit Power 11g 30 mw 100 mw 30 mw 10 mw 20 mw 20 mw 100 mw 100 mw Adding Location Probability Regions Location probability regions are optional regions that can be used to increase the accuracy of device location in VisualRF. VisualRF calculates device locations based on probability. VisualRF determines the probability of a device being located in every grid cell and places the device where the probability is the highest. Probability regions will add or remove up to 20% chance from the device location probability. They can be used to push users into regions where they are more likely to be located, like conference rooms and cubical farms, or they can be used to pull users out of regions where they are less likely to be like parking lots and courtyards. To add a probability region to a floor plan, follow these steps: 1. Select the Edit menu and click the Draw Region option. 2. Outline the desired probability region. Double click to end the outline process. 3. Name the region, select a Region Type of Location Probability and select OK. 4. Move the location probability slider to the desired level, as shown on Figure 209. Very Low will decrease the probability of a device being placed in that region by 20%. Very High will increase the probability of a device being placed in that region by 20%. 274 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

275 Figure 209 Adding a New Location Probability Region 5. Optionally, you can save the location region as the exterior walls. 100% attenuation can be selected to force VisualRF to only place devices inside of the selected region. No device will ever be placed outside of the probability region when 100% attenuation is selected. 100% attenuation is only recommended for tall buildings where it is extremely unlikely that any user is located outside of the building. No heat map or attenuation grid is calculated for devices outside of the 100% attenuation region. Adding an IDF To add an IDF to VisualRF, follow these steps: 1. In the Edit menu, select the Draw Region option. 2. Outline the desired IDF region. Double-click to end the outline process. 3. Name the region, select a Region Type of IDF, and select OK, as shown in Figure 210. Figure 210 Adding a new IDF Region Now that the IDF is defined you will see a green IDF icon on your floor plan. Double click that icon to navigate into the IDF. 1. Add a rack to the IDF by selecting the Add Empty Rack icon and dragging it to the background. 2. To add a planned device, select the Add Planned Device icon to view the Manually Provision Rack Gear menu. Select the device type in the Type menu, and then find the device you want to add. Drag it into the rack at the appropriate location. 3. To add a wired device that is currently being monitored by AMP, select Add Deployed Device. 4. Locate the device to be added. 5. Drag the device to the appropriate location in the rack, as shown in Figure 211. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 275

276 Figure 211 Provisioning Devices Wired devices that are added to an IDF are included in any BOM report covering that floor. Viewing Port Status on Deployed Switches Deployed switches on a rack will display the port status as red (down) and green (up) interface icons, which corresponds with the operationally up devices on the APs/Devices > Interfaces list. Planned switches do not display these status indicators in VisualRF. Figure 212 Deployed switch showing red and green port status icons Fine-Tuning Location Service in VisualRF > Setup There are several options on the VisualRF > Setup page which increase client location accuracy. All of these items will increase the processing requirements for the location service and could negatively impact the overall performance of AMP. 276 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

277 Grid Size - decreasing the grid size will enable the location to place clients in a small grid which will increase accuracy. You can right-click on a floor plan within a building view and change this setting. Dynamic Attenuation - enabling dynamic attenuation (which is on by default) instructs the location service to sample the current RF environment and to dynamically adjust Path Loss. Configuring Infrastructure Ensure that the hardware is configured to retrieve the RF information and that it provides this information on a timely basis. There are three unique timing mechanisms which impact location accuracy: how often the infrastructure collects and correlates RF statistics in their MIB, how often the AMP queries those MIB entries, and how often VisualRF service queries AMP for this RF information. Figure 213 Timing Factors Impacting Location Accuracy These best practices are recommended when configuring hardware infrastructure: For legacy autonomous APs, ensure on the Group > Radio page that Rogue Scanning is enabled and the interval is accurate, as shown in Figure 214: Figure 214 Group Rogue Scanning Configuration For thin APs, ensure that the controllers are configured to gather RF information from the thin APs frequently. For Cisco LWAPP, navigate to Groups > Cisco WLC Config page in AMP. Navigate the tree control to the Wireless section, and for each PHY navigate to RRM > General section. Figure 215 WLC RRM Configuration in AMP Review the values in the Monitor Intervals section. These should be configured to a recommended setting of 180 for better accuracy. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 277

278 Deploying APs for Client Location Accuracy Deploying access points for client location accuracy can be different than deploying access points for capacity. Follow these guidelines for best results: Ensure that at least 3 radios can hear each client devices at -85 dbm or below Ensure that you deploy an access point approximately every 3,500 square feet. For square or rectangular floor plans ensure access points are deployed on the exterior walls of each floor with access points in the middle as well. Refer to Figure 216 for an example. Figure 216 Rectangular Floor Plan AP Deployment Using QuickView to Assess RF Environments QuickView has four distinct views or entry points: client view, access point view, floor plan view, and network, campus, and building view. This section contains the following corresponding topics: Viewing a Wireless User's RF Environment on page 278 Viewing an AP s Wireless RF Environment on page 280 Viewing a Floor Plan s RF Environment on page 281 Viewing a Network, Campus, Building s RF Environment on page 282 Viewing a Wireless User's RF Environment 1. Navigate to Users > List in AMP. 2. Click the link under the Location column for the user of interest, as shown in Figure 217. A QuickView window of that location opens and indicates the client with a Username label, as shown in Figure 218: Figure 217 Link to user s thumbnail (the Location column) 278 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

279 Figure 218 QuickView of the selected device You can also access this information from the Clients > Client Detail page by selecting the QuickView thumbnail, located next to the Current Association section of this page as shown in Figure 219: Figure 219 QuickView thumbnail in Clients > Client Detail This view is focused on the wireless user enabling you quick resolution of a user's issues and therefore disables most RF objects by default. Users - only the user in focus is displayed APs - only the access point in which the focus client is associated with is displayed Radios - the heatmap represents only the radio to which the client in focus is associated Rogues - all rogues are off Client/Rogue Surveys - all surveys are off Walls - all walls are displayed Lines - client to AP of association Labels - all labels are disabled Tracking Location History Select a client icon in the Floor Plan and select Display from the pop-up menu shown in Figure 220: Figure 220 Show Location History A location history player, illustrated in Figure 221, appears at the bottom of the QuickView window. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 279

280 Figure 221 Location History Player Checking Signal Strength to Client Location 1. On a Floor Plan, locate the Signal Cutoff menu. 2. Select the desired signal level to display, as shown in Figure 222. The heatmap updates immediately. Figure 222 Signal Cutoff dbm Dropdown Menu Viewing an AP s Wireless RF Environment To view an access point's RF environment from APs/Devices > Monitor page: 1. Select a device of interest from APs/Devices > List, or any other AMP page that lists your APs. The APs/Devices > Monitor page opens. 2. Click on the QuickView thumbnail showing the location of the AP, shown on the right side of Figure 223: Figure 223 QuickView Thumbnail in APs/Devices > Monitor page for an AP A fully interactive QuickView display opens below the thumbnail on the same page (not in a new window), as shown in Figure 224: 280 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

281 Figure 224 Full QuickView in APs/Devices > Monitor page for an AP (partial view) This view is focused on enabling quick resolution of AP issues and therefore disables many RF objects by default as follows: Users - only users associated with radios within access point of focus are displayed APs - only the access point in focus is displayed Radios - the heatmap represents all radios within the access point of focus Rogues - all rogues are off Client/Rogue Surveys - all surveys are off Walls - all walls on displayed Lines - client to AP of association are displayed Labels - all labels are disabled Viewing a Floor Plan s RF Environment View a floor plan's RF environment from VisualRF > Floor Plans page. This page has a fixed sorting filter of Campus > Building > Floor number. Figure 225 Floor Plans List View OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 281

282 The VisualRF > Floor Plans page provides a snapshot of how VisualRF is performing, as described in Table 145: Table 145 Floor Plans list columns Field Description Campus Building Floor Name Size Grid Cell Size Campus associated to the floor. Building associated to the floor. Floor number. The decimal place can be used for mezzanine levels. Optional name of a floor. (If the name is not changed, it displays the name as Floor [Number] by default.) The height and width in feet of the floor plan, including white space. The size of the grid cells, in feet. # of APs The number of access points on the floor. # of Radios The number of radios associated with access points on the floor # of Users The number of wireless users associated with access points on the floor. NOTE: Locating users consumes significant VisualRF resources. A floor with hundreds or thousands of clients can take a long time to process. # of Rogues The number of rogue devices heard by access points on the floor. This number reflects the filters configured on the VisualRF > Setup. This means that while APs on the floor might hear more rogue devices, they are being filtered because of weak signal, they haven't been heard recently, or they are ad-hoc. File Size Original Floor Plan The floor plan background or image reported, in kilobytes. The larger the file, the longer it will take to render in the canvas. A link to download the original image background file. Viewing a Network, Campus, Building s RF Environment To view floors from a geographical perspective: 1. Navigate to the VisualRF > Floor Plans page. 2. Click on each network, campus, or building successively to drill down further until you reach the floor plan. This navigation provides information in each view as follows: Network View - Contains all campuses within your WLAN Campus View - All buildings within a campus Building View - All floors within a building Floor Plan View - All devices access points, clients, and rogues within the floor Viewing Campuses, Buildings, or Floors from a Tree View As an alternative to using QuickView, you can use the Tree View to view floors from a hierarchical tree, as follows: 1. Navigate to the VisualRF > Floor Plans page. 2. Select the Tree icon ( )at the top right of any view. The Network Tree View window, shown in Figure 226, appears on the screen. 282 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

283 Figure 226 Network Tree View - Floor highlighted 3. Use the arrows to drill down into the folders to select the Campus, Building, or Floor. Select the folder or floor plan icon to open the view you have selected. The Network Tree View window will remain on the screen until you close it. If you prefer not to use background maps for your campus or building placements, click a background and select Auto-Arrange to move the campuses, buildings from their placements into an alphabetically-sorted list. Planning and Provisioning VisualRF provides the capability to plan campuses, buildings, floors, and access points prior to the actual access point deployment. The following procedure describes the workflow: Creating a New Campus on page 283 Creating a New Building in a Campus on page 284 Importing a Floor Plan on page 285 Editing a Floor Plan Image on page 286 Provisioning Existing Access Points onto the Floor Plan on page 289 Automatically Provisioning APs onto a Floor Plan on page 290 Tweaking a Planning Region on page 291 Printing a Bill of Materials Report on page 292 Creating a New Campus Floors are associated with a building and buildings are associated with a campus. In order to create a new floor, you must first create a campus and building. To create and place your campus, follow these steps: 1. Navigate to VisualRF > Floor Plans. 2. Select the Add Campus button, located above the floor plan on the top left. The Create New Campus window, illustrated in Figure 227, appears. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 283

284 3. Enter the following campus information: Name of the campus Client Transmit Power - used in auto placement of access points onto floors within this campus. The range is 30mW to 100mW. Desired Speed (mbps)- used in auto placement of access points onto floors within this campus. The range is 6 to 200 mbps. Buildings and floors inherit transmit power and speed from the campus. Figure 227 Create New Campus window 4. Select OK to save. You will see a new Campus icon appear on the campus canvas. 5. Add appropriate network geographical background or upload a personalized image by right-clicking on the background. Set Map - Allows you to browse with the included maps. Auto Arrange Campuses -Arranges the campus in alphabetical order across the background. 6. Drag the new Campus icon to the appropriate location on the map background. QuickView automatically saves background map images, campus locations, building locations, and building types Creating a New Building in a Campus 1. Select the newly created Campus icon from the previous step. When the blank campus area opens, select the Add New Building icon. 2. When the New Building window appears, enter the following information: Table 146 New Building Fields and Descriptions Field Name Campus Longitude & Latitude Distance between floors Attenuation between floors Description Name of the building; located on an existing campus. Lists all campuses configured on your AMP. These fields are used to represent a building on Google Earth. The normal distance between floors in the building. This value can be overridden as each floor is created, but this is the default value for every new floor added to the system. This data element can be imported or exported to external planning tools like Ekahau. It is not currently utilized by OV3600. Enter the attenuation loss in decibels between floors. This value can be overridden as each floor is created, but this is the default value for every new floor added to the system. This data element can be imported or exported to external planning tools like Ekahau. It is not currently utilized by OV Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

285 Table 146 New Building Fields and Descriptions (Continued) Field Client Transmit Power Desired Speed Address Description This value is used when auto-provisioning access points onto a floor plan. Speed will determine the new access points when auto-provisioning. Building or Campus address (optional) Figure 228 Create New Building Window 3. Select OK to save. A new Building icon will appear in the middle of the canvas. 4. Drag the Building icon to the appropriate location on the map background. QuickView automatically saves background map images, campus locations, building locations, and building types. 5. Add appropriate geographical background or upload a personalized image by right-clicking on the background. Set Map - allows you to browse with the included maps. Custom - launches the image upload wizard documented in Importing a Floor Plan on page To change building types, right-click the Building icon. 7. Select proper building type. 8. Select the newly created Building icon from the previous step. You are redirected to a blank canvas without a background. You are now ready to import your floor plan. Importing a Floor Plan The following steps show how to import a floor plan background image file. 1. In VisualRF > Floor Plans, click the Add Floorplan icon (displays when viewing a Building) or use the Add button above the floor plan list at the bottom of the page. 2. Select Choose File to locate a floor plan image file from your hard drive. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 285

286 3. In VisualRF, select Upload. This opens the image file along with VisualRF planning tools on the left side. Figure 229 Floor Plan Imported into VisualRF If the floor plan does not require cropping, sizing, or layer control, then click Save and Close to begin provisioning APs or Save and New to upload a new floor plan. If the floor plan does require cropping, sizing, or layer control, then proceed to the next procedure. Editing a Floor Plan Image There are many ways to edit a floor plan that you have uploaded, as explained in the following topics: Cropping the Floor Plan Image on page 286 Sizing a Non-CAD Floor Plan on page 287 Removing Color from a Floor Plan Image on page 287 Assigning Campus, Building and Floor Numbers on page 288 Assigning Optional Planner, Owner, or Installer Information for the Floor Plan on page 288 Controlling the Layers in the Uploaded Floor Plan (CAD only) on page 288 Error Checking of CAD Images on page 288 Last Steps in Editing an Uploaded Image on page 289 Cropping the Floor Plan Image Use the cropping handles (red circles) to remove extra white space around the floor plan. VisualRF will calculate an attenuation grid for the entire map including white space. Reducing the white space on a floor plan will increase location accuracy and decrease the load an on the server. A good rule of thumb would be about ½ inch white space, if possible, on all sides. VisualRF dissects each floor plan into a grid consisting of cells specified in this setting. The Core Thread service calculates the path loss for every radio to every cell on the floor plan. 286 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

287 By default the importation wizard allocates 2,500 grid cells to each site based on dimensions. If you have a site that is 250 ft. by 100 ft, the Floor Plan importation wizard would calculate the grid cell size at 10 feet. 250 ft. x 100 ft. = 25,000 ft. 25,000 ft. / 2,500 ft. = 10 ft. Decreasing the grid cell size will increase accuracy, but it also increase CPU consumption by the floor caching threads and the location caching threads. Check the System ' Performance page to ensure your server is functioning properly when you make a change to this setting. Other items worth noting: If this is a CAD file, then the Floor Plan creation wizard will automatically inherit height and width from the drawing. If this is a non-cad file, then the height and width is zero. CAD files are converted to a JPG with a resolution of 4096 horizontal pixels at 100% quality prior to cropping. If you crop, then you will lose clarity. CAD files may not exceed 10 MB. Metric CAD files are supported. Importing GIF files for floor plans will result in blank QuickView thumbnails. Sizing a Non-CAD Floor Plan You should not have to resize a CAD drawing unless you see nonsensical dimensions. To resize a non-cad image if you already know the dimensions, follow these steps: 1. Select the Manually Measure Floor button in the Dimensions section. The pointer changes to a crosshair icon. 2. Locate two points within the floor plan that you know the distance. Most door jams (door openings) are 3 feet. 3. Select and hold to establish the first point and drag your mouse to the second point and release. 4. A distance dialogue box appears. Enter the proper length in feet, as shown in Figure 230. Figure 230 Manually Measuring a Floor Plan 5. Select OK. Floor plans can be resized in VisualRF after they have been uploaded. Within VisualRF you will also be able to zoom in on a room or doorway to increase the accuracy of your sizing. Removing Color from a Floor Plan Image To remove color, locate the Image Manipulation section and select B&W in the Image field. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 287

288 Assigning Campus, Building and Floor Numbers Locate the Floor Info Section and assign the following information, as detailed in Table 147 and illustrated in Figure 231: Table 147 Assigning numbers Setting Default Description Building dropdown N/A Figure 231 Entering Floor Info for the Uploaded Floor Plan Image Use this drop-down to associate the floor with a building which associate it to a Campus as well. Floor Number 0.0 The floor number. You can enter negative numbers for basements. NOTE: Each floor plan within a building must have a unique floor number. Floor Name Floor [Number] A descriptive name for the floor. It inherits the floor number as a name if nothing is entered. Ceiling Height 10 Specifies the height from the floor to the ceiling. This will default to the ceiling height for the building, but you can override here if needed for atria or basements. Ceiling Attenuation 20 Specifies the attenuation characteristics in db of the ceiling or the floor above. Assigning Optional Planner, Owner, or Installer Information for the Floor Plan Locate the Optional Information section and enter the following information in Table 148: Table 148 Optional Information for the Floor Plan Setting Default Description Owner N/A The owner of the floor (used in diagnostics and alerts). Planner N/A The person in charge of planning the RF layout for the floor. Installer N/A The person in charge of installing RF equipment for the floor. Controlling the Layers in the Uploaded Floor Plan (CAD only) Follow these steps for CAD images: 1. Find the CAD Layers section on the page. 2. Unselect the layers which are not required. There is slight delay because each request makes a round trip to the server. Error Checking of CAD Images VisualRF will check for errors in your uploaded CAD image. You can view any issues as follows: 1. Locate the CAD Info section, as shown in Figure Review the CAD version, units of measurement, and raw width and height numbers. 288 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

289 Figure 232 Checking for CAD errors Last Steps in Editing an Uploaded Image Click the Save and Close button to begin provisioning APs or Save and New to upload another floor plan. After clicking Save and Close, you is redirected back into QuickView where you can provision APs, IDFs, and wired infrastructure. Provisioning Existing Access Points onto the Floor Plan To provision existing AP in your network onto the floor plan you just uploaded, follow these steps: 1. Navigate to VisualRF > Floor Plans. 2. Select the floor plan you have uploaded using the floor number or name links in the list. 3. Select the Add Deployed Device icon in the Edit menu. A pop-up window list of devices in your OV3600 appears, as shown on Select whether to navigate by Group or by Folder in the View By field. Alternatively, you can use the Search field. 5. Expand the Group or Folder containing the access points which need to be provisioned on this floor plan. Note that by default, devices that have already been added to VisualRF are hidden. To show them, clear the Hide Devices already added to VisualRF checkbox at the bottom of the list. 6. Click and drag an AP to its proper location on the floor, as shown in Figure 233: Figure 233 Provisioning APs onto the Floor Plan OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 289

290 7. Once all APs are provisioned on the floor plan, select Save (floppy disk icon) in the top right of the QuickView window. The floor is submitted to one of the core threads to recalculate path loss and then to one of the location caching threads to recalculate client locations. All changes may not be visible on a refresh until this process complete. Automatically Provisioning APs onto a Floor Plan To automatically provision your access points onto your floor plan: 1. Select Draw Region from the Edit menu. A new provisioning popup appears as shown in 4. with a crosshair pointer. Figure 234 Planning Region Drawing and Selection Illustration 2. Draw your polygon as follows: Left-click to initiate the process. The tool will automatically shade in your provisioning area. Complete the polygon by double-clicking. 3. Once you have finished drawing the region, enter a name for the region and select a Region Type of Planning. Then select OK. 4. Enter the following information into the Autoprovision APs window as described in Table 149 and illustrated in Figure 235: Table 149 Fields in the Autoprovision APs Window Field Description Device Selection AP Type The type of AP used in this planning region. Radio Section Phy Xmit Gain EIRP Whether they PHY is set to 11n or no radio. Transmit power of the APs. Gain of the APs. EIRP of the APs. 290 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

291 Table 149 Fields in the Autoprovision APs Window (Continued) Field Environment Description A range from 1-4 that best describes whether the environment is related to an office space, cubicles, offices, or concrete. Decimal points are allowed. Plan By Section Coverage Location Number of APs Plan Coverage by Speed or Signal. Plan for location accuracy. This mode will result in additional APs placed near the edge of the region to aid in location calculation. Number of APs to place in the planning region. Client Info Section Enable Total clients in region Max clients per radio Whether to enable planning by user capacity. Set the anticipated number of clients that will be stationed in a region. The maximum number of clients supported by each radio. Other Section Plan Sensors Save Region as Walls Update Environment and Data Rate Whether to plan sensors into the region. Whether to save the edges of the planning region as walls. Whether to update the environment and data rate in case of changes. Figure 235 Autoprovision APs Window Illustration 5. When you re finished selecting the desired options, select OK. Tweaking a Planning Region If the planning layout does not meet your expectations, you can edit by right-clicking within the region to see the following options: Delete Planned APs in the Region - Deletes only provisioned APs in the region Reprovision APs - Remove all planned APs inside this region and prompts for new information to replan the region OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 291

292 Delete the Region - Deletes the region and all planned APs Edit the region - Change the name of the region Copy the Region to floors above - Will copy the region and auto plan for floors above. The starting floor will add one to the highest floor in the building and the ending floor defaults to 10 more than the starting floor. To replicate a floor plan, follow these steps: 1. Navigate back to the Building view by clicking on the navigation tags in the bottom-right corner of the window. 2. Right-click the floor and select Duplicate. 3. Enter the following information: Starting and ending floors Select the toggles to copy walls, regions, data rates (speeds), and AP placement The starting floor will add one to the highest floor in the building and the ending floor defaults to 10 more than the starting floor. 4. Select OK to save your changes. 5. Manually refresh page and your is redirected to the VisualRF > Floor Plan page. The Building view will reflect the new floors. You should see all replicate floors with matching number of access points. Auto-Matching Planned Devices You can right-click a campus, building, or network icon and select the Auto-Match Planned Devices option to efficiently match planned APs to managed APs. If you select this option for a campus, then all planned APs in that campus are checked. If used on a building, then all the APs in that building are checked. If used on a floor, then all APs on that floor are checked. Planned devices first attempt to auto-match on MAC address, and then by name. The VisualRF MAC address checks against all of the LAN MAC addresses of a deployed AP. Printing a Bill of Materials Report You can generate a Bill of Materials (BOM) Report from within VisualRF in Word format. Follow these steps: 1. Navigate back to the Network view. 2. Right select Campus icon and select Show Bill of Materials. A generating report popup appears. 3. Select options such as heatmap, speed, sensor coverage, wired range, and summary. 4. Select OK. A BOM report appears in Microsoft Word as illustrated in Figure 236: 292 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

293 Figure 236 Bill of Materials Report Illustration Importing and Exporting in VisualRF Exporting a campus To export a campus from VisualRF so you can import it into another AMP, follow these steps: 1. Navigate back to the Network view. 2. Right-click the Campus icon. 3. Select Export. An object selection window appears. 4. Select the objects to export and select Export. A File Download window appears. 5. Select Save and save the zipped file to your local hard drive for importation to another AMP. At this point, you are ready to deploy a production AMP and manage devices by importing your exported campus and matching the access points to your plan. Importing from CAD The Floor Plan Upload Wizard (FUW) should inherit all pertinent information from your CAD file if you follow this procedure: 1. Determine UNITS - all modern CAD versions (2001 and newer) support UNITS 2. Determine MEASURE - Legacy CAD versions (2000 and older) used a Imperial or Metric system. If UNITS are 0 or undefined, then the standard dictates defaulting to MEASURE value If MEASURE is 0 or undefined, then the standard dictates defaulting to English and inches 3. Find MODEL VIEW - If the drawing contains multiple views the FUW will default to the Model view 4. Determine Bounding Box - FUW will encompass all lines and symbols on the drawing and create a bounding box which is generally smaller than entire drawing. It is based on the UNITS or MEASUREMENT above. 5. Convert to JPG - FUW will convert the bounding box area to a JPG file with a resolution of 4096 horizontal pixels at 100% quality. 6. Start Web UI of FUW Step #1 - This is the cropping step. This and all subsequent steps use the converted JPG file. The greater the floor plan dimensions, the less clarity the background image provides. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 293

294 Batch Importing CAD Files This process provides the ability to automatically upload many CAD files and auto provision existing walls and access points, and contains the following topics: Requirements on page 294 Pre Processing Steps on page 294 Upload Processing Steps on page 294 Post Processing Steps on page 295 Sample Upload Instruction XML File on page 295 Common Importation Problems on page 295 Requirements Operating System: Client machine must be Windows XP, Windows Vista, or Windows 7 Flash: Version 9 or later Pre Processing Steps 1. Increase Memory Allocation in VisualRF > Setup as follows: 25 floors or less MB 25 to 75 floors - 1 GB More than 75 floors GB 2. Massage the output data. 3. Increase the Location Caching Timer to 1 hour so that VisualRF does not overload the server calculating client locations while calculating path loss and process floor plan images. Upload Processing Steps 1. Create CAD XML files which contain drawing filename, dimensions and optional information like device manufacture and model, device coordinates, wall coordinates and building material. This step is usually performed by your facilities or CAD department. The output of AutoCAD will not be properly formed XML, so you may need to massage the output data. 2. Copy all CAD drawings and corresponding XML files into a single directory on Windows machine. All files must be in a single directory. 3. Compress all files into a single *.zip file. 4. Open your browser and navigate to your AMP: 5. Select Browse to launch the File Explorer Window. 6. Select the zip file containing the upload instructions and click the Open button. The File Explorer Window will disappear you will return to the Batch Floor Upload Wizard. 7. Select Next. 8. The application validates the following information Well-formed XML All drawing files are accessible All APs are present All Building and Campuses are present 9. If there are any errors, none of the floor plans are created. 294 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

295 Post Processing Steps 1. Decrease the Location Caching Timer to previous value. 2. Review the VisualRF > Floor Plans page to ensure server is keeping up. Sample Upload Instruction XML File <?xml version='1.0' encoding='iso '?> <visualrf:site_batch xmlns:visualrf=' xmlns:xsi=' version='1' origin='lower-left'> <floor name='t-0607' number='21' building-id='218'> <image filename='t-0607_wls_02.dwg'/> <access-points> <access-point id=29648 x= y=293.15/> <access-point id=29678 x= y=293.63/> <access-point id=29748 x= y=432.62/> </access-points> <walls> <wall type=4 x1= y1= x2= y2=453.16/> <wall type=4 x1= y1= x2= y2=453.16/> <wall type=4 x1= y1= x2= y2=418.16/> </walls> </floor> <floor name='t-0068' number='22' building-id='218'> <image filename='t-0068_wls_01.dwg'/> </floor> <floor name='test JPG' number='23' building-id='218' width='523.34' height='231.34'> <image filename='f1wst IT_dwg.jpg'/> </floor> </visualrf:site_batch> Common Importation Problems Improper or undefined UNITS or MEASURE Text embedded into the Model view which causes an inconsistent bounding box Large dimensions which cause grainy resolution upon zoom Legacy CAD versions prior to Release 15 or AutoCAD Importing from an Alcatel-Lucent Controller The instructions below will enable you to seamlessly migrate all building, campus, and floor plan information previously entered into an Alcatel-Lucent controller. Pre-Conversion Checklist Prior to importing floor plans, ensure that VisualRF's memory allocation is sufficient for the anticipated number of floor plans. To change the memory allocation, navigate to the VisualRF > Setup page and configure the memory allocation accordingly. Memory allocation should equal.5 GB for 1-75 floor plans, 1 GB for floor plans, 1.5 GB for floor plans, and 2 GB for 501-1,000 floor plans. Importing a large number of floor plans can impact performance of the AMP server. VisualRF must create a thumbnail, provision APs, create attenuation grid, and locate all clients on each imported floor plan. This can cause the VisualRF > Floor Plans page to be unresponsive. Process on Controller 1. On the controller's UI, navigate to the Plan > Building List page. 2. Select the buildings to be exported and select Export. 3. When the dialog box appears, make sure that you have included all images and select Save to a file. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 295

296 Process on AMP 1. Navigate to VisualRF > Import. 2. Select the Import floor plans from an Alcatel-Lucent Controller link. 3. Select the Begin Importing Floor Plans link. 4. When prompted for input file, use the file saved from the controller process. VisualRF Location APIs VisualRF provides the following location APIs: Site Inventory: You can find the site_id from the Floor Plan List query defined on the XML API page This interface provides floor details including access points, walls, regions, surveys, etc. The corresponding example XML and schema are attached in visualrf_site_inventory.* Device Location: Provide the radio MAC of the client to locate. The corresponding site where the user was placed is provided along with the dimensions If a client is heard on multiple floors, it will only be placed on the floor that contains the AP it is associated with. Sample Device Location Response <visualrf:device_location version="1" xmlns:visualrf=" <device mac="00:13:02:c2:39:28" name="peter" site_id="4f b47-4ac eba3f7df3a6" site_name="newyork"> <site-width>124.51</site-width> <site-height>161.14</site-height> <x>82.50</x> <y>37.50</y> </device> </visualrf:device_location> Sample Site Inventory Response <amp:amp_site_inventory version="1" xmlns:amp= xmlns:xsi=" <site id="b45e7a49-23b5-4db0-891a-2e60bff90d2c" version="677"> <name>remax</name> <uom>ft</uom> <width>314.45</width> <height>425.88</height> <property name="site_owner" value="" format="" /> <property name="name" value="remax" format="" /> <property name="installer" value="" format="" /> <property name="planner" value="" format="" /> <image type="background"> <filename>/var/example/snapshot/b45e7a e6d2c.677/background.jpg</filename> <relative-url>/snapshot/b423b5-4db0-891a2e0d2c.677/background.jpg</relative-url> <pixel-width>1151</pixel-width> <pixel-height>1557</pixel-height> </image> <image type="thumbnail"> <filename>/var/example/snapshot/b45e7a49891af90d2c.677/thumb.jpg</filename> <relative-url>/snapshot/b45e7a49-23b5-4db0-891a2c.677/thumb.jpg</relative-url> <pixel-width>230</pixel-width> <pixel-height>311</pixel-height> </image> <ap id="12615" name="ap-4000m-1"> <x>118.97</x> <y>130.38</y> <total-bandwidth>0</total-bandwidth> <total-clients>0</total-clients> 296 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

297 <status>down</status> <uptime>0.0</uptime> <radio index="1" phy="g" mac="00:20:a6:5a:63:66" beamwidth="0.0" gain="1.5" antenna="" orientation="0.0" mount="ceiling" valid="false"> <discovering-radio id="11276" index="1" dbm="-85" /> <discovering-radio id="11828" index="1" dbm="-93" /> </radio> </ap> </site> </amp:amp_site_inventory> About VisualRF Plan Overview VisualRF Plan is a standalone Windows client that can be used for planning sites that do not yet use the OV3600 service on the Web. You can use VisualRF Plan to do basic planning procedures like adding a floor plan, provisioning APs, and generating a Bill of Materials (BOM) report. VisualRF Plan is free to use for anyone with an Alcatel-Lucent support account. No license is required. Minimum requirements Must be installed on a Windows machine with the following minimum specifications: 250 MB Hard drive storage space 2 GB RAM 2.0 GHz dual-core CPU If installing VisualRF Plan on a VMWare virtual machine hosted by a Mac computer, you must disable Folder Sharing. Installation To install VisualRF Plan after you have downloaded it from the Alcatel-Lucent support site: 1. The installer will prompt you for the location of the data directory. You must have access to the directory you choose for the installation. 2. Choose a directory for auto-backup. The default is user directory. 3. Follow the rest of the instructions on your installation screen. OmniVista 3600 Air Manager 7.4 User Guide Using VisualRF 297

298 Differences between VisualRF Plan and VisualRF online Table 150 VisualRF Plan vs. VisualRF Online Feature VisualRF VisualRF Plan Hardware sizing Installation required X X How to plan a site X X Navigation X X Track users Track interferers VisualRF APIs Location accuracy QuickView preferences Resource utilization X X X X X X Add external walls X X Client surveys X IDF X X View deployed switches View signal strength X X Planning and provisioning X X Import and Export X X 298 Using VisualRF OmniVista 3600 Air Manager 7.4 User Guide

299 Appendix A Setting Up Alcatel-Lucent Instant in OV3600 This appendix describes the Alcatel-Lucent Instant access point and Virtual Controller system, and the procedure to integrate this system with OmniVista 3600 Air Manager. The appendix contains the following topics: Overview of Alcatel-Lucent Instant on page 299 Using Alcatel-Lucent Instant with OV3600 on page 299 Workflow of the Alcatel-Lucent Instant and OV3600 Integration Process on page 300 OV3600 Pages with Instant-Specific Features on page 303 Other Available Features on page 304 Known Issues of the Alcatel-Lucent Instant Integration with OV3600 on page 304 Overview of Alcatel-Lucent Instant Alcatel-Lucent Instant is a system of up to 16 access points (OAW-IAP92, OAW-IAP93, or OAW-IAP105) per Layer 2 subnet. Alcatel-Lucent Instant IAPs are controlled by a single IAP that serves a dual role as a primary Virtual Controller, eliminating the need for dedicated controller hardware. This system can be deployed through a simplified setup process appropriate for smaller organizations, or for multiple geographically-dispersed locations without an on-site administrator. Only the first IAP/Virtual Controller you add to the network must be configured; the subsequent IAPs will all inherit the necessary configuration information from the Virtual Controller. Alcatel-Lucent Instant continually monitors the network to determine which IAP should function as the Virtual Controller at any time, and the Virtual Controller will move from IAP to IAP as necessary without impacting network performance. The Virtual Controller technology in Alcatel-Lucent Instant is capable of IAP auto discovery, 802.1X authentication, role- and device-based policy enforcement, rogue detection, and Adaptive Radio Management (ARM). Using Alcatel-Lucent Instant with OV3600 OV3600 has added centralized network management support for Alcatel-Lucent Instant in version With a distributed deployment where multiple locations each have an Alcatel-Lucent Instant Virtual Controller and IAPs, OV3600 serves as a centralized management console. OV3600 provides all functionality for normal WLAN deployments including long-term trend reporting, PCI compliance, configuration auditing, role-based administration, location services, RF visualization, and many other features. Integrating Alcatel-Lucent Instant systems into OV3600 is unique from the setup of any other device class due to the following considerations: Discovery: OV3600 does not discover Alcatel-Lucent Instant devices via scanning (SNMP or HTTP) the network. Each Alcatel-Lucent Instant deployment will automatically check-in to the OV3600 configured within the IAP's user interface. The first Virtual Controller for an organization will automatically appear as a new device in OV3600. Subsequent IAPs are discovered via the Virtual Controller, just like standard controller/thin AP deployments. OmniVista 3600 Air Manager 7.4 User Guide Setting Up Alcatel-Lucent Instant in OV

300 Auto-provisioning: The first authorized Virtual Controller requires manual authorization into OV3600 via shared secret to ensure security. Along with the shared secret, the Virtual Controller sends an Organization String which automatically initializes and organizes the IAPs in OV3600. Unlike the traditional infrastructure of a physical controller and thin APs, Alcatel-Lucent Instant automates many tedious steps of developing a complex hierarchical structure of folders, config groups, templates, admin users, and admin roles for Alcatel-Lucent Instant. Communication via HTTPS: Because Alcatel-Lucent Instant devices may be deployed behind NATenabled firewalls, Virtual Controllers "push" data to OV3600 via HTTPS. OV3600 initiates no connections to Alcatel-Lucent Instant devices via SNMP, TFTP, SSH, and the like. This enables quick remote setup without having to modify firewall rules. Virtual controller listed as separate device: The Virtual Controller is listed as an additional device, even though it is part of the existing set of IAPs. If you have 10 physical IAPs, OV3600 will list 10 Alcatel- Lucent Instant IAPs and one Alcatel-Lucent Instant Virtual Controller. You can identify the IAP acting as the Virtual Controller by their identical LAN MAC addresses in APs/Devices > List pages, Device Inventory reports, and any other OV3600 pages that list your network devices. Refer to the Alcatel-Lucent Instant Data Sheet for full operational and regulatory specifications, hardware capabilities, antenna plots, and radio details. Workflow of the Alcatel-Lucent Instant and OV3600 Integration Process The following is a sample setup workflow around a common Alcatel-Lucent Instant use case. Setting up Alcatel-Lucent Instant Hardware See the Alcatel-Lucent Instant Quick Start Guide, the Alcatel-Lucent Instant Professional Installation Guide, the OAW-IAP105 Wireless Access Point Installation Guide, and the OAW-IAP92 and OAW-IAP93 Wireless Access Point Installation Guide for information on setting up the hardware and configuring the network. Required Personnel For each remote location, an on-site installer is required to physically mount the IAPs, connect to the Alcatel-Lucent Instant SSID, configure the WLAN, configure the names of the IAPs, and enter the information in the first IAP's user interface that will enable communication with the OV3600. An OV3600 administrator sends an Organization String and Shared Secret key along with OV3600's IP address to the on-site installer. The OV3600 admin later validates the first Virtual Controller's Organization String and its Shared Secret when it appears in the APs/Devices > New list. The administrator also enables user roles to administer the Alcatel-Lucent Instant systems, makes any other changes in OV3600 as necessary. Creating your Organization String The Organization String is a set of colon-separated strings created by the OV3600 administrator to accurately represent the deployment of each Alcatel-Lucent Instant system. This string is entered into the Alcatel-Lucent Instant UI by the on-site installer. The format of the Organization String is "Org:subfolder1:subfolder2..." and so on, up to 31 characters long. "Org," the top-level string, is generally the name of your organization and is used to automatically generate the following (if not already present) in OV3600: OV3600 Role: "Org Admin" (initially disabled) OV3600 User: "Org Admin" (assigned to the role "Org Admin") 300 Setting Up Alcatel-Lucent Instant in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

301 Folder: "Org" (under the Top folder in OV3600) Configuration Group: "Org" Additional strings in the Organization String are used to create a hierarchy of subfolders under the folder named "Org": subfolder1 would be a folder under the "Org" folder subfolder2 would be a folder under subfolder1 To create your Organization String, consider the plan of how your Alcatel-Lucent Instant IAPs are to be physically distributed. As a best practice, the Organization String should mirror your company's geographical or internal reporting structure. For example, if you plan to deploy Alcatel-Lucent Instant in four stores in two different cities for Acme Corporation, your Organization Strings might look like these: Acme:New York:Times Square Store Acme:New York:Queens Store Acme:San Francisco:Sunset Store Acme:San Francisco:SOMA Store The Shared Secret Key The Shared Secret key is used by the administrator to manually authorize the first Virtual Controller for an organization that appears in the APs/Devices > New page in OV3600. Any string is acceptable. NOTE: Always ensure the protection of your organization's shared secret. Knowledge of this shared secret, the organization string, and communication protocol could allow a rogue device to masquerade as an Alcatel- Lucent Instant device. At this point, the admin in our example should send the Organization String, Shared Secret key, and OV3600 IP address to the on-site installers setting up Alcatel-Lucent Instant hardware inside the storefronts. Entering the Organization String and OV3600 Information into the IAP For the initial IAP/Virtual Controller set up in each location, the on-site installer logs in to the first IAP's web interface via the Alcatel-Lucent Instant configuration SSID, and navigates to Settings > OV3600. The installer then enters the correct Organization String, the OV3600 IP address, and the Shared Secret key, as shown in Figure 237. Figure 237 Alcatel-Lucent Instant UI: Settings > AirWave OmniVista 3600 Air Manager 7.4 User Guide Setting Up Alcatel-Lucent Instant in OV

302 Receiving the Alcatel-Lucent Instant Virtual Controller as a New Device in OV3600 After the installer enters this information in the Alcatel-Lucent Instant user interface, the device will immediately attempt to contact your OV3600 server. Within a few minutes, the New Devices link at the top of the OV3600 UI will increase by one - that first IAP is added as an Alcatel-Lucent Instant Virtual Controller in the APs/Devices > New page, as shown in Figure 238. Figure 238 New Instant Virtual Controller on APs/Devices > New Page Illustration Verifying the Shared Secret and Adding the Device When an Alcatel-Lucent Instant device appears in the APs/Devices > New page, the admin user should mouse over the value under the Type column to verify the device's Shared Secret with OV3600, as shown in Figure 239. Figure 239 Mouseover the Alcatel-Lucent Instant Type to Indicate Shared Secret If the incoming Shared Secret matches the one you created, select Add, then Save and Apply in the confirmation page. NOTE: With an Organization specified, you do not have to select any Group or Folder from the drop-down menus on the APs/Devices > New page. In fact, if you do change the Group/Folder drop-down menus, all Organization-specified Virtual Controllers will ignore these values and will use the folder/group values from the Organization String instead. If you select Add for some non-alcatel-lucent Instant devices as well as some Organization-specified Virtual Controllers, the drop-down menus will apply to the non-iaps but not the Virtual Controllers. If you have any Virtual Controllers with no Organization specified the first time they communicate with OV3600, then they will be placed in the Folder/Group drop-box values you have selected. OV3600 parses the information from the Organization String and auto-creates the following in its own interface: A new User Role (disabled by default for security reasons) named "Acme Admin" A new User named "Acme Admin" with a password equal to the Virtual Controller's Shared Secret A new configuration group called "Acme" A new folder just under the Top folder called "Acme" Two subfolders: "New York" and "San Francisco" from subfolder2 Two subfolders under New York: "Times Square Store" and "Queens Store" from subfolder3 Two subfolders under San Francisco: "Sunset Store" and "SOMA Store" from subfolder3 302 Setting Up Alcatel-Lucent Instant in OV3600 OmniVista 3600 Air Manager 7.4 User Guide

303 Remaining Manual Admin Tasks in OV3600 The Admin will then complete the following tasks in OV3600: 1. Enable the newly created Admin User Role in OV3600 Setup > Roles, as shown in Figure 240. Figure 240 Enable Admin User Role in AMP Setup > Roles 2. In Groups > Template for the newly created Acme group, verify the first Virtual Controller's autocreated template. NOTE: The auto-created template is most useful if the first Virtual Controller for the top-level Organization String is fully configured on-site before it is pointed at OV3600 in the Virtual Controller's UI. 3. Evaluate, approve, or ignore incoming Virtual Controllers with a different top level Organization String and/or Shared Secret in the APs/Devices > New list. Subsequent IAPs are auto-authorized if they have an Organization/Shared Secret key that matches the Shared Secret key of any existing authorized Virtual Controller in the top-level Organization String. 4. Set the initial Virtual Controller to Manage Read/Write mode and push the good configuration to the subsequent IAPs. 5. Set up OV3600 users to have access to specific folders, if desired. OV3600 Pages with Instant-Specific Features The following is a summary of OV3600 pages affected by Alcatel-Lucent Instant support: APs/Devices > New: When an Alcatel-Lucent Instant device appears in the APs/Devices > New page, an admin user can mouse over the value on the Type column to display the device's Shared Secret with OV3600. APs/Devices > List: The Virtual Controller is listed as an additional device, even though it is part of the existing set of IAPs. You can identify the IAP acting as the Virtual Controller by their identical LAN MAC addresses. Clients > Client Detail: Once IAPs are serving clients, the IAPs can use user-agent strings to extract operating systems and device descriptions of its clients, and then populate the Device Description and Device OS fields in Clients > Client Detail. APs/Devices > Audit: Alcatel-Lucent Instant configuration fetching can be performed in APs/Devices > Audit. The running configuration is stored on the IAP and verified by the template. APs/Devices > Monitor > Radio Statistics: The Radio Statistics page for Alcatel-Lucent Instant devices displays CPU Utilization, Channel Utilization, Bandwidth, Power, and MAC/Phy Error statistics. RAPIDS: Since Alcatel-Lucent Instant does not support mitigation or high-level rogue reporting, it does not synchronize classification. All rogue devices are reported and stored in the OV3600 for evaluation OmniVista 3600 Air Manager 7.4 User Guide Setting Up Alcatel-Lucent Instant in OV