COMMAND DESCRIPTION     16/190 82-CRA 119 1170/1-V1 Uen D

Commands: s through show a

Copyright

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

Disclaimer

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

Trademark List

Contents

1   Command Descriptions

Commands starting with “s” through commands starting with “show a” are included.

1.1   sa-filter

1.1.1   Purpose

Specifies an access control list (ACL) to filter source active (SA) messages coming in to, or going out of, the peer.

1.1.2   Command Mode

MSDP peer configuration

1.1.3   Syntax Description

1.1.4   Default

None

1.1.5   Usage Guidelines

Use the sa-filter command to specify an ACL to filter SA messages coming in to, or going out of, the peer.

Use the no form of this command to remove the SA filter.

1.1.6   Examples

The following example filters incoming SA messages from a peer using the ACL, peer-sa-filter-in-group:

[local]Redback(config-ctx)#ip access-list peer-sa-filter-in-group

[local]Redback(config-access-list)#seq 10 deny ip any 224.137.0.0 0.0.255.255

[local]Redback(config-access-list)#seq 20 deny ip any 224.134.1.0 0.0.0.255

[local]Redback(config-access-list)#seq 30 deny ip any host 224.131.1.1

[local]Redback(config-access-list)#seq 40 permit any any

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

[local]Redback(config-msdp)#peer 10.200.1.2 local-tcp-source lo1

[local]Redback(config-msdp-peer)#sa-filter in peer-sa-filter-in-group

The following example filters outgoing SA messages to a peer using the ACL, peer-sa-filter-out-source-group:

[local]Redback(config-ctx)#ip access-list peer-sa-filter-out-source-group

[local]Redback(config-access-list)#seq 10 deny ip 44.1.1.0 0.0.0.255 host 224.133.1.2

[local]Redback(config-access-list)#seq 20 deny ip 44.1.1.0 0.0.0.255 224.136.2.0 0.0.0.255

[local]Redback(config-access-list)#seq 30 permit ip any any

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

[local]Redback(config-msdp)#peer 10.200.1.2 local-tcp-source lo1

[local]Redback(config-msdp-peer)#sa-filter out peer-sa-filter-out-source-group

1.2   sample-interval

1.2.1   Purpose

Specifies the interval between the collection of bulkstats samples.

1.2.2   Command Mode

bulkstats configuration

1.2.3   Syntax Description

1.2.4   Default

The sampling interval is 15 minutes.

1.2.5   Usage Guidelines

Use the sample-interval command to specify the interval between the collection of bulkstats samples. Setting the sampling interval so that sampling occurs too often can decrease the performance of the SmartEdge® router.

Use the default form of this command to return the sampling interval to 15 minutes.

1.2.6   Examples

The following example sets the sampling interval to 30 minutes:

[local]Redback(config)#context local

[local]Redback(config-ctx)#bulkstats policy bulk

[local]Redback(config-bulkstats)#sample-interval 30

1.3   sampling

1.3.1   Purpose

Use the sampling command to enable random sampling for flows using a specific IP profile.

1.3.2   Command Mode

flow IP profile configuration

1.3.3   Syntax Description

This command has no keywords or arguments.

1.3.4   Default

Sampling is disabled.

1.3.5   Usage Guidelines

Use the sampling command to enable random sampling for flows using a specific IP profile.

Use the no version of this command to disable random sampling for flows using a specific IP profile.

1.3.6   Examples

The following example shows how to use the sampling command to enable random sampling for flows using the IP profile p1:

[local]Redback# configure
[local]Redback(config)# flow ip profile p1
[local]Redback(config-flow-ip-profile)#sampling

1.4   save configuration

1.4.1   Purpose

Saves the running configuration to a file on a remote server or the local file system.

1.4.2   Command Mode

exec (10)

1.4.3   Syntax Description

1.4.4   Default

Commands are saved to the default configuration file.

1.4.5   Usage Guidelines

Use the save configuration command to save the running configuration to a file on a remote server or the local file system.

Only those commands that modify the default configuration of the SmartEdge router are saved.

When saving the configuration to the local file system, the URL takes the following form:

[/device][/directory]/filename.ext

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

The value for the filename argument can be up to 256 characters in length. If you do not specify the filename.ext argument, the configuration is saved to the redback.cfg file.

To ensure that the binary database file (/flash/redback.bin) is created correctly when saving to the redback.cfg file, enter this command without a filename, or specify redback.cfg as the filename without a device or directory. For information about these files, see Managing Configuration Files.

When saving the configuration to a remote server, you can use the File Transfer Protocol (FTP), Remote Copy Protocol (RCP), Secured Copy Protocol (SCP), Secured FTP (SFTP), or Trivial FTP (TFTP).

Table 1 describes the syntax for the url argument when saving the file to a remote server.

You can specify the hostname argument only if Domain Name System (DNS) is enabled with the ip domain-lookup, ip domain-name, and ip name-servers commands (in context configuration mode); see the Command List.

Note:  

Use double slashes (//) if the pathname to the directory on the remote server is an absolute pathname; use a single slash (/) if it is a relative pathname (under the hierarchy of username account home directory).

If you attempt to overwrite an existing file on the local file system, the system prompts you for confirmation. Use the -noconfirm optional keyword to replace an existing file without providing confirmation to the system. In either case, the system saves a backup of the existing file with the .bak file extension. Only a single copy of the file is saved as a backup.

1.4.6   Examples

The following example saves the current active system configuration to a file, current.cfg, on the local file system. The user is prompted to overwrite an existing file:

[local]Redback#save configuration /flash/current.cfg



Save to file: current.cfg

Target file exists, overwrite? y

The following example shows that the existing current.cfg file has been saved as current.cfg.bak:

[local]Redback#directory /flash

Contents of /flash

total 2590

-rw-r--r--  1 root  10000     4564 Jan 23 2006  current.cfg

-rw-r--r--  1 root  10000     3654 Jan 23 2006  current.cfg.bak

-rw-r--r--  1 root  10000     1578 Jan 23 2006  redback.cfg

1.5   save log

1.5.1   Purpose

Saves one of the internal event log buffers to the flash file system.

1.5.2   Command Mode

exec (10)

1.5.3   Syntax Description

1.5.4   Default

None

1.5.5   Usage Guidelines

Use the save log command to save one of the internal event log buffers to the flash file system for later examination.

To examine the debugging messages, use the logging debug command (in global configuration mode); to save the messages prior to examining them, use the save log command. You can use the logging filter command (in context configuration mode) to specify different levels of logging filters.

For more information about the logging debug and logging filter commands, see the Command List.

1.5.6   Examples

The following example saves a copy of the log to the file, log.sav, in the /flash directory:

[local]Redback>save log log.sav

1.6   save seos-core

1.6.1   Purpose

Saves a previously written core dump of the operating system to the mass-storage device in the /md partition.

1.6.2   Command Mode

• exec (10)

1.6.3   Syntax Description

This command has no keywords or arguments.

1.6.4   Default

None

1.6.5   Usage Guidelines

Use the save seos-core command to save a core dump, which the operating system kernel has previously written to the swap partition on the mass-storage device, to the /md partition on the same device; the SmartEdge router must have a mass-storage device installed to use this command.

Either controller card can detect a problem and cause its kernel to dump an image of the running operating system on its mass-storage device. When you enter this command, you must be using a command-line interface (CLI) running on that same controller card to allow the command to access the core dump in the swap partition. For example, if the controller card that wrote the core dump has become the standby controller after reloading the operating system, you must connect to the local console for the standby controller card; if it was the active controller card, you can access the CLI from either the local console or the management port. Logging messages identify the controller card that wrote the core dump to the swap partition.

This command saves the core dump in two crash files. The filenames for these files, netbsd.0.core.gz and netbsd.0.gz, are fixed; however, you can rename the files after the save operation is complete. If you rename the files, we recommend that you add only the date to the filenames to ensure that “core” remains in the filename for the netbsd.0.core.gz file.

Note:  

The files created by this command are useful only for the support organization when troubleshooting the problem that caused the core dump.

1.6.6   Examples

The following example saves a core dump of the operating system to two crash files in the /md partition on the mass-storage device of the active controller card and renames them to include the date of the core dump:

[local]Redback#save seos-core 

dumplo = 89128960 (174080 * 512)

savecore:  number read 512 value of magic on disk is 76910538

savecore: newdumpmag: 4958fca

savecore: dumpsize is 91003972

savecore: /md/bounds: No such file or directory

savecore: writing compressed core to /md/netbsd.0.core.gz

savecore: total output bytes(uncompressed):442499072

savecore: writing compressed kernel to /md/netbsd.0.gz

[local]Redback#rename /md/netbsd.0.core.gz /md/netbsd031002.0.core.gz

[local]Redback#rename /md/netbsd.0.gz /md/netbsd031002.0.gz

1.7   schema

1.7.1   Purpose

Applies a system-level bulkstats schema profile to gather system-wide statistics using this policy.

1.7.2   Command Mode

bulkstats configuration

1.7.3   Syntax Description

1.7.4   Default

None

1.7.5   Usage Guidelines

Use the schema command to apply a system-level (global) bulkstats schema profile to gather system-wide statistics using this policy. You can apply multiple schema profiles using this command. Each schema can gather a different type and format of data. Each application of a schema profile is used to create a text record that is appended to the bulkstats collection file for this policy after every sample period.

Use the no form of this command to remove the specified schema profile.

1.7.6   Examples

The following example applies a previously configured schema profile sample for the bulk policy:

[local]Redback(config)#context local

[local]Redback(config-ctx)#bulkstats policy bulk

[local]Redback(config-bulkstats)#schema sample 

1.8   schema-dump

1.8.1   Purpose

Enables writing the definitions of the configured bulkstats schema profiles to the beginning of the bulkstats data collection file.

1.8.2   Command Mode

bulkstats configuration

1.8.3   Syntax Description

This command has no keywords or arguments.

1.8.4   Default

No schema profile definition is saved in any bulkstats data collection file for any policy.

1.8.5   Usage Guidelines

Use the schema-dump command to enable writing the definitions of the configured bulkstats schema profiles to the beginning of the bulkstats data collection file. When enabled, the definition of each configured schema profile is printed at the beginning of the bulkstats collection file.

Use the no form of this command to disable writing the definitions of schema profiles to the bulkstats data collection file.

1.8.6   Examples

The following example writes the definitions of the configured bulkstats schema profiles to the bulkstats data file:

[local]Redback(config)#context local

[local]Redback(config-ctx)#bulkstats policy bulk

[local]Redback(config-bulkstats)#schema-dump

1.9   scramble

1.9.1   Purpose

Enables X^43+1 synchronous payload envelope (SPE) scrambling on a Packet over SONET/SDH (POS) port, as specified in RFC 2615, PPP over SONET/SDH.

1.9.2   Command Mode

• port configuration

1.9.3   Syntax Description

This command has no keywords or arguments.

1.9.4   Default

SPE scrambling is enabled on the port.

1.9.5   Usage Guidelines

Use the scramble command to enable X^43 +1 scrambling on a POS port, as specified in RFC 2615, PPP over SONET/SDH.

Note:  

Enabling or disabling scrambling on a port also changes the Path Label Signal (C2) byte value to the default specified in RFC 2615; see the c2byte command (in port configuration mode).

Note:  

This command does not apply to Asynchronous Transfer Mode (ATM), Ethernet, or channelized OC-12 ports.

Note:  

The SmartEdge 100 router does not support POS ports.

Use the no form of this command to disable SPE payload scrambling.

Use the default form of this command to enable SPE payload scrambling.

1.9.6   Examples

The following example shows how to disable SPE scrambling for port 1 on the POS traffic card in slot 11. It also results in the C2 value being set to the value of 0xCF:

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

[local]Redback(config-port)#no scramble

1.10   send

1.10.1   Purpose

Configures the setting in the IGMP snooping profile that controls the ability of the associated circuits to send multicast data.

1.10.2   Command Mode

• IGMP snooping profile configuration

1.10.3   Syntax Description

1.10.4   Default

The sending of multicast data is permitted on all circuits.

1.10.5   Usage Guidelines

Use the send command to configure the setting in the IGMP snooping profile that controls the ability of the associated circuits to send multicast data.

Use the no form of this command to return the IGMP snooping profile to the default setting in which the sending of multicast data is permitted on all circuits.

1.10.6   Examples

The following example shows how to deny the sending of multicast data by all circuits attached to an IGMP snooping profile called sanjose1:

[local]Router#configure

[local]Router(config)#igmp snooping profile sanjose1

[local]Redback(config-igmp-snooping-profile)#send deny

The following example shows how to permit the sending of multicast data by all circuits attached to an IGMP snooping profile called sanjose1:

[local]Router#configure

[local]Router(config)#igmp snooping profile sanjose1

[local]Redback(config-igmp-snooping-profile)#send permit

1.11   send community

1.11.1   Purpose

Specifies that the community attribute is sent to the specified external Border Gateway Protocol (eBGP) neighbor or peer group.

1.11.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration

1.11.3   Syntax Description

This command has no keywords or arguments.

1.11.4   Default

The community attribute is not sent to the eBGP neighbor or peer group. The community attribute is always sent to internal BGP (iBGP) peers.

1.11.5   Usage Guidelines

Use the send community command to specify that the community attribute is sent to the specified eBGP neighbor or peer group.

Note:  

This command is used only with eBGP neighbors or peer groups. The community attribute is always sent to iBGP peers.

Note:  

You cannot enable this command on a BGP neighbor that is part of a peer group, because this feature cannot be customized for individual members inside of a peer group.

Use the no form of this command to restore the default behavior of not sending the community attribute to eBGP neighbors.

1.11.6   Examples

The following example sends the community attribute to the eBGP 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)#remote as-200

[local]Redback(config-bgp-neighbor)#send community

1.12   send ext-community

1.12.1   Purpose

Specifies that the extended community attribute is sent to the specified external Border Gateway Protocol (eBGP) neighbor or peer group.

1.12.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration

1.12.3   Syntax Description

This command has no keywords or arguments.

1.12.4   Default

The extended community attribute is not sent to the eBGP neighbor or peer group. The extended community attribute is always sent to internal BGP (iBGP) peers.

1.12.5   Usage Guidelines

Use the send ext-community command to specify that the extended community attribute is sent to the specified eBGP neighbor or peer group.

Note:  

This command is used only with eBGP neighbors or peer groups. The extended community attribute is always sent to iBGP peers.

Note:  

You cannot enable this command on a BGP neighbor that is part of a peer group, because this feature cannot be customized for individual members inside of a peer group.

Use the no form of this command to restore the default behavior of not sending the extended community attribute to eBGP neighbors.

1.12.6   Examples

The following example sends the extended community attribute to the eBGP 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)#remote as-200

[local]Redback(config-bgp-neighbor)#send ext-community

1.13   send filter prefix-list

1.13.1   Purpose

Advertises to a Border Gateway Protocol (BGP) peer that a BGP speaker can send prefixed-based filtering to a peer.

1.13.2   Command Mode

BGP neighbor configuration

1.13.3   Syntax Description

This command has no keywords or arguments.

1.13.4   Default

The command is disabled.

1.13.5   Usage Guidelines

Use the send filter prefix-list command to advertise to a BGP peer that a BGP speaker can send address prefix-based route filtering to a peer.

When this command is enabled, and if the BGP peer advertises its willingness to accept address prefixed-based filtering (through the accept filter prefix-list command in BGP neighbor configuration mode), this local BGP speaker sends its inbound address prefix-based filtering to the remote peer. The remote peer uses the received address prefix-based filtering along with its local routing policies to determine whether routes should be advertised to the peer.

Use this command to save resources and avoid the generation, transmission, and processing of unnecessary routing updates.

Note:  

This command cannot be enabled on a BGP neighbor that is part of a peer group because this feature cannot be customized for individual members inside of a peer group.

Use the show bgp neighbor ip-addr received prefix-filter command to display address prefix-based route filtering configuration information.

Use the no form of this command to disable a BGP speaker from accepting route filtering from a peer.

For further information, see the Internet Drafts, Cooperative Route Filtering Capability for BGP-4, draft-ietf-idr-route-filter-03.txt, and Address Prefix Based Outbound Route Filter for BGP-4, draft-chen-bgp-prefix-orf-02.txt.

1.13.6   Examples

The following example enables the external BGP (eBGP) speaker at IP address, 10.1.1.1, to send outbound route filters to BGP peers:

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

[local]Redback(config-bgp-neighbor)#send filter prefix-list

1.14   send join

1.14.1   Purpose

Sends join messages upstream on the RPF primary and secondary interface without any outgoing interfaces (OIFs) being present.

1.14.2   Command Mode

• pim-dual configuration

1.14.3   Syntax Description

This command has no keywords or arguments.

1.14.4   Default

The send-join feature is disabled for a group, and the SmartEdge router continues sending new join messages upstream in the network.

1.14.5   Usage Guidelines

Use the send-join command to send join messages upstream on the RPF primary and secondary interface without any OIFs being present. If a join message from IGMP is received by PIM after the send-join feature is enabled for a specific group, the SmartEdge router does not send any new join messages upstream in the network. Instead, the SmartEdge router immediately adds the client to the OIF list and starts forwarding the multicast stream. In other words, PIM sends the join messages upstream only once and maps the join from IGMP to PIM.

Use the no form of this command to disable the sending of join messages before any multicast receivers are present.

1.14.6   Examples

The following example shows how to enable the send-join feature on the group with an IP address of 255.100.1.1. With this configuration, PIM sends new join messages upstream only once and maps the join from IGMP to PIM:

[local]Redback(config-ctx)#pim dual-join group 225.100.1.1 source 192.110.30.6

[local]Redback(config-pim-dual)#send join

1.15   send label

1.15.1   Purpose

Enables a Border Gateway Protocol (BGP) router to send Multiprotocol Label Switching (MPLS) labels with BGP IP Version 4 (IPv4) or IP Version 6 (IPv6) routes to a peer BGP router.

1.15.2   Command Mode

BGP neighbor address family configuration

1.15.3   Syntax Description

This command has no keywords or arguments.

1.15.4   Default

BGP routers distribute BGP IPv4 unicast routes without MPLS labels.

1.15.5   Usage Guidelines

Use the send label command to enable a BGP router to send MPLS labels with BGP IPv4 or IPv6 routes to a peer BGP router.

Note:  

You must configure this command on both the local router and the peer router in order for the routers to send IPv4 unicast or IPv6 unicast routes with MPLS labels.

One application for this command is the BGP/MPLS Virtual Private Network (VPN) Carrier Supporting Carrier configuration. The user must configure this command on the provider edge (PE) and customer edge (CE) routers between the super carrier and the ISP carrier.

This command has the following restrictions:

• If the send label command is configured for a peer that is already up, the BGP session with that peer will be automatically reset to make the configuration effective.
• The send label command is available only in the local and VPN contexts. In the local context, the send label command is available in iBGP and eBGP peer configurations. In VPN contexts, the send label command is available in eBGP peer configurations.
• The send label command transports IPv6 routes only if MPLS is enabled on the IPv4 core.
• The send label command is supported for unicast address families only.
• The send label command is available only in the local and VPN contexts.

Use the no form of this command to disable the BGP router from sending MPLS labels with IPv4 unicast routes.

1.15.6   Examples

The following example enables the local router to send MPLS labels along with BGP IPv4 unicast routes to peer 1.1.1.1:

[local]Redback(config)#context local

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

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

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

[local]Redback(config-bgp-peer-af)#send label

The following example shows how to enable the local router to send MPLS labels along with BGP IPv6 routes to peer 1.1.1.1:

[local]Redback(config)#context local

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

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

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

[local]Redback(config-bgp-peer-af)#send label

1.16   send-lifetime

1.16.1   Purpose

Establishes a start date and time for sending the key, and optionally, a stop date and time for sending the key.

1.16.2   Command Mode

key chain configuration

1.16.3   Syntax Description

1.16.4   Default

If you do not use this command, the key is sent starting immediately and continues to be sent indefinitely. If you do not specify a duration when using this command, the key is sent indefinitely.

1.16.5   Usage Guidelines

Use the send-lifetime command to specify when the key being configured is to be sent. The format of the start-datetime and stop-datetime arguments is yyyy:mm:dd:hh:mm[:ss] and is defined as follows:

• yyyy = The year in four digits (for example, 2001).
• mm = The month of the year in two digits (for example, 01). The range of values is 1 to 12.
• dd = The day of the month in two digits (for example, 24). The range of values is 1 to 31.
• hh = The hour of the day in two digits (for example, 23). The range of values is 0 to 23.
• mm = The minute of the hour in two digits (for example, 59). The range of values is 0 to 59.
• ss = The second of the minute in two digits (for example, 55). The range of values is 0 to 59.

If you issue the send-lifetime command without any optional constructs, the key is sent starting with the date and time that you specify and continues to be sent indefinitely.

You can replace an existing send lifetime value by issuing the send-lifetime command again, and specifying new parameters.

Use the no form of this command to specify that the key is no longer to be sent.

1.16.6   Examples

The following example establishes a send lifetime of January 25, 2002 at one minute and one second after 4:00 a.m. The key is accepted indefinitely:

[local]Redback(config-key-chain)#send-lifetime 2002:25:04:01:01

The following example establishes a send lifetime of January 25, 2002 at exactly midnight, and specifies that the key is to be sent for 30 minutes (1800 seconds):

[local]Redback(config-key-chain)#send-lifetime 2002:25:00:00 duration 1800

1.17   seq (Macro)

1.17.1   Purpose

Specifies a command in the macro.

1.17.2   Command Mode

macro configuration

1.17.3   Syntax Description

1.17.4   Default

No commands are specified for a macro.

1.17.5   Usage Guidelines

Use the seq command to specify a command to be included in the macro.

Use $1, $2, and so on, as placeholders in the command-string argument to designate the arguments for the command. You can specify up to nine placeholders, $1 to $9, for command arguments. Use the asterisk (*) character to specify all values of that argument for the command.

Use the exit command (in macro configuration mode) to complete the macro and exit to global configuration mode.

Use the no form of this command to delete the command from the macro.

1.17.6   Examples

The following example defines the macro, show-all-port, to display port information:

[local]Redback(config)#macro inherit show-port-all

[local]Redback(config-macro)#seq 10 show port $1/$2

[local]Redback(config-macro)#seq 20 show circuit $1/$2

[local]Redback(config-macro)#exit

The following example displays port and circuit data for port 3 of the traffic card in slot 4 using the same macro:

[local]Redback>show-port-all 4 3

The following example defines a macro that uses the * character:

[local]Redback(config)#macro inherit show-all

[local]Redback(config-macro)#seq 10 show config $*

[local]Redback(config-macro)#seq 20 show ip interface $*

[local]Redback(config-macro)#seq 30 show circuit $*

[local]Redback(config-macro)#exit

The following example captures the information displayed by the same macro in the file, output.txt:

[local]Redback>show-all | append output.txt

1.18   seq (IPv4 ACL)

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

1.18.1   Purpose

Creates an IPv4 access control list (ACL) statement that denies or allows packets that meet the specified criteria and sets the order of the statement in the ACL.

1.18.2   Command Mode

access control list configuration

1.18.3   Syntax Descriptions

1.18.4   Default

None

1.18.5   Usage Guidelines

Use the seq deny and seq permit constructs to create IP ACL statements to deny or allow packets that meet the specified criteria. This command also sets the order of the statement in the ACL. You can also use the deny and permit commands to create IP ACL statements; in this case, the SmartEdge OS automatically sets the order of the statement in the ACL.

In the IPv4 syntax, the cond port and cond length constructs are mutually exclusive with the range port end-port and range length end-length constructs.

With the seq permit construct, you can use the optional max-sessions limit and min-sessions limit constructs to specify a maximum or minimum number of simultaneous SSH or Telnet sessions allowed from an IP address or subnet. These constructs are available if you use the service ssh server or service telnet server commands with the access-group keyword to enable the SSH or Telnet protocol and apply the ACL. For statements where the any keyword is specified for both source and destination, only the max-sessions limit construct applies.

Note:  

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

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

Table 11 lists the valid keyword values for the protocol argument:

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

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

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

Table 15 lists the valid keyword values for the icmp-type argument.

Table 7 lists the valid keyword values for the igmp-type argument.

Table 8 lists the valid keyword values for the dscp-value argument.

Table 9 lists the valid keyword values for the prec-value argument.

Table 10 lists the valid keyword values for the tos-value argument.

1.18.6   Examples

The following example specifies that all IP traffic to destination host, 10.25.1.1, is to be denied, and all other traffic on subnet 10.25.1/24 is to be permitted:

[local]Redback(config-ctx)#ip access-list protect201

[local]Redback(config-access-list)#seq 12 deny ip any host 10.25.1.1

[local]Redback(config-access-list)#seq 22 permit ip any 10.25.1.0 0.0.0.255

1.19   seq (IPv6 ACL)

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

1.19.1   Purpose

Creates an IPv6 access control list (ACL) statement that denies or allows packets that meet the specified criteria and sets the order of the statement in the ACL.

1.19.2   Command Mode

access control list configuration

1.19.3   Syntax Descriptions

1.19.4   Default

None

1.19.5   Usage Guidelines

Use the seq deny and seq permit constructs to create an IP ACL statement to deny or allow packets that meet the specified criteria. This command also sets the order of the statement in the ACL. You can also use the deny and permit commands to create an IP ACL statement; in this case, the SmartEdge OS automatically sets the order of the statement in the ACL.

In IPv6 statements, a total of 100 rules can be added to an ACL, and IPv6 administrative ACLs (in contexts) have an implicit statement that enables IPv6 Neighbor Discovery.

Note:  

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

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

Table 11 lists the valid keyword values for the protocol argument:

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

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

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

Table 15 lists the valid keyword values for the icmp-type argument.

Table 16 lists the valid keyword values for the traffic-class-value argument.

1.19.6   Examples

The following example denies TCP traffic with the prefix 22:1:1::2/128 with default forwarding (DSCP code df) and all UDP traffic from port 80 or 81, and permits all IPv6 traffic:

[local]Redback(config-ctx)#ipv6 access-list listmgt
[local]Redback(config-access-list)#seq 21 deny tcp 22:1:1::2/128 any traffic-class eq df
[local]Redback(config-access-list)#seq 31 deny udp any any range 80 81
[local]Redback(config-access-list)#seq 41 permit ipv6 any any
 

1.20   server

1.20.1   Purpose

Configures the NTP server for a context.

1.20.2   Command Mode

NTP server configuration

1.20.3   Syntax Description

1.20.4   Default

There is no NTP server enabled in the context.

1.20.5   Usage Guidelines

To allow the system clock to be synchronized to an authoritative time source, configure an NTP server in a context with the server command. To name the NTP broadcast interface (connected to the subnet served by this NTP server), use the source if-name construct.

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

1.20.6   Examples

The following example configures an NTP server for the ips202 context.

[local]Redback(config)#context isp202
[local]Redback(config-ctx)#ntp-mode
[local]Redback(config-ntp-server)#server-mode
[local]Redback(config-ntp-server)#server 1.1.1.2 prefer source ntp

1.21   server-group (DHCP)

1.21.1   Purpose

Assigns a Dynamic Host Configuration Protocol (DHCP) server to a DHCP server group.

1.21.2   Command Mode

DHCP relay server configuration

1.21.3   Syntax Description

1.21.4   Default

DHCP servers are assigned to the default DHCP server group.

1.21.5   Usage Guidelines

Use the server-group command to assign a DHCP server to a DHCP server group.

Use the no form of this command to assign a DHCP server to the default server group.

1.21.6   Examples

The following example assigns DHCP server, dserver7, to the int-grp DHCP server group:

[local]Redback(config-ctx)#dhcp relay server dserver7

[local]Redback(config-dhcp-relay)#server-group int-grp

[local]Redback(config-dhcp-relay)#

1.22   server-mode (NTP)

1.22.1   Purpose

Enables NTP server functionality in the context.

1.22.2   Command Mode

NTP server configuration

1.22.3   Syntax Description

This command has no keywords or arguments.

1.22.4   Default

NTP functionality is not enabled in the context.

1.22.5   Usage Guidelines

To enable NTP server functionality in a context, enter the server-mode command in NTP server configuration mode.

1.22.6   Examples

The following example enables NTP server functionality in the isp202 context.

[local]Redback(config)#context isp202
[local]Redback(config-ctx)#ntp-mode
[local]Redback(config-ntp-server)#server-mode

1.23   service

1.23.1   Purpose

Enables application-layer protocols in a context.

1.23.2   Command Mode

• context configuration

1.23.3   Syntax Description

1.23.4   Default

The FTP, RCP, SCP, SFTP, SSH, Telnet, and TFTP servers are enabled in the local context and disabled in all other contexts; the SCP, SFTP, SSH, Telnet, and TFTP clients are enabled in all contexts.

1.23.5   Usage Guidelines

Use the service command to enable application-layer protocols in a context.

Use the no form of this command to disable application-layer protocols in a context.

1.23.6   Examples

The following example enables Telnet service:

[local]Redback(config-ctx)#service telnet

1.24   service air-filter

1.24.1   Purpose

Updates the service date in the fan tray unit in a SmartEdge 400 chassis or the fan and alarm unit in a SmartEdge 800 chassis to the current month and year.

1.24.2   Command Mode

• exec

1.24.3   Syntax Description

This command has no keywords or arguments.

1.24.4   Default

The service date is not updated; if the alarm for the air filter is enabled, the alarm condition is raised based on the previous service date.

1.24.5   Usage Guidelines

Use the service air-filter command to update the service date in the fan tray unit in a SmartEdge 400 chassis, or the fan and alarm unit in a SmartEdge 800 chassis, to the current month and year. The service date is stored in the EEPROM in the unit.

Note:  

The SmartEdge 100 router does not support this command; its air filter is not managed by the SmartEdge OS.

If you have configured the alarm for the air filter with the system alarm command (in global configuration mode), you must enter this command after you replace the air filter in either chassis, the fan tray unit in a SmartEdge 400 chassis, or the fan and alarm unit in a SmartEdge 800 chassis. Otherwise, the alarm condition is raised based on the previous service date.

To display the current service date, enter the show hardware fantray detail command (in any mode).

1.24.6   Examples

The following example updates the service date with the current month and year. If the current date is February 2005, and the alarm has been enabled with a three-month service interval, the alarm condition becomes active in May 2005:

[local]Redback>service air-filter

1.25   service auto-system-recovery

1.25.1   Purpose

Enables automatic system recovery.

1.25.2   Command Mode

• global configuration

1.25.3   Syntax Description

This command has no keywords or arguments.

1.25.4   Default

Automatic system recovery is disabled.

1.25.5   Usage Guidelines

Use the service auto-system-recovery command to enable automatic system recovery.

Automatic system recovery allows the system to recover from an error condition in which a process halts. The recovery is carried out by switching to the standby controller card while reloading the current controller card. If the standby controller is not ready or is absent, only a reload is performed.

Note:  

The SmartEdge 100 router does not have a standby controller card.

Use the no form of this command to disable automatic system recovery.

1.25.6   Examples

The following example enables automatic system recovery:

[local]Redback(config)#service auto-system-recovery

1.26   service card-auto-reload

1.26.1   Purpose

Enables the automatic reload of the Packet Processing ASIC (PPA) code on a traffic card if either of its PPAs becomes inoperable.

1.26.2   Command Mode

global configuration

1.26.3   Syntax Description

This command has no keywords or arguments.

1.26.4   Default

The PPA code reloads automatically on a traffic card if either of the PPAs becomes inoperable.

1.26.5   Usage Guidelines

Use the service card-auto-reload command to automatically reload the PPA code on a traffic card if either of its PPAs becomes inoperable.

Use the no form of this command to disable the automatic reload of PPA code on a traffic card.

Note:  

You enter this command only once to enable automatic reload of the PPA code for any traffic card.

1.26.6   Examples

The following example configures the system to automatically reload PPA code on a traffic card on a traffic card if either of its PPAs becomes inoperable:

[local]Redback(config)#service card-auto-reload

1.27   service clips dhcp

service clips dhcp [allow-duplicate-mac | source-mac] [ignore-relay] [maximum max-num] [context ctx-name | {vendor-class-id [default default-id]}] [service-policy pol-name]

no service clips

1.27.1   Purpose

Enables dynamic clientless IP service selection (CLIPS) on an Ethernet port, 802.1Q permanent virtual circuit (PVC) on an Ethernet port, or Asynchronous Transfer Mode (ATM) PVC.

1.27.2   Command Mode

• ATM PVC configuration
• dot1q PVC configuration
• link group configuration
• link PVC configuration
• port configuration

1.27.3   Syntax Description

(1)  See the "Usage Guidelnes" section for more information.

1.27.4   Default

CLIPS is disabled.

1.27.5   Usage Guidelines

Use the service clips dhcp command to enable dynamic CLIPS on an Ethernet port, 802.1Q PVC on an Ethernet port, or ATM PVC.

• This feature does not apply to first-generation traffic cards.
• You can enable CLIPS service on this circuit using the service clips dhcp command, or you can assign this circuit to a CLIPS group, using the service clips-group command (in dot1q PVC or port configuration mode), but you cannot do both.
• giaddr guidelines

  You can specify a unique IP address for the giaddr field using the user-class-id or vendor-class-id command (in DHCP giaddr configuration mode); if you do not, the SmartEdge OS uses the primary IP address of the interface that you have configured for the DHCP server for the giaddr field.

• Authentication context guidelines
  • To use the context ctx-name construct or the vendor-class-id keyword, you must configure the IP address of a reachable Remote Authentication Dial-In User Service (RADIUS) server and enable subscriber authentication in the context in which the subscriber circuit is to be bound. Use the radius server and aaa authentication subscriber commands (in context configuration mode), respectively.
  • The format of the username sent in access-request and accounting packets to RADIUS is MAC-address@domain, where the domain name is the authentication context.
  • If the subscriber record is stored on a RADIUS server and you do not enter either the context ctx-name construct or the vendor-class-id keyword, the system authenticates the subscriber in the context defined with the aaa last-resort command (in context configuration mode).

Use the no form of this command to disable CLIPS service.

1.27.6   Examples

The following example shows how to create eight CLIPS static circuits with session numbers ranging from 1 to 8 on port 1 of the Ethernet traffic card installed in slot 3 and then bind each circuit to an automatically generated subscriber name beginning with the string 10-1-1:

[local]Redback(config)#port ethernet 3/1
[local]Redback(config-port)#service clips
[local]Redback(config-port)#clips pvc 1 through 8
[local]Redback(config-port)#bind auto-subscriber “10-1-1” local

The following example shows how to enable dynamic CLIPS on port 1 of the Ethernet traffic card installed in slot 3, using the pol-dhcp service policy:

[local]Redback(config)#port ethernet 3/1
[local]Redback(config-port)#service clips dhcp service-policy pol-dhcp

The following example shows how to allow the CLIPS subscribers to act as if they are directly connected to the SmartEdge OS on port 1 on the Ethernet traffic card installed in slot 1:

[local]Redback(config)#port ethernet 1/1
[local]Redback(config-port)#encapsulation dot1q
[local]Redback(config-port)#dot1q pvc 10
[local]Redback(config-dot1q-pvc)#service clips dhcp ignore-relay context dhcp

The following example shows how to allow the CLIPS subscribers that use port 2 on the Ethernet traffic card installed in slot 1 to have duplicate MAC addresses; the unique giaddr is specified using the secondary IP address assigned to the if-dhcp interface:

[local]Redback(config)#context local
[local]Redback(config-ctx)#interface if-dhcp multibind
[local]Redback(config-if)#ip address 200.1.1.1/24
[local]Redback(config-if)#ip address 200.1.2.1/24 secondary
[local]Redback(config-if)#dhcp proxy 16000
[local]Redback(config-dhcp-giaddr)#user-class-id net1 giaddr 200.1.2.1
[local]Redback(config-dhcp-giaddr)#end
[local]Redback(config)#port ethernet 1/2
[local]Redback(config-port)#encapsulation dot1q
[local]Redback(config-port)#dot1q pvc 10
[local]Redback(config-dot1q-pvc)#service clips dhcp allow-duplicate-mac

1.28   service clips-exclude

1.28.1   Purpose

Specifies a condition by which a Dynamic Host Configuration Protocol (DHCP) host can be excluded from clientless IP service selection (CLIPS) service on this port or permanent virtual circuit (PVC).

1.28.2   Command Mode

• ATM PVC configuration
• dot1q PVC configuration
• link group configuration
• link PVC configuration
• port configuration

1.28.3   Syntax Description

1.28.4   Default

No DHCP received IDs are excluded.

1.28.5   Usage Guidelines

Use the service clips-exclude command to specify a condition by which a DHCP host can be excluded from CLIPS service on this port or PVC. Any host that matches the exclusion condition is ineligible for CLIPS service and is treated as a normal DHCP client.

Note:  

You must first enable dynamic CLIPS service for this port or PVC using the service clips or service clips-group command (in ATM PVC, dot1q PVC, link group, link PVC, or port configuration mode). You must also configure an external proxy or internal DHCP server in the same context as that in which the host messages are received.

The following guidelines apply to the formats for the id argument:

• When you surround a string with quotation marks, they are not part of the comparison.
• You must enclose a string with quotation marks if the string includes a space.
• A hex numeric string must have an even number of characters.
• Any string format, alphanumeric or hex numeric, supports both uppercase and lowercase characters.

Matching is performed on an octet basis. The match fails, if after the calculation of the starting position of the octets to be matched (using the offset position construct), there are fewer octets available for matching in the received ID than are specified by the vendor-class-id id construct.

To specify multiple exclusion conditions, enter this command for each condition; a DHCP host is excluded if it matches any of the specified conditions.

Use the no or default form of this command to remove an exclusion condition from the configuration for this port or PVC.

1.28.6   Examples

The following example shows how to configure an Ethernet port for CLIPS service and excludes DHCP hosts with an ID of “BP29” and an offset of 3 octets. The matching operation is performed on the 3rd through the 6th octet. If the received ID is CCBP2945, the matching operation is successful:

[local]Redback(config)#port ethernet 14/1
[local]Redback(config-port)#service clips-exclude vendor-class-id “BP29” offset 3

In the following example, the same matching operation is performed but with an offset of –3. In this case, the matching operation starts at the 6th octet and the match always fails because the number of octets to be matched (4) is greater than the number of octets available to be matched:

[local]Redback(config)#port ethernet 14/1
[local]Redback(config-port)#service clips-exclude vendor-class-id “BP29” offset -3

1.29   service clips-group

1.29.1   Purpose

Assigns a port or permanent virtual circuit (PVC) to the specified clientless IP service selection (CLIPS) group.

1.29.2   Command Mode

• dot1q PVC configuration
• port configuration

1.29.3   Syntax Description

1.29.4   Default

No ports or PVCs are assigned to any CLIPS group.

1.29.5   Usage Guidelines

Use the service clips-group command to assign this port or PVC to the specified CLIPS group. You can assign any mix of ports and PVCs to a CLIPS group. When you assign the port or PVC to the CLIPS group, you enable the creation dynamic CLIPS service on that port or PVC.

You must first create the CLIPS group, using the clips-group command (in global configuration mode), before you can assign a port or PVC to it.

You cannot assign ports and PVCs that you have configured on different traffic cards to the same CLIPS group; that is, CLIPS group supports intra-card, inter-port redundancy, but not inter-card redundancy.

You can enable dynamic CLIPS service on this circuit using the service clips dhcp command (in ATM PVC, dot1q PVC, or port configuration mode), or you can assign this port or PVC to a CLIPS group, but you cannot do both.

Use the no form of this command to remove the port or PVC from the specified CLIPS group.

Note:  

This command is available only for Ethernet and Gigabit Ethernet ports and the 802.1Q PVCs configured on them.

1.29.6   Examples

The following example assigns an 802.1Q PVC on an Ethernet port to the dynamic-clips group:

[local]Redback(config)#port ethernet 4/1

[local]Redback(config-port)#encapsulation dot1q

[local]Redback(config-port)#dot1q pvc 3

[local]Redback(config-dot1q-pvc)#service clips-group dynamic-clips

1.30   service clips (static)

1.30.1   Purpose

Enables static clientless IP service selection (CLIPS) on an Ethernet port, 802.1Q permanent virtual circuit (PVC) on an Ethernet port, or Asynchronous Transfer Mode (ATM) PVC.

1.30.2   Command Mode

• ATM PVC configuration
• dot1q PVC configuration
• link group configuration
• link PVC configuration
• port configuration

1.30.3   Syntax Description

This command has no keywords or arguments.

1.30.4   Default

CLIPS is disabled.

1.30.5   Usage Guidelines

Use the service clips command to enable static CLIPS on an Ethernet port, 802.1Q PVC on an Ethernet port, or ATM PVC.

For static CLIPS circuits, you must also configure one or more CLIPS PVCs using the clips pvc command (in link group, link PVC, or port configuration mode); see the clips pvc command description.

You can enable CLIPS service on this circuit using the service clips command, or you can assign this circuit to a CLIPS group, using the service clips-group command (in dot1q PVC or port configuration mode), but you cannot do both.

Use the no form of this command to disable CLIPS service.

1.30.6   Examples

The following example shows how to create eight CLIPS static circuits with session numbers ranging from 1 to 8 on port 1 of the Ethernet traffic card installed in slot 3 and then bind each circuit to an automatically generated subscriber name beginning with the string 10-1-1:

[local]Redback(config)#port ethernet 3/1

[local]Redback(config-port)#service clips

[local]Redback(config-port)#clips pvc 1 through 8

[local]Redback(config-port)#bind auto-subscriber “10-1-1” local

1.31   service console-break

1.31.1   Purpose

Enables the console break feature.

1.31.2   Command Mode

global configuration

1.31.3   Syntax Description

This command has no keywords or arguments.

1.31.4   Default

The console break feature is disabled.

1.31.5   Usage Guidelines

Use the service console-break command to enable the console break feature. When this feature is enabled, you can press the Ctrl+Break keys (in sequence) when you are connected to the SmartEdge router through the console port to send a break sequence to the system to halt the system, and enter kernel debug mode.

After the system receives the break sequence from the console, the prompt changes to db>. At this point, you can enter the commands in Table 17.

The system waits for a command for 25 seconds. If you do not enter any command within this time, the system automatically reloads.

Use the no form of this command to disable the console break feature. When the feature is disabled, the system does not process a break sequence from the console port.

1.31.6   Examples

The following example enables the console break feature:

[local]Redback(config)#service console-break 

1.32   service crash-dump-dram

1.32.1   Purpose

Enables dynamic random-access memory (DRAM) data collection during a crash dump.

1.32.2   Command Mode

• global configuration

1.32.3   Syntax Description

This command has no keywords or arguments.

1.32.4   Default

DRAM data collection is enabled.

1.32.5   Usage Guidelines

Use the service crash-dump-dram command to enable DRAM data collection during a crash dump.

Use the no form of this command to disable DRAM data collection during a core dump. In situations where the Packet Processing ASIC (PPA) data collection might take a long time, you can use the no form of this command to skip the DRAM data collection.

Note:  

The reload card command (in exec mode) suppresses the in-progress DRAM data collection if confirmed by user.

Note:  

Because DRAM data collection during a crash dump is enabled by default, the service crash-dump-dram command is used only to return the router to its default behavior after it has been changed by the no form of this command.

1.32.6   Examples

The following example disables the DRAM data collection during a crash dump:

[local]Redback(config)#no service crash-dump-dram

1.33   service domain-wildcard

1.33.1   Purpose

Enables the creation of domain aliases with embedded wildcard characters.

1.33.2   Command Mode

global configuration

1.33.3   Syntax Description

This command has no keywords or arguments.

1.33.4   Default

Wildcards are not permitted in domain name aliases.

1.33.5   Usage Guidelines

Use the service domain-wildcard command in global configuration mode to enable the creation of domain aliases with embedded wildcard characters. See the domain command for rules on the use of domain name alias wildcard characters.

Use the no form of this command to disable the use of the * wildcard character.

1.33.6   Examples

The following example illustrates the creation of the RBAKERIC* and *com domain aliases for the context bar and the RB* and bob*bar domain aliases for the context bob:

[local]Redback(config)#service domain-wildcard

[local]Redback(config)#context bar 

[local]Redback(config-ctx)#domain RBAKERIC* 

[local]Redback(config-ctx)#domain *com 

[local]Redback(config-ctx)#commit 

[local]Redback(config-ctx)#exit 

[local]Redback(config)#context bob 

[local]Redback(config-ctx)#domain RB* 

[local]Redback(config-ctx)#domain bob*bar 

[local]Redback(config-ctx)#commit 

1.34   service inter-context routing

1.34.1   Purpose

Enables intercontext static routing among non-local contexts.

1.34.2   Command Mode

global configuration

1.34.3   Syntax Description

This command has no keywords or arguments.

1.34.4   Default

Disabled

1.34.5   Usage Guidelines

Use the service inter-context routing command to enable intercontext static routing among non-local contexts. When this command is not enabled, intercontext static routing can still be used between the local context and non-local contexts.

Note:  

This command can only be disabled when there is no instance of non-local context static routing configured on the router.

For more information on creating and servicing contexts, see Configuring Contexts and Interfaces.

1.34.6   Examples

The following example enables non-local inter-context static routing:

[local]Redback(config)#service inter-context routing

[local]Redback(config)#context cust-abc

[local]Redback(config-ctx)#ip route 11.1.1.0/24 context web-xyz

[local]Redback(config-ctx)#context web-xyz

[local]Redback(config-ctx)#ip route 12.2.0.0/16 context cust-abc

1.35   service load-balance ip

1.35.1   Purpose

Specifies whether the load balancing hash algorithm should include only Layer 3 information or both Layer 3 and Layer 4 information.

1.35.2   Command Mode

global configuration

1.35.3   Syntax Description

1.35.4   Default

The load balancing algorithm includes Layer 3 information only.

1.35.5   Usage Guidelines

Use the service load-balance ip command to specify whether the load balancing hash algorithm should include only Layer 3 information or both Layer 3 and Layer 4 information. Layer 3 information consists of the source and destination IP. Layer 4 information includes the destination ports for TCP and UDP packets.

Including the TCP and UDP source and destination ports in the load balancing hash algorithm provides the following functionaries:

• Balances the traffic load among available paths while keeping packets for a particular data flow in order.
• Preserves the same path for all packets in a given flow.

Note:  

The service load-balance ip command is supported only on IPV4 and only for complete packets. It is not supported for IPv6 or when IP fragmentation is used.

Note:  

Use the show ip route summary command to verify whether Layer 4 load balancing is enabled on a router.

1.35.6   Examples

The following example shows how to configure the load balancing algorithm to include both Layer 3 and Layer 4 information:

[local]Redback#configure

[local]Redback(config)#service load-balance ip layer-4

The following example shows how to return the load balancing algorithm to the default setting, which includes only Layer 3 information:

[local]Redback#configure

[local]Redback(config)#service load-balance layer-3

1.36   service multiple-contexts

1.36.1   Purpose

Enables the creation of multiple contexts on a system.

1.36.2   Command Mode

global configuration

1.36.3   Syntax Description

This command has no keywords or arguments.

1.36.4   Default

Multiple contexts are disabled.

1.36.5   Usage Guidelines

Use the service multiple-contexts command to enable the creation of multiple contexts on a system. By default, the “local” context is present, and you cannot use the context command (in global configuration mode) to create additional contexts until you enable the multiple context feature.

Use the no form of this command to disable multiple contexts.

1.36.6   Examples

The following example displays sample output when an administrator attempts to create a new context, netone, when the multiple context feature is disabled:

[local]Redback(config)#context netone



Context netone doesn’t exist.

To configure multiple contexts configure 'service multiple-contexts'

The following example enables the multiple context feature and creates the context, netone:

[local]Redback(config)#service multiple-contexts

[local]Redback(config)#context netone

1.37   service-policy

1.37.1   Purpose

Configures a service policy name and enters service policy configuration mode.

1.37.2   Command Mode

• global configuration

1.37.3   Syntax Description

1.37.4   Default

None

1.37.5   Usage Guidelines

Use the service-policy command to configure a service policy name and enter service policy configuration mode.

Use the no form of this command to remove a service policy.

1.37.6   Examples

The following example configures a service policy, local-only, and allows subscribers access to the local context only:

[local]Redback(config)#service-policy name local-only

[local]Redback(config-policy-svc)#allow context name local

1.38   service profile hotline

1.38.1   Purpose

Specifies an RSE profile that references a policy that defines the classes to which you want to map HTTP redirect rules.

1.38.2   Command Mode

• subscriber configuration

1.38.3   Syntax Description

1.38.4   Default

No RSE profile is specified for hotlining.

1.38.5   Usage Guidelines

Use the service profile hotline command to specify an RSE profile that references a policy that defines the classes to which you want to map HTTP redirect rules. This command maps the HTTP redirect rules to classes defined in the policy that is referenced in the specified RSE profile for a MIP FA subscriber.

Use the no form of this command in to remove the specified service profile so that HTTP redirect rules are not mapped to that classes defined in the referenced policy.

1.38.6   Examples

The following example shows how to specify an RSE profile for hotlining:

[local]Redback(config)#context local

[local]Redback(config-ctx)#subscriber default

[local]Redback(config-sub)#service profile hotline hp1

1.39   service upload-coredump

1.39.1   Purpose

Enables the sending of core dump files from the local SmartEdge router to the specified URL using the File Transfer Protocol (FTP).

1.39.2   Command Mode

• global configuration

1.39.3   Syntax Description

1.39.4   Default

None

1.39.5   Usage Guidelines

Use the service upload-coredump command to enable the sending of core dump files from the local SmartEdge router to a URL using FTP. The url argument takes the following form, where the username:passwd construct specifies the user and an optional password, the ip-addr argument is the IP address of the FTP server, the hostname argument is the hostname of the FTP server, and the optional :port and /directory arguments are a port or directory on the FTP server.

//username[:passwd]@{ip-addr | hostname} [:port] [//directory]

The hostname argument can only be used if Domain Name System (DNS) resolution is enabled using the ip domain-lookup, ip domain-name, and ip name-servers commands in context configuration mode. For more information, see the Command List.

Note:  

Use double slashes (//) if the pathname to the directory on the remote server is an absolute pathname; use a single slash (/ ) if it is a relative pathname (under the hierarchy of the username account home directory).

Note:  

We strongly recommend that you enable this feature because it maximizes the use of available disk space and improves system stability and performance. For more information about core dumps, crash files, and the operations commands to administer them, see Managing Files.

Use the no form of this command to disable the sending of crash files to the specified URL.

1.39.6   Examples

The following example specifies that crash files are to be sent to the specified URL using FTP:

[local]Redback(config)#service upload-coredump ftp://client1:secret@10.10.20.78//out 

1.40   service vxworks-log-to-screen

1.40.1   Purpose

Enables displaying VxWorks logs on a console connected to one of the console ports on the back of the chassis.

1.40.2   Command Mode

• global configuration

1.40.3   Syntax Description

This command has no keywords or arguments.

1.40.4   Default

By default, the VxWorks console port output is redirected, so it is not displayed even though the console cable is connected.

1.40.5   Usage Guidelines

Use the service vxworks-log-to-screen command to enable the VxWorks logs to display on a console connected to one of the console ports on the back of the chassis. Use this command to collect logs without interruption during a switchover or when the SmartEdge router is rebooting.

VxWorks is the OS on the controller cards that is responsible for most low-level processing, such as driving or monitoring traffic cards. To display the VxWorks logs on the VxWorks console, you may also need to set the vx-other flag in the Open Firmware (OFW) shell. To set this flag, access the OFW shell and enter the setenv vx-other 0x27a command at the OK prompt.

For procedures to access the OFW CLI, see Data Collection Guideline in the SmartEdge OS library.

1.41   session-action