Contents

1   Command Descriptions

Commands starting with “o” through commands starting with “po” are included.

1.1   oam fault-monitor

1.1.1   Purpose

Enables alarm indication signal (AIS) and remote defect indication (RDI) fault monitoring for any Asynchronous Transfer Mode (ATM) permanent virtual circuit (PVC) that references this profile and is not cross-connected.

1.1.2   Command Mode

• ATM profile configuration

1.1.3   Syntax Description

1.1.4   Default

Fault monitoring is disabled.

1.1.5   Usage Guidelines

Use the oam fault-monitor command to enable AIS and RDI fault monitoring of any ATM PVC that references this profile.

In compliance with the ITU standard, AIS is used to report faults in the upstream (forward) direction; RDI is used to report faults in the downstream (backward) direction.

If you reference this profile when configuring an ATM PVC that is later cross-connected, this command is disabled (ignored) in the profile.

Note:  

For more configuration guidelines for ATM profiles, VPs, and PVCs with regard to fault monitoring, see ATM Configuration Guidelines in Configuring Circuits.

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

1.1.6   Examples

The following example shows how to enable fault monitoring for an ATM profile, oam:

[local]Redback(config)#atm profile oam
[local]Redback(config-atm-profile)#oam fault-monitor end-to-end

1.2   oam manage

1.2.1   Purpose

Enables the operational state of any Asynchronous Transfer Mode (ATM) permanent virtual circuit (PVC) that is not cross-connected and that references this profile to be controlled by the state of its remote defect indication (RDI) and alarm indication signal (AIS) state at the F5 level.

1.2.2   Command Mode

ATM profile configuration

1.2.3   Syntax Description

1.2.4   Default

OAM management is disabled.

1.2.5   Usage Guidelines

Use the oam manage command to enable the operational state of any ATM PVC that references this profile to be controlled by the state of its RDI and AIS state at the F5 level. If the F5 RDI and AIS state is active, the operational state of the ATM PVC is down; if F5 RDI and AIS state is not active, the operational state is up.

If you reference this profile when configuring an ATM PVC that is later cross-connected, this command is disabled (ignored) in the profile.

Use the heartbeat keyword to enable continuity monitoring. Cells are issued repetitively with a periodicity of one cell each second independently of user cell traffic. After enabling continuity monitoring, if the PVC does not receive any monitoring cell within a time interval of 3.5 seconds, with a margin of ±.5 seconds, from a peer that is configured with continuity checking (heartbeat backward), the system declares a VP-AIS or a virtual circuit (VC)-AIS (or both) state due to a loss of continuity.

Use the auto-loopback keyword to cause the system to detect and clear the RDI/AIS state by using OAM F4 and F5 loopback cells to be periodically transmitted and its response cells monitored when appropriate.

If you specify either the heartbeat or the auto-loopback keyword, the operational state is controlled by both RDI/AIS, and either continuity check cells or ATM OAM loopback cells.

If you specify neither the heartbeat nor the auto-loopback keyword, OAM management is enabled with only the fault monitoring function.

In every case, the system monitors and reacts to an RDI/AIS state by declaring the ATM PVC down and sending an Simple Network Management Protocol (SNMP) trap.

Note:  

By default, because an ATM PVC is enabled when you create it, OAM management is in effect for any ATM PVC that references a profile that includes the oam manage command. However, if you disable the ATM PVC with the shutdown command (in ATM PVC configuration mode), then OAM management is not in effect. You must enable the ATM PVC with the no shutdown command (in ATM PVC configuration mode) for OAM management to determine the state of the ATM PVC.

Note:  

For more configuration guidelines for ATM profiles, VPs, and PVCs with regard to OAM, see ATM Configuration Guidelines in Configuring Circuits.

Use the no or default form of this command to disable OAM management of any ATM PVC that references this profile.

To display the values of the auto-loopback parameters and the ATM PVC status, enter the show atm pvc command (in any mode).

1.2.6   Examples

The following example shows how to enable the operational state of any ATM PVC that references the oam profile to be controlled by both the state of its RDI/AIS and by OAM loopback:

[local]Redback(config)#atm profile oam
[local]Redback(config-atm-profile)#oam manage end-to-end auto-loopback
 regular-timeout 45

1.3   oam xc

1.3.1   Purpose

Enables operations, administration, and maintenance (OAM) cells received on one of a pair of cross-connected Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs) that reference this profile to be forwarded to and transmitted on the other ATM PVC.

1.3.2   Command Mode

• ATM profile configuration

1.3.3   Syntax Description

1.3.4   Default

No OAM cells are forwarded

1.3.5   Usage Guidelines

Use the oam xc command to enable the OAM cells received on one of a pair of cross-connected ATM PVCs that reference this profile to be forwarded to and transmitted on the other ATM PVC.

If you reference this profile when configuring an ATM PVC that is not cross-connected, this command is disabled (ignored) in the profile; if the profile is also configured with either the oam fault-monitor or oam manage command (in ATM profile configuration mode), that command is enabled instead. If the ATM PVC is cross-connected at a later time, this command in the profile is enabled and either the oam fault-monitor or oam manage command is disabled.

Note:  

For more configuration guidelines for ATM profiles, VPs, and PVCs with regard to OAM, see ATM Configuration Guidelines in Configuring Circuits.

Use the no or default form of this command to disable the forwarding of all OAM cells.

1.3.6   Examples

The following example selectively disables the heartbeat option:

[local]Redback(config)#atm profile oam-xc
[local]Redback(config-atm-profile)#oam xc end-to-end loopback ais/rdi

The following example shows how to enable all OAM cells to be forwarded across the cross-connection of two ATM PVCs on ATM OC ports:

[local]Redback(config)#atm profile oam-xc
[local]Redback(config-atm-profile)#oam xc end-to-end loopback heartbeat ais/rdi
[local]Redback(config-atm-profile)#exit
[local]Redback(config)#port atm 3/1
[local]Redback(config-atm-oc)#atm pvc 100 100 profile oam-xc encapsulation raw
[local]Redback(config)#port atm 4/1
[local]Redback(config-atm-oc)#atm pvc 100 100 profile oam-xc encapsulation raw
[local]Redback(config-atm-oc)#exit
[local]Redback(config)#xc 3/1 vpi-vci 100 100 to 4/1 vpi-vci 100 100

1.4   offer-lease-time

1.4.1   Purpose

Specifies the offer lease time for this internal Dynamic Host Configuration Protocol (DHCP) server or one of its subnets.

1.4.2   Command Mode

• DHCP server configuration
• DHCP subnet configuration

1.4.3   Syntax Description

1.4.4   Default

The default value for the offer lease time is two minutes.

1.4.5   Usage Guidelines

Use the offer-lease-time command to specify the offer lease time for the DHCP server or one of its subnets. When entered in DHCP server configuration mode, specifies the offer lease time for the server and all its subnets; when entered in DHCP subnet configuration mode, specifies offer lease time for that subnet. The value specified for a subnet overrides the global value for the server.

Use the no form of this command to specify the default value for the offer lease time.

1.4.6   Examples

The following example specifies an offer lease time of 5 minutes (300) for the DHCP server and all its subnets:

[local]Redback(config)#context dhcp
[local]Redback(config-ctx)#dhcp server policy
[local]Redback(config-dhcp-server)#offer-lease-time 300

1.5   offset-list

1.5.1   Purpose

Configure a Routing Information Protocol (RIP) offset list.

1.5.2   Command Mode

RIP router configuration

1.5.3   Syntax Description

1.5.4   Default

No RIP offset list is configured.

1.5.5   Usage Guidelines

Use the offset-list command to configure a RIP offset list. A RIP offset list adds to the cost metric of inbound or outbound routes learned or advertised by RIP. RIP offset lists provide a method for adding to the cost metric of routes, which moves the routing switch’s route selection away from those routes.

The RIP offset list adds the offset value to the cost metric of all routes that match the specified prefix list.

Use the no form of this command to remove the RIP offset list.

1.5.6   Examples

The following example configures a RIP offset list to add 8 to the cost metric for all routes that match the IP prefix list, foo23:

[local]Redback(config-ctx)#router rip rip001
[local]Redback(config-rip)#offset-list foo23 in 8

1.6   oif-interface

1.6.1   Purpose

Identifies an interface connected to the subscriber device in a PIM-Dual Join implementation.

1.6.2   Command Mode

pim-dual configuration mode

1.6.3   Syntax Description

1.6.4   Default

None

1.6.5   Usage Guidelines

Use the oif-interface command to identify an interface connected to the subscriber device in a PIM-Dual Join implementation.

Use the no form of this command to identify the interface previously set.

1.6.6   Examples

The following example shows how to identify the interface int1 as the interface connected to the subscriber device in a PIM-Dual Join implementation:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#pim dual-join group 225.100.1.1 source 192.110.30.6
[local]Redback(config-pim-dual)#oif-interface int1

1.7   on-demand-diagnostic

1.7.1   Purpose

Places an I/O carrier card, services card, or line card in the on-demand diagnostics (ODD) state.

1.7.2   Command Mode

• card configuration

1.7.3   Syntax Description

This command has no keywords or arguments.

1.7.4   Default

None

1.7.5   Usage Guidelines

Use the on-demand-diagnostic command to place a carrier, line, or services card in the ODD state.

This command is available only for the SmartEdge® 100 I/O carrier card in slot 2 and the following SmartEdge line cards:

• ATM OC-12c/STM-3c, and second-generation ATM OC line cards
• 10/100 Ethernet and Fast Ethernet-Gigabit Ethernet (FE-GE) line cards
• Gigabit Ethernet line cards (any version)
• SONET/SDH OC-3c/STM-1c, OC-12c/STM-4c, OC-48c/STM-16c, and OC-192c/STM-64c line cards

Low-density versions of these line cards are also supported, but only the enabled ports are tested.

You must place the carrier card or line card in the out-of-service state with the shutdown command in ATM OC port configuration mode before you can enter this command. Specify slot 2 when you shut down the carrier card to shut down the I/O functions.

Use the no form of this command to remove the carrier card or line card from the ODD state.

1.7.6   Examples

[local]Redback(config)#card carrier 2
[local]Redback(config-card)#shutdown
[local]Redback(config-card)#on-demand-diagnostic 
[local]Redback(config-card)#end

[local]Redback(config)#card 10ge-1-port 3
[local]Redback(config-card)#shutdown
[local]Redback(config-card)#on-demand-diagnostic 
[local]Redback(config-card)#end

1.8   optimize replication

optimize replication

no optimize replication

1.8.1   Purpose and Usage Guidelines

Enables packet mesh ASIC (PMA)-based traffic replication on the current line card to the destination line cards. When not enabled, packet replication is performed in the ingress packet processing ASICs (iPPAs).

Use the optimize replication command to efficiently support high-bandwidth multicast services such as IPTV.

• This command is only supported on PPA3-based line cards: Gigabit Ethernet 20-port card (ge4-20-port) and 10 Gigabit Ethernet 4-port card (10ge-4-port).
• Mesh-based traffic replication is performed only on traffic sent to PPA3 destination line cards. This command has no effect on multicast traffic sent to PPA2 destination cards.
• All multicast traffic to destination PPA3 cards, belonging to any service (for example, IP routing, Layer-2 bridging), is replicated using the packet mesh.
• A maximum of two line cards in a system can be set to optimize replication. For example, you could assign two uplink (or trunk) ports carrying IPTV traffic for distribution among downlink ports.
• On the packet mesh, the queue and backplane priority of optimized multicast traffic is fixed at priority 1, which is just above the Differentiated Services Code Point (DSCP) value of unicast AF4 class (CS4) (IP precedence 4 FlashOver).
• Enabling or disabling this command causes traffic interruption of less than 1 second on the card.

1.8.2   Command Mode

card configuration

1.8.3   Syntax Description

This command has no arguments.

1.8.4   Default

Packet replication is performed on the ingress PPA. Use the no form of this command to return the card to the default condition.

1.8.5   Examples

[local]redback#card 10ge-4-port
[local]redback(config-card)# optimize replication

1.9   option

1.9.1   Purpose

Specifies an option for this internal Dynamic Host Configuration Protocol (DHCP) server or one of its subnets.

1.9.2   Command Mode

• DHCP server configuration
• DHCP subnet configuration

1.9.3   Syntax Description

1.9.4   Default

No DHCP options are specified for the DHCP server or for any of its subnets.

1.9.5   Usage Guidelines

Use the option command to specify an option for this internal DHCP server or for one of its subnets. When you enter this command in DHCP server configuration mode, it specifies the DHCP option for the server and all its subnets; when you enter it in DHCP subnet configuration mode, it specifies the option for that subnet. The value specified for a subnet overrides the global value for the server.

You can enter this command multiple times to specify as many different DHCP options as you require. Succeeding entries for the same DHCP option overwrite any previously entered value.

You can specify up to four IP addresses for a DHCP option that requires an IP address. If the DHCP option also requires an netmask argument in addition to the IP address, you can specify up to two IP addresses and their netmask arguments.

RFC 2132, DHCP Options and BOOTP Vendor Extensions, Section 3 through Section 9 describe the option numbers, names, and arguments. Table 1 to Table 7 list this data for the options in each section; options are listed by code within each table.

Use the no form of this command to remove the option from the internal DHCP server or subnet configuration.

Note:  

DHCP can send RADIUS-specified vendor-encapsulated options to the DHCP client. RADIUS sends the vendor-encapsulated options using the vendor-specific attribute (VSA) 127 (DHCP-Vendor-Encap-Options) provided by Ericsson AB. For more information about the format for VSA 127, see Redback VSAs Supported by the SmartEdge Router in RADIUS Attributes.

(1)  RFC 894, Standard for the Transmission of IP Datagrams over Ethernet Networks

(2)  RFC 1042, Standard for the Transmission of IP Datagrams over IEEE 802 Ethernet Networks

(1)  RFC 1001, Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Concepts and Methods

(2)  RFC 1002, Protocol Standard for a NetBIOS Service on a TCP/UDP transport: Detailed Specifications

1.9.6   Examples

The following example specifies the options for an internal DHCP server (and its subnets), which are overridden by the options for the sub2 subnet:

[local]Redback(config)#context dhcp
[local]Redback(config-ctx)#dhcp server policy

! Specify global options (these apply to all subnets)

[local]Redback(config-dhcp-server)#option domain-name redback.com
[local]Redback(config-dhcp-server)#option domain-name-server 10.1.1.254

! Create a subnet; specify options for this subnet, which override the global settings

[local]Redback(config-dhcp-server)#subnet 10.1.1.1/24 name sub2
[local]Redback(config-dhcp-subnet)#option router 10.1.1.1
[local]Redback(config-dhcp-subnet)#option domain-name hot.com

The following example adds a second IP address for the router option in the sub2 subnet configuration and includes option 21 (policy-filter) with two IP addresses and their netmasks:

[local]Redback(config)#context dhcp
[local]Redback(config-ctx)#dhcp server policy
[local]Redback(config-dhcp-server)#subnet 10.1.1.1/24 name sub2
[local]Redback(config-dhcp-subnet)#option router 10.1.1.1 10.1.1.2

[local]Redback(config-dhcp-subnet)#option 21 10.1.1.23 255.255.255.255 
10.1.1.33 255.255.255.255

1.10   option-82

1.10.1   Purpose

Creates a static mapping between the Agent-Circuit-Id subfield or the Agent-Remote-Id subfield in the option 82 field and an IP address.

1.10.2   Command Mode

• DHCP subnet configuration

1.10.3   Syntax Description

1.10.4   Default

No static mapping is created between an option 82 subfield and any IP address.

1.10.5   Usage Guidelines

Use the option-82 command to create a static mapping between the Agent-Circuit-Id subfield or the Agent-Remote-Id subfield in the option 82 field and an IP address. The option 82 field is sent in the DHCP discover packet.

The value for the ip-addr argument must be an IP address within this subnet, but not within any range of IP addresses that you have specified using the range command (in DHCP subnet configuration mode).

You can specify the remote agent ID and the circuit agent ID in vendor-specific attributes (VSAs) 96 and 97, respectively, using the radius attribute calling-station-id and radius attribute nas-port-id commands (in context configuration mode). vendor VSAs provided by Ericsson AB are described in RADIUS Attributes.

Use the no form of this command to delete the static mapping.

1.10.6   Examples

The following example creates a static mapping between option 82 Agent-Circuit-Id subfield, 4:1 vlan 102, and the 12.1.1.11 IP address:

[local]Redback(config)#context dhcp
[local]Redback(config-ctx)#dhcp server policy
[local]Redback(config-dhcp-server)#subnet 12.1.1.0/24 name sub2
[local]Redback(config-dhcp-subnet)#range 12.1.1.50 12.1.1.100
[local]Redback(config-dhcp-subnet)#mac-address 02:12:34:56:78:90 ip-address 12.1.1.10
[local]Redback(config-dhcp-subnet)#option-82 circuit-id “4:1 vlan 102” offset 3 ip-address 12.1.1.11

1.11   option domain name-server

1.11.1   Purpose

In a DHCPv6 server policy, specifies the IP address of the DNS name server to be used by clients for DNS hostname resolution.

1.11.2   Command Mode

DHCPv6 server policy configuration

DHCPv6 server policy subnet configuration

1.11.3   Syntax Description

1.11.4   Default

No DNS name server is specified in the DHCPv6 profile.

1.11.5   Usage Guidelines

Use the option domain-name-server command to specify the IPv6 address of the DNS name server to be used by IPv6 clients for DNS hostname resolution.

Use the no version of this command to remove a DNS name server from a DHCPv6 profile.

1.11.6   Examples

The following example configures a DHCPv6 server policy to direct clients to use the DNS name server on the IPv6 address 2005:db8:b:3f::2 for DNS hostname resolution:

[local]BRAS(config-ctx)#dhcpv6 server

[local]Redback(config-dhcpv6-server)#option domain-name-server 2005:db8:b:3f::2

1.12   option domain-search

1.12.1   Purpose

In a DHCPv6 server policy, specifies the domain name that a host appends to a hostname for DNS hostname resolution.

1.12.2   Command Mode

DHCPv6 server policy configuration

DHCPv6 server policy subnet configuration

1.12.3   Syntax Description

1.12.4   Default

No DNS name server is specified in the DHCPv6 server policy.

1.12.5   Usage Guidelines

Use the option domain-search command to specify the domain name that a host appends to a hostname for DNS hostname resolution.

Use the no version of this command to remove a specified domain name from a DHCPv6 server policy.

1.12.6   Examples

The following example configures the domain search option in a DHCPv6 server policy. In this example, the domain name SJ1.com is appended to hostnames queried for DNS resolution:

[local]BRAS(config-ctx)#dhcpv6 server

[local]Redback(config-dhcpv6-server)#option domain-search SJ1.com

1.13   option information-refresh-time

1.13.1   Purpose

In a DHCPv6 server policy, configures the number of seconds a client waits before refreshing the configuration information received from DHCPv6 server.

1.13.2   Command Mode

DHCPv6 server policy configuration

1.13.3   Syntax Description

1.13.4   Default

The number of seconds a client waits before refreshing the configuration information received from DHCPv6 server is not specified.

1.13.5   Usage Guidelines

Use the option information-refresh-time command to configure the number of seconds a client waits before refreshing the configuration information received from DHCPv6 server.

Use the no version of this command to return the DHCPv6 server policy refresh time attribute to the default configuration, where the number of seconds a client waits before refreshing the configuration information received from DHCPv6 server is not specified.

1.13.6   Examples

The following example configures the refresh time attribute in a DHCPv6 server policy to be 3000000 seconds. This means clients of this server refresh the configuration information received from this server every 3000000 seconds:

[local]BRAS(config-ctx)#dhcpv6 server

[local]Redback(config-dhcpv6-server)#option information-refresh-time 3000000

1.14   option preference

1.14.1   Purpose

In a DHCPv6 server policy, configures the preference value for a DHCPv6 server.

1.14.2   Command Mode

DHCPv6 server policy configuration

1.14.3   Syntax Description

1.14.4   Default

The preference value for a DHCPv6 server is not specified.

1.14.5   Usage Guidelines

Use the option preference command to configure the preference value for a DHCPv6 server.

A DHCPv6 server configured with a lower value is preferred over a server configured with a higher value.

When a client requests an IPv6 prefix, that client typically accepts the first IPv6 prefix it receives. However, you can configure a DHCPv6 server to be preferred so that the client accepts IPv6 prefixes from that server over any other DHCPv6 server.

Use the no version of this command to return the DHCPv6 server preference attribute to the default value.

1.14.6   Examples

The following example configures the preference attribute for a DHCPv6 server to be 5:

[local]Redback(config-ctx)#dhcpv6 server

[local]Redback(config-dhcpv6-server)#option preference 5

1.15   option rapid-commit

1.15.1   Purpose

Enables RAPID COMMIT in a DHCPv6 server policy (for faster IPv6 prefix delegation).

1.15.2   Command Mode

DHCPv6 server policy configuration

1.15.3   Syntax Description

This command has no keywords or arguments.

1.15.4   Default

RAPID COMMIT is disabled.

1.15.5   Usage Guidelines

Use the option rapid-commit command to enable RAPID COMMIT in a DHCPv6 server policy (for faster IPv6 prefix delegation).

Note:  

With the RAPID COMMIT option, only two messages (SOLICIT and REPLY messages) are exchanged between the DHCPv6 server and the CPE. The RAPID COMMIT option is typically used when there is only one server for a CPE to connect to.

Use the no version of this command to disable RAPID COMMIT in a DHCPv6 server policy.

1.15.6   Examples

The following example enables RAPID COMMIT in a DHCPv6 server policy:

[local]Redback(config-ctx)#dhcpv6 server

[local]Redback(config-dhcpv6-server)#option rapid-commit

1.16   optional-checksums

1.16.1   Purpose

Enables optional Intermediate System-to-Intermediate System (IS-IS) checksums on the interface.

1.16.2   Command Mode

IS-IS interface configuration

1.16.3   Syntax Description

1.16.4   Default

The command is disabled.

1.16.5   Usage Guidelines

Use the optional-checksums command to enable optional IS-IS checksums on the interface.

Use the no form of this command to disable optional IS-IS checksums.

1.16.6   Examples

The following example enables optional checksums 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))#optional-checksums

1.17   originate-default

1.17.1   Purpose

Originates the default route advertisement in the Open Shortest Path First (OSPF) or OSPF Version 3 (OSPFv3) routing domain.

1.17.2   Command Mode

• OSPF router configuration
• OSPF3 router configuration

1.17.3   Syntax Description

1.17.4   Default

No default route is originated. When this command is used to originate a default route, the metric value is 1.

1.17.5   Usage Guidelines

Use the originate-default command to originate the default route advertisement in the OSPF or OSPFv3 routing domain.

Use the no form of this command to remove the default route.

1.17.6   Examples

The following example configures the OSPF instance to originate a default route when there is a route in the RIB for routes matching the rmap01 route map:

[local]Redback(config-ospf)#originate-default route-map rmap01

1.18   originating-rp

1.18.1   Purpose

Configures an interface as the originating rendezvous point (RP) address.

1.18.2   Command Mode

MSDP router configuration

1.18.3   Syntax Description

1.18.4   Default

None

1.18.5   Usage Guidelines

Use the originating-rp command to configure an interface as the originating RP address. The IP address of the interface is used as the RP address in all source active (SA) messages originated by the router.

Use the no form of this command to remove the interface’s IP address for the originating RP address.

1.18.6   Examples

The following example configures the interface, ToLan04, to be used as the RP address:

[local]Redback(config-msdp)#originating-rp ToLan04

1.19   originating-rp sa-filter

1.19.1   Purpose

Configures an access control list (ACL) to filter incoming source active (SA) messages learned from the local rendezvous point (RP).

1.19.2   Command Mode

MSDP router configuration

1.19.3   Syntax Description

1.19.4   Default

None

1.19.5   Usage Guidelines

Use the originating-rp sa-filter command to configure an ACL to filter incoming SA messages learned from the local RP.

Use the no form of this command to remove the ACL.

1.19.6   Examples

The following example configures ACL 320 to filter incoming SA messages:

[local]Redback(config-ctx)#router msdp
[local]Redback(config-msdp)#originating-rp sa-filter 320

1.20   out-label

1.20.1   Purpose

Configures the outgoing label number for a static label-switched path (LSP).

1.20.2   Command Mode

MPLS static LSP configuration

1.20.3   Syntax Description

1.20.4   Default

None

1.20.5   Usage Guidelines

Use the out-label command to configure the outgoing label number for a static LSP.

1.20.6   Examples

The following example configures the outgoing label for the LSP, test14, to the value of 20:

[local]Redback(config-ctx)#router mpls-static
[local]Redback(config-mpls-static)#lsp test14
[local]Redback(config-mpls-static-lsp)#out-label 20

1.21   output-delay

1.21.1   Purpose

Adds a delay time between packets sent in multipacket Routing Information Protocol (RIP) or RIP next generation (RIPng) updates.

1.21.2   Command Mode

• RIPng router configuration
• RIP router configuration

1.21.3   Syntax Description

1.21.4   Default

Packets are sent without a delay.

1.21.5   Usage Guidelines

Use the output-delay command to add a delay time between packets in multipacket RIP or RIPng updates.

Note:  

This feature is useful for situations where a high-speed router is sending updates to a low-speed router.

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

1.21.6   Examples

The following example adds a delay time of 15 milliseconds between the sending of updates for the RIP instance, rip001:

[local]Redback(config-ctx)#router rip rip001
[local]Redback(config-rip)#output-delay 15

1.22   over-subscription-factor

1.22.1   Purpose

For Constrained Shortest Path First (CSPF), specifies the factor by which the bandwidth can exceed the subscribed amount for Resource Reservation Protocol (RSVP)-enabled interfaces.

1.22.2   Command Mode

• RSVP router configuration

1.22.3   Syntax Description

1.22.4   Default

100 percent.

1.22.5   Usage Guidelines

Use the over-subscription-factor command to specify the factor by which the bandwidth can exceed the subscribed amount for RSVP-enabled interfaces. This factor is multiplied by the available bandwidth to reserve the oversubscription amount. For example, if the hardware bandwidth for a Fast Ethernet port is 100 mbps and the oversubscription factor is 150 percent, the reserved bandwidth is 150 mbps. If you do not specify a bandwidth, the reserved bandwidth (the default value) is available. If bandwidth has been explicitly reserved (using the bandwidth command in RSVP interface configuration mode), that setting overrides this calculation.

To undersubscribe RSVP-enabled interfaces, set a value below 100 percent. To oversubscribe RSVP-enabled interfaces, set a value above 100 percent.

Note:  

The bandwidth command in the RSVP interface configuration mode overrides the over-subscription-factor command for the particular interface.

Use the no form of this command to remove the oversubscription-factor bandwidth value.

1.22.6   Examples

The following example shows how to configure the oversubscription-factor on an interface to 110 percent:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#router rsvp
[local]Redback(config-rsvp)#over-subscription-factor 110

1.23   over-subscription-rate

1.23.1   Purpose

Specifies the oversubscription rate allowed on an Asynchronous Transfer Mode (ATM) OC port.

1.23.2   Command Mode

• ATM OC configuration

1.23.3   Syntax Description

1.23.4   Default

The default rate is unlimited.

1.23.5   Usage Guidelines

Use the over-subscription-rate command to specify the oversubscription rate allowed on an ATM OC port.

A rate of 0% allows permanent virtual circuits (PVCs) to be created on the port up to the bandwidth of the port; a rate of 1,000% allows PVCs to be created on the port up to the bandwidth of the port +1000%.

Use the no form of this command to specify a rate of 0%.

Use the default form of this command to specify the default rate.

1.23.6   Examples

The following example shows how to specify an oversubscription rate of 100% for port 1 of the ATM OC-3c/STM-1c line card in slot 4:

[local]Redback(config)#port atm 4/1
[local]Redback(config-atm-oc)#over-subscription-rate 100

With framing bits taken into account, the ATM OC-3c/STM-1c port has a bandwidth of 149.76 Mbps. With an oversubscription rate of 100%, PVCs can be created up to a bandwidth of 299.52 Mbps on this port.

1.24   p2p-port

1.24.1   Purpose

Treats the associated port as always connected to a point-to-point link.

1.24.2   Command Mode

• spanning-tree profile configuration

1.24.3   Syntax Description

This command has no keywords or arguments.

1.24.4   Default

Depending on the type of port, the port is treated as either a full-duplex or half-duplex link.

1.24.5   Usage Guidelines

Use the p2p-port command to treat the associated port as always connected to a point-to-point link; that is, enable the port for full-duplex operation.

1.24.6   Examples

The following example illustrates how the spanning-tree profile command creates the spanning-tree profile womp and enables it for point-to-point linking. In the second part of the example, an Ethernet port is assigned the spanning-tree profile womp and, therefore, is enabled for point-to-point linking:

[local]Redback(config)#spanning-tree profile womp
[local]Redback(config-stp-prof)#p2p-port
[local]Redback(config-stp-prof)#exit
[local]Redback(config)#port ethernet 1/1
[local]Redback(config-port)#spanning-tree profile womp

1.25   packet-interval

1.25.1   Purpose

Specifies the sampling interval for packets.

1.25.2   Command Mode

flow IP sampling configuration

1.25.3   Syntax Description

1.25.4   Default

None.

1.25.5   Usage Guidelines

Use the packet-interval command to specify the sampling interval for packets. When random sampling is enabled with the sampling command, statistics are gathered for packets based on the packet interval. For example, if you configured the packet interval to be 9, then statics are gathered for one random packet out of every nine packets. The sampling counter restarts when the ninth packet is processed.

1.25.6   Examples

The following example shows how to use the packet-interval command to configure the sampling interval to be 100. In this example, statistics are gathered for one random packet out of every 100 packets:

local]Redback# configure
[local]Redback(config)# flow ip sampling
[local]Redback(config-flow-ip-sampling)# packet-interval 100

1.26   parameter

1.26.1   Purpose

Specifies a field in a service condition that can be dynamically changed.

1.26.2   Command Mode

• service profile configuration

1.26.3   Syntax Description

1.26.4   Default

No fields are defined in a service profile.

1.26.5   Usage Guidelines

Use the parameter command to specify a field in a service condition that can be dynamically changed. You can also use the parameter command to specify one of the predefined parameter names that is used to support dynamic class assignment. The maximum number of parameter instances in a service profile is 16; a parameter instance is each occurrence of the command in service profile configuration mode and each occurrence of the command for an array of parameter values in parameter array loop configuration mode.

For example, if the parameter value command appears twice in service profile configuration mode and once in parameter array loop configuration mode for a parameter with four values, the number of parameter instances is six.

Specify a value for each default-value argument if the subscriber configuration on the RADIUS server need not include this field. If the field is mandatory (the value must be specified in the subscriber configuration on the RADIUS server), do not specify a default value.

Use the attribute command (in service profile configuration mode) to specify the attribute that includes the field. If the field can have multiple values, use the foreach command (in service profile configuration mode) followed by the attribute command.

Use the no form of this command to remove the field from the service profile.

1.26.6   Examples

The following example specifies a mandatory redirect URL field for the HTTP redirect service condition; the field is defined in the HTTP-Redirect-URL VSA, using the attribute command (in service profile configuration mode):

[local]Redback(config-ctx)#radius service profile redirect
[local]Redback(config-svc-profile)#parameter value redirect-url
[local]Redback(config-svc-profile)#

The following example specifies a mandatory TCP port number field that can have an array of values; the field is defined using the attribute command within a loop initiated by the foreach command (in service profile configuration mode):

[local]Redback(config-ctx)#radius service profile redirect
[local]Redback(config-svc-profile)#parameter list tcp-port 
[local]Redback(config-svc-profile)#

The following example specifies default values for the TCP port number field; in this case, the TCP port number is optional and need not be specified by the RADIUS server:

[local]Redback(config-ctx)#radius service profile redirect
[local]Redback(config-svc-profile)#parameter list tcp-port www, 443, 8080
[local]Redback(config-svc-profile)#

The following example predefines classes “D1 D2 D4 D5” using the parameter %dynamic_class_qos_in and creates a reference to the predefined classes using the class_bearer variable:

[local]Redback(config-ctx)#radius service profile dyn-service
[local]Redback(config-svc-profile)#parameter value %dynamic_class_qos_in 
“D1 D2 D4 D5”
[local]Redback(config-svc-profile)#parameter value class_bearer 
%dynamic_class_qos_in

1.27   parent-class

1.27.1   Purpose

Maps a specific child class to a parent class.

1.27.2   Command Mode

• policy group class configuration

1.27.3   Syntax Description

1.27.4   Default

The mapping of a child class to a parent class is not specified.

1.27.5   Usage Guidelines

Use the parent-class command to map a metering or policing policy class to a class specified in another metering or policing policy. The class mapping configuration is employed when applying a hierarchical metering or policing policy to traffic on a child circuit that has its own metering and policing policy. Using the class mapping, the SmartEdge router determines the parent policy class for treating the child class traffic when enforcing the parent metering or policing policy. For more information about the mapping of the ACL class or a class-definition map class to a parent policy class, see Mapping a Child Policy Class to a Parent Class in Configuring Rate-Limiting and Class-Limiting.

Use the no form of this command to remove the mapping of the child class to the parent class.

1.27.6   Examples

The following example shows how to map a child class to a parent class. In this example, the child class voip is mapped to the parent class high and the child class data is mapped to the parent class low:

[local]Redback(config)#qos policy child-pol metering
[local]Redback(config-policy-metering)#ip access-group child-acl local
[local]Redback(config-policy-group)#class voip
[local]Redback(config-policy-group-class)#parent-class high
[local]Redback(config-policy-group-class)#rate 50 burst 100
[local]Redback(config-policy-class-rate)#class data
[local]Redback(config-policy-group-class)#parent-class low
[local]Redback(config-policy-group-class)#rate 20 burst 40

1.28   partition

1.28.1   Command Mode

SSE group configuration

1.28.2   Syntax Description

1.28.3   Default

No partition is configured.

1.28.4   Usage Guidelines

Creates the partition and enters SSE partition configuration mode. You can create multiple partitions. The partition name must be unique in the SSE group.

The disk and non-mirror keywords apply only to network-redundant SSE groups. For other operational settings, the command is rejected if these keywords are specified.

Any partition configured must be fully allocated on the SSE disk for it to be operational.

The no form of the command removes the partition from the SSE group. The partition still exists on the SSE disk and data is maintained. Use the delete partition sse slot disk_num partition_name command in exec mode to remove the partition and all data.

1.28.5   Examples

[local]Redback(config)#sse group sse_group_1
[local]Redback(config-SE-group)#partition p01 size 5 disk 1

1.29   passive

1.29.1   Purpose

When entered in OSPF area configuration mode, sets all interfaces configured in the specified Open Shortest Path First (OSPF) area to passive mode.

When entered in OSPF interface or OSPF3 interface configuration mode, sets an OSPF or OSPF Version 3 (OSPFv3) interface to passive mode.

1.29.2   Command Mode

• OSPF area configuration
• OSPF interface configuration
• OSPF3 interface configuration

1.29.3   Syntax Description

This command has no keywords or arguments.

1.29.4   Default

No interfaces are in passive mode.

1.29.5   Usage Guidelines

Use the passive command in OSPF area configuration mode to set all interfaces configured in the specified OSPF area to passive mode.

Note:  

OSPF passive mode disables OSPF interfaces from sending OSPF packets.

Setting all interfaces in an OSPF area to passive mode is useful for large, pure edge aggregation applications, where there may be hundreds, or perhaps thousands, of customer-facing circuits. To distribute routes for the customer-facing interfaces to the upstream routers, you can enable OSPF on the customer-facing interfaces, and then set them all to passive mode using the passive command in OSPF area configuration mode.

Use the passive command in OSPF interface or OSPF3 interface configuration mode to set an OSPF or OSPFv3 interface to passive mode.

Use the no or default form of this command to return the interface, or all interfaces within an OSPF area, to the default state.

1.29.6   Examples

The following example sets the ospf1 interface to passive mode:

[local]Redback(config-ospf-area)#interface ospf1
[local]Redback(config-ospf-if)#passive

1.30   passive-interface

1.30.1   Purpose

Configures the Intermediate System-to-Intermediate System (IS-IS) instance to advertise the interface’s IP address without actively running IS-IS on the interface.

1.30.2   Command Mode

IS-IS interface configuration

1.30.3   Syntax Description

This command has no keywords or arguments.

1.30.4   Default

Passive mode is disabled.

1.30.5   Usage Guidelines

Use the passive-interface command to configure the IS-IS instance to advertise the interface’s IP addresses without actively running IS-IS on the interface.

When an IS-IS interface is configured in passive mode, IS-IS packets are sent and no adjacency is formed on the interface. IS-IS advertises the interface’s IP address in its link-state protocol data units (LSPs).

The default metric value for a passive interface is 1. To change the metric value, use the metric command in IS-IS interface configuration mode.

Use the no form of this command to disable this option.

1.30.6   Examples

The following example configures the fa4/1 interface as a passive IS-IS interface:

[local]Redback(config-ctx)#router isis ip-backbone
[local]Redback(config-isis)#interface fa4/1
[local]Redback(config-isis-if)#passive-interface

1.31   password

1.31.1   Purpose

Specifies the authentication password that the subscriber enters when initiating a Point-to-Point Protocol (PPP) session.

1.31.2   Command Mode

subscriber configuration

1.31.3   Syntax Description

1.31.4   Default

None

1.31.5   Usage Guidelines

Use the password command to specify the authentication password that the subscriber enters when initiating a PPP session. When using Challenge Handshake Authentication Protocol (CHAP) Password Authentication Protocol (PAP), the password obtained from the subscriber must match the password configured in the corresponding subscriber record. This command is available for individual subscriber records, but not for a default subscriber record.

You can enter a password with embedded spaces by enclosing the entire password in double quotes; for example, “This is a Password With Spaces.”

Use the no form of this command to remove the password from the subscriber’s record.

1.31.6   Examples

The following example configures a password of DontTellAnyone:

[local]Redback(config-sub)#password DontTellAnyone

1.32   password (BGP)

1.32.1   Purpose

Configures an encrypted Message Digest 5 (MD5) password for the Border Gateway Protocol (BGP) neighbor or peer group.

1.32.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration

1.32.3   Syntax Description

1.32.4   Default

None

1.32.5   Usage Guidelines

Use the password command to assign an encrypted MD5 password for the BGP neighbor or peer group.

Note:  

For a BGP session to be established, the MD5 password must be the same on both the router and its neighbor.

Use the no form of this command to remove an assigned password from the BGP neighbor or peer group.

1.32.6   Examples

The following example assigns the password secret to the external BGP (eBGP) neighbor at IP address 10.10.1.1:

[local]Redback(config-bgp)#neighbor 10.10.1.1 external
[local]Redback(config-bgp-neighbor)#password secret

1.33   path-trace

1.33.1   Purpose

Specifies either the maximum length of the message or the text string to be traced on an administrative unit-3 (AU-3) or an AU-4 on a channelized STM-1 port.

1.33.2   Command Mode

• AU-3 configuration
• STM-1 configuration

1.33.3   Syntax Description

1.33.4   Default

The length is 16 and the message is Redback.

1.33.5   Usage Guidelines

Use the path-trace command to specify either the maximum length of the text or the text string to be traced on an AU-3 or AU-4 on a channelized STM-1 port.

If you enter the aug-mapping au3 command (in STM-1 configuration mode), the path-trace command is no longer available in STM-1 configuration mode; it is available in AU-3 configuration mode.

The first byte in a 16-character message is reserved for the results of a CRC7 calculated on the message.

The final two characters in a 64-character message are reserved for the CR/LF (0x0D/0x0A).

Use the no form of this command to set the maximum length to 16, and the message text to Redback. You cannot disable the path trace feature for channelized STM-1 ports.

Note:  

The message keyword is used without the text argument in the no form of this command.

Note:  

This command is also described in Configuring ATM, Ethernet, and POS Ports for ports on Packet over SONET/SDH (POS) and 4-port ATM OC-3c/STM-1c line cards.

1.33.6   Examples

The following example shows how to specify a path trace with a maximum message length of 64 and the text string for port 1 of the channelized STM-1 line card in slot 2; the port is mapped with the default administrative unit group (AUG) mapping, AU-4:

[local]Redback(config)#port channelized-stm1 2/1
[local]Redback(config-stm1)#path-trace length 64
[local]Redback(config-stm1)#path-trace this is a test of an extended length message.

1.34   path-trace (ATM OC, POS, WAN-PHY)

1.34.1   Purpose

Specifies the text string to be traced on a Packet over SONET/SDH (POS), second-generation Asynchronous Transfer Mode (ATM) OC, or Ethernet WAN-PHY port.

1.34.2   Command Mode

• ATM OC configuration
• port configuration

1.34.3   Syntax Description

1.34.4   Default

The transmitted text string is Redback.

1.34.5   Usage Guidelines

Use the path-trace command to specify the text string to be on a Packet over SONET/SDH (POS), second-generation Asynchronous Transfer Mode (ATM) OC, or Ethernet WAN-PHY port.

Note:  

The SmartEdge 100 router does not support POS ports.

The actual message length is 16 or 64 bytes, with one additional byte required for framing for a 15-character message and two additional bytes required for a 62-character message.

Note:  

For a POS port, you must first enable the path trace, path maintenance, and path alarm monitoring features for the card on which the port is configured, by using the sonet-eu command (in card configuration mode). The sonet eu command is not needed for ports on a second-generation ATM OC card.

You cannot disable the path trace feature for Ethernet WAN-PHY or second-generation ATM OC line cards; to disable the path trace feature for ports on POS line cards, you must enter the no form for the sonet-eu command (in card configuration mode).

Use the show port detail command (in any mode) to display the path trace length and message.

Use either the no or default form of this command to specify the default text string.

1.34.6   Examples

The following example shows how to enable path trace and specify the text string, this is a test, for port 1 on the POS line card in slot 9:

[local]Redback(config)#card oc3e-8-port 9
[local]Redback(config-card)#sonet-eu
[local]Redback(config-card)#exit
[local]Redback(config)#port pos 9/1
[local]Redback(config-port)#path-trace this is a test

[local]Redback(config)#card 10ge-1-port 2
[local]Redback(config-card)#exit
[local]Redback(config)#port wan-phy 2/1
Note: Creating a port may cause the card to reload. Commit to
continue; abort to exit without change
[local]Redback(config)#commit
[local]Redback(config-port)#path-trace this is a test

1.35   pe-type

1.35.1   Purpose

Specifies the connection type used between the local and remote provider edge (PE) devices.

1.35.2   Command Mode

VPLS profile neighbor configuration

1.35.3   Syntax Description

1.35.4   Default

The hub connection type is used.

1.35.5   Usage Guidelines

Use the pe-type command to specifies the connection type used between the local and remote PE devices. Currently, hub and spoke connection types are supported. For proper VPLS peering, both ends of the peer must be configured with the same connection type.

Use the no or default form of this command to specify the default connection type.

1.35.6   Examples

The following example sets the connection type to spoke:

[local]Redback#config
[local]Redback(config)#vpls profile foo
[local]Redback(config-vpls-profile)#neighbor 10.10.10.1
[local]Redback(config-vpls-profile-neighbor)#pe-type spoke
[local]Redback(config-vpls-profile-neighbor)#

1.36   peer-as

1.36.1   Purpose

Configures a peer’s autonomous system number (ASN).

1.36.2   Command Mode

MSDP peer configuration

1.36.3   Syntax Description

1.36.4   Default

None

1.36.5   Usage Guidelines

Use the peer-as command to configure a peer’s ASN.

Use the no form of this command to delete the source active (SA) number from the peer’s configuration.

1.36.6   Examples

The following example configures a peer’s SA number to 37:

[local]Redback(config-msdp)#peer 192.168.1.1 local-tcp-source ToWan12

[local]Redback(config-msdp-peer)#peer-as 37

1.37   peer-end-point

1.37.1   Purpose

Assigns IP addresses to the tunnel endpoints.

1.37.2   Command Mode

tunnel configuration

1.37.3   Syntax Description

1.37.4   Default

None

1.37.5   Usage Guidelines

Use the peer-end-point command to assign IP addresses to the tunnel endpoints. This command creates the tunnel between the two endpoints.

Note:  

IP-in-IP and overlay tunnels support a single tunnel circuit in each tunnel; GRE tunnels can support multiple tunnel circuits with the use of keys. For information about GRE tunnel circuits, see Configuring GRE Tunnels.

The remote IP address at one end of the tunnel is the same as the local IP address at the other end of the tunnel. If the remote IP address is not adjacent to the local IP address, and the remote site cannot be reached with a routing protocol, you must also enter the ip route command in context configuration mode.

If you create an overlay tunnel using the tunnel command with the ipv6v4-auto keyword, the system assigns an IP address to the remote endpoint. In this case, you do not include the remote rem-ip-addr construct when you enter this command.

The local loc-ip-addr construct must match the IP address of an interface.

If you are creating more than one tunnel, they can use the same IP address for the local endpoint (the IP address assigned to the interface) as long as the remote IP addresses are all different.

To use an interface and its local IP address for more than one tunnel, you must specify the loopback keyword with the interface command (in context configuration mode) when you create the interface for the tunnels. The loopback keyword allows you to reuse the IP address for more than one tunnel.

Use the no form of this command to delete this tunnel and any associated parameters that have been specified in tunnel configuration mode. The keywords are not available for the no form of this command.

1.37.6   Examples

The following example shows how to create an interface, toDenver, with a public IP address of 172.16.1.1; then it creates an overlay tunnel, DenverTnl, with a remote IP address of 172.16.1.2 and a local IP address of 172.16.1.1:

[local]Redback(config)#context local
[local]Redback(config-ctx)#interface toDenver
[local]Redback(config-if)#ip address 172.16.1.1/30
[local]Redback(config-if)#exit
[local]Redback(config-ctx)#exit
[local]Redback(config)#tunnel ipv6v4-manual DenverTnl 
[local]Redback(config-tunnel)#peer-end-point local 172.16.1.1 remote 172.16.1.2

The following example shows how to create two overlay tunnels each using an interface, LocalEnd. Both tunnels use the same local IP address; it is assumed that the remote IP address for Tun2 can be reached with a routing protocol, so the ip route command in context configuration mode is not needed:

[local]Redback(config)#context local
[local]Redback(config-ctx)#interface LocalEnd loopback
[local]Redback(config-if)#ip address 172.16.1.1/32
[local]Redback(config-if)#exit
[local]Redback(config-ctx)#tunnel Tunl 
[local]Redback(config-tunnel)#peer-end-point local 172.16.1.1 remote 172.16.1.2
[local]Redback(config-tunnel)#no shutdown
[local]Redback(config-tunnel)#exit
[local]Redback(config-ctx)#tunnel Tun2 
[local]Redback(config-tunnel)#peer-end-point local 172.16.1.1 remote 172.20.1.2
[local]Redback(config-tunnel-peer)#no shutdown
[local]Redback(config-tunnel-peer)#end

1.38   peer-group

1.38.1   Purpose

When entered in BGP router configuration mode, configures an internal Border Gateway Protocol (iBGP) or external BGP (eBGP) peer group and enters BGP peer group configuration mode.

When entered in BGP neighbor configuration or BGP neighbor address family configuration mode, applies the attributes of a configured peer group to a BGP neighbor or BGP neighbor address family.

1.38.2   Command Mode

• BGP neighbor address family configuration
• BGP neighbor configuration
• BGP router configuration

1.38.3   Syntax Description

1.38.4   Default

There are no preconfigured peer groups. Once a peer group is configured, it is enabled.

1.38.5   Usage Guidelines

Use the peer-group command in BGP router configuration mode to configure an iBGP or eBGP peer group and enter BGP peer group configuration mode.

Peer groups are helpful in cases where many BGP neighbors are configured with the same outbound update policies. Grouping a large number of neighbors into one or more peer groups simplifies modifications to a configuration, and more importantly, makes BGP update generation more efficient. The use of peer groups is strongly recommended when there are a large number of peers.

Note:  

BGP peer groups can be configured in standard contexts and VPN contexts.

You can apply attributes to BGP neighbors or BGP address families. Attributes that are not configurable for peer groups are those set by the following commands in BGP neighbor configuration mode: accept prefix-filter, local-as, and remote-as.

Use the peer-group command in BGP neighbor configuration mode to apply the characteristics of a peer group to one or more BGP neighbors. A neighbor can be assigned to a peer group only if the neighbor and the peer group is of the same type—external or internal BGP. If a neighbor belongs to a particular peer group, it cannot be configured to belong to another peer group. The previous peer group membership must first be explicitly deleted before the peer membership can be reconfigured.

Attributes are inherited from the peer group to which a neighbor is assigned. The following BGP neighbor configuration mode commands represent attributes that cannot be customized per neighbor when the neighbor is assigned to a peer group: advertisement-interval, ebgp-multihop, local-as, send community, and timers. Attributes inherited from a peer group that can be customized per neighbor include those set by the following commands: description, password, send prefix, shutdown, and update-source.

Use the peer-group command in BGP neighbor address family configuration mode to apply the characteristics of a peer group to one or more BGP neighbor address families. A BGP neighbor address family can belong to more than one peer group and can be modified to belong to a different peer group without having to delete the previous peer group association first.

Attributes are inherited from the peer group to which a BGP neighbor address family is assigned. The following commands in BGP neighbor address family configuration mode represent attributes that cannot be customized per address family once it is assigned to a peer group: as-path-list out, prefix-list out, remove-private-as, and route-map out. Attributes inherited from a peer group that can be customized per neighbor address family include those set by the following commands: as-path-list in, default-originate, maximum-prefix, prefix-list in, and route-map in.

By default, a configured peer group is automatically enabled. To disable a peer group, enter the shutdown command in BGP peer group configuration mode.

Use the no form of this command to remove a peer group.

1.38.6   Examples

The following example assigns the BGP neighbor at IP address 10.1.1.1 to the peer group pgrp-101. The BGP neighbor at IP address 10.1.1.1 inherits all of its configuration from peer group pgrp-101. The configuration also assigns the BGP neighbor at IP address 10.2.2.2 to the peer group pgrp-200. The BGP neighbor at IP address 10.2.2.2 inherits all outbound routing policies and the properties of the remove-private-AS command from peer group pgrp-200, but does not inherit the group’s inbound policies or description information:

[local]Redback(config-ctx)#router bgp 101
[local]Redback(config-bgp)#peer-group pgrp-101 internal
[local]Redback(config-bgp-peer-group)#description config IBGP neighbors
[local]Redback(config-bgp-peer-group)#password encrypted 8F733D8CD3F98AE0
[local]Redback(config-bgp-peer-group)#update-source interface1
[local]Redback(config-bgp-peer-group)#next-hop-self
[local]Redback(config-bgp-peer-group)#address-family ipv4 unicast
[local]Redback(config-bgp-peer-af)#maximum prefix 20000
[local]Redback(config-bgp-peer-af)#exit
[local]Redback(config-bgp-peer-group)#exit
[local]Redback(config-bgp)#peer-group pgrp-200 external
[local]Redback(config-bgp-peer-group)#ebgp-multihop 10
[local]Redback(config-bgp-peer-group)#address-family ipv4 unicast
[local]Redback(config-bgp-peer-af)#as-path-list aspath-in in
[local]Redback(config-bgp-peer-af)#as-path-list aspath-out out
[local]Redback(config-bgp-peer-af)#remove-private-AS
[local]Redback(config-bgp-peer-af)#exit
[local]Redback(config-bgp-peer-group)#exit
[local]Redback(config-bgp)#neighbor 10.1.1.1 internal
[local]Redback(config-bgp-neighbor)#peer-group pgrp-101
[local]Redback(config-bgp-neighbor)#address-family ipv4 unicast
[local]Redback(config-bgp-neighbor)#exit
[local]Redback(config-bgp)#neighbor 10.2.2.2 external
[local]Redback(config-bgp-neighbor)#peer-group pgrp-200
[local]Redback(config-bgp-neighbor)#remote-as 200
[local]Redback(config-bgp-neighbor)#description neighbor at corpA
[local]Redback(config-bgp-neighbor)#address-family ipv4 unicast
[local]Redback(config-bgp-peer-af)#as-path-list as-in in
[local]Redback(config-bgp-peer-af)#as-path-list as-out out
[local]Redback(config-bgp-peer-af)#route-map rtmap-out out

1.39   peer id

1.39.1   Purpose

Filters incoming new neighbor connections using the sender name of the incoming Access Node Control Protocol (ANCP) neighbor peer.

1.39.2   Command Mode

• ANCP neighbor configuration

1.39.3   Syntax Description

1.39.4   Default

If a peer name is not specified for this profile, there is no restriction on the sender name in a received General Switch Management Protocol (GSMP) adjacency protocol message from an ANCP neighbor peer.

1.39.5   Usage Guidelines

Use the peer id command to filter incoming new neighbor connections using the sender name of the incoming ANCP neighbor peer. The sender name is in the GSMP adjacency protocol message from the ANCP neighbor peer.

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

1.39.6   Examples

The following example specifies a name for an ANCP neighbor peer:

[local]Redback(config-ancp-neighbor)#peer id 01:02:03:04:05:06

1.40   peer ip-address

1.40.1   Purpose

Filter incoming new neighbor connections using the IP address of the incoming Access Node Control Protocol (ANCP) neighbor peer.

1.40.2   Command Mode

• ANCP neighbor configuration

1.40.3   Syntax Description

1.40.4   Default

If an IP address is not specified for this profile, there is no restriction on the IP address in a received General Switch Management Protocol (GSMP) adjacency protocol message from an ANCP neighbor peer.

1.40.5   Usage Guidelines

Use the peer ip-address command to filter incoming new neighbor connections using the IP address of the incoming ANCP neighbor peer. The incoming IP address is matched against the specified IP address and the connection rejected if there is no match.

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

1.40.6   Examples

The following example specifies IP address for an ANCP neighbor peer:

[local]Redback(config-ancp-neighbor)#peer ip-address 30.100.1.20 

1.41   peer (L2TP)

1.41.1   Purpose

Adds an existing peer to the current Layer 2 Tunneling Protocol (L2TP) group.

1.41.2   Command Mode

L2TP group configuration

1.41.3   Syntax Description

1.41.4   Default

No peer is added to the current L2TP group.

1.41.5   Usage Guidelines

Use the peer command to add an existing peer to an L2TP group. The l2tp-peer-name argument is the peer name specified in the l2tp-peer command in context configuration mode or its domain alias, specified by the domain command in L2TP peer configuration mode.

Use the preference priority construct to override the implicit priority for the peer, if you have specified the priority keyword in the algorithm command (in L2TP group configuration mode). Otherwise, the implicit priority is the order in which the peer commands are run, with the first peer entered having the highest priority.

If you have specified the weighted-round-robin keyword in the algorithm command (in L2TP group configuration mode), use the weight weight construct to assign a weight for the peer to be used in the calculation of the priority.

This command takes effect immediately, but does not affect Point-to-Point Protocol (PPP) sessions that are already established; only future PPP sessions.

Use the no form of this command to remove the named peer from the group.

1.41.6   Examples

The following example shows how to select (or create) an L2TP group, add three L2TP peers to the group, sets the algorithm to strict priority, and set the deadtime to 5 minutes:

[local]Redback(config-ctx)#l2tp-group name group1
[local]Redback(config-l2tp-group)#algorithm priority
[local]Redback(config-l2tp-group)#peer name sweet1 preference 10
[local]Redback(config-l2tp-group)#peer name sweet2 preference 20
[local]Redback(config-l2tp-group)#peer name sweet3 preference 30
[local]Redback(config-l2tp-group)#default deadtime

1.42   peer (L2VPN profile)

1.42.1   Purpose

Specify the IP address of the peer router that can be reached through the LSPs on the current router and enter L2VPN profile peer configuration mode.

1.42.2   Command Mode

• L2VPN profile configuration

1.42.3   Syntax Description

1.42.4   Default

none.

1.42.5   Usage Guidelines

Use the peer command to specify the IP address of the peer router that can be reached through the LSPs on the current router and enter L2VPN profile peer configuration mode.

1.42.6   Examples

The following example shows how to specify the IP address of the peer router 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)

1.43   peer (MSDP)

1.43.1   Purpose

Configures an Multicast Source Discovery Protocol (MSDP) peer and enters MSDP peer configuration mode.

1.43.2   Command Mode

MSDP router configuration

1.43.3   Syntax Description

1.43.4   Default

None

1.43.5   Usage Guidelines

Use the peer command to configure an MSDP peer and enter MSDP peer configuration mode for peer-specific configurations.

Use the no form of this command to delete an MSDP peer.

1.43.6   Examples

The following example configures a router with an IP address of 192.168.1.1 to be an MSDP peer that uses the ToWan12 interface for the TCP connection:

[local]Redback(config-ctx)#router msdp
[local]Redback(config-msdp)#peer 192.168.1.1 local-tcp-source ToWan12
[local]Redback(config-msdp-peer)#

1.44   peer (NTP)

1.44.1   Purpose

Configures an NTP peer for a context.

1.44.2   Command Mode

NTP server configuration

1.44.3   Syntax Description

1.44.4   Default

There is no NTP peer enabled in the context.

1.44.5   Usage Guidelines

To configure the system clock to synchronize a peer or to be synchronized by a peer, enable an NTP server in a context with the peer command.

To disable the NTP server, use the no form of the command.

1.44.6   Examples

The following example configures an NTP peer in the isp202 context:

[local]Redback(config)#context isp202
[local]Redback(config-ctx)#ntp-mode
[local]Redback(config-ntp-server)#peer 1.1.1.5 version 3 source ntp

1.45   periodic

1.45.1   Purpose

Creates a periodic time access control list (ACL) condition statement.

1.45.2   Command Mode

ACL condition configuration

1.45.3   Syntax Description

1.45.4   Default

None

1.45.5   Usage Guidelines

Use the periodic command to create a periodic time ACL condition statement that permits or denies packets, or assigns packets to a class, based on specific date and time ranges. A periodic time ACL condition is referenced by either an IP ACL statement or a policy ACL statement.

Each ACL condition statement can include up to seven absolute or periodic time statements in any combination.

Use the no form of this command to delete the periodic time ACL condition statement.

1.45.6   Examples

The following example creates a periodic ACL condition statement for the ACL condition, 55, which is referenced by the policy ACL, policy_acl_2, such that the Bar003 class name is applied every Wednesday from 9:00 p.m. to 11:00 p.m (21:00 to 23:00 in 24-hour format) to packets assigned to the Bar003 class:

[local]Redback(config-ctx)#policy access-list policy_acl_2
[local]Redback(config-access-list)#condition 55 time-range
[local]Redback(config-acl-condition)#periodic wednesday 21:00 to 23:00 class Bar003

1.46   permit (IPv4 ACL)

Statements in IPv4 and IPv6 ACLs can contain different criteria; for syntax for statements for IPv6 ACLs, see permit (IPV6 ACL).

1.46.1   Purpose

Creates an IP or policy access control list (ACL) statement to allow packets that meet the specified criteria.

1.46.2   Command Mode

access control list configuration

1.46.3   Syntax Description for IPv4 Statements

1.46.4   Default

None

1.46.5   Usage Guidelines

Use the permit command to create an IP or policy ACL statement to allow packets that meet the specified criteria.

To explicitly set the order of the statement in an ACL, use the seq permit command instead of this command.

In IPv4 statements, follow these guidelines:

• The cond port and cond length constructs are mutually exclusive with the range port end-port and range length end-length constructs.
• You can use the optional max-sessions limit and min-sessions limit constructs to specify a maximum or minimum number of simultaneous SSH or Telnet sessions allowed from an IP address or subnet. These constructs are available if you use the service ssh server or service telnet server commands with the ip access-group keyword to enable the SSH or Telnet protocol and apply the ACL. For statements where the any keyword is specified for both source and destination, only the max-sessions limit construct applies.
• If you specify a limit for both an IP address and the related subnet, the limit for the subnet takes precedence. Similarly, a limit specified for a larger subnet takes precedence over limits specified for related smaller subnets. From all sources combined, the SmartEdge router supports up to 32 active Telnet and SSH sessions.

Note:  

In all ACLs, there is an implicit deny any any statement at the end of the list. This implicit statement could block valid access to a context; for example, in the local context, it could block administrator access to the Ethernet management port. To allow administrator access, add a statement to explicitly allow access from authorized sources to the end of the list. For example, you could add a seq seq-num permit ip any any or seq seq-num permit ip src src-wildcard dest dest-wildcard statement.

Use the no form of this command to delete the statement with the specified sequence number from the ACL.

Table 9 lists the valid keyword values for the cond argument.

Table 10 lists the valid keyword values for the port argument when it is used to specify a TCP port.