Sorry, I meant to send this out earlier today:
Basically, it appears that 8.2R2.4 will not allow two prefix-lists in a
single term in a policy-statement. Here's the config of the original
show configuration policy-options policy-statement bgp-export
term 0-announce_aggregate {
from protocol aggregate;
then accept;
}
term 5-announce_connected {
from {
protocol direct;
prefix-list wan-subnets;
prefix-list ge-wan-subnets;
}
then accept;
}
term 10-announce_static {
from {
protocol static;
route-filter 0.0.0.0/0 exact reject;
route-filter 0.0.0.0/0 orlonger accept;
}
}
term 99-reject_all {
then reject;
}
show configuration policy-options prefix-list wan-subnets
apply-path "interfaces <t1-*> unit 0 family inet address <*>";
When commenting out the 'prefix-list wan-subnets' match statement or
moving it to a different term, it works fine. I looked through 8.2
release notes to see if there was a behavior change, but couldn't find
anything. It works in 8.2R1.7, but not sure about other versions. JTAC
is opening up a PR on this issue.
-evt
-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Scott Weeks
Sent: Monday, August 06, 2007 4:35 PM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] M10i can't commit configuration
-----Original Message-----
I'm getting the following error when trying to commit a
configuration on
cer1.bltmmdch-re0# commit and-quit
error: Check-out failed for Routing protocols process
(/usr/sbin/rpd)
without details
error: configuration check-out failed
We've restarted RPD and tried a 'commit full', but nothing
works. I'd
prefer not to have to restart the entire router, but will if
necessary.
----------------------------------------------------
----------------------------------------------------
-------- eric at atlantech.net wrote: ----------------
Nevermind - problem resolved. Seems to be a possible bug or simply an
undocumented syntax change between 8.2R1.x and 8.2R2.x.
----------------------------------------------------
Could you send the resolution to the list in case someone's
searching the web later on and happens across this exchange?
scott
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp