Even if it is "switched from spoke-to-spoke", at Layer 1 the spokes connect
via the hub. And to do anything with the traffic, Layer 2 must be
consulted -- which gives us Priscilla's DLCI switching table. And, unless
the traffic is unidirectional, you will need DLCIs for the opposite
direction, as well. I don't know Cisco FR that well, but in at least some
vendors' FR implementations, the "return" DLCIs do not have to have the same
numbers as the "forward" ones. That actually enables you to number according
to a pattern which indicates connectionality. And it also makes the DLCI
switching table twice the size that Priscilla showed.

Annlee

""Larry Letterman""  wrote in message
news:[EMAIL PROTECTED]
> My opinion is that it will go to the hub site since it's a point to
> point network..
> If the hub were to be a multi-point connection to the spokes, which
> would be one network,
> Then the traffic could be switched from spoke to spoke...
>
>
> Larry Letterman
> Cisco Systems
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Aaron Ajello
> Sent: Tuesday, June 24, 2003 10:06 AM
> To: [EMAIL PROTECTED]
> Subject: FR concept question [7:71263]
>
>
> This is probably a very simple concept question, but I've asked a couple
> people and haven't gotten a solid answer.
>
> If I've got two frame relay spoke sites connected point to point with a
> hub site and a server in one spoke site copies a file to a server in the
> other spoke site, does all the traffic pass through the hub site, or is
> it switched within the frame cloud?
>
> I guess what I'm wondering is does a frame cloud act somewhat like a
> lan, where initially packets will go through the default gateway and be
> routed and then the following packets will be switched?
>
> thanks.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=71290&t=71263
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to