From: Baety Wayne SrA 18 CS/SCBX (Wayne.Baety@kadena.af.mil)
Date: Tue Mar 18 2003 - 21:43:39 GMT-3
You can use either multiple dlcis or multiple static mappings for each spoke
router to the hub router to simulate a broadcast environment on a partial
mesh frame relay network. The p2p IS-IS hellos will be replicated for each
mapping at the link layer on multipoint interfaces.
-----Original Message-----
From: steve r [mailto:route2hell@hotmail.com]
Sent: Wednesday, March 19, 2003 7:56 AM
To: Brian McGahan; 'Bernard'; ccielab@groupstudy.com
Subject: Re: ISIS INFO NEEDED
Thanks I will read the RFCs
Still looking for something else......
----- Original Message -----
From: "Brian McGahan" <brian@cyscoexpert.com>
To: "'steve r'" <route2hell@hotmail.com>; "'Bernard'" <dollar@lvcm.com>;
<ccielab@groupstudy.com>
Sent: Tuesday, March 18, 2003 4:24 PM
Subject: RE: ISIS INFO NEEDED
> Stephen,
>
> There are two network types and three IS-IS hello (IIH) types in
> IS-IS. The two network types are broadcast and point-to-point. The
> three hello types are L1 LAN, L2 LAN, and point-to-point. Neighbors
> cannot be adjacent unless the hello types match.
>
> Multipoint interfaces such as Ethernet, Token-Ring, and
> Frame-Relay and ATM main and multipoint subinterfaces are network type
> broadcast, and use L1 and L2 LAN hellos, depending on which level they
> are running. Point to point interfaces such as ISDN, HDLC, and
> point-to-point Frame-Relay and ATM are network type point-to-point, and
> send P2P hellos.
>
> As of 12.2(8)T you can send p2p hellos on a broadcast media by
> using the 'isis network point-to-point'. Other than that, the network
> type is based on the interface type.
>
> There is plenty of info on IS-IS on CCO, you just have to know
> where to look. You're not really going to find a better source for it
> unless you read the RFCs:
>
> RFC3373 - Three-Way Handshake for Intermediate System to Intermediate
> System (IS-IS) Point-to-Point Adjacencies
> RFC3359 - Reserved Type, Length and Value (TLV) Codepoints in
> Intermediate System to Intermediate System
> RFC3277 - Intermediate System to Intermediate System (IS-IS) Transient
> Blackhole Avoidance
> RFC2973 - IS-IS Mesh Groups
> RFC2966 - Domain-wide Prefix Distribution with Two-Level IS-IS
> RFC2763 - Dynamic Hostname Exchange Mechanism for IS-IS
> RFC1195 - Use of OSI IS-IS for routing in TCP/IP and dual environments
> RFC1142 - OSI IS-IS Intra-domain Routing Protocol
>
> For more info on IS-IS on CCO:
>
> http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Internetworki
> ng:ISIS
>
>
> HTH
>
> Brian McGahan, CCIE #8593
> Director of Design and Implementation
> brian@cyscoexpert.com
>
> CyscoExpert Corporation
> Internetwork Consulting & Training
> Toll Free: 866.CyscoXP
> Fax: 847.674.2625
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > steve r
> > Sent: Tuesday, March 18, 2003 12:27 PM
> > To: Bernard; ccielab@groupstudy.com
> > Subject: ISIS INFO NEEDED
> >
> > I been looking in cisco's sites and docs on ISIS and its topology with
> > frame
> > point to point and multipoint to different interfaces and
> > subinterfaces.(All
> > I found was some what worthless)
> > Does any one have any info OUTSIDE of Cisco on ISIS and its behavior
> with
> > frame-relay interfaces
> > OR Any Real World Experience on ISIS from ISPs.??
> >
> > (please hold back on the canned answer of use point to point to point
> to
> > point, or interface to interface only ).
> > The complex problems of ISIS using different interfaces types have
> > turned
> > me on to shooting in dark, with trial and error to get things working
> with
> > redistribution with other protocols.
> >
> > Stephen R
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:42 GMT-3