Guest

Preview Tool

Cisco Bug: CSCut39572 - In QinQ setup, SVLAN and CVLAN IDs are not consistently assigned

Last Modified

Oct 15, 2018

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases

7.6(101.248)

Description (partial)

Symptom:
Basic configuration information:
- One AP is in its own AP group.
- WLAN-VLAN mapping is defined in the AP group (open SSIDs). Different VLAN IDs are used on different AP groups for the same SSID. This is to fulfil the per SSID per AP VLAN ID assignment requirement.
- WLAN-VLAN mapping is assigned by AAA server using AAA override (802.1x SSIDs).
- SVLAN (outer VLAN) ID is specified in the AP group configuration. Different SVLAN IDs are used on different AP groups.

Observed behavior in non-QinQ setup:
- WLAN-VLAN mapping remains the same when clients move from one AP to another.  The VLAN ID used in the first AP will be maintained even after a client moves to the second AP.

Observed behavior in QinQ setup:
- CVLAN (inner VLAN, WLAN-VLAN mapping in AP group) ID is assigned in the same way as in non-QInQ setup when clients move from one AP to another.
- SVLAN ID is changed when clients move from one AP to another.  The SVLAN IDs defined in the AP group that the clients are currently connected to are used.

The problem is that the backend access gateway uses SVLAN-CVLAN pairs to identify the locations of the clients for access control, portal display and usage tracking.  The above behavior takes SVLAN ID values from AP group settings of the connected AP while the CVLAN ID values are taken from the WLAN-VLAN mapping of the previous AP.  It leads to incorrect SVLAN-CVLAN assignment and the access gateway presents wrong portal to customers.

The expected behavior is to always use the SVLAN and CVLAN IDs of the AP that the clients are currently connected.

Conditions:
In QinQ setup, SVLAN and CVLAN IDs are not consistently assigned when clients move from one AP to another
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.