Question 390
A lab access point advertises multi-link capabilities, but a packet capture from one channel is interpreted as the entire client's activity. What follow-up evidence should be trended across deployments?
Explanation
Correct Answer
Track link-ID decode gaps, channel observation coverage, unexpected single-link fallback and multi-link capture clock offsets. This addresses the decisive observation: A lab access point advertises multi-link capabilities, but a packet capture from one channel is interpreted as the entire client's activity.
Incorrect Answers
The option would address: Track PMF negotiation mismatches, unexpected unprotected robust frames and parser errors on protected subtypes. The scenario instead reports: A lab access point advertises multi-link capabilities, but a packet capture from one channel is interpreted as the entire client's activity. The decisive distinction is: Track link-ID decode gaps, channel observation coverage, unexpected single-link fallback and multi-link capture clock offsets.
Monitor aggregation decode errors, unexpected retransmission behavior and differences between transmitted A-MPDU and A-MSDU formats. In the reported case: A lab access point advertises multi-link capabilities, but a packet capture from one channel is interpreted as the entire client's activity. The decisive distinction is: Track link-ID decode gaps, channel observation coverage, unexpected single-link fallback and multi-link capture clock offsets.
Trend TID distributions, DSCP-to-user-priority mismatches and voice frames falling into unexpected access categories. The observed condition is: A lab access point advertises multi-link capabilities, but a packet capture from one channel is interpreted as the entire client's activity. The decisive distinction is: Track link-ID decode gaps, channel observation coverage, unexpected single-link fallback and multi-link capture clock offsets.