[alcatel-nsp] ISIS external routes

[Stefano Gridelli]

Bryan -

If I am not wrong the only way to control type of routes in ISIS is
by having or not your routers in the same ISIS area. Or by use of
redistribution ...

That is if your routers are in the same area, the route will be marked
as internal (preference = 15), while if they are in different areas, it
will
be marked as external (preference = 18).

Or you can have two routers in the same area and one of the two
routers redistribute from another protocol routes. Those imported
routes will be marked as "external" with preference equal to 18.

Of course you need L1/L2 capabilities on the router that redistributes
either between areas or protocols.

Also the instance option you were trying to use is only valid for OSPF
and not for ISIS:

  - no protocol
  - protocol <protocol> [all|{instance <instance>}]

 <protocol>           : bgp|isis|ospf|rip|bgp-vpn
 <instance>           : ospf-instance [1..31]
 <all>                : keyword [only used with ospf]


Check also the options under the "action" statement in route policy:

 [no] as-path         - Assign a BGP AS Path list to routes matching the
entry
 [no] as-path-prepend - Prepending a BGP AS number to the AS Path attribute
of
                        routes that match the entry
 [no] community       - Apply a BGP community list to routes matching the
                        entry
 [no] damping         - Configure a damping profile to be used for routes
                        matching the entry
 [no] local-preferen* - Assign a BGP Local Preference to routes matching the
                        entry
 [no] metric          - Assign a metric to routes matching the entry
 [no] next-hop        - Assign a next hop IP address to routes matching the
                        entry
 [no] next-hop-self   - Advertising a next hop IP address belonging to this
                        router to routes matching the entry
 [no] origin          - Set the BGP origin assigned to routes exported into
                        BGP that match the entry
 [no] preference      - Assign a route preference to routes matching the
entry
 [no] tag             - Assign an OSPF RIP or ISIS tag to routes matching
the
                        entry
 [no] type            - Assign an OSPF type metric to routes matching the
                        entry

Usually you use the "action" statement to play with routes' proprieties.

Thanks


On Sat, Nov 6, 2010 at 10:03 PM, Bryan <deadheadblues at gmail.com> wrote:

> Hello,
>
> I am redistributing routes into ISIS as follows, however they do not
> show up as "external" routes. Any idea why?
>
> R6--->R5
>
> R6:
>
> *A:r6>config>router# info
> ----------------------------------------------
> #--------------------------------------------------
> echo "IP Configuration"
> #--------------------------------------------------
>        interface "loop1"
>            address 100.6.6.1/32
>            loopback
>        exit
>        interface "loop2"
>            address 100.6.6.2/32
>            loopback
>        exit
>        interface "system"
>            address 6.6.6.6/32
>        exit
>        interface "tor5"
>            address 10.5.6.6/24
>            port 1/1/1
>        exit
> #--------------------------------------------------
> echo "ISIS (Inst: 2) Configuration"
> #--------------------------------------------------
>        isis 2
>            level-capability level-1
>            area-id 49.5678
>            no authentication-check
>            export "c2i"
>            all-l1isis 01:00:00:55:55:55
>            level 1
>                wide-metrics-only
>            exit
>            interface "system"
>            exit
>            interface "tor5"
>                hello-authentication-key
> ".C1Tp80nkJGSKaKFLTbXnr79N3s8jaqQ" hash2
>                hello-authentication-type password
>            exit
> #--------------------------------------------------
> echo "Policy Configuration"
> #--------------------------------------------------
>        policy-options
>            begin
>            prefix-list "loops"
>                prefix 100.6.6.1/32 exact
>                prefix 100.6.6.2/32 exact
>            exit
>            policy-statement "c2i"
>                entry 10
>                    from
>                        protocol direct
>                        prefix-list "loops"
>                    exit
>                    to
>                        protocol isis instance 2
>                    exit
>                    action accept
>                    exit
>                exit
>            exit
>            commit
>        exit
> ----------------------------------------------
>
> R5 route table:
>
> *A:r5>config>router# show router route-table
>
> 100.6.6.1/32                                  Remote  ISIS(2)  00h16m23s
> 15
>       10.5.6.6                                                     10
> 100.6.6.2/32                                  Remote  ISIS(2)  00h15m52s
> 15
>       10.5.6.6                                                     10
>
> Thanks,
> _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20101107/2676b079/attachment.html>