<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://connection.netcordia.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Terry&amp;#39;s Blog</title><subtitle type="html" /><id>http://connection.netcordia.com/blogs/terrys_blog/atom.aspx</id><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/default.aspx" /><link rel="self" type="application/atom+xml" href="http://connection.netcordia.com/blogs/terrys_blog/atom.aspx" /><generator uri="http://communityserver.org" version="3.1.20917.1142">Community Server</generator><updated>2008-06-20T16:35:00Z</updated><entry><title>Per-core licensing charges?</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/18/per-core-licensing-charges.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/18/per-core-licensing-charges.aspx</id><published>2008-08-18T15:08:00Z</published><updated>2008-08-18T15:08:00Z</updated><content type="html">Some vendors are charging licensing fees for each processor or even each processor core in a server. In an article on Network World Oracle is described as charging for each individual core on multi-cpu, multi-core systems. My view is that this type of pricing is too confusing and cumbersome for vendors or customers to track, espeically as virtualization allows a server instance to migrate between various physical systems. I think the licensing should be according to the server instance and dispense...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/18/per-core-licensing-charges.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=680" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author></entry><entry><title>Paris Traceroute</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/14/paris-traceroute.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/14/paris-traceroute.aspx</id><published>2008-08-14T16:06:00Z</published><updated>2008-08-14T16:06:00Z</updated><content type="html">Marty Adkins over at Netcraftsmen recently found an interesting network diagnostic tool: Paris Traceroute . It can find multi-path routes through a network where one device is doing load balancing of some sort. I&amp;#39;ve not yet used it,but it looks pretty useful. The source code is available! The web site (see link above) has a nice description of how it works and how it is better than the traditional traceroute. Good thinking on the part of the project members! -Terry...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/14/paris-traceroute.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=678" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author></entry><entry><title>Cloud Computing Applied to Network Management</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/04/cloud-computing-applied-to-network-management.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/04/cloud-computing-applied-to-network-management.aspx</id><published>2008-08-04T18:39:00Z</published><updated>2008-08-04T18:39:00Z</updated><content type="html">One of the new technology rages in the market today is Cloud Computing (and Storage), of which Amazon&amp;#39;s Web Services ( S3 , SQS, SimpleDB, EC2, and HaDoop) is one example. As I was reading through the example of &amp;quot;Grep the Web&amp;quot; described in the paper Cloud Architectures , I wondered what applicability this technology had to network management. In just a few minutes, I had a couple of ideas. Data storage. Keep large NMS data sets in the S3 storage system . The rates seem pretty reasonable...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/08/04/cloud-computing-applied-to-network-management.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=659" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="network analysis" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/network+analysis/default.aspx" /><category term="Amazon Web Services" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/Amazon+Web+Services/default.aspx" /><category term="data storage" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/data+storage/default.aspx" /><category term="NMS" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/NMS/default.aspx" /><category term="S3" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/S3/default.aspx" /></entry><entry><title>Configuration Rollback</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/30/configuration-rollback.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/30/configuration-rollback.aspx</id><published>2008-07-30T19:40:00Z</published><updated>2008-07-30T19:40:00Z</updated><content type="html">We were talking with Debra Curtis of Gartner yesterday about Network Configuration and Change Management (NCCM) and the topic of Rollback came up. Juniper has supported the &amp;#39;commit&amp;#39; operation since they started, allowing their devices to be rolled back easily. However, Cisco only recently added the &amp;#39;commit&amp;#39; feature and when you examine it carefully, you find that it doesn&amp;#39;t always work the way you want (e.g., rollback of ACLs is problematic). A basic rollback function re-installs...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/30/configuration-rollback.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=650" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="network world" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/network+world/default.aspx" /><category term="IOS" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/IOS/default.aspx" /><category term="rollback" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/rollback/default.aspx" /><category term="NCCM" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/NCCM/default.aspx" /></entry><entry><title>Cisco IOS 12.4(20)T Packet Capture Feature</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/29/cisco-ios-12-4-20-t-packet-capture-feature.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/29/cisco-ios-12-4-20-t-packet-capture-feature.aspx</id><published>2008-07-29T16:49:00Z</published><updated>2008-07-29T16:49:00Z</updated><content type="html">Jamey Heary, CCIE No. 7680, who writes for Network World&amp;#39;s Cisco Subnet, recently wrote about a set of new features in Cisco&amp;#39;s IOS 12.4(20)T release . One of the features he describes is pretty neat: Packet Capture. At times, the only way you can troubleshoot a network problem is to get a packet capture of some application or of the traffic on a suspect link. So you need to take your packet analyzer out to the site and capture data for this analysis. Distributed Sniffer and similar systems...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/29/cisco-ios-12-4-20-t-packet-capture-feature.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=646" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="network world" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/network+world/default.aspx" /><category term="Cisco Subnet" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/Cisco+Subnet/default.aspx" /><category term="Cisco IOS" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/Cisco+IOS/default.aspx" /><category term="PCAP" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/PCAP/default.aspx" /><category term="packet capture" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/packet+capture/default.aspx" /></entry><entry><title>Chilling Network Topology Discovery Patent Application</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/24/network-topology-discovery-patent-app.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/24/network-topology-discovery-patent-app.aspx</id><published>2008-07-24T19:07:00Z</published><updated>2008-07-24T19:07:00Z</updated><content type="html">I discovered a patent application (not yet granted) this week that gave me chills. Part of its claims* are performing Layer 2 and Layer 3 network topology discovery and display, as of October 2001. Huh? Network topology discovery and display was being done way before then. What&amp;#39;s chilling about this patent application? Having a patent granted that covers basic network discovery. That&amp;#39;s the foundation of many/all network management products, prior to the filing date and subsequent to then...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/24/network-topology-discovery-patent-app.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=640" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="network discovery" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/network+discovery/default.aspx" /><category term="network topology" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/network+topology/default.aspx" /><category term="patent" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/patent/default.aspx" /></entry><entry><title>Troubleshooting VoIP</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/21/troubleshooting-voip.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/21/troubleshooting-voip.aspx</id><published>2008-07-21T20:15:00Z</published><updated>2008-07-21T20:15:00Z</updated><content type="html">I&amp;#39;ve done a few seminars on troubleshooting VoIP at VoiceCon (Fall 07 and Spring 08). Somewhere along the way, someone mentioned a relatively new web site to me: voiptroubleshooter.com I finally took time today to look at it. The content is potentially useful, depending on your level of expertise. If you&amp;#39;re a long-time VoIP troubleshooter, then you&amp;#39;ll already know much of what&amp;#39;s there (or should). If you&amp;#39;re getting started, it has some useful background knowledge and procedures...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/21/troubleshooting-voip.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=629" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="voip" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/voip/default.aspx" /><category term="troubleshooting" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/troubleshooting/default.aspx" /></entry><entry><title>Publishing product power consumption and heating requirements</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/15/publishing-product-power-consumption-and-heating-requirements.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/15/publishing-product-power-consumption-and-heating-requirements.aspx</id><published>2008-07-15T16:22:00Z</published><updated>2008-07-15T16:22:00Z</updated><content type="html">In my last post, I described a common repository for EOL/EOS data for all vendors. Continuing the wishful thinking, I propose that vendors publish the power consumption and heat generation parameters for their products in a common format. With these parameters, site administrators can more readily measure the power consumption and cooling load of groups of equipment, such as in a data center or wiring closet. The rising cost of energy is forcing the IT industry to include these parameters into life...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/15/publishing-product-power-consumption-and-heating-requirements.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=618" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="EOL/EOS" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/EOL_2F00_EOS/default.aspx" /><category term="power and heating load" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/power+and+heating+load/default.aspx" /><category term="Green IT" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/Green+IT/default.aspx" /><category term="CMDB" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/CMDB/default.aspx" /></entry><entry><title>Identifying End-of-Life and End-of-Sales products</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/15/identifying-end-of-life-and-end-of-sales-products.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/15/identifying-end-of-life-and-end-of-sales-products.aspx</id><published>2008-07-15T15:18:00Z</published><updated>2008-07-15T15:18:00Z</updated><content type="html">You can save a lot of money by identifying obsolete products in your network that are costing more money to keep on maintenance contracts than replacement products cost. Vendors announce their obsolete products with End-of-Life or End-of-Sales postings. I would like to see the creation of a central repository and format for this information, so that it is easy for anyone to determine which equipment is out of date. There is a common format in use for security announcements, so why not a similar format...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/15/identifying-end-of-life-and-end-of-sales-products.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=617" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="EOL/EOS" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/EOL_2F00_EOS/default.aspx" /><category term="end-of-sale" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/end-of-sale/default.aspx" /><category term="wiki" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/wiki/default.aspx" /><category term="end-of-life" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/end-of-life/default.aspx" /><category term="EOS" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/EOS/default.aspx" /><category term="EOL" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/EOL/default.aspx" /><category term="Cisco Learning Network" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/Cisco+Learning+Network/default.aspx" /></entry><entry><title>The Original CCIE Lab's Plaque</title><link rel="alternate" type="text/html" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/06/20/the-original-ccie-lab-s-number.aspx" /><id>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/06/20/the-original-ccie-lab-s-number.aspx</id><published>2008-06-20T20:35:00Z</published><updated>2008-06-20T20:35:00Z</updated><content type="html">Stuart Biggs, who was awarded CCIE number 1025, was able to track down the original CCIE lab&amp;#39;s number plaque and get a picture (see below). I asked where it was currently located: They moved it to bldg K - ground floor where the elevators are. Stuart Stuart noted that the frame&amp;#39;s glass makes it difficult to get a good photo. Perhaps the certification group at Cisco can get a couple of close-ups of the emblem and the label to go with the overall photo. See you at Networkers (or Cisco Live...(&lt;a href="http://connection.netcordia.com/blogs/terrys_blog/archive/2008/06/20/the-original-ccie-lab-s-number.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=568" width="1" height="1"&gt;</content><author><name>tslattery</name><uri>http://connection.netcordia.com/members/tslattery.aspx</uri></author><category term="ccie" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/ccie/default.aspx" /><category term="Stuart Biggs" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/Stuart+Biggs/default.aspx" /><category term="CCIE lab" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/CCIE+lab/default.aspx" /><category term="CCIE lab plaque" scheme="http://connection.netcordia.com/blogs/terrys_blog/archive/tags/CCIE+lab+plaque/default.aspx" /></entry></feed>