The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2003-May> msg00106



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

Re: Re: Advertising Routes learnt from PE to PE

  • From: Aamer Akhter <aakhter@cisco.com>
  • Date: Thu, 15 May 2003 16:51:17 -0400
  • CC: <mpls-ops@mplsrc.com>
  • Resent-Date: Thu, 15 May 2003 17:54:27 -0400
  • To: <sthaug@nethelp.no>, <falsesylvia@yahoo.co.uk>
  • User-Agent: Microsoft-Entourage/10.1.1.2418

Steinar,

In your design, are you feeding the spoke's a default route/summary? The
below hub config (alone) will not readvertise to SpokeB prefix's learnt from
SpokeA.


On 5/15/03 4:08 PM, "sthaug@nethelp.no" <sthaug@nethelp.no> wrote:

>> You do use "hub and spoke"?
> 
> We use hub and spoke for a few customers that have specifically
> requested it. Most customers have a full mesh configuration.
> 
>> Care to share with us the "show running-config" so that we can all deploy it
>> too?
> 
> Nothing magic about it. An extract from the config on a hub:
> 
> ip vrf V80:Customer_A
> rd 64567:179
> route-target export 64567:115
> route-target import 64567:115
> route-target import 64567:116
> 
> interface FastEthernet3/0.16
> encapsulation dot1Q 16
> ip vrf forwarding V80:CustomerA
> ip address 10.116.32.2 255.255.248.0
> 
> and from a spoke:
> 
> ip vrf V69:Customer_A-s
> rd 64567:168
> route-target export 64567:116
> route-target import 64567:115
> 
> interface FastEthernet1/0.3
> encapsulation dot1Q 3
> ip vrf forwarding V77:CustomerA-s
> ip address 10.116.50.1 255.255.255.0
> 
> Steinar Haug, BaneTele
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-- 
Aamer Akhter / aa@cisco.com
NSITE - cisco Systems


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