Debug Commands: r to z

debug rbcp

To configure Router Blade Control (RBCP) debug options, use the debug rbcp command.

debug rbcp { all | detail | errors | packet} { enable | disable}

Syntax Description

all

Configures the debugging of RBCP.

detail

Configures the debugging of RBCP detail.

errors

Configures the debugging of RBCP errors.

packet

Configures the debugging of RBCP packet trace.

enable

Enables the RBCP debugging.

disable

Disables the RBCP debugging.

Command Default

None

Examples

The following example shows how to enable the debugging of RBCP settings:


(Cisco Controller) > debug rbcp packet enable

debug rfid

To configure radio frequency identification (RFID) debug options, use the debug rfid command.

debug rfid { all | detail | errors | nmsp | receive} { enable | disable}

Syntax Description

all

Configures the debugging of all RFID.

detail

Configures the debugging of RFID detail.

errors

Configures the debugging of RFID error messages.

nmsp

Configures the debugging of RFID Network Mobility Services Protocol (NMSP) messages.

receive

Configures the debugging of incoming RFID tag messages.

enable

Enables the RFID debugging.

disable

Disables the RFID debugging.

Command Default

None

Examples

The following example shows how to enable the debugging of RFID error messages:


(Cisco Controller) > debug rfid errors enable

debug snmp

To configure SNMP debug options, use the debug snmp command.

debug snmp { agent | all | mib | trap} { enable | disable}

Syntax Description

agent

Configures the debugging of the SNMP agent.

all

Configures the debugging of all SNMP messages.

mib

Configures the debugging of the SNMP MIB.

trap

Configures the debugging of SNMP traps.

enable

Enables the SNMP debugging.

disable

Disables the SNMP debugging.

Command Default

None

Examples

The following example shows how to enable the SNMP debugging:


(Cisco Controller) > debug snmp trap enable

debug transfer

To configure transfer debug options, use the debug transfer command.

debug transfer { all | tftp | trace} { enable | disable}

Syntax Description

all

Configures the debugging of all transfer messages.

tftp

Configures the debugging of TFTP transfers.

trace

Configures the debugging of transfer messages.

enable

Enables the debugging of transfer messages.

disable

Disables the debugging of transfer messages.

Command Default

None

Examples

The following example shows how to enable the debugging of transfer messages:


(Cisco Controller) > debug transfer trace enable

debug voice-diag

To trace call or packet flow, use the debug voice-diag command.

debug voice-diag { enable client_mac1 [ client_mac2] [ verbose] | disable}

Syntax Description

enable

Enables the debugging of voice diagnostics for voice clients involved in a call.

client_mac1

MAC address of a voice client.

client_mac2

(Optional) MAC address of an additional voice client.

Note 

Voice diagnostics can be enabled or disabled for a maximum of two voice clients at a time.

verbose

(Optional) Enables debug information to be displayed on the console.

Note 

When voice diagnostics is enabled from the NCS or Prime Infrastructure, the verbose option is not available.

disable

Disables the debugging of voice diagnostics for voice clients involved in a call.

Command Default

None

Usage Guidelines

Follow these guidelines when you use the debug voice-diag command:

  • When the command is entered, the validity of the clients is not checked.

  • A few output messages of the command are sent to the NCS or Prime Infrastructure.

  • The command expires automatically after 60 minutes.

  • The command provides the details of the call flow between a pair of client MACs involved in an active call.


    Note

    Voice diagnostics can be enabled for a maximum of two voice clients at a time.


Examples

The following example shows how to enable transfer/upgrade settings:


(Cisco Controller) > debug voice-diag enable 00:1a:a1:92:b9:5c 00:1a:a1:92:b5:9c verbose

debug wcp

To configure the debugging of WLAN Control Protocol (WCP), use the debug wcp command.

debug wcp { events | packet} { enable | disable}

Syntax Description

events

Configures the debugging of WCP events.

packet

Configures the debugging of WCP packets.

enable

Enables the debugging of WCP settings.

disable

Disables the debugging of WCP settings.

Command Default

None

Command History

Release Modification
7.6 This command was introduced in a release earlier than Release 7.6.

Examples

The following example shows how to enable the debugging of WCP settings:

(Cisco Controller) >debug wcp packet enable

debug web-auth

To configure debugging of web-authenticated clients, use the debug web-auth command.

debug web-auth { redirect{ enable mac mac_address | disable} | webportal-server { enable | disable}}

Syntax Description

redirect

Configures debugging of web-authenticated and redirected clients.

enable

Enables the debugging of web-authenticated clients.

mac

Configures the MAC address of the web-authenticated client.

mac_address

MAC address of the web-authenticated client.

disable

Disables the debugging of web-authenticated clients.

webportal-server

Configures the debugging of portal authentication of clients.

Command Default

None

Command History

Release Modification
7.6 This command was introduced in a release earlier than Release 7.6.

Examples

The following example shows how to enable the debugging of a web authenticated and redirected client:

(Cisco Controller) > debug web-auth redirect enable mac xx:xx:xx:xx:xx:xx

debug wips

To configure debugging of wireless intrusion prevention system (WIPS), use the debug wips command.

debug wips { all | error | event | nmsp | packet} { enable | disable}

Syntax Description

all

Configures debugging of all WIPS messages.

error

Configures debugging of WIPS errors.

event

Configures debugging of WIPS events.

nmsp

Configures debugging of WIPS Network Mobility Services Protocol (NMSP) events.

packet

Configures debugging of WIPS packets.

enable

Enables debugging of WIPS.

disable

Disables debugging of WIPS.

Command Default

None

Command History

Release Modification
7.6 This command was introduced in a release earlier than Release 7.6.

Examples

The following example shows how to enable debugging of all WIPS messages:

(Cisco Controller) > debug wips all enable

debug wps sig

To configure the debugging of Wireless Provisioning Service (WPS) signature settings, use the debug wps sig command.

debug wps sig { enable | disable}

Syntax Description

enable

Enables the debugging for WPS settings.

disable

Disables the debugging for WPS settings.

Command Default

None

Command History

Release Modification
7.6 This command was introduced in a release earlier than Release 7.6.

Examples

The following example shows how to enable the debugging of WPS signature settings:


(Cisco Controller) > debug wps sig enable

debug wps mfp

To configure the debugging of WPS Management Frame Protection (MFP) settings, use the debug wps mfp command.

debug wps mfp { client | capwap | detail | report | mm} { enable | disable}

Syntax Description

client

Configures the debugging for client MFP messages.

capwap

Configures the debugging for MFP messages between the controller and access points.

detail

Configures the detailed debugging for MFP messages.

report

Configures the debugging for MFP reporting.

mm

Configures the debugging for MFP mobility (inter-Cisco WLC) messages.

enable

Enables the debugging for WPS MFP settings.

disable

Disables the debugging for WPS MFP settings.

Command Default

None

Command History

Release Modification
7.6 This command was introduced in a release earlier than Release 7.6.

Examples

The following example shows how to enable the debugging of WPS MFP settings:


(Cisco Controller) > debug wps mfp detail enable