45631, 45066 45777

45871, 45914, 45917 45932
46001 46080, 46128, 46142

10 | Fixed Issues

46348 46483
Clients no longer experience a delay in switching to a VLAN specified by server derivation rule. Improvements to the Auth and STM modules prevent the controller from failing to respond due to IPIP loops. For APs using a bridge-mode SSID, VLANs in a virtual AP profile no longer appear in the Datapath VLAN Multicast Entries table, since the VLAN is only local to the bridge. Improvements to the Authmgr module increase controller stability. The DNSmasq process on 600 Series switches has been improved to allow a DNS query of a domain name longer than 51 characters. Improvements to NAT discovery payload handing allow the switch to continue to respond properly even if the NAT discovery payload includes in an incorrect length. Captive Portal whitelists can be created or modified regardless of whether the PWA license is installed on the switch. In a RAP-5WN deployment, a Vonage phone adapter that plugs into a wired port in bridge mode is now able to obtain an IP address using DHCP. The internal database on a master switch can be used for 802.1x machine authentication. If a captive portal page requires a user to click an Accept button to agree to a user policy, the customer will not be redirected to the requested Web site until the Accept button is clicked. The process to add and modify users and bridge mode has been improved, increasing AP stability. If an AP uplink's router port is shut down for extended period of time, the AP will automatically recreate an IPsec tunnel to the switch once the router port is reenabled.

46963 47032, 49180 47069

47805 48387

46237 46249

Table 3 Fixed in AOS-W 5.0.3 Bug ID

25362, 24401 28532

Stale vpn user entries are no longer building up in the user table because their associated L2TP tunnels are now deleted when no longer in use. Previous parsing mechanism used space as delimiter, so if there is a space in cluster profile, it would pick the wrong values. The parsing mechanism has been changed to TLV blocks, which can handle any possible case. Internal database fields for both usernames and emails can be up to 128 characters. Clients can now successfully authenticate against configured 802.1x profiles and the associated auth module crash has been fixed. An issue in which local-userdb entries became corrupted after a power failure has been fixed.

34993 37703, 46596 38793, 37387 38938
The errorlog no longer shows a missing VPN auth profile for every reboot of the switch when there is a RAP terminating on that switch.

Fixed Issues | 11

38964, 42709, 42708, 42751 39595, 41875 40032
Session age now checks for reverse age against configured timeout to avoid pre-aging session to avoid spurious deletes.
An issue in which APs rebootstrap when datapath SP becomes busy has been fixed.
The OAW-AP105 no longer constantly detects spurious radar when operating DFS channels (52, 56, 60, and 64). The Network Summary > APs Down page in the WebUI no longer returns a blank page. It now returns the same information as AP database table in the CLI.
40225, 40639, 45001, 37873, 40558 40664
An snmpd process crash that occurs when deleting a version 3 trap host has been fixed. Username checking in single-session captive-portal is no longer case-sensitive. When DNS interception is disabled using the command ip cp-redirect-address disable it is now correctly disabled and remains that way after rebooting the switch. When using Internet Explorer 6.0, a Guest Provision Profile user is now able to add/delete new users with the browser freezing or displaying error messages. Bridge clients now correctly get an IP address when switching from a standard VAP to a backup VAP on the same Remote AP, when the RAP is coming through a DSL router or NAT device. When a netdestination invert rule is changed, the change is now correctly reflected in the ACL immediately. A switch cfg module crash caused by an older heartbeat message packet received by the master switch; a switch entry was created for the old message, however the magic cookie was not set causing the assert call to fail. This issue has been fixed. The issue with TCP connections not being closed after role change has been fixed. The phone number and IP address of an NOE phone are now correctly displayed in the output of the show voice client-status command. The command show ap debug driver-log shows the kernel log messages and the driver log as well. Once the driver log is retrieved from the driver, the second read does not retrieve any messages because all of the messages has already been consumed and there are no new messages in the driver log. The ARM algorithm now takes into account RF anomalies to prevent APs from continually moving to channels with high amounts of interference. Special characters can be used when creating a new dialer group profile or modifying an existing one.

41353, 44508 41408

41727 41822, 44062 41894
41935, 44103 42010, 43743 42132
When ip local-proxy-arp on interface vlan is enabled, ARP for wireless clients are no longer broadcasted to all APs that share the same user VLAN. Instead switch does proxy-arp for the wireless client. L3 GRE now works correctly when Keepalive is enabled.

12 | Fixed Issues

42261 42333, 42524
The issue with the file transmission over poor links has been fixed. wlanAPSysLocation has been added to AP table, which gives the value of the syslocation provisioning parameter for the AP. Aeroscout tags now correctly associate with Alcatel-Lucent APs. The Token Caching Function has been verified. The username is now concatenated with device MAC so same user on different devices will get different cached entries in local user db. This way, a same user using a 2nd device will always go to server the first time (since no hit in cache), and create a different cache entry for the 2nd device. From then on, each device will use its own cached entry without interfering with each other. Increased stability in the UAPSD (WMM-powersave) protocol prevents unintended lock-outs on AlcatelLucent Mobile IP Touch (MIPT) wireless telephones after Virtual Router Redundancy Protocol (VRRP) failover. On APs, the number of open file descriptors for each monitor process are now checked once per minute and reboot the device only if the a process has more than 75% of the maximum number (1024) of file descriptors open. The Tx and Rx databytes now support 64 bits on all platforms. The issue in which APs terminating on a switch rebootstrap whenever the master switch is rebooted has been fixed. The OAW-AP120 Series and OAW-AP105 are now supported in the Philippines (country code PH).

42670, 43267

42771 42841, 40322 42862, 42865 42882
Spectrum Load Balancing domain now correctly calculates domain neighborhoods and will not incorrectly load balance all APs. The OAW-AP70 no longer crashes every few minutes when JP2 or JP3 country code is set, ARM scanning is enabled, and the APs 11b/g radio is set to channel 14. When using a wildcard certificate for Captive Portal, the URL is redirected to captiveportal-login instead of the portal. Improvements have been made to the derivation logic to prevent clients from being incorrectly moved from role to role when roaming.

43958 43977

44492 44605

44619, 44493 44968

14 | Fixed Issues

45384, 45680

AMSDU is now disabled by default with a knob in the firewall command in the CLI.
The Handoff Assist log message has been enahanced to show the actual low RSSI of the client. UPS Delivery Information Acquisition Devices (DIADs) stay properly connected to an Remote AP in bridge mode. Switches can include an AP group name (Aruba-AP-Group) in the list of RADIUS attributes sent in a RADIUS authentication request. Improvements to the switch kernel prevent APs from performing unintended reboots. Clients are no longer being incorrectly deauthenticated when admission control is mandatory for VO and VI. EAP termination on legacy switches no longer intermittently stops working.

46163 46421

46715, 44859

Fixed Issues | 15

16 | Fixed Issues

Chapter 4

Known Issues
The following are known issues and limitations for this release of AOS-W. Applicable bug IDs or workarounds are included: Table 4 Known Issues and Limitations Bug ID
Do not enable Firewall TCP enforcement when IP mobility is enabled. Workaround: None. On Alcatel-Lucent 4306 Series switches, when firewall enforce-tcp-sequence is enabled, there is an up to 3 second delay when TCP connections are established. Workaround: None. When a DHCP helper IP is configured, it is internally maintained as 2 separate entries for the vlan. Now if you try to delete the helper IP or change it to another helper IP, one incarnation of the same old helper IP is retained. So DHCP requests from a client on the vlan, the request will still get relayed to the old helper IP. Workaround: If you want to change/delete the DHCP helper IP, first delete the helper IP, do a write mem and reboot the box. This will remove the helper IP completely from the vlan after the box boots up again. Now you can assign a new helper IP if required. In the Alcatel-Lucent version, under Startup Wizard > VLAN and IP Interface > VLAN, when the user attempts to select a VLAN from the drop-down menu, the user will recieve a Java script error and be unable to configure a VLAN pool. Workaround: Configure VLANs through the CLI. Multiple logins can be allowed when single-session is enabled, if a RADIUS server allows caseinsensitive usermanes. Workaround: None: On some occasions, Remote AP stops responding to association messages for clients connecting to split-tunnel SSIDs when the AP is also advertising a backup/always mode bridge SSID. Workaround: None. After a VIA session is timed out, VIA is unable to make a new connection and shows the VIA Peer not responding message. This could happen if you have configured more than 10 tunnel IP addresses in VIA connection profile. VIA supports only 10 user configurable tunnel addresses and one for internally assigned IP address. Workaround: On the switch update the VIA connection profile to have only 10 tunnel address. On the client do the following: 1. Navigate to the Setting > Connection Profile and click the Clear Profile button. 2. In the Status tab, click the Download Profile button. Enter your domain credentials and the VIA switch IP address and download new profiles.

Known Issues | 17

Table 4 Known Issues and Limitations Bug ID
If the DNS IP address is not configured on the switch for VPN remote clients then the client fails to set the IP address on the Windows Vista and Windows 7 systems. To verify if it is related to DNS entry or not, start wireshark on Virtual adapter and check the DHCP (bootp) protocol packets. Workaround: Using CLI :(host)(config)# vpdn group l2tp client configuration dns <dns-ip1> <dns-ip2> (host)(config)# Write mem Using the WebUI : 1. Navigate to Configuration > Advanced Services > VPN Services IPSEC and set the Primary DNS Server under L2TP and XAUTH Parameters. 2. save configuration. Symbol wireless barcode scanners may unexpectedly de-authenticate and disassociate from remote APs. The current QBSS-alternative implementation in AOS-W has the following limitations: Probe-response may not actually reflect the real status if local probe is enabled. After cac-capacity is reached, if you disconnect and re-connect a phone again, the call may not go through for 10 seconds. Even if you disable local probe, sometime phone roaming can fail in the following scenario: 1. Spectralink phone roams when th ephone sees an AP with better RSSI( ~10dB difference) 2. let us say the cac is configured to 10. There are 16 phones and 2 APs 3. 6 phones associated to AP2 and 10 phones associated to AP1. 4. 6 phones associated to AP1 moved to nearer to AP2 where RSSI of AP2 is 10dB better than RSSI of AP1. 5. Even if there is retry or packet loss issue for the phones associated with APs, the 6 phones will try to move to AP2. 6. They send QBSS probs and AP will send out QBSS + responses to all 6 Phones. 7. Then the 6 Phones will try to associate to AP2 since all 6 got QBSS response. But only 4 phones will succeed and two will rejected eventually. 8. This will cause some temporary call drops for the two rejected phones.
After the STM module is respawned (i.e. after a crash), the show voice commands will not display any information because the memory that stores the data is cleared after STM restarts. Due to the use of different methods to setup an IPSec policy filter between the Alcatel-Lucent dialer and the Microsoft native dialer, the Aruba dialer will break the Microsoft ntive dialer for IPSec L2TP. The show datapath command does not return any output for RAPs connetced to high latency 3G/ EVDO links. Bulk RAP provisioning for multiple AP groups does not support triangulation. User role and VLAN derivation based on DHCP-option-77 is support on RAPs. When a user changes VLANs, the SSID user entry for both VLANs will be updated. Unicast and multicast key rotation does not work for split-tunnel 802.1x authentication. Hitachi wireless IP 5000 phone with firmware version 2.5.2 LA1 cannot associate with an AP in WPA2PSK-AES mode when the SSID has both WPA-PSK-TKIP and WPA2-PSK-AES enabled on it. This is because the STA is sending AES CCMP as the multicast cipher, instead of TKIP. NTP must be run on the switch before VRRP. If this is not done, the system clocks between switches in a master-backup setup will not be synced correctly. Switches can only export up to 100 VLAN subnets to neighbors.

28608, 32076 32320

18 | Known Issues

32650 32896

If the local-userdb-ap entry is deleted for a non-remote AP, the AP will reboot. An Air Monitor will not process Ethernet frames on the 'eth1' interface, except in cases where eth0 and eth1 are deployed in a standby configuration for an AP-70. In this scenario, if eth1 is active, the Air Monitor will receive the ethernet frames on this interface. This issue will affect rogue AP classification for devices on the eth1 interface. Alcatel-Lucent VIA does not support new pin and next pin mode for Radius authentication. For RAPs, the local debugging ping and treaceroute tools will not work if the APs IP address is not routable. In the WebUI, under Monitoring > Access Points > USB, the serial number will not be displayed. Double encryption does not work for tunnel SSIDs on AP-120 series and RAP-5s conneted to an M3 switch. All client associations will be cleared for an AP terminated to local switchwhen the master switch is rebooted. Load balancing over equally costed routes does not work. The RAP DHCP server feature does not work. Clients will not recieve an IP address. Deny time range in virtual AP does not work in split-tunnel and Bridge mode. The ap-group provisioning profile will always take precedence over the ap-name provisioning profile. Max-retries cannot be configured in an SSID profile.

33192 33541

33829 34148

35231, 35605

The uplink connection to a RAP must be through ethernet port 0, otherwise the RAP will not come up. When RAP reboots after provisioning at home, if the wired port is in tunnel mode, local debugging page does not refresh as local debugging does not work on tunnel mode vap/port. Dynamic pullout or plug-in of an EVDO modem on a RAP does not work with Huawei E272 RFProtect sheilding fails if the SSID is using WEP authentication. It will work when the SSID is open or using WPA PSK. RAP-5 and RAP-5WN cannot be used as a mesh point. Mesh points are unable to get an IP address from a DHCP pool defined on the switch if the rf-band configured under dummy split VAP is not the same as the rf-band configured under the mesh cluster. RAPs cannot be provisioned when using D-Link DIR-100 NAT device due to decryption failures. RAPs running AOS-W 2.5 cannot upgrade directly to AOS-W 5.0 because AOS-W 2.5 does not support AES. There is a discrepency in the way the CLI and WebUI display local-userdb users. The WebUI does not have following columns: Staus, Sponsor-Name and Grantor-Name but the specified tables are shown in CLI. Uplink Manager functionalities appear on non-4306 series platforms but cannot be used.

35674 36117

36291 36601

36891 36923

Known Issues | 19

37700 37774

When a clients ethernet port is connected, the client fails wireless 802.1x authentication. CPSec CAP cannot TFTP core files to the configured dumpserver unless a route is added on the upstream router to point to the switch for AP subnets. If cookies are disabled in Microsoft Internet Explorer (IE) VIA profiles cannot be download. Workaround: Enable cookies in IE to download VIA profiles. A switch will not process OSPF LS Update packets if the packet is fragmented. MTU size is not displayed in an ap bss-table for RAP bridge port because there is no data-pkt tunnel between RAP and switch for bridge mode. Therefore, no MTU discovery happens Aruba VIA client does not automatically detect Aruba Captive Portal. Workaround: Launch Aruba VIA client after completing the authentication process using the Aruba Captive Portal. Aruba VIA client is not supported on 64-bit operating systems. Only one VAP can have band steering enabled per ap group. Enabling it on multiple VAPs will not give expected results for clients connecting to all VAPs having band steering enabled. The master-ip parameter has been removed from the command ap system-profile.

37858 37905

38105 38398

38403, 38602 38782

Spectrum load balancing requires scanning to be enabled in the ARM profile. The aaa profile used for the dummy-split-vap should not have L2 authentication enabled. A mgmt-user with a username of l, s, or w cannot be created since they are the starting character of keywords under the mgmt-user command. A mgmt-user username cannot exceed more than 16 characters, however local-userdb username can exceed 16 characters. Voice ALGs are not supported in bridge mode. IPSec encryption is not available for d-tunnel wireless traffic on RAPs. Cluster-root cannot point to the VRRP IP address of cluster-member-ip. The limit for static routes is 128, not 256. RAP-2WG cannot be used as a remote mesh point since the RAP-2WG does not have an 802.11a radio and mesh points are configured over a radio. The rapconsole does not show the IP addresses of clients. When a split-tunneled wired client is disconnected from a RAP, the client is immediately removed from the user table. Saving the 3G/EVDO values for the provisioning at home feature can take up to 30 seconds. When the save is complete, the page will refresh automatically. Versions AOS-W pre-3.4 do not support local-userdb export files generated by versions of AOS-W 3.4 or newer.

If you must use TFTP, ensure that your TFTP servers can send more then 30 MB of data.
Always upgrade the non-boot partition first. If something happens during upgrade, you can restore the flash, and switch back to the boot partition. Upgrading the non-boot partition gives you a smoother downgrade path should it be required.

Basic Upgrade Sequence

Testing your clients and ensuring performance and connectivity is probably the most time-consuming part of the upgrade. Best practices recommends that you enlist users in different locations to assist with the validation before you begin the upgrade. The list below is an overview of the upgrade and validation procedures.
If you manage your switches via the AirWave Wireless Management Suite, the AirWave upgrade process automates most of these steps.
1. Upload the same version of the new software image onto all switches. 2. Reboot all switches simultaneously. 3. Execute the ping -t command to verify all your switches are up after the reboot. 4. Open a Secure Shell session (SSH) on your Master Switch. 5. Execute the show ap database command to determine if your APs are up and ready to accept clients. 6. Execute the show ap active to view the up and running APs. 7. Cycle between step5 and step6 until a sufficient amount of APs are confirmed up and running. The show ap database command displays all of the APs, up or down. If some access points are down, execute the show datapath session table <access point ip address> command and verify traffic is passing. If not, attempt to ping them. If they still do not respond, execute a show ap database long command to view the wired mac address of the AP; locate it in your infrastructure. 8. Verify that the number of access points and clients are what you would expect. 9. Test a different type of client for each access method (802.1x, VPN, Remote AP, Captive Portal, Voice) and in different locations when possible.

24 | Upgrade Procedures

Managing Flash Memory
All Alcatel-Lucent switchs store critical configuration data on an onboard compact flash memory module. To maintain the reliability of your WLAN network, Alcatel-Lucent recommends the following compact flash memory best practices:
Do not exceed the size of the flash file system. For example, loading multiple large building JPEGs for RF Plan can consume flash space quickly. Warning messages alert you that the file system is running out of space if there is a write attempt to flash and 5 Mbytes or less of space remains.
Other tasks which are sensitive to insufficient flash file system space include:
DHCP lease and renew information is stored in flash. If the file system is full, DHCP addresses can not be distributed or renewed. If a switch encounters a problem and it needs to write a log file, it will not be able to do so if the file system is full and critical troubleshooting information will be lost

In certain situations, a reboot or a shutdown could cause the switch to lose the information stored in its compact flash card. To avoid such issues, it is recommended that you issue the halt command before rebooting.

Before you upgrade

You should ensure the following before installing a new image on the switch:
Make sure you have at least 10 MB of free compact flash space (show storage command). Run the tar crash command to ensure there are no process died files clogging up memory and FTP/ TFTP the files to another storage device. Remove all unnecessary saved files from flash (delete filename command).

Backing up Critical Data

It is important to frequently back up all critical configuration data and files on the compact flash file system to an external server or mass storage facility. At the very least, you should include the following files in these frequent backups:
Configuration data WMS database Local user database Licensing database Floor plan JPEGs Customer captive portal pages Customer x.509 certificates
Backup and Restore Compact Flash on the WebUI
The WebUI provides the easiest way to back up and restore the entire compact flash file system. The following steps describe how to back up and restore the compact flash file system using the WebUI on the switch: 1. Navigate to the Maintenance > File > Backup Flash page. 2. Click Create Backup to back up the contents of the Compact Flash file system to the file flashbackup.tar.gz. 3. Click Copy Backup to copy the file to an external server.

Upgrade Procedures | 25

You can later copy the backup file from the external server to the Compact Flash file system by navigating to the Maintenance > File > Copy Files page. 4. To restore the backup file to the Compact Flash file system, navigate to the Maintenance > File > Restore Flash page. Click Restore.
Backup and Restore Compact Flash on the CLI
The following steps describe the back up and restore procedure for the entire Compact Flash file system using the switchs command line: 1. Enter enable mode in the CLI on the switch. Use the backup command to back up the contents of the Compact Flash file system to the file flashbackup.tar.gz:
(host) # backup flash Please wait while we tar relevant files from flash. Please wait while we compress the tar file. Checking for free space on flash. Copying file to flash. File flashbackup.tar.gz created successfully on flash.
2. Use the copy command to transfer the backup flash file to an external server:
(host) copy flash: flashbackup.tar.gz ftp: <ftphost> <ftpusername> <ftpuserpassword> <remote directory>
You can later transfer the backup flash file from the external server to the Compact Flash file system with the copy command:

(host) # copy tftp: <tftphost> <filename> flash: flashbackup.tar.gz
3. Use the restore command to untar and extract the flashbackup.tar.gz file to the Compact Flash file system:

(host) # restore flash

License Mapping
License consolidation and even renaming of licenses occur over time. Figure 2 is an up-to-date illustration of the consolidated licenses effective with this release.

Licensing Change History

The following changes and/or consolidations were made to the AOS-W licensing.

AOS-W 5.0

MAP was merged into base AOS-W VPN was merged into base AOS-W RAP was merged into AP license PEF (user basis) was converted to PEFNG (AP basis) with AOS-W 5.0

AOS-W 3.4.1

VOC was merged into PEF. This merge happened with AOS-W 3.4.1 IMP was merged into base AOS-W

AOS-W 3.4.0

ESI was merged into PEF

26 | Upgrade Procedures

AOS-W Legacy and End-of-Life
AAA was merged into ESI with the release of AOS-W 2.5.3. CIM is End-of-life
Releases older than AOS-W 2.5.4 have been End-of-Lifed.
Figure 2 License Consolidation

Base AOS

AP Capacity Licensed by # APs
PEFNG - Wired, WLAN Licensed by # APs
PEFV VPN/VIA Controller Box License
WIP (no change) Licensed by # APs

(indoor)

(outdoor)

AAA (2.5 legacy)

Upgrading from 3.4.x to 5.0
Read all the following information before you upgrade to AOS-W 5.0.3.1. If you are upgrading from a version earlier than 3.4.x, see Upgrading from 3.3.x to 5.0 on page 30 or Upgrading from 2.5.x to 3.3.x to 5.0. on page 31.
Caveats on page27 Load New Licenses on page28. Save your Configuration on page28. Install AOS-W 5.0.3.1 on page28

Caveats

Before upgrading to AOS-W 5.0 take note of these known upgrade caveats.
If you have occasion to downgrade to a prior version, and your current AOS-W 5.0 configuration has CPSec enabled, you must disable CPSec before you downgrade. For more information on configuring control plane security and auto-certificate provisioning, refer to the AOS-W 5.0 User Guide.

Upgrade Procedures | 27

License_Conversion

Load New Licenses

Before you upgrade to AOS-W 5.0, assess your software license requirements and load any new or expanded licenses you require prior to upgrading to AOS-W 5.0. Software licenses in AOS-W 5.0 are consolidated and in some instances license names and modules are renamed to more accurately represent the modules supported by the licenses (see Figure 2). For a detailed description of these new license modules, refer to the Software Licenses chapter in the user guide.

# boot config-file <backup configuration filename>
3. Execute the show image version command to view the partition on which your previous software image is stored. In the following example, partition 0, the backup system partition, contains the backup release 3.4.1.23. Partition 1, the default boot partition, contains the AOS-W 5.0.3.1 image:
#show image version ---------------------------------Partition : 0:0 (/dev/hda1) Software Version : AOS-W 3.4.1.23 (Digitally Signed - Production Build) Build number : 20219 Label : 20219 Built on : 2009-12-11 20:51:46 PST ---------------------------------Partition : 0:1 (/dev/hda2) **Default boot** Software Version : AOS-W 5.0.0.0 (Digitally Signed - Production Build) Build number : 23711 Label : 23711 Built on : 2010-03-25 01:59:13 PDT
You cannot load a new image into the active system partition (the default boot).
4. Set the backup system partition as the new boot partition:
# boot system partition 0

5. Reboot the switch:

# reload
6. When the boot process is complete, verify that the switch is using the correct software:

# show image version

Upgrade Procedures | 33

Switch Migration

This section outlines the steps involved in migrating from an Alcatel-Lucent PPC switch environment to MIPS switch environment. These steps takes into consideration the common Alcatel-Lucent WLAN switch environment. You must have an operational PPC switch in the environment when migrating to a new switch. The switches are classified as:
MIPS SwitchesOAW-S3, OmniAccess 4504/4604/4704, 4306 WLAN Series PPC SwitchesOmniAccess 4302, OmniAccess 4308T, OmniAccess 4324, and OAS-S-1/OAS-S-2
Use this procedure to upgrade from one Alcatel-Lucent switch model to another. Take care to ensure that the new switch has equal or greater capacity than the switch you are replacing.
Migration instructions include:
Single Switch Environment on page 34 Multiple Master Switch Environment on page 34 Master/Local Switch Environment on page 34
Single Switch Environment
A single switch environment is one active switch, or one master switch that may have standby master switch that backs up the master switch.

Replacing the standby switchDoes not require downtime Replacing the master switchRequires downtime
Multiple Master Switch Environment
An all master environment is considered an extension of the single master switch. You can back up the master switches with a standby switch. In an all master switch deployment, each master switch is migrated as if it were in a standalone single switch environment. For every master-standby switch pair
Master/Local Switch Environment
In a master/local environment, replace the master switch first and then replace the local switches.
Replacing the local standbys (when present) Replacing local switchesone switch at a time

Before You Start

You must have:
Administrative access to the switch via the network Administrative access to the switch via the switchs serial port Pre-configured FTP/TFTP server that can be reached from the switch Alcatel-Lucent serial cable The AOS-W version (same as the rest of the network)

34 | Upgrade Procedures

Basic Migration Steps
1. Upgrade your network to the newer image to ensure that the image on the newer switches match the image on the rest of the switches in your network. 2. Backup the switch data from the PPC switch. 3. Physically swap the hardware (for example, mounting, cabling, power). 4. Initialize the new switch. 5. Install the backed up data onto the new switch. 6. Test the new setup.
Before You Call Technical Support
Before you place a call to Technical Support, please follow these steps: 1. Provide a detailed network topology (including all the devices in the network between the user and the Alcatel-Lucent switch with IP addresses and Interface numbers if possible). 2. Provide the switch logs and output of the show tech-support command via the WebUI Maintenance tab or via the CLI (tar logs tech-support). 3. Provide the syslog file of the switch at the time of the problem. Alcatel-Lucent strongly recommends that you consider adding a syslog server if you do not already have one to capture from the switch. 4. Let the support person know if this is a new or existing installation. This helps the support team to determine the troubleshooting approach, depending on whether you have:
an outage in a network that worked in the past. a network configuration that has never worked. a brand new installation.
5. Let the support person know if there are any recent changes in your network (external to the AlcatelLucent switch) or any recent changes to your switch and/or AP configuration. 6. If there was a configuration change, list the exact configuration steps and commands used. 7. Provide the date and time (if possible) when the problem first occurred. 8. If the problem is reproducible, list the exact steps taken to recreate the problem. 9. Provide any wired or wireless sniffer traces taken during the time of the problem. 10. Provide the wireless device's make and model number, OS version (including any service packs or patches), wireless NIC make and model number, wireless NIC's driver date and version, and the wireless NIC's configuration. 11. Provide the switch site access information, if possible.

wlsxSwitchTotalNumAccessPoints.1.3.6.1.4.1.14823.2.2.1.1.3.1
snmpget -v 2c -m ALL -c <SNMP community string> <Local switch IP>.1.3.6.1.4.1.14823.2.2.1.1.3.1
Number of Down APs per Switch
globalAPState.1.3.6.1.4.1.14823.2.2.1.1.3.4.1.6
snmpwalk -v 2c -m ALL -c <snmp community name> <Master switch IP addr>.1.3.6.1.4.1.14823.2.2.1.1.3.4.1.6 | grep -c 'INTEGER: 2'
Number of Successful 802.1x Authentications
To list the current dot1x users, enter:
snmpwalk -v 2c -m ALL -c <snmp community name> <switch IP addr>.1.3.6.1.4.1.14823.2.2.1.1.2.1 | grep -c "<dot1x>"
Number of Rogue APs per SwitchCount per Building
wlsrAmRAPType.1.3.6.1.4.1.14823.2.3.1.1.4.1.1.6
snmpwalk -v 2c -m ALL -c <snmp community name> <AP IP addr>.1.3.6.1.4.1.14823.2.3.1.1.4.1.1.6 | grep -c "unsecure"
Number of Interfering APs per Switch
snmpwalk -v 2c -m ALL -c <snmp community name> <AP IP addr>.1.3.6.1.4.1.14823.2.3.1.1.4.1.1.6 | grep -c "interfering"

Using MIBs | 25

Noise Level per AP
apChannelNoise.1.3.6.1.4.1.14823.2.2.1.1.3.3.1.13
snmpwalk -v 2c -c <snmp community name> <switch IP addr>.1.3.6.1.4.1.14823.2.2.1.1.3.3.1.13 | grep "<ap bssid in decimal format>"
AP Information from Master Switch
wlsxSwitchGlobalAPTable.1.3.6.1.4.1.14823.2.2.1.1.3.4
The following command retrieves the BSSIDs and local switch IP of each AP.
snmpwalk -v 2c -m ALL -c <snmp community name> <Master switch IP addr>.1.3.6.1.4.1.14823.2.2.1.1.3.4

Information from Any AP

wlsrConfigTable.1.3.6.1.4.1.14823.2.3.1.1.1.1
The following information can be retrieved from an AP: Current configuration of SSID, Mode, Current Channel, Tx-Power, RTS Threshold, Retry Limit, Preamble, Beacon Interval, Power Mgmt, Load Balance, Supported Rates, DTIM Period, LMS Address, Encryption, Status, Ageout, MTU, Location, Hide SSID, Deny Broadcast, BG mode, Radio Chipset, Regulatory Domain, Country Code, and Tx Rates.
snmpwalk -v 2c -m ALL -c <snmp community name> <AP IP addr>.1.3.6.1.4.1.14823.2.3.1.1.1.1
Frame Retry Rate per AP BSSID
apBSSFrameRetryRate.1.3.6.1.4.1.14823.2.2.1.1.3.5.1.13
snmpwalk -v 2c -c <snmp community name> <switch IP addr>.1.3.6.1.4.1.14823.2.2.1.1.3.5.1.13 | grep "<ap bssid in decimal format>"
Frame Low-Speed Rate per AP BSSID
apBSSFrameLowSpeedRate.1.3.6.1.4.1.14823.2.2.1.1.3.5.1.14
snmpwalk -v 2c -c <snmp community name> <switch IP addr>.1.3.6.1.4.1.14823.2.2.1.1.3.5.1.14 | grep "<ap bssid in decimal format>"
Frame Receive Error Rate per AP BSSID
apBSSFrameReceiveErrorRate.1.3.6.1.4.1.14823.2.2.1.1.3.5.1.17

wlsrStaFrameHighBandwidthRate 1.3.6.1.4.1.14823.2.3.1.1.3.4.1.1.26

wlsrStaStatsEntry

Syntax Max-Access Status Description Index wlsrStaStatsEntry not-accessible current Station statistics. { wlsrStaAddress}

wlsrStaAddress

Syntax Max-Access Status Description MacAddress not-accessible current The MAC Address of the station connected to this access point.

AP and AM | 59

wlsrStaTxPkts
Syntax Max-Access Status Description Counter32 read-only current The total packets transmitted to the station.

wlsrStaTxBytes

Syntax Max-Access Status Description Counter32 read-only current The total bytes transmitted to the station.

wlsrStaRxPkts

Syntax Max-Access Status Description Counter32 read-only current The total packets received from the station.

wlsrStaRxBytes

Syntax Max-Access Status Description Counter32 read-only current The total bytes received from the station.

wlsrStaTxRetryPkts

Syntax Max-Access Status Description Counter32 read-only current The retry packets transmitted by the station

wlsrStaRxRetryPkts

Syntax Max-Access Status Description Counter32 read-only current The retry packets received from the station.

60 | AP and AM

wlsrStaTxFragmentedPkts
Syntax Max-Access Status Description Counter32 read-only current The fragmented packets transmitted by the station.

wlsrStaRxFragmentedPkts

Syntax Max-Access Status Description Counter32 read-only current The fragmented packets received from the station.

wlsrStaReceiveErrPkts

Syntax Max-Access Status Description Counter32 read-only current The total error packets received from this station.

wlsrStaTxTotSignal

Syntax Max-Access Status Description Integer32 read-only current The attribute indicates the total transmitted signal computed for this station.

wlsrStaTxSignalPkts

Syntax Max-Access Status Description Counter32 read-only current The total signal packets transmitted by this station.

wlsrStaTxCurSignal

Syntax Max-Access Status Description Integer32 read-only current This attribute indicate the stations current transmit signal strength.

AP and AM | 61

wlsrStaTxHighSignal
Syntax Max-Access Status Description Integer32 read-only current This attribute indicate the stations high transmit signal strength.

wlsrStaRxTotNoise

Syntax Max-Access Status Description Counter32 read-only deprecated Total noise.

wlsrStaRxNoisePkts

Syntax Max-Access Status Description Counter32 read-only deprecated Received noise.

wlsrStaRxCurrentNoise

Syntax Max-Access Status Description Integer32 read-only deprecated Current noise.

wlsrTransmitterMac

Syntax Max-Access Status Description MacAddress read-only current This object is used in the traps to indicate the MAC address of the transmitter.

wlsrRSSI

Syntax Max-Access Status Description Integer32 read-only current This object is used in the traps to indicate the signal strength indicator.

wlsrRogueInfoURL

Syntax Max-Access Status Description DisplayString(Size(0.256)) read-only current This object is used to point to the WEBGUI rogue access point information URL.

86 | AP and AM

wlsrInterferingAPInfoURL
Syntax Max-Access Status Description DisplayString(Size(0.256)) read-only current This object is used to point to the WEBGUI rogue interfering access point information URL.

wlsrTrapsGroup

The wlsr Traps group is type notification. Table 21 wlsrTrapsGroup OIDs Object
wlsrUnsecureApDetected wlsrStaImpersonation wlsrReservedChannelViolation wlsrValidSSIDViolation wlsrChannelMisconfiguration wlsrOUIMisconfiguration wlsrSSIDMisconfiguration wlsrShortPreableMisconfiguration wlsrWPAMisconfiguration wlsrAdhocNetworkDetected wlsrStaPolicyViolation wlsrRepeatWEPIVViolation wlsrWeakWEPIVViolation wlsrChannelInterferenceDetected wlsrAPInterferenceDetected wlsrStaInterferenceDetected wlsrFrameRetryRateExceeded wlsrFrameReceiveErrorRateExceeded wlsrFrameFragmentationRateExceeded wlsrFrameBandWidthRateExceeded wlsrFrameLowSpeedRateExceeded wlsrFrameNonUnicastRateExceeded wlsrLoadbalancingEnabled wlsrChannelFrameRetryRateExceeded wlsrChannelFrameFragmentationRateExceeded
1.3.6.1.4.1.14823.2.3.1.1.100.1001 1.3.6.1.4.1.14823.2.3.1.1.100.1002 1.3.6.1.4.1.14823.2.3.1.1.100.1003 1.3.6.1.4.1.14823.2.3.1.1.100.1004 1.3.6.1.4.1.14823.2.3.1.1.100.1005 1.3.6.1.4.1.14823.2.3.1.1.100.1006 1.3.6.1.4.1.14823.2.3.1.1.100.1007 1.3.6.1.4.1.14823.2.3.1.1.100.1008 1.3.6.1.4.1.14823.2.3.1.1.100.1009 1.3.6.1.4.1.14823.2.3.1.1.100.1010 1.3.6.1.4.1.14823.2.3.1.1.100.1011 1.3.6.1.4.1.14823.2.3.1.1.100.1012 1.3.6.1.4.1.14823.2.3.1.1.100.1013 1.3.6.1.4.1.14823.2.3.1.1.100.1014 1.3.6.1.4.1.14823.2.3.1.1.100.1015 1.3.6.1.4.1.14823.2.3.1.1.100.1016 1.3.6.1.4.1.14823.2.3.1.1.100.1017 1.3.6.1.4.1.14823.2.3.1.1.100.1018 1.3.6.1.4.1.14823.2.3.1.1.100.1019 1.3.6.1.4.1.14823.2.3.1.1.100.1020 1.3.6.1.4.1.14823.2.3.1.1.100.1021 1.3.6.1.4.1.14823.2.3.1.1.100.1022 1.3.6.1.4.1.14823.2.3.1.1.100.1023 1.3.6.1.4.1.14823.2.3.1.1.100.1024 1.3.6.1.4.1.14823.2.3.1.1.100.1025 wlsrTrapsGroup 1001 wlsrTrapsGroup 1002 wlsrTrapsGroup 1003 wlsrTrapsGroup 1004 wlsrTrapsGroup 1005 wlsrTrapsGroup 1006 wlsrTrapsGroup 1007 wlsrTrapsGroup 1008 wlsrTrapsGroup 1009 wlsrTrapsGroup 1010 wlsrTrapsGroup 1011 wlsrTrapsGroup 1012 wlsrTrapsGroup 1013 wlsrTrapsGroup 1014 wlsrTrapsGroup 1015 wlsrTrapsGroup 1016 wlsrTrapsGroup 1017 wlsrTrapsGroup 1018 wlsrTrapsGroup 1019 wlsrTrapsGroup 1020 wlsrTrapsGroup 1021 wlsrTrapsGroup 1022 wlsrTrapsGroup 1023 wlsrTrapsGroup 1024 wlsrTrapsGroup 1025

staBwRate

Syntax Max-Access Status Description Integer32 read-only current Bandwidth rate in Kbps of the station.

staFrameRetryRate

Syntax Max-Access Status Description Integer32 read-only current Station frame retry rate.

staFrameLowSpeedRate

Syntax Max-Access Status Description Integer32 read-only current Station frame low speed rate.

staFrameNonUnicastRate

Syntax Max-Access Status Description Integer32 read-only current Station frame non-unicast packet rate.

234 | Switch

staFrameFragmentationRate
Syntax Max-Access Status Description Integer32 read-only current Station frame fragmentation rate.

staFrameReceiveErrorRate

Syntax Max-Access Status Description Integer32 read-only current Station frame receive error rate.

wlsxAccessPointInfoGroup

The wlsx Access Point Info group contains tables that provide access point information. Table 75 wlsxAccessPointInfoGroup OIDs Object
wlsxSwitchTotalNumAccessPoints wlsxSwitchTotalNumStationsAssociated
1.3.6.1.4.1.14823.2.2.1.1.3.1. 1.3.6.1.4.1.14823.2.2.1.1.3.2 wlsxAccessPointInfoGroup 2 wlsxAccessPointInfoGroup 2
wlsxSwitchTotalNumAccessPoints
Syntax Max-Access Status Description Unsigned32 read-only current Total number of access points connected to this switch.
wlsxSwitchTotalNumStationsAssociated
Syntax Max-Access Status Description Unsigned32 read-only current Total number of stations associated to this switch.

Switch | 235

wlsxSwitchAccessPointTable
The objects of the wlsx Switch Access Point table list the access points connected to this switch. Table 76 wlsxSwitchAccessPointTable OIDs Object
wlsxSwitchAccessPointEntry apBSSID apESSID apSlot apPort apIpAddress apPhyType apType apCurrentChannel apLocation apTotalTime apInactiveTime apLoadBalancing apChannelNoise apSignalToNoiseRatio apTransmitRate apReceiveRate
1.3.6.1.4.1.14823.2.2.1.1.3.3.1 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.1 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.2 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.3 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.4 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.5 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.6 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.7 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.8 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.9 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.10 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.11 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.12 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.13 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.14 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.15 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.16 wlsxSwitchAccessPointTable 1 wlsxSwitchAccessPointEntry 1 wlsxSwitchAccessPointEntry 2 wlsxSwitchAccessPointEntry 3 wlsxSwitchAccessPointEntry 4 wlsxSwitchAccessPointEntry 5 wlsxSwitchAccessPointEntry 6 wlsxSwitchAccessPointEntry 7 wlsxSwitchAccessPointEntry 8 wlsxSwitchAccessPointEntry 9 wlsxSwitchAccessPointEntry 10 wlsxSwitchAccessPointEntry 11 wlsxSwitchAccessPointEntry 12 wlsxSwitchAccessPointEntry 13 wlsxSwitchAccessPointEntry 14 wlsxSwitchAccessPointEntry 15 wlsxSwitchAccessPointEntry 16

wlsxCoverageHoleDetected

Objects Status Description { apLocation, apIpAddress, wlsxStationMacAddress } current A trap which indicates that an access point at location apLocation and address apIpAddress has detected a coverage hole.

wlsxChannelChanged

Objects Status Description { apLocation, apIpAddress, apCurrentChannel } deprecated A trap which indicates that an access point at location apLocation and address apIpAddress has changed the channel to apCurrentChannel.

Switch | 257

wlsxStationAddedToBlackList
Objects Status Description { wlsxStationMacAddress, wlsxStationBlackListReason } current A trap which indicates that a station with address wlsxStationMacAddress is black listed for wlsxStationBlackListReason reason.
wlsxStationRemovedFromBlackList
Objects Status Description { wlsxStationMacAddress } current A trap which indicates that a station with address wlsxStationMacAddress is removed from black list.

wlsxIpSpoofingDetected

Objects Status Description { wlsxSpoofedIpAddress, wlsxSpoofedOldPhyAddress, wlsxSpoofedNewPhyAddress } current A trap indicating that the switch detected IP spoofing.
wlsxDBCommunicationFailure
Objects Status Description { wlsxDBName, wlsxDBUserName, wlsxDBIpAddress, wlsxDBType } current A trap to indicate that communication with database failed.

wlsxVrrpStateChange

Objects Status Description { wlsxVrID, wlsxVrMasterIp, wlsxVrrpOperState } current A trap which indicates that VRRP state has changed on the switch.
wlsxAPRadioAttributesChanged
Objects Status Description { apLocation, apIpAddress, apCurrentChannel, wlsxApTxPower } current A trap which indicates changes in the radio attributes of an access point at location apLocation and address ap IpAddress. Ap channel is apCurrentChannel Transmit power is apTxPower

258 | Switch

wlsxESIServerUp
Objects Status Description { wlsxESIServerGrpName, wlsxESIServerName, wlsxESIServerIpaddress } current A trap which indicates that a ESI server <wlsxESIServerName> in group <wlsxESIServerGrpName> with <wlsxESIServerIpaddress> is up.

Syntax Status Description History Integer success(1), error(2) current Configuration transfer types. Added in AOS-W 3.1
ArubaConfigurationChangeType
Syntax Integer create(1) delete(2) modify(3) current Configuration change types. Added in AOS-W 3.1
296 | Textual Conventions

ArubaCallStates

Syntax Integer idle(0) initiated(1) connecting(2) delivered(3) connected(4) offered(5) alerting(6) releasing(7) cancelling(8) transient(9) dummy503(10) succ(11), fail(12) aborted(13) blocked(14) current The call state. Added in AOS-W 3.1

ArubaVoipProtocol

Syntax Integer sccp(1) svp(2) vocera(3) sip(9) ua(11) current VoIP protocol used. Added in AOS-W 3.1

ArubaVoipRegState

Syntax Integer unkown(0) registering(1) unregistering(2) challenge(3) registered(4) unregistered(5) current VoIP registered state. Added in AOS-W 3.1
Textual Conventions | 297

ArubaVoiceCdrDirection

Syntax Integer og(0) ic(1) current VoIP CDR direction. Added in AOS-W 3.1

ArubaVoiceCacBit

Syntax Bits cacActiveLoadBalancing(0) cacHighCapThresholdReached(1) cacHandRsrvThresholdReached(2) cacPeakCapacityReached(3) current Voice CAC bit flags. Added in AOS-W 3.1

ArubaMeshRole

Syntax Integer nonmesh(0) point(1) portal(2) current Mesh role. Added in AOS-W 3.2.0.0.
298 | Textual Conventions

ArubaHTRate

Syntax Integer unknown(0) ht6dot5(1) ht13(2) ht13dot5(3) ht15(4) ht19dot5(5) ht26(6) ht27(7) ht30(8) ht39(9) ht40dot5(10) ht45(11) ht52(12) ht54(13) ht58dot5(14) ht60(15) ht65(16) ht78(17) ht81(18) ht90(19) ht104(20) ht108(21) ht117(22) ht120(23) ht121dot5(24) ht130(25) ht135(26) ht150(27) ht162(28) ht180(29) ht216(30) ht240(31) ht243(32) ht270(33) ht300(34) current Represents HT rate. Added in AOS-W 3.2.0.0.
Textual Conventions | 299
300 | Textual Conventions

Chapter 15

This module defines the Traps that can be generated by the. Traps are MIB objects (variables) that transmit information to the SNMP Manager when an event occurs. Traps are included as varbinds (variable bindings) in the trap protocol data unit (PDU). Varbinds are defined in the Description section of the tables of the following sections. Figure 16 shows the architecture of the Traps MIB relative to 1.3.6.1.4.1.14823 (iso.org.dod.internet.private.enterprise.aruba). The Traps are listed in the file aruba-trap.my. For information about downloading Aruba MIB files, see Downloading MIB Files on page 23. Figure 16 Trap Hierarchy

Aruba AP

wlsx Trap MIB
1.3.6.1.4.1.14823.2.3.1.11

Syntax Max-Access Status Description MacAddress accessible-for-notify current This object represents the MAC address of the user.

wlsxTrapUserName

Syntax Max-Access Status Description DisplayString(Size(0.64)) accessible-for-notify current This object represents the user name.

wlsxTrapUserRole

Syntax Max-Access Status Description DisplayString(Size(0.64)) accessible-for-notify current This object represents the authentication method of the user.

Traps | 313

wlsxTrapUserAuthenticationMethod
Syntax Max-Access Status Description ArubaAuthenticationMethods accessible-for-notify current This object represents the authentication method of the user.

wlsxTrapAPRadioNumber

Syntax Max-Access Status Description Integer32 accessible-for-notify current This object represents the radio number.

wlsxTrapRogueInfoURL

Syntax Max-Access Status Description DisplayString(Size(0.64)) accessible-for-notify current This object is used to point to the WEBGUI Rogue AP information URL.
wlsxTrapInterferingAPInfoURL
Syntax Max-Access Status Description DisplayString(Size(0.64)) accessible-for-notify current This object is used to point to the WEBGUI Rogue interfering access point information URL.

wlsxTrapPortNumber

Syntax Max-Access Status Description Integer32 accessible-for-notify current This object is used in the traps to indicate the port number.

wlsxTrapTime

Syntax Max-Access Status Description DateAndTime accessible-for-notify current This object is used in all the enterprise traps to indicate the time when the trap is generated on the switch.

314 | Traps

wlsxTrapHostIp
Syntax Max-Access Status Description IpAddress accessible-for-notify current This object represents the trap host.

wlsxTrapHostPort

Syntax Max-Access Status Description Integer32 accessible-for-notify current This object represents the trap host port.

wlsxInterferingApDetected
Objects { wlsxTrapTargetAPBSSID, wlsxTrapTargetAPSSID, wlsxTrapAPMacAddress, wlsxTrapAPRadioNumber, wlsxTrapAPLocation, wlsxTrapAPChannel, wlsxTrapInterferingAPInfoURL } current This trap indicates that an interfering access point is detected by an air monitor located at wlsrLocation on channel wlsrCurrentChannel. Added in AOS-W 3.1.0.0.

wlsxPortUp

Objects Status Description { wlsxTrapCardSlot, wlsxTrapPortNumber, wlsxTrapAdminStatus, wlsxTrapOperStatus } current This trap indicates that a physical port is up.

wlsxPortDown

Objects Status Description { wlsxTrapCardSlot, wlsxTrapPortNumber, wlsxTrapAdminStatus, wlsxTrapOperStatus } current This trap indicates that a physical port is down.

wlsxBSSIDIsUpS

Objects Status Description { wlsxTrapAPMacAddress, wlsxTrapAPRadioNumber, wlsxTrapAPBSSID } current This trap indicates that an access point is up.

Traps | 341

wlsxBSSIDIsDown
Objects Status Description { wlsxTrapAPMacAddress, wlsxTrapAPRadioNumber, wlsxTrapAPBSSID } current This trap indicates that an access point is down.

wlsxColdStart

Status Description current An enterprise version of cold start trap, which contains the switch time stamp.

wlsxWarmStart

Status current

wlsxAPImpersonation

Objects Status Description { wlsxTrapTargetAPBSSID, wlsxTrapTargetAPSSID, wlsxTrapAPMacAddress, wlsxTrapAPRadioNumber, wlsxTrapAPLocation, wlsxTrapAPChannel } current This trap indicates that an air monitor detected station impersonation.

wlsxInformQueueOverFlow

Objects Status Description { wlsxTrapHostIp, wlsxTrapHostPort } current This trap indicates that an inform queue overflow condition occurred.

wlsxNAuthServerIsDown

Objects Status Description History { wlsxTrapTime, wlsxTrapAuthServerName } current This trap indicates that an authentication server is down. Added in AOS-W 3.1.0.0.

wlsxCTSTransferError

Objects Status Description History { wlsxTrapTime, wlsxTrapCTSTransferType, wlsxTrapCTSURL } current This trap indicates the status of the configuration transfer from the management station. Added in AOS-W 3.1.0.0.

342 | Traps

wlsxCTSTransferSucceeded
wlsxConfigurationUpdateError
Objects Status Description History { wlsxTrapTime, wlsxTrapConfigurationId, wlsxTrapUpdateFailureReason, wlsxTrapUpdateFailedObj } current This trap indicates the configuration update status. Added in AOS-W 3.1.0.0.
wlsxConfigurationUpdateSucceeded
Objects Status Description History { wlsxTrapTime, wlsxTrapConfigurationId } current This trap indicates the configuration update status. Added in AOS-W 3.1.0.0.

wlsxUser6SessionTimeLength
Syntax Max-Access Status Description History Integer32 not-accessible current Pre-defined user session time length. Added in AOS-W 3.3.0.0.

wlsxUser6SessionTime

Syntax Max-Access Status Description History Counter32 read-only current Number of users that are connected to the essid whose sessions expired in this time interval. Added in AOS-W 3.3.0.0.

User6 | 375

376 | User6
The Voice module provides information about Voice call status and call detail reporting. Figure 19 shows the architecture of the User MIB relative to 1.3.6.1.4.1.14823 (iso.org.dod.internet.private.enterprise.aruba). The Voice MIBs are listed in the file aruba-voice.my. For information about downloading Aruba MIB files, see Downloading MIB Files on page 23.

Voice | 377

Figure 19 Voice Hierarchy

wlsx Voice MIB Modules

1.3.6.1.4.1.14823.2.3.1.12

wlsx Voice Stats Group

1.3.6.1.4.1.14823.2.3.1.12.1
wlsx Voice Cdr Info Group
1.3.6.1.4.1.14823.2.3.1.12.1.1
wlsx Voice Call Ctrs Group
1.3.6.1.4.1.14823.2.3.1.12.1.2 1.3.6.1.4.1.14823.2.3.1.12.1.2.1
wlsx Voice Call Ctrs Total
wlsx Voice Client Info Group wlsx Voice Client Table
1.3.6.1.4.1.14823.2.3.1.12.1.3 1.3.6.1.4.1.14823.2.3.1.12.1.3.2
wlsx Voice AP Bssid Info Group wlsx Voice AP Bssid Total
1.3.6.1.4.1.14823.2.3.1.12.1.4 1.3.6.1.4.1.14823.2.3.1.12.1.4.1 1.3.6.1.4.1.14823.2.3.1.12.1.4.2
wlsx Voice AP Bssid Table
Table 100 Voice MIB Objects Table
This object lists the total number of call detail records of the switch. This table lists information of the call detail records of the switch. This table lists the number of calls through the call center. This table lists the total number of active calls of the client. This table lists all voice client information. This object lists the total number of active VoIP. This table lists active VoIP information.

378 | Voice

wlsxVoiceCdrTotal
The integer object of wlsx Voice CDR total lists the total number of Call Detail Records of the switch.
Syntax Max-Access Status Description History Unsigned32 read-only current Total number of CDR information in the switch. Added in AOS-W 3.2.0.0.

wlsxVoiceAPBssidEntry

Syntax max-Access Status Description Index History VoiceAPBssidEntry not-accessible current Entry to AP. {wlanAPMacAddress, wlanAPRadioNumber, wlanAPBSSID} Added in AOS-W 3.2.0.0.

voiceAPBssidName

Syntax Max-Access Status Description History DisplayString read-only current Voice access point name. Added in AOS-W 3.2.0.0.

voiceAPBssidGroup

Syntax Max-Access Status Description History DisplayString read-only current Voice access point group. Added in AOS-W 3.2.0.0.

Voice | 391

voiceAPBssidIp
Syntax Max-Access Status Description History IpAddress read-only current Voice access point IP address. Added in AOS-W 3.2.0.0.

voiceAPBssidTotCalls

Syntax Max-Access Status Description History Unsigned32 read-only current Voice access point total calls. Added in AOS-W 3.2.0.0.

voiceAPBssidVoiceType

Syntax Max-Access Status Description History DisplayString read-only current Voice access point type. Added in AOS-W 3.2.0.0.

voiceAPBssidFlag

Syntax Bits apRemoteAP(0) apPPPOE(1) apWiredApEnabled(2) apEnet1Mode(3) apActiveLoadBalancing(4) apDisconnectExtraCalls(5) apBatteryBoost(6) read-only current Voice access point flag. Added in AOS-W 3.2.0.0.

392 | Voice

voiceAPBssidUpTime
Syntax Max-Access Status Description History TimeTicks read-only current Voice access point up time Added in AOS-W 3.2.0.0.

voiceAPBssid100Sent

Syntax Max-Access Status Description History Counter32 read-only current Voice 100 sent. Added in AOS-W 3.2.0.0.

voiceAPBssid503Sent

Syntax Max-Access Status Description History Counter32 read-only current Voice 503 sent. Added in AOS-W 3.2.0.0.
voiceAPBssidExtraCallDisc
Syntax Max-Access Status Description History Counter32 read-only current Voice access point extra call disconnect. Added in AOS-W 3.2.0.0.

voiceAPBssidKickedOff

Added in AOS-W 3.2.0.0.

wlsxWlanRadioTable

The objects of the wlsx WLAN Radio table provide information on the access points connected in radios that are known to the Alcatel-Lucent switch. This table is indexed by the MAC address of the AP and the type of the radio. Table 109 wlsxWlanRadioTable OIDs Object
wlsxWlanRadioEntry wlanAPRadioNumber wlanAPRadioType wlanAPRadioChannel wlanAPRadioTransmitPower wlanAPRadioMode wlanAPRadioUtilization wlanAPRadioNumAssociatedClients wlanAPRadioNumMonitoredClients wlanAPRadioNumActiveBSSIDs wlanAPRadioNumMonitoredBSSIDs wlanAPRadioBearing wlanAPRadioTiltAngle wlanAPRadioHTMode wlanAPRadioHTExtChannel wlanAPRadioHTChannel
1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.1 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.2 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.3 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.4 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.5 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.6 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.7 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.8 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.9 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.10 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.11 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.12 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.13 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.14 1.3.6.1.4.1.14823.2.2.1.5.2.1.5.1.15 wlsxWlanRadioTable 1 wlsxWlanRadioEntry 1 wlsxWlanRadioEntry 2 wlsxWlanRadioEntry 3 wlsxWlanRadioEntry 4 wlsxWlanRadioEntry 5 wlsxWlanRadioEntry 6 wlsxWlanRadioEntry 7 wlsxWlanRadioEntry 8 wlsxWlanRadioEntry 9 wlsxWlanRadioEntry 10 wlsxWlanRadioEntry 11 wlsxWlanRadioEntry 12 wlsxWlanRadioEntry 13 wlsxWlanRadioEntry 14 wlsxWlanRadioEntry 15

wlsxWlanRadioEntry

Syntax Max-Access Status Description History WlanRadioEntry not-accessible current Index {wlanAPMacAddress, wlanAPRadioNumber} Added in AOS-W 2.3.

WLAN | 409

wlanAPRadioNumber
Syntax Max-Access Status Description History Integer32 not-accessible current The number of the radio Added in AOS-W 2.3. Updated in AOS-W 3.2.0.0.description.

wlanAPRadioType

Syntax Max-Access Status Description History ArubaPhyType read-write current Type of the radio Added in AOS-W 2.3. Updated in AOS-W 3.2.0.0.Max-Access changed from read-only to read-write

wlanAPRadioChannel

Syntax Max-Access Status Description History Integer32 read-only current The channel the radio is currently operating on. Added in AOS-W 2.3. Updated in AOS-W OS 3.2description.

wlanAPRadioTransmitPower

516 | SNMP MIBs Reference
wlsxIfExtPortEntry ifExtSlotNumber ifExtPortNumber ifExtPortIfIndex ifExtAdminState ifExtOperState ifExtPoeState ifExtIsTrusted ifExtDot1DState ifExtMode ifExtAccessVlanId ifExtTrunkNativeVlanId ifExtTrunkIsAllowedAll ifExtTrunkAllowedVlanList ifExtIngressACLName ifExtEgressACLName ifExtSessionACLName ifExtXsecVlan ifExtIsMonitoring ifExtIsMux ifExtUserSlotNumber ifExtUserPortNumber ifExtPortSpeed ifExtPortDuplex ifExtPortType ifExtDescr wlsxIfExtVlanTable wlsxIfExtVlanEntry ifExtVlanId ifExtVlanName ifExtVlanStatus wlsxIfExtVlanMemberTable wlsxIfExtVlanMemberEntry ifExtVlanMemberStatus
.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.1.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.2.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.3.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.4.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.5.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.6.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.7.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.8.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.9.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.10.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.11.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.12.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.13.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.14.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.15.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.16.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.17.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.18.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.19.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.20.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.21.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.22.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.23.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.24.1.3.6.1.4.1.14823.2.2.1.3.1.1.1.25.1.3.6.1.4.1.14823.2.2.1.3.1.2.1.3.6.1.4.1.14823.2.2.1.3.1.2.1.1.3.6.1.4.1.14823.2.2.1.3.1.2.1.1.1.3.6.1.4.1.14823.2.2.1.3.1.2.1.2.1.3.6.1.4.1.14823.2.2.1.3.1.2.1.3.1.3.6.1.4.1.14823.2.2.1.3.1.3.1.3.6.1.4.1.14823.2.2.1.3.1.3.1.1.3.6.1.4.1.14823.2.2.1.3.1.3.1.1
SNMP MIBs Reference | 517
ifExtVlanMemberSlot ifExtVlanMemberPort ifExtVlanMemberType wlsxIfExtVlanInterfaceTable wlsxIfExtVlanInterfaceEntry ifExtVlanInterfaceIfIndex ifExtVlanInterfaceDescription ifExtVlanInterfaceBWContract ifExtVlanInterfaceAdminState ifExtVlanInterfaceOperState ifExtVlanInterfaceIpAddress ifExtVlanInterfaceIpMask ifExtVlanInterfaceIsLocalArp ifExtVlanInterfaceStatus ifExtVlanInterfaceIpRouting ifExtVlanInterfaceIpNatInside ifExtVlanInterfaceIpIgmpSnooping wlsxUserMIB wlsxUserAllInfoGroup wlsxTotalNumOfUsers wlsxUserTable wlsxUserEntry nUserPhyAddress nUserIpAddress nUserName nUserRole nUserUpTime nUserAuthenticationMethod nUserSubAuthenticationMethod nUserAuthServerName nUserExtVPNAddress nUserApLocation nUserApBSSID nUserIsOnHomeAgent
.1.3.6.1.4.1.14823.2.2.1.3.1.3.1.2.1.3.6.1.4.1.14823.2.2.1.3.1.3.1.3.1.3.6.1.4.1.14823.2.2.1.3.1.3.1.4.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.1.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.2.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.3.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.4.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.5.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.6.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.7.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.8.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.9.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.10.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.11.1.3.6.1.4.1.14823.2.2.1.3.1.4.1.12.1.3.6.1.4.1.14823.2.2.1.4.1.3.6.1.4.1.14823.2.2.1.4.1.1.3.6.1.4.1.14823.2.2.1.4.1.1.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.1.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.2.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.3.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.4.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.5.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.6.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.7.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.8.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.9.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.10.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.11.1.3.6.1.4.1.14823.2.2.1.4.1.2.1.12

wlanAPStatsTotPktsAtHT117Mbps. 450 wlanAPStatsTotPktsAtHT120Mbps. 450 wlanAPStatsTotPktsAtHT121dot5Mbps. 451 wlanAPStatsTotPktsAtHT130Mbps. 451 wlanAPStatsTotPktsAtHT135Mbps. 452 wlanAPStatsTotPktsAtHT13dot5Mbps. 441 wlanAPStatsTotPktsAtHT13Mbps. 440 wlanAPStatsTotPktsAtHT150Mbps. 452 wlanAPStatsTotPktsAtHT15Mbps. 441 wlanAPStatsTotPktsAtHT162Mbps. 453 wlanAPStatsTotPktsAtHT180Mbps. 453 wlanAPStatsTotPktsAtHT19dot5Mbps. 442 wlanAPStatsTotPktsAtHT216Mbps. 454 wlanAPStatsTotPktsAtHT240Mbps. 454 wlanAPStatsTotPktsAtHT243Mbps. 454 wlanAPStatsTotPktsAtHT26Mbps. 442 wlanAPStatsTotPktsAtHT270Mbps. 455 wlanAPStatsTotPktsAtHT27Mbps. 443 wlanAPStatsTotPktsAtHT300Mbps. 455 wlanAPStatsTotPktsAtHT30Mbps. 443 wlanAPStatsTotPktsAtHT39Mbps. 444 wlanAPStatsTotPktsAtHT40dot5Mbps. 444 wlanAPStatsTotPktsAtHT45Mbps. 444 wlanAPStatsTotPktsAtHT52Mbps. 445 wlanAPStatsTotPktsAtHT54Mbps. 445 wlanAPStatsTotPktsAtHT58dot5Mbps. 446 wlanAPStatsTotPktsAtHT60Mbps. 446 wlanAPStatsTotPktsAtHT65Mbps. 447 wlanAPStatsTotPktsAtHT6dot5Mbp. 440 wlanAPStatsTotPktsAtHT78Mbps. 447 wlanAPStatsTotPktsAtHT81Mbps. 448 wlanAPStatsTotPktsAtHT90Mbps. 448 wlsxHT40MHzIntoleranceAP. 352 wlsxHT40MHzIntoleranceSta. 352 wlsxHtGreenfieldSupported. 352 wlsxMonStationHTRateStatsEntry. 202 wlsxSwitchUser6Entry. 227 wlsxTotalNumOfUsers6. 366 wlsxUser6AllInfoGroup. 366, 494 wlsxUser6AuthenticationFailed. 260 wlsxUser6EntryAuthenticated. 259 wlsxUser6EntryCreated. 259 wlsxUser6EntryDeAuthenticated. 260 wlsxUser6EntryDeleted. 259 wlsxUser6SessionTime. 375 wlsxUser6SessionTimeLength. 375 wlsxUser6SessionTimeTable. 375 wlsxUser6Table. 366 AOS-W 3.3.0.0 wlanStaHTMod. 424 home agent. 131

inform request. 21

Index | 565
Location user station. 353

WMS. 109, 397

mesh. 127 MIB files. 23

network traffic. 149

ping alarms. 21 ports. 113
resource usage. 261 roaming agent. 131
Scan RF spectrum. 35 signal quality. 205 SNR. 205 switch. 213, 365, 493 synchronize. 105
TC. 285 terminal server function. 22 Traffic redirect. 109 Traps access points. 83 information. 21 MIB hierarchy. 301 switch trap notifications. 252 switch traps. 246 types. 21 wlsx trap definitions. 318 wlsx trap objects group. 302

user access. 353

VLAN. 113 voice status. 377

566 | Index