Contents

1   Command Descriptions

Commands starting with “c” through commands starting with “clear mr” are included.

1.1   c2byte

1.1.1   Purpose

Defines the value for the Path Signal Label (C2) byte for a Packet over SONET/SDH (POS) port.

1.1.2   Command Mode

port configuration

1.1.3   Syntax Description

1.1.4   Default

The default value is 22 (hexadecimal 0x16).

1.1.5   Usage Guidelines

Use the c2byte command to define the value for the C2 byte for a POS port. RFC 2615, PPP over SONET/SDH, specifies that a C2 byte value of 22 (hexadecimal 0x16) is used to indicate Point-to-Point Protocol (PPP) with X^43 + 1 scrambling, and the value of 207 (hexadecimal 0xCF) is used to indicate PPP without scrambling.

Note:  

The SmartEdge® 100 router does not support POS ports.

Note:  

The SmartEdge router automatically configures the C2 byte to 22 (0x16) when synchronous payload envelope (SPE) scrambling is enabled, and to 207 (0xCF) when SPE scrambling is disabled; see the scramble command. To define a different C2 byte value to interoperate with another vendor’s equipment and you need to enable SPE scrambling, first enable SPE scrambling (it is enabled by default), and then override the C2 byte value with this command.

Note:  

This command applies only to a POS port on an OC-48c/STM-16c line card, OC-12c/STM-4c line card, or OC-3c/STM-1c line card.

Note:  

The C2 byte for a port on any Asynchronous Transfer Mode (ATM) OC line card is fixed at 0x13 and cannot be changed.

Use the default form of this command to define the C2 byte with the default value.

1.1.6   Examples

The following example shows how to define the value 22 (hexadecimal value 0x16) for the C2 byte for a POS port in slot 9:

[local]Redback(config)#port pos 9/1

[local]Redback(config-port)#c2byte 22

1.2   capabilities

1.2.1   Purpose

Enables the advertisement of router capabilities using Open Shortest Path First (OSPF) opaque link-state advertisements (LSAs).

1.2.2   Command Mode

OSPF router configuration

1.2.3   Syntax Description

1.2.4   Default

Advertisement of router capabilities is disabled.

1.2.5   Usage Guidelines

Use the capabilities command to enable the advertisement of router capabilities using OSPF opaque LSAs.

The capabilities LSAs advertise the optional OSPF capabilities enabled on the router to all IGP neighbors. Table 1 shows the reserved OSPF router capability bits and the associated capabilities that can be advertised.

Use the no form of this command to disable advertisement of router capabilities using OSPF opaque LSAs.

1.2.6   Examples

The following example enables the advertisement of router capabilities using Type 10 (area-scope) opaque LSAs:

[local]Redback(config-ctx)#router ospf 424

[local]Redback(config-ospf)#capabilities area-scope

1.3   card

card card-type slot

no card card-type slot

1.3.1   Purpose

Selects a carrier card, services card, or line card to take out of service for an on-demand diagnostic (ODD) session, or to place in service after an ODD session, and enters card configuration mode.

1.3.2   Command Mode

global configuration

1.3.3   Syntax Description

1.3.4   Default

None

1.3.5   Usage Guidelines

Use the card command to select a line or services card to take out of service for an ODD session, or to place in service after an ODD session, and enter card configuration mode.

This command is not required for any line card that is already installed; the operating system recognizes the type of each installed card. However, you can use this command to configure a line card and its associated ports, channels, and circuits before the line card is actually installed in the chassis.

If you configure a line card and then insert a different line card type in the slot, the ports on that line card do not come up.

Use the no form of this command to remove the configuration of a card from the configuration database.

Risk of data corruption and loss of charging records. Removing an SSE card from configuration without first shutting it down can cause file corruption. To avoid the risk, do one of the following before entering the no card sse slot command:

• If the SSE card is in assigned to an SSE group, enter the no bind sse group name and commit commands. Wait at least 15 seconds for the card to completely shut down.
• If the SSE card is not configured for redundancy, shut down the card with the shutdown and commit commands and wait for 15 seconds before entering the no card sse slot command.

1.3.6   Examples

The following example selects an ATM OC-12c/STM-4c line card in slot 2 to take out of service:

[local]Redback(config)#card atm-oc12-1-port 2
[local]Redback(config-card)#

The following example selects a 4-port 10GE aggregation card in slot 4 to take out of service:

[local]Redback(config)#card 10ge-4-port-sm 4
[local]Redback(config-card)#

1.4   care-of-address

1.4.1   Purpose

Specifies the interface used for the care-of-address (CoA) advertised by this foreign-agent (FA) instance.

1.4.2   Command Mode

FA configuration

1.4.3   Syntax Description

1.4.4   Default

The interface used for the CoA is not specified in advertisement messages.

1.4.5   Usage Guidelines

Use the care-of-address command to specify the interface used for the CoA advertised by this FA instance. Enter this command multiple times to specify multiple CoA interfaces. This command specifies an existing interface as the CoA interface; you must first create that interface using the interface command (in context configuration mode).

Use the no form of this command to specify the default condition.

1.4.6   Examples

The following example creates the coa interface in the local context and specifies it as the CoA interface for the FA instance:

[local]Redback(config)#context local
[local]Redback(config-ctx)#interface coa
[local]Redback(config-if)#exit
[local]Redback(config-ctx)#router mobile-ip
[local]Redback(config-mip)#foreign-agent
[local]Redback(config-mip-fa)#care-of-address coa local

1.5   ccm

1.5.1   Purpose

Enables the maintenance association endpoints (MEPs) in the current maintenance association (MA) to broadcast CCM PDUs, monitor for connectivity faults, and enter the CCM configuration mode where the CCM parameters can be configured.

1.5.2   Command Mode

MA configuration

1.5.3   Syntax Description

This command has no keywords or arguments.

1.5.4   Default

CCM is disabled. If CCM is enabled, the default settings of its parameters are as follows:

• interval—100 milliseconds between transmission of CCM PDUs.
• count—3; that is, a connectivity fault is declared if MA detects the failure of three consecutive CCMs.

1.5.5   Usage Guidelines

Use the ccm command to enable the MEPs in the current MA to broadcast CCM PDUs, monitor for connectivity faults, and enter the CCM configuration mode where the CCM parameters can be configured.

The CCM parameters include the frame-loss and std-interval parameters.

Use the no or default form of this command to disable CCM.

The default CCM PDU multicast address is 01:80:C2:00:00:3y, where y is the current MD level.

1.5.6   Examples

In the following example, the ccm command enables the SmartEdge router to monitor the bayarea MA for connectivity faults using CCMS PDUs. The default CCM parameters are used:

[local]Redback(config)#ethernet-cfm instance-1
[local]Redback(config-ether-cfm)#level 4
[local]Redback(config-ether-cfm)#domain-name abc.com
[local]Redback(config-ether-cfm)#maintenance-association bayarea
[local]Redback(config-ether-cfm-ma)#ccm

1.6   ccod-mode port-listen

1.6.1   Purpose

Enables port listening mode for this Asynchronous Transfer Mode (ATM) port.

1.6.2   Command Mode

• ATM OC configuration

1.6.3   Syntax Description

This command has no keywords or arguments.

1.6.4   Default

Port listening mode is disabled for all ATM ports.

1.6.5   Usage Guidelines

Use the ccod-mode port-listen command to enable port listening mode for this ATM port. This command is available only for ports on second-generation ATM OC line cards.

Note:  

Enabling port listening mode with this command must precede the configuration of any ATM VPs or PVCs on this port.

Use this command to specify the full range of ATM virtual path identifiers (VPIs) and virtual circuit identifiers (VCIs) (VCI 0 to 255, VPI 1 to 65,535) when entering the atm pvc on-demand command (in ATM OC configuration mode) to create listening on-demand ATM permanent virtual circuits (PVCs) for this port. Otherwise, the range specified must be within the limits for that type of port.

This command does not change the maximum number of active PVCs that are supported on the type of ATM port on which you are creating them, nor the number of active PVCs that are supported for each line class on that type of ATM port. For PVC limits for ATM ports and line classes, see the tables that specify PVC limits in ATM Configuration Guidelines in Configuring Circuits:

• Traffic Class Combinations for ATM Priority Mode: Traffic Class Combinations for ATM Priority Mode
• PVC Limits on First-Generation ATM OC Ports: PVC Limits on First-Generation ATM OC Ports
• Shaped VP Limits for ATM Traffic Cards: Shaped VP Limits for ATM Traffic Cards
• PVC Limits on Shaped VPs for ATM Traffic Cards: Shaped VP Limits for ATM Traffic Cards
• PVC Limits for ATM Cards Without ATMWFQ Policy: PVC Limits for ATM Cards Without ATMWFQ Policy
• PVC Limits for ATM Traffic Cards with ATMWFQ CoS Queues: PVC Limits for ATM Traffic Cards with ATMWFQ CoS Queues

Use the no or default form of this command to disable port listening mode for this port.

1.6.6   Examples

The following example shows how to enable port listening mode for port 2 on the 4-port ATM OC-3c/STM-1c line card in slot 3:

[local]Redback(config)#port atm 3/2

[local]Redback(config-atm-oc)#ccod-mode port-listen

1.7   cd

1.7.1   Purpose

Changes the current working directory.

1.7.2   Command Mode

exec (10)

1.7.3   Syntax Description

1.7.4   Default

None

1.7.5   Usage Guidelines

Use the cd command to change the current working directory. By default, the current working directory when you log on to the system is /flash.

You must specify a directory on the local file system, with a URL in the following form:

[/device][/directory]...[/directory]

The value for the device argument can be flash, or if a mass-storage device is installed, md. If you do not specify the device argument, the default value is the device in the current working directory. Directories can be nested to any level.

1.7.6   Examples

The following example changes the current working directory to /flash/config/old:

[local]Redback>cd /flash/config/old

Current directory is now /flash/config/old

The following example changes the current working directory to the parent directory:

[local]Redback>cd ..

Current directory is now /flash/config

The following example changes the current working directory to the mass-storage device:

[local]Redback>cd /md

Current directory is now /md

1.8   cell-encap

1.8.1   Purpose

Enables and configures ATM cell mode encapsulation on the specified cross-connection (XC).

1.8.2   Command Mode

• L2VPN profile peer configuration

1.8.3   Syntax Description

1.8.4   Default

ATM cell mode encapsulation is disabled on XCs.

1.8.5   Usage Guidelines

Use the cell-encap command to enable and configure ATM cell mode encapsulation in an L2VPN profile. All ATM XCs that have this profile attached inherit this configuration.

After ATM cell mode encapsulation is enabled in an L2VPN profile, you cannot use the xc command to disable cell mode encapsulation on XCs that have that L2VPN profile attached. Instead, you must disable cell mode encapsulation in the L2VPN profile.

After ATM cell mode encapsulation is disabled in an L2VPN profile that is attached to an XC, you cannot modify the cell encapsulation setting in the L2VPN profile.

Use the no form of this command to disable ATM cell mode encapsulation in an L2VPN profile.

1.8.6   Examples

The following example shows how to enable and configure ATM cell mode encapsulation in an L2VPN profile called pr1:

[local]Redback(config)#l2vpn profile pr1
Redback(config-l2vpn-xc-profile)#peer 111.111.111.111
Redback(config-l2vpn-xc-profile-peer)#cell-encap nto1-vcc

1.9   circuit-group

1.9.1   Purpose

Creates a circuit group and assigns to it the specified name or selects an existing circuit group, and then enters circuit-group configuration mode.

1.9.2   Command Mode

global configuration

1.9.3   Syntax Description

1.9.4   Default

By default, no circuit groups exist and no ports or link groups are associated with a newly-created circuit group.

1.9.5   Usage Guidelines

Use the circuit-group command to create a circuit group and assign it a specified name, and then enter circuit-group configuration mode. If the specified circuit group already exists, this command allows you to configure the specified circuit group by entering circuit-group configuration mode.

The following existing commands are available in circuit-group configuration mode:

• qos hierarchical mode
• qos policy metering
• qos policy policing
• qos policy queuing (for priority weighted fair queuing [PWFQ] policies only)
• qos profile overhead
• qos rate
• qos weight

A circuit group that is created specifying a port (using the port slot/port construct) or link-group (using the link-group lg-name construct) is known as a homed circuit group. A homed circuit group supports all configuration parameters and bindings, including those related to traffic management and priority weighted fair queuing (PWFQ), while a nonhomed circuit group supports only metering and policing bindings. However, a nonhomed circuit group may include circuits that span physical ports.

To change a circuit group from a homed to a nonhomed mode, delete the circuit group and then recreate it. You can add a port or link-group reference to a nonhomed circuit group to convert it to a homed circuit group only if the circuit group does not have any configured members.

A port or link group must be specified for a circuit group to enable the following QoS-related configuration command options:

• qos hierarchical mode strict
• qos policy queuing
• qos profile overhead
• qos rate
• qos weight

Use the no form of the circuit-group command to remove the specified circuit group, its children circuit groups, and all circuit-group-member commands that reference those circuit groups from the configuration.

1.9.6   Examples

The following example shows how to create a nonhomed circuit group named group7 and configure policing and metering policies to apply to this circuit group and its members:

[local]Redback(config)#circuit-group group7
[local]Redback(config-circuit-group)#qos policy policing group_policing_policy hierarchical
[local]Redback(config-circuit-group)#qos policy metering group_metering_policy inherit

The following example shows how to create a homed circuit group named group8 that resides on slot 1, port 2. A queuing policy named MyPolicy is configured to apply to this circuit group and its members:

[local]Redback(config)#circuit-group group8 port 1/2
[local]Redback(config-circuit-group)#qos policy queuing MyPolicy

[local]Redback(config)#circuit-group vp10 port 1/1 virtual port
[local]Redback(config-circuit-group)#qos policy queuing pwfq1

[local]Redback(config)#circuit-group parentCG port 1/1x
[local]Redback(config-circuit-group)#qos policy policing parent-Police hierarchical
[local]Redback(config)#circuit-group childCG1 parent-circuit-group parentCG
[local]Redback(config-circuit-group)#qos policy policing child-Police inherit
[local]Redback(config)#circuit-group childCG2 parent-circuit-group parentCG 
[local]Redback(config-circuit-group)#qos policy policing child-Police inherit

[local]Redback(config)#circuit-group parentCG2 port 1/1
[local]Redback(config-circuit-group)#qos policy policing Hi-Police hierarchical
[local]Redback(config-circuit-group)#qos policy metering Hi-Meter hierarchical
[local]Redback(config-circuit-group)#qos policy queuing TMPOLICY5

[local]Redback(config)#circuit-group childCG1 parent-circuit-group parentCG2
[local]Redback(config)#circuit-group childCG2 parent-circuit-group childCG1 
[local]Redback(config)#circuit-group childCG3 parent-circuit-group childCG2

1.10   circuit-group-member

1.10.1   Purpose

Specifies that the 802.1Q PVC or PVCs or subscriber being configured are members of the specified circuit group.

1.10.2   Command Mode

• dot1q PVC configuration
• access link-group PVC configuration
• subscriber configuration (default subscriber profile, subscriber profile or subscriber record)

1.10.3   Syntax Description

1.10.4   Default

Dot1q PVCs and subscribers are not members of circuit groups.

1.10.5   Usage Guidelines

Use the circuit-group-member command to specify that the 802.1Q PVC or PVCs or subscriber being configured are to be members of the specified circuit group.

Note:  

At most, each circuit may belong to one circuit group.

Use the no form of this command to remove the specified dot1q PVC or PVCs from any circuit group to which it currently belongs. The name argument is optional in this case. Using the no form of this command to remove the circuit-group membership from a subscriber record or profile has no effect on the active subscriber sessions associated with the record or profile belonging to the circuit group. However, new subscriber's circuits will not become members of the circuit group once up.

Note:  

You must explicitly remove a circuit from an existing circuit group membership (by using the no option of circuit-group-member command) before assigning it to a new circuit group.

For more information about circuit group membership, see Circuit Groups.

1.10.6   Examples

The following example shows how to define a circuit group named group7 and then specify a range of dot1q PVCs (50 through 60) that is to be a member of the circuit group:

[local]Redback(config)#circuit-group group7
[local]Redback(config-circuit-group)#qos policy policing group
_policing_policy hierarchical
[local]Redback(config-circuit-group)#qos policy 
metering group_metering_policy inherit

[local]Redback(config)#port ethernet 12/1
[local]Redback(config-port)#encapsulation dot1q
[local]Redback(config-port)#dot1q pvc 50 through 60
[local]Redback(config-dot1q-pvc)#circuit-group-member group7

[local]Redback(config)#circuit-group myVP1 port 1/1 virtual-port
[local]Redback(config)#port ethernet 1/1
[local]Redback(config-port)#dot1q pvc 1 encap 1qtunnel
[local]Redback(config-dot1q-pvc)#circuit-group-member myVP1
[local]Redback(config-dot1q-pvc)#qos rate max 1000000
[local]Redback(config-dot1q-pvc)#dot1q pvc 1:1
[local]Redback(config-dot1q-pvc)#qos policy queuing pwfq2

[local]Redback(config)#circuit-group myVP2 port 1/1 virtual-port
[local]Redback(config-circuit-group)#qos policy queuing pwfq1
[local]Redback(config)#context zone1
[local]Redback(config-ctx)#subscriber profile isp2
[local]Redback(config-sub)#circuit-group-member myVP2

1.11   circuit mtu

1.11.1   Purpose

Configures the Intermediate System-to-Intermediate System (IS-IS) interface maximum transmission unit (MTU) size independent of the IP interface MTU size.

1.11.2   Command Mode

IS-IS interface configuration

1.11.3   Syntax Description

1.11.4   Default

None

1.11.5   Usage Guidelines

Use the circuit mtu command to configure the IS-IS interface MTU size independent of the IP interface MTU size. This configuration command decouples the IS-IS packet MTU and IP packet MTU, if needed, because IS-IS link-state packets must be flooded over all the IS-IS interfaces without link fragmentation. You can use this command to ensure that the maximum size of link-state packets are be transmitted to all the neighbors while ensuring that IP packets delivery remains efficient.

Use the no form of this command to use the same MTU size for the IS-IS interface and the IP interface.

1.11.6   Examples

The following IS-IS interface configuration shows an IS-IS running over Ethernet. Not all the routers on this Ethernet LAN can handle IS-IS packets over 1,500 bytes, and this Ethernet interface MTU is above 1,500 bytes, thus the user sets the IS-IS MTU different from the IP interface MTU:

[local]Redback(config-ctx)#router isis ip-backbone
[local]Redback(config-isis)#interface ge10/1
[local]Redback(config-isis-if)#circuit mtu 1500

1.12   circuit protocol

1.12.1   Purpose

Creates a child circuit on a multiprotocol Asynchronous Transfer Mode (ATM) or 802.1Q permanent virtual circuit (PVC), specifies an encapsulation for it, and enters ATM or dot1q child protocol configuration mode.

1.12.2   Command Mode

• ATM PVC configuration
• dot1Q PVC configuration

1.12.3   Syntax Description

1.12.4   Default

No child circuit is created for a multiprotocol ATM or 802.1Q PVC.

1.12.5   Usage Guidelines

Use the circuit protocol command to create a child circuit on a multiprotocol ATM or 802.1Q PVC, specify a protocol for it, and then enter ATM or dot1q child protocol configuration mode.

You must have specified the multi keyword when you created the ATM PVC using the atm pvc command (in ATM OC configuration mode), or when you created the 802.1Q PVC using the dot1q pvc command (in port configuration mode); otherwise, you cannot create child circuits on the ATM or 802.1Q PVC.

This command, together with the xc command (in global configuration mode), acts as a filter on a multiprotocol ATM or 802.1Q PVC to pass only the type of packets specified by the value of the encaps-type argument.

Use the no form of this command to delete the circuit.

Use the circuit protocol command to create a child circuit on an 802.1Q PVC, specify a protocol for it, and then enter dot1q child protocol configuration mode.

This command, together with the xc command (in global configuration mode), acts as a filter on an 802.1Q PVC to pass only the type of packets specified by the value of the encaps-type argument.

Use the no form of this command to delete the circuit.

1.12.6   Examples

The following example shows how to create an ATM PVC encapsulated to support multiple protocols and creates an IPv6oE-encapsulated child circuit on that PVC. Only incoming IPv6oE-encapsulated packets are passed through the cross-connection:

[local]Redback(config)#port atm 3/1
[local]Redback(config-atm-oc)#atm pvc 10 10 profile pf3 encapsulation multi
[local]Redback(config-atm-pvc)#circuit protocol ipv6oe
[local]Redback(config-atm-child-proto)#

The following example shows how to create an 802.1Q PVC encapsulated to support multiple protocols and creates a PPPoE-encapsulated child circuit on that PVC. Only incoming IPv6oE-encapsulated packets are passed through the cross-connection:

[local]Redback(config)#port ethernet 4/1
[local]Redback(config-port)#encapsulation dot1q
[local]Redback(config-port)#dot1q pvc 10 profile pf2 encapsulation multi
[local]Redback(config-dot1q-pvc)#circuit protocol pppoe
[local]Redback(config-dot1q-child-proto)#

1.13   circuit type

1.13.1   Purpose

Configures the type of Intermediate System-to-Intermediate System (IS-IS) adjacency on the interface.

1.13.2   Command Mode

IS-IS interface configuration

1.13.3   Syntax Description

1.13.4   Default

The circuit type is level 1 and level 2.

1.13.5   Usage Guidelines

Use the circuit type command to configure the type of IS-IS adjacency on the interface.

Use the no form of this command to restore the setting to the default type of level 1 and level 2.

1.13.6   Examples

The following example configures the circuit type to level-2 for the fa4/1 interface running the ip-backbone IS-IS instance. Level 1 Hello packets are not sent on the fa4/1 interface:

[local]Redback(config-ctx)#router isis ip-backbone
[local]Redback(config-isis)#interface fa4/1
[local]Redback(config-isis-if)#circuit type level-2-only

1.14   class

1.14.1   Purpose

Creates a class in a class-based policy and accesses policy group class configuration mode.

1.14.2   Command Mode

policy group configuration

1.14.3   Syntax Description

1.14.4   Default

None

1.14.5   Usage Guidelines

Use the class command to create a class in a class-based policy and access policy group class configuration mode. This command allows a forward policy, a Network Address Translation (NAT) policy, or a quality of service (QoS) policy to apply a different action to different sets (classes) of packets that are defined in the applied policy access control list (ACL).

If the class-name argument matches a class-name argument in a rule in the policy ACL, the class-based policy processes packets of that type as specified by the class-based policy. If a rule for the class-name argument is not specified in the policy ACL, the class-based policy considers the class to be dormant and takes no action. If a rule for the class-name argument is specified in the ACL, but you do not include the class in the policy (using this command), the SmartEdge router considers those packets to be in the default class.

Use the no form of this command to delete the specified class.

1.14.6   Examples

The following example applies the QoSACL-1 policy ACL to a QoS policing policy that prioritizes incoming packets in the Web class using a Differentiated Service Code Point (DSCP) value of DF. For the VOIP class, incoming traffic packets are prioritized with a DSCP value of AF11:

[local]Redback(config-policy-policing)#access-group QoSACL-1 local
[local]Redback(config-policy-group)#class Web
[local]Redback(config-policy-group-class)#rate 6000 burst 3000
[local]Redback(config-policy-class-rate)#exceed mark dscp DF
[local]Redback(config-policy-group-class)#exit
[local]Redback(config-policy-group)#class VOIP
[local]Redback(config-policy-group-class)#mark dscp AF11

The following example applies the PBR_ACL policy ACL to the MirrorPolicy forward policy, which mirrors all traffic packets in the Web class to the mirror output destination, WebTraffic:

[local]Redback(config)#forward policy MirrorPolicy
[local]Redback(config-policy-frwd)#access-group PBR_ACL local
[local]Redback(config-policy-group)#class Web
[local]Redback(config-policy-group-class)#mirror destination WebTraffic all

1.15   class-group

1.15.1   Purpose

Specifies a class definition and enters policy group configuration mode.

1.15.2   Command Mode

• metering policy configuration
• policing policy configuration

1.15.3   Syntax Description

1.15.4   Default

No class definition is assigned to a policing or metering policy.

1.15.5   Usage Guidelines

Use the class-group command to specify a class definition and enter policy group configuration mode. A packet subject to the policing or metering policy being configured is assigned a class according to the referenced class definition. In policy group configuration mode, you can reference class names defined in the class definition and assign actions to perform on packets assigned to a class. You can configure any command or action that is available for policy access control list (ACL) classes or for class-definition classes.

Class-definition policing or metering is an alternative to ACL policing or metering. For each metering or policing policy, you can specify either an ACL group or a class group, but not both. Unlike ACL metering and policing policies, which require access to the packet’s IP header, you can apply class-definition metering and policing policies to Layer 2 circuits, such as Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC) sessions, Layer 2 Virtual Private Networks (VPNs) and cross-connections, and bridged circuits. When you apply policing and metering policies to Layer 2 circuits, you cannot use the mark dscp and mark precedence commands to mark packets and assign priority because these commands also require access to the packet’s IP header. When a packet arrives, the SmartEdge router applies any ingress classification propagation and mapping to determine a packet’s initial packet descriptor (PD) value. If you use a class definition to apply a policing policy, the resulting PD value for the packet determines its class.

You can use class-definition policing or metering to propagate quality of service (QoS) settings without configuring classification maps.

Use the qos class-definition command (in global configuration mode) to define a class definition to be referenced by a metering or policing policy.

Use the no form of this command to remove the class group reference.

1.16   cleanup-timer

1.16.1   Purpose

Configures the L2TP tunnel teardown value.

1.16.2   Command Mode

L2TP peer configuration

1.16.3   Syntax Description

1.16.4   Default

For tunnels with named peers, the L2TP tunnel does not timeout even when no subscriber sessions have been connected. For tunnels with unnamed peers, the default timeout is 60 seconds.

Use the no or default form of this command to disable any timeout settings that have been configured by this command and return the L2TP tunnel to the default timeout condition.

1.16.5   Usage Guidelines

Use the cleanup-timer command to configure the L2TP tunnel teardown value. If no subscriber sessions have been the connected over the L2TP tunnel for a time greater than or equal to the specified time, the tunnel is disconnected.

Supported on all line cards.

1.16.6   Examples

The following example shows how this command is used:

[local]Redback(config-ctx)#l2tp-peer default
[local]Redback(config-l2tp)#cleanup-timer 12000

1.17   clear aaa route subscriber aggregate

1.17.1   Purpose

Clears all routes downloaded from the route download server. In addition, if this command is issued, the SmartEdge router ceases to attempt to download the routes. However, if the interval timer expires, then the SmartEdge router initiates a download. Alternatively, a download must be manually initiated using the download aaa route command.

1.17.2   Command Mode

exec

1.17.3   Examples

[local]Redback#clear aaa route subscriber aggregate

1.18   clear access-group

1.18.1   Purpose

Clears counters for the ACLs that are applied to the specified port, channel, circuit, or interface.

1.18.2   Command Mode

exec (10)

1.18.3   Syntax Description

Keywords and arguments for the circuit-filter argument are:

1.18.4   Default

None

1.18.5   Usage Guidelines

Use the clear access-group command to clear counters for the ACLs that are applied to the specified port, channel, circuit, or interface.

Note:  

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

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

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

1.18.6   Examples

The following example clears forward policy ACL counters for incoming traffic on port 1 of the line card installed in slot 1:

[local]Redback#clear access-group forward 1/1 in counters

The following example clears counters for policy ACLs used with the NAT policy applied to the if-nat-1 interface:

[local]Redback#clear access-group nat interface if-nat-1 in counters

The following example clears QoS policy ACL counters for the incoming traffic on port 1 of the line card installed in slot 1:

[local]Redback#clear access-group qos 1/1 in counters

The following example clears RPF hit counters for IP ACLs applied to the RPF eth1 interface:

[local]Redback#clear access-group rpf interface eth1 in counters

The following example clears hit counters and deny log entries for the administrative port ACL:

[local]Redback#clear access-group ip-filter admin in all

[local]Redback#clear access-group ipv6 forward 1/1 in counters

[local]Redback#clear access-group ipv6 qos l2tp lns 1 in counters 

1.19   clear access-line

1.19.1   Purpose

Deletes the digital subscriber line (DSL) attributes that the system has learned from the DSL access multiplexer (DSLAM) for the selected DSLs.

1.19.2   Command Mode

exec

1.19.3   Syntax Description

1.19.4   Default

None

1.19.5   Usage Guidelines

Use the clear access-line command to delete the DSL attributes that the system has learned from the DSLAM for the selected DSLs. This command deletes only the attributes that the system has learned from the ANCP; it does not delete those attributes learned from the signaling described in the DSL Forum TR-101, Migration to Ethernet-Based DSL Aggregation document.

For every selected DSL, if the DSL port on the DSLAM was signaled as down (with a Port-Down message) or if the connection to the associated ANCP neighbor peer is down, the DSL attributes are deleted.

Note:  

If the state of a DSL line is SHOWTIME, the associated DSL attributes are not deleted.

Note:  

This command does not delete attributes from any DSL that is signaled as up and for which an ANCP connection is still up.

1.19.6   Examples

The following example deletes DSL attributes for circuit agent ID abc-2.1:

[local]Redback#clear access-line agent-circuit-id abc-2.1

1.20   clear administrator

1.20.1   Purpose

Terminates one or all of an administrator’s remote (Telnet or Secure Shell [SSH]) terminal sessions.

1.20.2   Command Mode

exec

1.20.3   Syntax Description

1.20.4   Default

If you use this command without the optional tty-name argument, all sessions for the specified administrator are cleared.

1.20.5   Usage Guidelines

Use the clear administrator command to end one or all of an administrator’s remote terminal sessions with the following criteria:

• An administrator in the local context can end any administrator session.
• Administrators in any other context can end sessions only in their own context.
• This command does not end the current session.

Use the optional tty-name argument to indicate a specific terminal session to be cleared. If you use the command without this argument, all of the specified administrator’s sessions are cleared. The output of the show administrators command (in exec mode) displays the TTY names.

1.20.6   Examples

The following example clears a single terminal session for a administrator, test:

[local]Redback#clear administrator test ttyp2

1.21   clear ancp neighbor

1.21.1   Purpose

Terminates the Transmission Control Protocol (TCP) connection for Access Node Control Protocol (ANCP) sessions for one or more ANCP neighbor peers.

1.21.2   Command Mode

exec (10)

1.21.3   Syntax Description

1.21.4   Default

None

1.21.5   Usage Guidelines

Use the clear ancp neighbor command to terminate the TCP connection for ANCP sessions for one or more ANCP neighbor peers.

Use the purge keyword to delete the DSL attributes for all DSLs managed by this ANCP neighbor peer and restore the subscriber rates to the values specified in the QoS policies that are attached to the subscriber circuits. This keyword initiates a warning message that purging the attributes for the subscriber connections can possibly cause service degradation, and asks for confirmation. The DSL attributes are deleted only after all subscriber sessions are ended on this ANCP neighbor peer.

1.21.6   Examples

The following example terminates ANCP sessions with the ANCP neighbor peer with IP address 10.1.1.1:

[local]Redback#clear ancp neighbor 10.1.1.1

1.22   clear ancp neighbor statistics

1.22.1   Purpose

Clears Access Node Control Protocol (ANCP) neighbor statistics for one or more ANCP neighbor peers.

1.22.2   Command Mode

exec (10)

1.22.3   Syntax Description

1.22.4   Default

None

1.22.5   Usage Guidelines

Use the clear ancp neighbor statistics command to clear ANCP neighbor statistics for one or more ANCP neighbor peers. Display these statistics with the show ancp neighbor statistics command (in any mode).

1.22.6   Examples

The following example clears ANCP neighbor statistics for all ANCP neighbor peers:

[local]Redback#clear ancp neighbor all statistics

1.23   clear arp-cache

1.23.1   Purpose

Clears all entries from the Address Resolution Protocol (ARP) table.

1.23.2   Command Mode

exec (10)

1.23.3   Syntax Description

1.23.4   Default

No entries are cleared from the ARP table.

1.23.5   Usage Guidelines

Use the clear arp-cache command to clear all ARP table entries.

Use the ip-addr argument to clear the specified host IP address from the ARP table.

1.23.6   Examples

The following example clears all ARP table entries:

[local]Redback#clear arp-cache

The following example clears the IP address, 43.56.26.45, from the ARP table:

[local]Redback#clear arp-cache 43.56.26.45

1.24   clear arp-cache interworking

1.24.1   Purpose

Clears information for cross-connections between Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs) and 802.1Q PVCs from the Address Resolution Protocol (ARP) table.

1.24.2   Command Mode

exec (10)

1.24.3   Syntax Description

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

1.24.4   Default

None

1.24.5   Usage Guidelines

Use the clear arp-cache interworking command to clear information for cross-connections between ATM PVCs and 802.1Q PVCs from the ARP table.

Note:  

The command used to configure interworking cross-connections is the xc command (in global configuration mode); for more information, see Configuring Cross-Connections.

1.24.6   Examples

The following example clears information for VLAN ID 1 from the ARP table:

[local]Redback#clear arp-cache interworking 2/1 vlan-id 1

1.25   clear arp-cache statistics

1.25.1   Purpose

Clears traffic statistics from the Address Resolution Protocol (ARP) table.

1.25.2   Command Mode

exec (10)

1.25.3   Syntax Description

This command has no keywords or arguments.

1.25.4   Default

Statistics are not cleared from the ARP table.

1.25.5   Usage Guidelines

Use the clear arp-cache statistics command to clear traffic statistics from the ARP table.

1.25.6   Examples

The following example clears traffic statistics from the ARP table:

[local]Redback#clear arp-cache statistics

1.26   clear as-path-list

1.26.1   Purpose

Clears match and cache hit counts for a specified Border Gateway Protocol (BGP) autonomous system (AS) path list.

1.26.2   Command Mode

exec (10)

1.26.3   Syntax Description

1.26.4   Default

None

1.26.5   Usage Guidelines

Use the clear as-path-list command to clear match and cache hit counts for a specified BGP AS path list.

Note:  

A reference to an AS path list that does not exist, or does not contain any configured entries, implicitly matches and permits all AS paths.

1.26.6   Examples

The following example clears match and cache hit counts for the aslist1 AS path list:

[local]Redback#clear as-path-list aslist1

1.27   clear atm circuit

1.27.1   Purpose

Clears one or more Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs).

1.27.2   Command Mode

exec (10)

1.27.3   Syntax Description

1.27.4   Default

None

1.27.5   Usage Guidelines

Use the clear atm circuit command to clear one or more ATM PVCs and all the subscriber sessions on it. If an ATM PVC was created on demand, it is deleted. This command is available only in the local context.

Note:  

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

Note:  

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

Use the all keyword to clear all ATM PVCs on the system, specified port, or specified VP.

1.27.6   Examples

The following example shows how to clear all ATM PVCs on the system:

[local]Redback#clear atm circuit all

The following example shows how to clear all ATM PVCs on port 1 of the ATM OC-3 line card in slot 4:

[local]Redback#clear atm circuit 4/1 all

1.28   clear atm counters

1.28.1   Purpose

Clears the traffic counters for one or more Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs).

1.28.2   Command Mode

exec (10)

1.28.3   Syntax Description

1.28.4   Default

Clears all ATM counters for all ATM PVCs.

1.28.5   Usage Guidelines

Use the clear atm counters command to clear traffic counters for one or more ATM PVCs.

Note:  

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

Note:  

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

You must specify the vpi vpi and vci start-vci constructs to clear only the counters for a specific ATM PVC. Use the through end-vci construct to clear the counters for a range of VCIs. If you do not specify any optional constructs, the clear atm counters command clears all ATM counters for all ATM PVCs on the port in the current context.

1.28.6   Examples

The following example shows how to clear the traffic counters for the ATM PVC on port 1 on the ATM line card in slot 3:

[local]Redback#clear atm counters 3/1

1.29   clear bgp

1.29.1   Purpose

Resets Border Gateway Protocol (BGP) connections or forces BGP updates to be generated.

Note:  

The clear bgp command is used for test purposes only, and using it to apply new routing policies is no longer required, because routing policies are automatically updated.

1.29.2   Command Mode

exec (10)

1.29.3   Syntax Description

1.29.4   Default

None

1.29.5   Usage Guidelines

Use the clear bgp command to reset BGP connections, or to force BGP updates to be generated.

Note:  

The clear bgp command is used for test purposes only, and using it to apply new routing policies is no longer required, because routing policies are automatically updated.

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] construct to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.29.6   Examples

The following example resets all BGP connections:

[local]Redback#clear bgp *

1.30   clear bgp external

1.30.1   Purpose

Resets external Border Gateway Protocol (eBGP) connections or forces BGP updates to be generated for eBGP connections without dropping the connections.

1.30.2   Command Mode

exec (10)

1.30.3   Syntax Description

1.30.4   Default

None

1.30.5   Usage Guidelines

Use the clear bgp external command to reset eBGP connections or force BGP updates to be generated for eBGP connections without causing a hard reset (which drops connections immediately).

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.30.6   Examples

The following example resets all eBGP connections:

[local]Redback#clear bgp external

1.31   clear bgp flap-statistics

1.31.1   Purpose

Clears Border Gateway Protocol (BGP) connection route-flap statistics.

1.31.2   Command Mode

exec (10)

1.31.3   Syntax Description

1.31.4   Default

None

1.31.5   Usage Guidelines

Use the clear bgp flap-statistics command to clear BGP route-flap statistics.

1.31.6   Examples

The following example clears all BGP route-flap statistics:

[local]Redback#clear bgp flap-statistics

1.32   clear bgp ipv4 multicast

1.32.1   Purpose

Resets Border Gateway Protocol (BGP) IP Version 4 (IPv4) address connections or forces BGP updates to be generated for connections using multicast address prefixes without dropping the connections.

1.32.2   Command Mode

exec (10)

1.32.3   Syntax Description

1.32.4   Default

None

1.32.5   Usage Guidelines

Use the clear bgp ipv4 multicast command to reset BGP IPv4 address connections or force BGP updates to be generated for connections using multicast address prefixes without causing a hard reset (which drops the connection immediately).

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.32.6   Examples

The following example resets all BGP multicast connections using IPv4 address prefixes:

[local]Redback#clear bgp ipv4 multicast *

1.33   clear bgp ipv4 unicast

1.33.1   Purpose

Resets Border Gateway Protocol (BGP) IP Version 4 (IPv4) address connections or forces BGP updates to be generated for connections using unicast address prefixes without dropping the connections.

1.33.2   Command Mode

exec (10)

1.33.3   Syntax Description

1.33.4   Default

None

1.33.5   Usage Guidelines

Use the clear bgp ipv4 unicast command to reset BGP IPv4 address connections, or force BGP updates to be generated for connections using unicast address prefixes without causing a hard reset (which drops the connection immediately).

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.33.6   Examples

The following example resets all BGP unicast connections using IPv4 address prefixes:

[local]Redback#clear bgp ipv4 unicast *

1.34   clear bgp ipv4 vpn

1.34.1   Purpose

Resets Border Gateway Protocol (BGP) IP Version 4 (IPv4) address connections or forces BGP updates to be generated for connections using Virtual Private Network (VPN) prefixes without dropping the connections.

1.34.2   Command Mode

exec (10)

1.34.3   Syntax Description

1.34.4   Default

None

1.34.5   Usage Guidelines

Use the clear bgp ipv4 vpn command to reset BGP IPv4 connections or force BGP updates to be generated for connections using VPN prefixes without causing a hard reset (which drops the connection immediately).

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.34.6   Examples

The following example performs a route refresh to all iBGP neighbors for the IPv4 VPN address family:

[local]Redback#clear bgp ipv4 vpn * soft out

1.35   clear bgp ipv6 unicast *

1.35.1   Purpose

Resets or forces updates for all Border Gateway Protocol (BGP) unicast neighbor connections that use IP Version 6 (IPv6) address prefixes without dropping the connection.

1.35.2   Command Mode

exec (10)

1.35.3   Syntax Description

1.35.4   Default

None

1.35.5   Usage Guidelines

Use the clear bgp ipv6 unicast * command to reset or force updates for all BGP unicast neighbor connections that use IPv6 address prefixes without dropping the connection.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.35.6   Examples

The following example forces the reset of all BGP unicast connections using IPv6 address prefixes:

[local]SE1#clear bgp ipv6 unicast * soft 

The following example forces the reset of all outbound BGP unicast connections using IPv6 address prefixes:

[local]SE1#clear bgp ipv6 unicast * soft out

1.36   clear bgp ipv6 unicast as

1.36.1   Purpose

Resets or forces Border Gateway Protocol (BGP) inbound updates to be generated for BGP IPv6 unicast neighbor connections in the specified autonomous system number (ASN) without dropping the connection.

1.36.2   Command Mode

exec (10)

1.36.3   Syntax Description

1.36.4   Default

None

1.36.5   Usage Guidelines

Use the clear bgp ipv6 as command to reset or force BGP inbound updates to be generated for BGP IPv6 unicast neighbor connections in the specified autonomous system number (ASN) without dropping the connection.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.36.6   Examples

The following example resets or forces BGP inbound updates to be generated for BGP IPv6 unicast neighbor connections in the ASN 600:

[local]SE1#clear bgp ipv6 unicast ipv6 as 600 soft in

1.37   clear bgp ipv6 unicast external

1.37.1   Purpose

Resets or forces Border Gateway Protocol (BGP) updates for all external IP Version 6 (IPv6) BGP neighbor unicast connections.

1.37.2   Command Mode

exec (10)

1.37.3   Syntax Description

1.37.4   Default

None

1.37.5   Usage Guidelines

Use the clear bgp ipv6 unicast external command to reset or force BGP updates for all external IPv6 BGP neighbor unicast connections.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.37.6   Examples

The following example resets or forces BGP updates for all external IPv6 BGP neighbor unicast connections:

[local]SE1#clear bgp ipv6 unicast external soft 

1.38   clear bgp ipv6 unicast flap-statistics

1.38.1   Purpose

Clears Border Gateway Protocol (BGP) IP Version 6 (IPv6) unicast connection route-flap statistics.

1.38.2   Command Mode

exec (10)

1.38.3   Syntax Description

1.38.4   Default

None

1.38.5   Usage Guidelines

Use the clear bgp ipv6 unicast flap-statistics command to clear BGP IPv6 unicast connection route-flap statistics.

1.38.6   Examples

The following example clears the unicast connection route-flap statistics for the BGP IPv6 address 172.29.32.129/10:

[local]SE1#clear bgp ipv6 unicast flap-statistics 172.29.32.129/30

The following example clears the unicast connection route-flap statistics for BGP IPv6 routes that match the AS paths 64137 and 14207:

[local]SE1#clear bgp ipv6 unicast flap-statistics 64137 14207

1.39   clear bgp ipv6 unicast message-statistics

1.39.1   Purpose

Clears message statistics for Border Gateway Protocol (BGP) IP Version 6 (IPv6) unicast routes.

1.39.2   Command Mode

exec (10)

1.39.3   Syntax Description

1.39.4   Default

None

1.39.5   Usage Guidelines

Use the clear bgp ipv6 unicast message-statistics command to clear message statistics for BGP IPv6 unicast routes.

1.39.6   Examples

The following example clear message statistics for all BGP IPv6 unicast routes:

[local]SE1#clear bgp ipv6 unicast message-statistics 

1.40   clear bgp ipv6 unicast neighbor

1.40.1   Purpose

Resets or forces Border Gateway Protocol (BGP) updates for the specified BGP IP Version 6 (IPv6) neighbor connection.

1.40.2   Command Mode

exec (10)

1.40.3   Syntax Description

1.40.4   Default

None

1.40.5   Usage Guidelines

Use the clear bgp ipv6 unicast neighbor command to reset or force BGP updates for the specified BGP IPv6 neighbor unicast connection.

1.40.6   Examples

The following example reset or force BGP updates for the BGP IPv6 neighbor unicast connection whose IP address is 120.19.18.193

[local]SE1#clear bgp ipv6 unicast neighbor 120.19.18.193  

1.41   clear bgp ipv6 unicast peer-group

1.41.1   Purpose

Resets or forces Border Gateway Protocol (BGP) updates for the specified BGP IP Version 6 (IPv6) unicast connection with the specified peer group without dropping the connection.

1.41.2   Command Mode

exec (10)

1.41.3   Syntax Description

1.41.4   Default

None

1.41.5   Usage Guidelines

Use the clear bgp ipv6 unicast peer-group command to reset or force BGP updates for the specified BGP IPv6 unicast connection with the specified peer group without dropping the connection.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.41.6   Examples

The following example resets the unicast connection with the peer group called groupA:

[local]SE1#clear bgp ipv6 unicast peer-group groupA 

1.42   clear bgp ipv6 vpn *

1.42.1   Purpose

Resets or forces updates for all Border Gateway Protocol (BGP) VPN neighbor connections that use IP Version 6 (IPv6) address prefixes without dropping the connection.

1.42.2   Command Mode

exec (10)

1.42.3   Syntax Description

1.42.4   Default

None

1.42.5   Usage Guidelines

Use the clear bgp ipv6 vpn * command to reset or force updates for all BGP VPN neighbor connections that use IPv6 address prefixes without dropping the connection.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.42.6   Examples

The following example forces the reset of all BGP VPN connections using IPv6 address prefixes:

[local]SE1#clear bgp ipv6 vpn * soft 

The following example forces the reset of all outbound BGP VPN connections using IPv6 address prefixes:

[local]SE1#clear bgp ipv6 vpn * soft out

1.43   clear bgp ipv6 vpn as

1.43.1   Purpose

Resets or forces Border Gateway Protocol (BGP) inbound updates to be generated for BGP IPv6 VPN neighbor connections in the specified autonomous system number (ASN) without dropping the connection.

1.43.2   Command Mode

exec (10)

1.43.3   Syntax Description

1.43.4   Default

None

1.43.5   Usage Guidelines

Use the clear bgp ipv6 vpn as command to reset or force BGP inbound updates to be generated for BGP IPv6 VPN neighbor connections in the specified autonomous system number (ASN) without dropping the connection.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.43.6   Examples

The following example resets or forces BGP inbound updates to be generated for BGP IPv6 VPN neighbor connections in the ASN 600:

[local]SE1#clear bgp ipv6 vpn ipv6 as 600 soft in

1.44   clear bgp ipv6 vpn external

1.44.1   Purpose

Resets or forces Border Gateway Protocol (BGP) updates for all external IP Version 6 (IPv6) BGP neighbor VPN connections.

1.44.2   Command Mode

exec (10)

1.44.3   Syntax Description

1.44.4   Default

None

1.44.5   Usage Guidelines

Use the clear bgp ipv6 vpn external command to reset or force BGP updates for all external IPv6 BGP neighbor VPN connections.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.44.6   Examples

The following example resets or forces BGP updates for all external IPv6 BGP neighbor VPN connections:

[local]SE1#clear bgp ipv6 vpn external soft

1.45   clear bgp ipv6 vpn flap-statistics

1.45.1   Purpose

Clears Border Gateway Protocol (BGP) IP Version 6 (IPv6) VPN connection route-flap statistics.

1.45.2   Command Mode

exec (10)

1.45.3   Syntax Description

1.45.4   Default

None

1.45.5   Usage Guidelines

Use the clear bgp ipv6 vpn flap-statistics command to clear BGP IPv6 VPN connection route-flap statistics.

1.45.6   Examples

The following example clears the VPN connection route-flap statistics for the BGP IPv6 address 172.29.32.129/10:

[local]SE1#clear bgp ipv6 vpn flap-statistics 172.29.32.129/30

The following example clears the VPN connection route-flap statistics for BGP IPv6 routes that match the AS paths 64137 and 14207:

[local]SE1#clear bgp ipv6 vpn flap-statistics 64137 14207

1.46   clear bgp ipv6 vpn message-statistics

1.46.1   Purpose

Clears message statistics for Border Gateway Protocol (BGP) IP Version 6 (IPv6) VPN routes.

1.46.2   Command Mode

exec (10)

1.46.3   Syntax Description

1.46.4   Default

None

1.46.5   Usage Guidelines

Use the clear bgp ipv6 command to clear message statistics for BGP IPv6 VPN routes.

1.46.6   Examples

The following example clear message statistics for all BGP IPv6 VPN routes:

[local]SE1#clear bgp ipv6 vpn message-statistics 

1.47   clear bgp ipv6 vpn neighbor

1.47.1   Purpose

Resets or forces Border Gateway Protocol (BGP) updates for the specified BGP IP Version 6 (IPv6) neighbor connection.

1.47.2   Command Mode

exec (10)

1.47.3   Syntax Description

1.47.4   Default

None

1.47.5   Usage Guidelines

Use the clear bgp ipv6 vpn neighbor command to reset or force BGP updates for the specified BGP IPv6 neighbor VPN connection.

1.47.6   Examples

The following example reset or force BGP updates for the BGP IPv6 neighbor VPN connection whose IP address is 120.19.18.193:

[local]SE1#clear bgp ipv6 vpn neighbor 120.19.18.193  

1.48   clear bgp ipv6 vpn peer-group

1.48.1   Purpose

Resets or forces Border Gateway Protocol (BGP) updates for the specified BGP IP Version 6 (IPv6) VPN connection with the specified peer group without dropping the connection.

1.48.2   Command Mode

exec (10)

1.48.3   Syntax Description

1.48.4   Default

None

1.48.5   Usage Guidelines

Use the clear bgp ipv6 vpn peer-group command to reset or force BGP updates for the specified BGP IPv6 VPN connection with the specified peer group without dropping the connection.

Note:  

The soft keyword works only if the peer router advertises the route-refresh capability.

1.48.6   Examples

The following example resets the VPN connection with the peer group called groupA:

[local]SE1#clear bgp ipv6 vpn peer-group groupA 

1.49   clear bgp message-statistics

1.49.1   Purpose

Clears Border Gateway Protocol (BGP) message statistics.

1.49.2   Command Mode

exec (10)

1.49.3   Syntax Description

1.49.4   Default

None

1.49.5   Usage Guidelines

Use the clear bgp message-statistics command to clear BGP message statistics.

1.49.6   Examples

The following example clears BGP message statistics:

[local]Redback#clear bgp message-statistics

1.50   clear bgp neighbor

1.50.1   Purpose

Resets Border Gateway Protocol (BGP) neighbor connections or forces BGP updates to be generated without dropping the connections.

1.50.2   Command Mode

exec (10)

1.50.3   Syntax Description

1.50.4   Default

None

1.50.5   Usage Guidelines

Use the clear bgp neighbor command to reset BGP neighbor connections or force BGP updates to be generated for connections without causing a hard reset (which drop connections immediately).

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.50.6   Examples

The following example causes a hard reset in which the connection to the BGP neighbor at IP address, 10.11.48.170, is immediately dropped:

[local]Redback#clear bgp neighbor 10.11.48.170

 Jan 5 19:32:02: %BGP-6-INFO: 10.11.48.170 DOWN - User action
 Jan 5 19:32:07: %BGP-6-INFO: 10.11.48.170 UP

The following example displays output from the show bgp neighbor summary command:

[local]Redback>show bgp neighbor summary
BGP router identifier: 1.1.1.71, local AS number: 64001
Neighbors Configured: 10, Established: 9
Neighbor      AS     MsgRcvd   MsgSent InQ OutQ Reset Up/Down  State
10.11.64.170  64001  45        55        0    0     1 01:32:17 Connect
CapSent : refresh restart unicast

1.51   clear bgp peer-group

1.51.1   Purpose

Resets Border Gateway Protocol (BGP) peer group connections or forces BGP updates to be generated without dropping the connections.

1.51.2   Command Mode

exec (10)

1.51.3   Syntax Description

1.51.4   Default

None

1.51.5   Usage Guidelines

Use the clear bgp peer-group command to reset BGP peer group connections or force BGP updates to be generated for connections without causing a hard reset (which drop connections immediately).

Note:  

Prior to Release 2.5, when there was a change in an inbound or outbound routing policy, such as a prefix list, autonomous system (AS) path list, or route map, for a BGP peer, the clear bgp neighbor ip-addr soft [in | out] command had to be manually issued to make the policy change effective. Currently, routing policy changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command to update routing policies can cause updates to be unnecessarily sent; therefore, it is not recommended.

To aggregate multiple policy changes, the operating system performs the necessary action 15 seconds after a policy change.

1.51.6   Examples

The following example resets the connection with peer group, groupA:

[local]Redback#clear bgp peer-group groupA

1.52   clear bridge loop-detection

1.52.1   Purpose

Unblocks all circuits on the specified bridge that are blocked by MAC moves loop detection and clears the bridge MAC moves loop-detection counters.

1.52.2   Command Mode

exec

1.52.3   Syntax Description

1.52.4   Default

None

1.52.5   Usage Guidelines

Use the clear bridge loop-detection command to unblock all circuits on the specified bridge that are blocked by MAC moves loop detection and clears the bridge MAC moves loop-detection counters.

1.52.6   Examples

The following example unblocks all circuits in the brdgrp1 bridge:

[local]Redback#clear bridge loop-detection brdgrp1 all

1.53   clear bridge table

1.53.1   Purpose

Clears the bridge table for the specified bridge.

1.53.2   Command Mode

exec

1.53.3   Syntax Description

1.53.4   Default

None

1.53.5   Usage Guidelines

Use the clear bridge table command to clear the bridge table for the specified bridge.

1.53.6   Examples

The following example clears the bridge table for the isp1 bridge:

[local]Redback#clear bridge table isp1

1.54   clear circuit counters

1.54.1   Purpose

Clears circuit counters for one or more circuits in the system.

1.54.2   Command Mode

exec (10)

1.54.3   Syntax Description

1.54.4   Default

Clears circuit counters for all circuits of all types in the system.

1.54.5   Usage Guidelines

Use the clear circuit counters command to clear circuit counters.

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

Table 4 lists the values for the circuit-type argument.

Note:  

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

If you enter the optional slot, port, or chan-num arguments, the command clears the counters for the specified card, port, or channel; if you enter the optional sub-chan-num argument, the command clears the counters for the DS-1 channel or the DS-0 channel group.

Note:  

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

Note:  

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

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

If you enter the optional circuit-id argument, the command clears the counters for the specified circuit.

If you specify the VLAN tag value for an 802.1Q tunnel, the command clears the counters for all the PVCs within the tunnel.

If you enter the optional circuit-type argument, the command clears the counters for all circuits of the specified type.

1.54.6   Examples

The following example clears all Cisco HDLC circuit counters on port 1 in slot 6:

[local]Redback#clear circuit counters 6/1 chdlc

1.55   clear circuit counters vpls

1.55.1   Purpose

Clears circuit counters for Virtual Private LAN Services (VPLS) circuits in the system.

1.55.2   Command Mode

exec (10)

1.55.3   Syntax Description

1.55.4   Default

None

1.55.5   Usage Guidelines

Use the clear circuit counters vpls command to clear circuit counters for VPLS circuits in the system.

Use the clear circuit counters vpls circuit-id command to clear circuit counters for a single VPLS circuit. You can use the show vpls peer command (in any mode) to display a list of all VPLS circuit IDs.

1.55.6   Examples

The following example clears all VPLS-related circuit counters:

[local]Redback>clear circuit counters vpls

The following example clears circuit counters for the VPLS circuit, 1250:

[local]Redback>clear circuit counters vpls 1250

1.56   clear circuit loop-detection

1.56.1   Purpose

Disables MAC moves loop detection on the specified circuits.

1.56.2   Command Mode

exec

1.56.3   Syntax Description

1.56.4   Default

none

1.56.5   Usage Guidelines

Use the clear circuit loop-detection command to disable MAC moves loop detection on the specified circuits. If blocked, the circuits are unblocked and their loop-detection counters cleared.

The circuit-id argument is composed of the keywords and arguments as described in the following syntax:

slot/port {vpls vpls-id | vlan vlan-id}

Table 5 describes the components of the circuit-id argument:

1.56.6   Examples

The following example disables MAC moves loop detection on the VPLS 1225 circuit in slot 2, port 1:

[local]Redback#clear bridge loop-detection 2/1 vpls 1225

1.57   clear clips counters

1.57.1   Purpose

Clears clientless IP service selection (CLIPS) counters.

1.57.2   Command Mode

exec (10)

1.57.3   Syntax Description

This command has no keywords or arguments.

1.57.4   Default