[j-nsp] Default-information originate on Juniper JUNOS
Alexander Arsenyev (GU/ETL)
alexander.arsenyev at ericsson.com
Tue Oct 25 08:09:16 EDT 2005
<quote>
> I'm looking for the way to do the same thing as the "default-information originate always" command on Cisco routers but on > Juniper JUNOS v7.0. This is for the RIP V2 protocol. Has anybody an idea?
[…]
policy-options {
policy-statement default {
term conditional {
from {
protocol aggregate;
route-filter 0.0.0.0/0 exact;
}
then accept;
}
term suppress {
then reject;
}
}
[…]
protocols {
rip {
send multicast;
receive version-2;
group unix {
export default; <<<<<<<<<<<<<<
neighbor fe-0/3/3.0 {
</quote>
I know the question originator did not explicitly ask for this but anyway...
AFAIK, one of differences between Cisco and Juniper implementations of RIP is that on Juniper routers RIP does not advertise even connected subnets it is running over :
http://www.juniper.net/techpubs/software/junos/junos73/swconfig73-routing/html/rip-config2.html#1014087 ,
"The local router imports all routes by default from this neighbor and does not advertise routes"
So to make it 100% compatible with Cisco RIP implementation the above JUNOS RIP export policy (policy-statement default) should contain an additional term (named "connected" in the example below) between terms "conditional" and "suppress", something like:
term connected {
from protocol direct;
route-filter <whatever subnets RIP is running over>;
}
then accept:
HTH
Cheers
Alex
More information about the juniper-nsp
mailing list