From: Tom Larus (tlarus@xxxxxxxxxxxxxxx)
Date: Thu Jun 06 2002 - 19:20:22 GMT-3
This has been one of those days when nothing went easily. If you only have
to look at he solution once in a while, you are pretty darn good. And even
the solutions don't always have things done just right (or as well as they
could be, to put it very politely).
A little tip on voice config. I have been using dial-peer numbers that are
the same or similar to the phone numbers. Seemed like a good idea until I
realized that I was neglecting to use destination-pattern statements.
Is it just me, or does it seem like IPSEC configuration syntax is
unnecessarily tedious. Yes, I know that there are certain things that just
have to be configured, but you would think Cisco could have made the syntax
a bit more elegant. I can't help but think that someone in marketing wants
things to seem more complicated than they are, as if customers who use this
stuff would believe that tedious complexity and nearly-opaque language would
scare off the evildoers and make the networks safer.
It's been a long day. You have company.
Best wishes,
Tom Larus
----- Original Message -----
From: "Kevin Wollenweber" <kwollenw@cisco.com>
To: "Dennis Laganiere" <dennisl@advancedbionics.com>
Cc: "'Bill Mckenzie'" <bmckenzie@hotmail.com>; <ccielab@groupstudy.com>
Sent: Thursday, June 06, 2002 2:21 PM
Subject: RE: Preparation Frustration
> I couldn't agree more. I had been having the same problem for awhile. I
> think the best advice is what Dennis said below. Just don't get caught up
> on the same thing multiple times. If you get stuck for so long that you
> have to go to the solutions, make a note of the topic and spend some time
> going through the solution and making sure you understand why things are
> that way. Eventually that is one more topic that you understand ;)
>
> Kevin
>
> On Thu, 6 Jun 2002, Dennis Laganiere wrote:
>
> > I want to say that everybody goes through this (although I'm sure
somebody
> > will try to prove how smart they are by denying it... :)). What Caslow
> > recommends is keeping a journal of your progress so you can easily see
what
> > things have blocked your progress. I like to create a flashcard for
> > everything that kicked my butt so I can review them when I have a few
> > minutes of downtime.
> >
> > The main thing is to never make the same mistake or have the same
problem
> > twice. If something stops you once, make sure you know that particular
> > "gotcha" the next time it comes up. Believe it or not, there are only a
> > limited number of mistakes to be made - if you only make each one once,
you
> > will find yourself at the end of the list eventually...
> >
> > Please consider this the contribution of my $.02
> >
> > Hope that helps...
> >
> > --- Dennis
> >
> > -----Original Message-----
> > From: Bill Mckenzie [mailto:bmckenzie@hotmail.com]
> > Sent: Thursday, June 06, 2002 10:12 AM
> > To: ccielab@groupstudy.com
> > Subject: OT: Preparation Frustration
> >
> > I'm sorry, this is a little off topic but if I don't ask I'm going to go
> > insane. It seems I get stuck on a least a little part of almost every
single
> >
> > lab I do. Sometimes small, sometimes a lot (BGP). I end up having to
look at
> >
> > a piece of the solution almost always to complete what I need to do. And
> > since each section is graded all or nothing, missing one line could blow
> > it.My question is, does anyone else have to resort to this? I'm not
> > scheduled to take the lab until Nov. 1st, but I'm already thinking about
> > rescheduling it.
> >
> > Any comments to let me know that I'm not the only one that gets totally
> > stuck would be appreciated by my self-esteem.
> >
> > Thanks,
> > Bill Mckenzie
> >
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:27 GMT-3