[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juniper-nsp
Subject:    RE: [j-nsp] FBF Problems
From:       "Edson Cardoso" <ecardoso () qos ! com ! br>
Date:       2004-10-27 9:12:49
Message-ID: 2415F0AC5E674C45A69DD75532969D620FD749 () fortaleza ! corp1 ! com ! br
[Download RAW message or body]

Tnks Daniel
I figure out that I forgot the Rib-Groups... Now is fixed and working well.... You \
now, sometimes we have blackholes in our brain.. :)   
Tnks again
Edson
 
________________________________

From: juniper-nsp-bounces@puck.nether.net on behalf of Daniel Roesen
Sent: Wed 10/27/2004 5:20 AM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] FBF Problems



On Wed, Oct 27, 2004 at 05:02:21AM -0300, Edson Cardoso wrote:
> nucleo@Netuno-re0# run show route table PBR-UOL hidden extensive
> 
> PBR-UOL.inet.0: 1 destinations, 1 routes (0 active, 0 holddown, 1 hidden)
> 0.0.0.0/0 (1 entry, 0 announced)
> Static Preference: 5
> Next hop type: Unusable <-- ??????
> Next-hop reference count: 5
> State: <Hidden Int Ext>
> Age: 1:30
> Task: RT
> AS path: I
> Indirect next hops: 1
> Protocol next hop: 200.221.31.121 Indirect next hop: 0 -

You have to import your interface routes also into your routing-instance
by deploying a rib-group.

routing-options {
    interface-routes {
        rib-group inet ifroutes;
    }
    rib-groups {
        ifroutes {
            import-rib [ inet.0 PBR-UOL.inet.0 ];
        }
    }
}

Without doing so, your next-hop cannot be resolved to an egress
interface within the routing-instance PBR-UOL.


Best regards,
Daniel

--
CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp


_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp


[prev in list] [next in list] [prev in thread] [next in thread]