Table Of Contents

Dialer Profiles Backup Commands

backup interface dialer

backup load

Dialer Profiles Backup Commands

---

This chapter describes the commands used to configure Dialer Profiles for backing up physical interfaces.

Dialer interfaces can be configured as the logical intermediary between one or more physical interfaces and another physical interface that is to function as backup.

Dialer interfaces can be configured to use a specific dialing pool; in turn physical interfaces can be configured to belong to the same dialing pool.

The advantage of using Dialer Profiles for backing up physical interfaces is that it enables ISDN B channels to be used independently, which allows a single BRI to back up two serial interfaces.

For dialer profiles backup configuration tasks and examples, refer to the "Configuring Dial Backup with Dialer Profiles" chapter in the Configuration Fundamentals Configuration Guide.

backup interface dialer

To configure a dialer interface as a secondary or dial backup, use the backup interface dialer interface configuration command. To disable this feature, use the no form of this command.

backup interface dialer number
no backup interface dialer number

Syntax Description

number

Dialer interface number to use as the backup interface.

Default

Disabled

Command Mode

Interface configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 11.2.

Multiple dialer interfaces can use the same dialer pool, which might have a single ISDN interface as a member. Thus, that ISDN interface can back up different serial interfaces and can make calls to different sites.

Example

The following example shows the configuration of a site that backs up two leased lines using one BRI. Two dialer interfaces are defined. Each serial (leased line) interface is configured to use one of the dialer interfaces as a backup. Both of the dialer interfaces use dialer pool 1, which has BRI 0 as a member. Thus, BRI 0 can back up two different serial interfaces and can make calls to two different sites.

interface dialer0

 ip unnumbered loopback0

 encapsulation ppp

 dialer remote-name Remote0

 dialer pool 1

 dialer string 5551212

 dialer-group 1

interface dialer1

 ip unnumbered loopback0

 encapsulation ppp

 dialer remote-name Remote1

 dialer pool 1

 dialer string 5551234

 dialer-group 1

interface bri 0

 encapsulation PPP

 dialer pool-member 1

 ppp authentication chap

interface serial 0

 ip unnumbered loopback0

 backup interface dialer 0

 backup delay 5 10

interface serial 1

 ip unnumbered loopback0

 backup interface dialer1

 backup delay 5 10

backup load

To set a traffic load threshold for dial backup service, use the backup load interface configuration command. To return to the default value, use the no form of this command.

backup load {enable-threshold | never} {disable-load | never}
no backup load {enable-threshold | never} {disable-load | never}

Syntax Description

enable-threshold	Percentage of the primary line's available bandwidth that the traffic load must exceed to enable dial backup.
disable-load	Percentage of the primary line's available bandwidth that the traffic load must be less than to disable dial backup.
never	Sets the secondary line never to be activated due to traffic load.

Default

No threshold is predefined.

Command Mode

Interface configuration

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0.

When the transmitted or received load on the primary line is greater than the value assigned to the enable-threshold argument, the secondary line is enabled.

The secondary line is disabled when one of the following conditions occurs:

•The transmitted load on the primary line plus the transmitted load on the secondary line is less than the value entered for the disable-load argument.

•The received load on the primary line plus the received load on the secondary line is less than the value entered for the disable-load argument.

If the never keyword is used instead of an enable-threshold value, the secondary line is never activated because of traffic load. If the never keyword is used instead of a disable-load argument, the secondary line is never activated because of traffic load.

Example

The following example sets the traffic load threshold to 60 percent of the primary line serial 0. When that load is exceeded, the secondary line is activated, and will not be deactivated until the combined load is less than 5 percent of the primary bandwidth.

interface serial 0

 backup load 60 5

 backup interface serial 1