[j-nsp] bgp policy

[Mark Tinka]

On Tuesday 02 February 2010 06:32:32 am Raheel Muhammad 
wrote:

> May be a simple question but i spent lot of time on it
>  but still cant get anything, may be i am thinking in
>  wrong direction. Customer is advertising x.x.150.0/23 to
>  us and we have allowed x.x.128.0/19 upto /24 in our
>  policy but it is not getting advertised to our upstreams
>  i could see x.x.150.0/23 in received-routes but not
>  seeing in advertise-routes but if i am putting
>  specifically x.x.150.0/23 upto /24 then it is getting
>  advertised. Why is that ?
> 
> I tried other way i put x.x.144.0/21 upto /24 in my
>  policy, this way it works but why not working with
>  x.x.128.0/19 upto /24.

Let's take a look at your policy configuration.

Was this /19 allocated to you or your customer?

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20100202/6b2ccf3a/attachment.bin>