Dialer Profiles allow different dialing information to be configured onto logical interfaces. The logical interfaces may have different dialing destinations, different remote router names, etc., but they'll be using the same physical interface.
Dialer strings are used on dialer profiles. Note that each logical interface has a different IP address, a different remote router to dial, and a different dialer string, but they will be using the same physical interface to dial out. The commands dialer pool and dialer pool-member are used to link the logical and physical interfaces. The number following each command must match for the logical interface to correctly bind to the physical interface.
R1(config)#interface dialer0
R1(config-if)#ip address 172.16.1.1 255.255.255.0
R1(config-if)#encapsulation ppp
<. The encapsulation type is placed on both the logical and physical interfaces. >
R1(config-if)#dialer remote-name Remote0
R1(config-if)#dialer pool 1
< places logical interface into dialer pool >
R1(config-if)#dialer string 5551212
< number dialed to contact router Remote0 >
R1(config-if)#dialer-group 1
< links logical interface to dialer-list 1 >
R1(config)#interface dialer1
R1(config-if)#ip address 172.16.1.2 255.255.255.0
R1(config-if)#encapsulation ppp
R1(config-if)#dialer remote-name Remote1
R1(config-if)#dialer pool 1
R1(config-if)#dialer string 5551234
R1(config-if)#dialer-group 1
R1(config)#interface bri0
R1(config-if)#no ip address
< With dialer profiles, IP addresses are assigned to logical interfaces. >
R1(config-if)#encapsulation ppp
< The encapsulation type is place on both the logical and physical interfaces.>
R1(config-if)#dialer pool-member 1
< The number associated with this command should match the number configured with the dialer pool number on the logical dialer interfaces. >
R1(config-if)#isdn spid1 0835866101
R1(config-if)#isdn spid2 0835866301
When configuring dialer profiles, the encapsulation type should be placed on both the physical BRI interface and the logical dialer interfaces. The SPIDs are configured on the physical interface as well.
Configuring dialer profiles can be a little tricky at first, and the best way to master this skill is to get real hands-on practice in your own CCNA / CCNP home lab or a rack rental service. Either way, hands-on is the best practice. Best of luck in your CCNA studies!
Microsoft Office Certification Exam
Frame Relay VCs use Data-Link Connection Identifiers (DLCI - pronounced "del-see") as their addresses. Unlike other Cisco technologies, VCs have only a single DLCI in their header. They do not have a source and destination.
DLCIs have local significance only. DLCI numbers are not advertised to other routers, and other routers can use the same DLCI numbers without causing connectivity issues.
Cisco uses the term global addressing to describe a technique by which a router in a frame relay network is reached via the same DLCI number from each router in the network. For example, in a 25-router network, the same DLCI number would be used to reach ?Router A? by each router.
Global Addressing is an organizational tool that does not affect the fact that DLCIs have local significance only.
The locally significant DLCI must be mapped to the destination router's IP address. There are two options for this, Inverse ARP and static mapping.
In both of the following examples, the single physical Serial interface on Router 1 is configured with two logical connections through the frame relay cloud, one to Router 2 and one to Router 3.
Inverse ARP runs by default once Frame Relay is enabled, and starts working as soon as you open the interface. By running show frame-relay map after enabling Frame Relay, two dynamic mappings are shown on this router. If a dynamic mapping is shown, Inverse ARP performed it.
R1#show frame map
Serial0 (up): ip 200.1.1.2 dlci 122(0x7A,0x1CA0), dynamic,
broadcast,, status defined, active
Serial0 (up): ip 200.1.1.3 dlci 123(0x7B,0x1CB0), dynamic,
broadcast,, status defined, active
Static mappings require the use of a frame map statement. To use static mappings, turn Inverse ARP off with the no frame-relay inverse-arp statement, and configure a frame map statement for each remote destination that maps the local DLCI to the remote IP address. Frame Relay requires the broadcast keyword to send broadcasts to the remote device.
R1#conf t
R1(config)#interface serial0
R1(config-if)#no frame-relay inverse-arp
R1(config-if)#frame map ip 200.1.1.2 122 broadcast
R1(config-if)#frame map ip 200.1.1.3 123 broadcast
The syntax of the frame map statement maps the remote IP address to the local DLCI.
Broadcasts will not be transmitted by default; the broadcast option must be configured.
R1#show frame map
Serial0 (up): ip 200.1.1.2 dlci 122(0x7A,0x1CA0), static,
broadcast,
CISCO, status defined, active
Serial0 (up): ip 200.1.1.3 dlci 123(0x7B,0x1CB0), static,
broadcast,
CISCO, status defined, active
Hands-on practice is the best way to prepare for CCNA exam success. Working with Frame Relay in a lab environment practically guarantees that you'll truly master the concepts shown here - and then you're on your way to the CCNA and becoming a master network engineer.
Chris Bryant has sinced written about articles on various topics from CISCO CCNA, Personal Desktop and Cisco CCNP. Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage , home of free and CCNP tutorials! Pass the. Chris Bryant's top article generates over 27100 views. to your Favourites.
Best Pay Per Click Sites By using the valuable tips outline here, you will be well ahead of your competition using pay per click