Appendix B – WMS Offload Details ............................29 State Correlation Process .............................. 29 Appendix C – Converting from MMS to Dell PowerConnect W AWMS ................31 Migrating Floor Plans from RF Plan to AWMS ......................34 Appendix D – Increasing Location Accuracy ........................35...
Note: There should never be a Local controller managed by an AWMS server whose Master controller is also not under management. Prerequisites for Integrating Dell PowerConnect W Infrastructure You will need the following information to monitor and manage your Dell PowerConnect W infrastructure. SNMP community string (monitoring & discovery) Telnet/SSH credentials (configuration only) “enable”...
Dell Feature Implementation Schedule for AWMS Feature AWMS Implementation Ability filter User Session by Dell PowerConnect ArubaOS roles AOS 5.0 support RAP white list management for RN 3.1 Added support for rogue containment Added support for configuring controller specific overrides...
Click Save. Device Setup Communication Page (Credential & Timing) Credentials AWMS requires several credentials to properly interface with Dell infrastructure. The Discover process detailed in Section 3 requires proper global credential configuration. Navigate to Device > Setup Communication page Locate the Default Credentials section...
Page 7
Figure 3 Credential Setup Required Fields for Discovery Enter SNMP Community String Note: Be sure to note the community string, because it must match the SNMP Trap community string which is configured later in this document. Required Fields for Configurations and Basic Monitoring Enter Telnet/SSH Username ...
Creating an Dell PowerConnect Specific Policy (Group) in AWMS It is prudent to establish an Dell PowerConnect Group within AWMS. During the discovery process you will move new discovered controllers into this group. Basic Monitoring Configuration Navigate to the Groups>List page Click Add.
Note : You should reference the Dell PowerConnect W Configuration Guide for additional information on Policy configuration. Configuration Reference the Dell PowerConnect ArubaOS Configuration Guide located on Home > Documentation page for detailed instructions.
Thin APs are added (migrated from New to Managed or Monitoring) simultaneously. Master Controller Discovery Scan networks containing Dell PowerConnect W Master controllers from Device > Discover page. This will use your Global Credentials configured in the previous section. - or - Manually enter the Master controller on the Device >...
Ensure “Monitor Only” option is selected Click the “Add” button Navigate to APs/Devices > New page Select the Dell PowerConnect W Master controller Ensure “Monitor Only” option is selected Click the “Add” button Figure 7 Add New Controller Local Controller Discovery Local controllers are discovered via the Master controller.
Customer wants to relate Auth failures to a client device, AP, Group of APs, and controller. AWMS provides this unique correlation capability. Prerequisites for Integration If you have not discovered the Dell infrastructure or configured credentials, proceed to Sections 3 and 4 of this document. Enable Stats Utilizing AWMS GUI To enable stats on the Aruba controllers: Navigate to Groups>Basic page...
This will push a set of commands via SSH to all Dell PowerConnect local Controllers. AWMS must have read/write access to the controllers in order to push these commands. See Device Setup Communication Section below for help configuring your device credentials.
SNMPv3 user. AWMS must have read/write access to the controllers in order to push these commands. Note : This process will not reboot your controllers. See Appendix A on how to utilize the Dell PowerConnect W CLI to enable stats or wms offload.
Page 16
Warning : Do not configure the SNMP version to v3, because AWMS does not support SNMPv3 traps/informs. Dell PowerConnect ArubaOS Traps utilized by AWMS Auth Traps Utilized by AWMS wlsxNUserAuthenticationFailed wlsxUserAuthenticationFailed (AMP does not use this trap) wlsxNAuthServerReqTimedOut ...
Page 17
(Controller-Name) (config) # snmp-server trap enable <TRAPS FROM LIST ABOVE> Note : See Appendix A for the full command that can be copied and pasted directly into the Dell PowerConnect W CLI. (Controller-Name) (config) # write mem Saving Configuration...
Page 18
SNMP TRAP HOSTS --------------- HOST VERSION SECURITY NAME PORT TYPE TIMEOUT RETRY ---- ------- ------------- ---- ---- ------- ----- 10.2.32.4 SNMPv2c public Trap Verify firewall port 162 (default) is open between AWMS and the controller. Validate traps are making it into AWMS by issuing the following commands from AWMS command line.
Plan Tab - where floor plans are stored and heatmaps are generated. Prior to offloading wms ensure that you have exported floor plans from the Dell PowerConnect ArubaOS and imported into AWMS. All functionality within the Plan Tab is incorporated with the VisaulRF module in AWMS.
Page 20
Policy Violations – no summary data available in AWMS Unauthorized Devices Detected – no summary data available in AWMS Rogue AP Classification Summary Rogue APs Detected – summary data available on RAPIDS > Overview page Rogue APs Disabled – no summary data available in AWMS Suspected Rogue APs –...
Dell-Specific Capabilities within AWMS Dell PowerConnect Traps for RADIUS Auth & IDS Tracking The authentication failure traps are received by the AWMS server and correlated to the proper controller, AP, and user. See Figure below showing all authentication failures related to a controller.
View Controller License Information Navigate to the Device > Detail page of a controller under AWMS management Click on the License link Figure 16 License Popup 6.4 - Device Classification Only utilize this section if you have completed WMS offload procedure above. After offloading WMS, AWMS maintains the primary (ARM, WIPS, and WIDS) state classification for all devices discovered over-the-air.
Page 23
Select the proper classification from the Controller Classification Pull Down Figure 17 Rogue Detail Warning : Changing the controller’s classification within the Dell PowerConnect W AWMS UI will push a reclassification message to all controllers managed by the AWMS server that are in Groups with the Offloading the WMS database parameter set to Yes.
Page 24
Figure 18 User Classification Warning : Changing User Classification within the Dell PowerConnect W AWMS UI will push a user reclassification message to all controllers managed by the AWMS server that are in groups with the Offloading the WMS database parameter set to Yes.
Enable Stats Utilizing the Dell PowerConnect W CLI (Local Controller in Master Local Environment) Note : Do not use these commands if using the Dell PowerConnect W AWMS WebUI to set these commands. SSH into the controller, and enter “enable” mode, and issue the following commands: (Controller-Name) # configure terminal Enter Configuration commands, one per line.
Page 26
Note : Do not use these commands if using the Dell PowerConnect W AWMS WebUI. [root@AWMS ~]# snmpwalk -v3 -a SHA -l AuthPriv -u <MMS-USER> -A <MMS-SNMP- PASSWORD> -X <MMS-SNMP-PASSWORD> <DELL CONTROLLER IP ADDRESS> wlsxSystemExtGroup WLSX-SYSTEMEXT-MIB::wlsxSysExtSwitchIp.0 = IpAddress: 10.51.5.222 WLSX-SYSTEMEXT-MIB::wlsxSysExtHostname.0 = STRING: aruba-3600-2 WLSX-SYSTEMEXT-MIB::wlsxSysExtSwitchLastReload.0 = STRING: User reboot.
Note : You will need to wait until the next Rogue Poll Period on execute a “Poll Now” for each local controller to see rogue devices begin to appear in AWMS after doing a “restart wms” in Dell PowerConnect W.
WMS offload instructs the Master controller to stop correlating ARM, WIPS, and WIDS state information amongst its Local controllers, because AWMS will assume this responsibility. Figure 4 below depicts how Dell PowerConnect W AMWS communicates state information with Local controllers.
Page 30
Ability to better classify devices based on AWMS wire-line information not currently available in Dell PowerConnect ArubaOS. AWMS provides a near real-time event notification and classification of new devices entering air space. RAPIDS gains additional wire-line discovery data from Dell PowerConnect W controllers.
Appendix C – Converting from MMS to Dell PowerConnect W AWMS The instructions below will enable you to seamlessly migrate all building, campus, and floor plan information previously entered into MMS or Dell PowerConnect W into Dell PowerConnect W AWMS. Pre conversion checklist The conversion tool is only supported for IE6 and later.
Page 32
Password Context (optional) – leave this blank unless you have enabled context on you MMS. Most customers do not utilize context. If you are using context, then you will have to enter a different user for each context defined within MMS. Figure 21 MMS Export to AWMS window Click on the “Export”...
Page 33
Process to Import within AWMS Navigate to VisualRF > Import page Select the “Import floor plans from an Dell PowerConnect W Controller ” link A detailed set of directions will appear. Click on the “Begin Importing Floor Plans” link at the bottom of the instructions and it will...
Browse for the file that was saved during the controller export process above. Click the “Upload” button to validate the XML exported from the controller. If there are errors in the XML you will see errors on screen. Figure 25 File Upload Explorer Importing a large number of floor plans can impact performance on the AMWS server.
110 milliseconds 242.64 seconds Leveraging RTLS to Increase Accuracy Overview This section provides instructions for integrating the AWMS, Dell WLAN infrastructure and Dell’s RTLS feed for more accurately locating wireless clients and WiFi Tags. Minimum Requirements AWMS version 7.0 or higher Dell PowerConnect ArubaOS (AOS) 6.x or higher...
Page 36
Figure 27 Typical Tag Deployment Prerequisites You will need the following information to monitor and manage your Dell infrastructure. Ensure AWMS server is already monitoring Dell infrastructure Ensure WMS offload process is complete Ensure firewall configuration for port 5050 (default port) supports bidirectional UDP communication between the AWMS server’s IP address and each access point’s IP address.
Page 37
A new section will automatically appear with the following settings RTLS Port – match controller default is 5050 RTLS Username – match the SNMPv3 "MMS" username configured on controller RTLS Password – match the SNMPv3 "MMS" password configured on controller ...
Page 38
Figure 26 RTLS Service Status Check the RTLS log file to ensure Tag chirps are making it to the AWMS server. SSH into your AWMS server. [root@AWMSServer]# logs [root@AWMSServer]# tail rtls payload: 00147aaf01000020001a1ec02b3200000001000000137aae0100000c001a1ec02b3 20000001a1e82b322590006ddff02 1224534900.588245 - got 96 bytes from 10.51.1.39 on port 5050 Mon Oct 20 13:35:00 2008: 1224534900.588338 - got 96 bytes from 10.51.1.39 on port 5050 payload:...
Page 39
Verify external applications can see WiFi Tag information by exercising the Tag XML API. https://<AWMS SERVER IP>/visualrf/rfid.xml You should see the following XML output <visualrf:rfids version="1"> <rfid battery-level="0" chirp-interval="" radio-mac="00:14:7E:00:4C:E0" vendor=""> <radio phy="g" xmit-dbm="10.0"/> <discovering-radio ap="SC-MB-03-AP10" dBm="-91" id="811" index="1" timestamp="2008-10-21T12:23:30-04:00"/> <discovering-radio ap="SC-MB-03-AP06"...
Page 40
Wi-Fi Tag Setup Guidelines Ensure tags can be heard by at least 3 access points from any given location. The recommended is 4 for best results. Ensure tags chirp on all regulatory channels Component Description Autonomous AP Standalone device which performs radio and authentication functions Thin AP Radio-only device coupled with WLAN Controller to perform authentication WLAN Controller...