Contents

1   Command Descriptions

Commands starting with “d” through “debug l” are included.

1.1   dad-transmits

1.1.1   Purpose

Configures the number of Neighbor Solicitation (NS) messages the SmartEdge® router sends to its peers for duplicate address detection (DAD) to ensure that the link-local address and the global address of the interface are unique.

1.1.2   Command Mode

ND profile configuration

1.1.3   Syntax Description

1.1.4   Default

The default num-dad-transmits value is 1.

1.1.5   Usage Guidelines

Use the dad-transmit command to configure the number of NS messages the SmartEdge router sends to its peers for DAD to ensure that the link-local address of the SmartEdge router and the global unicast address of the interface that is bound to the circuit are unique. If the router does not receive a response after the last NS message is sent, the addresses are considered unique. For more information about DAD, see Configuring ND.

Use the default form of this command to revert to the default setting.

1.1.6   Examples

The following example shows how to configure a DAD transmit value of 3 for the ND profile ndprofile7:

[local]Redback(config)#context local

[local]Redback(config-ctx)#nd profile ndprofile7

[local]Redback(config-nd-profile)#dad-transmit 3

1.2   dampening

1.2.1   Purpose

Enables external Border Gateway Protocol (eBGP) route dampening for the specified address family.

1.2.2   Command Mode

BGP address family configuration

1.2.3   Syntax Description

1.2.4   Default

Route dampening is disabled. When enabled, the value for the half-life argument is 15 minutes. The value for the reuse argument is 750 minutes. The value for the suppress argument is 2,000 minutes. The value for the max-suppress argument is 4 times the value of the half-life argument.

1.2.5   Usage Guidelines

Use the dampening command to enable eBGP route dampening for the specified address family.

When a route from a remote peer is withdrawn, the local BGP speaker considers the withdrawn route to be a flap, and assigns a penalty of 1,000 to the route. If the remote peer sends a replacement route, the local BGP speaker assigns a penalty of 500 to the route.

Use the no form of this command to disable route dampening for the specified address family.

1.2.6   Examples

The following example shows how to enable route dampening:

[local]Redback(config)#router bgp 64000

[local]Redback(config-bgp)#address-family ipv4 multicast

[local]Redback(config-bgp-af)#dampening

1.3   deadtime

1.3.1   Purpose

Sets the minimum amount of time during which any “dead” peer in the group is ignored when computing the Layer 2 Tunneling Protocol (L2TP) group algorithm.

1.3.2   Command Mode

L2TP group configuration

1.3.3   Syntax Description

1.3.4   Default

The deadtime is set to five minutes.

1.3.5   Usage Guidelines

Use the deadtime command to set the minimum amount of time during which any “dead” peer in the group is ignored when computing the L2TP group algorithm.

A peer is labeled “dead” after it is determined that a new tunnel cannot be established to the peer. This feature prevents an L2TP peer that is not functioning fully from being inundated with connection attempts without disconnecting the peer altogether. It also allows you to identify peers that are not fully functional.

A peer remains labeled as “dead” until a new session is established to it as follows:

• After the deadtime is expired and a connection request arrives, the peer is again considered as a destination, according to the group algorithm.
• If a connection attempt is not made to the peer (the peer is not selected as the destination), the “dead” label is not removed.
• If a connection attempt is made and is successful, the “dead” label is removed from the peer; if the attempt is not successful, the deadtime is again applied to the peer.

  Note:  

  Current sessions to the peer are not brought down if the peer is labeled “dead”. Only attempts to add new tunnels are affected.

  
  

A “dead” peer is labeled as “dead” in the output of the show l2tp peer command in any mode for at least the length of time indicated in the minutes argument.

Use the no or default form of this command to set the deadtime to two minutes.

1.3.6   Examples

The following example shows how to select (or create) an L2TP group and set the number of deadtime minutes to two:

[local]Redback(config-ctx)#l2tp-group name group1

[local]Redback(config-l2tp-group)#default deadtime

The following example shows how to select (or create) an L2TP group and set the number of deadtime minutes to 10:

[local]Redback(config-ctx)#l2tp-group name group1

[local]Redback(config-l2tp-group)#deadtime 10

1.4   debug aaa

1.4.1   Purpose

Enables the generation of accounting, authorization, and authentication (AAA) debug messages.

1.4.2   Command Mode

exec (10)

1.4.3   Syntax Description

1.4.4   Default

The generation of debug messages is disabled.

1.4.5   Usage Guidelines

Use the debug aaa command to enable the generation of AAA debug messages on an SmartEdge router.

Note:  

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

Note:  

You can enter this command multiple times to enable the generation of various types of AAA debug messages.

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 AAA debug messages.

1.4.6   Examples

The following example shows how to enable generation of all AAA debug messages:

[local]Redback#debug aaa all

1.5   debug aaa tacacs+

1.5.1   Purpose

Enables the generation of Terminal Access Controller Access Control System Plus (TACACS+) debug messages.

1.5.2   Command Mode

exec (10)

1.5.3   Syntax Description

1.5.4   Default

The generation of TACACS+ debug messages is disabled.

1.5.5   Usage Guidelines

Use the debug aaa tacacs+ command to enable the generation of TACACS+ debug messages. You can enter this command multiple times, specifying different types of debugging messages.

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 TACACS+ debug messages.

1.5.6   Examples

The following example shows how to enable generation of TACACS+ debug messages for authorization attributes:

[local]Redback#debug aaa tacacs+ attributes

1.6   debug ancp

1.6.1   Purpose

Enables the generation of debug messages for Access Node Control Protocol (ANCP) packets.

1.6.2   Command Mode

exec (10)

1.6.3   Syntax Description

1.6.4   Default

The generation of debug messages for ANCP packets is disabled.

1.6.5   Usage Guidelines

Use the debug ancp command to enable the generation of debug messages for ANCP packets.

Note:  

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

Table 1 lists the keywords for the types of ANCP events or data for which you can enable the generation of 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 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 ANCP packets.

1.6.6   Examples

The following example shows how to enable generation of debug messages for ANCP packets:

[local]Redback#debug ancp packet

1.7   debug arp

1.7.1   Purpose

Enables the generation of Address Resolution Protocol (ARP) debug messages for the current context.

1.7.2   Command Mode

exec (10)

1.7.3   Syntax Description

1.7.4   Default

The generation of ARP debug messages is disabled. If you use this command without any optional syntax, only the generation of ARP event debug messages is enabled.

Note:  

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

1.7.5   Usage Guidelines

Use the debug arp command to enable the generation of ARP debug messages for the current context.

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 ARP debug messages.

1.7.6   Examples

The following example shows how to enable generation of ARP VRRP event debug messages:

[local]Redback#debug arp vrrp

1.8   debug as-path-list

1.8.1   Purpose

Enables the generation of debug messages for the maintenance of autonomous system (AS) path lists and the comparison of Border Gateway Protocol (BGP) AS path attributes with AS path lists.

1.8.2   Command Mode

exec (10)

1.8.3   Syntax Description

1.8.4   Default

None

1.8.5   Usage Guidelines

Use the debug as-path-list command to enable the generation of debug messages for the maintenance of AS path lists and the comparison of BGP AS path attributes with AS path lists.

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.8.6   Examples

The following example shows how to enable generation of debug messages for AS path lists:

[local]Redback#debug as-path-list

1.9   debug atm oam

1.9.1   Purpose

Enables the display of operations, administration, and maintenance (OAM) cells for a specific Asynchronous Transfer Mode (ATM) permanent virtual circuit (PVC).

1.9.2   Command Mode

exec (10)

1.9.3   Syntax Description

1.9.4   Default

The generation of debug messages is disabled for all ATM PVCs.

1.9.5   Usage Guidelines

Use the debug atm oam command to enable the display of OAM cells for a specific ATM PVC. The first 40 bytes of each generated OAM cell displays.

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 standby and switchover keywords are not available for the SmartEdge 100 router.

Note:  

The SmartEdge 100 router limits the value of the slot argument to 2.

Note:  

The value for the port argument on the SmartEdge 100 router depends on the MIC slot in which the ATM OC MIC is installed.

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 a specific ATM PVC.

1.9.6   Examples

The following example shows how to enable the display of OAM cells for ATM PVC with VPI 0 and VCI 100 on port 1 in slot 3:

[local]Redback#debug atm oam 3/1 vpi 0 vci 100

1.10   debug bfd

1.10.1   Purpose

Enables the generation of Bidirectional Forwarding Detection (BFD) 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 bfd command to enable the generation of BFD 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.10.6   Examples

The following example shows how to enable generation of BFD session debug messages:

[local]Redback#debug bfd session

1.11   debug bgp bestpath

1.11.1   Purpose

Enables the generation of messages for BGP best path events.

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 bgp bestpath command to enable the generation of messages for BGP best path events for the current context. The output of the debug bgp bestpath command includes information about how and why a BGP was selected and the length of time the BGP routing process took to perform best path calculation. This information can be useful when troubleshooting BGP. Enter this command without the optional ip-prefix keyword to enable the generation of BGP best-path debug messages for all IP prefixes configuring on this router.

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.11.6   Examples

The following example shows how to enable the generation of messages for all BGP best path events:

[local]Redback#debug bgp bestpath

1.12   debug bgp event

1.12.1   Purpose

Enables the generation of messages for all general Border Gateway Protocol (BGP) events.

1.12.2   Command Mode

exec (10)

1.12.3   Syntax Description

1.12.4   Default

The generation of debug messages is disabled.

1.12.5   Usage Guidelines

Use the debug bgp event command to enable the generation of messages for all general BGP 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.12.6   Examples

The following example shows how to enable the generation of messages for all general BGP events:

[local]Redback#debug bgp event

1.13   debug bgp listen

1.13.1   Purpose

Enables the generation of debug messages for Border Gateway Protocol (BGP) passive open connections.

1.13.2   Command Mode

exec (10)

1.13.3   Syntax Description

1.13.4   Default

The generation of debug messages is disabled.

1.13.5   Usage Guidelines

Use the debug bgp listen command to enable the generation of debug messages for BGP passive open connections, where the remote peer connects to port 179 on the local SmartEdge router.

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.13.6   Examples

The following example enables the generation of debug messages for BGP passive open connections:

[local]Redback#debug bgp listen

1.14   debug bgp message

1.14.1   Purpose

Enables the generation of debug messages for Border Gateway Protocol (BGP) non-update 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 bgp message command to enable the generation of debug messages for BGP non-update 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 shows how to enable generation of debug messages for BGP non-update messages for the BGP neighbor, 10.1.1.1:

[local]Redback#debug bgp 10.1.1.1 message

1.15   debug bgp policy

1.15.1   Purpose

Enables the generation of debug messages for Border Gateway Protocol (BGP) routing policies.

1.15.2   Command Mode

exec (10)

1.15.3   Syntax Description

1.15.4   Default

The generation of debug messages is disabled.

1.15.5   Usage Guidelines

Use the debug bgp policy command to enable the generation of debug messages for BGP routing policies.

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.15.6   Examples

The following example shows how to enable the generation of debug messages for BGP routing policies:

[local]Redback#debug bgp policy

1.16   debug bgp rib

1.16.1   Purpose

Enables the generation of debug messages for interaction between the Border Gateway Protocol (BGP) and the Routing Information Base (RIB).

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 bgp rib command to enable the generation of debug messages for interactions between the BGP routing process 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.16.6   Examples

The following example shows how to enable generation of debug messages for BGP RIB events:

[local]Redback#debug bgp rib

1.17   debug bgp session-state

1.17.1   Purpose

Enables the generation of debug messages for Border Gateway Protocol (BGP) session states and timers.

1.17.2   Command Mode

exec (10)

1.17.3   Syntax Description

1.17.4   Default

Need default information

1.17.5   Usage Guidelines

Use the debug bgp session-state command to enable the generation of debug messages for BGP session states and timers.

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 shows how to enable generation of debug messages for session states and timers for the BGP neighbor, 10.1.1.1:

[local]Redback#debug bgp 10.1.1.1 session-state

1.18   debug bgp update

1.18.1   Purpose

Enables the generation of debug messages for Border Gateway Protocol (BGP) updates.

1.18.2   Command Mode

exec (10)

1.18.3   Syntax Description

1.18.4   Default

The generation of debug messages is disabled.

1.18.5   Usage Guidelines

Use the debug bgp update command to enable the generation of messages for BGP update events.

We recommend the use of the prefix-list pl-name construct when there is a large number of routes in the BGP routing table.

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.18.6   Examples

The following example shows how to enable generation of debug messages for BGP updates for the BGP neighbor, 10.1.1.1:

[local]Redback#debug bgp 10.1.1.1 update

1.19   debug bridge

debug [boot {active | standby} | switchover] bridge {ageing | config | loop-detection | table}

1.19.1   Purpose

Enables the generation of debug messages for bridge-related events and entities.

1.19.2   Command Mode

exec (10)

1.19.3   Syntax Description

1.19.4   Default

None

1.19.5   Usage Guidelines

Use the debug bridge command to enable the generation of debug messages for bridge-related events and entities.

The output for loop detections indicate the following information. Output can be extensive and impact the performance of a production system. Be cautious when enabling bridge debugging messages on large configurations.

• %s LD Disabled CCT %s in bridge %s\n
• State of sending circuit (cct)
• Upticks/retry timeouts
• Whether a circuit is blocked and the retry timeout
• The LD state sent
• LD state change log with from and to state
• Nonblockable circuits
• The circuit chosen for blocking, with its priority/move count and if the threshold is exceeded
• MAC move counts

Note:  

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

1.19.6   Examples

The following example shows how to enable the generation of debug messages for the aging of the BFEs:

[local]Redback#debug bridge ageing

1.20   debug cfm

1.20.1   Purpose

Enables the generation of debug logs for connectivity fault management (CFM) related events.

1.20.2   Command Mode

exec (10)

1.20.3   Syntax Description

1.20.4   Default

None

1.20.5   Usage Guidelines

Use the debug cfm command to enable the generation of debug logs for CFM related events.

1.20.6   Examples

The following example shows how to enable logging of CFM PDU processing:

[local]Redback#debug cfm packet

1.21   debug circuit

1.21.1   Purpose

Enables the generation of debug messages for one or more circuits in the system.

1.21.2   Command Mode

exec (10)

1.21.3   Syntax Description

1.21.4   Default

The generation of debug messages for any circuit is disabled.

1.21.5   Usage Guidelines

Use the debug circuit command to enable the generation of debug messages for one or more circuits in the system.

Note:  

The SmartEdge 100 router limits the value of the slot argument to 2.

Note:  

The value for the port argument on the SmartEdge 100 router is either of the following:

• For a native port, it is either 1 or 2.
• For a MIC port, it depends on the type of MIC and the slot in which it is installed.

To enable the generation of debug messages for specific circuits, follow this two-step process:

1. Decide which type of debug messages to log for the circuits. You can use the facility and category arguments as a construct. For instance, to log all incoming and outgoing PPP packets, use ppp as the value for facility argument and packet as the value for the category argument. Not all facilities have attendant categories.
2. Decide which circuits to debug.For example, to enable debugging on only the circuit on slot 1, port 2, channel 1, subchannel 1, use 1/2 as the value of the slot/port argument, :1 as the value of the channel argument, and :1 as the value of the subchannel argument.

General debugging provides wide coverage. By enabling debug messages for specific circuits, you receive only debug messages related to the circuits of interest.

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.

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

If you specify the VLAN tag value for an 802.1Q tunnel, the command generates debug messages for the tunnel, but not the PVCs within the tunnel.

Table 3 lists the supported facilities for the facility argument. Not all facilities are available for all debug commands, and not all facilities have an “all” option.

Note:  

The SmartEdge 100 router does not support the chdlc and fr keywords.

Use the no forms of this command to disable the generation of debug messages for one or more circuits:

• no debug circuit slot/port circuit-id disables circuit-level debugging only for the specified circuit. All other circuit-level debugging remains in place.
• no debug circuit facility category disables circuit-level debugging for the specified category within the specified facility.
• no debug circuit all disables circuit-level debugging for all circuits, including all facilities and categories. This command restores the system to the default settings.

1.21.6   Examples

The following example show how to enable the generation of all PPP debug messages for all circuits on port 1 on the traffic card in slot 3:

[local]Redback#debug circuit 3/1

[local]Redback#debug circuit ppp all

The following example shows how to enable the generation of AAA debug messages for only subchannel 1 on channel 2 of slot 1, port 1:

[local]Redback#debug circuit 1/1 :2 :1

[local]Redback#debug circuit aaa all

1.22   debug circuit mobile-ip

1.22.1   Purpose

Enables the generation of debug messages for Mobile IP services on a circuit.

1.22.2   Command Mode

exec

1.22.3   Syntax Description

1.22.4   Default

The generation of debug messages for Mobile IP services on a circuit is disabled.

1.22.5   Usage Guidelines

Use the debug circuit mobile-ip command to enable the generation of debug messages for Mobile IP services on a circuit. To use this command, do the following:

1. Issue the debug circuit handle command.
2. Issue the debug mobile-ip command.

When you use this command without specifying an option, the system generates debug messages for all Mobile IP events on a circuit.

Use the no form of this command to disable the generation of debug messages for HAs and FAs on a circuit.

For information about the debug circuit command, see the Command List.

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.22.6   Examples

The following example shows how to limit the generation of debug messages to circuit handle 255/4:1023:63/1/1/12 for an FA instance on a circuit GRE 12:

[local]RedBack#debug circuit handle 255/4:1023:63/1/1/12

[local]Redback#debug circuit mobile-ip foreign-agent

1.23   debug clips

1.23.1   Purpose

Enables the generation of clientless IP service selection (CLIPS) debug messages.

1.23.2   Command Mode

exec

1.23.3   Syntax Description

1.23.4   Default

The generation of CLIPS debug messages is disabled.

1.23.5   Usage Guidelines

Use the debug clips command to enable the generation of CLIPS 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 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 shows how to enable the generation of CLIPS debug messages about all CLIPS details:

[local]Redback#debug clips all

1.24   debug cls

1.24.1   Purpose

Enables the generation of debug messages for IP classifier processes.

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 cls command to enable the generation of debug messages for IP classifier processes. The IP classifier process is responsible for ACL computations and processing, so this command is useful for debugging when ACLs are configured and operating.

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 logging of classifier process debug messages.

1.24.6   Examples

The following example shows how to remove a configured access group, tc1, from the two interface, resulting in debug messages that are displayed by the debug cls command with the work keyword:

[local]Redback(config-ctx)#interface two

[local]Redback(config-if)#no ip access-group tc1

[local]Redback(config-if)#end

[local]Redback#debug cls work

Jul 18 15:51:10: %CLS-7-WORK: (WORK) cls_process_work_order@1458: 
WORK_ORDER: ACL_UNBIND (type=1 prec=1) ctx=0x40080001, ifGrid=0x10000002, (OUT)

Jul 18 15:51:10: %CLS-7-WORK: (WORK) cls_int_unbind_to_ppa@700: 
PPA_UNBIND( ifGrid=0x10000002/OUT, img_grid 400a2000 )

Jul 18 15:51:10: %CLS-7-WORK: (WORK) cls_CLSImageReleaseXX@718: cls_IFCClassifierDelete@349  
released image=0x400a2000; refCount=1

Jul 18 15:51:10: %CLS-7-WORK: (WORK) cls_HWReleaseXX@531: cls_IFCClassifierDelete@353 
released hw=0x400b2200, slot=12; refCount=1

Jul 18 15:51:10: %CLS-7-WORK: (WORK) cls_IFCGC@764: deleting ifc=0x10000002

1.25   debug community-list

1.25.1   Purpose

Enables the generation of debug messages for the maintenance of community lists and for the comparison of Border Gateway Protocol (BGP) community attributes with community lists.

1.25.2   Command Mode

exec (10)

1.25.3   Syntax Description

1.25.4   Default

None

1.25.5   Usage Guidelines

Use the debug community-list command to enable the generation of debug messages for the maintenance of community lists and for the comparison of BGP community attributes with community lists.

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 shows how to enable the generation of debug messages for community lists:

[local]Redback#debug community-list

1.26   debug context

1.26.1   Purpose

Enables the generation of debug messages for the current context.

1.26.2   Command Mode

exec (10)

1.26.3   Syntax Description

1.26.4   Default

The generation of debug messages is disabled.

1.26.5   Usage Guidelines

Use the debug context command to enable the generation of debug messages for the current context.

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 100 router does not support standby controller cards; therefore, the standby and switchover keywords are not applicable.

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.26.6   Examples

The following example enables the generation of context debug messages:

[local]Redback#debug context general

1.27   debug cspf

1.27.1   Purpose

Enables the generation of debug messages for Constrained Shortest Path First (CSPF) events.

1.27.2   Command Mode

exec

1.27.3   Syntax Description

1.27.4   Default

The generation of debug messages for CSPF is disabled.

1.27.5   Usage Guidelines

Use the debug cspf command to enable the generation of debug messages for CSPF 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.

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

1.27.6   Examples

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

[local]Redback#debug cspf ted

1.28   debug dhcp-relay

1.28.1   Purpose

Enables the generation of debug messages for external Dynamic Host Configuration Protocol (DHCP) servers.

1.28.2   Command Mode

exec (10)

1.28.3   Syntax Description

1.28.4   Default

The generation of debug messages for external DHCP server events is disabled.

1.28.5   Usage Guidelines

Use the debug dhcp-relay command to enable the generation of debug messages for external DHCP server events.

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.28.6   Examples

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

[local]Redback#debug dhcp-relay packet

1.29   debug dhcp-server

1.29.1   Purpose

Enables the generation of debug messages for internal Dynamic Host Configuration Protocol (DHCP) servers.

1.29.2   Command Mode

exec (10)

1.29.3   Syntax Description

1.29.4   Default

The generation of debug messages for internal DHCP server events is disabled.

1.29.5   Usage Guidelines

Use the debug dhcp-server command to enable the generation of debug messages for internal DHCP server events.

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.29.6   Examples

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

[local]Redback#debug dhcp-server packet

1.30   debug dhcpv6

1.30.1   Command Mode

exec (10)

1.30.2   Syntax Description

1.30.3   Default

None

1.30.4   Usage Guidelines

Use the debug dhcpv6 command to generate DHCPv6-related debugging messages. To generate them all, use the all keyword. To filter them by one part of the DHCPv6 functionality, use one of the other keywords.

1.30.5   Example

The following example shows how to generate debugging messages related to DHCPv6 exceptions:

[local]Redback#debug dhcpv6 exception

1.31   debug dot1q

1.31.1   Purpose

Enables the generation of debug messages for various types of 802.1Q permanent virtual circuit (PVC)-related events.

1.31.2   Command Mode

exec (10)

1.31.3   Syntax Description

1.31.4   Default

The generation of debug messages for all 802.1Q-related events is disabled. The default, if the generation of debug messages is enabled without any optional keywords, is to generate debug messages for all types of 802.1Q-related events.

1.31.5   Usage Guidelines

Use the debug dot1q command to enable the generation of debug messages for various types of 802.1Q-related 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 802.1Q events.

1.31.6   Examples

The following example shows how to enable the generation of debug messages for 802.1Q PVC events:

[local]Redback#debug dot1q pvc

1.32   debug ext-community-list

1.32.1   Purpose

Enables the generation of debug messages for the maintenance of extended community lists and for the comparison of Border Gateway Protocol (BGP) extended community attributes with extended community lists.

1.32.2   Command Mode

exec (10)

1.32.3   Syntax Description

1.32.4   Default

None

1.32.5   Usage Guidelines

Use the debug ext-community-list command to enable the generation of debug messages for the maintenance of extended community lists and for the comparison of BGP extended community attributes with extended community lists.

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.32.6   Examples

The following example shows how to enable the generation of debug messages for extended community lists:

[local]Redback#debug ext-community-list

1.33   debug frame-relay l2vpn

1.33.1   Purpose

Enables the generation of debug messages for Layer 2 Virtual Private Network (L2VPN)-enabled Frame Relay permanent virtual circuits (PVCs).

1.33.2   Command Mode

exec (10)

1.33.3   Syntax Description

1.33.4   Default

The generation of debug messages is disabled.

1.33.5   Usage Guidelines

Use the debug frame-relay l2vpn command to enable the generation of debug messages for L2VPN-enabled Frame Relay PVCs.

Note:  

The SmartEdge 100 router does not support Frame Relay PVCs.

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.

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 L2VPN-enabled Frame Relay debug messages.

1.33.6   Examples

The following example shows how to enable the generation of L2VPN-enabled Frame Relay debug messages:

[local]Redback#debug frame-relay l2vpn

1.34   debug frame-relay lmi

1.34.1   Purpose

Enables the generation of debug messages for all Frame Relay Local Management Interface (LMI) packet exchanges with a service provider.

1.34.2   Command Mode

exec (10)

1.34.3   Syntax Description

1.34.4   Default

The generation of debug messages is disabled for all Frame Relay LMI messages. The default, if the generation of debug messages is enabled without the optional slot, port, chan-num, and sub-chan-num arguments, is to generate debug messages for LMI packet messages for all Frame Relay ports in all slots.

1.34.5   Usage Guidelines

Use the debug frame-relay lmi command to enable the generation of debug messages for all Frame Relay LMI packet messages with a service provider.

Note:  

The SmartEdge 100 router does not support Frame Relay PVCs.

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.

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 LMI packet messages.

1.34.6   Examples

The following example shows how to enable the generation of debug messages for all Frame Relay LMI packet messages on channel 2 on port 1 of the channelized OC-12 traffic card in slot 3:

[local]Redback#debug frame-relay lmi 3/1:2

1.35   debug frame-relay packet

1.35.1   Purpose

Enables the generation of debug messages for Frame Relay Local Management Interface (LMI) packet messages, except those relating to LMI permanent virtual circuit (PVC) status.

1.35.2   Command Mode

exec (10)

1.35.3   Syntax Description

1.35.4   Default

The generation of debug messages for Frame Relay LMI packet messages, except for those related to LMI PVC status, is disabled.

1.35.5   Usage Guidelines

Use the debug frame-relay packet command to enable the generation of debug messages for Frame Relay LMI packet messages, except those relating to LMI PVC status, with the service provider. To enable the generation of debug messages for all Frame Relay LMI messages, including PVC status, use the debug frame-relay lmi command.

Note:  

The SmartEdge 100 router does not support Frame Relay PVCs.

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.

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 Frame Relay LMI packet messages.

1.35.6   Examples

The following example shows how to display typical debug messages when the generation of debug messages for Frame Relay LMI packet messages is enabled:

Aug 13 22:29:11: %FR-7-PKT: Port 3/1:4.31/6/2/30 (i) Packet length 14

Aug 13 22:29:11: %FR-7-PKT: Port 3/1:5.31/6/2/38 (i) Packet length 14

Aug 13 22:29:11: %FR-7-PKT: Port 3/1:6.31/6/2/46 (i) Packet length 14

Aug 13 22:29:13: %FR-7-PKT: Port 3/1:7.31/6/2/54 (o) Packet length 14

Aug 13 22:29:13: %FR-7-PKT: Port 3/1:8.31/6/2/62 (o) Packet length 14

Aug 13 22:29:13: %FR-7-PKT: Port 3/1:9.31/6/2/70 (o) Packet length 14

1.36   debug gre

1.36.1   Purpose

Enables the generation of debug messages for Generic Routing Encapsulation (GRE)-related events.

1.36.2   Command Mode

exec (10)

1.36.3   Syntax Description

1.36.4   Default

The generation of debug messages for GRE-related events is disabled.

1.36.5   Usage Guidelines

Use the debug gre command to enable the generation of debug messages for GRE-related 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.