Guest

Preview Tool

Cisco Bug: CSCvv78719 - AP2800/3800/4800/1560/6300 fails to transmit data frame to the client from the radio interface

Last Modified

Oct 09, 2020

Products (1)

  • Cisco Aironet 1850 Series Access Points

Known Affected Releases

8.5(161.0) 8.5(161.6) ap-17.3.1.9

Description (partial)

Symptom:
COS AP could not send out the data frame to the client from the radio interface

it seems the AP could not send out the data frame to the client from the radio interface. (TCP-SYN&DNS)

From wireless client capture: No found tcp.flags == 0x0012
From OTA capture: No found tcp.flags == 0x0012
From AP uplink capture:  found many tcp.flags == 0x0012
No found SYN-ACK on OTA & PC.
No found SYN-ACK on OTA & PC.

 
DNS:
in the AP debug, there are both DNS query and response,
but we could not see it in the radio sniffer trace.

Jul  3 02:11:35 kernel: [*07/03/2020 02:11:35.5619] [1593742295:561896] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 57355 opcode 0
Jul  3 02:11:35 kernel: [*07/03/2020 02:11:35.9526] [1593742295:952632] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 31337 opcode 0
Jul  3 02:11:35 kernel: [*07/03/2020 02:11:35.9528] [1593742295:952830] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 31337 opcode 0
Jul  3 02:11:35 kernel: [*07/03/2020 02:11:35.9609] [1593742295:960956] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] <apr1v1> [D:W] DNS REPLY : id 31337 opcode 0
Jul  3 02:11:36 kernel: [*07/03/2020 02:11:36.5336] [1593742296:533664] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 48392 opcode 0
Jul  3 02:11:36 kernel: [*07/03/2020 02:11:36.5416] [1593742296:541644] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] <apr1v1> [D:W] DNS REPLY : id 48392 opcode 0
Jul  3 02:11:36 kernel: [*07/03/2020 02:11:36.5678] [1593742296:567864] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 57355 opcode 0
Jul  3 02:11:36 kernel: [*07/03/2020 02:11:36.5769] [1593742296:576953] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] <apr1v1> [D:W] DNS REPLY : id 57355 opcode 0
Jul  3 02:11:37 kernel: [*07/03/2020 02:11:37.0897] [1593742297: 89727] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 53874 opcode 0
Jul  3 02:11:37 kernel: [*07/03/2020 02:11:37.0966] [1593742297: 96687] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] <apr1v1> [D:W] DNS REPLY : id 53874 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.0902] [1593742298: 90228] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 53874 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.5518] [1593742298:551814] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 48392 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.5518] [1593742298:551847] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 48392 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.5601] [1593742298:560145] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] <apr1v1> [D:W] DNS REPLY : id 48392 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.5722] [1593742298:572244] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 57355 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.5724] [1593742298:572400] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 57355 opcode 0
Jul  3 02:11:38 kernel: [*07/03/2020 02:11:38.5814] [1593742298:581399] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] <apr1v1> [D:W] DNS REPLY : id 57355 opcode 0
Jul  3 02:11:39 kernel: [*07/03/2020 02:11:39.0951] [1593742299: 95185] [AP3C51.0E40.871E] [9c:da:3e:91:99:61] < wifi1> [U:W] DNS QUERY : id 53874 opcode 0

From AP uplink capture: found many DNS query&reply.
From OTA&wireless PC capture: found many DNS query only

Conditions:
Seen with MU-MIMO enabled, and with an AP of one of the following models:
2800/3800/4800/1560/6300

This bug does not apply to any other AP model.
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.