nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

dm raw-packet-debugging mode assistance

johnpenaflor

Dear Admin,

please assist due to our dm raw-packet-debugging mode doesn't provide any output. see the details below.

UNIT 1: SL 1: ICX7150-48PF-2X10G_2X1G POE 48-port Management Module

Command Output

Switch1#dm raw max 20
Switch1#dm raw mode brief
Switch1#dm raw
Raw packet debugging is on now
Switch1#
Switch1#
Switch1#

Find more posts tagged with

Accepted answers

All comments

happytohelp

Hi johnpenaflor,

Are you accessing the switch via console/telnet or ssh ? You can check via 'show who'.

Also share output of 'show debug'.

Mayank

Hi Johnpenaflor,

Thank you for reaching us.

I understand that when you are using dm raw-packet-debugging mode doesn't provide any output to you .

The dm raw command usage vary in different scenarios for example :

* If you're connected via SSH:

If you are connected via ssh or telnet, you also need to specify the session # which can be checked with the show who command.

- Sh who
To see which SSH session you're in

- Debug destination ssh X
To direct the logs to the SSH we're in

- Debug dest ssh x
- Dm raw mode brief
- Dm raw filter none
- Dm raw max 20
- Dm raw

But in case you are connected via console then use the below process :

* If you're connected via Console session:

- Dm raw mode brief
- Dm raw filter none
- Dm raw max 20
- Dm raw

Moving Forward the dm raw utility is a debug which will show the packets that are hitting the cpu. This will tell us if there is any specific traffic that is causing the high cpu spikes. But we always suggest our customer to use this command under tac supervision.

You can also refer the below short video for more information on DM raw command :

https://youtu.be/6a18tpkE_y4?si=IZB0H3tTCQtXnL0p

Moving Forward If this issue is not resolved , Please log a ticket with the below link so that we will help you further

https://support.ruckuswireless.com/contact-us

I hope this information helps you

Please feel free to leave us a message if any concerns

Thanks

Chandini

Hi Johnpenaflor

Thank you for reaching us.

Adding to the post could you also please help us with the firmware version running on the switch ?

Thanks

johnpenaflor

Hi Happytohelp,

I am conneceted via ssh.

show who output below.

SSH connections (inbound):
1 established, client ip address 192.168.0.14, server hostkey DSA, user is admin, privilege super-user
using vrf default-vrf.
you are connecting to this session
22 second(s) in idle
2 closed
3 closed
4 closed
5 closed
6 closed
7 closed
8 closed
9 closed
10 closed
SSH connection (outbound):
11 closed
12 closed
13 closed
14 closed
15 closed
16 closed
17 closed
18 closed
19 closed
20 closed

show debug output.

Debug message destination: Console
Running Config was potentially changed at 1697456886.80783748 epoch time
SZ_Server_IP: 0.0.0.0 SZ_Server_port 0
RSTP ALL Transistions debugging is on

johnpenaflor

Hi Mayank,

thank you very much for your reply. it is indeed that the link you provided is helpful specially the videos in youtube ruckus network education. additionally I have applied the debug destination ssh (X). however I have flooded by the debug output which I cannot stop. refer on the output below.

Debug: Oct 16 15:53:56 RSTP[25d6b91]: Timer Alert - hello when timer_expired on port 1/1/1(0) , VLAN 115
Debug: Oct 16 15:53:56 RSTP: PTX entering the Periodic state , port 1/1/1(0) VLAN 115
Debug: Oct 16 15:53:56 RSTP[25d6b91]: Tx RSTP Config BPDUDebug: Oct 16 15:53:56 Port 1/1/1(0) VLAN 115
0000 02 02 7e 1000c0c5205845a0 00000000
1000c0c5205845a0 08 001 0000 1400 0200 0f00
Debug: Oct 16 15:53:56 RSTP[25d6b91]: Timer Alert - hello when timer_expired on port 1/1/11(10) , VLAN 115
Debug: Oct 16 15:53:56 RSTP: PTX entering the Periodic state , port 1/1/11(10) VLAN 115
Debug: Oct 16 15:53:56 RSTP[25d6b91]: Tx RSTP Config BPDUDebug: Oct 16 15:53:56 Port 1/1/11(10) VLAN 115
0000 02 02 7e 1000c0c5205845a0 00000000

could you share the shortcut for stopping it.

thank you.

johnpenaflor

Hi Chandini,

our version is ver 08.0.90gT211

Mayank

Hi Johnpenaflor ,

To stop you can open another ssh session and run undebug all, that will stop all debug to the debug destination ssh x .Or you can also try Ctrl+c to stop

Thanks

happytohelp

Hi johnpenaflor,

You are connecting via ssh session 1 while the default debug destination is console. So you can configure "debug destination ssh 1" to redirect the logs to your session.

You can type "undebug all" to stop.