The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Sep> msg00097



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

VPN definition/topology - fully meshed, partially meshed, hub and spoke

  • From: "Grace" <gyeow@singnet.com.sg>
  • Date: Thu, 19 Sep 2002 18:23:30 +0800
  • Resent-Date: Thu, 19 Sep 2002 07:43:28 -0400
  • To: <mpls-ops@mplsrc.com>

Hello,

Blur on route-target import and export, and how it's used to set up meshed,
hub & spokes, and hybrid topologies.

Do they control which routes are advertised to which sites?

                CE5            CE6
                    |                |
                    |                |
CE1 ----- PE1--------PE2 ------CE2
                    |                |   |
                    |               /    \
                CE3        CE4   CE5

The connections are shown above.
The requirements:

CE1 can only access CE3.
CE2 can only access CE3. (no info must be passed between CE1 and CE2, not
even if CE3 allows it)

CE3 can also access CE6 and CE7 (CE1 and CE2 cannot access CE6 and CE7 via
CE3)
CE4 can access only CE6 and CE7 (no info must be passed between CE3 and CE4)
CE5 can only access CE6.

CE6 can also access CE7.
CE7 is the Internet Provider's router.

My solution was
VPN-A: CE1 (spoke), CE2 (spoke), CE3 (hub)
VPN-B: CE3 (spoke), CE4 (spoke), CE5 (spoke), CE6 (hub)
VPN-C: CE3 (spoke), CE4 (spoke), CE6 (spoke), CE7 (hub)

Does it work out? Any way to simplify? Are they really considered different
VPNs (A,B,C)? Or if they all belong to the same company/administrator, is it
considered just one VPN?

Thanks,
grace



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