What about becoming BICSI certified?
"Priscilla Oppenheimer" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> At 10:01 AM 1/4/01, Tony van Ree wrote:
>
> >A couple of thoughts based on the PVC fault thread but looking at a
> >different angle.
> >
> >Should we as aspiring "communications experts" understand:
> >1 Fundamental electrical and magnetic propogation theory.
> >2 Basic cabling technology, design and termination.
>
> Yes. Cisco Networking Academy requires almost a whole semester on
> electricity, cabling, building wiring, etc. Now, I think that's overkill,
> but at least some study in these areas is a good idea if you want to be an
> efficient troubleshooter.
>
> Priscilla
>
> >Well lets consider the number of faults that can be put into this
> >category. It used to be 75%+ faults were of a physical nature. I think
> >the figure would still be quite high but I don't have recent figures.
> >
> >Most intermittent faults are due to connections and/or connectors. Ofter
> >due to poor installation and/or plugs being inserted and removed
regularly
> >and/or incorrectly.
> >
> >The next most common cause of intermittent faults is magnetic (Noise)
> >interferance. Usually due to poor cabling layouts and/or poor
> >installation methods.
> >
> >The most common cause of permanent damage to to ports is due to incorrect
> >installation of cables (NT1 to Ethernet ports is a good one that comes up
> >a lot).
> >
> >In switching the most common problems are duplex mismatches. Usually due
> >to a misunderstanding of what duplex setting do.
> >
> >These are just some considerations there are heaps more. Most are easily
> >avoided but difficult to diagnose. An understanding of the fundamentals
> >involved can avoid disaster.
> >
> >Just as a beat up on all. I work in an environment where we supply Telco
> >type services and IP connectivity to thousands (this figure is an
> >understatement). A part of my job is to troubleshoot client connections
> >to our access servers. I can often go for a week or two handling about
10
> >faults or more per day without finding a fault in the configuration of
the
> >access servers, connections to the access servers and/or the clients
> >CPE. This does not leave much but I'll bet most still blame us. I don't
> >know how often I will suggest change this setting in your server an all
> >will be fine. Bink up it comes and so does the question "what did you do
> >at your end to fix my server?"
> >
> >Incidently the next most common problem I come across is
username/password
> >errors particularly where people mix cases and/or use non alphanumeric
> >characters in usernames. In my opinoin this shouls be avoided (In
Cisco's
> >also). The term username in the Cisco sense is really a hostname (PPP)
> >and should follow the Unix Hostmane rules to avoid stange issues.
> >
> >Most faults a simple and can be avoided by careful planning.
> >
> >Just some thoughts and ramblings from Teunis
> >
> >Teunis
> >Hobart, Tasmania
> >Australia
> >
> >
> >--
> >www.tasmail.com
> >
> >
> >_________________________________
> >FAQ, list archives, and subscription info:
> >http://www.groupstudy.com/list/cisco.html
> >Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>
> ________________________
>
> Priscilla Oppenheimer
> http://www.priscilla.com
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
