<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Cool Technology - Category - Fryguy's Blog</title><link>https://hugo.fryguy.net/categories/cool-technology/</link><description>Cool Technology - Category - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 02 Oct 2014 17:31:04 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/categories/cool-technology/" rel="self" type="application/rss+xml"/><item><title>Meet the new ISR Series – ISR 4000 running IOS-XE</title><link>https://hugo.fryguy.net/2014/10/02/meet-the-new-isr-series-isr-4000-running-ios-xe/</link><pubDate>Thu, 02 Oct 2014 17:31:04 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2014/10/02/meet-the-new-isr-series-isr-4000-running-ios-xe/</guid><description><![CDATA[  
In June of 2013 Cisco released the newest member of the ISR family, the ISR4451-X router (Cisco –  <a href="http://blogs.cisco.com/enterprise/introducing-an-entirely-new-direction-in-branch-offices/" target="_blank" rel="noopener noreferrer">blog post</a>).  At that time it was the only model in the ISR44xx line, but today it now has some new siblings.  Today, October 2, 2014, Cisco has introduced some companious, namely the ISR 4321, 4331, 4351, and 4431.  
&nbsp;  
The below graphic from Cisco that shows the new line and the performance characteristcs of each.  You will note, for example, that the ISR4321 says 50–100 Mbps.  The base version of the device will support 50 Mbps, but to move to 100 Mbps on that box you just need a software license.  This will allow a network to grow with it needs without having to replace hardware, you will just have to add a license file.  Back in the ISR G1/G2 days we need to sometime replace hardwre in order to gain additional performance, but that is not the case with the ISR 4000 series.  Much of that comes thanks to Cisco using <a href="http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-3sg/QA_C67-622903.html" target="_blank" rel="noopener noreferrer">IOS-XE </a>on these devices.  A quick blurb IOS-XE from the previous link is :]]></description></item><item><title>Cisco IOS-XRv (V as in Virtual!)</title><link>https://hugo.fryguy.net/2014/02/08/cisco-ios-xrv-v-as-in-virtual/</link><pubDate>Sun, 09 Feb 2014 02:50:25 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2014/02/08/cisco-ios-xrv-v-as-in-virtual/</guid><description><![CDATA[<p align="center">
  
</p>
<p>There was a tweet on Friday that some may have missed, but it is one that you do not want to miss. It was a subtle little announcement from @CiscoIOSXR about IOS XRv!</p>
<blockquote class="twitter-tweet" data-partner="tweetdeck">
  <p>
    Your wait for IOS XR is over! Download IOS XRv here! 🙂 <a href="http://t.co/0WVMAuHqU1">http://t.co/0WVMAuHqU1</a> <a href="https://twitter.com/search?q=%23IWantIOSXR&src=hash">#IWantIOSXR</a> <a href="https://twitter.com/search?q=%23IOSXR&src=hash">#IOSXR</a><br /> — IOS XR (@CiscoIOSXR) <a href="https://twitter.com/CiscoIOSXR/statuses/431919459968618496">February 7, 2014</a>
  </p>
</blockquote>
<p><span style="color: #ff0000;">Note:</span>  On Tuesday, February 11th there was an update that they are still working on the entitlement issue.  Tweet is included below as well.</p>
<blockquote class="twitter-tweet" data-partner="tweetdeck">
  <p>
    <a href="https://twitter.com/fryguy_pa">@fryguy_pa</a> <a href="https://twitter.com/steve">@steve</a> We have a plan to resolve the entitlement checking issue, but this means images will be pulled off CCO for 3 days 🙁<br /> — IOS XR (@CiscoIOSXR) <a href="https://twitter.com/CiscoIOSXR/statuses/433140288404484096">February 11, 2014</a>
  </p>
</blockquote>
<p> </p>
<p align="left">
   So yes, that is a V as in Virtual!  Finally, IOS XRv has been released –  and on the latest IOS-XR code, 5.1.1!
</p>
<p>So a few things about IOS XRv –  first of all, it is a 32–bit softwrae version running on the QNX microkernel.  The VM contains a single RP and a some LC Interfaces.<br>
The demo version of the software is <strong>FREE</strong> for users, has AAA hard-coded users in it, and is rate-limited to 2 Mbps.   There is also a Simulation Image available and has no hard-coded users and is rate-limited to 50 Mbps.  Finally there is a Production Image that has no hard-coded users and no rate-limit.<br>
To run the IOX XRv Router you will need:<br>
</p>]]></description></item><item><title>OpenFlow and SDN from the Symposiom</title><link>https://hugo.fryguy.net/2011/11/07/openflow-and-sdn-from-the-symposiom/</link><pubDate>Mon, 07 Nov 2011 16:02:43 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/11/07/openflow-and-sdn-from-the-symposiom/</guid><description><![CDATA[<p align="center">
  
</p>
<p>On October 26th I attended the OpenFlow Symposium in San Jose, CA hosted by <a href="http://www.packetpushers.net" target="_blank" rel="noopener noreferrer">Packet Pushers</a> and <a href="http://techfieldday.com/2011/openflow-symposium/" target="_blank" rel="noopener noreferrer">TechFieldDay</a> at the DoubleTree San Jose. The purpose of this symposium was to help gain more exposure to OpenFlow as well as discuss what some of the major players see and feel about the technology. In attendance was representatives from Big Switch Networks, Brocade, Cisco, Google, Juniper, NEC, and Yahoo!. They each were allowed to present their views and feelings and then the panel was opened up for discussion and questions.<br>
My take was that Google and Yahoo! are big into this technology as they have the most to gain from it.  They run warehouse size data centers all over the world, and this type of technology has a huge benefit to them as it means they can develop their own controllers and control merchant silicon, thus releasing them from relying on other vendors network hardware to support their data center. Not only that, but they can help prioritize and track individual flows based on what the user is doing. For example – a person who is placing items in their carts and heading to checkout can have a higher priority flow over someone just looking around.  The speed to finish the transaction is important to them, not to mention they can also secure that traffic in the network differently then a person who is just looking.</p>]]></description></item><item><title>Home Virtualization and Learning</title><link>https://hugo.fryguy.net/2011/09/15/home-virtualization-and-learning/</link><pubDate>Thu, 15 Sep 2011 12:05:09 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/09/15/home-virtualization-and-learning/</guid><description><![CDATA[<p align="center">
  
</p>
<p>As some of you have seen on my Twitter feed, I am playing with some home virtualization ideas. By Home Virtualization I am referring to running ESXi Hyper-visor at home for my “servers” as well as trying to see if I can virtualize the families computers. This is an interesting concept that comes with some unique challenges, and a few of them I am still trying to figure out!<br>
The server part has been the easy one, just did a Physical to Virtual (P2V) conversion via the free tool VMware vCenter Converter at VMWare – <a href="http://www.vmware.com/products/converter/" target="_blank" rel="noopener noreferrer">link</a>. The tool will allow you to take a currently running server and convert it to a Virtual machine on your ESXi server. I moved my families Domain Controller / DNS server over, powered it on in the VMware console application, then powered off the physical box. Once the IP address was moved to the new server, everything just worked.</p>
<p style="padding-left: 30px;">
  <em>Curious note on the P2V tool. I have also used this when I purchased a new computer or fix a friends computer. I will P2V the computer first, this way no matter what happens I can still spin up the old computer under VMPlayer &#8211; <a href="http://www.vmware.com/appliances/directory/1069213" target="_blank" rel="noopener noreferrer">link</a>. When I get a new computer I just copy the Virtual Machine to my new computer so that I can access all the old software and such whenever I need to. If I need to see how something was configured, just launch the VM and take a look. It is an snapshot in time of the old computer.</em>
</p>
<p style="padding-left: 30px;">]]></description></item><item><title>FastMAC U-Socket Power Outlet (U=USB)</title><link>https://hugo.fryguy.net/2011/06/18/fastmac-u-socket-power-outlet-uusb/</link><pubDate>Sat, 18 Jun 2011 02:13:28 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/06/18/fastmac-u-socket-power-outlet-uusb/</guid><description><![CDATA[<p> <br>
<a href="/wp-content/uploads/2011/06/Outlet1.jpg" rel=""></a><br>
Well this week I FINALLY got my FastMAC U-Socket power outlet – keep in mind I ordered it back in March of 2011 – only took about 3 months to get it.  I knew it was back ordered when I ordered it, but I honestly never expected it to take 3 months.  The company did nothing to my awareness to notify me of the status during those three months.  I finally had to call and ask for a status when I noticed the website was showing <em>in-stock</em> – but when I did call they did move me ahead in the queue for shipment and I got them about  a week later.  Now that they are in-stock there, that fiasco should not happen to anyone else (chalk it up to wanting to be one of the first).  The only thing I am a little sore on is the shipping – even after all that time I was still had to pay to have them shipped. I would have been happy with a coupon equal to the shipping charge, oh-well – no big deal to be honest – <em><strong>the wait was worth it!</strong></em><br>
_**</p>]]></description></item><item><title>What's in my toolbag</title><link>https://hugo.fryguy.net/2011/06/16/whats-in-my-toolbag/</link><pubDate>Thu, 16 Jun 2011 17:56:32 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/06/16/whats-in-my-toolbag/</guid><description><![CDATA[<p><a href="/wp-content/uploads/2011/06/Tool-Bag.jpg" rel=""></a><br>
 <br>
This post is more of an informative post with regards to what tools I tend to use on a regular basis in my job.  Recently, Stretch wrote about what was in his tool bag over on <a href="http://packetlife.net/blog/2011/jun/16/whats-your-tool-bag/" target="_blank" rel="noopener noreferrer">PacketLife.Net </a>.  He has some GREAT information over there beside just that post, so if you have never visited you should wander over there when you have time.<br>
 <br>
For the most part I tend to use the many of the same tools he discussed, but figured it would be nice to share what I have in my bag. So, without further typing, here we go!<br>
<span style="color: #ff0000;"><em>Note:  If you click on the pictures it will take you to a link to where you can either get the tool or a similar tool if the one I had is no longer availablee</em></span></p>

<p style="text-align: left;">
  This is probably my most used tool when I do not have to make cables.  It contains just about every nut, bolt, and screw that you will find in a data center.  It is easy to use, quick to find, and very versatile. No need to separate screw drivers or pliers, just grab this and you are good to go!
</p>
<p style="text-align: left;">]]></description></item><item><title>Cisco Archive and Configure</title><link>https://hugo.fryguy.net/2011/06/06/cisco-archive-and-configure/</link><pubDate>Mon, 06 Jun 2011 08:15:36 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/06/06/cisco-archive-and-configure/</guid><description><![CDATA[<p style="text-align: center;">
  <a href="/?p=1069"></a>
</p>
<p>There has been some interesting discussions on configuration differences with IOS and JUNOS on Twitter the past few days.  One of the biggest things has been the inclusion of a Rollback command in JUNOS; and to be perfectly honest, that has to be one of the best commands that JUNOS has!<br>
In case you are not familiar with it, in JUNOS if you submit a change and then enter <em>commit confirm (default 10 minutes)</em>, the router will not “save” the configuration change until you <em>commit</em> the change again.  This way if you make a change, lock yourself out of the device, it will revert to the previous configuration and you should have your access back.<br>
<em>(some housekeeping)</em><br>
<span style="color: #ff0000;"><strong>Router/Switch Output</strong></span><br>
<span style="color: #0000ff;"><strong> Commands</strong></span><br>
<span style="color: #339966;"><strong> Notes<br /> </strong></span><br>
<span style="color: #ff0000;">[edit]<br /> user@host# </span><span style="color: #0000ff;">commit confirmed</span><br>
<span style="color: #ff0000;">commit confirmed will be automatically rolled back in 10 minutes unless confirmed</span><br>
<span style="color: #ff0000;">commit complete</span><br>
<span style="color: #ff0000;">#commit confirmed will be rolled back in 10 minutes</span><br>
<span style="color: #ff0000;"><span style="color: #339966;">By entering commit again, the change will become permenant</span><br /> [edit]</span><br>
<span style="color: #ff0000;">user@host# </span><span style="color: #0000ff;">commit<br /> </span><br>
Now, what about IOS?  Well, typically we do the <em>reload in x</em> command before we make a change, but is there another way?  Well, yes there is!  We have the <em>archive</em> command and the <em>config replace</em> command string that will perform a similar function to to the JUNOS command and less drastic then the <em>reload in</em> command.<br>
So, lets first cover the <em>archive</em> command.<br>
The <em>archive</em> command allows you to make an archive of the config either over a time-period (say 1440 minutes) or when the <em>write-memory</em> command is initiated.  The archive can be stored in flash, tftp, ftp, or a few other places. To setup archiving:<br>
<span style="color: #ff0000;">Rack1R2#</span><span style="color: #0000ff;">conf t</span><br>
<span style="color: #ff0000;">Enter configuration commands, one per line.  End with CNTL/Z.</span><br>
<span style="color: #339966;">To enter the archive config, enter the archive command</span><br>
<span style="color: #ff0000;">Rack1R2(config)#<span style="color: #0000ff;">archive</span></span><br>
<span style="color: #339966;">From there, you need to tell it 1) where to store the file and 2) what to call it.</span><br>
<span style="color: #339966;">Here it will be flash:/archive with a name of Rollback</span><br>
<span style="color: #ff0000;">Rack1R2(config-archive)#<span style="color: #0000ff;">path flash:/archive/Rollback</span></span><br>
<span style="color: #339966;">Here I tell it to archive the previous config whenever the write-memory command is executed</span><br>
<span style="color: #ff0000;">Rack1R2(config-archive)#<span style="color: #0000ff;">write-memory</span></span><br>
<span style="color: #339966;">Also, I might as well make sure that we back it up once a day at a minimum.  Range is from 1 minute to 525600 minutes (1 year)</span><br>
<span style="color: #ff0000;">Rack1R2(config-archive)#<span style="color: #0000ff;">time-period ?</span></span><br>
<span style="color: #ff0000;">&lt;1-525600&gt;  Number of minutes to wait between archive creation</span><br>
<span style="color: #ff0000;">Rack1R2(config-archive)#<span style="color: #0000ff;">time-period 1440</span></span><br>
<span style="color: #ff0000;">Rack1R2(config-archive)#</span><br>
Now, if we look at the flash:/archive/ folder, what will we see?  Lets look (I already have some saved in memory)<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">dir flash:archive</span></span><br>
<span style="color: #ff0000;">Directory of flash:/archive/</span><br>
<span style="color: #ff0000;">17  -rw-        1806   Jun 3 2011 19:34:16 +00:00  Rollback-2</span><br>
<span style="color: #ff0000;">18  -rw-        1806   Jun 3 2011 19:35:02 +00:00  Rollback-3</span><br>
<span style="color: #ff0000;">16  -rw-        1744   Jun 3 2011 19:31:54 +00:00  Rollback-1</span><br>
<span style="color: #ff0000;">512057344 bytes total (328622080 bytes free)</span><br>
<span style="color: #ff0000;">Rack1R2#</span><br>
As you can see, we have a few files there, each appended with a number (call it revision with highest being most recent). To check, use the show archive command<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">show archive</span></span><br>
<span style="color: #ff0000;">There are currently 4 archive configurations saved.</span><br>
<span style="color: #ff0000;">The next archive file will be named flash:/archive/Rollback-4</span><br>
<span style="color: #ff0000;">Archive #  Name</span><br>
<span style="color: #ff0000;"></span><br>
<span style="color: #ff0000;">1       flash:/archive/Rollback-1</span><br>
<span style="color: #ff0000;">2       flash:/archive/Rollback-2</span><br>
<span style="color: #ff0000;">3       flash:/archive/Rollback-3 &lt;- Most Recent</span><br>
<span style="color: #ff0000;">4</span><br>
<span style="color: #ff0000;">5</span><br>
<span style="color: #ff0000;">6</span><br>
<span style="color: #ff0000;">7</span><br>
<span style="color: #ff0000;">8</span><br>
<span style="color: #ff0000;">9</span><br>
<span style="color: #ff0000;">10</span><br>
<span style="color: #ff0000;">11</span><br>
<span style="color: #ff0000;">12</span><br>
<span style="color: #ff0000;">13</span><br>
<span style="color: #ff0000;">14</span><br>
<span style="color: #ff0000;">Rack1R2#</span><br>
So, what does all this mean and how does this relate to the commit confirm command in Junos?  Good question!  Here we go!<br>
So, when you need to do a change, just execute the <em>archive config</em> command prior to the change.  That will create a snapshot of the existing config in the archive directory.<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">archive config</span></span><br>
<span style="color: #ff0000;"></span><br>
Lets take a look and see what revision we have saved:<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">show archive</span></span><br>
<span style="color: #ff0000;">There are currently 5 archive configurations saved.</span><br>
<span style="color: #ff0000;">The next archive file will be named flash:/archive/Rollback-5</span><br>
<span style="color: #ff0000;">Archive #  Name</span><br>
<span style="color: #ff0000;"></span><br>
<span style="color: #ff0000;">1       flash:/archive/Rollback-1</span><br>
<span style="color: #ff0000;">2       flash:/archive/Rollback-2</span><br>
<span style="color: #ff0000;">3       flash:/archive/Rollback-3</span><br>
<span style="color: #ff0000;">4       flash:/archive/Rollback-4 &lt;- Most Recent</span><br>
<span style="color: #ff0000;">5</span><br>
<span style="color: #ff0000;">6</span><br>
<span style="color: #ff0000;">7</span><br>
<span style="color: #ff0000;">8</span><br>
<span style="color: #ff0000;">9</span><br>
<span style="color: #ff0000;">10</span><br>
<span style="color: #ff0000;">11</span><br>
<span style="color: #ff0000;">12</span><br>
<span style="color: #ff0000;">13</span><br>
<span style="color: #ff0000;">14</span><br>
<span style="color: #ff0000;">Rack1R2#</span><br>
Now, there is another command that we need to know about – its the <em>configure replace</em> command!  We can use that similar to the commit confirm command because of the archive command.<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">configure replace flash:archive/Rollback-4 time 60</span></span><br>
That is all good – lets test the command!<br>
 <br>
I have R1 and R2 configured like the diagram below, connected via Frame-Relay and all interfaces are in RIPv2<br>
<a href="/wp-content/uploads/2011/06/Archive_Diagram_rev1.jpg" rel=""></a><br>
Here is the routing table and interface status on R2:<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">sh ip route</span></span><br>
<span style="color: #ff0000;">Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP</span><br>
<span style="color: #ff0000;">D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area</span><br>
<span style="color: #ff0000;">N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2</span><br>
<span style="color: #ff0000;">E1 – OSPF external type 1, E2 – OSPF external type 2</span><br>
<span style="color: #ff0000;">i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2</span><br>
<span style="color: #ff0000;">ia – IS-IS inter area, * – candidate default, U – per-user static route</span><br>
<span style="color: #ff0000;">o – ODR, P – periodic downloaded static route</span><br>
<span style="color: #ff0000;">Gateway of last resort is not set</span><br>
<span style="color: #ff0000;">150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks</span><br>
<span style="color: #ff0000;">R       150.1.1.1/32 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1</span><br>
<span style="color: #ff0000;">C       150.1.12.0/24 is directly connected, Serial4/0.1</span><br>
<span style="color: #ff0000;">R       150.1.11.0/24 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1</span><br>
<span style="color: #ff0000;">R       150.1.111.1/32 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1</span><br>
<span style="color: #ff0000;">150.2.0.0/32 is subnetted, 3 subnets</span><br>
<span style="color: #ff0000;">C       150.2.222.2 is directly connected, Loopback2</span><br>
<span style="color: #ff0000;">C       150.2.22.2 is directly connected, Loopback1</span><br>
<span style="color: #ff0000;">C       150.2.2.2 is directly connected, Loopback0</span><br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">sh ip int br | ex un</span></span><br>
<span style="color: #ff0000;">Interface                  IP-Address      OK? Method Status                Protocol</span><br>
<span style="color: #ff0000;">Serial4/0.1                150.1.12.2      YES manual up                    up</span><br>
<span style="color: #ff0000;">Loopback0                  150.2.2.2       YES manual up                    up</span><br>
<span style="color: #ff0000;">Loopback1                  150.2.22.2      YES manual up                    up</span><br>
<span style="color: #ff0000;">Loopback2                  150.2.222.2     YES manual up                    up</span><br>
<span style="color: #ff0000;">Rack1R2#</span><br>
Here is the same information for R1<br>
<span style="color: #ff0000;">Rack1R1#<span style="color: #0000ff;">sh ip route</span></span><br>
<span style="color: #ff0000;">Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP</span><br>
<span style="color: #ff0000;">D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area</span><br>
<span style="color: #ff0000;">N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2</span><br>
<span style="color: #ff0000;">E1 – OSPF external type 1, E2 – OSPF external type 2</span><br>
<span style="color: #ff0000;">i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2</span><br>
<span style="color: #ff0000;">ia – IS-IS inter area, * – candidate default, U – per-user static route</span><br>
<span style="color: #ff0000;">o – ODR, P – periodic downloaded static route</span><br>
<span style="color: #ff0000;">Gateway of last resort is not set</span><br>
<span style="color: #ff0000;">150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks</span><br>
<span style="color: #ff0000;">C       150.1.1.1/32 is directly connected, Loopback0</span><br>
<span style="color: #ff0000;">C       150.1.12.0/24 is directly connected, Serial4/0.1</span><br>
<span style="color: #ff0000;">C       150.1.11.0/24 is directly connected, Loopback1</span><br>
<span style="color: #ff0000;">C       150.1.111.1/32 is directly connected, Loopback2</span><br>
<span style="color: #ff0000;">150.2.0.0/32 is subnetted, 3 subnets</span><br>
<span style="color: #ff0000;">R       150.2.222.2 [120/1] via 150.1.12.2, 00:00:12, Serial4/0.1</span><br>
<span style="color: #ff0000;">R       150.2.22.2 [120/1] via 150.1.12.2, 00:00:12, Serial4/0.1</span><br>
<span style="color: #ff0000;">R       150.2.2.2 [120/1] via 150.1.12.2, 00:00:13, Serial4/0.1</span><br>
<span style="color: #ff0000;">Rack1R1#<span style="color: #0000ff;">sh ip int br | ex un</span></span><br>
<span style="color: #ff0000;">Interface                  IP-Address      OK? Method Status                Protocol</span><br>
<span style="color: #ff0000;">Serial4/0.1                150.1.12.1      YES manual up                    up</span><br>
<span style="color: #ff0000;">Loopback0                  150.1.1.1       YES manual up                    up</span><br>
<span style="color: #ff0000;">Loopback1                  150.1.11.1      YES manual up                    up</span><br>
<span style="color: #ff0000;">Loopback2                  150.1.111.1     YES manual up                    up</span><br>
<span style="color: #ff0000;">Rack1R1#</span><br>
Lets test the connectivity by PINGing R2 Loopback 2 from R1 Loopback2<br>
<span style="color: #ff0000;">Rack1R1#<span style="color: #0000ff;">ping 150.2.222.2 so lo2</span></span><br>
<span style="color: #ff0000;">Type escape sequence to abort.</span><br>
<span style="color: #ff0000;">Sending 5, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:</span><br>
<span style="color: #ff0000;">Packet sent with a source address of 150.1.111.1</span><br>
<span style="color: #ff0000;">!!!!!</span><br>
<span style="color: #ff0000;">Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms</span><br>
<span style="color: #ff0000;">Rack1R1#</span><br>
Good, now lets test the config replace command (IOS Rollback)<br>
First, we will archive the config<br>
<span style="color: #0000ff;"><span style="color: #ff0000;">Rack1R2#</span>archive config</span><br>
Now lets see what archives we have:<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">sh archive</span></span><br>
<span style="color: #ff0000;">There are currently 6 archive configurations saved.</span><br>
<span style="color: #ff0000;">The next archive file will be named flash:/archive/Rollback-6</span><br>
<span style="color: #ff0000;">Archive #  Name</span><br>
<span style="color: #ff0000;"></span><br>
<span style="color: #ff0000;">1       flash:/archive/Rollback-1</span><br>
<span style="color: #ff0000;">2       flash:/archive/Rollback-2</span><br>
<span style="color: #ff0000;">3       flash:/archive/Rollback-3</span><br>
<span style="color: #ff0000;">4       flash:/archive/Rollback-4</span><br>
<span style="color: #ff0000;">5       flash:/archive/Rollback-5 &lt;- Most Recent<br /> <span style="color: #008000;">[– SNIP –]</span><br /> </span><br>
Ok, Rollback-5 is the most recent.<br>
Now on R1 we will start a 1000 packet ping<br>
<span style="color: #ff0000;">Rack1R1#<span style="color: #0000ff;">ping 150.2.222.2 so lo2 repeat 100</span></span><br>
<span style="color: #ff0000;">Type escape sequence to abort.</span><br>
<span style="color: #ff0000;">Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:</span><br>
<span style="color: #ff0000;">Packet sent with a source address of 150.1.111.1</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
Now that we have that started, lets move on<br>
Now, on R2 we will execute the configure replace command, set the timer to 60 seconds, then shut down the Serial 4/0 (frame-relay) interface<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">configure replace flash:/archive/Rollback-5 time 60 </span></span><br>
<span style="color: #ff0000;">Timed Rollback: Backing up to flash:/archive/Rollback-7</span><br>
<span style="color: #ff0000;"><span style="color: #339966;">It will now ask you to make sure you want to do this – checks and balances</span><br /> This will apply all necessary additions and deletions</span><br>
<span style="color: #ff0000;">to replace the current running configuration with the</span><br>
<span style="color: #ff0000;">contents of the specified configuration file, which is</span><br>
<span style="color: #ff0000;">assumed to be a complete configuration, not a partial</span><br>
<span style="color: #ff0000;">configuration. Enter Y if you are sure you want to proceed. ? [no]: <strong><span style="color: #0000ff;">Y</span></strong></span><br>
<span style="color: #ff0000;">Total number of passes: 0</span><br>
<span style="color: #ff0000;">Rollback Done</span><br>
<span style="color: #ff0000;"></span><span style="color: #ff0000;">*Jun  3 21:43:22.026: Rollback:Acquired Configuration lock.</span><br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">conf t</span></span><br>
<span style="color: #ff0000;">Enter configuration commands, one per line.  End with CNTL/Z.</span><br>
<span style="color: #ff0000;">Rack1R2(config)#<span style="color: #0000ff;">int ser 4/0 </span></span><br>
<span style="color: #ff0000;">Rack1R2(config-if)#<span style="color: #0000ff;">shut</span></span><br>
<span style="color: #ff0000;">Rack1R2(config-if)#</span><br>
<span style="color: #ff0000;">*Jun  3 21:43:28.274: %LINK-5-CHANGED: Interface Serial4/0, changed state to administratively down</span><br>
<span style="color: #ff0000;">*Jun  3 21:43:29.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial4/0, changed state to down</span><br>
<span style="color: #ff0000;">Rack1R2(config-if)</span><br>
Hmm, if we look at the ping that we have going on R1 we see that it can no longer PING R2<br>
<span style="color: #ff0000;">Rack1R1#<span style="color: #0000ff;">ping 150.2.222.2 so lo2 repeat 1000</span></span><br>
<span style="color: #ff0000;">Type escape sequence to abort.</span><br>
<span style="color: #ff0000;">Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:</span><br>
<span style="color: #ff0000;">Packet sent with a source address of 150.1.111.1</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!………………………….</span><br>
<span style="color: #ff0000;">……..</span><br>
Lets wait…. there, the config just rolled back on R2 and R1 can PING again!<br>
<span style="color: #ff0000;">Rack1R1#<span style="color: #0000ff;">ping 150.2.222.2 so lo2 repeat 1000</span></span><br>
<span style="color: #ff0000;">Type escape sequence to abort.</span><br>
<span style="color: #ff0000;">Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:</span><br>
<span style="color: #ff0000;">Packet sent with a source address of 150.1.111.1</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!………………………….</span><br>
<span style="color: #ff0000;">…………………!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">!!!!!!!!!!!!!!!!!!!!</span><br>
<span style="color: #ff0000;">Success rate is 94 percent (948/1000), round-trip min/avg/max = 56/57/240 ms</span><br>
<span style="color: #ff0000;">Rack1R1#</span><br>
So what happened on R2?  Here is the output on the console:<br>
<span style="color: #ff0000;">Rack1R2(config-if)#Timed Rollback: rolling to:flash:/archive/Rollback-7</span><br>
<span style="color: #ff0000;">!Pass 1</span><br>
<span style="color: #339966;">Neat, it will show you the commands it is about to enter!</span><span style="color: #ff0000;"><br /> </span><br>
<span style="color: #ff0000;">!List of Commands:</span><br>
<span style="color: #ff0000;">interface Serial4/0</span><br>
<span style="color: #ff0000;">no shutdown</span><br>
<span style="color: #ff0000;">end</span><br>
<span style="color: #ff0000;">Total number of passes: 1</span><br>
<span style="color: #ff0000;">Rollback Done</span><br>
<span style="color: #ff0000;">*Jun  3 21:44:22.218: Rollback:Acquired Configuration lock.</span><br>
<span style="color: #ff0000;">Rack1R2(config-if)#</span><br>
<span style="color: #ff0000;">*Jun  3 21:44:22.778: %PARSER-3-CONFIGNOTLOCKED: Unlock requested by process ’21’. Configuration not locked.</span><br>
<span style="color: #ff0000;">Rack1R2(config-if)#</span><br>
<span style="color: #ff0000;">*Jun  3 21:44:24.586: %LINK-3-UPDOWN: Interface Serial4/0, changed state to up</span><br>
<span style="color: #ff0000;">*Jun  3 21:44:25.586: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial4/0, changed state to up</span><br>
<span style="color: #ff0000;">Rack1R2(config-if)#</span><br>
If all is good after your change and you need to not roll-back, just issue the command <em>configure confirm</em> and it will cancel the rollback._<br>
_<br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">configure confirm</span></span><br>
 <br>
<span style="color: #000000;">If you already issued that command, you will get the following output:</span><br>
<span style="color: #ff0000;">Rack1R2#<span style="color: #0000ff;">configure confirm </span></span><br>
<span style="color: #ff0000;">%No timed rollback pending</span><br>
<span style="color: #ff0000;">Rack1R2#</span><br>
Not as simple as the JUNOS commands, but is still valuable in the IOS world!<br>
 <br>
<a href="http://dl.dropbox.com/u/5753029/Archive%20Blog/R1_Archive.txt" target="_blank" rel="noopener noreffer ">R1 Config Here</a><br>
<a href="http://dl.dropbox.com/u/5753029/Archive%20Blog/R2_Archive.txt" target="_blank" rel="noopener noreffer ">R2 Config Here</a><br>
 </p>]]></description></item></channel></rss>