348 Words. Plan about 1 minute(s) to read this.
This will be a challenging lab. I think I can do nearly everything with some help from the doc CD, but there’s no way I’ll get it all done in 8 hours. I’ve still created my time budget like I did for scenario 4, and I’m still going to try to work within those parameters. I figure the more I treat each practice lab like the real lab, the better off I’ll be in the long run. It’s just the realistic side of me saying that I won’t fit it all in during the alloted time.
The lab is similar to the other scenarios for the core routing and switching pieces, like OSPF, EIGRP, RIP, BGP and redistribution. The scenario has some new twists like a VPN tunnel and QoS using RSVP. It struck me while reading the section that despite all the QoS studying I’ve done in recent months, I don’t know anything about RSVP except that you’re supposed to use it to reserve bandwidth. There’s an IPv6 summarization requirement, meaning I still really have to figure that out. It seems like if I get to the point of understanding IPv6 summarization, that’s an easy point or two on the lab. There’s some IPv6 multicast config for the 3560, as well as what I think is IP source guard (I have to read the requirement again to be sure), and 802.1x. There’s also some NAT and dense mode multicast.
There are a LOT of detailed requirements in this scenario. Very specific tasks requiring that OSPF behave a certain way, BGP be configured like-so, etc.
All I got done tonight after getting home late and having 2 children requiring my attention plus a new kitten that’s being socialized, was to clear the configs, put in the default config, and configure the frame-relay and HDLC links. Oh, and read the scenario over once and assigned time values to each section. So that’s something. But hardly any great achievement for the evening. I’m going to go review the answer key for the frame section, and make sure I didn’t miss out on any issues.
Ethan Banks writes & podcasts about IT, new media, and personal tech.
about | subscribe | @ecbanks