01-15-2014 02:54 AM
I have a wireless meshed network, AP-104 on main network, linking to a building with another ap-104, this remote network is connected to the main network no probelm. If i plug in a laptop in the remote network i get an IP from the main LAN.
The problem is that no AP's on the remote site are joining the instant network, so when i look at the virtual controller i only see the two AP's providing the mesh link.
When i boot one of the AP-93's i get the following message over and over again:
Rebooting AP due to uplink ap denied me, from (MAC and IP of remote LAN Meshing AP)
I have just gone to the latest firmware 220.127.116.11-18.104.22.168_41049, this seemed to have caused the problem.
Any info / ideas appreciated,
01-15-2014 05:28 AM
Do you have auto join enabled ?
Is it possible for you to check if the mesh point (console boot process) was able to go through the upgrade ?
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
01-15-2014 09:00 AM
Turns out its a version 4 firmware issue.
We had just a basic layer 2 bridge, so the main lan (building a) was extended to the remote site (building b), in building b we have more AP's for extending wireless coverage in building b.
Version 4 stops this working!!
01-16-2014 06:31 AM
I had a called raised with TAC, they didnt suggest to go to 22.214.171.124 at the time, and i needed to get it back up again so decided to roll back.
I had to roll backto 126.96.36.199-188.8.131.52 for it to work.
The latest available firmware on autoupdate will break the network described earlier. Apparently the two mesh AP's will need to be in a dedicated instant network, This instant network when denies any other AP's in building b to join the instant network. These AP's would need to be in their own instant network.