[150043] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Common operational misconceptions

daemon@ATHENA.MIT.EDU (Brandt, Ralph)
Fri Feb 17 13:28:58 2012

Date: Fri, 17 Feb 2012 13:28:04 -0500
In-Reply-To: <4F3E7F1F.3060504@ispalliance.net>
From: "Brandt, Ralph" <ralph.brandt@pateam.com>
To: "Scott Helms" <khelms@ispalliance.net>,
	<nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

To find counterfeit they teach you what good money looks like.  When you
are looking at a sniffer trace you are generally looking for something
that is not right.=20



Ralph Brandt
Communications Engineer
HP Enterprise Services
Telephone +1 717.506.0802
FAX +1 717.506.4358
Email Ralph.Brandt@pateam.com
5095 Ritter Rd
Mechanicsburg PA 17055

-----Original Message-----
From: Scott Helms [mailto:khelms@ispalliance.net]=20
Sent: Friday, February 17, 2012 11:24 AM
To: nanog@nanog.org
Subject: Re: Common operational misconceptions

On 2/17/2012 10:18 AM, Steve Clark wrote:
> I agree with this 100%.
>
> Having worked with many people over the last 40 years, the good=20
> trouble shooters understood how things
> were suppose to work. This helps immeasurably in determining where to=20
> start looking.
>

This is dead on and why I always start classes with a refresher on the=20
OSI model.  While the model isn't perfect it lets technicians and=20
engineers construct a reasonable model of how things *ought* to be=20
working.  While you certainly will run into devices that bend or even=20
break the rules (sometimes for good reasons) its much easier to=20
understand the exceptions if you know the normal operation for a=20
repeater, bridge, or router.

--=20
Scott Helms
Vice President of Technology
ISP Alliance, Inc. DBA ZCorum
(678) 507-5000
--------------------------------
http://twitter.com/kscotthelms
--------------------------------




home help back first fref pref prev next nref lref last post