Customer Service Center
Home
Knowledge Base
Contact Support
License Activation
|
Contact Support
|
License Activation
|
Spirent KB Article
Doc ID: KNI16637
Printer Friendly
Email Article Link
Spirent TestCenter: 5.06 - C1 Roaming sometimes loops in the list ONLY at a small subset of ALL the set BSSIDs
Symptoms
The intention of the test is to show that a specific client will roam both to the DUT and away from the DUT to all available BSSIDs in the list and back to the DUT (back and forth multiple times).
IE there is a BSSD of B4:FB:E4:1E:C8:1E which is the DUT. The test would exercise all roam variations for the DUT.
The client device(s) does not roam around ALL the BSSIDs on the BSSIDs’ list specified under Target AP Editor window, does not matter if the profile has 30 APs available or a much smaller list like 10 APs, when the roaming event is triggered, the sequential roam would just not advance to the full set of APs.
Sometimes It would seem to just stay on the first few BSSIDs of the list available, or in the worst case, only on the first BSSID, additionally the “Fast Transition Failure” counter sometimes increments and sometimes looks like we are just “skipping” some of the BSSIDs on the list.
As per our discussion, this issue is impacting you because you cannot prove all roam cases (a 40x40 matrix) until the Spirent client will alternate between a single BSSID and all the BSSIDs for your other various products.
At the time some BSSIDs are skipped once, the client does NOT try to connect to them anymore, looks like all of those BSSIDs are now on sort of Spirent client “Black List”. But a simple close of the .tcc file and open of it totally reset the “blacklist” type behavior. Reset of the Spirent client, and presenting it with the same BSSD roaming list makes this to work again for a while.
Duplicate the BSSID of a DUT and inserting these into a BSSID roaming sequence to demonstrate roam “to” and “from” a specified DUT, so the device (STC device) just skip the duplicates and is NOT reporting any failure on the counters (Fast Transition Failure counter keeps = 0).
Environment
Spirent TestCenter
WiFi
C1
Roaming
BSSID
Duplicate BSSID
Explanation/Resolution
Basically, we need to determine why the devices do NOT ROAM through all the list of BSSID and just at a small subset of the list
Is the "Black List" behavior an expected behavior or NOT?.
ANSWER
: There is NO black list behavior expected, this has been
fixed within 5.16 release
Why the Roam feature skips the duplicates?
ANSWER
: When a Duplicate BSSID is ignored, the Fast Transition Failure counter increment, issue
fixed within 5.19 release
And why we are just "skipping" some BSSID and NOT reporting any Failure on the counters.
ANSWER
: Same as bullet 2 above, the issue should be
fixed within 5.19 release
What qualifies the FT-Transition success and failure counter for Spirent? How engaged is this check? L2UF frame?
ANSWER
: STC check roaming message exchanges and if there is reject to re association or authentication failure or there is no response for roaming request after some time then we treat it as failure.
CR-01431514
Subject: 5.06 - C1 Roaming sometimes loops in the list ONLY at a small subset of ALL the set BSSIDs
Date/Time Opened: 2/192020
Date/Time Closed: 6/15/2021
Target Release: 5.20
Root Cause
Defect
Version
2.0
Publish Date
2021-06-15
Categories
Product : WiFi,Spirent TestCenter,WiFi
Related Articles