Contents

1   Command Descriptions

Commands starting with “debug m” through commands starting “debug z” are included.

1.1   debug mobile-ip

1.1.1   Purpose

Enables the generation of debug messages for Mobile IP events.

1.1.2   Command Mode

exec (10)

1.1.3   Syntax Description

1.1.4   Default

The generation of debug messages for Mobile IP events is disabled.

1.1.5   Usage Guidelines

Use the debug mobile-ip command to enable the generation of debug messages for Mobile IP events.

Use the no form of this command to disable the generation of debug messages for the specified type of Mobile IP events.

Note:  

The SmartEdge™ 100 router does not support the standby and switchover keywords.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.1.6   Examples

The following example enables the generation of debug messages for all Mobile IP events:

[local]Redback#debug mobile-ip all

1.2   debug mobile-ip agent-common

1.2.1   Purpose

Enables the generation of debug messages that are common to both the home-agent (HA) instance and foreign-agent (FA) instances.

1.2.2   Command Mode

exec (10)

1.2.3   Syntax Description

1.2.4   Default

The generation of debug messages for HA instance and FA instance events is disabled.

1.2.5   Usage Guidelines

Use the debug mobile-ip agent-common command to enable the generation of debug messages for HA and FA instances. When you use this command without specifying an option, the system generates debug messages for all FA and HA events.

Use the no form of this command to disable the generation of debug messages for HA instance and FA instance events.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.2.6   Examples

The following example limits the generation of debug messages to Mobile IP interface events:

[local]Redback#debug mobile-ip agent-common interface

1.3   debug mobile-ip authentication

1.3.1   Purpose

Enables the generation of debug messages for authentication and security in Mobile IP.

1.3.2   Command Mode

exec (10)

1.3.3   Syntax Description

1.3.4   Default

The generation of debug messages for Mobile IP authentication is disabled.

1.3.5   Usage Guidelines

Use the debug mobile-ip authentication command to enable the generation of debug messages for Mobile IP authentication. When you use this command without specifying an option, the system generates debug messages for all Mobile IP authentication events.

Use the no form of this command to disable the generation of debug messages for Mobile IP authentication.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.3.6   Examples

The following example limits the generation of debug messages to AAA events:

[local]Redback#debug mobile-ip authentication aaa

1.4   debug mobile-ip foreign-agent

1.4.1   Purpose

Enables the generation of debug messages for the foreign-agent (FA) instance.

1.4.2   Command Mode

exec (10)

1.4.3   Syntax Description

1.4.4   Default

The generation of debug messages for the FA instance is disabled.

1.4.5   Usage Guidelines

Use the debug mobile-ip foreign-agent command to enable the generation of debug messages for the FA instance. When you use this command without specifying an option, the system generates debug messages for all FA events.

Use the no form of this command to disable the generation of debug messages for the FA.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.4.6   Examples

The following example enables the generation of debug messages for Mobile IP care-of address events:

[local]Redback#debug mobile-ip foreign-agent care-of-address

1.5   debug mobile-ip home-agent

1.5.1   Purpose

Enables the generation of debug messages for home-agent (HA) instance.

1.5.2   Command Mode

exec (10)

1.5.3   Syntax Description

1.5.4   Default

The generation of debug messages for Mobile IP HA events is disabled.

1.5.5   Usage Guidelines

Use the debug mobile-ip home-agent command to enable the generation of debug messages for HA instance events. When you use this command without specifying an option, the system generates debug messages for all HA instance events.

Use the no form of this command to disable the generation of debug messages for the HA instance.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.5.6   Examples

The following example limits the generation of debug messages to the FA peer:

[local]Redback#debug mobile-ip home-agent foreign-agent-peer

1.6   debug mobile-ip interaction

1.6.1   Purpose

Enables the generation of debug messages for Mobile IP module interaction events with other SmartEdge modules, such as Router Configuration Manager (RCM) and Interface and Circuit State Manager (ISM).

1.6.2   Command Mode

exec (10)

1.6.3   Syntax Description

1.6.4   Default

The generation of debug messages for external Mobile IP events is disabled.

1.6.5   Usage Guidelines

Use the debug mobile-ip interaction command to enable the generation of debug messages for Mobile IP events relating to interactions with modules, such RCM and ISM. When you use this command without specifying an option, the system generates debug messages for all Mobile IP module interaction events.

Use the no form of this command to disable the generation of debug messages for external Mobile IP events.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.6.6   Examples

The following example limits the generation of debug messages to RCM events:

[local]Redback#debug mobile-ip interaction rcm

1.7   debug mobile-ip packet

1.7.1   Purpose

Enables the generation of debug messages for Mobile IP packets. This is a filtered debugging feature for specific source, destination, circuit, or packet types.

1.7.2   Command Mode

exec (10)

1.7.3   Syntax Description

1.7.4   Default

The generation of debug messages for Mobile IP packets is disabled.

1.7.5   Usage Guidelines

Use the debug mobile-ip packet command to enable the generation of debug messages for Mobile IP packets. This is a filtered debugging feature for specific source, destination, circuit, or packet types. When you use this command without specifying an option, the system generates debug messages for all Mobile IP packet events.

Use the no form of this command to disable the generation of debug messages for the specified type of Mobile IP packets.

Note:  

The SmartEdge router does not support the standby and switchover keywords.

You can determine the value of the circuit-handle argument for the mobile node (MN) access interface or the care-of-address (CoA) interface using the show mobile-ip command or the show mobile-ip home-agent-peer command with the detail keyword.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.7.6   Examples

The following example limits the generation of debug messages to registration request (reg-request) packets in both directions:

[local]Redback#debug mobile-ip packet type reg-request

1.8   debug mobile-ip packet-io

1.8.1   Purpose

Enables the generation of debug messages on I/O events on the kernel socket interface for Mobile IP services.

1.8.2   Command Mode

exec (10)

1.8.3   Syntax Description

1.8.4   Default

The generation of debug messages for I/O packets events on a kernel socket interface for Mobile IP services is disabled.

1.8.5   Usage Guidelines

Use the debug mobile-ip packet-io command to enable the generation of debug messages for I/O packets on a kernel socket interface for Mobile IP services. When you use this command without specifying an option, the system generates debug messages for all I/O packet events on a kernel socket interface for Mobile IP services.

Use the no form of this command to disable the generation of debug messages on I/O packet events on a kernel interface for Mobile IP services.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.8.6   Examples

The following example limits the generation of debug messages to output packet events on a kernel socket interface:

[local]Redback#debug mobile-ip packet-io send

1.9   debug mpls-static

1.9.1   Command Mode

exec (10)

1.9.2   Syntax Description

1.9.3   Default

None

1.9.4   Usage Guidelines

Use the debug mpls-static command to enable the generation of static MPLS debugging messages.

Disable the generation of debug messages with the no form of the command.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

1.9.5   Example

The following example enables the generation of static MPLS label-mapping messages:

[local]Redback#debug mpls-static label-mapping

1.10   debug msdp

1.10.1   Purpose

Enables the generation of Multicast Source Discovery Protocol (MSDP) debug messages.

1.10.2   Command Mode

exec (10)

1.10.3   Syntax Description

1.10.4   Default

The generation of debug messages is disabled.

1.10.5   Usage Guidelines

Use the debug msdp command to enable the generation for all MSDP debug messages.

Use the peer-addr argument to enable the generation of MSDP debug messages for a specific MSDP peer.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of MSDP debug messages.

1.10.6   Examples

The following example enables the generation of MSDP debug messages for the peer address, 192.168.5.5:

[local]Redback#debug msdp peer 192.168.5.5

1.11   debug nat

1.11.1   Purpose

Enables the generation of Network Address Translation (NAT) debug messages.

1.11.2   Command Mode

exec (10)

1.11.3   Syntax Description

1.11.4   Default

The generation of debug messages is disabled.

1.11.5   Usage Guidelines

Use the debug nat command to enable the generation of NAT debug messages.

Note:  

The SmartEdge 100 router does not support the standby and switchover keywords.

To store messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command in exec mode to display these stored messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.11.6   Examples

The following example enables the generation of NAT debug messages:

[local]Redback#debug nat

1.12   debug nd

1.12.1   Purpose

Enables the generation of debug messages for Neighbor Discovery (ND) events.

1.12.2   Command Mode

exec (10)

1.12.3   Syntax Description

1.12.4   Default

The generation of debug messages for ND events is disabled.

1.12.5   Usage Guidelines

Use the debug nd command to enable the generation of debug messages for ND events.

Note:  

The SmartEdge router does not support the standby and switchover keywords.

Table 1 lists the keywords supported by the packet-type argument.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command in exec mode to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages for ND events.

1.12.6   Examples

The following example enables the generation of debug messages for interface events for the int1 interface:

[local]Redback#debug nd filter interface int1

1.13   debug ntp

1.13.1   Purpose

Enables the generation of debug messages for the Network Time Protocol (NTP).

1.13.2   Command Mode

exec (10)

1.13.3   Syntax Description

1.13.4   Default

The generation of debug messages for NTP is disabled.

1.13.5   Usage Guidelines

Use the debug ntp command to enable the various types of debug messages for NTP.

Note:  

The SmartEdge 100 router does not support the standby and switchover keywords.

To store messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command in exec mode to display these stored messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages for NTP.

1.13.6   Examples

The following example enables the generation of debug messages for NTP packet and update messages. The commands are followed by sample debug message output:

[local]Redback#debug ntp packet

[local]Redback#debug ntp update



Feb 23 23:36:37: %NTP-7-PKT: Send packet to 155.53.12.12 

Feb 23 23:36:37: %NTP-7-PKT: Receive packet from 155.53.12.12 

Feb 23 23:36:39: %NTP-7-PKT: Send packet to 155.53.32.75 

Feb 23 23:36:39: %NTP-7-PKT: Receive packet from 155.53.12.12 

Feb 23 23:36:39: %NTP-7-PKT: Receive packet from 155.53.32.75 

Feb 23 23:36:43: %NTP-7-PKT: Send packet to 155.53.32.75 

Feb 23 23:36:43: %NTP-7-PKT: Receive packet from 155.53.32.75 

Feb 23 23:36:44: %NTP-7-PKT: Send packet to 155.53.12.12 

Feb 23 23:36:44: %NTP-7-PKT: Receive packet from 155.53.12.12 

Feb 23 23:36:47: %NTP-7-PKT: Send packet to 155.53.32.75 

Feb 23 23:36:47: %NTP-7-PKT: Receive packet from 155.53.32.75 

Feb 23 23:36:48: %NTP-7-PKT: Send packet to 155.53.12.12 

Feb 23 23:36:48: %NTP-7-PKT: Receive packet from 155.53.12.12 

Feb 23 23:36:49: %NTP-7-PKT: Send packet to 155.53.32.75 

Feb 23 23:36:49: %NTP-7-PKT: Receive packet from 155.53.32.75 

Feb 23 23:36:50: %NTP-7-PKT: Send packet to 155.53.12.12 

Feb 23 23:36:50: %NTP-7-PKT: Receive packet from 155.53.12.12 

Feb 23 23:36:50: %NTP-7-UPD: adjust clock: current offset at 4287 usecs 

Feb 23 23:36:51: %NTP-7-PKT: Send packet to 155.53.32.75 

Feb 23 23:36:51: %NTP-7-PKT: Receive packet from 155.53.32.75 

Feb 23 23:37:06: %NTP-7-PKT: Send packet to 155.53.32.75 

Feb 23 23:37:06: %NTP-7-PKT: Receive packet from 155.53.32.75 

Feb 23 23:37:07: %NTP-7-PKT: Send packet to 155.53.12.12 

Feb 23 23:37:07: %NTP-7-PKT: Receive packet from 155.53.12.12 

Feb 23 23:37:07: %NTP-7-UPD: adjust clock: current offset at 4200 usecs

1.14   debug ospf

1.14.1   Purpose

Enables the generation of debug messages for all Open Shortest Path First (OSPF) events.

1.14.2   Command Mode

exec (10)

1.14.3   Syntax Description

1.14.4   Default

The generation of debug messages is disabled.

1.14.5   Usage Guidelines

Use the debug ospf command to enable the generation of debug messages for all OSPF events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.14.6   Examples

The following example enables the generation of debug messages for OSPF events:

[local]Redback#debug ospf

1.15   debug ospf bfd

1.15.1   Purpose

Enables the generation of Bidirectional Forwarding Detection (BFD) debug messages for all Open Shortest Path First (OSPF) instances.

1.15.2   Command Mode

exec (10)

1.15.3   Syntax Description

This command has no keywords or arguments.

1.15.4   Default

The generation of debug messages is disabled.

1.15.5   Usage Guidelines

Use the debug ospf bfd command to enable the generation of BFD debug messages for all OSPF instances.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.15.6   Examples

The following example enables the generation of BFD debug messages for all OSPF instances:

[local]Redback#debug opsf bfd

1.16   debug ospf flooding

1.16.1   Purpose

Enables the generation of debug messages for Open Shortest Path First (OSPF) flooding events.

1.16.2   Command Mode

exec (10)

1.16.3   Syntax Description

1.16.4   Default

The generation of debug messages is disabled.

1.16.5   Usage Guidelines

Use the debug ospf flooding command to enable the generation of debug messages for OSPF flooding events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.16.6   Examples

The following example enables the generation of debug messages for OSPF flooding events:

[local]Redback#debug ospf flooding

1.17   debug ospf interface

1.17.1   Purpose

Enables the generation of debug messages for a specific Open Shortest Path First (OSPF) interface.

1.17.2   Command Mode

exec (10)

1.17.3   Syntax Description

1.17.4   Default

The generation of debug messages is disabled.

1.17.5   Usage Guidelines

Use the debug ospf interface command to enable the generation of debug messages for a specific interface.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.17.6   Examples

The following example enables the generation of debug messages for events for the OSPF interface at IP address 10.10.1.1:

[local]Redback#debug ospf interface 10.10.1.1

1.18   debug ospf ldp-synchronization

1.18.1   Purpose

Enable the generation of Open Shortest Path First (OSPF) Label Distribution Protocol-Interior Gateway Protocol (LDP-IGP) debug messages.

1.18.2   Command Mode

exec (10)

1.18.3   Syntax Description

This command has no keywords or arguments.

1.18.4   Default

The generation of debug messages is disabled.

1.18.5   Usage Guidelines

Use the debug ospf ldp-synchronization command to enable the generation of OSPF LDP-IGP debug messages.

Use the no form of this command to disable the generation of OSPF LDP-IGP debug messages.

1.18.6   Examples

The following example shows how to enable the generation of OSPF LDP-IGP debug message on your system:

[local]Redback#debug ospf ldp-synchronization

1.19   debug ospf lsdb

1.19.1   Purpose

Enables the generation of debug messages for Open Shortest Path First (OSPF) link-state database (LSDB) events.

1.19.2   Command Mode

exec (10)

1.19.3   Syntax Description

1.19.4   Default

The generation of debug messages is disabled.

1.19.5   Usage Guidelines

Use the debug ospf lsdb command to enable the generation of debug messages for OSPF LSDB events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.19.6   Examples

The following example enables the generation of debug messages for all OSPF LSDB events:

[local]Redback#debug ospf lsdb

1.20   debug ospf neighbor

1.20.1   Purpose

Enables the generation of debug messages for Open Shortest Path First (OSPF) neighbor events.

1.20.2   Command Mode

exec (10)

1.20.3   Syntax Description

1.20.4   Default

The generation of debug messages is disabled.

1.20.5   Usage Guidelines

Use the debug ospf neighbor command to enable the generation of debug messages for OSPF neighbor events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.20.6   Examples

The following example enables the generation of debug messages for only the OSPF neighbor at IP address 43.23.45.8:

[local]Redback#debug ospf neighbor neighbor-id 43.23.45.8

1.21   debug ospf packet

1.21.1   Purpose

Enables the generation of debug messages for Open Shortest Path First (OSPF) packet events.

1.21.2   Command Mode

exec (10)

1.21.3   Syntax Description

1.21.4   Default

The generation of debug messages is disabled.

1.21.5   Usage Guidelines

Use the debug ospf packet command to enable the generation of debug messages for OSPF packet events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.21.6   Examples

The following example enables the generation of debug messages for OSPF Hello packet events:

[local]Redback#debug ospf packet hello

1.22   debug ospf rcm

1.22.1   Purpose

Enables the generation of debug messages for interactions between Open Shortest Path First (OSPF) and the Router Configuration Manager (RCM).

1.22.2   Command Mode

exec (10)

1.22.3   Syntax Description

1.22.4   Default

The generation of debug messages is disabled.

1.22.5   Usage Guidelines

Use the debug ospf rcm command to enable the generation of debug messages for interactions between OSPF and the RCM. The RCM manages the configuration database.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.22.6   Examples

The following example enables the generation of debug messages for OSPF RCM events:

[local]Redback#debug ospf rcm

1.23   debug ospf redistribution

1.23.1   Purpose

Enables the generation of debug messages for Open Shortest Path First (OSPF) redistribution events.

1.23.2   Command Mode

exec (10)

1.23.3   Syntax Description

1.23.4   Default

The generation of debug messages is disabled.

1.23.5   Usage Guidelines

Use the debug ospf redistribution command to enable the generation of debug messages for OSPF redistribution events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.23.6   Examples

The following example enables the generation of debug messages for redistribution events pertaining to OSPF instance 64001:

[local]Redback#debug ospf redistribution instance 64001

1.24   debug ospf rib

1.24.1   Purpose

Enables the generation of debug messages for interactions between Open Shortest Path First (OSPF) and the Routing Information Base (RIB).

1.24.2   Command Mode

exec (10)

1.24.3   Syntax Description

1.24.4   Default

The generation of debug messages is disabled.

1.24.5   Usage Guidelines

Use the debug ospf rib command to enable the generation of debug messages for interactions between OSPF and the RIB.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.24.6   Examples

The following example enables debug messages for OSPF RIB events for external routes:

[local]Redback#debug ospf rib route-type external

1.25   debug ospf spf

1.25.1   Purpose

Enables the generation of debug messages for Open Shortest Path First (OSPF) Shortest Path First (SPF) calculations.

1.25.2   Command Mode

exec (10)

1.25.3   Syntax Description

1.25.4   Default

The generation of debug messages is disabled.

1.25.5   Usage Guidelines

Use the debug ospf spf command to enable the generation of debug messages for OSPF SPF calculations.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.25.6   Examples

The following example enables the generation of debug messages for OSPF SPF calculations:

[local]Redback#debug ospf spf

1.26   debug packet

1.26.1   Purpose

Enables the generation of debug messages that include the header and data of the packet on a specified circuit for a specified traffic direction.

1.26.2   Command Mode

exec (10)

1.26.3   Syntax Description

1.26.4   Default

The generation of debug messages for packets on a circuit is disabled.

1.26.5   Usage Guidelines

Use the debug packet circuit command to enable the generation of debug messages that include the header and data of the packet on a specified circuit for a specified traffic direction. This command supports the following circuit types:

• Cross-connect circuit
• 802.1Q PVC
• 802.1Q tunnel
• PPPoE circuit
• VLL access circuits

The debug packet circuit command also supports these listed circuit types over the following link groups:

• Access link group (economical and noneconomical)
• 802.1Q link group (applies to constituent circuits only)
• Ethernet link group (applies to constituent circuits only)

Enabling packet sampling on more than one circuit is permitted. Specify whether the debugging of packets is to apply to incoming or outgoing traffic on the circuit by using either the in or out keyword.

To enable the generation of debug messages for packets on a circuit belonging to a specified link group, use the lg lg-name or lg lg-id construct with the debug packet circuit command.

For 802.1Q and Ethernet link groups, you can apply the debug packet circuit command to only each constituent circuit within the link group instead of the entire link group. The constituent circuits are the physical ports or channels in the link group bundle. Before applying this command to a constituent circuit, obtain the slot and port, or slot, port, and circuit ID of the constituent circuit by using the show link-group lg-name detail command. This information is displayed in the Constituent Circuits field within the command output. Use the debug packet circuit slot/port [circuit-id] {in | out} command to sample traffic on the given constituent circuit within the link group.

Note:  

Applying the debug packet circuit command to a link group is functionally equivalent to applying this command to each constituent circuit of the link group. The application implies that the debug request remains active on the constituent circuits that have not received or transmitted the requested number of packets defined by the count parameter until the request is canceled by the no debug packet circuit command. We recommend that after you issue the debug packet circuit command for a link group and the requested number of packets is displayed, issue the no debug packet circuit command for the link group.

To enable the generation of debug messages for packets on a circuit within a specified slot and port number of a traffic card, use the slot and port keywords with the debug packet circuit command. After you have selected either the link group or slot and port in which the circuit resides, specify the circuit-id argument.

The debug packet circuit command is not persistent. After closing the vty session, this command is disabled.

Table 2 lists the values for the circuit-id argument.

The syntax for the circuit-id argument is [pppoe sess-id] [vlan-id vlan-id].

Use the no debug packet all command to cancel the generation of debug messages for all circuits in both directions of the current CLI session. Use the no debug packet circuit {lg {lg-name | id lg-id} | slot/port [circuit-id] command with either the in or out keyword to cancel the generation of debug messages for incoming or outgoing traffic on the specified circuit.

1.26.6   Examples

The following example shows how to enable the generation of debug messages for incoming packets on a circuit in slot 9 and port 1. The debug messages are to display 1000 consecutive packets with each packet displaying the first 128 bytes:

[local]Redback#debug packet circuit 9/1 in count 1000 size 128


741474a9/0000000144/559600000:09/IPPA/EU00: 9/1:1023:63/1/1/5

debug packet 1/1 timestamp 144.847569955 length 128/252 eu 5

ETH   DST_MAC 00:30:88:02:7D:74 SRC_MAC 00:10:94:00:00:01 ETHER_TYPE ipv4(0800)

IP   VER 4 HDR_LEN 20 LEN 238 ID 0 FRAG_OFFS 0 TTL 10 PROTO udp

     CHKSUM 9DF1 SRC 9.1.0.2 DST 9.10.0.2

UDP  SRC_PORT 1024 DST_PORT 0 LEN 218 CHK_SUM FFFF

DATA 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

    10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F

    20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F

    30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F

    40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F

    50 51 52 53 54 55

1.27   debug pedgr

1.27.1   Purpose

Enables the generation of debug messages for process execution descriptor graph (PEDGR) events.

1.27.2   Command Mode

exec (10)

1.27.3   Syntax Description

1.27.4   Default

The generation of debug messages for PEDGR events is disabled.

1.27.5   Usage Guidelines

Use the debug pedgr command to enable the generation of debug messages for PEDGR events.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

Note:  

The SmartEdge router does not support standby controller cards; therefore, the standby and switchover keywords are not applicable.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.27.6   Examples

The following example enables the generation of debug messages for PEDGR events:

[local]Redback#debug pedgr

1.28   debug pim

1.28.1   Purpose

Enables the generation of Protocol Independent Multicast (PIM) debug messages.

1.28.2   Command Mode

exec (10)

1.28.3   Syntax Description

1.28.4   Default

The generation of debug messages is disabled.

1.28.5   Usage Guidelines

Use the debug pim command to enable the generation of PIM debug messages.

Use the group-addr argument to enable the generation of PIM debug messages for a specific IGMP group.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of PIM debug messages.

1.28.6   Examples

The following example enables the generation of PIM debug messages for the group, 224.1.1.1:

[local]Redback#debug pim 224.1.1.1

1.29   debug pim bfd

1.29.1   Purpose

Enables generation of Protocol Independent Multicast (PIM) Bidirectional Forwarding Detection (BFD) debug messages.

1.29.2   Command Mode

exec (10)

1.29.3   Syntax Description

This command has no keywords or arguments.

1.29.4   Default

Generation of debug messages is disabled.

1.29.5   Usage Guidelines

Use the debug pim bfd command to enable generation of PIM BFD debug messages.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Use the terminal monitor command (in exec mode) if you are connected through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable generation of PIM BFD debug messages.

1.29.6   Examples

The following example enables generation of PIM BFD debug messages.

[local]router1#debug pim bfd

1.30   debug pim packet

1.30.1   Purpose

Enables the generation of Protocol Independent Multicast (PIM) multicast data packet debug messages.

1.30.2   Command Mode

exec (10)

1.30.3   Syntax Description

1.30.4   Default

The generation of debug messages is disabled.

1.30.5   Usage Guidelines

Use the debug pim packet command to enable the generation of PIM multicast data packet debug messages.

Use the group-addr argument to enable the generation of PIM multicast data packet debug messages for a specific IGMP group.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of PIM debug multicast data packet messages.

1.30.6   Examples

The following example enables the generation of all PIM multicast data packet debug messages:

[local]Redback#debug pim packet

The following example enables the generation of PIM multicast data packet debug messages for the IGMP group, 224.1.1.1:

[local]Redback#debug packet 224.1.1.1

1.31   debug pim ppa

1.31.1   Purpose

Enables the generation of debug messages for Protocol Independent Multicast (PIM) routes downloaded to Packet Processing ASICs (PPAs).

1.31.2   Command Mode

exec (10)

1.31.3   Syntax Description

1.31.4   Default

The generation of debug messages is disabled.

1.31.5   Usage Guidelines

Use the debug pim ppa command to enable the generation of debug messages for PIM routes downloaded to PPAs.

Use the slot-num argument or group-addr argument to enable the generation of PIM multicast data packet debug messages only for a specific slot or IGMP group, respectively. Use the slot-num group-addr construct to enable the generation of PIM multicast data packet debug messages only for a specific IGMP group on a specific slot.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages for PIM routes downloaded to PPAs.

1.31.6   Examples

The following example enables the generation of debug messages for PIM routes downloaded to PPAs:

[local]Redback#debug pim ppa

1.32   debug pim rp-mapping

1.32.1   Purpose

Enables the generation of bootstrap router (BSR) and rendezvous point (RP) debug messages.

1.32.2   Command Mode

exec (10)

1.32.3   Syntax Description

1.32.4   Default

The generation of debug messages is disabled.

1.32.5   Usage Guidelines

Use the debug pim rp-mapping command to enable the generation of BSR and RP debug messages.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secured Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of BSR and RP debug messages.

1.32.6   Examples

The following example enables the generation of BSR and RP debug messages:

[local]Redback#debug pim rp-mapping

1.33   debug pm

1.33.1   Purpose

Enables the generation of debug messages for the Process Manager (PM).

1.33.2   Command Mode

exec (10)

1.33.3   Syntax Description

1.33.4   Default

The generation of debug messages for the PM is disabled.

1.33.5   Usage Guidelines

Use the debug pm command to enable the generation of debug messages for the PM.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

Note:  

The SmartEdge router does not support standby controller cards; therefore, the standby and switchover keywords are not applicable.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.33.6   Examples

The following example enables PM memory-error events:

[local]Redback#debug pm memory-error

1.34   debug policy access-list

1.34.1   Purpose

Enables the generation of debug messages for policy access control lists (ACLs).

1.34.2   Command Mode

exec (10)

1.34.3   Syntax Description

1.34.4   Default

The generation of debug messages is disabled.

1.34.5   Usage Guidelines

Use the debug policy access-list command to enable the generation of debug messages for policy ACLs.

Note:  

The SmartEdge router does not support the standby and switchover keywords.

To store messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command in exec mode to display these stored messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages for policy ACLs.

1.34.6   Examples

The following example enables the generation of debug messages for policy ACLs:

[local]Redback#debug policy access-list

1.35   debug policy general

1.35.1   Purpose

Enables the generation of debug messages for all configured routing policies, including autonomous system (AS) path lists, community lists, IP access control lists (ACLs), IP prefix lists, key chains, and route maps.

1.35.2   Command Mode

exec (10)

1.35.3   Syntax Description

1.35.4   Default

None

1.35.5   Usage Guidelines

Use the debug policy general command to enable the generation of debug messages for all configured routing policies, including AS path lists, community lists, IP ACLs, IP prefix lists, key chains, and route maps.

Use the boot active or boot standby construct to enable debugging messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debugging messages while the system is switching from the active to the standby controller card.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.35.6   Examples

The following example enables the generation of debug messages for all configured routing policies:

[local]Redback#debug policy general

1.36   debug ppp

1.36.1   Purpose

Enables the generation of debug messages for various types of Point-to-Point Protocol (PPP) events on the system.

1.36.2   Command Mode

exec (10)

1.36.3   Syntax Description

1.36.4   Default

The generation of debug messages for all PPP events on the system is disabled.

1.36.5   Usage Guidelines

Use the debug ppp command to enable the generation of debug messages for various types of PPP events on the system.

Table 3 lists the types of PPP events for which you can enable debug messages.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information on logging, see Logging.

Use the no form of this command to disable the generation of debug messages for PPP events.

1.36.6   Examples

The following example shows how to enable the generation of debug messages for PPP packet events:

[local]Redback#debug ppp packet

1.37   debug ppp multilink

1.37.1   Purpose

Enables the generation of debug messages for Multilink Point-to-Point Protocol (MP) events.

1.37.2   Command Mode

exec (10)

1.37.3   Syntax Description

1.37.4   Default

The generation of debug messages for MP events is disabled.

1.37.5   Usage Guidelines

Use the debug ppp multilink command to enable the generation of debug messages for MP events.

Use the boot active or boot standby construct to enable debug messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debug messages while the system is switching from the active to the standby controller card.

Note:  

The SmartEdge 100 router does not support the standby and switchover keywords.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages for MP events.

1.37.6   Examples

The following example shows how to enable the generation of debug messages for MP events:

[local]Redback#debug ppp multilink

1.38   debug pppoe

1.38.1   Purpose

Enables the generation of debug messages for various types of Point-to-Point Protocol over Ethernet (PPPoE) events.

1.38.2   Command Mode

exec (10)

1.38.3   Syntax Description

1.38.4   Default

Debugging is disabled.

1.38.5   Usage Guidelines

Use the debug pppoe command to enable the generation of debug messages for various types of PPPoE events.

Use the boot active or boot standby construct to enable debug messages during a system reload for the active or standby controller card, respectively.

Use the switchover keyword to enable debug messages while the system is switching from the active to the standby controller card.

Note:  

The SmartEdge 100 router does not support the standby and switchover keywords.

Use the exception keyword to enable the display of PPPoE exception debug messages.

Use the timer keyword to display timer-related debug messages.

To store debug messages in the system log buffer, use the logging debug command (in global configuration mode). Use the show log command (in exec mode) to display these stored debug messages.

To display messages in real time, use the logging console command (in context configuration mode) if you are connected to the system through the console port. Or, use the terminal monitor command (in exec mode) if you are connected to the system through a Telnet or Secure Shell (SSH) session.

Note:  

For more information about logging commands and the terminal monitor command, see the Command List.

Use the no form of this command to disable the generation of debug messages.

1.38.6   Examples

The following example shows how to enable the generation of all types of PPPoE debug messages and displays sample debug messages:

[local]Redback#debug pppoe all

1.39   debug qos

1.39.1   Purpose

Enables the generation of quality of service (QoS) debug messages.

1.39.2   Command Mode

exec (10)

1.39.3   Syntax Description