From: Wang Dehong-DWANG1 (Dehong.Wang@motorola.com)
Date: Tue Aug 10 2004 - 18:14:44 GMT-3
Brian
Thanks for the clarification and i will remember this one. Another one off my "not-sure-lists" :)
- Dehong
-----Original Message-----
From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
Sent: Tuesday, August 10, 2004 4:01 PM
To: Wang Dehong-DWANG1; Edwards, Andrew M; ccielab@groupstudy.com
Subject: RE: ISIS 12.2T command
Dehong,
Not necessarily. Partially meshed networks can work with L1 to
a degree. The hub can exchange routes with the spokes, and the spokes
can exchange routes with the hub, but the spokes will not see each
others routes. Design-wise the solution is just to run point-to-point
ip subnets. A workaround if you don't want to do this would be to have
the spokes just default to the hub.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Wang Dehong-DWANG1
> Sent: Tuesday, August 10, 2004 2:14 PM
> To: 'Brian McGahan'; Edwards, Andrew M; ccielab@groupstudy.com
> Subject: RE: ISIS 12.2T command
>
> Brian
>
> I have another question related to your post.. does this means that
full-
> mesh is required for frame-replay configuration using ISIS? I think it
is
> no, but not so sure. If hub-spoke configuration works with ISIS,
should
> hub-router be selected as DIS always like ip os net broadcast case?
>
> thanks.
>
> - Dehong
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Brian McGahan
> Sent: Tuesday, August 10, 2004 1:36 PM
> To: Edwards, Andrew M; ccielab@groupstudy.com
> Subject: RE: ISIS 12.2T command
>
>
> Andy,
>
> It changes the hello type sent out the interface. IS-IS
> supports three packet formats, L1 LAN, L2 LAN, and point-to-point. L1
> LAN is for level-1 adjacencies on multipoint medias, while L2 LAN is
for
> level-2 adjacencies on multipoint medias. Both support DIS elections.
> Point-to-point is for both L1 and L2 adjacency on point-to-point
> connections, and does not support a DIS election.
>
> It's like the difference between ip ospf network broadcast and
> ip ospf network point-to-point. Keep in mind that IS-IS adjacency
> cannot form unless there is a match in the network type. You can see
> what network type an interface is running by issuing the "debug isis
> adj" command and watch what packets are sent out the interface.
>
>
> HTH,
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987 x 705
> Outside US: 775-826-4344 x 705
> 24/7 Support: http://forum.internetworkexpert.com
> Live Chat: http://www.internetworkexpert.com/chat/
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Edwards, Andrew M
> > Sent: Tuesday, August 10, 2004 1:01 PM
> > To: ccielab@groupstudy.com
> > Subject: Re: ISIS 12.2T command
> >
> > Group,
> >
> > I'm trying to figure out when to use the following interface
command:
> >
> > Isis network point-to-point
> >
> > I know what the docCD says, but why would I want to convert
broadcast
> to
> > unicast flooding over broadcast media? Would this be like neighbor
> > statements in RIP?
> >
> > andy
> >
> >
>
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:40 GMT-3