|
|
Cisco CCNA / CCNP Certification Exam Tutorial: Configuring PPP CallbackConfiguring and testing PPP Callback is an important part of passing the Cisco CCNA and CCNP exams - but it's also important in production networks. Learn the "hows" and "whys" of PPP Callback from Chris Bryant, CCIE #12933. You may run into situations where a router in a remote location needs to dial in to a central router, but the toll charges are much higher if the remote router makes the call. This scenario is perfect for PPP Callback, where the callback client places a call to a callback server, authentication takes place, and the server then hangs up on the client! This ensures that the client isn't charged for the call. The server then calls the client back. In the following example, R2 has been configured as the client and R1 is the callback server. Let's look at both configurations and the unique commands PPP Callback requires. Client: username R1 password CCIE interface BRI0
Most of that configuration will look familiar to you, but the ppp callback request command might not. This command enables the BRI interface to request the callback. Simple enough, right? The PPP Callback Server config requires more configuration and an additional map-class as well. Server: username R2 password CCIE interface BRI0
map-class dialer CALL_R2_BACK
Examining the PPP Callback Server command from the top down... dialer callback-secure enables security on the callback. If the remote router cannot be authenticated for callback, the incoming call will be disconnected. The dialer map statement now calls the class CALL_R2_BACK, shown at the bottom of the config excerpt. ppp callback accept enables PPP callback on this router. dialer callback-server username tells the callback server that the device referenced in the dialer map statement is a callback client. The only way to find out if the config works is to test it, so let's send a ping from R2 to R1 and see if the callback takes place. R2#ping 172.12.12.1 Type escape sequence to abort.
02:45:42: BR0 DDR: Dialing cause ip (s=172.12.12.2, d=172.12.12.1)
The callback was successfully negotiated, and the call then disconnected. R1 then called R2 back, and show dialer on R1 confirms the purpose of the call. R1#show dialer BRI0 - dialer type = ISDN Dial String Successes Failures Last DNIS Last status
BRI0:1 - dialer type = ISDN
, it can save your organization quite a bit of money!
Article Tags: %link-3-updown: Interface Bri0:1,, Interface Bri0:1, Changed, Bri0:1, Changed State, Callback Server, %link-3-updown: Interface, Interface Bri0:1,, Bri0:1, Changed, Changed State, Br0:1 Ddr:, Ddr: Callback Source: Free Articles from ArticlesFactory.com
ABOUT THE AUTHORChris Bryant, CCIE #12933, is the owner of The Bryant Advantage (http://www.thebryantadvantage.com), home of free CCNA and CCNP tutorials! For my FREE "How To Pass The CCNA" or "CCNP" ebook, visit the website and download your copies.
|
||||||||||||||||||||||||||||||||||||||||||
Partners
|