<?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>prtg | Scott Piggott</title>
	<atom:link href="https://piggott.us/tag/prtg/feed/" rel="self" type="application/rss+xml" />
	<link>https://piggott.us</link>
	<description></description>
	<lastBuildDate>Fri, 11 Sep 2009 02:39:48 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://piggottcdn.sirv.com/WP_piggott.us/2025/02/cropped-cropped-cropped-PGT3.png?w=32&#038;h=32&#038;scale.option=fill&#038;cw=32&#038;ch=32&#038;cx=center&#038;cy=center</url>
	<title>prtg | Scott Piggott</title>
	<link>https://piggott.us</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">111240843</site>	<item>
		<title>Fixing SNMP in Mac OS X Server 10.5.7</title>
		<link>https://piggott.us/2009/09/fixing-snmp-in-mac-os-x-server-10-5-7/</link>
		
		<dc:creator><![CDATA[spiggott]]></dc:creator>
		<pubDate>Fri, 11 Sep 2009 02:39:48 +0000</pubDate>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[prtg]]></category>
		<category><![CDATA[snmp]]></category>
		<category><![CDATA[snowleopard]]></category>
		<guid isPermaLink="false">http://www.spiggott.com/?p=207</guid>

					<description><![CDATA[<p>I monitor my network with PRTG Network Monitor. After recently upgrading our Xserve from 10.5.4 to 10.5.7 (server), its status changed in PRTG to &#8220;in alarm&#8221; and was unable to connect via SNMP to collect any data. It turns out that the default configuration of the SNMP agent changed with the 10.5.7 upgrade, tightening access [&#8230;]</p>
<p>The post <a href="https://piggott.us/2009/09/fixing-snmp-in-mac-os-x-server-10-5-7/">Fixing SNMP in Mac OS X Server 10.5.7</a> first appeared on <a href="https://piggott.us">Scott Piggott</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>I monitor my network with <a title="PRTG" href="http://www.paessler.com/prtg">PRTG Network Monitor</a>. After recently upgrading our Xserve from 10.5.4 to 10.5.7 (server), its status changed in PRTG to &#8220;in alarm&#8221; and was unable to connect via SNMP to collect any data. It turns out that the default configuration of the SNMP agent changed with the 10.5.7 upgrade, tightening access restrictions for the community string &#8220;public&#8221;. The fix is fairly simple. Edit line 97 of /etc/snmp/snmpd.conf and restart the SNMP daemon to reload the config file.<span id="more-411"></span></p>
<p>The default SNMP configuration in 10.5.7 and above  limits unauthenticated access to the system contact info as shown in lines 96 and 97 of /etc/snmp/snmpd.conf:</p>
<p style="padding-left: 30px; "><code># We limit unauthenticated requesters to the system contact info<br />
<strong> rocommunity public default .1.3.6.1.2.1.1.4</strong></code></p>
<p>To allow access to MIB-2 info only, edit line 97 as follows:</p>
<p style="padding-left: 30px;"><code><strong>rocommunity public default .1.3.6.1.2.1</strong></code></p>
<p>To allow unlimited access, edit line 97 as follows:</p>
<p style="padding-left: 30px;"><code><strong>rocommunity public</strong></code></p>
<p>Then restart SNMP:</p>
<p style="padding-left: 30px;"><code><strong>sudo killall -c snmpd -HUP</strong></code></p>
<p><strong>NOTE: </strong>The new default configuration of SNMP in 10.5.7 is the same in Snow Leopard.</p><p>The post <a href="https://piggott.us/2009/09/fixing-snmp-in-mac-os-x-server-10-5-7/">Fixing SNMP in Mac OS X Server 10.5.7</a> first appeared on <a href="https://piggott.us">Scott Piggott</a>.</p>]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">411</post-id>	</item>
	</channel>
</rss>
