Mailing List Archive

Hi Rich,

a Juniper's KB view note deals with the subject : Note 652
(if you have access to the kb).

Roughly, here are the steps described in the note :
1. create a static route w/0.0.0.0 and discard,
2. create a policy to export that route,
3. include the policy in the neighbor statement for the neighbor to whom you
want this to apply.

Cheers,

Nicolas.

# Hi,
#
# We've got a few M-40's handling our transit which get full internet
# routing tables via BGP. In turn, we want them to advertise a default
# route via OSPF to all the internal OSPF capable routers.
#
# I was wondering what's the best way to do this on a Juniper.
# Is there an
# equivalent of the "default-information originate" and
# "default-network"
# commands or is there a better implementation under Junos?
#
# Cheers,
#
# Rich

I agree with 1 & 2.

But with 3, OSPF only allows you to export policies at the global level
(unlike bgp global, group & neighbour import/export ability).
Need to keep the LSDB's the same.............

neil@lab001# set protocols ospf ?
Possible completions:
+ apply-groups Groups from which to inherit configuration data
> area Configure an OSPF area
disable Disable OSPF
+ export Export policy
external-preference Preference of external routes
> graceful-restart Configure graceful restart attributes
> overload Set the overload mode (repel transit traffic)
preference Preference of internal routes
reference-bandwidth Bandwidth for calculating metric defaults
rib-group Routing table group for importing OSPF routes
route-type-community Specify BGP extended community value to encode OSPF
route type
> traceoptions Trace options for OSPF
> traffic-engineering Configure traffic engineering attributes

Neil.

-----Original Message-----
From: Nicolas Fevrier [mailto:nicolas.fevrier@telindus.fr]
Sent: 04 April 2003 14:13
To: variable@ednet.co.uk; juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] Advertising a default route from JUNOS


Hi Rich,

a Juniper's KB view note deals with the subject : Note 652
(if you have access to the kb).

Roughly, here are the steps described in the note :
1. create a static route w/0.0.0.0 and discard,
2. create a policy to export that route,
3. include the policy in the neighbor statement for the neighbor to whom you
want this to apply.

Cheers,

Nicolas.

# Hi,
#
# We've got a few M-40's handling our transit which get full internet
# routing tables via BGP. In turn, we want them to advertise a default
# route via OSPF to all the internal OSPF capable routers.
#
# I was wondering what's the best way to do this on a Juniper.
# Is there an
# equivalent of the "default-information originate" and
# "default-network"
# commands or is there a better implementation under Junos?
#
# Cheers,
#
# Rich





_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030404/f9c224cd/attachment.htm

On Fri, 4 Apr 2003, Neil Stirling wrote:

> I agree with 1 & 2.
>
> But with 3, OSPF only allows you to export policies at the global level
> (unlike bgp global, group & neighbour import/export ability).
> Need to keep the LSDB's the same.............

That's fine, but nailing up static routes isn't a great idea. Is there
any way I can get the Juniper to stop announcing the default route if it
loses a particular peering session/interface goes down?

Cheers,

Rich

You could create a generate route like such:

generate {
route 0.0.0.0/0 policy if-upstream-routes-exist;
}


policy-statement if-upstream-routes-exist {
term only-certain-contributing-routes {
from {

route-filter 10.100.0.0/17 exact;
}
then accept;
}
term reject-all-other-routes {
then reject;
}
}

then just follow the remaining instructions for advertising it into OSPF.


Thanks,

Mario Puras
SoluNet Technical Support
Mailto: mpuras@solunet.com
Direct: (321) 309-1410
888.449.5766 (USA) / 888.SOLUNET (Canada)



-----Original Message-----
From: variable@ednet.co.uk [mailto:variable@ednet.co.uk]
Sent: Friday, April 04, 2003 11:22 AM
To: juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] Advertising a default route from JUNOS


On Fri, 4 Apr 2003, Neil Stirling wrote:

> I agree with 1 & 2.
>
> But with 3, OSPF only allows you to export policies at the global level
> (unlike bgp global, group & neighbour import/export ability).
> Need to keep the LSDB's the same.............

That's fine, but nailing up static routes isn't a great idea. Is there
any way I can get the Juniper to stop announcing the default route if it
loses a particular peering session/interface goes down?

Cheers,

Rich

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