[j-nsp] ISIS default route question

[Yue Min]

ha, I figured it out. :)

on core1, define a generated route ( 0/0, not default ) with a policy
match "from protocol isis, from route-filter 0/0 exact", then export
this generated route to L2. match condition for the policy used by
generate could be something else more specific. tested works.

On Fri, Sep 4, 2009 at 1:01 AM, Yue Min<smartsuites at gmail.com> wrote:
> hey everyone,
>
> I'm studying junos isis. well, most part is simillar to cisco, but I
> got a problem with default route. here's the senario:
>
> ISP router ---(ebgp with default route )--> edge1 ( L1 router
> )---->core1(L1/2 router)----l2 adj---->core2(L1/2 router)----->L1
> router
>
> for propergating the default learned from ISP at edge1 to the rest of
> isis network, the cisco solution is simple ( core1 generates default
> with a rotue-map to check DMZ link up/down ), but I can't figure out
> junos solution. Can someone help me out on this? Thanks. not quite
> familar with junos isis since it's not in our production. :)
>
> Min
>