XCC - VLAN mapping - no IP address
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-16-2021 09:43 PM
Hello,
Devices are not getting an IP address when mapped to a certain VLAN after successful authentication.
VLAN mapping on the XCC is configured as below
Switchport where the AP is connected has the VLAN tagged.
Extreme Control is returning:
XCC version: 05.36.02
Any ideas what it could be?
Thank you,
Klaus
Devices are not getting an IP address when mapped to a certain VLAN after successful authentication.
VLAN mapping on the XCC is configured as below
Switchport where the AP is connected has the VLAN tagged.
Extreme Control is returning:
Tunnel-Private-Group-Id='14:1'
Tunnel-Type='13:1' Tunnel-Medium-Type='6:1' |
XCC version: 05.36.02
Any ideas what it could be?
Thank you,
Klaus
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-22-2021 11:39 PM
Opened a TAC case and was given this:
Detailed steps are provided in the following article which is to create Tunnel-Private-Group-ID for XCC
https://extremeportal.force.com/ExtrArticleDetail?an=000059011
Detailed steps are provided in the following article which is to create Tunnel-Private-Group-ID for XCC
https://extremeportal.force.com/ExtrArticleDetail?an=000059011
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-23-2021 04:09 PM
Check the levels of code you are running. We are running the below levels and the integration is working fine. We were initially running an earlier version of XMC/Control and had problems as you are noticing.
XMC/ Control: v8.5.6.17
XCC: 05.36.03.0017
Essentially policy takes care of the vlan / isid without any special tweaking. I am having issues getting captive portal to work (in our case it is hosted on control) but the basic vlan assignment & fa works fine.
Switch Definition for XCC in Control:


XMC/ Control: v8.5.6.17
XCC: 05.36.03.0017
Essentially policy takes care of the vlan / isid without any special tweaking. I am having issues getting captive portal to work (in our case it is hosted on control) but the basic vlan assignment & fa works fine.
Switch Definition for XCC in Control:
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-29-2021 10:39 AM
Glenn,
Are you using different VLANs for Guest User registration and Guest Access after the successful auth.? If yes, we have recently discovered an issue that prevents the client from getting IP from a new VLAN even if correct role has been assigned after Guest User registration. It has to do with DHCP packet ACKs when the user is in unauthenticated state. it is being looked at and a fix should be introduced in one of the coming releases.
However, you should not have any issues, if the pre and post registration VLANs are the same.
Regards,
Ovais
Are you using different VLANs for Guest User registration and Guest Access after the successful auth.? If yes, we have recently discovered an issue that prevents the client from getting IP from a new VLAN even if correct role has been assigned after Guest User registration. It has to do with DHCP packet ACKs when the user is in unauthenticated state. it is being looked at and a fix should be introduced in one of the coming releases.
However, you should not have any issues, if the pre and post registration VLANs are the same.
Regards,
Ovais
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-29-2021 04:19 PM
Hi Ovais,
For our captive portal the vlan is the same. We do have a lot of WPA2 Enterprise networks which switch vlans.. is the bug just related to captive portal?
Rgds,
Glenn
For our captive portal the vlan is the same. We do have a lot of WPA2 Enterprise networks which switch vlans.. is the bug just related to captive portal?
Rgds,
Glenn
