The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2003-Mar> msg00090



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: Hub and Spoke

  • From: "M. ELK" <elkou141061@hotmail.com>
  • Date: Tue, 25 Mar 2003 16:49:16 +0000
  • Resent-Date: Tue, 25 Mar 2003 13:01:27 -0500
  • To: rogerw@nordlink.com, mpls-ops@mplsrc.com
  • X-OriginalArrivalTime: 25 Mar 2003 16:49:16.0820 (UTC) FILETIME=[7921ED40:01C2F2EE]
  • X-Originating-Email: [elkou141061@hotmail.com]
  • X-Originating-IP: [57.250.229.136]



Roger

i guess Below model mentioned in Your msg  is not "Hup and spoke" rather 
"Central services" .
In a "Hup and spoke" ,Spoke site(s)could communicate through
the HUP.

A good explanation is found in "MPLS and VPN Architect" page
240 for "Central services" and page 242 for "Hup-And Spoke" .

Brgds



>From: Roger Clark Williams <rogerw@nordlink.com>
>To: MPLS-ops Mailing List <mpls-ops@mplsrc.com>
>Subject: [MPLS-OPS]: Hub and Spoke
>Date: Tue, 25 Mar 2003 07:28:02 -0800
>
>John, the model I use in my classes is a bank that does credit card 
>clearing for two other banks. No bank wants it's network to be "seen" by 
>any other, but yet each bank has to be able to get to the particular 
>clearing site. This would be a classic hub-and-spoke model. Clearly, there 
>are a number of ways to accomplish this, but we are discussing one way, the 
>MPLS VPN way.
>
>Roger Williams
>
>
>>Resent-Date: Tue, 25 Mar 2003 08:16:16 -0500
>>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to 
>>mpls-ops-request@mplsrc.com using -f
>>X-Originating-IP: [203.124.147.65]
>>X-Originating-Email: [johnsmith0302@hotmail.com]
>>From: "john smith" <johnsmith0302@hotmail.com>
>>To: Marcel_TUIHANI/opt@OPT.PF, mpls-ops@mplsrc.com
>>Subject: Re: [MPLS-OPS]: "Hub and sopke" approach
>>Date: Tue, 25 Mar 2003 12:54:56 +0000
>>X-OriginalArrivalTime: 25 Mar 2003 12:54:56.0390 (UTC) 
>>FILETIME=[BC769260:01C2F2CD]
>>Resent-From: mpls-ops@mplsrc.com
>>X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/5483
>>X-Loop: mpls-ops@mplsrc.com
>>Resent-Sender: mpls-ops-request@mplsrc.com
>>
>>
>>i maybe questioning, the fundamentals..
>>
>>why do you want hub and spoke? whats so nice about that sort of a 
>>topology?
>>
>>-JS
>>
>>
>>
>>
>>
>>>From: Marcel_TUIHANI/opt@OPT.PF
>>>To: mpls-ops@mplsrc.com
>>>Subject: [MPLS-OPS]: "Hub and sopke" approach
>>>Date: Mon, 24 Mar 2003 06:58:26 -1000
>>>
>>>Can anyone give me one or, i may be several solution about "hub and 
>>>sopke"
>>>configuration on Cisco equipement.
>>>Actually, I use on my MPLS/VPN network an "Hub and spoke" architecture.
>>>Sites linked on different PE can't communicate together. However, for 
>>>sites
>>>linked on the same PE, it isn't  possible to prevent that they 
>>>communicate
>>>directly.
>>>
>>>I would like to know, how implement an "Hub and spoke" architecture on 
>>>the
>>>same PE.
>>>One site central and several distants sites.
>>>
>>>Marcel TUIHANI,
>>>Office des Postes et des Télécommunications
>>>Polynésie Française - TAHITI.
>>>
>>>
>>>-------
>>>The MPLS-OPS Mailing List
>>>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>>>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>>
>>
>>_________________________________________________________________
>>MSN 8 with e-mail virus protection service: 2 months FREE* 
>>http://join.msn.com/?page=features/virus
>>
>>-------
>>The MPLS-OPS Mailing List
>>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml


_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE* 
http://join.msn.com/?page=features/junkmail

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml