Closed
Bug 1254417
Opened 9 years ago
Closed 9 years ago
change ateam SSID mandatory rate
Categories
(Infrastructure & Operations Graveyard :: NetOps: Office Wireless, task)
Infrastructure & Operations Graveyard
NetOps: Office Wireless
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: van, Assigned: van)
Details
the old samsung devices autophone is testing only supports 2.4ghz. there is an AP(210) with both the 2.4ghz and 5ghz radios enabled in the lab but for some reason these old devices will sometimes decide to associate to an [1]AP in the employee seating area then disconnect because it doesn't have a decent enough connection to download the tests. this causes dead air time due to the excessive retransmits.
we can fix this by changing the SSID's required transmission rate before associating to 18 mb/s. currently it's set to mandatory at [2]11 mb/s.
i've verified the test phones on the 2.4ghz already connected to AP210 have a transmission rate above 18 mb/s.
[1]
12.97%
<157>timestamp10.252.0.30 AUTHORIZATION-SUCCESS: user: last-resort-ateam-211066; mac: 00:26:37:88:9a:fc; author reason: new session; ssid: ateam; AP 5224/1 <---- should be AP 5230/1
3.11%
<156>timestamp10.252.0.30 DOT1X_AAA_ERR: Excessive retransmits; client: last-resort; mac: 78:d6:f0:cf:8d:11; ssid: ateam; AP 5224/1 <---- should be AP 5230/1
[2]
set service-profile ateam transmit-rate 11g mandatory 11.0 disabled 1.0,2.0,5.5,6.0,9.0 beacon-rate 11.0 multicast-rate AUTO
set service-profile ateam transmit-rate 11ng mandatory 11.0 disabled 1.0,2.0,5.5,6.0,9.0 beacon-rate 11.0 multicast-rate AUTO
Assignee | ||
Updated•9 years ago
|
Assignee: network-operations → vle
Comment 1•9 years ago
|
||
whistlepig - https://whistlepig.mozilla.org/en-US/detail/617/
Assignee | ||
Comment 2•9 years ago
|
||
this was completed last saturday.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•