<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OpenNMS Patterns and Scripts</title>
	<atom:link href="http://opennms.dougbakewell.ca/feed" rel="self" type="application/rss+xml" />
	<link>http://opennms.dougbakewell.ca</link>
	<description>Implementing OpenNMS in an enterprise IT environment.</description>
	<lastBuildDate>Tue, 11 Jan 2011 00:29:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Small Update to Node Details (nodedetails.cgi)</title>
		<link>http://opennms.dougbakewell.ca/posts/small-update-to-node-details-nodedetails-cgi</link>
		<comments>http://opennms.dougbakewell.ca/posts/small-update-to-node-details-nodedetails-cgi#comments</comments>
		<pubDate>Fri, 31 Dec 2010 19:07:01 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=1341</guid>
		<description><![CDATA[Someone pointed out that the Node Details (nodedetails.cgi) report would be more useful if it only displayed services that are being monitored on a node, as opposed to all the services that have been discovered by OpenNMS. After running this by a few of my users, all agreed that it was better to hide services that are [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/small-update-to-node-details-nodedetails-cgi/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Auditing Node Configuration</title>
		<link>http://opennms.dougbakewell.ca/posts/auditing-node-configuration</link>
		<comments>http://opennms.dougbakewell.ca/posts/auditing-node-configuration#comments</comments>
		<pubDate>Mon, 15 Nov 2010 19:17:08 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Patterns]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=1273</guid>
		<description><![CDATA[Issue In a large scale deployment it becomes difficult to know if nodes are configured correctly in OpenNMS. As with any large configuration, things get missed and small mistakes can lead to critical holes in monitoring. The scripts on this site help maintain node configurations but some aspects of a node can not be checked [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/auditing-node-configuration/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Node Details (nodedetails.cgi)</title>
		<link>http://opennms.dougbakewell.ca/posts/nodedetails-cgi</link>
		<comments>http://opennms.dougbakewell.ca/posts/nodedetails-cgi#comments</comments>
		<pubDate>Thu, 07 Oct 2010 18:08:23 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=52</guid>
		<description><![CDATA[Issue I often want to review important aspects of nodes in OpenNMS including: SNMP status, monitored services, IP addresses, group membership, data links, and critical path settings. The OpenNMS interface does not provide an easy way to quickly review these items in bulk. Some of this information can be viewed on the OpenNMS node page but a [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/nodedetails-cgi/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Script Speed vs. Impacting OpenNMS</title>
		<link>http://opennms.dougbakewell.ca/posts/script-speed-vs-impacting-opennms</link>
		<comments>http://opennms.dougbakewell.ca/posts/script-speed-vs-impacting-opennms#comments</comments>
		<pubDate>Tue, 05 Oct 2010 19:00:59 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=1172</guid>
		<description><![CDATA[I&#8217;ve been asked a similar question by two different people so I figured a public response was in order. After looking at the scripts on this site they noticed that some of them could be changed to run much faster. Most of the speed increase would come from performing a single large SQL statement and parsing the [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/script-speed-vs-impacting-opennms/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Comments / Forced Unmanged (commentsforced.cgi)</title>
		<link>http://opennms.dougbakewell.ca/posts/commentsforced-cgi</link>
		<comments>http://opennms.dougbakewell.ca/posts/commentsforced-cgi#comments</comments>
		<pubDate>Fri, 24 Sep 2010 19:54:36 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=1165</guid>
		<description><![CDATA[Issue The OpenNMS poller-configuration.xml file controls what services are monitored. Fine grain exceptions to the poller-configuration.xml can be created using the OpenNMS web interface: node admin page -&#62; Manage and Unmanage Interfaces and Services. This allows monitoring of a service or an entire interface to be turned off when the poller-configuration.xml would normally cause it to be [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/commentsforced-cgi/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Known Names (knownnames.cgi)</title>
		<link>http://opennms.dougbakewell.ca/posts/knownnames-cgi</link>
		<comments>http://opennms.dougbakewell.ca/posts/knownnames-cgi#comments</comments>
		<pubDate>Thu, 23 Sep 2010 18:09:50 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=48</guid>
		<description><![CDATA[Issue OpenNMS stores name information from several sources in its database but only makes some of it available in the web interface. It&#8217;s useful to see all this information in one place for auditing and searching. It&#8217;s also important to check which name (Manually set by administrator, DNS, NetBIOS (SMB), SNMP, or lowest numbered IP) OpenNMS has chosen for [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/knownnames-cgi/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Install/Ugrade Scripts</title>
		<link>http://opennms.dougbakewell.ca/posts/install-upgrade</link>
		<comments>http://opennms.dougbakewell.ca/posts/install-upgrade#comments</comments>
		<pubDate>Sat, 18 Sep 2010 16:39:24 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=872</guid>
		<description><![CDATA[The noc-install-upgrade.sh script will install or upgrade all the scripts from this site onto a Linux system. It&#8217;s only prerequisite is that OpenNMS be installed first. Also, I recommend reading the information on this site before installing. It&#8217;s not required to install the scripts in this way. If you only want a small subset, the scripts can be [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/install-upgrade/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Check DNS Reverse Lookups (check-dns)</title>
		<link>http://opennms.dougbakewell.ca/posts/check-dns-reverse-lookups-check-dns</link>
		<comments>http://opennms.dougbakewell.ca/posts/check-dns-reverse-lookups-check-dns#comments</comments>
		<pubDate>Thu, 16 Sep 2010 19:05:51 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=815</guid>
		<description><![CDATA[Issue OpenNMS stores DNS reverse lookups for the IP addresses it discovers (iphostname column of the ipInterface table). It appears that OpenNMS only performs the DNS reverse lookup once and stores the result. Therefore, OpenNMS may never be aware of a DNS change. The DNS reverse lookup is visible in the OpenNMS web interface on the node page as &#8220;IP [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/check-dns-reverse-lookups-check-dns/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Statistics (stats)</title>
		<link>http://opennms.dougbakewell.ca/posts/stats</link>
		<comments>http://opennms.dougbakewell.ca/posts/stats#comments</comments>
		<pubDate>Tue, 14 Sep 2010 19:07:29 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=938</guid>
		<description><![CDATA[Issue As with any large system, statistics are a useful management tool. OpenNMS gives the number of nodes at the bottom of the Node List page but few other statistics are available. In particular, knowing how many interfaces and services have been discovered and are monitored would be useful. The number of active jrb files [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/stats/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Automating Critical Paths (set-critical-paths)</title>
		<link>http://opennms.dougbakewell.ca/posts/set-critical-paths</link>
		<comments>http://opennms.dougbakewell.ca/posts/set-critical-paths#comments</comments>
		<pubDate>Fri, 10 Sep 2010 19:30:40 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[Scripts]]></category>

		<guid isPermaLink="false">http://opennms.dougbakewell.ca/?p=817</guid>
		<description><![CDATA[Issue If you&#8217;ve ever had a router go down and been flooded by outage notifications for devices behind the router then you probably looked into using OpenNMS&#8217;s critical path outage feature. Critical path outages stop notifications about a node if another IP address is also not available. If properly configured, a router failure will only [...]]]></description>
		<wfw:commentRss>http://opennms.dougbakewell.ca/posts/set-critical-paths/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

