How to view RSSI on 9124AX

[mbeaulieu]

Hello,

I have this basic setup that I want to use for coverage testing purpose consisting of two C9124AX AP, where one is a C9124AXD setup as the RAP and the other one is an C9124AXI setup as a MAP. My intend is to use the RAP at a fix location and the MAP mounted on a small cart pushed by someone. So my question is, is there a way I can see real time RSSI in dBm of the RAP to MAP link?

Thanks

[Gaurav Kansal]

Dear Mbeaulieu,

You may please go through this link and you find related commands.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/managing-rogue-devices.html

GoodLuck
Regards
Gaurav Kansal

If you find this post helpful then please vote as Helpful and if it solves your issue then please mark as Solution.

[cmcclinton]

Yes from the CLI using a debug command.

SSH to your RAP

Do a 'show dot11 clients' to find the MAC of your MAP. The MAC address of a RAP/MAP is always plus 11 on the base radio mac, so you can use that to confirm the AP you wish to test.

e.g. 

#show dot11 clients

Total dot11 clients: 1
Client MAC Slot ID WLAN ID AID WLAN Name RSSI Maxrate is_wgb_wired
34:5D:A8:3F:29:31 1 18 256 N/A -36 MCS112SS No

NB The MAC listed about is 11 higher than the base MAC of the AP in question.

Do a term mon so you can see debug output and run a debug on the client data rate. Note i found that while the debug output is giving you all that good info the SSH session can still timeout so worth hitting the enter key from time to time.

term mon
debug dot11 client rate 34:5D:A8:3F:29:31

You will get a constantly updating debug giving you the RSSI and the MCS data rate 

Nov 21 04:00:44 kernel: [*11/21/2023 04:00:44.8330] MAC Tx-Pkts Rx-Pkts Tx-Rate(Mbps) Rx-Rate(Mbps) RSSI SNR Tx-Retries
Nov 21 04:00:44 kernel: [*11/21/2023 04:00:44.8331] 34:5D:A8:3F:29:31 0 0 HE-20,2SS,MCS11,GI0.8 (286) HE-20,2SS,MCS11,GI0.8 ,STBC(286) -33 63 0
Nov 21 04:00:45 kernel: [*11/21/2023 04:00:45.8333] 34:5D:A8:3F:29:31 4 9 HE-20,2SS,MCS11,GI0.8 (286) HE-20,2SS,MCS11,GI0.8 ,STBC(286) -34 62 0
Nov 21 04:00:46 kernel: [*11/21/2023 04:00:46.8336] 34:5D:A8:3F:29:31 14 14 HE-20,2SS,MCS11,GI0.8 (286) HE-20,2SS,MCS11,GI0.8 ,STBC(286) -35 61 0
Nov 21 04:00:47 kernel: [*11/21/2023 04:00:47.8338] 34:5D:A8:3F:29:31 2 5 HE-20,2SS,MCS11,GI0.8 (286) HE-20,2SS,MCS11,GI0.8 ,STBC(286) -35 61 0
Nov 21 04:00:48 kernel: [*11/21/2023 04:00:48.8341] 34:5D:A8:3F:29:31 3 3 HE-20,2SS,MCS11,GI0.8 (286) HE-20,2SS,MCS11,GI0.8 ,STBC(286) -34 62 0

[mbeaulieu]

Hi,

This seems to be exactly what I am looking for. I will try this sometime in July and will let you know, but thanks

[Rich R]

@cmcclinton 
> Note i found that while the debug output is giving you all that good info the SSH session can still timeout so worth hitting the enter key from time to time.

exec-timeout 0