2 vs. 3 spatial streams or 3502 vs. 3602?

Hello,
I have a customer asking why I would recommend a 3602E over a 3502E.
An extra spatial stream and the purported field upgradeability to 802.11ac seem to be the most compelling.
My question: In a deployment where 5Ghz 802.11n 40Mhz client NICs have, at most, two dual band external antennas, will three spatial streams increase theoretical throughput capacity, especially in a scenario where clients are uploading multiple gigabyte files over the air?
On a related note, anybody aware of robust commercial grade 802.11ac NICs on the horizon?
Thanks!

I'd like to chime in, since George and Scott has already discussed all aspects already.
The next question is WHAT clients?
Smartphones and tablets are notorious, in marketing data sheets, for muddling the facts. True, they can "support" 802.11n, I'll be a d1ck and say 2 x 3 MIMO. The question I normally throw is this: Can the product really push 300 Mbps? The answer is no. Smartphones and tablets, in the current market, do not have the capacity to transmit nor the power to process 300 Mbps.
Current smartphones and tablets can't process more than MCS 7 (around 35 Mbps). I am not sure about the new 802.11ac smartphones and tablets (like the Samsung Galaxy S4) as George hasn't gotten around yet.

Similar Messages

Beamforming vs Spatial Stream

Hi everyone,
Currently I'm study on wireless. I'm confused between beamforming and spatial stream. Are they the same technologies? Or before spatial stream is running after beamforming was formed?
Thanks and Regards,
Ong

Hi Ong,
Refer below as it explain what beamforming or client link specific to Cisco technology.
http://www.cisco.com/c/dam/en/us/products/collateral/wireless/aironet-3600-series/at_a_glance_c45-691984.pdf
http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1130-ag-series/white_paper_c11-516389.html
Spatial streams are way of transmitting & receiving multiple data streams when client or AP having multiple Tx/Rx radios. Here is some useful video on that
https://www.youtube.com/watch?v=rP3ggDP_Ero
HTH
Rasika
**** Pls rate all useful responses ****

Is AP-3602 a 3:4:3 or a 4:4:3 ?

If the nomenclature is x:y:z, where x = transmitters, y = receivers, and z = spatial streams, and the 1262 is 2:3:2 (two TX, three RX, 2 streams), then what is a 3602 ?
I've seen both 4:4:3 and 3:4:3. Are there three or 4 transmitters ? I get there are four receivers.

4 transmitters allows you to beamform to 802.11n devices. You can't beamform to 802.11n devices with 2 transmitters. The more transmitters and receivers you have the better perceived signal you can acheive on each end when you combine the RF data streams.
This is a good article that goes over in detail the benefits of the multiple transmitters/receivers and spatial streams:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps10092/white_paper_c11-516389.html

How many clients support access points 1602, 2602, 3602?

Hi! How many clients support access point 1602, 2602, 3602. I have found for example that the 1602 supports 32 ClientLink clients and max 128 clients, APs 2602, 3602 supports 128 ClientLink clients and max 200 clients. But is it really? And can we say for example that the AP 2602 will withstand max 200 clients?

The reason the answer varies so much, is because there are so many variables (this is also why the value ranges so much from one manufacture to the next). When determining the answer you are looking for you need to consider the following factors and likely more:
AP model and the features it supports
single, dual, or tri radio AP
20, 40, or 80Mhz wide channels
Device type (b/g, b/g/n, a/b/g/n, a/b/g/n/ac, spatial stream support, and channel width support)
Security/QOS method(s) employed
Average distance from the AP
Obstructions between devices and radios
Number of competing radios for the same channel
Data rates configuration
Rogue detection/mitigation configuration
Surrounding client density not just the area of concern client density
Noise floor levels
Application types/per user network load (is it heavy like YouTube traffic or a drone on the network like Pandora)
Network latency on the switching side - including the internet circuit
Application of per SSID, per user, and or per application rate limiting
The list continues, but I think you get the idea
I have personally seen 80 devices on a 5Ghz radio of a 3500 access point with several other access points and at least 200 other clients in the area and it was working well. That being said I would never design to expect that many on a single radio, but I think it is better said that you can safely design for 20-30 clients per 2.4Ghz radio and 25-40 clients per 5Ghz radio.
The default statement of 20-25 per AP and similar low expectation statements concerning Cisco wireless have been around for many years. It is now 2014. About 65% of clients support 5Ghz, ~9% support AC (already), ~90% support some form of N, and ~0.01% support B only. The landscape of wireless is changing fast making questions like this one have ever changing answers.
I hope this helps :).
John

Hostapd - client sees network but can't connect

I have a mobile phone Samsung S5230W with WiFi capability, and a laptop HP Compaq nx7400 with Broadcom BCM4311 wireless card. I'm trying to share an Internet connection between those two devices, but I can't because i receive 'authentication failed' message, even that the password is right -
##### hostapd configuration file ##############################################
# Empty lines and lines starting with # are ignored
# AP netdevice name (without 'ap' postfix, i.e., wlan0 uses wlan0ap for
# management frames); ath0 for madwifi
interface=wlan0
# In case of madwifi, atheros, and nl80211 driver interfaces, an additional
# configuration parameter, bridge, may be used to notify hostapd if the
# interface is included in a bridge. This parameter is not used with Host AP
# driver. If the bridge parameter is not set, the drivers will automatically
# figure out the bridge interface (assuming sysfs is enabled and mounted to
# /sys) and this parameter may not be needed.
# For nl80211, this parameter can be used to request the AP interface to be
# added to the bridge automatically (brctl may refuse to do this before hostapd
# has been started to change the interface mode). If needed, the bridge
# interface is also created.
bridge=br0
# Driver interface type (hostap/wired/madwifi/test/none/nl80211/bsd);
# default: hostap). nl80211 is used with all Linux mac80211 drivers.
# Use driver=none if building hostapd as a standalone RADIUS server that does
# not control any wireless/wired driver.
driver=nl80211
# hostapd event logger configuration
# Two output method: syslog and stdout (only usable if not forking to
# background).
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
# bit 3 (8) = WPA
# bit 4 (16) = driver interface
# bit 5 (32) = IAPP
# bit 6 (64) = MLME
# Levels (minimum value for logged events):
# 0 = verbose debugging
# 1 = debugging
# 2 = informational messages
# 3 = notification
# 4 = warning
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
# Dump file for state information (on SIGUSR1)
dump_file=/tmp/hostapd.dump
# Interface for separate control program. If this is specified, hostapd
# will create this directory and a UNIX domain socket for listening to requests
# from external programs (CLI/GUI, etc.) for status information and
# configuration. The socket file will be named based on the interface name, so
# multiple hostapd processes/interfaces can be run at the same time if more
# than one interface is used.
# /var/run/hostapd is the recommended directory for sockets and by default,
# hostapd_cli will use it when trying to connect with hostapd.
ctrl_interface=/var/run/hostapd
# Access control for the control interface can be configured by setting the
# directory to allow only members of a group to use sockets. This way, it is
# possible to run hostapd as root (since it needs to change network
# configuration and open raw sockets) and still allow GUI/CLI components to be
# run as non-root users. However, since the control interface can be used to
# change the network configuration, this access needs to be protected in many
# cases. By default, hostapd is configured to use gid 0 (root). If you
# want to allow non-root users to use the contron interface, add a new group
# and change this value to match with that group. Add users that should have
# control interface access to this group.
# This variable can be a group name or gid.
#ctrl_interface_group=wheel
#ctrl_interface_group=0
##### IEEE 802.11 related configuration #######################################
# SSID to be used in IEEE 802.11 management frames
ssid=network
# Country code (ISO/IEC 3166-1). Used to set regulatory domain.
# Set as needed to indicate country in which device is operating.
# This can limit available channels and transmit power.
#country_code=US
# Enable IEEE 802.11d. This advertises the country_code and the set of allowed
# channels and transmit power levels based on the regulatory limits. The
# country_code setting must be configured with the correct country for
# IEEE 802.11d functions.
# (default: 0 = disabled)
#ieee80211d=0
# Operation mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g,
# Default: IEEE 802.11b
hw_mode=g
# Channel number (IEEE 802.11)
# (default: 0, i.e., not set)
# Please note that some drivers (e.g., madwifi) do not use this value from
# hostapd and the channel will need to be configuration separately with
# iwconfig.
channel=1
# Beacon interval in kus (1.024 ms) (default: 100; range 15..65535)
beacon_int=100
# DTIM (delivery trafic information message) period (range 1..255):
# number of beacons between DTIMs (1 = every beacon includes DTIM element)
# (default: 2)
dtim_period=2
# Maximum number of stations allowed in station table. New stations will be
# rejected after the station table is full. IEEE 802.11 has a limit of 2007
# different association IDs, so this number should not be larger than that.
# (default: 2007)
max_num_sta=5
# RTS/CTS threshold; 2347 = disabled (default); range 0..2347
# If this field is not included in hostapd.conf, hostapd will not control
# RTS threshold and 'iwconfig wlan# rts <val>' can be used to set it.
rts_threshold=2347
# Fragmentation threshold; 2346 = disabled (default); range 256..2346
# If this field is not included in hostapd.conf, hostapd will not control
# fragmentation threshold and 'iwconfig wlan# frag <val>' can be used to set
# it.
fragm_threshold=2346
# Rate configuration
# Default is to enable all rates supported by the hardware. This configuration
# item allows this list be filtered so that only the listed rates will be left
# in the list. If the list is empty, all rates are used. This list can have
# entries that are not in the list of rates the hardware supports (such entries
# are ignored). The entries in this list are in 100 kbps, i.e., 11 Mbps = 110.
# If this item is present, at least one rate have to be matching with the rates
# hardware supports.
# default: use the most common supported rate setting for the selected
# hw_mode (i.e., this line can be removed from configuration file in most
# cases)
supported_rates=10 20 55 110 60 90 120 180 240 360 480 540
# Basic rate set configuration
# List of rates (in 100 kbps) that are included in the basic rate set.
# If this item is not included, usually reasonable default set is used.
#basic_rates=10 20
#basic_rates=10 20 55 110
#basic_rates=60 120 240
# Short Preamble
# This parameter can be used to enable optional use of short preamble for
# frames sent at 2 Mbps, 5.5 Mbps, and 11 Mbps to improve network performance.
# This applies only to IEEE 802.11b-compatible networks and this should only be
# enabled if the local hardware supports use of short preamble. If any of the
# associated STAs do not support short preamble, use of short preamble will be
# disabled (and enabled when such STAs disassociate) dynamically.
# 0 = do not allow use of short preamble (default)
# 1 = allow use of short preamble
#preamble=1
# Station MAC address -based authentication
# Please note that this kind of access control requires a driver that uses
# hostapd to take care of management frame processing and as such, this can be
# used with driver=hostap or driver=nl80211, but not with driver=madwifi.
# 0 = accept unless in deny list
# 1 = deny unless in accept list
# 2 = use external RADIUS server (accept/deny lists are searched first)
macaddr_acl=0
# Accept/deny lists are read from separate files (containing list of
# MAC addresses, one per line). Use absolute path name to make sure that the
# files can be read on SIGHUP configuration reloads.
#accept_mac_file=/etc/hostapd/hostapd.accept
#deny_mac_file=/etc/hostapd/hostapd.deny
# IEEE 802.11 specifies two authentication algorithms. hostapd can be
# configured to allow both of these or only one. Open system authentication
# should be used with IEEE 802.1X.
# Bit fields of allowed authentication algorithms:
# bit 0 = Open System Authentication
# bit 1 = Shared Key Authentication (requires WEP)
auth_algs=1
# Send empty SSID in beacons and ignore probe request frames that do not
# specify full SSID, i.e., require stations to know SSID.
# default: disabled (0)
# 1 = send empty (length=0) SSID in beacon and ignore probe request for
# broadcast SSID
# 2 = clear SSID (ASCII 0), but keep the original length (this may be required
# with some clients that do not support empty SSID) and ignore probe
# requests for broadcast SSID
ignore_broadcast_ssid=0
# TX queue parameters (EDCF / bursting)
# default for all these fields: not set, use hardware defaults
# tx_queue_<queue name>_<param>
# queues: data0, data1, data2, data3, after_beacon, beacon
# (data0 is the highest priority queue)
# parameters:
# aifs: AIFS (default 2)
# cwmin: cwMin (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023)
# cwmax: cwMax (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023); cwMax >= cwMin
# burst: maximum length (in milliseconds with precision of up to 0.1 ms) for
# bursting
# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e):
# These parameters are used by the access point when transmitting frames
# to the clients.
# Low priority / AC_BK = background
#tx_queue_data3_aifs=7
#tx_queue_data3_cwmin=15
#tx_queue_data3_cwmax=1023
#tx_queue_data3_burst=0
# Note: for IEEE 802.11b mode: cWmin=31 cWmax=1023 burst=0
# Normal priority / AC_BE = best effort
#tx_queue_data2_aifs=3
#tx_queue_data2_cwmin=15
#tx_queue_data2_cwmax=63
#tx_queue_data2_burst=0
# Note: for IEEE 802.11b mode: cWmin=31 cWmax=127 burst=0
# High priority / AC_VI = video
#tx_queue_data1_aifs=1
#tx_queue_data1_cwmin=7
#tx_queue_data1_cwmax=15
#tx_queue_data1_burst=3.0
# Note: for IEEE 802.11b mode: cWmin=15 cWmax=31 burst=6.0
# Highest priority / AC_VO = voice
#tx_queue_data0_aifs=1
#tx_queue_data0_cwmin=3
#tx_queue_data0_cwmax=7
#tx_queue_data0_burst=1.5
# Note: for IEEE 802.11b mode: cWmin=7 cWmax=15 burst=3.3
# Special queues; normally not user configurable
#tx_queue_after_beacon_aifs=2
#tx_queue_after_beacon_cwmin=15
#tx_queue_after_beacon_cwmax=1023
#tx_queue_after_beacon_burst=0
#tx_queue_beacon_aifs=2
#tx_queue_beacon_cwmin=3
#tx_queue_beacon_cwmax=7
#tx_queue_beacon_burst=1.5
# 802.1D Tag (= UP) to AC mappings
# WMM specifies following mapping of data frames to different ACs. This mapping
# can be configured using Linux QoS/tc and sch_pktpri.o module.
# 802.1D Tag 802.1D Designation Access Category WMM Designation
# 1 BK AC_BK Background
# 2 - AC_BK Background
# 0 BE AC_BE Best Effort
# 3 EE AC_BE Best Effort
# 4 CL AC_VI Video
# 5 VI AC_VI Video
# 6 VO AC_VO Voice
# 7 NC AC_VO Voice
# Data frames with no priority information: AC_BE
# Management frames: AC_VO
# PS-Poll frames: AC_BE
# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e):
# for 802.11a or 802.11g networks
# These parameters are sent to WMM clients when they associate.
# The parameters will be used by WMM clients for frames transmitted to the
# access point.
# note - txop_limit is in units of 32microseconds
# note - acm is admission control mandatory flag. 0 = admission control not
# required, 1 = mandatory
# note - here cwMin and cmMax are in exponent form. the actual cw value used
# will be (2^n)-1 where n is the value given here
wmm_enabled=1
# WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD]
# Enable this flag if U-APSD supported outside hostapd (eg., Firmware/driver)
#uapsd_advertisement_enabled=1
# Low priority / AC_BK = background
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
# Note: for IEEE 802.11b mode: cWmin=5 cWmax=10
# Normal priority / AC_BE = best effort
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
# Note: for IEEE 802.11b mode: cWmin=5 cWmax=7
# High priority / AC_VI = video
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
# Note: for IEEE 802.11b mode: cWmin=4 cWmax=5 txop_limit=188
# Highest priority / AC_VO = voice
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
# Note: for IEEE 802.11b mode: cWmin=3 cWmax=4 burst=102
# Static WEP key configuration
# The key number to use when transmitting.
# It must be between 0 and 3, and the corresponding key must be set.
# default: not set
#wep_default_key=0
# The WEP keys to use.
# A key may be a quoted string or unquoted hexadecimal digits.
# The key length should be 5, 13, or 16 characters, or 10, 26, or 32
# digits, depending on whether 40-bit (64-bit), 104-bit (128-bit), or
# 128-bit (152-bit) WEP is used.
# Only the default key must be supplied; the others are optional.
# default: not set
#wep_key0=123456789a
#wep_key1="vwxyz"
#wep_key2=0102030405060708090a0b0c0d
#wep_key3=".2.4.6.8.0.23"
# Station inactivity limit
# If a station does not send anything in ap_max_inactivity seconds, an
# empty data frame is sent to it in order to verify whether it is
# still in range. If this frame is not ACKed, the station will be
# disassociated and then deauthenticated. This feature is used to
# clear station table of old entries when the STAs move out of the
# range.
# The station can associate again with the AP if it is still in range;
# this inactivity poll is just used as a nicer way of verifying
# inactivity; i.e., client will not report broken connection because
# disassociation frame is not sent immediately without first polling
# the STA with a data frame.
# default: 300 (i.e., 5 minutes)
#ap_max_inactivity=300
# Maximum allowed Listen Interval (how many Beacon periods STAs are allowed to
# remain asleep). Default: 65535 (no limit apart from field size)
#max_listen_interval=100
# WDS (4-address frame) mode with per-station virtual interfaces
# (only supported with driver=nl80211)
# This mode allows associated stations to use 4-address frames to allow layer 2
# bridging to be used.
#wds_sta=1
##### IEEE 802.11n related configuration ######################################
# ieee80211n: Whether IEEE 802.11n (HT) is enabled
# 0 = disabled (default)
# 1 = enabled
# Note: You will also need to enable WMM for full HT functionality.
ieee80211n=0
# ht_capab: HT capabilities (list of flags)
# LDPC coding capability: [LDPC] = supported
# Supported channel width set: [HT40-] = both 20 MHz and 40 MHz with secondary
# channel below the primary channel; [HT40+] = both 20 MHz and 40 MHz
# with secondary channel below the primary channel
# (20 MHz only if neither is set)
# Note: There are limits on which channels can be used with HT40- and
# HT40+. Following table shows the channels that may be available for
# HT40- and HT40+ use per IEEE 802.11n Annex J:
# freq HT40- HT40+
# 2.4 GHz 5-13 1-7 (1-9 in Europe/Japan)
# 5 GHz 40,48,56,64 36,44,52,60
# (depending on the location, not all of these channels may be available
# for use)
# Please note that 40 MHz channels may switch their primary and secondary
# channels if needed or creation of 40 MHz channel maybe rejected based
# on overlapping BSSes. These changes are done automatically when hostapd
# is setting up the 40 MHz channel.
# Spatial Multiplexing (SM) Power Save: [SMPS-STATIC] or [SMPS-DYNAMIC]
# (SMPS disabled if neither is set)
# HT-greenfield: [GF] (disabled if not set)
# Short GI for 20 MHz: [SHORT-GI-20] (disabled if not set)
# Short GI for 40 MHz: [SHORT-GI-40] (disabled if not set)
# Tx STBC: [TX-STBC] (disabled if not set)
# Rx STBC: [RX-STBC1] (one spatial stream), [RX-STBC12] (one or two spatial
# streams), or [RX-STBC123] (one, two, or three spatial streams); Rx STBC
# disabled if none of these set
# HT-delayed Block Ack: [DELAYED-BA] (disabled if not set)
# Maximum A-MSDU length: [MAX-AMSDU-7935] for 7935 octets (3839 octets if not
# set)
# DSSS/CCK Mode in 40 MHz: [DSSS_CCK-40] = allowed (not allowed if not set)
# PSMP support: [PSMP] (disabled if not set)
# L-SIG TXOP protection support: [LSIG-TXOP-PROT] (disabled if not set)
#ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40]
##### IEEE 802.1X-2004 related configuration ##################################
# Require IEEE 802.1X authorization
ieee8021x=0
# IEEE 802.1X/EAPOL version
# hostapd is implemented based on IEEE Std 802.1X-2004 which defines EAPOL
# version 2. However, there are many client implementations that do not handle
# the new version number correctly (they seem to drop the frames completely).
# In order to make hostapd interoperate with these clients, the version number
# can be set to the older version (1) with this configuration value.
#eapol_version=2
# Optional displayable message sent with EAP Request-Identity. The first \0
# in this string will be converted to ASCII-0 (nul). This can be used to
# separate network info (comma separated list of attribute=value pairs); see,
# e.g., RFC 4284.
#eap_message=hello
#eap_message=hello\0networkid=netw,nasid=foo,portid=0,NAIRealms=example.com
# WEP rekeying (disabled if key lengths are not set or are set to 0)
# Key lengths for default/broadcast and individual/unicast keys:
# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits)
# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits)
#wep_key_len_broadcast=5
#wep_key_len_unicast=5
# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once)
#wep_rekey_period=300
# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if
# only broadcast keys are used)
eapol_key_index_workaround=0
# EAP reauthentication period in seconds (default: 3600 seconds; 0 = disable
# reauthentication).
#eap_reauth_period=3600
# Use PAE group address (01:80:c2:00:00:03) instead of individual target
# address when sending EAPOL frames with driver=wired. This is the most common
# mechanism used in wired authentication, but it also requires that the port
# is only used by one station.
#use_pae_group_addr=1
##### Integrated EAP server ###################################################
# Optionally, hostapd can be configured to use an integrated EAP server
# to process EAP authentication locally without need for an external RADIUS
# server. This functionality can be used both as a local authentication server
# for IEEE 802.1X/EAPOL and as a RADIUS server for other devices.
# Use integrated EAP server instead of external RADIUS authentication
# server. This is also needed if hostapd is configured to act as a RADIUS
# authentication server.
eap_server=0
# Path for EAP server user database
#eap_user_file=/etc/hostapd/hostapd.eap_user
# CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
#ca_cert=/etc/hostapd/hostapd.ca.pem
# Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS
#server_cert=/etc/hostapd/hostapd.server.pem
# Private key matching with the server certificate for EAP-TLS/PEAP/TTLS
# This may point to the same file as server_cert if both certificate and key
# are included in a single file. PKCS#12 (PFX) file (.p12/.pfx) can also be
# used by commenting out server_cert and specifying the PFX file as the
# private_key.
#private_key=/etc/hostapd/hostapd.server.prv
# Passphrase for private key
#private_key_passwd=secret
# Enable CRL verification.
# Note: hostapd does not yet support CRL downloading based on CDP. Thus, a
# valid CRL signed by the CA is required to be included in the ca_cert file.
# This can be done by using PEM format for CA certificate and CRL and
# concatenating these into one file. Whenever CRL changes, hostapd needs to be
# restarted to take the new CRL into use.
# 0 = do not verify CRLs (default)
# 1 = check the CRL of the user certificate
# 2 = check all CRLs in the certificate path
#check_crl=1
# dh_file: File path to DH/DSA parameters file (in PEM format)
# This is an optional configuration file for setting parameters for an
# ephemeral DH key exchange. In most cases, the default RSA authentication does
# not use this configuration. However, it is possible setup RSA to use
# ephemeral DH key exchange. In addition, ciphers with DSA keys always use
# ephemeral DH keys. This can be used to achieve forward secrecy. If the file
# is in DSA parameters format, it will be automatically converted into DH
# params. This parameter is required if anonymous EAP-FAST is used.
# You can generate DH parameters file with OpenSSL, e.g.,
# "openssl dhparam -out /etc/hostapd/hostapd.dh.pem 1024"
#dh_file=/etc/hostapd/hostapd.dh.pem
# Configuration data for EAP-SIM database/authentication gateway interface.
# This is a text string in implementation specific format. The example
# implementation in eap_sim_db.c uses this as the UNIX domain socket name for
# the HLR/AuC gateway (e.g., hlr_auc_gw). In this case, the path uses "unix:"
# prefix.
#eap_sim_db=unix:/tmp/hlr_auc_gw.sock
# Encryption key for EAP-FAST PAC-Opaque values. This key must be a secret,
# random value. It is configured as a 16-octet value in hex format. It can be
# generated, e.g., with the following command:
# od -tx1 -v -N16 /dev/random | colrm 1 8 | tr -d ' '
#pac_opaque_encr_key=000102030405060708090a0b0c0d0e0f
# EAP-FAST authority identity (A-ID)
# A-ID indicates the identity of the authority that issues PACs. The A-ID
# should be unique across all issuing servers. In theory, this is a variable
# length field, but due to some existing implementations requiring A-ID to be
# 16 octets in length, it is strongly recommended to use that length for the
# field to provid interoperability with deployed peer implementations. This
# field is configured in hex format.
#eap_fast_a_id=101112131415161718191a1b1c1d1e1f
# EAP-FAST authority identifier information (A-ID-Info)
# This is a user-friendly name for the A-ID. For example, the enterprise name
# and server name in a human-readable format. This field is encoded as UTF-8.
#eap_fast_a_id_info=test server
# Enable/disable different EAP-FAST provisioning modes:
#0 = provisioning disabled
#1 = only anonymous provisioning allowed
#2 = only authenticated provisioning allowed
#3 = both provisioning modes allowed (default)
#eap_fast_prov=3
# EAP-FAST PAC-Key lifetime in seconds (hard limit)
#pac_key_lifetime=604800
# EAP-FAST PAC-Key refresh time in seconds (soft limit on remaining hard
# limit). The server will generate a new PAC-Key when this number of seconds
# (or fewer) of the lifetime remains.
#pac_key_refresh_time=86400
# EAP-SIM and EAP-AKA protected success/failure indication using AT_RESULT_IND
# (default: 0 = disabled).
#eap_sim_aka_result_ind=1
# Trusted Network Connect (TNC)
# If enabled, TNC validation will be required before the peer is allowed to
# connect. Note: This is only used with EAP-TTLS and EAP-FAST. If any other
# EAP method is enabled, the peer will be allowed to connect without TNC.
#tnc=1
##### IEEE 802.11f - Inter-Access Point Protocol (IAPP) #######################
# Interface to be used for IAPP broadcast packets
#iapp_interface=eth0
##### RADIUS client configuration #############################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting
# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=127.0.0.1
# Optional NAS-Identifier string for RADIUS messages. When used, this should be
# a unique to the NAS within the scope of the RADIUS server. For example, a
# fully qualified domain name can be used here.
# When using IEEE 802.11r, nas_identifier must be set and must be between 1 and
# 48 octets long.
#nas_identifier=ap.example.com
# RADIUS authentication server
#auth_server_addr=127.0.0.1
#auth_server_port=1812
#auth_server_shared_secret=secret
# RADIUS accounting server
#acct_server_addr=127.0.0.1
#acct_server_port=1813
#acct_server_shared_secret=secret
# Secondary RADIUS servers; to be used if primary one does not reply to
# RADIUS packets. These are optional and there can be more than one secondary
# server listed.
#auth_server_addr=127.0.0.2
#auth_server_port=1812
#auth_server_shared_secret=secret2
#acct_server_addr=127.0.0.2
#acct_server_port=1813
#acct_server_shared_secret=secret2
# Retry interval for trying to return to the primary RADIUS server (in
# seconds). RADIUS client code will automatically try to use the next server
# when the current server is not replying to requests. If this interval is set,
# primary server will be retried after configured amount of time even if the
# currently used secondary server is still working.
#radius_retry_primary_interval=600
# Interim accounting update interval
# If this is set (larger than 0) and acct_server is configured, hostapd will
# send interim accounting updates every N seconds. Note: if set, this overrides
# possible Acct-Interim-Interval attribute in Access-Accept message. Thus, this
# value should not be configured in hostapd.conf, if RADIUS server is used to
# control the interim interval.
# This value should not be less 600 (10 minutes) and must not be less than
# 60 (1 minute).
#radius_acct_interim_interval=600
# Dynamic VLAN mode; allow RADIUS authentication server to decide which VLAN
# is used for the stations. This information is parsed from following RADIUS
# attributes based on RFC 3580 and RFC 2868: Tunnel-Type (value 13 = VLAN),
# Tunnel-Medium-Type (value 6 = IEEE 802), Tunnel-Private-Group-ID (value
# VLANID as a string). vlan_file option below must be configured if dynamic
# VLANs are used. Optionally, the local MAC ACL list (accept_mac_file) can be
# used to set static client MAC address to VLAN ID mapping.
# 0 = disabled (default)
# 1 = option; use default interface if RADIUS server does not include VLAN ID
# 2 = required; reject authentication if RADIUS server does not include VLAN ID
#dynamic_vlan=0
# VLAN interface list for dynamic VLAN mode is read from a separate text file.
# This list is used to map VLAN ID from the RADIUS server to a network
# interface. Each station is bound to one interface in the same way as with
# multiple BSSIDs or SSIDs. Each line in this text file is defining a new
# interface and the line must include VLAN ID and interface name separated by
# white space (space or tab).
#vlan_file=/etc/hostapd/hostapd.vlan
# Interface where 802.1q tagged packets should appear when a RADIUS server is
# used to determine which VLAN a station is on. hostapd creates a bridge for
# each VLAN. Then hostapd adds a VLAN interface (associated with the interface
# indicated by 'vlan_tagged_interface') and the appropriate wireless interface
# to the bridge.
#vlan_tagged_interface=eth0
##### RADIUS authentication server configuration ##############################
# hostapd can be used as a RADIUS authentication server for other hosts. This
# requires that the integrated EAP server is also enabled and both
# authentication services are sharing the same configuration.
# File name of the RADIUS clients configuration for the RADIUS server. If this
# commented out, RADIUS server is disabled.
#radius_server_clients=/etc/hostapd/hostapd.radius_clients
# The UDP port number for the RADIUS authentication server
#radius_server_auth_port=1812
# Use IPv6 with RADIUS server (IPv4 will also be supported using IPv6 API)
#radius_server_ipv6=1
##### WPA/IEEE 802.11i configuration ##########################################
# Enable WPA. Setting this variable configures the AP to require WPA (either
# WPA-PSK or WPA-RADIUS/EAP based on other configuration). For WPA-PSK, either
# wpa_psk or wpa_passphrase must be set and wpa_key_mgmt must include WPA-PSK.
# For WPA-RADIUS/EAP, ieee8021x must be set (but without dynamic WEP keys),
# RADIUS authentication server must be configured, and WPA-EAP must be included
# in wpa_key_mgmt.
# This field is a bit field that can be used to enable WPA (IEEE 802.11i/D3.0)
# and/or WPA2 (full IEEE 802.11i/RSN):
# bit0 = WPA
# bit1 = IEEE 802.11i/RSN (WPA2) (dot11RSNAEnabled)
wpa=3
# WPA pre-shared keys for WPA-PSK. This can be either entered as a 256-bit
# secret in hex format (64 hex digits), wpa_psk, or as an ASCII passphrase
# (8..63 characters) that will be converted to PSK. This conversion uses SSID
# so the PSK changes when ASCII passphrase is used and the SSID is changed.
# wpa_psk (dot11RSNAConfigPSKValue)
# wpa_passphrase (dot11RSNAConfigPSKPassPhrase)
#wpa_psk=---
wpa_passphrase=---
# Optionally, WPA PSKs can be read from a separate text file (containing list
# of (PSK,MAC address) pairs. This allows more than one PSK to be configured.
# Use absolute path name to make sure that the files can be read on SIGHUP
# configuration reloads.
#wpa_psk_file=/etc/hostapd/hostapd.wpa_psk
# Set of accepted key management algorithms (WPA-PSK, WPA-EAP, or both). The
# entries are separated with a space. WPA-PSK-SHA256 and WPA-EAP-SHA256 can be
# added to enable SHA256-based stronger algorithms.
# (dot11RSNAConfigAuthenticationSuitesTable)
wpa_key_mgmt=WPA-PSK
# Set of accepted cipher suites (encryption algorithms) for pairwise keys
# (unicast packets). This is a space separated list of algorithms:
# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
# Group cipher suite (encryption algorithm for broadcast and multicast frames)
# is automatically selected based on this configuration. If only CCMP is
# allowed as the pairwise cipher, group cipher will also be CCMP. Otherwise,
# TKIP will be used as the group cipher.
# (dot11RSNAConfigPairwiseCiphersTable)
# Pairwise cipher for WPA (v1) (default: TKIP)
wpa_pairwise=CCMP
# Pairwise cipher for RSN/WPA2 (default: use wpa_pairwise value)
rsn_pairwise=CCMP
# Time interval for rekeying GTK (broadcast/multicast encryption keys) in
# seconds. (dot11RSNAConfigGroupRekeyTime)
wpa_group_rekey=600
# Rekey GTK when any STA that possesses the current GTK is leaving the BSS.
# (dot11RSNAConfigGroupRekeyStrict)
#wpa_strict_rekey=1
# Time interval for rekeying GMK (master key used internally to generate GTKs
# (in seconds).
wpa_gmk_rekey=86400
# Maximum lifetime for PTK in seconds. This can be used to enforce rekeying of
# PTK to mitigate some attacks against TKIP deficiencies.
#wpa_ptk_rekey=600
# Enable IEEE 802.11i/RSN/WPA2 pre-authentication. This is used to speed up
# roaming be pre-authenticating IEEE 802.1X/EAP part of the full RSN
# authentication and key handshake before actually associating with a new AP.
# (dot11RSNAPreauthenticationEnabled)
rsn_preauth=1
# Space separated list of interfaces from which pre-authentication frames are
# accepted (e.g., 'eth0' or 'eth0 wlan0wds0'. This list should include all
# interface that are used for connections to other APs. This could include
# wired interfaces and WDS links. The normal wireless data interface towards
# associated stations (e.g., wlan0) should not be added, since
# pre-authentication is only used with APs other than the currently associated
# one.
#rsn_preauth_interfaces=eth0
# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e) is
# allowed. This is only used with RSN/WPA2.
# 0 = disabled (default)
# 1 = enabled
#peerkey=1
# ieee80211w: Whether management frame protection (MFP) is enabled
# 0 = disabled (default)
# 1 = optional
# 2 = required
#ieee80211w=0
# Association SA Query maximum timeout (in TU = 1.024 ms; for MFP)
# (maximum time to wait for a SA Query response)
# dot11AssociationSAQueryMaximumTimeout, 1...4294967295
#assoc_sa_query_max_timeout=1000
# Association SA Query retry timeout (in TU = 1.024 ms; for MFP)
# (time between two subsequent SA Query requests)
# dot11AssociationSAQueryRetryTimeout, 1...4294967295
#assoc_sa_query_retry_timeout=201
# okc: Opportunistic Key Caching (aka Proactive Key Caching)
# Allow PMK cache to be shared opportunistically among configured interfaces
# and BSSes (i.e., all configurations within a single hostapd process).
# 0 = disabled (default)
# 1 = enabled
#okc=1
##### IEEE 802.11r configuration ##############################################
# Mobility Domain identifier (dot11FTMobilityDomainID, MDID)
# MDID is used to indicate a group of APs (within an ESS, i.e., sharing the
# same SSID) between which a STA can use Fast BSS Transition.
# 2-octet identifier as a hex string.
#mobility_domain=a1b2
# PMK-R0 Key Holder identifier (dot11FTR0KeyHolderID)
# 1 to 48 octet identifier.
# This is configured with nas_identifier (see RADIUS client section above).
# Default lifetime of the PMK-RO in minutes; range 1..65535
# (dot11FTR0KeyLifetime)
#r0_key_lifetime=10000
# PMK-R1 Key Holder identifier (dot11FTR1KeyHolderID)
# 6-octet identifier as a hex string.
#r1_key_holder=000102030405
# Reassociation deadline in time units (TUs / 1.024 ms; range 1000..65535)
# (dot11FTReassociationDeadline)
#reassociation_deadline=1000
# List of R0KHs in the same Mobility Domain
# format: <MAC address> <NAS Identifier> <128-bit key as hex string>
# This list is used to map R0KH-ID (NAS Identifier) to a destination MAC
# address when requesting PMK-R1 key from the R0KH that the STA used during the
# Initial Mobility Domain Association.
#r0kh=02:01:02:03:04:05 r0kh-1.example.com 000102030405060708090a0b0c0d0e0f
#r0kh=02:01:02:03:04:06 r0kh-2.example.com 00112233445566778899aabbccddeeff
# And so on.. One line per R0KH.
# List of R1KHs in the same Mobility Domain
# format: <MAC address> <R1KH-ID> <128-bit key as hex string>
# This list is used to map R1KH-ID to a destination MAC address when sending
# PMK-R1 key from the R0KH. This is also the list of authorized R1KHs in the MD
# that can request PMK-R1 keys.
#r1kh=02:01:02:03:04:05 02:11:22:33:44:55 000102030405060708090a0b0c0d0e0f
#r1kh=02:01:02:03:04:06 02:11:22:33:44:66 00112233445566778899aabbccddeeff
# And so on.. One line per R1KH.
# Whether PMK-R1 push is enabled at R0KH
# 0 = do not push PMK-R1 to all configured R1KHs (default)
# 1 = push PMK-R1 to all configured R1KHs whenever a new PMK-R0 is derived
#pmk_r1_push=1
##### Neighbor table ##########################################################
# Maximum number of entries kept in AP table (either for neigbor table or for
# detecting Overlapping Legacy BSS Condition). The oldest entry will be
# removed when adding a new entry that would make the list grow over this
# limit. Note! WFA certification for IEEE 802.11g requires that OLBC is
# enabled, so this field should not be set to 0 when using IEEE 802.11g.
# default: 255
#ap_table_max_size=255
# Number of seconds of no frames received after which entries may be deleted
# from the AP table. Since passive scanning is not usually performed frequently
# this should not be set to very small value. In addition, there is no
# guarantee that every scan cycle will receive beacon frames from the
# neighboring APs.
# default: 60
#ap_table_expiration_time=3600
##### Wi-Fi Protected Setup (WPS) #############################################
# WPS state
# 0 = WPS disabled (default)
# 1 = WPS enabled, not configured
# 2 = WPS enabled, configured
#wps_state=0
# AP can be configured into a locked state where new WPS Registrar are not
# accepted, but previously authorized Registrars (including the internal one)
# can continue to add new Enrollees.
#ap_setup_locked=1
# Universally Unique IDentifier (UUID; see RFC 4122) of the device
# This value is used as the UUID for the internal WPS Registrar. If the AP
# is also using UPnP, this value should be set to the device's UPnP UUID.
# If not configured, UUID will be generated based on the local MAC address.
#uuid=12345678-9abc-def0-1234-56789abcdef0
# Note: If wpa_psk_file is set, WPS is used to generate random, per-device PSKs
# that will be appended to the wpa_psk_file. If wpa_psk_file is not set, the
# default PSK (wpa_psk/wpa_passphrase) will be delivered to Enrollees. Use of
# per-device PSKs is recommended as the more secure option (i.e., make sure to
# set wpa_psk_file when using WPS with WPA-PSK).
# When an Enrollee requests access to the network with PIN method, the Enrollee
# PIN will need to be entered for the Registrar. PIN request notifications are
# sent to hostapd ctrl_iface monitor. In addition, they can be written to a
# text file that could be used, e.g., to populate the AP administration UI with
# pending PIN requests. If the following variable is set, the PIN requests will
# be written to the configured file.
#wps_pin_requests=/var/run/hostapd_wps_pin_requests
# Device Name
# User-friendly description of device; up to 32 octets encoded in UTF-8
#device_name=Wireless AP
# Manufacturer
# The manufacturer of the device (up to 64 ASCII characters)
#manufacturer=Company
# Model Name
# Model of the device (up to 32 ASCII characters)
#model_name=WAP
# Model Number
# Additional device description (up to 32 ASCII characters)
#model_number=123
# Serial Number
# Serial number of the device (up to 32 characters)
#serial_number=12345
# Primary Device Type
# Used format: <categ>-<OUI>-<subcateg>
# categ = Category as an integer value
# OUI = OUI and type octet as a 4-octet hex-encoded value; 0050F204 for
# default WPS OUI
# subcateg = OUI-specific Sub Category as an integer value
# Examples:
# 1-0050F204-1 (Computer / PC)
# 1-0050F204-2 (Computer / Server)
# 5-0050F204-1 (Storage / NAS)
# 6-0050F204-1 (Network Infrastructure / AP)
#device_type=6-0050F204-1
# OS Version
# 4-octet operating system version number (hex string)
#os_version=01020300
# Config Methods
# List of the supported configuration methods
# Available methods: usba ethernet label display ext_nfc_token int_nfc_token
# nfc_interface push_button keypad
#config_methods=label display push_button keypad
# Static access point PIN for initial configuration and adding Registrars
# If not set, hostapd will not allow external WPS Registrars to control the
# access point. The AP PIN can also be set at runtime with hostapd_cli
# wps_ap_pin command. Use of temporary (enabled by user action) and random
# AP PIN is much more secure than configuring a static AP PIN here. As such,
# use of the ap_pin parameter is not recommended if the AP device has means for
# displaying a random PIN.
#ap_pin=12345670
# Skip building of automatic WPS credential
# This can be used to allow the automatically generated Credential attribute to
# be replaced with pre-configured Credential(s).
#skip_cred_build=1
# Additional Credential attribute(s)
# This option can be used to add pre-configured Credential attributes into M8
# message when acting as a Registrar. If skip_cred_build=1, this data will also
# be able to override the Credential attribute that would have otherwise been
# automatically generated based on network configuration. This configuration
# option points to an external file that much contain the WPS Credential
# attribute(s) as binary data.
#extra_cred=hostapd.cred
# Credential processing
# 0 = process received credentials internally (default)
# 1 = do not process received credentials; just pass them over ctrl_iface to
# external program(s)
# 2 = process received credentials internally and pass them over ctrl_iface
# to external program(s)
# Note: With wps_cred_processing=1, skip_cred_build should be set to 1 and
# extra_cred be used to provide the Credential data for Enrollees.
# wps_cred_processing=1 will disabled automatic updates of hostapd.conf file
# both for Credential processing and for marking AP Setup Locked based on
# validation failures of AP PIN. An external program is responsible on updating
# the configuration appropriately in this case.
#wps_cred_processing=0
# AP Settings Attributes for M7
# By default, hostapd generates the AP Settings Attributes for M7 based on the
# current configuration. It is possible to override this by providing a file
# with pre-configured attributes. This is similar to extra_cred file format,
# but the AP Settings attributes are not encapsulated in a Credential
# attribute.
#ap_settings=hostapd.ap_settings
# WPS UPnP interface
# If set, support for external Registrars is enabled.
#upnp_iface=br0
# Friendly Name (required for UPnP)
# Short description for end use. Should be less than 64 characters.
#friendly_name=WPS Access Point
# Manufacturer URL (optional for UPnP)
#manufacturer_url=http://www.example.com/
# Model Description (recommended for UPnP)
# Long description for end user. Should be less than 128 characters.
#model_description=Wireless Access Point
# Model URL (optional for UPnP)
#model_url=http://www.example.com/model/
# Universal Product Code (optional for UPnP)
# 12-digit, all-numeric code that identifies the consumer package.
#upc=123456789012
##### Multiple BSSID support ##################################################
# Above configuration is using the default interface (wlan#, or multi-SSID VLAN
# interfaces). Other BSSIDs can be added by using separator 'bss' with
# default interface name to be allocated for the data packets of the new BSS.
# hostapd will generate BSSID mask based on the BSSIDs that are
# configured. hostapd will verify that dev_addr & MASK == dev_addr. If this is
# not the case, the MAC address of the radio must be changed before starting
# hostapd (ifconfig wlan0 hw ether <MAC addr>). If a BSSID is configured for
# every secondary BSS, this limitation is not applied at hostapd and other
# masks may be used if the driver supports them (e.g., swap the locally
# administered bit)
# BSSIDs are assigned in order to each BSS, unless an explicit BSSID is
# specified using the 'bssid' parameter.
# If an explicit BSSID is specified, it must be chosen such that it:
# - results in a valid MASK that covers it and the dev_addr
# - is not the same as the MAC address of the radio
# - is not the same as any other explicitly specified BSSID
# Please note that hostapd uses some of the values configured for the first BSS
# as the defaults for the following BSSes. However, it is recommended that all
# BSSes include explicit configuration of all relevant configuration items.
#bss=wlan0_0
#ssid=test2
# most of the above items can be used here (apart from radio interface specific
# items, like channel)
#bss=wlan0_1
#bssid=00:13:10:95:fe:0b
I tried to access this network through the other device - same problem. What's the problem? Thanks in advance.

Retracting the question...no one seems to know.
LarryMcJ

ASK THE EXPERTS - Update on 802.11n with Fred Niehaus

Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to get an update on 802.11n with Cisco expert Fred Niehaus. Fred is a Technical Marketing Engineer for the Wireless Networking Business Unit at Cisco, where he is responsible for developing and marketing enterprise wireless solutions using Cisco Aironet and Airespace wireless LAN products. In addition to his participation in major deployments, Fred has served as technical editor for several Cisco Press books including the "Cisco 802.11 Wireless Networking Reference Guide" and "The Business Case for Enterprise-Class Wireless LANs." Prior to joining Cisco with the acquisition of Aironet, Fred was a support engineer for Telxon Corporation, supporting some of the very first wireless implementations for major corporate customers. Fred has been in the data communications and networking industry for more than 20 years and holds a Radio Amateur (Ham) License "N8CPI."
Remember to use the rating system to let Fred know if you have received an adequate response.
Fred might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Other Mobility Subjects discussion forum shortly after the event. This event lasts through March 25, 2011. Visit this forum often to view responses to your questions and the questions of other community members.

So there are two parts of this question, the latter part I cannot address as it is a future question. Cisco does not comment on products that have not been released or on the strategy of next generation products.
That said, Cisco was first to market with an 802.11n Access Point and well (we didn't all go on vacation after we did that)
So let's talk a little about spatial streams in general and how it relates to what customers are doing today.
The Cisco 1040, 1140, 1250, 1260 and 3500 Series Access Points are all two spatial streams (2SS).
As of the time of this writing, a critical mass of 3SS and 4SS compatible clients have yet to be deployed, and the vast majority of WiFi clients that will be deployed over the next 18 months will be 1SS and 2SS clients.
The higher SS clients are likely only show up in some higher end notebooks -- Why? well it is a given that smartphones and tablets are likely to continue to be 1SS and in some rare cases 2SS.
This is because additional radios used in this technology consume battery life, add to the physical size of the device and increase the cost. Also many devices leverage the same single antenna for cellular as well as WiFi. Therefore, it is my opinion that 3SS Access Points provide little if any performance benefit for smartphones or tablets in the enterprise today, and any real throughput gain is likely to occur with high end notebooks in close proximity to the Access Point and those are rolling out very slowly and we are monitoring this.
Now we get to my favorite part of this.. I get to ask myself a question and then answer it..
So Fred are you saying that there is no value in 3SS and 4SS?
Of course not, 3SS performs similar to 2SS beyond a short distance, and with any multi-SS product RF interference must be addressed to capture the performance benefits of higher SS Access Points. Actual throughput in any WiFi environment is highly dependent on the presence of interferers and obstacles.
Without the ability to mitigate the impact of interference, 3SS solutions will "downshift" to 2SS of 1SS and lose all the performance benefits anyway IMHO.
I don't want to sound like a commercial, but you really do need Cisco cleanair technology in the AP and Cisco innovations deliver more and will go beyond the simple 3SS aspects of the 802.11n standard.
IMHO it's more about CleanAir, good RF system design, and what we put into the AP with regard to performance "in the environment" and not what is on some spec sheet today.
For more on Cisco CleanAir see the following URL http://www.cisco.com/en/US/netsol/ns1070/index.html
Fred

What do these settings mean on the 5th gen AE?

Just got my new Airport Extreme (MD031LL/A running Version 7.5.2) setup last night and being an IT guy, I'm always eager to dig into the Advanced menu options to see what tweaks and customizations my toys are capable of. There are a few questions that I have:
1. On the advanced controls, what should I set my Multicast Rate to (Low, Medium, High)? I have searched online but haven't found any good consistent answers about what this does or what the 3 settings actually change.
2. Is it necessary to check the box for "5GHz Network Name" to get the most from the 5GHz network? Some sites/forums say that allowing your 5GHz 802.11N devices to be connected to a separate network will result in faster data transfer rates on the LAN for those devices. I don't really see why that would be the case since, if the device is capable, it will connect at that level, and if not, it won't.
3. How do you configure the Syslog Destination Address? When I click on that field to enter a location I just get the "dong" error.
4. What is the WPA Group Key Timeout?

abrauda wrote:
1. On the advanced controls, what should I set my Multicast Rate to (Low, Medium, High)?
On former versions of the AP-Extreme there where real values instead of low - medium - high.
It's important for streaming media; e.g. music.
Apple: ""Multicast rate: Choose a multicast rate from the pop-up menu. If you set the
multicast rate high, only clients on the network that are within range and can achieve the speed you set will receive transmissions."" (Manual, Chapter 3, Page 23)
abrauda wrote:
2. Is it necessary to check the box for "5GHz Network Name" to get the most from the 5GHz network? Some sites/forums say that allowing your 5GHz 802.11N devices to be connected to a separate network will result in faster data transfer rates on the LAN for those devices. I don't really see why that would be the case since, if the device is capable, it will connect at that level, and if not, it won't.
It's not necessary but recommended.
If not set, the connected devices are able to switch the radio band if e.g. the signal fade, and with that use the attached BSSID of that radio band. That could lead to trouble (drop outs) e.g. if you stream music to a AP-Express.
Setting a name for the 5GHz allows you to force the 5GHz capable devices to use that connection only.
For instance, with a 2011 MBPro on the 2.4GHz 802.11n you will have a max connection speed of 150MBit/s and on 5GHz 802.11n 450MBit/s due to MiMo ( http://en.wikipedia.org/wiki/MIMO ) with a 150MBit/s for each spatial stream.
abrauda wrote:
3. How do you configure the Syslog Destination Address? When I click on that field to enter a location I just get the "dong" error.
Check "Allow SNMP" and enter the IP address of the computer that will receive the logs in the Syslog Destination Address field.
abrauda wrote:
4. What is the WPA Group Key Timeout?
it sets the frequency of encryption key rotation between the stations and the access point (Extreme). See --> http://en.wikipedia.org/wiki/CCMP
Lupunus
Message was edited by: lupunus

AP Capacities

I am about start a project to upgrade my wireless access points. We have auite a mix of 1131, 1142, 3502 and 3602 APs. I'd like to be able to compare the capacities of these devices in terms of throughput and particularly, number of users. I am having a difficult time finding this information. 've looked at the data sheets with no real success. Can anyone point me to it?
Thanks,
Wes

I understand... but this is wireless and you have to do your own testing to determine how may devices you can have on a given access point. There is no hard document for this at all!!!!!! You have to look at your oversubscription calculations like you would do on a switch to determine what works for you. You also are comparing old AP's to the new generation 2 access points... you need to compare apples to apples. Performance is different, but 25 is still the number no matter what. If your trying to fund a project with no idea experience in wireless, well that would be hard. In schools, there are putting one ap per classroom that can have 25-30 max students. I have clients that double up AP's if they have more than 20 seats in a room. So again... your best bet is to use the 25 clients per AP unless you are doing video and then you can lower your estimate to around 5.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Is anyone using a 1252 ap in bridge mode with channel bonding?

Is anyone using a 1252 ap in bridge mode, with channel bonding?
I had a question a while ago from a customer with regards to bridging with a 1252 ap to increase throughput for a wireless link he was using, from the throughput improvements in 802.11n. At the time I spoke to Cisco Pre-Sales, and they indicated that the bridge function in the 1252 exists for 'testing' purposes. I advised our customer that although it should be possible to implement, we may run into difficulties with TAC support ect. in the event of problems with the link.
Can anyone comment if this is a Cisco validated/approved design now?
Also, has anyone done this and tested the throughput achievable?
Has anyone bridged both 2.4Ghz and 5Ghz radios on a 1252?
The reason I ask is I've seen a note about a Cisco 5Ghz 802.11n bridge being launched.
Thanks in advance.
Alex.

Hi All,
Thanks for all the feedback; I have finally done some throughput testing with the 1252's. Please note, this is very rough, just to give an idea on throughput that's achievable, and what you can enable. Did this a few weeks back, and have now wiped the cnf, so dont have the show runs any more....
The two devices were set up a few feet apart, with the standard 2dBi and 3dBi antenna.
All tests done on the 5GHz radio with Autonomous AP IOS.
I did data transfers via a laptop either end of the link; transferring data using the Test TCP utility (wasn't going for scientific tests, just getting some idea of throughput).
802.11a @ 54mbs (20Mhz chan) WGB - root to non root = 2.43 - 2.5MB/Sec = 19.44 - 20 Mbps
802.11a @ 54mbs (20Mhz chan) WGB non root to root = 2.42 - 2.44MB/Sec = 19.44 - 20 Mbps
802.11n @ 'n' rates( 20Mhz chan) WGB root to non root = 6.18 - 6.33MB/Sec = 49.44 - 50.64 Mbps
802.11n @ 'n' rates ( 20Mhz chan) WGB non root to root = 4.77 - 5.00MB/Sec = 38.16 - 40 Mbps
802.11n @ 'n' rates ( 40Mhz chan) WGB root to non root = 8.59 - 8.58MB/Sec = 68.64 - 68.64 Mbps
802.11n @ 'n' rates ( 40Mhz chan) WGB non root to root = 6.35 - 7.20MB/Sec = 50.8 - 57.6 Mbps
802.11n @ 'n' rates ( 40Mhz chan) Bridge root to non root = 9.73 - 10MB/Sec = 77.84 - 80 Mbps
802.11n @ 'n' rates ( 40Mhz chan) Bridge non root to root = 8.40 - 8.57MB/Sec = 67.2 - 68.56 Mbps
So basically, as per the above posts, you can implement bridging on the 1252's and utilise the 802.11n rates and features, SGI, Spatial Streams and Channel Bonding etc, to achieve higher throughput.
Also, as per the above posts, this is still not supported by Cisco, so, in my case, I'd be highlighting that to customers straight off, but don't see it as too much of an impediment to deploy, as long as the customer weighs up the risks.
On a side note, I attended a Cisco session recently, and was told that the 802.11n Bridge, (the 1430?) was on hold indefinitely. My feeling is that this makes it more pressing that Cisco introduces support for bridging on the 1252.
Get in the ear of your local Wireless SE's, the more they hear it, the more they'll moan to the Wireless BU in San Jose! ;-)
Bridging with 802.11n has some interesting possibilities, I worked with Alvarion 5GHz bridges 6 or 7 years ago, that could do 'near LOS' - Worked well in cities, using reflection of the RF from buildings. I had never heard of 802.11n back then, but I'm guessing Alvarion was using MIMO to achieve good non-LOS connectivity in the 5GHz band.
Cheers,
Alex.

Aironet 1261 AP Problem with speed.

Hi guys,
I appreciate I am not Cisco trained and probably should have never purchased such a piece of kit, but my SMB run from home needed stability so I thought I would try to enter the world of Cisco.
I have spent the week setting up the Aironet AP 1261, Standalone, Power through traditional adapter, 2.4ghz only. 1261 being single band.
I have researched each setting and option as much as possible but I am still only getting 65mbps max, I believe I should be able to achieve 144mbps with this hardware. Is that correct?
I have used a combination of the web interface and IOS via Telnet. (being a server administrator using SSH, Telnet was ok for me to pick up quickly).
I understand I need WAPv2, with AES CCM Encryption on an Open Security network in order to achieve the speed I am after. These are all applied as far as I can tell.
WMM is the problem for me. (Also a requirement I understand). The thing is I have found WMM in two locations.
1. Under the Network interface setup, which seems to related to the World Mode Management. (off, legacy and dot11d).
2. WMM is also Wifi MultiMedia. Which is on.
I can only choose Legacy for the WMM in place 1 I mentioned, as the Country Codes are not populated which means I am unable to select dot11d.
Any help appreciated getting me to 144mbps.
If you also spot anything else dodgy with my amateur attempt of the config I love to know
Thank you in advance for tolerating someone trying to swim out of their depth.
Attached is my config.
Have a great week.
David J Cooper.

The HTC one is an 802.11ac device with a single spatial stream. In order to get faster than 72Mbps you need to use wider channels which are only available in 5Ghz.
If you had a 1262, you could set the dot11radio 1 to 40Mhz channel and that would enable 144. Moving to 802.11ac you can go to 80Mhz channels for even faster rates.
Since you have a 2.4Ghz only AP, you will be limited to 72 with this client.
Sent from Cisco Technical Support Android App

Ask the Expert: Cisco's 802.11ac Solutions - Deployment, Design, and Interop

Ask your Questions on Cisco’s 802.11ac Solutions - Deployment, Design, and Interop with Cisco Experts: Richard Hamby and Shankar Ramanathan.
Monday, March 30th, 2015 to Friday, April 10th, 2015
Richard Hamby is a senior technical support engineer and Team Lead of the Cisco Technical Assistance Center in Richardson, Texas. He is an expert in Indoor and Outdoor wireless for the full line of Cisco Unified and Converged Access Wireless products, as well as TAC Engineering Engagement Engineer liaison to project engineering teams for new Cisco wireless products. Prior to his current role, Richard was a customer support engineer with the AAA Security TAC team supporting Cisco identity management solutions and been with Cisco since 2009.
Shankar Ramanathan is a Customer Support Engineer at the Cisco Technical Center. He is a Technical Content Engineer and Subject Matter Expert for Cisco Enterprise Unified and Converged Access wireless mobility solution including Wireless LAN Controller 2500/5500/WISM2/7500/8500, Converged access 5760/3650/3850 switches, Access Points Lightweight and Autonomous, VoWLAN (792x/9971) , Cisco Prime Infrastructure SNMP management, Cisco Mobility Services Engine(MSE/ CMX). Prior to joining Cisco in November 2011, he worked as a wireless network engineer at Elan Technologies, responsible for RF wireless network planning, simulation, propagation path analysis, and optimization of Wi-Fi 802.11 mesh and WiMax (802.16 d/e) networks for various system integration and automation projects. Shankar holds a master of science degree in electrical engineering specializing in communications and signal process from the State University of New York, Buffalo. Shankar has a CCIE in Wireless(#40548) and CCNA certified (number 410004168640IMZF) and has over six years of industry experience.
Find other https://supportforums.cisco.com/expert-corner/events.
**Ratings Encourage Participation! **
Please be sure to rate the Answers to Questions

A common question we are asked is 'why is my device not achieving 11ac data rates?'
One of the most common answers relates to client compatibility/capability. To get the highest possible data rates of 11ac (assuming proper distance and RF health), the AP and the client device must both be capable supporting the requirements - 5GHZ, 80MHz Channel, short guard interval, 3 spatial streams. Each spatial stream has a max of 433.3Mb/s (at 80MHz, short GI).
The majority of 11ac-capable wireless cards on the market do not support 3 spatial streams. Most adapters in wireless-capable devices are 1SS or 2SS. For example, the Intel 7260 11ac adapter used in many devices is a 2SS adapter - therefore it's max possible data rate is 866.7. Another common adapter in use is the 11ac Broadcom 3SS that Apple uses in the newer Macbooks. These devices can achieve the 1.3GBs PHY data rate.
This guidance is the same for 11n adapters as well. To achieve max rate, your 11n AP and adapter must both support 40MHz channels, 3SS, short GI.
Note: The 11n and 11ac standards both define support for 4SS. 4SS-capable devices are rare, so 3SS is essentially our reality.
One of the most useful references for questions related to this topic is the AP Data Sheet for each AP. Here's the AP3700 for example:
http://www.cisco.com/c/en/us/products/collateral/wireless/3700-series-access-point/data_sheet_c78-729421.html
Table 1 lists the expected data rate per MCS Index value by #SS at each channel width and GI. Indexes 0-7 are the same for 11n and 11ac (11n limited to 40MHz channels of course). And MCS 8 & 9 are 11ac-only 256-QAM modulations.

Invalid MIC from Mobile Device

Hello guys,
i have two media tablets same hardware same driver. One is working proper and the other one is not able to associate with my ssid.
the debug out shows the follow:
*dot1xMsgTask: Feb 06 14:51:25.007: a8:54:b2:00:8b:34 Starting key exchange to mobile a8:54:b2:00:8b:34, data packets will be dropped*dot1xMsgTask: Feb 06 14:51:25.007: a8:54:b2:00:8b:34 Sending EAPOL-Key Message to mobile a8:54:b2:00:8b:34 state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00*Dot1x_NW_MsgTask_4: Feb 06 14:51:25.027: a8:54:b2:00:8b:34 Received EAPOL-Key from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:25.027: a8:54:b2:00:8b:34 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:25.027: a8:54:b2:00:8b:34 Received EAPOL-key in PTK_START state (message 2) from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:25.027: a8:54:b2:00:8b:34 Received EAPOL-key M2 with invalid MIC from mobile a8:54:b2:00:8b:34 version 2*osapiBsnTimer: Feb 06 14:51:26.173: a8:54:b2:00:8b:34 802.1x 'timeoutEvt' Timer expired for station a8:54:b2:00:8b:34 and for message = M2*dot1xMsgTask: Feb 06 14:51:26.173: a8:54:b2:00:8b:34 Retransmit 1 of EAPOL-Key M1 (length 121) for mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:26.257: a8:54:b2:00:8b:34 Received EAPOL-Key from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:26.257: a8:54:b2:00:8b:34 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:26.257: a8:54:b2:00:8b:34 Received EAPOL-key in PTK_START state (message 2) from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:26.257: a8:54:b2:00:8b:34 Received EAPOL-key M2 with invalid MIC from mobile a8:54:b2:00:8b:34 version 2*osapiBsnTimer: Feb 06 14:51:27.173: a8:54:b2:00:8b:34 802.1x 'timeoutEvt' Timer expired for station a8:54:b2:00:8b:34 and for message = M2*dot1xMsgTask: Feb 06 14:51:27.173: a8:54:b2:00:8b:34 Retransmit 2 of EAPOL-Key M1 (length 121) for mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:27.197: a8:54:b2:00:8b:34 Received EAPOL-Key from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:27.197: a8:54:b2:00:8b:34 Ignoring invalid EAPOL version (1) in EAPOL-key message from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:27.197: a8:54:b2:00:8b:34 Received EAPOL-key in PTK_START state (message 2) from mobile a8:54:b2:00:8b:34*Dot1x_NW_MsgTask_4: Feb 06 14:51:27.197: a8:54:b2:00:8b:34 Received EAPOL-key M2 with invalid MIC from mobile a8:54:b2:00:8b:34 version 2*osapiBsnTimer: Feb 06 14:51:28.173: a8:54:b2:00:8b:34 802.1x 'timeoutEvt' Timer expired for station a8:54:b2:00:8b:34 and for message = M2*dot1xMsgTask: Feb 06 14:51:28.173: a8:54:b2:00:8b:34 Retransmit failure for EAPOL-Key M1 to mobile a8:54:b2:00:8b:34, retransmit count 3, mscb deauth count 2*dot1xMsgTask: Feb 06 14:51:28.173: a8:54:b2:00:8b:34 Resetting MSCB PMK Cache Entry 0 for station a8:54:b2:00:8b:34*dot1xMsgTask: Feb 06 14:51:28.173: a8:54:b2:00:8b:34 Removing BSSID 34:db:fd:67:89:2a from PMKID cache of station a8:54:b2:00:8b:34*dot1xMsgTask: Feb 06 14:51:28.173: a8:54:b2:00:8b:34 Setting active key cache index 0 ---> 8*dot1xMsgTask: Feb 06 14:51:28.173: a8:54:b2:00:8b:34 Sent Deauthenticate to mobile on BSSID 34:db:fd:67:89:20 slot 1(caller 1x_ptsm.c:546)
config of the SSID:
(Cisco Controller) >show wlan 6WLAN Identifier.................................. 6Profile Name..................................... MedientechnikNetwork Name (SSID).............................. MedientechnikStatus........................................... EnabledMAC Filtering.................................... DisabledBroadcast SSID................................... DisabledAAA Policy Override.............................. DisabledNetwork Admission Control Client Profiling Status ....................... Disabled DHCP ......................................... Disabled HTTP ......................................... Disabled Radius-NAC State............................... Disabled SNMP-NAC State................................. Disabled Quarantine VLAN................................ 0Maximum number of Associated Clients............. 0Maximum number of Clients per AP Radio........... 200Number of Active Clients......................... 1Exclusionlist.................................... DisabledSession Timeout.................................. 86400 secondsUser Idle Timeout................................ 300 seconds--More-- or (q)uitUser Idle Threshold.............................. 0 BytesNAS-identifier................................... KPSS_WLC1CHD per WLAN..................................... EnabledWebauth DHCP exclusion........................... DisabledInterface........................................ medientechnikMulticast Interface.............................. Not ConfiguredWLAN IPv4 ACL.................................... unconfiguredWLAN IPv6 ACL.................................... unconfiguredmDNS Status...................................... DisabledmDNS Profile Name................................ default-mdns-profileDHCP Server...................................... DefaultDHCP Address Assignment Required................. DisabledStatic IP client tunneling....................... DisabledPMIPv6 Mobility Type............................. noneQuality of Service............................... SilverPer-SSID Rate Limits............................. Upstream DownstreamAverage Data Rate................................ 0 0Average Realtime Data Rate....................... 0 0Burst Data Rate.................................. 0 0Burst Realtime Data Rate......................... 0 0Per-Client Rate Limits........................... Upstream DownstreamAverage Data Rate................................ 0 0Average Realtime Data Rate....................... 0 0--More-- or (q)uitBurst Data Rate.................................. 0 0Burst Realtime Data Rate......................... 0 0Scan Defer Priority.............................. 4,5,6Scan Defer Time.................................. 100 millisecondsWMM.............................................. AllowedWMM UAPSD Compliant Client Support............... DisabledMedia Stream Multicast-direct.................... DisabledCCX - AironetIe Support.......................... DisabledCCX - Gratuitous ProbeResponse (GPR)............. DisabledCCX - Diagnostics Channel Capability............. DisabledDot11-Phone Mode (7920).......................... DisabledWired Protocol................................... NonePassive Client Feature........................... EnabledPeer-to-Peer Blocking Action..................... DisabledRadio Policy..................................... AllDTIM period for 802.11a radio.................... 1DTIM period for 802.11b radio.................... 1Radius Servers Authentication................................ Disabled Accounting.................................... Disabled Dynamic Interface............................. Disabled Dynamic Interface Priority.................... wlanLocal EAP Authentication......................... Disabled--More-- or (q)uitSecurity 802.11 Authentication:........................ Open System FT Support.................................... Disabled Static WEP Keys............................... Disabled 802.1X........................................ Disabled Wi-Fi Protected Access (WPA/WPA2)............. Enabled WPA (SSN IE)............................... Disabled WPA2 (RSN IE).............................. Enabled TKIP Cipher............................. Disabled AES Cipher.............................. Enabled Auth Key Management 802.1x.................................. Disabled PSK..................................... Enabled CCKM.................................... Disabled FT-1X(802.11r).......................... Disabled FT-PSK(802.11r)......................... Disabled PMF-1X(802.11w)......................... Disabled PMF-PSK(802.11w)........................ Disabled FT Reassociation Timeout................... 20 FT Over-The-DS mode........................ Enabled GTK Randomization.......................... Disabled SKC Cache Support.......................... Disabled--More-- or (q)uit CCKM TSF Tolerance......................... 1000 WAPI.......................................... Disabled Wi-Fi Direct policy configured................ Disabled EAP-Passthrough............................... Disabled CKIP ......................................... Disabled Web Based Authentication...................... Disabled Web-Passthrough............................... Disabled Conditional Web Redirect...................... Disabled Splash-Page Web Redirect...................... Disabled Auto Anchor................................... Disabled FlexConnect Local Switching................... Disabled flexconnect Central Dhcp Flag................. Disabled flexconnect nat-pat Flag...................... Disabled flexconnect Dns Override Flag................. Disabled FlexConnect Vlan based Central Switching ..... Disabled FlexConnect Local Authentication.............. Disabled FlexConnect Learn IP Address.................. Enabled Client MFP.................................... Disabled PMF........................................... Disabled PMF Association Comeback Time................. 1 PMF SA Query RetryTimeout..................... 200 Tkip MIC Countermeasure Hold-down Timer....... 60AVC Visibilty.................................... Disabled--More-- or (q)uitAVC Profile Name................................. NoneFlow Monitor Name................................ NoneCall Snooping.................................... DisabledRoamed Call Re-Anchor Policy..................... DisabledSIP CAC Fail Send-486-Busy Policy................ EnabledSIP CAC Fail Send Dis-Association Policy......... DisabledKTS based CAC Policy............................. DisabledAssisted Roaming Prediction Optimization......... Disabled802.11k Neighbor List............................ Disabled802.11k Neighbor List Dual Band.................. DisabledBand Select...................................... DisabledLoad Balancing................................... DisabledMulticast Buffer................................. Disabled Mobility Anchor List WLAN ID IP Address Status ------- --------------- ------802.11u........................................ DisabledMSAP Services.................................. Disabled
(Cisco Controller) >show sysinfoManufacturer's Name.............................. Cisco Systems Inc.Product Name..................................... Cisco ControllerProduct Version.................................. 7.4.110.0Bootloader Version............................... 1.0.1Field Recovery Image Version..................... 6.0.182.0Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27Build Type....................................... DATA + WPS
My understanding is that because of the invalid MIC the WLC interpret that the frames are corrupt ?
What could be the problem ?
Thanks for your help !!!!
Kind regards
Philip

802.11n and Apple iPad, Cisco Cius tablet, and Apple iPhone 4
Each Wi-Fi enabled phone and tablet that supports 802.11n has specific antenna and channel configurations. Specifications for each device are listed on the manufacturer's website. Because these devices are 802.11n-enabled, they can use 802.11n enhancements such as MIMO and frame aggregation to help improve their upstream and downstream performance. The specifications for the Apple iPad, Cisco Cius, and Apple iPhone 4 follow:
• The Apple iPad is a one-spatial stream (single antenna) 802.11n-enabled device that operates in 2.4- and 5-GHz spectrums using 20-MHz channels.
• The Cisco Cius tablet is a one-spatial stream (single antenna) 802.11n-enabled device that operates in the 2.4-GHz spectrum using 20-MHz channels and the 5-GHz spectrum using 20- or 40-MHz channels.
• The Apple iPhone 4 is a one-spatial stream 802.11n-enabled device that operates in only the 2.4-GHz spectrum using 20-MHz channels.
How to Optimize 802.11n WLANs to Support Wi-Fi Enabled Phones and Tablets
The following steps are recommended to help optimize a Cisco Unified Wireless Network 802.11n deployment to more effectively support the Apple iPad, Apple iPhone 4, Cisco Cius tablet, and other Wi-Fi phones, tablets, or clients with similar wireless profiles.

1552 in P-MP acting as 802.11a Wireless Bridge with single antenna SISO

Can you configure three Cisco 1552EUs to act as a RAP and two MAPs in a bridge only Point to Multipoint configuration.
I'd like to disable two of the 5Ghz antenna ports and use just a single TX/RX port and a single directional antenna for each AP.
Does this simply reduce the system gain because you lose the MRC MIMO advantage / gain of either 1.7 or 4.7db (depending on qty of spatial streams).
Also, are the 1552EU's backward compatible with the Cisco 1310's in the configuration mentioned above.
Thanks for any comments.

The transfer speeds sound about right. The "54Mbps" is a signaling rate, not a throughput.
To make 802.11 wireless "reliable" (comparable to a wired network) the data is, in effect, sent twice and staggered such that a glitch usually doesn't get both.
In terms of throughput of your data, a strong signal with good signal quality, using IP, unencrypted should run ~22-26Mbps (some variability for noise/interference, mixed frame sizes, TCP ACK times, application responses, etc).
So, at ~24 Mbps (megabits per second) you're looking at ~4 megabytes per second versus 100Mbps/12.5mBps as a probable max rate.
Given that, a transfer that takes approximately one minute on a wired network under typical conditions ... having it take four-to-five minutes on a typical wireless system is about right.
For power settings, you can adjust the power by monitoring the RSSI values on the receiving system. If I can find the docs on Cisco's main site I'll post 'em up later (gotta run ...), but if the mechanical install is good, then it'll just be a little keyboard work.
Good Luck
Scott

Typical propagation distance of outdoor(1552E series) access point

Hello All,
I need to propose an design for outdoor WAP deployment for an huge resort. As it is a complete open space area without any obstruction, I believe the signal can be propagated easily in over 35 meters radius across the access point. However I don't get any documentation to know exact propagation distance.
Could someone please share their experiences as to what is the ideal distance of signal coverage that could be covered by a typical Cisco outdoor access point? I do not want to go for over quoting as that might result from the client opting for other vendor's product. I would thus want to go with most appropriate plan.
Also apart from 11ac capability and multiple spatial streams, does 1570 AP have any other major improvement as well our its predecessor 1552E series AP.
Please share your expereinces.
Best Regards,
Muhammed Adnan

Factors Affecting Wireless Networking Performance
There are many factors that affect your Wireless Networking Performance that are dependent on various areas within the network itself from the technology of the devices used, the local environment the signals will travel through, the fundamental physics behind wireless transmission and more. Some of these cannot be avoided and measures must be taken to try to minimise the negative affect that these factors will have on the network performance but others can be resolved completely either though equipment upgrading or good network planning.
There are some well known factors that affect Wireless Networking performance that most people will identify easily but that does not lessen their importance when considering network planning, these are:
Obvious Factors Affecting Wireless Networking Performance
    Physical Obstructions
    Network Range & Distance between Devices
    Wireless Network Interference
    Signal Sharing
Quite Well Known Factors Affecting Wireless Networking Performance
    Network Usage & Load
    Poorly Deployed Antennas
    Local Environment Characteristics
    Spectrum Channel Limitations
    Signal Reflection
    Wireless Signal Restriction
Lesser Known Factors Affecting Wireless Networking Performance
    Transmitter Power Limitations
    Backwards Compatibility with Older Standards
    Polarisation of Signal
    Speed Loss Due to Wireless Overheads
    Lowering Performance to Stay Connected

Cisco AP 3700 PoE

Assuming we have a 802.3at (30W) capable Switch but we don’t need 802.11ac on the Cisco 3700 AP…can we disable the 802.11ac functionality ?
I also think that without disabling the 802.11ac functionality on the 3700 AP the AP/Switch will negotiate automatically on 802.3at (~20W) ? maybe i could set a max poe for 15.4W on the switch (Cisco 3650) so the AP can’t get more power... ?
Thanks for any informations!
Manuel

No need to disable .11ac functionality,
PoE power requirements
AP-3700 (.3at) mode
Full functionality requires 15 Watts for the AP to shift into 4x4:3 mode with both radios enabled
With the WSSI module installed it is an additional 3W so draw is 18 Watts with both radios enabled.
In the described modes above, you cannot get to 15 Watts at the end of a CAT-5 cable using 802.3af (15.4W)
When using CAT-5e or better, there is about 1.4 Watt loss at the end of a 100m cable (for this reason)...
For full functionality you should use either:
802.3at, PoE Plus, .3at injector, DC Power Brick, Cisco ePoE, or AIR-PWRINJ4
Also always use CAT-5e or better as there is more loss of power in Cat5
If the additional power is not available and cannot be negotiated, the AP will function with reduced performance in 15.4 Watt (802.3af modes).
AP-3700 (.af) 15.4 Watt mode.
When in 802.3af mode the AP-3700 will come up in 3x3:3 mode with both radios (same as many competitors) who only have 3 radios but you lose the ability of that 4th radio which helps not only in overall performance but also allows the AP to beam-form (to a 3 spatial stream client).
Additionally, if you do need to use a module and still have a need to operate from a 15.4 Watt power source, the AP will still allow the three Watt module to run but will scale back to a 2x2:2 mode on the other two radios.
Regards,
Fred Niehaus N8CPI
Technical Marketing Engineer
Wireless Networking Group
Cisco Systems, Inc

2 vs. 3 spatial streams or 3502 vs. 3602?

Similar Messages

Maybe you are looking for