Go CCIE Go!! - A Cisco Certified Internetwork Expert

———————————————————— Links ————————————————————
Visual Depiction http://home1.gte.net/res0psau/labs/frame-switch/frame-switch-2.pdf
Sample Generic (Full Mesh) Frame Relay Switch Config http://home1.gte.net/res0psau/labs/frame-switch/rebuild-generic-fr-switch.txt
———————————————————— dlci numbering convention ————————————————————
dlci 101 ^^^ |||__ Destination port (i.e., Serial 1) || ||___ Source port (i.e., Serial 0) | |____ Means Nothing really. Just a place holder. Could signify the first frame-relay switch. ———————————————————— Sample config ————————————————————
interface Serial0 no ip address encapsulation frame-relay no fair-queue clockrate 56000 frame-relay intf-type dce
! — route traffic from s0 (dlci 101), to s1 (dlci 110)
frame-relay route 101 interface Serial1 110
interface Serial1 no ip address encapsulation frame-relay clockrate 56000 frame-relay intf-type dce
! — route traffic from s1 (dlci 110) to s0 (dlci 101)
frame-relay route 110 interface Serial0 101

— kelly http://home1.gte.net/res0psau/index.html#Hang-Gliding-Stuff
— — / / / / — –

Quoting Ian Stong : Just use different numbers for each configuration line. Example follows: frame-relay switching ! interface Serial6 description Connection from R2 to R4/5/6 no ip address no ip directed-broadcast encapsulation frame-relay frame-relay intf-type dce clock rate 64000 frame-relay route 104 interface Serial9 401 frame-relay route 105 interface Serial5 501 frame-relay route 106 interface Serial7 601 no shut ! interface Serial9 description Connection from R4 to R2/4/6 no ip address no ip directed-broadcast encapsulation frame-relay frame-relay intf-type dce clock rate 64000 frame-relay route 401 interface Serial6 104 frame-relay route 405 interface Serial5 504 frame-relay route 406 interface Serial7 604 no shut ! So on and so forth. At the completion you will have a full mesh to work with so you can get from one router to the next. Thanks, Ian www.ccie4u.com —–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of brady.brewer@emersonnetworkpower.com Sent: Friday, June 30, 2006 11:53 AM To: masterdt@yahoo.com; ccielab@groupstudy.com Subject: RE: Configuring a Frame-Relay Switch David, This only really shows a point to point setup, my confusion is on Multipoint - Fully meshed design. Because the local input DLCI# commands cannot be repeated, I am confused on how to set this up and how it works. Any insight you may have on this would be helpful. Thanks. —–Original Message—– From: David Timmons [mailto:masterdt@yahoo.com] Sent: Friday, June 30, 2006 11:48 AM To: Brewer, Brady [LBRT/LNA]; ccielab@groupstudy.com Subject: Re: Configuring a Frame-Relay Switch Hi, You might look at this link: http://www.cisco.com/en/US/customer/tech/tk713/tk237/technologies_config uration_example09186a0080094a3c.shtml I think it will get you started in the right direction…. — brady.brewer@emersonnetworkpower.com wrote: > Can someone point me in the right direction in terms > of understanding > the commands that actually emulate a frame-relay > switch in the Cisco IOS > code. > > I am attempting to setup my own home lab and its not > very clear when > attempting to setup a multipoint frame cloud , how > to actually configure > it on the Cisco router. > > > Command. > > Interface serial1 > Frame-relay route (assuming this is the local DLCI, > i.e. programmed on > the closet router, for instance 200) route interface > serial4 405 > (terminating DLCI) > > > > My question is how do you setup a fully meshed > environment . For > instance, the local DLCI number above would need to > be duplicated to > come up with the environment of a fully meshed > network. > > However, I know this is a wrong perception on my > part because the Cisco > software will not allow for duplicate input DLCI’s > to be programmed. > > Can some explain to me how this is accomplished on > the router emulating > a Frame-Switch > > So that a Hub router would have > > Router ——- PVC 200 ——————- 405 > ——- PVC 200 —————– 502 > > Thanks. > > Brady- > > This e-mail is intended only for the addressee named > above. > As this e-mail may contain confidential or > privileged information, > if you are not the named addressee, you are not > authorized to > retain, read, copy or disseminate this message or > any part of it. > >