Contents

1   Command Descriptions

Commands starting with “dec” through commands starting with “dz” are included.

1.1   decrement ttl

1.1.1   Purpose

Enables transit routers to decrement the Multiprotocol Label Switching (MPLS) time-to-live (TTL) by 1 at each hop.

1.1.2   Command Mode

MPLS router configuration

1.1.3   Syntax Description

This command has no keywords or arguments.

1.1.4   Default

Transit routers are enabled to decrement the MPLS TTL by 1 at each hop.

1.1.5   Usage Guidelines

Use the decrement ttl command to enable transit routers to decrement the MPLS TTL by 1 at each hop.

Use the no form of this command to disable transit routers from decrementing the MPLS TTL by 1 at each hop.

Note:  

The default behavior of the SmartEdge® router is to decrement the MPLS TTL by 1 at each hop, so the decrement ttl command is used to return the router to its default behavior after it has been changed by the no form of this command.

1.1.6   Examples

The following example enables transit routers to decrement the MPLS TTL by 1 at each hop:

[local]Redback(config-ctx)#router mpls 234

[local]Redback(config-mpls)#decrement ttl

1.2   default-information originate

1.2.1   Purpose

In RIP interface configuration mode, configures the specified Routing Information Protocol (RIP) or RIP next generation (RIPng) interface to originate the default route.

In RIP router configuration mode, injects the default route into the RIP or RIPng instance.

1.2.2   Command Mode

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

1.2.3   Syntax Description

1.2.4   Default

The default route is not sent.

1.2.5   Usage Guidelines

Use the default-information originate command (in RIP or RIPng interface configuration mode) to configure the specified RIP or RIPng interface to originate the default route, which is 0.0.0.0 for IPv4 and ::/0 for IPv6.

Use the default-information originate command (in RIP or RIPng router configuration mode) to inject the default route into the RIP or RIPng instance.

To apply a route map to the default route, use the optional route-map map-name construct. In this case, the default route is generated only when there is a match in the specified route map.

Use the no or default form of this command (in RIP or RIPng interface configuration mode) to configure the interface to not originate the default route.

Use the no or default form of this command (in RIP or RIPng router configuration mode) to not inject the default route into the RIP or RIPng instance.

1.2.6   Examples

The following example injects the default route into the rip001 RIP instance:

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

[local]Redback(config-rip)#default-information originate

The following example originates the default route from the fe1 interface for the rip002 RIP instance:

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

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

[local]Redback(config-rip-if)#default-information originate

1.3   default-lease-time

1.3.1   Purpose

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

1.3.2   Command Mode

• DHCP server configuration
• DHCP subnet configuration

1.3.3   Syntax Description

1.3.4   Default

The default length of time is two hours.

1.3.5   Usage Guidelines

Use the default-lease-time command to specify the default lease time for the DHCP server or one of its subnets. In DHCP server configuration mode, this command specifies the default lease time for all subnets; in DHCP subnet configuration mode, it specifies the default lease time for that subnet. The value you specify for a subnet overrides the global value for the server.

Note:  

If the default lease time is set very low, it will affect the performance of the SmartEdge router, causing some subscribers to lose their leases.

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

1.3.6   Examples

The following example specifies a default lease time of 4 hours (14000) for the DHCP server and all its subnets:

[local]Redback(config)#context dhcp

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

[local]Redback(config-dhcp-server)#default-lease-time 14400

1.4   default-metric (OSPF)

1.4.1   Purpose

Configures the default metric used for redistributed Open Shortest Path First (OSPF) or OSPF Version 3 (OSPFv3) routes when no metric is specified.

1.4.2   Command Mode

• OSPF router configuration
• OSPF3 router configuration

1.4.3   Syntax Description

1.4.4   Default

No default metric is configured. If a metric value is not configured through the redistribute command in OSPF router configuration mode or applied via a route map, the metric in the system routing table is used.

1.4.5   Usage Guidelines

Use the default-metric command to configure the default metric used for redistributed OSPF or OSPFv3 routes when no metric is specified. You can specify a metric through the redistribute command (in OSPF or OSPF3 router configuration mode), or indirectly by applying a route map through the route-map command (in route map configuration mode).

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

1.4.6   Examples

The following example configures a default metric value of 40:

[local]Redback(config-ospf)#default-metric 40

1.5   default-metric (RIP)

1.5.1   Purpose

Sets the default metric for the Routing Information Protocol (RIP) or RIP next generation (RIPng) instance.

1.5.2   Command Mode

• RIPng router configuration
• RIP router configuration

1.5.3   Syntax Description

1.5.4   Default

The metric value is 0.

1.5.5   Usage Guidelines

Use the default-metric command to set the default metric for the RIP or RIPng instance. The default value is used when a route with incompatible metrics is received into the RIP or RIPng instance; for example, when a route from a different routing domain is imported into RIP or RIPng.

Use the no or default form of this command to return the default metric value to 0.

1.5.6   Examples

The following example sets the default metric to 11 for the RIP instance, rip001:

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

[local]Redback(config-rip)#default-metric 11

1.6   default-originate

1.6.1   Purpose

Advertises the default route of the specified address family, even when the default route is not installed in the Border Gateway Protocol (BGP) routing table, to the BGP neighbor.

1.6.2   Command Mode

• BGP neighbor address family configuration
• BGP peer group address family configuration

1.6.3   Syntax Description

1.6.4   Default

No default route is sent to peers.

1.6.5   Usage Guidelines

Use the default-originate command to advertise the default route of the specified address family, even when the default route is not installed in the BGP routing table, to the BGP neighbor. The default route, 0.0.0.0/0, is typically sent to a BGP neighbor that does not carry full Internet routes.

If the route-map map-name keyword construct is not used, or if the specified route map does not include a match ip address prefix-list pl-name statement, the specified address family unconditionally advertises the default route to the BGP neighbor.

When the route-map map-name keyword construct is used, and the route map has a match ip address prefix-list pl-name statement, the specified address family advertises the default route only if the address prefix entry specified in the IP prefix list exists in the routing information base (RIB).

Use the no form of this command to avoid sending the default route to neighbors or peer groups.

1.6.6   Examples

The following example sends the unicast default route unconditionally to the neighbor at IP address 102.210.210.1, and only sends it to the neighbor at IP address, 68.68.68.68, when route, 20.0.0.0/8, with the next-hop address, 192.192.192.253:

[local]Redback(config-ctx)#route-map map1

[local]Redback(config-route-map)#match ip address prefix-list pref1

[local]Redback(config-route-map)#match ip next-hop prefix-list next-hop-list

[local]Redback(config-route-map)#exit

[local]Redback(config-ctx)#ip prefix-list pref1

[local]Redback(config-prefix-list)#permit 20.0.0.0/8

[local]Redback(config-prefix-list)#exit

[local]Redback(config-ctx)#ip prefix-list next-hop-list

[local]Redback(config-prefix-list)#permit 192.192.192.253/32

[local]Redback(config-prefix-list)#exit

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

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

[local]Redback(config-bgp-neighbor)#remote-as 200

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

[local]Redback(config-bgp-peer-af)#default-originate

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

[local]Redback(config-bgp-neighbor)#exit

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

[local]Redback(config-bgp-neighbor)#remote-as 300

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

[local]Redback(config-bgp-peer-af)#default-originate route-map map1

1.7   default-peer

1.7.1   Purpose

Configures a default peer from which to accept all Multicast Source Discovery Protocol (MSDP) source active (SA) messages.

1.7.2   Command Mode

MSDP router configuration

1.7.3   Syntax Description

1.7.4   Default

None

1.7.5   Usage Guidelines

Use the default-peer command to configure a default peer from which to accept all MSDP SA messages. A default peer is needed in topologies where MSDP peers do not coexist with BGP peers. In such a case, the reverse path forwarding (RPF) check on SA messages can fail, and no SA messages are accepted. In these cases, you can configure the peer as a default peer, and bypass RPF checks.

Note:  

An MSDP peer must already be configured before it can be made a default peer.

The peer-addr argument must be the IP address of a previously configured peer.

Use the pl-name argument to allow only those SA entries whose RP is permitted in the prefix list; otherwise, all SA messages from the default peer are accepted.

Use the no form of this command to disable the default peer.

1.7.6   Examples

The following example configures the peer address, 192.168.3.8, as the default peer:

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

[local]Redback(config-msdp)#default-peer 192.168.3.8

1.8   default-route

1.8.1   Purpose

Changes the attributes of a default route originated into a stub area or a not-so-stubby-area (NSSA).

1.8.2   Command Mode

• OSPF area configuration
• OSPF3 area configuration

1.8.3   Syntax Description

1.8.4   Default

The metric value for the default route is 1. For stub areas, a Type 3 LSA with a metric value of 1 is advertised. The metric type is ignored. For NSSAs that import summary advertisements, a Type 7 LSA with a metric value of 1 and a route metric type of 2 is advertised. For NSSAs that do not import summary advertisements, a Type 3 LSA with a metric value of 1 is advertised. The metric type is ignored.

1.8.5   Usage Guidelines

Use the default-route command to change the attributes of a default route originated into a stub area or NSSA. The LSA advertising the default route depends on the area type and whether summary advertisements (Type 3 and 4 LSAs) are advertised into the area.

For stub areas, a Type 3 LSA with a metric value of 1 is advertised by default. The default-route command can be used to modify the metric. The metric type is ignored.

For NSSAs that import summary advertisements, a Type 7 LSA with a metric value of 1 and route metric type of 2 is advertised by default. The default-route command can be used to modify the metric or metric type.

For NSSAs that do not import summary advertisements, a Type 3 LSA with a metric value of 1 is advertised by default. The default-route command can be used to modify the metric. The metric type is ignored.

If there are two routers originating a default route with the same metric value, the closest router is chosen to perform routing.

Use the no form of this command to restore the default attributes for the originated default route.

1.8.6   Examples

The following example configures a default route metric value of 3:

[local]Redback(config-ospf-area)#default-route metric 3

1.9   delete

1.9.1   Purpose

Deletes a file from the local file system on either the active or standby controller card.

1.9.2   Command Mode

exec (10)

1.9.3   Syntax Description

1.9.4   Default

None

1.9.5   Usage Guidelines

Use the delete command to delete a file from the local file system on either the active or standby controller card.

Use the mate keyword to specify the controller card to which you are not connected.

Note:  

The SmartEdge 100 router does not support standby controller cards; therefore, the mate keyword is not applicable.

When referring to a file, 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.

Use the command-line interface (CLI) online Help for this command or the show crashfiles command (in any mode) to list the crash files currently located on the system.

If you do not specify the -noconfirm keyword, the system prompts you to confirm the deletion. Enter y to confirm the operation; if you enter any other character, the system does not delete the file.

1.9.6   Examples

The following example deletes a file in a nested subdirectory:

[local]Redback#delete /flash/backup/old/current.cfg

The following example deletes a crash file using the online Help to determine the URL; a confirmation message is accepted:

[local]Redback#delete crashfile ?



  /md/dlmd_50.core         

  /md/dlmd_50.mini.core         

  WORD                   URL of file to delete in local filesystem



[local]Redback#delete crashfile /md/dlmd_50.core

Are you sure you want to delete /md/dlmd_50.core ?y

1.10   delete partition

1.10.1   Command Mode

exec (10)

1.10.2   Syntax Description

1.10.3   Default

None.

1.10.4   Usage Guidelines

Removes the specified partition on an SSE disk. All data in the partition is deleted.

This command cannot be executed if the partition is mounted on any other card.

1.10.5   Examples

[local]Redback#delete partition sse 2 1 p01

[local]Redback#delete partition sse 2 1 p01

1.11   demand-circuit

1.11.1   Purpose

Configures Open Shortest Path First (OSPF) or OSPF Version 3 (OSPFv3) to treat a point-to-point (P2P) or point-to-multipoint (P2MP) interface as a demand circuit as described in RFC 1793, Extending OSPF to Support Demand Circuits.

1.11.2   Command Mode

• OSPF interface configuration
• OSPF3 interface configuration

1.11.3   Syntax Description

This command has no keywords or arguments.

1.11.4   Default

Demand circuit support is disabled on P2P and P2MP interfaces. Demand circuit support is implicitly enabled on virtual links and sham links.

1.11.5   Usage Guidelines

Use the demand-circuit command to configure OSPF or OSPFv3 to treat a P2P or P2MP interface as a demand circuit, as described in RFC 1793, Extending OSPF to Support Demand Circuits.

Demand circuits are network segments whose costs vary with usage; charges can be based both on connect time and on bytes or packets transmitted. OSPF or OSPFv3 routing usually requires a demand circuit’s underlying data-link connection to be constantly open, resulting in unwanted usage charges. Using the demand-circuit command enables OSPF or OSPFv3 Hello packets and the refresh of OSPF or OSPFv3 routing information to be suppressed on-demand circuits, allowing the underlying data-link connections to be closed when not carrying traffic.

Note:  

Hello suppression is not be negotiated unless demand circuit support is enabled.

Use the no form of this command to remove the demand circuit designation.

1.11.6   Examples

The following example configures the OSPF interface POS1/2 in area 0 to be a demand circuit:

[local]Redback(config-ospf)#area 0

[local]Redback(config-ospf-area)#interface POS1/2

[local]Redback(config-ospf-if)#demand-circuit

1.12   deny (IPv4 ACL)

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

1.12.1   Purpose

Creates an IPv4 access control list (ACL) statement that denies packets that meet the specified criteria.

1.12.2   Command Mode

access control list configuration

1.12.3   Syntax Descriptions

1.12.4   Default

None

1.12.5   Usage Guidelines

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

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

In IPv4 statements, follow these guidelines:

• The cond port and cond length constructs are mutually exclusive with the range port end-port and range length end-length constructs.
• If you specify a limit for both an IP address and the related subnet, the limit for the subnet takes precedence. Similarly, a limit specified for a larger subnet takes precedence over limits specified for related smaller subnets. From all sources combined, the SmartEdge router supports up to 32 active Telnet and SSH sessions.

Note:  

In all ACLs, there is an implicit deny any any statement at the end of the list. Be aware that 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 coming in 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.

The following tables list the valid keyword values for the protocol argument in statements for IPv4 ACLs, see Table 1.

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

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

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

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

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

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

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

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

1.12.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)#deny ip any host 10.25.1.1

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

1.13   deny (IPv6 ACL)

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

1.13.1   Purpose

Creates an IPv6 access control list (ACL) statement that denies packets that match the specified criteria.

1.13.2   Command Mode

access control list configuration

1.13.3   Syntax Descriptions

1.13.4   Default

None

1.13.5   Usage Guidelines

Use the deny command to create an IP ACL statement to deny packets that match the specified criteria. This command does not set the order of the statement in the ACL; the OS automatically sets the order. Use the seq deny command to set 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) automatically enable 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 deny ipv6 any any or deny 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 10 lists the valid keyword values for the protocol argument:

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

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

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

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

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

1.13.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)#deny tcp 22:1:1::2/128 any traffic-class eq df
[local]Redback(config-access-list)#deny udp any any range 80 81
[local]Redback(config-access-list)#permit ipv6 any any
 

1.14   deny (service policy)

1.14.1   Purpose

Denies access to the specified context, Point-to-Point over Ethernet (PPPoE) service, or domain for PPPoE subscriber sessions that are attached to the service policy. This command also denies a DHCP client host access to the circuit that is associated with the service policy.

1.14.2   Command Mode

service policy configuration

1.14.3   Syntax Description

1.14.4   Default

None

1.14.5   Usage Guidelines

Use the deny command to deny access to the specified context, PPPoE service, or domain for subscriber PPPoE sessions that are attached to the service policy. You can also use the deny command to deny a DHCP client host access to the circuit that is associated with the service policy.

Any DHCP hosts, contexts, PPPoE services, or domains that are not explicitly specified through this command are implicitly allowed.

Note:  

The router does not support both allow and deny in the same service profile.

Use the no form of this command to allow access to a prohibited context, PPPoE service, or domain. Or, you can use the no form of this command to remove a configuration that denies a DHCP client host access to the circuit that is associated with the service policy.

1.14.6   Examples

The following example shows how to configure a service policy, local-only, which denies subscriber access to the ctx_black context and dmn_black domain:

[local]Redback(config)#service-policy name local-only
[local]Redback(config-policy-svc)#deny context name ctx_black 
[local]Redback(config-policy-svc)#deny domain name dmn_black

The following example shows how to create a service policy called AllowData, which denies the PPPoE service named voice and allows all other PPPoE services:

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

[local]Redback(config-policy-svc)#deny pppoe service-name voice

The following example shows how to create a service policy called deny hosts, which denies the DHCP client hosts named group1, group4, and group5 access to the circuit that is associated with the specified service policy and allows all other DHCP client hosts to access the circuit:

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

[local]Redback(config-policy-svc)#deny dhcp hostname group1

[local]Redback(config-policy-svc)#deny dhcp hostname group4

[local]Redback(config-policy-svc)#deny dhcp hostname group5

1.15   description (ACL)

1.15.1   Purpose

Associates a text description with an IP access control list (ACL) or a policy ACL.

1.15.2   Command Mode

access control list configuration

1.15.3   Syntax Description

1.15.4   Default

No description is associated with the ACL.

1.15.5   Usage Guidelines

Use the description command to associate a text description with the ACL.

You can use a text description to notate what an ACL consists of or how it is to be used. Only one description can be associated with a single ACL. To revise a description, create a new one, and the old one is overwritten.

Use the no form of this command to remove the description from an ACL.

1.15.6   Examples

The following example creates a text description to be associated with the IP ACL, restricted:

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

[local]Redback(config-access-list)#description private net

The following example creates a text description to be associated with the policy ACL, trafficin:

[local]Redback(config-ctx)#policy access-list trafficin

[local]Redback(config-access-list)#description inbound traffic web

1.16   description (APS)

1.16.1   Purpose

Associates textual information with an Automatic Protection Switching (APS) or Multiplex Section Protection (MSP) group.

1.16.2   Command Mode

APS configuration

1.16.3   Syntax Description

1.16.4   Default

No description is associated with an APS/MSP group.

1.16.5   Usage Guidelines

Use the description command to associate textual information with an APS/MSP group. The show configuration command displays this text for the APS/MSP group.

Use the no or default form of this command to delete the existing description. Because only one description for an APS/MSP group can exist, when you use the no or default form of this command, it is not necessary to include the text argument. To change a description, create a new one; it overwrites the existing one.

1.16.6   Examples

The following example shows how to associate a description with the APS/MSP group lab48:

[local]Redback(config)#aps group lab48 pos

[local]Redback(config-aps)#description OC-48 APS

1.17   description (ATM, Frame Relay)

1.17.1   Purpose

Associates a textual description with an Asynchronous Transfer Mode (ATM) or Frame Relay profile or permanent virtual circuit (PVC).

1.17.2   Command Mode

• ATM profile configuration
• ATM PVC configuration
• Frame Relay profile configuration
• Frame Relay PVC configuration

1.17.3   Syntax Description

1.17.4   Default

No description is associated with any profile or PVC.

1.17.5   Usage Guidelines

Use the description command to associate textual information with an ATM or Frame Relay profile or PVC. This text is displayed by the appropriate show command.

Use the no or default form of this command to delete the existing description. Because there can be only one description for a profile or PVC, when you use the no or default form of this command, it is not necessary to include the text argument. To change a description, create a new one; it overwrites the existing one.

1.17.6   Examples

The following example shows how to associate a description with an ATM PVC configured on an ATM OC port:

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

[local]Redback(config-atm-oc)#atm pvc 0 32 profile dslam1 encapsulation bridge1483

[local]Redback(config-atm-pvc)#description ATM bridged 1483 circuit

1.18   description (BGP)

1.18.1   Purpose

Associates a description with the Border Gateway Protocol (BGP) neighbor or peer group.

1.18.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration

1.18.3   Syntax Description

1.18.4   Default

None

1.18.5   Usage Guidelines

Use the description command to associate a description with the BGP neighbor or peer group. This command does not affect the BGP connection. It is used as a note in the configuration.

Use the no form of this command to remove a description from the configuration. Because there can be only one description for a BGP neighbor or peer group, when you use the no form of this command, it is not necessary to include the text argument.

1.18.6   Examples

The following example provides the description, Palo Alto BGP Neighbor 12, for the BGP neighbor at IP address, 102.210.210.1:

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

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

[local]Redback(config-bgp-neighbor)#description Palo Alto BGP Neighbor 12

1.19   description (bridge)

1.19.1   Purpose

Associates a textual description with a bridge.

1.19.2   Command Mode

bridge configuration

1.19.3   Syntax Description

1.19.4   Default

No description is associated with any bridge.

1.19.5   Usage Guidelines

Use the description command to associate textual information with a bridge. This text displays by the appropriate show command.

Use the no or default form of this command to delete the existing description. Because there can be only one description for a bridge, when you use the no or default form of this command, it is not necessary to include the text argument. To change a description, create a new one; it overwrites the existing one.

1.19.6   Examples

The following example shows how to associate a description with the bridge, isp1, configured in the bridge context:

[local]Redback(config)#context bridge
[local]Redback(config-ctx)#bridge isp1
[local]Redback(config-bridge)#description Bridge for all traffic to ISP1

1.20   description (Dot1Q)

1.20.1   Purpose

Associates a textual description with an 802.1Q profile or permanent virtual circuit (PVC).

1.20.2   Command Mode

• dot1q profile configuration
• dot1q PVC configuration

1.20.3   Syntax Description

1.20.4   Default

No description is associated with any profile or PVC.

1.20.5   Usage Guidelines

Use the description command to associate textual information with an 802.1Q profile or PVC. This text is displayed by the appropriate show command.

Use the no or default form of this command to delete the existing description. Because there can be only one description for a profile or PVC, when you use the no or default form of this command, it is not necessary to include the text argument. To change a description, create a new one; it overwrites the existing one.

1.20.6   Examples

The following example provides the description, local vlan, for the 802.1Q PVC 100:

[local]Redback(config-port)#dot1q pvc 100
[local]Redback(config-dot1q-pvc)#description local vlan

1.21   description (interface)

1.21.1   Purpose

Associates a text description with an interface.

1.21.2   Command Mode

interface configuration

1.21.3   Syntax Description

1.21.4   Default

None

1.21.5   Usage Guidelines

Use the description command to associate a text description with an interface. The description appears in the output of the show ip interface and show configuration commands. Text can be any alphanumeric string, including spaces. For more information on the show configuration command, see Using the CLI.

Use the no or default form of this command to delete the existing description. Because there can be only one description for an interface, you can omit the text argument when you use the no form of this command. To change a description, create a new one; it overwrites the existing one.

1.21.6   Examples

The following example creates the interface, upstream, as the upstream interface to the goldisp.net service provider:

[local]Redback(config-ctx)#interface upstream

[local]Redback(config-if)#description interface to goldisp.net

1.22   description (L2TP peer)

1.22.1   Purpose

Associates textual information with a Layer 2 Tunneling Protocol (L2TP) peer.

1.22.2   Command Mode

L2TP peer configuration

1.22.3   Syntax Description

1.22.4   Default

No description is associated with the L2TP peer.

1.22.5   Usage Guidelines

Use the description command to associate textual information with the L2TP peer. The description appears in the output of the show configuration command with the l2tp keyword in any mode.

Use the no or default form of this command to delete the existing description. Because there can be only one description for a peer, when you use the no form of this command, it is not necessary to include the text argument.

To change a description, create a new one; it overwrites the existing one.

1.22.6   Examples

The following example shows how to select (or create) an L2TP peer, and then associates a text description with it:

[local]Redback(config)#context local
[local]Redback(config-ctx)#l2tp-peer name isp1.net remote 172.16.1.2 local 172.16.1.1
[local]Redback(config-l2tp)#description Corporate offices in Connecticut

The following example shows how to change the description created in the previous example:

[local]Redback(config-l2tp)#description Corporate offices in Hartford

The following example shows how to delete an existing description:

[local]Redback(config-l2tp)#no description

1.23   description (link group)

1.23.1   Purpose

Specifies a text string description of the access link group.

1.23.2   Command Mode

link group configuration

1.23.3   Syntax Description

1.23.4   Default

The link group has no description in the default state.

1.23.5   Usage Guidelines

Use the description command in link group configuration mode to specify a text string description of the access link group.

For access link groups, the description can be used as a prefix to the RADIUS NAS-PORT-ID attribute. Enter a unique ID for each access link group.

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

1.23.6   Examples

The following example illustrates the use of the description command:

[local]Redback(config)#link-group lg1 access

[local]Redback(config-link-group)#description 35ttf

1.24   description (lists)

1.24.1   Purpose

Associates a description with the autonomous system (AS) path list, community list, extended community list, IP prefix list, or IP Version 6 (IPv6) prefix list.

1.24.2   Command Mode

• AS path list configuration
• community list configuration
• extended community list configuration
• IP prefix list configuration
• IPv6 prefix list configuration

1.24.3   Syntax Description

1.24.4   Default

None

1.24.5   Usage Guidelines

Use the description command to associates a description with the AS path list, community list, extended community list, IP prefix list, or IPv6 prefix list. For more information, see the as-path-list, community-list, ext-community-list, ip prefix-list, and ipv6 prefix-list commands in context configuration mode.

Use the no form of this command to remove a description. Because there can be only one description for an AS path list, community list, extended community list, IP prefix list, or IPv6 prefix list, when you use the no form of this command, it is not necessary to include the text argument.

1.24.6   Examples

The following example configures a description for the community list, com-list1:

[local]Redback(config-ctx)#community-list com-list1

[local]Redback(config-community-list)#description filter for community1

1.25   description (MPLS static and RSVP LSPs)

1.25.1   Purpose

Associates a description with a static label-switched path (LSP) or a Resource Reservation Protocol (RSVP) LSP.

1.25.2   Command Mode

• MPLS static LSP configuration
• RSVP LSP configuration

1.25.3   Syntax Description

1.25.4   Default

None

1.25.5   Usage Guidelines

Use the description command to associate a description with a static LSP or an RSVP LSP. This command does not affect the LSP; it is used only as a note in the configuration.

Use the no form of this command to remove a description from the configuration. Because there can be only one description for an LSP, when you use the no form of this command, it is not necessary to include the text argument.

1.25.6   Examples

The following example provides the description, Shortcut to Net 41A, for the MPLS static LSP, To41A:

[local]Redback(config)#context sj1

[local]Redback(config-ctx)#router mpls-static

[local]Redback(config-mpls-static)#lsp To41A

[local]Redback(config-mpls-static-lsp)#description Shortcut to Net 41A

[local]Redback(config-mpls-static-lsp)#

1.26   description (MSDP peers)

1.26.1   Purpose

Associates a text description with an Multicast Source Discovery Protocol (MSDP) peer.

1.26.2   Command Mode

MSDP peer configuration

1.26.3   Syntax Description

1.26.4   Default

None

1.26.5   Usage Guidelines

Use the description command to associate a text description with an MSDP peer. The description can be a maximum of 80 characters.

Use the no form of this command to remove the description from the MSDP peer. Because there can be only one description for an MSDP peer, when you use the no form of this command, it is not necessary to include the text argument.

1.26.6   Examples

The following example sets the MSDP peer description to Peer66 to used for testing:

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

[local]Redback(config-msdp-peer)#description Peer66 to used for testing

1.27   description (port)

1.27.1   Purpose

Associates textual information with a port.

1.27.2   Command Mode

• ATM DS-3 configuration
• ATM OC configuration
• DS-0 group configuration
• DS-1 configuration
• DS-3 configuration
• E1 configuration
• E3 configuration
• interface configuration
• port configuration

1.27.3   Syntax Description

1.27.4   Default

No description is associated with a port.

1.27.5   Usage Guidelines

Use the description command to associate textual information with the port. The show port detail command for the port displays this text.

Use the no or default form of this command to delete the existing description. Because there can be only one description for a port, when you use the no or default form of this command, it is not necessary to include the text argument. To change a description, create a new one; it overwrites the existing one.

1.27.6   Examples

The following example shows how to associate a description with the management port on the controller card in slot 7:

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

[local]Redback(config-port)#description Management port

1.28   description (port, channel)

1.28.1   Purpose

Associates a text description with a port or channel.

1.28.2   Command Mode

• ATM DS-3 configuration
• ATM OC configuration
• DS-0 group configuration
• DS-1 configuration
• DS-3 configuration
• E1 configuration
• E3 configuration
• interface configuration
• port configuration
• STM-1 configuration

1.28.3   Syntax Description

1.28.4   Default

No description is associated with a port or channel.

1.28.5   Usage Guidelines

Use the description command to associate a text description with a port or channel. This text appears in the output of the show port detail command (in any mode).

Use the no or default form of this command to delete the existing description. Because there can be only one description for a port or channel; when you use the no or default form of this command, it is not necessary to include the text argument. To change a description, create a new one; it overwrites the existing one.

1.28.6   Examples

The following example shows how to associate a description with channelized OC-12 port 1 in slot 4:

[local]Redback(config)#port channelized-oc12 4/1

[local]Redback(config-port)#description channelized OC-12 in New York

1.29   description (snmp alarm)

1.29.1   Purpose

Describes the alarm model.

1.29.2   Command Mode

SNMP alarm model configuration

1.29.3   Syntax Description

1.29.4   Default

None

1.29.5   Usage Guidelines

Use the description command to describe the alarm model you are configuring.

Use the no form to remove the description of the alarm model.

1.29.6   Examples

The following example shows how to configure the description of an alarm model to LinkUp Administrative.

[local]jazz#config
[local]jazz(config)#snmp alarm model 1 state major
[local]jazz(config-snmp-alarmmodel)#description LinkUp Administrative
[local]jazz(config-snmp-alarmmodel)#exit

1.30   description (SSE)

1.30.1   Command Mode

SSE group configuration

1.30.2   Syntax Description

1.30.3   Default

No description is associated with the SSE group.

1.30.4   Usage Guidelines

Associates a text description with an SSE group. Only one description can be associated with an SSE group. To revise a description, create a new one, and the old one is overwritten.

Use the no or default form of this command to delete the existing description.

1.30.5   Examples

[local]Redback(config)#sse group sse_group_1 network-redundant
[local]Redback(config-SE-group)#description SSE group 1

1.31   description (tunnel)

1.31.1   Purpose

Associates textual information with the tunnel.

1.31.2   Command Mode

tunnel configuration

1.31.3   Syntax Description

1.31.4   Default

No description is associated with the tunnel.

1.31.5   Usage Guidelines

Use the description command to associate textual information with the tunnel. The description appears in the output of the show configuration command with the tunnel keyword (in any mode).

Use the no form of this command to delete the existing description. Because there can be only one description for a tunnel, when you use the no form of this command, it is not necessary to include the text argument.

To change a description, create a new one; it overwrites the existing one.

1.31.6   Examples

The following example shows how to select (or create) a GRE tunnel, and then associate a text description with it:

[local]Redback(config)#tunnel gre HartfordTnl

[local]Redback(config-tunnel)#description Corporate offices in Hartford

The following example shows how to change the description created in the previous example:

[local]Redback(config-tunnel)#description Branch offices in Hartford

The following example shows how to delete an existing description:

[local]Redback(config-tunnel)#no description

1.32   description (VPLS profiles)

1.32.1   Purpose

Associates a description with a neighbor.

1.32.2   Command Mode

VPLS profile neighbor configuration

1.32.3   Syntax Description

1.32.4   Default

None

1.32.5   Usage Guidelines

Use the description command to associate a description with a neighbor. This command does not affect the neighbor, but is used only as a note in the configuration.

Note:  

The neighbor is identified by the IP address of the remote provider edge (PE) device.

Use the no form of this command to remove a description from the neighbor. Because there can be only one description for a neighbor, when you use the no form of this command, it is not necessary to include the text argument.

1.32.6   Examples

The following example provides the description, test-peer, for the neighbor, 10.10.10.1:

[local]Redback#config

[local]Redback(config)#vpls profile foo

[local]Redback(config-vpls-profile)#neighbor 10.10.10.1

[local]Redback(config-vpls-profile-neighbor)#description test-peer

[local]Redback(config-vpls-profile-neighbor)#

1.33   destination

1.33.1   Purpose

Configures the Network Address Translation (NAT) policy or its class to use the specified IP address in destination IP address translation or destination NAT (DNAT).

1.33.2   Command Mode

• NAT policy configuration
• NAT policy class configuration

1.33.3   Syntax Description

1.33.4   Default

No predefined IP address is configured as a destination IP address.

1.33.5   Usage Guidelines

Use the destination command to configure the NAT policy or its class to use the specified IP address in DNAT. DNAT replaces the original destination IP addresses of all packets or the packets of a specific class with a predefined IP address.

When a destination IP address is configured for a given class, the SmartEdge router applies this predefined IP address to all packets of the class.

You can enable DNAT with or without having to perform NAT.

Note:  

If you configure DNAT with NAT, the context name specified in the destination command must be the same as the context name specified in the pool command.

Configuring DNAT without NAT requires that you configure the destination command with the ignore command.

Use the destinationip-addrr context-name construct to specify that the configured destination IP address resides within the specified context. Without the name of the context specified, the configured destination IP address is assumed to be either in the context in which the NAT pool is defined or, if no NAT pool is defined, in the context in which the NAT policy is defined.

1.33.6   Examples

The following example shows how to configure DNAT with NAT. A predefined destination address is configured for the NAT-CLASS1 class within the NAT policy NAT-POLICY. For all packets from class NAT-CLASS1, the destination address of each packet is replaced by 64.233.267.100 so that all packets from class NAT-CLASS1 are forwarded to that address. On the return path, a reverse translation from 64.233.267.100 to the original destination address is performed so that the returning traffic appears to be sent from the original destination address:

[local]Redback(config-ctx)#nat policy NAT-POLICY

!Default class

[local]Redback(config-policy-nat)#pool NAT-POOL-DEFAULT local

!Named classes

[local]Redback(config-policy-nat)#access-group NAT-ACL

[local]Redback(config-policy-acl)#class NAT-CLASS1

[local]Redback(config-policy-acl-class)#pool NAT-POOL1 local

[local]Redback(config-policy-acl-class)#destination 64.233.167.100

The following example shows how to configure DNAT without NAT. A predefined destination address is configured for the NAT-CLASS2 class within the NAT policy NAT-POLICY. For the NAT-CLASS2 class within the NAT policy NAT-POLICY, the destination address of each packet is replaced by 64.233.267.100 so that all packets from class NAT-CLASS2 are forwarded to that address. In this example, the source address is not translated:

[local]Redback(config-ctx)#nat policy NAT-POLICY

!Default class

[local]Redback(config-policy-nat)#pool NAT-POOL-DEFAULT local

!Named classes

[local]Redback(config-policy-nat)#access-group NAT-ACL

[local]Redback(config-policy-acl)#class NAT-CLASS2

[local]Redback(config-policy-acl-class)#ignore

[local]Redback(config-policy-acl-class)#destination 64.233.167.100

1.34   detection-multiplier

1.34.1   Purpose

Specifies the detection multiplier value.

1.34.2   Command Mode

• BFD interface configuration
• BFD neighbor configuration

1.34.3   Syntax Description

1.34.4   Default

The default detection multiplier value is 3.

1.34.5   Usage Guidelines

Use the detection-multiplier command to specify the detection multiplier value.

The negotiated minimum transmit interval (the minimum desired transmit interval agreed upon by both peers) is multiplied by the detection multiplier value to provide the detection time for the transmitting system in asynchronous mode. The detection time is the time it takes to declare a neighbor as down. For example, if the minimum desired transmit interval was negotiated at 10 ms and the detection multiplier is set to 3, then the detection time is 30 ms. Using the detection multiplier adds robustness to Bidirectional Forwarding Detection (BFD) by allowing the system to not bring down a neighbor if only one BFD packet is missed.

Use the no or default form of this command to return the detection multiplier value to 3.

1.34.6   Examples

The following example sets the detection multiplier value on the interface, to_foo, to 7:

[local]Redback(config)#context local

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

[local]Redback(config-bfd)#interface to_foo

[local]Redback(config-bfd-if)#detection-multiplier 7

[local]Redback(config-bfd-if)#

1.35   dhcp max-addrs

1.35.1   Purpose

Indicates that associated hosts are to use Dynamic Host Configuration Protocol (DHCP) to dynamically acquire address information for the subscriber’s circuit, and sets a maximum number of IP addresses that the SmartEdge router expects the external DHCP server to assign to hosts associated with the circuit.

1.35.2   Command Mode

subscriber configuration

1.35.3   Syntax Description

1.35.4   Default

None

1.35.5   Usage Guidelines

Use the dhcp max-addrs command to indicate that associated hosts are to use DHCP to dynamically acquire address information for the subscriber’s circuit, and to set a maximum number of IP addresses that the SmartEdge router expects the external DHCP server to assign to hosts associated with the circuit.

For non-CLIPS subscribers, the SmartEdge router deducts the value of the max-sub-addrs argument from the value for the max-dhcp-addrs argument that you configured for a DHCP proxy or DHCP relay interface, using the dhcp proxy or dhcp relay commands (in interface configuration mode), available at the time a subscriber is bound to a circuit. When the value for the max-dhcp-addrs argument for a DHCP proxy or DHCP relay interface reaches 0, that interface is no longer available for subscriber bindings.

For dynamic CLIPS subscribers, you must configure the subscriber record or profile with no IP address and specify 1 as the value for the max-sub-addrs argument; for information about CLIPS, see Configuring CLIPS.

Use the no form of this command to disable the use of DHCP for the subscriber’s circuit.

Note:  

If you configure a subscriber record with a dhcp max-addrs command and with one or more static IP host addresses, using the ip address command (in interface configuration mode), the static IP addresses always take precedence; the associated circuit is bound to an interface on the basis of the static IP addresses. If you configure the record with a dhcp max-addrs command, and you do not configure any static addresses for it, the associated circuit is bound to the first available interface with capacity for this subscriber.

1.35.6   Examples

The following example configures the subscriber, dhcp-test, to expect a total of 8 IP addresses that can be assigned at any time:

[local]Redback(config-ctx)#subscriber name dhcp-test

[local]Redback(config-sub)#dhcp max-addrs 8

1.36   dhcp proxy

1.36.1   Purpose

Enables this interface to act as proxy between subscribers and an external Dynamic Host Configuration Protocol (DHCP) server, and access DHCP giaddr configuration mode.

1.36.2   Command Mode

interface configuration

1.36.3   Syntax Description

1.36.4   Default

DHCP proxy is disabled.

1.36.5   Usage Guidelines

Use the dhcp proxy command to enable this interface to act as a proxy between subscribers and an external DHCP server, and access DHCP giaddr configuration mode.

When you enable DHCP proxy, the interface relays all DHCP packets, including the release and renewal of IP addresses for subscriber sessions, between the DHCP server and the subscriber. To the subscriber, the SmartEdge router appears to be the DHCP server.

The SmartEdge router uses the value for the max-dhcp-addrs argument to load balance between IP addresses from multiple pools. When you configure the SmartEdge router for subscriber DHCP proxy, the value of the max-dhcp-addrs argument indicates the total number of subscriber requests that will be forwarded on the interface.

The SmartEdge router deducts the max-sub-addrs value for the dhcp max-addrs command (in subscriber configuration mode) from the current value for max-dhcp-addrs argument for the DHCP proxy interface at the time a subscriber is bound to a circuit using that interface. When the value of max-dhcp-addrs for a DHCP proxy interface reaches 0, that interface is no longer available for subscriber bindings.

Use the no form of this command to disable DHCP proxy on the interface.

Note:  

You can configure an interface to act as either a DHCP relay or a DHCP proxy; the dhcp relay and dhcp proxy commands are mutually exclusive.

Note:  

For the dhcp proxy command to take effect, you must configure an external DCHP server, using the dhcp relay server command in the context in which the interface is configured.

1.36.6   Examples

The following example enables the proxy1 interface to act as a DHCP proxy for the DHCP server at IP address, 10.30.40.50:

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

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

[local]Redback(config-ctx)#interface proxy1

[local]Redback(config-if)#ip address 10.1.2.3 255.255.255.0

[local]Redback(config-if)#dhcp proxy 253

1.37   dhcp relay

1.37.1   Purpose

Enables this interface to relay Dynamic Host Configuration Protocol (DHCP) messages to an external DHCP server, and access DHCP giaddr configuration mode.

1.37.2   Command Mode

interface configuration

1.37.3   Syntax Description

1.37.4   Default

DHCP relay is disabled.

1.37.5   Usage Guidelines

Use the dhcp relay command to enable this interface to relay DHCP messages to an external DHCP server, and access DHCP giaddr configuration mode.

The SmartEdge router uses the value for the max-dhcp-addrs argument to load balance between IP addresses from multiple pools. When you configure the SmartEdge router for subscriber DHCP relay, the value of the max-dhcp-addrs argument indicates the total number of subscriber requests that can be forwarded on the interface.

The value of the max-sub-addrs argument for the dhcp max-addrs command (in subscriber configuration mode) is deducted from the max-dhcp-addrs value configured for a DHCP relay interface available at the time a subscriber is bound to a circuit on that interface. When the value of max-dhcp-addrs for a DHCP relay interface reaches 0, that interface is no longer available for subscriber bindings.

Note:  

You can configure an interface to act as either a DHCP relay or a DHCP proxy; the dhcp relay and dhcp proxy commands are mutually exclusive.

Note:  

For the dhcp relay command to take effect, you must configure an external DCHP server, using the dhcp relay server command in the context in which the interface is configured.

Use the no form of this command to disable DHCP relay on the interface.

1.37.6   Examples

The following example enables DHCP relay on interface eth1, which is configured with a total of 253 IP addresses that can be allocated by the DHCP server at any time from the 10.1.1.0 subnet:

[local]Redback(config-ctx)#interface eth1

[local]Redback(config-if)#ip address 10.1.1.0 255.255.255.0

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

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

1.38   dhcp relay option

1.38.1   Purpose

Enables the sending of Dynamic Host Configuration Protocol (DHCP) options in DHCP packets relayed by the interfaces in the specified context.

1.38.2   Command Mode

context configuration

1.38.3   Syntax Description

1.38.4   Default

DHCP options are not sent.

1.38.5   Usage Guidelines

Use the dhcp relay option command to enable the sending of DHCP options in all DHCP packets that are relayed by the interfaces in the specified context.

On some networks, DHCP is used to dynamically configure IP address information for subscriber hosts. The SmartEdge router can act as a relay or as a proxy for DHCP servers. DHCP is typically used with RFC 1483 bridge-encapsulated circuits, as opposed to Point-to-Point Protocol (PPP) circuits.

The SmartEdge router can use DHCP relay options to help track DHCP requests. Some options can also enhance the DHCP server’s function. The DHCP relay options are described in RFC 3046, DHCP Relay Agent Information Option.

In order for relay options to take effect, you must enable DHCP relay for the context, using the dhcp relay server command (in context configuration mode), and for an interface, using the dhcp relay or dhcp proxy command (in interface configuration mode). You must also configure subscriber records, using the dhcp max-addrs command (in subscriber configuration mode) to indicate that associated hosts are to use DHCP relay to dynamically acquire address information.

Use the no form of this command to disable the sending of DHCP options.

1.38.6   Examples

The following example enables the sending of DHCP relay options:

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

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

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

The following example prepends the system hostname, SE800, to the agent circuit id field of DHCP option 82 and, by default, uses the colon (:) to separate the hostname from the circuit id field:

[local]Redback(config)#server hostname SE800

[local]Redback(config)#context local

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

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

[local]Redback(config-ctx)#dhcp relay option hostname

The DHCP server’s lease log for this configuration would be similar to the following example:

lease 120.1.3.191 {

  starts 2 2005/11/08 10:05:21;

  ends 2 2005/11/08 10:35:21;

  binding state active

  netx binding state free

  hardware ethernet 00:dd:00:00:00:1e;

  uid “\001\006\000\335\000\000\000\036”;

option agent.circuit-id “SE800:1/4 vpi-vci 0 103”;

}

1.39   dhcp relay server

1.39.1   Purpose

Configures an external Dynamic Host Configuration Protocol (DHCP) server and enters DHCP relay server configuration mode.

1.39.2   Command Mode

context configuration

1.39.3   Syntax Description

1.39.4   Default

Disabled

1.39.5   Usage Guidelines

Use the dhcp relay server command to configure an external DHCP server and enter DHCP relay server configuration mode. You can configure up to five external DHCP servers in each context.

If you have configured Remote Authentication Dial-In User Service (RADIUS) authentication, the SmartEdge router sends an accounting record to RADIUS every time DCHP assigns or releases an IP address.

Note:  

For the dhcp relay server command to take effect, you must also enable DHCP relay or DHCP proxy on an interface in the same context, using the dhcp proxy or dhcp relay command (in interface configuration mode).

To indicate that associated hosts are to use DHCP relay to dynamically acquire address information, you must configure the subscriber default profile, a named profile, or subscriber records with the dhcp max-addrs command (in subscriber configuration mode).

Use the no form of this command to disable the DHCP server.

1.39.6   Examples

The following example configures an external DHCP server at IP address, 10.30.40.50, and enters DHCP relay server configuration mode:

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

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

1.40   dhcp relay server retries

1.40.1   Purpose

Specifies the number of attempts and the interval to wait for each attempt when trying to reach an external Dynamic Host Configuration Protocol (DHCP) server before it is marked unreachable.

1.40.2   Command Mode

context configuration

1.40.3   Syntax Description

1.40.4   Default

Up to three attempts are made to reach a DHCP server, with a wait interval of 30 seconds for each attempt.

1.40.5   Usage Guidelines

Use the dhcp relay server retries command to specify the number of attempts and the interval to wait for each attempt when trying to reach an external DHCP server before it is marked unreachable.

If the interval expires without receiving a reply from the DHCP server, another DHCP request is sent to the DHCP server until the maximum consecutive number of attempts has been reached. If the interval expires after the last attempt without reaching the DHCP server, then the DHCP server is marked unreachable.

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

1.40.6   Examples

The following example configures the SmartEdge router to make up to 5 attempts to reach a DHCP server, with a wait interval of 15 seconds for each attempt:

[local]Redback(config-ctx)#dhcp relay server retries 5 timeout 15

[local]Redback(config-ctx)#

1.41   dhcp relay suppress-nak

1.41.1   Purpose

Disables the sending of a DHCPNAK message when the SmartEdge router receives a DHCPREQUEST message for which it does not have an entry.

1.41.2   Command Mode

context configuration

1.41.3   Syntax Description

This command has no keywords or arguments.

1.41.4   Default

A DHCPNAK message is always sent.

1.41.5   Usage Guidelines

Use the dhcp relay suppress-nak command to disable the sending of a DHCPNAK message when the SmartEdge router receives a DHCPREQUEST message for which it does not have an entry. In this case, the request is dropped.

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

1.41.6   Examples

The following example disables the sending of a DHCPNAK message:

[local]Redback(config-ctx)#dhcp relay suppress-nak

1.42   dhcp server

1.42.1   Purpose

Enables this interface for internal Dynamic Host Configuration Protocol (DHCP) server support and assigns the IP address to be used for this support.

1.42.2   Command Mode

interface configuration

1.42.3   Syntax Description

1.42.4   Default

No internal DHCP servers are created.

1.42.5   Usage Guidelines

Use the dhcp server command to enable this interface for internal DHCP server support and assign the IP address to be used for this support.

For information about the context command (in global configuration mode), the interface command (in context configuration mode), and the ip address command (in interface configuration mode), see Configuring Contexts and Interfaces.

Note:  

The actual choice of an IP address for the internal DHCP server is made by authentication, authorization, and accounting (AAA), subject to any static mappings, subnets, and ranges that you have configured for the server.

Note:  

IP pools on an interface can be used to provide addresses for the DHCP server. If there is no range of values specified on a DHCP subnet, the DHCP server takes the IP addresses from the IP pool defined in the interface command. This IP pool can also be used by the DHCP server and PPP subscribers on the same interface.

Use the no form of this command to delete the internal DHCP server.

1.42.6   Examples

The following example creates an internal DHCP server using the secondary IP address for the dhcp-if interface in the dhcp context:

[local]Redback(config)#context dhcp

[local]Redback(config-ctx)#interface dhcp-if multibind

[local]Redback(config-if)#ip address 12.1.1.1/24

[local]Redback(config-if)#ip address 13.1.1.1/24 secondary

[local]Redback(config-if)#dhcp server 13.1.1.1

1.43   dhcp server policy

1.43.1   Purpose

Enables internal Dynamic Host Configuration Protocol (DHCP) server functions in this context and accesses DHCP server configuration mode.

1.43.2   Command Mode

context configuration

1.43.3   Syntax Description

This command has no keywords or arguments.

1.43.4   Default

Internal DHCP server functions are disabled for this context.

1.43.5   Usage Guidelines

Use the dhcp server policy command to enable internal DHCP server functions in this context and access DHCP server configuration mode.

Note:  

IP pools on an interface can be used to provide addresses for the DHCP server. If there is no range of values specified on a DHCP subnet, the DHCP server takes the IP addresses from the IP pool defined in the interface command. This IP pool can also be used by the DHCP server and PPP subscribers on the same interface.

Use the no form of this command to disable internal DHCP server functions.

1.43.6   Examples

The following example enables DHCP server functions in the dhcp context:

[local]Redback(config)#context dhcp

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

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

1.44   dhcpv6 server (DHCPv6 Policy)

1.44.1   Purpose

Enables a DHCPv6 server policy and accesses DHCPv6 server policy configuration mode.

1.44.2   Command Mode

context configuration

1.44.3   Syntax Description

This command has no keywords or arguments.