|
|
For information about preparations for configuring Dialer Profiles, see the "Deciding and Preparing to Configure DDR" chapter of this manual.
The Dialer Profiles feature is contrasted with legacy DDR. For information about legacy DDR, see the other chapters in the "Dial-on-Demand Routing" part of this manual.
For information about dial backup using Dialer Profiles, see the "Configuring Backup with Dialer Profiles" chapter of this manual.
For a complete description of the Dialer Profiles commands in this chapter, refer to the "Peer-to-Peer DDR with Dialer Profiles Commands" chapter of the Dial Solutions Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Dialer Profiles supports most routed protocols. However, Frame Relay, ISO CLNS, and LAPB are not supported.
Dialer profiles allow the configuration of physical interfaces to be separated from the logical configuration required for a call, and they also allow the logical and physical configurations to be bound together dynamically on a per-call basis.
A dialer profile consists of the following elements:
All calls going to or from the same destination subnetwork use the same dialer profile.
A dialer interface configuration includes all settings needed to reach a specific destination subnetwork (and any networks reached through it). Multiple dial strings can be specified for the same dialer interface, each dial string being associated with a different dialer map-class. The dialer map-class defines all the characteristics for any call to the specified dial string. For example, the map-class for one destination might specify a 56-kbps ISDN speed; the map-class for a different destination might specify a 64-kbps ISDN speed.
Each dialer interface uses a dialer pool, a pool of physical interfaces ordered on the basis of the priority assigned to each physical interface. A physical interface can belong to multiple dialer pools, contention being resolved by priority. ISDN BRI and PRI interfaces can set a limit on the minimum and maximum number of B channels reserved by any dialer pools. A channel reserved by a dialer pool remains idle until traffic is directed to the pool.
Figure 115 shows a typical application of dialer profiles. Router A has dialer interface 1 for dial-on-demand routing with subnetwork 1.1.1.0, and dialer interface 2 for dial-on-demand routing with subnetwork 2.2.2.0. The IP address for dialer interface 1 is its address as a node in network 1.1.1.0; at the same time, that IP address serves as the IP address of the physical interfaces used by the dialer interface 1. Similarly, the IP address for dialer interface 2 is its address as a node in network 2.2.2.0.
Figure 116 illustrates the relations among the concepts of dialer interface, dialer pool, and physical interfaces. Dialer interface 0 uses dialer pool 2. Physical interface BRI 1 belongs to dialer pool 2 and has a specific priority in the pool. Physical interface BRI 2 also belongs to dialer pool 2. Because contention is resolved on the basis of priority-levels of the physical interfaces in the pool, BRI 1 and BRI 2 have to be assigned different priorities in the pool. Perhaps BRI 1 is assigned priority 100 and BRI 2 is assigned priority 50 in dialer pool 2 (a priority of 50 is higher than a priority of 100). BRI 2 has a higher priority in the pool and its calls will be placed first.
To configure dialer profiles, perform the tasks in the following section:
The following tasks can be configured whether you use legacy DDR or Dialer Profiles. Perform these tasks as needed for your network:
See the "Dialer Profiles Configuration Examples" section for comprehensive configuration examples.
To configure a dialer profile, perform the tasks in the following sections. The first and last are required. Map-class configuration is optional.
Any number of dialer interfaces can be created for a router. Each dialer interface is the complete configuration for a destination subnetwork and any networks reached through it. The router on the destination subnetwork sends traffic on to the appropriate shadowed networks.
To configure a dialer interface, complete the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Create a dialer interface. | interface dialer number |
| Step 2 Specify the IP address and mask of the dialer interface as a node in the destination network to be called. | ip address address mask |
| Step 3 Specify PPP encapsulation. | encapsulation ppp |
| Step 4 Specify the remote router CHAP authentication name. | dialer remote-name name |
| Step 5 Specify the remote destination to call and the map class that defines characteristics for calls to this destination. | dialer string string class class-name |
| Step 6 Specify the dialing pool to use for calls to this destination. | dialer pool number |
| Step 7 Assign the dialer interface to a dialer group. | dialer-group number |
| Step 8 Specify an access list by list number or by protocol and list number to define the "interesting" packets that can trigger a call. | dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number} |
Map class configuration is optional but allows you to specify different characteristics for different types of calls on a per-call-destination basis. For example, you can specify higher priority and a lower wait-for-carrier time for an ISDN-calls map class than for a modem-calls map class. You can also specify a different speed for some ISDN calls than for other ISDN calls.
A specific map class is tied to a specific call destination by the use of the map-class name in the dialer-string command with the class keyword.
To specify a map class and define its characteristics, complete the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
| Specify a map class and enter map-class configuration mode. | map-class dialer class-name |
| Specify the fast idle timer value. | dialer fast-idle seconds |
| Specify the idle time before the calls in this map class are disconnected. | dialer idle-timeout seconds |
| Specify the length of time to wait for a carrier when dialing out to the dial string associated with the map class. | dialer wait-for-carrier-time seconds |
| For ISDN only, specify the bit rate used on the B channel associated with a specified map class or specify that an ISDN semipermanent connection is to be used for calls associated with this map. | dialer isdn [speed speed] [spc] |
To configure a physical interface, complete the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the physical interface. | interface type number |
| Step 2 Enable PPP encapsulation. | encapsulation ppp |
| Step 3 Specify PPP CHAP authentication, if you also want to receive calls on this interface. | ppp authentication chap |
| Step 4 Put the interface in a dialing pool and, optionally, assign the interface a priority. For ISDN interfaces, you can also optionally specify the minimum number of channels reserved and maximum number of channels that can be for this dialing pool. | dialer pool-member number [priority priority] dialer pool-member number [priority priority] [min-link minimum] [max-link maximum]1 |
| Step 5 (Optional) Repeat Step 4 if you want to put the interface in additional dialing pools. | dialer pool-member number [priority priority] or dialer pool-member number [priority priority] [min-link minimum] [max-link maximum] |
Repeat this procedure for additional physical interfaces that you want to use with dialer profiles.
Both legacy DDR and Dialer Profiles support the following routed protocols: AppleTalk, Banyan VINES, DECnet, IP, Novell IPX, and XNS.
To configure Dialer Profiles for a routed protocol, perform the tasks in the relevant section:
To configure Dialer Profiles for AppleTalk, you specify AppleTalk access lists and then configure the dialer interface for Dialer Profiles, defining the dialer list to be used. Use the dialer-list protocol command to define permit or deny conditions for the entire protocol; for a finer granularity, use the dialer-list protocol command with the list keyword. See the "Configure a Dialer Interface" section earlier in this chapter for more information about defining dialer lists.
To configure DDR for Banyan VINES, perform one of the following tasks in global configuration mode:
| Task | Command |
|---|---|
| Specify a VINES standard access list. or Specify a VINES extended access list. | vines access-list access-list-number {permit | deny} source source-mask1
vines access-list access-list-number {permit | deny} source source-mask [destination] [destination-mask] |
After you specify VINES standard or extended access lists, configure the dialer interface for Dialer Profiles, defining the dialer list to be used. Use the dialer-list protocol command to define permit or deny conditions for the entire protocol; for a finer granularity, use the dialer-list protocol command with the list keyword. See the "Configure a Dialer Interface" section earlier in this chapter for more information about defining dialer lists.
To configure DDR for DECnet, perform one of the following tasks in global configuration mode: After you specify DECnet standard or extended access lists, configure the dialer interface for Dialer Profiles, defining the dialer list to be used. Use the dialer-list protocol command to define permit or deny conditions for the entire protocol; for a finer granularity, use the dialer-list protocol command with the list keyword. See the "Configure a Dialer Interface" section earlier in this chapter for more information about defining dialer lists.
| Task | Command |
|---|---|
| Specify a DECnet standard access list. or Specify a DECnet extended access list. | access-list access-list-number {permit | deny} source source-mask1
access-list access-list-number {permit | deny} source source-mask [destination] [destination-mask] |
To configure DDR for IP, perform one of the following tasks in global configuration mode:
| Task | Command |
|---|---|
| Specify an IP standard access list. or Specify an IP extended access list. | access-list access-list-number {deny | permit} source [source-mask] access-list access-list-number {deny | permit} protocol source source-mask destination destination-mask [operator operand] |
You can now also use simplified IP access lists that use the abbreviation any instead of the numeric forms of source and destination addresses and masks. Other forms of IP access lists are also available. For more information, see the "IP Services Commands" chapter in the Network Protocols Command Reference, Part 1.
To use dynamic routing where multiple remote sites communicate with each other through a central site, you might need to disable the IP split horizon feature. Split horizon applies to RIP, IGRP, and Enhanced IGRP. Depending on which routing protocol is configured, see the chapter "Configuring RIP," "Configuring IGRP," or "Configuring Enhanced IGRP." See the "Configuring IP Routing Protocols" chapter in the Network Protocols Configuration Guide, Part 1 for more information.
On DDR links for Novell IPX, the link may come up often even when all client sessions are idle because the server sends watchdog or keepalive packets to all the clients approximately every 5 minutes. You can configure a local router or access server to idle out the DDR link and respond to the watchdog packets on behalf of the clients.
To modify the Dialer Profiles dialer interface configuration for Novell IPX, perform the following tasks in interface configuration mode:
| Task | Command |
|---|---|
| Disable fast switching for IPX. | no ipx route-cache |
| Enable IPX watchdog spoofing. or Enable SPX keepalive spoofing. | ipx watchdog-spoof ipx spx-spoof |
| Set the idle time after which SPX keepalive spoofing begins. | ipx spx-idle-time delay-in-seconds |
To configure XNS for DDR, perform one of the following tasks in global configuration mode:
| Task | Command |
|---|---|
| Specify a standard XNS access list. or Specify an extended XNS access list. | access-list access-list-number {deny | permit} source-network[.source-address [source-address-mask]] [destination-network[.destination-address [destination-address-mask]]]
access-list access-list-number {deny | permit} protocol [source-network[.source-host |
After you specify an XNS access list, configure the dialer interface for Dialer Profiles, defining the dialer list to be used. Use the dialer-list protocol command to define permit or deny conditions for the entire protocol; for a finer granularity, use the dialer-list protocol command with the list keyword. See the "Configure a Dialer Interface" section earlier in this chapter for more information about defining dialer lists.
The Cisco IOS software supports transparent bridging over both legacy DDR and Dialer Profiles, and it provides you some flexibility in controlling access and configuring the interface.
To configure Dialer Profiles for bridging, complete the tasks in the following sections:
IP packets are routed by default unless they are explicitly bridged; all others are bridged by default unless they are explicitly routed. To bridge IP packets, complete the following task in global configuration mode:
| Task | Command |
|---|---|
| Disable IP routing. | no ip routing |
If you choose not to bridge another protocol, use the relevant command to enable routing of that protocol. For more information about tasks and commands, refer to the relevant protocol chapter in either the Network Protocols Configuration Guide, Part 1 or the Network Protocols Configuration Guide, Part 2.
You must specify the type of spanning tree bridging protocol to use and also identify a bridge group. To specify the spanning tree protocol and a bridge group number, complete the following task in global configuration mode:
| Task | Command |
|---|---|
| Define the type of spanning tree protocol and identify a bridge group. | bridge bridge-group protocol {ieee | dec} |
The bridge-group number is used when you configure the interface and assign it to a bridge group. Packets are bridged only among members of the same bridge group.
You can control access by defining any transparent bridge packet as interesting, or you can use the finer granularity of controlling access by Ethernet type codes. To control access for DDR bridging, complete one of the following tasks in global configuration mode:
To identify all transparent bridge packets as interesting, complete the following task in global configuration mode:
| Task | Command |
|---|---|
| Define a dialer list that treats all transparent bridge packets as interesting. | dialer-list dialer-group protocol bridge permit |
To control access by Ethernet type codes, complete the following tasks in global configuration mode:
| Task | Command |
|---|---|
| Identify interesting packets by Ethernet type codes (access list numbers must be in the range 200-299). | access-list access-list-number {permit | deny} type-code [mask] |
| Define a dialer list for the specified access list. | dialer-list dialer-group protocol bridge list access-list-number |
For a table of some common Ethernet types codes, see the "Ethernet Types Codes" appendix in the Bridging and IBM Networking Command Reference.
To specify the interface and enter interface configuration mode, complete the following task, starting in global configuration mode:
| Task | Command |
|---|---|
| Specify the serial or ISDN interface and enter interface configuration mode. | interface type number |
You can configure the destination by specifying either of the following:
To configure the destination for bridging over a specified interface, complete the following task in interface configuration mode:
| Task | Command |
|---|---|
| Configure the dial string to call. | dialer string dial-string |
Packets are bridged only among interfaces that belong to the same bridge group. To assign an interface to a bridge group, complete the following task in interface configuration mode:
| Task | Command |
|---|---|
| Assign the specified interface to a bridge group. | bridge-group bridge-group |
To monitor DDR dialer profile connections, perform the following tasks in privileged EXEC mode:
| Task | Command |
|---|---|
| Display information for the interfaces configured for DDR dialer profiles. | show dialer interface |
| Display information about the ISDN interface. | show interfaces bri 0 |
| Display status about the IPX interface. | show ipx interface [type number] |
| Display information about the IPX packets transmitted by the router or access server, including watchdog counters. | show ipx traffic |
| Display information about the AppleTalk packets transmitted by the router or access server. | show appletalk traffic |
| Display information about the Banyan VINES packets transmitted by the router or access server. | show vines traffic |
| Display information about the DECnet packets transmitted by the router or access server. | show decnet traffic |
| Display information about the XNS packets transmitted by the router or access server. | show xns traffic |
| Clear the values of the general diagnostic statistics. | clear dialer |
This section provides two comprehensive configuration examples:
This central site can place or receive calls from three remote sites over four ISDN BRI lines. Each remote site is on a different IP subnet and has different bandwidth requirements. Therefore three dialer interfaces and three dialer pools are defined.
! This is a Dialer Profile for reaching remote subnetwork 1.1.1.1. interface Dialer1 ip address 1.1.1.1 255.255.255.0 encapsulation ppp dialer remote-name Smalluser dialer string 4540 dialer pool 3 dialer-group 1 ! This is a Dialer Profile for reaching remote subnetwork 2.2.2.2. interface Dialer2 ip address 2.2.2.2 255.255.255.0 encapsulation ppp dialer remote-name Mediumuser dialer string 5264540 class Eng dialer load-threshold 50 either dialer pool 1 dialer-group 2 ! This is a Dialer Profile for reaching remote subnetwork 3.3.3.3. interface Dialer3 ip address 3.3.3.3 255.255.255.0 encapsulation ppp dialer remote-name Poweruser dialer string 4156884540 class Eng dialer hold-queue 10 dialer load-threshold 80 dialer pool 2 dialer-group 2 ! This map class ensures that these calls use an ISDN speed of 56 kbps. map-class dialer Eng isdn speed 56 interface BRI0 encapsulation PPP ! BRI 0 has a higher priority than BRI 1 in dialer pool 1. dialer pool-member 1 priority 100 ppp authentication chap interface BRI1 encapsulation ppp dialer pool-member 1 priority 50 dialer pool-member 2 priority 50 ! BRI 1 has a reserved channel in dialer pool 3; the channel remains inactive ! until BRI 1 uses it to place calls. dialer pool-member 3 min-link 1 ppp authentication chap interface BRI2 encapsulation ppp ! BRI 2 has a higher priority than BRI 1 in dialer pool 2. dialer pool-member 2 priority 100 ppp authentication chap interface BRI3 encapsulation ppp ! BRI 3 has the highest priority in dialer pool 2. dialer pool-member 2 priority 150 ppp authentication chap
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 BRI 0, and BRI 0 1s a member of the two dialer pools. 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 2 dialer string 5551234 dialer-group 1 interface bri 0 encapsulation PPP dialer pool-member 1 dialer pool-member 2 ppp authentication chap interface serial 0 ip unnumbered loopback0 backup interface dialer0 backup delay 5 10 interface serial 1 ip unnumbered loopback0 backup interface dialer1 backup delay 5 10
|
|