Bryan -<div><br></div><div>If I am not wrong the only way to control type of routes in ISIS is </div><div>by having or not your routers in the same ISIS area. Or by use of</div><div>redistribution ...</div><div><br></div><div>
<div>That is if your routers are in the same area, the route will be marked </div><div>as internal (preference = 15), while if they are in different areas, it will </div><div>be marked as external (preference = 18). </div>
</div><div><br></div><div>Or you can have two routers in the same area and one of the two</div><div>routers redistribute from another protocol routes. Those imported</div><div>routes will be marked as "external" with preference equal to 18.</div>
<div><br></div><div>Of course you need L1/L2 capabilities on the router that redistributes</div><div>either between areas or protocols.</div><div><br></div><div>Also the instance option you were trying to use is only valid for OSPF </div>
<div>and not for ISIS:</div><div><br></div><div><div> - no protocol</div><div> - protocol <protocol> [all|{instance <instance>}]</div><div><br></div><div> <protocol> : bgp|isis|ospf|rip|bgp-vpn</div>
<div> <instance> : ospf-instance [1..31]</div><div> <all> : keyword [only used with ospf]</div><div><br></div></div><div><br></div><div>Check also the options under the "action" statement in route policy:</div>
<div><br></div><div><div> [no] as-path - Assign a BGP AS Path list to routes matching the entry</div><div> [no] as-path-prepend - Prepending a BGP AS number to the AS Path attribute of</div><div> routes that match the entry</div>
<div> [no] community - Apply a BGP community list to routes matching the</div><div> entry</div><div> [no] damping - Configure a damping profile to be used for routes</div><div> matching the entry</div>
<div> [no] local-preferen* - Assign a BGP Local Preference to routes matching the</div><div> entry</div><div> [no] metric - Assign a metric to routes matching the entry</div><div> [no] next-hop - Assign a next hop IP address to routes matching the</div>
<div> entry</div><div> [no] next-hop-self - Advertising a next hop IP address belonging to this</div><div> router to routes matching the entry</div><div> [no] origin - Set the BGP origin assigned to routes exported into</div>
<div> BGP that match the entry</div><div> [no] preference - Assign a route preference to routes matching the entry</div><div> [no] tag - Assign an OSPF RIP or ISIS tag to routes matching the</div>
<div> entry</div><div> [no] type - Assign an OSPF type metric to routes matching the</div><div> entry</div><div><br></div><div>Usually you use the "action" statement to play with routes' proprieties.</div>
<div><br></div><div>Thanks</div><div><br></div><br><div class="gmail_quote">On Sat, Nov 6, 2010 at 10:03 PM, Bryan <span dir="ltr"><<a href="mailto:deadheadblues@gmail.com">deadheadblues@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<br>
<br>
I am redistributing routes into ISIS as follows, however they do not<br>
show up as "external" routes. Any idea why?<br>
<br>
R6--->R5<br>
<br>
R6:<br>
<br>
*A:r6>config>router# info<br>
----------------------------------------------<br>
#--------------------------------------------------<br>
echo "IP Configuration"<br>
#--------------------------------------------------<br>
interface "loop1"<br>
address <a href="http://100.6.6.1/32" target="_blank">100.6.6.1/32</a><br>
loopback<br>
exit<br>
interface "loop2"<br>
address <a href="http://100.6.6.2/32" target="_blank">100.6.6.2/32</a><br>
loopback<br>
exit<br>
interface "system"<br>
address <a href="http://6.6.6.6/32" target="_blank">6.6.6.6/32</a><br>
exit<br>
interface "tor5"<br>
address <a href="http://10.5.6.6/24" target="_blank">10.5.6.6/24</a><br>
port 1/1/1<br>
exit<br>
#--------------------------------------------------<br>
echo "ISIS (Inst: 2) Configuration"<br>
#--------------------------------------------------<br>
isis 2<br>
level-capability level-1<br>
area-id 49.5678<br>
no authentication-check<br>
export "c2i"<br>
all-l1isis 01:00:00:55:55:55<br>
level 1<br>
wide-metrics-only<br>
exit<br>
interface "system"<br>
exit<br>
interface "tor5"<br>
hello-authentication-key<br>
".C1Tp80nkJGSKaKFLTbXnr79N3s8jaqQ" hash2<br>
hello-authentication-type password<br>
exit<br>
#--------------------------------------------------<br>
echo "Policy Configuration"<br>
#--------------------------------------------------<br>
policy-options<br>
begin<br>
prefix-list "loops"<br>
prefix <a href="http://100.6.6.1/32" target="_blank">100.6.6.1/32</a> exact<br>
prefix <a href="http://100.6.6.2/32" target="_blank">100.6.6.2/32</a> exact<br>
exit<br>
policy-statement "c2i"<br>
entry 10<br>
from<br>
protocol direct<br>
prefix-list "loops"<br>
exit<br>
to<br>
protocol isis instance 2<br>
exit<br>
action accept<br>
exit<br>
exit<br>
exit<br>
commit<br>
exit<br>
----------------------------------------------<br>
<br>
R5 route table:<br>
<br>
*A:r5>config>router# show router route-table<br>
<br>
<a href="http://100.6.6.1/32" target="_blank">100.6.6.1/32</a> Remote ISIS(2) 00h16m23s 15<br>
10.5.6.6 10<br>
<a href="http://100.6.6.2/32" target="_blank">100.6.6.2/32</a> Remote ISIS(2) 00h15m52s 15<br>
10.5.6.6 10<br>
<br>
Thanks,<br>
_______________________________________________<br>
alcatel-nsp mailing list<br>
<a href="mailto:alcatel-nsp@puck.nether.net">alcatel-nsp@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/alcatel-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/alcatel-nsp</a><br>
</blockquote></div><br></div>