From: 910T (910t@cox.net)
Date: Thu Jun 19 2003 - 16:50:36 GMT-3
"This kind of stuff will sit in the back of my head until I know what's
going on... "
I know what you mean--I'm the same way. May I offer some friendly advice?
Forget about the answer key or only resort to it to clarify ambiguous
objectives. Use the scenarios as suggestions, but exercise the means to
_know_ your solution is correct for the stated objective. Lab it and use the
appropriate show or debug commands to clearly demonstrate you've met the
objective(s). Think about it: during the real lab exam, if the objective is
clear and your can clearly demonstrate you understood the objective and can
show you've met it, how could they not give you the points, regardless of
what some answer key states or omits? If you misunderstand the objective,
then oh well...better luck next time. If its ambiguous, it's up to you to
clarify it with the help of the proctor...and then nail it.
I'm saying all this because I believe you actually came up with an incorrect
solution initially but then came up with the right solution and are now
second-guessing yourself because the answer isn't in the answer key. Pruning
is a global-level command that just restricts broadcasts, et. al., within a
given VLAN to only those trunks that have switches with members of that VLAN
downstream. It won't prevent "the propagation" of a VLAN over a given trunk.
On the other hand, the 'switchport trunk allowed vlan remove'
interface-level command will prevent traffic tagged for the specified
VLAN(s) from traversing that trunk.
Regards,
Mas Kato, CCIE #7772
https://ecardfile.com/id/mkato
----- Original Message -----
From: "Joe Deleonardo" <jdeleonardo@cox.net>
To: <ccielab@groupstudy.com>; <cciesecurity@yahoogroups.com>;
<security@groupstudy.com>
Sent: Wednesday, June 18, 2003 11:00 AM
Subject: STP down a trunk
Hi,
I'm working on a problem.... besides these groups have been too quite. ;-)
It's a lab in a Cisco book. One of the steps is, "do not propagate VLAN26
and
VLAN13 down the trunk."
At first I thought about pruning, but there's only one CAT 3550 switch in
the
design. Then I thought about using, "switchport trunk allowed vlan remove
26"
etc. Then I checked the final config per Cisco and neither idea I had for
taking care of that step showed up in the final config.
There's nothing in the final solution that's foreign to me or that I think
will solve this step. It's a very basic switch config.
Here's the trunk config:
int f0/5
switchport mode trunk
switchport trunk encap dot1q
Here is the config for one of the vlans:
int f0/6
switchport mode access
switchport access vlan 26
An excerpt from the vlan database:
vtp server
vtp domain lab
vtp password cisco
vlan 26 name VLAN26
Now I know what you're thinking. If there is only one cat 3550 switch, then
why the password. Maybe it's for planning for a future addition or just
plain security? But in this map and problem there is only one CAT 3550.
I suppose it could just be an oversight on the side of the author, by not
including the solution. But I've gone back and re-read everything about the
encapsulation, trunking and vlans I could find and I can't find anything.
This kind of stuff will sit in the back of my head until I know what's going
on... any ideas? I'm just afraid I'm missing something key.
Thanks,
Joe
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:01 GMT-3