RE: NAT

[Ali Önder Ergün (Koç.Net)]

mailto:[EMAIL PROTECTED]]
Sent: Friday, April 06, 2001 6:20 PM
To: [EMAIL PROTECTED]
Subject: NAT


I was wondering if anyone could shed some light on a NAT issue I am
dealing with.  I have a Cisco 3362 router which is used for ISDN
connectivity.  I have several client networks that I connect to and now
have two clients with similar address ranges.  Client A uses a
10.1.1.0/24 network and a new client B uses a 10.0.0.0/8 addressing
scheme with several subnets.  The routes are as follows:

ip route 10.1.1.0 255.255.255.0 192.168.10.49 (for Client A)
ip route 10.1.0.0 255.255.0.0 192.168.10.130 (Client B)

You can see why there is a problem because any similar addresses within
the 10.1.1.x range on both networks, will mean that the router has no
idea where to send the traffic.

The dialer interface on my end has an address of 192.168.10.1 and the
BRI interface on the remote router is 192.168.10.130.  I have full
access and control to the router I am dialing in to so making changes is
quite easy.  I am thinking about using Network Address Translation on
the remote router somehow.

Any suggestions?

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

what is the passing mark for CCNP switching?

[Sim, CT (Chee Tong)]

Hi.. May I know what is the passing mark for CCNP switching? How many
questions and time allow?  Whether the mark is from the scale from 300 to
1000 like what CCNA 2.0 do??

SCT 

==
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
==
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.


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

Mzmaker

[John Chang]

I have a 2514 w/ 8Mb flash.  When I used mzmaker to compress IOS 12 that is 
10MB it worked fine.  However, after writing the .mz file to flash and 
starting up the router it keeps looping "Error : memory requirements exceed 
available memory
Memory required : 0x00AF99A0

Exception: Software forced crash at 0x111E (PC)"

and giving this error.  Does this not work since on a 2500 series router 
the IOS runs in the flash and not ram?  Thanks.
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Switching.

[CISQUO]

Hi people,

Cleared Switching this morning. It was pretty tough , as this was the first CCNP exam .

Hope to clear Routing soon.

1 down 3 to go.

Shree.

_
Chat with your friends as soon as they come online. Get Rediff Bol at
http://bol.rediff.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: 2 8mb flash partitions

[Circusnuts]

I believe the actual command is #no partition FLASH

- Original Message -
From: "Fred Danson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 09, 2001 3:51 AM
Subject: 2 8mb flash partitions


> Hey Group,
>
> I noticed that one of my 2500 routers which has a total of 16mb of flash
on
> 2 SIMMs has the flash split up into 2 partitions. If I wanted to put an
IOS
> on the router which was larger than 8mb, would it work? Is it possible to
> span a file over multiple flash SIMMs?
>
> Thanks in advance,
> Fred
> _
> Get your FREE download of MSN Explorer at http://explorer.msn.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: What does this line mean

[Traceroute]

- Original Message -
From: "John Brandis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 08, 2001 10:06 PM
Subject: What does this line mean


> no ip classless = you are not using classless routing
> ip route 10.0.0.0 255.0.0.0 10.10.32.0 = ther is a static route to network
10.0.0.0 with the class A subnet 255.0.0.0 and the default gateway is
10.10.32.0


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

2 8mb flash partitions

[Fred Danson]

Hey Group,

I noticed that one of my 2500 routers which has a total of 16mb of flash on 
2 SIMMs has the flash split up into 2 partitions. If I wanted to put an IOS 
on the router which was larger than 8mb, would it work? Is it possible to 
span a file over multiple flash SIMMs?

Thanks in advance,
Fred
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

ISL using 11.2?????

[Jeff]

I am using a 4500 with a Fast Ethernet interface and would like to be able
to route between VLANs that are setup on my 2900. I don't have the option to
use encapsulation ISL using Ver 11.2 on the 4500. Do I have to upgrade to
11.3 or something higher to be able to use ISL?

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

upgrading boot and IOS...

[Katson PN Yeung]

Dear all,

I have an old 7507 and would like to upgrade the boot image and IOS to
12.0.x... can someone suggests:
1. The most reliable IOS version in 12.0.x?
2. I would most like to take away my ethernet and channelized T1 module.
(therefore, I have AIP, RSP2(64M ram), VIP+PA-FE-TX x 2, and SSIP8.



Please see my sh ver below:


Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-AJSV-M), Version 11.2(18)BC, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 15-Apr-99 06:59 by krunyan
Image text-base: 0x600108A0, data-base: 0x60C3A000

ROM: System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)
BOOTFLASH: GS Software (RSP-BOOT-M), Version 11.1(6), RELEASE SOFTWARE (fc1)

7057old uptime is 7 weeks, 3 days, 3 hours, 28 minutes
System restarted by reload at 08:04:18 HKT Fri Feb 16 2001
System image file is "slot0:rsp-ajsv-mz_112-18_BC.bin", booted via slot0

cisco RSP2 (R4600) processor with 65536K bytes of memory.
R4600 processor, Implementation 32, Revision 2.0
Last reset from power-on
G.703/E1 software, Version 1.0.
SuperLAT software copyright 1990 by Meridian Technology Corp).
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.0.
Chassis Interface.
1 SSIP controller (8 Serial).
1 AIP controller (1 ATM).
1 MIP controller (2 T1).
2 VIP2 controllers (2 FastEthernet)(8 Ethernet).
8 Ethernet/IEEE 802.3 interface(s)
2 FastEthernet/IEEE 802.3 interface(s)
39 Serial network interface(s)
1 ATM network interface(s)
2 Channelized T1/PRI port(s)
123K bytes of non-volatile configuration memory.

20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
No slave installed in slot 3.
Configuration register is 0x2102


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

Re: Boot Rom for Cisco 2500 series routers

[Ping]

jonh:

cisco shiped it for free for me .

John Hardman wrote:

> Humm... Interesting, Cisco is willing to give them away free, but they do
> not ship for free. I wonder which is the better deal, your price for
> something free or something for free.
>
> HTH
> --
> John Hardman CCNP MCSE+I
>
> ""CiScO"" <[EMAIL PROTECTED]> wrote in message
> 97kpdn$883$[EMAIL PROTECTED]">news:97kpdn$883$[EMAIL PROTECTED]...
> > Is there anyone looking for Cisco 2500 router boot roms? I have the latest
> > from Cisco,  version 11.0(10c)XB2. I currently have several sets left. All
> > brand new. I am willing to ship the item at no cost within the US. If
> you're
> > interested please send an email so we can arrange shipping and payment.
> >
> > Helpful Links below:
> >
> > Boot Rom features and fixes:
> > http://www.cisco.com/warp/public/471/30.shtml
> >
> > Replacing Boot Rom chips Instructions:
> >
> http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/cis2500/2500c
> > fig/bootrom.htm
> >
> >
> > Thanks!
> >
> > Joe N. CCNA
> > http://www.tmjf.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: Frame Relay

[Ping]

go here http://www.fatkid.com/html/frame_relay.html

Mark Rose wrote:

> A while back there was a posting showing how to set up a frame relay switch
> with 3 routers (with configs). I misplaced the copy I had. I couldn't find
> it in the archives. Could someone help me out.
>
> TIA
> Mark
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

IP Classless

[John Brandis]

no ip classless
ip route 10.0.0.0 255.0.0.0 10.10.32.0

Whats this mean

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

What does this line mean

[John Brandis]

no ip classless
ip route 10.0.0.0 255.0.0.0 10.10.32.0

Thanks

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

Re: Frame Relay

[Ping]

in your lab ...you need a dce/dte cable.
in the real world you would use a csu/dsu
but i a read of certain config that in the real word a dte/dce cable is used

John Chang wrote:

> First time doing this and sorry for my ignorance. If I have a 4500M as my
> Frame Relay cloud.  How do I connect my 2501 router to it?  Do I just use a
> DCE to DTE cable?  And in the real world would I use a DSU/CSU?  Future
> reference: In the CCIE lab exam do they use DSU/CSU?  Thank you!
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Pre-sales consultant

[Arthur Simplina]

Hello,

A pre-sales consultant job ( in network and system solutions field) is a
great job?
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: methods for summarizing routes in FATKID ospf401

[John Kurkjian]

How about default routes (0.0.0.0 0.0.0.0)?

John

Clue Less <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi,
>
> Just trying out ospf401 on fatkid, and was reading the hints about
> summarizing.  Here's the hint
>
> "There are two built in OSPF methods to summarize OSPF routes. One way
> summaries between areas. The other summarizes between Autonomous
> Systems.  Do you know a third way to summarize routes, which works for
> any router, running any routing protocol?  How about a fourth?"
>
> http://www.fatkid.com/html/401_advanced_opsf_-_hints.html
>
> Does anyone know the 3rd or other ways and could kindly let me know?
>
> Clue Less.
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

I need ICRC. I have most other CCNA2.0/MCSEW2K.

[Arthur Simplina]

I need ICRC and I now have most other CCNA2.0/MCSEW2K.

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

Re: methods for summarizing routes in FATKID ospf401

[Richard Deal]

What about a static route?

"Clue Less" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi,
>
> Just trying out ospf401 on fatkid, and was reading the hints about
> summarizing.  Here's the hint
>
> "There are two built in OSPF methods to summarize OSPF routes. One way
> summaries between areas. The other summarizes between Autonomous
> Systems.  Do you know a third way to summarize routes, which works for
> any router, running any routing protocol?  How about a fourth?"
>
> http://www.fatkid.com/html/401_advanced_opsf_-_hints.html
>
> Does anyone know the 3rd or other ways and could kindly let me know?
>
> Clue Less.
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

methods for summarizing routes in FATKID ospf401

[Clue Less]

Hi,

Just trying out ospf401 on fatkid, and was reading the hints about
summarizing.  Here's the hint

"There are two built in OSPF methods to summarize OSPF routes. One way
summaries between areas. The other summarizes between Autonomous
Systems.  Do you know a third way to summarize routes, which works for
any router, running any routing protocol?  How about a fourth?"

http://www.fatkid.com/html/401_advanced_opsf_-_hints.html

Does anyone know the 3rd or other ways and could kindly let me know?

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

ISDN irregularity

[jenny . mcleod]

8000 bytes = 64000 bits.  What speed is your ISDN channel?  How long will
it take a ping to get to the other side and back?  How long is your
timeout?

I expect that if you increase the timeout you will see your pings return.

JMcL
-- Forwarded by Jenny Mcleod/NSO/CSDA on 09/04/2001
10:23 am ---


"Savvas Themistocleous" <[EMAIL PROTECTED]>@groupstudy.com on 06/04/2001
08:17:17 pm

Please respond to "Savvas Themistocleous" <[EMAIL PROTECTED]>

Sent by:  [EMAIL PROTECTED]



To:   <[EMAIL PROTECTED]>
cc:


Subject:  ISDN irregularity


Hi all,

I have just picked up something strange on my AS5300. Is this standard for
an Isdn connection with an MTU over 8000, it has a regular pattern which
suggests that it is standard to me. Any ideas? I thought fragmentation
should occur past this to 18024.

JHB-AS5300#ping
Protocol [ip]:
Target IP address: 216.0.53.162
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: y
Sweep min size [36]: 5000
Sweep max size [18024]: 1000
% Bad maximum size
JHB-AS5300#ping
Protocol [ip]:
Target IP address: 216.0.53.162
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: y
Sweep min size [36]: 5000
Sweep max size [18024]: 1
Sweep interval [1]: 500
Type escape sequence to abort.
Sending 55, [5000..1]-byte ICMP Echos to 216.0.53.162, timeout is 2
seconds:
!!.!!.!!.!

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

Re: OSPF virtual links

[Fred Danson]

The changes you listed really won't do anything. As long as the IP address 
on the interface falls into the network + wildcard mask range used in the 
network statement, it will work fine. You can check to see if the interface 
is active in the ospf process using the show ip ospf interface command.


>From: "Arthur Simplina" <[EMAIL PROTECTED]>
>Reply-To: "Arthur Simplina" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: OSPF virtual links
>Date: Sun, 08 Apr 2001 20:15:15 -0400
>
>My comments follow below. Please let me know how it worked out.
>
>
>---
>> >OSPF virtual links. Here's my configs: > >R2503 - backbone router
>> >hostname r2503 >!
>
>
>> >router ospf 100 >network 192.1.1.1 0.0.0.0 area 0
>> >--
>
>Please change your config to:
>   router ospf 100
>   network 192.1.1.0 0.0.0.255 area 0
>
>
>---
>
>> >R2523- backbone router, link between R2503 & R4000 >hostname r2523
>
>
>> >router ospf 100 >area 1 virtual-link 3.3.3.3 >network 192.1.1.2 0.0.0.0
>>area 0 >network 193.1.1.2 0.0.0.0 area 1 >
>> >-
>
>For R2523, please change your config to:
>  router ospf 100
>  area 1 virtual-link 3.3.3.3
>  network 192.1.1.0 0.0.0.255 area 0
>  network 193.1.1.0 0.0.0.255 area 1
>
>---
>
>> > >R4000, in areas 1 & 4, has a virtual link through R2523 >hostname 
>>r4000
>
>> >router ospf 100 >network 152.1.1.1 0.0.0.0 area 4 >network 193.1.1.1
>>0.0.0.0 area 1 >area 1 virtual-link 2.2.2.2 >!
>-
>
>For R4000, please change your config to:
>   router ospf 100
>   network 152.1.1.0 0.0.0.255 area 4
>   network 193.1.1.0 0.0.0.255 area 1
>   area 1 virtual-link 2.2.2.2
>
>---
>>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>_
>Get your FREE download of MSN Explorer at http://explorer.msn.com
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: CCIE Lab Report - unsuccesful

[Marty Adkins]

John Hardman wrote:
> 
> I sniped most of your report below with the exception of point #5. I have
> been trying to form a picture of the lab, trying to make it a part of me
> that I visit on a regular basis. When I was in Taekwon-Do I found that the
> more time I spent in visualization the better I got. It goes beyond just
> "seeing it", but a total emersion in the expeirence. And this is what I have
> been trying to do with the lab, so a little more detail will help me fill
> out my vision... NDA permiting, what can be asked of the proctor?
> 
For a little visualization, point your browser to
http://www.tara.ca/ourlabs/ccie.html and peak at Halifax.
They're redesigned their site -- they used to have a Quicktime 360 degree
"movie" of the lab.  Back when I was still teaching CCIE prep classes
I used to show it to people.  It helped take the edge off of the unknown.

  Marty Adkins Email: [EMAIL PROTECTED]
  Mentor Technologies  Phone: 240-568-6526
  133 National Business Pkwy   WWW: http://www.mentortech.com
  Annapolis Junction, MD  20701Cisco CCIE #1289
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: OSPF virtual links

[Arthur Simplina]

My comments follow below. Please let me know how it worked out.


---
> >OSPF virtual links. Here's my configs: > >R2503 - backbone router 
> >hostname r2503 >!


> >router ospf 100 >network 192.1.1.1 0.0.0.0 area 0 
> >--

Please change your config to:
   router ospf 100
   network 192.1.1.0 0.0.0.255 area 0


---

> >R2523- backbone router, link between R2503 & R4000 >hostname r2523


> >router ospf 100 >area 1 virtual-link 3.3.3.3 >network 192.1.1.2 0.0.0.0 
>area 0 >network 193.1.1.2 0.0.0.0 area 1 > 
> >-

For R2523, please change your config to:
  router ospf 100
  area 1 virtual-link 3.3.3.3
  network 192.1.1.0 0.0.0.255 area 0
  network 193.1.1.0 0.0.0.255 area 1

---

> > >R4000, in areas 1 & 4, has a virtual link through R2523 >hostname r4000

> >router ospf 100 >network 152.1.1.1 0.0.0.0 area 4 >network 193.1.1.1 
>0.0.0.0 area 1 >area 1 virtual-link 2.2.2.2 >!
-

For R4000, please change your config to:
   router ospf 100
   network 152.1.1.0 0.0.0.255 area 4
   network 193.1.1.0 0.0.0.255 area 1
   area 1 virtual-link 2.2.2.2

---
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_
Get your FREE download of MSN Explorer at http://explorer.msn.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: OSPF virtual links

[Stefan Dozier]

At 03:59 PM 4/7/01 -0400, Fred Danson wrote:

>interface Serial0
>ip address 192.1.1.1 255.255.255.0
>no ip directed-broadcast
>ip ospf interface-retry 0  < see CCO link below
>no ip mroute-cache
>no fair-queue


http://www.cisco.com/warp/public/104/28.shtml


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

Re: Cisco IOS Documentation: How useful is it, really?

[Circusnuts]

http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1228062723

This is the best IOS & command reference I know of.  I've purchased the
11.0(22) release a few years ago & now one of these 12.1's.  I can think of
no better way to master Cisco IOS.

Phil

- Original Message -
From: "EA Louie" <[EMAIL PROTECTED]>
To: "Control Program" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, April 08, 2001 7:33 PM
Subject: Re: Cisco IOS Documentation: How useful is it, really?


> - Original Message -
> From: Control Program <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, April 08, 2001 8:36 AM
> Subject: Cisco IOS Documentation: How useful is it, really?
>
>
> > I'm interested in thoughts and opinions on the practical utility of the
> > official Cisco IOS Configuration Guides and Command References available
> in
> > print, on CCO, and on the documentation CD-ROMs that ship with Cisco
> > products.  There have been a number of allusions on and off this list to
> the
> > importance (or even necessity) of studying the official docs if "you're
> > serious about CCIE preparation."  I even recall seeing some advice given
> by
> > someone that one should read the entire set of configuration guides and
> > command references before attempting the lab exam.
> >
> First off, the "practical utility" for the IOS Config guides is in the
> configuration of the devices (duh), and not for light reading unless you
> have a photographic memory (which actually might be a detriment ;-)
>
> If you've ever put together a configuration for multiple routers (for
> example, even a small 5 site WAN), you discover that the parameters set on
> one device are dependent on its neighbors, and that if you don't get the
> commands right, the results that you want will not be realized.  Sometimes
> it can be easy (point-to-point T1's and RIP all using fixed subnet masks),
> but the complexity rises as the routing protocol is implemented and
features
> required are added, and WAN technologies used.
>
> > How useful do you all find the IOS documentation, both with respect to
> CCIE
> > study, and in general?
> >
> VERY.  You go to http://www.cisco.com and click on Training and
> Certifications.  From there, there are links that take you to the CCIE
> Blueprint, which lists a plethora (ad nauseum) of the material that you
need
> to be familiar with, and it is NOT all Cisco documentation.  But there are
> lots of links to Cisco IOS Documentation there, and some good white
papers,
> too.
>
> > Have you succeeded in using it to learn to configure services you were
> > previously unfamiliar with, or is it just useful as a reference once you
> > already mainly know what you're doing?  Is it even useful as a
reference?
> >
> Yes - ergo ATM (LANE) and LECS/LES/BUS configuration at a router and ATM
> switch level (two different devices, two different IOSes).  Also, the
> interface buffers (queuing commands), and it has really helped me in my
BGP
> configurations and in route redistribution.  Again, if you haven't had
> experience on the console, its almost impossible to study the
configuration
> guides except to get familiar with how these device commands are entered.
>
> Many times, the configuration examples at the bottom of the Config Guides
> are good starting points, but don't provide sufficient detail to solve my
> particular problem.  Knowing the context of a router (one big ARP table)
> helps alot, and knowing the capabilities and limitations of the router in
> terms of filtering and traffic movement also help.  Interface-specific
> commands versus global commands also proves to be valuable, because it
gives
> me a reference point to search the documentation.
>
> >
> > My own thoughts:
> >
> > I ask because I find the IOS documentation hard to digest at best, and
> > actively confusing at worst.  I use it frequently, but almost
exclusively
> as
> > a reference to look up command options and syntax details.  Even then,
> half
> > the time I find that there either isn't enough detail in the manual to
> > answer the question I have, or there's so much detail that the
information
> > I'm looking for is buried in an avalanche of optional parameters and
> > unrelated features.  The idea of resorting to the IOS documentation to,
> say,
> > learn how to set up async and ISDN interfaces using a combination of
> static
> > and dynamic addressing to support user dialin and backup/DDR functions
on
> an
> > access server makes my blood run cold.  It could be done - eventually -
> but
> > it would require piecing the information together from eight different
> > chapters, one of which would provide 200 pages of information just on
PPP,
> > another of which would provide 150 pages of information on ISDN
signaling,
> > and so on.
> >
> If you're just reading the configuration guides without live equipment to
> see what the config command does, then it *is* confusing at best,
> frustrating at worst.  I've studied the configuratio

Re: Cisco IOS Documentation: How useful is it, really?

[EA Louie]

- Original Message -
From: Control Program <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 08, 2001 8:36 AM
Subject: Cisco IOS Documentation: How useful is it, really?


> I'm interested in thoughts and opinions on the practical utility of the
> official Cisco IOS Configuration Guides and Command References available
in
> print, on CCO, and on the documentation CD-ROMs that ship with Cisco
> products.  There have been a number of allusions on and off this list to
the
> importance (or even necessity) of studying the official docs if "you're
> serious about CCIE preparation."  I even recall seeing some advice given
by
> someone that one should read the entire set of configuration guides and
> command references before attempting the lab exam.
>
First off, the "practical utility" for the IOS Config guides is in the
configuration of the devices (duh), and not for light reading unless you
have a photographic memory (which actually might be a detriment ;-)

If you've ever put together a configuration for multiple routers (for
example, even a small 5 site WAN), you discover that the parameters set on
one device are dependent on its neighbors, and that if you don't get the
commands right, the results that you want will not be realized.  Sometimes
it can be easy (point-to-point T1's and RIP all using fixed subnet masks),
but the complexity rises as the routing protocol is implemented and features
required are added, and WAN technologies used.

> How useful do you all find the IOS documentation, both with respect to
CCIE
> study, and in general?
>
VERY.  You go to http://www.cisco.com and click on Training and
Certifications.  From there, there are links that take you to the CCIE
Blueprint, which lists a plethora (ad nauseum) of the material that you need
to be familiar with, and it is NOT all Cisco documentation.  But there are
lots of links to Cisco IOS Documentation there, and some good white papers,
too.

> Have you succeeded in using it to learn to configure services you were
> previously unfamiliar with, or is it just useful as a reference once you
> already mainly know what you're doing?  Is it even useful as a reference?
>
Yes - ergo ATM (LANE) and LECS/LES/BUS configuration at a router and ATM
switch level (two different devices, two different IOSes).  Also, the
interface buffers (queuing commands), and it has really helped me in my BGP
configurations and in route redistribution.  Again, if you haven't had
experience on the console, its almost impossible to study the configuration
guides except to get familiar with how these device commands are entered.

Many times, the configuration examples at the bottom of the Config Guides
are good starting points, but don't provide sufficient detail to solve my
particular problem.  Knowing the context of a router (one big ARP table)
helps alot, and knowing the capabilities and limitations of the router in
terms of filtering and traffic movement also help.  Interface-specific
commands versus global commands also proves to be valuable, because it gives
me a reference point to search the documentation.

>
> My own thoughts:
>
> I ask because I find the IOS documentation hard to digest at best, and
> actively confusing at worst.  I use it frequently, but almost exclusively
as
> a reference to look up command options and syntax details.  Even then,
half
> the time I find that there either isn't enough detail in the manual to
> answer the question I have, or there's so much detail that the information
> I'm looking for is buried in an avalanche of optional parameters and
> unrelated features.  The idea of resorting to the IOS documentation to,
say,
> learn how to set up async and ISDN interfaces using a combination of
static
> and dynamic addressing to support user dialin and backup/DDR functions on
an
> access server makes my blood run cold.  It could be done - eventually -
but
> it would require piecing the information together from eight different
> chapters, one of which would provide 200 pages of information just on PPP,
> another of which would provide 150 pages of information on ISDN signaling,
> and so on.
>
If you're just reading the configuration guides without live equipment to
see what the config command does, then it *is* confusing at best,
frustrating at worst.  I've studied the configuration guides without
equipment around, but I also have the benefit of setting up lots of
equipment, so when the config guide refers to a command, I know the basic
context of why it needs to be done.  Much of the configuration can be trial
and error, much like any other programmable device, as they don't put every
possible combination of every command into the config guides, but that's why
the TAC has resorted to providing sample configurations which are now very
well documented:
http://www.cisco.com/public/technotes/serv_tips.shtml

As far as detail is concerned, I agree with you that there often is a big
(sometimes HUGE) disconnect between the config gu

Re: OSPF virtual links

[Stefan Dozier]

At 03:59 PM 4/7/01 -0400, Fred Danson wrote:

Fred I setup Lab #30 just to see if I would experience the same thing,
and initially I did, until I rebooted RouterA (your R2503). 
Somehow rebooting allowed reachability and I was able to ping
the 152.1.1.1 address (actaully I used 192.168.104.3).

I also noticed the "ip ospf interface-retry 0" on several interfaces
in your config, I had them in mine's also. I gotta look that one up
but I suspect that it appears in the config because the opposite side
of the link hasn't been initialized or configured yet!

After I deleted all the "ip ospf interface-retry 0" entries off the
interface configs and rebooted all three routers, I still have
reachibility to 192.168.104.3 (your 152.1.1.1) and also found 
that network 192.168.104.0 (your 152.1.0.0) is in the routing 
table of RouterB (your 2523).

I have all the router configs and sh commands as well as the 
capture of the successful ping, but I'll reserve posting them
to save bandwidth until I hear if you rebooted and cleaned up
the configs and your problem still exist.

Stefan


>Hey group,
>
>I am in the middle of Lab #30 from the CCIE Lab Study Guide which involves 
>OSPF virtual links. Here's my configs:
>
>R2503 - backbone router
>hostname r2503
>!
>!
>ip subnet-zero
>!
>!
>!
>interface Loopback0
>ip address 1.1.1.1 255.255.255.0
>no ip directed-broadcast
>!
>interface Ethernet0
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial0
>ip address 192.1.1.1 255.255.255.0
>no ip directed-broadcast
>ip ospf interface-retry 0
>no ip mroute-cache
>no fair-queue
>!
>interface Serial1
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface BRI0
>no ip address
>no ip directed-broadcast
>shutdown
>!
>router ospf 100
>network 192.1.1.1 0.0.0.0 area 0
>!
>ip classless
>!
>!
>!
>line con 0
>transport input none
>line aux 0
>line vty 0 4
>!
>end
>
>--
>
>R2523- backbone router, link between R2503 & R4000
>hostname r2523
>!
>!
>ip subnet-zero
>!
>!
>!
>interface Loopback0
>ip address 2.2.2.2 255.255.255.0
>no ip directed-broadcast
>!
>interface Serial0
>ip address 193.1.1.2 255.255.255.0
>no ip directed-broadcast
>ip ospf interface-retry 0
>no ip mroute-cache
>no fair-queue
>!
>interface Serial1
>ip address 192.1.1.2 255.255.255.0
>no ip directed-broadcast
>ip ospf interface-retry 0
>clockrate 64000
>!
>interface Serial2
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial3
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial4
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial5
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial6
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial7
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial8
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface Serial9
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface TokenRing0
>no ip address
>no ip directed-broadcast
>shutdown
>!
>interface BRI0
>no ip address
>no ip directed-broadcast
>shutdown
>!
>router ospf 100
>area 1 virtual-link 3.3.3.3
>network 192.1.1.2 0.0.0.0 area 0
>network 193.1.1.2 0.0.0.0 area 1
>!
>ip classless
>!
>!
>!
>line con 0
>transport input none
>line aux 0
>line vty 0 4
>!
>end
>
>-
>
>R4000, in areas 1 & 4, has a virtual link through R2523
>hostname r4000
>!
>!
>!
>!
>interface Loopback0
>ip address 3.3.3.3 255.255.255.0
>!
>interface Ethernet0
>ip address 152.1.1.1 255.255.255.0
>no keepalive
>media-type 10BaseT
>!
>interface Serial0
>ip address 193.1.1.1 255.255.255.0
>no ip mroute-cache
>no fair-queue
>clockrate 64000
>!
>interface Serial1
>no ip address
>shutdown
>!
>interface TokenRing0
>no ip address
>shutdown
>!
>router ospf 100
>network 152.1.1.1 0.0.0.0 area 4
>network 193.1.1.1 0.0.0.0 area 1
>area 1 virtual-link 2.2.2.2
>!
>ip classless
>!
>!
>!
>line con 0
>line aux 0
>line vty 0 4
>login
>!
>end
>
>-
>
>the virtual link seems to be working fine. Here's a paste of
>show ip ospf virtual-link from r2523
>r2523#show ip ospf vir
>Virtual Link OSPF_VL0 to router 3.3.3.3 is up
>  Run as demand circuit
>  DoNotAge LSA allowed.
>  Transit area 1, via interface Serial0, Cost of using 64
>  Transmit Delay is 1 sec, State POINT_TO_POINT,
>  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
>Hello due in 00:00:01
>Adjacency State FULL (Hello suppressed)
>
>Here's a paste of show ip ospf virtual-link from r4000
>r4000#show ip ospf vir
>Virtual Link OSPF_VL0 to router 2.2.2.2 is up
>  Run as demand circuit
>  DoNotAge LSA allowed.
>  Transit area 1, via interface Serial0, Cost of using 64
>  Transmit Delay is 1 sec, State POINT_TO_POINT,
>  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
>Hello due in 00:00:03
>Adjacency State FULL (Hello suppressed)
>
>Here's the problem. I cannot

Re: ccna/ccnp presentations

[Howard C. Berkowitz]

>hi,
>
>can anyone tell me where can i get( buy) the power point presentations used
>for teaching ccnp and ccna in the class room.
>are the available to cisco training partners only.?


Correct. Training partners only.,

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

Re: CCIE Lab Report - unsuccesful

[Tim Ross]

Chuck,

I am surprised that you didn't pass on the first attempt (you're scaring
me). But I also think that it is an important part of the process. My first
attempt will be in August. Failing the Lab makes us see the value and
difficulty of the lab; appreciate the level of expertise required to pass;
and the only way this certification can hold its value in the future. You
said that you could do everything in the lab, but overlooked some simple
things that kept you out of Day 2. It might be something completely
different for me, but the Lab is where we find these things out, so we will
be detail oriented, and at a consistent level of expertise when passing the
lab.

Study hard and good luck,

Tim


- Original Message -
From: "Chuck Larrieu" <[EMAIL PROTECTED]>
To: "Cisco Mail List" <[EMAIL PROTECTED]>
Sent: Saturday, April 07, 2001 6:34 PM
Subject: CCIE Lab Report - unsuccesful


> Hey, everyone, how you all been?
>
> The short story is I did not make it to day 2. The rest of this is a bit
> long winded, and easily skipped.
>
> First of all, I was quite pleased to find upon reading through my Day 1
> scenario that there was nothing I couldn't do, given time. There are
plenty
> of practice labs from several different sources which cover all the core
> topics, so there were no surprises for me.
>
> Secondly, I was quite pleased when during my review of Day 1 results with
> the proctor,  he told me they were going to change the written instruction
> on a particular section because of the solution I used. I'm actually quite
> surprised it hasn't been done before. I was grudgingly given points,
> although I was told my solution was definitely not what they had in mind.
>
> However, in the end,  it was a few simple omissions that cost me the
points
> I would have needed to squeak into Day 2.
>
> Only one of the six of us who began together was invited to the second
day.
>
> Things I learned:
>
> 1) having the core topics down cold is CRUCIAL. No kidding!
>
> 2) Time is crucial, but not, I believe, in the way I have seen it
discussed
> in many places. I highly doubt that typing 80 words a minute versus my 20
> WPM was the difference. Not when I spent as much time as I did
> contemplating. You  can't think it. You have to know it.
>
> By 2:00 p.m. I knew I didn't have a prayer of hitting all the
requirements.
> At that point I started counting points, putting myself in a defensive
mode.
> By quitting time, if I got full credit for everything I thought I
deserved,
> I would have had 31 points. As I found out in my review, I missed a few
> simple things, and blew myself out of the water. This leads back to the
> internalization of the core topics. You can't be thinking about how to
> configure anything. You have to just bang them out, the same way you bang
> out shaving or washing your hands or eating your lunch.
>
> 3) Methodology is crucial. You have to have a good methodology that is
> internalized and is habitual. You can't be thinking "what's next?" I don't
> believe it matters what your methodology is, so long as you are consistent
> and quick. My own methodology failed me because I was constantly
adjusting,
> rather than banging it out.
>
> 4) I spent a good two hours last night in my hotel room debriefing myself.
I
> have six pages of notes regarding my day one experience. This will form
the
> basis of my study plan for my second attempt.  I know that it is highly
> unlikely I will have a scenario like the one I just worked on next time
> through. But I will focus on methodology and speed.
>
> 5) Good rapport with the proctor is helpful. I was able to get the
> information I needed by carefully wording my questions and making sure
that
> my desired result was understood. The proctor is under a bit of stress
> himself, with so many folks vying for his attention. He may think you are
> asking something you are not. I made sure that if I was not getting an
> answer that made sense that I clarified my request, so that the answer was
> one that helped me understand.  I will say also that the test I saw was
> reasonably clear. The questions I had tended to be the result of outputs
> from various show and debug commands, to clarify what the expectation was.
>
> A few other comments:
>
> I was far too aggressive in scheduling my lab date.  Should have pushed it
> out 60 days. Don't be in a hurry. Those without a lot of hands on need to
> spend several months of several hours a day practicing. No two ways about
> it.
>
> There has been a lot of discussion about the patch panels used in the lab.
> All I can say is that the panels are clearly labeled. IMHO you have
nothing
> to worry about. That said, I did have to revisit the rack twice, in order
to
> make a cabling change. This was purely the result of a chicken or egg
> situation, and not due to any difficulty with the rack itself. People with
> home labs know well the issue with hooking up routers back to back.
>
> I sat next to a guy this morning ( a day 

Re: CCIE Lab Report - unsuccesful

[Lou Nelson]

Chuck,
Thank You.  Over the past year + you have been a mentor (and Joe) to many of
us.  As you had success, many of us were inspired.  I know I was always a
few steps behind ya... with the NA then NP then DA then DP... now I just got
my ATM specialization so on to the written.  But thru all this you have
inspired.  Now , you inspire not with success but by being positive when it
would be easy to get negative and push blame every where else.  Stay in
there... there are many of us lurkers (I do post on occasion) wishing the
best for you!

Lou





""Chuck Larrieu"" <[EMAIL PROTECTED]> wrote in message
000d01c0bfcc$08c90800$[EMAIL PROTECTED]">news:000d01c0bfcc$08c90800$[EMAIL PROTECTED]...
> Hey, everyone, how you all been?
>
> The short story is I did not make it to day 2. The rest of this is a bit
> long winded, and easily skipped.
>
> First of all, I was quite pleased to find upon reading through my Day 1
> scenario that there was nothing I couldn't do, given time. There are
plenty
> of practice labs from several different sources which cover all the core
> topics, so there were no surprises for me.
>
> Secondly, I was quite pleased when during my review of Day 1 results with
> the proctor,  he told me they were going to change the written instruction
> on a particular section because of the solution I used. I'm actually quite
> surprised it hasn't been done before. I was grudgingly given points,
> although I was told my solution was definitely not what they had in mind.
>
> However, in the end,  it was a few simple omissions that cost me the
points
> I would have needed to squeak into Day 2.
>
> Only one of the six of us who began together was invited to the second
day.
>
> Things I learned:
>
> 1) having the core topics down cold is CRUCIAL. No kidding!
>
> 2) Time is crucial, but not, I believe, in the way I have seen it
discussed
> in many places. I highly doubt that typing 80 words a minute versus my 20
> WPM was the difference. Not when I spent as much time as I did
> contemplating. You  can't think it. You have to know it.
>
> By 2:00 p.m. I knew I didn't have a prayer of hitting all the
requirements.
> At that point I started counting points, putting myself in a defensive
mode.
> By quitting time, if I got full credit for everything I thought I
deserved,
> I would have had 31 points. As I found out in my review, I missed a few
> simple things, and blew myself out of the water. This leads back to the
> internalization of the core topics. You can't be thinking about how to
> configure anything. You have to just bang them out, the same way you bang
> out shaving or washing your hands or eating your lunch.
>
> 3) Methodology is crucial. You have to have a good methodology that is
> internalized and is habitual. You can't be thinking "what's next?" I don't
> believe it matters what your methodology is, so long as you are consistent
> and quick. My own methodology failed me because I was constantly
adjusting,
> rather than banging it out.
>
> 4) I spent a good two hours last night in my hotel room debriefing myself.
I
> have six pages of notes regarding my day one experience. This will form
the
> basis of my study plan for my second attempt.  I know that it is highly
> unlikely I will have a scenario like the one I just worked on next time
> through. But I will focus on methodology and speed.
>
> 5) Good rapport with the proctor is helpful. I was able to get the
> information I needed by carefully wording my questions and making sure
that
> my desired result was understood. The proctor is under a bit of stress
> himself, with so many folks vying for his attention. He may think you are
> asking something you are not. I made sure that if I was not getting an
> answer that made sense that I clarified my request, so that the answer was
> one that helped me understand.  I will say also that the test I saw was
> reasonably clear. The questions I had tended to be the result of outputs
> from various show and debug commands, to clarify what the expectation was.
>
> A few other comments:
>
> I was far too aggressive in scheduling my lab date.  Should have pushed it
> out 60 days. Don't be in a hurry. Those without a lot of hands on need to
> spend several months of several hours a day practicing. No two ways about
> it.
>
> There has been a lot of discussion about the patch panels used in the lab.
> All I can say is that the panels are clearly labeled. IMHO you have
nothing
> to worry about. That said, I did have to revisit the rack twice, in order
to
> make a cabling change. This was purely the result of a chicken or egg
> situation, and not due to any difficulty with the rack itself. People with
> home labs know well the issue with hooking up routers back to back.
>
> I sat next to a guy this morning ( a day 1 candidate ) who was getting up
> every few minutes and going to the back of the rack to move cables around.
> Completely unnecessary and driving the proctor nuts. There is no need for
> any candidate to

Re: BSCN Exam

[Rick Cossey]

I would study Scalable Cisco Networks..
I would also have started by looking at the
course on www.cisco.com, but then again that would
require work on your part
Rick
"Chiao Liang" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi All
>
> I will be taking my BSCN in 3 weeks times, so would like to know what
> should i study for? or is there any other materials i can get from the
> web.
>
> Thank, with regards
> Chan
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

RE: Cisco IOS Documentation: How useful is it, really?

[Urooj's Hi-speed Internet]

Well if you have a desire to pass the CCIE Lab, I think it would be very
difficult, shall I say virtually impossible, to sail through without a fair
command over Cisco IOS Configuration Guides and Command References. I
realize that it may be very difficult to remember every bit of it, but the
ability to navigate to where a feature is located and to retreive it quickly
may make the difference between pass and fail. In my case I never studied
Bruce Caslow's book or Jeff Doyle's (Routing TCP/IP) but still managed to
pass. So, it all depends, if you skip Cisco IOS Configuration Guides and
Command References, the sailing may not be very smooth.

Aziz S. Islam

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Control Program
Sent: Sunday, April 08, 2001 11:37 AM
To: [EMAIL PROTECTED]
Subject: Cisco IOS Documentation: How useful is it, really?


I'm interested in thoughts and opinions on the practical utility of the
official Cisco IOS Configuration Guides and Command References available in
print, on CCO, and on the documentation CD-ROMs that ship with Cisco
products.  There have been a number of allusions on and off this list to the
importance (or even necessity) of studying the official docs if "you're
serious about CCIE preparation."  I even recall seeing some advice given by
someone that one should read the entire set of configuration guides and
command references before attempting the lab exam.

How useful do you all find the IOS documentation, both with respect to CCIE
study, and in general?

Have you succeeded in using it to learn to configure services you were
previously unfamiliar with, or is it just useful as a reference once you
already mainly know what you're doing?  Is it even useful as a reference?


My own thoughts:

I ask because I find the IOS documentation hard to digest at best, and
actively confusing at worst.  I use it frequently, but almost exclusively as
a reference to look up command options and syntax details.  Even then, half
the time I find that there either isn't enough detail in the manual to
answer the question I have, or there's so much detail that the information
I'm looking for is buried in an avalanche of optional parameters and
unrelated features.  The idea of resorting to the IOS documentation to, say,
learn how to set up async and ISDN interfaces using a combination of static
and dynamic addressing to support user dialin and backup/DDR functions on an
access server makes my blood run cold.  It could be done - eventually - but
it would require piecing the information together from eight different
chapters, one of which would provide 200 pages of information just on PPP,
another of which would provide 150 pages of information on ISDN signaling,
and so on.

I just can't imagine the official documentation as the preferred means to
learn to do something new.  Should you be familiar with the structure and
contents?  Of course.  It's still the last word when it comes to resolving
ambiguities or finding information on that one option you knew was there but
couldn't remember the keyword for.  Is it time well-spent to sit there and
study these manuals as an attempt to increase your knowledge and
proficiency?  Not in my experience.  That's not to say you won't learn
anything by doing it - just that there are better ways to use your time.

Comments encouraged!  Maybe some of you have actually devised a way to
triage the documentation and learn a lot from it despite the way it's
organized.  If so, I'd love to hear your strategies.


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

RE: CCIE Lab Report - unsuccesful

[Urooj's Hi-speed Internet]

Hi Chuck,
Thanks for taking the time to narrate your candid and thorough post-lab
experiences. The outcome should not discourage you as the whole group
remains impressed with your wealth of knowledge, the desire to know more,
and your fine power of expression. I have been there too, and finally sailed
through. Believe me, the pleasure of conquering it would be immense. Just
hang-in there without losing your sense of direction and you will succeed.
Best of luck.

Aziz S. Islam
All the CCXX (Routing & Switching)

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Chuck Larrieu
Sent: Saturday, April 07, 2001 9:34 PM
To: Cisco Mail List
Subject: CCIE Lab Report - unsuccesful


Hey, everyone, how you all been?

The short story is I did not make it to day 2. The rest of this is a bit
long winded, and easily skipped.

First of all, I was quite pleased to find upon reading through my Day 1
scenario that there was nothing I couldn't do, given time. There are plenty
of practice labs from several different sources which cover all the core
topics, so there were no surprises for me.

Secondly, I was quite pleased when during my review of Day 1 results with
the proctor,  he told me they were going to change the written instruction
on a particular section because of the solution I used. I'm actually quite
surprised it hasn't been done before. I was grudgingly given points,
although I was told my solution was definitely not what they had in mind.

However, in the end,  it was a few simple omissions that cost me the points
I would have needed to squeak into Day 2.

Only one of the six of us who began together was invited to the second day.

Things I learned:

1) having the core topics down cold is CRUCIAL. No kidding!

2) Time is crucial, but not, I believe, in the way I have seen it discussed
in many places. I highly doubt that typing 80 words a minute versus my 20
WPM was the difference. Not when I spent as much time as I did
contemplating. You  can't think it. You have to know it.

By 2:00 p.m. I knew I didn't have a prayer of hitting all the requirements.
At that point I started counting points, putting myself in a defensive mode.
By quitting time, if I got full credit for everything I thought I deserved,
I would have had 31 points. As I found out in my review, I missed a few
simple things, and blew myself out of the water. This leads back to the
internalization of the core topics. You can't be thinking about how to
configure anything. You have to just bang them out, the same way you bang
out shaving or washing your hands or eating your lunch.

3) Methodology is crucial. You have to have a good methodology that is
internalized and is habitual. You can't be thinking "what's next?" I don't
believe it matters what your methodology is, so long as you are consistent
and quick. My own methodology failed me because I was constantly adjusting,
rather than banging it out.

4) I spent a good two hours last night in my hotel room debriefing myself. I
have six pages of notes regarding my day one experience. This will form the
basis of my study plan for my second attempt.  I know that it is highly
unlikely I will have a scenario like the one I just worked on next time
through. But I will focus on methodology and speed.

5) Good rapport with the proctor is helpful. I was able to get the
information I needed by carefully wording my questions and making sure that
my desired result was understood. The proctor is under a bit of stress
himself, with so many folks vying for his attention. He may think you are
asking something you are not. I made sure that if I was not getting an
answer that made sense that I clarified my request, so that the answer was
one that helped me understand.  I will say also that the test I saw was
reasonably clear. The questions I had tended to be the result of outputs
from various show and debug commands, to clarify what the expectation was.

A few other comments:

I was far too aggressive in scheduling my lab date.  Should have pushed it
out 60 days. Don't be in a hurry. Those without a lot of hands on need to
spend several months of several hours a day practicing. No two ways about
it.

There has been a lot of discussion about the patch panels used in the lab.
All I can say is that the panels are clearly labeled. IMHO you have nothing
to worry about. That said, I did have to revisit the rack twice, in order to
make a cabling change. This was purely the result of a chicken or egg
situation, and not due to any difficulty with the rack itself. People with
home labs know well the issue with hooking up routers back to back.

I sat next to a guy this morning ( a day 1 candidate ) who was getting up
every few minutes and going to the back of the rack to move cables around.
Completely unnecessary and driving the proctor nuts. There is no need for
any candidate to touch the back of the rack.

You can't let little stuff stop you. Those with extensive hands on
experience know that 

Re: CCIE Lab Report - unsuccesful

[Cisco Kidd]

Sorry about that Chuck...I dont know you but after reading this I can
feel your pain. You will get it next time...

Thanks for the info. :-)

>From: "Chuck Larrieu" >Reply-To: "Chuck Larrieu" >To: "Cisco Mail List"
>Subject: CCIE Lab Report - unsuccesful >Date: Sat, 7 Apr 2001 18:34:20
-0700 > >Hey, everyone, how you all been? > >The short story is I did not
make it to day 2. The rest of this is a bit >long winded, and easily
skipped. > >First of all, I was quite pleased to find upon reading
through my Day 1 >scenario that there was nothing I couldn't do, given
time. There are plenty >of practice labs from several different sources
which cover all the core >topics, so there were no surprises for me. >
>Secondly, I was quite pleased when during my review of Day 1 results
with >the proctor, he told me they were going to change the written
instruction >on a particular section because of the solution I used. I'm
actually quite >surprised it hasn't been done before. I was grudgingly
given points, >although I was told my solution was definitely not what
they had in mind. > >However, in the end, it was a few simple omissions
that cost me the points >I would have needed to squeak into Day 2. >
>Only one of the six of us who began together was invited to the second
day. > >Things I learned: > >1) having the core topics down cold is
CRUCIAL. No kidding! > >2) Time is crucial, but not, I believe, in the
way I have seen it discussed >in many places. I highly doubt that typing
80 words a minute versus my 20 >WPM was the difference. Not when I spent
as much time as I did >contemplating. You can't think it. You have to
know it. > >By 2:00 p.m. I knew I didn't have a prayer of hitting all the
requirements. >At that point I started counting points, putting myself in
a defensive mode. >By quitting time, if I got full credit for everything
I thought I deserved, >I would have had 31 points. As I found out in my
review, I missed a few >simple things, and blew myself out of the water.
This leads back to the >internalization of the core topics. You can't be
thinking about how to >configure anything. You have to just bang them
out, the same way you bang >out shaving or washing your hands or eating
your lunch. > >3) Methodology is crucial. You have to have a good
methodology that is >internalized and is habitual. You can't be thinking
"what's next?" I don't >believe it matters what your methodology is, so
long as you are consistent >and quick. My own methodology failed me
because I was constantly adjusting, >rather than banging it out. > >4) I
spent a good two hours last night in my hotel room debriefing myself. I
>have six pages of notes regarding my day one experience. This will form
the >basis of my study plan for my second attempt. I know that it is
highly >unlikely I will have a scenario like the one I just worked on
next time >through. But I will focus on methodology and speed. > >5) Good
rapport with the proctor is helpful. I was able to get the >information I
needed by carefully wording my questions and making sure that >my desired
result was understood. The proctor is under a bit of stress >himself,
with so many folks vying for his attention. He may think you are >asking
something you are not. I made sure that if I was not getting an >answer
that made sense that I clarified my request, so that the answer was >one
that helped me understand. I will say also that the test I saw was
>reasonably clear. The questions I had tended to be the result of outputs
>from various show and debug commands, to clarify what the expectation
was. > >A few other comments: > >I was far too aggressive in scheduling
my lab date. Should have pushed it >out 60 days. Don't be in a hurry.
Those without a lot of hands on need to >spend several months of several
hours a day practicing. No two ways about >it. > >There has been a lot of
discussion about the patch panels used in the lab. >All I can say is that
the panels are clearly labeled. IMHO you have nothing >to worry about.
That said, I did have to revisit the rack twice, in order to >make a
cabling change. This was purely the result of a chicken or egg
>situation, and not due to any difficulty with the rack itself. People
with >home labs know well the issue with hooking up routers back to back.
> >I sat next to a guy this morning ( a day 1 candidate ) who was getting
up >every few minutes and going to the back of the rack to move cables
around. >Completely unnecessary and driving the proctor nuts. There is no
need for >any candidate to touch the back of the rack. > >You can't let
little stuff stop you. Those with extensive hands on >experience know
that sometimes routers do funny things like boot into >rommon> or behave
as if there is an extensive paste going on in the >configuration
dialogue. I have a router here at home that boots into rommon >once in a
while. A reload has always done the trick ( knock on wood ) >sometimes
leaning on control-C will stop a misbehaving configuration >dialogue. No

ccna/ccnp presentations

[umer khan]

hi,

can anyone tell me where can i get( buy) the power point presentations used
for teaching ccnp and ccna in the class room.
are the available to cisco training partners only.?

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

Found Cool Site for Cisco lab rental

[Paul Gorman]

Hello,
Found this great site for Cisco lab rental for telnet or walkin.
http://www.voxcomm.com

Also, selling Cisco gear at cost for training and study groups.
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: Router config

[Howard C. Berkowitz]

It's not clear to me what problem this configuration will solve.  RIP 
summarizes at classful boundaries anyway, so the 192.168.1.0/24 
network would be advertised to any other network (assuming 
auto-summary is not disabled).  This configuration would advertise 
the /24 supernet inside 192.168.1.0/24, but without any more 
information, how is that useful to anyone?

Hope I'm not venting too much, but there are lots of posts of single 
router configurations with questions "what does this do?"  Try to put 
this in perspective -- a router, in and of itself, doesn't do 
anything very interesting.  To understand the effects, I have to know 
more about the network into which the router is placed.  I need to 
know addressing assumptions, and whether the router connects to other 
routers -- and what THEY do.

>this *will* originate a route of 192.168.1.0/24 by injecting the static into
>RIP, but to properly summarise - ie only originate the aggregate address and
>not the more-specifics - you would need to filter the /30s associated with
>the serial interfaces with a distribute-list or route-map.  Unfortunately
>RIP doesn't have the inbuilt summarization capabilities of OSPF or IS-IS.
>
>Andy
>
>"Ping" wrote:
>>  it is way to summarize..
>>  that is what is being done by
>>
>>  router rip
>>  network 192.168.1.0
>>  redistribute static
>>  !
>>  ip route 192.168.1.0 255.255.255.0 loopback 0
>>
>>  Hunt Lee wrote:
>>
>>  > I don't understand the following routing configs.  I understand that
>>  > redistribute static means it will redistribute static routes into RIP
>>  > network, but that's all I could see.  Can anybody please shed some light
>>  > on this?
>>  >
>>  > interface Serial 0
>>  > ip address 192.168.1.1 255.255.255.252
>>  > !
>>  > interface Serial 1
>>  > ip address 192.168.1.5 255.255.255.252
>>  > !
>>  > interface Serial 2
>>  > ip address 192.168.1.9 255.255.255.252
>>  > !
>>  > interface Serial 3
>>  > ip address 192.168.1.13 255.255.255.252
>>  > !
>>  > interface Serial 4
>>  > ip address 192.168.1.17 255.255.255.252
>>  > !
>>  > router rip
>>  > network 192.168.1.0
>>  > redistribute static
>>  > !
>>  > ip route 192.168.1.0 255.255.255.0 loopback 0
>>  >
>>  > Regards,
>>  > Hunt Lee
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

RE: Cisco IOS Documentation: How useful is it, really?

[Chuck Larrieu]

Hint - during my review with the proctor after my recent failed attempt, the
proctor told me that in his opinion it was critical that one be familiar
with the configuration guides, and that one have practiced using the
configurations presented there.

Several folks who passed the lab first time through have said similar
things.

FWIW

Chuck

-Original Message-
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Control Program
Sent:   Sunday, April 08, 2001 8:37 AM
To: [EMAIL PROTECTED]
Subject:Cisco IOS Documentation: How useful is it, really?

I'm interested in thoughts and opinions on the practical utility of the
official Cisco IOS Configuration Guides and Command References available in
print, on CCO, and on the documentation CD-ROMs that ship with Cisco
products.  There have been a number of allusions on and off this list to the
importance (or even necessity) of studying the official docs if "you're
serious about CCIE preparation."  I even recall seeing some advice given by
someone that one should read the entire set of configuration guides and
command references before attempting the lab exam.

How useful do you all find the IOS documentation, both with respect to CCIE
study, and in general?

Have you succeeded in using it to learn to configure services you were
previously unfamiliar with, or is it just useful as a reference once you
already mainly know what you're doing?  Is it even useful as a reference?


My own thoughts:

I ask because I find the IOS documentation hard to digest at best, and
actively confusing at worst.  I use it frequently, but almost exclusively as
a reference to look up command options and syntax details.  Even then, half
the time I find that there either isn't enough detail in the manual to
answer the question I have, or there's so much detail that the information
I'm looking for is buried in an avalanche of optional parameters and
unrelated features.  The idea of resorting to the IOS documentation to, say,
learn how to set up async and ISDN interfaces using a combination of static
and dynamic addressing to support user dialin and backup/DDR functions on an
access server makes my blood run cold.  It could be done - eventually - but
it would require piecing the information together from eight different
chapters, one of which would provide 200 pages of information just on PPP,
another of which would provide 150 pages of information on ISDN signaling,
and so on.

I just can't imagine the official documentation as the preferred means to
learn to do something new.  Should you be familiar with the structure and
contents?  Of course.  It's still the last word when it comes to resolving
ambiguities or finding information on that one option you knew was there but
couldn't remember the keyword for.  Is it time well-spent to sit there and
study these manuals as an attempt to increase your knowledge and
proficiency?  Not in my experience.  That's not to say you won't learn
anything by doing it - just that there are better ways to use your time.

Comments encouraged!  Maybe some of you have actually devised a way to
triage the documentation and learn a lot from it despite the way it's
organized.  If so, I'd love to hear your strategies.


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

CAT4003 Switch behaviour

[Hussam Adili]

Hello all,

I have a cisco 4003 switch to which I plugged an Intrusion detection
system which is running in promiscuous mode. what I was expecting to see
is  only broadcast traffic and I was planning to do port mirroring to
monitor other network traffic..

The funny thing is that I could see all traffic moving back and forth
between machines on all ports. (Looks like a Hub behavior). I plugged in
a Sniffer Pro and I could see the same thing!!!

Any comments would be appreciated
--
Hussam N. Adili
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Cisco IOS Documentation: How useful is it, really?

[Control Program]

I'm interested in thoughts and opinions on the practical utility of the
official Cisco IOS Configuration Guides and Command References available in
print, on CCO, and on the documentation CD-ROMs that ship with Cisco
products.  There have been a number of allusions on and off this list to the
importance (or even necessity) of studying the official docs if "you're
serious about CCIE preparation."  I even recall seeing some advice given by
someone that one should read the entire set of configuration guides and
command references before attempting the lab exam.

How useful do you all find the IOS documentation, both with respect to CCIE
study, and in general?

Have you succeeded in using it to learn to configure services you were
previously unfamiliar with, or is it just useful as a reference once you
already mainly know what you're doing?  Is it even useful as a reference?


My own thoughts:

I ask because I find the IOS documentation hard to digest at best, and
actively confusing at worst.  I use it frequently, but almost exclusively as
a reference to look up command options and syntax details.  Even then, half
the time I find that there either isn't enough detail in the manual to
answer the question I have, or there's so much detail that the information
I'm looking for is buried in an avalanche of optional parameters and
unrelated features.  The idea of resorting to the IOS documentation to, say,
learn how to set up async and ISDN interfaces using a combination of static
and dynamic addressing to support user dialin and backup/DDR functions on an
access server makes my blood run cold.  It could be done - eventually - but
it would require piecing the information together from eight different
chapters, one of which would provide 200 pages of information just on PPP,
another of which would provide 150 pages of information on ISDN signaling,
and so on.

I just can't imagine the official documentation as the preferred means to
learn to do something new.  Should you be familiar with the structure and
contents?  Of course.  It's still the last word when it comes to resolving
ambiguities or finding information on that one option you knew was there but
couldn't remember the keyword for.  Is it time well-spent to sit there and
study these manuals as an attempt to increase your knowledge and
proficiency?  Not in my experience.  That's not to say you won't learn
anything by doing it - just that there are better ways to use your time.

Comments encouraged!  Maybe some of you have actually devised a way to
triage the documentation and learn a lot from it despite the way it's
organized.  If so, I'd love to hear your strategies.


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

Passes BSCN yesterday.

[Peter K]

It wasn't that bad.
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: CCIE Lab Report - unsuccesful

[W. Alan Robertson]

Chuck,

Sorry to hear about the outcome of your practical exam.  Take solice in the fact
that so many people have to retake it.  It is a testament to the certification's
value, and to the ability of those that make it.  Persistance separates life's
winners from life's losers.  At some point, you'll get there, and the sense of
satifsafaction will be delicious.  :)

Speaking of persistance, I know a guy that bills himself as "The World's Worst
CCIE."  He took six attempts to pass the written exam, and then took six trips
to Raleigh for the practical.  He was not being sponsored by his employer
either...  That's $7200.00 in various exam fees alone, not including travel
costs.  I worked with him on a project for several months, and he was no dummy.
By my estimation, Murphy's law comes into play.  A lab candidate will invariably
draw the lab scenario for which he is least prepared.  That's just how it seems
to work out.

I read your report more than once, and with great interest.  Thanks for taking
the time to provide your insight and observations.  One of the frustrating
things about preparing for this, particularly gearing up for the first attempt,
is the uncertainty.

For instance, I'm pretty good at DLSw.  I've been fortunate enough to use it in
a very large production environment.  In my implementation, we used TCP
encapsulation exclusively, with static peering.  Is it enough that I know about
the other means of encapsulation, or dynamic peering?  My environment was SNA.
I haven't used it with NetBIOS...  Is the behavior identical?  Can I skip
preparing for DLSw because of my experience with it, or do I need to reserve
some of my precious time for DLSw experimentation?

Another example: I'm a whiz with Frame-Relay.  Until a week ago, I was in the
midst of a huge frame deployment, some 1500 sites.  That said, it was a fairly
vanilla environment.  Nothing special about it.  Looking for confidence, I was
looking at the Frame Configuration Guide on CCO last night, with the expectation
that I was gonna know most of it.  It was a big mistake.  There were so many
commands that I had never used, nor did I know they even existed.  I knew I'd
want to revisit frame the old fashioned way (I've been using
subinterface/point-to-point for so long, I hardly remember building frame-relay
maps by hand), and revist split horizons, but geeze...

I could spend from today until July (my 1st lab exam) covering these two topics,
topics that I feel good about, and still not get close to what I'd consider
"Full Mastery."

Understand that I'm not a paper anything.  I don't have my CCNA ot CCNP.  I
passed the written exam with virtually no studying, because I have been working
with Cisco routers since '94, and because I have never been satisfied knowing
how to do something without having a pretty good understanding of the how/why
what I was doing worked.  I came into this process with the expectation that
because of my background, I'd have a more difficult time with the esoteric
detail of the written exam than I would with the lab.  I am a hands-on guy.

Accounts, such as yours, are an invaluable resource to me, not because they
remove the uncertainty, but I feel like they help me manage the uncertainty.  I
hear what I need to hear: If you're good at what you do and you prepare
effectively, you can and will be successful.

Thanks.

Alan~

- Original Message -
From: "Chuck Larrieu" <[EMAIL PROTECTED]>
To: "Cisco Mail List" <[EMAIL PROTECTED]>
Sent: Saturday, April 07, 2001 9:34 PM
Subject: CCIE Lab Report - unsuccesful
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

BSCN Exam

[Chiao Liang]

Hi All

I will be taking my BSCN in 3 weeks times, so would like to know what
should i study for? or is there any other materials i can get from the
web.

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

Re: Router config

[andyh]

this *will* originate a route of 192.168.1.0/24 by injecting the static into
RIP, but to properly summarise - ie only originate the aggregate address and
not the more-specifics - you would need to filter the /30s associated with
the serial interfaces with a distribute-list or route-map.  Unfortunately
RIP doesn't have the inbuilt summarization capabilities of OSPF or IS-IS.

Andy

"Ping" wrote:
> it is way to summarize..
> that is what is being done by
>
> router rip
> network 192.168.1.0
> redistribute static
> !
> ip route 192.168.1.0 255.255.255.0 loopback 0
>
> Hunt Lee wrote:
>
> > I don't understand the following routing configs.  I understand that
> > redistribute static means it will redistribute static routes into RIP
> > network, but that's all I could see.  Can anybody please shed some light
> > on this?
> >
> > interface Serial 0
> > ip address 192.168.1.1 255.255.255.252
> > !
> > interface Serial 1
> > ip address 192.168.1.5 255.255.255.252
> > !
> > interface Serial 2
> > ip address 192.168.1.9 255.255.255.252
> > !
> > interface Serial 3
> > ip address 192.168.1.13 255.255.255.252
> > !
> > interface Serial 4
> > ip address 192.168.1.17 255.255.255.252
> > !
> > router rip
> > network 192.168.1.0
> > redistribute static
> > !
> > ip route 192.168.1.0 255.255.255.0 loopback 0
> >
> > Regards,
> > Hunt Lee
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

RE: Venting about another employee [was Re: Cisco Certs Becoming Paper CCXX - Senior Citizen Reply]

[Bob Vance]

What he said.
:)
I was about to fire off a missive, when I noticed that everything that I
wanted to say was contained herein(after, as well :), hereinafter
referred to as "content", said content solely the property of Greg,
hereinafter referred to, both on and off the "list" (see section 6.2.1,
subsection 3.b, paragraph 1) as "Old Guy", said content being wholly
derived, thunk up, and maintained by Old Guy.  All rights to content
remain with Old Guy, with no liability incurred by Old Guy for any
misuse, misunderstanding, or misrepresentation of said content.


-
Tks| 
BV | 
Sr. Technical Consultant,  SBM, A Gates/Arrow Co.
Vox 770-623-3430   11455 Lakefield Dr.
Fax 770-623-3429   Duluth, GA 30097-1511
=


> -Original Message-
> From: Greg Macaulay [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 03, 2001 9:30 AM
> To: The.Rock; [EMAIL PROTECTED]
> Subject: RE: Cisco Certs Becoming Paper CCXX - Senior Citizen Reply
>
>
> "certs don't prove anything" ??? I'm not sure that I can agree with
that
> statement. Certs IMHO represent an interest by the individual in the
subject
> matter, and a determined effort to undertake studies necessary to
become
> more knowledgeable.
>
> Certainly, obtaining a cert. does not make one a guru.  But it usually
> (albeit not all the time) indicates a person who has shown some
willingness
> to learn.  I view the knowledge I gained by studying for my certs as a
> foundation to be built upon over the coming years. Perhaps I have only
a
> passing or introductory knowledge of some subjects at this juncture --
but
I
> assume -- and I certainly hope that as every year passes, I will build
upon
> that foundation knowledge and at some point I will undergo a slow, but
> steady metamorphosis into a guru of sorts!  But at this juncture with
my
> certs, I would certainly agree that I have just enough knowledge to be
> dangerous! 
>
> I would compare the cert study to obtaining academic and professional
> degrees.  Certainly upon graduation, grads are not experts in any
area,
but
> they possess the fundamentals upon which to build.  A lawyer, for
example,
> may indeed represent any survivors of a plane crash is his/her back
yard
on
> the day he/she is admitted to the Bar, but law school graduation and
passing
> a Bar Examination DOES NOT indicate an expertise -- but it does
indicate
the
> individual has the foundational knowledge and the potential to become
an
> expert at some point in the future.  I would submit that the same goes
for
> physicians, accountants, architects, etc.
>
> I think that the real problem is how these certs. have been marketed.
> Instead of promising IMMEDIATE big bucks, the certs, should be an
entry
> ticket into this career.  Individuals who possess these certs should
be
> respected for the time, effort and interest they have shown in
studying
for
> and obtaining a cert.  But whether they are PAPER CERTS is truly a
> mischaracterization.  As I put forth above, every academic or
professional
> degree is indeed initially a paper cert -- but with potential.  IT
folks
who
> obtain these certs by and large have the potential to succeed.  Just
as
> there are bright, average and incompetent lawyers, doctors and others,
the
> same would hold true in our field.  Some individuals in inately
intuitive,
> without certs, and others -- the majority -- will become the average
IT
> Joe/Jane who work day-to-day in this field.  Certainly there will
always
be
> the small numbers who are totally incompetent.  But it is not because
the
> certs are merely paper.
>
> That's my 2 cents.
>
> Greg Macaulay, CCNP, CCDP, MCSE
> Attorney/Law Professor (Retired)
> Lifetime member of AARP
> Oldest CCNP/CCDP in existence
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Solaris

[Muhammad Alkhattab]

Hi  All you gurus,
I am about to take the exams of  Solaris 8 System Administration I & 11.Do
anyone have or know of anything site where there is Questions and
Answers.Thanks for your help.

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

RE: CCIE Lab Report - unsuccesful

[Bob Vance]

Well, this news is certainly a blow -- I felt as if *I* had failed :|

Of course, if it weren't hard, who'd want it?
When you pass the next time, it will be just that much more special :)

Thanks for sharing your thoughts.

You still da man, in my book!


-
Tks| 
BV | 
Sr. Technical Consultant,  SBM, A Gates/Arrow Co.
Vox 770-623-3430   11455 Lakefield Dr.
Fax 770-623-3429   Duluth, GA 30097-1511
=





-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Chuck Larrieu
Sent: Saturday, April 07, 2001 9:34 PM
To: Cisco Mail List
Subject: CCIE Lab Report - unsuccesful


Hey, everyone, how you all been?

The short story is I did not make it to day 2. The rest of this is a bit
long winded, and easily skipped.

First of all, I was quite pleased to find upon reading through my Day 1
scenario that there was nothing I couldn't do, given time. There are
plenty
of practice labs from several different sources which cover all the core
topics, so there were no surprises for me.

Secondly, I was quite pleased when during my review of Day 1 results
with
the proctor,  he told me they were going to change the written
instruction
on a particular section because of the solution I used. I'm actually
quite
surprised it hasn't been done before. I was grudgingly given points,
although I was told my solution was definitely not what they had in
mind.

However, in the end,  it was a few simple omissions that cost me the
points
I would have needed to squeak into Day 2.

Only one of the six of us who began together was invited to the second
day.

Things I learned:

1) having the core topics down cold is CRUCIAL. No kidding!

2) Time is crucial, but not, I believe, in the way I have seen it
discussed
in many places. I highly doubt that typing 80 words a minute versus my
20
WPM was the difference. Not when I spent as much time as I did
contemplating. You  can't think it. You have to know it.

By 2:00 p.m. I knew I didn't have a prayer of hitting all the
requirements.
At that point I started counting points, putting myself in a defensive
mode.
By quitting time, if I got full credit for everything I thought I
deserved,
I would have had 31 points. As I found out in my review, I missed a few
simple things, and blew myself out of the water. This leads back to the
internalization of the core topics. You can't be thinking about how to
configure anything. You have to just bang them out, the same way you
bang
out shaving or washing your hands or eating your lunch.

3) Methodology is crucial. You have to have a good methodology that is
internalized and is habitual. You can't be thinking "what's next?" I
don't
believe it matters what your methodology is, so long as you are
consistent
and quick. My own methodology failed me because I was constantly
adjusting,
rather than banging it out.

4) I spent a good two hours last night in my hotel room debriefing
myself. I
have six pages of notes regarding my day one experience. This will form
the
basis of my study plan for my second attempt.  I know that it is highly
unlikely I will have a scenario like the one I just worked on next time
through. But I will focus on methodology and speed.

5) Good rapport with the proctor is helpful. I was able to get the
information I needed by carefully wording my questions and making sure
that
my desired result was understood. The proctor is under a bit of stress
himself, with so many folks vying for his attention. He may think you
are
asking something you are not. I made sure that if I was not getting an
answer that made sense that I clarified my request, so that the answer
was
one that helped me understand.  I will say also that the test I saw was
reasonably clear. The questions I had tended to be the result of outputs
from various show and debug commands, to clarify what the expectation
was.

A few other comments:

I was far too aggressive in scheduling my lab date.  Should have pushed
it
out 60 days. Don't be in a hurry. Those without a lot of hands on need
to
spend several months of several hours a day practicing. No two ways
about
it.

There has been a lot of discussion about the patch panels used in the
lab.
All I can say is that the panels are clearly labeled. IMHO you have
nothing
to worry about. That said, I did have to revisit the rack twice, in
order to
make a cabling change. This was purely the result of a chicken or egg
situation, and not due to any difficulty with the rack itself. People
with
home labs know well the issue with hooking up routers back to back.

I sat next to a guy this morning ( a day 1 candidate ) who was getting
up
every few minutes and going to the back of the rack to move cables
around.
Completely unnecessary and driving the proctor nuts. There is no need
for
any candidate to touch the back of the rack.

You can't let litt

MCNS - ephemeral Pix commands?

[Dropped Packet]

Several commands on the PIX have "come and gone" over time.

Without getting into the NDA swamp, does anyone know if Cisco generally 
favors "older" or "newer" commands?

My concern is over some type of fill-in-the-blank command scenario where 
something like an ACCESS-LIST approach would be valid on one PIX version and 
using "OUTBOUND" would be valid on another.

TIA for any comments.





_
Get your FREE download of MSN Explorer at http://explorer.msn.com
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: SSRP question

[EA Louie]

CCO is a good resource for this - my search turned up these documents:
Sample SSRP Configuration:
http://www.cisco.com/warp/public/121/ssrpconfig.html

Configuring LAN Emulation-the section on Configure Fault Tolerant Operation
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/switc
h_c/xcprt7/xclane.htm

LAN Emulation and MPOA-the section on SSRP for Fault-Tolerant Operation of
LANE Server Components
http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_0/13_19/atg/lan
e.htm

and one of my favorites for overall SSRP/LANE implementation comes from the
Internetwork Design Guide-Designing ATM Internetworks
http://www.cisco.com/univercd/cc/td/doc/cisintwk/idg4/nd2008.htm

My local SE gave me a great PowerPoint presentation on SSRP during an
implementation a few years ago.  If I can still find it (it's hardcopy),
I'll scan it and send it to you offline.

For the FastEtherchannel at 800 Mbps (8 100M trunks is a lot of  ports to be
using between switches) being Gigabit,  it isn't.  Gigabit is 1000Mbps.

- Original Message -
From: Omer Ehsan Dar <[EMAIL PROTECTED]>
To: Cisco GroupStudy <[EMAIL PROTECTED]>
Sent: Friday, April 06, 2001 11:08 PM
Subject: SSRP question


> Hi all, I wanted to read up on SSSRP I could only find some stuff in
> Network Case studies but nothing except the word occuring in a couple of
> instances in Caslow or giles. Can somebody recommend some other source.
> Alos what would you term fast etherchannel as gigabit or not it is 800
> Megs?
> thanks
> Omer
_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Re: CCIE Lab Report - unsuccesful

[EA Louie]

Chuck - as a 2-time failer, I can empathize with you.  You sound like a real
trooper, and I'm very confident that *your* next time through will be
passing with flying colors.

Your #3 is extremely critical for anyone who takes the exam.  There are
moments (usually in the beginning of the test) where one asks themself
"WTF?", and if they stay there for too long, all the blood leaves the brain.
Therefore, that 15-25 minutes that you'd spend with methodology and keeping
with a plan is oh-so-critical.

Thanks very much for sharing your experience with us - hopefully, the other
CCIE lab hopefuls will be encouraged and keep studying hard for the lab.

-e-

- Original Message -
From: Chuck Larrieu <[EMAIL PROTECTED]>
To: Cisco Mail List <[EMAIL PROTECTED]>
Sent: Saturday, April 07, 2001 6:34 PM
Subject: CCIE Lab Report - unsuccesful


> Hey, everyone, how you all been?
>
> The short story is I did not make it to day 2. The rest of this is a bit
> long winded, and easily skipped.
>
> First of all, I was quite pleased to find upon reading through my Day 1
> scenario that there was nothing I couldn't do, given time. There are
plenty
> of practice labs from several different sources which cover all the core
> topics, so there were no surprises for me.
>
> Secondly, I was quite pleased when during my review of Day 1 results with
> the proctor,  he told me they were going to change the written instruction
> on a particular section because of the solution I used. I'm actually quite
> surprised it hasn't been done before. I was grudgingly given points,
> although I was told my solution was definitely not what they had in mind.
>
> However, in the end,  it was a few simple omissions that cost me the
points
> I would have needed to squeak into Day 2.
>
> Only one of the six of us who began together was invited to the second
day.
>
> Things I learned:
>
> 1) having the core topics down cold is CRUCIAL. No kidding!
>
> 2) Time is crucial, but not, I believe, in the way I have seen it
discussed
> in many places. I highly doubt that typing 80 words a minute versus my 20
> WPM was the difference. Not when I spent as much time as I did
> contemplating. You  can't think it. You have to know it.
>
> By 2:00 p.m. I knew I didn't have a prayer of hitting all the
requirements.
> At that point I started counting points, putting myself in a defensive
mode.
> By quitting time, if I got full credit for everything I thought I
deserved,
> I would have had 31 points. As I found out in my review, I missed a few
> simple things, and blew myself out of the water. This leads back to the
> internalization of the core topics. You can't be thinking about how to
> configure anything. You have to just bang them out, the same way you bang
> out shaving or washing your hands or eating your lunch.
>
> 3) Methodology is crucial. You have to have a good methodology that is
> internalized and is habitual. You can't be thinking "what's next?" I don't
> believe it matters what your methodology is, so long as you are consistent
> and quick. My own methodology failed me because I was constantly
adjusting,
> rather than banging it out.
>
> 4) I spent a good two hours last night in my hotel room debriefing myself.
I
> have six pages of notes regarding my day one experience. This will form
the
> basis of my study plan for my second attempt.  I know that it is highly
> unlikely I will have a scenario like the one I just worked on next time
> through. But I will focus on methodology and speed.
>
> 5) Good rapport with the proctor is helpful. I was able to get the
> information I needed by carefully wording my questions and making sure
that
> my desired result was understood. The proctor is under a bit of stress
> himself, with so many folks vying for his attention. He may think you are
> asking something you are not. I made sure that if I was not getting an
> answer that made sense that I clarified my request, so that the answer was
> one that helped me understand.  I will say also that the test I saw was
> reasonably clear. The questions I had tended to be the result of outputs
> from various show and debug commands, to clarify what the expectation was.
>
> A few other comments:
>
> I was far too aggressive in scheduling my lab date.  Should have pushed it
> out 60 days. Don't be in a hurry. Those without a lot of hands on need to
> spend several months of several hours a day practicing. No two ways about
> it.
>
> There has been a lot of discussion about the patch panels used in the lab.
> All I can say is that the panels are clearly labeled. IMHO you have
nothing
> to worry about. That said, I did have to revisit the rack twice, in order
to
> make a cabling change. This was purely the result of a chicken or egg
> situation, and not due to any difficulty with the rack itself. People with
> home labs know well the issue with hooking up routers back to back.
>
> I sat next to a guy this morning ( a day 1 candidate ) who was getting up
> every few minutes 

Catalyst 2800

[Sammi]

Hello all,
For study purposes, I've given a Catalyst 2800, with a couple more to
follow.
The problem is, no one has any idea of the configuration.
I don't have a serial cable, though can order one if need be. Can I
interface on port 25 for management purposes? Straight or cross-over
cable? And where am I to go from there? Do I get a sniffer so I can
discover the IP and then telnet or hyperterminal in?
Would like to experiment with VLANs but have to get the door open.

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