From: KK FoK (rgb98a@xxxxxxxxxxx)
Date: Fri Nov 23 2001 - 03:41:42 GMT-3
In that case I assume that on local frame-relay interface you do mapping to
local ip to allow pinging those local interfaces. If there is no local
mapping then the ping script will die rigth there.
In the lab I'm not sure if mapping to local ip is required when the
requirements said all interfaces should be pingabe from every router.
>From: "Charles Huang" <CharlesNY2000@Yahoo.Com>
>Reply-To: "Charles Huang" <CharlesNY2000@Yahoo.Com>
>To: "Wright, Jeremy" <JA_WRIGHT@admworld.com>, <ccielab@groupstudy.com>
>Subject: Re: CCIE #8431 Ping Script
>Date: Wed, 21 Nov 2001 20:55:20 -0500
>
>Basically ping script is just a ping command with a list of all the ip
>addresses on the network.
>
>for example if you setup router1 ethernet0 ip add 192.168.1.2, serial0 ip
>192.168.2.2 then you would
>put
>
>ping 192.168.1.2
>ping 192.168.2.2
>
>on your ping script ( type it in the notepad window ) when you setup more
>routers with more
>interfaces, just add the ip address to the list, including the loopback
>address. When you are all
>done with your IGP routing/redistribution. copy all the list you have and
>paste it in to your
>router console. then you would see the router starts to ping each IP
>address and it will die where
>the ping doesn't reply. one setting you need to change from the
>HyperTerminal is
>
>go to File > Properties > Settings > ASCII Setup > change line delay to
>250ms or 500ms
>
>on the lab is very hard to look in the routing table to vertify that every
>route came from the right
>source. it would be much faster just to run the ping script on every
>router to vertify the
>connectivity. but one bad thing about the ping script is that you can't
>vertify the route source.
>for example you suppose to learn a route from OSPF but instead you learned
>it from IGRP because IGRP
>has a better admin distance. this is the kind of things you need to
>watchout for when running the
>ping script.
>
>The following are some links on Cisco which I found very helpful. hope it
>will helps you too.
>
>Routing Protocols
>http://www.cisco.com/warp/public/619/index.shtml
>
>OSPF Technical Tips
>http://www.cisco.com/warp/public/104/index.shtml
>
>BGP Technical Tips
>http://www.cisco.com/warp/public/459/18.html
>
>IGRP/EIGRP Technical Tips
>http://www.cisco.com/warp/public/103/index.shtml
>
>NAT Technical Tips
>http://www.cisco.com/warp/public/556/index.shtml
>
>HSRP Technical Tips
>http://www.cisco.com/warp/public/619/index.shtml
>
>
>
>
>Charles
>
>
>
>
>----- Original Message -----
>From: "Wright, Jeremy" <JA_WRIGHT@admworld.com>
>To: "'Charles Huang'" <CharlesNY2000@yahoo.com>; <ccielab@groupstudy.com>
>Sent: Wednesday, November 21, 2001 9:15 AM
>Subject: RE: CCIE #8431
>
>
> > Congrats on your journey...could you possibly let me/us in on the ping
> > script. Thanks.
> >
> > -----Original Message-----
> > From: Charles Huang [mailto:CharlesNY2000@Yahoo.Com]
> > Sent: Tuesday, November 20, 2001 9:54 PM
> > To: ccielab@groupstudy.com
> > Subject: CCIE #8431
> >
> >
> > Finally it's my turn to write my CCIE experience.
> >
> > I passed the lab this Monday, the 19th at San Jose. This is my first
>time
> > taking the lab so I don't know how it is compare to the 2 day lab.
>Although
> > I
> > do think this lab is harder than the 2 day lab because on the 2 day lab
>you
> > need to score 55 out of 75 to get to the trouble shooting part. But if
>you
> > were to take the 1 day lab, 55 out of 75 = 73% that would fail the lab
> > already
> > (without the chance to trouble shoot). to score 80 points on the one
>day
> > lab
> > is like score 60 out of 75 on the 2 day lab before trouble shooting.
>And
> > most
> > people made it to trouble shooting, pass the lab. ( I guess the one
>didn't
> > pass were the one score between 55-60 ) Maybe this is one of the reason
> > Cisco
> > remove the trouble shooting part from the lab.
> >
> > This one day lab is kind of long. Every question is straight forward.
>If
> > you
> > don't understand a question. Ask the proctor right away. my proctor
>(Jose)
> > was very helpful and very professional. as always, ask the question in
>a
> > positive way. He helped me clarified many questions. I got more than
>half
> > of
> > the lab done by lunch time, but I miss one of questions. I didn't want
>to
> > go
> > back because I was afraid I won't have enough time. around 2pm I have
> > finish
> > all the exercises. and that calm me down alot. I go back to check the
> > question I miss, and It was one simple typo. I noticed one thing very
> > helpful
> > was the "ping script" -- I learned this trick from Bryan Cox (CCIE 8305)
>we
> > took the ECP1 class together -- after 2 and a half hours of checking my
> > work,
> > I'm pretty sure I pass.
> >
> > Here's the schedule I have for my lab in San Jose
> > 8:00-11:30 Lab
> > 11:30-12:00 Lunch ($10 coupon) get the chicken soup, it taste good. but
>dont
> > eat too much or you'll fall asleep in the afternoon
> > 12:00-4:30 Lab
> >
> > I had a total of 8 hours lab time.
> > The desk was kind of small about 4' x 30"
> > I notice some of my routers are still running 12.0 version, not 12.1
> > I heard T train IOS was not in the lab which is not true. I DO have a T
> > train
> > IOS
> > One of my router was very buggy. After I config one of the routing
> > protocols
> > I did a "show ip protocol" and nothing came up. I did a show run and
>the
> > config was there. I clear the routing protocol, and still no luck. I
>was
> > about to reboot the router then one thing came to my mind. I recall one
>of
> > the buggy T train IOS have this problem. So I did a show version, and
>It is
> > the exact same version. to resolve the problem you simply need to copy
>down
> > the routing protocol config. remove it from the config and pasted back.
> > WOLA
> > it worked. so know your IOS problems.
> >
> >
> > Here's the list of things I went over before my lab
> >
> > OSPF -
> >
>P2P,P2M,Broadcast,non-Broadcast,Virtual-Link,demand-circuit,summarization
> > BGP -
> >
>confederation,aggregate,supress-map,community,dampening,MED,as-path,reg-exp,
> > s
> > ync,as-set,peer group,advertise-map,password
> > EIGRP - summary,distribute-list,route-map, load-balancing
> > RIP - v1,v2,authentication,timer
> > IGRP - default-network, split-horizon, timer
> > IS-IS - L1,l2,password,priority, L1&L2 circuit
> > ATM - PVC P2P, PVC P2M, SVC, CLIP,ATM QoS
> > IPX - RIP,EIGRP,NLSP,SAP,Watch-dog,SPX-spoof,GNS,floating-static
> > DLSW - TCP,FST,Direct,Frame,Border
> > peer,cluster,sap-priority,locaddr-priority,transparent map.
> > IP Sec - ESP,AH,transport/tunnel,pre-share key,RSA key,CET,CA
> > Voice - VOIP,VOFR,num-exp,dial-peer,FXO,FXS
> > Multicast - PIM-DM/SM,RP,auto-rp,dvmrp
> > QoS - Priority queue,custom queue,WFQ,RED,WRED,RSVP,GTS,FRTS
> > Access-List - Dynamic,Reflex,Intercept,CBAC
> > ISDN - PPP, Multilink,CHAP,PPP,Call back,Dialer Watch, Snapshot
> > Bridge - SRB,SRT,TB,SR/TLB,bridge priority
> > Catalyst - logging,permit list,port security,port channel,trunk,
> > static/dynamic map
> > Misc -
>DHCP,NAT,HSRP,NTP,SNMP,TFTP,Syslog,RMON,RSH,SSH,IP-Accounting,moble
> > ip
> >
> > Since this is a Routing & Switching lab. I went through all the routing
> > protocols, not just the command references but also how they work. When
>I
> > see
> > a question on the lab. You would know the exact config you need to make
>it
> > work.
> >
> > If you go through the above list, understand your routing protocols and
> > knows
> > the exact config when you see the requirements. I'm sure you will pass
>the
> > exam with ease.
> >
> > Last but not least. I want to thank Paul for hosting this group and I
>want
> > to
> > thank all of the members in this group. You guys helped me pass my lab.
> >
> >
> > Good Luck to all of you and let us know when you pass.
> >
> >
> > CCIE Security next
> >
> > Charles Huang
> > CCIE 8431
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:21 GMT-3