28.06.2014 Views

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

36. IPCP: Install route to 192.168.1.1 (from source)<br />

37. Line protocol on Interface BRI0/0:1, changed state to up<br />

38. Interface BRI0/0:1 is now connected to 5551234 smarts<br />

In line 1 we see our PPP request beginning. Line 2 shows us a request from our source to<br />

start an LCP session. Line 3 shows our destination requesting CHAP password<br />

authentication from the source. Lines 4-7 repeat this process until, in line 8, the CHAP<br />

password authentication times out. (See? Nothing is perfect). In line 9 a request from<br />

our source to start an LCP session is repeated. Line 10 shows our destination requesting<br />

a CHAP password for authentication. Line 11 shows acknowledgement of the CHAP<br />

request. Line 12 shows acknowledgement of the acknowledgement that the information<br />

requesting CHAP password verification, the LCP state is set to open, and the next phase<br />

of PPP establishment starts. Lines 15-20 show us a similar process for verifying the<br />

CHAP password. Line 21 sets our PPP phase (LCP) as up. Line 22 starts our IPCP<br />

negotiation. (This intermingles with CDPCP so I will break them out separately.) Here a<br />

request for the BRI ip address of the destination is requested. Lines 23-28 and 21-33<br />

show the exchange of ip addresses between source and destination. Lines 29-30 and 34-<br />

25 show the CDPCP exchange sequence. Finally our route is installed in line 36. Then<br />

our state is up and connected in lines 37-38.<br />

Physical Layer:<br />

Now lets look at our dialer events and interface states.<br />

kissane#debug dialer<br />

Dial on demand events debugging is on<br />

1. 02:07:54: BR0/0 DDR: Dialing cause ip (s=192.168.1.2, d=192.168.1.1)<br />

2. 02:07:54: BR0/0 DDR: Attempting to dial 5551234<br />

3. 02:07:54: %LINK-3-UPDOWN:Interface BRI0/0:1, changed state to up<br />

4. 02:07:54: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected<br />

to 5551234<br />

5. 02:07:56: BR0/0:1 DDR: dialer protocol up<br />

6. 02:07:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface<br />

BRI0/0:1, changed state to up<br />

7. 02:08:00: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected<br />

to 5551234 smarts<br />

Since there is not a lot here let’s just go line <strong>by</strong> line. Line 1 shows our DDR dialing with<br />

source and destination addresses. Then, in line 2 we dial our destination number set in<br />

our dialer map statement. Our state comes up on our source, we are connected, the dialer<br />

protocol comes up, our state comes up on our destination, and our BRI line is connected.<br />

Not too tough. For a more exacting look combine the debug dialer with debug ppp<br />

negotiation.<br />

429

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!