From: Scott Morris (swm@emanon.com)
Date: Fri Jun 30 2006 - 13:43:02 ART
Each PVC is treated separately. So your "full mesh" indicates a number of
pvc's between each router.
As an example, here's what we use in basic pod setup:
frame-relay switching
!
!
!
interface Serial0
description Connection to R2 INT S0/1/0
no ip address
encapsulation frame-relay
no ip mroute-cache
no fair-queue
clockrate 4000000
frame-relay intf-type dce
frame-relay route 204 interface Serial1 402
frame-relay route 205 interface Serial2 502
frame-relay route 206 interface Serial3 602
no shut
!
interface Serial1
description Connection to R4 INT s0/0/0
no ip address
encapsulation frame-relay
clockrate 4000000
frame-relay intf-type dce
frame-relay route 402 interface Serial0 204
frame-relay route 405 interface Serial2 504
frame-relay route 406 interface Serial3 604
no shut
!
interface Serial2
description Connection to R5 int S0/1/0
no ip address
encapsulation frame-relay
clockrate 115200
frame-relay intf-type dce
frame-relay route 502 interface Serial0 205
frame-relay route 504 interface Serial1 405
frame-relay route 506 interface Serial3 605
no shut
!
interface Serial3
description Connection to R6 Int S4/0
no ip address
encapsulation frame-relay
clockrate 115200
frame-relay intf-type dce
frame-relay route 602 interface Serial0 206
frame-relay route 604 interface Serial1 406
frame-relay route 605 interface Serial2 506
no shut
So by creating multiple entries there, you are drawing out each PVC. Sit
down with this, and some paper and starting drawing lines. Soon, as you go
through the commands, the building will make sense.
Remember that each line describes one-way communications.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.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.
>
>
This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:34 ART