Header Only - DO NOT REMOVE - Extreme Networks
Question

Whats your expirence using the 8.32.xxxx software release?


Userlevel 4
I have started using the latest EWC software release (8.32.xxxx) in production environments to use the new 3715 access points. In two projects i have some issue using it:

The biggest problem is a complete freeze of some processes (C25 controller), including the internal dhcp server und resulting in an inaccessible web interface (timeout/hang after login screen). Just opened a case for GTAC.

Interested in other user expirence.

Regards
Hartmut

12 replies

We have a few 8.32 deployments but all on v2110 controllers with no issues as yet.
We're on 08.21.01.0198 (C4110-2 controllers) and have seen this issue since we upgraded in October. The response from the controller is very janky and sporadic. It will be working fine one moment, then hang or respond sluggishly. Clicking refresh will resolve the issue most of the time and the page will pop up as though there was never a problem. Its as though the browser has finished rendering the page in the background but was unable to display it for whatever reason. I've put up with it for now because the refresh generally gets me to where I want to be, but it would be nice to know if this is a known bug and there is a fix for it, even if that means upgrading again.
Colin Steadman wrote:

We're on 08.21.01.0198 (C4110-2 controllers) and have seen this issue since we upgraded in October. The response from the controller is very janky and sporadic. It will be working fine one moment, then hang or respond sluggishly. Clicking refresh will resolve the issue most of the time and the page will pop up as though there was never a problem. Its as though the browser has finished rendering the page in the background but was unable to display it for whatever reason. I've put up with it for now because the refresh generally gets me to where I want to be, but it would be nice to know if this is a known bug and there is a fix for it, even if that means upgrading again.

I saw this issue on C5210 controllers throughout the 08.21.xx firmware. I found the best browsers to use were Chrome (Windows) or Safari (Mac). I am not sure if the issue was addressed in 08.31.xx or 08.32.xx, but I am now on 08.32.01.0035 and it seems to be resolved. The currently available version is 08.32.04.0006.
Colin Steadman wrote:

We're on 08.21.01.0198 (C4110-2 controllers) and have seen this issue since we upgraded in October. The response from the controller is very janky and sporadic. It will be working fine one moment, then hang or respond sluggishly. Clicking refresh will resolve the issue most of the time and the page will pop up as though there was never a problem. Its as though the browser has finished rendering the page in the background but was unable to display it for whatever reason. I've put up with it for now because the refresh generally gets me to where I want to be, but it would be nice to know if this is a known bug and there is a fix for it, even if that means upgrading again.


I would agree with that IE (especially later versions) has been very unreliable with identiFi controller management but Chrome & Firefox are generally very stable. Same goes for the NMS interface too.
Colin Steadman wrote:

We're on 08.21.01.0198 (C4110-2 controllers) and have seen this issue since we upgraded in October. The response from the controller is very janky and sporadic. It will be working fine one moment, then hang or respond sluggishly. Clicking refresh will resolve the issue most of the time and the page will pop up as though there was never a problem. Its as though the browser has finished rendering the page in the background but was unable to display it for whatever reason. I've put up with it for now because the refresh generally gets me to where I want to be, but it would be nice to know if this is a known bug and there is a fix for it, even if that means upgrading again.

Thanks guys, I much prefer Chrome anyway so will install that until a window opens up for another software upgrade.
Userlevel 7
Colin Steadman wrote:

We're on 08.21.01.0198 (C4110-2 controllers) and have seen this issue since we upgraded in October. The response from the controller is very janky and sporadic. It will be working fine one moment, then hang or respond sluggishly. Clicking refresh will resolve the issue most of the time and the page will pop up as though there was never a problem. Its as though the browser has finished rendering the page in the background but was unable to display it for whatever reason. I've put up with it for now because the refresh generally gets me to where I want to be, but it would be nice to know if this is a known bug and there is a fix for it, even if that means upgrading again.

Colin,

I would suggest at a minimum you run the 8.21.12 code. You may need to clear your browser cache from time to time when anomalies arise. In the release notes we report all the browsers we test against. Unfortunately we can't test all the patches that get released in between the GA code cycle. If you find something that's reproducible, please feel free to reach out to the GTAC and open a ticket for investigation.

Regards,
Doug Hyde
ESE Extreme Networks
Userlevel 7
Hartmut,

I will take a look at your ticket and review the files you posted.

Regards,

Doug Hyde
ESE Extreme Networks
I have one issue with Policy on the controller with code 8.32. If Deny everything and then go into the filter rules to allow certain ports it doesn't work. I have to choose Containment VLAN and then allow certain ports and then deny all.. Very odd.. I even worked on this issue with GTAC.
Userlevel 7
Jim Seaman wrote:

I have one issue with Policy on the controller with code 8.32. If Deny everything and then go into the filter rules to allow certain ports it doesn't work. I have to choose Containment VLAN and then allow certain ports and then deny all.. Very odd.. I even worked on this issue with GTAC.

was that for a captive portal WLAN service?
what AP type did you use, legacy or only new ones?
Jim Seaman wrote:

I have one issue with Policy on the controller with code 8.32. If Deny everything and then go into the filter rules to allow certain ports it doesn't work. I have to choose Containment VLAN and then allow certain ports and then deny all.. Very odd.. I even worked on this issue with GTAC.

No. Open network. No captive portal.
Userlevel 7
Jim Seaman wrote:

I have one issue with Policy on the controller with code 8.32. If Deny everything and then go into the filter rules to allow certain ports it doesn't work. I have to choose Containment VLAN and then allow certain ports and then deny all.. Very odd.. I even worked on this issue with GTAC.

Might be useful so below a example that works for access control=deny, running 8.32.04.

In that case I'll allow only DHCP/DNS for the clients and also http/https traffic.
The last rule is important to allow the return/downlink traffic.
And also please make sure that you set the default topology in the WLAN service.

Userlevel 7
Jim Seaman wrote:

I have one issue with Policy on the controller with code 8.32. If Deny everything and then go into the filter rules to allow certain ports it doesn't work. I have to choose Containment VLAN and then allow certain ports and then deny all.. Very odd.. I even worked on this issue with GTAC.

Do you have any legacy access points (26xx or 4102) in your configuration or any access points that have not been updated to the 8.32.x image??

General rule...

Default action is the last rule on the rules list. All your traffic will hit the filter rules before hitting the default action. Couple of things to point out...

Access - In Policy Rules List ( Most Common)

Allow = Puts the traffic in the default topology defined in the WLAN service else apply the default topology defined in the Global Default Policy (most cases B@AP Untagged)
Contain to VLAN = Traffic goes in the VLAN ID selected
Deny = Traffic is dropped if you match this rule

If you do not have an end rule that says deny all traffic then the default action is hit. The same access rules above apply.

Ap's with older code or ap's that do not support these advance access methods in the Filter Rules List will default to supporting contain to VLAN as the default action. If the access is set to allow on the individual rule line then the traffic will be placed in the default actions contain to VLAN ID.

Reply