Hi,

I still seem to strike the odd AppleTalk network,  certainly a lot of IPX.  I am 
usually called on when the client IT people are confused.  Often the equipment is not 
Cisco.

I guess we each have a different need but it is important that things such as the CCIE 
have a high level of regard in the IT world.  Therefore I would think a CCIE needs to 
know a lot about a lot.  The CCIE needs to be an "expert" on things "internetworking". 
 This to me means if there is something the CCIE does not know he needs to be able to 
quickly identify what is not known and know who to talk to or where to get the info.

As an "expert" the CCIE should then be able to share the acquired knowledge without 
fear of his or her position.

Teunis
Hobart, Tasmania
Australia



On Wednesday, December 27, 2000 at 01:47:38 PM, John Hardman wrote:

> Humm... interesting question.
> 
> >From one point of view...
> 
> What should be tested (or not tested):
> 
> In over 10 years of IT work I have only ran across AppleTalk once, so drop
> AppleTalk (which they are doing).
> 
> In the same time frame I have only ran across one IPX network that wasn't
> either in the process of being converted to 100BaseT or was only being used
> in the DC to connect to a Novell server that was a file server which had
> it's drives mapped to NT drives. So IPX should take a big back seat to IP.
> 
> TR, well personally I like it, but again I have only seen one network with
> TR that wasn't planned to be changed to 100BaseT. Come to think of it, they
> announced the upgrade a couple of months after I left there. So TR should
> also be in the back seat.
> 
> Bridging, humm... well in some respects it is rarely used in the networks I
> have seen, mostly to get to SNA servers. But then again you had better know
> your IRB pretty well with all of the L3 switching that companies are being
> sold these days.
> 
> L3 switching, better know that pretty well. There are just too many
> companies being sold L3 that it had better take a bigger role in the lab.
> 
> The R/S written and lab should take on more of the service provider element.
> I am not saying that the new SP track should be rolled into the RS track.
> But with outsourcing and the Internet with VPN, dial and the like taking a
> bigger and bigger role in most companies, better know your ATM, dial, VPN,
> BGP, etc, etc. The same can be said for security.
> 
> Not having taken the lab, I can not really say as to how IPX, TR, or
> bridging is tested. It could be that it is tested as a primary thing and not
> as a secondary, e.g. "well looks like we are going to have to deal with that
> TR segment over rather we want to or not". The same could be said for ATM,
> maybe it should be a primary and not a secondary.
> 
> Well there is $0.02 from one point of view, HTH.
> --
> John Hardman CCNP MCSE+I
> 
> 
> ""Chuck Larrieu"" <[EMAIL PROTECTED]> wrote in message
> 002c01c0703c$c2ef8680$[EMAIL PROTECTED]">news:002c01c0703c$c2ef8680$[EMAIL PROTECTED]...
> > We've all seen a number of comments about the CCIE written and the CCIE
> Lab,
> > regarding content. Most of those comments have been negative.
> >
> > So, what SHOULD be tested? What SHOULD a CCIE know?
> >
> > Anyone?
> >
> > Chuck
> > ----------------------
> > I am Locutus, a CCIE Lab Proctor. Xx_Brain_dumps_xX are futile. Your life
> as
> > it has been is over ( if you hope to pass ) From this time forward, you
> will
> > study US!
> > ( apologies to the folks at Star Trek TNG )
> >
> > _________________________________
> > 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]
> 
> 


--
www.tasmail.com


_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to