From: Niche (jackyliu419@gmail.com)
Date: Mon Nov 07 2005 - 01:58:44 GMT-3
Hi Scott,
Thanks alot for the clarification on the ATM aspect. =)
I just hope the ISDN issue won't get into so complex in real lab.
P.S. If what Scott's said really happen on, the only thing I can sure is I
will be locked outside my home... ("deny ip any any" in dialer-list??)
Thanks again Scott~
Jacky
On 11/7/05, Scott Morris <swm@emanon.com> wrote:
>
> According to the docs on the CD:
> " Inverse ARP is enabled by default for IP and IPX if the protocol is
> already running on the ATM interface or subinterface and no static map is
> configured. You will disable Inverse ARP if you configure a static map for
> IP or IPX. "
> When you use the "protocol" command, that is establishing a static map!
> You can verify this with "show atm map" output. It it not necessary to do
> any further disabling.
> For demand-circuit, if you deny ospf from interesting traffic, will that
> side be able to dial in case any routing information changes? If they both
> figure out a change at the same time, it's possible that you could get two
> calls, but that depends a lot on the structure (and looping in the
> background?) of your network, and not incredibly likely.
> Just imagine that your wife wants you to call, and you never do until
> she's already asleep. It's karma. ;)
>
> ------------------------------
> *From:* Niche [mailto:jackyliu419@gmail.com]
> *Sent:* Sunday, November 06, 2005 8:39 PM
> *To:* Scott Morris
> *Cc:* Desmond Ong; ccielab@groupstudy.com
> *Subject:* Re: Workbooks practice doubts
>
> Hi Scott,
>
> Hope you don't mind to clarify my concept on this point:
>
> >4) under atm, when ask not to rely on remote router for arp, i need to
> >configure "no protocol ip inarp" together with no atm "ilmi-keepalive"
> >right?
>
> >>4. The ilmi-keepalive part seems to be a command that magically >>pops
> up on some IOS versions/routers, but it isn't a part of the inarp >>process
> AFAIK
>
> According to the document I read from Cisco document (I don't have any ATM
> to lab =/), inarp is off by default. So that's why usually we need static
> mapping for the remote end,
> "protocol ip x.x.x.x broadcast"
> I assume "no protocol ip inarp" actually is just a good-habit practice
> instead of must-have procedure, am I correct?
>
> For "ospf demand-circuit", if both side are being required has dialing
> capability, I will put it on one side and the other side i will just deny
> OSPF in dialer-list... just imagine you would like to call your wife and
you
> wife would like to call you at the same time.
>
> Cheers~
> Jacky
>
> On 11/7/05, Scott Morris <swm@emanon.com> wrote:
> >
> > 1. If you want to restrict things, you should do it for all your vty
> > ports.
> > Most people think of 0-4, because those have always been the "defaults"
> > for
> > a long, long time.
> >
> > 2. Not necessary. Some people do to make themselves feel better though.
> >
> > 3. What methods are available for you to use? ;)
> >
> > 4. The ilmi-keepalive part seems to be a command that magically pops up
> > on
> > some IOS versions/routers, but it isn't a part of the inarp process
> > AFAIK
> >
> > 5. You'd have to answer that based on what your scenario/topology is to
> > figure out what's best. Have you labbed it to see what does or doesn't
> > happen?
> >
> > 6. Who is doing the dialing? If both sides can initiate a call, then I'd
> >
> > say yes. If not, no. *shrug*
> >
> > 7. This is a design thing, and can lead to some serious sub-optimal
> > routing
> > in your network. Will you be counted off for that? Maybe, maybe not. But
> > there is no perfect answer for this one.
> >
> > 8. See the archives. You don't have to unless the lab says to. Many
> > people do like the magical stuff, many people do not. I'm one of the
> > latter, but that's just me!
> >
> > All of these questions are great ones, but unfortunately, they may also
> > come
> > with the "it depends" caveat! Try different things in context of the lab
> > you are working on to see what does or doesn't happen. You'll learn lots
> > along the way, and may answer your own question, at least within that
> > topology set!
> >
> > Cheers,
> >
> > Scott
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com ] On Behalf Of
> > Desmond Ong
> > Sent: Sunday, November 06, 2005 6:44 AM
> > To: ccielab@groupstudy.com
> > Subject: Workbooks practice doubts
> >
> > Hi there,
> >
> > i am having some doubts while doing my workbooks...
> >
> > 1) if i want to prevent telnet access to my router, i need to put in
> > access-class XXX under line vty 0 4. do i need to put it under line vty
> > 5
> > 15?
> >
> > 2) how to determine which side of the isdn router to put the isdn ospf
> > demand circuit command? can i put on both sides?
> >
> > 3)when ask not to use static mapping on atm, how to i configure
> >
> > 4) under atm, when ask not to rely on remote router for arp, i need to
> > configure "no protocol ip inarp" together with no atm "ilmi-keepalive"
> > right?
> >
> > 5) under frame-relay, when ask not to rely on remote router for arp, i
> > need
> > to put " no frame-relay inarp", how about no arp frame-relay" so that i
> > will
> > not response to other router arp request...
> >
> > 6)Does the "dialer-load threshold either" command need to put on both
> > side
> > of the isdn router when not explicitly asked?
> >
> > 7)when configuring bgp, if by next hop is available by IGP, can i still
> > put
> > in the next-hop-self command under every peering to ibgp peers?
> >
> > 8)ipv6 - do we need to put in eui-64 for site local address? i
> > understand is
> > for automatically assigning the host portion of the address...
> >
> >
> > apologise for the lengthy questions.....
> >
> > Thanks!
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:05 GMT-3