Just to follow up for posterity (or if somebody comes across the same
issue and is searching the archive), here's the solution to my earlier
problem outlined below:
The describe problem is a known issue on JunOS 8.2 and 8.3 releases,
and the current solution is to downgrade to 8.1R2.4.
JUNOS Problem Report Number 99293 has some additional details.
Regards,
~Aaron
On 5/25/07, Aaron Daubman <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I'm wondering why my commit is failing with the following error:
> (the error is obvious, however I don't understand why this would
> matter - the same config is running and working on a GSR - the whole
> reason I'm using a qualified next-hop is because the interface is not
> point-to-point and has no unicast global...)
>
> # commit
> [edit routing-options rib inet6.0 static route 2001:5:1:1::/64]
> 'qualified-next-hop 2001:5:1:1:200:FF:FE05:101'
> RT: next-hop ge-1/1/0.0 is not point-to-point
> error: configuration check-out failed
>
> Am I missing something or is there a way to force this?
>
> The relevant configuration is below:
> -------------------------------------------------
> <snip>
> ge-1/1/0 {
> hold-time up 0 down 0;
> mac 00:00:00:15:00:01;
> unit 0 {
> family inet6 {
> address fe80::200:ff:fe15:1/64;
> }
> }
> }
> <snip>
> routing-options {
> rib inet6.0 {
> static {
> route 2001:5:1:1::/64 {
> qualified-next-hop 2001:5:1:1:200:FF:FE05:101 {
> interface ge-1/1/0.0;
> }
> retain;
> install;
> }
> }
> }
> <snip>
> -------------------------------------------------
>
> Thanks,
> ~Aaron
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
