9:38am Wow, I cant believe I only have 10 days left to prepare. I’ll have to make the most of it. Just completed the first vol3 lab. Pretty easy stuff, definitely missing the multicast section. The last will probably progressively get harder. One new thing I tried in this lab when redistributing between rip and ospf to save time is to use:
ospf distance external 121
I normally use tags just to be sure, but these are time consuming, i changed the external distance and it worked fine, but this wont work if another part of the lab is redistributing into ospf, because then the routes redistributed into rip will be prefered with a admin distance of 120.
1am Just completed vol3lab5. First half done, but as I thought they are getting harder and longer to complete. If I keep a steady pace, I could possibly complete them by tuesday.
Some interesting scenarios in the first few labs:
The question is to setup the a hub and spoke frame links so that if the DLCI becomes inactive or deleted the interface goes into down state. I initially set it up with a multipoint subinterface but when I verified this, the link stayed up
sh frame-re pvc in s1/0 | in 301
DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = Serial1/0.301sh ip int brief | in 301
Serial1/0.301 190.1.135.3 YES unset up up
I changed the multipoint to ppp over frame on point-to-point sub interfaces. The goal was to keep the ip the same for both circuits the same on the hub. PPPoFr work for this because even though I used two different sub interfaces they link to same virtual-template. One ip is linked to different dlci’s. So after the change and removing the dlci’s from the frame switch, the interface went down when the dlci’s were deleted or inactive. The solution guide used the first method but does not show any verification.
sh ip int brief | in 301
Serial1/0.301 unassigned YES unset down down
The first few times I used PPPoFr it was a bit unfamiliar and tried to avoid it if possible, but its really quite simple. Consider the following few lines to change from a multipoint to PPPoFr config. The PPPoFr has exactly the same amount of statements. 2 frame-relay commands and one ip address.
interface Serial1/0.301 point-to-point
frame-relay interface-dlci 301 ppp Virtual-Template1
interface Serial1/0.305 point-to-point
frame-relay interface-dlci 305 ppp Virtual-Template1interface Virtual-Template1
ip address 190.1.135.3 255.255.255.0
Another interesting discovery was that it seems that is only possible to run one ospf virtual-link over a point-to-point interface and the secondary virtual links will only come up when the interface is changed with ip ospf network point-to-multipoint. Any other type besides ptp would probably work. When I see an opportunity in another lab I will double check this.

