COMMAND DESCRIPTION     6/190 82-CRA 119 1170/1-V1 Uen B    

Commands: debug m through debug z

© Ericsson AB 2009–2010. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List

SmartEdge is a registered trademark of Telefonaktiebolaget L M Ericsson.
NetOp is a trademark of Telefonaktiebolaget L M Ericsson.

Contents

1Command Descriptions
1.1debug mobile-ip
1.2debug mobile-ip agent-common
1.3debug mobile-ip authentication
1.4debug mobile-ip foreign-agent
1.5debug mobile-ip home-agent
1.6debug mobile-ip interaction
1.7debug mobile-ip packet
1.8debug mobile-ip packet-io
1.9debug msdp
1.10debug nat
1.11debug nd
1.12debug ntp
1.13debug ospf
1.14debug ospf bfd
1.15debug ospf flooding
1.16debug ospf interface
1.17debug ospf ldp-synchronization
1.18debug ospf lsdb
1.19debug ospf neighbor
1.20debug ospf packet
1.21debug ospf rcm
1.22debug ospf redistribution
1.23debug ospf rib
1.24debug ospf spf
1.25debug packet
1.26debug pedgr
1.27debug pim
1.28debug pim packet
1.29debug pim ppa
1.30debug pim rp-mapping
1.31debug pm
1.32debug policy access-list
1.33debug policy general
1.34debug ppp
1.35debug ppp multilink
1.36debug pppoe
1.37debug qos
1.38debug radius
1.39debug rcm
1.40debug rip
1.41debug route-map
1.42debug rsvp
1.43debug rsvp bfd
1.44debug shmlib
1.45debug snmp
1.46debug spanning-tree
1.47debug ssh
1.48debug static
1.49debug static dvsr
1.50debug subscriber
1.51debug sysmon ftp
1.52debug talk
1.53debug tap
1.54debug tunnel client
1.55debug vpls
1.56debug vrrp


1   Command Descriptions

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

1.1   debug mobile-ip

debug [{boot {active | standby} | switchover}] mobile-ip [all | event-types]

no debug [{boot {active | standby} | switchover}] mobile-ip [all | event-types]

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

boot

Optional. Limits the generation of debug messages to system reload events.

active

Enables the generation of debug messages to active controller card events.

standby

Enables the generation of debug messages to standby controller card events.

switchover

Optional. Limits the generation of debug messages to during a switchover from the active to the standby controller.

all

Enables the generation of debug messages for all Mobile IP events.

event types

Optional. Limits the generation of debug messages to the following Mobile IP event types:


  • agent-common—Limits the generation of debug messages to events common to both the HA and FA.

  • authentication—Limits the generation of debug messages for Mobile IP to authentication events.

  • foreign-agent—Limits the generation of debug messages for the FA instance events.

  • home-agent—Limits the generation of debug messages to HA instance events.

  • interaction—Limits the generation of debug messages for Mobile IP module interaction events, such as Router Configuration Manager (RCM) and Interface and Circuit State Manager (ISM) events.

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

  • packet-io—Limits the generation of debug messages on I/O packets events on a kernel socket interface for Mobile IP services.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug mobile-ip agent-common [instance | interface | internal | shared-memory | tunnel]

no 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

instance

Optional. Limits the generation of debug messages to Mobile IP instance events common to the HA and FA.

interface

Optional. Limits the generation of debug messages to Mobile IP access interface events.

internal

Optional. Limits the generation of debug messages to Mobile IP internal queue, time, and thread events.

shared-memory

Optional. Limits the generation of debug messages to Mobile IP shared memory events.

tunnel

Optional. Limits the generation of debug messages to Mobile IP tunnel creation and state events.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug mobile-ip authentication [aaa | fa-ha | mn-ha]

no 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

aaa

Optional. Limits the generation of debugging messages to authentication, authorization, and accounting (AAA) interface to Mobile IP.

fa-ha

Optional. Limits the generation of debugging messages between foreign-agent (FA) and home-agent (HA) authentication and security events.

mn-ha

Optional. Limits the generation of debugging messages between mobile node (MN) and HA authentication and security events.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug mobile-ip foreign-agent [visitor | core | home-agent-peer | care-of-address]

no 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

visitor

Optional. Limits the generation of debug messages to visitor events on this FA instance.

core

Optional. Limits the generation of debug messages to core FA instance events.

home-agent-peer

Optional. Limits the generation of debug messages to home-agent (HA) peer events of this FA instance.

care-of-address

Optional. Limits the generation of debug messages to care-of-address events of this FA instance.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug mobile-ip home-agent [binding | core | foreign-agent-peer | local-address]

no 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

binding

Optional. Limits the generation of debug messages to bindings.

core

Optional. Limits the generation of debug messages to core HA instance events.

foreign-agent-peer

Optional. Limits the generation of debug messages to foreign-agent (FA) peer events of this HA instance.

local-address

Optional. Limits the generation of debug messages to local address events for this HA instance for Mobile IP.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug mobile-ip interaction [configuration | ism | rcm | route]

no 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

configuration

Optional. Limits the generation of debug messages to Mobile IP configuration events.

ism

Optional. Limits the generation of debug messages to Mobile IP interaction with the Interface State (ISM) module.

rcm

Optional. Limits the generation of debug messages to Mobile IP interaction with the Router Configuration Manager (RCM) module.

route

Optional. Limits the generation of debug messages to Mobile IP interaction with the Router Information Base (RIB) module.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug [{boot {active | standby} | switchover}] mobile-ip packet [errors] [hex-dump] [send] [receive] [type packet-type] [source src-ip-addr] [destination dest-ip-addr] [circuit circuit-handle]

no debug [{boot {active | standby} | switchover}] mobile-ip packet [errors] [hex-dump] [send] [receive] [type packet-type] [source src-ip-addr] [destination dest-ip-addr] [circuit circuit-handle]

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

boot

Optional. Limits the generation of debug messages to system reload events.

active

Enables the generation of debug messages to active controller card events.

standby

Enables the generation of debug messages to standby controller card events.

switchover

Optional. Limits the generation of debug messages to events during a switchover from the active to the standby controller.

errors

Optional. Limits the generation of debug messages to Mobile IP packets with errors events.

send

Optional. Limits the generation of debug messages to transmitted Mobile IP packet events.

receive

Optional. Limits the generation of debug messages to received Mobile IP packet events.

type packet-type

Optional. Type of packet for which the generation of debug messages is limited to, according to one of the following keywords:


  • advertisement—Limits the generation of debug messages to Mobile IP advertisement packets.

  • reg-request—Limits the generation of debug messages to Mobile IP registration-request packets.

  • reg-reply—Limits the generation of debug messages to Mobile IP registration-reply packets.

  • reg-revocation—Limits the generation of debug messages to Mobile IP registration-revocation packets.

  • reg-revocation-ack—Limits the generation of debug messages to Mobile IP registration-revocation acknowledgement packets.

  • xid—Limits the generation of debug messages to logical link control (LLC) exchange ID (XID) packets.

hex-dump

Optional. Limits the generation of debug messages to a hexadecimal dump to the standard output.

source src-ip-addr

Optional. Limits the generation of debug messages to the source IP address.

destination dest-ip-addr

Optional. Limits the generation of debug messages to the destination IP address.

circuit circuit-handle

Optional. Limits the generation of debug messages to the circuit.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

debug mobile-ip packet-io [receive | send]

no 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

receive

Optional. Limits the generation of debugging messages to input packet events on a kernel socket interface for Mobile IP services.

send

Optional. Limits the generation of debugging messages to output packets events on a kernel socket interface for Mobile IP services.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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 msdp

debug [boot {active | standby} | switchover] msdp {all | peer [peer-addr] | sa-cache}

no debug [boot {active | standby} | switchover] msdp {all | peer [peer-addr] | sa-cache}

1.9.1   Purpose

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

1.9.2   Command Mode

exec (10)

1.9.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables all MSDP debug messages.

peer

Enables MSDP peer debug messages.

peer-addr

Optional. IP address of the MSDP peer.

sa-cache

Enables MSDP source active (SA) cache debug messages.

1.9.4   Default

The generation of debug messages is disabled.

1.9.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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.9.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.10   debug nat

debug [{boot {active | standby} | switchover}] nat {aaa | all | cli | config | ppa | rcm | work}

no debug [{boot {active | standby} | switchover}] nat {aaa | all | cli | config | ppa | rcm | work}

1.10.1   Purpose

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

1.10.2   Command Mode

exec (10)

1.10.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

aaa

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

all

Enables the generation of debug messages for all NAT events.

cli

Enables the generation of debug messages for NAT parser events.

config

Enables the generation of debug messages for NAT configuration events.

ppa

Enables the generation of debug messages for NAT Packet Processing ASIC (PPA) events.

rcm

Enables the generation of debug messages for NAT Router Configuration Manager (RCM) events.

work

Enables the generation of debug messages for NAT work orders.

1.10.4   Default

The generation of debug messages is disabled.

1.10.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of any debug messages on a production system.

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

1.10.6   Examples

The following example enables the generation of NAT debug messages:

[local]Redback#debug nat

1.11   debug nd

debug [boot {active | standby} | switchover] nd {all | circuit | config | dns | filter interface if-name | global | interface | ism | lc | packet [packet-type] [detail] | rib | subscriber| timer}

no debug [boot {active | standby} | switchover] nd {all | circuit | config | dns | filter interface if-name | global | interface | ism | lc | packet [packet-type] [detail] | rib | subscriber| timer}

1.11.1   Purpose

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

1.11.2   Command Mode

exec (10)

1.11.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Optional. Enables the generation of debug messages for all ND events.

circuit

Enables the generation of debug messages for ND circuit events.

config

Enables the generation of debug messages for ND configuration events.

dns

Enables the generation of debug messages for ND Domain Name System (DNS) events.

filter interface if-name

Name of the interface for which the generation of debug messages for ND interface events is enabled.

global

Optional. Enables the generation of debug messages for all ND packet, ISM, DNS, RIB, and timer events in all contexts.

interface

Enables the generation of debug messages for ND interface events.

ism

Enables the generation of debug messages for ND Interface and Circuit State Manager (ISM) events.

lc

Enables the generation of debug messages for ND traffic card events.

packet

Enables the generation of debug messages for ND packet events.

packet-type

Optional. ND packet type, according to one of the keywords listed in Table 1. If this argument is not specified, the packet keyword enables the generation of debug messages for all packet types.

detail

Optional. Includes an ND packet dump for ND packet events.

rib

Enables the generation of debug messages for ND Routing Information Base (RIB) events.

subscriber

Enables the generation of debug messages for events related to ND subscriber circuits and ND profiles.

timer

Enables the generation of debug messages for ND timer events.

1.11.4   Default

The generation of debug messages for ND events is disabled.

1.11.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

Table 1    ND Packet Types

Keyword

Packet Type

na

ND neighbor advertisement packets

ns

ND neighbor solicitation packets

ra

ND neighbor router advertisement packets

redirect

ND neighbor redirect packets

rs

ND neighbor router solicitation packets

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.11.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.12   debug ntp

debug [boot {active | standby} | switchover] ntp {all | general | packet | update}

no debug [boot {active | standby} | switchover] ntp {all | general | packet | update}

1.12.1   Purpose

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

1.12.2   Command Mode

exec (10)

1.12.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables the generation of debug messages for all NTP messages.

general

Enables the generation of debug messages for NTP general messages.

packet

Enables the generation of debug messages for NTP packet messages.

update

Enables the generation of debug messages for NTP time update messages.

1.12.4   Default

The generation of debug messages for NTP is disabled.

1.12.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

1.12.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.13   debug ospf

debug [boot {active | standby} | switchover] ospf

no debug [boot {active | standby} | switchover] ospf

1.13.1   Purpose

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

1.13.2   Command Mode

exec (10)

1.13.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.13.4   Default

The generation of debug messages is disabled.

1.13.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 OSPF events:

[local]Redback#debug ospf

1.14   debug ospf bfd

debug ospf bfd

no debug ospf bfd

1.14.1   Purpose

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

1.14.2   Command Mode

exec (10)

1.14.3   Syntax Description

This command has no keywords or arguments.

1.14.4   Default

The generation of debug messages is disabled.

1.14.5   Usage Guidelines

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


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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 BFD debug messages for all OSPF instances:

[local]Redback#debug opsf bfd

1.15   debug ospf flooding

debug [boot {active | standby} | switchover] ospf flooding

no debug [boot {active | standby} | switchover] ospf flooding

1.15.1   Purpose

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

1.15.2   Command Mode

exec (10)

1.15.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.15.4   Default

The generation of debug messages is disabled.

1.15.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 debug messages for OSPF flooding events:

[local]Redback#debug ospf flooding

1.16   debug ospf interface

debug [boot {active | standby} | switchover] ospf interface address ip-addr

no debug [boot {active | standby} | switchover] ospf interface address ip-addr

1.16.1   Purpose

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

1.16.2   Command Mode

exec (10)

1.16.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

address ip-addr

Interface IP address. Enables the generation of debug messages for the interface using the specified IP address.

1.16.4   Default

The generation of debug messages is disabled.

1.16.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 events for the OSPF interface at IP address 10.10.1.1:

[local]Redback#debug ospf interface 10.10.1.1

1.17   debug ospf ldp-synchronization

debug ospf ldp-synchronization

no debug ospf ldp-synchronization

1.17.1   Purpose

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

1.17.2   Command Mode

exec (10)

1.17.3   Syntax Description

This command has no keywords or arguments.

1.17.4   Default

The generation of debug messages is disabled.

1.17.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.17.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.18   debug ospf lsdb

debug [boot {active | standby} | switchover] ospf lsdb [area-scope-opaque | as-scope-opaque | external | link-scope-opaque | network | nssa | router | summary-asbr | summary-network] [advertising-router ip-addr] [link-state-id ip-addr]

no debug [boot {active | standby} | switchover] ospf lsdb [area-scope-opaque | as-scope-opaque | external | link-scope-opaque | network | nssa | router | summary-asbr | summary-network] [advertising router ip-addr] [link-state-id ip-addr]

1.18.1   Purpose

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

1.18.2   Command Mode

exec (10)

1.18.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

area-scope-opaque

Optional. Enables the generation of debug messages for area scoped opaque LSDB events only.

as-scope-opaque

Optional. Enables the generation of debug messages for AS scoped opaque LSDB events only.

external

Optional. Enables the generation of debug messages for external LSDB events only.

link-scope-opaque

Optional. Enables the generation of debug messages for link scoped opaque LSDB events only.

network

Optional. Enables the generation of debug messages for network LSDB event only.

nssa

Optional. Enables the generation of debug messages for not-so-stubby-area (NSSA) events only.

router

Optional. Enables the generation of debug messages for router events only.

summary-asbr

Optional. Enables the generation of debug messages for summaries of autonomous system boundary router (ASBR) events only.

summary-network

Optional. Enables the generation of debug messages for summaries of area border router (ABR) events only.

advertising-router ip-addr

Optional. Advertising router IP address. Enables the generation of debug messages for the specified IP address only.

link-state-id ip-addr

Optional. Link-state ID address. Enables the generation of debug messages for the specified IP address only.

1.18.4   Default

The generation of debug messages is disabled.

1.18.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 enables the generation of debug messages for all OSPF LSDB events:

[local]Redback#debug ospf lsdb

1.19   debug ospf neighbor

debug [boot {active | standby} | switchover] ospf neighbor [neighbor-id ip-addr]

no debug [boot {active | standby} | switchover] ospf neighbor [neighbor-id ip-addr]

1.19.1   Purpose

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

1.19.2   Command Mode

exec (10)

1.19.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

neighbor-id ip-addr

Optional. Neighbor ID. Enables the generation of debug messages for the specified neighbor only.

1.19.4   Default

The generation of debug messages is disabled.

1.19.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 only the OSPF neighbor at IP address 43.23.45.8:

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

1.20   debug ospf packet

debug [boot {active | standby} | switchover] ospf packet [ack | database | errors | hello | request | update] [send | recv] [destination ip-addr | source ip-addr]

no debug [boot {active | standby} | switchover] ospf packet [ack | database | errors | hello | request | update] [send | recv] [destination ip-addr | source ip-addr]

1.20.1   Purpose

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

1.20.2   Command Mode

exec (10)

1.20.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

ack

Optional. Enables the generation of debug messages for acknowledgement (ack) packets only.

database

Optional. Enables the generation of debug messages for database description packets only.

errors

Optional. Enables the generation of debug messages for packet errors only.

hello

Optional. Enables the generation of debug messages for Hello packets only.

request

Optional. Enables the generation of debug messages for link-state request packets only.

update

Optional. Enables the generation of debug messages for link-state update packets only.

send

Optional. Enables the generation of debug messages for sent packets only.

recv

Optional. Enables the generation of debug messages for received packets only.

destination ip-addr

Optional. Destination IP address. Enables the generation of debug messages for packets sent to the specified IP address only.

source ip-addr

Optional. Source IP address. Enables the generation of debug messages for packets coming from the specified IP address only.

1.20.4   Default

The generation of debug messages is disabled.

1.20.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 OSPF Hello packet events:

[local]Redback#debug ospf packet hello

1.21   debug ospf rcm

debug [boot {active | standby} | switchover] ospf rcm

no debug [boot {active | standby} | switchover] ospf rcm

1.21.1   Purpose

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

1.21.2   Command Mode

exec (10)

1.21.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.21.4   Default

The generation of debug messages is disabled.

1.21.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 RCM events:

[local]Redback#debug ospf rcm

1.22   debug ospf redistribution

debug [boot {active | standby} | switchover] ospf redistribution [instance instance-id]

no debug [boot {active | standby} | switchover] ospf redistribution [instance instance-id]

1.22.1   Purpose

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

1.22.2   Command Mode

exec (10)

1.22.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

instance instance-id

Optional. OSPF instance ID. The range of values is 1 to 65,535. Enables the generation of debug messages for the specified OSPF instance only.

1.22.4   Default

The generation of debug messages is disabled.

1.22.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 redistribution events pertaining to OSPF instance 64001:

[local]Redback#debug ospf redistribution instance 64001

1.23   debug ospf rib

debug [boot {active | standby} | switchover] ospf rib [area area-id] [instance instance-id] [route-type {external | inter-area | intra-area}]

no debug [boot {active | standby} | switchover] ospf rib [area area-id] [instance instance-id] [route-type {external | inter-area | intra-area}]

1.23.1   Purpose

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

1.23.2   Command Mode

exec (10)

1.23.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

area area-id

Optional. Area ID. Enables the generation of debug messages for only the specified area.

instance instance-id

Optional. OSPF instance ID. The range of values is 1 to 65,535. Enables the generation of debug messages for only the specified instance.

route-type

Optional. Enables the generation of debug messages for the specified route type.

external

Enables the generation of debug messages for external OSPF routes.

inter-area

Enables the generation of debug messages for interarea OSPF routes.

intra-area

Enables the generation of debug messages for intra-area OSPF routes.

1.23.4   Default

The generation of debug messages is disabled.

1.23.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 debug messages for OSPF RIB events for external routes:

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

1.24   debug ospf spf

debug [boot {active | standby} | switchover] ospf spf [externals | incremental | intra-area | nssa | scheduling | summaries | virtual-links] [area area-id] [instance instance-id]

no debug [boot {active | standby} | switchover] ospf spf [externals | incremental | intra-area | nssa | scheduling | summaries | virtual-links] [area area-id] [instance instance-id]

1.24.1   Purpose

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

1.24.2   Command Mode

exec (10)

1.24.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

externals

Optional. Enables the generation of debug messages for external computations.

incremental

Optional. Enables the generation of debug messages for incremental computations.

intra-area

Optional. Enables the generation of debug messages for intra-area path computations.

nssa

Optional. Enables the generation of debug messages for not-so-stubby-area (NSSA) computations.

scheduling

Optional. Enables the generation of debug messages for SPF scheduling and triggering.

summaries

Optional. Enables the generation of debug messages for summary computations.

virtual-links

Optional. Enables the generation of debug messages for virtual links.

area area-id

Optional. Enables the generation of debug messages for all areas or for the specified area.

instance instance-id

Optional. Enables the generation of debug messages for all instances or for the specified instance.

1.24.4   Default

The generation of debug messages is disabled.

1.24.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 the generation of debug messages for OSPF SPF calculations:

[local]Redback#debug ospf spf

1.25   debug packet

For circuits specified by link groups, the syntax is:

debug packet circuit lg {lg-name | id lg-id} [circuit-id] {in | out} [countnumber of packets] [sample-intervalsample-interval-in-msec] [size packet-size-in-bytes | header-only] [ip aclacl-name [contextacl-context]]

no debug packet circuit lg {lg-name | id lg-id} [circuit-id] {in | out} [count number of packets] [sample-interval sample-interval-in-msec] [size packet-size-in-bytes | header-only] [ip acl acl-name [context acl-context]]

no debug packet all

For circuits specified by slot and port, the syntax is:

debug packet circuit {slot/port} [circuit-id] {in | out} [count number of packets] [sample-interval sample-interval-in-msec] [size packet-size-in-bytes | header-only] [ip acl acl-name [context acl-context]]

no debug packet circuit {slot/port} [circuit-id] {in | out} [count number of packets] [sample-interval sample-interval-in-msec] [size packet-size-in-bytes | header-only] [ip acl acl-name [context acl-context]]

no debug packet all

1.25.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.25.2   Command Mode

exec (10)

1.25.3   Syntax Description

circuit

Specifies the circuit to monitor.

lg lg-name

Specifies the name of the link group for which the generation of debug messages is enabled.

id lg-id

Specifies the ID of the link group for which the generation of debug messages is enabled.

slot

Chassis slot number of the traffic card for which the generation of debug messages is enabled.

port

Required if you enter the slot argument. Port number for which the generation of debug messages is enabled.

circuit-id

Circuit identifier according to one of the constructs listed in Table 2 for which the generation of debug messages is enabled.

in

Specifies that the debugging of packets is to apply only to incoming traffic on the circuit.

out

Specifies that the debugging of packets is to apply only to outgoing traffic on the circuit.

count number of packets

Specifies the number of consecutive packets to display. The range of values is from 1 to 1000.

sample-interval sample-interval-in-msec

Specifies a minimum interval between packet samples in milliseconds. The range of values is from 1 to 20000.

size packet-size-in-bytes

Specifies the number of bytes from the beginning of a packet to display. The range of values is from 1 to 160.

header-only

Specifies that only packet headers are to be displayed.

ip acl acl-name

Specifies the name of the IP ACL to be used to filter packets for debugging.

context acl-context

Specifies the name of the context in which the specified IP ACL resides.

all

Applies only to the no form of the debug packet command. Cancels the generation of debug messages for all circuits in both directions of the current CLI session.

1.25.4   Default

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

1.25.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:

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

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.

Table 2    Values for the circuit-id Argument

Construct

Description

pppoe sess-id

Specifies a PPPoE circuit. The range of values for the sess-id argument is from 1 to 65534.

vlan-id vlan-id

Specifies the VLAN tag value for an 802.1Q tunnel or PVC. The vlan-id argument is one of the following arguments:


  • pvc-vlan-id—VLAN tag value of a PVC that is not within an 802.1Q tunnel.

  • tunl-vlan-id—VLAN tag value of a tunnel.

  • tunl-vlan-id:pvc-vlan-id—VLAN tag value for the tunnel followed by the VLAN tag value for the PVC within the tunnel.


The range of values for either VLAN tag value is 1 to 4095.

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.25.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.26   debug pedgr

debug [{boot {active | standby} | switchover}] pedgr

no debug [{boot {active | standby} | switchover}] pedgr

1.26.1   Purpose

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

1.26.2   Command Mode

exec (10)

1.26.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.26.4   Default

The generation of debug messages for PEDGR events is disabled.

1.26.5   Usage Guidelines

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


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

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

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

[local]Redback#debug pedgr

1.27   debug pim

debug [boot {active | standby} | switchover] pim [group-addr]

no debug [boot {active | standby} | switchover] pim [group-addr]

1.27.1   Purpose

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

1.27.2   Command Mode

exec (10)

1.27.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

group-addr

Optional. IP address of the Internet Group Management Protocol (IGMP) group.

1.27.4   Default

The generation of debug messages is disabled.

1.27.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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.27.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.28   debug pim packet

debug [boot {active | standby} | switchover] pim packet [group-addr]

no debug [boot {active | standby} | switchover] pim packet [group-addr]

1.28.1   Purpose

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

1.28.2   Command Mode

exec (10)

1.28.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

group-addr

Optional. IP address of the Internet Group Management Protocol (IGMP) group.

1.28.4   Default

The generation of debug messages is disabled.

1.28.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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.28.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.29   debug pim ppa

debug [boot {active | standby} | switchover] pim ppa [slot-num [group-addr] | group-addr]

no debug [boot {active | standby} | switchover] pim ppa

1.29.1   Purpose

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

1.29.2   Command Mode

exec (10)

1.29.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

slot-num

Optional. Slot number.

group-addr

Optional. IP address of the Internet Group Management Protocol (IGMP) group.

1.29.4   Default

The generation of debug messages is disabled.

1.29.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

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

[local]Redback#debug pim ppa

1.30   debug pim rp-mapping

debug [boot {active | standby} | switchover] pim rp-mapping

no debug [boot {active | standby} | switchover] pim rp-mapping

1.30.1   Purpose

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

1.30.2   Command Mode

exec (10)

1.30.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.30.4   Default

The generation of debug messages is disabled.

1.30.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

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

[local]Redback#debug pim rp-mapping

1.31   debug pm

debug [{boot {active | standby} | switchover}] pm [{all | config | general | ipc | memory-error | process}]

no debug [{boot {active | standby} | switchover}] pm [{all | config | general | ipc | memory-error | process}]

1.31.1   Purpose

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

1.31.2   Command Mode

exec (10)

1.31.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Optional. Enables debug messages for all PM events.

config

Optional. Enables debug messages for PM configuration events.

general

Optional. Enables debug messages for general PM events.

ipc

Optional. Enables debug messages for interprocess communication (IPC) PM events.

memory-error

Optional. Enables debug messages for PM memory-error events.

process

Optional. Enables debug messages for PM process events.

1.31.4   Default

The generation of debug messages for the PM is disabled.

1.31.5   Usage Guidelines

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


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

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

The following example enables PM memory-error events:

[local]Redback#debug pm memory-error

1.32   debug policy access-list

debug [{boot {active | standby} | switchover}] policy access-list

no debug [{boot {active | standby} | switchover}] policy access-list

1.32.1   Purpose

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

1.32.2   Command Mode

exec (10)

1.32.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.32.4   Default

The generation of debug messages is disabled.

1.32.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of any debug messages on a production system.

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

1.32.6   Examples

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

[local]Redback#debug policy access-list

1.33   debug policy general

debug [boot {active | standby} | switchover] policy general

no debug [boot {active | standby} | switchover] policy general

1.33.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.33.2   Command Mode

exec (10)

1.33.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.33.4   Default

None

1.33.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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 the generation of debug messages for all configured routing policies:

[local]Redback#debug policy general

1.34   debug ppp

debug [boot {active | standby} | switchover] ppp {all | event-type}

no debug [boot {active | standby} | switchover] ppp {all | event-type}

1.34.1   Purpose

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

1.34.2   Command Mode

exec (10)

1.34.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.


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

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card and enable debug messages while the system is switching from the active to the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables the generation of debug messages for all PPP event types.

event-type

Type of event, according to one of the keywords listed in Table 3.

1.34.4   Default

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

1.34.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.

Table 3    Event Types

Keyword

Description

authentication

Password Authentication Protocol (PAP)/Challenge Handshake Authentication Protocol (CHAP) authentication events

circuit

Circuit-related events

config

Configuration-related events

down

PPP session down-related events

exception

Exception events, such as when a timer expires

fsm

State-change events for the Finite State Machine (FSM)

ipc

Interprocess communication (IPC)-related events

ipcp

Internet Protocol Control Protocol (IPCP) events

ism

Interface and Circuit State Manager (ISM)-related events

lcp

Link Control Protocol (LCP) events

multilink

PPP multilink events

negotiation

Negotiation events

nlcp

Network Link Control Protocol (NLCP) events

packet

PPP packet events

phase

PPP phase events

ppa

Packet Processing ASIC (PPA)-related events

rcm

Router Configuration Manager (RCM)-related events

session

PPP session-related events

timer

PPP timer-related events


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

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

[local]Redback#debug ppp packet

1.35   debug ppp multilink

debug [boot {active | standby} | switchover] ppp multilink

no debug [boot {active | standby} | switchover] ppp multilink

1.35.1   Purpose

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

1.35.2   Command Mode

exec (10)

1.35.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.35.4   Default

The generation of debug messages for MP events is disabled.

1.35.5   Usage Guidelines

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


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of any debug messages on a production system.

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

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

[local]Redback#debug ppp multilink

1.36   debug pppoe

debug [boot {active | standby} | switchover] pppoe {all | cct | discovery | exception | info | packet | timer}

no debug [boot {active | standby} | switchover] pppoe {all | cct | discovery | exception | info | packet | timer}

1.36.1   Purpose

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

1.36.2   Command Mode

exec (10)

1.36.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables the generation of PPPoE debug messages for all types of events.

cct

Enables the generation of PPPoE debug messages for circuit-related events.

discovery

Enables the generation of PPPoE debug messages for discovery protocol-related events.

exception

Enables the generation of PPPoE exception debug messages.

info

Enables the generation of PPPoE debug messages for PPPoE information.

packet

Enables the generation of PPPoE debug messages for packet input and output events.

timer

Displays timer-related debug messages.

1.36.4   Default

Debugging is disabled.

1.36.5   Usage Guidelines

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


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of any debug messages on a production system.

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.36.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.37   debug qos

debug [{boot {active | standby} | switchover}] qos {all | cli | config | internal | ism | ppa | rcm}

no debug [{boot {active | standby} | switchover}] qos {all | cli | config | internal | ism | ppa | rcm}

1.37.1   Purpose

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

1.37.2   Command Mode

exec (10)

1.37.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables the generation of debug messages for all QoS events.

cli

Enables the generation of debug messages for QoS parser events.

config

Enables the generation of debug messages for QoS daemon configuration events.

internal

Enables the generation of debug messages for QoS internal events.

ism

Enables the generation of debug messages for QoS Interface and Circuit State Manager (ISM) events.

ppa

Enables the generation of debug messages for QoS Packet Processing ASIC (PPA) events.

rcm

Enables the generation of debug messages for QoS Router Configuration Manager (RCM) events.

1.37.4   Default

The generation of debug messages is disabled.

1.37.5   Usage Guidelines

Use the debug qos command to enable the generation of QoS 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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of any debug messages on a production system.

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

1.37.6   Examples

The following example enables the generation of QoS PPA event debug messages:

[local]Redback#debug qos ppa

1.38   debug radius

debug [{boot {active | standby} | switchover}] radius {accounting | attributes | authentication | authorization | packet}

no debug [{boot {active | standby} | switchover}] radius {accounting | attributes | authentication | authorization | packet}

1.38.1   Purpose

Enables the generation of Remote Authentication Dial-In User Service (RADIUS) debug messages.

1.38.2   Command Mode

exec (10)

1.38.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

accounting

Enables the generation of RADIUS accounting debug messages.

attributes

Enables the generation of RADIUS attribute debug messages.

authentication

Enables the generation of RADIUS authentication debug messages.

authorization

Enables the generation of RADIUS authorization debug messages.

packet

Enables the generation of RADIUS packet-level debug messages.

1.38.4   Default

The generation of debug messages is disabled.

1.38.5   Usage Guidelines

Use the debug radius command to enable the generation of RADIUS debug messages.

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


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

1.38.6   Examples

The following example enables the generation of packet-level debug messages for RADIUS:

[local]Redback#debug radius packet

The following example enables the generation of RADIUS authentication debug messages:

[local]Redback#debug radius authentication

The following example disables the generation of RADIUS authentication debug messages:

[local]Redback#no debug radius authentication

1.39   debug rcm

debug [{boot {active | standby} | switchover}] rcm[event]

no debug [{boot {active | standby} | switchover}] rcm [event]

1.39.1   Purpose

Enables the generation of debug messages for the Router Configuration Manager (RCM).

1.39.2   Command Mode

exec (10)

1.39.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

event

Optional. Enables debugging messages for only RCM events.

1.39.4   Default

The generation of debug messages for the RCM is disabled.

1.39.5   Usage Guidelines

Use the debug rcm command to enable the generation of debug messages for the RCM.


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

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.

Use the optional event keyword to enable the debug messages for only RCM 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.

1.39.6   Examples

The following example enables debugging messages for only RCM events:

[local]Redback#debug rcm event

1.40   debug rip

debug [boot {active | standby} | switchover] rip {all | config | global-rib | interface | packet [recv | request | response | send] | policy | route | timer} [detail]

no debug [boot {active | standby} | switchover] rip {all | config | global-rib | interface | packet [recv | request | response | send] | policy | route | timer} [detail]

1.40.1   Purpose

Enables the generation of Routing Information Protocol (RIP) debug messages.

1.40.2   Command Mode

exec (10)

1.40.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables the generation of messages for all RIP debug options.

config

Enables the generation of debug messages for RIP configuration events.

global-rib

Enables the generation of debug messages for global Routing Information Base (RIB) events.

interface

Enables the generation of debug messages for RIP interface events.

packet

Enables the generation of debug messages for all RIP packet events.

recv

Optional. Enables the generation of debug messages for only received RIP packets.

request

Optional. Enables the generation of debug messages for only request packets.

response

Optional. Enables the generation of debug messages for only response packets.

send

Optional. Enables the generation of debug messages for only send packets.

policy

Enables the generation of debug messages for RIP policy events.

route

Enables the generation of debug messages for RIP routing table events.

timer

Enables the generation of debug messages for RIP timer events.

detail

Optional. Provides detailed information in debug messages.

1.40.4   Default

The generation of debug messages is disabled.

1.40.5   Usage Guidelines

Use the debug rip command to enable the generation of RIP 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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

1.40.6   Examples

The following example enables the generation of debug messages for all RIP packet events:

[local]Redback#debug rip packet all 

1.41   debug route-map

debug [boot {active | standby} | switchover] route-map

no debug [boot {active | standby} | switchover] route-map

1.41.1   Purpose

Enables the generation of debug messages for the maintenance of route maps and for the comparison of routes to route maps.

1.41.2   Command Mode

exec (10)

1.41.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.41.4   Default

None

1.41.5   Usage Guidelines

Use the debug route-map command to enable the generation of debug messages for the maintenance of route maps and for the comparison of routes to 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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

The following example enables the generation of debug messages for route maps:

[local]Redback#debug route-map

1.42   debug rsvp

debug [boot {active | standby} | switchover] rsvp [auth | cfg | errors | frr | interface [address ip-addr] | io | ism | label | lm | nbr | nhop | packet [recv [packet-type] | send [packet-type]] | path | ping | psb | qos | rib | rsb | session | state-changes | timers]

no debug [boot {active | standby} | switchover] rsvp [auth | cfg | frr | errors | interface [address ip-addr] | io | ism | label | lm | nbr | nhop | packet [recv [packet-type] | send [packet-type]] | path | ping | psb | qos | rib | rsb | session | state-changes | timers]

1.42.1   Purpose

Enables the generation of debug messages for Resource Reservation Protocol (RSVP) activities.

1.42.2   Command Mode

exec (10)

1.42.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

auth

Optional. Enables the generation of authentication debug messages.

cfg

Optional. Enables the generation of configuration event debug messages.

errors

Optional. Enables the generation of protocol error debug messages.

frr

Optional. Enables the generation of fast reroute event debug messages.

interface

Optional. Enables the generation of interface event debug messages.

address ip-addr

Optional. IP address for the specific interface to be debugged.

io

Optional. Enables the generation of packet I/O debug messages.

ism

Optional. Enables the generation of Interface And Circuit State Manager (ISM) event debug messages.

label

Optional. Enables the generation of label operation debug messages.

lm

Optional. Enables the generation of label manager debug messages.

nbr

Optional. Enables the generation of neighbor event debug messages.

nhop

Optional. Enables the generation of next-hop event debug messages.

packet

Optional. Enables the generation of packet debug messages.

recv

Optional. Enables the generation of packet reception debug messages.

packet-type

  • path-err—Specifies path-error packets.

  • path-tear—Specifies path-tear packets.

  • resv—Specifies reservation packets.

  • resv-err—Specifies reservation error packets.

  • resv-tear—Specifies reservation tear packet.

send

Optional. Enables the generation of packet transmission debug messages.

path

Optional. Enables the generation of label-switched path (LSP) origination debug messages.

ping

Optional. Enables the generation of RSVP LSP ping event debug messages.

psb

Optional. Enables the generation of path state block (PSB) event debug messages.

qos

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

rib

Optional. Enables the generation of Routing Information Base (RIB) event debug messages.

rsb

Optional. Enables the generation of Reservation State Block (RSB) event debug messages.

session

Optional. Enables the generation of session event debug messages.

state-changes

Optional. Enables the generation of LSP state change debug messages.

timers

Optional. Enables the generation of timer events debug messages.

1.42.4   Default

The generation of debug messages is disabled.

1.42.5   Usage Guidelines

Use the debug rsvp command to enable the generation of debug messages for RSVP activities.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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 RSVP activities.

1.42.6   Examples

The following example enables the generation of debug messages for all RSVP activities:

[local]Redback#debug rsvp

1.43   debug rsvp bfd

debug rsvp bfd

no debug rsvp bfd

1.43.1   Purpose

Enables the generation of event debug messages for Resource Reservation Protocol (RSVP) Bidirectional Forwarding Detection (BFD).

1.43.2   Command Mode

exec (10)

1.43.3   Syntax Description

This command has no keywords or arguments.

1.43.4   Default

The generation of debug messages is disabled.

1.43.5   Usage Guidelines

Use the debug rsvp bfd command to enable the generation of event debug messages for RSVP BFD.

Use the no form of this command to disable the generation of event debug messages for RSVP BFD.

1.43.6   Examples

The following example enables the generation of event debug messages for RSVP BFD:

[local]Redback#debug rsvp bfd

1.44   debug shmlib

debug [{boot {active | standby} | switchover}] shmlib

no debug [{boot {active | standby} | switchover}] shmlib

1.44.1   Purpose

Enables the generation of debug messages for the shared memory library.

1.44.2   Command Mode

exec (10)

1.44.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.44.4   Default

The generation of debug messages for the shared memory library is disabled.

1.44.5   Usage Guidelines

Use the debug shmlib command to enable the generation of debug messages for the shared memory library.


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

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

The following example enables the generation of debug messages for shared memory library events:

[local]Redback#debug shmlib

1.45   debug snmp

debug [{boot {active | standby} | switchover}] snmp {all | general | mib mib-description | packet | pdu {notify | request}}

no debug [{boot {active | standby} | switchover}] snmp {all | general | mib mib-description | packet | pdu}

1.45.1   Purpose

Enables the generation of Simple Network Management Protocol (SNMP) debug messages.

1.45.2   Command Mode

exec (10)

1.45.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

mib mib-description

Optional. Enables the generation of debug messages for an SNMP MIB you identify using the mib-description argument. The value of the mib-description argument can be any one of the keywords listed in the Usage Guidelines.

all

Enables the generation of debug messages for all SNMP events.

general

Enables the generation of debug messages for general SNMP events.

packet

Enables the generation of debug messages for SNMP packets.

pdu

Enables the generation of debug messages for the protocol data unit (PDU) field in SNMP packets.

1.45.4   Default

The generation of debug messages for SNMP is disabled.

1.45.5   Usage Guidelines

Use the debug snmp command to enable the generation of SNMP debug messages.


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

Table 4 lists the keywords to use to enable debugging for specific MIBs supported by this command.

Table 4    Keywords for MIB Descriptions

Keyword

MIB Description

alarm

Display debugging messages for ALARM-MIB

all

Display debugging messages for all MIBs

aps

Display debugging messages for APS-MIB

atm

Display debugging messages for ATM-MIB

bgp

Display debugging messages for BGP-MIB

bind

Display debugging messages for RBN-BIND-MIB

bpa

Display debugging messages for BGP policy-based accounting MIB

bridge

Display debugging messages for BRIDGE-MIB

bulkstats

Display debugging messages for RBN-BULKSTATS-MIB

cardmon

Display debugging messages for RBN-CARDMON-MIB

cellpw

Display debugging messages for RBN-ATM-CELL-PW-MIB

cfgfile

Display debugging messages for RBN-CONFIG-FILE-MIB

circuitGroup

Display debugging messages for RBN-CIRCUIT-GROUP-MIB

cpumeter

Display debugging messages for RBN-CPU-METER-MIB

dhcp

Display debugging messages for RBN-DHCP-MIB

ds1

Display debugging messages for DS1-MIB

ds3

Display debugging messages for RBN-BULKSTATS-MIB

entity

Display debugging messages for ENTITY-MIB

envmon

Display debugging messages for RBN-ENVMON-MIB

etherwis

Display debugging messages for Ether-WIS-MIB

fr

Display debugging messages for FRAME-RELAY-DTE-MIB

if

Display debugging messages for IF-MIB

ip

Display debugging messages for IP-MIB

ipbind

Display debugging messages for RBN-IP-BIND-MIB

ipf

Display debugging messages for IP-FORWARD-MIB

ippool

Display debugging messages for RBN-IPPOOL-MIB

l2tp

Display debugging messages for RBN-L2TP-MIB

mau

Display debugging messages for MAU-MIB

memory

Display debugging messages for RBN-MEMORY-MIB

ne

Display debugging messages for RBN-NOTIFY-ENHANCE-MIB

ospf

Display debugging messages for OSPF-MIB

pvc

Display debugging messages for RBN-PVC-MIB

qos

Display debugging messages for RBN-QOS-MIB

radius

Display debugging messages for RBN-RADIUS-MIB

rmon

Display debugging messages for RMON-MIBs

sonet

Display debugging messages for SONET-MIBs

sr

Display debugging messages for RBN-SYS-RESOURCES-MIBs

subscriber

Display debugging messages for RBN-SUBSCRIBER-ACTIVE-MIBs

tacacs

Display debugging messages for RBN-TACACS-MIBs

tcp

Display debugging messages for TCP-MIB

udp

Display debugging messages for UDP-MIB

vrrp

Display debugging messages for VRRP-MIB and RBN-FAST-VRRP-MIB

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

1.45.6   Examples

The following example displays all categories of debug information for SNMP and enables the SNMP server:

[local]Redback#debug snmp all

[local]Redback#config

[local]Redback(config)#snmp server

[local]Redback(config)#exit

[local]Redback#
Jun 26 11:06:29: %SNMP-7-GEN: snmp process is ALIVE

Jun 26 11:06:29: %SNMP-7-GEN: snmp ready to receive packets

1.46   debug spanning-tree

debug [{boot {active | standby} | switchover}] spanning-tree {all | config | packet-arg | packet-io-arg | rcm | timers}

no debug [{boot {active | standby} | switchover}] spanning-tree {all | config | packet-arg | packet-io-arg | rcm | timers}

1.46.1   Purpose

Enables the generation of debug messages for the Rapid Spanning Tree Protocol (RSTP).

1.46.2   Command Mode

exec (10)

1.46.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Generates all debug messages related to RSTP.

config

Generates debug messages related to RSTP configuration events.

packet-arg

Generates debug messages related to the received and transmitted RSTP packets.


The syntax for the packet-arg argument is:


packet [receive | send] [hex-dump | verbose] [type {cfg | mstp | rstp | tcn}] [trace]

packet-io-arg

Generates debug messages related to RSTP packet input/output flow.


The syntax for the packet-io-arg argument is:


packet-io [receive | send] [hex-dump]

rcm

Generates debug messages for RSTP Router Configuration Manager (RCM) events.

timers

Generates debug messages related to RSTP timers.

1.46.4   Default

The generation of debug messages for RSTP is disabled.

1.46.5   Usage Guidelines

Use the debug spanning-tree command to enable generation of debug messages for RSTP.


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

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 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 RSTP.

1.46.6   Examples

The following example enables the generation of detailed debug messages for RSTP:

[local]Redback#debug spanning-tree

1.47   debug ssh

debug [{boot {active | standby} | switchover}] ssh {all | ssh-general | sshd-detail | sshd-general}

no debug [{boot {active | standby} | switchover}] ssh {all | ssh-general | sshd-detail | sshd-general}

1.47.1   Purpose

Enables the generation of debug messages for Secure Shell (SSH).

1.47.2   Command Mode

exec (10)

1.47.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Generates all debug messages related to SSH.

ssh-general

Generates general debug messages related to SSH.

sshd-detail

Generates detailed daemon (server) debug messages related to SSH.

sshd-general

Generates general daemon (server) debug messages related to SSH.

1.47.4   Default

The generation of debug messages for SSH is disabled.

1.47.5   Usage Guidelines

Use the debug ssh command to generate debug messages for the SSH.


 Caution! 
Risk of performance loss. Enabling debug messages can severely affect system performance. To reduce the risk, use debug commands only when necessary and for as short a time as possible.

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 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 SSH.

1.47.6   Examples

The following example enables the generation of detailed debug messages for SSH:

[local]Redback#debug sshd-detail

1.48   debug static

debug [boot {active | standby} | switchover] static {all | config | ism | rib}

no debug [boot {active | standby} | switchover] static {all | config | ism | rib}

1.48.1   Purpose

Enables the generation of debug messages for static IP routes.

1.48.2   Command Mode

exec (10)

1.48.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

all

Enables the generation of all debug message options for static IP routes.

config

Enables the generation of debug messages for the IP static route configuration.

ism

Enables the generation of debug messages for interactions between static IP routes and the Interface State and Circuit Manager (ISM).

rib

Enables the generation of debug messages for interactions between static IP routes and the Routing Information Base (RIB).

1.48.4   Default

The generation of debug messages is disabled.

1.48.5   Usage Guidelines

Use the debug static command to enable the generation of debug messages for static IP routes.

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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

The following example enables the generation of debug messages for interactions between static IP routes and the ISM:

[local]Redback#debug static ism

1.49   debug static dvsr

debug [boot {active | standby} | switchover] static dvsr [detail | packet]

no debug [boot {active | standby} | switchover] static dvsr [detail | packet]

1.49.1   Purpose

Enables the generation of dynamically verified static routing (DVSR) debug messages.

1.49.2   Command Mode

exec (10)

1.49.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

detail

Optional. Enables the generation of detailed debug messages for DVSR activities.

packet

Optional. Enables the generation of debug messages for DVSR verification IP packets.

1.49.4   Default

The generation of debug messages is disabled.

1.49.5   Usage Guidelines

Use the debug static dvsr command to enable the generation of DVSR 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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

The following example enables the generation of detail DVSR debug messages:

[local]Redback#debug static dvsr detail
Mar 28 22:45:35: %STATIC-7-DVSR_DET: dvsr node: seq_num 258, verify-addr 192.168.1.5, ping operation

Mar 28 22:45:35: %STATIC-7-DVSR_DET:  + send an icmp pkt to 192.168.1.5, src 0.0.0.0, len 56, seq_num 258

Mar 28 22:45:35: %STATIC-7-DVSR_DET: dvsr node: seq_num 259, verify-addr 192.168.1.5, ping operation

Mar 28 22:45:35: %STATIC-7-DVSR_DET:  + send an icmp pkt to 192.168.1.5, src 0.0.0.0, len 56, seq_num 259

1.50   debug subscriber

debug subscriber username username

no debug

1.50.1   Purpose

Enables the generation of subscriber debug messages for Mobile IP user name events on a home-agent (HA) instance and foreign-agent (FA) instance.

1.50.2   Command Mode

exec (10)

1.50.3   Syntax Description

username

Limits the generation of subscriber debug messages to a single Mobile IP subscribed identified by username or NAI.

username

Network Access Identifier (NAI) that identifies the user.

1.50.4   Default

The generation of subscriber debug messages for Mobile IP service username events on an HA instance is disabled.

1.50.5   Usage Guidelines

Use the debug subscriber command to enable the generation of subscriber debug messages for Mobile IP user name events on an HA and FA instance.

Use the no form of this command to disable the generation of subscriber debug messages for Mobile IP services user name events on an HA instance and FA instance.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

The following example show how to enable the generation of debug messages for this session to user1@rback:

[local]RedBack#debug subscriber username user1@user1@rback

The following example shows how to enable the generation of debug messages to the GRE12 Mobile IP tunnel circuit :

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

The debug messages are not generated until the required circuit debug commands are enabled. For example, to see all Mobile IP subscriber binding events on an HA instance, you must enable the debug circuit mobile-ip home-agent command; for example:

[local]RedBack#debug circuit mobile-ip home-agent binding

1.51   debug sysmon ftp

debug [{boot {active | standby} | switchover}] sysmon ftp

no debug [{boot {active | standby} | switchover}] sysmon ftp

1.51.1   Purpose

Enables the generation of debug messages related to transferring crash files out of the SmartEdge router using File Transfer Protocol (FTP).

1.51.2   Command Mode

exec (10)

1.51.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.51.4   Default

The generation of debug messages related to transferring crash files out of the SmartEdge router using FTP is disabled.

1.51.5   Usage Guidelines

Use the debug sysmon ftp command to enable the generation of debug messages related to transferring crash files out of the SmartEdge router using FTP.

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.

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

1.51.6   Examples

The following example enables all system monitoring debugging messages:

[local]Redback#debug sysmon ftp

1.52   debug talk

debug [{boot {active | standby} | switchover}] talk

no debug [{boot {active | standby} | switchover}] talk

1.52.1   Purpose

Enables the generation of debug messages for communications with another administrator during active Telnet or Secure Shell (SSH) sessions on the same SmartEdge router.

1.52.2   Command Mode

exec (10)

1.52.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

1.52.4   Default

The generation of debug messages for talk is disabled.

1.52.5   Usage Guidelines

Use the debug talk command to enable the generation of debug messages for communications with another administrator during active Telnet or SSH sessions on the same 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 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 SSH session.

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

1.52.6   Examples

The following example enables the generation of detailed debug messages for talk:

[local]Redback#debug talk

1.53   debug tap

debug [{boot {active | standby} | switchover}] tap {aaa | all | config | ppa | rcm | rpm | show | work}

no debug [{boot {active | standby} | switchover}] tap {aaa | all | config | ppa | rcm | rpm | show | work}

1.53.1   Purpose

Enables the generation of debug messages for the specified lawful intercept (LI) events.

1.53.2   Command Mode

exec (LI authorized administrator)

1.53.3   Syntax Description

boot

Optional. Enables the generation of debug messages during a system reload.

active

Enables the generation of debug messages for the active controller card.

standby

Enables the generation of debug messages for the standby controller card.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

aaa

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

all

Enables the generation of debug messages for all LI events.

config

Enables the generation of debug messages for LI configuration events.

ppa

Enables the generation of debug messages for LI Packet Processing ASIC (PPA) events.

rcm

Enables the generation of debug messages for LI Router Configuration Manager (RCM) events.

rpm

Enables the generation of debug messages for LI Routing Policy Manager (RPM) events.

show

Enables the generation of debug messages for LI show events.

work

Enables the generation of debug messages for LI work events.

1.53.4   Default

The generation of debug messages for LI events is disabled.

1.53.5   Usage Guidelines

Use the debug tap command to enable the generation of debug messages for the specified LI events.

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


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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 the specified LI events

1.53.6   Examples

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

[local]Redback#debug tap aaa

1.54   debug tunnel client

debug tunnel client

no debug tunnel client

1.54.1   Purpose

Enables the generation of debug messages for dynamic tunnel client events.

1.54.2   Command Mode

exec (10)

1.54.3   Syntax Description

This command has no keywords or arguments.

1.54.4   Default

The generation of debug messages for dynamic tunnel client events is disabled.

1.54.5   Usage Guidelines

Use the debug tunnel client command to enable the generation of debug messages for dynamic tunnel events.

Use the no form of this command to disable the generation of debug messages for dynamic tunnel client events.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

The following example shows how to limit the generation of debug messages for dynamic tunnel clients:

[local]Redback#debug tunnel client

1.55   debug vpls

debug vpls {all | cct | cfg | event | peer | sm | state}

no debug vpls {all | cct | cfg | event | peer | sm | state}

1.55.1   Purpose

Enables the generation of Virtual Private LAN Services (VPLS) debug messages.

1.55.2   Command Mode

exec (10)

1.55.3   Syntax Description

all

Enables the generation of all debug messages.

cct

Enables the generation of debug messages related to circuit and pseudo-wire processing.

cfg

Enables the generation of configuration-related debug messages.

event

Enables the generation of event messages.

sm

Enables the generation of debug messages related to shared memory operations.

state

Enables the generation of state debug messages.

1.55.4   Default

The generation of debug messages is disabled.

1.55.5   Usage Guidelines

Use the debug vpls command to enable the generation of VPLS debug messages.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution before enabling the generation of any debug messages on a production system.

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

The following example enables the generation of all VPLS debug messages:

[local]Redback#debug vpls all

1.56   debug vrrp

debug [boot {active | standby} | switchover] vrrp {all | arp [if-name [vrrp-id]] | general | ism | packet [error | receive | send] [if-name [vrrp-id]] | pktio [receive | send] | rcm | rpm | state [if-name [vrrp-id]] | snmp}

no debug [boot {active | standby} | switchover] vrrp {all | arp [if-name [vrrp-id]] | general | ism | packet [error | receive | send] [if-name [vrrp-id]] | pktio [receive | send] | rcm | rpm | state [if-name [vrrp-id]] | snmp}

1.56.1   Purpose

Enables the generation of Virtual Router Redundancy Protocol (VRRP) debug messages.

1.56.2   Command Mode

exec (10)

1.56.3   Syntax Description

active

Enables the generation of debug messages for the active controller card.

all

Enables the generation of all VRRP debug messages.

arp

Enables the generation of debug messages for Address Resolution Protocol (ARP) and VRRP interactions.

boot

Optional. Enables the generation of debug messages during a system reload.

error

Optional. Enables the generation of debug messages for packet errors only.

general

Enables the generation of debug messages for general operations.

if-name

Optional. Interface name. Enables the generation of debug messages for the specified VRRP interaction on only the named interface.

ism

Enables the generation of Interface and Circuit State Manager (ISM) and VRRP interactions.

packet

Enables the generation of debug messages for packet events.

pktio

Enables the generation of debug messages for packet I/O events.

rcm

Enables the generation of debug messages for Router Configuration Manager (RCM) and VRRP interactions.

receive

Optional. Enables the generation of debug messages for received packet I/O events only.

rpm

Enables the generation of debug messages for Router Policy Manager (RPM) and VRRP interactions.

send

Optional. Enables the generation of debug messages for sent packet I/O events only.

snmp

Enables the generation of debug messages for VRRP-MIB and RBN-FAST-VRRP-MIB.

standby

Enables the generation of debug messages for the standby controller card.

state

Enables the generation of debug messages for the virtual router state.

switchover

Optional. Enables the generation of debug messages during a switchover from the active to the standby controller.

vrrp-id

Optional. Virtual router ID. The range of values is 1 to 255. Used in conjunction with the optional if-name argument. Enables the generation of debug messages for the specified VRRP interaction for only traffic sent to or from the specified VRRP ID over the named interface.

1.56.4   Default

The generation of debug messages is disabled.

1.56.5   Usage Guidelines

Use the debug vrrp command to enable the generation of VRRP 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.


 Caution! 
Risk of performance loss. Enabling the generation of debug messages can severely affect system performance. To reduce the risk, exercise caution when enabling the generation of debug messages on a production system.

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

1.56.6   Examples

The following example enables the generation of debug messages for all VRRP packet events:

[local]Redback#debug vrrp packet all