Section 1 – Bridging and Switching – 18 Points
I did pretty well on this section. If I had been grading this I would have received 12 out of 18 points.
Most of the tasks were pretty simple VTP, EtherChannel, and Trunking tasks. You needed to know your technologies in order to decipher some of the tasks, but the wording was not too tricky. For instance, knowing that “untagged traffic” on a trunk means that you need to use dot1q trunking with a native VLAN.
The first of my lost points (and the only task I was completely stumped on) were due to a single task sandwiched into a simple EtherChannel section:
Ensure that SW1 is the 801.2ad decision maker for this logical link.
I had NO idea what 801.2ad was. I looked through the 3560 configuration guide, but to no avail. I finally broke down and Googled it (I would not allow myself to do this on a mock lab):
Your search – 801.2ad – did not match any documents.
Make sure all words are spelled correctly.
Try different keywords.
Try more general keywords.
Okay. That’s odd. Maybe it’s a misprint and it should be “802.1ad”. That did pull up some documents, but what the hell are “Provider Bridges”?
This sounds like Service Provider technology to me. I popped over to IE’s forums and found this post:
It is a find and replace error. It should read 802.3ad.
Brian Dennis, CCIE4 #2210 (R&S/ISP-Dial/Security/SP)
So it was a typo. I am a little disappointed that IE has not fixed this since it was recognized as an error back in June. Here’s what I was able to dig up on 802.3ad:
Link aggregation, or IEEE 802.3ad, is a computer networking term which describes using multiple Ethernet network cables/ports in parallel to increase the link speed beyond the limits of any one single cable or port, and to increase the redundancy for higher availability.
Link aggregation is an inexpensive way to set up a high-speed backbone network that transfers much more data than any one single port or device can deliver. Although in the past various vendors used proprietary techniques, the preference today is to use the IEEE standard Link Aggregation Control Protocol (LACP).
Ah!!! The section asks to build an EtherChannel using LACP. It still took some searching in the 3560 Configuring EtherChannel chapter to find this:
sw1#sh run | i lacp
lacp system-priority 1
sw1#sh lacp sys-id
This is an example of an obscure (at least to me) technology causing you to lose some otherwise easy points. The section was worth 3 points, but since I did not know what 802.3ad was (even without the typo) I lost all 3 points.
The only other place where I lost points was in the 802.1x Authentication section. I am far from an 802.1x expert, but the task was pretty straighforward and everything I needed (except for one bit) was in the DOC:
I was able to follow the step-by-step instructions and configure everything correctly except for this task:
The radius server is expecting the source of these packets to come from 188.8.131.52
184.108.40.206 is sw1’s Loopback 0 interface. I could not find a way to source packets from that interface. In the end I thought that maybe this was the default behavior. No such luck. 😦
The command that I needed was “ip radius source-interface”
That task cost me 3 more points
I did pull one section out of my butt though. 🙂 The last section concerned increasing the number of routes that the 3560s could handle. I wasn’t sure but I thought that this had to do with the SDM template. I was able to quickly read through the DOC for that feature and correctly configure the switches (Table 7-1 is a really good resource).
I feel like I made good time even with looking up a couple of topics in the DOC. I would venture that this section was probably quite a bit easier than the actual lab.