Chapter 10

1:
Is it possible to specify the backup load command on subinterfaces? Why or why not?
A1:
Answer: No. Because load is calculated on a per-interface basis, the backup load command cannot be configured on subinterfaces.
2:
What two circumstances can trigger dial backup?
A2:
Answer:

Failure of the primary link

Traffic on the primary link reaching or exceeding the set threshold
3:
What is a drawback of using physical interfaces for backup?
A3:
Answer: Physical interfaces are placed in standby mode when they are idle and cannot be used to connect to other sites. Backup using dialer profiles overcomes this shortcoming.
4:
Which interfaces can be used as backup interfaces?
A4:
Answer:

Serial interfaces

ISDN interfaces

Asynchronous interfaces

Dialer pools
5:
What is one reason that ISDN interfaces are used mostly for backup interfaces instead of primary interfaces?
A5:
Answer: Cost is the main reason that ISDN interfaces are used primarily in a backup role.
6:
Which command specifies interesting traffic to bring up an ISDN interface?
A6:
Answer: The dialer-list command specifies interesting traffic that brings up an ISDN interface.
7:
Which command specifies the amount of time before a backup interface is activated in case of a primary link failure?
A7:
Answer: The backup delay command allows you to specify the amount of time before the backup interface is activated.
8:
Which command specifies the load threshold at which a backup interface is brought up in case of load sharing?
A8:
Answer: The backup load command allows you to specify the load threshold at which the backup interface is brought up.
9:
What is a possible alternative to dial backup?
A9:
Answer: Floating static routes
10:
Which commands associate a virtual dialer interface with a physical interface when you configure dialer profiles?
A10:
Answer: The dialer pool command on the dialer interface and the dialer pool-member command on the physical interface.

[ LiB ]

1:	Is it possible to specify the backup load command on subinterfaces? Why or why not?
A1:	Answer: No. Because load is calculated on a per-interface basis, the backup load command cannot be configured on subinterfaces.
2:	What two circumstances can trigger dial backup?
A2:	Answer: Failure of the primary link Traffic on the primary link reaching or exceeding the set threshold
3:	What is a drawback of using physical interfaces for backup?
A3:	Answer: Physical interfaces are placed in standby mode when they are idle and cannot be used to connect to other sites. Backup using dialer profiles overcomes this shortcoming.
4:	Which interfaces can be used as backup interfaces?
A4:	Answer: Serial interfaces ISDN interfaces Asynchronous interfaces Dialer pools
5:	What is one reason that ISDN interfaces are used mostly for backup interfaces instead of primary interfaces?
A5:	Answer: Cost is the main reason that ISDN interfaces are used primarily in a backup role.
6:	Which command specifies interesting traffic to bring up an ISDN interface?
A6:	Answer: The dialer-list command specifies interesting traffic that brings up an ISDN interface.
7:	Which command specifies the amount of time before a backup interface is activated in case of a primary link failure?
A7:	Answer: The backup delay command allows you to specify the amount of time before the backup interface is activated.
8:	Which command specifies the load threshold at which a backup interface is brought up in case of load sharing?
A8:	Answer: The backup load command allows you to specify the load threshold at which the backup interface is brought up.
9:	What is a possible alternative to dial backup?
A9:	Answer: Floating static routes
10:	Which commands associate a virtual dialer interface with a physical interface when you configure dialer profiles?
A10:	Answer: The dialer pool command on the dialer interface and the dialer pool-member command on the physical interface.