1242 AG joins Mesh, but clients can't connect

Unanswered Question
Sep 14th, 2010
User Badges:

Our site is using a 2106 controller, to which is connected a 1520 root AP, which is parent to another 1520 mesh AP about 250 meters distant. These two AP's are working well. We had a metal building where connectivity was poor, where we added a 1242AG. It joins the network fine and all diagnostics I can view - that are meaningful to me - appear OK. However, clients roaming from the range of the mesh 1520 to the 1242AG are dropped and can't reconnect. Signal diagnostics on two separate clients (one Intel chipset, one Atheros) show strong 2.4 GHz signal in the building and correct SSID. I have connected successfully once, but very tenuous. Ping latencies very variable and up to half are dropped.


Is there something obvious we are overlooking? Why won't the clients stay connected / reconnect like they do when we roam from the root AP to the other 1520 mesh AP?


Controller Inventory:

Model No.AIR-WLC2106-K9
Burned-in MAC Address
Maximum number of APs supported6
FIPS Prerequisite ModeDisable

UDI :

Product Identifier DescriptionAIR-WLC2106-K9
Version Identifier DescriptionV04
Serial Number
Entity NameChassis
Entity Description2100 Series WLAN Controller:6 APs




1242 Inventory:

Product ID
Version ID
Serial Number
Entity Name
Entity Description
Certificate Type
H-REAP Mode supported
Software Version
Boot Version
IOS Version
Mini IOS Version


1520 Inventory:

Product ID
Version ID
Serial Number
Entity Name
Entity Description
Certificate Type
H-REAP Mode supported
Software Version
Boot Version
IOS Version
Mini IOS Version
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
nazdravii Fri, 09/17/2010 - 06:20
User Badges:

A couple more details . . .

Client with a few advanced diagnostics shows multiple "association time-out", constantly incrementing in the range where we expect it to connect to the 1242AG AP.

Pinging the root AP or the 1st mesh AP (the parent of the 1242AG) from a PC connected to the wired switch to which the root AP & 2106 is connected, the first packet is dropped then the succeeding 3 are returned without errors and <1ms). However no packets are returned - request timed out for the 1242AG.

nazdravii Tue, 09/21/2010 - 13:23
User Badges:

http://www.newegg.com/Product/Product.aspx?Item=N82E16833978020   Made a few changes and some results are better:

1) Set "diversity" of 1242AG's 5 GHz antenna to "right", the external antenna through which we expect it to join with nearby mesh AP. Having done this, still cannot "ping" the 1242AG.

2) Set Mesh > Bridge Data Rate to "auto" for all AP's. Had been changed from 24 Mbps (fixed) to 54 Mbps (fixed)


Now we can ping the IP of the 1242 AG. Clients can now roam to the 1242AG and stay connected, however data rates slow to a crawl. Pinging the 1242 from a switch-connected server (same switch to which root AP and 2106 are connected) is not terrible - round trip times 3 ms to 35 ms. Pinging the same server from a client connected to the 1242 access point yield latencies in the 1000's. Remote client sessions just barely hang on.


So is the 1242AG too distant? There is no line-of-sight to the parent 1522, elevations differ by about 70 feet . . . any opinions whether that's the key issue to address?


Antenna recommendations? Using this one . . .

Actions

This Discussion

Related Content