WLAN_TroubleshootingGuide

Troubleshooting Avaya WLAN 8100

Release 3.0NN47251-700

Issue 08.01June 2014

© 2014 Avaya Inc.

All Rights Reserved.

NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reservesthe right to make changes and corrections to the information in thisdocument without the obligation to notify any person or organizationof such changes.

Documentation disclaimer“Documentation” means information published by Avaya in varyingmediums which may include product information, operatinginstructions and performance specifications that Avaya may generallymake available to users of its products and Hosted Services.Documentation does not include marketing materials. Avaya shall notbe responsible for any modifications, additions, or deletions to theoriginal published version of documentation unless suchmodifications, additions, or deletions were performed by Avaya. EndUser agrees to indemnify and hold harmless Avaya, Avaya's agents,servants and employees against all claims, lawsuits, demands andjudgments arising out of, or in connection with, subsequentmodifications, additions or deletions to this documentation, to theextent made by End User.

Link disclaimerAvaya is not responsible for the contents or reliability of any linkedwebsites referenced within this site or documentation provided byAvaya. Avaya is not responsible for the accuracy of any information,statement or content provided on these sites and does notnecessarily endorse the products, services, or information describedor offered within them. Avaya does not guarantee that these links willwork all the time and has no control over the availability of the linkedpages.

WarrantyAvaya provides a limited warranty on Avaya hardware and software.Refer to your sales agreement to establish the terms of the limitedwarranty. In addition, Avaya’s standard warranty language, as well asinformation regarding support for this product while under warranty isavailable to Avaya customers and other parties through the AvayaSupport website: http://support.avaya.com or such successor site asdesignated by Avaya. Please note that if you acquired the product(s)from an authorized Avaya Channel Partner outside of the UnitedStates and Canada, the warranty is provided to you by said AvayaChannel Partner and not by Avaya.

LicensesTHE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO ORSUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AREAPPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/ORINSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (ASAPPLICABLE) UNDER A COMMERCIAL AGREEMENT WITHAVAYA OR AN AVAYA CHANNEL PARTNER. UNLESSOTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOESNOT EXTEND THIS LICENSE IF THE SOFTWARE WASOBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYAAFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYARESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOUAND ANYONE ELSE USING OR SELLING THE SOFTWAREWITHOUT A LICENSE. BY INSTALLING, DOWNLOADING ORUSING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOMYOU ARE INSTALLING, DOWNLOADING OR USING THESOFTWARE (HEREINAFTER REFERRED TOINTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TOTHESE TERMS AND CONDITIONS AND CREATE A BINDINGCONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants you a license within the scope of the license typesdescribed below, with the exception of Heritage Nortel Software, forwhich the scope of the license is detailed below. Where the orderdocumentation does not expressly identify a license type, theapplicable license will be a Designated System License. The

applicable number of licenses and units of capacity for which thelicense is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the documentation or othermaterials available to you. “Software” means Avaya’s computerprograms in object code, provided by Avaya or an Avaya ChannelPartner, whether as stand-alone products, pre-installed , or remotelyaccessed on hardware products, and any upgrades, updates, bugfixes, or modified versions thereto. “Designated Processor” means asingle stand-alone computing device. “Server” means a DesignatedProcessor that hosts a software application to be accessed bymultiple users. “Instance” means a single copy of the Softwareexecuting at a particular time: (i) on one physical machine; or (ii) onone deployed software virtual machine (“VM”) or similar deployment.

License typesDesignated System(s) License (DS). End User may install and useeach copy of the Software only on a number of DesignatedProcessors up to the number indicated in the order. Avaya mayrequire the Designated Processor(s) to be identified in the order bytype, serial number, feature key, location or other specificdesignation, or to be provided by End User to Avaya throughelectronic means established by Avaya specifically for this purpose.

CPU License (CP). End User may install and use each copy of theSoftware on a number of Servers up to the number indicated in theorder provided that the performance capacity of the Server(s) doesnot exceed the performance capacity specified for the Software. EndUser may not re-install or operate the Software on Server(s) with alarger performance capacity without Avaya’s prior consent andpayment of an upgrade fee.

Heritage Nortel Software“Heritage Nortel Software” means the software that was acquired byAvaya as part of its purchase of the Nortel Enterprise SolutionsBusiness in December 2009. The Heritage Nortel Software currentlyavailable for license from Avaya is the software contained within thelist of Heritage Nortel Products located at http://support.avaya.com/licenseinfo under the link “Heritage Nortel Products”. For HeritageNortel Software, Avaya grants Customer a license to use HeritageNortel Software provided hereunder solely to the extent of theauthorized activation or authorized usage level, solely for the purposespecified in the Documentation, and solely as embedded in, forexecution on, or (in the event the applicable Documentation permitsinstallation on non-Avaya equipment) for communication with Avayaequipment. Charges for Heritage Nortel Software may be based onextent of activation or use authorized as specified in an order orinvoice.

CopyrightExcept where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, Hosted Service,or hardware provided by Avaya. All content on this site, thedocumentation, Hosted Service, and the Product provided by Avayaincluding the selection, arrangement and design of the content isowned either by Avaya or its licensors and is protected by copyrightand other intellectual property laws including the sui generis rightsrelating to the protection of databases. You may not modify, copy,reproduce, republish, upload, post, transmit or distribute in any wayany content, in whole or in part, including any code and softwareunless expressly authorized by Avaya. Unauthorized reproduction,transmission, dissemination, storage, and or use without the expresswritten consent of Avaya can be a criminal, as well as a civil offenseunder the applicable law.

Third Party Components“Third Party Components” mean certain software programs orportions thereof included in the Software or Hosted Service maycontain software (including open source software) distributed underthird party agreements (“Third Party Components”), which containterms regarding the rights to use certain portions of the Software(“Third Party Terms”). As required, information regarding distributedLinux OS source code (for those Products that have distributed LinuxOS source code) and identifying the copyright holders of the ThirdParty Components and the Third Party Terms that apply is availablein the Documentation or on Avaya’s website at: http://support.avaya.com/Copyright or such successor site as designatedby Avaya. You agree to the Third Party Terms for any such ThirdParty Components

http://support.avaya.com/

http://support.avaya.com/LicenseInfo


http://support.avaya.com/Copyright

http://support.avaya.com/Copyright

Preventing Toll Fraud“Toll Fraud” is the unauthorized use of your telecommunicationssystem by an unauthorized party (for example, a person who is not acorporate employee, agent, subcontractor, or is not working on yourcompany's behalf). Be aware that there can be a risk of Toll Fraudassociated with your system and that, if Toll Fraud occurs, it canresult in substantial additional charges for your telecommunicationsservices.

Avaya Toll Fraud InterventionIf you suspect that you are being victimized by Toll Fraud and youneed technical assistance or support, call Technical Service CenterToll Fraud Intervention Hotline at +1-800-643-2353 for the UnitedStates and Canada. For additional support telephone numbers, seethe Avaya Support Website: http://support.avaya.com/. Suspectedsecurity vulnerabilities with Avaya products should be reported toAvaya by sending mail to: [email protected].

TrademarksThe trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation, Hosted Service(s), and Product(s) providedby Avaya are the registered or unregistered Marks of Avaya, itsaffiliates, or other third parties. Users are not permitted to use suchMarks without prior written consent from Avaya or such third partywhich may own the Mark. Nothing contained in this site, theDocumentation, Hosted Service(s) and Product(s) should beconstrued as granting, by implication, estoppel, or otherwise, anylicense or right in and to the Marks without the express writtenpermission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners.Linux® is the registered trademark of Linus Torvalds in the U.S. andother countries.

Downloading DocumentationFor the most current versions of Documentation, see the AvayaSupport website: http://support.avaya.com, or such successor site asdesignated by Avaya.

Contact Avaya SupportSee the Avaya Support website: http://support.avaya.com for Productor Hosted Service notices and articles, or to report a problem withyour Avaya Product or Hosted Service. For a list of support telephonenumbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated byAvaya), scroll to the bottom of the page, and select Contact AvayaSupport.


http://support.avaya.com



Contents

Chapter 1: Introduction............................................................................................................ 6Purpose.................................................................................................................................. 6Related Resources.................................................................................................................. 6

Documentation.................................................................................................................. 6Training............................................................................................................................ 6Viewing Avaya Mentor videos............................................................................................. 7

Support.................................................................................................................................. 7Chapter 2: New in this release................................................................................................. 8

Features................................................................................................................................. 8Other changes........................................................................................................................ 9

Chapter 3: Troubleshooting Planning................................................................................... 10Chapter 4: Troubleshooting Tools........................................................................................ 12

Port mirroring........................................................................................................................ 12Port mirroring commands....................................................................................................... 13Port statistics........................................................................................................................ 13Time domain reflectometer..................................................................................................... 13System logs.......................................................................................................................... 13IP Flow information export...................................................................................................... 14Remote packet capture.......................................................................................................... 14Traffic monitoring.................................................................................................................. 15

Chapter 5: Configuring troubleshooting features............................................................... 16Configuring Serviceability....................................................................................................... 16

Configuring RMON with the CLI........................................................................................ 16Configuring IPFIX using CLI............................................................................................. 21

Configuring diagnostics and graphing..................................................................................... 24System diagnostics and statistics using CLI....................................................................... 25Network monitoring configuration using CLI....................................................................... 28

Chapter 6: General diagnostic tools..................................................................................... 41CLI command modes............................................................................................................. 41Wireless Management System............................................................................................... 42Virtual link aggregation control protocol (VLACP)..................................................................... 42

Chapter 7: Initial Troubleshooting........................................................................................ 44Gather information................................................................................................................. 44

Chapter 8: Troubleshooting WLAN ...................................................................................... 47Troubleshooting Wireless LAN Management System issues..................................................... 47Troubleshooting Layer 2 and Layer 3 issues............................................................................ 49Troubleshooting a failed configuration restore (from an ascii file) on a domain controller............. 50Troubleshooting AP related issues.......................................................................................... 50Troubleshooting client-related issues...................................................................................... 55

4 Troubleshooting Avaya WLAN 8100 June 2014Comments? [email protected]

mailto:[email protected]?subject=Troubleshooting Avaya WLAN 8100

Troubleshooting client connectivity issues due to failed authentication................................. 61Troubleshooting client connectivity issues due to failed MAC validation............................... 64Troubleshooting DHCP-related client connectivity issues.................................................... 65Troubleshooting client traffic issues.................................................................................. 66

Troubleshooting wireless clients using Remote Packet Capture................................................ 67Troubleshooting the E911 feature........................................................................................... 71

Appendix A: Resetting the mobility domain password ...................................................... 74

Contents

June 2014 Troubleshooting Avaya WLAN 8100 5Comments? [email protected]


Chapter 1: Introduction

PurposeThis document:

• Provides troubleshooting information and procedures for the WLAN Controller 8180 andAccess Point 8120.

• Describes the diagnostic tools and utilities available for troubleshooting the WLAN 8100 Seriesproducts including the Command Line Interface (CLI) and the Wireless Management System(WMS).

• Guides you through some common problems to achieve a first tier solution to these situations.

• Advises you what information to compile prior to troubleshooting or calling Avaya for help.

This document assumes that you:

• Are familiar with networking concepts and terminology.

• Have experience with Graphical User Interface (GUI).

• Have basic knowledge of network topologies.

Related Resources

DocumentationFor a list of the documentation for this product, see Documentation Reference for Avaya WLAN8100, NN47251-100.

TrainingOngoing product training is available. For more information or to register, see http://avaya-learning.com/.

Enter the course code in the Search field and click Go to search for the course.


http://avaya-learning.com/

http://avaya-learning.com/


Course Code Course Title6769X Avaya Wireless LAN 8100 Implementation and Management4D00045V Avaya VENA Unified Access ImplementationWireless LAN 8100 AIPS credential 7D00060A Wireless LAN 8100 Implementation Assessment (online test)

Viewing Avaya Mentor videosAvaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avayaproducts.

About this taskVideos are available on the Avaya Support website, listed under the video document type, and onthe Avaya-run channel on YouTube.

Procedure• To find videos on the Avaya Support website, go to support.avaya.com and perform one of the

following actions:

• In Search, type Avaya Mentor Videos to see a list of the available videos.

• In Search, type the product name. On the Search Results page, select Video in theContent Type column on the left.

• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor andperform one of the following actions:

• Enter a key word or key words in the Search Channel to search for a specific product ortopic.

• Scroll down Playlists, and click the name of a topic to see the available list of videos postedon the website.

Note:

Videos are not available for all products.

SupportGo to the Avaya Support website at http://support.avaya.com for the most up-to-datedocumentation, product notices, and knowledge articles. You can also search for release notes,downloads, and resolutions to issues. Use the online service request system to create a servicerequest. Chat with live agents to get answers to questions, or request an agent to connect you to asupport team if an issue requires additional expertise.

Support



http://www.youtube.com/AvayaMentor



Chapter 2: New in this release

The following sections detail what's new in the Troubleshooting Avaya WLAN 8100, NN47251-700for Release 3.0.

Related LinksFeatures on page 8Other changes on page 9

FeaturesSee the following sections for information about the feature changes:

• Support for External Captive Portal on page 8

• Support for Link Layer Discovery Protocol (LLDP) on page 8

• Bonjour Gateway support on page 9

For information on the WMS enhancements and on Avaya Command Line Interface (CLI)commands, see Using WMS and EDM on Avaya WLAN 8100, NN47251-108 and ACLI CommandsReference for Avaya WLAN 8100, NN47251-107 respectively.

For more information on feature fundamentals, see Feature Overview for Avaya WLAN 8100,NN47251-102.

Support for External Captive PortalWireless LAN Cotroller 8100 can support external captive portal with patented floating CPIPmapping method and RFC 5176 Change of Authorization (CoA) to achieve a linearly scalingstandalone external captive portal solution that is designed for both large and small deployment.WLAN 8100 users can provide their own external captive portal based on design guideline fromAvaya.

The WLAN controller leverages RFC 5176 CoA (Change of Authorization) to support small, medium,and large scale deployments.

Support for Link Layer Discovery Protocol (LLDP)The Link Layer Discovery Protocol (LLDP) is a data link layer protocol in the Internet Protocol Suiteused by network devices for neighbor identity and capability discovery. Avaya AP advertises itsstatus to the neighbors and relays the information and status about the LLDP neighbors to itsmanaging wireless controller.



LLDP support on AP can advertise its status, capabilities, and process information from other LLDPneighbors. Eg. PoE switches.

Bonjour Gateway supportBonjour is a service discovery protocol of Apple. Bonjour locates devices such as printers, othercomputers, and the services that those devices offer on a local network using multicast domainname system (mDNS) service records. Bonjour can be extended across subnets by using AvayaWLAN 8100 Bonjour Gateway feature, which selectively relays service discovery packets acrossnetworks without using external gateway or custom router configuration.

Related LinksNew in this release on page 8

Other changesThere are no other changes to this document for release 3.0.

Related LinksNew in this release on page 8

Other changes



Chapter 3: Troubleshooting Planning

There are some things you can do to minimize the need for troubleshooting and to plan for doing itas effectively as possible.

First, use the WLAN 8100 Series Documentation Roadmap to familiarize yourself with thedocumentation set, so you know where to get information when you need it.

Second, make sure the system is properly installed and maintained so that it operates as expected.

Third, make sure you gather and keep up to date the site map, logical connections, deviceconfiguration information, and other data that you will require if you have to troubleshoot.

• A site network map identifies where each device is physically located on your site, which helpslocate the users and applications that are affected by a problem. You can use the map tosystematically search each part of your network for problems.

• You must know how your devices are connected logically and physically with virtual local areanetworks (VLAN).

• You should maintain online and paper copies of your device configuration information. Ensurethat all online data is stored with your site’s regular data backup for your site. If your site has nobackup system, copy the information onto a backup medium and store the backup offsite.

• Store passwords in a safe place. It is a good practice to keep records of your previouspasswords in case you must restore a device to a previous software version. You need to usethe old password that was valid for that version.

• It is a good practice to maintain a device inventory, which list all devices and relevantinformation for your network. Use this inventory to easily see the device types, IP addresses,ports, MAC addresses, and attached devices.

• If your hubs or switches are not managed, you must keep a list of the MAC addresses thatcorrelate to the ports on your hubs and switches.

• Maintain a change-control system for all critical systems. Permanently store change-controlrecords.

• It is a good practice to store the details of all key contacts, such as support contacts, supportnumbers, engineer details, and telephone and fax numbers. Having this information availableduring troubleshooting saves you time.

Fourth, understand the normal network behavior so you can be more effective at troubleshootingproblems.

• Monitor your network over a period of time sufficient to allow you to obtain statistics and data tosee patterns in the traffic flow, such as which devices are typically accessed or when peakusage times occur.

• Use a baseline analysis as an important indicator of overall network health. A baseline view ofnetwork traffic as it typically is during normal operation is a reference that you can compare to



network traffic data that you capture during troubleshooting. This should speed the process ofisolating network problems.



Chapter 4: Troubleshooting Tools

The WLAN 8100 series products support a range of protocols, utilities and diagnostic tools that youcan use to monitor and analyze traffic, capture and analyze data packets, trace data flows, viewstatistics, and manage event messages.

Certain protocols and tools are tailored for troubleshooting specific WLAN 8100 Series networktopologies. Other tools are more general in their application and can be used to diagnose andmonitor ingress and egress traffic.

This chapter describes the available troubleshooting tools and their applications.

Related LinksPort mirroring on page 12Port mirroring commands on page 13Port statistics on page 13Time domain reflectometer on page 13System logs on page 13IP Flow information export on page 14Remote packet capture on page 14Traffic monitoring on page 15

Port mirroringThe WLAN 8100 port mirroring feature helps you to monitor and analyze network traffic. Portmirroring requires one or more ports for mirroring and one for monitoring.

The mirror port allows both ingress and egress traffic. When port mirroring is enabled, a copy of theingress or egress packets on the mirrored port also flow through the monitoring port. This helps youobserve and analyze packet traffic on the monitoring port while it continues uninterrupted and flowsnormally through the mirror port. You can analyse packet traffic on the monitoring port using anetwork analyzer.

Related LinksTroubleshooting Tools on page 12



Port mirroring commandsYou can use the port mirroring commands to assist in diagnostics and information gathering.


Port statisticsUse port statistics commands to display information on received and transmitted packets at theports. The ingress and egress counts occur at the MAC layer. Count updates occur once everysecond.


Time domain reflectometerThe WLAN 8100 Series device is equipped with a time domain reflectometer (TDR). The TDRprovides a diagnostic capability to test connected cables for defects, such as short pin and pin open.You can obtain TDR test results from the CLI or the WMS.

The cable diagnostic tests only apply to Ethernet copper ports; fiber ports cannot be tested. You caninitiate a test on multiple ports at the same time. When you test a cable with the TDR, if the cablehas a 10/100 MB/s link speed, the link is broken during the test and restored only when the test iscomplete. TDR test does not affect the gigabit links.


System logsYou can use the syslog messaging feature of the WLAN 8100 series products to manage eventmessages. The WLAN 8100 series syslog software communicates with a server softwarecomponent named syslogd that resides on your management workstation.

The daemon syslogd is a software component that receives and locally logs, displays, prints, orforwards messages that originate from sources that are internal and external to the workstation. Forexample, syslogd software concurrently handles messages received from applications running onthe workstation, as well as messages received from an WLAN 8100 series device running in anetwork accessible to the workstation.

Related Links

Port mirroring commands



Troubleshooting Tools on page 12

IP Flow information exportThe WCS implements IP flow information e (IPFIX) for the wired ports. You can define flows basedon IP addresses and TCP/UDP ports, and collect statistics for these flows. The collected statisticsare exported to the IPFIX collector.

In Release 1.1, the only external collector supported is NetQOS. At this time, up to two collectorscan be supported. IPFIX data is exported from the switch in Netflow version 9 format. Data isexported using UDP port 9995.


Remote packet captureRemote packet capture enables live debugging to troubleshoot client related issues. It can also beused to monitor traffic in a wireless network. Remote packet capture enables you to capture packetson wireless interfaces on any AP in the mobility domain. You can use this feature to troubleshootwireless connectivity issues and identify the nature of the wireless traffic at different locations in thedeployment. You can monitor wireless traffic in general. For more information, see FeatureOverview for Avaya WLAN 8100, NN47251-102.

To enable remote packet capture, you typically configure a capture profile on the AMDC of themobility domain and then apply this profile to specific APs in the mobility domain. Each captureprofile supports multiple configuration parameters that specify the behavior of the capture. You canconfigure up to four capture profiles on the AMDC.

A single stream of packet capture between the remote capture device and observer host is called acapture instance. A remote capture device can have one capture instance per capture profile with amaximum of 4 capture instances.

A capture instance is started when a capture profile is applied to a AP using a start action.

A capture instance cannot be started when the configuration profiles are not synchronized in themobility domain. A capture instance that is not active can be restarted using a restart action.

A capture instance that is active can be stopped using a stop action.

Before starting the capture instance, you must install Wireshark on the observer host to captureframes on the observer host IP of the capture instance.

Wireshark is a packet analyzer with extensive capabilities to analyze various protocols and is freelyavailable for download from the internet. Wireshark version 1.6 or higher support decoding ofCAPWAP encapsulated data.

After you install Wireshark, start the capture stream for the capture instance. Wireshark displaysreceived packets from the capture stream on the configured UDP port for the capture instance.

Troubleshooting Tools



Wireshark can be configured to decode all packets received on the UDP port of the capture streamas CAPWAP data packets.

The UDP port that is used for CAPWAP capture stream to the observer host is configured in thecapture profile.

To troubleshoot wireless clients using remote packet capture, see Troubleshooting wireless clientsusing Remote Packet Capture on page 67.

Packet Capture failure scenarios• If a controller fails after the capture has been activated for APs managed by the failing

controller then all APs managed by the failing controller stop any active captures. The capturestatus information on the active mobile domain controller (A-MDC) removes the entries for theAPs managed by the failed controller.

• If the A-MDC fails then the backup mobility domain controller (B-MDC) takes over as A-MDC.In this case, the remote packet capture instance information of all managed APs that had anongoing capture is deleted.


Traffic monitoringTraffic monitoring is the collection and analysis of traffic flow and application related measurements.This involves collecting, storing, and analyzing flow and application measurements exported fromthe flow meters in the IP network, and provides access to the analyzed measurement. The collectionprocess is hosted by the flow collector-analyzer devices under the IPFIX architecture.


Traffic monitoring



Chapter 5: Configuring troubleshootingfeatures

This chapter describes methods and procedures necessary to configure RMON and IPFIX and themethods and procedures necessary to configure diagnostics and graphing.

Related LinksConfiguring Serviceability on page 16Configuring diagnostics and graphing on page 24

Configuring ServiceabilityThe following sections describe the methods and procedures necessary to configure RMON andIPFIX.

Related LinksConfiguring troubleshooting features on page 16Configuring RMON with the CLI on page 16Configuring IPFIX using CLI on page 21

Configuring RMON with the CLIThe following sections describe the CLI commands used to configure and manage RMON.

Related LinksConfiguring Serviceability on page 16Viewing RMON alarms on page 17Viewing RMON events on page 17Viewing RMON history on page 17Viewing RMON statistics on page 17Setting RMON alarms on page 18Deleting RMON alarm table entries on page 18Configuring RMON event log and traps on page 19Deleting RMON event table entries on page 19



Configuring RMON history on page 19Deleting RMON history table entries. on page 20Configuring RMON statistics on page 20Disabling RMON statistics on page 21

Viewing RMON alarmsAbout this taskUse the following procedure to view RMON alarms.

Procedure1. Enter Privileged Executive mode.

2. Use the show rmon alarm command to display information about RMON alarms.

Viewing RMON eventsAbout this taskUse the following procedure to display information regarding RMON events.


2. Enter the show rmon event command.

Viewing RMON historyAbout this taskUse this procedure to display information regarding the configuration of RMON history.


2. Enter the show rmon history [<port>] command.

Variable Definitions

Variable Definition<port> The specified port number for which RMON history

settings is displayed.

Viewing RMON statisticsAbout this taskUse the following procedure to display information regarding the configuration of RMON statistics.


Configuring Serviceability



2. Enter the show rmon stats command.

Setting RMON alarmsAbout this taskUse the following procedure to set

Procedure1. Enter Global Configuration mode.

2. Enter the rmon alarm <1-65535> <WORD> <1-2147483647> {absolute | delta}rising-threshold <-2147483648-2147483647> [<1-65535>] falling-threshold <-2147483648-2147483647> [<1-65535>] [owner <LINE>]command.


Parameter Description<1-65535> Unique index for the alarm entry.<WORD> The MIB object to be monitored. This object identifier can be an English

name.<1-2147483647> The sampling interval, in seconds.absolute Use absolute values (value of the MIB object is compared directly with

thresholds).delta Use delta values (change in the value of the MIB object between samples

is compared with thresholds).rising-threshold<-2147483648-2147483647 >[<1-65535>]

The first integer value is the rising threshold value. The optional secondinteger specifies the event entry to be triggered after the rising threshold iscrossed. If omitted, or if an invalid event entry is referenced, no event istriggered.

falling-threshold<-2147483648-2147483647 >[<1-65535>]

The first integer value is the falling threshold value. The optional secondinteger specifies the event entry to be triggered after the falling threshold iscrossed. If omitted, or if an invalid event entry is referenced, no event istriggered.

[owner <LINE>] Specify an owner string to identify the alarm entry.

Deleting RMON alarm table entriesAbout this taskUse the following procedure to delete RMON alarm table entries.


2. Enter the no rmon alarm [<1-65535>] command.

Configuring troubleshooting features




Variable Definition[<1-65535>] The number assigned to the alarm. If no number is

selected, all RMON alarm table entries are deleted.

Configuring RMON event log and trapsAbout this taskUse the following procedure to configure RMON event log and trap settings.


2. Enter the rmon event <1-65535> [log] [trap] [description <LINE>] [owner<LINE>] command.


Parameter Description<1-65535> Unique index for the event entry.[log] Record events in the log table.[trap] Generate SNMP trap messages for events.[description <LINE>] Specify a textual description for the event.[owner <LINE>] Specify an owner string to identify the event entry.

Deleting RMON event table entriesAbout this taskUse the following procedure to clear entries in the table.


2. Enter the no rmon event [<1-65535>] command to delete the entries.


Variable Definition[<1-65535>] Unique identifier of the event. If not given, all table

entries are deleted.

Configuring RMON historyAbout this taskUse the following procedure to configure RMON history settings.





2. Enter the rmon history <1-65535> <LINE> <1-65535> <1-3600> [owner<LINE>] command to configure the RMON history..


Parameter Description<1-65535> Unique index for the history entry.<LINE> Specify the port number to be monitored.<1-65535> The number of history buckets (records) to keep.<1-3600> The sampling rate (how often a history sample is collected).[owner <LINE>] Specify an owner string to identify the history entry.

Deleting RMON history table entries.About this taskUse this procedure to delete RMON history table entries.


2. Enter the no rmon history [<1-65535>] command to delete the entries.


Variable Definition[<1-65535>] Unique identifier of the event. If not given, all table

entries are deleted.

Configuring RMON statisticsAbout this taskUse this procedure to configure RMON statistics settings.


2. Enter the rmon stats <1-65535> <LINE> [owner <LINE>] command to configureRMON statistics.


Parameter Description<1-65535> Unique index for the stats entry.[owner <LINE>] Specify an owner string to identify the stats entry.




Disabling RMON statisticsAbout this taskUse this procedure to disable RMON statistics. If the variable is omitted, all entries in the table arecleared.


2. Enter the no rmon stats [<1-65535>] command to disable RMON statistics.


Variable Definition<1-65535> Unique index for the statistics entry. If omitted, all

statistics are disabled.

Configuring IPFIX using CLIThe following sections describe the commands used in the configuration and management of IPFlow Information Export (IPFIX) using the CLI.

Related LinksConfiguring Serviceability on page 16Configuring IPFIX collectors on page 21Enabling IPFIX globally on page 22Configuring unit specific IPFIX on page 22Enabling IPFIX on the interface on page 23Enabling IPFIX export through ports on page 23Deleting the IPFIX information for a port on page 23Viewing the IPFIX table on page 23

Configuring IPFIX collectorsAbout this taskThe ip ipfix collector command is used to configure IPFIX collectors. IPFIX collectors areused to collect and analyze data exported from an IPFIX compliant switch. In WLAN Release 1.1,the only external collector supported is NetQOS. At this time, up to two collectors can be supported.

IPFIX data is exported from the switch in Netflow version 9 format. Data is exported using UDP port9995.

IPFIX data is not load balanced when two collectors are in use. Identical information is sent to bothcollectors.

Use the following procedure to configure the IPFIX collectors.





2. Use the ip ipfix collector <unit_number> <collector_ip_address>command to configure the IPFIX collector.


Parameter Description<unit_number> The unit number of the collector. Currently up to two collectors are

supported so the values 1 or 2 are valid.<collector_ip_address> The IP address of the collector.

Enabling IPFIX globallyAbout this taskUse the following procedure to globally enable IPFIX on the switch.


2. Use the ip ipfix enable command to enable IPFIX on the switch.

Configuring unit specific IPFIXAbout this taskUse the following command to configure unit specific IPFIX parameters.


2. Use the ip ipfix slot <unit_number> [aging-interval <aging_interval>][export-interval <export_interval>] [exporter-enable] [template-refresh-interval <template_refresh_interval>] [template-refresh-packets <template_refresh_packets>] command to enable IPFIX on the switch.


Parameter Description<unit_number> The unit number of the collector. Currently up to two collectors are

supported so the values 1 or 2 are valid.<aging_interval> The IPFIX aging interval. This value is in seconds from 0 to 2147400.<export_interval> The IPFIX export interval. This interval is the value at which IPFIX data is

exported in seconds from 10 to 3600.<template_refresh_interval> The IPFIX template refresh interval. This value is in seconds from 300 to

3600.<template_refresh_packets> The IPFIX template refresh packet setting. This value is the number of

packets from 10000 - 100000.




Enabling IPFIX on the interfaceAbout this taskUse the following procedure to enable IPFIX on the interface.

Procedure1. Enter Interface Configuration mode.

2. Use the ip ipfix enable command to enable IPFIX on the interface.

Enabling IPFIX export through portsAbout this taskUse the following procedure to enable the ports exporting data through IPFIX.

Procedure1. Enter Interface Configuration mode.

2. Use the ip ipfix port <port_list> command to enable IPFIX on the interface.


Variable Definitionport-list Single or comma-separated list of ports.

Deleting the IPFIX information for a portAbout this taskUse the following procedure to delete the collected IPFIX information for a port.


2. Use the ip ipfix flush port <port_list> [export-and-flush] command todelete the collected IPFIX information for the port or ports.


Variable Definitionport-list Single or comma-separated list of ports.export-and-flush Export data to a collector before it is deleted.

Viewing the IPFIX tableAbout this taskUse the following procedure to display IPFIX data collected from the switch.





2. Use the show ip ipfix table <unit_number> sort-by <sort_by> sort-order<sort_order> display <num_entries> command view the IPFIX data.


Variable Definition<unit_number> The unit number of the collector. Currently up to two collectors are supported so

the values 1 or 2 are valid.<sort_by> The value on which the data is sorted. Valid options are:

• byte-count

• dest-addr

• first-pkt-time

• last-pkt-time

• pkt-count

• port

• protocol

• source-addr

• TCP-UDP-dest-port

• TCP-UDP-src-port

• TOS<sort_order> The order in which the data is sorted. Valid options are ascending and descending.<num_entries> The number of data rows to display. Valid options are:

• all

• top-10

• top-25

• top-50

• top-100

• top-200

Configuring diagnostics and graphingThe following sections describe the methods and procedures necessary to configure diagnosticsand graphing.

Related LinksConfiguring troubleshooting features on page 16System diagnostics and statistics using CLI on page 25




Network monitoring configuration using CLI on page 28

System diagnostics and statistics using CLIThe following sections describe the procedures you can use to perform system diagnostics andgather statistics using the CLI.

Related LinksConfiguring diagnostics and graphing on page 24Viewing port-statistics on page 25Displaying port operational status on page 26Validating port operational status on page 26Showing port information on page 27

Viewing port-statisticsAbout this taskUse this procedure to view the statistics for the port on both received and transmitted traffic.


2. Enter the show port-statistics [port <portlist>] command.WC8180#show port-statistics Port: 1--------Received Packets: 6338006 Multicasts: 1428257 Broadcasts: 4812 Total Octets: 464732046 FCS Errors: 0 Undersized Packets: 0 Oversized Packets: 0 Filtered Packets: 0 Pause Frames: 0Transmitted Packets: 12149510 Multicasts: 272137 Broadcasts: 2225 Total Octets: 1206701939 Collisions: 0 Single Collisions: 0 Multiple Collisions: 0 Excessive Collisions: 0 Deferred Packets: 0 Late Collisions: 0 Pause Frames: 0 Packets 64 bytes: 1700394 65-127 bytes: 14013526 128-255 bytes: 2640263 256-511 bytes: 11186 512-1023 bytes: 10363

Configuring diagnostics and graphing



1024-1518 bytes: 1245 1519-9216 bytes(Jumbo): 110539 Dropped On No Resources: 0

Related LinksSystem diagnostics and statistics using CLI on page 25


Variable Definitionport <portlist> The ports to display statistics for. When no port list is specified,

all ports are shown.

Displaying port operational statusAbout this taskUse this procedure to display the port operational status.

Important:If you use a terminal with a width of greater than 80 characters, the output is displayed in atabular format.


2. Enter the show interfaces [port list] verbose command. If you issue thecommand with no parameters the port status is shown for all ports.

3. Observe the CLI output.

Validating port operational statusAbout this taskUse the command show interfaces to validate port operational status.

A sample output is as follows:WC8180#show interfaces Status Auto Flow Port Trunk Admin Oper Link LinkTrap Negotiation Speed Duplex Control---- ----- ------- ---- ---- -------- ----------- -------- ------ -------1 Enable Down Down Enabled Enabled 2 Enable Down Down Enabled Enabled 3 Enable Up Up Enabled Enabled 100Mbps Full Disable 4 Enable Down Down Enabled Enabled 5 Enable Down Down Enabled Enabled 6 Enable Down Down Enabled Enabled 7 Enable Down Down Enabled Enabled 8 Enable Down Down Enabled Enabled 9 Enable Down Down Enabled Enabled 10 Enable Down Down Enabled Enabled 11 Enable Down Down Enabled Enabled 12 Enable Down Down Enabled Enabled 13 Enable Down Down Enabled Enabled 14 Enable Down Down Enabled Enabled 15 Enable Down Down Enabled Enabled




16 Enable Down Down Enabled Enabled 17 Enable Down Down Enabled Enabled 18 Enable Down Down Enabled Enabled 19 Enable Down Down Enabled Enabled 20 Enable Down Down Enabled Enabled 21 Enable Down Down Enabled Enabled 22 Enable Down Down Enabled Enabled 23 Enable Down Down Enabled Enabled 24 Enable Down Down Enabled Enabled 25 Enable Down Down Enabled Disabled 10Gbps Full Disable 26 Enable Down Down Enabled Disabled 10Gbps Full Disable

You can also use the show interfaces command to validate port operational status after VLACPor STP configuration.


Showing port informationAbout this taskPerform this procedure to display port configuration information.


2. Enter the show interfaces <portlist> config command.

3. Observe the CLI output.WC8180#show interfaces 1 config Port: 1 Trunk: Admin Status: Enable Oper Status: Down VLACP Oper Status: Down STP Oper Status: Disabled Link: Up LinkTrap: Enabled Autonegotiation: Enabled Speed: 100Mbbps Duplex: Full Flow Control: Disable Energy Saver: Disabled Oper Energy Saver: No Power Saving

*****VLAN interfaces configuration***** Filter Filter Untagged UnregisteredPort Frames Frames PVID PRI Tagging Name---- -------- ------------ ---- --- ------------- --------------1 Yes Yes 1 0 TagAll Port 1

*****VLAN ID port member configuration*****Port VLAN VLAN Name VLAN VLAN Name VLAN VLAN Name---- ---- ---------------- ---- ---------------- ---- ----------------1 15 VLAN1 20 mgmt 30 system 128 employee 129 voice 130 guest---- ---- ---------------- ---- ---------------- ---- ---------------- *****Spanning-tree port configurations*****




Port Trunk Participation Priority Path Cost State ---- ----- --------------- -------- --------- ----------1 Disabled


Network monitoring configuration using CLIThe following sections describe viewing and configuring network monitoring using the CLI.

Related LinksConfiguring diagnostics and graphing on page 24Viewing CPU utilization on page 28Viewing memory utilization on page 28Configuring the system log on page 29Configuring remote syslog logging for AP 8120 — on Linux on page 32Configuring remote syslog logging for AP 8120 — on Windows on page 33Configuring remote logging on page 34Configuring port mirroring on page 37

Viewing CPU utilizationAbout this taskUse this procedure to view the CPU utilization

Procedure1. Enter the Privileged Executive mode of the Avaya CLI.

2. Enter the show cpu-utilization command.

3. Observe the displayed information.

Sample output:WC8180#show cpu-utilization ---------------------------------------------------------------- CPU Utilization----------------------------------------------------------------

Unit 10 Sec, 1 Min, 10 Min, 60 Min, 24 Hrs, System Boot-Up----------------------------------------------------------------Host 9% 14% 15% 16% NA 16% WCP 3% 2% 2% 2% NA 1% WDP 1% 1% 1% 1% NA 7%

Viewing memory utilizationAbout this taskUse this procedure to view the memory utilization




Procedure1. Enter the Privileged Executive mode of the Avaya CLI.

2. Enter the show memory-utilization command.

3. Observe the displayed information.OL-AMDC#show memory-utilization --------------------------------------------------------- Memory Utilization (in MB)---------------------------------------------------------Unit Total Used Free Peak---------------------------------------------------------Host 1024 265 759 265 WCP 1632 1061 571 1062WDP 281 41 240 41

Configuring the system logThe following sections describe the CLI commands used in the configuration and management ofthe system log.

Related LinksNetwork monitoring configuration using CLI on page 28Displaying the system log on page 29Disabling the system log on page 30Configuring the system log on page 30Setting the system log to default on page 31Clearing the system log on page 31

Displaying the system logUse this procedure to display the configuration and the current contents of the system event log.

CLI Reference:WC8180(config)#show logging ?Show logging information system Show the contents of logging buffers wireless-controller Show logging information of wireless controller

Before you beginEnsure that you are in the Privileged Executive mode of the Avaya CLI.

Procedure1. Enter the command show logging system to view the contents of logging buffers.

Use the following command options to view the contents of logging buffers.WC8180(config)#show logging system ? config Display configuration of event logging critical Critical event informational Informational message




serious Serious event message <cr> WC8180(config)#show logging system critical ? informational Informational message serious Serious event message <cr> WC8180(config)#show logging system serious ? informational Informational message <cr>

2. Enter the command show logging wireless-controller to view logging informationof a wireless controller.

Use the following command options to view the logging information of a wireless controller.WC8180(config)#show logging wireless-controller ? volatile Display log messages in DRAMWC8180(config)#show logging wireless-controller volatile ? critical Critical event messages informational Informational messages serious Serious event messages <cr>

Disabling the system logUse this procedure to disable the system event log.

Before you beginEnter the global configuration mode of the Avaya CLI.

ProcedureEnter the command no logging to disable the system log.

Configuring the system logUse this procedure to configure the system event log.

CLI Reference:WC8180(config)#logging ? disable Disable the event log enable Enable the event log level The severity level of events that will be logged in DRAM nv-level The severity level of events that will be saved in NV storage remote Configure remote logging parameters volatile Configure options for logging to DRAM

Before you beginEnsure that you are in the Privileged Executive mode of the Avaya CLI.

Procedure1. Enter the command logging disable to disable the event log.

2. Enter the command logging enable to enable the event log.




3. Use the following command options to configure the severity level of events to be logged inDRAM:WC8180(config)#logging level ? critical Critical event informational Informational message none No events stored in volatile storage serious Serious event message

4. Use the following command options to configure the severity level of events to be saved inthe NV storage:WC8180(config)#logging nv-level ? critical Critical event none No events saved in NV storage serious Serious event message

5. Use the following command options to configure remote logging parameters:WC8180(config)#logging remote ? address Configure remote syslog address enable Enable remote logging level Configure remote logging level secondary-address Configure remote syslog address

6. Use the following command options to configure options for logging to DRAM:WC8180(config)#logging volatile ? latch Latch DRAM log when it is full overwrite Overwrite DRAM log when it is full

Setting the system log to defaultUse this procedure to restore default system log configuration.

Before you beginYou are in the Global configuration mode of the Avaya CLI.

Procedure1. Enter the command default logging to restore default system log configuration.

2. Enter the command default logging remote command to restore factory defaultremote logging parameters.

CLI reference:WC8180(config)#default logging ? remote Restore factory default remote logging parameters <cr>

Use the following command options to further configure default remote logging parameters:WC8180(config)#default logging remote ? address Restore factory default remote syslog address level Restore factory default remote logging level secondary-address Restore factory default second remote syslog address

Clearing the system logUse this procedure to clear the system log.




Before you beginEnter the global configuration mode of the Avaya CLI.

Procedure1. Use the command clear logging system [non-volatile] [nv] [volatile] to

clear the system log.

CLI reference:WC8180(config)#clear logging system ? non-volatile Clear log messages from NVRAM nv Clear log messages from NVRAM and DRAM volatile Clear log messages from DRAM <cr>

2. Use the following command options to clear log messages from NVRAM:WC8180(config)#clear logging system non-volatile ? critical Clear critical log messages serious Clear serious log messages <cr>

3. Use the command clear logging system nv to clear log messages from NVRAM andDRAM.

4. Use the following command options to clear log messages from DRAM:WC8180(config)#clear logging system volatile ? critical Clear critical log messages informational Clear informational log messages serious Clear serious log messages <cr>

Configuring remote syslog logging for AP 8120 — on LinuxAs part of remote syslog server configuration, you configure a part of the DHCP option 43 and thedhcpd.conf file using the following syslog options. Use the following procedure on a Linux server.

1. Edit dhcpd.conf (/root/dhcp.conf).

2. Configure option AVAYA-WC8120_AP syslog IP address as shown in the followingexample. Configuring syslog ports and code levels (code level 7 for Debug) are optional.

Note:

If you are debugging for a specific AP, as for example host debug_ap1 {, ensure youupdate the MAC address sub option for the IP address.

3. Restart dhcpd.

Example




Related LinksNetwork monitoring configuration using CLI on page 28

Configuring remote syslog logging for AP 8120 — on WindowsAs part of remote syslog server configuration, you configure the DHCP option 43. Use the followingprocedure on a Windows server.

Before you beginEnsure that DHCP is installed on the Windows server.

Procedure1. On Windows, navigate to Start, All Programs, Administrative Tools, DHCP.

2. Select DHCP, <Scope Name>, Scope Options.

The scope options are displayed on the right-hand-side pane.




3. Double click the 043 Vendor Specific Info option.

The Scope Options window displays.

a. In the Available Options pane, ensure that 043 Vendor Specific Info is selected.

b. In the Data entry pane, enter the following data.08 08 Avaya AP 01 04 IP Address of the Controller(04 Length of the IP Address)09 04 Syslog IP Address (04 length of the IP Address)10 02 Syslog Server Port 51411 01 Debug Log Level 7

Related LinksNetwork monitoring configuration using CLI on page 28

Configuring remote loggingYou can use the Avaya CLI to configure remote logging. The following sections describe thecommands to configure remote logging.




Related LinksNetwork monitoring configuration using CLI on page 28Disabling remote logging on page 35Enabling remote logging on page 35Setting the remote logging address on page 35Clearing the remote server IP address on page 36Setting the log severity on page 36Resetting the severity level on page 36Setting the default remote logging level on page 37

Disabling remote loggingAbout this taskUse this procedure to disable remote logging.

Procedure1. Enter the Global Configuration mode of the Avaya CLI.

2. Use the command no logging remote enable to disable remote logging.

3. (Optional) Use the following additional command options to disable other remote loggingparameters.WC8180(config)#no logging remote ? address Clear remote syslog address enable Disable remote logging level Clear remote logging level secondary-address Clear second remote syslog address

Enabling remote loggingUse this procedure to enable remote logging. By default, remote logging is disabled.

Procedure1. Enter Global Configuration mode of the Avaya CLI.

2. Enter the logging remote enable command to enable the use of a remote syslog serverfor logging.

Setting the remote logging addressUse this procedure to set the address of a remote server for the syslog.


2. Enter the logging remote address <A.B.C.D> command to set the address of theremote server for the syslog.

CLI reference:WC8180(config)#logging remote address ? A.B.C.D IP address of remote syslog server





Parameters and variables Description<A.B.C.D> Specifies the IP address of the remote server in dotted-decimal

notation. The default address is 0.0.0.0.

Clearing the remote server IP addressUse this procedure to clear the IP address of the remote server.


2. Enter the command no logging remote address command to clear the IP address ofthe remote syslog server.

Setting the log severityAbout this taskUse this command to set the severity level of the logs sent to the remote server.


2. Enter the logging remote level {critical | informational | serious |none} command to set the severity level of the logs that will be sent to the server.


Parameters and variables Description{critical | serious | informational | none} Specifies the severity level of the log messages to be sent to

the remote server:

• critical

• informational

• serious

• none

Resetting the severity levelAbout this taskUse this command to remove severity level setting


2. Enter the no logging remote level command to remove the severity level of the logsthat will be sent to the server. The level is set to none.




Setting the default remote logging levelAbout this taskUse this procedure to set the remote logging level to default.


2. Enter the default logging remote level command to sets the severity level of thelogs sent to the remote server. The default level is none.

Configuring port mirroringUse the following CLI commands to configure port mirroring.

Related LinksNetwork monitoring configuration using CLI on page 28Displaying the port-mirroring configuration on page 37Configure port-mirroring on page 37Disabling port-mirroring on page 39Displaying Many-to-Many port-mirroring on page 39Configuring Many-to-Many port-mirroring on page 39Disabling Many-to-Many port-mirroring on page 40

Displaying the port-mirroring configurationAbout this taskUse this procedure to display the existing port-mirroring configuration.


2. Enter the show port-mirroring command to display the port-mirroring configuration.

Configure port-mirroringAbout this taskUse this procedure to set the port-mirroring configuration


2. Enter the port-mirroring mode {disable | Xrx monitor-port <portlist>mirror-ports <portlist> | Xtx monitor-port <portlist> mirror-ports<portlist> | ManytoOneRx monitor-port <portlist> mirror-ports<portlist> | ManytoOneTx monitor-port <portlist> mirror-port-X<portlist> | ManytoOneRxTx monitor-port <portlist> mirror-port-X<portlist> | XrxOrXtx monitor-port <portlist> mirror-port-X<portlist> | XrxOrYtx monitor-port <portlist> mirror-port-X




<portlist> mirror-port-Y <portlist> | XrxYtxmonitor-port <portlist>mirror-port-X <portlist> mirror-port-Y <portlist> | XrxYtxOrYrxXtxmonitor-port <portlist> mirror-port-X <portlist> mirror-port-Y<portlist> | Asrc monitor-port <portlist> mirror-MAC-A <macaddr> |Adst monitor-port <portlist> mirror-MAC-A <macaddr> | AsrcOrAdstmonitor-port <portlist> mirror-MAC-A <macaddr> | AsrcBdst monitor-port <portlist> mirror-MAC-A <macaddr> mirror-MAC-B <macaddr> |AsrcBdstOrBsrcAdst monitor-port <portlist> mirror-MAC-A <macaddr>mirror-MAC-B <macaddr>} command to display the port-mirroring configuration.


Parameter Descriptiondisable Disables port-mirroring.monitor-port Specifies the monitor port.mirror-port-X Specifies the mirroring port X.mirror-port-Y Specifies the mirroring port Y.mirror-MAC-A Specifies the mirroring MAC address A.mirror-MAC-B Specifies the mirroring MAC address B.portlist Enter the port numbers.ManytoOneRx Many to one port mirroring on ingress packets.ManytoOneTx Many to one port mirroring on egress packets.ManytoOneRxTx Many to one port mirroring on ingress and egress traffic.Xrx Mirror packets received on port X.Xtx Mirror packets transmitted on port X.XrxOrXtx Mirror packets received or transmitted on port X.XrxYtx Mirror packets received on port X and transmitted on port Y.

This mode is not recommended for mirroring broadcast andmulticast traffic.

XrxYtxOrXtxYrx Mirror packets received on port X and transmitted on port Y orpackets received on port Y and transmitted on port X.

XrxOrYtx Mirror packets received on port X or transmitted on port Y.macaddr Enter the MAC address in format H.H.H.Asrc Mirror packets with source MAC address A.Adst Mirror packets with destination MAC address A.AsrcOrAdst Mirror packets with source or destination MAC address A.AsrcBdst Mirror packets with source MAC address A and destination

MAC address B.AsrcBdstOrBsrcAdst Mirror packets with source MAC address A and destination

MAC address B or packets with source MAC address B anddestination MAC address A.




Disabling port-mirroringAbout this taskUse this procedure to disable port-mirroring

Procedure1. Enter Global Configuration mode

2. Enter the no port-mirroring command to disable port-mirroring.

Displaying Many-to-Many port-mirroringAbout this taskUse this procedure to display Many-to-Many port-mirroring settings

Procedure1. Enter Privileged Executive mode

2. Enter the show port-mirroring command.

3. Observe the displayed information.

Configuring Many-to-Many port-mirroringAbout this taskUse this procedure to configure Many-to-Many port-mirroring


2. Enter the port-mirroring <1-4> allow-traffic mode {disable | Adst |Asrc | AsrcBdst | AsrcBdstOrBsrcAdst | AsrcOrAdst | ManyToOneRx |ManyToOneRxTx | ManyToOneTx | Xrx | XrxOrXtx | XrxOrYtx | XrxYtx |XrxYtxOrYrxXtx | Xtx} command.

3. Enter the command from step 2 for up to four instances.


Variable Valuedisable Disable mirroring.Adst Mirror packets with destination MAC address AAsrc Mirror packets with source MAC address A.AsrcBdst Mirror packets with source MAC address A and

destination MAC address B.AsrcBdstOrBsrcAdst Mirror packets with source MAC address A and

destination MAC address B or packets with sourceMAC address B and destination MAC address A.

AsrcOrAdst Mirror packets with source or destination MACaddress A.




Variable ValueManyToOneRx Mirror many to one port mirroring on ingress packets.ManyToOneRxTx Mirror many to one port mirroring on ingress and

egress packets.ManyToOneTx Mirror many to one port mirroring on egress packets.Xrx Mirror packets received on port X.XrxOrXtx Mirror packets received on port X and transmitted on

port Y.XrxYtx Mirror packets received on port X and transmitted on

port Y.XrxYtxOrYrxXtx Mirror packets received on port X and transmitted on

port Y or packets received on port Y and transmittedon port X.

Xtx Mirror packets received on port X or transmitted onport Y

Disabling Many-to-Many port-mirroringAbout this taskUse this procedure to disable Many-to-Many port-mirroring


2. Enter the port-mirroring [<1-4>] mode disable or no port-mirroring[<1-4>] command to disable a specific instance.

3. Enter the no port-mirroring command to disable all instances.


Variable Definition<1-4> The port-mirroring instance.




Chapter 6: General diagnostic tools

The WLAN 8100 series device has diagnostic features available with the command line interface(CLI), WLAN Management System (WMS) and the Enterprise Device Manager (EDM). You can usethese diagnostic tools to help you troubleshoot operational and configuration issues. You canconfigure and view files (such as software image files and reports), view and monitor port statistics,trace a route, run loopback and ping tests, test the switch fabric, and view the address resolutiontable.

You can access the Avaya CLI using either a direct console connection to the switch or by using theTelnet or SSH protocols to connect to the switch remotely.

You can use the WMS in cases where the troubleshooting steps require corroborating information toensure diagnosis. The WMS is now stabilized and vastly improved with respect to performance,reliability of the data displayed and consistency, to create a better user experience. The WMSprovides enhanced:

• monitoring capabilities, enhanced user experience with the provision to perform domain-wideactions, and a consistent look-and feel

• troubleshooting or diagnostics• reporting capabilities

Related LinksCLI command modes on page 41Wireless Management System on page 42Virtual link aggregation control protocol (VLACP) on page 42

CLI command modesThe CLI has five major command modes. Each mode supports a specific set of commands. Thecommand set of a higher privilege mode is a superset of a lower privilege mode. That is, all lowerprivilege mode commands are accessible when using a higher privilege mode.

The command modes are as follows:

• User EXEC mode: The User EXEC mode (also referred to as exec mode) is the default CLIcommand mode. User EXEC is the initial mode of access when the switch is first turned on.User EXEC mode provides a limited subset of CLI commands. This mode is the mostrestrictive CLI mode and supports few commands.

• Privileged EXEC mode: The Privileged EXEC mode (also referred to as privExec mode)enables you to perform basic switch-level management tasks, such as downloading software



images, setting passwords, and booting the switch. Privileged EXEC mode is an unrestrictedmode that allows you to view all settings on the switch, and if you are logged in with writeaccess, it also allows you to access all configuration modes and commands that affectoperation of the switch (such as downloading images and rebooting).

• Global configuration mode: The Global Configuration mode (also referred to as config mode)enables you to perform general configuration for the switch such as IP address, SNMPparameters, Telnet access, and VLANs.

• Interface configuration mode: The Interface Configuration mode (also referred to as config-if mode) enables you to configure parameters for each port or VLAN, such as speed, duplexmode, and rate-limiting.

Related LinksGeneral diagnostic tools on page 41

Wireless Management SystemThe Wireless Management System (WMS) is a web-based interface that you can use to plan,configure, deploy, and monitor the WLAN solution and its users.

Access control for WMS users is classified based on the following predefined roles:

• Security administrator (ROLE_SECURE_ADMIN): Has full access control and can createusers, delete users, and set permissions.

• Configuration administrator ( ROLE_ADMIN ): Has privileges to define and applyconfigurations but does not have access control and user creation privileges.

• Monitoring user (ROLE_USER): Only has monitoring privileges. Does not have configurationor access control privileges.


Virtual link aggregation control protocol (VLACP)Virtual link aggregation control protocol (VLACP) is a Layer 2 handshaking protocol providing end-to-end failure detection between two physical Ethernet interfaces. This protocol allows the switch todetect unidirectional or bidirectional link failures.

With VLACP, far-end failures can be detected allowing multilink trunks (MLT) to fail over properlywhen end-to-end connectivity is not guaranteed for certain links in an aggregation group.

VLACP is configured for each port. The port can be an individual port or member of MLT. For properVLACP operation there must be a logical point to point connection (L2 tunnel) between twoendpoints. VLACP does not work for point-to-multipoint connections. On VLACP enabled ports,VLACPDUs are sent periodically. If PDUs are not received on a particular link, that link is broughtdown after a configurable timeout period. You can also configure the destination MAC address.

General diagnostic tools




Virtual link aggregation control protocol (VLACP)



Chapter 7: Initial Troubleshooting

The types of problems that typically occur with networks involve connectivity and performance. It isusually best to follow the OSI network architecture layers. Confirm that the physical environment,such as the cables and module connections, is operating without any failures before moving up tothe network and application layers.

Gather informationBefore contacting Technical Support, you must gather information that can help the TechnicalSupport personnel. This includes the following information:

• Default configuration of the switch: Use the show running-config command.

• System status: Use the command show tech. This command displays technical informationabout the system status, as well as information about the hardware, software, and switchoperation. This command displays more information than the similar show sys-infocommand.

• Information about past events: For more information, review the log files.• The software version that is running on the device. Use the commands show sys-info orshow system verbose to display the software version that is running.

Sample output of the show sys-info command:WC8180#show sys-info Operation Mode: SwitchMAC Address: 00-24-B5-1F-A8-00Reset Count: 157Last Reset Type: Software DownloadPower Status: Primary PowerAutotopology: EnabledPluggable Port 13: SXPluggable Port 14: SXPluggable Port 15: NonePluggable Port 16: NonePluggable Port 17: NonePluggable Port 18: NonePluggable Port 19: NonePluggable Port 20: NonePluggable Port 21: NonePluggable Port 22: NonePluggable Port 23: NonePluggable Port 24: NonePluggable Port 25: NonePluggable Port 26: NoneBase Unit Selection: Base unit using rear-panel switch



sysDescr: Wireless LAN Controller WC8180 HW:00 FW:1.0.2.0 SW:v3.0.0.058 Mfg Date:20100329 HW Dev:noneSerial #: LBNNTMJPWB0025 Operational license: Base software Installed license: Base software sysObjectID: 1.3.6.1.4.1.45.3.77.1sysUpTime: 1 day, 01:47:52 sysNtpTime: SNTP not synchronized.sysRtcTime: Tuesday 2013/07/30 14:34:33sysServices: 6 sysContact: sysName: OL-AMDC sysLocation: Stack sysAssetId: Unit sysAssetId: OL-AMDC#

Sample output of the show system verbose command:WC8180#show system verbose System Information: Operation Mode: Switch MAC Address: 00-24-B5-1F-A8-00 Reset Count: 157 Last Reset Type: Software Download Autotopology: Enabled sysObjectID: 1.3.6.1.4.1.45.3.77.1 sysUpTime: 1 day, 02:01:20 sysNtpTime: SNTP not synchronized. sysRtcTime: Tuesday 2013/07/30 14:48:00 sysServices: 6 sysContact: sysName: OL-AMDC sysLocation: Stack sysAssetId: Unit sysAssetId: Operational license: Base software Installed license: Base softwareUnit #1: Switch Model: WC8180 Pluggable Port 13: (13) SX Pluggable Port 14: (14) SX Pluggable Port 15: (15) None Pluggable Port 16: (16) None Pluggable Port 17: (17) None Pluggable Port 18: (18) None Pluggable Port 19: (19) None Pluggable Port 20: (20) None Pluggable Port 21: (21) None Pluggable Port 22: (22) None Pluggable Port 23: (23) None Pluggable Port 24: (24) None Pluggable Port 25: (25) None Pluggable Port 26: (26) None Hardware Version: 00 Firmware Version: 1.0.2.0 Software Version: v3.0.0.058 Serial Number: LBNNTMJPWB0025 Manufacturing Date: 20100329 Power Status: Primary Power Fan #1 Status: Normal Fan #2 Status: Normal Fan #3 Status: Normal Fan #4 Status: Normal

Gather information



• Network topology diagram: Get an accurate and detailed topology diagram of your networkthat shows the nodes and connections. Your planning and engineering function should havethis diagram.

• Information about recent system changes: Find out about recent changes or upgrades toyour system, your network, or custom applications (for example, has the configurationchanged ?). Get the date and time of the changes, and the names of the persons who madethem. Get a list of events that occurred prior to the trouble, such as an upgrade, a LAN change,increased traffic, or installation of new hardware.

• Connectivity information: When connectivity problems occur, get information on at least fiveworking source and destination IP pairs and five IP pairs with connectivity issues. To do this,use these commands:- show running-config- show port-statistics <port>

Initial Troubleshooting



Chapter 8: Troubleshooting WLAN

This chapter describes procedures to help you troubleshoot Wireless LAN (WLAN) operations andissues regarding the WLAN management system.

Related LinksTroubleshooting Wireless LAN Management System issues on page 47Troubleshooting Layer 2 and Layer 3 issues on page 49Troubleshooting a failed configuration restore (from an ascii file) on a domain controller onpage 50Troubleshooting AP related issues on page 50Troubleshooting client-related issues on page 55Troubleshooting wireless clients using Remote Packet Capture on page 67Troubleshooting the E911 feature on page 71

Troubleshooting Wireless LAN Management Systemissues

This section details how to troubleshoot Wireless LAN Management System (WMS) browser,monitoring screens or dashboard timestamp issues.

Problem description and symptomsYou can encounter one of the following issues when accessing the WMS screens:

• when accessing the WMS screens, the browser does not respond to user requests• when accessing the WMS using the WMS IP address in the address bar, the browser displays

a completely blank screen

You can encounter the following issues on the WMS monitoring screens or dashboard timestamps:• Monitoring screens or Dashboard timestamps show up in red and display Update attemptat <HH:MM:SS> Failed.

• When trying to import, add or initiate actions for any devices, you receive the error Failed tocontact target device via SNMP@ <IP: port no>.

What to checkIf one of the two WMS browser issue arises, check whether the browser cache memory utilization isdisproportionately large when compared to the available disk memory. This disproportion can slow



browser operation or cause the browser to stop processing requests. To check this setting inInternet Explorer and Firefox, follow the appropriate steps provided.

For Internet Explorer1. In Internet Explorer, from the Tools menu go to Internet Options, General.2. In the Browsing History area of the General tab click Settings.3. In the Temporary Internet Files and History Settings dialog, in the Check disk space to use

field verify that the amount of memory provided is available in the hard drive. It isrecommended that you use a value that is within the range suggested by the OS.

4. In the Temporary Internet Files and History Settings dialog, in the Days to keep pages inhistory field, it is recommended that you keep a history of a couple of weeks of data. Therecommended value for this field is 14 days.

For Firefox1. From the Firefox menu, go to Options, Privacy.2. In the Privacy tab, in the History area choose Remember History from the drop-down list.

For issues with WMS Monitoring Screens or Dashboard timestamps1. Check reachability [using PING/TRACEROUTE] from the WMS server to the Target devices

(WC/WCP/WSP).2. Check the routing table on the WMS server for multiple default routes.3. Check if HTTP port number on the WC/WCP has been changed.4. Check if HTTPS is configured on the WC/WCP along with a static DNS address configured

on any one of the interfaces of WMS server.

Recommended actionComplete the procedure for your browser to clear the browser cache and resolve the WMS browserissue.

For Internet Explorer1. From the Tools menu go to Internet Options, General.2. In the Browsing history area click Delete.3. In the Delete Browsing History dialog, select the following options:

a. Temporary Internet Filesb. Cookiesc. History

4. Click Delete.

For Firefox1. From the Firefox menu, go to Options, Privacy.2. Click the Clear your recent history link.

Troubleshooting WLAN



Note:If the History memory is set to Remember nothing in the drop-down list, no action isrequired.

3. In the Clear All History dialog, in the Time range to clear drop-down list, select Everything.4. Click the Details button and select the following options to clear:

a. Browsing & Download Historyb. Cookiesc. Cache

For issues with WMS Monitoring Screens or Dashboard timestamps1. If reachability is broken, make the WMS server reachable to WC/WCP/WSP devices.2. If multiple default routes are present, make sure it has only one default address.3. If HTTP port number on the WC/WCP has changed, add or edit the device credentials of the

WC/WCP in WMS on the Administration, Device Credentials page. This ensures that theHTTP port configured on the WMS is the same as that of the WC/WCP.

4. If you have a static DNS address configured, either change the static DNS to a dynamicDNS IP address or change the HTTPS mode to HTTP on WC/WCP.

Related LinksTroubleshooting WLAN on page 47

Troubleshooting Layer 2 and Layer 3 issuesAbout this taskPerform the following procedure to troubleshoot Layer 2 and 3 issues.

Procedure1. Log into the controller.

2. Press CTRL + Y on the keyboard to enter the console menu.

3. Select IP Configuration/Setup from the console menu to check the controller IPconfiguration.

4. Press CTRL + R to return to the console menu.

5. Select SNMP Configuration from the console menu to check the controller SNMPconfiguration.


7. Select Switch Configuration from the console menu.

8. Use the options in this menu to track the various aspects of switch configuration.


Troubleshooting Layer 2 and Layer 3 issues



10. Select Spanning Tree Configuration from the console menu.

11. Use the options in this menu to track the various aspects of the spanning tree configuration.


13. Select Command Line Interface from the menu.

14. Type the enable command to enter Privileged mode.

15. Use the command show ip to view the IP address configuration.

16. Use the command ping <ip_address> to ping another device on the network.

17. Use the command show wireless to view the overall status of the wireless system.


Troubleshooting a failed configuration restore (from anascii file) on a domain controller

When you restore configuration on a controller from an ascii backup file (for example after a factoryreset), the restore fails, if VLANs in the backup file already exist on the controller.

During the restore, the identical VLAN does not get configured on the controller and the restoreaborts thereafter.

To overcome this problem, perform one of the following:

• Manually edit the ascii configuration backup file to remove those VLANs that already exist onthe controller and then perform the restore.

• Restore from a binary configuration back up file, if available.


Troubleshooting AP related issuesAbout this taskPerform the following procedure to troubleshoot access point (AP) related issues.

Procedure1. Log into the controller.






4. Enter the enable command to enter the Privileged mode of the Avaya CLI.

5. Use the command show wireless to view the overall status of the wireless system.

Sample output:WCP8180#show wireless Operation Mode : WCP Status : Enabled Interface IP : 30.1.1.51 TCP/UDP base port : 61000 Base MAC Address : 58:16:26:FD:F9:00

6. Use the command show wireless domain ap database to view information aboutaccess points configured for the wireless domain.

Sample output (Unified Access):WCP8180#show wireless domain ap databaseTotal number of entries in AP database = 4---------------------------------------------------------------- Profile/ Radio 1 Radio 2 Preferred PreferredAP MAC Country Channel Channel WCP WSP ----------------- ------- ------- ------- ------------ --------00:10:20:20:30:10 10/US Auto Auto 30.1.1.51 1.1.1.100:10:20:20:30:50 10/US 60 1 30.1.1.51 0.0.0.000:10:20:20:30:90 10/US Auto Auto 30.1.1.51 0.0.0.0----------------------------------------------------------------

Sample Output (Overlay):WC8180#show wireless domain ap databaseTotal number of entries in AP database = 3---------------------------------------------------------- Profile/ Radio 1 Radio 2 PreferredAP MAC Country Channel Channel WC----------------- ------- ------- ------- ---------------00:10:20:20:30:10 10/US Auto Auto 30.1.1.5100:10:20:20:30:50 10/US 60 1 30.1.1.5100:10:20:20:30:90 10/US Auto Auto 30.1.1.51----------------------------------------------------------

7. Use the command show wireless domain ap discovered to view access points thathave been discovered. Access points listed here must eventually be added to the DomainAP database to be managed by the controller of the domain.

Sample output:WC8180#show wireless domain ap discoveredTotal number of discovered APs = 2----------------------------------------------------------------------AP MAC AP IP AP Model Country Reason----------------- ------------ ------- ------ --------------------00:1B:4F:69:F5:20 172.16.3.35 AP8120 TW Not present in AP DB2C:F4:C5:98:75:C0 172.16.3.36 AP8120 DE Not present in AP DB----------------------------------------------------------------------

Observe the Reason column to understand why the AP is in the discovered state. Thefollowing are valid reason codes:

• Not present in AP DB

Troubleshooting AP related issues



• Mismatched country code• Mismatched AP model• No matching AP profile• Max-Domain-WSP-Capacity

8. Use the following commands to diagnose why an AP that is in the network is not discoveredby the AMDC.

a. On the AMDC check the TCP/UDP base port using the command show wireless.The default port is 61000.

Sample output (Overlay):WC8180#show wireless Operation Mode : WC Status : Enabled Interface IP : 192.171.0.56 TCP/UDP base port : 61000 Base MAC Address : 00:24:B5:1F:A8:00 Tunnel Path MTU : 1424

Sample Output (Unified Access)WCP8180#show wireless Operation Mode : WCP Status : Enabled Interface IP : 192.171.0.57 TCP/UDP base port : 61000 Base MAC Address : 58:16:26:FD:F9:00

b. On the AP, check the DHCP option 43 configuration.c. Ensure that both the port numbers match. Otherwise, the AP cannot be discovered.

9. Use the command show wireless ap status to display all access points that are part ofthe wireless domain and also information on the managing controller.

Sample output (Unified Access):WCP8180#show wireless ap statusTotal APs: 1, Managed APs: 1, Failed APs: 0 -----------------------------------------------------------------------AP MAC WCP IP WSP IP WCP WSP Need Img Status Status Upgrd----------------- ------------ --------------- ---------- ----------70:38:EE:89:C7:E0 30.1.1.51 1.1.1.1 Managed Connected Yes-----------------------------------------------------------------------

Sample output (Overlay)WC8180#show wireless ap statusTotal APs: 1, Managed APs: 1, Failed APs: 0----------------------------------------------------------------------AP MAC AP IP Controller IP Status Need Image Upgrade----------------- ------------ -------------- ---------- ----------00:1B:4F:69:F0:80 172.16.3.33 30.1.1.51 Managed No---------------------------------------------------------------------

10. Use the command show wireless ap status <ap_mac_address> detailcommand to display detailed information about each AP that is a part of the wireless domain.




Sample Output (Unified Access):WCP8180# show wireless ap status 70:38:EE:89:C7:E0 detail---------------------------------------------------------------AP (MAC=70:38:EE:89:C7:E0) IP Address : 172.16.7.14 WCP Status : Managed WSP Status : Connected WCP Assignment-Method : Least-Load WSP Assignment-Method : Least-Load AP Label : Hardware Type : Avaya AP8120-O Software Version : 2.0.0.077 Serial Number : 12SK06400009 Location : Country Code : US Band Plan : FCC Locale : US/40 Age (since last update) : 0d:00:00:01 System Up Time : 1:00:49:05 Discovery Reason : Controller IP via DHCP Managing Controller : Local Controller WCP System IP Address : 30.1.1.51 Profile Id : 23 WCP Managed Time : 0d:00:08:46 WSP System IP Address : 1.1.1.1 WSP Connected Time : 0d:00:09:20 Profile Name : Outdoor-US Configuration Apply Status : Success Authenticated Clients : 0 Configuration Failure Error : Reset status : Not Started Code Download Status : Not Started Image Upgrade Needed : Yes Ap Techdump Status : Not Started---------------------------------------------------------------

Sample output (Overlay):WC81810#show wireless ap status detailTotal APs: 1, Managed APs: 1, Failed APs: 0-------------------------------------------------------AP (MAC=00:1B:4F:69:F0:80) IP Address : 172.16.3.33 Status : Managed WC Assignment-Method : Least-Load AP Label : Hardware Type : Avaya AP8120 Software Version : 2.0.0.075 Serial Number : LBNNTMJXAD08J2 Location : Country Code : TW Band Plan : APL3 Locale : TW/3 Age (since last update) : 0d:00:00:03 System Up Time : 0d:17:03:56 Discovery Reason : IP Poll Managing Controller : Local Controller WC System IP Address : 30.1.1.51 WC Managed Time : 0d:00:21:34 Profile Id : 1 Profile Name : Default Configuration Apply Status : Success Authenticated Clients : 0 Configuration Failure Error :

Troubleshooting AP related issues



Reset status : Not Started Code Download Status : Not Started Image Upgrade Needed : No Ap Techdump Status : Not Started--------------------------------------------------------

11. Use the command show wireless controller status to determine the current statusof the wireless controller. This command also indicates if the controller is the Active orBackup Mobility Domain Controller (MDC).

Sample output:WCP8180#show wireless controller status MDC-Capable : Enabled Domain Role : Active MDC MDC IP Address : 192.171.0.57 Max. # Managed APs : 512 Max. # Managed WSPs : 16 Total APs : 1 Total Managed APs : 1 Total Managed Switches : 1 Total Discovered APs : 0 Total Connection Failed APs : 0 Total Clients : 0 Total Authenticated Clients : 0 WLAN Utilization : 19 % Total # of TSPEC Voice Streams : 0 Total # of TSPEC Video Streams : 0 Total # of TSPEC Stream Clients : 0 Total # of TSPEC Stream Roaming Clients : 0 Stored Primary AP Image Version : 2.0.0.078 Stored Secondary AP Image Version : 2.0.0.028 # of APs Required Image Upgrade : 1 All AP Image Update Status : None Status of All AP Reset : None Controller Base Mac Address : 58:16:26:FD:F9:00

12. Use the command show wireless ap radio tspec-status to display AvailableAdmission Capacity on a per User Priority or per Access Category basisinformation in Beacon and Probe Response messages.

Sample output:wc1#show wireless ap radio tspec-status

AP MAC Address:: 00:1B:4F:69:F0:80 Radio Interface::1 Traffic Type::VoiceOperation Status :DisabledActive Traffic Streams :0Traffic Stream Clients: :0Traffic Stream Roaming Clients :0Medium Time Admitted :0Medium Time Unallocated :0Medium Time Roaming Unallocated :0

AP MAC Address::00:1B:4F:69:F0:80 Radio Interface::1 Traffic Type::VideoOperation Status :DisabledActive Traffic Streams :0Traffic Stream Clients: :0Traffic Stream Roaming Clients :0Medium Time Admitted :0Medium Time Unallocated :0Medium Time Roaming Unallocated :0




13. Use the command show wireless switch peer-device to view the status of theaccess tunnel between the AP and the controller.

Sample output:WC8180#show wireless switch peer-device---------------------------------------------------------------------------Device Peer MAC Peer Address Peer Port Status TunnelID------- ----------- -------------- --------- ------ --------WC81xx CC:F9:54:EB:0D:00 192.171.0.60 61012 Up 00006AP81XX 00:1B:4F:6C:1B:A0 172.16.7.11 61012 Up 00002AP81XX 58:16:26:AC:63:60 172.16.7.12 61012 Up 00001AP81XX 70:38:EE:89:C7:E0 172.16.7.14 61012 Up 00003---------------------------------------------------------------------------

14. Use the command show wireless client tspec-status to display the currentTSPEC inactivity level.

15. Use the following command to view any unmanaged APs in the domain:WC8180#show wireless domain ap unmanaged -----------------------------------------------------AP MAC Address AP IP Address Status ----------------- --------------- -----------------00:1B:4F:6C:1B:00 0.0.0.0 Unmanaged 00:1B:4F:6C:1B:01 0.0.0.0 Unmanaged 00:1B:4F:6C:1B:02 0.0.0.0 Unmanaged 00:1B:4F:6C:1B:03 0.0.0.0 Unmanaged 00:1B:4F:6C:1B:04 0.0.0.0 Unmanaged

Use the command show logging wireless-controller volatile to view thecontroller log messages for further information on these APs.


Troubleshooting client-related issuesAbout this taskPerform the following procedure to troubleshoot client-related issues.

Procedure1. Log onto the controller.



4. Type the enable command to enter Privileged mode.

5. Use the command show wireless ap status to view the overall status of registeredaccess points.

Troubleshooting client-related issues



Sample output (Unified Access):WCP8180#show wireless ap statusTotal APs: 1, Managed APs: 1, Failed APs: 0 -----------------------------------------------------------------------AP MAC WCP IP WSP IP WCP WSP Need Img Status Status Upgrade----------------- ------------ --------------- ---------- ----------70:38:EE:89:C7:E0 30.1.1.51 1.1.1.1 Managed Connected Yes-----------------------------------------------------------------------

Sample output (Overlay)WC8180#show wireless ap statusTotal APs: 1, Managed APs: 1, Failed APs: 0----------------------------------------------------------------------AP MAC AP IP Controller IP Status Need Image Upgrade----------------- ------------ -------------- ---------- ----------00:1B:4F:69:F0:80 172.16.3.33 30.1.1.51 Managed No---------------------------------------------------------------------

6. Use the command show wireless ap status <ap_mac_address> detail to viewdetailed information about individual access points.

Sample Output (Unified Access):WCP8180# show wireless ap status 70:38:EE:89:C7:E0 detail---------------------------------------------------------------AP (MAC=70:38:EE:89:C7:E0) IP Address : 172.16.7.14 WCP Status : Managed WSP Status : Connected WCP Assignment-Method : Least-Load WSP Assignment-Method : Least-Load AP Label : Hardware Type : Avaya AP8120-O Software Version : 2.0.0.077 Serial Number : 12SK06400009 Location : Country Code : US Band Plan : FCC Locale : US/40 Age (since last update) : 0d:00:00:01 System Up Time : 1:00:49:05 Discovery Reason : Controller IP via DHCP Managing Controller : Local Controller WCP System IP Address : 30.1.1.51 Profile Id : 23 WCP Managed Time : 0d:00:08:46 WSP System IP Address : 1.1.1.1 WSP Connected Time : 0d:00:09:20 Profile Name : Outdoor-US Configuration Apply Status : Success Authenticated Clients : 0 Configuration Failure Error : Reset status : Not Started Code Download Status : Not Started Image Upgrade Needed : Yes Ap Techdump Status : Not Started---------------------------------------------------------------




Sample output (Overlay):WC81810#show wireless ap status detailTotal APs: 1, Managed APs: 1, Failed APs: 0-------------------------------------------------------AP (MAC=00:1B:4F:69:F0:80) IP Address : 172.16.3.33 Status : Managed WC Assignment-Method : Least-Load AP Label : Hardware Type : Avaya AP8120 Software Version : 2.0.0.075 Serial Number : LBNNTMJXAD08J2 Location : Country Code : TW Band Plan : APL3 Locale : TW/3 Age (since last update) : 0d:00:00:03 System Up Time : 0d:17:03:56 Discovery Reason : IP Poll Managing Controller : Local Controller WC System IP Address : 30.1.1.51 WC Managed Time : 0d:00:21:34 Profile Id : 1 Profile Name : Default Configuration Apply Status : Success Authenticated Clients : 0 Configuration Failure Error : Reset status : Not Started Code Download Status : Not Started Image Upgrade Needed : No Ap Techdump Status : Not Started--------------------------------------------------------

7. Use the command show wireless ap-profile network to view information about thecorrelation between network and AP profiles.

Note:

The AMDC does not show the ap-profile status as associated if the AP assigned tothat ap-profile is managed by a peer controller. Check the associated status from thepeer.

Sample output:WCP8180#show wireless ap-profile network--------------------------------------------------------------------AP Profile Id Radio Id VAP Id Network Profile Id Radio Operation------------- -------- ------ ------------------ --------------- 1 1 1 1 On 1 2 1 1 On

8. Use the command show wireless network-profile <profile_number> to viewinformation about configured network profiles.

Sample output:WCP8180#show wireless network-profile 2-------------------------------------------------------------------------Id Profile Name Mobility VLAN Security Mode Captive Portal--- ------------------- ------------------- -------------- -------------- 2 NP-staff MV-staff open Disabled-------------------------------------------------------------------------




To view detailed information on a configured network profile, use the command showwireless network-profile <profile_number> detail.

Sample output:WC8180#sh wireless network-profile 2 detail Network Profile ID: 2 Name : network_profile2 SSID : rpc2 Hide SSID : No Mobility Vlan Name : mob-client Probe Request : Enabled Captive Portal Mode : Disabled User Validation : open Captive Portal Profile Id : 0 Local User Group : Default RADIUS Authentication Profile Name : RADIUS Accounting Profile Name : RADIUS Accounting Mode : Disabled Security Mode : open MAC Validation : Disabled Wireless ARP Suppression : Disabled Radius offload : Disabled

9. Use the command show wireless switch vlan-map to view information about thecorrelation between wired and wireless VLANs.

Note:

This command is applicable only in Overlay deployments.

Sample output:WC8180# show wireless switch vlan-map--------------------------------------------------------------------------Mobility VLAN Name LVID State Role WCP-V Admin Mapped------------------- ----- ----- ---- ----- ------------MV_EMP 0 Active None Yes NoMV_VOICE 0 Active None Yes NoMV_GUEST 70 Active Server Yes Yesdefault-MVLAN 0 Active None Yes No--------------------------------------------------------------------------Total Number of Mobility VLANs = 4

10. Use the command show wireless security {mac-db | mac-filter-blacklist|radius | user-db | wids-wips} to display information about wireless securitysettings.

CLI Reference:WCP8180#show wireless security ?Display wireless security configurations mac-db Show black and white listed users mac-filter-blacklist Show wireless security mac-filter-blacklist radius Display global RADIUS configuration user-db Display local user configurations wids-wips Display WIDS/WIPS information

Displaying blacklisted and whitelisted users




Sample output:WCP8180#show wireless security mac-db blacklist Total blacklisted users: 2MAC Address User Name----------------- -----------00:01:02:03:1D:05 User_01 00:01:02:03:1D:45 User_02 WCP8180#show wireless security mac-db whitelist

Total whitelisted users: 2

MAC Address User Name----------------- -----------00:01:02:03:04:06 User_0300:01:02:03:04:07 User_04

Enabling blacklist MAC filtering and verifying that it is enabledWCP8180(config)#wirelessWCP8180(config-wireless)#securityWCP8180(config-security)#mac-filter-blacklistWCP8180(config-security)#show wireless security mac-filter-blacklistmac-filter-blacklist: Enable

Displaying global RADIUS configuration

CLI Reference:WCP8180(config-wireless)#show wireless security radius ?Parameters: <cr>Sub-Commands/Groups: profile Display radius profiles server Display radius servers

Sample output:WCP8180#show wireless security radiusRadius server timeout: 2 (sec.)Radius server retries: 3Radius known client db ageout: 30 (min.)---------------------------------------------

Sample RADIUS profile output:WC8180#show wireless security radius profile Total radius profiles: 2, auth: 1, acct: 1Radius Profile Type Server-selection-------------------------------- ------------------------------Auth1 Authentication PriorityAcct1 Accounting N/A

Sample RADIUS server output:WC8180#show wireless security radius server

Total radius servers: 1Server IP Radius Profile Port# Priority Status --------------- -------------------------------- ----- -------- -------172.16.2.11 Auth1 1812 1 Up

Displaying WIDS/WIPS information:




Wireless intrusion detection (WIDS) supports detection of rogue clients and AP(s) in thewireless network based on a configurable set of detection criterion. Wireless intrusionprevention (WIPS) takes proactive action to mitigate the threat posed by rogue devices. TheWIDS/WIPS policy specifies the configuration elements for the WIDS/WIPS feature. Thisincludes the rogue classification criterion, known AP database and rogue AP database.

CLI Reference:CP8180#show wireless security wids-wips ?Display WIDS/WIPS information adhoc-clients Display Ad Hoc network information ageout Display WIDS ageout time configuration ap-deauth-attacks Display AP de-authentication attack status detected-clients Display detected clients information global-status Display WIDS/WIPS global status known-ap Display WIDS known AP information mitigation Display WIPS mitigation configuration rf-scan Display WS managed AP RF Scan data rogue-ap-classification Display AP rogue classification rogue-ap-controls Display WIDS AP configuration. rogue-client-classification Display client rogue classification rogue-client-controls Display WIDS client configuration triangulation-table Display signal triangulation status

Sample outputs:WCP8180#show wireless security wids-wips detected-clients

Domain Role :Active MDCTotal Rogue Clients :0Total Detected Clients :3

Detected Client RSSI Last Client MAC Status Det Mit Ch (%) Sig Update ----------------- ------------- --- --- --- ---- ---- ------------00:00:1A:2D:F3:99 detected Y N 157 6 -89 0d:01:08:53 00:00:4D:C1:91:FE detected Y N 157 8 -87 0d:01:03:53 00:00:4D:C1:92:00 detected Y N 157 7 -88 0d:01:04:23WCP8180#show wireless security wids-wips rogue-client-controls

Rogue detected trap interval: 300Known client database radius profile:

Threshold Threshold Rogue State Interval Value ---------------------------------------- ---------- ---------- ----------Client is not in known DB Disabled Authenication request exceeded Enabled 60 10 Probe request exceeded Enabled 60 120 DeAuthenication request exceeded Enabled 60 10 Authenication failure exceeded Enabled 5 Client is authenicated with unknown AP Disabled

11. Use the command show wireless client info to display information about the currentstatus of wireless clients.

Sample output:wc1#show wireless client infoTotal number of client(s): 1

-------------------------------------------------------------------




Client AP IP Controller Chnl SSID Client IP Address Address IP Address Status----------------- --------------- --------------- ----- ------------client: 00:41:DD:02:00:00 11.0.0.88 172.16.3.32 173.16.3.3 11 AP8120-E Authenticated--------------------------------------------------------------------

12. Use the command show wireless radio tspec <radio_number> to display informationabout overall system usage, the number of associated stations, the measured channelutilization percentage, and the total available admission capacity in units of mediumTime.

Sample Output:WCP8180#show wireless radio tspec 1------------------------------------------------------------------------ Radio ACM Mode ACM Limit Roam Profile TSPEC ----------------- ----------------- Shared Reserve ID Mode voice video voice video Limit Limit ------- -------- -------- -------- -------- -------- ------ ------- 1 Disabled Disabled Disabled 20 15 0 5------------------------------------------------------------------------

Related LinksTroubleshooting WLAN on page 47Troubleshooting client connectivity issues due to failed authentication on page 61Troubleshooting client connectivity issues due to failed MAC validation on page 64Troubleshooting DHCP-related client connectivity issues on page 65Troubleshooting client traffic issues on page 66

Troubleshooting client connectivity issues due to failedauthentication

Before you beginEnsure that at least one wireless network exists that the client can connect to.

About this taskUse the following procedure to troubleshoot WPA2-AES-PEAP clients that did not connect as aresult of failed authentication. WPA2-AES-PEAP stands for Wi-Fi Protected Access II — AdvancedEncryption Standard (AES) — Protected Extensible Authentication Protocol (PEAP).

Procedure1. Ensure that client configuration for WPA2–PEAP-AES is correct.

Perform the following steps.

These steps are based on the Windows 7 operating system.

a. On the Windows Control Panel, click Network and Sharing Center.

b. On the left hand side panel, click Manage wireless networks.

The system displays the wireless networks that are currently in use.




Note:

If no wireless networks are displayed, you must first add a wireless network.

On the Manage wireless networks window, click Add to create a new network.

Figure 1: Wireless networks currently in use

c. Double-click the icon for the wireless network that the client is connected to.

The system displays the <Network-Name>Wireless Network Properties dialog box.

d. Click the Security tab.

• Ensure that WPA2–Enterprise is selected in the Security type field.

• Ensure that AES is selected in the Encryption type field.

• Ensure that the network authentication method chosen is Protected EAP (PEAP).




Figure 2: Wireless Network Properties

2. Ensure that the wireless client is not blacklisted with the WLAN controller.

Use the following CLI command:WC8180#show wireless security mac-db blacklist <mac addr>

Sample output:

The following sample output indicates a wireless client with MAC address00:00:0E:F1:2B:FB that is blacklisted with the WLAN controller.WC8180#show wireless security mac-db blacklist 00:00:0E:F1:2B:FB

MAC Address User Name ----------------- ---------------- 00:00:0E:F1:2B:FB WC8180#

3. Ensure that the authentication credentials (user-name and password) obtained from thewireless client for PEAP Authentication, is correct.




4. Execute the following command to verify the reason for failure in the Authentication Failuretrap.WC8180#show logging wireless-controller volatile

5. Check the logs on the RADIUS server to troubleshoot the authentication failure.

Note:

The path to the location of the logs can vary depending on your RADIUS server.

Related LinksTroubleshooting client-related issues on page 55

Troubleshooting client connectivity issues due to failed MACvalidation

About this taskUse the following procedure to troubleshoot client connectivity issues due to failed MAC validation.

Procedure1. Ensure that blacklist MAC filtering is not enabled on your network.

Use the following command:WC8180#show wireless security mac-filter-blacklist mac-filter-blacklist: DisableWC8180#

2. Verify that the wireless client is not listed in the blacklist database.

Note:

This step is optional. Perform this step only if blacklist MAC filtering is enabled on yournetwork.

Use the following command:WCP8180#show wireless security mac-db blacklist

3. If the configured MAC validation mode is RADIUS, ensure that the client MAC address (to bevalidated in the RADIUS server) is configured on the RADIUS server.

Note:

If the client MAC address of a client is not added to the RADIUS server, the client isblacklisted for a configured time period. Use the command show logging wireless-controller volatile to verify how long a wireless client must wait before it canattempt to connect another time.

4. If the MAC validation mode is configured as local-whitelist, ensure that the MACaddress of the client is added to the local whitelist database.




If the client is not already whitelisted, perform the following steps to add a client to the localwhitelist database:

a. Enter the wireless security configuration mode of the ACLI:WC8180#conf tEnter configuration commands, one per line. End with CNTL/Z.WC8180(config)#wirelessWC8180(config-wireless)#securityWC8180(config-security)#

b. Add the wireless client to the local whitelist database.WC8180(config-security)#mac-db whitelist ?H.H.H MAC address of the whitelisted user


Troubleshooting DHCP-related client connectivity issuesAbout this taskUse the following procedure to troubleshoot wireless clients if you suspect that a valid DHCP IPaddress was not generated for the client.

Procedure1. Ensure the mobility VLAN associated to SSID of your wireless network is mapped to the

local VLAN.

Use the following CLI command:WC8180#show wireless switch vlan-map <mobility-vlan-name>

Sample output:

In the following example, the mobility VLAN mob-vlan1 is mapped to a local VLAN withVLAN ID 70.WC8180#show wireless switch vlan-map mob-vlan1---------------------------------------------------------------Mobility VLAN Name LVID State Role WCP-V Admin Mapped------------------- ----- ----- ---- ----- ------------mob-vlan1 70 Active Server Yes Yes ---------------------------------------------------------------WC8180#

2. If the switch VLAN map for a mobility VLAN is not configured, ensure that there is a VLANserver available for the mobility VLAN in the domain. Verify using the following command:WC8180#show wireless switch vlan-servers ---------------------------------------------------Mobility VLAN Name Current Server MAC Priority------------------ ------------------ --------RADIUS CC:F9:54:E0:A5:00 7 ----------------------------------------------------Total Number of Entries = 1WC8180#




3. If the client is a RADIUS authenticated client and the mobility VLAN is pushed as an attributefrom RADIUS server, ensure that the mobility VLAN that is pushed has a local VLANmapping on the controller.

In Overlay deployments, execute the following CLI command on the controller. In UnifiedAccess deployments, execute the command on the wireless switching point (WSP).WC8180#show wireless switch vlan-map <mobility-vlan-name>

4. Ensure that the DHCP server is able to receive the discover packets from clients and is ableto assign an IP address from a defined scope.


Troubleshooting client traffic issuesAbout this taskUse the following procedure to troubleshoot issues with client data traffic.

Procedure1. Ensure that network connectivity between the source and destination is good.

For example, you can execute the ping or traceroute commands on the source anddestination to check for connectivity.

2. Ensure that client-QoS is not enabled on the network that the clients are connected to.

Use the following command:WC8180#show wireless network-profile client-qos -------------------------------------------------------Network Client Diffserv Policy Name Profile OoS ----------------------------------- Id Mode Down Up -------- -------- ------------------ --------------- 1 Disabled 2 Disabled -------------------------------------------------------WC8180#

3. If client-QoS is enabled, check whether the DiffServ policy is applied on to clients eitherusing the network-profile configuration or using RADIUS attributes.

In the following example, the client with MAC address 00:00:34:33:e0:ab is notassociated with a DiffServ policy.WC8180#show wireless client qos status 00:00:34:33:e0:ab

Client Mac Address: 00:00:34:33:e0:ab QoS Operational Status: Disabled Client to AP(Ingress) AP to Client(Egress) --------------------- -------------------- QoS Bandwidth limit(bps): 0 0 Diffserv Policy Name: None None




4. If a DiffServ policy is applied to a client, ensure that the policy is not configured to filter trafficsent from the wireless client.

Use the following command:WC8180#show wireless diffserv classifierblock <classifier-block-name> detail Classifier block sample-classifier-block------------------------Element ID: 1Protocol: 1WC8180#

5. Ensure that the same Tunnel path MTU is configured across all controllers in the domain,and the packet size of the data transmitted by the client is within this limit.

Use the following command to verify the Path MTU on a controller:WC8180#show wireless Operation Mode : WC Status : Enabled Interface IP : 192.168.36.4 TCP/UDP base port : 61000 Base MAC Address : CC:F9:54:E0:BE:00 Tunnel Path MTU : 1900WC8180#


Troubleshooting wireless clients using Remote PacketCapture

Use this procedure to troubleshoot wireless clients using Remote Packet Capture.

For a complete listing of the CLI commands to configure Remote Packet Capture, see the ACLICommands Reference for Avaya WLAN 8100, NN47251-107.

Before you begin• You know the MAC address of the AP to which the client is connected.• Ensure that you do the following on the Observer host PC.

- Download the Netcat application from http://netcat.sourceforge.net/download.php to alocation on the PC.

- Open a UDP port for listening.

Important:If you do not open the UDP port on the observer host then the capture device receivesthe ICMP port unreachable error for every capture packet in the capture stream.This severely impacts the performance.

- Launch Netcat.

Troubleshooting wireless clients using Remote Packet Capture


http://netcat.sourceforge.net/download.php


On a Windows machine, execute the following command at the location of installation ofNetcat. In the following example, 172.16.9.10 is the IP address of the Observer host PCand the observer port is 37008.D:\RPC\NetCat>nc -l -u -p 37008 -s 172.16.9.10 -vlistening on [172.16.9.10] 37008 ...

On a Linux machine, execute the command nc –l –u <port number>.

- Launch Wireshark to capture frames.

• In Wireshark, ensure that you configure the CAPWAP UDP data port correctly. To decodethe information packets correctly, this port must be the same as that opened for listeningon the observer host PC. On Wireshark, navigate to Edit, Preferences, CAPWAP.Update the field CAPWAP data UDP port.

• Also ensure that you deselect Swap Frame Control.

Figure 3: Configuration of the CAPWAP UDP port on Wireshark

Procedure1. Configure a capture profile.

Capture profiles are used for remote packet capture. Remote packet capture enables livedebugging to troubleshoot client related issues. It can also be used to monitor traffic in awireless network. After you configure a capture profile, you must apply these profiles tospecific access points (AP) within the mobility domain to start a packet capture. You canconfigure up to 4 capture profiles.

In the following example, you configure a capture profile named sample-capture withprofile Id 2.




Note:

A default capture profile with profile Id 1 is automatically created. You can choose to usethis profile or configure a suitable one using the following steps.

WCP8180 (config-wireless)#capture-profile 2Entering capture-profile (id = 2) ...WCP8180(config-capture-profile)#profile-name sample-capture

Verify configuration of the capture profile, using one of the following commands. In thefollowing example, 172.16.9.10 is the IP address of the Observer host PC and theobserver port is 37008.WCP8180# show wireless capture-profile 2-----------------------------------------------------------Id Profile Name Observer IP Observer Port--- ------------------------- --------------- ------------- 2 sample-capture 172.16.9.10 37008-----------------------------------------------------------

OrWCP8180# show wireless capture-profile 2 detailCapture Profile ID: 2 Name : sample-capture Observer IP Address : 172.16.9.10 Observer UDP Port : 37008 Filter Promiscous mode : Disabled Filter Interfaces : All Radios Filter Flow direction : Transmit and Receive Filter SSID : Filter Client MAC : 00:00:00:00:00:00 Filter 802.11 : data Filter Duration : 300 Filter SNAP Length : 128

Important:

The default value of the snap length is 128 in the configured capture profile. This valuecan be modified between 32 and 1024. In Wireshark, when the packet length exceedsthe configured snap length in the capture profile, the captured packets showed asMalformed.

To verify configuration of all capture profiles, use the following command:WCP8180# WCP8180 (config-wireless)#show wireless capture-profile detail

2. Monitor and troubleshoot wireless clients using Remote Packet Capture.

To use the Remote Packet Capture feature, you must assign the capture profile to an AP,and then start a packet capture instance on the AMDC. You need an observer host PC toview the packet capture.

Use the following command to start a packet capture. In this example, 00:1B:4F:6C:1F:80 is the MAC address of the AP to which you want to associate the capture profile. Theprofile ID of the Capture profile sample-capture is 2.WC8180# wireless capture-instance start ap 00:1B:4F:6C:1F:80 profile 2

Troubleshooting wireless clients using Remote Packet Capture



View capture instances as follows:

To view capture instances for a specific AP:WC8180# show wireless capture-instance ap <ap-mac>

To view capture instances for a specific profile:WC8180# show wireless capture-instance profile <profile-Id>

To view all capture instances:WC8180# show wireless capture-instance

3. Optionally configure filters for the capture profile sample-capture to customize yourpacket capture. You can set one of the following packet capture filters:

• client-mac: to filter capture by client MAC address

• include-beacons: to Include 802.11 beacons in capture data

• include-control: to include 802.11 control frames in capture data

• include-data: to include 802.11 data in capture data

• include-mgmt: to include 802.11 mgmt frames other than probes/beacons in the capturedata

• include-probes: to include 802.11 probes in capture data

• ssid: to filter capture by ssid

For example, if you want to troubleshoot a wireless client (with MAC address00:13:46:EA:CC:12), configure the filter client-mac in the capture profile sample-capture as follows:WCP8180 (config-wireless)#capture-profile 2Entering capture-profile (id = 2) ...WCP8180(config-capture-profile)#filters client-mac 00:13:46:EA:CC:12

Verify filter configuration using the following command:WCP8180# show wireless capture-profile 2 detailCapture Profile ID: 2 Name : sample-capture Observer IP Address : 172.16.9.10 Observer UDP Port : 37008 Filter Promiscous mode : Disabled Filter Interfaces : All Radios Filter Flow direction : Transmit and Receive Filter SSID : Filter Client MAC : 00:13:46:EA:CC:12 Filter 802.11 : data Filter Duration : 300 Filter SNAP Length : 128

4. Optionally, to monitor network activity, you can enable the promiscuous mode in the captureprofile sample-capture as follows.

The Promiscuous mode is a mode of operation in which every data packet transmitted canbe received and read by a network adapter thus allowing your computer to read frames




intended for other machines or network devices. The promiscuous mode must be supportedby each network adapter as well as by the input/output driver in the host operating system.

To enable promiscuous mode, use the following command:WCP8180 (config-wireless)#capture-profile 2 Entering capture-profile (id = 2) ...WCP8180(config-capture-profile)#promisc-mode enable

To disable promiscuous mode, use the command:WCP8180(config-capture-profile)# no promisc-mode


Troubleshooting the E911 featureAbout this taskIn the current version of the Sentry 8100 Scout application, you perform configurations by manuallyediting an XML config file. When you configure the Sentry 8100 Scout application, you must edit theconfiguration file and populate the values of a number of settings for the Sentry application to runproperly.

The WLAN 8100 generates a log file that you can use to troubleshoot issues with the E911 feature.You can change the log settings in the config file. By default, the output location for the log file is C:\Program Files (x86)\Conveyant Systems\Sentry 8100 Scout\8100Scout.log .

To turn on full logging for troubleshooting, you must modify the config file 8100Scout.exe.config bychanging the level value attribute in the logging section of the configuration file from INFO toDEBUG.

For more information on the E911 feature, see WLAN 8100 – E911 Solution Technical ConfigurationGuide (NN48500-610)

Procedure1. On the Windows server where you install the Sentry 8100 Scout applications, navigate to the

8100Scout.exe.config file.

Important:

If you followed the default install options when you installed the Sentry 8100 Scoutapplication, you can find the configuration file in the following location:

C:\Program Files (x86)\Conveyant Systems\Sentry 8100 Scout\8100Scout.exe.config

2. In the logging section of the config file, change the level value from INFO to DEBUG. Anexample of this portion of the configuration file is shown in the following code sample.<log4net></log4net>  <root>  <level value="DEBUG" />  <appender-ref ref="LogFileAppender"/>  </root>   <appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender">  <param name="File" value="8100Scout.log" /> <param name="AppendToFile" value="true" /> <rollingstyle value="Size" /> <maxSizeRollBackups value="10" /> <maximumFileSize value="1MB" /> <staticLogFileName value="true" />  <layout type="log4net.Layout.PatternLayout"> <param name="ConversionPattern" value="%-5p %d{yyyy-MM-dd HH:mm:ss} - %m%n />  </layout> <appender>

</log4net>





Troubleshooting the E911 feature



Appendix A: Resetting the mobility domainpassword

Before you begin• You have administrative privileges on the controller.

About this taskSometimes, as part of troubleshooting, you may want to reset the mobility domain password orsecret. The domain secret is the password that you use when you configure the mobility domaincontroller (AMDC or BMDC) to be MDC-capable.

You may also want to reset the mobility domain password if, for example, you forgot the originalpassword.

Use this procedure to reset the mobility domain password.

ProcedureEnable MDC-capability on the controller using the new mobility domain secret.

Note:

When prompted, enter the new mobility domain password (secret).WCP8180(config-wireless)#controller mdc-capable% Domain secret should be between 10-15 characters long.% Domain secret must contain a minimum of 2 upper, 2 lowercase letters% 2 numbers and 2 special characters like !@#$%^&*()

Enter domain Secret: *****

Verify Domain secret: *****

Date post:	24-Dec-2015
Category:	Documents
Upload:	nestor-gallego
View:	39 times
Download:	1 times

WLAN_TroubleshootingGuide

Documents