CCIE Pursuit Blog

January 17, 2008

Internetwork Expert Volume III: Lab 2 – Section 3

WAN Technologies – 12 Points

3.1 Point-To-Point

Simple PTP Frame Relay configuration using the main ints and disabling Inverse-ARP.  This looks like hub and spoke, but there is nothing in the task that say that we need to be able ping from spoke to spoke.

3.2 Point-To-Point

r4 uses two point-to-point subinterfaces while r3 and r5 use main interfaces.  Keep in mind for OSPF.

3.3 Point-To-Point

Use a multipoint subinterface to connect to bb1 on DLCI 101.  Use inverse-arp. 

“Do not diable Inverse-ARP but do not allow r6 to map ununsed DLCI’s using Inverse-ARP.”

DLCIs assigned to the physical interface by defaul, so while our multipoint subinterface will have Inverse-ARP enabled by default we don’t need to do any other tweaking as only DLCI 101 will be assigned to the subinterface.

r6(config-if)#int s0/0/0.1 mul
r6(config-subif)#desc ->bb1 FR DLCI 101
r6(config-subif)#ip add 54.1.4.6 255.255.255.0
r6(config-subif)#frame interface-dlci 101

Weird…Inverse-ARP never worked….so I tried a static map:

interface Serial0/0/0
 no ip address
 encapsulation frame-relay IETF
 frame-relay lmi-type cisco
interface Serial0/0/0.1 multipoint
 description ->bb1 FR DLCI 101
 ip address 54.1.4.6 255.255.255.0
 frame-relay interface-dlci 101

r6(config)#int s0/0/0.1
r6(config-subif)#no frame-relay interface-dlci 101
r6(config-subif)#frame map ip 54.1.4.254 101 broad

r6(config-subif)#do sh frame map
Serial0/0/0.1 (up): ip 54.1.4.254dlci 101(0x65,0x1850), static,
              broadcast,
              IETF, status defined, active 

r6(config-subif)#do p 54.1.4.254

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 54.1.4.254, timeout is 2 seconds:
…..
Success rate is 0 percent (0/5)
r6(config-subif)#do p 54.1.4.254

Here’s my problem (from CCOnlineLabs documentation):

INER6 S0/0/0 61  – INEBB1 S0/0 61

DLCI 101 is not available on r6.  I need to use DLCI 61 instead.

After the “fix”:

r6#sh frame map
Serial0/0/0.1 (up): ip 54.1.3.254dlci 61(0x3D,0xCD0), dynamic,
              broadcast,
              IETF, status defined, active

Note the IP address….WTF?!!!

I jumped on bb1 and found out that there is no 54.1.4/0/24 network configured.  Wonderful.

BB1#sh ip int br | i 54.1.4.254
BB1#sh ip int br | i 54.1.3.254
Serial0/0.61
               54.1.3.254      YES manual up                    up

BB1#sh frame pvc | i 101
BB1#

Alright….I’m rolling with the 54.1.3.0/24 network….hopefully this doesn’t kick me in the nards once IGP gets routes from bb1.

After changing PTM subint to 54.1.3.6/24:

Serial0/0/0.1 (up): ip 54.1.3.254dlci 61(0x3D,0xCD0), dynamic,
              broadcast,
              IETF, status defined, active

r6#p 54.1.3.254

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 54.1.3.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/58/60 ms

IE solution shows “54.1.1.6/24”  WTF????

Lab02 – Notes on ALL Tasks

(*) Task 3.3: diagram is wrong, R6 has 54.1.1.6/24 ( not 54.1.4.6/24) !!!

HUH???  Forget it.  If something blows up later, I’ll come back to this.

3.4 PPP

‘encap ppp’ on both sides of the link.  That’s it.  Really.

3.5 PPP Authentication

Nice and easy task as we are told to use PAP and have both routers sent their user/pass.  Just remember your ppp pap sent-username command

ppp pap sent-username

Advertisements

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: