<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for HandsomePlanet</title>
	<atom:link href="http://www.handsomeplanet.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.handsomeplanet.com</link>
	<description>technology and other perplexities</description>
	<lastBuildDate>Fri, 08 Oct 2010 16:19:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Cisco IOS CLI regular expressions, Part II — ‘AND’ by admin</title>
		<link>http://www.handsomeplanet.com/archives/11/comment-page-1#comment-9</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 08 Oct 2010 16:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.handsomeplanet.com/?p=11#comment-9</guid>
		<description>I understand that it is possible to create more precise matches using the method you have described well here. In practice, it makes more sense to match only what needs to be matched with the least possible typing. While you are correct that there are multiple matches with a partial representation of the regex for an IP, on a live network it is usually sufficient to get close.  If you are doing &#039;show run&#039; and are matching an IP, you are matching the output of a static config, and presumably searching for known data.  Even for dynamic data with many possible matches, it often makes more sense to do a quick and inexact search and then refine your regular expression to get the match you need (based on the output).  This also cuts down on typos.  Enclosing the expression in parens will also take care of space matching, if one is disinclined to use the underscores (as I am).</description>
		<content:encoded><![CDATA[<p>I understand that it is possible to create more precise matches using the method you have described well here. In practice, it makes more sense to match only what needs to be matched with the least possible typing. While you are correct that there are multiple matches with a partial representation of the regex for an IP, on a live network it is usually sufficient to get close.  If you are doing &#8216;show run&#8217; and are matching an IP, you are matching the output of a static config, and presumably searching for known data.  Even for dynamic data with many possible matches, it often makes more sense to do a quick and inexact search and then refine your regular expression to get the match you need (based on the output).  This also cuts down on typos.  Enclosing the expression in parens will also take care of space matching, if one is disinclined to use the underscores (as I am).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cisco IOS CLI regular expressions, Part II — ‘AND’ by ciscozine</title>
		<link>http://www.handsomeplanet.com/archives/11/comment-page-1#comment-8</link>
		<dc:creator>ciscozine</dc:creator>
		<pubDate>Fri, 08 Oct 2010 14:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.handsomeplanet.com/?p=11#comment-8</guid>
		<description>To check exacly an IP address use the backslash (\) before the dot (.) to remove the special meaning of the dot (.) character and the underscore (_) to check the space before/after the IP address. For example, to find the ip address 10.0.0.1 in the running configuration, use the command

show run &#124; i _10\.0\.0\.1_

and not the command (it can match 10.0.0.1, 110.0.0.1, 10.1.1.11, …)

show run &#124; i 10.0.0.1

More info on http://www.ciscozine.com/2010/10/06/using-regular-expressions-with-the-show-command/</description>
		<content:encoded><![CDATA[<p>To check exacly an IP address use the backslash (\) before the dot (.) to remove the special meaning of the dot (.) character and the underscore (_) to check the space before/after the IP address. For example, to find the ip address 10.0.0.1 in the running configuration, use the command</p>
<p>show run | i _10\.0\.0\.1_</p>
<p>and not the command (it can match 10.0.0.1, 110.0.0.1, 10.1.1.11, …)</p>
<p>show run | i 10.0.0.1</p>
<p>More info on <a href="http://www.ciscozine.com/2010/10/06/using-regular-expressions-with-the-show-command/" rel="nofollow">http://www.ciscozine.com/2010/10/06/using-regular-expressions-with-the-show-command/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

