On Tue, Feb 2, 2010 at 3:24 PM, Raheel Muhammad <[email protected]>wrote:
> Hi, > > It is our customer prefix and we are acting as a transit provider. > Configuration is simple > > term term-1 > from > route-filter x.x.128.0/19 upto /24 > > Regards > Raheel > On Tue, Feb 2, 2010 at 4:07 AM, Mark Tinka <[email protected]> > wrote: > > > 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. > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Regards, W _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
