Contents

1   Command Descriptions

Commands starting with “t” through commands starting with “z” are included.

1.1   table-map

1.1.1   Purpose

Assigns a traffic index to routes installed for a Border Gateway Protocol (BGP) address family.

1.1.2   Command Mode

BGP address family configuration

1.1.3   Syntax Description

1.1.4   Default

A table map is not applied to a BGP address family.

1.1.5   Usage Guidelines

Use the table-map command to assign a traffic index to routes installed for a BGP address family.

Traffic index counters are maintained on interfaces with traffic index accounting enabled. Traffic indices are associated with BGP routes based on route-maps matching on BGP attributes. When IP packets are received on an interface with traffic index accounting enabled, and the route lookup for the packet’s destination IP address corresponds to a BGP route with a traffic index assigned, the corresponding byte and packet counters are incremented. For more information, see the set traffic-index and traffic-index accounting commands.

Use the route-map command in BGP neighbor address family configuration mode and BGP peer group address family configuration mode to determine the attribute modifications and filtering conditions of the applied route map.

Use the no form of this command to remove the table map.

1.1.6   Examples

The following example assigns a traffic index to routes installed for a BGP address family using the bgp-accounting route map:

[local]Redback(config-ctx)#router bgp 64001

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

[local]Redback(config-bgp-af)#table-map bgp-accounting

1.2   tacacs+ deadtime

1.2.1   Purpose

Modifies the interval during which the SmartEdge® router is to treat a nonresponsive Terminal Access Controller Access Control System Plus (TACACS+) server as “dead,” and instead, try to reach another server if one is configured.

1.2.2   Command Mode

Context configuration

1.2.3   Syntax Description

1.2.4   Default

The SmartEdge router waits 5 minutes after a timeout occurs before considering the affected server to be eligible to accept TACACS+ requests again.

1.2.5   Usage Guidelines

Use the tacacs+ deadtime command to modify the interval during which the SmartEdge router is to treat a nonresponsive TACACS+ server as “dead,” and try, instead, to reach another configured server.

If a server fails to respond to a TACACS+ request within the configured TACACS+ timeout window, which configured with the tacacs+ timeout command (in context configuration mode), it is declared dead. No TACACS+ requests are sent to a dead server until the server deadtime (the value of the interval argument) expires, at which time the server is again considered eligible for new TACACS+ requests and resumes its original priority. However, if all servers are unresponsive, the SmartEdge router uses local authentication, if enabled. If local authentication is disabled and all servers are unresponsive, authentication fails. Use the aaa authentication administrator command in context configuration mode to enable local authentication; for more information, see Configuring Bridging

Use the no form of this command or specify a value of 0 for the interval argument to disable the deadtime feature, which means that the server is always eligible for TACACS+ requests.

Use the default form of this command to reset the number of retransmission attempts to 5 minutes.

1.2.6   Examples

The following example specifies a deadtime interval of 10 minutes:

[local]Redback(config-ctx)#tacacs+ deadtime 10

1.3   tacacs+ max-retries

1.3.1   Purpose

Modifies the number of retransmission attempts the SmartEdge router will make to open a Transmission Control Protocol (TCP) connection to the Terminal Access Controller Access Control System Plus (TACACS+) server in the event that no response is received from the server within the timeout period.

1.3.2   Command Mode

Context configuration

1.3.3   Syntax Description

1.3.4   Default

The SmartEdge router makes three attempts to open a TCP connection to the TACACS+ server.

1.3.5   Usage Guidelines

Use the tacacs+ max-retries command to modify the number of retransmission attempts the SmartEdge router makes to open a TCP connection to the TACACS+ server in the event that no response is received from the server within a timeout period.

The timeout period is configured through the tacacs+ timeout command (in context configuration mode).

If no acknowledgment is received, all configured TACACS+ servers in the context are tried (moving from the last server back to the first, if necessary) until the maximum number of retransmission attempts have been made for each configured server.

Use the no form of this command or specify a value of 0 for the retries argument to disable the retransmission completely.

Use the default form of this command to reset the number of retransmission attempts to 3.

1.3.6   Examples

The following example modifies the retry count to allow the SmartEdge router to make up to 5 attempts to open a TCP connection to the TACACS+ server in the event that no response is received from the server within the timeout period:

[local]Redback(config-ctx)#tacacs+ max-retries 5

1.4   tacacs+ server

1.4.1   Purpose

Configures the IP address or hostname for a Terminal Access Controller Access Control System Plus (TACACS+) server.

1.4.2   Command Mode

Context configuration

1.4.3   Syntax Description

1.4.4   Default

None

1.4.5   Usage Guidelines

Use the tacacs+ server command to configure the IP address or hostname for a TACACS+ server. The SmartEdge router can support up to five TACACS+ servers in each context. The servers are assigned priority based on the order configured. The first configured server is used first. If the first server becomes unavailable or unreachable, the second server is used, and so on.

The keykey construct allows you to specify the authentication key that the SmartEdge router uses to communicate with the TACACS+ server. After the configuration is saved, this key is stored in the encrypted form. The output of the show configuration command displays the encrypted-key keyword with the encrypted key indicating that the key is encrypted.

The encrypted-keykey construct allows you to specify and enter an encrypted authentication key, which was previously configured in clear text using the keykey construct. Use the encrypted-keykey construct, if you want the tacacs+ server command configured with an encrypted authentication key as part of a configuration file you are loading onto a SmartEdge router. Copy the encrypted key from either the output of the show configuration command or a configuration file that contains it, and then paste it as the key argument within the encrypted-key key construct of the tacacs+ server command configuration of the configuration file you are loading. The SmartEdge router does not encrypt the encrypted key before storing it because the key is already encrypted.

Use the no form of this command to delete a previously configured TACACS+ server.

1.4.6   Examples

The following example shows how define a TACACS+ server with an IP address, 10.43.32.56, and a key, Secretkey, for authentication:

[local]Redback(config-ctx)#tacacs+ server 10.43.32.56 key Secretkey port 53

The following example shows how to define a TACACS+ server with an IP address, 12.33.56.78, and an encrypted key, A04915CDD716F0CC3BC20910847B1834, for authentication:

[local]Redback(config-ctx)#tacacs+ server 12.33.56.78 encrypted-key 
A04915CDD716F0CC3BC20910847B1834 port 53

1.5   tacacs+ strip-domain

1.5.1   Purpose

Specifies that the domain portion of a structured username be removed before relaying an authentication, authorization, or accounting request to a Terminal Access Controller Access Control System Plus (TACACS+) server.

1.5.2   Command Mode

Context configuration

1.5.3   Syntax Description

This command has no keywords or arguments.

1.5.4   Default

The SmartEdge router sends entire structured username, including the domain name, to the TACACS+ server.

1.5.5   Usage Guidelines

Use the tacacs+ strip-domain command to specify that the domain portion of a structured username be removed before relaying an authentication, authorization, or accounting request to a TACACS+ server. For example, subscriber name joe is sent rather than joe@local. The domain portion can be stripped, even if custom structured username formats have been defined using the aaa username-format command (in global configuration mode).

The decision to strip the domain name depends on whether subscriber and administrator records are defined with or without the domain name in the TACACS+ server configuration.

Use the no or default form of this command to disable the stripping of the domain portion of the structured username.

1.5.6   Examples

The following example prevents the domain portion of the structured username from being sent to the TACACS+ server:

[local]Redback(config-ctx)#tacacs+ strip-domain

1.6   tacacs+ timeout

1.6.1   Purpose

Modifies the maximum amount of time the SmartEdge router waits for a response from a Terminal Access Controller Access Control System Plus (TACACS+) server before assuming that a packet is lost or that the TACACS+ server is unreachable.

1.6.2   Command Mode

Context configuration

1.6.3   Syntax Description

1.6.4   Default

The timeout interval is 10 seconds.

1.6.5   Usage Guidelines

Use the tacacs+ timeout command to modify the maximum amount of time that the SmartEdge router waits for a response from a TACACS+ server before assuming that a packet is lost or that the TACACS+ server is unreachable.

The timeout value is displayed in the output of the show tacacs+ server command.

Use the default form of this command to return the timeout to the default value of 10 seconds.

1.6.6   Examples

The following example sets the TACACS+ timeout to 60 seconds:

[local]Redback(config-ctx)#tacacs+ timeout 60

1.7   tag

1.7.1   Purpose

Configures the route tag value for a dynamically verified static routing (DVSR) profile.

1.7.2   Command Mode

DVSR profile configuration

1.7.3   Syntax Description

1.7.4   Default

The default route tag value is 0.

1.7.5   Usage Guidelines

Use the tag command to configure the route tag value for a DVSR profile. For route redistribution, the route tag can be used for route map matches.

Note:  

You can also define the route tag value when configuring a DVSR route. In that case, the specified DVSR route tag value overwrites the value in the DVSR profile.

Use the no form of this command to delete the route tag value from a DVSR profile.

Use the default form of this command to configure the route tag for a DVSR profile to be 0 (the default value).

1.7.6   Examples

The following example defines a DVSR profile using a route tag of 123; however, it is not used by the DVSR route 10.1.0.0/16, because it defines its own route tag value of 456:

[local]Redback(config-ctx)#dvsr-profile abc-webfarm
[local]Redback(config-dvsr)#tag 123
[local]Redback(config-dvsr)#exit
[local]Redback(config-ctx)#ip route 10.0.0.0/8 10.10.10.10 dvsr abc-webfarm
[local]Redback(config-ctx)#ip route 10.1.0.0/16 10.10.10.10 dvsr abc-webfarm tag 456

1.8   talk

1.8.1   Purpose

Enables you to establish communications with another administrator during active Telnet or Secure Shell (SSH) sessions on the same SmartEdge router.

1.8.2   Command Mode

Exec

1.8.3   Syntax Description

1.8.4   Default

Communications with other active administrators are disabled. If the ctx-name argument is not entered, the system assumes the local context.

1.8.5   Usage Guidelines

Use the talk command to establish communications with other active administrators during active Telnet or SSH sessions on the same SmartEdge router. This visual communication program copies lines from one administrator’s terminal to that of another administrator.

When communication is established, two administrators can type simultaneously, with their output appearing in separate windows. To exit, press Ctrl+x+c. The system restores the terminal to its previous state.

1.8.6   Examples

The following example displays a sample message that indicates the admin1 administrator is contacting you through the talk program:

Message from Redback Talk Daemon@Redback at 5:50 ... 

"admin1" wants to talk to you, respond with: talk admin1@local ttyp0 

1.9   targeted-hello holdtime

1.9.1   Purpose

Configures the time for which Label Distribution Protocol (LDP) targeted Hello adjacency is maintained in the absence of targeted Hello messages from an LDP neighbor.

1.9.2   Command Mode

LDP router configuration

1.9.3   Syntax Description

1.9.4   Default

The default LDP targeted Hello adjacency holdtime is 45 seconds.

1.9.5   Usage Guidelines

Use the targeted-hello holdtime command to configure the time for which LDP targeted Hello adjacency is maintained in the absence of targeted Hello messages from an LDP neighbor.

If LDP targeted Hello messages from an LDP neighbor are not received after the specified Hello holdtime, the LDP adjacency is deleted. If this is the last adjacency between the local LDP instance and an LDP neighbor, the LDP session to that LDP neighbor is torn down.

The locally configured targeted Hello holdtime as specified by the targeted-hello holdtime command is included in the targeted Hello messages sent to remote LDP neighbors. The negotiated holdtime used to timeout a targeted Hello adjacency is the minimum of the time value specified by the targeted-hello holdtime command and the Hello holdtime received in targeted Hello messages from the LDP neighbor of the adjacency.

Use the hello holdtime command in LDP router configuration mode to change the locally configured LDP link hello holdtime.

Use the targeted-hello interval command in LDP router configuration mode to change the locally configured LDP targeted hello interval.

Use the default form of this command to return to the default value of 45 seconds.

1.9.6   Examples

The following example configures a Hello holdtime of 60 seconds:

[local]Redback(config-ctx)#router ldp
[local]Redback(config-ldp)#targeted-hello holdtime 60

1.10   targeted-hello interval

1.10.1   Purpose

Configures the interval between consecutive LDP targeted Hello messages used in extended LDP discovery.

1.10.2   Command Mode

LDP router configuration

1.10.3   Syntax Description

1.10.4   Default

The default LDP targeted Hello interval is 15 seconds.

1.10.5   Usage Guidelines

Use the targeted-hello interval command to configure the interval between consecutive LDP targeted Hello messages used in extended LDP discovery.

If the targeted Hello interval is explicitly configured, then the specified value is used to control targeted Hello interval regardless of the targeted Hello holdtime; however, if the targeted Hello interval is not explicitly configured, the targeted Hello interval used is the negotiated LDP targeted Hello holdtime divided by three. The negotiated LDP targeted Hello holdtime is the lesser of the received LDP targeted Hello holdtime and the locally configured LDP targeted Hello holdtime.

Use the targeted-hello holdtime command in LDP router configuration mode to change the locally configured LDP targeted Hello holdtime.

Use the hello holdtime command in LDP router configuration mode to change the locally configured LDP link Hello holdtime.

Use the no form of this command to use the negotiated LDP targeted Hello holdtime divided by three as the targeted-hello interval.

Use the default form of this command to return to the default value of 15 seconds.

1.10.6   Examples

The following example configures a targeted Hello interval of 10 seconds:

[local]Redback(config-ctx)#router ldp
[local]Redback(config-ldp)#targeted-hello interval 10

1.11   tcp keepalive

1.11.1   Purpose

Modifies the Transmission Control Protocol (TCP) keepalive parameters.

1.11.2   Command Mode

Global configuration

1.11.3   Syntax Description

1.11.4   Default

The values for the TCP keepalive parameters are described in the Syntax Description section.

1.11.5   Usage Guidelines

Use the tcp keepalivecommand to modify the TCP keepalive parameters.

To display the current TCP keepalive settings and TCP status, use the show tcp command (in any mode); for details about this command, see the Command List.

Use the default form of this command to return the TCP keepalive parameters to their default settings.

1.11.6   Examples

The following example shows how to change the count to 4 tries:

[local]Redback#configure 
[local]Redback(config)#tcp keepalive count 4 

1.12   tcp path-mtu-discovery

1.12.1   Purpose

Enables the negotiation of the maximum transmission unit (MTU) for Transmission Control Protocol (TCP) sessions.

1.12.2   Command Mode

Global configuration

1.12.3   Syntax Description

This command has no keywords or arguments.

1.12.4   Default

MTU negotiation is disabled.

1.12.5   Usage Guidelines

Use the tcp path-mtu-discovery command to enable the negotiation of the MTU for TCP sessions. Enabling MTU negotiation has no effect on existing TCP sessions.

TCP has the ability to dynamically discover the largest MTU that can be used on the session pipe that minimizes fragmentation and maximizes efficiency. As described in RFC 1191, Path MTU Discovery, the default size of an IP packet is 576 bytes. The IP and TCP portions of the frame occupy 40 bytes leaving 536 bytes for the data payload. This payload is referred to as the maximum segment size (MSS).

This command allows the MSS (and hence the MTU) to be negotiated. When you enter this command and start a TCP session, the SYN packet sent by the SmartEdge router contains a TCP option specifying a larger MSS. This larger MSS is the MTU of the outbound interface minus 40 bytes. If the MTU of the outbound interface is 1500 bytes, the advertised MSS is 1460.

Both the SmartEdge router and the remote router must be configured for MTU negotiation to work properly. If both routers have MTU negotiation enabled, the SYN from one router to the other contains the optional TCP value advertising the higher MSS. The returning SYN then advertises the higher MSS value. If one router has MTU negotiation enabled and the second router never advertises the larger MSS, the first router is locked into sending the default values.

Use the no or default form of this command to disable the negotiation of the MTU for TCP sessions.

1.12.6   Examples

The following example enables the negotiation of the MTU for TCP sessions:

[local]Redback(config)#tcp path-mtu-discovery 

1.13   tcp persist-state

tcp persist-state {min-system-memory memory | timeout seconds}

default tcp persist-state {min-system-memory | timeout}

no tcp persist-state

1.13.1   Purpose

Indicates when to drop a TCP session that has been in a persist state for too long.

1.13.2   Command Mode

Global configuration

1.13.3   Syntax Description

1.13.4   Default

The system drops TCP sessions that use less than 50 MB of memory and remain in the persist state for more than 600 seconds.

1.13.5   Usage Guidelines

Use the tcp persist-state command to identify the parameters around which to drop a TCP session that remains in the persist state for longer than a period of time that you specify. It is possible for a TCP peer to open many TCP connections and put them into the persist state. If these connections contain a large amount of data pending to send, the pending data can consume a significant portion of the system memory. This can deny service by using up so much system memory that other functions cannot work.

You can use this command with the show tcp brief command. This command will display your settings for the tcp persist-state command. You can use the show tcp stat command to display the number of TCP sessions that were dropped as a result of a TCP session staying too long in the persist state.

Use the default form of this command to set the system to the default settings for dropping TCP sessions. The default setting is that the system drops TCP sessions that use less than 50 MB of memory and remain in the persist state for more than 600 seconds. You can use the default form of this command with the min-system-memory keyword to set the system to the default setting for memory or with the timeout keyword to set the system to the default for time in the persist state.

Use the no form of this command to identify that the system should never drop a TCP session in the persist state.

1.13.6   Examples

The following example shows how to set the system to use the default for system memory (50 MB) while setting the time for the system to wait to drop TCP sessions to 250 seconds:

[local]Redback(config)#default tcp persist-state min-system-memory
[local]Redback(config)#tcp persist-state timeout 250

1.14   tcp-port local

1.14.1   Purpose

Assign a Transmission Control Protocol (TCP) port on which the SmartEdge router listens for Access Node Control Protocol (ANCP) sessions.

1.14.2   Command Mode

ANCP configuration

1.14.3   Syntax Description

1.14.4   Default

The default TCP port, 6,068, is assigned as the local port.

1.14.5   Usage Guidelines

Use the tcp-port local command to specify the TCP port on which the SmartEdge router listens for ANCP sessions.

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

1.14.6   Examples

The following example specifies 6070 as the port number for the local TCP port:

[local]Redback(config-ancp)#tcp-port local 6070

1.15   tcp-port remote

1.15.1   Purpose

Filter incoming new neighbor connections using the Transmission Control Protocol (TCP) port on which the SmartEdge router receives the General Switch Management Protocol (GSMP) messages from an Access Node Control Protocol (ANCP) neighbor peer.

1.15.2   Command Mode

ANCP neighbor configuration

1.15.3   Syntax Description

1.15.4   Default

If a TCP remote port number is not specified for this profile, there is no restriction on the TCP remote port number in a received GSMP adjacency protocol message from an ANCP neighbor.

1.15.5   Usage Guidelines

Use the tcp-port remote command to filter incoming new neighbor connections using the TCP port number on which the SmartEdge router receives the GSMP messages from an ANCP neighbor peer.

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

1.15.6   Examples

The following example specifies 7070 as the port number for a remote TCP port:

[local]Redback(config-ancp-neighbor)#tcp-port remote 7070

1.16   telnet

1.16.1   Purpose

Establishes a remote Telnet session from the SmartEdge router to a host.

1.16.2   Command Mode

Exec

1.16.3   Syntax Description

1.16.4   Default

None

1.16.5   Usage Guidelines

Use the telnet command to establish a Telnet session from the SmartEdge router to a host.

Note:  

By default, Telnet service is enabled in all local contexts.

Use the port argument to specify a port other than the default TCP port. Ensure that the port on the remote host is activated for Telnet.

1.16.6   Examples

The following example establishes a Telnet session with a host at IP address, 192.168.190.32:

[local]Redback>telnet 192.168.190.32

The following example establishes a Telnet session to a host at IP address, 192.168.190.32, using port 2222:

[local]Redback>telnet 192.168.190.32 2222

1.17   te-metric

1.17.1   Purpose

Specifies the traffic engineer (TE) metric for an interface that is used during Constrained Shortest Path First (CSPF) calculation.

1.17.2   Command Mode

RSVP interface configuration

1.17.3   Syntax Description

1.17.4   Default

When you do not specify a TE metric, the value is the same as the Interior Gateway Protocol (IGP) metric.

1.17.5   Usage Guidelines

Use the te-metric command to specify the TE metric for an interface that is used during CSPF calculation.

Use the no form of this command to remove the TE metric value specified on an interface.

1.17.6   Examples

The following example shows how to configure the TE metric on an interface to 15:

[local]Redback#configure

[local]Redback(config)#context local

[local]Redback(config-ctx)#router rsvp

[local]Redback(config-rsvp)#interface rsvp05

[local]Redback(config-rsvp-if)#te-metric 15

1.18   terminal length

1.18.1   Purpose

Sets the terminal length to be used for the administrator’s terminal for the duration of the current exec session.

1.18.2   Command Mode

Exec

1.18.3   Syntax Description

1.18.4   Default

The default terminal length is 24 lines.

1.18.5   Usage Guidelines

Use the terminal length command to set the length in terminal lines for an exec session. Upon exit of the exec session, the value is reset to the default length of 24 lines. Setting the terminal length to 0 disables auto-more processing.

Use the default form of this command to return the terminal length to the default value.

1.18.6   Examples

The following command sets the session terminal length to 30 lines:

[local]Redback>terminal length 30

1.19   terminal monitor

1.19.1   Purpose

Enables the display of system events on a remote (Telnet or Secure Shell [SSH]) session continuously as they are logged.

1.19.2   Command Mode

Exec

1.19.3   Syntax Description

This command has no keywords or arguments.

1.19.4   Default

Events are not logged to administrator terminals.

1.19.5   Usage Guidelines

Use the terminal monitor command to enable the display of events on the current terminal. This command can be useful for viewing the Event Log output while connected to a system by Telnet or SSH, rather than while working on the console.

Use the no form of this command to disable terminal monitoring.

1.19.6   Examples

The following example enables the display of logged events on the current terminal while connected using Telnet:

[local]Redback>terminal monitor

1.20   terminal width

1.20.1   Purpose

Sets the terminal width in characters to be used for the administrator’s terminal for the duration of the current exec session.

1.20.2   Command Mode

Exec

1.20.3   Syntax Description

1.20.4   Default

The default terminal width is 80 characters.

1.20.5   Usage Guidelines

Use the terminal width command to set the width in characters of the terminal for an exec session. Upon exit from this session, the value is reset to the default width of 80 characters.

Use the default form of this command to change the terminal width to the default value.

1.20.6   Examples

The following command changes the session terminal width to 70 characters:

[local]Redback>terminal width 70

1.21   test aaa

1.21.1   Purpose

Tests the communications link to a Remote Authentication Dial-In User Service (RADIUS) server.

1.21.2   Command Mode

Exec (10)

1.21.3   Syntax Description

1.21.4   Default

None

1.21.5   Usage Guidelines

Use the test aaa command to test the communications link to a RADIUS server. The SmartEdge router creates an authentication or accounting message that includes the specified username and transmits it to the server as specified by the server-ip ip-addr port construct.

Note:  

You must access the context in which the servers are configured before you can run this test.

The response from the specified server occurs asynchronously; that is, the command-line interface (CLI) prompt appears immediately after you enter the command, but the system might not display the results from the server immediately. (The length of time depends on the timeout value configured for the context.)

Table 1 lists the fields that the system displays for the test aaa command.

1.21.6   Examples

The following example tests the communications link with a RADIUS authentication message:

[local]Redback#test aaa authentication username b-32@local protocol 
radius server-ip 10.1.1.10 1645

Apr 29 20:22:03: %AAA-7-AUTHEN: aaa_idx 92: Sending RADIUS_SERVER_TEST

to radius.

  Pid 146: Testing radius server ...

[local]Redback#

        Radius authentication test response:

           Server:           10.1.1.10/1645

           Server response:  Accepted.

           ------------------------------

           Attributes list:

           User-Name = b-32@local

           NAS_Identifier = Redback

           NAS-Port = 16842817

           NAS-Port-Type = 0

           Platform_Type = 2

           OS_Version = 4.0.5

           Service-Type = 2

           Framed-IP-Address = 255.255.255.254

           ------------------------------

           Send count:       1

           Send time:        Apr 29 20:22:03 2005

           Response time:    Apr 29 20:22:03 2005

The following example tests the communications link with a RADIUS accounting message:

[local]Redback#test aaa accounting username b-32@local protocol 
radius server-ip 10.1.1.10 1646

Apr 29 20:30:24: %AAA-7-AUTHEN: aaa_idx 92: Sending RADIUS_SERVER_TEST

to radius.

  Pid 146: Testing radius server ...

[local]Redback#

        Radius accounting test response:

           Server:           10.1.1.10/1646

           Server response:  Accepted.

           Send count:       1

           Send time:        Apr 29 20:30:24 2005

           Response time:    Apr 29 20:30:24 2005

The following example tests the communications link with a RADIUS authentication message when the server is shut down:

[local]Redback#test aaa authentication username b-32@local protocol radius server-ip 10.1.1.10 1645

Apr 29 20:31:09: %AAA-7-AUTHEN: aaa_idx 92: Sending RADIUS_SERVER_TEST to radius.
  Pid 146: Testing radius server ...
        Radius authentication test response:
           Server:           10.1.1.10/1645
           Server response:  Timeout.
           Send count:       4
           Send time:        Apr 29 20:31:09 2005

1.22   threshold

1.22.1   Purpose

Specifies the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) signal degrade bit error rate (SD-BER) or signal fail BER (SF-BER) threshold for a SONET/SDH or WAN-PHY port.

1.22.2   Command Mode

• ATM OC configuration
• Port configuration

1.22.3   Syntax Description

1.22.4   Default

The default thresholds for SD-BER and SF-BER are 10E-7 and 10E-4, respectively.

1.22.5   Usage Guidelines

Use the threshold command to specify the SONET/SDH SD-SER or SF-BER threshold for a SONET/SDH or WAN-PHY port.

Note:  

This command does not apply to channelized OC-12 ports.

Use the no or default form of this command to specify the default values for the SF-BER and SD-BER thresholds.

1.22.6   Examples

[local]Redback(config)#port atm 3/1
[local]Redback(config-atm-oc)#threshold sd-ber 8
[local]Redback(config-atm-oc)#threshold sf-ber 6

[local]Redback(config)#port ethernet 3/1 wan-phy
Note: Creating a port may cause the card to reload. Commit to continue; abort to exit without change
[local]Redback(config-port)#commit
[local]Redback(config-port)#threshold sd-ber 8
[local]Redback(config-port)#threshold sf-ber 6

1.23   threshold (malicious traffic)

1.23.1   Purpose

Specifies the high and low threshold values for malicious traffic alarms.

1.23.2   Command Mode

Malicious-traffic alarms configuration mode

1.23.3   Syntax Description

1.23.4   Default

The high threshold has a default value of 100,000, and the low threshold has a default value of 10,000.

1.23.5   Usage Guidelines

Use the threshold command to specify the high and low threshold values, in packets, for malicious traffic alarms.

Use the no form of this command to remove the alarm threshold settings.

For information about detecting and monitoring malicious traffic, see Configuring Malicious Traffic Detection and Monitoring.

1.23.6   Examples

The following example shows how to specify a high threshold of 300,000 packets and a low threshold of 5000 packets:

[local]Redback(config-malicious-traffic-alarms)#threshold high 300000 low 5000

1.24   time-out

1.24.1   Purpose

Specifies the number of seconds for the router to wait for a dynamic tunnel to be established before bringing the current subscriber or visitor down.

1.24.2   Command Mode

Dynamic Tunnel Profile configuration

1.24.3   Syntax Description

1.24.4   Default

3 seconds

1.24.5   Usage Guidelines

Use the time-out command to specify the number of seconds for the router to wait for a dynamic tunnel to be established before bringing the current subscriber or visitor down.

Use the no or default form of this command to restore the setting to its default value of 3 seconds.

1.24.6   Examples

The following example shows how to set the timeout for prof1 to 10 seconds:

[local]Redback(config)#context local
[local]Redback(config-ctx)#router mobile-ip
[local]Redback(config-mip)#dynamic-tunnel-profile prof1
[local]Redback(config-mip-dyn-tun1-profile)#time-out 10
[local]Redback(config-mip-dyn-tun1-profile)#end

1.25   timeout abandoned

1.25.1   Purpose

Configures the timeout value for P2MP TCP sessions that have no active parent session.

1.25.2   Command Mode

NAT policy configuration

1.25.3   Syntax Description

1.25.4   Default

The default value is 2 hours 4 minutes.

1.25.5   Usage Guidelines

1.25.6   Example

1.26   timeout (HTTP redirect)

1.26.1   Purpose

Sets the maximum time the SmartEdge router displays the customized http-redirect message to the subscriber before the subscriber HTTP session is redirected to the preconfigured URL.

1.26.2   Command Mode

HTTP redirect profile configuration

1.26.3   Syntax Description

1.26.4   Default

The default timeout is 1 second.

1.26.5   Usage Guidelines

Use the timeout command to set the maximum time the SmartEdge router displays the customized http-redirect message to the subscriber before the subscriber HTTP session is redirected to the preconfigured URL.

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

1.26.6   Examples

The following example shows how to configure an HTTP redirect message and a timeout for the http-redirect profile ericsson:

[local]Redback(config)#http-redirect profile ericsson 

[local]Redback(config-hr-profile)#message “Please wait while you are 
redirected to the portal server. Thank you.”

[local]Redback(config-hr-profile)#timeout 20

1.27   timeout (L2TP Peers)

1.27.1   Purpose

Specifies the amount of time to wait for an acknowledgment before a control message is retransmitted to a Layer 2 Tunneling Protocol (L2TP) peer.

1.27.2   Command Mode

L2TP peer configuration

1.27.3   Syntax Description

1.27.4   Default

3 seconds.

1.27.5   Usage Guidelines

Use the timeout command to specify the amount of time to wait for an acknowledgment before a control message is retransmitted to an L2TP peer. You need only increase the value if many sessions are established or if the media is slow.

Use the no or default form of this command to reset the timeout to the default.

1.27.6   Examples

The following example shows how to configure the peer so that retransmission of a control message occurs after 5 seconds without an acknowledgment:

[local]Redback(config-ctx)#l2tp-peer name peer1

[local]Redback(config-l2tp)#timeout 5

1.28   timeout login

1.28.1   Purpose

Sets the amount of time the system waits before timing out during a logon attempt after a Telnet or SSH (Secure Shell) session starts.

1.28.2   Command Mode

Global configuration

1.28.3   Syntax Description

1.28.4   Default

The system waits 10 minutes for a response during a logon attempt after a Telnet or SSH session starts.

1.28.5   Usage Guidelines

Use the timeout login command to set the amount of time the system waits before timing out during log on attempt after a Telnet or SSH session starts.

Use the no form of this command to disable the logon timeout value.

Use the default form of this command to configure the default logon timeout value.

1.28.6   Examples

The following example configures the system to time out if a user does not enter logon information for 5 minutes:

[local]Redback(config)#timeout login response 5 

1.29   timeout (NAT)

1.29.1   Command Mode

• NAT policy configuration
• Policy group class configuration

1.29.2   Syntax Description

1.29.3   Default

For default values, see the Syntax Description section. For the ignore action in a NAT policy, all default timeouts are 20 seconds.

1.29.4   Usage Guidelines

Use the timeout command to modify the period after which NAT times out if no activity occurs. Timeout applies only if there is relevant translation.

Use the no form of this command to reset the timeout to its default value.

1.29.5   Examples

The following example configures basic NAT to time out after no activity has occurred for 7200 seconds (2 hours):

[local]Redback(config-ctx)#ip nat pool NAT-POOL
[local]Redback(config-nat-pool)#address 171.71.71.0/24
[local]Redback(config-nat-pool)#exit
[local]Redback(config-ctx)#nat policy NAT-1
[local]Redback(config-policy-nat)#pool NAT-POOL local
[local]Redback(config-policy-nat)#timeout basic 7200

The following example configures an enhanced NAT policy with a class that times out P2MP TCP sessions with no parent sessions after one hour (3600 seconds):

[local]Redback(config)#context nat-context
[local]Redback(config-ctx)#nat policy nat-policy-1 enhanced
[local]Redback(config-policy-nat)#pool nat-pool-1 nat-context   
[local]Redback(config-policy-nat)#access-group nat-acl
[local]Redback(config-policy-acl)#class nat-class
[local]Redback(config-policy-acl-class)#timeout abandoned 3600

Typically, more attributes would be added to the policy.

1.30   timeout session

1.30.1   Purpose

Specifies the maximum idle timeout for any administrator account or administrator sessions on the console port (in global configuration mode), or disables the global or administrator session idle timer.

1.30.2   Command Mode

• Administrator configuration
• Global configuration

1.30.3   Syntax Description

1.30.4   Default

The maximum session idle time for the administrator account is governed by the global session idle timer. The maximum session idle time is 10 minutes.

1.30.5   Usage Guidelines

Use the timeout session idle command to specify the maximum idle time for any administrator account session, or disable the global or administrator session idle timer. When specified, the system disconnects any session with no input for the specified time. The value that you specify in the administrator session overrides the value specified for the global session idle timer; if disabled, there is no timeout value.

To specify a different timeout session for a specific administrator, use this command (in administrator configuration mode); the value you specify for a specific administrator overrides the value specified for the global session idle timer.

Use the no form of this command to disable the global session idle timer; the global form of the command does not affect the session idle timer for a specific administrator.

Use the default form of this command to specify the default value for the global session idle timer.

1.30.6   Examples

The following example configures the system to disconnect any administrator session after remaining idle for 30 minutes:

[local]Redback(config)#timeout session idle 30 

The following example specifies the session idle timer for this administrator to 60 minutes. This value overrides the value specified for the global session idle timer:

[local]Redback(config-administrator)#timeout session idle 60 

1.31   timeout (subscriber)

1.31.1   Purpose

Configures the absolute or idle session timeout criteria for a subscriber session.

1.31.2   Command Mode

Subscriber configuration

1.31.3   Syntax Description

1.31.4   Default

Subscriber sessions do not time out. Idle timeouts, if configured, apply to traffic in both the send and receive directions, and the bytes-per-second threshold is zero.

1.31.5   Usage Guidelines

Use the timeout command to set the absolute or idle session timeout criteria for a subscriber session. The system terminates subscriber sessions when they reach timeout.

Note:  

This command applies to either locally terminated or Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC) subscriber sessions.

Note:  

Keepalive messages are not considered traffic for purposes of measuring idle time.

Use the no forms of this command to restore the default behaviors.

1.31.6   Examples

The following example sets an absolute timeout value of 20 minutes:

[local]Redback(config-sub)#timeout absolute 20

1.32   timer retry

1.32.1   Purpose

Specifies the interval that the headend (ingress) router waits between attempts to establish the primary path during Constrained Shortest Path First (CSPF) calculation.

1.32.2   Command Mode

• RSVP router configuration

1.32.3   Syntax Description

1.32.4   Default

The ingress router waits for 30 seconds between attempts to establish the primary path.

1.32.5   Usage Guidelines

Use the timer retry command to specify the interval that the ingress router waits between attempts to establish the primary path during CSPF calculation.

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

1.32.6   Examples

The following example shows how to specify that the ingress router wait 5 seconds between attempts to establish the primary path:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#router rsvp
[local]Redback(config-rsvp)#timer retry 5

1.33   timers active-open

1.33.1   Purpose

Specifies the interval the router waits for a BGP peer to come up after a graceful restart before starting the best path computation.

1.33.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration

1.33.3   Syntax Description

1.33.4   Default

The router waits 20 seconds for a BGP peer to come up before starting the best path computation.

1.33.5   Usage Guidelines

Use the timers active-open command to specify the interval the router waits for a BGP peer to come up after a graceful restart before starting the best path computation.

Note:  

For BGP sessions over port pseudowires, we recommend setting the timers active-open interval to be 40 seconds or more. This is because the port pseudowire typically takes 30 seconds to come up after a switchover.

The timers active-open interval configuration for a BGP neighbor (in BGP neighbor configuration mode) takes precedence over an interval configuration for a peer group (in BGP peer group configuration mode). For example, if you specify an interval of 40 seconds for a BGP neighbor that is part of a peer group that has a timers active-open interval of 20 seconds, the BGP neighbor interval (40 seconds) overrides the peer group interval of 20 seconds.

Use the no or default form of this command to return the router to the default configuration, where the router waits 20 seconds for a BGP peer to come up before starting the best path computation.

1.33.6   Examples

1.33.6.1   Configuring the timers active-open Interval for a BGP Neighbor (Peer)

The following example configures the router to wait 40 seconds for the BGP peer (whose IP address is 123.45.34.2) to come up after a graceful restart before starting the best path computation:

[local]Redback(config-ctx)#router bgp 100
[local]Redback(config-bgp)#neighbor 123.45.34.2 external
[local]Redback(config-bgp-neighbor)#timers active-open 40

1.33.6.2   Configuring the timers active-open Interval for a BGP Peer-Group and a BGP Neighbor (Peer)

The following example configures the router to:

• Wait 50 seconds for any BGP peer in peer group sanjose to come up after gracefully restarting before starting the best path computation.
• Wait 100 seconds for a particular peer (whose IP address is 123.45.34.2) to come up after a graceful restart before starting the best path computation

If the peer on IP address 123.45.34.2 is part of the peer group sanjose, the router waits 100 seconds for that peer to come up before starting best path computation. This is because the timers active-open interval configuration in BGP neighbor configuration mode takes precedence over the timers active-open interval configuration in BGP peer group configuration mode.

[local]Redback(config-ctx)#router bgp 65

[local]Redback(config-bgp)#peer-group sanjose external

[local]Redback(config-bgp-peer-group)#timers active-open 50

[local]Redback(config-bgp-peer-group)#exit

[local]Redback(config-bgp)#neighbor 123.45.34.2 external

[local]Redback(config-bgp-neighbor)#peer-group sanjose

[local]Redback(config-bgp-neighbor)#timers active-open 100

1.34   timers basic

1.34.1   Purpose

Modifies the Routing Information Protocol (RIP) or RIP next generation (RIPng) timers for the specified RIP or RIPng instance or interface.

1.34.2   Command Mode

• RIP interface configuration
• RIPng interface configuration
• RIPng router configuration
• RIP router configuration

1.34.3   Syntax Description

1.34.4   Default

RIP and RIPng updates are sent every 30 seconds, a route is declared invalid if an update is not received after 180 seconds, better routes are released after 180 seconds, and a route is flushed from the routing table after 240 seconds.

1.34.5   Usage Guidelines

Use the timers basic command in RIP or RIPng interface configuration mode to modify the RIP or RIPng timers for the specified interface.

Use the timers basic command in RIP or RIPng router configuration mode to modify the RIP or RIPng timers for the specified instance.

Use the no or default form of this command to restore the default RIP or RIPng timer settings.

1.34.6   Examples

The following example sets the RIP timers for the RIP instance rip001. The update interval is set to 45 seconds, the invalid interval to 200 seconds, the holddown interval to 200 seconds, and the flush interval to 260 seconds:

[local]Redback(config-ctx)#rip001
[local]Redback(config-rip)#timers basic 45 200 200 260

The following example modifies the RIP timers for the fe01 interface. The update interval is set to 45 seconds, the invalid interval to 200 seconds, the holddown interval to 200 seconds, and the flush interval to 260 seconds:

[local]Redback(config-ctx)#router rip rip002

[local]Redback(config-rip)#interface fe01

[local]Redback(config-rip-if)#timers basic 45 200 200 260

1.35   timers keepalive

1.35.1   Purpose

Modifies Border Gateway Protocol (BGP) timers for the routing instance, neighbor, or peer group.

1.35.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration
• BGP router configuration

1.35.3   Syntax Description

1.35.4   Default

The keepalive time is 60 seconds. The hold time is 180 seconds.

1.35.5   Usage Guidelines

Use the timers keepalive command in BGP router configuration mode to modify keepalive and hold time timers for all BGP neighbors.

Use the timers keepalive command in BGP neighbor configuration mode to modify keepalive and hold time timers for a specific neighbor. Values set for a BGP neighbor override the values set for the BGP routing instance.

Use the timers keepalive command in BGP peer group configuration mode to modify keepalive and hold time timers for a peer group.

Note:  

If a neighbor is part of a peer group, and you try to apply this command in BGP neighbor configuration mode, the timer conditions are not applied to the neighbor. Use the timers keepalive command in BGP peer group configuration mode instead.

Use the no form of this command to restore timer settings to their default values.

1.35.6   Examples

The following example sets the keepalive period to 45 seconds and the holdtime to 135 seconds for only the neighbor at IP address 123.45.34.2:

[local]Redback(config-ctx)#router bgp 100
[local]Redback(config-bgp)#neighbor 123.45.34.2 external
[local]Redback(config-bgp-neighbor)#timers keepalive 45 holdtime 135

1.36   timeslot

timeslot start1 – end1, [start2 – end2,...]

default timeslot

1.36.1   Purpose

Defines a one or more groups of timeslots in a channelized DS1 or E1 channel (fractional T1/E1).

1.36.2   Command Mode

DS-0 group configuration

1.36.3   Syntax Description

1.36.4   Default

Only the starting timeslot is provisioned.

1.36.5   Usage Guidelines

The timeslot command defines one or more DS0 subchannels added to the starting DS0 subchannel (also known as a timeslot) within the parent DS1 or E1 (fractional T1/E1).

Note:  

The starting timeslot is defined as the timeslot provisioned by the port ds0s command prior to entering the timeslot command.

• You can only specify DS0 timeslots that are greater than or equal to the starting timeslot within the parent DS1 or E1 (fractional T1/E1). The port ds0s command identifies the lowest numbered timeslot for the subchannel within its parent DS1 or E1.
• The starting DS0 timeslot is the subchannel set by the port ds0s command in its nxds0-channel-id argument.
• The timeslot command adds additional timeslots to the current DS0 subchannel.
• Each channelized DS1 channel is comprised of 24 NxDS0 (DS0s, DS0- Group) or up 24 timeslots for single NxDS0 starting from the timeslot number 1.
• Each channelized E1 channel is comprised of 31 NxDS0 (DS0s, DS0- Group) or up 31 timeslots for single NxDS0 starting from the timeslot number 1..
• See the timeslot command for details.

1.36.6   Examples

In the following example, the port ds0s 2/1:2:3:1 command establishes timeslot 1 as the default. The timeslot 1-12 command adds timeslots 2 through 12 to the NxDS0 group (fractional T1).

config
!
service multiple-contexts
!
software license
 all-ports password <plain text passcode> card ch-oc3oc12-8or2-port slot 2
!
!
card ch-oc3oc12-8or2-port 2
 no shutdown
 clock-source global-reference
!
!
! Example for POS, using SDH AUG mapping au3-no-tug to channelize:
! chSTM1 -> DS3
! chSTM1 -> chDS3
! chSTM1 -> chDS3 -> DS1
! chSTM1 -> chDS3 -> chDS1 -> DS0s
! chSTM1 -> chDS3
! chSTM1 -> chDS3 -> E1
! chSTM1 -> chDS3 -> chE1 -> DS0s
!
port channelized-stm1 2/1 pos
 no shutdown
 aug-mapping au3-no-tug
 clock-source card-reference
 !
 port ds3 2/1:1
  no shutdown
  clock-source card-reference
  encapsulation ppp
  bind interface pos_chstm1->ds3_1 redkite1
 !
 port channelized-ds3 2/1:2
  no shutdown
  clock-source card-reference
 !
  port ds1 2/1:2:1
   no shutdown
   clock-source card-reference
   encapsulation ppp
   bind interface pos_chstm1->chds3->ds1_1 redkite1
  !
  port ds1 2/1:2:2
   no shutdown
   clock-source card-reference
   bind interface pos_chstm1->chds3->ds1_2 redkite1
  !
  port channelized-ds1 2/1:2:3
   no shutdown
   clock-source card-reference
  !
   port ds0s 2/1:2:3:1
    no shutdown
    timeslot 1-12
    encapsulation ppp
    bind interface pos_chstm1->chds3->chds1->ds0s_1 redkite1

1.37   timers password

1.37.1   Purpose

Configures the time interval, in seconds, during which an old Message Digest 5 (MD5) password can coexist with a new MD5 password for authentication.

1.37.2   Command Mode

BGP router configuration

1.37.3   Syntax Description

1.37.4   Default

The timer interval is set to 1,800 seconds.

1.37.5   Usage Guidelines

Use the timers password command to configure the time interval, in seconds, during which an old MD5 password can coexist with a new MD5 password for authentication. Configuring the password timer interval affects only the Border Gateway Protocol (BGP) peers which have existing MD5 passwords replaced after this configuration is committed.

1.37.6   Examples

The following example allows new MD5 passwords for BGP peers to coexist with the password being replaced for 300 seconds (5 minutes):

[local]Redback(config-ctx)#router bgp 1000
[local]Redback(config-bgp)#timers password 300

1.38   traceroute

1.38.1   Purpose

Traces the IP route that packets take when traveling to the specified destination.

1.38.2   Command Mode

• Exec

1.38.3   Syntax Description

1.38.4   Default

The traceroute command sends three 140-byte packets on UDP port 33434, using a timeout of 2 seconds and a time to live value of 30.

1.38.5   Usage Guidelines

Use the traceroute command to trace the routes that packets take when traveling to the specified destination. Each line in the display shows the next hop in the path between the system and the destination address.

You can only use the hostname argument if DNS is enabled via the ip domain-lookup, ip domain-name, and ip name-servers commands (in context configuration mode). For more information about these commands, see Configuring DNS.

If the destination IP address of the traced route results in the packet going through a Multiprotocol Label Switching (MPLS) label-switched path (LSP), the output displays the label stack along each hop of the LSP.

The ping and traceroute commands (in exec mode) can have vastly different outcomes, depending on the context in which the commands are issued. In particular, a destination (as denoted by an IP address) that can be reached by the ping or traceroute command in one context might not be reachable from another context.

Press Ctrl+C to stop a traceroute.

1.38.6   Examples

The following command discovers the route from the local context to the IP address 206.124.29.1, using 100-byte packets, UDP port 73, ttl 20, timeout 3, and count 3:

[local]Redback>traceroute 206.124.29.1 timeout 3 count 3 maxttl 20 
port 73 size 100

traceroute to (206.124.29.1), 20 hops max, 140 byte packets

 1  155.53.145.254 (155.53.145.254)     0 ms  0 ms  0 ms

 2  155.53.200.254 (155.53.200.254)     0 ms  0 ms 16 ms

 3  206.83.66.193 (206.83.66.193)      16 ms 16 ms 16 ms

 4  206.83.90.66 (206.83.90.66)        16 ms 16 ms 16 ms

 5  157.130.193.197 (157.130.193.197)  16 ms 33 ms 16 ms

 6  157.130.194.18 (157.130.194.18)    16 ms 33 ms 16 ms

 7  209.104.192.49 (209.104.192.49)    50 ms 66 ms 50 ms

 8  209.104.198.38 (209.104.198.38)    50 ms 66 ms 66 ms

 9  206.124.1.22 (206.124.1.22)        66 ms 66 ms 66 ms

10  206.124.29.1 (206.124.29.1)        83 ms 66 ms 83 ms

The following example displays a destination IP address of a traced route resulting in the packet going through an MPLS LSP, and includes the label stack along each hop of the LSP:

[local]Redback>traceroute 5.5.5.5

se_traceroute to 5.5.5.5 (5.5.5.5), 30 hops max, 40 byte packets

 1  100.1.1.1 (100.1.1.1)   4.749 ms  4.111 ms  3.986 ms

 2  40.1.1.2 (40.1.1.2)   6.321 ms  6.457 ms  5.289 ms

         MplsLabel: 19 MplsExpBits: 0 TTL: 1

         MplsLabel: 786434 MplsExpBits: 0 TTL: 1

 3  60.1.1.1 (60.1.1.1)   3.815 ms  4.159 ms  4.120 ms

         MplsLabel: 786434 MplsExpBits: 0 TTL: 1

 4  5.5.5.5 (5.5.5.5)   5.870 ms  9.108 ms  6.639 ms

1.39   traceroute ipv6

1.39.1   Purpose

Traces the IP route that IPv6 packets take when traveling to the specified destination.

1.39.2   Command Mode

Exec

1.39.3   Syntax Description

1.39.4   Default

The traceroute ipv6 command sends three 140-byte packets on UDP port 33434, using a timeout of 2 seconds and a time to live value of 30.

1.39.5   Usage Guidelines

Use the traceroute ipv6 command to trace the routes that packets take when traveling to the specified destination. Each line in the display shows the next hop in the path between the system and the destination address.

You can only use the hostname argument if DNS is enabled via the ip domain-lookup, ip domain-name, and ipv6 name-servers commands (in context configuration mode). For more information about these commands, see Configuring DNS.

If the destination IPv6 address of the traced route results in the packet going through a Multiprotocol Label Switching (MPLS) label-switched path (LSP), the output displays the label stack along each hop of the LSP.

The ping ipv6 and traceroute ipv6 commands (in exec mode) can have vastly different outcomes, depending on the context in which the commands are issued. In particular, a destination (as denoted by an IPv6 address) that can be reached by the ping ipv6 or traceroute ipv6 command in one context might not be reachable from another context.

Press Ctrl+C to stop a traceroute.

1.39.6   Examples

1.39.6.1   IPV6 Trace Route

The following command discovers the route from the vpn1 context to the IPv6 address 77::103. This example displays output for a route with three labels:

[vpn1]PE>traceroute ipv6 77::103 

traceroute6 to 77::103 from 11::100, 30 hops max, 12 byte packets
 1  ::ffff:19.20.21.2  3.504 ms  3.263 ms  3.616 ms
         MplsLabel: 589826 MplsExpBits: 0 TTL: 1
         MplsLabel: 589825 MplsExpBits: 0 TTL: 1
 2  ::ffff:20.20.20.102  2.784 ms  3.118 ms  3.094 ms
         MplsLabel: 589826 MplsExpBits: 0 TTL: 1
         MplsLabel: 589825 MplsExpBits: 0 TTL: 2
 3  * * *                                              
 4  fe80::230:88ff:fe04:3009  3.146 ms  2.695 ms  3.016 

[local]PE#show bgp route ipv4 vpn labels

VPN RD: 100.100.100.100:1
Network            Next Hop            Rcv Label      Alloc Label
11.11.11.100/32    0.0.0.0                nolabel        589826
15.16.17.0/24      0.0.0.0                nolabel        589826
77.77.77.103/32    100.100.100.103        589826         nolabel

VPN RD: 100.100.100.103:1
Network            Next Hop            Rcv Label      Alloc Label
77.77.77.103/32    100.100.100.103        589826         nolabel
[local]PE1# 
         
[vpn1]PE#show ipv6 route
Codes: C - connected, S - static, S dv - dvsr, R - RIP, e B - EBGP, i B - IBGP
       O   - OSPF, O3  - OSPFv3, IA - OSPF(v3) inter-area,
       N1  - OSPF(v3) NSSA external type 1, N2  - OSPF(v3) NSSA external type 2
       E1  - OSPF(v3) external type 1, E2  - OSPF(v3) external type 2
       i   - IS-IS, L1 - IS-IS level-1,  L2  - IS-IS level-2, N - NAT
       IPH - IP Host, SUB A - Subscriber address, SUB S - Subscriber static
       SUB P - AAA downloaded aggregate subscriber routes
       SUB N - Subscriber ND, SUB D - Subscriber DHCP-PD
       M F - Mobile Sub Foreign Agent, M H - Mobile Sub Home Agent
       M G - Mobile Sub GTP
       A - Derived Default, MeH - Media Nexthop
       >   - Active Route, * - LSP

Type    Network             Next Hop        Dist  Metric    UpTime  Interface

> C     11::100/128         11::100            0       0  06:09:06  net1
> C     17::/64                                0       0  06:08:58  to-CE1
> e B   18::100/128         17::2             20       0  06:08:36  to-CE1
> e B   77::103/128         100.100.100.103   20       0  06:06:18
> e B   88::/64             100.100.100.103   20       0  06:06:06
> e B   99::103/128         100.100.100.103   20       0  06:06:06
> e B   200::/64            17::2             20       0  05:30:00  to-CE1
> e B   300::/64            17::2             20       0  05:30:00  to-CE1
> e B   400::/64            17::2             20       0  05:30:00  to-CE1
> e B   500::/64            17::2             20       0  05:30:00  to-CE1
> e B   600::/64            17::2             20       0  05:30:00  to-CE1
> e B   800::/64            100.100.100.103   20       0  05:30:30
> e B   3dde::1/128         17::2             20       0  05:28:10  to-CE1
> e B   3ffe::1/128         17::2             20       0  05:28:10  to-CE1
> e B   4000:0:2:1::/64     17::2             20       0  05:28:40  to-CE1
> e B   8bbc::1/128         17::2             20       0  05:28:40  to-CE1
> e B   8f82::/64           17::2             20       0  05:28:10  to-CE1
> e B   f2cb::/64           100.100.100.103   20       0  05:27:40
[     

[vpn1]PE#show nd neighbor
IPv6 Address                            Age    Link-layer Addr   State  Circuit
17::1                                   0      00:30:88:15:b0:c7 intf   1/3 vlan-id 1
17::2                                   60     00:30:88:15:b0:c8 probe  1/3 vlan-id 1
fe80::230:88ff:fe15:b0c7                0      00:30:88:15:b0:c7 intf   1/3 vlan-id 1
fe80::230:88ff:fe15:b0c8                76     00:30:88:15:b0:c8 probe  1/3 vlan-id 1
 



! PE2 is the node on the remote end of the route. 

[CE2]PE2#show ipv6 route
Codes: C - connected, S - static, S dv - dvsr, R - RIP, e B - EBGP, i B - IBGP
       O   - OSPF, O3  - OSPFv3, IA - OSPF(v3) inter-area,
       N1  - OSPF(v3) NSSA external type 1, N2  - OSPF(v3) NSSA external type 2
       E1  - OSPF(v3) external type 1, E2  - OSPF(v3) external type 2
       i   - IS-IS, L1 - IS-IS level-1,  L2  - IS-IS level-2, N - NAT
       IPH - IP Host, SUB A - Subscriber address, SUB S - Subscriber static
       SUB P - AAA downloaded aggregate subscriber routes
       SUB N - Subscriber ND, SUB D - Subscriber DHCP-PD
       M F - Mobile Sub Foreign Agent, M H - Mobile Sub Home Agent
       M G - Mobile Sub GTP
       A - Derived Default, MeH - Media Nexthop
       >   - Active Route, * - LSP

Type    Network             Next Hop        Dist  Metric    UpTime  Interface

> e B   11::100/128         88::2             20       0  06:12:29  to-vpn-smith
> e B   17::/64             88::2             20       0  06:12:29  to-vpn-smith
> e B   18::100/128         88::2             20       0  06:12:29  to-vpn-smith
> e B   77::103/128         88::2             20       0  06:14:30  to-vpn-smith
> C     88::/64                                0       0  06:14:50  to-vpn-smith
> C     99::103/128         99::103            0       0  06:15:00  loCE2
> e B   200::/64            88::2             20       0  05:36:12  to-vpn-smith
> e B   300::/64            88::2             20       0  05:36:12  to-vpn-smith
> e B   400::/64            88::2             20       0  05:36:12  to-vpn-smith
> e B   500::/64            88::2             20       0  05:36:12  to-vpn-smith
> e B   600::/64            88::2             20       0  05:36:12  to-vpn-smith
> C     800::/64                               0       0  05:36:42  bgp1
> e B   3dde::1/128         88::2             20       0  05:33:52  to-vpn-smith
> e B   3ffe::1/128         88::2             20       0  05:33:52  to-vpn-smith
> e B   4000:0:2:1::/64     88::2             20       0  05:34:52  to-vpn-smith
> e B   8bbc::1/128         88::2             20       0  05:34:52  to-vpn-smith
> e B   8f82::/64           88::2             20       0  05:34:22  to-vpn-smith
> i B   f2cb::/64           800::2           200       0  05:34:40

1.39.6.2   MPLS LSP Trace Route

The following example displays a destination IP address of a traced route resulting in the packet going through an MPLS LSP, and includes the label stack along each hop of the LSP:

[local]Redback>traceroute 5.5.5.5

se_traceroute to 5.5.5.5 (5.5.5.5), 30 hops max, 40 byte packets

 1  100.1.1.1 (100.1.1.1)   4.749 ms  4.111 ms  3.986 ms

 2  40.1.1.2 (40.1.1.2)   6.321 ms  6.457 ms  5.289 ms

         MplsLabel: 19 MplsExpBits: 0 TTL: 1

         MplsLabel: 786434 MplsExpBits: 0 TTL: 1

 3  60.1.1.1 (60.1.1.1)   3.815 ms  4.159 ms  4.120 ms

         MplsLabel: 786434 MplsExpBits: 0 TTL: 1

 4  5.5.5.5 (5.5.5.5)   5.870 ms  9.108 ms  6.639 ms

1.40   traceroute mpls

1.40.1   Purpose

Initiates a Multiprotocol Label Switching (MPLS) trace across a Resource Reservation Protocol (RSVP) label-switched path (LSP) or a Label Distribution Protocol (LDP) LSP.

1.40.2   Command Mode

All modes

1.40.3   Syntax Description

1.40.4   Default

None

1.40.5   Usage Guidelines

Use the traceroute mpls command to initiate a MPLS trace across a RSVP LSP or a LDP LSP. This command is useful for troubleshooting MPLS networks.

Use the lsp-name or ip-address argument to display information only for the specified LSP, or use any of the available keywords to display LSP information only for the specified keyword.

Note:  

By default, most show commands (in any mode) display information for the current context only or, depending on the command syntax, for all contexts. If you are an administrator for the local context, you can insert the optional context ctx-name construct, preceding the show command, to view output for the specified context without entering that context. For more information about using the context ctx-name construct, see the context command.

Note:  

By appending a space followed by the pipe ( | ) character at the end of a show command, you can filter the output using a set of modifier keywords and arguments. For more information, see Modifying Output of show Commands in Using the CLI.

1.40.6   Examples

The following example shows how to initiate an MPLS trace across a LDP LSP. This LSP contains an equal-cost multi-path (ECMP) next-hop entry at the transit node:

[local]Redback>traceroute mpls ldp 80.1.1.0/24 range 127.0.0.0.1 127.0.0.10 1
Sending 5 100-byte MPLS echos to LDP 80.1.1.0/24, source 180.180.180.180, 
timeout is 1 second, send interval is 0 msec: 
Pkt Hop       Recv Intf       Down Intf        Down Nbr  RTT  MTU  RC
  1   0       N/A             20.1.1.4         20.1.1.4    0    0  Ingress
  1   1       20.1.1.4         60.1.1.1        60.1.1.1    8    0  Transit
                               60.1.2.1        60.1.2.1
  1   2        60.1.1.1             N/A             N/A    8    0  Egress
  2   0             N/A        20.1.1.4        20.1.1.4    8    0  Ingress
  2   1        20.1.1.4        60.1.1.1        60.1.1.1    5    0  Transit
                               60.1.2.1        60.1.2.1
  2   2        60.1.2.1             N/A             N/A    5    0  Egress
  3   0             N/A        20.1.1.4        20.1.1.4    5    0  Ingress
  3   1        20.1.1.4        60.1.1.1        60.1.1.1    5    0  Transit
                               660.1.2.1        60.1.2.1
  3   2        60.1.1.1             N/A             N/A    5    0  Egress
  4   0             N/A        20.1.1.4        20.1.1.4    5    0  Ingress
  4   1        20.1.1.4        60.1.1.1        60.1.1.1    7    0  Transit
                               660.1.2.1        60.1.2.1
  4   2        60.1.2.1             N/A             N/A    6    0  Egress
  5   0             N/A        20.1.1.4        20.1.1.4    6    0  Ingress
  5   1        20.1.1.4        60.1.1.1        60.1.1.1    6    0  Transit
                               660.1.2.1        60.1.2.1
  5   2        60.1.1.1             N/A             N/A    5    0  Egress
  6   0             N/A        20.1.1.4        20.1.1.4    5    0  Ingress
  6   1        20.1.1.4        60.1.1.1        60.1.1.1    4    0  Transit
                               660.1.2.1       60.1.2.1
  6   2        60.1.2.1             N/A             N/A    5    0  Egress
  7   0             N/A        20.1.1.4        20.1.1.4    5    0  Ingress
  7   1        20.1.1.4        60.1.1.1        60.1.1.1    34   0  Transit
                               60.1.2.1        60.1.2.1
  7   2        60.1.1.1             N/A             N/A    7    0  Egress
  8   0             N/A        20.1.1.4        20.1.1.4    7    0  Ingress
  8   1        20.1.1.4        60.1.1.1        60.1.1.1    6    0  Transit
                               60.1.2.1        60.1.2.1
  8   2        60.1.2.1             N/A             N/A    5    0  Egress
  9   0             N/A        20.1.1.4        20.1.1.4    5    0  Ingress
  9   1        20.1.1.4        60.1.1.1        60.1.1.1    4    0  Transit
                               60.1.2.1        60.1.2.1
  9   2        60.1.1.1             N/A             N/A    5    0  Egress
  10  0             N/A        20.1.1.4        20.1.1.4    5    0  Ingress
  10  1        20.1.1.4        60.1.1.1        60.1.1.1    5    0  Transit
                               60.1.2.1        60.1.2.1
  10  2        60.1.2.1             N/A             N/A    6    0  Egress

1.41   track

1.41.1   Purpose

When used in RSVP router configuration mode, creates a tracking object on an access router.

When used in RSVP LSP configuration mode, enables the LSP to track the interfaces contained in the specified object.

1.41.2   Command Mode

RSVP router configuration

RSVP LSP configuration

1.41.3   Syntax Description

1.41.4   Default

None

1.41.5   Usage Guidelines

Use the track command in RSVP router configuration mode to create a tracking object on an access router. Use the track command in RSVP LSP configuration mode to enable an LSP to track the interfaces contained in a specific object.

Use the no form of this command to delete the tracking object from an access router.

1.41.6   Examples

The following example shows how to create a tracking object called san-jose-1. In this example, san-jose-1 contains the interfaces called red and blue:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#router rsvp
[local]Redback(config-rsvp)#track san-jose-1
[local]Redback(config-rsvp-track_obj)#interface red
[local]Redback(config-rsvp-track_obj)#interface blue

The following example shows how to enable the LSP called verde to track the interfaces in the object called san-jose-1:

[local]Redback#config
[local]Redback(config)#context local
[local]Redback(config-ctx)#router rsvp
[local]Redback(config-rsvp)#lsp verde
[local]Redback(config-rsvp-lsp)#track san-jose-1
[local]Redback(config-rsvp-lsp)#exit

1.42   track-igp-metric

1.42.1   Purpose

Enables Label Distribution Protocol (LDP) label-switched paths (LSPs) to inherit the Intermediate System-to-Intermediate System (IS-IS) routing metric for Border Gateway Protocol (BGP) to use when selecting a path.

1.42.2   Command Mode

LDP router configuration

1.42.3   Syntax Description

This command has no keywords or arguments.

1.42.4   Default

By default, inheriting the IS-IS routing metric is disabled.

1.42.5   Usage Guidelines

Use the track-igp-metric command to enable LDP LSPs to inherit the IS-IS routing metric for BGP to use when selecting a path.

Use the no form of this command to disable LDP LSPs from inheriting the IS-IS metric.

1.42.6   Examples

The following example enables LDP LSPs to inherit the IS-IS routing metric for BGP to use when selecting a path:

[local]Redback(config-ctx)#router ldp
[local]Redback(config-ldp)#track-igp-metric

1.43   track interface

1.43.1   Purpose

Enables tracking of an interface by the specified VRRP instance.

1.43.2   Command Mode

Interface configuration

1.43.3   Syntax Description

1.43.4   Default

Interface tracking is disabled.

1.43.5   Usage Guidelines

Use the track interface command to enable the tracking of an interface by the specified VRRP instance.

Note:  

Only one interface can be configured for each command line. To track multiple interfaces, you must enter a separate command line for each interface you want to track.

Use the no form of this command to disable interface tracking by a VRRP instance.

1.43.6   Examples

The following example shows how use the local VRRP instance to track the eth0 interface. In this case, if eth0 goes down, the local VRRP instance priority is decremented by 100:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#interface eth0
[local]Redback(config-if)#ip address 10.1.1.1/24
[local]Redback(config-if)#vrrp 1 backup
[local]Redback(config-vrrp)#virtual address 10.1.1.2
[local]Redback(config-vrrp)#priority 200
[local]Redback(config-vrrp)#track interface uplink local decrement 100

1.44   track network

1.44.1   Purpose

Enables the backup VRRP router to track a specified network through the IP network prefix of that network.

1.44.2   Command Mode

VRRP configuration mode.

1.44.3   Syntax Description

1.44.4   Default

The default decrement priority value is 10.

1.44.5   Usage Guidelines

Use the track network command to enable the backup VRRP router to track a specified network through the IP network prefix of that network.

Note:  

When a network regains reachability after a switchover, the VRRP router reverts to its original priority.

A change in router priority can cause a master VRRP router to become a backup VRRP router, and a backup router to become a master router.

Note:  

A single backup VRRP router can track up to 10 IP network prefixes.

Use the no or default form of this command to disable IP network prefix tracking for all IP prefixes or for a specific IP address.

1.44.6   Examples

The following example configures the backup VRRP router 1 to track the network with the IP network prefix 192.168.100.1/24. In this example, the priority of VRRP router1 is decremented by 100 if the network with the IP network prefix 192.168.100.1/24 cannot be reached:

[local]SE1(config)#context local 
[local]SE1(config-ctx)#interface vlan1 
[local]SE1(config-if)#vrrp 1 backup
[local]SE1(config-vrrp)#track network 192.168.100.1/24 decrement 100

1.45   track spanning-tree

1.45.1   Purpose

Configures the current bridge to track the Rapid Spanning Tree Protocol (RSTP) master bridge specified in this command.

1.45.2   Command Mode

Bridge configuration

1.45.3   Syntax Description

1.45.4   Default

RSTP tracking is disabled.

1.45.5   Usage Guidelines

Use the track spanning-tree command to configure the current bridge to track the RSTP master bridge specified.

Bridges that are not running RSTP and are enabled for tracking by the track spanning-tree command are called client bridges. The state of all client bridge circuits on the same port as a master bridge circuit follow the state of the RSTP master. When the state of the circuit controlled by the master bridge changes to blocking, forwarding, or flushing, all circuits on the same port of the tracking client bridges change to the same state.

See the RSTP tracking requirements and restrictions listed in Configuring Bridging.

Use the no form of this command to disable tracking of the RSTP master bridge.

1.45.6   Examples

The following example shows the configuration of blue which is an RSTP master bridge and green which is one of its non-RSTP client bridges:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#bridge blue
[local]Redback(config-bridge)#spanning-tree
[local]Redback(config-bridge-stp)#master
[local]Redback(config-bridge-stp)#end
!
[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#bridge green
[local]Redback(config-bridge)#track spanning-tree blue local
[local]Redback(config-bridge)#end

1.46   track (vrrp)

1.46.1   Purpose

Changes a static dot1q PVC into a track PVC, or disables following a VRRP session on the current circuit.

1.46.2   Command Mode

dot1q PVC configuration

1.46.3   Syntax Description

1.46.4   Default

The current circuit is not a track PVC.

1.46.5   Usage Guidelines

Use the track vrrp command to change a static dot1q PVC into a track PVC, or to disable following a VRRP session on the current circuit.

A track PVC is a PVC that tracks the state of a VRRP interface. The track PVC carries traffic when it is active and no traffic when it is in backup state. Only one track option can be defined on a PVC.

When a static 802.1Q PVC is configured to track the state of a VRRP interface, all of its child circuits inherit this functionality and also track the state of that same VRRP interface.

Use the no track vrrp form of this command to change the current PVC into a static PVC. Use the no track none form of this command to enable following a VRRP session on the current circuit.

1.46.6   Examples

The following example shows how use the track vrrp command:

[local]Redback#configure
[local]Redback#port ethernet 5/1
[local]Redback(config)#dot1q pvc 108 encapsulation pppoe
[local]Redback(config-dot1q-pvc)#track vrrp 7 one pctx
[local]Redback(config-dot1q-pvc)#bind authentication chap context 
pctx maximum 2

1.47   traffic-engineering

1.47.1   Purpose

Enables Multiprotocol Label Switching (MPLS) traffic engineering within Intermediate System-to-Intermediate System (IS-IS) routing.

1.47.2   Command Mode

IS-IS router configuration

1.47.3   Syntax Description

1.47.4   Default

MPLS traffic engineering is disabled.

1.47.5   Usage Guidelines

Use the traffic-engineering command to enable MPLS traffic engineering within IS-IS routing. Enabling traffic engineering allows IS-IS link-state protocol data units (LSPs) to carry traffic engineering information on IS-IS interfaces. Traffic engineering information includes link IP addresses, link bandwidth and link administrative colors.

Traffic engineering can be enabled on either IS-IS level 1, level 2, or both level 1 and level 2 routing.

Note:  

• Resource Reservation Protocol (RSVP) must be configured on the interface for IS-IS traffic engineering information to be included in its LSP for the link.
• An IS-IS metric style of wide or transition must be used for traffic engineering to take effect.
• The global router-id command in context configuration mode must be configured for the IS-IS LSP to carry the specified IP address of the router ID interface.

Use the show isis database extensive command to see the traffic engineering information for the IS-IS link in the LSPs, and the show isis interface detail command to see if the interface has traffic engineering information for the routing level.

Use the no form of this command to disable MPLS traffic engineering within IS-IS routing.

1.47.6   Examples

The following example displays that IS-IS traffic engineering is enabled for IS-IS level-2 routing:

[local]Redback(config-ctx)#router isis ip-backbone
[local]Redback(config-isis)#traffic-engineering level-2

1.48   traffic-index accounting

1.48.1   Purpose

Enables Border Gateway Protocol (BGP) attribute-based accounting on an interface.

1.48.2   Command Mode

Interface configuration

1.48.3   Syntax Description

This command has no keywords or arguments.

1.48.4   Default

BGP attribute-based accounting is disabled.

1.48.5   Usage Guidelines

Use the traffic-index accounting command to enable BGP attribute-based accounting on an interface.

Per index counters for interfaces with BGP attribute-based accounting enabled are maintained for BGP routes assigned a traffic index. The byte and packet counters for a traffic index are incremented based on the route traversed by IP traffic received on the ingress interface. For more information, see the set traffic-index and table-map commands.

Use the no or default form of this command to disable BGP attribute-based accounting on an interface.

1.48.6   Examples

The following example enables BGP policy accounting on the interface, value-added:

[local]Redback(config)#interface value-added
[local]Redback(config-if)#ip address 10.200.1.1/30
[local]Redback(config-if)#traffic-index accounting

1.49   transfer-interval

1.49.1   Purpose

Specifies the interval after which bulkstats data for this policy is uploaded to a remote file server.

1.49.2   Command Mode

Bulkstats configuration

1.49.3   Syntax Description

1.49.4   Default

The bulkstats transfer interval is 60 minutes.

1.49.5   Usage Guidelines

Use the transfer-interval command to specify the interval after which bulkstats data for this policy is uploaded to a remote file server. Use the bulkstats force transfer command in exec mode to force an immediate transfer for this policy. For information on the bulkstats force transfer command, see the Command List.

Use the default form of this command to return the transfer interval to 60 minutes.

1.49.6   Examples

The following example specifies that bulkstats data is transferred to a remote file server every 180 minutes:

[local]Redback(config)#context local
[local]Redback(config-ctx)#bulkstats policy bulk
[local]Redback(config-bulkstats)#transfer-interval 180

1.50   transmit-delay

1.50.1   Purpose

Sets a delay value, increasing the age of link-state advertisements (LSAs) sent over the specified interface, sham link, or virtual link.

1.50.2   Command Mode

• OSPF interface configuration
• OSPF sham link configuration
• OSPF virtual link configuration
• OSPF3 interface configuration

1.50.3   Syntax Description

1.50.4   Default

No delay value is set. When set, the delay value is one second.

1.50.5   Usage Guidelines

Use the transmit-delay command to set a delay value, increasing the age of LSAs sent over the specified interface, sham link, or virtual link.

Before a link-state update packet is advertised, the age of the LSAs in the packet must be increased by a value proportionate to the speed of the interface, sham link, or virtual link; for example, on a very slow interface, sham link, or virtual link, you might set the transmit delay to two seconds to ensure that you do not receive an LSA that is less recent than the copy in the router’s link-state database.

Use the no or default form of this command return the delay value to its default setting.

1.50.6   Examples

The following example sets an Open Shortest Path First (OSPF) interface transmit delay to 3 seconds:

[local]Redback(config-ospf-if)#transmit-delay 3

1.51   transmit-hold count

1.51.1   Purpose

Sets the transmit hold count.

1.51.2   Command Mode

Spanning-tree configuration

1.51.3   Syntax Description

1.51.4   Default

6 seconds

1.51.5   Usage Guidelines

Use the transmit-hold count command to set the transmit hold count; that is, the minimum amount of time between the transmission of BPDUs. This command applies when the current bridge is the root bridge.

1.51.6   Examples

An example of setting the transmit hold count time follows:

[local]Redback(config-bridge-stp)#transmit-hold count 4

1.52   transport address

1.52.1   Purpose

Configures the transport address advertised in Label Distribution Protocol (LDP) Hello messages.

1.52.2   Command Mode

LDP router configuration

1.52.3   Syntax Description

1.52.4   Default

The label-switched router (LSR) router ID is used as the transport address.

1.52.5   Usage Guidelines

Use the transport address command to configure the transport address advertised in LDP Hello messages. Transport addresses are advertised in LDP Hello messages and are exchanged among LDP neighbors. LDP uses the local transport address as the source, and the received transport address as the destination when trying to establish a Transmission Control Protocol (TCP) connection to a neighbor. Therefore, transport addresses must be reachable. LDP also uses transport addresses to determine which of the two LSRs should perform active open.

If a transport address is not explicitly configured, the LSR router ID is used as the transport address. In this case, the router ID must be reachable; however, if a transport address is explicitly configured, then the specified value is used. In this case, the router ID is not required to be reachable.

1.52.6   Examples

The following example configures a transport address of 20.1.1.1:

[local]Redback(config-ctx)#router ldp
[local]Redback(config-ldp)#transport address 20.1.1.1

1.53   transport protocol

1.53.1   Purpose

Configures the transport protocol used to export the flow records.

1.53.2   Command Mode

Flow collector configuration

1.53.3   Syntax Description

1.53.4   Default

The default transport protocol for the flow records is UDP.

1.53.5   Usage Guidelines

Use the transport protocol udp command to configure the transport protocol used to export the flow records.

Note:  

In this release, UDP is the only supported transport protocol for the flow records.

Use the no form of this command to use the default transport protocol for the flow records (UDP).

1.53.6   Examples

The following example shows how to configure the SmartEdge router to use UDP for transporting flow records to an external collector called c1:

[local]Redback)#configure
[local]Redback)(config)#context corp2
[local]Redback(config-ctx)#flow collector c1
[local]Redback(config-flow-collector)#transport protocol udp

1.54   transport protocol (NAT)

1.54.1   Command Mode

NAT logging profile configuration

1.54.2   Syntax Description

1.54.3   Default

The default transport protocol for the flow records is UDP.

1.54.4   Usage Guidelines

Use the transport protocol udp command to configure the transport protocol used to export the flow records.

Note:  

UDP is the only supported transport protocol for the flow records.

Use the no form of this command to use the default transport protocol for the flow records (UDP).

For information about how to configure a NAT logging profile, see thenat logging-profile command and Configure an Enhanced NAT Policy with Logging and Paired Mode.

1.54.5   Examples

The following example show how to configure the SmartEdge router to use UDP for transporting flow records for a NAT logging profile.

[local]Ericsson#configure
Enter configuration commands, one per line, 'end' to exit
[local]Ericsson(config)#context nat-context
[[local]Ericsson(config-ctx)#nat logging-profile nat-log-profile
[local]Ericsson(config-nat-profile)#transport protocol udp

1.55   traps (SNMP server configuration)

traps {ifmib [ encaps | ip] | ds1mib | ds3mib | l2tpmib | l2vpnmib | mplsl3vpn interval seconds| nemib [ exclusive | non-exclusive] | ssemib | vrrpmib}

no traps {ifmib [ encaps | ip] | ds1mib | ds3mib | l2tpmib | l2vpnmib | mplsl3vpn | nemib [ exclusive | non-exclusive] | ssemib | vrrpmib}

1.55.1   Purpose

Enables Simple Network Management Protocol (SNMP) notifications for events described in the selected Management Information Bases (MIBs).

1.55.2   Command Mode

SNMP server configuration

1.55.3   Syntax Description

1.55.4   Default

Notification of all conditions is disabled globally for all encapsulation layers, IP layers, and L2TP tunnels.

1.55.5   Usage Guidelines

Use the traps command to enable SNMP notifications for events described in the selected MIBs.

You can enter this command multiple times to enable notifications for encapsulation layers, IP layers, or L2TP tunnels.

Note:  

By default, only IF-MIB physical ports generate linkUp and linkDown notifications.

When entered with the nemib non-exclusive and nemib exclusive constructs, the notifications in the RBN-NOTIFY-ENHANCE-MIB provide more information than the corresponding notifications in standard MIBs, such as IF-MIB, DS1-MIB, DS3-MIB, ENTITY-MIB, and some earlier Enterprise MIBs, such as RBN-CARDMON-MIB.

The nemib exclusive construct disables the following standard traps:

• linkDown and linkUp
• dsx1LineStatusChange and dsx3LineStatusChange
• entConfigChange and rbnCardAlarm

If you specify neither the nemib non-exclusive nor nemib exclusive construct, the notifications in the RBN-NOTIFY-ENHANCE-MIB are disabled by default.

Use the no form of this command to disable notifications of up and down conditions for encapsulation layers, IP layers, or L2TP tunnels and to use the unenhanced versions of the traps.

1.55.6   Examples

The following example enables notifications for Cisco HDLC, PPP, and Frame Relay encapsulation layers, IP layers, and L2TP tunnels:

[local]Redback(config)#snmp server enhance ifmib 
[local]Redback(config-snmp-server)#traps ifmib encaps 
[local]Redback(config-snmp-server)#traps ifmib ip 
[local]Redback(config-snmp-server)#traps l2tpmib 
[local]Redback(config-snmp-server)#traps nemib exclusive 

1.56   traps (DS-0 group configuration)

1.56.1   Purpose

Enables linkUp and linkDown notifications for Cisco HDLC, Point-to-Point Protocol (PPP), and Frame Relay encapsulation layers (IF-MIB encapsulation layers) on the DS-0 channel group.

1.56.2   Command Mode

DS-0 group configuration

1.56.3   Syntax Description

1.56.4   Default

If this command is not entered, notification of up and down conditions is enabled or disabled by the traps command in (SNMP server configuration mode).

1.56.5   Usage Guidelines

Use the traps command to enable linkUp and linkDown notifications locally for Cisco HDLC, PPP, and Frame Relay encapsulation layers on the DS-0 channel group. This command overrides, for this DS-0 channel group, any global specification for encapsulation layers you have specified with the traps command (in SNMP server configuration mode).

Table 3 lists the combinations of global and local settings and the resulting notifications for encapsulation layers.

Use the no or default form of this command to disable encapsulation layer notifications locally; as a result, encapsulation layer notifications are enabled or disabled globally as specified with the traps command in (SNMP server configuration mode).

1.56.6   Examples

The following example shows how to enable encapsulation notifications globally and disable them locally for the DS-0 channel group on port 1 of a channelized E1 traffic card:

[local]Redback(config)#snmp server enhance ifmib 
[local]Redback(config-snmp-server)#traps ifmib encaps 
[local]Redback(config-snmp-server)#exit
[local]Redback(config)#port ds0s 5/1:7
[local]Redback(config-ds0-group)#traps ifmib disabled

1.57   trunk

1.57.1   Purpose

Specifies that any circuit to which this profile is assigned is a trunk circuit.

1.57.2   Command Mode

Bridge profile configuration

1.57.3   Syntax Description

This command has no keywords or arguments.

1.57.4   Default

Any circuit to which this profile is assigned is a tributary circuit.

1.57.5   Usage Guidelines

Use the trunk command to specify that any circuit to which this profile is assigned is a trunk circuit.

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

Tributary circuits face subscribers. Trunk circuits face service providers. In other words, tributary circuits are access facing, while trunk circuits are network facing.

1.57.6   Examples

The following example shows how to specify that the profile be a trunk profile:

[local]Redback(config)#bridge profile prof-isp1
[local]Redback(config-bridge-profile)#trunk

1.58   ttl

1.58.1   Purpose

Configures the time-to-live (TTL) value for a dynamically verified static routing (DVSR) profile.

1.58.2   Command Mode

DVSR profile configuration

1.58.3   Syntax Description

1.58.4   Default

The default TTL value is 5.

1.58.5   Usage Guidelines

Use the ttl command to configure the TTL value for a DVSR profile. The TTL value controls the maximum number of hops the verification packet can traverse; for example, if there are multiple paths to reach the verify host address, you must restrict the verification packet to the shorter paths to be considered a successful verification.

Use the no form of this command to delete the TTL value from a DVSR profile.

Use the default form of this command to configure a DVSR profile to use the default TTL value of 5.

1.58.6   Examples

The following example defines a DVSR profile using a TTL value of 2:

[local]Redback(config-ctx)#dvsr-profile abc-webfarm
[local]Redback(config-dvsr)#ttl 2

1.59   tunnel

1.59.1   Purpose

Creates or selects a tunnel and accesses tunnel configuration mode.

1.59.2   Command Mode

Global configuration

1.59.3   Syntax Description

1.59.4   Default

No tunnels are created.

1.59.5   Usage Guidelines

Use the tunnel command to create or select a tunnel and enter tunnel configuration mode.

If the remote end point of a GRE tunnel is a SmartEdge router, you must also create the GRE tunnel configuration on the remote SmartEdge router.

Note:  

If the traffic receiving end of a GRE tunnel is a SmartEdge router, you must configure the router with a GRE tunnel whose local endpoint is the traffic receiving endpoint of the tunnel. This configuration is required in order to respond to GRE keepalives sent by the traffic sending end of the tunnel.

You can create multiple tunnels, but usually only one tunnel between sites.

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

1.59.6   Examples

The following example shows how to create a GRE tunnel, HartfordTnl:

[local]Redback(config)#tunnel gre HartfordTnl
[local]Redback(config-tunnel)#

1.60   tunnel-auth key

1.60.1   Purpose

Specifies a Layer 2 Tunneling Protocol (L2TP) key to be used by a peer to encrypt and decrypt information sent on the control channel.

1.60.2   Command Mode

L2TP peer configuration

1.60.3   Syntax Description

1.60.4   Default

No password is created.

1.60.5   Usage Guidelines

Use the tunnel-auth key command to specify the key to be used by a peer to encrypt and decrypt information sent on the control channel.

The key argument is an alphanumeric string used for the peer password.

Use the no or default form of this command to delete any previously established primary password.

1.60.6   Examples

The following example establishes 6dkq7pv as the password for peer peer1:

[local]Redback(config-ctx)#l2tp-peer name peer1 media udp remote 
dns yellow
[local]Redback(config-l2tp)#tunnel-auth key 6dkq7pv

1.61   tunnel domain

1.61.1   Purpose

Enables the dynamic assignment of a subscriber’s Point-to-Point Protocol (PPP) session to a Layer 2 Tunneling Protocol (L2TP) peer that has the same domain alias as the subscriber’s domain alias.

1.61.2   Command Mode

Subscriber configuration

1.61.3   Syntax Description

This command has no keywords or arguments.

1.61.4   Default

Dynamic assignment is disabled; subscriber PPP sessions are terminated and routed rather than tunneled.

1.61.5   Usage Guidelines

Use the tunnel domain command to enable the dynamic assignment of a subscriber’s PPP session to an L2TP peer that has the same domain alias as the subscriber’s domain alias (the @ctx-name portion of the structured subscriber name). This domain alias is also a domain alias for the context in which both are configured. You create domain aliases for a context using the domain command in context configuration mode.

To allow the subscriber PPP sessions to be tunneled, you must have configured the PPP for the subscriber circuit.

This command and the tunnel name command in subscriber configuration mode are mutually exclusive.

You can configure multiple subscribers with dynamic peer assignment if you enter this command for the default or named subscriber profile instead of individual subscriber records.

PPP sessions are tunneled in the upstream direction to the remote peer.

Use the no form of this command to disable dynamic assignment for a subscriber.

1.61.6   Examples

The following example shows how to configure the default subscriber profile to cause PPP sessions to be mapped to the tunnel that has the same name as the user’s domain name:

[local]Redback(config)#context local
[local]Redback(config-ctx)#subscriber default
[local]Redback(config-sub)#tunnel domain

1.62   tunnel ldp-path

1.62.1   Purpose

Enables L2VPN-to-LDP LSP mapping in an L2VPN profile.

1.62.2   Command Mode

• L2VPN profile peer configuration
• L2VPN profile backup peer configuration

1.62.3   Syntax Description

This command has no keywords or arguments.

1.62.4   Default

L2VPN-to-LDP LSP mapping is not configured in an L2VPN profile.

1.62.5   Usage Guidelines

Use the tunnel ldp-path command to configure L2VPN-to-LDP LSP mapping in an L2VPN profile. All L2VPN circuits attached to the specified profile are mapped to an LDP LSP.

Use the no form of this command to disable L2VPN-to-LDP LSP mapping in an L2VPN profile.

1.62.6   Examples

The following example shows how to enable L2VPN-to-LDP LSP mapping in an L2VPN profile:

[local]Redback(config)#l2vpn profile pr1
[local]Redback(config-l2vpn-xc-profile)#peer 111.111.111.111
[local]Redback(config-l2vpn-xc-profile-peer)#tunnel ldp-path

The following example shows how to configure a backup tunnel in an L2VPN profile. Any backup L2VPN cross-connects that have the profile called pro attached are mapped to an LDP LSP:

[local]Redback(config)#l2vpn profile prof2

[local]Redback(config-l2vpn-xc-profile)#backup peer 100.100.100.2

[local]Redback(config-l2vpn-xc-profile-peer)#tunnel ldp-path

1.63   tunnel lsp

1.63.1   Purpose

In a Layer 2 VPN (L2VPN) profile, specifies a particular Resource Reservation Protocol (RSVP) tunnel for carrying traffic exiting an L2VPN cross-connect (XC).

1.63.2   Command Mode

• L2VPN profile peer configuration
• L2VPN profile backup peer configuration

1.63.3   Syntax Description

1.63.4   Default

L2VPN-to-RSVP tunnel mapping is not configured in an L2VPN profile.

1.63.5   Usage Guidelines

Use the tunnel lsp command to specify a particular RSVP tunnel for carrying traffic exiting an L2VPN XC. Any L2VPN circuits that are associated with this L2VPN profile inherit this configuration.

Use the no form of this command to remove L2VPN-to-RSVP tunnel mapping configuration from an L2VPN profile.

1.63.6   Examples

The following example shows how to specify an RSVP tunnel called lsp1A for carrying traffic exiting an L2VPN XC. All L2VPN circuits that have the L2VPN profile called pr1 attached inherit this configuration:

[local]Redback(config)#l2vpn profile pr1
Redback(config-l2vpn-xc-profile)peer 111.111.111.111
Redback(config-l2vpn-xc-profile-peer) tunnel lsp lsp1A

The following example shows how to configure a backup tunnel in an L2VPN profile. Any backup L2VPN XCs that have the profile called prof1 attached are mapped to the RSVP tunnel called lsp-to-target2:

[local]Redback(config)#l2vpn profile prof1
[local]Redback(config-l2vpn-xc-profile)#backup peer 100.100.100.2
[local]Redback(config-l2vpn-xc-profile-peer)#tunnel lsp lsp-to-target2

1.64   tunnel name

1.64.1   Purpose

Statically assigns the subscriber’s Point-to-Point Protocol (PPP) session to a specified Layer 2 Tunneling Protocol (L2TP) peer or group of L2TP peers.

1.64.2   Command Mode

Subscriber configuration

1.64.3   Syntax Description

1.64.4   Default

A PPP session is terminated rather than tunneled.

1.64.5   Usage Guidelines

Use the tunnel name command to statically assign the subscriber’s PPP session to a specific L2TP peer or group of peers. You can use a peer name or the domain alias for the peer name, a group name, or a domain alias for the group name as the tunl-name argument, which is included in the subscriber record.

Note:  

This command and the tunnel domain command in subscriber configuration mode are mutually exclusive.

Use the no form of this command to remove the peer or peer group name or alias from the subscriber record.

1.64.6   Examples

The following example shows how to ensure that the subscriber uses the tunnel freds-corp.com:

[local]Redback(config)#context local
[local]Redback(config-ctx)#subscriber name fred
[local]Redback(config-sub)#tunnel name freds-corp.com

1.65   tunnel-type

1.65.1   Purpose

Enables use of Generic Routing Encapsulation (GRE) tunnel types by mobile nodes (MN).

1.65.2   Command Mode

HA configuration

1.65.3   Syntax Description

1.65.4   Default

IP-in-IP tunnels are enabled implicitly; no optional tunnel types are enabled.

1.65.5   Usage Guidelines

Use the tunnel-type command to use of GRE tunnel types by MNs.

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

1.65.6   Examples

The following example enables the GRE tunnel type:

[local]Redback(config)#context ha
[local]Redback(config-ctx)#router mobile-ip
[local]Redback(config-mip)#home-agent
[local]Redback(config-mip-ha)#tunnel-type gre

1.66   tunnel-window

1.66.1   Purpose

Specifies the size of the control message window that is advertised to a Layer 2 Tunneling Protocol (L2TP) peer in Start-Control-Connection-Request (SCCRQ) or Start-Control-Connection-Reply (SCCRP) messages.

1.66.2   Command Mode

L2TP peer configuration

1.66.3   Syntax Description

1.66.4   Default

Up to eight control messages can be sent by an L2TP peer before acknowledgment from the SmartEdge router.

1.66.5   Usage Guidelines

Use the tunnel-window command to specify the size of control message window that is advertised to an L2TP peer in SCCRQ or SCCRP messages. The size of the window controls how many messages can be sent by a peer before it must wait for acknowledgement from the SmartEdge router.

You might need to change the number of messages, depending on the number of control messages a peer can generate at one time. For example, if a peer brings up many sessions all at once, you might need to increase the number of messages. However, changing the size of the control message window does not take effect until a new tunnel to the peer is established.

We recommend that you configure the control message window size to match the size configured on the L2TP peer, unless instructed to do otherwise by technical support.

Use the no or default form of this command to set the size of the control message window to the default.

1.66.6   Examples

The following example shows how to configure the peer to be able to send up to 15 control messages before acknowledgment from the SmartEdge router:

[local]Redback(config-ctx)#l2tp-peer name peer1
[local]Redback(config-l2tp)#tunnel-window 15

1.67   turbo

1.67.1   Purpose

Enables fast IGMP message processing in the PPA.

1.67.2   Command Mode

IGMP snooping bridge configuration

1.67.3   Syntax Description

This command has no keywords or arguments.

1.67.4   Default

Fast IGMP message processing is disabled.

1.67.5   Usage Guidelines

Use the turbo command to enable fast IGMP message processing in the PPA.

Use the no form of this command to remove a configuration for IGMP message processing in the PPA.

1.67.6   Examples

The following example enables fast IGMP message processing in the PPA:

[local]Router(config)#context sj1
[local]Router(config-ctx)#bridge br-sj-1
[local]Router(config-bridge)#igmp snooping
[local]Router(config-igmp-snooping)#turbo

1.68   type (DSL)

1.68.1   Purpose

Specifies the digital subscriber line (DSL) data type for the overhead profile and accesses overhead type configuration mode.

1.68.2   Command Mode