[j-nsp] policy based routing, rib-groups and issues...

[Andrew Ramsey]

Hi, 

Couple of things:

1.  Put a counter on the filter "servers-to-peerX" to check for packets
coming in.
2.  Put a filter and counter on the interface to "peerX" (in/out) to
check for packets leaving/into the router

The static route "route 0.0.0.0/0 next-table inet.0" looks like it's
defeating the purpose of what you're trying to achieve.  You should
remove it - I don't think it's causing you a problem though since you
have this:

192.168.90.0/24     *[BGP/170] 00:15:03, MED 0, localpref 400
                      AS path: 23059 I
                    > to 192.168.91.26 via ge-7/0/0.3

I think it looks like you're in good shape in the "server" to "peerX"
direction.  What about the other way?  Is there a route for the "server"
in peerX.inet.0?

Andy

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Bill Petrisko
> Sent: Tuesday, October 26, 2004 4:15 AM
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] policy based routing, rib-groups and issues...
> 
> 
> On Tue, Oct 26, 2004 at 09:56:51AM +0200, Daniel Roesen wrote:
> > On Tue, Oct 26, 2004 at 12:45:28AM -0700, Bill Petrisko wrote:
> > > routing-instances {
> > >     peerX {
> > >         instance-type forwarding;
> > >         routing-options {
> > >             static {
> > >                 route 0.0.0.0/0 next-table inet.0;
> > >             }       
> > >         }           
> > >     }               
> > > }                   
> > 
> > I haven't played with this yet, but this looks fishy. What 
> do you want 
> > to achieve with "next-table inet.0"?
> > 
> > Try replacing "next-table inet.0" with "next-hop 192.168.91.26" to 
> > send traffic down the private peering.
> 
> Does not make any difference.
> 
> The next-table inet.0 puts the following into the peerX.inet.0
> table:
> 
> 0.0.0.0/0          *[Static/5] 00:03:39
>                       to table inet.0
> 
> Which, I believed might direct the traffic over to inet.0
> for any routes that were not specifically in peerX.inet.0
> 
> bill
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
>