From: Erick B. (erickbe@yahoo.com)
Date: Mon Jun 16 2003 - 22:54:29 GMT-3
One more reason I can think of is, if there is a
non-cisco router on the FR cloud then you need to do
IETF encapsulation as well and if you autosense LMI it
probably doesn't use IETF encapsulation.
Erick
--- "Dana J. Dawson" <djdawso@qwest.com> wrote:
> Some things are good ideas for administrative and
> maintenance issues rather than
> purely technical ones. For example, suppose the
> router won't always be a Cisco
> running that version of code, perhaps because you
> have an old spare for
> emergency reasons? As another example, here in our
> shop we never use Frame
> Relay Inverse ARP if we don't have to, since it
> makes troubleshooting IP
> connectivity issues harder. It may not be quite as
> convenient, but in the long
> run those few extra commands are worth it. It's
> sort of like putting comments
> in your code. They don't make the code work any
> better, but a year and a half
> later when someone else is looking at the config,
> you want it to be as easy as
> possible for them to figure out what's going on.
>
> This is just my $.02 - I'm sure there are compelling
> arguments on the flip side
> of this, too.
>
> HTH
>
> Dana
>
> --
>
> Dana J. Dawson djdawso@qwest.com
> Senior Staff Engineer CCIE #1937
> Qwest Communications
> 600 Stinson Blvd., Suite 1S
> Minneapolis MN 55413-2620
>
> "Hard is where the money is."
>
> Joe Deleonardo wrote:
> > Hi,
> >
> > Assuming:
> > - you're on a DTE
> > - you're on 11.2 or later
> > - you don't have any specification requirements
> >
> > Is there any reason why you might want to specify
> your LMI type statically?
> >
> > I asking because I can't find a reason, however
> I'm looking at a
> > configuration where they do specify it statically,
> but there doesn't seem to
> > be a reason why... at least not that I'm aware of.
> >
> > Thanks,
> >
> > Joe
>
>
>
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:59 GMT-3