<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://connection.netcordia.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Terry&amp;#39;s Blog - All Comments</title><link>http://connection.netcordia.com/blogs/terrys_blog/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>re: Chilling Network Topology Discovery Patent Application</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/07/24/network-topology-discovery-patent-app.aspx#644</link><pubDate>Tue, 29 Jul 2008 13:28:44 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:644</guid><dc:creator>jennis</dc:creator><description>&lt;p&gt;It is scary that something like this could gain patent protection because of a lack of prior art patents and no awareness on the examiner's part of all the prior art in existing products. &amp;nbsp;Having been a designer for some of these products, I can tell you that some of the things they are claiming were not viewed back then as being sufficiently &amp;quot;novel and nonobvious&amp;quot; to be patentable given state of the art in the industry. &amp;nbsp;My quick look through claims yields this list of things I believe are prior art that could be researched into something conclusive:&lt;/p&gt;
&lt;p&gt;* Claim 1 was done earlier by at least Brix (now EXFO) and maybe NetQoS&lt;/p&gt;
&lt;p&gt;* Claim 3 was done earlier by at least Brix and maybe Concord (now CA)&lt;/p&gt;
&lt;p&gt;* Claim 19 describes what Concord E-Health has been doing since the earth cooled.&lt;/p&gt;
&lt;p&gt;* Claim 21 was done earlier by at least Brix&lt;/p&gt;
&lt;p&gt;* Claim 22 was done earlier by at least Visual Networks, NetQoS and Brix&lt;/p&gt;
&lt;p&gt;* Claim 24 was done earlier by at least Brix&lt;/p&gt;
&lt;p&gt;* Acterna (JDSU) and Spirent have been doing much of the synthetic stuff much longer.&lt;/p&gt;
&lt;p&gt;I also managed to find this whitepaper from April 2002 describing what Brix was doing in space: &lt;a rel="nofollow" target="_new" href="http://phoenix.labri.fr/documentation/sip/Documentation/Papers/Performance/voip_wp_04-29-02.pdf"&gt;phoenix.labri.fr/.../voip_wp_04-29-02.pdf&lt;/a&gt;. &amp;nbsp;I bet there is a lot more documentation out there like this.&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=644" width="1" height="1"&gt;</description></item><item><title>re: Vyatta Open Source Router</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/10/29/vyatta-open-source-router.aspx#569</link><pubDate>Mon, 23 Jun 2008 16:56:19 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:569</guid><dc:creator>packetfish</dc:creator><description>&lt;p&gt;I agree, this guy can't play in big carrier router-land currently -- ie- running sonet ports and such, but a few DS3s or gig ports?!? You bet... Since this isn't apples to apples (Cisco's are typically IPC based and distributed, whereas vyatta really isn't).... should they add IPC (something I believe XORP has and did quite well) into the mix for this beast and get it working reliably, have a few hardware vendors jump on board, then their might be some additional ground on this project in terms of usage. Vyatta really is a bundling of what has best of breed in routing land in open source, cleaned up some code, and made syntax a little more friendly. QOS is there, but not so much.&lt;/p&gt;
&lt;p&gt;As far as monitoring, I think you are forgetting vyatta is linux based and while its not supported directly by vyatta per se, there is nothing preventing you from installing packages like NRPE and using a nagios machine to monitor logs, procs, or whatever else you might need to watch on your router....the beauty of an open platform.&lt;/p&gt;
&lt;p&gt;If your running a business and need to keep costs and keep opex under control, you really can't go wrong I don't think trying this out for your application before blowing a huge wad of cash on a Cisco or Juniper. Really, how many offices or locations have much more than DS3s to begin with, or anything other than some type of metro ethernet drop where you're sub 100M are your rates any ways?&lt;/p&gt;
&lt;p&gt;Case in point, Cisco 2821 with DSL and 2 T1 (+ 16 Poe + Poe PWR supply), about 10 k, vyatta replacement about 400 bucks (reclaimed older server, quad port NIC), add another 500 if you need the 16 poe ports. If 'd need DSL and not so many eth ports, 125 for a sangoma DSL nic, to be directly supported in CLI in the next release of vyatta in July.&lt;/p&gt;
&lt;p&gt;I think there is much fear/bashing surrouding vyatta from the Cisco community of users as whomever has vendor certs, all of a sudden those become cheapened if their are a bunch of open source router jockies that can do it, but also much cheaper. What would be your take on devaluation of certifications given your a CCIE? &amp;nbsp;;-) &amp;nbsp;&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=569" width="1" height="1"&gt;</description></item><item><title>ccie written</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/05/28/a-suggestion-for-the-ccie-written-test-program.aspx#540</link><pubDate>Sat, 14 Jun 2008 02:01:38 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:540</guid><dc:creator>ccie written</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;ccie written&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=540" width="1" height="1"&gt;</description></item><item><title>www t c p heart test</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/08/24/the-origin-of-ttcp-test-tcp.aspx#535</link><pubDate>Fri, 13 Jun 2008 02:44:17 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:535</guid><dc:creator>www t c p heart test</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;www t c p heart test&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=535" width="1" height="1"&gt;</description></item><item><title>The History of Ping</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/08/24/the-origin-of-ttcp-test-tcp.aspx#507</link><pubDate>Wed, 21 May 2008 17:35:47 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:507</guid><dc:creator>Netcordia Blog</dc:creator><description>&lt;p&gt;Everyone doing networking these days knows about the ping program. What is often not known is how it&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=507" width="1" height="1"&gt;</description></item><item><title>re: The Top 25 Network Problems And Their Business Impact</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/05/14/the-top-25-network-problems-and-their-business-impact.aspx#489</link><pubDate>Thu, 15 May 2008 16:02:26 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:489</guid><dc:creator>tslattery</dc:creator><description>&lt;p&gt;Some people have asked if the number on each problem means anything. &amp;nbsp;No, it is just a handle that makes it easy to refer to them without typing the name of the problem.&lt;/p&gt;
&lt;p&gt;If you'd like to provide information ranking them in your network, we can make the number mean something.&lt;/p&gt;
&lt;p&gt; &amp;nbsp;-Terry&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=489" width="1" height="1"&gt;</description></item><item><title>re: Useful Visualization</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2008/02/20/useful-visualization.aspx#432</link><pubDate>Thu, 03 Apr 2008 20:25:46 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:432</guid><dc:creator>tslattery</dc:creator><description>&lt;p&gt;Steve,&lt;/p&gt;
&lt;p&gt;Thanks for pointing out Netcosm. &amp;nbsp;I've seen that and haven't yet figured out how it would be useful to me in an operational network. &amp;nbsp;The audio would be useful. &amp;nbsp;There was a paper presented at Usenix many, many years ago about using syslog events to drive sounds. &amp;nbsp;There's also SonicFinder, developed by someone at Apple. &amp;nbsp;I don't have enough eyes to view the active things happening on the network, especially anything that's large enough to be really interesting (more than 50 routers and switches, plus all the servers). &amp;nbsp;Having the sound of a brook bubbling in the background, augmented with crickets and birds for other events, plus the occasional boom of something big happening would be interesting. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;It would be somewhat like watching a tail of syslog running in a window. &amp;nbsp;While I might not have my eye on it all the time, I will probably get used to how it scrolls and notice when the scrolling is different, drawing my attention to it.&lt;/p&gt;
&lt;p&gt;Probably useful as a blog topic...&lt;/p&gt;
&lt;p&gt; &amp;nbsp;-Terry&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=432" width="1" height="1"&gt;</description></item><item><title>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx#425</link><pubDate>Thu, 27 Mar 2008 09:24:06 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:425</guid><dc:creator>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx"&gt;connection.netcordia.com/.../the-history-of-the-cisco-cli.aspx&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=425" width="1" height="1"&gt;</description></item><item><title>http://community.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx#424</link><pubDate>Wed, 26 Mar 2008 08:53:33 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:424</guid><dc:creator>http://community.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://community.netcordia.com/blogs/terrys_blog/archive/2007/10/28/the-history-of-the-cisco-cli.aspx"&gt;community.netcordia.com/.../the-history-of-the-cisco-cli.aspx&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=424" width="1" height="1"&gt;</description></item><item><title>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/08/16/ccie-test-and-numbering.aspx</title><link>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/08/16/ccie-test-and-numbering.aspx#422</link><pubDate>Thu, 20 Mar 2008 05:53:37 GMT</pubDate><guid isPermaLink="false">5d983763-db35-4d57-ab7d-8a0a48ffcea2:422</guid><dc:creator>http://connection.netcordia.com/blogs/terrys_blog/archive/2007/08/16/ccie-test-and-numbering.aspx</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://connection.netcordia.com/blogs/terrys_blog/archive/2007/08/16/ccie-test-and-numbering.aspx"&gt;connection.netcordia.com/.../ccie-test-and-numbering.aspx&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://connection.netcordia.com/aggbug.aspx?PostID=422" width="1" height="1"&gt;</description></item></channel></rss>