Re: Natting multicast problem...

The first time I had the problem I didn't have the chance to tell the
proctor. They took the points because the solution was broke when
they looked at it (without looking at the config-another story for
another time).

The second was a very well known bug with the IPS sensor in the
field. Get to the lab? Winnar version.

But I do appreciate the doubt from all of y'alls.-

Sent from my iPhone

On Aug 20, 2009, at 12:00 PM, Scott Morris <smorris_at_ine.com> wrote:

> Great point there! The only thing I'd add is to be aware, if you
> try to tell the proctor you have a bug... They have seen probably
> EVERY version of misconfiguration there is. And they may likely
> know exactly what you did (or didn't do) by your describing the
> "bug". Don't take it the wrong way when they tell you it's not a
> bug and send you back to your desk...
>
> It's nothing personal!
>
>
> Scott Morris, CCIEx4 (R&S/ISP-Dial/Security/Service Provider) #4713,
> JNCIE-M #153, JNCIS-ER, CISSP, et al.
> JNCI-M, JNCI-ER
> evil_at_ine.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Outside US: 775-826-4344
>
> Knowledge is power.
> Power corrupts.
> Study hard and be Eeeeviiiil......
>
>
>
> Rick Mur wrote:
>>
>> I never ran into a bug on both my labs, all things I thought it was
>> a bug was just me thinking the wrong way :-)
>>
>> It will not change the point of the conversation. The labs are
>> developed and tested on the same platform and the same version as
>> you'll get on your attempt. Therefore minimizing the possibility of
>> running into a bug.
>>
>> And please be cautious when calling it a bug, since most times it's
>> a misconfiguration, misassumption or just a clear or reload would
>> fix it. I've helped dozens of customers who claimed to have found a
>> bug which turned out to be something else.

Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 20 2009 - 12:22:52 ART