A fabric access point is joined and a client is passing traffic. A capture on the controller's data path shows none of that client's frames. What does the empty capture mean?
Select an answer to reveal the explanation.
Short Explanation
The client is talking, and you are listening on the wrong wire. In this fabric the data goes to the fabric edge, not through the controller's data path. An empty capture there is what a working client looks like.
Full Explanation
Fabric wireless keeps CAPWAP control with the controller and sends user data to the fabric edge. A client that is passing traffic will not show up on the controller's data path, so this empty capture means you are looking in the wrong place. It does not mean the client is idle. Fabric data does not always appear on the controller. The access point is joined, so the empty data capture is not a failed join. Fabric does not mirror user data to the controller, and an empty capture there does not prove the edge is down. The edge is where the frames should be. A fabric client is passing traffic, and a capture on the controller's data path is empty. In fabric mode the data goes to the fabric edge, not through the controller data tunnel. That empty capture is expected. Exam caveat: control traffic can still appear at the controller while data does not. Do not read a healthy control session as proof that data is tunneled there too. Operational check: capture on the fabric edge for that client and confirm the frames are there while the controller data path stays empty.