Controllerless Networks

Hi,

I'm having a strange issue while configuring an IAP-RAP3 (also tried with a IAP-105) via Airwave and the Instant GUI there.

In my scenario, I create a new wireless guest network, nothing fancy, just a simple one with internal IAP authentication and captive portal. However, I would also like to include a network access rule to this network, and here comes the point:

In the Airwave Instant GUI, I create the rule, then after clicking "Apply all" the setting is saved and prepared to be pushed to my IAP.

The IAP accepts all the network configuration, but it does not accept the network access rule. I always get a mismatch for my VC and finally it states "Retry limit reached" (see image)

I tried clicking the "Apply All" button below repeatedly, but the mismatch is still there.

I have version 7.7.9 of Airwave and the latest version of IAP (6.3.1.2-4.0.0.3_41784).

Thanks any help,

best regards

Are you using the internal Captive Portal on the IAP or an external one?

There are certain configuration elements that are not available when authorizing against the internal DB of the IAP and things like role derivation is one of them. For things like this, you need an external Captive Portal along with an external radius source.

Also keep in mind that there is generally a stagger between feature functionality in IAP vs what is supported in Airwave. Both are new releases, I'll check with QA for you to see if this is the case here.

Cheers,

Adam

I'm using the internal Captive Portal of the IAP. 

I thought that network access rules wouldn't state a problem to Airwave, actually I configured them from Airwave in the instant GUI. So it may be that this functionality in Airwave is not yet implemented on the IAP firmware?

I checked with a few and this could be a bug. To verify, can you create a new group in Airwave, enable the IGC and then move the devices in question to the group and try to push the config again?

If it works, great - but still may want to open a TAC case as it should work as you've descrbed. If it doesn't work, TAC case is of course the way to go to get this replicated and tracked as a bug for resolution.

Cheers, Adam

I have exact the same issue here - is this a confirmed bug? (using Airwave 7.7.9, IAP-115 with latest Firmware and playing around with internal Captive Portal and Firewall Rules...)