The MPLS-OPS Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
RE: Hub and Spoke
-
From: Jerome Law <Jerome.Law@vanco.co.uk>
-
Date: Tue, 25 Mar 2003 15:38:31 -0000
-
Resent-Date: Tue, 25 Mar 2003 12:02:30 -0500
-
To: "'Roger Clark Williams'" <rogerw@nordlink.com>, MPLS-ops Mailing List <mpls-ops@mplsrc.com>
Title: RE: [MPLS-OPS]: Hub and Spoke
This model is very common now rather in the hey days of a distributed model. Most corporate are consolidating their data centers or head offices.
-----Original Message-----
From: Roger Clark Williams [mailto:rogerw@nordlink.com]
Sent: 25 March 2003 15:28
To: MPLS-ops Mailing List
Subject: [MPLS-OPS]: Hub and Spoke
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
**********************************************************************
Any opinions expressed in the email are those of the individual and
not necessarily the company. This email and any files transmitted with
it are confidential and solely for the use of the intended recipient.
If you are not the intended recipient or the person responsible for
delivering it to the intended recipient, be advised that you have
received this email in error and that any dissemination, distribution,
copying or use is strictly prohibited.
If you have received this email in error, or if you are concerned with
the content of this email please e-mail to:
e-security.support@vanco.co.uk
The contents of an attachment to this e-mail may contain software
viruses which could damage your own computer system. While the sender
has taken every reasonable precaution to minimise this risk, we cannot
accept liability for any damage which you sustain as a result of
software viruses. You should carry out your own virus checks before
opening any attachments to this e-mail.
**********************************************************************
| |
|