Re: IS-IS route Leaking Behavior

Dear Faizan,

Let me try to summarize it with the following points:
1.By default, only L1 internal routes are leaked to L2.
2. There are two solutions to this, one is to manually force the routes to
be leaked into L2 by writing a policy that redistributes routes from L1 to
L2 and what routes need to go there. Note that you also need to acquaint
for the internal routes. The second solution is to use wide metrics which
will use TLVs 135 (if I am not mistaken) instead of using TLV 128. TLV135
doesn't have any indication of internal/external and thus the route will be
leaked to L2 automatically.
3.For leaking routes from L2 to L1, you always need a policy because the
default is to only offer a default route based on the presence of the
attached bit.

HTH,

Thank You

On Sun, Apr 29, 2012 at 7:53 PM, faizan khurshid <
faizankhurshid921_at_hotmail.com> wrote:

> Dear Folk
>
> I need to know to route leaking behavior of IS-IS in Cisco
>
> By default level-1 not to advertise level-2
>
> Q1. Advertise level1 internal route to level2
>
> .Which metric will it be use for it, is it IP INTERNAL/IP EXTERNAL
>
> Q2.Advertising level1 external route into Level2 can use use Wide-metric?
>
> Q3.Advertising Level2 external route into level1
>
> Q4.Advertising Level1 summary route External/Internal both into LEvel2 and
> vice-versa
>
>
>
> Thanks
>
> Faizan Khurshid
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
KJ
Blogs and organic groups at http://www.ccie.net