on the subject .......
another good search engine is the cisco/google engine
http://cisco.google.com/cisco
i have found this very helpfull in "pointing me in the right direction"..
it will usually find a page that is in the general topic and i can search
around from there to find what i really want...
someone on the list passed this on to me some time ago .....( nice chap
...forgot his name).....
Sherlock Holmes (Sir Arthur Conen Doyle) once said ."the more sorces of
information one has the quicker the truth will present itself"...
CU
steve
>From: "Priscilla Oppenheimer"
>Reply-To: "Priscilla Oppenheimer"
>To: [EMAIL PROTECTED]
>Subject: RE: Figuring out Config Register Values [7:15894]
>Date: Mon, 13 Aug 2001 15:35:25 -0400
>
>Cisco research skills are as important as configuration and design skills
>and almost as challenging. When you find something that someone else
>couldn't find, please tell us how you did it. Page-by-page navigation
>instructions are very helpful because they help us learn the structure of
>the documentation.
>
>Your Cisco career will die if you don't get good at finding stuff in the
>documentation, and the only way to get good at this is to spend time with
>it. Here's where I like to start:
>
>http://www.cisco.com/univercd/cc/td/doc/product/software/index.htm
>
>Regarding the search engine, the best advice is not to depend on it too
>much. It is not very effective. It's much better to know where to look in
>the documentation. Also, take some time to learn the search engine's
>caveats for those times when you really want to use it.
>
>For example, the Cisco search engine automatically adds "and" between the
>words you enter so it only returns those pages that include all of your
>search terms. To restrict a search further, just include more terms.
>
>The search engine does not support the logical "or" operator. It only
>returns pages that contain all the terms.
>
>You can search for phrases by adding quotation marks. Words enclosed in
>double quotes ("like this") will appear together in all returned documents.
>
>Searches are not case sensitive. All letters, regardless of how you type
>them, will be understood as lower case. I discovered this the hard way. I
>did a search on SAID. Big mistake. ;-) But then I changed it to SAID VLAN
>and that was more effective.
>
>There's more info on the search engine here:
>
>http://www.cisco.com/public/extra_search_help.html
>
>Priscilla
>
>At 02:50 PM 8/13/01, Daniel Cotts wrote:
> >You are correct.
> >Instead of posting a URL I've sometimes given directions page by page to
> >show how I reached a given topic.
> >Any thoughts on how to teach CCO navigation?
> >
> > > -----Original Message-----
> > > From: EA Louie [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, August 13, 2001 1:10 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Figuring out Config Register Values [7:15894]
> > >
> > >
> > > Bri - that sounds good to me! :-) although I find that most people
> > > 1. just don't know WHAT to search for... searching on CCO is
> > > an art that
> > > evolves using practice, practice, practice, and weeding out
> > > the worthless
> > > hits
> > > 2. don't know how to find what they searched for in the
> > > webpages presented
> > >
> > > for those who are CCIE bound, it's an imperative to know the
> > > basics of the
> > > IOS documentation layout on the CD ROM. Otherwise, the
> > > search engine brings
> > > up way too much information to be sifted through during the Lab.
> > >
> > > -e-
> > >
> > > ----- Original Message -----
> > > From: Brian
> > > To: EA Louie
> > > Sent: Monday, August 13, 2001 10:37 AM
> > > Subject: Re: Figuring out Config Register Values [7:15894]
> > >
> > >
> > > > I suggest a new rule for the list. If I don't know the
> > > answer, goto CCO
> > > to
> > > > search and get the answer easily, about a topic I know very
> > > little about,
> > > > then I perhaps shouldn't post the results of my arduous search.
> > > >
> > > > Bri
> > > >
> > > > ----- Original Message -----
> > > > From: "EA Louie"
> > > > To:
> > > > Sent: Monday, August 13, 2001 10:45 AM
> > > > Subject: Re: Figuring out Config Register Values [7:15894]
> > > >
> > > >
> > > > > my search on 'config reg bit settings' got me this hit on
> > > the first try:
> > > > >
> > > > >
> > > >
> > > http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix
> > > /cis2500/2509/
> > > > > acsvrug/maint.htm#20837 (
> > > > > To:
> > > > > Sent: Monday, August 13, 2001 10:10 AM
> > > > > Subject: Figuring out Config Register Values [7:15894]
> > > > >
> > > > >
> > > > > > I have been searching high and low on Cisco's website
> > > for information
> > > on
> > > > > how
> > > > > > to figure out the hexidecimal values of various Config-Register.
> > > > Example,
> > > > > > 0x2141, 0x102, 0x2142, 0x2102 etc. I would like to
> > > know how to figure
> > > > out
> > > > > > the bit value and be able to tell what each value is trying to
> > > > accomplish
> > > > > > just by looking at them. If anyone out there can help
> > > please do.
> > > Thank
> > > > > you
> > > > > >
> > > > > >
> > > > > >
> > > _________________________________________________________________
> > > > > > Get your FREE download of MSN Explorer at
> > > > http://explorer.msn.com/intl.asp
> > > > > _________________________________________________________
> > > > > Do You Yahoo!?
> > > > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > Report misconduct
> > > and Nondisclosure violations to [EMAIL PROTECTED]
>________________________
>
>Priscilla Oppenheimer
>http://www.priscilla.com
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16045&t=15894
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
