Jump to content

Recommended Posts

Posted

Not seen any problems as yet, upgrading lots of flavours of Apple devices. It could well be a Meru issue which can be addressed with a firmware upgrade.

 

Talking of which, in typical Apple style, iOS9.0.1 is now out (already) and is approx. 30MB in size depending on the device.

Posted

did you try the workaround:

 

Workaround:

 

1) Please make Sure SSID broadcast is set to ON, on the ESS profile.

 

2) Please set the SSID broadcast Preference for Vport is set to "Till association".

 

 

 

Above settings are changed from GUI and does not require AP/controller reboot to take the change in effect.

 

(Login to GUI>Configuration>ESS>configure the SSID as per the steps mentioned)

 

 

 

With the above two changes test the IOS9 client connectivity.

 

 

 

If no success Please make following changes on 3-4 Aps in one location and try connecting,

 

 

 

Identify an access-points for test.

 

Access the controller on CLI-SSH (putty).

 

• Type "show ap" to find the apid of the access point which we will use for test.

 

• Type "conn ap ex for ap ID 14 type conn ap 14".

 

• Type following two commands.

 

• radio parentbeacon radio0 never

 

• radio parentbeacon radio1 never

 

. Exit

Posted
I can't see this option : Please set the SSID broadcast Preference for Vport is set to "Till association".

 

Anywhere :(

 

Config > EES > (pick profile):

It called: "SSID Broadcast Preference" just above the transmission rates. It's only available for Virtual Port. Half our network is virtual port and half 802.11ac is virtualcell. I don't see the option in the virtualcell network.

Posted

We too are having this issue.

 

Changing SSID Broadcast Preference to "Till Association" didn't do the trick for us. However, 'allowing multicast flag' did work (as described at the end of the thread from the top link in the first post). It still isn't bullet proof though - one iPad seems to be dropping off before we have to reconnect it again. I'm looking forward to an actual fix from Meru.

Posted
We are running Meru kit and had a couple of iphone users running ios 9 who couldn't connect, we just reset the network settings on the devices, reconnected and it was fine. I'm hoping it doesn't end up being a wider issue.
Posted

We have had the same issues, only updated 2 Ipad air 2`s to IOS 9.0.1 thankfully. The workaround above did fix the issue where the SSID wasn't appearing at all.

But now on one of the devices the SSID disappears and reappears constantly.

Spent 2h 30m on the phone to Meru yesterday (which was very painful!) they ran a few scripts on the AP`s.

Hoping they fix this soon as more and more will be coming in with IOS 9!

Posted

Hi. I've been having this problem and I've seen a solution on the meru forums that worked for me. You just need to enable Allow Multicast Flag in the ESS settings. I've pasted below what it actually does but whatever it is, it lets IOS9 devices connect. Not a full fix but it will do for now.

 

On: Enables multicasting.

Enable multicasting only if you need to use a multicast application. Enabling multicasting causes all multicast packets on the air side to appear on the wired side, and all multicast packets on the wired side to appear on the air side.

Caution! Multicasting is allowed only when an ESS profile has a one-to-one mapping with the default VLAN for this ESS profile; no other ESS profile uses the same VLAN and security rules associated with this ESS profile do not redirect traffic to another VLAN. Multicasting is an advanced feature. Enable multicasting only if you need to use a multicast application. Enabling multicasting causes all multicast packets on the air side to appear on the wired side, and all multicast packets on the wired side to appear on the air side.

 

Off: Disables multicasting.

Posted
Hi. I've been having this problem and I've seen a solution on the meru forums that worked for me. You just need to enable Allow Multicast Flag in the ESS settings. I've pasted below what it actually does but whatever it is, it lets IOS9 devices connect. Not a full fix but it will do for now.

 

On: Enables multicasting.

Enable multicasting only if you need to use a multicast application. Enabling multicasting causes all multicast packets on the air side to appear on the wired side, and all multicast packets on the wired side to appear on the air side.

Caution! Multicasting is allowed only when an ESS profile has a one-to-one mapping with the default VLAN for this ESS profile; no other ESS profile uses the same VLAN and security rules associated with this ESS profile do not redirect traffic to another VLAN. Multicasting is an advanced feature. Enable multicasting only if you need to use a multicast application. Enabling multicasting causes all multicast packets on the air side to appear on the wired side, and all multicast packets on the wired side to appear on the air side.

 

Off: Disables multicasting.

 

Will try now

Posted

Has there been any updates on this?

 

So far there seems to be two possible resolutions:

 

Resolution 1:

 

On each AP:

 

radio parentbeacon radio0 never

radio parentbeacon radio1 never

(can be scripted to run on all at reboot so settings are not lost?)

 

AND

 

On the controller (ESS settings):

 

Set SSID Broadcast on

Set the SSID broadcast Preference for Vport is set to "Till association".

 

Resolution 2:

 

On the controller (ESS settings): Allow Multicast.

 

Does anyone have any experience on which resolution is more effective?

 

Does the issue lie with Apple or Meru (or both)?

 

Is there a long-term fix due (either from Meru or Apple)?

 

Does the IOS9.02 update fix it?

 

We notice at the issue affects 320, but not 332i or AP832e

 

Controller MC4200 6.1-2-28.

 

Thanks,

 

Bruce.

Posted

From the Meru Forums

 

Note that it is now asked to also file a ticket with Apple:

please note that Meru/Fortinet has already opened up a ticket and filed a bug with Apple developers and Apple has requested that Meru customers experiencing connectivity issues with IOS9 clients contact apple support and open a ticket referencing the Apple bug ID # 22800345.

 

I can only recommend all of you to do this as the final fix will have to come from Apple...

Posted
We raised a ticket with MERU and they dialled in and did some tinkering and it's now working....

 

Do Meru still provide support for AP320 APs?

 

Thanks,

 

Bruce.

Posted
We raised a ticket with MERU and they dialled in and did some tinkering and it's now working....

 

Did they inform you what changes they made?

 

Thanks,

 

Bruce.

Posted
yes they are still supported

 

Can I ask what date this was? Because when we contacted Meru, they apparently told us it wasn't an issue with Meru, but things could changed since.

 

Thanks,

 

Bruce.

Posted
Can I ask what date this was? Because when we contacted Meru, they apparently told us it wasn't an issue with Meru, but things could changed since.

 

Thanks,

 

Bruce.

 

The last software maintenance release was 15th August, but you should still get software support until Feb 2016 - depends on your contract though!

There is a field notice in your support portal about it.

Posted
Did they inform you what changes they made?

 

Thanks,

 

Bruce.

 

All I know is this:

 

A script was loaded onto the Meru controller by Meru Support, this would have run when the APs were rebooted - however, not sure as to the content of the script.

Posted
All I know is this:

 

A script was loaded onto the Meru controller by Meru Support, this would have run when the APs were rebooted - however, not sure as to the content of the script.

 

probably the "radio parentbeacon never" thing in the Meru document I posted

Posted

The field notice from Meru (which CyberNerd posted above) describes adding a boot script for the access points to the system. However, the instructions are for version 6.1........... we are running 4!

 

Does anyone know how I can add this AP script on for this version? For 6.1 it seems it is under 'maintenance --> Profile Management' but there isn't a 'profile management' option in version 4. It must be possible somehow - I have found a 'default init script' box under 'Configuration --> Controller' but I assume this is to specify the location a script as opposed to editing/uploading one. Thanks

Posted
@nick3young. If you don't have any luck in this thread, and you don't have an active support contract with Meru then you might want to talk to Switchshop or BuildingZones who both employ highly regarded and long experienced Meru engineers.
Posted

Haha... that doesn't half read like a shameless plug Psydii.... we're not affiliated with either of those two companies in any way are we?! :-)

 

I do have an active support contract but I'm sure you'll know now these things can often work. I will have to jump through countless hoops and layers of support before I can get a straight answer to the question I posted above. I was hoping someone on here might have already tried the fix on the same version as me and be able to provide me with a quick response. I will fall back on our support (and post the fix here though) if it does seem like nobody is using our prehistoric version of Meru!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...