Interesting - I could just be butt-ass wrong then. It has been a while
since I've been on a network that utilized point-to-multipoint frame
relay - and never on the switch configuration side.
Let me look into it more.
Mike
Chuck Larrieu wrote:
> I'd sure like to see a working config for something like you mention....
>
> looking at it from the frame switch side, there can be only one frame route
> per dlci
>
> the dlci is an endpoint identifier of a PVC, and as such there can be only
> one dlci per pvc.
>
> in the hub and spoke situation, there must be two dlcis at the hub - one
for
> each spoke.
>
> note the error message below.
>
> MANAGER#sh frame route
> Input Intf Input Dlci Output Intf Output Dlci Status
> Serial2/2 999 Serial2/1 807 inactive
>
> MANAGER#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> MANAGER(config)#int s 2/2
> MANAGER(config-if)#frame route 999 int s 2/0 804
> Can't use same dlci on overlapping circuits Frame Circuit -> DLCI 20
> Site1 (10.1.1.2/24) -> Frame Circuit -> DLCI 30
> Site2 -(10.1.1.3/24) > Frame Circuit -> DLCI 40
>
> Notice that each of these guys only has a single DLCI, however, they all
sit
> on the same IP segment.
>
> You would use this setup in cases where the remote sites don't necessarily
> need to talk to each other. If they do, then you have a split horizon
> problem, and you either need to sub-interface on the hub site, or put in
> frame-relay maps everywhere.
>
> What's confusing about it is that in a normal frame world, you build PVCs
to
> each other directly. So each side of the PVC has a DLCI identifier.
>
> Mike
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=14918&t=14495
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
