[j-nsp] Policy option for advertising full routes

[Doug Marschke]

Are the routes you wish to advertise to your customer active routes in your
inet.0 table?

If you do a show route advertising-protocol bgp xxx.xxx.x.x what does it
show?


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Ihsan Junaidi
Ibrahim
Sent: Sunday, October 23, 2005 2:05 AM
To: Alan Gravett
Cc: Juniper-NSP
Subject: Re: [j-nsp] Policy option for advertising full routes

On Sun, 23 Oct 2005 15:16:55 +0800, Alan Gravett <alangra at gmail.com> wrote:

> All seems more complicated than necessary - if the customer wants you to
> send him full routes
> then you don't need any export policy, BGP will do this automatically,  
> i.e.
> advertise the active
> route for every destination.
>  The advantage for your customer is if they are multihomed they can  
> achieve
> some measure of
> load sharing based either on shorter AS-PATH if no policies are applied,  
> or
> manipulate the BGP
> attributes to achieve more granular control.
>

I have not defined any export policy yet the customer didn't manage to  
receive any routes from us as shown by his received-routes attribute.

I have defined the following BGP peering configuration
group Customer-1 {
             type external;
             multihop;
             local-address xxx.xxx.xxx.xxx; # local lo0
             import from_customer1;
             remove-private;
             peer-as xxxxx;
             neighbor xxx.xxx.xxx;
}

The BGP peering is established and I can import/advertise his networks  
just fine.

-- 
Thank you for your time,
Ihsan Junaidi Ibrahim
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp