<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Isis - Tag - Fryguy's Blog</title><link>https://hugo.fryguy.net/tags/isis/</link><description>Isis - Tag - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 11 Feb 2013 13:05:55 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/tags/isis/" rel="self" type="application/rss+xml"/><item><title>Junos – IS-IS</title><link>https://hugo.fryguy.net/2013/02/11/junos-is-is/</link><pubDate>Mon, 11 Feb 2013 13:05:55 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2013/02/11/junos-is-is/</guid><description><![CDATA[  
Here is our IS-IS Lab Topology  
 
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-size: medium;"><span style="font-family: Calibri;">Time to do some IS-IS labs.<span style="mso-spacerun: yes;">  </span>I am going to try and make these short and simple.<span style="mso-spacerun: yes;">  </span>I am sure as I get more into Junos I will write more complex IS-IS topologies and start to include LDP as well. <!--?xml:namespace prefix ="" o ns ="" "urn:schemas-microsoft-com:office:office" ?--></span></span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-family: Calibri; font-size: medium;"> </span>
</p>]]></description></item><item><title>IOS XR – ISIS</title><link>https://hugo.fryguy.net/2012/09/21/ios-xr-isis/</link><pubDate>Fri, 21 Sep 2012 12:37:49 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/09/21/ios-xr-isis/</guid><description><![CDATA[<p align="center">
  
</p>
<p>Time for some IS-IS routing! Between IS-IS and OSPF, those are the two most coming SP core routing protocols.<br>
<span style="color: blue;">RP/0/7/CPU0:R1#<span style="color: red;">conf t<br /> </span>Thu Mar 29 22:09:12.786 UTC</span><br>
First we need to name our process<br>
<span style="color: blue;">RP/0/7/CPU0:R1(config)#</span><span style="color: red;">router isis LAB</span><br>
Then configure our Network Entity ( Area )<br>
<span style="color: blue;">RP/0/7/CPU0:R1(config-isis)#</span><span style="color: red;">net 49.0000.0000.0001.00</span><br>
Then we assign the interfaces to the process, as well as the address family.<br>
<span style="color: blue;">RP/0/7/CPU0:R1(config-isis)#<span style="color: red;">int l0</span><br /> RP/0/7/CPU0:R1(config-isis-if)#<span style="color: red;">address-family ipv4<br /> </span>RP/0/7/CPU0:R1(config-isis-if-af)#<span style="color: red;">exit</span><br /> RP/0/7/CPU0:R1(config-isis-if)#<span style="color: red;">address-family ipv6</span><br /> RP/0/7/CPU0:R1(config-isis-if-af)# <span style="color: red;">exit</span><br /> RP/0/7/CPU0:R1(config-isis-if)#<span style="color: red;">int g0/3/0/2<br /> </span>RP/0/7/CPU0:R1(config-isis-if)#<span style="color: black;">address-family ipv4</span><br /> RP/0/7/CPU0:R1(config-isis-if-af)# <span style="color: red;">exit</span><br /> RP/0/7/CPU0:R1(config-isis-if)#<span style="color: red;">address-family ipv6<br /> </span>RP/0/7/CPU0:R1(config-isis-if-af)# <span style="color: red;">exit</span><br /> RP/0/7/CPU0:R1(config-isis-if)#</span> <span style="color: red;">exit</span><br>
Notice I did not specify an IS-IS Level when I started, but we can set this to Level-2<br>
<span style="color: blue;">RP/0/7/CPU0:R1(config-isis)#</span><span style="color: red;">is-type level-2-only</span><br>
Now, when we show the config, you will notice Level-2 is set to the top of the config when applied, not in the order I entered it. This is the beauty of a staging config, you can enter some things in the wrong order but they will be applied in the correct order.</p>]]></description></item></channel></rss>